QA Infection: Difference between revisions

From CCMDB Wiki
Jump to navigation Jump to search
Line 16: Line 16:
* End Date: NONE. Ongoing project for [[CCVSM]] cross Canada Collaborative.--[[User:TOstryzniuk|TOstryzniuk]] 16:51, 4 October 2010 (CDT)
* End Date: NONE. Ongoing project for [[CCVSM]] cross Canada Collaborative.--[[User:TOstryzniuk|TOstryzniuk]] 16:51, 4 October 2010 (CDT)
* Units Collecting: Medicine wards: HSC, STB, VIC, GRA
* Units Collecting: Medicine wards: HSC, STB, VIC, GRA
**Med wards do not submit [http://ltc.umanitoba.ca/wikis/ccmdb/index.php/QA_Infection#Line_Count_Form_used_by_ICU.27sCentral Line count forms].


==Data Collection Instructions==
==Data Collection Instructions==

Revision as of 13:14, 2010 November 16

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.
  • STB_CICU or STB_CCU do not submit Line count forms.

Medicine wards

  • part B only - DX of 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 Instructions

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.
  • Go to VAP article for more information about VAP.

The site where the VAP had "first" occurred at is the site that must get the credit for where this complication had occurred.

NOTE

VAP cannot be coded as a complication on a Medicine ward but can be used as an Admitting diagnosis if patient came from an ICU and requires ongoing treatment for this problem. If resolved in the ICU, don't code as an admitting DX to you ward.

B. Central Line Infection

  1. If a patient develops a Complication of Central Line Infection while in your unit, the following entry must be made in the L_TmpV2 file:
    • Project: QAInf
    • Item: Central Line Infection
    • 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
  2. Patient already has a CLR-BSI present on admission to your unit:
    • in the admitting diagnosis field, enter Central Line Infection.
    • do not enter the DATE of positive culture in the Temp Studies field.
    • if the patient is from another ICU in the city, email the collector at that site to check if CLR_BSI was captured as a "complication" at that site.

The site where the CLR-BSI had "first" occurred at is the site that must get the credit for where this complication had occurred.

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.

Consistency Checks

Tmp Checker will check for the following:

Dx but no tmp

If Complication Diagnosis is one of:

then

  • L_TmpV2 entry with project "ICU Infection Audit" with date needed

Tmp but no dx

If "QAInf" entry is present in L_TmpV2 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

Template: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)