BedHeldEnd DtTm

Projects
Active?:	planned
Program:	CC and Med
Requestor:	???
Collection start:	2023-01-01
Collection end:

Data Collection

Collect for all patients where beds are held due to AMA or procedure at other sites.

Collection Instructions

• Project :BedHeldEnd DtTm
• Items: AMA or Procedure
• Date (field E): Discharge date as per ADT (ie when the bed was released)
• Time (field M): Discharge time as per ADT (ie when the bed was released)
• Not used: Integer, Real, Checkbox, Comment

Sources

Use the discharge dttm as per Cognos2 Ender/ADT.

Background

As discussed at JALT ...

The frequency of people leaving AMA (esp from ward) is not low. And, per Lisa, most of these are without notice. Thus it is not a trivial issue that there is a nontrivial difference between when the patient actually stops being under care vs. when the bed is released for reassignment.

Our [previous instructions were to note in the Dispo DtTm field when the person left AMA, or was noted to be gone and assumed AMA. If a bed is "held" and the patient indeed returns, goes back into that bed without being readmitted (because the bed was held), then this isn't to be considered to be an AMA. This follows the same kind of reasoning as Visits to temporary locations. This meant we had no way to report bed times lost to AMA.

We then realized that this issue is the same for bed times lost to beds held when a patient is sent to another hospital for a procedure, expecting to return (so the bed from the sending site is held) but then does not return.

These 2 situations are easy for the DCs to identify and they always do so anyway, so we decided to track this to allow us to report on this more meaningfully.

Still need to integrate this: So we will distinguish between: (a) Actual time under care, which is from Admit DtTm to the patient's Dispo DtTm -- we'll call this the patient's length of stay which LOS link? SMW Cargo Categories (b) What we'll call "Bed Assigned Time", i.e. from Admit DtTm to the time when the bed is released for reassignment, which we will call "BedHeldEndTime". This latter is generally available from Cognos (ADT), and Tina will create machinery to record BedHeldEndTime as a temp item. As above, this will ONLY be recorded in the situations when a patient leaves AMA but the bed is held for a bit hoping they come back (but they never do so) , or patient goes elsewhere for a procedure expecting them to return so bed is held but they never do come back. There will be 2 items for BedHeldEnd DtTm:AMA and Procedure

• SMW

• Cargo

• Categories

Collection parameters

• End Date: planned as continuous collection without an end date

Data Use

Which Indicators or Reports will use this? Ttenbergen 12:04, 2022 December 8 (CST)

• SMW

• Cargo

• Categories

Consistency Checks

{{{1}}}

added: no added date action: no action date

• Cargo

• Categories

Data Integrity Checks (automatic list)

	App	Status
Query check tmp BedHeld	CCMDB.accdb	implemented