Off ward field: Difference between revisions

From CCMDB Wiki
Jump to navigation Jump to search
m (cat)
Line 52: Line 52:
[[Category: Registry Data]]
[[Category: Registry Data]]
[[Category: L_Log table]]
[[Category: L_Log table]]
[[Category: Overflow]]

Revision as of 13:26, 2016 October 31

The Off ward field is set to true if the patient spent any time in an off-ward bed between Arrive DtTm and Dispo DtTm.

Collection Instructions

The field is located underneath the Service/Location field.

If the patient meets the definition at the top, check the "off ward" checkbox.

The Pre-admit Inpatient Institution field and Previous Location field of the next encounter would use the Service/Location field of the previous collection location where available, not the off-ward location.

The Service/Location field would contain the laptop's regular collection location, not the off-ward location.

The Dispo field of the next encounter would use the Service/Location field of the next collection location where available, not the off-ward location.

Questions

Not intended for off-ward tests

Question - This does replace other off-ward collection

Template:Discussion

  • I am unclear as to the definition of "Off Ward".....does this apply to ICU patients only? Does this apply to HSC and STB only? Is the "any time off ward" meant to replace the previous OVZ concept (Var 5) that is currently used for medicine? Could some examples/scenarios please be provided? Thanks, Pamela Piche 08:19, 2016 June 30 (CDT)
    • Yes, we used to do this differently for ICU and Med, this new way of doing it replaces that. Only place that still does something else is CCU Service Tracking and only at STB.m Ttenbergen 10:33, 2016 July 4 (CDT)


EMIP

EMIPs are in their collection location, e.g. GRA_EMIP, so they are not off ward. Don't check the field.

Parked in ER

Parked in ER (which we will no longer collect) for ICU transfers is before Arrive DtTm, so they are not "off ward". Don't check the field. Does this refer to the D4 beds temporarily on H7a and all our patients sitting on RR6 as we keep them under our initial ward profile location?

Data Use

Relevant to occupancy and some patient risks.

See also

Legacy

initial mis-connection

From 2016-07-01 to 2016-08-?? the control for this field had been incorrectly connected to the pharm_complete field. Since medicine doesn't use that field we could reclaim data for medicine from there. CC uses the field so could not reclaim data for them. Data for CC will be reported starting 2016-09-01.

pre-2016 fields for similar content

We used to collect related information in multiple places. Once we are comfortable with the new dispo fields we want to stop collection of the old fields. The fields are:

Old data would be transferred to new fields where the translation is not ambiguous. We can keep a snapshot of Centralized with the data pre-translation in case we ever want to go back to it.