Off ward field: Difference between revisions
Ttenbergen (talk | contribs) m →Background: m |
Ttenbergen (talk | contribs) |
||
| Line 2: | Line 2: | ||
== Collection Instructions == | == Collection Instructions == | ||
The field is located | The field is located underneath the [[Service/Location field]]. | ||
If the patient spent any time beyond the difference between [[Accept DtTm]] and [[Arrive DtTm]] off ward, check the "off ward" checkbox. | If the patient spent any time beyond the difference between [[Accept DtTm]] and [[Arrive DtTm]] off ward, check the "off ward" checkbox. | ||
| Line 15: | Line 15: | ||
Need to address how to deal with EMIPs Ttenbergen 10:17, 2016 June 23 (CDT) | Need to address how to deal with EMIPs Ttenbergen 10:17, 2016 June 23 (CDT) | ||
The [[Pre-admit Inpatient Institution field]] | The [[Service/Location field]] would contain the laptop's regular collection location, not the off-ward location. | ||
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 [[Dispo field]] of the next encounter would use the [[Service/Location field]] of the next collection location where available, not the off-ward location. | |||
== Background == | == Background == | ||
Revision as of 10:34, 23 June 2016
The Off ward field is set to true if the patient spent any time off ward.
Collection Instructions
The field is located underneath the Service/Location field.
If the patient spent any time beyond the difference between Accept DtTm and Arrive DtTm off ward, check the "off ward" checkbox.
- we are working on a useful definition... Ttenbergen 10:17, 2016 June 23 (CDT)
- needs to be consistent with
Template:Discussion Need to address how to deal with EMIPs Ttenbergen 10:17, 2016 June 23 (CDT)
The Service/Location field would contain the laptop's regular collection location, not the off-ward location.
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 Dispo field of the next encounter would use the Service/Location field of the next collection location where available, not the off-ward location.
Background
needed
Data Use
needed
Legacy
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.