Service/Location field: Difference between revisions

(95 intermediate revisions by 10 users not shown)

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~~.

{{DJ |

* [[JALT Meeting - Rolling Agenda and Minutes 2025#JALT 2025-12-18 | 2025-12-18 JALT]] - the notes about [[2025-05 Revision of concept around ICUotherService]] / [[Intended1stSrvc]] also talked about [[Service/Location]] being made consistent with [[Boarding Loc]]; did we decide to proceed with this? The change to [[s_dispo table]] would be easy, but it would also apply to eg [[Previous Location]], and any cross-checks or report using string literals to match would be affected, so testing the impact would be harder. [[User:Ttenbergen|Ttenbergen]] 02:42, 24 December 2025 (CST)

}}

~~Patients boarding~~ on ~~other wards or units~~ are ~~coded~~ as the ~~home unit~~. ~~Collectors~~ can ~~use~~ "~~record~~" field for ~~tracking actual location~~.

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

{{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 [[Intended1stSrvc]]

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

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

~~== Collection Instruction ==~~

'''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.

~~essentially like [[Location]] is done now~~

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'''.

~~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.~~

* In the Prev Service location drop-down list has one selection ("Other) then states "known but on our list"....shouldn't it be "Known but not on our list"?--[[User:Llemoine|Llemoine]] 07:47, 2016 March 24 (CDT)

** 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

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

~~To be filled in~~

== ~~Reports~~ ==

== Integrity checks ==

~~To be filled in~~

== ~~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~~

[[Category: 2016 Time and Place changes]]

[[Category:2016 Time and Place changes]]

[[Category:Registry Data]]

[[Category:Data Collection Guide]]

@@ 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.
+{{DJ |
+* [[JALT Meeting - Rolling Agenda and Minutes 2025#JALT 2025-12-18 | 2025-12-18 JALT]] - the notes about [[2025-05 Revision of concept around ICUotherService]] / [[Intended1stSrvc]] also talked about [[Service/Location]] being made consistent with [[Boarding Loc]]; did we decide to proceed with this? The change to [[s_dispo table]] would be easy, but it would also apply to eg [[Previous Location]], and any cross-checks or report using string literals to match would be affected, so testing the impact would be harder. [[User:Ttenbergen|Ttenbergen]] 02:42, 24 December 2025 (CST)
+}}
-Patients boarding on other wards or units are coded as the home unit. Collectors can use "record" field for tracking actual location.
+== 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.
+{{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 [[Intended1stSrvc]]
+{{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]].
-== Collection Instruction ==
+'''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.
-essentially like [[Location]] is done now
+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'''.
-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.
+{{Location dropdown cleanup}}
-* In the Prev Service location drop-down list has one selection ("Other) then states "known but on our list"....shouldn't it be "Known but not on our list"?--[[User:Llemoine|Llemoine]] 07:47, 2016 March 24 (CDT)
-** 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
 == 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.
-To be filled in
-== 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:Registry Data]]
+[[Category:Data Collection Guide]]