Skip to main content
Patient Protect circular logo mark in purple and white used for site navigationPatient Protect

HIPAA Compliance for Telehealth Clinicians

The HIPAA compliance and security operating system for telehealth practices. Remote care spreads the clinical environment across platforms, home offices, personal devices, recordings, and multiple states — and a signed platform BAA covers none of it. Patient Protect runs the risk analysis across that whole footprint, sets remote-work policy, trains the workforce, and keeps the evidence.

What HIPAA actually looks like for telehealth clinicians.

The regulatory framework, the enforcement patterns OCR has historically cited, the non-HIPAA standards that apply, the gaps audits routinely surface, and the record-retention overlay — HIPAA’s six-year rule for compliance documentation, and the separate state law that governs how long clinical records must be kept.

Regulatory framework

Telehealth practices operate under HIPAA as covered entities through standard electronic transactions, with specific overlays from the DEA's telemedicine final rule (effective 2026 post-PHE), state-by-state telehealth licensure compacts (IMLC for medical, PSYPACT for psychology, ASLP-IC for SLP/audiology, others), and state-specific telehealth practice rules. The post-PHE landscape restored most pre-pandemic prescribing limits with specific telehealth-permitted exceptions. State medical boards govern licensure and practice standards; state pharmacy boards govern e-prescribing requirements; state insurance commissioners govern parity-of-coverage rules for telehealth services.

OCR enforcement patterns

OCR's telehealth enforcement record has expanded as the post-PHE landscape took shape. Recurring patterns include disclosure errors when a telehealth platform is shared across multiple covered entities, recording without consent, audio-only services used outside permitted scenarios, and missing in-person evaluation for controlled-substance prescribing where DEA rules require it. The FTC's BetterHelp settlement and GoodRx settlement (both 2023) under the Health Breach Notification Rule signaled regulatory attention on telehealth and consumer-health data sharing that complements HIPAA enforcement.

Standards beyond HIPAA

DEA EPCS for any controlled-substance prescribing. The DEA telemedicine final rule and its specific exceptions (one-day supply, etc.). State telehealth licensure compacts. Audio-only restrictions in many state telehealth frameworks. State-specific consent requirements for telehealth visits. CMS reimbursement rules for telehealth services post-PHE. State controlled-substance e-prescribing requirements that may exceed federal DEA minimums.

Common compliance gaps

Common in telehealth compliance reviews: licensure-state mismatch where the patient's state of residence differs from the prescriber's licensure state, audio-only services used outside permitted DEA or state framework, recording-of-visits without clear consent infrastructure, missing in-person evaluation for controlled-substance prescribing, multi-state breach notification matrix not pre-built, telehealth platform BAA assumed but not verified, and inadequate identity verification at the start of clinical encounters.

Compliance documentation, then state record law.

HIPAA's six-year rule governs compliance documentation, not clinical records (§164.530(j)). State law governs patient record retention, and telehealth-specific rules vary widely. DEA EPCS retention requirements are separate and longer for controlled-substance prescribing audit trails (typically two to five years depending on rule). State medical boards may require longer retention for telehealth visits than for in-person visits in some jurisdictions. Multi-state telehealth operations face the highest retention floor of any operating jurisdiction's law.

Reference summary, not legal advice. This page summarizes how HIPAA and adjacent regulatory frameworks apply to telehealth clinicians based on Patient Protect’s reading of the relevant CFR provisions, OCR enforcement record, and state statutes. Operators with specific compliance questions should consult a qualified HIPAA attorney. Patient Protect is a HIPAA compliance platform; we are not a law firm and do not provide legal advice.

Where telehealth clinicians are most exposed.

Your telehealth platform vendor may not cover you

Zoom, Doxy.me, SimplePractice, Spruce — a signed BAA is mandatory, but most clinicians never verify encryption settings, recording storage locations, or session metadata handling. The COVID-era enforcement discretion has ended, so those configuration decisions now sit squarely inside the practice's own Security Rule obligations.

Home offices and personal devices are uncontrolled environments

Clinicians conducting sessions from home laptops, tablets, and personal phones introduce risks no brick-and-mortar practice faces. Shared family devices, unencrypted Wi-Fi, screen visibility to household members — each is a potential breach vector OCR evaluates during audits.

Session recordings and chat logs create long-lived ePHI

Recorded telehealth sessions, chat transcripts, and asynchronous messages are ePHI that must be encrypted at rest, access-controlled, and retained per your retention policy. Many clinicians store recordings in consumer cloud storage with no BAA and no access audit trail.

Multi-state practice multiplies regulatory exposure

Telehealth clinicians often serve patients across state lines. Each state may layer additional privacy requirements on top of federal HIPAA. A single compliance gap doesn't just affect one jurisdiction — it can trigger enforcement actions in every state where you treat patients.

Built for telehealth clinicians, not hospital systems.

Telehealth-specific risk assessment

SRA wizard covers video platform security, remote device policies, session recording storage, and cross-state practice — not a generic in-office questionnaire repurposed for virtual care.

Platform vendor BAA tracking

Track BAAs with Zoom, Doxy.me, SimplePractice, scheduling tools, payment processors, and every other vendor in your telehealth stack. Expiration alerts and e-sign built in.

Secure patient messaging

Replace personal texts, email, and consumer chat apps with BAA-gated messaging. Patient communication stays inside your compliance perimeter — no matter where you're practicing from.

Remote work policy templates

Pre-built policies for home office security, BYOD device management, and remote session protocols. Customize for your practice and document workforce acknowledgment automatically.

Multi-state licensure and breach notification matrix

Telehealth operations across 30+ states face a state-by-state matrix of licensure compacts, breach notification timelines, and AG-notification thresholds. The platform pre-loads each state's requirements; the alternative is reading 50 statutes after an incident with the timeline already running.

Post-PHE controlled substance prescribing compliance

The DEA's telemedicine final rule (effective 2026) restored most pre-PHE prescribing limits with specific telehealth-permitted exceptions. Patient Protect tracks prescriber-by-prescriber compliance with the registration, in-person evaluation, and audit-trail requirements that controlled-substance telehealth now requires.

State-specific HIPAA rules for telehealth clinicians.

HIPAA is federal — but your state layers additional breach notification deadlines, AG reporting requirements, and privacy laws on top. Select your state to see what applies to your practice.

District of Columbia compliance requirements for telehealth clinicians

In addition to federal HIPAA requirements, telehealth clinicians operating in District of Columbia must comply with the following state-specific obligations.

Breach notification deadline

In the most expedient time possible and without unreasonable delay, subject to the needs of law enforcement and any measures necessary to determine the scope of the breach and restore the reasonable integrity of the data system.

The statute does not fix a numeric outer bound. Unreasonable delay is itself a violation and may result in state enforcement action, so treat the operative timeframe as the shortest window your incident circumstances reasonably support.

Attorney General notification

Required for all breaches

Your practice must notify the state AG in addition to affected patients and HHS.

District of Columbia-specific laws & requirements

DC uses the New-York pattern: HIPAA covers individual notice, but AG notice is independent

For HIPAA-regulated entities operating in DC, satisfying HIPAA breach-notification obligations to individuals is deemed to satisfy the § 28-3852 individual-notice requirement under subsection (g). But the separate DC Attorney General notification obligation under § 28-3852(b-1) is triggered independently once a breach affects 50 or more DC residents, and HIPAA compliance does not substitute for that AG notice. Practices notifying HHS under HIPAA still owe a separate written AG notice to DC.

Source: D.C. Code § 28-3852(a)

Verified against primary state authority as of August 2026. General reference — consult legal counsel for your specific obligations.

Primary sources: code.dccouncil.gov · oag.dc.gov

What happens after the paperwork is done.

Every major compliance platform covers risk assessments and policy templates. This is the part that differs.

What to ask

Patient Protect

01

Risk assessment that satisfies §164.308(a)(1)

A readiness quiz is not a risk analysis.

Full SRA wizard mapped to NIST CSF with live scoring

02

Auto-generated policies with workforce acknowledgment

HIPAA requires documented proof your staff reviewed them.

48 policies from your risk profile, versioned acknowledgment

03

Staff training with delivery tracking

§164.308(a)(5) — sending a PDF is not sufficient.

HIPAA Foundations — 19 modules, 95 assessment questions, verifiable certificates

04

Full BAA lifecycle management

Expired BAAs are a top enforcement target.

E-signature, renewal alerts, Vendor Risk Scanner

Yes on all 10. Now run the checklist on the rest.

From $39/mo · No long-term contracts.

Enterprise-grade compliance. Independent-practice pricing.

No contracts · No setup fees · Cancel anytime

Basic

$39/mo

Risk assessments, policies, BAA management, training, and compliance scoring.

Recommended

Pro

$99/mo

Everything in Basic plus secure messaging, breach intelligence, live diagnostics, and AI compliance assistant.

See full feature comparison →

Common questions about HIPAA compliance for telehealth clinicians.

Is telehealth subject to HIPAA?

Yes — if the practice is a covered entity. Telehealth does not change the covered-entity test, and once the practice is covered, the full Security Rule, Privacy Rule, and Breach Notification Rule apply to remote care exactly as they do in person. The COVID-era enforcement discretion has ended, so the transitional allowances that once covered consumer video tools no longer apply.

What telehealth platforms are HIPAA compliant?

A platform is HIPAA compliant only if it offers a signed BAA, end-to-end encryption, and proper access controls. Zoom (healthcare plan), Doxy.me, and several EHR-integrated platforms offer BAAs — but compliance also depends on how you configure and use them. Patient Protect's risk assessment evaluates your actual setup, not just the vendor's marketing claims.

Can I use my personal phone or laptop for telehealth?

You can, but only with proper safeguards — full-disk encryption, passcode lock, separate user profiles, and documented BYOD policies. OCR evaluates whether personal devices used for clinical care meet the same security standards as dedicated clinical systems. Patient Protect includes remote device policy templates and training modules for exactly this scenario.

What does HIPAA compliance cost for a telehealth practice?

Traditional compliance consultants charge $4,000–$10,000 per year for telehealth practices, often more for multi-state providers. Patient Protect starts at $39/month ($468/year) with no contracts — covering risk assessments, platform BAA tracking, remote work policies, staff training, and continuous compliance monitoring.

Are audio-only telehealth visits HIPAA-compliant?

Audio-only telehealth (telephone-only) is permitted under HIPAA when the practice has appropriate safeguards — the call must occur on a HIPAA-compliant infrastructure, identity verification must occur before clinical content, and PHI must not be left on insecure voicemail systems. CMS extended audio-only Medicare reimbursement post-PHE for behavioral health and limited other categories; the HIPAA framework applies regardless of reimbursement category.

Does HIPAA require video for telehealth visits?

No. HIPAA is technology-agnostic — it requires safeguards proportionate to the risk, not specific media. Many state telehealth licensure frameworks require video for specific service types (controlled-substance prescribing, certain mental health services), but that's a state-law requirement layered on top of HIPAA, not a HIPAA requirement itself.

How do multi-state telehealth operations handle breach notification?

Each state where the breach affects residents has its own notification timeline, AG-notification threshold, and required disclosure content. A breach affecting residents of 30 states triggers 30 different notification clocks the moment it's detected. The practical implication: pre-load every operating-state's requirements into the breach response protocol so the response can ship parallel notifications rather than sequential ones.

Does a telehealth practice have to complete a HIPAA Security Risk Analysis?

Yes, and telehealth does not narrow the scope — it widens it. Every covered practice must conduct and document an accurate, thorough assessment of the risks affecting all its ePHI. For telehealth that means the platform and its configuration, administrative access, waiting-room controls, chat, metadata, and recording features; every clinician device, home network, and physical privacy condition; the EHR, intake, scheduling, portal, e-prescribing, and billing systems; session recordings, transcripts, and uploaded documents; and remote onboarding, device loss, account compromise, and termination. A signed platform BAA covers none of this — it is a contract, not an analysis.

Which of our telehealth vendors need Business Associate Agreements?

Any organization maintaining or transmitting ePHI for the practice: the telehealth platform itself, the EHR, scheduling and intake tools, patient messaging, e-prescribing service, transcription and recording storage, cloud storage and backup, billing service, and any subcontractor those vendors use. The platform is necessary but not sufficient — a signed platform BAA does not configure the platform, secure the clinician's device, control where recordings are stored, train the workforce, or complete the SRA. Payers, laboratories performing tests, and other treating clinicians involved in a patient's care are not business associates.

What are we responsible for in a clinician's home office?

All of it, from HIPAA's perspective. The home office is a location where the practice creates and maintains ePHI, so it belongs in the risk analysis and needs written standards the same way a clinic room would: a lockable or private space where sessions cannot be overheard, a screen not visible to household members, a secured home network rather than an open one, encrypted devices with automatic screen lock, a rule against shared family computers and accounts, headphone use, and a documented procedure for device loss. The uncomfortable part for most practices is that this requires telling clinicians how to arrange a room in their own home — which is exactly why it needs to be written policy rather than an assumption.

Is the government's Security Risk Assessment Tool mandatory?

No. The government's SRA Tool is one method designed to help small and medium-sized organizations perform the required analysis. HIPAA requires the underlying risk analysis — not the use of one particular tool. Patient Protect provides its own guided SRA and connects the findings directly to remediation, policies, tasks, and documentation.

Does our EHR make the practice HIPAA compliant?

No. An EHR may provide important safeguards for the records it maintains, but it does not conduct the practice's complete SRA, remediate every identified risk, train the workforce, manage all policies, identify every Business Associate, prepare the practice for incidents, or preserve the full body of compliance evidence.

How much does Patient Protect cost for a telehealth practice?

Patient Protect Basic costs $39 per office per month and includes up to 25 personnel. It includes the guided Security Risk Analysis, risk management, policies, workforce training, workforce and vendor management, BAA tracking, compliance scoring, and centralized documentation needed to operate the practice's core HIPAA compliance program.

Patient Protect is intuitive, proactive, and affordable — exactly what small clinics like ours need to keep patient data safe and stay on the right side of HIPAA.
Dr. Thomas E Murray, D.D.S.Patient Protect Member Since 2017

Your telehealth practice has compliance gaps beyond what your platform covers.

See your real exposure in five minutes. Free risk assessment — no login required.

Or explore the full HIPAA compliance software comparison or all HIPAA compliance solutions