Telehealth HIPAA Compliance: Providers Can’t Rely on Old Waivers
Telehealth HIPAA Compliance: Providers Can’t Rely on Old Waivers

Yes, HIPAA applies to telehealth whenever electronic protected health information, or ePHI, is created, received, maintained, or transmitted, and according to Hhs the pandemic-era enforcement discretion no longer applies. If you deliver care remotely, your first moves are a telehealth-focused risk analysis, confirmed business associate agreements with every vendor that touches ePHI, and platform encryption with multi-factor authentication turned on.
TL;DR:
- Standard landline calls fall outside the Security Rule, but internet audio or video services require safeguards such as encryption and access controls.
- Telephone carriers are generally conduits, but video, scheduling, transcription, and cloud vendors handling ePHI need signed business associate agreements before accessing patient data.
- An impermissible disclosure is presumed a breach; document a formal assessment showing low probability of compromise, or notify patients and HHS within statutory timelines.
- Require multi factor authentication for every staff account touching ePHI, retain session logs for audits, and patch clinical devices on a defined schedule.
- Scope risk analyses to video, chat, recordings, integrations, and remote devices, then document remediation priorities, update written policies, and retain staff training records.
Table of Contents
- Which HIPAA rules apply to telehealth and how they govern remote care
- Technical safeguards providers must verify for telehealth platforms
- Business associate agreements and practical vendor-management checklist
- Telehealth-focused risk analysis, policies, training, and incident response
- Consent, recordings, documentation, and retention rules for telehealth encounters
- CMS, licensure, and operational issues that affect telehealth HIPAA compliance
- How CoreWorx operationalizes telehealth compliance fixes
- What most practices get wrong about telehealth compliance
- Get your telehealth systems audit-ready with CoreWorx
- FAQ
- Sources
Which HIPAA rules apply to telehealth and how they govern remote care
Three HIPAA rules govern telehealth once ePHI enters the picture. The Privacy Rule controls how you use and disclose patient information during a virtual visit. The Security Rule requires technical, administrative, and physical safeguards whenever that information is transmitted or stored electronically. The Breach Notification Rule dictates what happens if something goes wrong.
Not every telehealth interaction triggers the Security Rule. HHS guidance on audio-only telehealth clarifies that a call placed over a standard landline is not electronic transmission, so it falls outside Security Rule scope. The moment you switch to VoIP, a smartphone app, or any internet-based audio or video service, the safeguards apply in full, including encryption and access controls.
Breach response works on a presumption you need to understand before an incident happens, not during one:
- Any impermissible use or disclosure of PHI is presumed to be a breach under the Breach Notification Rule.
- The burden falls on you to document a low probability of compromise through a formal risk assessment if you want to avoid notification obligations.
- Failing that documentation, you must notify affected individuals and HHS within the statutory timelines.
- Keep records of every assessment, whether or not it results in a reportable breach, since auditors will ask for them.
OCR currently treats pandemic-era flexibilities as expired, according to HHS.gov, which means covered entities are expected to have fully configured, compliant telehealth platforms now, not platforms running on temporary leniency.
Technical safeguards providers must verify for telehealth platforms
The Security Rule requires access controls, encryption, and audit controls, and the HHS Security Rule overview spells out what that looks like in practice for telehealth specifically. Four areas deserve direct verification rather than assumption.
Encryption needs to cover data both in transit and at rest. Most mainstream telehealth platforms default to modern encryption standards, but you still need to confirm the setting is active rather than optional, especially on any custom-built or integrated tool.
Authentication is where many practices leave gaps. Require multi-factor authentication for every provider account with access to ePHI, and enforce least-privilege permissions so staff only see what their role requires.
- Turn on MFA for all clinician and staff accounts touching telehealth systems, not just admin logins.
- Log session-level details: who joined, from what device, from what IP address, and at what time.
- Retain those logs long enough to support an audit or breach investigation.
- Patch operating systems and endpoint software on a defined schedule rather than ad hoc.
- Deploy endpoint detection and response (EDR) tools on any device used for clinical video or messaging.
Device hardening often gets overlooked because it feels like an IT problem separate from HIPAA. It isn’t. A clinician’s laptop or tablet used for telehealth is part of your Security Rule obligations the moment it touches ePHI, and HHS guidance materials recommend system hardening and security baselines as standard practice. Partner resources on endpoint security for distributed teams offer additional detail on patching cadence and monitoring if you manage a remote clinical workforce.
Pro Tip: Audit your MFA coverage quarterly, not annually. New staff accounts and third-party integrations are the most common places MFA quietly falls off.
Business associate agreements and practical vendor-management checklist
Not every telehealth vendor needs a business associate agreement (BAA). A plain telephone carrier is typically a conduit and falls outside BAA requirements. A video platform, scheduling tool, transcription service, or cloud storage provider that creates, receives, maintains, or transmits ePHI on your behalf is a business associate, and you need a signed BAA before that vendor touches patient data.
Work through vendor relationships with a consistent process:
- Identify every tool in your telehealth workflow that could touch ePHI, including scheduling, messaging, video, and any AI transcription add-on.
- Determine whether each vendor is a conduit or a business associate based on what it actually does with the data, not its marketing label.
- Confirm a signed BAA exists for every business associate, covering permitted uses, security obligations, and breach notification timelines.
- Verify the BAA addresses subcontractor flow-down, since many platforms rely on hosting or infrastructure partners of their own.
- Request evidence of secure configuration: a recent penetration test summary, a SOC 2 report, or equivalent documentation where available.
- Ask vendors directly how they handle breach notification timing and what data they retain after a contract ends.
A structured BAA review checklist helps compliance officers catch gaps before OCR does, particularly around subcontractor obligations that get missed in standard templates.
Telehealth-focused risk analysis, policies, training, and incident response
A generic HIPAA risk analysis misses telehealth-specific exposure. According to HHS risk analysis guidance, there’s no single mandated format, but the assessment has to be thorough and scoped to your actual environment, including video communications, recordings, third-party integrations, and remote device data flows.
- Scope the analysis to cover every channel where ePHI moves: live video, chat, file sharing, recordings, and any API integration with your EHR.
- Document remediation priorities in order of risk, not in the order they’re easiest to fix.
- Update written policies to reflect what the analysis found, and schedule a review date rather than letting policies sit indefinitely.
- Train staff on telehealth-specific scenarios: what to do if a session disconnects mid-visit, how to verify patient identity remotely, and how to report a suspected incident.
- Keep signed training completion records on file, since this is one of the first items auditors request.
Incident response for telehealth needs its own runbook. Contain the exposure first, whether that means disabling an account or isolating a device. Preserve logs and session data for forensics before anything gets overwritten. Notify per your documented timeline, and prepare the OCR report if the breach assessment doesn’t support a low-probability finding.
Pro Tip: Run a tabletop exercise simulating a telehealth-specific incident, like a clinician’s device being lost mid-shift, at least once a year. Documentation of that exercise counts as evidence of a tested policy.

HHS guidance materials note that a documented risk analysis and tested written policies are treated favorably in OCR investigations, which makes this section less of a formality and more of a direct liability reducer.
Consent, recordings, documentation, and retention rules for telehealth encounters
Every telehealth encounter needs a documentation trail that holds up under audit. Capture patient consent before or at the start of the visit, and record how identity was verified, what modality was used, and what device the patient connected from.
- Log session metadata for each encounter: identity verification method, platform used, device type, and start and end timestamps.
- Decide in advance whether recording is required, optional, or prohibited for each visit type, and document that policy rather than leaving it to clinician discretion.
- Store any recordings or transcripts with the same access controls applied to the rest of your ePHI, not in a separate, less-monitored system.
- Set a retention period for recordings and session logs that matches your audit and legal requirements, and apply it consistently.
Transcription and AI-assisted documentation tools add another layer worth checking, since some AI-enabled healthcare solutions handle recordings and transcripts as part of the clinical workflow, and those tools need the same BAA and access-control scrutiny as any other business associate.
CMS, licensure, and operational issues that affect telehealth HIPAA compliance
CMS guidance intersects with HIPAA obligations in ways that affect your documentation and billing decisions, not just your privacy program.
- The CMS Medicare telemedicine fact sheet confirms patient consent is required for telehealth services and that CMS defers to state law for licensure, meaning you need to verify compliance in the state where the patient is physically located, not just where your practice is based.
- Telehealth-eligible billing codes change from year to year, and CMS 2026 eCQM guidance notes that providers should verify current code eligibility before submitting for quality reporting.
- Documentation decisions tied to billing, including which codes qualify for telehealth delivery, should align with the consent and identity-verification records you’re already keeping for HIPAA purposes.
How CoreWorx operationalizes telehealth compliance fixes
Turning a risk analysis into working safeguards is where most practices stall. We built our Discovery Audit specifically to close that gap: a structured review that produces a prioritized list of technical and policy gaps rather than a generic report that sits in a drawer.
- A gap list scored by risk, matched against Security Rule requirements and your actual telehealth workflow.
- A remediation roadmap that sequences fixes, from quick wins like MFA rollout to larger platform changes.
- Policy and BAA review templates adapted to the vendors you actually use.
- A path from audit to build: once gaps are prioritized, we move directly into secure implementation.
Our HIPAA-compliant patient portal case study shows how that audit-to-build path plays out for a practice moving from a fragmented setup to a documented, access-controlled system.
What most practices get wrong about telehealth compliance
Most compliance gaps I’ve seen traced back to two things: nobody updated the BAA when the vendor changed its product, and session logs existed but nobody could actually produce them when asked. Encryption and MFA get attention because they’re visible. Documentation discipline doesn’t, and it’s the thing OCR actually reviews first during an investigation.
The quickest wins are rarely technical. They’re contractual and procedural: re-reading your BAAs after a vendor update, confirming logs are retained long enough to matter, and writing down the risk assessment you already did in your head. A platform without paperwork behind it looks the same to an auditor as no platform at all.
— Cameron
Get your telehealth systems audit-ready with CoreWorx
Closing the gaps covered above usually takes more than a checklist. Our team runs a Discovery Audit, a one-time engagement that maps your telehealth workflow against Security Rule requirements and hands you a prioritized remediation list instead of a stack of findings with no next step.

From there, we build the fix:
- A HIPAA-compliant patient portal or telehealth integration, scoped and priced through our custom software guide.
- Managed AI agent support for documentation or intake workflows, starting at $1,500 per month through our managed agents plan.
- Full-service builds spanning web, mobile, and cloud integration through our service lineup.
If you’re not sure where your telehealth setup stands, start with the audit. It’s the fastest way to know exactly what needs fixing before an investigation forces the question.
This article is general information, not a substitute for advice from a qualified lawyer. Consult a qualified legal professional about your own circumstances before acting on anything here.
FAQ
What does HIPAA compliant mean in healthcare?
Being HIPAA compliant means a covered entity or business associate meets the requirements of the Privacy, Security, and Breach Notification Rules for any protected health information it handles. In telehealth, that includes signed BAAs with relevant vendors, documented risk analyses, and technical safeguards like encryption and access controls, as outlined by HHS.gov.
Did Congress extend telehealth in 2026?
Telehealth billing and coverage flexibilities under Medicare have been subject to periodic extensions, and eligible codes can change from year to year according to CMS eCQM guidance. Providers should verify current code eligibility directly with CMS rather than relying on a prior year’s list.
Is Zoom compliant with HIPAA?
Whether any video platform supports HIPAA compliance depends on the plan, configuration, and whether a signed business associate agreement is in place, not the brand name alone. The safeguards that matter, including encryption, access controls, and a BAA covering the vendor’s handling of ePHI, are detailed in the HIPAA Security Rule overview.
What video conferencing is HIPAA compliant?
No video platform is inherently HIPAA compliant on its own. Compliance depends on configuring encryption and access controls correctly, securing a BAA with the vendor as a business associate, and documenting that setup as part of your Security Rule safeguards, per HHS.gov.