Date change bug

Hazel from the Vic just reported (Thanks for letting me know! Ttenbergen 10:35, 28 July 2011 (CDT)) that she has had dates change on their own after ver_2011-07-25 went out. This may be related to the buttons I added to the date fields in [[ver_2011-07-13

Apparently Hazel sent data Jul 27, and when she looked at the data this morning some of the dates had changed. Some of them had changed to dates that our error checker should not have let through, which is even more concerning.

Summary

I will move things here from the discussion if I notice patterns. Ttenbergen 15:27, 29 July 2011 (CDT) Please add if you have additional information

• date errors seem to be mostly a day earlier or later
  • need to keep in mind that some of these could be actual entry errors, need to find a way to make this happen.
• change is not happening during send, it is happening to data on the laptops, complete or not.
• error does not only affect sent data
• error seems to be happening as records are opened and closed

Discussion

• Has anyone else had any weird occurrences with dates since the last roll-out? Ttenbergen 10:35, 28 July 2011 (CDT)
  • I have noticed that some of my admit dates have changed. When I look at the profile the next day I notice that the date is either a day earlier or a day later than what I originally entered. I thought I was just making a lot of entry errors but now I think it is a glitch. I correct the date and hopefully the ones I sent are OK. I checked with Pagasa a few random ones which seem OK. The output files had already been deleted so I couldn't view my sent files. Anyway when Pagasa cross references the tiss, these errors will be evident. --LKolesar 11:16, 28 July 2011 (CDT)
  • I was auditing my ICU dates and observed my dates changed again without my prompting. I had closed the database yesterday. Opened it today with Serial #5052 for instance with different dates from last time checked. I corrected and closed the database. Viewed Serial #5052 and again, dates changed. This is after updating with newest version.I wonder if this problem is limited to just ‘sent’ patients? Hazel has not used the new added buttons for dates. --Hazel Rona
  • I would suggest that no one SEND in files until Tina resolves this. Tina could you not go back to the pre July 25 version and only have one person test latest version? Pagasa is on vacation for the next two weeks and there will be no other person to monitor this problem further. Collectors will have to check their send files on the Regional Server and check ALL the DATES against their paper log and fix any errors on regional server until Tina confirms problem is fixed. --TOstryzniuk 13:05, 29 July 2011 (CDT)
  • I’ve audited my files. Dates are altered not only on sent files but also on incomplete files. This means that before the bug is expunged, our dates may be likely inaccurate, despite checking ‘reg’ or ‘temp’ or even ‘complete’. --Hazel Rona
  • Laura has noticed also, that when she views the Patient List, she see an admit date and when she goes directly into the individual profile (registry screen) the admission date is changed. She thinks it changes when you go into patient files.
  • Audit: 1. Vic ICU & N5/S5. Dates per csv are accurate (and crosschecked against Medical Records). No changes made. 2. Date bug troubleshooting: Observed discrepancies between logsheets and csv dates on Medicine file. This was a transcribing error from recording dates on Thursday vs. Wednesday when I sent. This means that dates changed in the database between Wednesday and Thursday without user intervention. I’ve audited my files. Dates are altered not only on sent files but also on incomplete files. This means that before the bug is expunged, our dates may be likely inaccurate, despite checking ‘reg’ or ‘temp’ or even ‘complete’.--Hazel Rona
  • I checked Batch #29 sent July 26,11 N3 The only date or time I changed is serial #7285 it appeared to be an entry error for the admit time. For Batch # 30 sent July 26,11 for W3 Serial #3585 the admit date was blank I entered Sept 13,11 at 1220 hrs. The date for serial # 3989 was wrong (1 day earlier) and time wrong I corrected these. Please contact me if you have any questions. Sheila Dowson

Summary

I will move things here from the discussion if I notice patterns. Ttenbergen 15:27, 29 July 2011 (CDT)

• date errors seem to be mostly a day earlier or later
  • need to keep in mind that some of these could be actual entry errors, need to find a way to make this happen.
• change is not happening during send, it is happening to data on the laptops, complete or not.
• error does not only affect sent data
• error seems to be happening as records are opened and closed

Debugging notes

I will put here what I am doing or testing. Ttenbergen 15:27, 29 July 2011 (CDT)

• OK, can make an error happen if I enter a date that would be rejected (e.g. dis. dt before adm. dt) manually (no buttons), and then click the exit door without exiting the field first. For me that error means I can't exit at all, so I am not sure if that would be how bad data gets in... Ttenbergen 10:58, 28 July 2011 (CDT)
• I think it was a problem with the order in which the program writes and checks values. I made some changes and hope that the problem is resolved with CCMDB.mdb_Change_Log_2011#ver_2011-07-28. Please do a News&backup to download, and let me know if this problem persists. Ttenbergen 12:45, 28 July 2011 (CDT)

The Plan to FIX Admit, transfer & Discharge Date errors

DATE errors could be present from any files sent from July 13.11 to date. (admit, transfer, discharge).

• Error likely started in files ADDED ON or AFTER July 25 so data sent before this date is likely not affected.

• Pagasa has put ALL the SENT csv files on the Regional Server from July 13.11 to date.
  • CC_Date_Repair - contains all the ICU batches sent to date.
  • Med_Date_Repair - contains all Med batches sent to date.

• DATA COLLECTORS: Please check all your sent CSV files on the Regional Server against your paper ADMIT LOG. Also, for any data SENT or ADDED to laptop ON or AFTER the roll out of version on July 25.11, check all dates.
  • For any data files send BEFORE July 25th, do a random check of dates. It is likely these files are not be affected.
• Make any required DATE corrections directly on the CSV file on the Regional Server.

• Let JULIE know by EMAIL, when you have completed all corrections for your location.

• Pagasa will re-append and overwrite erroneous data into the master database repository.
• Pagasa will not correct these DATE errors manually. The Collectors will have to fix the CSV files on Regional Server.
• TISS will be scanned in after all correction to DATES are completed.

--TOstryzniuk 15:46, 28 July 2011 (CDT)