DeviceUse Study: Difference between revisions
Jump to navigation
Jump to search
Ttenbergen (talk | contribs) mNo edit summary |
TOstryzniuk (talk | contribs) |
||
| Line 19: | Line 19: | ||
{{Discussion}} | {{Discussion}} | ||
Because the DeviceUse data will be repeatedly send each week to L_TMPV2, the collectors must be precise when entering dates and time for devices and not be putting dummy times in and keep changing them. The statistician will be reporting this information weekly regardless if the rest of file is completed or not. Will need to discuss this more later. | Because the DeviceUse data will be repeatedly send each week to L_TMPV2, the collectors must be precise when entering any dates and time for devices and not be putting dummy times in and keep changing them. The statistician will be reporting this information weekly regardless if the rest of file is completed or not. Will need to discuss this more later. | ||
**Is anyone else going to have a hard time getting precise '''times''' when entering the dates? I think this will be a challenge! [[User:GHall|GHall]] 20:26, 6 September 2011 (CDT) | **Is anyone else going to have a hard time getting precise '''times''' when entering the dates? I think this will be a challenge! [[User:GHall|GHall]] 20:26, 6 September 2011 (CDT) | ||
*** I wonder if the focus is on ''actual'' times rather than dummy ones; considering the paragraph then explains that the data will be sent every time, I would think that that is what this is about more than accuracy. [[User:Ttenbergen|Ttenbergen]] 09:38, 7 September 2011 (CDT) | *** I wonder if the focus is on ''actual'' times rather than dummy ones; considering the paragraph then explains that the data will be sent every time, I would think that that is what this is about more than accuracy. [[User:Ttenbergen|Ttenbergen]] 09:38, 7 September 2011 (CDT) | ||
****We will pilot the process first and find out what the issue might be in obtaining this data and work them out before we actually launch. The only way we will know if there will be issues dates and in particular, times, is when we actually test the process first and find out.--[[User:TOstryzniuk|TOstryzniuk]] 17:52, 7 September 2011 (CDT) | |||
==Items Collected== | ==Items Collected== | ||
Revision as of 16:52, 2011 September 7
Project Name
DeviseUse Study
Purpose
Patient quality of care improvements in Critical Care.
- Monitor resource allocation and monitor complication rates related to length of ICU medical device use. (VAP, Central Line Related Blood stream Infection (CLR-BSI), unplanned extubations)
Who
Information to be collected from charts daily by Regional Database Team - Critical Care areas.
- Monitoring being done by the Critical Care QA Team along with the cross Canada ICU collaborative project teams CCVSM.
Where
Collected in L_Tmp
- Deposited into data repository L TmpV2 in the output folder on the Regional Server.
How often data is sent
- Information sent each week with sending to L TmpV2 even though patient files is not complete.
Template:Discussion Because the DeviceUse data will be repeatedly send each week to L_TMPV2, the collectors must be precise when entering any dates and time for devices and not be putting dummy times in and keep changing them. The statistician will be reporting this information weekly regardless if the rest of file is completed or not. Will need to discuss this more later.
- Is anyone else going to have a hard time getting precise times when entering the dates? I think this will be a challenge! GHall 20:26, 6 September 2011 (CDT)
- I wonder if the focus is on actual times rather than dummy ones; considering the paragraph then explains that the data will be sent every time, I would think that that is what this is about more than accuracy. Ttenbergen 09:38, 7 September 2011 (CDT)
- We will pilot the process first and find out what the issue might be in obtaining this data and work them out before we actually launch. The only way we will know if there will be issues dates and in particular, times, is when we actually test the process first and find out.--TOstryzniuk 17:52, 7 September 2011 (CDT)
- I wonder if the focus is on actual times rather than dummy ones; considering the paragraph then explains that the data will be sent every time, I would think that that is what this is about more than accuracy. Ttenbergen 09:38, 7 September 2011 (CDT)
- Is anyone else going to have a hard time getting precise times when entering the dates? I think this will be a challenge! GHall 20:26, 6 September 2011 (CDT)
Items Collected
S_Tmp:
- Art line_IN - date & time
- Art line_OUT - date & time
- Central line_IN - date & time
- Central line_OUT
- PICC line _IN - date & time
- PICC line_OUT - date & time
- ETT_IN - date & time
- ETT_OUT - date & time - (bool_var) unplanned extubation check mark means YES
- Trach_IN - date & time
- Trach_OUT - date & time
- Vent start_IN - date & time
- Vent stop_OUT - date & time
- DC Vent will be defined as OFF the ventilator for >=48 hrs
- BIPAP start_IN - date & time
- BIPAP stop_OUT - date & time
- DC BIPAP will be defined as OFF the ventilator for >=24 hrs
Start Date
Stop Date
Analysis
Will be handled by Statistician
- number of central line days between Central Line Related Blood stream Infection (CLR-BSI)
- number of Vent days between Central Line Related Blood stream Infection (CLR-BSI)
- number of Vent days between unplanned extubations
- number of Vent days between VAP??
--TOstryzniuk 18:02, 31 August 2011 (CDT)