Boarding Loc: Difference between revisions

(9 intermediate revisions by 3 users not shown)

Line 15:

==== [[CSS]] / [[Cognos2 Unit Starter]] ====

Usually the Cognos Unit start time from [[CSS]] or [[Cognos2 Unit Starter]] can be used as [[Boarding Loc]].

* sometimes the first [[Service tmp entry]] and first and second [[Boarding Loc]]~~may~~ all have the same date and time~~. The date and time for these entries must be confirmed by looking at the chart, specifically orders, flowsheets, and progress notes~~

* sometimes the first [[Service tmp entry]] and first and second [[Boarding Loc]] all have the same date and time; see [[#Special Case - Can't have two Boarding Locs with same DtTm]]

==== First set of vital signs for CC ====

[[ICU Curriculum]]: The first set of vital signs is used as [[Boarding Loc]] dttm for arrival on the unit for [[Critical Care program]] admissions, if it is different from the Cognos Unit Start DtTm.

Line 24:

Line 25:

=== How to enter ===

You can use the [["make loc" button]] to generate and pre-populate these entries.

*Use tmp fields:

** Project: '''{{PAGENAME}}'''

Line 33:

Line 34:

** Item:

*** for the initial unit or ER and each physical move to another unit, enter the location by using the "make loc" button in [[Patient Viewer Tab Cognos ADT2]]

*** ~~please note that~~ if a boarding location appears in COGNOS but the patient does NOT move/arrive to that boarding location, do NOT enter that boarding location. We only capture boarding locations where the patient physically arrives

*** if a boarding location appears in COGNOS but the patient does NOT move/arrive to that boarding location, do NOT enter that boarding location. We only capture boarding locations where the patient physically arrives (also see [[Wrong service or unit entries in Cognos]])

**** if the ward is not available in the dropdown, please notify Tina, Lisa, and Julie; Tina/Lisa will add the location to the dropdown and update the wiki as needed~~; Julie will note the change for her reports. eg. during the various COVID waves, many surgical wards were used for medicine overflow or COVID patients~~

**** if the ward is not available in the dropdown, please notify Tina, Lisa, and Julie; Tina/Lisa will add the location to the dropdown and update the wiki as needed

{{Discuss |

**** leave what is in Cognos, the main office doesn't use this part for anything for home locations, but it can be used to crosscheck accuracy.

***** what is this about? [[User:Ttenbergen|Ttenbergen]] 17:42, 19 August 2025 (CDT)

}}

* '''no location entered''' is the default

** that entry will not be allowed in a complete record; it is automatically deleted when by Cognos Make Loc button, but needs to be removed before setting a record to complete if it is still present.

Line 46:

Line 50:

==== Special Case - Can't have two Boarding Locs with same DtTm ====

* No two different [[Boarding Loc]] ~~recordss should~~ have same start_dt and start_tm~~.'''~~

* No two different [[Boarding Loc]] records can have same start_dt and start_tm; if two locations have the same Start_DtTm in [[CSS]]/[[Cognos2 Unit Starter]] this is an error.

** if two locations have the same Start_DtTm in [[CSS]]/[[Cognos2 Unit Starter]] this is an error~~. Change one to be off by one minute, put a note in [[Notes field]] to check boarding location to confirm the correct date and time for the boarding locations of concern~~.

* The date and time for these entries must be confirmed by looking at the chart, specifically orders, flowsheets, and progress notes

** This case is especially common in the context of [[DtTm for First Boarding Loc and First Service]]

{{DJ | It says:

* Change one to be off by one minute, put a note in [[Notes field]] to check boarding location to confirm the correct date and time for the boarding locations of concern.

** how does that fit in with reviewing reality in the chart?

** I don't know what you mean by this? It means you double check the correct first service and first and second boarding loc dttm [[User:Lkaita|Lisa Kaita]] 21:14, 6 September 2025 (CDT)

*** Well, it seems like this triggers an error check, so you pull the times a minute apart to overcome the error check and put a note to remind you to check later. So either the check should run later (on complete or send) or we shouldn't have it at all. But a check that just gets you to "tweak" the data to make it go away isn't a good idea.

* sure if you can have the cross check on completion that would be better, the prior scenario is almost always for SICU admissions from ER [[User:Lkaita|Lisa Kaita]] 15:51, 26 November 2025 (CST)

** Julie, do you use Boarding Loc info on incomplete charts? Would either the current collection practice, or delaying the check, mess with measures or indicators? [[User:Ttenbergen|Ttenbergen]] 22:09, 26 November 2025 (CST)

}}

* This case is especially common in the context of [[DtTm for First Boarding Loc and First Service]]

{{Ex |

* Example: Not infrequently, the COGNOS data for HSC_SICU patients coming from the ER will show the first service, first boarding location (ER) and the second boarding location (SICU) as all having the same start_DtTm. Our solution for this is to change the second boarding location (SICU) to be off by one minute.

Line 70:

Line 82:

* I have no idea, I suppose this can happen although I have not ever seen this at any of the facilities, I believe you were the original author of this so feel free to do what you want with this [[User:Lkaita|Lisa Kaita]] 13:46, 6 August 2025 (CDT)

** Julie, do you know what this is about? If the same applies for Med as for ICU in this, then lets get rid of the confusing entry. [[User:Ttenbergen|Ttenbergen]] 17:23, 6 August 2025 (CDT)

*** we have one case S4_STB_Med-2892 where first3 days at SBGH ICMS then transferred to SBGH-L2CC.--[[User:JMojica|JMojica]] 16:42, 18 August 2025 (CDT)

**** What else would they use? The entry would come from Cognos, no? It's entered by drop-down, so I don't think they could enter anything but the actual entry. Is this stated here really as a reminder for you, in case this happens again? If so, would it be better to store it in L_Problems table? If it is an instruction to collectors, would you explain further what you actually intend? [[User:Ttenbergen|Ttenbergen]] 17:33, 19 August 2025 (CDT)

}}

@@ Line 15: / Line 15: @@
 ==== [[CSS]] / [[Cognos2 Unit Starter]] ====
 Usually the Cognos Unit start time from [[CSS]] or [[Cognos2 Unit Starter]] can be used as [[Boarding Loc]].
-* sometimes the first [[Service tmp entry]] and first and second [[Boarding Loc]]may all have the same date and time.  The date and time for these entries must be confirmed by looking at the chart, specifically orders, flowsheets, and progress notes
+* sometimes the first [[Service tmp entry]] and first and second [[Boarding Loc]] all have the same date and time; see [[#Special Case - Can't have two Boarding Locs with same DtTm]]
 ==== First set of vital signs for CC ====
 [[ICU Curriculum]]: The first set of vital signs is used as [[Boarding Loc]] dttm for arrival on the unit for [[Critical Care program]] admissions, if it is different from the Cognos Unit Start DtTm.
@@ Line 24: / Line 25: @@
 === How to enter ===
 You can use the [["make loc" button]] to generate and pre-populate these entries.
 *Use tmp fields:
 ** Project: '''{{PAGENAME}}'''
@@ Line 33: / Line 34: @@
 ** Item:
 *** for the initial unit or ER and each physical move to another unit, enter the location by using the "make loc" button in [[Patient Viewer Tab Cognos ADT2]]
-*** please note that if a boarding location appears in COGNOS but the patient does NOT move/arrive to that boarding location, do NOT enter that boarding location.  We only capture boarding locations where the patient physically arrives
+*** if a boarding location appears in COGNOS but the patient does NOT move/arrive to that boarding location, do NOT enter that boarding location.  We only capture boarding locations where the patient physically arrives (also see [[Wrong service or unit entries in Cognos]])
-**** if the ward is not available in the dropdown, please notify Tina, Lisa, and Julie; Tina/Lisa will add the location to the dropdown and update the wiki as needed; Julie will note the change for her reports. eg. during the various COVID waves, many surgical wards were used for medicine overflow or COVID patients
+**** if the ward is not available in the dropdown, please notify Tina, Lisa, and Julie; Tina/Lisa will add the location to the dropdown and update the wiki as needed
+{{Discuss |
 **** leave what is in Cognos, the main office doesn't use this part for anything for home locations, but it can be used to crosscheck accuracy.
+***** what is this about? [[User:Ttenbergen|Ttenbergen]] 17:42, 19 August 2025 (CDT)
+}}
 * '''no location entered''' is the default
 ** that entry will not be allowed in a complete record; it is automatically deleted when by Cognos Make Loc button, but needs to be removed before setting a record to complete if it is still present.
@@ Line 46: / Line 50: @@
 ==== Special Case - Can't have two Boarding Locs with same DtTm ====
-* No two different [[Boarding Loc]] recordss should have same start_dt and start_tm.'''
+* No two different [[Boarding Loc]] records can have same start_dt and start_tm; if two locations have the same Start_DtTm in [[CSS]]/[[Cognos2 Unit Starter]] this is an error.
-** if two locations have the same Start_DtTm in [[CSS]]/[[Cognos2 Unit Starter]] this is an error. Change one to be off by one minute, put a note in [[Notes field]] to check boarding location to confirm the correct date and time for the boarding locations of concern.
 * The date and time for these entries must be confirmed by looking at the chart, specifically orders, flowsheets, and progress notes
-** This case is especially common in the context of [[DtTm for First Boarding Loc and First Service]]
+{{DJ | It says:
+* Change one to be off by one minute, put a note in [[Notes field]] to check boarding location to confirm the correct date and time for the boarding locations of concern.
+** how does that fit in with reviewing reality in the chart?
+** I don't know what you mean by this?  It means you double check the correct first service and first and second boarding loc dttm [[User:Lkaita|Lisa Kaita]] 21:14, 6 September 2025 (CDT)
+*** Well, it seems like this triggers an error check, so you pull the times a minute apart to overcome the error check and put a note to remind you to check later. So either the check should run later (on complete or send) or we shouldn't have it at all. But a check that just gets you to "tweak" the data to make it go away isn't a good idea.
+* sure if you can have the cross check on completion that would be better, the prior scenario is almost always for SICU admissions from ER [[User:Lkaita|Lisa Kaita]] 15:51, 26 November 2025 (CST)
+** Julie, do you use Boarding Loc info on incomplete charts? Would either the current collection practice, or delaying the check, mess with measures or indicators? [[User:Ttenbergen|Ttenbergen]] 22:09, 26 November 2025 (CST)
+}}
+* This case is especially common in the context of [[DtTm for First Boarding Loc and First Service]]
 {{Ex |
 * Example: Not infrequently, the COGNOS data for HSC_SICU patients coming from the ER  will show the first service, first boarding location (ER) and the second boarding location (SICU) as all having the same start_DtTm. Our solution for this is to change the second boarding location (SICU) to be off by one minute.
@@ Line 70: / Line 82: @@
 * I have no idea, I suppose this can happen although I have not ever seen this at any of the facilities, I believe you were the original author of this so feel free to do what you want with this [[User:Lkaita|Lisa Kaita]] 13:46, 6 August 2025 (CDT)
 ** Julie, do you know what this is about? If the same applies for Med as for ICU in this, then lets get rid of the confusing entry. [[User:Ttenbergen|Ttenbergen]] 17:23, 6 August 2025 (CDT)
+*** we have one  case S4_STB_Med-2892 where first3 days at SBGH ICMS then transferred to SBGH-L2CC.--[[User:JMojica|JMojica]] 16:42, 18 August 2025 (CDT)
+**** What else would they use? The entry would come from Cognos, no? It's entered by drop-down, so I don't think they could enter anything but the actual entry. Is this stated here really as a reminder for you, in case this happens again? If so, would it be better to store it in L_Problems table? If it is an instruction to collectors, would you explain further what you actually intend?  [[User:Ttenbergen|Ttenbergen]] 17:33, 19 August 2025 (CDT)
 }}