QA Infection
Purpose
Kendiss Olafson & the QA team are monitoring Central Line Infections and VAPs in the ICUs.
- We may also monitor central line rates on medicine wards pending follow up with Dr. Roberts.
Specs
- Start Date: Saturday August 22, 2009
- End Date / Duration: 1 year, then evaluate.TOstryzniuk 12:00, 20 August 2009 (CDT)
- Units Collecting: all ICU's except STB_CCU & STB_CICU
Note: We might start to collect Central Line Infections in Medicine as well pending input from Dr. Roberts.
Data Collection Method
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)
If an ICU or Medicine 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)
discussion
Only ICU collects VAP complication date. Is that because Med should never code VAP complication? If so, that check needs to be done elsewhere... Ttenbergen 17:40, 19 August 2009 (CDT)
- Correct - no VAP's in Medicine complications. CCMDB.mdb should have the this check programmed into it. If VAP is coded in complication (medicine) then this should be flagged in yellow as an error. Can you do it there? The other option is the data cleaner Pagasa uses, however this is checking data after it is already appended to master database and creates more work for Pagasa. TOstryzniuk 14:43, 20 August 2009 (CDT)
- How about if VAP is coded as admit? I should be able to code it; I'd like to make it a hard "no", though, rather than just yellowing it. OK? Ttenbergen 16:09, 20 August 2009 (CDT)
- VAP can be coded as an admit DX when patient moves between ICU. For example: VAP acquired as a complication at VIC_MICU - patient then transferred to HSC-MICU, VAP is still an active problem being tx'd therefore VAP is an admitting DX for HSC_MICU but no start date for VAP is required if transferred from another ICU.TOstryzniuk 11:17, 21 August 2009 (CDT)
- Correct - no VAP's in Medicine complications. CCMDB.mdb should have the this check programmed into it. If VAP is coded in complication (medicine) then this should be flagged in yellow as an error. Can you do it there? The other option is the data cleaner Pagasa uses, however this is checking data after it is already appended to master database and creates more work for Pagasa. TOstryzniuk 14:43, 20 August 2009 (CDT)
Consistency Checks
Tmp Checker will check for the following:
If Complication Diagnosis is:
- Central line infection (code 86)
- VAP (code 39)
then L_TmpV2 entry with project "ICU Infection Audit" with date needed
- date not required if 86 or 39 is in ADMIT Diagnosis.
Send mode
Data for a patient will be sent once that patient is marked as "FinalCheck".