CCMDB Wiki

Service/Location field: Difference between revisions

← Older edit
m →additional locations required?: if clear pls delete section
No edit summary
 
(76 intermediate revisions by 8 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 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.
== Collection Instruction ==
{{Discussion}}
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:
*why is the field call SERVICE LOCATION rather than LOCATION.  adds to the confusion. Is there a point to include addition word Service to location.  There really is not such thing as a Service Location.
* [[GRA_Med]], [[HSC_Med]], [[STB_Med]] for medicine
**Suggestion, just call the field LOCATION as it was called before.  Less confusion.
* [[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]])
** I agree to call it as LOCATION. [[User:JMojica|JMojica]] 13:25, 2016 April 18 (CDT)
 
Patients boarding on other wards or units are coded as the home unit. Collectors can use "record" field for tracking actual location.
== 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.
{{Ex|x=
# 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]]
# 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'''
* see [[ICUotherService]]
 
{{DJ|{{DL|
* 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 discussed at JALT [[User:Lkaita|Lisa Kaita]] 21:45, 9 September 2025 (CDT)
* '''OK, discussion seems to be complete, we will change [[ICUotherService]] to [[Intended1stSrvc]]. I have cleaned up most peripheral links, but Lisa, could you make sure that this page reflects post-[[ICUotherService]] collection instructions? Any info about the ''change'' should really only be in [[2025-05 Revision of concept around ICUotherService]], which I have already linked from the legacy section of this page. We need to make sure that the info to make sense of the continuity of the data lives in that page. [[User:Ttenbergen|Ttenbergen]]
* '''What will be the turn-over for this? New admissions starting Oct 1? [[User:Ttenbergen|Ttenbergen]] 14:54, 26 September 2025 (CDT)
}} }}
 
 
{{Guideline Minimal Data Set}}
 
== Implementation ==
The field is populated with options from the [[s_dispo table]].


== Collection Instruction ==
=== Adding a new service/location entry ===
essentially like [[Location]] is done now
* 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'. "]].
}}


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.
=== 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]].  


==Questions==
'''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.
=== additional locations required? ===
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'''.
*Please add 'EMIP' option to the dropdown for each hospital.--[[User:LKolesar|LKolesar]] 14:27, 2016 April 14 (CDT)
** right now only some sites have [[EMIP]]; why to all sites need it now? Are we talking about the same thing? Ttenbergen 12:08, 2016 April 18 (CDT)
*** if this is clear now please delete the section Ttenbergen 20:00, 2016 April 25 (CDT)


=== change a location ===
{{Location dropdown cleanup}}
*Is it possible to change gra_w3 to gra_s3? It hasn't been called 3west for a long time - it was expanded and now is 3south [[User:Mschaffer|Mschaffer]]
** asked Julie... Ttenbergen 12:08, 2016 April 18 (CDT)
** we did a similar change in STB before (E6 to B5, B4 to 5B).  is 3south the final location - if yes, then OK to change.  [[User:JMojica|JMojica]] 13:25, 2016 April 18 (CDT)
***3south is the final unit. I thought it might be easier to change now when we are changing all locations. It has been 3South for years. [[User:Mschaffer|Mschaffer]] 14:56, 2016 April 18 (CDT)
**** OK changed in new version. Ttenbergen 19:59, 2016 April 25 (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]].


== {{CCMDB Data Integrity Checks}} ==
Used to categorize/stratify the distribution of patients across [[program]] and [[site]] when reporting summary statistics.
* [[Minimal Data Set]]


== Reports ==
== Integrity checks ==
To be filled in
{{Data Integrity Check List}}


== Implementation ==
== Log / legacy ==
The field is populated with options from the [[s_dispo table]].
This field is subject to [[Change from Service Location to Service, Boarding Loc and Transfer Ready DtTm tmp entry]] and [[2025-05 Revision of concept around ICUotherService]]. 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:
* [[Service tmp entry]] for the service
* [[Boarding Loc]] for the physical 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.


== 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]]
Retrieved from "https://ccmdb.kuality.ca/index.php?title=Service/Location_field"