Skip to main content

Medical clinic WiFi providers checklist: patient access, clinical networks and HIPAA evidence

Use this checklist to choose a medical clinic WiFi provider that keeps patient WiFi away from clinical systems, gives every salaried doctor, locum and visiting clinician an individual, revocable credential, and runs on your existing access points. You will also know which six tests to run and which records to keep for your annual HIPAA audit.

By Iain JewittPublished
📖 14 min read3,116 words2 worked examples11 key definitions

Video overview

Medical clinic WiFi providers checklist: patient access, clinical networks and HIPAA evidence

A medical clinic needs three separate networks. Patients get filtered WiFi with no route to clinical systems. Practice-managed devices sit on the clinical network. Staff physicians, locums and visiting clinicians each get individual, revocable access. Choose a clinic WiFi provider that runs on your existing access points and produces access records for your HIPAA submission.

What does medical practice WiFi need to do?

A practice network carries people with different levels of trust. A patient in the waiting room is anonymous and brings an unmanaged cell phone. A staff physician is a known employee with access to patient records. A locum physician may work two sessions and never return. Each group needs its own network, or its own identity on a shared one.

You probably do not control the clinical network. In the US, regional healthcare networks commission core medical IT under federal and state digital services models. Your health system's IT delivery partner normally runs the clinical network. It also runs that network's connection to the secure health data network. Your WiFi provider runs everything else and keeps it away from that network.

Which networks does a medical clinic need, and who uses each?

Network Who uses it How they join What it can reach Filtering
Patient WiFi Patients, caregivers and visitors in the waiting room Open or Enhanced Open network with a captive portal Internet only DNS filtering by content category, plus a per-device bandwidth limit
Clinical network Practice-owned PCs, laptops and tablets IEEE 802.1X with device certificates, run by your IT delivery partner Secure clinical systems, EHR applications, practice file shares Set by your IT delivery partner
Staff personal devices Staff physicians, nurses, reception and admin staff on their own cell phones Individual credential tied to each person Internet only Malware and phishing blocking
Visiting clinician access Locums, contracted staff, community and hospital clinicians Individual credential with an expiration date Internet only, so they can reach their own employer's VPN Malware and phishing blocking
Building devices Check-in kiosks, call screens, door entry, printers Device-specific keys Only the services each device needs Allow-list only

The last row catches practices out. Kiosks and call screens often join whichever network was nearest at installation. Give them their own segment. The same pattern of public, staff and visiting-professional networks appears in fitness center and gym WiFi providers: members, swim-school parents and staff on one platform.

Why must patient devices stay off clinical systems?

A patient's cell phone has an unknown patch level and unknown apps. On the same segment as a reception PC, malware on that phone can scan for it and attack it. Security obligations apply to every organization that connects. Patient WiFi with any route to clinical systems puts your HIPAA compliance position at risk.

What do you need before you choose a medical practice WiFi provider?

Find out what your health system already provides

Many practices already run WiFi installed under a network agreement or a later IT contract. Ask your IT lead three questions. Who owns the access points? Who manages the firewall? Is patient WiFi in the current contract? The answers decide whether you replace a service, add to it or run alongside it.

Map what you already have

Before you speak to providers, list:

  • Access point make, model and firmware, and whether the vendor still supports it.
  • Internet lines: the primary connection, any separate broadband line, and their speeds.
  • Who holds admin rights to the switches and firewall.
  • How many sites you run, and whether staff move between them.
  • Where staff identities live: a practice or health system Microsoft Entra ID tenant, Okta, Google Workspace, or nowhere central.

Agree who owns which decision

The practice manager owns the decision. Your Data Privacy Officer reviews the patient captive portal; medical practices must comply with CCPA/CPRA and federal privacy laws. The IT lead signs off anything that touches the clinical network.

10 questions to ask medical practice WiFi providers

  1. Which access point vendors does it run on? Purple runs on Cisco Meraki, HPE Aruba, Ruckus, Juniper Mist, Ubiquiti UniFi, Cambium, Extreme and Fortinet.
  2. Can it keep patient, staff and visiting clinician traffic on separate segments with no route between them?
  3. Does each clinician get an individual credential instead of a shared password?
  4. Can a credential carry an expiration date for locums?
  5. Does it connect to Microsoft Entra ID, Okta or Google Workspace for salaried staff?
  6. Does it filter the patient network by category, and can you allow health information sites?
  7. What personal data does the patient captive portal collect, and where is it stored?
  8. Which certifications does the provider hold?
  9. Will it sign a data processing agreement under CCPA/CPRA?
  10. Can it export an access list for your HIPAA evidence?

How do you set up patient, staff and clinician access?

This section covers the decisions. Configuration steps differ by access point vendor, so follow Purple's support documentation for your hardware.

Patient WiFi in the waiting room

Separate the patient network in three layers:

  • Its own VLAN. A VLAN (virtual LAN, defined in IEEE 802.1Q) splits one physical network into logically separate segments. Patient WiFi gets its own network name and its own VLAN.
  • An internet-only route. The firewall denies the patient VLAN any route to internal addresses. That includes clinical systems, printers and the HSCN connection.
  • Client isolation. Patient devices cannot see or reach each other.

An open network sends traffic over the air unencrypted. Enhanced Open, based on Opportunistic Wireless Encryption (OWE, RFC 8110), encrypts each connection without a password. Some older patient devices do not support it. Check whether your access points offer a transition mode that serves both.

A captive portal is the page a device sees before it gets internet access. Keep yours to terms of use and a privacy notice. Patients are not in your waiting room to be marketed to. Purple uses conscious-choice opt-ins, so nothing is pre-checked. In a GP setting, the safest choice is no marketing opt-in at all. Purple's Guest WiFi runs the patient network and captive portal.

Set a per-device bandwidth limit on the access points. Without one, a few streaming devices can saturate a shared line. WiFi Analytics shows how many patient devices connect and when, which helps you size that limit.

Practice devices on the clinical network

Practice-owned devices that open EMIS Web or SystmOne belong on the clinical network your ICB IT delivery partner runs. These typically join using IEEE 802.1X, the standard that authenticates each device before it joins. The usual method is EAP-TLS, which uses a certificate on the device instead of a password. There is nothing to share or phish. Purple's role here is the boundary: no Purple-managed network has a route into it.

Salaried GPs, locums and visiting clinicians

Staff personal cell phones and visiting clinicians' laptops do not belong on the clinical network. They need internet access, and visiting clinicians use it to reach their own employer's VPN. What they need from you is an individual credential you can revoke.

Approach Credential per person Removing a leaver Hardware needed HIPAA evidence Suits
Shared staff password No, one key for everyone Change the key and re-enter it on every device Any access point None per person No one; replace it
Individual keys (iPSK) through SecurePass Yes Revoke one key; everyone else stays connected Your existing supported access points Named list with start and end dates Locums, ARRS staff, staff personal cell phones
IEEE 802.1X with Microsoft Entra ID, Okta or Google Workspace Yes, the person's directory account Disable the account and WiFi access stops WPA2 or WPA3-Enterprise access points plus Purple's cloud RADIUS Sign-in records tied to directory accounts Salaried staff with directory accounts

An iPSK (individual pre-shared key) gives each person their own WiFi password on the same network name. RADIUS is the protocol an access point uses to ask a server whether a device may join. Purple provides cloud RADIUS, so you host no server in the practice.

Apply three rules:

  • Salaried staff. If your practice or network runs Microsoft Entra ID, Okta or Google Workspace, connect it. Purple's Identity-Based Networks follow joiners, movers and leavers from the directory. Email accounts sit in a central tenant, so confirm options with your IT administrator first.
  • Locums. Issue an individual key with an end date matching the booking.
  • Visiting clinicians. Issue individual keys valid at every site, and review the list quarterly.

For the wider process behind this, read What is user provisioning? a plain-english guide for 2026.

Filtering on the patient network

Shield, Purple's filtering add-on, applies DNS filtering to the patient network. DNS filtering checks each website lookup against content categories and refuses blocked ones. It needs no software on patient devices.

Public standards set a useful baseline for public spaces. Standard policies expect pornography and explicit content to be blocked. Add malware and phishing categories. Children use waiting-room WiFi too.

Do not block what patients need. People look up symptoms, sexual health, mental health and drug support while they wait. Broad categories can block exactly the pages a doctor wants patients to read. Allow-list trusted health sites and test those topics directly. For a multi-site view of filtering policy, see Guest WiFi and DNS filtering platforms for MSPs: a multi-site checklist for multi-tenant management and white label.

Got questions about your specific setup?

Our team works with venue operators, IT managers, and network engineers across 80,000 venues. Book a 20-minute call and we will show you how others like you solved it.

How do you check the separation and filtering work?

Run these tests from a cell phone on each network:

  1. Route test. From patient WiFi, try to reach a reception PC, a printer and a clinical system address. Every attempt should fail.
  2. Isolation test. Put two cell phones on patient WiFi. Neither should see the other.
  3. Filter test. Visit a site in each blocked category. Each should return the block page.
  4. Health information test. Load health authority pages on sexual health, mental health and drug support. Each should load.
  5. Revocation test. Revoke a test temporary key. The test device should lose access.
  6. Bandwidth test. Run a speed test on patient WiFi. It should not exceed the per-device limit.

Record the date, the tester and each result. Repeat after any network change and before each HIPAA compliance audit. That record is evidence in its own right.

Which WiFi evidence supports your HIPAA submission?

HIPAA compliance for primary care network security is built on HHS data security standards. Practices submit attestation documentation annually. Check which requirements your practice completes this year. WiFi has no dedicated section, but it supports evidence across several standards.

Evidence What to keep Links to
Network diagram Each network name, VLAN and permitted route IT Protection
Segmentation test record Dated results of the six tests above IT Protection
Access list Named staff and clinician credentials with start and end dates Managing Data Access
Leaver process Written steps plus a log of revocations Managing Data Access
Access point firmware status Asset register entries with firmware and vendor support dates Unsupported Systems
Supplier assurance ISO 27001 and SOC 2 Type II certificates, Data Processing Agreement Accountable Vendors
Incident contact Provider's security contact and connection log retention period Responding to Incidents
Patient privacy notice Captive portal terms and privacy information CCPA/CPRA Privacy Notice

Build this pack once and update it when the network changes. Then annual reviews become a check-in, not a reconstruction.

What goes wrong, and how do you fix it?

A rogue device bridges patient WiFi onto the clinical network

Someone plugs a consumer router into a clinical wall port to boost signal. Patient traffic now lands on the clinical segment. Ask your IT delivery partner to restrict unused switch ports. Serve patient WiFi only from managed access points.

The shared staff password never changes

Every substitute provider and former employee still knows it. Replace it with individual keys and retire the shared network name.

Filtering blocks health information

A broad category blocks a sexual health or mental health page. Allow-list the domain and rerun the health information test.

Encrypted DNS bypasses filtering

Some browsers use DNS over HTTPS (RFC 8484), which can route lookups around a DNS filter. Block outbound DNS to resolvers other than the filter at the firewall. Ask your provider how it handles known DNS over HTTPS endpoints.

Substitute provider access outlives the placement

A key without an end date stays valid indefinitely. Set end dates at issue and review the full list quarterly.

The captive portal asks for too much

Name, email, and date of birth fields add CCPA/CPRA obligations with no benefit to the practice. Cut the portal back to terms acceptance.

How have primary care sites applied this?

These scenarios are illustrative, built from common primary care setups. The figures are counts within each scenario, not survey data.

Scenario 1: a four-practice clinic group with rotating clinicians

Situation. A primary care network covers four practices in one town. Each site had one shared staff WiFi password, unchanged for several years. The group's 14 staff members and nine regular locums moved between sites. When the clinic prepared its HIPAA compliance audit submission, nobody could list who had WiFi access.

What was done. The clinical network stayed with the IT delivery partner, untouched. Purple ran as a cloud overlay on the existing Cisco Meraki access points at all four sites. Each site gained filtered patient WiFi on its own VLAN. All 23 clinicians received individual keys valid across the group. Locum keys carried end dates matched to bookings.

Outcome. Four shared passwords became 23 named credentials, each with an owner and an end date. Removing a leaver became one action instead of re-keying four sites. The access list came from an export, not memory. Route tests at all four sites found no path from patient WiFi to any clinical address.

Scenario 2: a shared health center waiting room

Situation. A health center houses two medical practices, a community nursing team, and a pharmacy around one waiting area. Patient WiFi ran on the same flat network as the reception PCs. Afternoon video streaming slowed the shared line. A parent complained that the patient WiFi had no content filtering.

What was done. Patient WiFi moved to its own VLAN with an internet-only route and client isolation. Each patient device received a bandwidth limit on the access points. Shield blocked pornography, illegal content, malware, and phishing. The team allow-listed trusted medical resources.

Outcome. Re-testing from a patient device reached none of the reception PCs, printers, or clinical addresses. Every blocked category returned the block page, and every tested health page loaded. No single patient device could exceed its configured limit. The dated test record went into both practices' HIPAA evidence logs.

What does it cost, and what do you get back?

Costs fall into four lines:

  • Access points. If the vendor still supports yours, you keep them. Purple is hardware-agnostic, so most practices buy no new hardware. Read Why your next WiFi upgrade doesn't need new hardware.
  • Software licenses. These cover patient WiFi, staff and clinician access, and filtering. Purple quotes on your site count and the networks you need.
  • IT set-up time. VLAN and firewall changes need your IT delivery partner. Check whether the existing contract covers them.
  • Administration. Issuing and revoking credentials, reviewing filter policy, and running the annual tests.

What you get back:

  • Access points you already own stay in service.
  • A leaver or departing locum is removed in one action.
  • HIPAA evidence builds up as you run the network.
  • Patient WiFi that cannot reach clinical systems, with a dated test to prove it.
  • A supplier certified to ISO 27001 and Cyber Essentials, CCPA/CPRA compliant and B Corp certified. Purple has operated since 2012 and runs across 80,000+ live venues in 90 countries.

See how Purple works across primary and secondary care on the Healthcare page.

Frequently asked questions

Does Purple work with the access points our practice already has?

Yes, Purple is hardware-agnostic and runs as a cloud overlay on Cisco Meraki, HPE Aruba, Ruckus, Juniper Mist, Ubiquiti UniFi, Cambium, Extreme and Fortinet access points. You keep the hardware your healthcare organization or practice already owns, provided the vendor still supports it. Check firmware status first. Unsupported access points are a HIPAA compliance finding in their own right, whoever provides the WiFi software.

Can patient WiFi share a broadband line with practice systems?

Yes, if the patient network has its own VLAN, an internet-only route and a per-device bandwidth limit. The firewall must deny any route from the patient VLAN to internal addresses, including the internal network connection. Agree the design with your IT delivery partner. Then run the segmentation tests and keep the dated results with your HIPAA evidence.

Do patients have to register to use waiting-room WiFi?

No. A medical practice can run patient WiFi with a captive portal that asks only for acceptance of terms and shows a privacy notice. Collecting names, email addresses or marketing consent adds CCPA/CPRA obligations with little benefit to the practice. Purple uses conscious-choice opt-ins, so nothing is pre-checked, and you decide which fields the captive portal shows.

How do locums get WiFi without the shared staff password?

Give each temporary clinician an individual key that expires when the shift ends. With an individual pre-shared key (iPSK), every locum has a personal password on the same network name. Revoking one key leaves everyone else connected. The resulting access list doubles as HIPAA evidence for managing data access. Locums reach their own systems over the internet, never through your clinical network.

What supplier assurance does Purple provide for our HIPAA compliance?

Purple provides ISO 27001 and Cyber Essentials certificates and confirms CCPA/CPRA compliance. It has operated since 2012 across 80,000+ live venues in 90 countries. Together with a data processing agreement, those certificates form the accountable supplier evidence HIPAA asks for. Your IT department may run its own supplier checks, so share the certificates with its digital team early.

Who should own practice WiFi, the practice or the health system?

The health system normally owns the clinical network; ownership of patient and staff WiFi varies by area. Under standard IT operating models, health systems commission core IT, and some contracts include patient WiFi. Ask your IT lead what the current contract covers before you buy. Purple runs alongside a health system-managed clinical network without touching it.

How much work is a deployment for a small practice?

Most of the effort is agreeing on the network design, not installing hardware. Purple runs as a cloud overlay on supported access points, so there is no rip and replace. The practical steps are agreeing on VLANs and firewall rules with your IT delivery partner, setting up the captive portal and filtering, issuing credentials, and running the segmentation tests.

Does filtering patient WiFi stop patients reading health information?

No, not if you set it up correctly. Block pornography, illegal content, malware and phishing, then allow-list health information sites. Avoid broad categories that catch sexual health, mental health or drug support pages. Test those pages from a patient device after every policy change and record the result with your HIPAA compliance evidence.

Key Definitions

VLAN

A virtual LAN as defined in IEEE 802.1Q, which tags Ethernet frames with a VLAN identifier so one physical network carries logically separate segments, each with its own broadcast domain.

Patient WiFi gets its own network name and VLAN, and the firewall denies that VLAN any route to internal addresses. This is the first layer of separation you ask a provider and your IT delivery partner to agree on.

IEEE 802.1X

The IEEE standard for port-based network access control. It runs the Extensible Authentication Protocol (EAP) between the device, the access point and an authentication server, so each device or person is authenticated before any traffic is allowed.

Your IT delivery partner typically uses it on the clinical network. Purple uses it with WPA2 or WPA3-Enterprise access points and cloud RADIUS so salaried staff sign in with their directory accounts.

EAP-TLS

An EAP method used within IEEE 802.1X that authenticates the device with a digital certificate over a TLS exchange instead of a password, so there is no shared secret to leak or phish.

It is the usual method for clinic-owned PCs, laptops and tablets that open EHR software. Purple's role is to make sure no Purple-managed network has a route into that certificate-protected network.

iPSK (individual pre-shared key)

A WPA2-Personal style passphrase issued per person on a shared network name, so each key maps to one named individual and can be revoked without changing anyone else's key.

SecurePass issues iPSKs to locums, healthcare staff and staff personal phones. Revoking one key leaves everyone else connected, and the named list with start and end dates becomes HIPAA evidence for managing data access.

RADIUS

Remote Authentication Dial-In User Service, the protocol an access point uses to ask an authentication server whether a device may join, carrying the IEEE 802.1X and EAP exchange.

Purple provides cloud RADIUS, so you host no server in the practice. It links access points to Microsoft Entra ID, Okta or Google Workspace for salaried staff.

Enhanced Open (OWE)

Opportunistic Wireless Encryption, specified in RFC 8110, which runs a Diffie-Hellman key exchange during association so each client connection is encrypted without a password.

Use it for patient WiFi so waiting-room traffic is not sent unencrypted over the air. Some older patient devices do not support it, so check whether your access points offer a transition mode.

Captive portal

The page a device sees before it gets internet access. Where it collects personal data, CCPA/CPRA requires privacy information at the point of collection.

In a GP practice, keep it to terms of use and a privacy notice. Purple uses conscious-choice opt-ins with nothing pre-checked, and your Data Protection Officer reviews it.

DNS over HTTPS

A protocol specified in RFC 8484 that carries DNS queries inside HTTPS, encrypting lookups and sending them to a resolver of the browser's choice.

It can route patient lookups around a DNS filter such as Shield. Block outbound DNS to resolvers other than the filter at the firewall, and ask your provider how it handles known DNS over HTTPS endpoints.

Health Insurance Portability and Accountability Act (HIPAA)

The US federal law establishing national standards to protect sensitive patient health information from being disclosed without the patient's consent or knowledge.

WiFi has no dedicated section, but your network diagram, test record, access list, termination log, firmware status and supplier certificates support evidence for compliance audit requirements.

Healthcare Network Infrastructure

The data network for healthcare organizations. Every connecting organization accepts security obligations under their compliance and network agreements.

Your regional IT delivery partner normally runs the practice's secure connection. Patient WiFi with any route to it puts that agreement and your HIPAA compliance position at risk.

Client isolation

An access point setting that blocks wireless clients on the same network from communicating directly with each other at layer 2.

It is the third layer of patient WiFi separation after the VLAN and the internet-only route. The isolation test, two cell phones on patient WiFi that cannot see each other, proves it works.

Worked Examples

A four-practice primary care network has one shared staff WiFi password per site, unchanged for years. Its 14 healthcare staff and nine regular locums move between sites, and nobody can list who has WiFi access for the HIPAA audit. What should it do?

The clinical network stayed with the health system's IT delivery partner, untouched. Purple ran as a cloud overlay on the existing Cisco Meraki access points at all four sites, so no new hardware was needed. Each site gained filtered patient WiFi on its own VLAN. All 23 clinicians received individual keys valid across the network, and locum keys carried end dates matched to bookings. Four shared passwords became 23 named credentials, each with an owner and an end date. Removing a leaver became one action instead of re-keying four sites. The HIPAA access list came from an export, not memory, and route tests at every site found no path from patient WiFi to any clinical address.

A medical center houses two practices, a community nursing team and a pharmacy around one waiting area. Patient WiFi runs on the same flat network as the reception PCs, afternoon streaming slows the shared line, and a parent has complained about the lack of content filtering. How do you fix it?

Patient WiFi moved to its own VLAN with an internet-only route and client isolation, removing any path to reception PCs. Each patient device received a bandwidth limit on the access points, so a few streams could no longer saturate the line. Shield blocked pornography, illegal content, malware and phishing, and the team allow-listed trusted medical resources so health information stayed reachable. Re-testing from a patient device reached none of the reception PCs, printers or clinical addresses. Every blocked category returned the block page, and every tested health page loaded. No single patient device could exceed its configured limit. The dated test record went into both practices' HIPAA evidence.

Frequently asked questions

Does Purple work with the access points our practice already has?

Yes, Purple is hardware-agnostic and runs as a cloud overlay on Cisco Meraki, HPE Aruba, Ruckus, Juniper Mist, Ubiquiti UniFi, Cambium, Extreme and Fortinet access points. You keep the hardware your healthcare system or practice already owns, provided the vendor still supports it. Check firmware status first. Unsupported access points are a HIPAA compliance finding in their own right, whoever provides the WiFi software.

Can patient WiFi share an internet connection with practice systems?

Yes, if the patient network has its own VLAN, an internet-only route and a per-device bandwidth limit. The firewall must deny any route from the patient VLAN to internal addresses, including internal clinical network connections. Agree on the design with your IT delivery partner. Then run the segmentation tests and keep the dated results with your HIPAA compliance evidence.

Do patients have to register to use waiting-room WiFi?

No. A medical practice can run patient WiFi with a captive portal that asks only for acceptance of terms and shows a privacy notice. Collecting names, email addresses or marketing consent adds CCPA/CPRA obligations with little benefit to the practice. Purple uses conscious-choice opt-ins, so nothing is pre-ticked, and you decide which fields the captive portal shows.

How do visiting physicians get WiFi without the shared staff password?

Give each visiting physician an individual key that expires when the assignment ends. With an individual pre-shared key (iPSK), every visiting physician has a personal password on the same network name. Revoking one key leaves everyone else connected. The resulting access list doubles as HIPAA compliance evidence for managing data access. Visiting physicians reach their own systems over the internet, never through your clinical network.

What supplier assurance does Purple provide for our HIPAA compliance?

Purple provides ISO 27001 and Cyber Essentials certificates and confirms CCPA/CPRA compliance. It has operated since 2012 across 80,000+ live venues in 90 countries. Together with a business associate agreement under HIPAA, those certificates form the accountable supplier evidence that HIPAA requires. Your healthcare system may run its own vendor checks, so share the certificates with its digital team early.

Who should own practice WiFi, the practice or the healthcare system?

The health system normally owns the clinical network; ownership of patient and staff WiFi varies by region. Core practice IT is often managed at the system level, and some contracts include patient WiFi. Ask your IT lead what the current contract covers before you buy. Purple runs alongside a managed clinical network without touching it.

How much work is a deployment for a small practice?

Most of the effort is agreeing on the network design, not installing hardware. Purple runs as a cloud overlay on supported access points, so there is no rip and replace. The practical steps are agreeing on VLANs and firewall rules with your IT delivery partner, setting up the captive portal and filtering, issuing credentials, and running the segmentation tests.

Does filtering patient WiFi stop patients reading health information?

No, not if you set it up correctly. Block pornography, illegal content, malware and phishing, then allow-list health information sites such as cdc.gov. Avoid broad categories that catch sexual health, mental health or drug support pages. Test those pages from a patient device after every policy change and record the result with your HIPAA compliance evidence.

Got questions about your specific setup?

Our team works with venue operators, IT managers, and network engineers across 80,000 venues. Book a 20-minute call and we will show you how others like you solved it.