Service/Location field

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

Legacy field replaced by Boarding Loc and Service tmp entry

• SMW

Legacy implementation right in the table

• Cargo

• Categories

• Forms

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.

Hey T, this page is for the Service location field in the demographics Tab correct? not sure why we have this as a legacy field? Or am I misunderstanding this?Lisa Kaita 15:11, 2024 March 6 (CST) I think that was written when we first changed and decided to only have <site>_<program>, ie before we split the CC program back up. In a way it is still legacy as that meaning, because now the meaningful info should live in Service and Unit entries in tmp. Between this and your question below about where that info should live, we may want to make an overarching page for the three concepts. I was wondering if we already have one, but the closest thing is Change from Service Location to Service, Boarding Loc and Transfer Ready DtTm tmp entry and that's not quite it. The cleanest way to to it might be to make a new page of the current Collection instructions for Service/Location vs Boarding Loc vs Service page, interlink it with the change page, and then keep only the current state/collector instruction in the "collection instructions..." page and the history in the "Change..." page. This is one of those things that are difficult to document because we need both the current state for collection and the complete history for interpretation. Having two pages like that should do it. Ttenbergen 16:30, 2024 March 6 (CST) I am not entirely clear on your instructions, or how to go about doing some of this, maybe when you have time we can chat about it, no rush Lisa Kaita 12:25, 2024 March 12 (CDT) Are you in today to chat? Ttenbergen 11:22, 2024 March 21 (CDT)

• SMW

• Cargo

• Categories

• This does not apply to STB_MICU, STB_CICU, STB_ACCU or HSC MICU, HSC SICU, HSC_IICU. Service Location field will not change.

Collection Instruction

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

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)

Bed Borrow

• 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. ACCU patient, followed by ACCU service but physically located in CICU, service location=ACCU. The Boarding Loc in the Tmp will identify that they are "borrowing" a bed in CICU. If this patient is then transferred to their normal unit, ACCU, add this location as a Boarding Loc in the tmp, this would be a single profile. If the patient was NOT followed by ACCU but by CICU, see ICUotherService for instructions on how to collect.

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

"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

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
• 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 (automatic list)

	App	Status
Query check minimal data set incomplete	CCMDB.accdb	implemented
Check function location NE dispo	CCMDB.accdb	implemented
Check function previous NE Location	CCMDB.accdb	implemented
Check function preAdmit NE Location	CCMDB.accdb	implemented
Query s tmp ABO TEE checks	CCMDB.accdb	implemented
Query send check centralized is owner	CCMDB.accdb	implemented
Query s tmp EuroSCORE II checks	CCMDB.accdb	implemented
Query s tmp Boarding Loc no borrow but entry	CCMDB.accdb	retired
PL SameCHART Site Diff PHIN	Centralized data front end.accdb	implemented
Link suspect mismatch pre inpt ours incomplete query	Centralized data front end.accdb	implemented
Link suspect not same visitAdmitDtTm query	Centralized data front end.accdb	implemented
Reconnect check orphans query	Centralized data front end.accdb	implemented

Implementation

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.

Legacy

This field is subject to Change from Service Location to Service, Boarding Loc and Transfer Ready DtTm tmp entry. However, we still need it because of how we decided to collect patients at HSC and STB CC.

This field is part of the 2016 Time and Place changes and corresponds to to the old Location field, resp L_Log.R_Location.