Transfer Delay: Difference between revisions

From CCMDB Wiki
Jump to navigation Jump to search
m m
m m
Line 1: Line 1:
The Transfer Delay is the difference between [[Discharge date and time]] and [[Transfer Ready date and time]] in decimal days.
{{Data_element


Transfer Delay Over 4 hours in days for survivors - this is derived by subtracting 4 hours from Transfer Delay above.
| field_name = Transfer Delay
 
| element_description =  '''Transfer Delay''' is the difference between Dispo_DtTM and Transfer_Ready_DtTm in decimal days.
 
| in_table = created_variables_common table
 
| data_type = number
 
| datafield_length = single
 
| program_collecting = Med and CC
 
| created_raw = created
 
}}
 
It's is calculated by [[query created_variables_common_maker|query ''created_variables_common_maker'']] and stored in [[created_variables_common table |''created_variables_common'' table]] in [[CFE]].
 
'''Transfer Delay Over 4 hours''' in days for survivors - this is derived by subtracting 4 hours from Transfer Delay above.


==Start Date==
==Start Date==
Line 35: Line 53:
                       else if discharge time  >=  1200 HR dummy=1200HR  (12:00 noon)
                       else if discharge time  >=  1200 HR dummy=1200HR  (12:00 noon)
                 This is as per approval by  Dr. Roberts .
                 This is as per approval by  Dr. Roberts .
== related fields ==
* [[Arrive_DtTm]]
* [[Dispo_DtTm]]
* [[LOS]]
* [[Transfer Delay]]





Revision as of 13:27, 2016 September 19

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"created" is not in the list (Raw, Created, not entered) of allowed values for the "FieldCreatedRaw" property.
Start Date: 1988-07-11
End Date: 2300-01-01
Sort Index: 999

Transfer Delay is the difference between Dispo_DtTM and Transfer_Ready_DtTm in decimal days.

  • SMW

Legacy implementation right in the table

  • Cargo


  • Categories
  • Forms


It's is calculated by query created_variables_common_maker and stored in created_variables_common table in CFE.

Transfer Delay Over 4 hours in days for survivors - this is derived by subtracting 4 hours from Transfer Delay above.

Start Date

ICU-January 15, 1999

data use

  • Quarter and Fiscal Year Reports of both Critical Care and Medicine Programs
  • Medicine Overstay Project
  • Critical Care Vital Sign Monitor Project
  • Critical Care Quality Improvement Team

IICU and H6 Reporting

Sept 12.12 - 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

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

The 'discharge to location' will be used to define the destination. As per Dr. Garland & Dr.Paunovic. - Trish Ostryzniuk 14:18, 2012 September 13 (CDT)

IICU Transfer Delay Exception

Waiting time for IICU only starts when IICU attending physician has deemed the patient a candidate. IICU consults (patients) cannot wait to be seen until IICU has a bed available.(as per Dr. Bojan Paunovic)Trish Ostryzniuk 14:53, 2012 September 13 (CDT)

  • I moved this here from Transfer Ready date and time because I remembered that the IICU reporting was documented here. I am not sure this is collectable as instructed. If a patient is transfer ready according to usual definition, and at a later time dr approves him for IICU, then do you really want to lose the original transfer ready date/time? I think the problem is trying to use the transfer ready date to gain some information about IICU when that is really a different concept. If we want this information we should consider collecting it in, e.g. a tmp entry. Ttenbergen 21:49, 2014 February 26 (CST) Template:Discussion
    • there is no more discussion to further investigate this issue. if the transfer ready date/time is defined as when the time that deemed a patient need to move to HSC IICU and not the time when the bed is available at HSC IICU, I think we are capturing the information the Directors' need. JMojica 10:12, 2014 May 20 (CDT)
      • If all we want is the final request for a discharge then this is not a special case; collection instruction already say to collect the request for discharge and to update this if condition deteriorates. If this is true, then there is no special case here and we can get rid of this heading altogether. However it was documented separately, which would only be necessary if there is something different. We would not say "do this for all patient, and do it for purple patients as well", right? So, either there is a difference, in which case I want to clarify what it is, or there is not, in which case I would like to take the extraneous info out of here altogether. If there is a difference it needs to also be reflected in Transfer_Ready_date_and_time#ICU. - Ttenbergen 12:03, 2014 May 22 (CDT)

Calculation when transfer time missing

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

For Critical Care if discharge time  < 1000 HR then dummy=0001 HR (12:01 am) ,
                      else if discharge time  >=  1000 HR dummy=1000HR  (10:00 am)
               This is based on Critical Care Vital Monitor rule.
For Medicine, if discharge time  < 1200 HR then dummy=0001 HR (12:01 am) ,
                      else if discharge time  >=  1200 HR dummy=1200HR  (12:00 noon)
               This is as per approval by  Dr. Roberts .

related fields