CCU Service Tracking: Difference between revisions

From CCMDB Wiki
Jump to navigation Jump to search
mNo edit summary
 
(40 intermediate revisions by 5 users not shown)
Line 1: Line 1:
{{Project
|ProjectActive=legacy
|ProjectProgram=CC
|ProjectRequestor=Unknown/legacy
|ProjectCollectionStartDate=2010-10-01
|ProjectCollectionStopDate=2016-07-07
|Project=CCU Service Tracking
}}
{{LegacyContent
|explanation=was replaced as part of [[2016 Time and Place changes]]
|successor=[[Previous Service field]]
|content=
== 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.  


== Data Collection Instructions ==
== Data Collection Instructions ==
For each patient occupying a STB MICU bed, that during their stay in MICU have been under Cardiology Service at any time, enter the service they are admitted under. If the service changes during the stay, enter the new service as well.  
For patients occupying a STB MICU or CICU bed and have been under Cardiology Service (as opposed to Cardiac Surgery) at any time, enter the service they are admitted under in tmp. If the service changes during the stay, enter a new tmp entry for the new service as well.  
*If a patient occupying a STB MICU bed remains under MICU coverage their entire stay, there is no need to make a tmp entry for CCU Service at all.   
 
If a patient occupying a STB MICU or CICU bed remains under their own service coverage their entire stay, there is no need to make a tmp entry for CCU Service at all.   
 
Use tmp fields:
* Project: '''CCU_Service'''
* Project: '''CCU_Service'''
* Item: '''CCU''' or '''MICU'''
* Item: '''CCU''' or '''MICU''' or '''CICU'''
* start_dt: date of admission/service change
* start_dt: '''date of service change'''
* start_tm: time of admission/service change
* start_tm: '''time of service change'''
** If the pt arrives under Cardiology (CCU) service the date and time for this tmp entry will be the same as the admission date and time to MICU.


== Start/End Dates ==
== Start/End Dates ==
*Start: 2015-Jun-01
*Start: 2015-Jun-01
*End: there is no planned end date
** added data back from Oct 1, 2010
*End: July 7, 2016 (we moved to using [[Previous Service field]]


=={{CCMDB Data Integrity Checks}}==
=== pre-start data===
* query ''s_tmp_CCU_Service_missing'' - each STB_MICU pt has to have at least one  
*Julie will go back to October 2010 to make all the profiles reflect the new method of tracking CCU service (previously had made another profile when the service changed, (ie start under cardiology then another profile if MICU took over care). This will be fixed for the sake of consistency of data.--[[User:LKolesar|LKolesar]] 13:37, 2015 August 11 (CDT)
** Done (07Aug2015) and all the patients under Cardiology service with admit dates from Oct 1, 2010 to May 31, 2015 are appended in  L_TmpV2 table of CFE. Included are those with whole stay at MICU under Cardiology service (N=586) and the 13 cases found with partial stay under Cardiology service  (i.e. they have 2 records in L_TmpV where the first one denotes the CCU service and the second one is the change to MICU service). [[User:JMojica|JMojica]] 17:00, 2015 August 11 (CDT)
 
==CCMDB Data Integrity Checks==
* query ''s_tmp_CCU_Service_shouldntve'' - no pt not STB_MICU can have any
* 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)
* 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
* added code to check that same service in consecutive sequence is not allowed


== What if there is more than one ==
== SAS Program ==
{{discussion}}
* The data is saved in table L_TmpV2 under project 'CCU Service' of the centralized_data.mdb
* 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).
* The SAS program that reads the data is in X:\Julie\SAS_CFE\CFE_macros\CFE_CCUServiceTracking.sas
** 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?
== Details ==
**** The later entry would have a different date. Do we need more than that? Ttenbergen 15:41, 2015 May 28 (CDT)
STB/MICU -Merged files
***** 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)
We had 13 patients edited manually - combined to one admission  (CCU in MICU under CCU care then transferred to MICU service. instead of having 2 admission in MICU, made it one.  The CCU Service Tracking in TMP had been updated due to these changes (i.e. two rows containing  ITEM=CCU and start date_time=admit date_time in CCU service as well as  ITEM=MICU and start date_time=admit date_time in MICU service  were added for each D_ID).
 
*STB_MICU-26117
**Merged into one all tables except old tiss in July 23, 2015.  Old tiss fixed and added May 10, 2017.  Kept 26117 and deleted STB_MICU-26128.
*STB_MICU-26611
**Merged into one all tables except old tiss in July 23, 2015.  Old tiss fixed and added May 10, 2017. Kept 26611 and deleted STB_MICU-26626
*STB_MICU-26683
**Merged into one all tables except old tiss in July 23, 2015. Old tiss fixed and added May 10, 2017. Kept 26683 and deleted STB_MICU-26695
*STB_MICU-27144
**Merged into one all tables except old tiss in July 23, 2015.  Old tiss fixed and added May 10, 2017. Kept 26117 and deleted STB_MICU-27161
*STB_MICU-27861
**Merged into one July 23, 2015.  Kept 27861 and deleted STB_MICU-27876
*STB_MICU-27917
**Merged into one July 23, 2015.  Kept 27917 and deleted STB_MICU-27930
*STB_MICU-28043
**Merged into one July 23, 2015. Kept 28043 and deleted STB_MICU-28048
*STB_MICU-28205
**Merged into one July 23, 2015. Kept 28205 and deleted STB_MICU-28216
*STB_MICU-28233
**Merged into one July 23, 2015.  Kept 28233 and deleted STB_MICU-28244
*STB_MICU-28330
**Merged into one July 23, 2015.  Kept 28330 and deleted STB_MICU-28340
*STB_MICU-28629
**Merged into one July 23, 2015. Kept 28629 and deleted STB_MICU-28652
*STB_MICU-28727
**Merged into one July 23, 2015.  Kept 28727 and deleted STB_MICU-28741
*STB_MICU-28884
**Merged into one July 23, 2015. Kept 28884 and deleted STB_MICU-28901
--[[User:PTorres|PTorres]] 10:02, 2015 October 2 --(CDT)[[User:PTorres|PTorres]] 16:54, 2017 May 10 (CDT)


== See also ==
see also [[STB Cardiac Care patients]]
see also [[STB Cardiac Care patients]]


{{Data Integrity Check List|}}


[[Category: St Boniface Hospital Office (Critical Care)]]
}}
[[Category: Site Specific Collection Guide]]
[[Category:L TmpV2 Data]]
[[Category: L_TmpV2 Data]]
[[Category:Legacy Overflow]]
[[Category: Special Short Term Projects]]
[[Category: All Projects ICU only]]

Latest revision as of 14:50, 2020 January 31

Projects
Active?: legacy
Program: CC
Requestor: Unknown/legacy
Collection start: 2010-10-01
Collection end: 2016-07-07

Legacy Content

This page contains Legacy Content.

Click Expand to show legacy content.

Purpose

We want to know how much of the load of the STB MICU is due to which service.

Data Collection Instructions

For patients occupying a STB MICU or CICU bed and have been under Cardiology Service (as opposed to Cardiac Surgery) at any time, enter the service they are admitted under in tmp. If the service changes during the stay, enter a new tmp entry for the new service as well.

If a patient occupying a STB MICU or CICU bed remains under their own service coverage their entire stay, there is no need to make a tmp entry for CCU Service at all.

Use tmp fields:

  • Project: CCU_Service
  • Item: CCU or MICU or CICU
  • start_dt: date of service change
  • start_tm: time of service change
    • If the pt arrives under Cardiology (CCU) service the date and time for this tmp entry will be the same as the admission date and time to MICU.

Start/End Dates

  • Start: 2015-Jun-01
    • added data back from Oct 1, 2010
  • End: July 7, 2016 (we moved to using Previous Service field

pre-start data

  • Julie will go back to October 2010 to make all the profiles reflect the new method of tracking CCU service (previously had made another profile when the service changed, (ie start under cardiology then another profile if MICU took over care). This will be fixed for the sake of consistency of data.--LKolesar 13:37, 2015 August 11 (CDT)
    • Done (07Aug2015) and all the patients under Cardiology service with admit dates from Oct 1, 2010 to May 31, 2015 are appended in L_TmpV2 table of CFE. Included are those with whole stay at MICU under Cardiology service (N=586) and the 13 cases found with partial stay under Cardiology service (i.e. they have 2 records in L_TmpV where the first one denotes the CCU service and the second one is the change to MICU service). JMojica 17:00, 2015 August 11 (CDT)

CCMDB Data Integrity Checks

  • 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

SAS Program

  • The data is saved in table L_TmpV2 under project 'CCU Service' of the centralized_data.mdb
  • The SAS program that reads the data is in X:\Julie\SAS_CFE\CFE_macros\CFE_CCUServiceTracking.sas

Details

STB/MICU -Merged files

We had 13 patients edited manually - combined to one admission (CCU in MICU under CCU care then transferred to MICU service. instead of having 2 admission in MICU, made it one. The CCU Service Tracking in TMP had been updated due to these changes (i.e. two rows containing ITEM=CCU and start date_time=admit date_time in CCU service as well as ITEM=MICU and start date_time=admit date_time in MICU service were added for each D_ID).

  • STB_MICU-26117
    • Merged into one all tables except old tiss in July 23, 2015. Old tiss fixed and added May 10, 2017. Kept 26117 and deleted STB_MICU-26128.
  • STB_MICU-26611
    • Merged into one all tables except old tiss in July 23, 2015. Old tiss fixed and added May 10, 2017. Kept 26611 and deleted STB_MICU-26626
  • STB_MICU-26683
    • Merged into one all tables except old tiss in July 23, 2015. Old tiss fixed and added May 10, 2017. Kept 26683 and deleted STB_MICU-26695
  • STB_MICU-27144
    • Merged into one all tables except old tiss in July 23, 2015. Old tiss fixed and added May 10, 2017. Kept 26117 and deleted STB_MICU-27161
  • STB_MICU-27861
    • Merged into one July 23, 2015. Kept 27861 and deleted STB_MICU-27876
  • STB_MICU-27917
    • Merged into one July 23, 2015. Kept 27917 and deleted STB_MICU-27930
  • STB_MICU-28043
    • Merged into one July 23, 2015. Kept 28043 and deleted STB_MICU-28048
  • STB_MICU-28205
    • Merged into one July 23, 2015. Kept 28205 and deleted STB_MICU-28216
  • STB_MICU-28233
    • Merged into one July 23, 2015. Kept 28233 and deleted STB_MICU-28244
  • STB_MICU-28330
    • Merged into one July 23, 2015. Kept 28330 and deleted STB_MICU-28340
  • STB_MICU-28629
    • Merged into one July 23, 2015. Kept 28629 and deleted STB_MICU-28652
  • STB_MICU-28727
    • Merged into one July 23, 2015. Kept 28727 and deleted STB_MICU-28741
  • STB_MICU-28884
    • Merged into one July 23, 2015. Kept 28884 and deleted STB_MICU-28901

--PTorres 10:02, 2015 October 2 --(CDT)PTorres 16:54, 2017 May 10 (CDT)

see also STB Cardiac Care patients

Data Integrity Checks (automatic list)

none found

Retrieved from "https://ccmdb.kuality.ca/index.php?title=CCU_Service_Tracking&oldid=141892"