Service/Location field

From CCMDB Wiki
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.

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:

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.

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

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.

Integrity checks

Data Integrity Checks (automatic list)

 AppStatus
Query check minimal data set incompleteCCMDB.accdbimplemented
Check function location NE dispoCCMDB.accdbimplemented
Check function previous NE LocationCCMDB.accdbimplemented
Check function preAdmit NE LocationCCMDB.accdbimplemented
Query s tmp ABO TEE checksCCMDB.accdbimplemented
Query send check centralized is ownerCCMDB.accdbimplemented
Query s tmp Boarding Loc no borrow but entryCCMDB.accdbretired
PL SameCHART Site Diff PHINCentralized data front end.accdbimplemented
Link suspect mismatch pre inpt ours incomplete queryCentralized data front end.accdbimplemented
Link suspect not same visitAdmitDtTm queryCentralized data front end.accdbimplemented
Reconnect check orphans queryCentralized data front end.accdbimplemented

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.

Related articles

Related articles: