Requested CCMDB changes for the next version: Difference between revisions

From CCMDB Wiki
Jump to navigation Jump to search
Line 4: Line 4:
Access Query sort for MR LIST: Can you please add to query for MR list to also be be sorted by DISCHARGE date so that the oldest DISCHARGE is first on the list and the most current discharges are last on the list.  This would apply for MR list sorted by ID or the MR sorted by FN or LN. Data collection Priority is: overstay, minimal dataset followed by completion of oldest discharges rather than most current discharges. List organized by oldest discharge date first would then allow collectors to submit priority list to MR rather than writing them out by hand to ensure order oldest dates first. [[User:TOstryzniuk|Trish Ostryzniuk]] 19:11, 2013 January 28 (EST)
Access Query sort for MR LIST: Can you please add to query for MR list to also be be sorted by DISCHARGE date so that the oldest DISCHARGE is first on the list and the most current discharges are last on the list.  This would apply for MR list sorted by ID or the MR sorted by FN or LN. Data collection Priority is: overstay, minimal dataset followed by completion of oldest discharges rather than most current discharges. List organized by oldest discharge date first would then allow collectors to submit priority list to MR rather than writing them out by hand to ensure order oldest dates first. [[User:TOstryzniuk|Trish Ostryzniuk]] 19:11, 2013 January 28 (EST)
* ability to sort like this is already available in the patient list. What are we actually trying to do here? Ttenbergen 14:20, 2013 January 31 (EST) {{discussion}}
* ability to sort like this is already available in the patient list. What are we actually trying to do here? Ttenbergen 14:20, 2013 January 31 (EST) {{discussion}}
*sort so that OLDEST discharge DATE are always first on the list.-[[User:TOstryzniuk|Trish Ostryzniuk]] 17:54, 2013 February 4 (EST)
*No it is not.  We need to sort so that OLDEST discharge DATE are always first on the list.-[[User:TOstryzniuk|Trish Ostryzniuk]] 17:54, 2013 February 4 (EST)


== Bug Fixes ==
== Bug Fixes ==

Revision as of 17:57, 2013 February 6

see the Development Documentation Category for other development logs

New change request

additional MR List options

Access Query sort for MR LIST: Can you please add to query for MR list to also be be sorted by DISCHARGE date so that the oldest DISCHARGE is first on the list and the most current discharges are last on the list. This would apply for MR list sorted by ID or the MR sorted by FN or LN. Data collection Priority is: overstay, minimal dataset followed by completion of oldest discharges rather than most current discharges. List organized by oldest discharge date first would then allow collectors to submit priority list to MR rather than writing them out by hand to ensure order oldest dates first. Trish Ostryzniuk 19:11, 2013 January 28 (EST)

  • ability to sort like this is already available in the patient list. What are we actually trying to do here? Ttenbergen 14:20, 2013 January 31 (EST) Template:Discussion
  • No it is not. We need to sort so that OLDEST discharge DATE are always first on the list.-Trish Ostryzniuk 17:54, 2013 February 4 (EST)

Bug Fixes

  • with reg already checked, was able to change discharge date to a future date and it didn't uncheck initially; it did catch on trying to final-check, so this is a low-grade bug, just should be fixed eventually. Only way for a bad date to go through is if it were changed after final-check had already been set. Ttenbergen 20:37, 2012 November 1 (EDT)
  • able to uncheck checkboxes without finalcheck unchecking. Need to determine if this could lead to bad data going through. Ttenbergen 14:45, 2012 May 22 (CDT)
  • if an error handler turns the dx tab yellow this is not automatically reset when a new patient is opened. Ttenbergen 13:15, 2012 October 31 (EDT)

New projects

Collection tool improvement requests

  • Would it be possible to have a line showing the cumulative totals of treatment days for the Pharm drugs collected in this field? (as in Labs)10:04, 2012 December 21 (EST)
    • How would this help with collection? I am asking to find out if there might be more to it. For example, are you trying to compare the summary to something else, maybe that can be built in as well. I just need to understand how you would use this. Ttenbergen 10:14, 2012 December 21 (EST)

Next Round of Data Changes

  • make sure that the updater works if there is no network connection on first opening Access. likely will require the copying of the new data file to happen in the news.batch instead, so would need to update that. Ttenbergen 15:11, 2012 July 4 (CDT)

Bugs that need replicating

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.

Changes Under Discussion

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.

See Category:Potential Change as well, this are only changes without a home article.

apache check no longer yellowing fields

Template:Potential Change

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 addressed (with reasons)

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.

Off-line copy of wiki for laptop

see Wiki onto laptops

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)