WiFi for healthcare facilities

Healthcare WiFi carries some of the most important traffic of any building: clinical devices, staff communication, patient records and location tracking, alongside patients and visitors. It has to be designed for reliability first, with careful segmentation and security, and validated with the devices staff actually use.

What the network has to support

Clinical devices such as infusion pumps, patient monitors, portable imaging and medication carts, many of which have strict, maker-specified network requirements.
Staff communication: WiFi phones, badges and smartphones used for calls, alerts and messaging, often while walking.
Clinical workstations on wheels and tablets used at the bedside.
Location services: real-time tracking of equipment and, in some facilities, staff or patients. See RFID and asset tracking.
Building systems, including some nurse call, access control and environmental monitoring.
Patients and visitors, who expect guest WiFi for long stays and waiting areas.

Design priorities

Reliability and roaming

Staff move constantly while on calls or receiving alerts, so the network must let devices roam without interruption, with secondary coverage throughout clinical areas. Voice-grade design, commonly around −67 dBm with good signal-to-noise ratio, is a typical starting point. See Why −67 dBm is the WiFi design target. Where device makers specify stricter requirements, theirs take priority.

Device requirements

Each type of clinical device may support only certain bands, channels, security methods or WiFi generations. The design must be built around those limits, and changes to the network should be tested against them before rollout. Clinical engineering or biomedical staff should be involved from the start.

Difficult construction

Healthcare buildings contain shielded imaging rooms, lead-lined walls, heavy concrete, elevator banks, and dense mechanical and medical gas services above the ceiling. These affect signal and limit where access points can go. Infection control rules also affect how and when ceiling work can be done in patient areas.

Capacity in busy spaces

Emergency departments, waiting rooms, cafeterias and teaching spaces can be dense, with many staff and visitor devices at once.

Security and privacy

Health information is protected by provincial health privacy laws, and the network must support the facility's obligations. Common practices include:

Separating clinical devices, staff devices, building systems and guests onto different network segments.
Using strong authentication for staff and devices, often through RADIUS integrated with Active Directory.
Keeping guest WiFi fully isolated from clinical and administrative networks. See Guest WiFi done safely.
Securing network equipment physically, especially in public areas.

One radio layer, separate segments. Every group connects through the same access points, but each is placed on its own network segment with policies that control what it can reach. Guest traffic goes to the internet only and has no route to clinical or staff systems.

The facility's privacy and security teams set the policies; the network design has to support them.

Installation in an operating facility

Most healthcare WiFi work happens in buildings that never close. Ceiling work in patient areas may require infection control measures and approval, and work near sensitive equipment or in shielded rooms needs coordination with clinical engineering. Scheduling, containment and clean-up must follow the facility's procedures, and changes to a live network should be staged and tested so clinical devices are not interrupted.

The work does not end at handover. Clinical device fleets change, new wings open, and firmware updates to access points or devices can change how they behave together. A change process that tests updates against critical devices before rollout, periodic validation surveys of clinical areas, and up-to-date as-built records of access point locations and settings all help keep the network dependable. When a device maker updates its network requirements, the design should be checked against them.

Working with clinical engineering

Clinical engineering, or biomedical engineering, usually holds the information the network design depends on. Before design starts, gather:

A list of wireless clinical device models in use or planned, with quantities and the areas where each is used.
Each maker's published network requirements: supported bands and channels, security methods, signal targets and roaming behaviour.
Any devices that cannot use DFS channels, 6 GHz or newer security methods.
Who must approve network changes, and how changes are tested before they reach clinical areas.
The facility's infection control, access and scheduling requirements for work in each area.

A worked example: a new inpatient wing

A facility is opening a new inpatient wing that will use WiFi staff phones, mobile workstations, wireless patient monitors and equipment tracking. The design starts with clinical engineering's device list, which shows the monitors need stricter signal and roaming performance than the phones, and that the tracking system needs several access points heard in every room.

Because the wing is new, the design begins with a predictive model, checked on site once walls are up and before ceilings close, with particular attention to shielded rooms and the elevator core. Access points are placed so patient rooms and corridors both have secondary coverage, and the segment plan keeps monitors, staff devices, building systems and guests apart. Before the wing opens, the validation survey is followed by walk tests with each critical device type along real staff routes, and the results are reviewed with clinical engineering before sign-off.

Validating clinical areas

Survey each band the clinical devices use, separately.
Walk-test calls and alerts on staff phones along corridors, through stairwells and in elevators where coverage is expected.
Check roaming with mobile workstations and monitors moving between rooms.
Record results by area, so later changes can be checked against them.

Test with the real devices. A survey adapter is not an infusion pump or a staff phone. Validation should include the critical clinical and communication devices, along the routes and in the rooms where they are used.

How ehZee can help

We design healthcare WiFi starting with why each group needs the network and which devices depend on it, then survey the facility, design coverage, roaming and segmentation, and validate the result. Our WiFi design and build service works alongside your IT, clinical engineering and facilities teams, whose policies and requirements shape the design.

Common questions

Can clinical devices share a network with staff devices?

They often share the same access points but should be on separate segments, with policies controlling what each can reach. The facility's security team decides the rules.

Why do staff phones drop calls when walking?

Usually because of gaps in secondary coverage, roaming settings, or the phone's own roaming behaviour. A survey along the routes staff walk, with the phones themselves, will show where.

Should each device type have its own network name?

Not necessarily. Every network name adds overhead on every channel, so many facilities keep the number small and place devices on the right segment through authentication and policy instead. Where a device type cannot use the facility's standard security method, a separate network name may be needed for it. The design balances both.

Does WiFi interfere with medical equipment?

Facilities and device makers set rules on wireless use near sensitive equipment. Follow the facility's policy and the device makers' guidance, and involve clinical engineering in the design.