Service/Location field: Difference between revisions

From CCMDB Wiki
Jump to navigation Jump to search
← Older editNewer edit →
mNo edit summary
Line 3: Line 3:
| CCMDB_label = Service Location
| CCMDB_label = Service Location
| CCMDB_tab = Dispo
| CCMDB_tab = Dispo
| element_description = Collection location a patient is admitted to.
| element_description = Legacy field replaced by [[Boarding Loc]] and [[Service tmp entry]]
| in_table = L_Log table
| in_table = L_Log table
| data_type = number
| data_type = number
Line 14: Line 14:


== Collection Instruction ==
== Collection Instruction ==
For Medicine patients,In the Dispo under Service Location select the generic GRA_Med, HSC_Med, STB_Med
When entering from [[Cognos Admitter]] or [["Add Patient with Serial Helper" button]], or in [[Patient Viewer Tab Dispo]], under {{PAGENAME}} select the generic site/program entry:
 
* [[GRA_Med]], [[HSC_Med]], [[STB_Med]] for medicine
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. 
* [[GRA_CC]], [[HSC_CC]], [[STB_CC]] for critical care
*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.


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


{{Guideline Minimal Data Set}}
{{Guideline Minimal Data Set}}
Line 30: Line 32:
See [[Site and Location table]] for possible entries.
See [[Site and Location table]] for possible entries.


Use to determine the location or services the patient went during a hospital stay.  
Used 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.
Used to categorize/stratify the distribution of patients across hospitals and wards/units when reporting summary statistics.


== Integrity checks ==
== Integrity checks ==
Line 45: Line 47:


'''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.  
'''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'''.
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 ==
== 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.
This field is part of the [[2016 Time and Place changes]] and corresponds to to the old Location field, resp L_Log.R_Location.


Revision as of 21:54, 18 October 2020

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):

Legacy field replaced by Boarding Loc and Service tmp entry

  • SMW

Legacy implementation right in the table

  • Cargo


  • Categories
  • Forms


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:

The concepts that used to be stored in this are essentially now stored as:

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 EuroSCORE II checksCCMDB.accdbimplemented
Query Check_from_ED_and_prev_location_same_siteCCMDB.accdbready to implement
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
Link_suspect_visitAdmitDtTm_mult_to-from-home queryCentralized data front end.accdbready 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.

Related articles

Related articles:
Retrieved from "https://ccmdb.kuality.ca/index.php?title=Service/Location_field&oldid=146562"