ER Wait: Difference between revisions

From CCMDB Wiki
Jump to navigation Jump to search
Line 15: Line 15:
* '''ER_Wait''' project   
* '''ER_Wait''' project   
* as appropriate one of the following items
* as appropriate one of the following items
** direct admit
** direct admit - direct admit patient parked in ER on the way
** ER Admit
** ER Admit - any other ER admission
* the date & time from the unit log or nurses note.  
* the date & time from the unit log or nurses note.  



Revision as of 16:32, 2 June 2011

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

Purposes of collecting "Move" 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).

  • NOTE: We will NO longer be tracking the second purpose of moves and that is; how much time an in-service medicine patient spends on off service wards while still under a medicine service physician's care.

Start and stop date

  • Start Date: probably 6 jun 2011
  • Stop Date: none

Collection Guideline

For every patient admitted from the ER, enter Template:Discussion (which, when they arrive on the ward or when they arrive in ER?)

    • enter into TMP the date and time when they arrive to a medicine ward bed.--TOstryzniuk 17:09, 2 June 2011 (CDT)
  • ER_Wait project
  • as appropriate one of the following items
    • direct admit - direct admit patient parked in ER on the way
    • ER Admit - any other ER admission
  • the date & time from the unit log or nurses note.

Data is only sent when all of patient file is complete.

Reporting and Analysis

Julie? Template:Discussion

Integrity Check

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)

Data Structure

We capture medicine ward patient movements (moves) in L_TmpV2. The data is sent to and stored in TmpV2_1.mdb.