Transfer Ready DtTm field
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 |
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 the history of this page for how it has been used at different times.
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?
|
Any of these criteria, for a patient going to a lower level of care, as per hierarchy below:
- The goal here is to identify the intention of the team to send the patient to a lower level if there was an available bed there.
- Obviously we don't always know the team's intentions, but if they do write them down, then USE THAT INFO.
- Regarding the statement that the patient is "medically stable"
- This phrase could mean that the person is improved enough to go elsewhere, but it does NOT necessarily mean that. For example it could technically indicate that the condition is not changing lately, which may or may NOT mean that they're ready to go elsewhere.
- Thus, by itself that phrase cannot be used alone to suggest the patient is transfer ready
- e.g. Deconditioned patient may be medically stable but intention can be to leave them where they are for now to re-condition
- e.g. Patient is medically stable but still needs a sitter --> another situation in which just being "medically stable" isn't sufficient to tell us if they're transfer ready
- In an ICU setting, you CAN take the following to indirectly indicate transfer ready to a lower level of care when nothing has been written:
- care is stepped down to WARD FREQUENCY (q4hrs or less) of vitals, off ALL forms of life support except possibly intermittent dialysis
- HSC_IICU consult is written
- In a ward setting, you can take the following to indirectly indicate transfer ready to a lower level of care when nothing has been written:
- care is stepped down to change iv meds to po, remove monitoring
- In either ICU or ward setting being made ACP-C can be taken as indirect evidence of being 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.
status changing back and forth
If a patient changes from being transfer ready back to not being transfer ready, collect the first time they are transfer ready on their current level of care. If they become no longer transfer ready, leave it alone, and if they become transfer ready again at the same level of care, retain only the original Transfer Ready DtTm for that level.
If the patient moves to a different (higher or lower) level of care, then enter an additional Transfer Ready DtTm tmp entry.
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