CCU Service Tracking: Difference between revisions
Jump to navigation
Jump to search
Ttenbergen (talk | contribs) m →What if there is more than one: This section can be deleted when Julie has read. ~~~~ |
Ttenbergen (talk | contribs) m live now |
||
| Line 1: | Line 1: | ||
== Purpose == | == Purpose == | ||
We want to know how much of the load of the STB MICU is due to which service. | We want to know how much of the load of the STB MICU is due to which service. | ||
| Line 12: | Line 10: | ||
== Start/End Dates == | == Start/End Dates == | ||
*Start: | *Start: 2015-Jun-01 | ||
*End: there is no planned end date | *End: there is no planned end date | ||
Revision as of 09:48, 1 June 2015
Purpose
We want to know how much of the load of the STB MICU is due to which service.
Data Collection Instructions
For each patient occupying a STB MICU bed, enter the service they are admitted under. If the service changes during the stay, enter the new service as well.
- Project: CCU_Service
- Item: CCU or MICU
- start_dt: date of admission/service change
- start_tm: time of admission/service change
Start/End Dates
- Start: 2015-Jun-01
- End: there is no planned end date
Template:CCMDB Data Integrity Checks
- query s_tmp_CCU_Service_missing - each STB_MICU pt has to have at least one
- query s_tmp_CCU_Service_shouldntve - no pt not STB_MICU can have any
- query s_tmp_CCU_Service_twins - can't have two entries that are the same (ie same service and time)
- added code to check that same service in consecutive sequence is not allowed
What if there is more than one
- Julie said: More than one CCU or MICU scenario – we need a label or counter maybe under the integer (say 1- first case, 2- second case and so on) to be explicit. Or we can be implicit by just looking at the dates sequence but there will be a problem when DC change any previously entered date(s).
- I don't understand the scenario you describe. Are you concerned about accidental, unintended edits by collectors? Either way, wouldn't the entry still be consistent even if the date were edited? Ttenbergen 14:54, 2015 May 27 (CDT)
- example is CCU-MICU-CCU or MICU-CCU-MICU . there is a second CCU or MICU service which is real, how will it be differentiated with entry error/edit?
- The later entry would have a different date. Do we need more than that? Ttenbergen 15:41, 2015 May 28 (CDT)
- I am OK with the dates as long as there are no two consecutive dates of same service that will show up. The data must have a date sequence of alternating service (CCU-MICU-CCU or MICU-CCU-MICU) and not CCU-CCU-MICU or MICU-MICU-CCU.
- OK, I have added that one to cross checks. This section can be deleted when Julie has read. Ttenbergen 09:51, 2015 June 1 (CDT)
- I am OK with the dates as long as there are no two consecutive dates of same service that will show up. The data must have a date sequence of alternating service (CCU-MICU-CCU or MICU-CCU-MICU) and not CCU-CCU-MICU or MICU-MICU-CCU.
- The later entry would have a different date. Do we need more than that? Ttenbergen 15:41, 2015 May 28 (CDT)
- example is CCU-MICU-CCU or MICU-CCU-MICU . there is a second CCU or MICU service which is real, how will it be differentiated with entry error/edit?
- I don't understand the scenario you describe. Are you concerned about accidental, unintended edits by collectors? Either way, wouldn't the entry still be consistent even if the date were edited? Ttenbergen 14:54, 2015 May 27 (CDT)
See also
see also STB Cardiac Care patients