Service/Location field: Difference between revisions

From CCMDB Wiki
Jump to navigation Jump to search
← Older edit
m cat
No edit summary
 
(86 intermediate revisions by 10 users not shown)
Line 1: Line 1:
''This field is currently being implemented, please check the instructions and put a discussion for anything that isn't clear. ''
{{Data_element
| field_name = Service_Location
| CCMDB_label = Service Location
| CCMDB_tab = Dispo
| element_description = Encodes which program a record is part of.
| in_table = L_Log table
| data_type = number
| datafield_length = long integer
| program_collecting = Med and CC
| created_raw = Raw
| data_element_start_date = 2016-07-01
| data_element_sort_index = 40
}}
 
== Collection Instruction ==
When entering from [[CSS]] 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
* [[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]])
 
== ICU Bed Borrow ==
'''Bed Borrow Only'''
* 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. 
**examples: 
1. ACCU patient, followed by ACCU service but borrowing a bed 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 CICU service takes over care, then a new profile would be started, showing the [[Service Location]]= CICU and the new CICU [[Service tmp entry]] and CICU [[Boarding Loc]]
2. HSC MICU borrows a bed in SICU, but MICU follows them:
* [[Service/Location]]= HSC MICU, the [[Boarding Loc]] in the Tmp will identify that MICU is borrowing a bed in HSC SICU, If the patient is later transferred to HSC MICU, this location would be added as a [[Boarding Loc]], this would remain a single profile.
*If the Service changes to an SICU service and they take over care, then a new profile would be started showing the new [[Service Location]]= SICU and the new SICU [[Service tmp entry]] and SICU [[Boarding Loc]]


Collection location a patient is admitted to, very similar to current "Location" field. This will be a dropdown that allows an appropriate subset of the contents of s_dispo.


Patients boarding on other wards or units are coded as the home unit. Collectors can use "record" field for tracking actual location.
'''Bed and Service Borrow Scenarios'''
* see [[ICUotherService]]


== Collection Instruction ==
{{DL|
essentially like [[Location]] is done now
* is this section still current? [[User:Ttenbergen|Ttenbergen]] 11:13, 6 March 2025 (CST)
* It up for discussion tomorrow at [[JALT Meeting - Rolling Agenda and Minutes 2025]] [[User:Lkaita|Lisa Kaita]] 21:04, 10 March 2025 (CDT)
* Allan spoke with Bojan, to be discussed at next JALT [[User:Lkaita|Lisa Kaita]] 14:48, 16 April 2025 (CDT)
* still being dicussed at JALT [[User:Lkaita|Lisa Kaita]] 21:45, 9 September 2025 (CDT)}}
{{Guideline Minimal Data Set}}
 
== Implementation ==
The field is populated with options from the [[s_dispo table]].
 
=== 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.
{{Collapsable | always=
* the name for a service location must be no longer than 8 characters, ie 3 for the hosp identifier, an underscore, and at most 4 for the local identifier |
full=
The Service/Location field is one of the components that make up the [[D_ID field]] when a record is sent. That field has a length of 18. For 5 digit identifiers:
* [[D_ID]] field length:  18
* H5_SOH_Geriatrics-19866 length: 24
* [[Laptop identifier]] and [[Pat_ID]] for a record, eg H5_-19866, lenght: 10
** this is assuming a 5 digit [[Pat_ID]]; as of 2025-03 our largest is 43865 so this will be OK for some time
** so our new s_dispo entry can be max 8 for service_locations
** 4 of that is always e.g. HSC_, so the local descriptor portion is max 4
*** e.g. HSC_AAAA will work, HSC_BBBBB will not
* if a Service_Location is used that results in a [[D_ID]] length > 18 the error will be a counterintuitive [[Error "Invalid SQL statment..." when sending | "Invalid SQL statement; expected 'DELETE', 'INSERT', 'PROCEDURE', 'SELECT', or 'UPDATE'. "]].
}}
 
=== Retiring an available Service/Location field entry ===
<!-- linked to heading from [S locations allowed collection table#Removing entries] -->
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 you know the location exactly, you can type it. Otherwise press the "magic wand" button to take you to the [[S dispo chooser‎]] to help filter options if desired.
'''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'''.


{{discussion}}
{{Location dropdown cleanup}}
* some of my patients come from Cancer care direct (out patient clinic) to medicine. Oncology or cancer care is not available as an option and the space does not allow you to type it in. Judy K Mar 24th 2016
** Judy I think you are referring either to the [[Previous Location field]] or the [[previous service field]] field... which one is it? Instead of answering here, could you please put the question there and remove it from here? I wonder if the collection instructions in that article might even answer your question...Ttenbergen 11:35, 2016 March 24 (CDT)


== Data Use / Purpose ==
== Data Use / Purpose ==
To be filled in  
This essentially only encodes which [[program]] and [[site]] a record belongs to. It has additional meanings in legacy data, see [[Change from Service Location to Service, Boarding Loc and Transfer Ready DtTm tmp entry]].
 
Used to categorize/stratify the distribution of patients across [[program]] and [[site]] when reporting summary statistics.
 
== Integrity checks ==
{{Data Integrity Check List}}


== {{CCMDB Data Integrity Checks}} ==
== Log / legacy ==
To be filled in
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.


== Reports ==
The concepts that used to be stored in this are essentially now stored as:
To be filled in  
* [[Service tmp entry]] for the service
* [[Boarding Loc]] for the physical location


== Implementation ==
This field is part of the [[2016 Time and Place changes]] and corresponds to to the old Location field, resp L_Log.R_Location.
The field is populated with options from the [[s_dispo table]].


== Legacy ==
== Related articles ==  
This field is part of the [[2016 Time and Place changes]] and corresponds to to the old [[Location]] field
{{Related Articles}}


[[Category: 2016 Time and Place changes]]
[[Category:2016 Time and Place changes]]
[[Category: Admit/Discharge]]
[[Category:Registry Data]]
[[Category:Data Collection Guide]]

Latest revision as of 21:45, 9 September 2025

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

Encodes which program a record is part of.

  • SMW

Legacy implementation right in the table

  • Cargo


  • Categories
  • Forms


Collection Instruction

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:

ICU Bed Borrow

Bed Borrow Only

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

1. ACCU patient, followed by ACCU service but borrowing a bed in CICU:

2. HSC MICU borrows a bed in SICU, but MICU follows them:

  • Service/Location= HSC MICU, the Boarding Loc in the Tmp will identify that MICU is borrowing a bed in HSC SICU, If the patient is later transferred to HSC MICU, this location would be added as a Boarding Loc, this would remain a single profile.
  • If the Service changes to an SICU service and they take over care, then a new profile would be started showing the new Service Location= SICU and the new SICU Service tmp entry and SICU Boarding Loc


Bed and Service Borrow Scenarios


  • SMW


  • Cargo


  • Categories

Minimal Data Set

This entry is part of the Minimal Data Set. Special collection instructions apply, see that page for more info.

Implementation

The field is populated with options from the s_dispo table.

Adding a new service/location entry

* the name for a service location must be no longer than 8 characters, ie 3 for the hosp identifier, an underscore, and at most 4 for the local identifier   

The Service/Location field is one of the components that make up the D_ID field when a record is sent. That field has a length of 18. For 5 digit identifiers:

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.

"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

Data Use / Purpose

This essentially only encodes which program and site a record belongs to. It has additional meanings in legacy data, see Change from Service Location to Service, Boarding Loc and Transfer Ready DtTm tmp entry.

Used to categorize/stratify the distribution of patients across program and site 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

Log / 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.

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

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=167544"