Quick answer
Do telehealth providers need a VPN?
It helps when clinicians see patients or open records on networks you don't control. A VPN encrypts traffic between each device and the VPN server, so home, clinic guest or hotel Wi-Fi sees encrypted data. HIPAA's Security Rule requires transmission security for covered entities, but a VPN alone doesn't make anyone compliant, and it doesn't replace your platforms' own security.
| Situation | What a VPN does |
|---|---|
| Visits and charting from a home office | Encrypts traffic to the VPN server, on top of HTTPS. |
| Clinic guest or hotel Wi-Fi | Encrypts traffic on a network others share. |
| Known phishing pages posing as EHR or payer portals | Web Shield blocks known ones while connected. |
| A stolen EHR password | No. Use two-step sign-in. |
| HIPAA compliance | No. A VPN is one safeguard, not compliance. |
Telehealth has become a standard care delivery model for millions of patients and tens of thousands of providers. Psychiatrists seeing patients from their home office. Physical therapists guiding exercise sessions via video. Nurse practitioners prescribing via remote visits. Dietitians tracking patient progress through secure messaging. In every one of these interactions, protected health information is flowing across an internet connection — over whatever network the provider happens to be using.
HIPAA doesn't pause for telehealth. For covered entities, the same Security Rule that applies to a hospital's records system applies to a video visit from a kitchen table. Its transmission security standard calls for measures that guard against unauthorized access to electronic PHI sent over a network, and it treats encryption as addressable (45 CFR 164.312(e)). For providers on home networks, clinic hotspots or anywhere that isn't a managed network, a VPN is one practical way to add encryption. It doesn't make anyone compliant on its own.
What HIPAA Requires for Telehealth Transmission Security
HIPAA's Security Rule (45 CFR § 164.312(e)) addresses the transmission of electronic PHI (ePHI). Specifically:
- Transmission Security (§ 164.312(e)(1)) — Covered entities must implement technical security measures to guard against unauthorized access to ePHI that is being transmitted over an electronic communications network. This is a required standard, not addressable.
- Encryption (§ 164.312(e)(2)(ii)): implement a mechanism to encrypt ePHI whenever deemed appropriate. This is addressable. According to HHS, you implement it if your risk assessment finds it reasonable and appropriate. If not, you document why and use an equivalent alternative where that is reasonable and appropriate.
HHS doesn't require a specific product. It asks covered entities to assess the risks to ePHI in their own setting and choose safeguards that fit (HHS risk analysis guidance). Home Wi-Fi, a clinic's guest hotspot and hotel internet are networks your organization may not control, so they belong in that risk analysis.
In practice, many providers working from home rely on two layers: the telehealth platform's own security for the visit, and a VPN that adds encryption for the rest of the connection, including EHR logins, patient messaging, prescription platforms and insurance portals.
CyberFence Teams, in one minute.
See how a small team gets VPN apps for staff devices and manages licenses from one dashboard.
Watch the 1-minute Teams film
Select play to load YouTube, then start the film in the player. YouTube processes data when loaded; its privacy policy applies.
Watch on YouTube (opens a new tab)
Read the video transcript
Your remote and traveling employees connect from home offices, airports, hotels, and client sites. Your clients trust your business. But you can't control every network your team uses.
Meet CyberFence Teams. Business VPN. Built for small teams. Help protect their internet connections with encrypted VPN protection. Web Shield helps block known harmful sites. Email breach monitoring helps identify known exposures. A practical layer for remote-work and business-travel security.
With apps for iPhone, iPad, Android, Mac, and Windows. Manage your team licenses in one place via the web app. Invite employees and manage team access, all from one dashboard.
CyberFence Teams. Protect the connections your business depends on.
What Telehealth Providers Transmit and Access Remotely
The clinical encounter itself is only part of the security picture. A telehealth provider's remote work session typically involves:
- EHR access — Epic, Cerner, athenahealth, eClinicalWorks, Practice Fusion. The EHR login and session contain the complete patient record for every patient seen during that session. EHR logins are worth protecting because they open records for many patients.
- Telehealth platform — Zoom for Healthcare, Doxy.me, Teladoc, Amwell, SimplePractice, TheraNest (for behavioral health). The platform credentials and session management controls are separate from the video encryption itself — a compromised account could be used to impersonate the provider, access scheduled visit records, or expose patient contact information.
- Prescription platforms — DEA-registered electronic prescribing systems (Surescripts, DoseSpot, DrFirst) used to prescribe controlled and non-controlled medications during telehealth visits. Prescription system credentials provide access to patient medication histories and prescription records.
- Patient messaging — Secure patient messaging through the EHR portal or a standalone platform (Klara, Spruce, OhMD). Message content may include PHI, medication questions, lab results, and patient-reported symptoms.
- Insurance and billing portals — Payer portals for authorization requests, claims submission, and eligibility verification. These portals contain patient insurance information, procedure codes, and claims history.
- Lab and diagnostic portals — LabCorp, Quest Diagnostics, and hospital system lab portals accessed to review test results and upload orders during telehealth visits.
Each of these platforms has its own login, session and connection, and they all travel over the same home network. Most already use HTTPS. A VPN adds a layer of encryption between the device and the VPN server, so the internet provider and others on the local network see encrypted traffic to the VPN server, not which healthcare systems are in use. It covers the apps that go through the VPN while it's connected.
The Home Network Security Gap
Many telehealth providers working from home connect through residential internet service, such as Comcast, Spectrum or AT&T, over consumer routers that may still use default passwords or old firmware. Past the Wi-Fi itself, the traffic is protected by whatever each app provides.
When a psychiatrist signs in to the EHR from home, that session travels from the laptop through the home router to the internet provider's network. The internet provider can see which sites the laptop connects to and when. On a home network shared with family members, a compromised device can be a risk to other devices on the same network.
A VPN encrypts traffic from the provider's device to the VPN server. While it's connected, the home router and the internet provider see encrypted traffic to the VPN server instead of EHR sessions, telehealth platform connections and patient messaging.
Clinic Hotspots and Hybrid Telehealth Settings
Many telehealth providers aren't working exclusively from home — they're conducting remote visits from clinic waiting rooms, shared workspace settings, or hotspot connections while traveling between locations. These environments introduce risks that a home network doesn't have: other people on the same network, unknown network configuration, and no control over who else might be monitoring traffic.
A clinic's patient waiting room Wi-Fi — used because the provider's exam room is occupied — is a shared network that patients, visitors, and anyone in range can access. An attacker on the same network can potentially monitor unencrypted traffic from other devices. When a telehealth provider logs into their EHR or prescription platform from this network without VPN encryption, those credentials travel over a network they don't control.
Connect CyberFence when you start work, before you open the EHR or prescription platform on a clinic hotspot, hotel Wi-Fi or café internet. Make it part of the routine, like checking your camera before a visit.
The Phishing Risk for Telehealth Platforms
Telehealth providers can receive a specific kind of phishing: fake messages that pose as telehealth platforms, EHR vendors and health system IT departments.
Examples to watch for:
- Fake "Zoom for Healthcare security alert" emails requiring immediate re-verification of credentials
- Spoofed EHR vendor messages (Epic, Cerner, athenahealth) claiming account lockout or security update
- Fake DEA electronic prescribing system alerts requiring credential confirmation
- Spoofed payer portal notifications claiming authorization expiration requiring immediate login
While CyberFence is connected, Web Shield blocks known malicious and phishing sites before the page loads, on the connected laptop, phone or tablet. If a link in one of these emails points to a reported phishing page, it doesn't load. It can't catch every new site, so check the sender and sign in through your usual bookmark.
What CyberFence Provides for Telehealth Providers
- Encryption on networks you don't control: home networks, clinic hotspots and hotel Wi-Fi, between each device and US-based servers while connected
- Another layer for logins: sign-ins to Epic, Cerner, athenahealth, Doxy.me, SimplePractice and other platforms travel inside the VPN connection, on top of their own HTTPS
- Prescription platform security — DEA-registered electronic prescribing connections encrypted through the VPN tunnel
- Web Shield: blocks known phishing sites posing as telehealth platforms, EHR vendors and insurance portals, while connected. It can't catch every new site
- A published no-logs policy: read CyberFence's privacy policy to see what it does and doesn't keep
- US-operated: a US-operated company with US-based servers
- Each person's devices: with Teams, each person gets their own account and apps for iPhone, iPad, Android, Mac and Windows. Check your plan's device allowance
Telehealth has extended care into home offices, satellite clinics and mobile settings, and for covered entities the Security Rule applies in all of them. A VPN is one practical way to add encryption on networks you don't control. It doesn't make a practice compliant, stop a stolen password or protect the patient's side of the visit. CyberFence Teams is $12 per person/month, billed annually, for teams of 2 to 500 people. A solo provider can start with a personal plan at $7.99/mo. See our guide for therapists who work remotely.
Frequently Asked Questions
Does HIPAA require telehealth providers to use a VPN?
HIPAA doesn't name a product. For covered entities, the Security Rule requires transmission security and treats encryption as addressable, based on your risk analysis. A VPN is one way to add encryption.
Does a VPN make a telehealth practice HIPAA compliant?
No. It can be one safeguard, but compliance depends on your whole program, including your platforms, agreements, training and risk analysis.
Does Web Shield stop all phishing?
No. It blocks known malicious and phishing sites while CyberFence is connected. New pages may not be listed yet.
I'm a solo provider. Do I need Teams?
No. A personal plan starts at $7.99/mo. Teams is for practices that want an account for each clinician.
How much does CyberFence Teams cost?
$12 per person a month, billed annually, for teams of 2 to 500 people. It includes VPN, Web Shield and Breach Monitor.
Read Next
Want to go deeper? Read how CyberFence protects other regulated industries , the CyberFence Teams product page , or CyberFence plans and pricing .