Hospital Patient Flow Bottlenecks: How Real-Time Locating Cuts Bed Turnover and ED Boarding Delays

By the MGM Solutions team — life-safety RTLS specialists since 2002.

Ask a hospital where its patient flow bottleneck is and you will get a confident answer. Ask for the
timestamped data behind it and the confidence usually drops. Most flow conversations run on recollection
and on timestamps that were entered by a person, minutes or hours after the event, while that person was
doing three other things.

That is the real problem. Hospital bed turnover time is a measurement problem before it is a
staffing problem, and you cannot fix a queue you cannot see. Real-time locating replaces
remembered timestamps with observed ones, which is far less glamorous than the dashboards suggest and
far more useful.

This article covers where the delay actually accumulates, what RTLS measures automatically, what it
does not fix, and how to run a flow project that survives contact with a live unit.

Where the Time Actually Goes

The interval that gets blamed is “housekeeping is slow.” The interval that usually matters is
everything on either side of housekeeping. Break a single bed turnover into its component gaps:

• Discharge order to patient physically leaving. Transport requested, transport
  arrives, wheelchair located, family retrieved from the cafeteria.
• Patient out to room marked dirty. A notification step that depends entirely on
  someone remembering to make it.
• Dirty to EVS staff in the room. Queue position, travel distance, competing
  priorities, and whether the request ever reached the right person.
• Clean complete to room marked available. Another manual notification, another
  place where minutes disappear.
• Available to next patient assigned and moved. Bed board latency plus transport
  again.

In most facilities the actual cleaning is the shortest and most predictable segment. The waiting and
the notification gaps around it are where the hours live, and they are precisely the segments that no
one is timing. Meanwhile the emergency department boards patients for a bed that has been physically
ready for forty minutes without anyone downstream knowing.

What RTLS Measures Without Anyone Doing Anything

A location system with room-level certainty produces the flow timestamps as a by-product of people
and equipment simply moving. Nobody logs anything.

Two things follow from this. First, the measurement is honest — it is not filtered through the
memory or the incentives of the person entering it. Second, it is granular: instead of “average
turnover is 118 minutes,” you get five separate distributions and can see which one has the long tail.
That is usually enough to reallocate effort without hiring anyone.

We build this on the same infrastructure as our life-safety applications. The same tag and the same
in-room receivers that support
wander and elopement
management and clinical rounding
generate the flow data, which is why flow analytics is usually an incremental cost rather than a
separate project. Our
patient flow optimization overview
covers the deployment side in more detail.

Why Zone-Level Location Is Not Enough Here

Flow measurement only works if the system knows which room, not which wing. A system that
places a transporter “somewhere on 4 West” cannot tell you when they entered room 412, which means it
cannot time the segment you are trying to fix.

This is the same certainty-versus-inference distinction that governs life-safety accuracy. SecurTRAK
uses infrared for room-level confirmation — IR does not pass through walls, so a read means
presence in that room, not a probability — with 433 MHz active RFID carrying the data
building-wide and low frequency handling doorway and elevator triggers. Systems that infer position
from signal strength produce flow reports that look precise and are not, and clinical leaders stop
trusting them within a quarter. See
why Wi-Fi, BLE, and 900 MHz fall
short for the underlying physics.

What RTLS Will Not Fix

We would rather say this plainly than have you discover it after purchase.

• It will not create capacity. If you are short of beds or short of EVS staff at
  2 p.m. every day, better data tells you precisely how short. That is genuinely useful for staffing
  cases, but it is not the same as relief.
• It will not fix a broken bed-board process. If the status change still has to be
  keyed into a system nobody has open, automatic timestamps just document the delay.
• It will not survive being used punitively. The fastest way to kill a flow program
  is to use individual location data in performance reviews. Staff will leave badges in lockers, and your
  dataset dies. Set the policy up front, in writing, with your nursing and labor stakeholders, and report
  at the unit and process level.
• It will not replace clinical judgment about discharge readiness. Flow data shows
  where the queue is; it does not decide who is ready to leave.

A Realistic Sequence for a Flow Project

1. Pick one unit and two metrics. Typically discharge-order-to-bed-available and
   EVS-request-to-EVS-in-room. Resist the enterprise dashboard for now.
2. Baseline for four weeks before changing anything. Without a clean baseline you
   will not be able to defend the improvement later, and you will not know which change caused it.
3. Publish the segment breakdown to the people who work the unit. Charge nurses and
   EVS leads usually identify the fix themselves once they can see which segment is long.
4. Automate the one notification that costs the most. Almost always “room is clean and
   available.” Wiring that to the bed board is frequently the single highest-return change in the project.
5. Then expand. Second unit, then the ED-to-inpatient handoff, then transport
   dispatch.

Facilities that follow this sequence tend to report their gains in the notification and queue
segments rather than in cleaning speed — which is the point. You are removing waiting, not
pushing people to work faster.

Flow Is a Second-Order Benefit of a Life-Safety Platform

We are candid about where our center of gravity is. MGM built its reputation on campus-wide
life safety: elopement prevention, wireless staff duress, and infant security, indoors and
outdoors, on a single infrastructure, in VA medical centers and hospitals since 2002 with 99.8%
uptime. Patient flow is a genuine benefit of that same infrastructure, and for many of our customers it
is what makes the financial case close — but it is not the reason we would tell you to buy a
life-safety system.

If flow is your primary goal and safety is secondary, say so during the evaluation. It changes where
the receivers go and how the analytics are configured, and it is a much better conversation to have
before the design is finished. For the cost side, see
how to build a
business case for hospital RTLS.

Frequently Asked Questions

Related reading:
RTLS Nurse Call
Integration  • 
Hospital Equipment
Hoarding  • 
RTLS for Hospital CIOs