CCMDB Wiki

Requested CCMDB changes for the next version: Difference between revisions

← Older edit
mNo edit summary
mNo edit summary
 
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:


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.


== Bug Fix Requests ==
== integrity checks checklist ==
===Date/Time===
{{#ask: [[DICStatus::ready to implement]][[DICApp::CCMDB.accdb]] OR [[DICStatus::needs review]][[DICApp::CCMDB.accdb]]
*New version of laptop has errors in the data set rule. It is giving a null value error after you enter a time. We could before this version just type in the time and not use the :/ and now it comes up as an error.[[User:WGobert|gogogirl]] 14:38, 6 October 2009 (CDT)
|?DICStatus = Status
** Thanks for the report, and for making me aware we needed this spot for it. Chances are if you got this problem, so does everyone else, since all collectors use the same CCMDB.mdb again now. Which field are you working with when this problem arises? And, I seem to remember you guys having some involvement with eHealth over there lately. What was done? [[User:Ttenbergen|Ttenbergen]] 14:51, 6 October 2009 (CDT)
|limit=20
***It is in the registry page. Not on the temp studies when you also use a time. It seems only to really be the time field in registry page. I am not aware of issues with ehealth. No wireless yet.[[User:WGobert|gogogirl]] 15:09, 6 October 2009 (CDT)
|format=broadtable
**** OK, I am able to replicate the error and should be able to fix. [[User:Ttenbergen|Ttenbergen]] 10:19, 7 October 2009 (CDT)
|class=sortable wikitable smwtable
**** Can someone tell me if this is still a problem? I think this was fixed, just making sure. [[User:Ttenbergen|Ttenbergen]] 12:54, 29 October 2009 (CDT)
|default=No cross checks ready to implement
}}


== Improvement Requests ==
== 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
}}


=== currently none ===
== Next Round of Data Changes ==
Flag this in the relevant pages as follows so it lists properly in [[To do list]]. See there for actual changes requested.


==Changes Under Discussion==
{ {Todo
These requested changes can not be processed until the questions about them have been answered.
| 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>
}}


===ARF & CRF & ARI Integrity Check===
== Bugs that need input ==
Implement rule as per [[Renal Coding Considerations]]  
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.
{{#ask: [[Category:Bugs needing input]]
|?Modification date
|default=No corresponding old article found
|format=broadtable
|limit=100
|link=all
|headers=show}}


{{Discussion}}
=== renal task checks ===
====Discussion====
* [[Check Renal Tasks]]
There is a discussion about that rule in that article, so this check can't be implemented until the discussion is completed. Please continue discussion there to keep all in one place. [[User:Ttenbergen|Ttenbergen]] 11:00, 23 April 2009 (CDT)
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  |
---------------------


=== VAP in medicine ===
* 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)
VAP should not be coded as a complication in medicine.
** 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)


==== Discussion ====
=== apache check no longer yellowing fields ===
see [[VAP#Discussion - Coding VAP in Medicine]]
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)


== Previous requests that were not made (with reasons) ==
=== 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.


== Wikis onto laptop ==
=== prevent setting recordstatus from sent to complete ===
* '''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)
*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.


*As moved from Diagnosis Coding:
=== sending only lab/pharm sums to centralized_data.mdb ===
::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.  
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.  
::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.  
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.  
::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)
Will leave alone unless main office really wants this done... Ttenbergen 12:35, 2013 November 11 (CST)


=== Default location field to main collection location ===
There have been requests to default the location field to the main (or only) collection location.
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.
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)"
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 ===
change the settings form to have a save and a cancel button...


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


=== Facilitate exchange of patient discharge times ===
=== APACHE lab value limit change request ===
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)
*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)
* 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)
** 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)


=== Logging errors in the CCMDB.mdb ===
Add a table to the CCMDB that records every time an error is generated with the following details:
* Date/time of error
* patient ID (Hosp Loc Serial)
* Field Identifier
* error descriptor (text)
* erroneous value
Make that table sync to a central repository on send.
== After-Laptop changes ==
=== Improve Data Entry for Tasks ===
make tasks easier to enter, e.g. a checklist
[[Category: IT Instructions]]
[[Category: Questions IT]]
[[Category: Questions]]
[[Category: Development Documentation]]
[[Category: Development Documentation]]
[[Category: CCMDB.accdb]]
Retrieved from "https://ccmdb.kuality.ca/index.php?title=Requested_CCMDB_changes_for_the_next_version"