Transfer Delay (Critical Care): Difference between revisions

From CCMDB Wiki
Jump to navigation Jump to search
mNo edit summary
mNo edit summary
Line 12: Line 12:




Before Oct 1, 2020, it is calculated by [[Created_Variables_Common_maker query]] and stored in [[Created_Variables_Common table]] in [[CFE]]. Starting Oct 1, 2020, it will be added but haven't started. {{Discuss | who = Tina | are you planning to add the updated  calculation based on the new process in the created variables ? --[[User:JMojica|JMojica]] 16:55, 2021 June 11 (CDT) }}  
Before Oct 1, 2020, it is calculated by [[Created_Variables_Common_maker query]] and stored in [[Created_Variables_Common table]] in [[CFE]].  
 
== Changes for [[PatientFollow Project]] ==
Starting Oct 1, 2020, it will need to be calculated differently.  
{{DJ|
* Multiple ward/unit stays are now in one profile. What will Transfer Delay mean, will it be from the first time the pt is ready (ie one per profile) or one for each [[Boarding Loc]]? Once we settle the details we should implement this in [[CFE]] so it can be derived without the use of SAS.
}}


== Definition Details ==
== Definition Details ==

Revision as of 17:20, 2021 July 13

Data Element (edit)
Field Name: Transfer Delay
CCMDB Label: not stated
CCMDB tab: not stated
Table: Created_Variables_Common table
Data type: number
Length: single
Program: Med and CC
Created/Raw: Created
Start Date: 1999-01-15
End Date: 2300-01-01
Sort Index: 7

Transfer Delay is the difference between Dispo_DtTm and Transfer_Ready_DtTm in decimal days. Other terms use to call it are Beds Occupied by transferable patients, Wasted Beds, Avoidable Days.

  • SMW

Legacy implementation right in the table

  • Cargo


  • Categories
  • Forms



Before Oct 1, 2020, it is calculated by Created_Variables_Common_maker query and stored in Created_Variables_Common table in CFE.

Changes for PatientFollow Project

Starting Oct 1, 2020, it will need to be calculated differently.

  • Multiple ward/unit stays are now in one profile. What will Transfer Delay mean, will it be from the first time the pt is ready (ie one per profile) or one for each Boarding Loc? Once we settle the details we should implement this in CFE so it can be derived without the use of SAS.
  • SMW


  • Cargo


  • Categories

Definition Details

  • Transfer Delay Over 2 hours for Critical Care (ie subtract 2 hrs from transfer delay)
  • I don't quite understand this. Does it mean that, for whatever report uses this, it only considers the TRDtm+4hrs?
  • SMW


  • Cargo


  • Categories

Use

  • The purpose is to determine the amount of time the patient is occupying a bed in an ICU or an IICU or a High Observation ward or a regular ward setting when the patient is no longer needing that level of care (also refer as wasted bed) from the Transfer Ready DtTm until the Dispo DtTm.

Which Transfer Ready DtTm To Use?

Before Oct 1, 2020

Starting Oct 1, 2020

  • For each record and each boarding location in ICU and Medicine, the transfer date and time is taken from the Transfer Ready DtTm tmp entry.
  • For each record, it is possible to have one or more entries of Transfer Ready DtTm corresponding to one or more boarding locations.
  • if the patient moves to various locations, the first Transfer Ready DtTm from a Boarding Loc the same level of care will be used
    • For example, a Med patient stays in high obs bed and then move to regular ward bed and then another regular ward bed. There are two levels of care - one for high obs and another which is lower, for the regular ward. At least two Transfer Ready DtTm intent are expected here - first intent for high obs ready to go to a regular ward and the second intent is from a regular ward to be discharged to another lower level of care or home or PCH. Assuming that there are transfer orders both at regular ward 1 and regular ward 2 and both are with same level of care, the first Transfer Ready DtTm time will be used in calculating the wasted bed for that lower level of care. There will be another wasted bed to be calculated for the high Obs level of care from the Transfer Ready DtTm to the time the patient left the high obs bed (ie the Dispo DtTm or the next Boarding Loc start DtTm. The sum of the two scenarios will be the total wasted bed for that patient.
    • if the Med patient stays in more than one regular wards (or boarding location) or a CC patient stays in more than one ICU location (or boarding ICU location), all locations are considered with the same level of care, the wasted bed is calculated from the first Transfer Ready DtTm until Dispo DtTm.

IICU and H6 Reporting

For the ICU annual and quarter reports, the transfer ready delay to the IICU and to HSC H6 (LTV) will be reported separately from the transfer delay to the other Wards and home. This imply that in addition to the total transfer delay, there will be two more derived delay variables, namely:

  1. to HSC IICU/H6, and
  2. to other wards/Home (including nursing home/long term care facility)

The Dispo location will be used to define the destination. As per Dr. Garland & Dr.Paunovic.

Calculation when transfer time missing

The following definitions are used by Julie in reporting from SAS, and by centralized_data_front_end.accdb to calculate the created_variables query.

  • if discharge time < 1000 HR then dummy=0001 HR (12:01 am),
  • else if discharge time >= 1000 HR dummy=1000HR (10:00 am)

This was based on Critical Care Vital Sign Monitor.

This is as per approval by Dr. Dan Roberts.


Data use

Data Integrity Checks (automatic list)

 AppStatus
Query check long transfer delayCCMDB.accdbneeds review

related fields

Related Articles

Related articles: