Transfer Ready DtTm field: Difference between revisions

From CCMDB Wiki
Jump to navigation Jump to search
mNo edit summary
mNo edit summary
Line 16: Line 16:
| todo_action = 2022-03-10
| todo_action = 2022-03-10
}}
}}
{{Todo
| who = Tina
| todo_added = 2022-04-26
| todo_action = 2022-04-26
| question =  _dev_ccmdb
* remove field from sending
}}


{{Data_element
{{Data_element

Revision as of 13:54, 2022 May 3

See Transfer Ready DtTm tmp entry

Once the following query comes up empty this field should be removed from view in CCMDB.accdb

SELECT L_Log.D_ID, L_Log.RecordStatus, L_Log.Accept_DtTm, L_Log.Arrive_DtTm, Nz([Accept_DtTm],Nz([arrive_dttm],#1/1/1900#))<=#10/15/2020# AS filter
FROM L_Log
WHERE (((L_Log.RecordStatus)="incomplete") AND ((Nz([Accept_DtTm],Nz([arrive_dttm],#1/1/1900#))<=#10/15/2020#)=True)); 
  • 2022-04-19 pt is on Brynn's laptop; Lisa agreed that Brynn would look into thinned chart to see if we can clear this up
  • 2022-04-14 checked again, still there; H7_HSC_IICU-3097 was discharged over a year ago, emailed Lisa
  • 2022-02-10 checked, one record left and it has dispo dttm H7_HSC_IICU-3097; something seems odd about that one, so look into if still present in a month
  • added: 2021-04-14
  • action: 2022-03-10
  • Cargo


  • Categories

_dev_ccmdb

  • remove field from sending
  • added: 2022-04-26
  • action: 2022-04-26
  • Cargo


  • Categories


 
 
 
 

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.

  • SMW

Legacy implementation right in the table

  • Cargo


  • Categories
  • Forms


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.

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: