DtTm for First Boarding Loc and First Service: Difference between revisions
Jump to navigation
Jump to search
Ttenbergen (talk | contribs) Created page with "Work in progress to replace Template:First Service and Boarding Loc same ~~~~ ---- 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 compared to new entries in CSS and CE. Once the patient is discharged for a given record, the first Boarding Loc DtTm to be consistent with the first Service tmp entry; see . This is because we do..." |
Ttenbergen (talk | contribs) mNo edit summary |
||
| Line 6: | Line 6: | ||
Once the patient is discharged for a given record, the first [[Boarding Loc]] DtTm to be consistent with the first [[Service tmp entry]]; see . 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]]; see . 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. | ||
== Background == | === Example === | ||
* when a patient is transferred to one of our units, eventually the first [[Service tmp entry]] service and first [[boarding Loc]] will have to be the same date and time (we have a [[query check_tmp_Boarding_Loc_Service_first_same | cross-check]] for this). However, often they are not the same in Cognos. In these cases, always use the first actual Cognos service entry with its Cognos date and time as your first [[Service tmp entry]]. If that is different from the first Cognos unit entry (which you would use as your first [[Boarding Loc]] entry, that is OK ''for the time being'')(make a note in the [[Notes field]] to change to the first [[Boarding Loc]] date and time at a later date when reviewing the chart so you know BL needs changing, not Service). | |||
*example- patient transfers from ICU to medical unit. first medicine service=May10@1400, First boarding loc=May10@1630. While the correct first service and first [[Boarding Loc]] should be May 10@1630, enter the first service date and time from COGNOS for both first service (May 10@1400). There are two reasons for this; if you change the first service date and time without excluding that service it will fill up your CSS and you will not get the associated service end date and time. If you exclude then that service entry all together or change the time then the record will not show up in [[Cognos2 Ender]]. | |||
=== 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. | 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. | ||
Revision as of 12:59, 25 January 2023
Work in progress to replace Template:First Service and Boarding Loc same Ttenbergen 12:15, 2023 January 25 (CST)
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 compared to new entries in CSS and CE.
Once the patient is discharged for a given record, the first Boarding Loc DtTm to be consistent with the first Service tmp entry; see . 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
- when a patient is transferred to one of our units, eventually the first Service tmp entry service and first boarding Loc will have to be the same date and time (we have a cross-check for this). However, often they are not the same in Cognos. In these cases, always use the first actual Cognos service entry with its Cognos date and time as your first Service tmp entry. If that is different from the first Cognos unit entry (which you would use as your first Boarding Loc entry, that is OK for the time being)(make a note in the Notes field to change to the first Boarding Loc date and time at a later date when reviewing the chart so you know BL needs changing, not Service).
- example- patient transfers from ICU to medical unit. first medicine service=May10@1400, First boarding loc=May10@1630. While the correct first service and first Boarding Loc should be May 10@1630, enter the first service date and time from COGNOS for both first service (May 10@1400). There are two reasons for this; if you change the first service date and time without excluding that service it will fill up your CSS and you will not get the associated service end date and time. If you exclude then that service entry all together or change the time then the record will not show up in Cognos2 Ender.
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: |