RTLS Integration with Access Control, Elevators, and CCTV: Closing the Elopement Loop

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

Most wander-management systems do one thing: they tell you something happened. A tagged patient
approaches a monitored exit, a horn sounds, a message goes out, and from that moment forward the outcome
depends entirely on whether a human being is close enough, free enough, and fast enough to intercept.

That is a notification system. A life-safety system closes the loop — the
location event does not just announce itself, it acts: the door holds, the elevator will not take the
person to the lobby, and the camera covering that door is already on the responder’s screen with the
right timestamp.

This article is about what those integrations actually do, what they require, and the questions that
separate a real integration from a line item on a brochure.

Why the Alert Alone Is Not Enough

Run the timeline of a typical exit event. The patient reaches the door. The system detects the tag
and alarms. A staff member sees or hears it, decides it is real, works out which door, and starts
moving. Even in a well-run unit that decision-and-travel time is measured in tens of seconds —
and it competes with everything else happening on the floor at that moment.

Now add integration. The same detection event holds the maglock so the door does not open, denies the
elevator call, and pulls the relevant camera to the security workstation. The clock stops immediately
rather than at the end of a human response chain. The staff response still happens — it just no
longer has to be the only thing standing between the patient and the parking lot.

This is the practical difference between the door being a boundary and the door being an alarm.

The Four Integrations That Matter Most

1. Access Control and Door Hardware

The core integration. When a tagged patient enters the low-frequency field at a monitored doorway,
the RTLS sends a signal to the access control system or directly to the door hardware to hold the lock,
release a delayed egress, or annunciate locally. Done properly, it is patient-specific: the door holds
for the tagged individual and behaves normally for everyone else, which is what makes it usable on a
door staff and visitors pass through all day.

The hard requirements here are life-safety code compliance and fail-safe behavior. Delayed egress and
electrified locking on paths of egress are governed by NFPA 101 and your local authority having
jurisdiction, and every locking interface has to release on fire alarm and on loss of power. This is
non-negotiable and must be designed with your AHJ and fire-alarm vendor at the table, not resolved
during commissioning. Any integrator who is casual about this should not be wiring your doors.

2. Elevator Control

Elevators are the most commonly missed vector in wander management. A unit can have every stair and
exterior door covered and still lose a patient who simply steps into an elevator and rides down. Because
the car is a moving metal box, systems that infer location from radio signal strength frequently lose
the tag entirely for the duration of the ride and reacquire it somewhere unexpected.

The integration is straightforward when the location data is trustworthy: a low-frequency field at the
elevator lobby detects the tagged patient, and the RTLS signals the elevator controller to refuse the
car call, restrict floor selection, or return the car to a designated floor with a hold. It is one of
the highest-value integrations per dollar in a multi-story building, and it is why we treat elevator
lobbies as chokepoints in the same class as exterior doors.

3. Video Surveillance (CCTV / VMS)

Video integration does two jobs. Live, it puts the correct camera in front of the responder without
anyone hunting through a matrix — the location event carries the door identity, so the workstation
can call the associated view automatically. After the fact, it bookmarks the video clip against the
location event, which turns a two-hour scrub through recorded footage into a single click.

That second job is worth more than it first appears. Documented, timestamped evidence of when an alarm
fired and how staff responded is exactly what is needed for incident review, for survey findings, and for
liability defense. We covered that dimension in
how hospitals reduce
liability and lawsuits with RTLS.

4. Nurse Call, Paging, and Mobile Devices

The alert has to reach a person who is already holding a device, not a station nobody is standing at.
Integration with nurse call, middleware, and smartphones routes the event to the assigned caregivers with
the patient name, the door, and the map location. Escalation rules matter as much as delivery: unacked
after thirty seconds escalates to the charge nurse, then to security. See
RTLS nurse call
integration for how this pipeline is built.

Integration Comparison: What Each One Buys You

Integration Only Works If the Location Data Is Trustworthy

Every one of these integrations takes an action on behalf of the location system. That raises the
cost of being wrong. A false room-level read is an annoyance in an asset report; a false door event that
locks a corridor or refuses an elevator is an operational incident, and enough of them will get the
integration switched off.

This is why we insist on certainty rather than inference at the points where actions
are triggered. SecurTRAK uses low-frequency fields to define chokepoints physically — the tag is
in the field or it is not — infrared for room-level confirmation, since IR does not pass through
walls, and 433 MHz active RFID to carry those confirmed events building-wide through walls and floors.
Signal-strength estimation is not used to decide whether to hold a door. The
technology comparison explains why
that distinction is structural rather than a matter of tuning.

The Loop Does Not Close at the Building Line

A fully integrated door still only protects a door. If the patient does get outside — through
a propped door, a loading dock, with a visitor — most systems go dark exactly when the search
begins.

SecurTRAK is the only RTLS platform that delivers every life-safety use case — patient
elopement prevention, wireless staff duress, infant security, and asset tracking — both indoors
and outdoors on a single infrastructure. One tag, one map, one alerting pipeline, from the
patient room to the parking lot. The integrations described above hold the line at the door; campus-wide
coverage is what you have left if the door does not hold. See
campus-wide
elopement prevention for the full argument, and
wireless staff duress for how the same
outdoor coverage protects staff walking to their cars.

Questions to Ask Before You Sign

1. Name the products. Which access control platform, which elevator controller, which
   VMS, which nurse call system, at which versions — and where has this exact combination been
   installed before?
2. Who owns the interface? Integrations cross vendor lines. Get one party accountable
   for the end-to-end behavior in writing, or you will be mediating during an incident.
3. What happens on failure? Network down, server down, power lost at the door. Ask for
   the failure mode of each integration in plain language, and confirm every locking interface releases on
   fire alarm.
4. Has the AHJ reviewed the locking scheme? Egress code is not something to interpret
   after installation.
5. How is it tested? Ask for a written commissioning test per door and per elevator
   bank, and ask how often it is retested. Integrations rot quietly when the VMS or ACS is upgraded.
6. What is logged? You want a durable, exportable record of the event, the action
   taken, and the acknowledgement — for both quality review and
   Joint
   Commission survey readiness.

Frequently Asked Questions

Related reading:
How to Prevent Patient
Elopement in Hospitals  • 
RTLS for Behavioral
Health  • 
Corrections Facility Solutions