Site and Location table: Difference between revisions

From CCMDB Wiki
Jump to navigation Jump to search
TOstryzniuk (talk | contribs)
TOstryzniuk (talk | contribs)
Line 122: Line 122:
some of this information is repeated in link above. Clearer details here but I am not sure how best combined since one article is about registry type and the other is about site location and both are related "changes" for STB cardiology patient overflowing into CICU and MICU.--[[User:TOstryzniuk|TOstryzniuk]] 15:03, 10 December 2010 (CST)
some of this information is repeated in link above. Clearer details here but I am not sure how best combined since one article is about registry type and the other is about site location and both are related "changes" for STB cardiology patient overflowing into CICU and MICU.--[[User:TOstryzniuk|TOstryzniuk]] 15:03, 10 December 2010 (CST)


#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:[[Overflow to other units - Critical Care HSC and STB only#STB-CCU overflow patient in MICU (under cardiology service) |STB_CCU overflow patient in STB_MICU]]
#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: [[Overflow to other units - Critical Care HSC and STB only#STB-CCU overflow patient in MICU (under cardiology service) |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:*[[Overflow to other units - Critical Care HSC and STB only#STB-CCU overflow patient in CICU  (under cardiology care)| STB_CCU overflow in STB_CICU]]
#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: [[Overflow to other units - Critical Care HSC and STB only#STB-CCU overflow patient in CICU  (under cardiology care)| 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.   
#*[[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
#If MICU attending physician '''takes over''' their '''care''', a NEW profile will be started

Revision as of 13:02, 2012 June 4

This table shows Hospitals/Sites and locations where we collect data and their codes for entry into the Location field. In some circumstances you will need to use the hospital and location on their own, and in some they will be combined. If they are combined, they should be written as <hospital>_<location> (eg HSC_A4).

  • The table also shows the dates when data collection was started in each unit.

items in blue are links to details recorded below

Hospital/Site ICU ward location Medicine ward location Data Collection Start Date
HSC MICU, SICU, CCU, IICU
  • MICU-July 1, 1988
  • SICU-July 1, 1988
  • IICU-May 13, 1997
  • CCU-May 1, 1999
  • A4-October 1, 2003
  • H4-April 1, 2004
  • D4-March 1, 2004
  • D5-March 1, 2004
  • B3-February 1, 2005
  • H4H-May 1, 2005
  • HSC Med nonteaching contingency beds - 2010
STB
  • CCU
  • B4-NTU (B4 changed to 5B- NTU. Change date: Nov 17.09. (non acute geri rehab)
  • B5- CTU change date: Oct 14.09 (stop at serial 6310 move to E6), (stop at serial 4597-Deb's PDA every 86-100)
  • E6- CTU change date: Oct 14.09 (start at serial 6311)(start at serial 4598 -Deb's every 86-100))
  • E5- CTU
    • Med overflow tracking to the following units: (A5, A6 & E6)
  • CCU-May 24, 1999
  • MICU-May 24,1999
  • SICU-May 24, 1999
    • Combined SICU/MICU Unit: January 15, 2007
  • CICU-January 15, 2007
  • B5(E6)-August 1, 2004
    • Moved to E6-October 14, 2009
  • B4-November 1, 2004
    • Moved to 5B-November 17, 2009
  • E5-December 1, 2004
VIC MICU
  • MICU-June 1, 1999
  • N5-August 1, 2005
  • S5-September 1, 2005
  • S3-October 1, 2005
  • S4-October 1, 2005 (included medicine patients on N4-legacy)
    • S4-Opened as a CTU August 1, 2009
  • N3F & S4F-Family Medicine-July 1, 2005 to June 30, 2006
  • EMIP-February 1, 2007
GRA MICU
  • MICU-September 14, 1998
  • N3-January 1, 2005
  • N5-January 1, 2005
  • W3/E3 (referred to at the Grace as 3 South) also known as W3-January 1, 2005
  • EMIP-November 1,2010
CON MICU 0
  • May 1, 1999
OAK MICU 0
  • June 1, 1999


Details for Grace W3 / E3 / S3

The data for Grace W3 actually includes the east(E) and west(W) wings of the third floor. Apparently at some point, the Grace refers to W3 & E3 as ward S3. Since we had been collecting data for a year or two before this came up, we decided not to change our location label.

Details for STB ICU

STB_MICU & SICU

  • the units were combined into "one unit" called STB_MICU
Date of change

January 15, 2007

STB_CICU

  • Cardiac Surgery Intensive Care Unit STB_CICU was established
Date of change

January 15, 2007

CICU overflow into MICU

Go to: STB_CICU overflow in STB_MICU

NEW - STB_CCU physician service patients physically located in STB_MICU unit - Collection Process CHANGE for LOCATION and Registry Patient Type

Template:Discussion some of this information is repeated in link above. Clearer details here but I am not sure how best combined since one article is about registry type and the other is about site location and both are related "changes" for STB cardiology patient overflowing into CICU and MICU.--TOstryzniuk 15:03, 10 December 2010 (CST)

  1. 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
  2. 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.
  3. If MICU attending physician takes over their care, a NEW profile will be started
  4. Site_Location for the NEW profile will be STB_MICU
  5. Registry Patient Type will be coded as Medical to indicate the patient is under Medical Physician Service Care
    • 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.
    • The data integrity rules in 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.
  6. If the patient is moved FROM STB_MICU TO STB_CCU location on A5, a new profile will again be used:
  7. Site_Location will be STB_CCU
  8. Registry Patient Type will be coded as Cardiac to indicate the patient is under Cardiac Physician Service Care.
Date of change
  • November 1, 2010.

Details for Vic N4/S3

Unit 3 is a medical rehab ward. It has 30 beds. However, both the Family Medicine program and the VMU program admit patients here. So this S3 ward got added to the N4 ward and the same data collector collects both units. There can be anywhere from 10-20 VMU patients on unit 3 at any one time, it fluctuates. These patients are all medically stable with d/c planning issues. Are they PCH bound, Geri-rehab bound, awaiting HC, many things, but when they become unstable, they get moved off that ward. So there you have the story of the N4/S3 ward.WGobert 09:21, 28 November 2008 (CST)

STB ward change B5 to E6

October 14th all new new admits on this day change location to E6.

  • Any new patients admitted to B5 on Oct 14th onward will have LOCATION of E6. (starts at serial number 6311 Gayle’s PDA and serial 4598 Deb’s PDA for B5 patients).
  • Any patient admitted to B5 Oct 13th or earlier will retain LOCATION of B5. (Last B5 patient serial 6310 (Gayle PDA) & 4597(deb’s PDA)

Move dates:

  • If the B5 admit date was “on” or after Oct 14 then moves data should be to E6.
  • If the B5 ward admit date was October 13th or “earlier” then move data is B5 even if patient is move to you on or after October 14.

Integrity Checks

Variable 1 & 2 of Other Wards:

  • If the admit date of the other ward was October 13th or “earlier” then var 1 should be FROM B5.
  • If the admit date of the other ward was “on” or after Oct 14 then var 1 should be FROM E6.
  • If the discharge date of the other ward was October 13th or “earlier” then var 2 should be TO B5.
  • If the discharge date of the other ward was “on” or after Oct 14 then var 2 should be TO E6.

Details for HSC_B3

  • Data collection started on this unit October 18, 2004. One side of this ward is Medicine patients, mostly cardiac patients. Use to be cardiology beds. Dan might remember? The other side of this ward is days surgery patients that we do not collect data on.TOstryzniuk 18:59, 5 January 2010 (CST)


Template:Discussion

  • Need to clean up table above further.TOstryzniuk 20:37, 18 January 2010 (CST)
    • Trish, you asked me a long time ago if I could help clean this up. I would like to set this up as headings and sub-headings rather than a table. If that's OK with you I'll take care of it. Just let me know. Ttenbergen 10:28, 3 November 2010 (CDT)
      • Yes, that would be great! Thank you.-TOstryzniuk 14:54, 10 December 2010 (CST)