|
|
| Line 47: |
Line 47: |
| ** this and related checks are all stuck in [[Check Renal Tasks]] questions | | ** 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]] | | ** this also shows up in [[Change_Priorities#Need_and_NDC:_for_ARF.2C_CRF_.26_Task_dialysis]] |
| === 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 |