Requested CCMDB changes for the next version

Requested CCMDB changes for the next version

• also see CCMDB.mdb Change Log 2009 for changes that have been rolled out to sites.

• this information was transferred here from ccmdb change log for 2008.TOstryzniuk 15:06, 29 December 2008 (CST)
  • There are changes in the master version that were not part of the version current changes are based off. These changes need to be added to the change version before sending it life!

March 2.09-NO LABS and NO Pharmacy

• CHANGE Suggestion: next ACCESS version there should be 2 separate check boxes for NO lab and NO Pharm TOstryzniuk 13:29, 2 March 2009 (CST)
  • March 30, 2009-Hi Trish, We had the same issue with comorbids, and what we did was add a comorbid entry that says “no comorbids”. We then made Access deal with stripping that out. I think this would be better than adding a checkbox. If you add this to the requested changes” I’ll put it in. Tina
    • sounds good. Go for it.--TOstryzniuk 17:55, 30 March 2009 (CDT)

• • • • PROBLEM: there are a few patients who do not have any labs & pharmacy data from the items we are tracking. ACCESS will not allow a collector to SEND if there is no data in BOTH LAB and PHARM. One site's workaround is to put EKG into lab field for the sole purpose of getting past this ACCESS restriction. This is not an acceptable workaround.--TOstryzniuk 13:29, 2 March 2009 (CST)

Checks and Updates

(currently all done, ready for roll-out)?

• What does this mean? TOstryzniuk 13:29, 2 March 2009 (CST)

BRR, XBR & T6

• If Cardiac Arrest Witnessed 100-2 in ADMIT or COMPLICATION DX slot then the following must also be marked:
• For CCMDB.mdb:
  • ICU Var 2 – “BRR” or “XBR”

• For Data Cleaner:
  • ICU Var 2 – “BRR” or “XBR”

AND

• • TISS item T6-hypothermia/hyperthermia blanket

I put this back in here, not sure where it went.--TOstryzniuk 15:02, 3 April 2009 (CDT)

• what happened to the BRR XBR check that was in this article? I put it into BRR article under data integrity rule.TOstryzniuk 15:31, 23 March 2009 (CDT)

Updates required for Laptops

• automate the backup to the Regional Server
• automate a backup to the SD card
• automate checking for new front-end on every log in to the network
• Must be able to enter new files into Access
• look into possibility of automatically downloading WIKI guide to laptop each day that it is synch'd. (portable version of guideline)--TOstryzniuk 20:11, 4 April 2009 (CDT)

QA Functionality

Facilitate exchange of patient discharge times

DCs have to know the discharge times for patients arriving at their wards from another collected ward. We should automate that rather than have them exchange manually. Might be an extension of the status file for Julie...Ttenbergen 16:05, 3 February 2009 (CST)

• moved a note into Admit, Transfer and Discharge date and time, as this is unrelated to updates to the program. Ttenbergen 09:27, 11 February 2009 (CST)

Logging errors in the CCMDB.mdb

Add a table to the CCMDB that records every time an error is generated with the following details:

• Date/time of error
• patient ID (Hosp Loc Serial)
• Field Identifier
• error descriptor (text)
• erroneous value

Make that table sync to a central repository on send.

Defer or in Discussion

ARF & CRF & ARI Integrity Check

• if CRF (351) in comorbid then ARF (Diagnosis (350) or ARI (364) cannot be in admit or complication. (see CRF vs ARF, ARI, Renal Transplant)

Discussion

• The 364 is new since the discussion about the cleaner. What is it about? Ttenbergen 15:55, 5 November 2008 (CST)
  • Yes, since I have been further reviewing patient profiles in more detail from the problems that SAS has generated, I see renal insufficiency (364)being coded in admit or complication DX slots for patients who have a comorbid condition of chronic renal failure (351).
• The article CRF vs ARF, ARI, Renal Transplant also mentions something about transplant. Is that still accurate? Ttenbergen 14:12, 18 February 2009 (CST)

Ensure that date/time formats are explicit

Make sure that Access explicitly looks for the format set out in Date and Time Format, rather than using the PC format. Template:Discussion

Discussion

• Right now CCMDB.mdb uses dd-mmm-yyyy, e.g. 12 Jan 2009. This is less ambiguous than the standard set out on the wiki. I think it's the better option since it eliminates the chance for transposition errors. I think we should use this format for collection. This does not affect how it is sent to Ed, or how it is stored in Ed's program. If Trish is OK with this, this section should be removed from the change log and Date and Time Format should be updated accordingly. Ttenbergen 12:58, 12 February 2009 (CST)

take out Autopsy YES OR NO

• ACCESS program is affected because of the way S or E is tied to autopsy on PDA.
• PDA Reader or master database utility programs are not affected if this field is left BLANK.

TOstryzniuk 16:29, 12 December 2008 (CST)

• Approved, leave blank.TOstryzniuk 05:24, 19 January 2009 (CST)

Discussion

Julie and Dr. Garland are currently working on moving the whole survive/expire issue into a "Dispo" field. I suggest we wait until they are done rather than implementing this twice. The advantage is that their change will use a data approach (discharge-to has a table) whereas editing the survive/expire options would be a manual change on HanDBase (notoriously unreliable). Ttenbergen 13:56, 10 February 2009 (CST)

APACHE II Screen

• get rid of fields that are not long being collected on the APACHE II screen (SAPS II items).
• total Bilirubin, CPAP, urine CC;s, Urea,SAP_Systolic,
• also - eliminate APACHE II Active TX field.

Discussion

• Is this for the CCMDB or for HanDBase? Bad idea to mess with HanDBase as it reverts and causes errors for unknown reasons. Since we are moving away from HanDBase, we should leave this alone and let it resolve itself. If it is about an issue in the CCMDB.mdb, please explain further. Ttenbergen 13:56, 10 February 2009 (CST)
  • CCMDB.mdb only since we are stuck with Handibase and it's problems until everyone is on laptops.TOstryzniuk 13:28, 9 March 2009 (CDT)
    • Tina, you do what you need to do to transition from HanDBase to just CCMDB. I know the story about HanDBase. If you can hide or get rid of these fields from CCMDB then do it. Having fields that are no longer collected creates confusion, especially for new hires. If this answers your question, then can you remove this discussion. Thanks.--TOstryzniuk 21:03, 4 April 2009 (CDT)

Registry Patient Type - eliminate this field

• The Access program is affected because it requires this field to be filled in before sending is allowed.
• PDA Reader or master database utility programs are not affected if this field is left BLANK
• needs to be approved by Critical Care before implementation of change.

TOstryzniuk 16:29, 12 December 2008 (CST)

• approved, leave blank. TOstryzniuk 05:27, 19 January 2009 (CST)

Discussion

This can be removed in Access and in the output, but I would suggest leaving it alone on the PDA for now due to HanDBase. Access would no longer check for it. If that is OK, this can be moved to "Checks and Updates".Ttenbergen 14:00, 10 February 2009 (CST)

APACHE II ACTIVE TX-eliminate this

• ACCESS program is affected because it makes this a required field (though my understanding is that many data collectors have set default for boxed to be checked).
• PDA Reader or master database utility programs are not affected if this field is left BLANK
• needs to be approved by Critical Care before implementation of this change

TOstryzniuk 16:29, 12 December 2008 (CST)

• Approved, leave blank. TOstryzniuk 05:25, 19 January 2009 (CST)

Discussion

• are you saying that ccmdb.mdb will not allow sending a pt with unchecked active tx? Ttenbergen 14:25, 11 February 2009 (CST)
  • YES.TOstryzniuk 13:35, 9 March 2009 (CDT)

s_Fi02 table in Handibase

• The S_FI02 (note: with a zero rather than a capital o) is a relic we have been unable to get rid of due to technical problems. It is the mis-spelled table name for S_FIO2 (i.e. capital o). Nothing can be done about it until the PDAs are all gone, so this should be taken out of the change log. (see S FI02 for details; remove the link from there if this is taken out of here.)

Ttenbergen 13:30, 10 February 2009 (CST)

Ensure discharge time = 0:00 can't get through

to implement check mentioned in Admit, Transfer and Discharge date and time but not currently working Template:Discussion

Discussion

• Check appears to be working for Admit and Discharge. Can't run check for Transfer time because transfer time is not mandatory. If there is a bug in this, please describe. Ttenbergen 12:47, 18 February 2009 (CST)