|Data Element (edit)|
|CCMDB Label:||Service Location|
|Program:||Med and CC|
Legacy field: the entry is now static on most laptops, and the information that used to be stored in here is now stored in Boarding Loc and Service tmp entry as part of Change from Service Location to Service, Boarding Loc and Transfer Ready DtTm tmp entry.
- This does not apply to STB_MICU, STB_CICU, STB_ACCU or HSC_IICU. Service Location field will not change.
see Change_from_Service_Location_to_Service,_Boarding_Loc_and_Transfer_Ready_DtTm_tmp_entry#The_change for how to code during the transition to the new scheme
- GRA_Med, HSC_Med, STB_Med for medicine
- GRA_CC, HSC_CC, 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)
The concepts that used to be stored in this are essentially now stored as:
"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.
Since no one person knows when this is the case on all laptops for all fields Tina will need to make a query that checks for this in the centralized data. Ttenbergen 15:42, 2020 October 20 (CDT)
Minimal Data Set
This entry is part of the Minimal Data Set. Special collection instructions apply, see that page for more info.
Adding a new service/location entry
- add to s_dispo table
- add to s_locations_allowed_collection table
- consider all checks in Category:Service/Location check to see if they need to be modified to work right for the new location.
Data Use / Purpose
See Site and Location table for possible entries.
Used to determine the location or services the patient went during a hospital stay.
Used to categorize/stratify the distribution of patients across hospitals and wards/units when reporting summary statistics.
Data Integrity Checks (SMW)
|Query s tmp ABO TEE checks||CCMDB.accdb||implemented|
|Query check minimal data set incomplete||CCMDB.accdb||implemented|
|Query send check centralized is owner||CCMDB.accdb||implemented|
|Check function location NE dispo||CCMDB.accdb||implemented|
|Query s tmp Boarding Loc date item||CCMDB.accdb||implemented|
|Check function previous NE Location||CCMDB.accdb||implemented|
|Query s tmp Boarding Loc no borrow but entry||CCMDB.accdb||implemented|
|Check function preAdmit NE Location||CCMDB.accdb||implemented|
|Query check ER Delay not too big||CCMDB.accdb||needs review|
|PL SameCHART Site Diff PHIN||Centralized data front end.accdb||implemented|
|PL SamePHIN Site Diff chart||Centralized data front end.accdb||implemented|
|PL 1orphans||Centralized data front end.accdb||implemented|
|Link suspect mismatch pre inpt ours incomplete query||Centralized data front end.accdb||implemented|
The field is populated with options from the s_dispo table.
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.
This field is subject to Change from Service Location to Service, Boarding Loc and Transfer Ready DtTm tmp entry.
This field is part of the 2016 Time and Place changes and corresponds to to the old Location field, resp L_Log.R_Location.