Transfer Ready DtTm field: Difference between revisions
Ttenbergen (talk | contribs) mNo edit summary |
Ttenbergen (talk | contribs) mNo edit summary |
||
Line 42: | Line 42: | ||
For each patient, | For each patient, | ||
* enter the first date/time of '''intent''' to transfer to lower level in the [[Level of care hierarchy]] is documented into the Transfer Ready Date and Time Field; see [[#status changing back and forth]] | * enter the first date/time of '''intent''' to transfer to lower level in the [[Level of care hierarchy]] is documented into the Transfer Ready Date and Time Field; see [[#status changing back and forth]] | ||
** if a patient '''arrives transfer-ready''' to a [[Level of care hierarchy | lower level]] of care '''than ''the current'' ward''' enter the same date into [[Transfer Ready DtTm field]] as in | ** if a patient '''arrives transfer-ready''' to a [[Level of care hierarchy | lower level]] of care '''than ''the current'' ward''' enter the same date into [[Transfer Ready DtTm field]] as in ''Arrive_DtTm field''. | ||
* if not available because the patient was '''clearly not transfer ready''', leave the date/time '''empty''' and enter "'''not transfer ready'''" into the "'''[[TR info status field]]'''" | * if not available because the patient was '''clearly not transfer ready''', leave the date/time '''empty''' and enter "'''not transfer ready'''" into the "'''[[TR info status field]]'''" | ||
* if not available but the patient probably was transfer ready and it just wasn't documented, leave the date/time '''empty''' and enter '''"not available"''' into the "'''[[TR info status field]]'''" | * if not available but the patient probably was transfer ready and it just wasn't documented, leave the date/time '''empty''' and enter '''"not available"''' into the "'''[[TR info status field]]'''" |
Revision as of 14:31, 21 April 2022
See Transfer Ready DtTm tmp entry
![]() |
Once the following query comes up empty this field should be removed from view in CCMDB.accdb
|
|
Legacy Content
This page contains Legacy Content.
- Explanation: This is a legacy data field, its DataElementEndDate is in the past.
- Successor: No successor was entered
Click Expand to show legacy content.
Data Element (edit) | |
Field Name: | Transfer_Ready_DtTm |
CCMDB Label: | Transfer Ready DtTm |
CCMDB tab: | Dispo |
Table: | L_Log table |
Data type: | date |
Length: | not stated |
Program: | Med and CC |
Created/Raw: | Raw |
Start Date: | 2016-07-01 |
End Date: | 2020-10-15 |
Sort Index: | 47 |
Data Dependencies(Reports/Indicators/Data Elements): | No results |
Date and time the intent to discharge a patient to a lower level in the Level of care hierarchy was documented.
See Transfer Ready DtTm tmp entry for what this field is about, or see the history of this page for how it has been used at different times before moving to the new field.
Collection Instruction
Entering a Transfer Ready DtTm
Follow the instructions in Transfer Ready DtTm tmp entry.
Before 2020-10-15 |
For each patient,
This entry is about the time of an intent, nothing to do with what actually happened to the patient after. |
What is transfer ready?
moved to Transfer Ready DtTm tmp entry#Transfer Ready
Hierarchy of levels of care
We require an entry in this field when the intent is to transfer from higher to lower level of care. See Level of care hierarchy for a list.
Cross Checks
Data Integrity Checks (automatic list)
App | Status | |
---|---|---|
Check Function Panelling admit transfer same | CCMDB.accdb | retired |
Query check dispo lower acuity than location | CCMDB.accdb | retired |
Link suspect transfer ready before arrive date | Centralized data front end.accdb | retired |
Legacy
Similar to the old Transfer Ready date and time, but we eliminated special cases and differences between medicine and critical care. Going forward the entry will be collected even if pt dies or goes to ER etc. It's the intent that counts, not what ended up happening. Resp. field names L_Log.R_TRDate and L_Log.R_TRTime