Transfer Ready DtTm field: Difference between revisions

From CCMDB Wiki
Jump to navigation Jump to search
m (→‎Legacy: cat)
 
(140 intermediate revisions by 13 users not shown)
Line 1: Line 1:
''This field is currently being implemented, please check the instructions and put a discussion for anything that isn't clear. ''
{{Data element
|field_name=Transfer_Ready_DtTm
|CCMDB_label=Transfer Ready DtTm
|CCMDB_tab=Dispo
|in_table=L_Log table
|data_type=date
|program_collecting=Med and CC
|created_raw=Raw
|data_element_start_date=1999-06-01
|data_element_end_date=2020-10-15
|data_element_sort_index=47
|element_description=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]]


The [[Transfer Ready DtTm field]] contains the date and time that the '''intent to discharge''' a patient to a lower level of care was documented. A "lower level of care" would be from an ICU to a ward, or from ward/ICU to hospital out of town, PCH, care facility or home.
The data in this field will be retained in [[Centralized data.mdb]]'s [[L_Log table]] since it doesn't follow the same pattern as the new entry. The field no longer exists in [[CCMDB data.mdb]].
 
 
 
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 ==
== Collection Instruction ==
=== Entering a Transfer Ready DtTm ===
Follow the instructions in [[Transfer Ready DtTm tmp entry]].
{{Collapsable
| always= Before 2020-10-15
| full= 
For each patient,  
For each patient,  
* if a date/time of '''intent''' to transfer to lower level of care is documented, enter it into the Transfer Ready Date and Time Field
* 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''' enter the same date into [[Transfer Ready DtTm field]] as in [[Arrive_DtTm field]].
** 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, 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]]'''"  
This entry has nothing to do with what actually happened to the patient after.
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]]


== Questions? ==
=== Hierarchy of levels of care ===
=== status changing back and forth ===
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.
* What about patients whose status changes from transfer ready to not ready? In old system, medicine would keep the transfer ready date and ICU would not. I have emailed Allan Garland for an answer. Ttenbergen 17:37, 2016 April 28 (CDT)


== Data Use ==
=== Collection Start Dates ===
Used to generate [[Transfer_Delay]], which is used in [[Overstay]] and several reports, see also [[Transfer_Delay#data use]].
* Critical Care: all units on board June 1, 1999
* Medicine : all wards on board Jan 1, 2005


== {{CCMDB Data Integrity Checks}} ==
== Cross Checks ==
* Function ''ADT_Chronological()''{{discussion}} Need to pull together existing and implement for new situation
{{Data Integrity Check List}}
* when is it mandatory (not died and not AMA and certain destinations...)
 
== Implementation ==
no comments


== Legacy ==
== 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.  
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
== Related Articles ==
{{Related Articles}}


[[Category: 2016 Time and Place changes]]
[[Category: 2016 Time and Place changes]]
[[Category: Admit/Discharge]]
[[Category: Admit/Discharge]]
[[Category: Transfer Ready]]
[[Category: Transfer Ready]]
[[Category: Registry Data]]

Latest revision as of 16:44, 2023 October 18

 
 
 
 

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: 1999-06-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.

  • SMW

Legacy implementation right in the table

  • Cargo


  • Categories
  • Forms


See Transfer Ready DtTm tmp entry

The data in this field will be retained in Centralized data.mdb's L_Log table since it doesn't follow the same pattern as the new entry. The field no longer exists in CCMDB data.mdb.


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,

  • 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 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"

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.

Collection Start Dates

  • Critical Care: all units on board June 1, 1999
  • Medicine : all wards on board Jan 1, 2005

Cross Checks

Data Integrity Checks (automatic list)

 AppStatus
Check Function Panelling admit transfer sameCCMDB.accdbretired
Query check dispo lower acuity than locationCCMDB.accdbretired
Link suspect transfer ready before arrive dateCentralized data front end.accdbretired

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

Related Articles

Related articles: