Opened the wrong way — this page has no styling and no images.
Image and stylesheet paths are resolved from the site root (/assets/…), so opening the file directly resolves them to C:\assets\… and nothing loads.
To see it properly: unzip 2_双击进后台改字_仅Windows.zip and double-click 启动后台.bat — the browser then shows the full site with styling, images and the ZH/EN switch.
(This zip is a plain static preview: opened directly it shows one page at a time, without styles, images or the language switch.)
Once uploaded it works normally: live traffic arrives over http, not by double-clicking a file.
This notice only appears when the file is opened locally; online visitors never see it.
ProductsWireless access & coverageSwitching & data centerOptical access & transportOptics & cabling
ServicesManaged NOCImplementation & deliverySpare parts & maintenanceAdvisory & architecture
SolutionsManaged network operations & NOCCampus & wireless coverageCloud-network branchesSecurity & compliance
Case studiesScale · managed operationsSpeed · bulk migrationContinuity · legacy retrofitTechnical notes
About usCompany profileCertificationsOffices & contactTechnical notes
Resources & contactTechnical notesFAQDelivery processPricingPrivacy & termsContact usOffice address
Technical notes / Healthcare wireless

Wi-Fi 7 in healthcare: how seamless roaming is actually built

A dropped connection in an office costs a video call. A dropped connection in a hospital can cost a medication order or a stream of vital signs. This article maps Wi-Fi 7 capabilities onto hospital settings and says which route suits the ward and which belongs to outpatients.

4 sets
Conflicting requirements
5 capabilities
Wi-Fi 7 capabilities
2 routes
Seamless roaming routes
3 phases
Staged upgrade

Why a hospital is the hardest wireless environment

Hospital wireless has to satisfy four sets of requirements that pull against each other — which is why it is harder than an office or a shopping centre:

01 Mobility

Sessions must not drop

Nurses carry PDAs between wards, corridors and lift lobbies, and the ward trolley moves between floors. The session has to hold — no logging in again at every handover.

02 Density

Hundreds of clients in one area

One trolley may carry a PDA, an infusion monitor and a tablet at once; a single ward can have a hundred IoT devices online together — density well beyond an office.

03 Separation

Three networks side by side

Internal (HIS/LIS/PACS), external (public Wi-Fi) and IoT (asset tags, infusion monitoring) must be physically or logically separated, meeting MLPS 2.0 and health commission rules.

04 Reliability

Downtime measured in minutes

Medication orders, nursing records and live monitoring need carrier-grade availability. Wi-Fi 5 and early Wi-Fi 6 traded these four against each other: stronger encryption meant worse roaming, wider coverage meant less capacity.

Five Wi-Fi 7 capabilities, and what they mean in a hospital

Wi-Fi 7 (802.11be) is not simply twice the rate; it is a systematic rework of the protocol. Five of its features matter directly here:

CapabilityWhat it doesWhy it matters here
MLO, multi-linkA client can hold several bands — 2.4G / 5G / 6G — at once, in parallel or with intelligent switchingA nursing handheld makes the next link before dropping the last when it moves between APs, so the session holds; interference on one link is covered automatically
320 MHz channels320 MHz of bandwidth in the 6 GHz band (policy in mainland China is still pending; 5 GHz still offers headroom through channel combinations)Markedly lower latency for bulk transfers such as PACS image reads and surgical teaching
4K-QAM12 bits per symbol, roughly 20% more throughput than Wi-Fi 6's 1024-QAMMore throughput at the same signal quality, which is what dense ward access needs
Preamble puncturingWhen part of a channel is interfered with, only the affected sub-channels are avoided instead of dropping the whole channel's rateWards are full of Bluetooth, microwave and telemetry equipment, so interference handling decides whether the service is stable
R-TWTReserved transmission slots for critical traffic that ordinary clients cannot takeDeterministic latency for monitors, infusion pumps and other critical IoT endpoints

A common misunderstanding: per-AP headline rates (5.97 Gbps, 8.45 Gbps) are lab figures for aggregated links. For a hospital, look at three things instead — measured throughput per client, roaming handover latency, and concurrent client capacity — not the number on the datasheet.

Seamless roaming: two workable routes

Much of what is marketed as seamless roaming is fast roaming: handover cut from seconds to hundreds of milliseconds, session preserved, but still perceptible. Only two routes actually stop the client from roaming at all:

Route A

Distributed antennas

An AP host plus feeder cable and discreet antennas along the ward corridor puts the whole ward in one radio domain, so a client moving within it never roams at all. Feeder runs reach a hundred metres and can be cascaded across floors; one host serves 8–12 rooms.

Route B

Multiple APs in one BSS

Several APs broadcast the same BSSID and are scheduled together by the controller, so the client believes it is on one network throughout. The experience is good, but standardisation is still in progress, implementations are largely vendor-proprietary and cost per point is higher.

ItemDistributed antennasMulti-AP coordination
Roaming behaviourNo roaming inside the ward; one fast handover at its edgeImperceptible across a floor; a better experience
Cost per pointLower — one host covers 8–12 roomsHigher — one AP per room
Bandwidth ceilingFeeder loss caps per-room rate; fine for PDAs and tabletsIndependent radio per room, higher bandwidth, suits image review
IoT expansionIoT slots on the host take Bluetooth / RFID gatewaysDepends on the AP's own IoT module
Where it fitsWards — where mobile nursing livesOutpatient halls, ICU, operating theatres

The options in the market today: Huawei AirEngine Wi-Fi 7 with iMaster NCE management (physical separation of the three networks); Ruijie distributed APs with Wi-Fi 7 seamless roaming (hybrid power-fiber between floors); H3C WTU distributed (strong value in wards and dormitories); Aruba (HPE) CX with Central (widely deployed in international hospitals and upscale hotels); Sangfor and Xinrui, strong on continuous operation and security integration.

Separation and compliance: meet the rules first, then judge performance

Under the Baseline for Classified Protection of Cybersecurity 2.0 and the health commission's national standards for hospital IT, hospital wireless carries three hard requirements:

01

Internal and external separated

The clinical network (HIS/PACS) and the internet egress must be separated, and public Wi-Fi must not share the core path with clinical traffic.

02

IoT carried separately

Medical IoT endpoints are numerous with a low security baseline: give them their own SSID and VLAN, and add 802.1X/MAC admission plus device fingerprinting.

03

Audit and traceability

Wireless access logs are kept to MLPS requirements, and access in sensitive areas such as pharmacies and equipment rooms must be traceable.

04

Recommended architecture

One physical network, three logical ones: shared core and APs, with VXLAN or multiple SSIDs separating clinical, public and IoT traffic, and admission policy classifying devices automatically.

A warning when specifying: enterprise Wi-Fi 7 requires WPA3-Enterprise (802.1X). Put the integration cost of an authentication server — or of joining the existing AD/Radius — into the bill of materials. It is routinely omitted from low bids and expensive to add later.

Five practical recommendations

01

Test the clients before choosing the APs

The network cards in existing PDAs and trolley terminals decide the real experience. Some older devices support only 2.4G or Wi-Fi 4/5, so survey the installed base first and budget for replacement where needed.

02

Distributed antennas in wards, density in outpatients

Wards are about mobile nursing, so seamless roaming comes first; outpatient halls are about sudden density, so high-density mounted APs come first. Do not mix the two or specify one model for both.

03

Size the uplink once

Wi-Fi 7 APs generally offer 2.5G/5G/10G uplinks. For a new campus, go straight to 10G at the access layer with a 40G core — otherwise you build a bottleneck where the AP is Wi-Fi 7 and the uplink is gigabit.

04

Plan controllers and licences over five years

AP counts keep growing during a project as IoT expands. Buy AC capacity, AP licences and admission licences at 120% of the end-state, so a second phase is not stranded by an end-of-sale.

05

Ask the vendor for roaming verification

Write into the contract that acceptance includes a roaming test with nursing devices moving between wards, with roaming traces and latency statistics as evidence — not just a coverage survey.

Three phases: a whole-site swap is not advisable

Phase one

0–6 months: seamless roaming in the wards

Distributed antennas in the wards, with core and aggregation moved to 40G/10G, and existing Wi-Fi 5 APs reused for IoT only. Target: mobile nursing performing as it should, and the three networks separated.

Phase two

6–18 months: outpatients and medical technology

High-density Wi-Fi 7 across outpatients, medical technology and offices, with admission integrated to AD. Target: whole-site coverage, one authentication and audit trail.

Phase three

18–36 months: IoT convergence and operations

Asset tracking, infusion monitoring and environmental sensing onboarded, with AI operations switched on. Target: wireless moves from cost line to the foundation of a smart hospital.

Phasing is easier on the budget and gives installed devices a natural replacement cycle. It is also worth telling the hospital plainly that Wi-Fi 5 is past end-of-sale and end-of-support: every further year widens the security exposure, which is the strongest argument for the upgrade budget.

Compiled by the Penghai technical team from a technical article on our WeChat account. Technical parameters follow each vendor's official documentation; for a specific project, the site survey and acceptance documents govern.

Survey the site first, then talk models and budget.

Contact us →