Service/Location field: Difference between revisions
Line 25: | Line 25: | ||
Use to determine the location or services the patient went during a hospital stay. | Use to determine the location or services the patient went during a hospital stay. | ||
Use to categorize the patient distribution across hospitals and wards/units. | Use to categorize the patient distribution across hospitals and wards/units when reporting summary statistics. | ||
== {{CCMDB Data Integrity Checks}} == | == {{CCMDB Data Integrity Checks}} == |
Revision as of 11:38, 2017 March 17
Data Element (edit) | |
Field Name: | Service_Location |
CCMDB Label: | Service 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: | 40 |
Collection location a patient is admitted to.
Collection Instruction
Enter the physical location of the patient.
If you know the location exactly, you can type it. otherwise use the "?" button. The dropdown is limited to locations where a laptop collects.
Only service locations allowed to be collected on this laptop based on its Settings (CCMBD.mdb) will be listed.
Patients in bed borrow locations on other wards or units are coded as the home unit. Collectors can use "record" field for tracking actual location.
Data Use / Purpose
Use to determine the location or services the patient went during a hospital stay.
Use to categorize the patient distribution across hospitals and wards/units when reporting summary statistics.
Template:CCMDB Data Integrity Checks
- Can not be blank
- previous_NE_Location() - Previous Location field can't be same as Service/Location field
- preAdmit_NE_Location() - Pre-admit Inpatient Institution field can't be same as Service/Location field
- location_NE_dispo() - Service/Location field can't be same as Dispo field
Following might still need to be implemented: Template:Discussion
Reports
To be filled in
Implementation
The field is populated with options from the s_dispo table.
Legacy
This field is part of the 2016 Time and Place changes and corresponds to to the old Location field, resp L_Log.R_Location.