Off ward field

From CCMDB Wiki
Revision as of 15:08, 1 March 2017 by LKolesar (talk | contribs) (How to identify off-ward patients: move info from stb instructions)
Jump to navigation Jump to search
Data Element (edit)
Field Name: off_ward
CCMDB Label: Off Ward
CCMDB tab: Dispo
Table: L_Log
Data type: number
Length: long integer
Program: Med and CC
Created/Raw: Raw
Start Date: 2016-07-01
End Date: 2300-01-01
Sort Index: 39
Data Dependencies(Reports/Indicators/Data Elements): No results

Checked/true if the patient who meets the Definition of a Medicine Service admission or Definition of an ICU admission spent any time in an bed that is not at their actual collection location between Arrive DtTm and Dispo DtTm.

  • SMW

Legacy implementation right in the table

  • Cargo


  • Categories
  • Forms


This includes patients who spent their entire admission off-ward, but not #EMIPs.

Collection Instructions

How to identify off-ward patients

<details needed>

Template:Discussion Current way of checking through transfer list from ER will miss off ward patients who arrived at off-ward locations from elsewhere than emerg. Laura and Tina discussed, did not find solution yet, should be rare, though. 13:41, 2017 March 1 (CST)

see also EPR Reports, Discharge Register, Transfer Register

We collect data on some patients who never arrive on one of our units, e.g. EMIPs, OVERs, ICU pts in PACU. (Template:Discussion any other scenarios?) Template:Discussion

from identifying in boarding locations...

  • Up to now, I have never made a profile on a PACU patient that never arrived in the ICU. It is possible that ICU accepts a pt in PA and then the pt never actually gets to the ICU (gets better or dies), however up to now I have never made a profile for these (very very rare if ever). Is this something you want done? The problem is that I would not know the pt was under ICU while in PACU if they never come to the ICU. There is nothing in our system to alert me to this.
    • However, if a patient who was accepted to ICU while in PACU does come to the ICU, then a profile is done and the accept time will reflect the time the pt was accepted to ICU service. --LKolesar 09:30, 2016 May 17 (CDT)
  • How does HSC SICU do it? Trish Ostryzniuk 16:58, 2016 May 17 (CDT)
  • These patients are found in several ways. The SICU clerk may know about the patient and put them in the SICU log book, or they may be on the white board and be shown as in PACU or there may be a green sheet for them. We now check EPR with a print out on Mondays, that show all admits from the last 7 days and make sure all patients have been caught.

It is possible that one or two a year are missed but we can't know about what has no documentation.--Jpeterson 07:39, 2016 May 18 (CDT)


These patients can be identified in the EPR as follows:

Template:Discussion Laura and Lisa agreed to fill in the details here. Ttenbergen 14:40, 2016 May 16 (CDT)

STB
  • Medicine service patients that spend all or part of their time on an off-service ward.

Process for identifying Overflow Patients

  1. Go to Citrix Apps on Desktop
  2. Click on EPR Reports
  3. Log in with username and password (same as your initial log into your computer)
  4. Click on “Patient List Reports”
  5. Click on “Transfer Register”
  6. Fill in Facility (hospital you are checking)
  7. Put in a time frame that you wish to search. Do not use the current date as you want it to reflect full days, not a partial day.
  8. Fill in unit as "emergency" of the correct facility
  9. Under “unit filters on”, select “from or to”. All other fields remain unchanged.
  10. Click on "View Report" button.
  11. Scroll though the list to look for only internal medicine patients that went to off-service wards. (Do not count patients that go to ICMS).


Note from Vic
  • Overs can only be found in the admission/disharge book in Medical records at the Vic. Copy the information (name and chart number and discharge date) The nurse collecting on CTU S4 collects this information. Check to see if patient is a VMU patient or CTU patient. If VMU give information to nurse who is collecting on 5N/5S ( VMU has separate laptop same with CTU ) Make sure you indicate that the patient is an Over in access ( enter OVZ) and follow your serial log numbers according to last log number. As in EMIPs/Overs when checking the book in Medical records initial the page of discharges last checked.

How to enter patient into CCMDB

Collection Instructions - current ward

If the patient meets the definition at the top, check the "off ward" checkbox located underneath the Service/Location field.

Enter the laptop's regular collection location into the Service/Location field, not the off-ward location.

Collection Instructions - next ward (if applicable)

The Pre-admit Inpatient Institution field and Previous Location field of the next encounter would use the Service/Location field of the previous collection location where available, not the off-ward location.

Collection Instructions - previous ward (if applicable)

The Dispo field of the previous encounter would use the Service/Location field of the next collection location where available, not the off-ward location.

Not intended for off-ward tests

see Bed holds

EMIP

EMIPs are in their collection location, e.g. GRA_EMIP, so they are not off ward. Don't check the field.

Parked in ER

Parked in ER is before Arrive DtTm, so they are not "off ward". Don't check the field.

Data Use

Relevant to occupancy and some patient risks.

See also

Legacy

initial mis-connection

From 2016-07-01 to 2016-08-?? the control for this field had been incorrectly connected to the pharm_complete field. Since medicine doesn't use that field we could reclaim data for medicine from there. CC uses the field so could not reclaim data for them. Data for CC will be reported starting 2016-09-01.

pre-2016 fields for similar content

We used to collect related information in multiple places. Once we are comfortable with the new dispo fields we want to stop collection of the old fields. The fields are:

Old data would be transferred to new fields where the translation is not ambiguous. We can keep a snapshot of Centralized with the data pre-translation in case we ever want to go back to it.