Project Borrow arrive

From CCMDB Wiki
Jump to navigation Jump to search
Projects
Active?: not yet active"not yet active" is not in the list (active, planned, legacy, aborted in planning) of allowed values for the "ProjectActive" property.
Program: CC
Requestor: Critical Care program (Allan Garland)
Collection start:
Collection end:

This project will track when and where the patient first borrows a bed.

Data Collection Instructions

Under which circumstances to enter this

  • For medicine: put a tmp entry for the first time a patient enters a borrowed location during their stay at your Service/Location; this may be at the beginning of their stay
  • For critical care: put a tmp entry for every move/borrow a patient makes during their stay at your Service/Location; including moves from borrowed location to your actual unit.
    • implementation comment: for any ward/unit names we need to use the "location_name" column content

How to enter this

  • Use tmp fields:
    • Project: Borrow arrive
    • Item: no borrow (default) or the ward/unit where the bed was borrowed
    • start_dt: arrival date at borrowed bed
    • start_tm: arrival time at borrowed bed
    • checkbox: to be checked only in case of "no borrow"

Special Case - admission is already to off-ward location

If pt is admitted to your service but even the original location is off-ward, code borrow arrive with borrow data and time = Arrive DtTm

Special Case - PACU

If a bed is borrowed in PACU / post-anesthesia care / recovery unit, code this as a borrow. (i.e. <hosp> - recovery, e.g. "HSC - recovery").

Special Case - EMIP

One could consider an EMIP a special case of this, but we will 'not code them in this project and instead follow the usual EMIP instructions.

Start/End Dates

  • Start: not yet determined
  • End: there is no planned end date

Examples

Template:Discussion still to come.

Template:CCMDB Data Integrity Checks

(start_dt, start_tm) outside of admission time

If

or

then give a hard error. This can't be.

Implemented as query ___not___yet___implemented___.

can't have two entries that are the same

Can't have two identical entries.

Implemented as query ___not___yet___implemented___.

can't borrow on own unit

This is allowed because this is how we would code a patient moving back to home unit. No check! Just leaving it here in case.

Data Use

Critical care program wants to know this to better understand patient flow and bed utilization.

SAS Program

The SAS program calculates the time spent in a borrowed bed at each ICU stay and summarize the total bed-days in a given interval that are taken up by boarders from elsewhere and how much a certain unit is boarding elsewhere.

Time spent in borrowed bed = Next Arrival Date_time - First Arrival Date_time
where Next Arrival Date_time = Dispo Date_time if there is no more next arrival date_time.

The SAS program is saved in X:\Julie\SAS_CFE\CFE_macros\Bed_Borrow.sas

Background

Will replace Off ward field to provide more meaningful data.

We used to collect Moves for Medicine but this was too much work because there are too many adminstrative moves. Also, the data wasn't being used. Now critical care has asked for this data. To keep collection instructions as consistent as possible between CC and Med, we decided to use the same structure for both, but only track the first instance for medicine, but all instances for CC.

Related articles

Related articles: