Previous Location field
| Data Element (edit) | |
| Field Name: | Previous_Location |
| CCMDB Label: | Previous Location |
| CCMDB tab: | Dispo |
| Table: | L_Log |
| 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 of a patient before arriving at the collection location.
For exceptions, see #EMIP, bed borrow).
Collection Instruction
For each patient,
- enter the option that most closely matches
- if you know the situation but nothing on the list matches closely, enter 'other - known but not listed
- if the situation is unknown, enter location missing/unknown
If you know the location exactly, you can type it. Otherwise press the "?" button to take you to the S dispo chooser to help filter options if desired.
For wards where we don't collect, enter e.g. HSC_ward. For wards where we do collect enter the actual ward as available in the dropdown.
Example
For example, a patient arriving from Selkirk Hospital via the local ER would have the ER coded in the Previous Location field and Selkirk coded in the Pre-admit Inpatient Institution field.
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.
direct transfer
For patients who get parked in the ER during a inter-facility transfer, enter the previous ward in Pre-admit Inpatient Institution field and enter your ER in Previous Location field. (In the past you would have entered the hospital and ward as the "admit from".)
EMIP/Bed borrow
See those articles. See also HSC Community and Clinical Decision Unit (CCDU).
from psych unit
Code patient from POU (pysch evaluation unit @ HSC) as "HSC ambulatory care" - it's not an inpatient ward.
Data collection units that have a mix of different physician serve types
We have a few units in the Region that have a mix of 2 different services (internal medicine, surgical, family medicine etc).
- VIC_S3 - is a mix of family medicine and internal medicine patients
- HSC_B3 - is a mix of day surgery & internal medicine patients
- any others?
For patients on these units:
- If patient is an internal medicine patient: enter the unit name (eg. VIC_S3)
- If patient is not a internal medicine patient, enter the generic hospital ward (e.g. VIC Ward); this will allow you to enter the Previous Service field with a physician service other than "Medicine".
Example: transfer from out-of-town ER
see Parked in ER
See also
from day surgery
For patients admitted from day surgery units, enter:
- Previous Location - <your hospital> Ward, e.g. HSC Ward
- Previous Service - General Surgery (or other surgical service listed in drop down.
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.
Template:CCMDB Data Integrity Checks
Implemented:
- Can not be blank
- previous_NE_Location() - Previous Location field can't be same as Service/Location field
- Patients with Previous Location field critical care must have Previous Service field critical care, and patients from medicine must have previous service medicine.
- query check_prev_pre-admit_consistent: for inpatient transfers within the region, Previous Location field and Pre-admit Inpatient Institution field should be same.
- query check_previous_location_vs_service_inconsistent: patients with Previous Location field in medicine must have Previous Service field medicine; patients from ICU (except CCU) must have previous service "critical care".
Following might still need to be implemented:
- Check ORDx; or not? Would have to be done for ICD10, so can it wait? Ttenbergen 16:26, 2016 May 25 (CDT)
- discussing with Julie, she seems open to waiting, told her I am starting Category:ICD10 and Template:ICD10 for stuff like this. Ttenbergen 10:56, 2016 June 2 (CDT)
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