QA Infection
Purpose
Kendiss Olafson & the QA team are monitoring Central Line Infections and VAPs in the ICUs.
Specs
ICU
Dates
- Start Date: Saturday August 22, 2009
- End Date: NONE - Continued project with the CCVSM cross Canada Collaborative--TOstryzniuk 16:53, 4 October 2010 (CDT)
- Units Collecting: all ICU's in the Region.
Medicine wards
- part B only - Central Line Infection start date
Dates
- Start Date: Monday October 19, 2009
- End Date: NONE. Ongoing project for CCVSM cross Canada Collaborative.--TOstryzniuk 16:51, 4 October 2010 (CDT)
- Units Collecting: Medicine wards: HSC, STB, VIC, GRA
Data Collection Method
A. VAP
If an ICU patient has a Complication of VAP, the following entry must be made in the L_TmpV2 file:
- Project: QAInf
- Item: VAP Infection
- Infx Dt: Date of infection (no time) is the date POSITIVE SPUTUM CULTURE was sent to micro lab.
- if no positive sputum culture, than not a VAP.
B. Central Line Infection
If a patient has a Complication of Central Line Infection, the following entry must be made in the L_TmpV2 file:
- Project: QAInf
- Item: Central Line Infection
- Infx Dt: Date of infection (no time) is the date positive blood culture was sent to micro lab.
- if no positive culture than not a CLR-BSI
Line Count Form used by ICU's
- Form is completed daily by CRN (charge nurse) or manager and FAXED to the Database Research office once per week (every Monday with previous weeks data).
- Data Processor makes a phone call to specific contact people in each ICU every week if the form is not submitted by Wednesday each week.
- Data Processor manually enters values from this form into an Access database on our office share drive X.
- The same form is used by ICU charge nurses for the QA ETT unschedule extubations project and for Central Line Infection Rate counting and QAInf ITEM B above. & article Central Line Infection
Consistency Checks
Tmp Checker will check for the following:
Dx but no tmp
If Complication Diagnosis is one of:
- Central line infection (code 86)
- VAP (code 39)
then
- L_TmpV2 entry with project "ICU Infection Audit" with date needed
Tmp but no dx
If "QAInf" entry is present in L_Tmp then
- program must be "CC"
- the corresponding diagnosis must exist
Send mode
Data for all patients meeting requirements for this study, including patients you are not sending this batch, will be sent every time complete patients are sent.
Discussion
- Tina - There is a problem with CCMDB.mdb in that it will allows a collector to select in TMP, an ITEM that is not related to the PROJECT selected. On the PDA you cannot do this. For example, in TMPV2 on the Regional server, serial 12857 HSC_SICU had Project VAP selected but ITEM was QASeptic and it should have been QAInf.
- we are also finding the follow data laundry duties:
- EXAMPLES:
- VAP date in tmpV2 but no DX in complication
- DX of VAP in complication codes but no date in TMPV2
- VAP is in admit DX (to ICU) which is possible when transferred from another ICU, however a start Date is included in tmpV2. Not needed.
- VAP is recorded as a complication in a specific unit, yet in tmpV2 the date when positive culture sent is before that ICU admission or after that ICU admission.
- Not sure if you can easily add any of these checks in ACCESS to reduce laundry duties back here at the ranch.--TOstryzniuk 15:57, 25 March 2010 (CDT)