CCMDB Wiki

Requested CCMDB changes for the next version: Difference between revisions

← Older edit
m →weird error check: removed in 2015-feb-04
mNo edit summary
 
(300 intermediate revisions by 10 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''
== Requests ==
==== after fixing the CCI page names on wiki, '''add wiki link for CCI codes in CCMDB.accdb''' ====


==Priority Bug Fix==
=== screen refresh reductions ===
=== "can't assign" error when opening patient in list ===
As part of troubleshooting Con's blinky screen Brendan suggested the following:
Como_checker crashes on opening patient in patient list; line starting with Q_str = Left goes bad if ???, but only some of the time. Wasn't able to replicate. This might be related to an error reported before that happens when many patients are deleted. Need more info...


==Important change request==
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.
* 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."
 
==APACHE ARF - add collection guideline to ccmdb.mdb==
*please add this to the APACHE screen so there is clear reminder what ARF is for APACHE. Perhaps laura can help with wording if needs to be shortened.[[User:TOstryzniuk|Trish Ostryzniuk]] 13:52, 2015 January 27 (CST)
**ARF Y only if both critieria are met: creatinine >=133 & urine output <=135 cc in 8 hr block in first 24 hrs in ICU.
 
==New change request==
* add checks
** [[! Automated Data Integrity Checks]]
** pull ahead [[Centralized_data_Vetting_Process#Check_for_problems]] checks into CCMDB where possible:
 
=== Missing Transfer Ready DtTm ===
Make sure checks run as defined in
* [["No Transfer Date" in Medicine]]
* [[Transfer_Ready_date_and_time#Medicine]]
 
* set date to discuss article with Trish for Oct 23 - Ttenbergen 16:36, 2014 October 22 (CDT)
 
* ''check_tmp_no_transfer_date''
** transfer date should not be required when moving from ward to ward
** I don't understand how we would check fro non-teaching in
** If a patient was transfer ready on teaching ward, but then move to nonteaching, then the transfer ready date on the non teaching ward is same as admit date to that ward (5 mins apart so access does not complain) ... However, a transfer date is not required for everyone sent to a non-teaching ward?


* this all is not clear to me at this point will need to look into later. Ttenbergen 16:28, 2015 January 19 (CST)
== 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 checks ready to implement
}}


== Bug Fixes ==
== Bug Fixes ==
''see [[:Category:Bugs]] and especially [[:Category:Bugs needing input]] for bugs with their own article''
''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 currently Ttenbergen 15:03, 2013 March 11 (EDT)
Flag this in the relevant pages as follows so it lists properly in [[To do list]]. See there for actual changes requested.  
* maybe updating e.g. '''pH, Temp, K, WBC''' should only be to one decimal point
WBC should only be to one decimal point.
to decimal data type with appropriate # of decimal digits. if we do those we should do the rest. Discussion email with Trish. Ttenbergen 14:26, 2014 July 31 (CDT)


=== After Ed ===
{ {Todo
* remove Ap_SapsSysBP etc after we stop sending to Ed's Ttenbergen 14:29, 2014 July 31 (CDT)
| 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 ==
== Bugs that need input ==
''See '''[[:Category:Bugs needing input]]'''. 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 [[:Category:Bugs needing input]]. 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.
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]]
=== Error when deleting many Pts and then opening next Pt ===
|?Modification date
* weird errors when deleting a pile of PTs and then opening the next Pt
|default=No corresponding old article found
** could not replicate... no idea what this is about. Does anyone get these and could provide more info?
|format=broadtable
|limit=100
|link=all
|headers=show}}


==Changes Under Discussion ==
=== renal task checks ===
* [[Check Renal Tasks]]
* [[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.  
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:  
See [[:Category:Potential Change]] as well, this are only changes without a home article.
* 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
=== Var 1 changes ===
** this and related checks are all stuck in [[Check Renal Tasks]] questions
* address [[Med_Var_1_-_Admit-from_Ward#Can.27t_enter_wards_outside_your_hospital]]
** this also shows up in [[Change_Priorities#Need_and_NDC:_for_ARF.2C_CRF_.26_Task_dialysis]]
** There are many questions in that article; if we want to proceed with this we should discuss Ttenbergen 16:36, 2014 October 22 (CDT)
 
=== Mandating colours ===
{{discussion}}
Several versions ago there was a discussion re. mandating Overstay colours. At the time Trish asked me not to make this mandatory, and I cautioned that this will lead to unreliable data. The question was not resolved. Trish, Julie, are you both OK with non-mandated Overstay colours? Ttenbergen 12:25, 2013 August 29 (CDT)
*I never said that. What is this about?  There was an email sent to you about making color visible and also about collector having to press confirm to record which color final that was posted.[[User:TOstryzniuk|Trish Ostryzniuk]] 17:11, 2013 September 19 (CDT)
** I had suggested making it mandatory for _every_ patient to have a colour before _any_ patient could be sent. At the time I understood that you were worried that this might keep collectors from sending, that there might be some legit reason they would have demographics for a patient but not yet an overstay colour. If this is no longer a concern I can implement this check. Ttenbergen 20:03, 2013 October 17 (CDT)
***I see workarounds if color is mandatory for every single patient on laptop before sending.  There are number of scenarios where staff cannot ideally complete all required data to generate a color before a send date each weel such as; vacation relief available or not, sick relief, short week due to stat days.  Minimal data set will be collected even more on paper and not entered into laptop before a send date. The data would be entered just after a send date so that sending is not impeded.  A color will be generated even if not final, just so sending is not blocked. This makes it unreliable also.  [[User:TOstryzniuk|Trish Ostryzniuk]] 17:50, 2013 October 18 (CDT)
****I agree. However, I also see bad data if there are no integrity checks. If Julie is aware of this loophole then maybe it's OK to leave it alone. Are you, Julie? {{discussion}} Ttenbergen 12:41, 2013 November 11 (CST)
* do additional error checking on the overstay questions to make sure one of each is present, or corresponding "missing"s. Ttenbergen 17:04, 2013 March 14 (EDT)
 
Related, moved from up higher...
* waiting for confirmation, likely: make it overstay colour required upon record completion unless pt is transferred. I have emailed Julie and Laura to see if there are reservations. Ttenbergen 10:32, 2014 September 8 (CDT)
* add check for Overstay colour and location before sending Ttenbergen 14:47, 2014 September 15 (CDT)
 
=== Pharmacy reference ===
=== 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  
* '''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  
Line 80: Line 67:
  | blah | blah blah  |
  | blah | blah blah  |
  ---------------------
  ---------------------
* If someone could set up the table on the wiki I will make a form with the content in the app. {{discussion}} 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.mdb.
* 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 no longer yellowing fields ===
{{Potential Change}}
apache check is no longer yellowing fields[[User:Ttenbergen|Ttenbergen]] 10:09, 10 January 2012 (CST)
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)
*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)
Line 118: 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 126: 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: Development Documentation]]
[[Category: CCMDB.mdb]]
[[Category: CCMDB.accdb]]
[[Category: Change Logs CCMDB]]
Retrieved from "https://ccmdb.kuality.ca/index.php?title=Requested_CCMDB_changes_for_the_next_version"