CCMDB.mdb Change Log 2009: Difference between revisions
TOstryzniuk (talk | contribs) mNo edit summary |
TOstryzniuk (talk | contribs) |
||
| Line 16: | Line 16: | ||
*''this information was transferred here from ccmdb change log for 2008.''[[User:TOstryzniuk|TOstryzniuk]] 15:06, 29 December 2008 (CST) | *''this information was transferred here from ccmdb change log for 2008.''[[User:TOstryzniuk|TOstryzniuk]] 15:06, 29 December 2008 (CST) | ||
=== | ===ICU_Var2: BRR & Complication DX code of Cardiac Arrest=== | ||
*If any complication DX slot is coded as: 100-1 or 100-2 | *If any complication DX slot is coded as: 100-1 or 100-2 | ||
*var slot 2: '''MUST''' have either BRR or XBR (new code). | *var slot 2: '''MUST''' have either BRR or XBR (new code). | ||
| Line 22: | Line 22: | ||
**XBR means cooling protocol was NOT applied to cardiac arrest pt. | **XBR means cooling protocol was NOT applied to cardiac arrest pt. | ||
***review with Julie. | ***review with Julie. | ||
*[[User:TOstryzniuk|TOstryzniuk]] | *[[User:TOstryzniuk|TOstryzniuk]] 16:03, 23 January 2009 (CST) | ||
===APACHE II Screen=== | ===APACHE II Screen=== | ||
Revision as of 16:03, 23 January 2009
The CCMDB.mdb Change Log logs changes made to the CCMDB.mdb, including lock-downs when one person is making changes so that no one else makes changes at the same time. New entries should be made at the top to be immediately apparent. Discussions should be added at the level of individual changes if they correspond to a change, and at the end of the article if they relate to the change process in general. When a change is tested and rolled out it is also documented here.
- see CCMDB Change Log for 2008 for changes made and rolled out in 2008.
The 2009 CCMDB Change Log
January 14, 2009
- s_FIO2 table's for ACCESS (ccmdb) and Handibase updated to include OxyMask FIO2 guess-ta-mits.
- Master on Regional Server updated.
- rolled out
- TOstryzniuk 19:06, 14 January 2009 (CST)
Requested CCMDB changes for the next version
- this information was transferred here from ccmdb change log for 2008.TOstryzniuk 15:06, 29 December 2008 (CST)
ICU_Var2: BRR & Complication DX code of Cardiac Arrest
- If any complication DX slot is coded as: 100-1 or 100-2
- var slot 2: MUST have either BRR or XBR (new code).
- BRR mean cooling protocol WAS applied to cardiac arrest pt.
- XBR means cooling protocol was NOT applied to cardiac arrest pt.
- review with Julie.
- TOstryzniuk 16:03, 23 January 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.
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). This file will be eliminated in future versions. (as of May 2008) TOstryzniuk 18:51, 14 January 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.
- needs to be approved by Critical Care before implementation of change.
TOstryzniuk 16:29, 12 December 2008 (CST)
- Approved, leave blank.TOstryzniuk 05:24, 19 January 2009 (CST)
Patient TYPE for Registry - eliminate this field
- 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)
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)
Admit-from and discharge-to for ICU can't be current location
a. The admit From should never be the same as the Hospital and Location code (ex. FROM = HM, Hosp=HSC, Loc=MICU) b. The discharge To should never be the same as the Hospital and Location code (ex. Hosp=HSC, Loc=MICU, To = HM) As 8(b)
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
Must be able to delete completed files inside Access
Must be able to enter new files into Access
Before being able to use on the laptops
- automate the backup to the server
- automate a backup to the SD card
- automate checking for new front-end on every log in to the network
MI Data Integrity Check
If 102-10 you must not use any another 102 with a subcode. update Myocardial infarction when done.
ARF & CRF & ARI Integrity Check
- if CRF (351) in comorbid then ARF(350) or ARI (364) cannot be in admit or complication.
- 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 364 is new since the discussion about the cleaner. What is it about? Ttenbergen 15:55, 5 November 2008 (CST)