Service/Location field

From CCMDB Wiki
Jump to navigation Jump to search
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):

Collection location a patient is admitted to.

  • SMW

Legacy implementation right in the table

  • Cargo


  • Categories
  • Forms


Collection Instruction

For Medicine patients,In the Dispo under Service Location select the generic GRA_Med, HSC_Med, STB_Med

In the Tmp enter Boarding Loc, Home medicine ward, Date and Time of arrival to the ward and in column Q enter the physical location of the patient.

  • If the patient is admitted to an off service (contingency,bed borrow) bed, enter Boarding Loc, boarding, Date and time of arrival to that ward and in column Q enter the physical location of the patient.


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.

Use to determine the location or services the patient went during a hospital stay.

Use to categorize/stratify the distribution of patients across hospitals and wards/units when reporting summary statistics.

Integrity checks

Data Integrity Checks (automatic list)

none found

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-numberPool mix-ups. Either way, needs to be planned.

Legacy

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: