Previous Location field

From CCMDB Wiki
Jump to navigation Jump to search
Data Element (edit)
Field Name: Previous_Location
CCMDB Label: Previous Location
CCMDB tab: Dispo
Table: L_Log table
Data type: number
Length: long integer
Program: Med and CC
Created/Raw: Raw
Start Date: 2016-07-01
End Date: 2300-01-01
Sort Index: 37

The most recent previous physical location (with #exceptions) of a patient before arriving at the collection location.

  • SMW

Legacy implementation right in the table

  • Cargo


  • Categories
  • Forms


Collection Instruction

For each patient,

  • enter the option that most closely matches:
  • if the patient is a direct admission use <site>_UC, <Site>_ER, <site>_ward, <site>_Med, <site>_ICU or temporary location depending on the scenario (see direct admit scenarios below)
  • if you know the situation but nothing on the list matches closely, enter other - known but not listed
  • if the situation is unknown, enter Not known
  • if the patient is in ER under a service we do not collect ie. cardiology, surgery etc use <site>_ER

If you know the location exactly, you can type it, otherwise click on the dropdown button to view the options

Where to find this information

If patient came from a different Winnipeg hospital this should be recorded in the “Visit History” on the EPR, but sometimes it is missing. Can also use paper chart sent to your hospital from the sending hospital for information.

Borrowed Bed Or Pt Boarding On Other Unit

  • Use the Boarding Loc of the service taking care of the patient:<site>_Med, GH-CC, HSC_MICU, HSC_SICU, HSC_IICU, STB MICU, STB_ICCS, STB_ACCU.

Direct Admit Scenarios

  • inpatients from CON, OAK, VIC who are direct transfers to HSC/STB/GRA, the Pre-admit Inpatient Institution and Previous Location will be <site>_ward, even if the patient spends time in that site's UC prior to transfer. If not yet an inpatient from CON/OAK/VIC and transfer is from their UC, then previous location is the <site>_UC.
  • For direct transfers from HSC/STB/GRA, if an inpatient, and no in-between temporary location, the Pre-admit Inpatient Institution is the same as Previous Location (e.g. GH_med, or HSC_MICU)
    • if there is a temporary location in-between, then Previous Location is equal to the temporary location (e.g. OR, RR, Cath Lab, Dialysis, IR or Other procedure location) and Pre-admit Inpatient Institution would be the previous <site>_inpatient location
    • If not yet an inpatient from HSC/STB/GRA and coming from <other site> ER then previous location is <other site> ER, and the Pre-admit Inpatient Institution would be not applicable
  • If a homeless patient is admitted directly then code them as admitted from home.
  • If a patient is admitted directly from prison, jail or a correctional institution, code this as an admission from "Institution NOS". See Prison / Jail / Correctional Institution for additional info.

Exceptions

  • We have a few units in the Region that have a mix of different services (internal medicine, surgical, family medicine etc). For patients from these units:
    • If patient was under internal medicine service, enter <site>_Med
    • If not under internal medicine service, enter the <site>_Ward
  • for Riverview and Deer Lodge Chronic Health Facility see Pre-admit Inpatient Institution field for the various wards that are considered an inpatient location
  • patients from POU (psych evaluation unit @ HSC) as "HSC ambulatory care" - This is not an inpatient ward.
  • patients admitted from day surgery units, enter <site>_Ward, e.g. HSC Ward (this is not considered to be an inpatient location) see Pre-admit Inpatient Institution field

Temporary locations

"Can we remove the items that are no longer Service/Locations, Previous Locations, Pre-admit Inpatient Institutions or dispo locations from the dropdowns?"

We can and will remove them, but that can only happen once no more laptops use them. We will need to keep track of this and then remove them when ready. If I removed them now, then any box that currently has them enter would misbehave.

query of what is currently available

SQL   
SELECT s_dispo.location_name, s_dispo.Site, s_dispo.active, s_dispo.inpatient, s_dispo.previous_location, s_dispo.s_location, s_dispo.dispo
FROM s_dispo
WHERE (((s_dispo.Site)>"") AND ((s_dispo.active)=True) AND ((s_dispo.inpatient)=True)) OR (((s_dispo.Site)>"") AND ((s_dispo.active)=True) AND ((s_dispo.previous_location)=True)) OR (((s_dispo.Site)>"") AND ((s_dispo.active)=True) AND ((s_dispo.s_location)=True)) OR (((s_dispo.Site)>"") AND ((s_dispo.active)=True) AND ((s_dispo.dispo)=True));

Query of what is currently used

query z_s_dispo_inactivatable

Data Use

This data is used for tracking where most of the traffic on our units/wards comes from. For starters it will be reported to Critical Care (Randy Martin), who was also the requestor of this data.

Cross Checks

Data Integrity Checks (automatic list)

 AppStatus
Check pre acute consistentCCMDB.accdbdeclined
Query check tmp ER Boarding Loc should exist if from ERCCMDB.accdbdeclined
Function Validate Previous LocationCCMDB.accdbimplemented
Query check prev pre-admit consistentCCMDB.accdbimplemented
Check function previous NE LocationCCMDB.accdbimplemented
Query check CCI from OR no CCICCMDB.accdbimplemented
Query check pt from ERCCMDB.accdbimplemented
Query check previous location vs service inconsistentCCMDB.accdbretired
Check Accept Loc ParkCCMDB.accdbretired
Query check VAP admit must be from ICUCCMDB.accdbretired
Link suspect mismatch from ours incomplete queryCentralized data front end.accdbimplemented
Link suspect not same visitAdmitDtTm queryCentralized data front end.accdbimplemented
Query cardiac arrest throughout admissionCentralized data front end.accdbneeds review

Implementation

The field is populated with options from the s_dispo table.

Legacy

This field is part of the 2016 Time and Place changes.

It a combination of our previous

Related articles

Related articles: