Hospital Wi-Fi isn't office Wi-Fi with better paint. Electronic medical records, patient monitoring, voice comms and real-time location tracking all ride on it now, and if it drops, that's not an inconvenience — it's a patient safety issue. We've designed and validated wireless networks in exactly this environment, and there's a pattern to getting it right: know what's running on the network, understand the building you're fighting, and build in enough redundancy that no single failure ever reaches a ward.

Hospital Wi-Fi: The Three Components

Before you design anything, it helps to break the problem into three parts — what's using the network, what's getting in the way, and what happens when something fails.

Clinical workloads: electronic medical records (EMR), patient monitoring, voice communications and real-time location services (RTLS) for tracking equipment and, sometimes, people. Add biomedical devices — infusion pumps, monitors — and you've got a mix that generic enterprise Wi-Fi was never built for.

The RF environment: hospitals are hostile territory for radio signals. Lead-lined radiology and oncology rooms block Wi-Fi almost completely. Fire-rated doors and concrete cores cause sudden signal drops. And 2.4GHz is a mess — microwave ovens in the staff kitchen, ageing DECT (cordless phone) handsets, and biomedical kit all competing for the same airtime.

Resilience: every layer, from the controller down to the power supply, needs a backup that kicks in without anyone noticing.

Pro-Tip: don't trust the floor plan for construction type. We've walked into "modern extension" wings labelled plasterboard on the drawings that turned out to be a full block wall behind a decorative panel — the kind of thing you only catch with an on-site survey, not a desktop prediction.

ASSOCIATED BLOGS:

• Cheapest vs Best Value Wi-Fi Design

Hospital Wi-Fi: A Staged Approach to Deployment

We treat a hospital wireless project as five stages, not one big design exercise.

Stage 1: Define Clinical Use Cases and Coverage Grades

Start with what the network needs to do, not the building. So how do you avoid over- or under-building? Match coverage density to the activity in each space:

Data-grade: administrative areas, offices — laptops on desks, lower density is fine.
Voice-grade: clinical corridors and wards, where staff carry communication badges needing consistent signal while moving.
RTLS-grade: anywhere you're tracking equipment or patients — the highest access point density of the three.

Don't mix grades on the same floor. It creates uneven density, and uneven density is where roaming problems start.

ASSOCIATED BLOGS:

• AP Placement - Location Grade Wi-Fi Tracking

Stage 2: Predictive Design, Then a Real Site Survey

Run a predictive design first, but don't stop there — hospital construction is too unpredictable for a desktop tool alone. A proper site survey catches the lead shielding, the fire doors, the glass consulting rooms next to solid concrete wards, all the things a floor plan won't tell you.

Access point placement matters as much as count. Too few, and you get coverage holes and congestion. Too many, and APs start interfering with each other. Mounting height around 2.4 to 3 metres is the sweet spot — high enough for line of sight, low enough to still talk to a handheld device carried at waist height.

We look for a primary signal of at least -67dBm, with a secondary signal of -70dBm or better in overlap zones — that secondary signal is what actually lets a device roam cleanly instead of clinging to a distant AP.

ASSOCIATED BLOGS:

• Cisco 9124 Antenna Guide

Stage 3: Build In Redundancy

This is where "high-availability" actually gets built, not just claimed.

Controllers: run paired wireless LAN controllers in active-standby. If the active controller fails, the standby takes over and client sessions survive the switch, thanks to Stateful Switchover (SSO). For mission-critical sites, we'll often recommend a third controller as a hot spare, so you're still covered even while one unit's in for repair.

Power: access points draw Power over Ethernet (PoE) from switches, so switch power is AP power. Put switches serving clinical areas on uninterruptible power supplies (UPS) for short outages, and make sure generator backup covers the gap until it kicks in.

Everything else: dual power supplies in switches and controllers, resilient uplinks to distribution, APs spread across more than one switch, and network gear split across at least two comms rooms. Then test it — deliberately fail things before go-live, and confirm coverage holds and clients don't notice.

ASSOCIATED BLOGS:

• Webinar: Infrastructure Backup for the Agentic Age

Stage 4: Secure It Properly

Hospital networks carry protected health information, so this isn't optional. WPA3-Enterprise with 802.1X ties access to individual credentials — clinical staff log in with hospital credentials, and every connection is logged. We deploy this through Cisco ISE or Aruba ClearPass, tied into the hospital's existing identity systems.

Segment traffic by device type: clinical systems reach EMR and medical device networks, guest devices get internet and nothing else. And keep scanning for rogue access points — it only takes one staff member plugging in a personal router to open a hole in an otherwise locked-down network.

ASSOCIATED BLOGS:

• Zero Trust Architecture (ZTA) Deployment
• Enhancing Network Security: Cisco Umbrella

Stage 5: Plan for What's Next

Wireless demand in a hospital only grows — more devices per staff member, more connected monitoring equipment, more building expansion. A few things worth doing now rather than later:

Address space: allocate more IP address room than you think you need — running out later means a disruptive re-architecture.
Wi-Fi 6E and 7: the 6GHz band is cleaner, but the access points that use it draw more power. Check your switches can deliver enough PoE wattage before you commit to a refresh, or budget for injectors.
Modular design: build in blocks that can be replicated for new wings, so the next building project doesn't mean redesigning from scratch.

Realistically, a large hospital deployment — surveys through to validated go-live — runs three to six months. That's not slow; it's the time it takes to do the validation properly, and it's a lot cheaper than fixing problems after clinical staff are relying on the network.

ASSOCIATED BLOGS:

• Cisco SIA Antennas

Hospital Wi-Fi: Summary

Hospital Wi-Fi has to work every time, because EMR access, voice comms, patient monitoring and asset tracking all depend on it. Get there by defining clinical use cases and coverage grades up front, backing predictive design with a real on-site survey, building redundancy into controllers and power (not just claiming it), securing the network properly, and designing with growth in mind. Skip the on-site survey or the redundancy testing, and you're gambling with outcomes that affect patient care.

Need Help With Your Hospital Wi-Fi Design?

We run Network Assessments to give hospitals a clear health check on coverage, redundancy and security — before or after a wireless deployment. If that's useful, get in touch with the IPTel team.