DtTm for First Boarding Loc and First Service: Difference between revisions
Ttenbergen (talk | contribs) mNo edit summary |
Ttenbergen (talk | contribs) m remove |
||
| Line 1: | Line 1: | ||
When data is first entered as per [[Using Cognos2 to keep track of patients]], the [[Service tmp entry]] is entered as in the [[Cognos2]] data. This is so the data can be matched to new entries in [[Cognos2 Service Starter]] and [[Cognos2 Ender]]. Some collectors were entering a "corrected" DtTm instead and "excluding" the record instead, but that would mean it doesn't show up in [[Cognos2 Ender]]. | |||
Once the patient is discharged for a given record, the first [[Boarding Loc]] DtTm is changed to be consistent with the first [[Service tmp entry]]. This is because we do not want to include time spent at a [[Boarding Loc]] under a different service in our reporting. It also allows us to do a cross-check [[query check_tmp_Boarding_Loc_Service_first_same]] to prevent accidental inconsistencies. | |||
Once the patient is discharged for a given record, the first [[Boarding Loc]] DtTm to be consistent with the first [[Service tmp entry]] | |||
=== Example === | === Example === | ||
Patient transfers from ICU to medical unit. Enter the unit and service including DtTm as they are in Cognos. | |||
When the patient is discharged from the service followed by your laptop, you will get a notification in [[Cognos2 Ender]]. At this point, or before setting the [[RecordStatus]] to "complete", do any needed corrections to the service start dttm, and then set the first [[Boarding Loc]] to the same value as the first [[Service tmp entry]]. | |||
=== Background === | === Background === | ||
Revision as of 13:23, 25 January 2023
When data is first entered as per Using Cognos2 to keep track of patients, the Service tmp entry is entered as in the Cognos2 data. This is so the data can be matched to new entries in Cognos2 Service Starter and Cognos2 Ender. Some collectors were entering a "corrected" DtTm instead and "excluding" the record instead, but that would mean it doesn't show up in Cognos2 Ender.
Once the patient is discharged for a given record, the first Boarding Loc DtTm is changed to be consistent with the first Service tmp entry. This is because we do not want to include time spent at a Boarding Loc under a different service in our reporting. It also allows us to do a cross-check query check_tmp_Boarding_Loc_Service_first_same to prevent accidental inconsistencies.
Example
Patient transfers from ICU to medical unit. Enter the unit and service including DtTm as they are in Cognos. When the patient is discharged from the service followed by your laptop, you will get a notification in Cognos2 Ender. At this point, or before setting the RecordStatus to "complete", do any needed corrections to the service start dttm, and then set the first Boarding Loc to the same value as the first Service tmp entry.
Background
We decided during Task Team Meeting - Rolling Agenda and Minutes 2021#ICU Database Task Group Meeting – April 22, 2021 that the first Service tmp entry DtTm should be the same as that for the first Boarding Loc entry.
This decision was based on popular demand rather than logic, reason or data integrity. We had previously entered 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
Related articles
| Related articles: |