Service/Location field: Difference between revisions
Ttenbergen (talk | contribs) No edit summary |
Ttenbergen (talk | contribs) No edit summary |
||
| Line 19: | Line 19: | ||
== ICU Bed Borrow == | == ICU Bed Borrow == | ||
=== Bed Borrow Only === | |||
* When a service borrows a bed in another unit/ward but still follows them, the [[Service Location]] should be the location where the patient would have been had there been enough beds/space for them. | * When a service borrows a bed in another unit/ward but still follows them, the [[Service Location]] should be the location where the patient would have been had there been enough beds/space for them. | ||
{{Ex|x= | {{Ex|x= | ||
| Line 30: | Line 30: | ||
}} | }} | ||
===Bed and Service Borrow Scenarios=== | |||
* see | * see [[Intended1stSrvc]] | ||
{{Guideline Minimal Data Set}} | {{Guideline Minimal Data Set}} | ||
Revision as of 15:40, 23 December 2025
| Data Element (edit) | |
| Field Name: | Service_Location |
| CCMDB Label: | Service 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: | 40 |
| Data Dependencies(Reports/Indicators/Data Elements): | |
Encodes which program a record is part of.
Collection Instruction
When entering from CSS or "Add Patient with Serial Helper" button, or in Patient Viewer Tab Dispo, under Service/Location field select the generic site/program entry:
- GRA_Med, HSC_Med, STB_Med for medicine
- GRA_CC, HSC_MICU, HSC_SICU, HSC_IICU, HSC_IICU, STB_MICU, STB_ACCU, STB_ICCS for critical care (see STB_CC#Decision to not combine collection of STB CC on one laptop)
ICU Bed Borrow
Bed Borrow Only
- When a service borrows a bed in another unit/ward but still follows them, the Service Location should be the location where the patient would have been had there been enough beds/space for them.
| Example: |
|
Bed and Service Borrow Scenarios
- see Intended1stSrvc
Minimal Data Set
This entry is part of the Minimal Data Set. Special collection instructions apply, see that page for more info.
Implementation
The field is populated with options from the s_dispo table.
Adding a new service/location entry
- add to s_dispo table
- consider all checks in Category:Service/Location check to see if they need to be modified to work right for the new location.
| * the name for a service location must be no longer than 8 characters, ie 3 for the hosp identifier, an underscore, and at most 4 for the local identifier |
|
The Service/Location field is one of the components that make up the D_ID field when a record is sent. That field has a length of 18. For 5 digit identifiers:
|
Retiring an available Service/Location field entry
Sometimes a ward may close or change names, or we may stop collecting somewhere. In that case, an entry for Service/Location needs to be made unavailable by editing the s_locations_allowed_collection table.
If a location is no longer available on a laptop records with that location can't be set to "complete". So, if we transition from one location to a new one, we need to get collectors to change the locations for all existing records to the new one, and change the number to using the new number series. Another option might be to keep old location available, at risk of manual mistakes and continuing to use the old location, and of location-number Pool mix-ups. Either way, needs to be planned.
"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.
| SQL query of what is currently available |
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 / Purpose
This essentially only encodes which program and site a record belongs to. It has additional meanings in legacy data, see Change from Service Location to Service, Boarding Loc and Transfer Ready DtTm tmp entry.
Used to categorize/stratify the distribution of patients across program and site when reporting summary statistics.
Integrity checks
Data Integrity Checks (automatic list)
none found
Log / legacy
This field is subject to Change from Service Location to Service, Boarding Loc and Transfer Ready DtTm tmp entry and 2025-05 Revision of concept around ICUotherService. However, we still need it because of how we decided to collect patients at HSC and STB CC.
The concepts that used to be stored in this are essentially now stored as:
- Service tmp entry for the service
- Boarding Loc for the physical location
This field is part of the 2016 Time and Place changes and corresponds to to the old Location field, resp L_Log.R_Location.