Blog

HIPAA-compliant email: what patient notifications need

Emily LaneEmily Lane
HIPAA-compliant email cover

HIPAA allows you to email patients, and HIPAA-compliant email comes down to what's in the message. An email that carries protected health information (PHI) needs a provider that signs a business associate agreement (BAA) and encryption you've judged adequate, while an email with no clinical detail, like "your results are ready, sign in to view them," can go through your regular provider.

Most patient email is that second kind: a reminder, a nudge, a notice that something is waiting in the portal. So the practical move is to split your email in two. Notification email stays PHI-free and runs on your regular provider. The rare email that has to carry clinical detail goes through a BAA-covered path built for it, or doesn't go by email at all. We're engineers, not your compliance lawyers, so treat this as the engineering reality, not legal advice.

Is email HIPAA compliant? What the rule says

Email itself is neither compliant nor non-compliant. What HIPAA cares about is how you protect PHI when it travels by email.

Email with patients is allowed. HHS says providers can email patients about their health as long as they apply reasonable safeguards, and that if a patient finds email unacceptable, the provider should accommodate a request to use a different method (HHS FAQ 570).

Encryption is addressable today. The Security Rule lists "Encryption and decryption" for stored data and "Encryption" for transmitted data as addressable specifications (45 CFR 164.312(a)(2)(iv) and (e)(2)(ii)). Addressable doesn't mean optional: you assess whether encryption is reasonable for your setup, and you document the decision if you go another way.

A proposed update would make encryption required. HHS proposed a Security Rule update on January 6, 2025, that would make encryption a required safeguard. It's still a proposal. The rule sits in Long-Term Actions with final action projected for July 2027 (RIN 0945-AA22). Plan for it, but don't treat it as law yet.

Patients can ask for their own records by unencrypted email. Under the right of access (45 CFR 164.524), if a patient asks to receive their PHI by unencrypted email, you warn them about the risk, confirm they still want it that way, and send it. After that, you aren't responsible for a disclosure that happens in transit (HHS FAQ 2061). That's the patient's choice about their own records, not a general permission for outbound email.

Notification email vs clinical email

The split that makes everything else manageable:

Notification emailClinical (PHI) email
What it saysSomething happened, go lookThe details themselves
PHI in the emailNoneYes
BAA with the email providerNot needed for PHI-free emailRequired
EncryptionStandard TLSEnforced TLS or an encrypted message
Example"Your results are ready, sign in to view them"A lab report, a visit summary, a referral letter
Recommended patternLink to the portalBAA-covered provider, or the portal instead

The decision rule for any email you're about to build:

  1. If the patient needs the details, send a notification that links to the portal, and show the details after sign-in.
  2. If the patient has to receive the details in the email itself, send it through a BAA-covered provider with enforced TLS or encrypted-message delivery.
  3. If the patient asked for their own records by plain email, follow the right-of-access steps above and document the warning and the confirmation.

Three ways to send patient email

Those three paths map to three sending patterns:

PatternHow it worksPHI in the emailBAA with the providerPatient frictionBest for
Link to portalThe email says something is ready and links to an authenticated pageNoneNot neededOne sign-inReminders, results ready, bills, new messages
Encrypted messageThe content travels over enforced TLS or sits behind a secure pickup pageYesRequiredLow to medium, depending on the methodDocuments the patient needs in hand
Patient-requested unencryptedThe patient asks for plain email, you warn and confirm, then sendYesRequired for the sending providerNoneA right-of-access request

Most product email belongs in the first row. It's the cheapest to run, it works with any provider, and nothing in it gets more sensitive as your templates grow.

Which email APIs sign a BAA

If an email carries PHI, the provider that sends it handles PHI on your behalf, so it needs a BAA. If a vendor won't sign one, you can't route PHI through it. Here's where the common providers stand.

Checked November 2026.

ProviderSigns a BAA?What the vendor says
Amazon SESYesA HIPAA-eligible service under the AWS BAA
Microsoft 365 / Exchange OnlineYesBAA included by default through Microsoft's Online Services Data Protection Addendum
Google WorkspaceYesGmail is among the Workspace services covered by Google's BAA, which an admin accepts
PauboxYesA BAA on every plan
LuxSciYesSecure High Volume Email is a HIPAA-eligible service under its BAA
MailgunConditionalA BAA addendum applies under a valid Service Order, only to the extent Mailgun acts as a business associate
Twilio SendGridNoNot a HIPAA-eligible service, and Twilio can't sign BAAs for SendGrid
PostmarkNoCan't sign BAAs
ResendNoCan't sign a BAA
Mailchimp Transactional (Mandrill)No BAA in its termsTerms disclaim liability for HIPAA requirements

Three of the most popular developer email APIs, SendGrid, Postmark, and Resend, don't sign BAAs. That doesn't rule them out for healthcare. It means they're fine for PHI-free notification email and not for anything carrying PHI. Microsoft 365 and Google Workspace are built for staff mailboxes, and their sending limits make them a poor fit for high-volume product email. For product email, the BAA options in this table are SES, Paubox, LuxSci, and Mailgun under the right agreement.

A BAA is necessary, not sufficient. It covers the vendor's side. You still own the configuration, the logs, and what goes in the body. For the rest of the stack (SMS, push, and in-app), see HIPAA-compliant notifications.

HIPAA email encryption: TLS isn't the whole answer

"Encrypted in transit" on a vendor's security page usually means opportunistic TLS, and opportunistic TLS can fail open.

Here's why. Mail servers negotiate encryption with STARTTLS: the receiving server advertises it, and the sender upgrades the connection. That advertisement travels in the clear, so an attacker in the middle can delete the "250 STARTTLS" response, and a sender that treats TLS as optional delivers in plaintext (RFC 3207, section 6).

MTA-STS closes that gap from the receiving side. A domain publishes a policy, and in enforce mode, senders must not deliver to hosts that fail certificate validation or don't support STARTTLS (RFC 8461). Delivery fails instead of downgrading. You can check any patient domain's policy in two commands:

Terminal
# Does the domain publish an MTA-STS policy?
dig +short TXT _mta-sts.gmail.com
# "v=STSv1; id=20190429T010101;"

# What mode is it in?
curl -s https://mta-sts.gmail.com/.well-known/mta-sts.txt
# version: STSv1
# mode: enforce
# ...

The catch is that MTA-STS is the patient's mail provider's choice, not yours. Not every domain publishes one. So for email that carries PHI, ask your provider whether it can require TLS for every message and hold or bounce it rather than fall back to plaintext. If it can't, use encrypted-message delivery or link to the portal.

For PHI-free notification email, none of this changes the risk much. There's no clinical detail in the message to intercept.

Where PHI leaks in an email stack

Putting PHI in an email doesn't create one copy. It creates one in every system the email touches. If the body carries a diagnosis, each of these now holds it:

  • Provider logs and activity feeds. Rendered bodies and template variables, visible to anyone with dashboard access.
  • Event webhooks. Delivered, bounced, and opened events carry recipient addresses, subject lines, and any custom fields you attached into whatever system receives them.
  • Bounce and suppression lists. Addresses and failure reasons, often kept long after the send.
  • Subject lines and preview text. Shown on lock screens and in notification banners before anyone opens the email.
  • Support tickets. Staff paste the email into a ticket to chase a delivery problem.
  • Your own send logs. Application logs and your notification layer's message history.

Each one needs a BAA, access controls, and a retention policy if PHI reaches it. Keep PHI out of the email, and the list stops mattering.

Writing PHI-free notification email

PHI-free email is a writing discipline more than a technical one. The rule of thumb: say that something happened, never what it was. And watch the fields that stack up. A generic reminder still reveals a condition if it comes from "Riverside Oncology" or links to /cardiology/appointments.

MessageDoDon't
AppointmentYour appointment is tomorrow at 9:30 AM. Confirm or reschedule here.The visit reason, the specialty, or a department name in the subject, body, or sender
Results readyYour latest results are ready. Sign in to view them.Test names, values, or what the result means
BillingYou have a new statement. Sign in to view it.Services, procedure codes, or diagnoses from the bill
Prescription readyYour prescription is ready for pickup.The medication name or dosage

Apply the same rule to the subject and the preview text, since those show up before anyone opens the email. Use your practice name as the sender, not a specialty clinic. For tested wording, see these appointment reminder templates.

What a confidentiality disclaimer does and doesn't do

The footer that starts "This email may contain confidential information" is the most common HIPAA email disclaimer. It tells someone who got the email by mistake that they shouldn't read or share it, and it asks them to tell you. That's useful.

It doesn't encrypt anything, it doesn't create a BAA, and it can't pull back an email that already went to the wrong person. A disclaimer on a PHI email sent through a provider that won't sign a BAA is still a problem. On a PHI-free notification, it's harmless.

Routing: one stack, two kinds of email

Put the pattern together and you get one sending layer with two lanes:

  • PHI-free notification email (reminders, results ready, statements, account email) goes through your regular provider, with templates reviewed once so nothing clinical slips in.
  • Email that has to carry PHI goes through a BAA-covered provider with enforced TLS or encrypted delivery. Or better, it doesn't go by email at all, and the patient reads it in the portal.

That's the job Courier does for the first lane. Courier routes email through the provider you connect, so you choose where it goes. Templates live in one place per message type, preferences let patients opt out of a category or pick a channel, and you can fall back to SMS when the email provider can't take the send. Here's a results-ready notification that tries email, then SMS:

JavaScript
import Courier from "@trycourier/courier";

const courier = new Courier({ apiKey: process.env.COURIER_API_KEY });

// A results-ready notification: a link, never the result.
await courier.send.message({
  message: {
    to: { user_id: "patient_4821" },
    template: "results-ready",
    routing: { method: "single", channels: ["email", "sms"] },
    data: { portal_url: "https://portal.example-health.com/results" },
  },
});

The data passed in is a link, not a result, so neither the email nor the SMS fallback carries clinical detail.

Courier maintains a HIPAA compliance program and signs BAAs with Enterprise customers. We recommend keeping PHI out of notification content either way, because a BAA and lean content work together. For the details, see Is Courier HIPAA compliant? and HIPAA compliance and BAAs in the docs.

Wrapping up

HIPAA-compliant email is mostly a content decision. Keep notification email PHI-free and it runs on any provider. When an email has to carry PHI, send it through a provider that signs a BAA and doesn't fall back to plaintext, or send the patient to the portal instead. For the texting side of the same problem, read Is texting patients a HIPAA violation?, and for how Courier supports healthcare teams, see Courier for healthcare.

Frequently asked questions

Is Gmail HIPAA compliant?

Gmail is covered when it's part of a Google Workspace account whose admin has accepted Google's BAA. Gmail is listed among the Workspace services that BAA covers. Without the signed BAA, don't put PHI in it.

Is Outlook or Microsoft 365 HIPAA compliant?

Microsoft 365 includes a HIPAA BAA by default through Microsoft's Online Services Data Protection Addendum, and Exchange Online is in scope. The BAA covers Microsoft's side. You still configure the safeguards and decide what goes in the email.

Is SendGrid HIPAA compliant?

SendGrid isn't a HIPAA-eligible service, and Twilio can't sign a BAA for it. You can use it for PHI-free notification email, but not for anything that carries PHI.

Can I email test results to a patient?

Test results shouldn't go out as a default outbound email. Send a notification that the results are ready and link to the portal. The exception is the right of access: if a patient asks for their results by unencrypted email, warn them about the risk, confirm they still want it, and then send it.

Do appointment reminder emails need encryption?

Appointment reminder emails that carry only the date, time, and a link to confirm or reschedule don't contain clinical detail, so standard TLS through your regular provider is a reasonable safeguard. Keep the visit reason, specialty, and department out of the subject, body, and sender name. Encryption is addressable today, so document the decision.

Does a confidentiality disclaimer make email HIPAA compliant?

A confidentiality disclaimer doesn't make email HIPAA compliant. It asks a mistaken recipient not to read or share the email, but it doesn't encrypt the message, create a BAA, or undo a misdirected send.