Definition

What is HIPAA-Compliant Messaging?

Patients expect to message their care team. HIPAA-compliant messaging lets you offer that without putting protected health information at risk.

HIPAA-compliant messaging vs standard SMS and consumer chat apps

Standard SMS / consumer apps

HIPAA-compliant messaging

Business Associate Agreement

Carriers and most consumer apps don't sign one

Vendor signs a BAA before any PHI is sent

Encryption in transit

SMS: not end to end. Consumer apps: varies

Encrypted, for example TLS 1.2 or higher

Encryption at rest

Messages sit on personal phones and carrier systems

Encrypted on the vendor's servers

Access control

Anyone holding the phone

Unique user logins, roles, and session control

Audit trail

None you can review

Logs of access and activity

Organisation control

Lives on staff's personal devices and accounts

Admins manage users, data and retention

Best for

Non-sensitive reminders, with patient consent

Any conversation that includes PHI

What HIPAA-compliant messaging means

HIPAA protects protected health information (PHI): anything that identifies a patient alongside their health, care or payment details. A message saying "Your lab results for Maria Lopez are ready" is PHI. So is a photo of a rash sent to a nurse.

There's no official HIPAA certification for software. A messaging tool is "HIPAA compliant" when it gives you the safeguards the rules require, and the vendor signs a BAA committing to protect the PHI it handles for you. Compliance is shared: the vendor secures the platform, and your organisation controls who uses it and how.

Key requirements

A signed Business Associate Agreement

Any vendor that creates, receives, stores or transmits PHI on your behalf is a business associate. HIPAA requires a written agreement with them before PHI flows through their service.

Access controls

Each user needs a unique login. Access should match the person's role, and sessions should end automatically after inactivity.

Audit controls

The system records activity, so you can investigate who accessed which conversation and when.

Integrity and transmission security

Messages must be protected from alteration and from interception in transit. Encryption is the standard way to do both.

Encryption at rest

The Security Rule treats encryption as "addressable", but in practice it's expected. Encrypted data that's lost or stolen generally doesn't count as a reportable breach under HHS guidance, which is reason enough to encrypt.

Where it's used

  • Telehealth apps: patients message their clinician between video visits.

  • Care team coordination: nurses, doctors and pharmacists discuss a patient in a group chat.

  • Patient support: billing and appointment questions handled by staff or an AI agent.

  • Remote monitoring: a device flags a reading and a nurse follows up in chat.

  • Pharmacy and labs: results and prescription questions answered in an authenticated app.

Simple test: if the message would identify a patient and say something about their health or care, it belongs in a channel covered by a BAA, not in a text or a notification preview.

Limits and pitfalls

  • Notifications leak. Push, SMS and email alerts often show a preview on the lock screen, and they pass through Apple, Google, carriers and email providers. Send "You have a new message" and keep the PHI inside the app.

  • Every vendor in the chain needs a BAA. If your chat sends messages to a third-party AI model, transcription or storage service, that provider needs its own BAA.

  • A BAA doesn't make you compliant. You still need policies, staff training, risk assessments and sensible retention.

  • Plain SMS is risky. HHS lets providers use unencrypted channels with patients who've been warned of the risk and still prefer them, but it's not the default for PHI. Use SMS for reminders without clinical details.

  • Personal devices need control. Staff using their own phones should sign in to the app, not forward screenshots or texts.

HIPAA-compliant messaging with CometChat

If you're building a telehealth or care app, the safest place for patient conversations is inside your own app, where users are signed in and you control the data.

Chat, calling and AI agents for healthcare

CometChat signs a Business Associate Agreement on the Advanced plan and above. Data is encrypted with AES-256 at rest and TLS 1.2 or higher in transit, with role-based permissions, multi-factor authentication and single sign-on, and audit trails. CometChat is SOC 2 Type II audited and ISO/IEC 27001 certified, and hosts data in the US, EU or India. If you connect your own AI model provider, your BAA with that provider is separate.

HIPAA-compliant chat API · Security and compliance

Frequently asked questions

Is regular texting HIPAA compliant?

Not by default. Standard SMS isn't encrypted end to end and carriers don't sign BAAs. HHS allows unencrypted messages to a patient who has been warned of the risk and still asks for them, but PHI is safer in an encrypted app covered by a BAA.

Is WhatsApp or iMessage HIPAA compliant?

They encrypt messages, but encryption alone isn't enough. You also need a BAA, access controls and audit logs your organisation manages, which consumer apps generally don't provide.

What makes a messaging app HIPAA compliant?

A signed BAA, encryption in transit and at rest, unique user logins with role-based access, audit logs, and admin control over users and data. Your organisation's policies and training complete it.

Is there a HIPAA certification for messaging apps?

No. HHS doesn't certify software. Vendors show their safeguards through BAAs and independent audits such as SOC 2 Type II or ISO 27001.

Can push notifications contain PHI?

They shouldn't. Push alerts pass through Apple or Google and can show on a locked screen. Send a generic alert and show the details only after the user signs in.

Related terms