HIPAA Compliance by Vertical

HIPAA Compliance for Telehealth Platforms

HIPAA compliance for telehealth platforms — video PHI, asynchronous messaging, state privacy laws, and enforcement after the COVID-19 public health emergency.

Key takeaways

  • PHI in scope: Video and audio recordings of clinical encounters, Asynchronous chat and store-and-forward messaging, Connected device data (remote patient monitoring), Provider notes synchronized to the EHR.
  • Start with these controls: Encryption of video and messaging in transit and of stored recordings at rest (addressable under the current Security Rule; implement it or document an equivalent alternative); BAA with the video platform vendor (for example, Zoom for Healthcare or Doxy.me); BAA with every AI scribe and transcription vendor.
  • The most common mistake: Using a consumer video account instead of a healthcare plan covered by a BAA
  • A signed BAA is required with every vendor that creates, receives, maintains, or transmits PHI on your behalf, and no tool is HIPAA compliant on its own.

PHI handled in this environment

  • Video and audio recordings of clinical encounters
  • Asynchronous chat and store-and-forward messaging
  • Connected device data (remote patient monitoring)
  • Provider notes synchronized to the EHR
  • Patient-uploaded photos and documents

Common compliance pain points

  • Recording and retention defaults: Some video platforms can record sessions by default. Every recording is PHI that has to be secured, retained according to your policy, and eventually destroyed. Decide up front whether you record at all, configure platform defaults to match, and document the decision.
  • State privacy laws on top of HIPAA: HIPAA sets a federal floor. State laws, such as the California Confidentiality of Medical Information Act and the Texas Medical Records Privacy Act, can add requirements, and state law that is more protective of privacy is not preempted. Telehealth that serves patients in several states needs to know which state laws apply to each patient.
  • Patients who ask for unencrypted email or text: HHS guidance allows providers to communicate by unencrypted email or text when the patient prefers it, after warning the patient of the risk. Record the warning and the patient's preference so the decision can be shown later.
  • Third-party scribes and transcription: AI scribes and transcription services receive full clinical encounters. A vendor that creates, receives, maintains, or transmits that PHI on your behalf is a business associate and needs a signed BAA, and its own subcontractors need BAAs with it.

Priority controls

  • Encryption of video and messaging in transit and of stored recordings at rest (addressable under the current Security Rule; implement it or document an equivalent alternative)
  • BAA with the video platform vendor (for example, Zoom for Healthcare or Doxy.me)
  • BAA with every AI scribe and transcription vendor
  • Documented retention policy with platform defaults aligned to it
  • Documented risk warning and patient preference for unencrypted email or text
  • A record of which state privacy laws apply to the patients you serve

Common mistakes

  • Using a consumer video account instead of a healthcare plan covered by a BAA
  • Recording sessions by default with no retention policy or destruction workflow
  • AI scribe vendor in production without a signed BAA
  • Texting or emailing PHI unencrypted without warning the patient and recording their preference
  • Not checking that vendor BAAs require breach notice to you quickly enough to meet your own 60-day outer limit for notifying patients

Enforcement context

During the COVID-19 public health emergency, OCR exercised enforcement discretion for good-faith telehealth using non-public-facing video tools. That discretion ended when the emergency expired on May 11, 2023, with a transition period that ran to August 9, 2023, so the ordinary HIPAA rules now apply to every telehealth session. Separately, HHS proposed a major Security Rule update in January 2025 (90 FR 898) that would, if finalized, require MFA and encryption with limited exceptions. It is a proposal, not current law.

Frequently asked questions

What PHI do telehealth organizations handle?

Video and audio recordings of clinical encounters; Asynchronous chat and store-and-forward messaging; Connected device data (remote patient monitoring); Provider notes synchronized to the EHR; Patient-uploaded photos and documents. Any of these, combined with an identifier, is protected health information when a covered entity or business associate holds it, and in electronic form it brings the Security Rule into scope.

What are the priority HIPAA controls for telehealth?

Encryption of video and messaging in transit and of stored recordings at rest (addressable under the current Security Rule; implement it or document an equivalent alternative); BAA with the video platform vendor (for example, Zoom for Healthcare or Doxy.me); BAA with every AI scribe and transcription vendor; Documented retention policy with platform defaults aligned to it; Documented risk warning and patient preference for unencrypted email or text; A record of which state privacy laws apply to the patients you serve.

What are the most common HIPAA mistakes in telehealth?

Using a consumer video account instead of a healthcare plan covered by a BAA; Recording sessions by default with no retention policy or destruction workflow; AI scribe vendor in production without a signed BAA; Texting or emailing PHI unencrypted without warning the patient and recording their preference; Not checking that vendor BAAs require breach notice to you quickly enough to meet your own 60-day outer limit for notifying patients.

What does HIPAA enforcement look like for telehealth?

During the COVID-19 public health emergency, OCR exercised enforcement discretion for good-faith telehealth using non-public-facing video tools. That discretion ended when the emergency expired on May 11, 2023, with a transition period that ran to August 9, 2023, so the ordinary HIPAA rules now apply to every telehealth session. Separately, HHS proposed a major Security Rule update in January 2025 (90 FR 898) that would, if finalized, require MFA and encryption with limited exceptions. It is a proposal, not current law.