Is Texting Patient Information a HIPAA Violation? Requirements and Examples

Check out the new compliance progress tracker


Product Pricing Demo Video Free HIPAA Training
LATEST
video thumbnail
Admin Dashboard Walkthrough Jake guides you step-by-step through the process of achieving HIPAA compliance
Ready to get started? Book a demo with our team
Talk to an expert

Is Texting Patient Information a HIPAA Violation? Requirements and Examples

Kevin Henry

HIPAA

March 27, 2024

7 minutes read
Share this article
Is Texting Patient Information a HIPAA Violation? Requirements and Examples

Texting Patient Information and HIPAA Compliance

Texting patient information is not automatically a HIPAA violation. HIPAA permits electronic communications so long as you implement appropriate HIPAA safeguards that protect the confidentiality, integrity, and availability of electronic protected health information (ePHI). In practice, that means you must control who can access messages, how they are secured, and how they are monitored and retained.

Because standard SMS/MMS lacks modern security controls, you should not use it to transmit ePHI. Instead, use secure messaging platforms that meet encryption requirements, support audit trail compliance, and allow you to enforce policies consistently across devices and users.

What turns a text into ePHI

  • Identifiers about a person (name, phone number, email, address, DOB, photos, or medical record numbers)
  • Combined with health information (symptoms, diagnoses, test results, medications, appointments at specialty clinics)
  • Any message that can reasonably identify an individual and relates to health care or payment

Compliance building blocks

  • Administrative: policies, training, sanctions, risk analysis procedures, and Business Associate Agreements with vendors that handle messages
  • Technical: strong authentication, access controls, encryption in transit and at rest, and detailed logging for audit trail compliance
  • Physical: managed devices, screen locks, and procedures for lost or stolen phones

If you rely on a third‑party messaging solution, obtain a Business Associate Agreement (BAA) that covers how the vendor protects ePHI, supports incident response, and returns or destroys data on termination.

Risks of Texting Patient Information

Traditional texting exposes ePHI to unauthorized access risks that are difficult to mitigate. Messages may be stored unencrypted on devices, backed up to consumer clouds, or previewed on lock screens. Once sent, you cannot recall or reliably delete them from recipients’ phones.

  • Misdirected messages due to wrong numbers, autocorrect, or group threads
  • Lost or stolen devices without passcodes or remote wipe capability
  • No reliable identity verification of recipients before viewing sensitive content
  • Lack of centralized retention, discovery, or audit logs to prove who saw what and when
  • Attachments (photos, lab screenshots) that persist indefinitely in camera rolls and backups

Because these risks undermine HIPAA safeguards, you need a controlled alternative for any workflow that involves ePHI.

HIPAA-Compliant Text Messaging

HIPAA does not prescribe a single tool, but your solution must meet encryption requirements and support enforceable security and privacy controls. Secure messaging platforms designed for health care are the most practical approach.

Core capabilities your platform should provide

  • End‑to‑end encryption with strong authentication (e.g., MFA) and automatic session timeouts
  • Centralized administration: user provisioning, role‑based access, directory control, and remote wipe
  • Message management: delivery controls, expiration, forwarding restrictions, screenshot deterrence, and message recall
  • Comprehensive logging and archiving to satisfy audit trail compliance and record retention needs
  • BAA from the vendor affirming HIPAA safeguards, incident handling, and data return/destruction
  • Integration with EHR/EMR, on‑call schedules, and clinical workflows to reduce workarounds

Process controls you must implement

  • Documented risk analysis procedures and periodic risk management reviews
  • Minimum necessary content: exclude diagnoses, test details, and images unless in a secured app
  • Identity verification before discussing ePHI; confirm the intended recipient and their authority
  • BYOD governance: device encryption, passcodes, mobile device management, and banned personal backups
  • Retention and e‑discovery plan aligned with organizational policy and state requirements

Patient-facing messaging guidance

  • Prefer secure portals/apps for clinical details; use SMS only for non‑PHI notifications or generic reminders
  • Inform patients about texting risks and document their preferences; never force unsecured channels
  • Avoid specialty clinic names or condition‑revealing terms in any open channel

This overview is informational and does not constitute legal advice. Consult counsel for policy decisions.

Ready to simplify HIPAA compliance?

Join thousands of organizations that trust Accountable to manage their compliance needs.

Examples of Compliant Text Messages

Patient-facing (no ePHI in open text)

  • “You have a new message from Dr. Rivera. Please log in to your secure patient app to view.”
  • “Reminder: appointment on 12/08 at 9:30 AM. Reply C to confirm or call to reschedule.”
  • “Your prescription is ready at your pharmacy. Details available in your secure portal.”

Internal care team (within a secure messaging platform)

  • “AB (MRN 0045123) ready for discharge; see updated EHR note and med reconciliation.”
  • “Rapid response activated for 4W‑12; labs and vitals posted in the secure thread.”
  • “Prior auth approved; attach summary from EHR (no screenshots via SMS).”

These examples assume a secure platform with encryption, access controls, archiving, and a BAA in place.

Examples of Non-Compliant Text Messages

  • “John Doe, DOB 01/03/1983: CT confirms diverticulitis. Start antibiotics today.” (PHI over SMS)
  • “Here’s the wound photo you requested.” (unencrypted clinical image sent via MMS)
  • “Group: Mary Smith needs early refill on oxycodone.” (identifies patient and medication in open thread)
  • EHR screenshots pasted into a consumer texting app (no control, no audit trail compliance)
  • “HIV Clinic: your appointment is tomorrow at 2 PM.” (reveals sensitive specialty care)

Financial Penalties for HIPAA Violations

Texting mistakes that expose ePHI can trigger enforcement by the Office for Civil Rights (OCR). Civil monetary penalties are assessed per violation and scaled by the level of culpability, with annual caps. Sanctions often include corrective action plans, external monitoring, and documentation requirements that persist for years.

Serious or intentional misuse of ePHI can also lead to criminal liability. Beyond regulatory penalties, organizations face breach notification costs, forensics, patient outreach, downtime, reputational harm, contractual exposure with payers and partners, and potential actions by state attorneys general. Business associates are directly liable when their services or staff contribute to a breach.

Recommendations for Secure Texting

Practical steps you can take now

  • Perform a documented risk analysis and update it whenever workflows or tools change.
  • Select secure messaging platforms that meet encryption requirements, offer robust admin controls, and will sign a Business Associate Agreement.
  • Write clear policies: minimum necessary, approved channels, BYOD, retention, incident response, and sanctions.
  • Train your workforce regularly; reinforce how to avoid unauthorized access risks (wrong numbers, lock‑screen previews, group chats).
  • Configure devices: enforce passcodes, auto‑lock, remote wipe, and disable message previews for notifications.
  • For patient outreach, limit SMS to neutral notifications and route clinical content to a secure app or portal.
  • Monitor and audit: review logs, message access, and exceptions; remediate gaps promptly.

Bottom line: texting can be compliant when you use a secure, managed platform, document and test your HIPAA safeguards, and keep message content to the minimum necessary.

FAQs

What constitutes a HIPAA violation when texting patient information?

A violation occurs when a message containing ePHI is sent or stored without appropriate safeguards—such as encryption, access controls, and auditability—or when it is disclosed to someone not authorized to receive it. Typical triggers include sending PHI over standard SMS/MMS, misdirecting messages, sharing screenshots from the EHR, or including condition‑revealing details in open channels.

How can healthcare providers ensure HIPAA compliance in text messaging?

Adopt a secure messaging platform with end‑to‑end encryption, strong authentication, centralized administration, and full logging; execute a Business Associate Agreement with the vendor; perform risk analysis procedures; enforce minimum‑necessary content rules; govern BYOD with mobile device management; train staff; and routinely monitor audit trails for compliance and anomalies.

What are common examples of non-compliant text messages?

Any SMS that includes a patient’s name or other identifiers plus health information (diagnoses, test results, medications), clinical photos sent via MMS, EHR screenshots pasted into a consumer app, and reminders that reveal sensitive specialties (e.g., addiction treatment or HIV clinics) are common non‑compliant examples.

What are the potential penalties for HIPAA texting violations?

Organizations may face civil monetary penalties scaled by culpability and capped annually, mandated corrective action plans with ongoing monitoring, breach notification costs, reputational damage, and possible criminal exposure for willful misuse. Business associates can also be held directly liable for violations tied to their services.

Share this article

Ready to simplify HIPAA compliance?

Join thousands of organizations that trust Accountable to manage their compliance needs.

Related Articles