Requested CCMDB changes for the next version: Difference between revisions

From CCMDB Wiki
Jump to navigation Jump to search
mNo edit summary
 
(948 intermediate revisions by 14 users not shown)
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''
== Bug Fixes ==
* see [[Out of Memory Error]]
== Requests ==
* see also [[:Category:Bugs]]
==== after fixing the CCI page names on wiki, '''add wiki link for CCI codes in CCMDB.accdb''' ====
== Collection tool improvement requests ==
* delay till February so I can take out pharmacy at the same time:
** get rid of the pivoter for labs, has not been used in ages [[User:Ttenbergen|Ttenbergen]] 15:22, 15 December 2011 (CST)
** get rid of old error checks [[User:Ttenbergen|Ttenbergen]] 11:17, 9 January 2012 (CST)


* check that pharm_flow dates are not past discharge date or past today[[User:Ttenbergen|Ttenbergen]] 10:09, 10 January 2012 (CST)
=== screen refresh reductions ===
* check that there is only one postal code, and that it only contains characters (as in first/lastname, possibly updt that to parameter whether space and "-" and "'" are allowed)[[User:Ttenbergen|Ttenbergen]] 10:09, 10 January 2012 (CST)
As part of troubleshooting Con's blinky screen Brendan suggested the following:  
* apache check is no longer yellowing fields[[User:Ttenbergen|Ttenbergen]] 10:09, 10 January 2012 (CST)
* make sure there is a patient number for minimal data set checks [[User:Ttenbergen|Ttenbergen]] 10:14, 10 January 2012 (CST)
* make sure that function uncheck() works, as it did not for diagnoses [[User:Ttenbergen|Ttenbergen]] 11:00, 10 January 2012 (CST)


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.


=== difficult, not sure what to do ===
== integrity checks checklist ==
* fix/improve/document duplicate error msgs [[User:Ttenbergen|Ttenbergen]] 17:28, 28 July 2011 (CDT)
{{#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 checks ready to implement
}}


== [[!_Automated_Data_Integrity_Checks]] updates ==
== Bug Fixes ==
* [[Check_ORDx#Discussion]] [[User:Ttenbergen|Ttenbergen]] 17:11, 26 July 2011 (CDT)
''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
}}


== Next Round of Data Changes ==
== Next Round of Data Changes ==
none for now
Flag this in the relevant pages as follows so it lists properly in [[To do list]]. See there for actual changes requested.  
 
== Bugs that need replicating ==
In order to troubleshoot bugs in the program we need to know how they happen. There are a number of articles about known bugs we are trying to fix in the [[:category:bugs | bugs category]]. Any further feedback on these bugs might be the piece of the puzzle that allows me to fix the bug.
 
===Apache Errors remaining yellow from one patient to the next ===
I left myself the following note: "some Apache errors still remain yellow from one patient to the next [[User:Ttenbergen|Ttenbergen]] 16:15, 2 June 2011 (CDT)". I can't even imagine now how that would be, since you would have to close one patient to open another. Does anyone else know what this was all about? [[User:Ttenbergen|Ttenbergen]] 17:56, 14 July 2011 (CDT)
 
===Access allows an Admit date in the future===
{{discussion}}
*We are still finding patient with admit dates in the future.  For example Concordia recently sent a file with admit date of July 2011. This date is beyond current date.  We thought this error was already address and entry level.--[[User:TOstryzniuk|TOstryzniuk]] 12:32, 9 June 2011 (CDT)
** I have tried to reg-complete check data for a patient with a future discharge date and it will not let me. So, I can't duplicate this. Can anyone else show me how one might make this happen? Trish, is this a one-of, or have there been others? [[User:Ttenbergen|Ttenbergen]] 17:45, 14 July 2011 (CDT)
 
=== Duplicate Priority error in Dxs when there is no duplicate Dx ===
I saw on Joyce's PC an error for a duplicate diagnosis priority when there was not one. I can't duplicate the error. Is anyone else getting an error about duplicate priorities when there are none? If so, can you tell me under what conditions the error happens? [[User:Ttenbergen|Ttenbergen]] 16:58, 1 September 2011 (CDT)


==Changes Under Discussion ==
{ {Todo
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.
| 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>
}}


=== if discharged to OR or AC then there must be notes ===
== Bugs that need input ==
{{discussion}}
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.
* add check and document: if discharged to OR or AC then there must be notes. [[User:Ttenbergen|Ttenbergen]] 17:08, 16 September 2011 (CDT)
{{#ask: [[Category:Bugs needing input]]
** Why would we need a note for discharges to OR, this is common practice.   ACF discharges are not allowed.  --[[User:LKolesar|LKolesar]] 06:48, 7 October 2011 (CDT)
|?Modification date
*** If I remember right this is something we discussed at some meeting. Apparently there are cricumstances where discharge is to OR, maybe it was if a patient dies in the OR (not dying on our unit, so it's not a deceased with no discharge-to. There was also some circumstance for a discharge to AC. The original request had been to just not allow this, but since there are exceptions I had suggested that we make it a comment-required issue. Does anyone who was part of the discussion remember this? [[User:Ttenbergen|Ttenbergen]] 09:22, 7 October 2011 (CDT)
|default=No corresponding old article found
*** I didn't implement anything about this for this round of changes because I am still confused. Could someone pls clarify? [[User:Ttenbergen|Ttenbergen]] 12:42, 18 November 2011 (CST)
|format=broadtable
|limit=100
|link=all
|headers=show}}


=== automate prioritization of acquireds/complications ===
=== renal task checks ===
[[Acquired Diagnosis / Complication#Automating Priorization]]
* [[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  |
---------------------


=== Integrity rule for [[ER Wait]] dates in TMP file===
* 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)
will need to bring in details from our email exchanges. [[User:Ttenbergen|Ttenbergen]] 17:56, 2 June 2011 (CDT)
** 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)


=== QA_Infection ===
=== apache check no longer yellowing fields ===
* see [[QA_Infection#Data Integrity Rules Under Discussion ]]
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)


=== Full Apache Score ===
== Previous requests that were not made (with reasons) ==
Add full apache score to the Viewer form
=== DOB format ===
* 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)
* "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)
** 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)
** there was discussion about doing this and we decided not to to keep dates consistent throughout the program.
{{discussion}}
* What would this "full apache score" be used for? Much of the diagnostic scoring seems to be documented only in the form of a [http://ltc.umanitoba.ca/ccmdb/images/a/ab/ApacheII_MacroDX_code_map.pdf macro] which will be a mess to decipher and implement in Access. What is the benefit? [[User:Ttenbergen|Ttenbergen]] 10:48, 29 October 2010 (CDT)
* if this is implemented, Marie Laporte offered to help test this (2010-06-21) [[User:Ttenbergen|Ttenbergen]] 10:43, 27 January 2011 (CST)


=== Help to manage Serial numbers===
=== prevent setting recordstatus from sent to complete ===
If I understand right data collectors currently collect one or more locations from one or more pools of serial number pools.
*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)
Details of the serial number system are located in [[Serial number]]. This has been flagged as one reason why people find paper printouts of the most recent patients sent useful.
** actually, need to be able to do that to re-send when needed.  


Serial numbers have to be unique for a collection location, so if a ward like HSC_H4H is collected on by multiple collectors then a serial number must never be re-used. This is currently achieved by assigning blocks of numbers for each 100 possible serial numbers to a given collector (again, see [[Serial number]] for details]]).
=== sending only lab/pharm sums to centralized_data.mdb ===
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.
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.
Will leave alone unless main office really wants this done... Ttenbergen 12:35, 2013 November 11 (CST)


A serial number must be entered before any other data since access uses it to set the relationships for the data. To accomplish that, function new_pat_id() opens a window requesting the serial number pops up when "add new patient" is clicked on the patient list.
Added question to [[Serial_number#Special-Use_Serial_Numbers]] to find out if any serial numbers need to be "reserved".
==== Possible Solution 1 ====
The program would provide a default serial number. For locations with only one serial pool, this would be a one-step, transparent process. Collectors with more than one serial number pools would get a dropdown list of possible pools; upon choosing one the program would default to serial (most recent+1). Collectors using only blocks of serial numbers would have to keep track if they are "leaving" their block (e.g. if you are using only 20-39 and the program defaults to 1140, you would have to realize that and change it to 1220).
To accomplish this, the _info table would store
* variable: serial_pools, value: comma-separated list of wards
* for each ward, a variable "Serial_pool" & <ward> (e.g. Serial_pool_HSC_H4H) with the most recent value used, updated automatically by the serial wizard
{{discussion}}
* Any thoughts about this? Do you think it would/wouldn't work or be helpful? Especially, do you think collectors would consistently "catch" the ends of blocks?
**This may not work as planned as there are times when the data collector assigns a number to a patient file in her log book but is unable to use it immediately and must use numbers out of order (even though the numbers are assigned in the right order).--[[User:CMarks|CMarks]] 08:39, 30 November 2010 (CST)
==== Possible Solution 2 ====
If we are not able to provide the next number on the list, we could at least suggest it, and then do error checking on what is chosen.
Scenario: When the "Add Patient" button is clicked on the Patient List, the msg box could default to (highest serial currently on the laptop)+1. If a different number is desired, the collector could change it. This would be followed by the existing checks for a blank ID and for an existing ID. The program would then check if the ID was '''smaller''' than the largest ID already present (since some collectors use multiple indices, this error would be ignorable). The program could also check if the new Patient ID is more than “X” greater than the previous max(Pat_ID) (what would be a reasonable "X"?) (again, this error would be ignorable).
{{discussion}}
* Do you think this would be helpful? Can you see problems with this? [[User:Ttenbergen|Ttenbergen]] 14:14, 15 July 2011 (CDT)
=== Facilitating diagnosis entries ===
{{discussion}}
* As discussed at the [[Minutes_Team_Meeting_December_1%2C_2010#Restructuring_DX_codes_in_Access |Meeting]] Laura Kolesar is reviewing the names of the diagnoses we use to make it more likely that you get the right one when you start typing. Laura, any progress on this? [[User:Ttenbergen|Ttenbergen]] 19:24, 30 December 2010 (CST)
** I have put the respiratory system changes on the regional server site for Tina and Trish to review before I proceed with similiar changes to the other systems.  When you get a chance, take a look and see what you think.  --[[User:LKolesar|LKolesar]] 14:08, 21 January 2011 (CST)
*** can't find the file, could  you tell me the file name and location on the regional server? [[User:Ttenbergen|Ttenbergen]] 18:03, 14 July 2011 (CDT)
**** As per Laura file is on [[Regional Server]]\maintenance\s_alldiagnosis.mdb [[User:Ttenbergen|Ttenbergen]] 12:20, 15 July 2011 (CDT)
=== Extra "pathogens" ===
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.
Some of you are entering [[Unknown Pathogen]], and then re-check all patients with unknown pathogens before sending.
{{Discussion}}
* Actually, I don't understand how this is better than just leaving the entry as "No Value" until you know what you will put there. This way you would get an error if you tried to set the dx to complete. Can someone explain to me how a different dropdown would improve upon this? I don't see how you use this in the field, so I might be missing something. [[User:Ttenbergen|Ttenbergen]] 19:43, 30 December 2010 (CST)
Also, some of you were addressing here how long they wait for a pathogen which is not immediately available; that is discussed in the article [[Pathogens]]. Here i am wondering if additional options would make collection easier.
=== change Final_checks to dropdown to allow for more options once we start to be able to send back data ===
* add s_FinalChecks, fix all spots that use FinalCheck (or make a function to check it)
== 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 125: 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 ===
see [[Wiki onto laptops]]


=== APACHE lab value limit change request ===
=== APACHE lab value limit change request ===
Line 133: 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: Questions IT]]
[[Category: Questions]]
[[Category: Development Documentation]]
[[Category: Development Documentation]]
[[Category: Change Logs CCMDB]]
[[Category: CCMDB.accdb]]

Latest revision as of 10:00, 2023 April 27

see the 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.

integrity checks checklist

 Status
Function long LOS()needs review
Query check CCI each count vs LOSneeds review
Query check long transfer delayneeds review

Bug Fixes

see Category:Bugs and especially Category:Bugs needing input for bugs with their own article

 StatusModification date"Modification date" is a predefined property that corresponds to the date of the last modification of a subject and is provided by Semantic MediaWiki.
Bug needing input7 November 2012 22:35:09
Combiner tab re-sorts after entering5 October 2022 17:07:01
CCI Picklist tab is slow25 January 2023 16:56:36
Repeat clicks being needed when entering CCI PX Type12 March 2024 15:51:37
Error "Invalid SQL statment..." when sending12 March 2024 16:10:23
Error: There isn't enough free memory to update the display. Close unneeded programs and try again.12 March 2024 16:13:18

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. 

{ {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> 
}}

Bugs that need input

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.

 Modification date"Modification date" is a predefined property that corresponds to the date of the last modification of a subject and is provided by Semantic MediaWiki.
Bug needing input7 November 2012 22:35:09
CCI Picklist tab is slow25 January 2023 16:56:36
Combiner tab re-sorts after entering5 October 2022 17:07:01
Error "Invalid SQL statment..." when sending12 March 2024 16:10:23
Error: There isn't enough free memory to update the display. Close unneeded programs and try again.12 March 2024 16:13:18
Repeat clicks being needed when entering CCI PX Type12 March 2024 15:51:37

renal task checks

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:

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  |
---------------------
  • 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 fieldsTtenbergen 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... 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? --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.

prevent setting recordstatus from sent to complete

  • Prevent RecordStatus of Sent files being changed from Sent to Incomplete if data altered after file sent inMlaporte 15:18, 2013 December 16 (CST)
    • actually, need to be able to do that to re-send when needed.

sending only lab/pharm sums to centralized_data.mdb

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. 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. 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." ... "--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. Ttenbergen 12:44, 12 January 2011 (CST) I have, though, reduced the location list to only those wards at a given laptop's site. Ttenbergen 18:09, 14 July 2011 (CDT)

Cancel for Settings

change the settings form to have a save and a cancel button...

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

APACHE lab value limit change request

  • 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. --TOstryzniuk 12:12, 6 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. Ttenbergen 08:53, 12 July 2010 (CDT)
Retrieved from "https://ccmdb.kuality.ca/index.php?title=Requested_CCMDB_changes_for_the_next_version&oldid=159141"