Three location-and-coverage low-voltage systems that share antenna, sensor, and ceiling infrastructure: real-time location services (RTLS) for asset, staff, and patient tracking; the dedicated patient-protection systems for infant abduction and patient/wander elopement; and the distributed antenna systems (DAS) that carry cellular and public-safety radio signal deep into a building whose construction otherwise blocks it. Each is a distinct system with its own owner, code basis, and failure consequence, yet all three are designed, pathway-coordinated, and commissioned together because they compete for the same ceiling, conduit, and head-end real estate.
RTLS, patient/infant security, and DAS are grouped not because they do the same job but because they are infrastructure-coupled. They are RF (radio-frequency) and sensor systems distributed across the entire occupied footprint; they all hang readers, antennas, exciters, or sensors in the ceiling plane; and they all terminate in the same telecom rooms and head-end spaces. A coordinated infrastructure approach prevents the most common and most expensive field problems: antenna and reader locations that collide with sprinkler heads, lighting, and HVAC diffusers; ceiling congestion that defeats reflected-ceiling-plan coordination; and pathway shortages discovered after the ceiling grid is closed.
They also share a defining design reality unique to healthcare: the building shell actively fights them. Lead-lined imaging suites, dense masonry, low-e glazing, metal-framed partitions, and deep floor plates attenuate RF and block line-of-sight — the same conditions that make Wi-Fi planning hard make RTLS coverage, security-tag reception, and cellular/public-safety penetration hard. Coverage modeling, not just code minimums, drives the device count.
Adjacent Articles carry the neighboring scope: nurse call and clinical-communications (UL 1069) is its own Article; access control, CCTV, and electronic-security integration is its own Article; and the Wi-Fi/wireless LAN, network core, and data-center coverage live in the network Article. This Article owns RTLS, the abduction/elopement protection systems, and DAS specifically.
RTLS is the platform that answers "where is it, where is the person, and where has it been" for tagged assets, staff, and patients. In a modern hospital it has grown from an asset-tracking convenience into clinical-workflow infrastructure that many departments depend on.
Different jobs require different location accuracy, and the chosen technology drives the infrastructure. There is no single "RTLS standard" governing accuracy; selection is a design decision matched to use case.
| Technology | Typical accuracy | Best for | Infrastructure footprint |
|---|---|---|---|
| Wi-Fi RTLS | Room-to-zone (several meters) | Asset tracking riding the existing WLAN | Tags only; rides Wi-Fi (coordinate with the network Article) |
| BLE (Bluetooth Low Energy) | Zone to ~1–3 m | Asset + staff, lower-cost dense deployment | Battery or PoE BLE gateways/beacons in ceiling |
| Active RFID (433 MHz / proprietary) | Zone-level | Asset tracking, long battery life | Ceiling readers/exciters + reference tags |
| Infrared (IR) | Room/sub-room certainty | Where which room must be unambiguous (clinical-grade) | IR sensors/exciters per room, often paired with RF |
| Ultra-wideband (UWB) | ~10–30 cm | Bay-level / precise clinical use, OR, asset density | Dense anchor grid, highest infrastructure cost |
| Ultrasound | Room/sub-room | Room-level certainty alternative to IR | Ceiling ultrasound receivers |
Most enterprise deployments are hybrid — for example RF (BLE/Wi-Fi) for coverage and approximate location, combined with IR or ultrasound where room-level certainty matters (such as confirming a patient or pump is in a specific bay rather than an adjacent one). The architecture decision — coverage-grade vs. clinical-grade location — must be made early, because clinical-grade location multiplies device counts and ceiling coordination.