ER Wait

We track the time medicine patients spend in the ER before being admitted to a medicine ward bed.

Purposes of collecting "ER Wait" data:

To assess the "time delay" from when a patient is first accepted to Medicine Service while in the site's own ER (emergency room) to when the patient actually arrives in a medicine ward bed of the same hospital. (This is done in conjunction with admit time).

Start and stop date

• Start Date: June 4, 2011 (NOTE: September 1, 2007 ER Wait was included with Moves for Medicine).
• Stop Date: none

Collection Guideline

For every patient admitted from the ER, enter date and time arrived to medicine ward bed

• Any patient admitted from the ER must have one ER Wait date/time entered into tmp file. It does not matter if first bed moved to into an in-service or off-service bed.

• project: ER_Wait
• as appropriate one of the following items
  • ER admission - is a patient who is admitted TO a medicine service physician FROM a ER physician service.
  • direct admit - A direct admission means direct admission TO medicine physician service but for some reason parked in ER before going to a ward bed. These patients are NOT admitted under a ER physician service prior to being accepted to medicine service.

• the date & time arrived in med ward bed from the unit log or nurses note.

TMP file entry

• PROJECT: ER_Wait
• ITEM: ER Admit or direct admit
• E: Date (arrived on ward bed)
• M: time (arrived to ward bed)

Sending to TmpV2.1mdb

ER Wait data is sent to Regional Server only when all of the patients data file is complete and also being sent in.

Reporting and Analysis

Julie? Template:Discussion

• because there was a change made to ITEM in temp for ER Wait, which was not the plan, Julie must reprogram her SAS to pull data from TmpV2.1mdb two different ways to calculate delay to ward bed from the ER. --TOstryzniuk 14:08, 16 June 2011 (CDT)

Integrity Check

Template:Potential Change To be implemented as per email exchange ~2011-05-25 between Julie Trish and Tina, and to be documented here. Ttenbergen 15:59, 2 June 2011 (CDT)

• "calculate the ER LOS for those coming from ER and show it up in the screen so the data collector will know the delays in ER and if it is more than 3 days, a message to confirm if correct should appear" because "The suggestion of adding the delays in ER are for 1) data quality (Is 0.001 or 30.279 delays in ER correct?) and 2) data information for data collectors (make them aware about the delays) in case they are not thinking about its implication/significance when they enter the move date." (as per email from Julie 2011-05-24)
  • I'd summarize that as:
    • If difference between date/time in tmp entry ("ER admission" or "direct admit" or both?) and admit dttm > 3 days then give warning to data collector but accept entry (since this could be true).
    • Check would run at either send time or at the time the tmp_checker button is pressed.
  • Is that correct? If so, Trish please feel free to prioritize under Change Priorities Ttenbergen 17:33, 2012 October 1 (CDT)

• do we want other checks, knowing what we know of this data another 1.5 years later? Ttenbergen 17:33, 2012 October 1 (CDT)Template:Potential Change

Data Structure

We capture ER Wait (moves) in L_TmpV2. The data is sent to and stored in TmpV2_1.mdb.