CCMDB Wiki

Requested CCMDB changes for the next version: Difference between revisions

← Older edit
TOstryzniuk (talk | contribs)
CCMDB_legit, approved, Bureaucrats, Administrators
27,522 edits
mNo edit summary
 
Line 1: Line 1:
== Requested CCMDB '''changes''' for the ''next version'' ==
''see the [[:Category: Development Documentation | Development Documentation Category]] for other development logs''
* see [[CCMDB.mdb Change Log 2009]] for changes that have been rolled out to sites.
== Requests ==
==== after fixing the CCI page names on wiki, '''add wiki link for CCI codes in CCMDB.accdb''' ====


=== Updates required for Laptops ===
=== screen refresh reductions ===
* automate the backup to the [[Regional Server]]
As part of troubleshooting Con's blinky screen Brendan suggested the following:  
* automate a backup to the SD card
* automate checking for new front-end on every log in to the network
* Must be able to enter new files into[[CCMDB.mdb | Access]]
* look into possibility of automatically downloading WIKI guide to laptop each day that it is synch'd.  (portable version of guideline)--[[User:TOstryzniuk|TOstryzniuk]] 20:11, 4 April 2009 (CDT)


=== QA Functionality ===
There’s code you can put in, I forget what the commands actually are, but it turns off the screen refresh during functions so the user doesn’t see what’s happening. You’d turn the refresh off before the function starts, they’ll see a static screen until you tell it to turn the refresh on, where the screen will then load just one time and all of the new info, all the rows, any formatting, or populating, etc.. is done. Instead of refreshing 10 or 20 times, once for each row.


==== Facilitate exchange of patient discharge times ====
== integrity checks checklist ==
DCs have to know the discharge times for patients arriving at their wards from another collected ward. We should automate that rather than have them exchange manually. Might be an extension of the status file for Julie...[[User:Ttenbergen|Ttenbergen]] 16:05, 3 February 2009 (CST)
{{#ask: [[DICStatus::ready to implement]][[DICApp::CCMDB.accdb]] OR [[DICStatus::needs review]][[DICApp::CCMDB.accdb]]
* moved a note into [[Admit, Transfer and Discharge date and time]], as this is unrelated to updates to the program. [[User:Ttenbergen|Ttenbergen]] 09:27, 11 February 2009 (CST)
|?DICStatus = Status
|limit=20
|format=broadtable
|class=sortable wikitable smwtable
|default=No cross checks ready to implement
}}


==== Logging errors in the CCMDB.mdb ====
== Bug Fixes ==
Add a table to the CCMDB that records every time an error is generated with the following details:  
''see [[:Category:Bugs]] and especially [[:Category:Bugs needing input]] for bugs with their own article''
* Date/time of error
{{#ask: [[Category:Bugs]] [[Category:Bugs needing input]]
* patient ID (Hosp Loc Serial)
|?DICStatus = Status
* Field Identifier
|?Modification date
* error descriptor (text)
|sort=Modification date
* erroneous value
|order=ascending
Make that table sync to a central repository on send.
|limit=20
|format=broadtable
|link=all
|class=sortable wikitable smwtable
}}


===Defer or in Discussion===
== Next Round of Data Changes ==
====ARF & CRF & ARI Integrity Check====
Flag this in the relevant pages as follows so it lists properly in [[To do list]]. See there for actual changes requested.
*if [[CRF - Chronic Renal Failure|CRF (351)]] in comorbid then [[ARF]] (Diagnosis (350) or [[ARI]] (364) cannot be in admit or complication. (see [[CRF vs ARF, ARI, Renal Transplant]])


{{Discussion}}
{ {Todo
| who = Tina
| todo_added = 2021-07-21
| todo_action =
| question = Dev_CCMDB_Data / Dev_CCMDB depending on if CCMDB needs update first.
<provide details of change>
}}


=====Discussion=====
== Bugs that need input ==
* The 364 is new since the discussion about the cleaner. What is it about? [[User:Ttenbergen|Ttenbergen]] 15:55, 5 November 2008 (CST)
In order to troubleshoot bugs in the program we need to know how they happen. Any further feedback on these bugs might be the piece of the puzzle that allows me to fix the bug. If you find a new bug, you please document it.
**Yes, since I have been further reviewing patient profiles in more detail from the problems that SAS has generated, I see renal insufficiency (364)being coded in admit or complication DX slots for patients who have a comorbid condition of chronic renal failure (351).
{{#ask: [[Category:Bugs needing input]]
*The article [[CRF vs ARF, ARI, Renal Transplant]] also mentions something about transplant. Is that still accurate? [[User:Ttenbergen|Ttenbergen]] 14:12, 18 February 2009 (CST)
|?Modification date
|default=No corresponding old article found
|format=broadtable
|limit=100
|link=all
|headers=show}}


=== renal task checks ===
* [[Check Renal Tasks]]
There are some possible changes identified that either need to be flagged as needing to be done, or where there is still a discussion going on.
Also related to this:
* confirm "if LOS <3 days and 350 in admit or acq or if 351 in com orbit, then a dialysis TASK item is ok not to be marked."
** right now this could go through
** this and related checks are all stuck in [[Check Renal Tasks]] questions
** this also shows up in [[Change_Priorities#Need_and_NDC:_for_ARF.2C_CRF_.26_Task_dialysis]]
=== Pharmacy reference ===
* '''reference sheet''' - some suggested we add a reference sheet. I could make a button on that screen to bring up a reference sheet. Problem is that would be at least the ''third'' copy of this information, leading to problems maintaining consistency. I would be willing to do it if we change the table with the info on the wiki to a plain-text formatted table that I can directly copy-and-paste into Access, e.g. something like
---------------------
| test | second test|
---------------------
| blah | blah blah  |
---------------------


==== Ensure that date/time formats are explicit ====
* If someone could set up the table on the wiki I will make a form with the content in the app. Any volunteers? I could add this to the next version easily. Ttenbergen 16:41, 2013 April 24 (EDT)
Make sure that Access explicitly looks for the format set out in [[Date and Time Format]], rather than using the PC format.
** No news in about a month. If anyone is interested in making that list, let me know and I'll put it into the CCMDB.accdb.
{{Discussion}}
*** No one ever volunteered to provide the sheet, so taking out the question. If someone is willing to work on this, please add a discussion back in. Ttenbergen 19:39, 2019 November 13 (CST)
=====Discussion=====
*Right now [[CCMDB.mdb]] uses dd-mmm-yyyy, e.g. 12 Jan 2009. This is less ambiguous than the standard set out on the wiki. I think it's the better option since it eliminates the chance for transposition errors. I think we should use this format for collection. This does not affect how it is sent to Ed, or how it is stored in Ed's program. If Trish is OK with this, this section should be removed from the change log and [[Date and Time Format]] should be updated accordingly. [[User:Ttenbergen|Ttenbergen]] 12:58, 12 February 2009 (CST)


====take out Autopsy YES OR NO====
=== apache check no longer yellowing fields ===
*ACCESS program is affected because of the way S or E is tied to autopsy on PDA.
apache check is no longer yellowing fields[[User:Ttenbergen|Ttenbergen]] 10:09, 10 January 2012 (CST)
*PDA Reader or master database utility programs are not affected if this field is left BLANK.
*yes, it is no longer yellowing the field, just the error box below. Can't find trace of the code, and not sure when it was changed. Ponder whether to re-instate, error checking is still being called and still prevents sending... [[User:Ttenbergen|Ttenbergen]] 17:13, 2012 January 31 (CST)
[[User:TOstryzniuk|TOstryzniuk]] 16:29, 12 December 2008 (CST)
**Do we want to re-implement this? Would take a few days of coding I think, so I haven't done it. Ttenbergen 16:58, 2012 October 1 (CDT)
*'''Approved, leave blank'''.[[User:TOstryzniuk|TOstryzniuk]] 05:24, 19 January 2009 (CST)
***not sure what you mean no longer yellowing fields.  Do you mean where there is an error (limit) or missing data that is not yellowing? --[[User:TOstryzniuk|Trish Ostryzniuk]] 19:13, 2013 January 28 (EST)
{{Discussion}}
**** been a while, I'll review and let you know what this is about. Ttenbergen 13:55, 2013 January 29 (EST)
=====Discussion=====
Julie and Dr. Garland are currently working on moving the whole survive/expire issue into a "Dispo" field. I suggest we wait until they are done rather than implementing this twice. The advantage is that their change will use a data approach (discharge-to has a table) whereas editing the survive/expire options would be a manual change on HanDBase (notoriously unreliable). [[User:Ttenbergen|Ttenbergen]] 13:56, 10 February 2009 (CST)


====APACHE II Screen====
== Previous requests that were not made (with reasons) ==
*get rid of fields that are not long being collected on the APACHE II screen (SAPS II items).
=== DOB format ===
*total Bilirubin, CPAP, urine CC;s, Urea,SAP_Systolic,
* "when you create a new profile and have to fill in the DOB it is backwards to what is written in the chart, so when we go to enter the DOB we have to stop and  think about it to enter it in our computer.  It is written in all chart as day/month/year,  we use to be able to enter it that way and it would automatically fall into place" - Pat 09:29, 2013 December 19 (CST)
*also - eliminate APACHE II Active TX field.
** there was discussion about doing this and we decided not to to keep dates consistent throughout the program.  
{{Discussion}}


=== prevent setting recordstatus from sent to complete ===
*Prevent RecordStatus of Sent files being changed from Sent to Incomplete if data altered after file sent in[[User:Mlaporte|Mlaporte]] 15:18, 2013 December 16 (CST)
** actually, need to be able to do that to re-send when needed.


====[[Registry Patient Type]] - eliminate this field====
=== sending only lab/pharm sums to centralized_data.mdb ===
*The Access program is affected because it requires this field to be filled in before sending is allowed.
All the info that is actually needed in centralized is the sum of labs and pharmacy. Was hoping to send only that, but it would complicate synching with collector laptops while adding little value, so not doing that for now.  
*PDA Reader or master database utility programs are not affected if this field is left BLANK
We could re-visit this if it is a problem, or if those files get unwieldy large. Also, could run a "summarizer" across those files for complete records only.
*needs to be approved by Critical Care before implementation of change.
Will leave alone unless main office really wants this done... Ttenbergen 12:35, 2013 November 11 (CST)
[[User:TOstryzniuk|TOstryzniuk]] 16:29, 12 December 2008 (CST)
*'''approved''', leave blank. [[User:TOstryzniuk|TOstryzniuk]] 05:27, 19 January 2009 (CST)
{{Discussion}}
=====Discussion=====
This can be removed in Access and in the output, but I would suggest leaving it alone on the PDA for now due to HanDBase. Access would no longer check for it. If that is OK, this can be moved to "Checks and Updates".[[User:Ttenbergen|Ttenbergen]] 14:00, 10 February 2009 (CST)


====APACHE II ACTIVE TX-eliminate this====
=== Default location field to main collection location ===
*ACCESS program is affected because it makes this a required field (though my understanding is that many data collectors have set default for boxed to be checked).
There have been requests to default the location field to the main (or only) collection location.  
*PDA Reader or master database utility programs are not affected if this field is left BLANK
I could set this up, but defaulting these would increase the chances of the data just being left in there if a patient is an exception.
*needs to be approved by Critical Care before implementation of this change
Upon consultation with Trish it was decided not to risk an increase in errors to make this more convenient.
[[User:TOstryzniuk|TOstryzniuk]] 16:29, 12 December 2008 (CST)
* "There are a number of site collecting on 2 or more units using the same laptop.  We get ward location entry error when there is a default location set."  ... "--[[User:TOstryzniuk|TOstryzniuk]] 12:25, 20 October 2010 (CDT)"
*Approved, leave blank.   [[User:TOstryzniuk|TOstryzniuk]] 05:25, 19 January 2009 (CST)
PS: If I enable defaulting for anywhere then I would not be able to disable defaulting for other locations, so it was decided not to have defaulting. [[User:Ttenbergen|Ttenbergen]] 12:44, 12 January 2011 (CST)
{{Discussion}}
I have, though, reduced the location list to only those wards at a given laptop's site. [[User:Ttenbergen|Ttenbergen]] 18:09, 14 July 2011 (CDT)
=====Discussion=====
* are you saying that ccmdb.mdb will not allow sending a pt with unchecked active tx? [[User:Ttenbergen|Ttenbergen]] 14:25, 11 February 2009 (CST)
**YES.[[User:TOstryzniuk|TOstryzniuk]] 13:35, 9 March 2009 (CDT)


====s_Fi02 table in Handibase====
=== Cancel for Settings ===
*The S_FI02  (note: with a zero rather than a capital o) is a relic we have been unable to get rid of due to technical problems. It is the mis-spelled table name for S_FIO2 (i.e. capital o). Nothing can be done about it until the PDAs are all gone, so this should be taken out of the change log. (see [[S FI02]] for details; remove the link from there if this is taken out of here.)
change the settings form to have a save and a cancel button...
[[User:Ttenbergen|Ttenbergen]] 13:30, 10 February 2009 (CST)


No can do. There are is a sb-form in settings form that would not be cancelled, so having a cancel would be misleading.


==== Ensure discharge time = 0:00 can't get through ====
=== APACHE lab value limit change request ===
to implement check mentioned in [[Admit, Transfer and Discharge date and time]] but not currently working
*Apache upper limit for creatinine is 2968, which is based on the highest APACHE that was ever in database.  STB has one pt with a creat of 3000 and has requested to change upper limit.  Laura K. --[[User:TOstryzniuk|TOstryzniuk]] 12:12, 6 July 2010 (CDT)
{{Discussion}}
** Decided to leave limits be and have collectors enter limit values and email Pagasa with real values when extreme values are encountered. Contacted Pagasa to let us know if such emails become too frequent. [[User:Ttenbergen|Ttenbergen]] 08:53, 12 July 2010 (CDT)
=====Discussion=====
* Check appears to be working for Admit and Discharge. Can't run check for Transfer time because transfer time is not mandatory. If there is a bug in this, please describe. [[User:Ttenbergen|Ttenbergen]] 12:47, 18 February 2009 (CST)


 
[[Category: Development Documentation]]
 
[[Category: CCMDB.accdb]]
[[Category: IT Instructions]]
[[Category: Questions IT]]
[[Category: Questions]]
Retrieved from "https://ccmdb.kuality.ca/index.php?title=Requested_CCMDB_changes_for_the_next_version"