CCMDB Wiki

Requested CCMDB changes for the next version: Difference between revisions

← Older edit
m Text replacement - "[[Category: " to "[[Category:"
 
Line 1: Line 1:
''see the [[:Category: Development Documentation | Development Documentation Category]] for other development logs''
''see the [[:Category: Development Documentation | Development Documentation Category]] for other development logs''
== Requests ==
==== after fixing the CCI page names on wiki, '''add wiki link for CCI codes in CCMDB.accdb''' ====


=== screen refresh reductions ===
As part of troubleshooting Con's blinky screen Brendan suggested the following:


== Bug Fixes ==
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.
None for the moment... [[User:Ttenbergen|Ttenbergen]] 14:10, 22 October 2010 (CDT)
 
== Functional Improvements ==
 
 
=== Implement mean BP calculation tool on laptop ===
It would be beneficial to put in a mean BP helper (like the ABG helper) so that we could enter our systolic and diastolic BP's and it would automatically calculate the mean BP and perhaps even indicate the higher apache score and then we could pick the worst one. This would make apache scores more accurate.
 
 
 
=== Default med pt type to "medicine"===
Set all newly entered med program patients pt type to medicine automatically for collectors to change as necessary, rather than always have to enter.  
 
 


== integrity checks checklist ==
{{#ask: [[DICStatus::ready to implement]][[DICApp::CCMDB.accdb]] OR [[DICStatus::needs review]][[DICApp::CCMDB.accdb]]
|?DICStatus = Status
|limit=20
|format=broadtable
|class=sortable wikitable smwtable
|default=No [[cross check]]s ready to implement
}}


== Bug Fixes ==
''see [[:Category:Bugs]] and especially [[:Category:Bugs needing input]] for bugs with their own article''
{{#ask: [[Category:Bugs]] [[Category:Bugs needing input]]
|?DICStatus = Status
|?Modification date
|sort=Modification date
|order=ascending
|limit=20
|format=broadtable
|link=all
|class=sortable wikitable smwtable
}}


=== Full Apache Score ===
== Next Round of Data Changes ==
Add full apache score to the Viewer form
Flag this in the relevant pages as follows so it lists properly in [[To do list]]. See there for actual changes requested.  
* That one would need thorough testing to make sure I got the score right, e.g. enter 10 patients and check if their apache scores in ccmdb are what you would have calculated. Any volunteers for the testing? If it won't be validated I'd rather not add this to confuse anyone. [[User:Ttenbergen|Ttenbergen]] 11:05, 9 June 2010 (CDT)
** Marie Laporte offered to help with this. I will let her know once I have implemented this. [[User:Ttenbergen|Ttenbergen]] 16:01, 2 July 2010 (CDT)


== Background/IT/Coding Improvements ==
{ {Todo
=== Logging errors in the CCMDB.mdb ===
| who = Tina
Add a table to the CCMDB that records every time an error is generated with the following details:
| todo_added = 2021-07-21
* Date/time of error
| todo_action =  
* patient ID (Hosp Loc Serial)
| question = Dev_CCMDB_Data / Dev_CCMDB depending on if CCMDB needs update first.  
* Field Identifier
<provide details of change>
* error descriptor (text)
}}
* erroneous value
Make that table sync to a central repository on send.


=== Changing the local data structure automatically ===
== Bugs that need input ==
Need a wayto make changes to data that is stored in \ccmdb_data\ccmdb.mdb, such as adding room numbers. By Access design, \ccmdb_program\ccmdb.mdb can not touch a linked table's structure. Will need to copy down new data structure and transfer existing data into that. This gives the opportunity to rename the data version into something less ambiguous.  
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.
If it is renamed, I'll also need to change news and backup file.  
{{#ask: [[Category:Bugs needing input]]
|?Modification date
|default=No corresponding old article found
|format=broadtable
|limit=100
|link=all
|headers=show}}


==== Data changes ====
=== renal task checks ===
When the trick to change the local data is figured out, do the following:  
* [[Check Renal Tasks]]
* why is the DOB defaulted to today?
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.
* add a field for room number to list (update [[Patient List]] when done)
Also related to this:  
* store the ABG calculation table locally (sL_AaDO2 values)
* 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."
===== Final Check into drop-down =====
** right now this could go through
Make final check into a drop down to comply with requirement for stating the status within the process of data once we store data on U of M. [[User:Ttenbergen|Ttenbergen]] 13:25, 8 December 2009 (CST)
** this and related checks are all stuck in [[Check Renal Tasks]] questions
* change can not be made via ccmdb.mdb since table structure for linked tables (as used by laptops) can not be manipulated externally.
** this also shows up in [[Change_Priorities#Need_and_NDC:_for_ARF.2C_CRF_.26_Task_dialysis]]
** option: Have ccmdb.mdb automatically generate a new .mdb based on the changes, and then change linking to that new .mdb
=== Pharmacy reference ===
* still required: change every spot that deals with finalcheck to deal with record_status instead. Easiest might be to make it a function finalcheck = (record_status = "CollectComplete")
* '''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  |
---------------------


* 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)
** 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.
*** 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)


=== apache check no longer yellowing fields ===
apache check is no longer yellowing fields[[User:Ttenbergen|Ttenbergen]] 10:09, 10 January 2012 (CST)
*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)
**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)
***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)
**** been a while, I'll review and let you know what this is about. Ttenbergen 13:55, 2013 January 29 (EST)


==Changes Under Discussion==
== Previous requests that were not made (with reasons) ==
These requested changes can not be processed until the questions about them have been answered. Wherever possible the discussion should conclude in the home article of the topic. If a topic has no home article, it can be listed here.
=== DOB format ===
* "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)
** there was discussion about doing this and we decided not to to keep dates consistent throughout the program.  


=== Counting Date Tracker ===
=== prevent setting recordstatus from sent to complete ===
One of the reasons some people keep paper is that they track on paper when they have last looked at labs etc so they know where to count from next time they review the chart. At some locations people put ticks in the charts to note how far they have collected, but at other locations that isn't done. I am not sure why...
*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)
I have had a suggestion that adding date/time fields to the program that would set to "now" upon double-clicking them would mean one more thing tracked in the .mdb rather than on paper. These fields would not be mandatory and they would not be sent in, they would just be for your own use.  
** actually, need to be able to do that to re-send when needed.  
Suggested date/times were:
*LAST COUNTED LABS
*LAST COUNTED EKG
*LAST COUNTED CXR
*LAST COUNTED PHARM
*CHART REVIEWED


==== Usefulness? ====
=== sending only lab/pharm sums to centralized_data.mdb ===
{{Discussion}}
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.
* Would your location use this or do you put checks on charts? Or, do you have an entirely different way you keep track of this?
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.
**I might use this but I put ticks in the chart so I know which labs I have counted.--[[User:MWaschuk|MWaschuk]] 17:43, 9 June 2010 (CDT)
Will leave alone unless main office really wants this done... Ttenbergen 12:35, 2013 November 11 (CST)
** We would not use this at STB because we utilize electronic chart to count labs at the end of a patient stay. --[[User:LKolesar|LKolesar]] 14:56, 10 June 2010 (CDT)
*** Laura, this is not just for Labs, do you get the other fields out of the electronic chart as well? [[User:Ttenbergen|Ttenbergen]] 15:37, 22 October 2010 (CDT)


==== Any problems/disadvantages implementing this? ====
{{Discussion}}
Trish (or anyone): Can you see any concerns if this were implemented? Would we automate something that could be done easier, or maybe doesn't need to be done at all? Any thoughts along that line? [[User:Ttenbergen|Ttenbergen]] 15:37, 22 October 2010 (CDT)
=== Facilitate exchange of patient discharge times ===
We discussed at the last collection meeting that we should provide the collectors with a tool to facilitate exchanging admit/discharge info. We discussed whether to include Comos etc. in this, and it was decided not to - Julie will from now on treat ANY como on this admisssion as a como for all subsequent ward stays on that admission. (see also [[Admit, Transfer and Discharge date and time]])
{{discussion}}
Trish - did I get that right, shall we proceed? [[User:Ttenbergen|Ttenbergen]] 14:59, 20 October 2010 (CDT)
=== Limited Labs List ===
We are gearing towards changing the lab lists, see new lab list at [[S AllLabsTable Ver2]]. 
{{Discussion}}
* Trish, is this to be implemented once possible, or do we need a discussion with collectors and a go-ahead from you? [[User:Ttenbergen|Ttenbergen]] 15:44, 2 July 2010 (CDT)
** I was under the impression that we could collect the reduced number of labs. Why should this be delayed?  It is just more work for no benefit.  --[[User:LKolesar|LKolesar]] 13:57, 1 October 2010 (CDT)
***Trish? [[User:Ttenbergen|Ttenbergen]]
==== Make a better labs entry system ====
Once reduction of number of labs collected is official and down to as many as can be, I will make it so the labs are entered in a pre-populated list. [[User:Ttenbergen|Ttenbergen]] 15:16, 2 July 2010 (CDT)
{{discussion}}
*Can you make it so the lab list does not mix up the priority numbers. Makes it hard to add new ones without using same number twice.[[User:LBilesky|LBilesky]] 08:23, 22 October 2010 (CDT)
** I am not sure what you mean. How is it mixing up any priorities? [[User:Ttenbergen|Ttenbergen]] 13:19, 22 October 2010 (CDT)
***I have run into the same problem. Seems once the file is closed and then reopened the lab list has sorted the labs alphabetically (not numerically by priority number)[[User:Mlaporte|Mlaporte]] 15:16, 22 October 2010 (CDT)
=== Tasks ===
For a long time now there have been requests to make the Tasks more of a drop-down, similar to the ADLs, or a checklist like the greensheets used to be. This is a mess to implement, since it doesn't correspond to the data structure this is stored in.
An alternative might be to automatically enter the five tasks as "blanks" for every new medicine patient. I would make 5 new tasks entries that would sort before each of the 5 existing options. This would be similar to a checklist in that the records are already there, and only would need to be edited.
{{discussion}}
I can not think of any data or process drawbacks of doing this... can anyone else? If I hear no issues by the time I get to this round of changes I will implement this.[[User:Ttenbergen|Ttenbergen]] 11:09, 20 October 2010 (CDT)
*Do you mean they will automatically pop up as negatives ie:no trach, no hemodialysis etc. and if the pt is on anything then we would change the task to reflect this? If so I think this would help.--[[User:CMarks|CMarks]] 14:50, 21 October 2010 (CDT)
** That is what I mean. Trish/Julie, do you think there would be a problem with this defaulting? [[User:Ttenbergen|Ttenbergen]] 13:20, 22 October 2010 (CDT)
=== get rid of old buttons ===
'''Unless I hear that there is still use for this button, I will remove both the "Edit Patients" button and the filter button from CCMDB.mdb in the next round of changes.''' Speak now or forever hold your peace if you think there would be a problem with this.
Note: [[Sending_Patients#Historical:Filtering_for_complete_patients]] needs to be fixed after this change.
*We use these buttons before sending files here at HSC otherwise we are unable to edit patients and filter completes.--[[User:CMarks|CMarks]] 08:08, 18 October 2010 (CDT)
**We use them at STB also it is handy to filter the completes especially when you are sending many profiles.  --[[User:LKolesar|LKolesar]] 11:55, 18 October 2010 (CDT)
{{discussion}}
When we had the PDAs, we needed to check the complete patients only at sending time since the PDAs could not do it as you go along. Now that we are collecting in Access all along, we no longer need to wait and batch this check for send day. Is there any reason  to not set a patient to "final checked" when you are finished collecting them? When final-check is clicked a bunch of tests run, so doing this when you still have the chart in front of you would save a trip back later.
Checking patient over at send time seems like an extra step that doesn't add any value any longer. Should we continue to do this? Trish, this probably requires input from you. [[User:Ttenbergen|Ttenbergen]] 11:09, 20 October 2010 (CDT)
=== Facilitating diagnosis entries ===
I have had various requests to make it faster or easier to enter diagnoses. A lot of those requests would be addressed with more training on the various ways diagnoses can be entered. I have added a fair bit of functionality, but there may not have been enough training on this yet. '''Trish, before I add much functionality here, could you put me on the next meeting agenda for 15 minutes to show/tell/discuss diagnoses entries. '''
{{Discussion}}
I discussed with Fran and Con that, if there were groups of diagnoses that often go together, it might be possible to combine them somehow. I could add a limited number of buttons to e.g. put in "cardiovascular- Hypertension, MI, hypercholesterol, etc." as requested by Con. Could collectors provide a list of dx groups for which this would be useful?
* (button name?): cardiovascular- Hypertension, MI, hypercholesterol,
=== extra "pathogens" ===
--[[User:MWaschuk|MWaschuk]] 17:46, 9 June 2010 (CDT)
As part of an effort to reduce relying on paper notes during collection, Marie brought up the possibility to put ''"waiting for tests"'' and ''"review"'' as options into the pathogen dropdown and to conditional-format the field in orange if they are chosen. Of course, choosing them would also disable checking DX complete.
{{Discussion}}
* Would anyone else find this useful? Should it be included in the Master DB? [[User:Ttenbergen|Ttenbergen]] 17:34, 9 February 2010 (CST)
** Yes, I would find this useful
***I usually put unknown pathogen in my pathogen slot if waiting for results, then when rechecking the profile upon discharge, I re-check on the EPR for results again. If still no results, I generally do not hold the profile longer. I wonder what our policy should be on this.  How long should we hold a profile for possible results?  This could back up our flow of profiles quite a bit.  What does everyone think?--[[User:LKolesar|LKolesar]] 15:08, 10 June 2010 (CDT)
=== Changes to the ccmdb.mdb to reduce reliance on paper ===
The "extra pathogens" entry above makes me wonder: are there other features collectors can think of that would suddenly make it more desirable to enter data electronically in the first place rather than on paper? This question really only applies to the access program (e.g. to laptop users) since we are phasing out the PDAs and I am not going to make any modifications to them because they cause cascading problems.
{{discussion}}
* Any thoughts? [[User:Ttenbergen|Ttenbergen]] 17:34, 9 February 2010 (CST)
== Bugs that need replicating ==
In order to troubleshoot a bug we need to know a way to "make it happen". This section contains bugs that have been reported but can not be demonstrated on demand.
=== [[WBC]] = 0 does not uncheck apache box ===
As per email from Pagasa, and confirmed by Tina, 28 jan 2010 [[User:Ttenbergen|Ttenbergen]] 14:32, 28 January 2010 (CST)
There may also still be a problem with sending very low numbers. Lois apparently thought she entered and sent WBC with a value of 0.02, which CCMDB.mdb should accept, but may not send properly. [[User:Ttenbergen|Ttenbergen]] 12:58, 29 January 2010 (CST)
==== How to demonstrate this bug ====
{{discussion}}
*Anyone?[[User:Ttenbergen|Ttenbergen]] 12:25, 12 April 2010 (CDT)
**HSC-MICU-Batch 22 sent June 2.10. See Pagasa Email sent June 3.10.  Will double check if it is the uploader program.  If value 0.02.
**I checked Lois original csv and WBC value entered was .02 but when I appended it tells me that incomplete apache score but after I appended it showing  blank on Ed's program.[[User:PTorres|PTorres]][User:PTorres|PTorres]] --[[User:TOstryzniuk|TOstryzniuk]] 17:27, 8 June 2010 (CDT)
*** Trish, have you been able to find out if this goes wrong in the uploader? [[User:Ttenbergen|Ttenbergen]] 16:19, 2 July 2010 (CDT)
****Yes, PDA uploader for ICU is not reading in a WBC value of 0.02 for WBC. Problem shipped over Programmer today.--[[User:TOstryzniuk|TOstryzniuk]] 14:52, 22 October 2010 (CDT)
=== Infection without pathogen subcode was sent to csv ===
Oaks - Patient coded for Cystitis Bladder Infection but no sub code? Admit date Jan 25/10-Jan. 30/10. Pagasa Torres.
Patient coded for Cystitis Bladder Infection but no sub code; Admit date Jan 25/10-Jan. 30/10.
Asked Wendy if there was any extraordinary edits for this pt, and she replied
"Nope and I too am surprised as it has always been caught if I miss it in the Edit Patients pane??? I just simply forgot as I was awaiting the results...have no idea how it got sent???"
==== How to demonstrate this bug ====
{{discussion}}
*Anyone? [[User:Ttenbergen|Ttenbergen]] 16:59, 9 February 2010 (CST)
=== Tasks not being sent ===
Occasionally Medicine TASK items don't get sent to the task.mdb. Need a way to flag this. [[User:Ttenbergen|Ttenbergen]] 15:53, 2 July 2010 (CDT)
* {{discussion}}How frequent of a problem is this, has it recurred since this was documented? [[User:Ttenbergen|Ttenbergen]] 11:09, 20 October 2010 (CDT)
**there has been no further reported problems from Pagasa or Julie since this was documented.  --[[User:TOstryzniuk|TOstryzniuk]] 15:24, 20 October 2010 (CDT)
==== How to demonstrate this bug ====
{{discussion}}
*Anyone? [[User:Ttenbergen|Ttenbergen]] 12:16, 22 October 2010 (CDT)
== Previous requests that were not addressed (with reasons) ==
=== Default location field to main collection location ===
=== Default location field to main collection location ===
There have been requests to default the location field to the main (or only) collection location.  
There have been requests to default the location field to the main (or only) collection location.  
Line 187: Line 98:
Upon consultation with Trish it was decided not to risk an increase in errors to make this more convenient.  
Upon consultation with Trish it was decided not to risk an increase in errors to make this more convenient.  
* "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)"
* "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)"
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)
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)


=== Cancel for Settings ===
=== Cancel for Settings ===
Line 192: Line 105:


No can do. There are is a sb-form in settings form that would not be cancelled, so having a cancel would be misleading.  
No can do. There are is a sb-form in settings form that would not be cancelled, so having a cancel would be misleading.  
=== Off-line copy of wiki for laptop ===
We found a way to do this, but it would add overhead work to the collectors' job and it would deter from using the wiki as a tool owned and updated by all, so Trish and Tina decided not to pursue this further.  [[User:Ttenbergen|Ttenbergen]] 15:01, 16 April 2010 (CDT)
* 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)
*As moved from Diagnosis Coding:
::A suggestion has been put forth to Tina is to find a away to allow a downloaded copy of the WIKI guide on laptops, the collection tool we are moving to soon.    I think this would be an excellent solution if she can do this.    Collectors would then be able to search for info no matter where they are in the collection field and each time they synch there laptop, they would get updated WIKI items.  That is the plan............but waiting to here from IT support.
::It is challenge right now in that the guideline information is not easily and quickly accessible while you are doing your work in the unit or in medical records.  Most collectors must run back to their office or find a free computer to log in and look up guide info.   
::Keep in mind, guide information changes regularily, so what you print out one day is outdated the next for a number of articles. [[User:TOstryzniuk|TOstryzniuk]] 11:25, 29 April 2009 (CDT)
*April 2010 - Trish and Tina reviewed the apparent option to have a COPY of wiki on laptop.  Problem if implemented:
# if collectors will not have the most update the copy on laptop because changes and updates are happening daily on the MAIN copy here, and thus changes to instruction will get missed.
#2. Don't want multiple copies of instruction and information on multiple laptops that are not up to date.
#Collector questions and contribution to the Wiki cannot be added to copy of Wiki on laptop.  Questions and contribution must be made centrally not locally so that information is in ONE PLACE and the same for everyone.--[[User:TOstryzniuk|TOstryzniuk]] 19:11, 20 April 2010 (CDT)


=== APACHE lab value limit change request ===
=== APACHE lab value limit change request ===
Line 211: Line 110:
** 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)
** 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)


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