Most hospital networks were not designed for the level of demand modern healthcare environments now require. Over the last decade, hospitals have layered connected medical devices, digital workflows, mobile applications, virtual care platforms, and RTLS deployments onto infrastructure that was originally built primarily for connectivity. The result is a wireless environment under growing strain — and a widening gap between what the network was designed to do and what clinical and operational teams now expect.
The scale of that strain is significant. The average hospital now houses between 10 and 15 connected medical devices per bed, totaling upwards of 350,000 IoMT devices in a single facility. Any disruption or added latency in that environment can delay clinical decisions, interrupt workflows, impact staff communication, and introduce operational risk. Even short outages are no longer just IT problems — they are patient care problems.
For hospitals evaluating a wireless refresh, the key question has shifted. It is no longer simply: “Do we need better Wi-Fi?” The more important question is: “Will our refreshed infrastructure support real-time operational visibility, scalable RTLS performance, and the clinical and operational workflows we are building toward over the next three to seven years?” The answer to that question shapes every infrastructure decision that follows.
A Wireless Refresh Is No Longer Just an IT Decision
Historically, wireless refresh cycles were driven by familiar IT priorities: closing coverage gaps, replacing aging access points, expanding bandwidth capacity, and resolving device compatibility issues. Those considerations remain valid, but the scope of the decision has expanded considerably.
Modern hospital wireless infrastructure is now expected to support not just connectivity but operational workflows that depend on continuous, accurate location data — asset tracking across clinical environments, staff safety and duress monitoring, patient flow visibility, and workflow automation that triggers on location events. These use cases place different demands on a wireless environment than clinical mobility or device connectivity alone. A hospital may have adequate bandwidth for laptops and mobile clinical devices while still lacking the infrastructure density and architectural design required for reliable RTLS performance.
Designing a refresh without accounting for these operational requirements often results in infrastructure that becomes insufficient well before the hardware lifecycle ends or the deployment of separate, shadow IOT and RTLS networks. The organizations that approach a wireless refresh strategically — defining operational goals first and infrastructure requirements second — are the ones that build environments capable of supporting both current workflows and future expansion.
Start With Operational Goals, Not Hardware Specifications
One of the most common mistakes in a wireless refresh is beginning with a hardware selection rather than a use case definition. Infrastructure requirements — particularly around device density and placement strategy — are directly shaped by what the network will be asked to support.
Before evaluating access points, gateways, or BLE infrastructure options, hospitals should work through a defined set of operational questions:
- Which RTLS use cases will we support — asset tracking, staff safety, patient flow, or a combination?
- Do we need zone-level, room-level, or sub-room location accuracy for each use case?
- How many connected devices will our environment need to support over the next three to seven years?
- Are we standardized on a wireless infrastructure provider, and how does RTLS fit within that environment?
- What integration requirements exist between our wireless infrastructure and downstream clinical or operational systems?
These answers have direct implications for infrastructure density, technology selection, and deployment architecture. A refresh designed around connectivity alone will likely require costly augmentation when RTLS objectives are defined later — often within the same hardware cycle.
Infrastructure Decisions Made Today Will Shape RTLS Performance Tomorrow
Talk with AiRISTA about evaluating your current environment, RTLS readiness, and infrastructure strategy before deployment decisions are finalized.
Schedule a consultation: salesinfo@airista.com | 1-844-816-7127
Wi-Fi: The Foundation
Despite the advancement of cellular technologies, Wi-Fi remains the backbone of the modern hospital wireless environment. For most hospitals, leveraging existing wireless investments for RTLS is both operationally practical and financially rational. Wi-Fi environments designed a few years ago for “voice grade” support clinical mobility, connected medical devices, voice and collaboration tools, mobile workflows, and typically basic zone-level location services. For Wi-Fi environments designed to be “RTLS grade”, accuracy improves beyond zone-level. With a calibrated location model, customers can reliably achieve room-level accuracy which is desired for use cases such as asset tracking and staff duress. The decision between a Wi-Fi based architecture for RTLS and other technologies is not a question of one being superior to the other — it is a question of use case requirements, existing/planned access point selection, and tag selection.
Evolving Role of BLE and UWB
Most modern access points now incorporate BLE radios, and AiRISTA provided BLE gateway infrastructure — compact, PoE-powered, and deployable at relatively low cost — can augment the BLE radios in access points from manufacturers, such as those from Cisco Meraki, HPE Networking, Arista Networks, and Extreme Networks, without requiring organizations to rebuild their wireless network architecture. For hospitals undergoing a wireless refresh, the most effective approach is typically a hybrid model: Wi-Fi supports enterprise connectivity and clinical mobility, while a purpose-designed BLE layer supports scalable RTLS workflows including asset tracking, staff safety, and patient flow. The reasons are straightforward: BLE balances infrastructure cost, tag battery efficiency, tag costs, and deployment flexibility to offer customizable location accuracy. Some access point manufacturers are also now incorporating UWB radios into their access points which can provide reliable sub-meter accuracy, but this requires careful planning to avoid misplacement, an issue that plagued early RTLS grade deployments, and comes with a limited amount of tags to select from.
AiRISTA’s Sofia™ platform is built to operate with varying technologies. Sofia™ ingests location data from both Wi-Fi infrastructure — including Cisco Spaces and HPE Aruba Networking integrations — and additional BLE gateways, normalizing that data into a unified location system of record that drives operational workflows and system integrations. This flexibility means hospitals are not locked into a single infrastructure path and can expand location capabilities as use cases evolve. Learn more about Sofia™ platform infrastructure support.
Infrastructure Density: The Most Overlooked Factor in RTLS Planning
Of all the considerations in a wireless refresh, infrastructure density is the one most consistently underestimated — and the one that most directly determines whether an RTLS deployment performs as expected.
The error happens predictably: access points are placed at or near previous locations, newer hardware is assumed to compensate through improved performance, and the design is signed off on coverage maps that show strong signal across the facility. The problem is that coverage and location accuracy are not the same thing, and coverage maps do not reveal location performance gaps.
RTLS location accuracy depends on a tag being visible to three or more access points or gateways simultaneously. A wireless environment that provides strong connectivity coverage may still produce inconsistent or unreliable location data if the infrastructure density required for trilateration is not present in clinical areas.
This distinction becomes critical during any hardware refresh. As hospitals upgrade access points — even within the same frequency bands — signal propagation characteristics, transmit power configurations, and channel assignments change. A new coverage analysis is not optional when RTLS performance is a requirement. If existing access point placement logic carries forward to refreshed hardware is one of the most common causes of location accuracy gaps discovered after deployment, at which point adding infrastructure is significantly more disruptive and expensive than planning for it correctly the first time.
The correct approach is to conduct a fresh site survey that evaluates both connectivity coverage and RTLS location performance requirements for each planned use case. The density requirements for reliable asset tracking is different than that needed to drive workflows for room entry/exits. Designing density to the most demanding use case or planning around future augmentation ensures the infrastructure serves all of them.
Hospitals that skip this step and assume existing placement logic applies to a new hardware generation frequently discover the gap only after deployment — at which point adding infrastructure is significantly more disruptive and expensive than planning for it correctly the first time.
How AiRISTA Supports the Wireless Refresh Decision
A wireless refresh is not a hardware procurement exercise. It is an infrastructure strategy decision — one that will shape what a hospital’s clinical and operational environment is capable of supporting for the next three to seven years. Getting it right requires understanding both the wireless infrastructure layer and the operational workflows that depend on it.
AiRISTA works with healthcare organizations at the assessment stage of a wireless refresh, before infrastructure commitments are made. That engagement typically covers:
- Evaluation of existing wireless environments and current RTLS readiness
- Use case definition — which operational workflows require location data, and at what accuracy level
- BLE infrastructure planning and density analysis aligned to specific use cases
- Review of existing infrastructure provider relationships (Cisco, HPE Aruba, Arista Networks, Extreme Networks) and how Sofia™ integrates within those environments
- Long-term scalability planning — ensuring the refresh supports both current deployment scope and future expansion
Rather than applying a standardized deployment model, AiRISTA’s approach is to identify the architecture best aligned to how the hospital actually operates — its existing investments, its clinical workflows, and its operational roadmap. The right wireless refresh strategy is not necessarily the most comprehensive or most expensive one. It is the one designed around the specific environment it will serve.
AiRISTA’s Sofia™ platform supports multiple infrastructure approaches within a single operational environment, allowing hospitals to leverage existing investments and integrate operational and clinical systems without complete redesigns as use cases evolve.
Building Infrastructure That Serves Operations — Not Just Connectivity
The hospitals that benefit most from a wireless refresh are not simply the ones that end up with faster networks. They are the ones that used the refresh as an opportunity to build an infrastructure foundation intentionally designed for the operational workflows that depend on it: real-time asset visibility, staff safety monitoring, patient flow coordination, and the scalable RTLS capabilities that support each of these across a growing clinical environment.
That outcome requires a different starting point than a traditional IT refresh. It requires defining operational objectives before selecting hardware, understanding the distinction between connectivity coverage and location performance, designing infrastructure density to the demands of location-dependent use cases, and selecting platform partners whose software is built to work within the infrastructure environments hospitals already have.
A wireless refresh is a significant investment. Done strategically, it creates a foundation the hospital will build on for years. Done reactively, it solves today’s connectivity problems while leaving the operational infrastructure questions unanswered — until the next refresh cycle makes them unavoidable.
Sources
Asimily, The State of Hospitals’ Cyber Asset Exposure Management in 2025 (IoMT devices per bed statistic); GlobalData / Clinical Trials Arena, The Hidden Bottleneck in Digital Healthcare: Why Hospital Wireless Networks Are Under Pressure in 2026 (April 2026); Ericsson / Medical Device Network, Is Hospital Connectivity Keeping Up With the Demands of Modern Care in 2026?; Juniper Research, IoMT Devices in Smart Hospitals Forecast; Cisco Systems, Healthcare Wireless Infrastructure Documentation; HPE Aruba Networking, Healthcare Solutions; Bluetooth SIG, Bluetooth Low Energy Overview.
About The Author
