Site and Location table

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).

items in blue are links to details recorded below

Hospital/Site	ICU Locations	Medicine Locations
HSC	MICU, SICU, CCU, IICU	A4, B3, H4, H4H, D4, D5,
STB	MICU CCU CICU	B4, B5, E5 Med overflow tracking to the following units: (A5, A6 & E6)
VIC	MICU	N4, N5, S3, S4, S5
GRA	MICU	N3, N5, W3
CON	MICU
OAK	MICU

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

• MICU/SICU were combined to MICU Jan.15, 2007
• Cardiac Care Unit CICU was established Jan 15, 2007

Details for Vic N4/S3

• The VGH has had two floors completely renovated and has moved two complete programs around. Initially when the medicine data base started, the fourth floor was a mix between medicine and surgery. The North ward had 30 beds and the south ward had 30 beds, and the medicine/surgical patients were mixed up between the two sides. So originally the data collection started on N4. The surgical program got moved to our old LDRP ward, on the second floor. So now 40 beds of surgery reside on second floor. The VMU ward got placed on S4 and family medicine on N4. We never changed the PDA's to reflect the S4 change, left it I believe as N4.
  • According to Tina, there would be major problems with Handibase/Active Sync Programs if change was made the reflect the S4 change.TOstryzniuk 12:45, 3 December 2008 (CST)
  • <Tina could you expand on this part of the PDA story>TOstryzniuk 12:45, 3 December 2008 (CST)
    • They are using laptops now, if we want to change this we would need to decide exactly what we want to do and then implement. Ttenbergen 14:03, 11 September 2009 (CDT)

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)

Discussion

• Is overflow tracking (OVER) documented anywhere on this wiki? It should be, and the reference in the table should link to it. Ttenbergen 15:12, 27 November 2008 (CST)
  • At the Vic we track overflow patients (OVER). If a patient goes from ER to a non-VMU bed(off service ward) for their whole stay, they get followed as an OVER patient.This patient has to be admitted to VMU before we track them. We use different serial numbers for this. If a patient is admitted to VMU and spends their whole hospital admission in ER they are followed as an Emergency Medical In Patient (EMIP), and they too have the different serial numbers(same series as the OVER patients). However, a VMU patient may first go to an off service ward from ER and then get moved to a VMU ward, this is tracked by our moves in the tmp. table.Their first move captures the admit time to the off service ward, and their second move captures the time they move to the VMU ward.WGobert 09:14, 28 November 2008 (CST)