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 for the above two scenerios will be coded as Cardiac to indicate the patient is under Cardiology Physician Service Care.
• If MICU attending physician takes over their care, a NEW profile will be started
  • Site_Location for the NEW profile will be STB_MICU
  • Registry Patient Type will be coded as Medical to indicate the patient is under Medical Physician Service Care
• If the patient is moved FROM STB_MICU TO STB_CCU location on A5, a new profile will again be used:
  • Site_Location will be STB_CCU
  • Registry Patient Type will be coded as Cardiac to indicate the patient is under Cardiac Physician Service Care.

Cardiac type means that Cardiology service is looking after the patient. If MICU takes over the patient, then Medical patient type will apply in these cases only. --LKolesar 11:15, 21 October 2010 (CDT) The same goes for when the cardiac patient is located in CICU: Location will be CICU, patient type will be cardiac because Cardiology looks after these patients. When the patient is transferred to CCU, a new profile is started.

• Example:
  • CCU patient in MICU bed or CICU under cardiac physician service care:
  • Hosp_Loc: STB_MICU or STB_CICU
  • Reg Pt Type: Cardiac
• This patient gets transferred to STB ICU Medicine service care physician but stays in same STB_MICU bed. Discharge to: St.Boniface MICU
  • New profile
  • Admit From: St Boniface MICU
  • Hosp_Loc: STB_MICU
  • Reg Pt type: Medical

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.

• was this done? Ttenbergen 18:15, 2012 October 31 (EDT) Template:Discussion

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.

• was this done? Ttenbergen 18:15, 2012 October 31 (EDT) Template:Discussion

This is not implemented. Ttenbergen 14:19, 2012 November 16 (EST)

Attempting to summarize:

• if registry type is "surgical" or "medical" then discharge to self is not allowed
• if registry type is "cardiac" then
  • If R_location = STB_MICU or R_location = STB_CICU then allowed to discharge to STB_MICU Template:Discussion
    • really? they can discharge to self? Please confirm, and then add back to Requested CCMDB changes for the next versionTtenbergen 14:19, 2012 November 16 (EST)

Template:Potential Change

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