Service/Location field: Difference between revisions

(39 intermediate revisions by 4 users not shown)

Line 3:

| CCMDB_label = Service Location

| CCMDB_tab = Dispo

| element_description = ~~Legacy field replaced by [[Boarding Loc]] and [[Service tmp entry]]~~

| element_description = Encodes which program a record is part of.

| in_table = L_Log table

| data_type = number

Line 12:

| data_element_sort_index = 40

}}

~~Legacy field replaced by [[Boarding Loc]] and [[Service tmp entry]] as part of [[Change from Service Location to Service, Boarding Loc and Transfer Ready DtTm tmp entry]].~~

== Collection Instruction ==

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:

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_CC~~]], [[~~STB_CC~~]] for critical care

* [[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]])

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

== ICU Bed Borrow ==

* [[Service ~~tmp entry~~]] for ~~the~~ service

'''Bed Borrow Only'''

* [[Boarding Loc]] ~~for~~ the ~~physical~~ location

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

{{Location ~~dropdown cleanup}}~~

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

~~{{Guideline Minimal Data Set}}~~

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

=~~= Adding a~~ new ~~service/location~~ entry ==

#* [[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.

* ~~add to ''~~[[~~s_dispo table~~]]''

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

* add to ''[[~~s_locations_allowed_collection table~~]]''

}}

* ~~consider all checks in~~ [[~~:Category:~~Service/Location ~~check~~]] ~~to see if they need to be modified to work right for~~ the new ~~location~~.

~~== Data Use / Purpose ==~~

'''Bed and Service Borrow Scenarios'''

~~See~~ [[~~Site and Location table~~]] ~~for possible entries.~~

* see [[ICUotherService]]

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

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

}} }}

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

~~== Integrity checks ==~~

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

Line 53:

Line 72:

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

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

== Log / legacy ==

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.

Line 61:

Line 94:

[[Category: 2016 Time and Place changes]]

[[Category:2016 Time and Place changes]]

~~[[Category: Admit/Discharge~~]]

[[Category:Registry Data]]

[[Category: Registry Data]]

[[Category:Data Collection Guide]]

[[Category: Data Collection Guide]]

@@ Line 3: / Line 3: @@
 | CCMDB_label = Service Location
 | CCMDB_tab = Dispo
-| element_description = Legacy field replaced by [[Boarding Loc]] and [[Service tmp entry]]
+| element_description = Encodes which program a record is part of.
 | in_table = L_Log table
 | data_type = number
@@ Line 12: / Line 12: @@
 | data_element_sort_index = 40
 }}
-Legacy field replaced by [[Boarding Loc]] and [[Service tmp entry]] as part of [[Change from Service Location to Service, Boarding Loc and Transfer Ready DtTm tmp entry]].
 == Collection Instruction ==
-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:
+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_CC]], [[STB_CC]] for critical care
+* [[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]])
-The concepts that used to be stored in this are essentially now stored as:
+== ICU Bed Borrow ==
-* [[Service tmp entry]] for the service
+'''Bed Borrow Only'''
-* [[Boarding Loc]] for the physical location
+* 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=
-{{Location dropdown cleanup}}
+# 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.
-{{Guideline Minimal Data Set}}
+#*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:
-== Adding a new service/location entry ==
+#* [[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.
-* add to ''[[s_dispo table]]''
+#*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]].
-* add to ''[[s_locations_allowed_collection table]]''
+}}
-* consider all checks in [[:Category:Service/Location check]] to see if they need to be modified to work right for the new location.
-== Data Use / Purpose ==
+'''Bed and Service Borrow Scenarios'''
-See [[Site and Location table]] for possible entries.
+* see [[ICUotherService]]
-Used to determine the location or services the patient went during a hospital stay.
+{{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)
+}} }}
-Used to categorize/stratify the distribution of patients across hospitals and wards/units when reporting summary statistics.
-== Integrity checks ==
+{{Guideline Minimal Data Set}}
-{{Data Integrity Check List}}
 == 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 ===
@@ Line 53: / Line 72: @@
 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 ==
+{{Location dropdown cleanup}}
-This field is subject to [[Change from Service Location to Service, Boarding Loc and Transfer Ready DtTm tmp entry]].
+== 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 Check List}}
+== Log / legacy ==
+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.
@@ Line 61: / Line 94: @@
 {{Related Articles}}
-[[Category: 2016 Time and Place changes]]
+[[Category:2016 Time and Place changes]]
-[[Category: Admit/Discharge]]
+[[Category:Registry Data]]
-[[Category: Registry Data]]
+[[Category:Data Collection Guide]]
-[[Category: Data Collection Guide]]