HIPAA Compliance by Vertical

HIPAA Compliance for Patient Engagement Platforms

HIPAA for patient engagement SaaS: reminders, two-way messaging, intake and surveys sent for providers, plus tracking pixels and subcontractor BAAs.

Key takeaways

  • PHI in scope: Appointment reminders and two-way patient messages, Digital intake forms, consents, and surveys, Patient contact details linked to a provider relationship, Campaign and engagement data tied to identifiable patients.
  • Start with these controls: Subcontractor BAAs with every SMS, email, forms, and analytics vendor that handles PHI; No third-party tracking pixels on patient-facing pages without a BAA or authorization; Minimum-necessary message templates by default.
  • The most common mistake: Advertising or analytics pixels on patient-facing pages with no 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

  • Appointment reminders and two-way patient messages
  • Digital intake forms, consents, and surveys
  • Patient contact details linked to a provider relationship
  • Campaign and engagement data tied to identifiable patients
  • EHR data synced to personalize outreach

Common compliance pain points

  • Messaging on the provider's behalf: Reminders and messages you send for a covered entity make you its business associate. HIPAA permits reminders by text and email, and providers may send unencrypted messages to patients who prefer them after warning them of the risk. Your product should make minimum-necessary templates the default and record each patient's preference.
  • Tracking technologies: Analytics and advertising pixels on patient-facing pages can disclose PHI to third parties. A federal court vacated part of HHS's guidance on online tracking technologies in June 2024 (American Hospital Association v. Becerra, N.D. Tex.), but disclosing PHI to a tracking vendor without a BAA or the patient's authorization is still a HIPAA problem. Audit what runs on your patient-facing pages.
  • Marketing versus care communications: Treatment reminders and care communications are permitted, but marketing communications that use PHI generally need the patient's written authorization under 45 CFR 164.508. Campaign features should let customers keep the two apart.
  • Subcontractor sprawl: SMS gateways, email providers, form builders, and analytics tools each see patient data. Every one that handles PHI on your behalf is a subcontractor business associate and needs a BAA, and provider customers will ask for the list.

Priority controls

  • Subcontractor BAAs with every SMS, email, forms, and analytics vendor that handles PHI
  • No third-party tracking pixels on patient-facing pages without a BAA or authorization
  • Minimum-necessary message templates by default
  • A record of each patient's communication preference and any risk warning given
  • An authorization step for marketing campaigns that use PHI
  • A HIPAA Security Rule risk analysis covering messaging and intake data

Common mistakes

  • Advertising or analytics pixels on patient-facing pages with no BAA
  • An SMS or email provider handling PHI without a subcontractor BAA
  • Reminder templates that name the procedure or condition
  • Marketing campaigns sent to patients using PHI without authorization
  • No record of patient communication preferences

Enforcement context

Since the 2013 Omnibus Rule, business associates are directly liable for Security Rule compliance and for uses and disclosures their BAAs do not permit. Online tracking has drawn regulator attention: in July 2023 HHS and the FTC jointly warned hospital systems and telehealth providers about the privacy risks of tracking technologies. HHS's January 2025 Security Rule proposal (90 FR 898) would add more prescriptive technical requirements if finalized; it is a proposal, not current law.

Frequently asked questions

What PHI do patient engagement platform organizations handle?

Appointment reminders and two-way patient messages; Digital intake forms, consents, and surveys; Patient contact details linked to a provider relationship; Campaign and engagement data tied to identifiable patients; EHR data synced to personalize outreach. 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 patient engagement platform?

Subcontractor BAAs with every SMS, email, forms, and analytics vendor that handles PHI; No third-party tracking pixels on patient-facing pages without a BAA or authorization; Minimum-necessary message templates by default; A record of each patient's communication preference and any risk warning given; An authorization step for marketing campaigns that use PHI; A HIPAA Security Rule risk analysis covering messaging and intake data.

What are the most common HIPAA mistakes in patient engagement platform?

Advertising or analytics pixels on patient-facing pages with no BAA; An SMS or email provider handling PHI without a subcontractor BAA; Reminder templates that name the procedure or condition; Marketing campaigns sent to patients using PHI without authorization; No record of patient communication preferences.

What does HIPAA enforcement look like for patient engagement platform?

Since the 2013 Omnibus Rule, business associates are directly liable for Security Rule compliance and for uses and disclosures their BAAs do not permit. Online tracking has drawn regulator attention: in July 2023 HHS and the FTC jointly warned hospital systems and telehealth providers about the privacy risks of tracking technologies. HHS's January 2025 Security Rule proposal (90 FR 898) would add more prescriptive technical requirements if finalized; it is a proposal, not current law.