STB Cardiac Care patients

The collection of Registry Patient Type and Site and Location differs from how we usually collect.

Data Collection

• Cardiology (CCU) Service Patients that are physically located in the STB MICU but are looked after by the Cardiology Service physician will be collected and entered into the database with a Site_location as: STB_MICU. GO TO: STB_CCU overflow patient in STB_MICU
• Cardiology Service Patients that are "physically located" in the STB_CICU but are looked after the Cardiology Service physician will collected and entered into the database with a Site_location as: STB_CICU. GO TO: STB_CCU overflow in STB_CICU
  • Registry Patient Type will be coded as Cardiac to indicate the diagnosis type if applicable.
  • In the tmp file, use CCU Service Tracking selection as CCU option and if the pt is later covered by the MICU during the same pt stay in MICU, then change the tmp option to MICU. --LKolesar 10:12, 2015 June 9 (CDT)

Potential Change up for discussion

• continue discussion in task group about method to capture cardiology service patients in ICMS at STB. Plan to suggest transitioning to having this information incorporated into the tmp file. ie DATE and Time that pt is under cardiology service and/or medicine service if it changes during the pt. stay. Advantages: remains as one profile instead of splitting which is less confusing; also it is clear when the pt is under which service; also the patient type can be left as pertaining to the diagnosis instead of the respective service coverage which would be more consistent across the city. --LKolesar 14:48, 2015 April 30 (CDT)
  • I like that idea Laura, less confusing, especially with one consistent profile Lisa Kaita 09:06, 2015 May 1 (CDT)
  • This had been implemented as CCU Service Tracking and Julie will go back to January, 2015 to change all pts to this format. --LKolesar 10:14, 2015 June 9 (CDT)

Now Legacy:Patients located on MISI

As of October 1, 2010 CCU collectors do not collect data on CCU (Cardiology) pts that are located in MICU or ICCS. Instead these pts are put as MICU or CICU location with cardiac type. The MICU or CICU collector is responsible for these patient profiles. If the pt care is transferred to the MICU attending, the profile will be restarted and it will be a medical type, instead of cardiac type. . Must remember to start a new tiss if the patient is transferred to the MICU physician's care. The first profile is logged out to MICU and the new profile is logged into MICU even though in both cases the location is MICU. This scenario happens rarely as usually Cardiology service looks after their patients while they are in MICU or CICU.

Legacy cardiac info

• prior to October 1, 2010: MSICU and ICCS had CCU patients as CCU overflows. They would often be located in one of these areas if they require intubation and /or IABP. However, they were still attended by the CCU doctors and the CCU data collector entered them as a CCU patient. They usually remained under CCU unless further multi system issues exist that the CCU attending wished to transfer the care to the ICU. In this case the patient is discharged from CCU and admitted to the ICU and the ICU data collector then would start a profile and continue to follow this patient. The respective TISS sheet followed the patient as they are moved between units if they continued to be a CCU pt.) The overflow was marked in the variable 5 slot.
  • This entire section is now legacy and Julie has changed this system to utilization of tmp section to designate Cardiology vs MICU coverage back to January 1, 2015. See CCU Service Tracking . Anything before that date will still have the old system of determining Cardiology service. --LKolesar 10:19, 2015 June 9 (CDT)

Data linking

The Statistician who uses SAS programs to link continuous admissions, will update her SAS program so that an admission FROM Site_Loc, STB_MICU TO Site_Loc,STB_MICU, will not be flagged as an error. The distinguishing feature of these cases will be Registry Patient Type, which will indicate the Physician Service Care the patient is under will in the STB MICU unit.

Template:CCMDB Data Integrity Checks

CCMDB.mdb will be changed to allow site and location STB_MICU with discharge to: STB MICU if Registry type is Cardiac. If registry type Medical or Surgical, then not allowed. If Site and location STB_CICU with discharge to: CICU if registry type is Cardiac. If registry type S then not allowed.

Origin of this article

This article combines information from the following locations to avoid inconsistencies and duplication:

• Registry Patient Type#StB Cardiac patients
• Site_and_Location#STB_CCU service patients physically located in STB_MICU unit
• STB Critical Care Collection Guide

Legacy

• Registry patient type said started in October 1, 2010
• Site and Location table said started in November 1, 2010

• does the inconsistency mean it's wrong? Ttenbergen
• CCU Service Tracking start January 1, 2015 (this is because Julie went back to fix the data to that date).--LKolesar 10:29, 2015 June 9 (CDT)