Boarding Loc: Difference between revisions

Line 20:

** Enter start_dt: '''arrival date at physical location''', under column E.

** Enter start_tm: '''arrival time at physical location''', under column M.

~~{{DiscussTask |~~

*** '''These will be the actual arrivals on the unit, which might of course be before the [[Accept DtTm]] / Service start dttm''' ( see [[#Why do we use the actual unit start dttm rather than the time they became our pt on a unit | why]])

*** ~~The~~ '''~~first''' entry for [[Boarding Loc]] and for [[Service tmp entry]] need to have~~ the ~~same date and time because we only care about~~ the ~~portion of time in that earliest location that was under our service. So~~, ~~e.g. if in ER the pt is accepted initially by surgery we don't care about the unit start date and time until our service takes over.~~

**** Flagging this: if we don't enter the actual unit start dttm (ie might be before ~~service start) then these won't line up with Cognos data, so will not proberly show up as having been entered. I think~~ the ~~actual unit start should be used and any stripping out of times is a matter of reporting. The corresponding entry in~~ [[~~Service tmp entry~~]] ~~will need to be updated accordingly. Ttenbergen 13:21, 2020 November 9~~ (~~CST)~~

***** why do we ~~need to collect information which are not directly related to CC or Int Med patients? regardless where we save~~ the data, we should be consistent. that is how we crosscheck errors (whether it is time,location, diagnosis, procedures). Is this a common situation or rare? if rare, then let it be an exception with Cognos data (e.g. not line up). if common, let us discuss in Task. --[[User:JMojica|JMojica]] 15:08, 2020 November 9 (CST)

****** We should collect the real data rather than ~~a made-up construct for two reasons: (1) it makes~~ the ~~meaning/definition of the date uniform: when the pt arrived on that unit as per ADT; if we collect it as you suggest then the meaning will be "either when they arrived or when~~ they became our ~~service"; so, more complicated definition, and it would re-encode something we already encode in service tmp instead. (2) If we encode some made-up date and time for~~ unit ~~start, then it will not link with the data in Cognos, so will always look as if not entered yet. [[User:Ttenbergen~~|~~Ttenbergen~~]] ~~10:50, 2020 November 18 (CST~~)

******* I have had several more requests to automate entering the ER start dates differently. We need to resolve this so we can either change the process or automate entering it "wrong". [[User:Ttenbergen|Ttenbergen]] 09:20, 2020 ~~November 26 (CST)~~

}}

** checkbox: not used for this project

** Item:

Line 46:

Line 40:

***Grace Main ICU Choose Boarding Location and GRA_MICU. Grace Recovery Room (ICU) Choose boarding location and GRA-recovery and enter comment Covid+ICU. For External(SDC/NFA) beds choose boarding loc and GRA-ICU boarding and enter exact location in comments.[[User:Gthomson2|Gthomson2]] 08:47, 2020 November 18 (CST)

**** These seem to be different from what is written up there. [[User:Ttenbergen|Ttenbergen]] 10:36, 2020 November 18 (CST)}}

==== Why do we use the actual unit start dttm rather than the time they became our pt on a unit ====

We decided to use the actual unit start dttm because as the start of the boarding loc entry for two reasons:

* it is the actual time a pt arrived on that unit, so it's a more intuitive data point for someone not familiar with our data

* it allows clean matching to Cognos entries so the various Cognos tools can identify if an entry has already been dealt with

=== Special Case - cross-program boarding ===

@@ Line 20: / Line 20: @@
 ** Enter start_dt: '''arrival date at physical location''', under column E.
 ** Enter start_tm: '''arrival time at physical location''', under column M.
-{{DiscussTask |
+*** '''These will be the actual arrivals on the unit, which might of course be before the [[Accept DtTm]] / Service start dttm''' ( see [[#Why do we use the actual unit start dttm rather than the time they became our pt on a unit | why]])<!-- as discussed at Task 2020-12-02 -->
-*** The '''first''' entry for [[Boarding Loc]] and for [[Service tmp entry]] need to have the same date and time because we only care about the portion of time in that earliest location that was under our service. So, e.g. if in ER the pt is accepted initially by surgery we don't care about the unit start date and time until our service takes over.
-**** Flagging this: if we don't enter the actual unit start dttm (ie might be before service start) then these won't line up with Cognos data, so will not proberly show up as having been entered. I think the actual unit start should be used and any stripping out of times is a matter of reporting. The corresponding entry in [[Service tmp entry]] will need to be updated accordingly.  Ttenbergen 13:21, 2020 November 9 (CST)
-***** why do we need to collect information which are not directly related to CC or Int Med patients?  regardless where we save the data, we should be consistent. that is how we crosscheck errors (whether it is time,location, diagnosis, procedures).  Is this a common situation or rare? if rare, then let it be an exception with Cognos data  (e.g. not line up).  if common, let us discuss in Task.  --[[User:JMojica|JMojica]] 15:08, 2020 November 9 (CST)
-****** We should collect the real data rather than a made-up construct for two reasons: (1) it makes the meaning/definition of the date uniform: when the pt arrived on that unit as per ADT; if we collect it as you suggest then the meaning will be "either when they arrived or when they became our service"; so, more complicated definition, and it would re-encode something we already encode in service tmp instead. (2) If we encode some made-up date and time for unit start, then it will not link with the data in Cognos, so will always look as if not entered yet. [[User:Ttenbergen|Ttenbergen]] 10:50, 2020 November 18 (CST)
-******* I have had several more requests to automate entering the ER start dates differently. We need to resolve this so we can either change the process or automate entering it "wrong". [[User:Ttenbergen|Ttenbergen]] 09:20, 2020 November 26 (CST)
-}}
 ** checkbox: not used for this project <!-- was used for cross checks in data before 2020-10-15 -->
 ** Item:
@@ Line 46: / Line 40: @@
 ***Grace Main ICU Choose Boarding Location and GRA_MICU. Grace Recovery Room (ICU) Choose boarding location and GRA-recovery and enter comment Covid+ICU. For External(SDC/NFA) beds choose boarding loc and GRA-ICU boarding and enter exact location in comments.[[User:Gthomson2|Gthomson2]] 08:47, 2020 November 18 (CST)
 ****  These seem to be different from what is written up there. [[User:Ttenbergen|Ttenbergen]] 10:36, 2020 November 18 (CST)}}
+==== Why do we use the actual unit start dttm rather than the time they became our pt on a unit ====
+We decided to use the actual unit start dttm because as the start of the boarding loc entry for two reasons:
+* it is the actual time a pt arrived on that unit, so it's a more intuitive data point for someone not familiar with our data
+* it allows clean matching to Cognos entries so the various Cognos tools can identify if an entry has already been dealt with
 === Special Case - cross-program boarding ===