ER Delay

Data Element (edit)
Field Name:	ER Delay
CCMDB Label:	not stated
CCMDB tab:	not stated
Table:	Created_Variables_Common table
Data type:	date
Length:	n/a
Program:	Med and CC
Created/Raw:	Created
Start Date:	1988-07-11
End Date:	2300-01-01
Sort Index:	8

The ER Delay is the difference between the pre-ER Boarding Loc and first post-ER Boarding Loc, for patients arriving from the ER.

• SMW

Legacy implementation right in the table

• Cargo

• Categories

• Forms

It's is calculated by Created_Variables_Common_maker query and stored in Created_Variables_Common table in CFE.

Data use

• Measure the time spent using ER bed/facilities/staff while already accepted under a Medicine or Critical Care Service.
• Measure the delay of movement of patient from ER bed to Medicine or Critical Care bed.

ER Delay when there are Visits to temporary locations between initial ER and first unit

for all

Make sure to update Visits to temporary locationswhen this is resolved, if needed.

added: no added date action: no action date

• Cargo

• Categories

Lisa replied ‘when boarding loc is only ER the arrivedttm equals accept dttm equals first service dttm, dispo time should be the discharge dttm'. I have thought the same – that this is how we were doing it with EMIPs. Can’t find this rule in WIKI. Before we move to tmp service and boarding loc. I calculated ER delay equals Arrive dttm – accept dttm. Now we added another or second way, ER Delay equals first post-ER Boarding Loc dttm - ER Boarding Loc dttm. This caused an issue for boarding loc only ER. There is no post-ER boarding loc. if I follow the first way, ER delay is ZERO since arrive dttm is the same as accept dttm. Should the whole stay at ER be considered as an ER delay or NOT? If yes, then in the past I was underestimating it because all EMIPs have ZERO delay. If YES in the question above, then we should add this rule for EMIP or ECIP cases Arrive dttm equals dispo dttm first post-ER Boarding Loc dttm equals dispo dttm in this way, ER Delay will be consistent in both formulas. For discussion. --JMojica 10:17, 2022 March 9 (CST) Discussed at Task Team Meeting - Rolling Agenda and Minutes 2022#ICU Database Task Group Meeting – March 9, 2022 - Julie and Lisa will bring more data to next task meeting Apr 6. Ttenbergen 22:27, 2022 March 9 (CST) now that we have retired accept/arrive concepts can we delete this? or do we need to update first service/second boarding loc? Lisa Kaita 08:01, 2022 April 28 (CDT) I think the question of how Julie will interpret and report the scenario she describes is still open, even when defined with Boarding Loc and Service tmp entry rather than Accept/Arrive. I think Julie was going to bring data today to hopefully decide and be done with this. Ttenbergen 10:42, 2022 May 4 (CDT) It sounded at task today as if this no longer needs to be discussed, we just need to make sure that this page explains how we now use it in this scenario. Then the question can come out. So, I have moved it to Questions for Julie. Ttenbergen 12:32, 2022 May 4 (CDT)

• SMW

• Cargo

• Categories

Data Integrity Checks (automatic list)

	App	Status
Query s tmp Boarding Loc ER delay reasonable	CCMDB.accdb	implemented

related fields

• Boarding Loc DtTms
• LOS
• Transfer Delay

Reporting and Analysis

The SAS Program to read the data is in X:\Julie\SAS_CFE\CFE_macros\datetimes.sas

Legacy

• Used to be just the difference between the Accept DtTm and Arrive_DtTm for patients arriving from the ER.
• Used to be collected as ER Wait and before that as Moves for Medicine.