Skip to content
HIPAA ComplianceConsulting

Industry: Telemedicine

HIPAA Compliance Consulting for Telemedicine and Telehealth

Telehealth organizations range from provider groups to pure technology platforms. Your HIPAA obligations depend on which one you are — and many companies are both.

Reviewed Request a HIPAA Consultation

Telemedicine is not one business model. A virtual-first medical group employing clinicians, a software platform licensed to hospitals and a direct-to-consumer app connecting patients with affiliated physicians can look similar to a patient, but they hold very different positions under HIPAA. The first question in any telehealth engagement is who the covered entity is, because every other obligation follows from that.

Telehealth also lost a safety net in 2023. During the COVID-19 public health emergency, OCR announced it would not penalize good-faith use of non-public-facing communication tools that did not otherwise meet HIPAA requirements. That enforcement discretion is over, and organizations that adopted tools under it should have revisited those choices.

Your HIPAA role depends on your model

Typical HIPAA roles in telehealth arrangements (actual role depends on contracts and facts)
ModelUsual HIPAA roleWhat that means in practice
Virtual medical or behavioral health group that bills insuranceCovered entityFull Privacy, Security and Breach Notification Rule obligations, plus BAAs with its technology vendors
Telehealth software licensed to hospitals or practicesBusiness associateDirect Security Rule liability, BAA terms with each customer, subcontractor BAAs with hosting and messaging vendors
Direct-to-consumer company with an affiliated professional corporationOften both: the PC is a covered entity; the management company is frequently its business associateResponsibilities must be mapped across the entities and reflected in agreements and policies
Consumer wellness app not acting for a covered entityOften neitherHIPAA may not apply, but the FTC Health Breach Notification Rule, FTC Act and state consumer health laws may

The end of OCR’s COVID-19 telehealth discretion

In practice, we still find remnants of the pandemic period: clinicians using personal messaging accounts, consumer video tools with no BAA, or session recordings saved to personal cloud drives. A post-pandemic inventory of tools in use, as opposed to tools officially approved, is usually the fastest way to find them.

Telehealth data flows to map

  • Video and audio sessions: where streams are routed, whether sessions are recorded, where recordings are stored and for how long.
  • Asynchronous messaging and photo uploads: storage locations, retention and who on the clinical team can see them.
  • Intake questionnaires and identity verification: third-party form builders and ID verification vendors frequently need BAAs.
  • e-Prescribing and lab ordering integrations, which send PHI to pharmacies and labs as treatment disclosures.
  • Marketing websites and apps: tracking pixels, session replay and analytics SDKs on pages where users book care or describe symptoms.
  • Clinician endpoints: home offices, personal devices and shared household networks.

Key regulatory considerations

Transmission security and access control

The Security Rule’s transmission security standard (§164.312(e)) and access control standard (§164.312(a)) apply to every session and message. Encryption in transit is an addressable specification, but for internet-based telehealth it is very difficult to justify not implementing it.

Online tracking technologies

OCR has issued guidance on tracking technologies on websites and apps used by covered entities and business associates. A federal court vacated part of that guidance in 2024, so its current scope should be confirmed with counsel. Regardless, sending identifiable health information to an analytics or advertising vendor without a permitted basis or BAA creates real risk.

State law

Telehealth crosses state lines by design. Several states have consumer health data or medical confidentiality laws that may apply alongside HIPAA. Requirements vary, so map where your patients are and confirm applicable laws with qualified legal counsel.

Common challenges for telehealth companies

  • Unclear division of responsibility between a management company and an affiliated professional corporation.
  • Engineering teams moving faster than BAAs: a new messaging, transcription or AI vendor integrated before anyone checked the contract.
  • Recordings and transcripts retained indefinitely by default.
  • Customer security questionnaires from health systems that the company cannot answer with evidence.

How we tailor a telemedicine engagement

We usually begin by documenting the entity structure and data flows, then run a HIPAA security risk assessment across the platform, cloud infrastructure and clinician endpoints. Platform companies often need HIPAA cloud compliance consulting to clarify shared-responsibility boundaries with their hosting providers, and a review of vendor and customer agreements through our business associate compliance work.

Provider-side organizations tend to need more emphasis on Privacy Rule workflows and clinician guidance. Our guide to HIPAA compliance for telehealth covers the operational side in more depth.

A BAA is the start of platform due diligence, not the end

A signed BAA tells you a video or messaging vendor accepts business associate obligations. It does not tell you whether the product is configured safely for your workflows. When we review a telehealth platform with a client, we look at the settings that determine real exposure.

  • Meeting links and waiting rooms: whether links are unique per visit and whether clinicians admit patients individually.
  • Recording and transcription defaults: whether they are off unless deliberately enabled, and where outputs are stored.
  • Administrative roles: who can change organization-wide settings, export data or add integrations.
  • Audit logs: whether session, access and administrative events are logged and available to you, and for how long.
  • Data location and retention: how long chat, files and recordings persist after the visit and whether you can delete them.
  • Integrations: what the platform sends to your EHR, scheduling and analytics tools, and whether each recipient is covered by an agreement.

Starting checklist for telehealth organizations

  1. 1

    Name the covered entity

    Document which legal entity furnishes care and bills, and which entities act as its business associates.

  2. 2

    Inventory tools actually in use

    Survey clinicians and staff for messaging, video and file-sharing tools, including anything adopted during the pandemic.

  3. 3

    Match tools to BAAs

    Confirm a BAA for every vendor that touches PHI, including transcription, AI scribe, form and ID verification vendors.

  4. 4

    Audit tracking on patient-facing pages

    Identify pixels and SDKs on booking, intake and symptom pages and decide with counsel what should be removed or contracted.

  5. 5

    Set recording and retention rules

    Decide whether sessions are recorded at all, where recordings live and when they are deleted.

Frequently asked questions

Can we still use video tools that won’t sign a BAA?

Not for sessions involving PHI if you are a covered entity or business associate. OCR’s COVID-era enforcement discretion ended in 2023, and vendors that create, receive, maintain or transmit PHI on your behalf need a BAA.

We only build the software. Are we a covered entity?

Usually not. A platform that handles PHI on behalf of providers is typically a business associate, which carries direct liability under the Security Rule and certain Privacy Rule provisions. If you also employ or contract clinicians who bill, the analysis changes.

Does HIPAA apply to our direct-to-consumer wellness app?

Not necessarily. If you are not a covered entity and are not acting on behalf of one, HIPAA may not apply, but the FTC Health Breach Notification Rule and state consumer health privacy laws might. That determination should be confirmed with counsel.

Is encryption required for telehealth video?

Encryption in transit is addressable under §164.312(e)(2)(ii), which means you must implement it if reasonable and appropriate or document an equivalent alternative. For internet-based video, implementing it is the norm.

Authoritative sources

This page is general information, not legal advice. Regulations and guidance change; confirm current requirements with the official sources above and, where needed, qualified legal counsel.

Talk through your HIPAA obligations with a consultant

Tell us about your organization, how you handle patient information, and what’s prompting the review. We’ll suggest a practical scope — and tell you if you don’t need us.