BIPAP/CPAP Task: Difference between revisions
Jump to navigation
Jump to search
TOstryzniuk (talk | contribs) m m |
No edit summary |
||
| Line 13: | Line 13: | ||
== Patient managed? == | == Patient managed? == | ||
If a patient managing their own BiPAP then this should not be marked. However, if it was '''newly started''' during this admission, mark it. | If a patient managing their own BiPAP then this should not be marked. However, if it was '''newly started''' during this admission, mark it. | ||
**thanks for putting the question out here. The workload we track is for a new starts as instructed above. Patient manages own but nurse helping, not tracking. That is how medicine drew the line for this item. | **thanks for putting the question out here. The workload we track is for a new starts as instructed above. Patient manages own but nurse helping, not tracking. That is how medicine drew the line for this item. | ||
*This is difficult to differentiate as it is poorly documented sometimes. For example a pt that has been on cpap or bipap at home now comes into the hospital with a condition where they cannot manage the bipap on their own (like a stroke or fever, etc). It would be much simpler to identify all bipap patients rather then trying to figure out which patients can manage their bipap on their own. I wonder what the rationale for this was?? Some of our tasks are not done by ward nurses (like dialysis), but we still track this. --[[User:LKolesar|LKolesar]] 12:22, 2014 November 17 (CST) | *This is difficult to differentiate as it is poorly documented sometimes. For example a pt that has been on cpap or bipap at home now comes into the hospital with a condition where they cannot manage the bipap on their own (like a stroke or fever, etc). It would be much simpler to identify all bipap patients rather then trying to figure out which patients can manage their bipap on their own. I wonder what the rationale for this was?? Some of our tasks are not done by ward nurses (like dialysis), but we still track this. --[[User:LKolesar|LKolesar]] 12:22, 2014 November 17 (CST) | ||
Revision as of 15:11, 2014 November 19
The BIPAP/CPAP task encodes whether or not a medicine patient was newly started on your ward. It is stored in the Diagnosis tab in ccmdb.mdb because that is the only way we could store it when we started to collect it.
Only mark if this was a new start on your ward. If a task was done prior to patient coming to your ward or after patient is transferred to another ward, it should be marked as none during the stay on your ward.
- These items are included in: S_AllDiagnoses table which is in CCMDB.mdb.
Possible entries for BiPAP/CPAP:
Patient managed?
If a patient managing their own BiPAP then this should not be marked. However, if it was newly started during this admission, mark it.
- thanks for putting the question out here. The workload we track is for a new starts as instructed above. Patient manages own but nurse helping, not tracking. That is how medicine drew the line for this item.
- This is difficult to differentiate as it is poorly documented sometimes. For example a pt that has been on cpap or bipap at home now comes into the hospital with a condition where they cannot manage the bipap on their own (like a stroke or fever, etc). It would be much simpler to identify all bipap patients rather then trying to figure out which patients can manage their bipap on their own. I wonder what the rationale for this was?? Some of our tasks are not done by ward nurses (like dialysis), but we still track this. --LKolesar 12:22, 2014 November 17 (CST)
- Only used to track New starts for this item. No changes.Trish Ostryzniuk 16:56, 2014 November 17 (CST)
- Question answered. Please clean up article to just contain instruction. thanks for your input!
- Only used to track New starts for this item. No changes.Trish Ostryzniuk 16:56, 2014 November 17 (CST)
Optiflow
Optiflow is not CPAP or BIPAP so don't mark this task for patients with Optiflow.
Data Structure
the list of options is in S_AllDiagnoses and the actual data is stored in L_Dxs.
Legacy
Task items replaced iTISS December 15, 2006.