Skip to main content

Dental group WiFi providers checklist: patient WiFi, clinical networks and multi-practice rollout

Use this checklist to shortlist a dental practice WiFi provider that separates patient, staff, clinical and payment networks identically at every practice. You can then pilot the design at one practice, run seven isolation checks and roll it out in batches. You will also know which WiFi evidence to keep for PCI DSS, CCPA/CPRA, HIPAA and SOC 2 Type II.

By Iain JewittPublished
📖 15 min read3,478 words3 worked examples10 key definitions

Video overview

Dental group WiFi providers checklist: patient WiFi, clinical networks and multi-practice rollout

Every dental practice needs four separate networks: patient WiFi in reception, staff access for clinicians, a clinical segment for imaging and practice management, and an isolated payment segment for card terminals. The right provider enforces that separation identically across every practice. It filters the patient network and produces the evidence PCI DSS and CCPA/CPRA audits ask for.

Which networks does a dental practice need, and who uses each?

A dental practice runs more connected equipment than its size suggests. Reception hosts patients on their own phones. Surgeries hold intraoral scanners, imaging workstations and sensors. The front desk runs the practice management system and the card terminal. Each group of devices carries a different risk, so each belongs on its own network.

Network Who uses it Typical devices How they connect Filtering What it can reach
Patient WiFi Patients and visitors in reception Personal cell phones, tablets, laptops Captive portal sign-in, client isolation on Purple Shield, family-safe policy Internet only
Staff WiFi Dentists, associates, hygienists, therapists, nurses, reception team Group laptops, tablets, staff cell phones 802.1X with group identity provider credentials Purple Shield, business policy Internet and approved internal applications
Clinical devices Equipment only, no people Intraoral scanners, imaging workstations, practice management terminals, networked printers iPSK per device class, or wired Allow-list of named vendor endpoints Imaging and practice management servers or cloud services only
Payment Card terminals only Wireless card terminals Dedicated network with its own key, or cellular Allow-list of the payment processor Payment processor only

A few terms appear throughout this guide, so here they are once:

  • Captive portal: the sign-in page a patient sees before getting online.
  • 802.1X: the IEEE standard for network access control. Each person authenticates with their own credentials, not a shared password.
  • RADIUS: the authentication server that checks those credentials and tells the access point what to allow.
  • iPSK (identity pre-shared key): a unique WiFi key per device or device group, on one network name.
  • VLAN: a virtual LAN that keeps traffic from different networks apart on the same physical switches and access points.

Each of the four networks maps to its own VLAN. Firewall rules sit between them. Patient traffic goes to the internet and nowhere else. Clinical and payment devices reach only the services they need.

Imaging and practice management systems handle health data, which CCPA/CPRA treats as sensitive personal information. Card terminals bring PCI DSS into play. Keeping both away from patient cell phones protects the data and limits how much of your network an auditor must examine.

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

Most of the work in a dental group WiFi project happens before anyone touches an access point. Gather six things first.

  1. A device inventory for every practice. List what connects, whether it is wired or wireless, and who supports it. Imaging vendors often specify network requirements, so collect their documentation.
  2. A people map. Note which associates, hygienists, therapists and traveling staff work at more than one practice. These people define your cross-practice access policy.
  3. Your identity provider. Microsoft Entra ID, Okta or Google Workspace already holds your staff accounts. Your WiFi should use those accounts, not a separate list.
  4. Your card payment set-up. Record how each terminal connects (WiFi, wired or cellular) and which PCI DSS self-assessment questionnaire your acquirer expects.
  5. Your data security obligations. Healthcare providers must comply with HIPAA each year. Many groups also maintain SOC 2 Type II compliance. Both ask about access control and network separation.
  6. Your current access points and broadband. Note the make and model at each practice. A hardware-agnostic platform can run on mixed estates, which matters after acquisitions.

The dental practice WiFi providers checklist

Put these 10 questions to every provider on your shortlist.

  1. Can you run patient, staff, clinical and payment networks with enforced separation at every practice from one policy?
  2. Do you run on the access points we already own, or do we need new hardware?
  3. Do staff authenticate with 802.1X against Microsoft Entra ID, Okta or Google Workspace?
  4. Can one clinician use the same credentials at every practice in the group?
  5. How do clinical devices that cannot run 802.1X get unique credentials?
  6. When someone leaves, how many places do we change to remove their access?
  7. Can you filter the patient and staff networks with different policies?
  8. What authentication logs and configuration exports can we hand to an auditor?
  9. Which security certifications do you hold? Purple holds ISO 27001 and Cyber Essentials.
  10. How do you handle the personal data patients give at sign-in under CCPA/CPRA?

A provider that answers "per site" to questions one, four or six will create work for every practice you add.

How do you set up patient, staff and clinical networks across every practice?

Build the design once, prove it at one practice, then roll it out in batches. Purple's support documentation covers the vendor-specific configuration steps for each access point platform.

Patient WiFi in reception

Patients get a short captive portal sign-in, then internet access with client isolation switched on. Client isolation stops one patient's phone from seeing another's. Set a per-device bandwidth limit so a large download in waiting room cannot slow the staff network.

Keep sign-in data to what you need. Purple's Guest WiFi uses conscious-choice opt-ins, so patients decide whether to hear from you. Never ask for clinical information at sign-in. If you plan to use the data for practice communications, read our guide to a first party data strategy for US venues.

WiFi Analytics shows visit and dwell data by practice. Practice managers can compare waiting room patterns across sites.

Staff access for clinicians who work across practices

Staff connect with 802.1X. The access point passes their credentials to Purple's cloud RADIUS, which checks them against your identity provider. Two common methods sit under 802.1X:

  • EAP-TLS uses a certificate on the device. It suits group-managed laptops and tablets.
  • PEAP uses a username and password inside an encrypted tunnel. It suits mixed or personal devices.

Use WPA3-Enterprise where your access points and devices support it. Because authentication runs against one identity provider, an associate who works Mondays in one practice and Thursdays in another uses the same credentials at both. Nobody hands them a practice password.

Purple's Identity-Based Networks handle joiners, movers and leavers through the identity provider. A new hygienist gets access when HR creates their account. A leaver loses access at their next authentication attempt once you disable the account. For locums, issue time-limited access that expires at the end of the booking.

SecurePass extends identity-based access to staff devices that sit outside your device management.

Clinical devices: imaging and practice management

Wire imaging workstations and practice management servers wherever the building allows. Wired connections remove a wireless attack surface and keep large image files off the airwaves.

Devices that must be wireless, such as some intraoral scanners and chairside tablets, join the clinical network with iPSK. Each device class gets its own key, and the RADIUS response places it on the clinical VLAN. If a scanner is replaced, you revoke one key without touching the others.

Firewall rules on the clinical VLAN allow traffic only to the imaging server, the practice management service and named vendor update endpoints. Patient and staff networks have no route in.

Payment: card terminals

PCI DSS v4.0 requirement 1.3.3 requires network security controls between every wireless network and the cardholder data environment. In practice, that means card terminals never share a network with patients or staff.

You have three options. Put wireless terminals on a dedicated payment network with its own key. Wire them to an isolated payment VLAN. Or use terminals with their own cellular connection, which keeps them off your network entirely. Check with your acquirer which option keeps your questionnaire smallest.

If you keep a wireless payment network, PCI DSS requirement 2.3.2 applies. You must change its key whenever someone who knows it leaves. Limit knowledge of that key to one or two named people.

Filtering on the patient and staff networks

Patients include children, and waiting areas are shared spaces. Purple Shield filters the patient network with a family-safe policy: block adult content, malware and phishing domains. Apply a separate business policy to the staff network that blocks malicious sites without blocking clinical research or supplier portals.

Review blocked-request reports monthly for the first quarter. Adjust where a legitimate site gets caught.

Rolling out across multiple practices

Create one template covering network names, VLANs, firewall rules, filtering policies and identity groups. Apply it to a pilot practice and run every check in the next section. Then deploy in batches of practices, newest acquisitions last, since they carry the most legacy configuration.

Purple runs as a cloud overlay on Cisco Meraki, HPE Aruba, Ruckus, Juniper Mist, Ubiquiti UniFi, Cambium, Extreme and Fortinet. Mixed estates after acquisitions stay on one policy. Our article on why your next WiFi upgrade doesn't need new hardware explains the overlay model.

How do you check the patient network cannot reach clinical systems?

Run these seven checks at the pilot practice, then at a sample of practices in each batch.

  1. Patient-to-clinical test. Connect a laptop to patient WiFi and attempt to reach the imaging server and practice management terminals. Every attempt should fail.
  2. Patient-to-payment test. From the same laptop, attempt to reach the card terminal addresses. Every attempt should fail.
  3. Client isolation test. Connect two devices to patient WiFi and confirm neither can see the other.
  4. Cross-practice login test. Have an associate sign in at two practices with the same credentials. Confirm they land on the staff VLAN at both.
  5. Leaver test. Disable a test account in your identity provider. Confirm it cannot reconnect at any practice.
  6. Filtering test. Request a known adult-content test domain from patient WiFi. Confirm Purple Shield blocks it.
  7. Clinical allow-list test. From a clinical device, confirm the practice management service works and general web browsing does not.

Record the date, tester and result for each check. Those records become audit evidence. For the wider picture beyond WiFi, read securing a business network: a practical guide for 2026.

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.

Which WiFi evidence supports your data security and PCI DSS obligations?

Your WiFi provider cannot make you compliant. It can produce most of the network evidence your assessments ask for. Keep the following for every practice.

Obligation What it asks WiFi evidence to keep
PCI DSS v4.0 req. 1.3.3 Network security controls between all wireless networks and the cardholder data environment Firewall rules showing patient and staff networks denied access to the payment segment
PCI DSS v4.0 req. 2.3.1 Wireless vendor defaults changed on networks connected to the cardholder data environment Configuration export showing default network names, keys and admin passwords replaced
PCI DSS v4.0 req. 2.3.2 Wireless keys changed when anyone with knowledge of them leaves Named key holders for the payment network, leaver records, staff on 802.1X with no shared key
PCI DSS v4.0 req. 11.2.1 Authorized and unauthorized wireless access points identified at least every three months Quarterly rogue access point reports per practice
PCI DSS v4.0 req. 11.4.5 Segmentation controls penetration tested at least every 12 months and after changes Segmentation test report covering every practice, plus your own check records
CCPA/CPRA Appropriate technical and organizational measures to secure personal data, including health data Network design, access policy, per-identity authentication logs
HIPAA Annual assessment for healthcare organizations, including network and access controls Network diagram per practice, staff access policy, leaver revocation records
SOC 2 Type II Essential controls, including firewalls, secure configuration and user access control Firewall configuration, account lists from the identity provider, filtering policy

The PCI Security Standards Council's information supplement on scoping and network segmentation explains why segmentation matters. Systems outside the cardholder data environment, properly isolated, fall out of scope. A flat practice network puts every device in scope.

Per-identity logs matter most during an incident. "Someone on the staff password" tells an investigator nothing. "This associate's account, at this practice, at this time" answers the question.

What goes wrong, and how do you fix it?

The inherited flat network

Acquired practices often run one network for everything, with the password on a sticky note at reception. Fix it by applying your template during integration, before connecting the practice to group systems. Treat the old password as compromised and retire it the same day.

The imaging vendor wants everything on one network

Some imaging software expects workstations, sensors and servers to discover each other on one subnet. Put all of those devices on the clinical VLAN together. That meets the vendor's need without exposing anything to patients or staff browsing.

Shared staff passwords survive the rollout

Reception teams sometimes keep a shared password "for emergencies". Remove it. Every staff device authenticates as a named person or a named device class. If a device cannot do 802.1X, it gets an iPSK on the clinical network.

Locum access that never expires

A locum's account stays live after the booking ends, and nobody notices. Issue locum access with a fixed end date from day one. Review active accounts in your identity provider monthly.

Card terminals drift onto patient WiFi

A replacement terminal arrives, and someone joins it to the network with the strongest signal. Hide the payment network name, restrict knowledge of its key, and include terminal connections in your quarterly check.

Patient streaming slows the office

Reception phones stream video while a scanner uploads images. Set bandwidth limits on patient WiFi and give the clinical VLAN priority on the practice's broadband.

Filtering blocks a legitimate site

A dental supplier or CPD platform lands in a blocked category. Add it to the staff allow-list in Purple Shield, and record why in your change log.

What does a multi-practice rollout look like in practice?

The two scenarios below are composites of common deployment patterns, not named Purple customers. The outcomes are the design results each one produces.

Scenario 1: a public-sector community dental service

Situation. A healthcare system runs a community dental service from 11 clinics inside health centers. Each clinic had one WiFi network with a shared password for staff. Patients used a second network on the same VLAN. Dental officers and therapists rotate between clinics weekly. The service needed cleaner evidence for its HIPAA compliance submission.

What was done. The healthcare system deployed Purple Access on its existing access points. Each clinic got three networks: patient, staff and clinical. Staff authenticate with 802.1X against Microsoft Entra ID. Imaging and practice management devices sit on the clinical VLAN with iPSK. Card payments are rare, so the organization moved its terminals to cellular. Purple Shield filters the patient network with a family-safe policy, as many patients are children.

Outcome. Shared staff passwords fell from 11 to zero. Rotating clinicians use one set of credentials across all 11 clinics. A leaver now needs one change in Microsoft Entra ID instead of 11 password changes. The HIPAA documentation included a network diagram and access policy covering every clinic. For the wider sector context, see our Healthcare page.

Scenario 2: a dental group in shopping centers and strip malls

Situation. A private dental group runs 14 practices. Six sit inside shopping centers and strip malls, and eight are downtown. Acquisitions left a mix of Cisco Meraki and Ubiquiti UniFi access points. Card terminals at most practices shared the single practice network with staff and patients. That put the whole network in PCI DSS scope.

What was done. The group applied one template to both hardware platforms through Purple's cloud overlay. Every practice got patient, staff, clinical and payment networks. Card terminals moved to a dedicated payment network with a key known to two named people. In shopping center units, the team picked network names that patients would not confuse with the center's own WiFi. The shopping center WiFi platforms guide covers how centers run their own shopper networks alongside tenants.

Outcome. Card terminals left the shared network at all 14 practices. Patient and staff networks dropped out of PCI DSS scope, leaving the payment network as the only wireless network in scope. Associates working across practices moved from up to three practice passwords to one identity. The group's Retail neighbors run similar segmentation for their own registers.

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

Your costs fall into four areas: the WiFi platform per practice, any access point upgrades, broadband, and the staff time for device audits and testing. On a hardware-agnostic platform, the second item is often zero. The segmentation penetration test is a separate annual cost under PCI DSS requirement 11.4.5, whichever provider you choose.

Approach New hardware needed Removing a leaver PCI DSS 2.3.2 key changes Cross-practice access Audit evidence Suits
One shared password per practice None Change the password at every practice they knew Required each time anyone leaves, at every affected practice A different password per practice No record of who connected A single practice with terminals on cellular
Per-practice VLANs configured site by site None if access points support VLAN tagging Change shared keys at each affected practice Required for any shared key on a payment network Configured separately at each practice Configuration exports per site, gathered by hand Two or three practices with on-site IT support
Identity-Based Networks from Purple's cloud overlay None on Cisco Meraki, HPE Aruba, Ruckus, Juniper Mist, Ubiquiti UniFi, Cambium, Extreme or Fortinet Disable one account in the identity provider None for staff on 802.1X; payment key held by named people One identity works at every practice Per-identity logs and one policy across all practices Groups that share clinicians across practices

What you get back is measurable in your own operation:

  • Smaller PCI DSS scope. Isolating terminals takes patient and staff networks out of scope, which shrinks your questionnaire and your segmentation test.
  • Fewer password changes. Staff on 802.1X remove the shared keys that requirement 2.3.2 forces you to rotate.
  • Faster onboarding. A new associate gets access at every practice when their account is created.
  • One evidence set. Logs, policies and configuration for every practice come from one place, ready for HIPAA, Cyber Essentials or a PCI assessment.

Purple runs across 80,000+ live venues in more than 90 countries (Purple master deck, 2026). The same platform scales from a five-practice group to a national estate.

Frequently asked questions

Does Purple work with the access points already installed in our practices?

Yes. Purple runs as a cloud overlay on Cisco Meraki, HPE Aruba, Ruckus, Juniper Mist, Ubiquiti UniFi, Cambium, Extreme and Fortinet access points. Groups that have grown through acquisition often run two or three of these platforms. Purple applies one set of patient, staff, clinical and payment policies across all of them, so you do not need to standardize hardware before rolling out.

Can associates and hygienists use one login at every practice in the group?

Yes. Staff authenticate with 802.1X against your identity provider, whether that is Microsoft Entra ID, Okta or Google Workspace. The same credentials work at every practice running Purple. An associate who works across three sites signs in once per device and connects automatically at each one. When they leave, disabling their account removes access everywhere.

Do card terminals need a separate network from patient WiFi?

Yes. PCI DSS v4.0 requirement 1.3.3 requires network security controls between every wireless network and the cardholder data environment. Put wireless terminals on a dedicated payment network, wire them to an isolated VLAN, or use cellular terminals. Keeping them apart also takes your patient and staff networks out of PCI DSS scope, which reduces your assessment effort.

Will a WiFi provider make our dental group PCI DSS compliant?

No. Compliance covers your whole payment process, and no WiFi provider can certify it for you. A provider can deliver the network separation PCI DSS expects and the evidence an assessor asks for. That includes firewall rules, per-identity authentication logs and configuration exports. You still need quarterly wireless scans and an annual segmentation penetration test.

Should patient WiFi in a dental waiting area be filtered?

Yes. Waiting areas are shared spaces and often include children, so filter adult content, malware and phishing domains. Purple Shield applies a family-safe policy to the patient network and a separate business policy to staff WiFi. Review blocked-request reports for the first few months and allow-list any legitimate sites that get caught.

How does Purple handle the personal data patients give at WiFi sign-in?

Purple processes sign-in data under CCPA/CPRA and holds ISO 27001 certification. Patients choose whether to receive communications through conscious-choice opt-ins, and you decide which fields the sign-in page asks for. Keep it to what you need, and never collect clinical information at sign-in. Health data stays on your clinical systems, which the patient network cannot reach.

What happens to WiFi access when a clinician leaves the group?

Their access ends when you disable their account in your identity provider. Because staff authenticate with 802.1X, there is no shared password to change at each practice. Their next connection attempt fails at every site. Clinical devices on iPSK are unaffected, since each device class has its own key that the departing clinician never held.

Key Definitions

802.1X

IEEE 802.1X is the IEEE standard for port-based network access control. It carries EAP authentication between the device, the access point and an authentication server, so each person signs in with their own credentials, not a shared password.

You meet it when you set up Staff WiFi. It lets one clinician use the same credentials at every practice and removes shared keys that PCI DSS requirement 2.3.2 forces you to rotate.

RADIUS

Remote Authentication Dial In User Service, specified in IETF RFC 2865. The access point sends credentials to a RADIUS server, which checks them and returns an accept or reject with attributes such as the VLAN to assign.

Purple's cloud RADIUS checks staff credentials against your identity provider and places iPSK devices on the clinical VLAN, so one policy applies across every practice.

EAP-TLS

The Extensible Authentication Protocol method defined in IETF RFC 5216, which authenticates the device with a certificate inside a TLS exchange under 802.1X.

Use it for group-managed laptops and tablets, where you can install certificates and avoid passwords on the WiFi entirely.

PEAP

Protected EAP, an 802.1X method that wraps a username and password exchange inside an encrypted TLS tunnel.

It suits mixed or personal staff devices that cannot hold a certificate, while still authenticating each person against your identity provider.

iPSK

Identity pre-shared key: a unique WiFi key per device or device group on one network name, with the RADIUS response assigning each key to a VLAN.

Clinical devices such as some intraoral scanners cannot run 802.1X. iPSK gives each device class its own key, so replacing a scanner means revoking one key only.

VLAN

A virtual LAN as defined by IEEE 802.1Q tagging, which keeps traffic from different networks apart on the same physical switches and access points.

Each of the four dental networks maps to its own VLAN, with firewall rules between them. Your access points must support VLAN tagging for site-by-site or overlay designs.

Captive portal

The sign-in page a visitor sees before gaining internet access on a guest network, typically collecting consent and limited personal data.

Patients sign in through it in reception. Keep fields to what you need, use conscious-choice opt-ins and never ask for clinical information.

Cardholder data environment

Under PCI DSS v4.0, the people, processes and systems that store, process or transmit cardholder data. Requirement 1.3.3 requires network security controls between all wireless networks and it.

Card terminals sit in it. Isolating them on a payment network, isolated VLAN or cellular keeps patient and staff networks out of PCI DSS scope.

Special category data

HIPAA Rules class protected health information (PHI) as sensitive data requiring strict security standards. Implementation specifications require appropriate technical and organizational security measures.

Imaging and practice management systems hold it, which is why the clinical VLAN must be unreachable from patient and staff networks.

HIPAA Security Rule Compliance

The US national security standard for protecting electronic protected health information (ePHI), covering technical safeguards including access control, audit controls, integrity, and transmission security.

Your WiFi provider should supply a network diagram per practice, a staff access policy and departure revocation records for the audit.

Worked Examples

A healthcare system runs a community dental service from 11 clinics in medical centers. Each clinic has one staff network with a shared password, patients share the same VLAN, and clinicians rotate between clinics weekly. How should it clean up its HIPAA compliance evidence?

The healthcare system deployed Purple on its existing access points and gave each clinic patient, staff and clinical networks. Staff authenticate with 802.1X against Microsoft Entra ID, so rotating clinicians use one set of credentials everywhere. Imaging and practice management devices sit on the clinical VLAN with iPSK. Card payments were rare, so terminals moved to cellular. Purple Shield filters the patient network with a family-safe policy because many patients are children. Shared staff passwords fell from 11 to zero, and a leaver now needs one change in Microsoft Entra ID instead of 11 password changes. The HIPAA compliance audit documentation included a network diagram and access policy covering every clinic. This is a composite scenario, not a named customer.

A private dental group runs 14 practices, six in shopping centers and strip malls, on a mix of Cisco Meraki and Ubiquiti UniFi access points. Card terminals share one network with staff and patients, putting everything in PCI DSS scope. What changes?

The group applied one template to both hardware platforms through Purple's cloud overlay, so acquisitions did not force a hardware standard. Every practice got patient, staff, clinical and payment networks. Card terminals moved to a dedicated payment network with a key known to two named people, meeting the intent of requirement 2.3.2. In shopping center units, network names were chosen so patients would not confuse them with the center's own WiFi. Card terminals left the shared network at all 14 practices. Patient and staff networks dropped out of PCI DSS scope, leaving the payment network as the only wireless network in scope. Associates moved from up to three practice passwords to one identity. This is a composite scenario, not a named customer.

A newly acquired practice runs one network for everything, with the password on a sticky note at reception. How do you bring it into the group?

Apply your group template during integration, before you connect the practice to group systems. The template sets network names, VLANs, firewall rules, filtering policies and identity groups in one step. Treat the old password as compromised and retire it the same day. Move staff onto 802.1X against your identity provider, give wireless clinical devices an iPSK per device class, and move card terminals to the payment network or cellular. Then run the seven isolation checks, including patient-to-clinical and patient-to-payment tests, and record date, tester and result. Deploying newest acquisitions last in each rollout batch helps, because they carry the most legacy configuration.

Frequently asked questions

Does Purple work with the access points already installed in our practices?

Yes. Purple runs as a cloud overlay on Cisco Meraki, HPE Aruba, Ruckus, Juniper Mist, Ubiquiti UniFi, Cambium, Extreme and Fortinet access points. Groups that have grown through acquisition often run two or three of these platforms. Purple applies one set of patient, staff, clinical and payment policies across all of them, so you do not need to standardize hardware before rolling out.

Can associates and hygienists use one login at every practice in the group?

Yes. Staff authenticate with 802.1X against your identity provider, whether that is Microsoft Entra ID, Okta or Google Workspace. The same credentials work at every practice running Purple. An associate who works across three sites signs in once per device and connects automatically at each one. When they leave, disabling their account removes access everywhere.

Do card terminals need a separate network from patient WiFi?

Yes. PCI DSS v4.0 requirement 1.3.3 requires network security controls between every wireless network and the cardholder data environment. Put wireless terminals on a dedicated payment network, wire them to an isolated VLAN, or use cellular terminals. Keeping them apart also takes your patient and staff networks out of PCI DSS scope, which reduces your assessment effort.

Will a WiFi provider make our dental group PCI DSS compliant?

No. Compliance covers your whole payment process, and no WiFi provider can certify it for you. A provider can deliver the network separation PCI DSS expects and the evidence an assessor asks for. That includes firewall rules, per-identity authentication logs and configuration exports. You still need quarterly wireless scans and an annual segmentation penetration test.

Should patient WiFi in a dental waiting area be filtered?

Yes. Waiting areas are shared spaces and often include children, so filter adult content, malware and phishing domains. Purple Shield applies a family-safe policy to the patient network and a separate business policy to staff WiFi. Review blocked-request reports for the first few months and allow-list any legitimate sites that get caught.

How does Purple handle the personal data patients give at WiFi sign-in?

Purple processes sign-in data under CCPA/CPRA and HIPAA and holds ISO 27001 certification. Patients choose whether to receive communications through conscious-choice opt-ins, and you decide which fields the sign-in page asks for. Keep it to what you need, and never collect clinical information at sign-in. Health data stays on your clinical systems, which the patient network cannot reach.

What happens to WiFi access when a clinician leaves the group?

Their access ends when you disable their account in your identity provider. Because staff authenticate with 802.1X, there is no shared password to change at each practice. Their next connection attempt fails at every site. Clinical devices on iPSK are unaffected, since each device class has its own key that the departing clinician never held.

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.