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
Data Dependencies(Reports/Indicators/Data Elements):	ICU Interfacility Report

Legacy field replaced by Boarding Loc and Service tmp entry

• SMW

Legacy implementation right in the table

• Cargo

• Categories

• Forms

Legacy field replaced by Boarding Loc and Service tmp entry as part of Change from Service Location to Service, Boarding Loc and Transfer Ready DtTm tmp entry.

Collection Instruction

When entering from Cognos Admitter 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_CC, 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:

• 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.

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

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 (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 Check_from_ED_and_prev_location_same_site	CCMDB.accdb	ready to implement
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
Link_suspect_visitAdmitDtTm_mult_to-from-home query	Centralized data front end.accdb	ready to implement

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.

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