Requested CCMDB changes for the next version

From CCMDB Wiki
Jump to navigation Jump to search

see the Development Documentation Category for other development logs see TISS28.mdb Change Log for TISS28 Access Program changes

Priority Bug Fix

Bug - Incomplete patients are being set to "sent" in Centralized data.mdb - likely fixed.

Important change request

  • Make sure that a .csv will not be overwritten with same name file.
  • change sent to use the same sent time for all records; right now it may tick over to a new second.
    • I think making a global variable, setting it in sending, and then calling it from query may work... Ttenbergen 17:14, 2014 April 7 (CDT)
  • add progress report form to send process Ttenbergen 12:05, 2014 April 14 (CDT)

New change request

checks for minimal data admit/discharge

generate apache for sending

Ed used to generate it on import, need to generate on sending now. Ttenbergen 22:02, 2013 November 18 (CST)

Tasks checks

as per Tasks_vs_iTISS#Data checking with SAS iTISS with Specific DX codes with Tasks

additional checks

speed up sending

review send queries to see if they can be sped up

Bug Fixes

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

Next Round of Data Changes

None currently Ttenbergen 15:03, 2013 March 11 (EDT)

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.

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 I believe we decided not to to keep dates consistent throughout the program. Can anyone remember details? Ttenbergen 15:40, 2014 January 26 (CST)

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.

Mandating colours

Template: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.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. 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? Template: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)

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. Template: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.

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)

Pharmacy Tally

  • 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)
      • moved this request here. If there are no further comments on it within 2 weeks then this section can please be delete by whoever stumbles on it next. Ttenbergen 16:28, 2013 March 11 (EDT)

Previous requests that were not made (with reasons)

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.

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)
Retrieved from "https://ccmdb.kuality.ca/index.php?title=Requested_CCMDB_changes_for_the_next_version&oldid=38354"