“10,000+ Appointments Booked Across AI-Powered Campaigns”-Get the System
Skip to content
MediaBloom
Blog
Insights 12 min readNov 17, 2026

HIPAA Compliant SMS: Rules for Texting Patients

What makes SMS HIPAA compliant: when texts need a BAA, what a reminder can say, and how to automate scheduling and follow-up without exposing patient data.

JJ
John Jahshan
Founder and CEO, MediaBloom
HIPAA Compliant SMS: Rules for Texting Patients

Watercolor frame for HIPAA texting article

SMS becomes HIPAA compliant when you control what the message says and who handles it. A text with no protected health information (PHI) is not a HIPAA problem. A text with PHI must travel through a secure service covered by a business associate agreement (BAA), unless the patient has asked or authorized otherwise. The practical path for a practice: keep reminders generic, move anything sensitive to a portal, and build the automation around those limits from day one. That is how we build texting and follow-up at MediaBloom: done-for-you, with the message rules designed into the workflow instead of patched on later.

This guide is for owners and decision-makers at medical practices, med spas and other healthcare-adjacent businesses that want faster follow-up and more booked appointments by text. Whether HIPAA applies to your business is a question for your compliance officer or healthcare attorney. If it does, the rules below tell you how to design the text workflow.

Mediabloom
Build Safer Patient Texting Workflows
MediaBloom builds AI systems and follow-up workflows with message rules designed in, helping practices automate reminders and lead follow-up.
Watch the AI voice agent demo

TL;DR

  • A text containing only a name, venue and appointment time does not violate HIPAA, according to the HIPAA Journal’s 2026 update.
  • PHI in a text needs a secure messaging service covered by a BAA, unless the patient requested or authorized otherwise.
  • Patients can ask to be texted. You can agree, but you must warn them of the risk, offer a secure alternative and document the warning.
  • Chatbots and voice agents follow the same logic: every vendor that touches PHI signs a BAA, and the bot gets a narrow job.
  • Design the message first, then automate it. Scheduling, reminders and speed-to-lead all work with minimal-PHI texts.

Table of Contents

What HIPAA actually says about texting

HIPAA does not ban text messages. It governs protected health information: health data tied to an identifiable person. A name paired with an appointment reason, a symptom or an insurance detail all count, as Medigy’s guidance explains, citing HHS.

That gives you two kinds of text:

  1. Texts without PHI. Appointment reminders with only a name, venue and time are permissible, per the HIPAA Journal.
  2. Texts with PHI. These must go through a HIPAA-compliant messaging service covered by a BAA, with encryption and access controls, unless the patient has requested or authorized otherwise.

A BAA is a written contract between a covered entity (a provider, health plan or clearinghouse) and a vendor that handles PHI for it. HHS’s business associate FAQs say it must describe the permitted uses and disclosures of PHI and restrict any further use or disclosure. For electronic PHI, it must require the vendor and its subcontractors to follow the Security Rule and report security incidents, including breaches of unsecured PHI.

One point trips up many teams: plain SMS cannot be encrypted. Psychiatric News notes that HIPAA allows unencrypted patient texting only when the patient has been warned of the risks and consents, with the warning and consent documented. So the safest default is a text that carries nothing worth protecting.

What a compliant reminder text can say

The rule of thumb is minimum necessary: send the least information that gets the patient to the appointment. HIPAA Journal explains that the Privacy Rule permits PHI for appointment reminders under its treatment, payment and operations provisions, but the minimum necessary standard applies when reminders reach family members, friends or a third-party channel that requires a BAA.

A generic reminder may include:

  • The date and time
  • The provider’s first and last name
  • The location

That list comes from the HIPAA Journal’s 2026 update. It also advises providing any needed PHI through a patient portal.

Example: safe versus risky

Safe: “Hi Dana, this is a reminder of your appointment with Dr. Alvarez on Tuesday at 2:30 PM at our Tampa office. Reply C to confirm or R to reschedule.”

Risky: “Hi Dana, your follow-up for the lab results on your thyroid panel is Tuesday at 2:30 PM. Your balance is $240.”

Safe and risky patient text comparison

The second message ties a person to a condition and a billing detail. Move that content to a portal login. UNC Health’s privacy guidance takes the same line: unencrypted patient texts only for limited purposes such as reminders and logistics, never Social Security numbers, financial information or sensitive medical details, and patient replies limited to preprogrammed responses.

That last point is useful for automation. Reply keywords (C to confirm, R to reschedule, STOP to opt out) keep the conversation inside a narrow lane and make booking fast.

When the patient wants to text you

Patients can ask for communication by text. Under 45 CFR §164.522(b), as the HIPAA Journal describes it, a reasonable request for confidential communication by alternative means, SMS included, must be honored even if it adds risk. You then need to:

  1. Warn the patient of the risks.
  2. Offer a compliant alternative, such as a secure portal.
  3. Document the warning.

Build this into intake. A consent step at registration, stored in your CRM against the patient record, means your team and your automations always know who agreed to what.

A separate point on direct disclosure: the minimum necessary standard does not apply to disclosures made directly to the patient, as the HIPAA Journal notes. The standard bites when a message goes through a third-party channel that needs a BAA, or reaches someone other than the patient. Most automated texting runs through such a channel, so plan for minimum necessary.

HIPAA compliant scheduling by text and online

Online scheduling and text confirmations are allowed. HIPAAnswers frames the conditions this way: the system and its reminder functions protect electronic PHI under the Security Rule, workflows limit uses and disclosures, and the vendor and its subcontractors sign BAAs. Reminders should leave out diagnosis or treatment details that scheduling does not need.

A scheduling workflow that holds up:

Step What happens PHI in the text?
New inquiry Lead submits a form or calls; an instant text offers times No
Booking Patient picks a slot by reply or link No, only date, time, provider, location
Confirmation Text confirms the visit No
Pre-visit forms Link to a secure portal No, details live in the portal
Reminder Text 24 to 48 hours before No
No-show or reschedule Text with reply options No

Every step moves the patient forward and none of them needs a diagnosis in the message. Speed matters as much as safety here. A practice that texts an inquiry back within minutes books more of the people who reached out, which is the job of speed-to-lead for medical and healthcare practices.

HIPAA compliant chatbots and voice bots

The same logic extends to AI. No official designation makes an AI model compliant on its own. HIPAA Vault’s checklist says compliance depends on how the system handles PHI, which vendors receive it, whether BAAs are in place and whether safeguards protect electronic PHI. Its risk analysis should cover the whole stack: model and API providers, retrieval systems, data stores and subcontractors.

What that means in practice:

  • BAAs across the chain. Every vendor touching PHI signs one, including the company supplying the language model.
  • Access and audit controls. Know who and what can see conversation data, and keep logs without copying PHI into every one.
  • Encryption in transit and at rest.
  • A defined retention period. Do not keep transcripts longer than you need.
  • A narrow scope. Medigy’s guidance says the strongest clinical bots have a defined job such as scheduling, reminders, insurance and billing questions, or pre-visit intake, and hand off to a person when a conversation turns urgent or distressing.
  • No diagnosing. A bot can collect what a patient reports and route it. It should not act as a clinical authority.

If your bot or voice agent is for booking, the cleanest design keeps clinical content out of the conversation entirely. Collect name, preferred time and callback number, confirm the slot and route anything clinical to staff. Our AI chatbot for medical and healthcare websites and AI voice agents are built for this kind of front-desk work: answering, qualifying and booking.

De-identify where you can

The safest PHI is PHI that never reaches the model in identifiable form. Aptible’s developer guidance describes HIPAA’s two de-identification standards under 45 CFR 164.514, Safe Harbor (removing 18 identifiers) and Expert Determination. It recommends tokenizing names, dates and Social Security numbers before they reach a language model. For a scheduling bot, this is a design choice you can make in the first week.

Vendor checklist before you turn anything on

Whether it is a texting platform, a chatbot or a voice agent, check the same items. AccountableHQ’s text-messaging policy checklist is a good outline:

  1. A documented risk analysis for the texting workflow.
  2. A secure platform with encryption, audit logs, role-based access and multi-factor authentication.
  3. Patient consent and an opt-out path.
  4. Minimum-necessary message content.
  5. Device safeguards: device management, remote wipe, encryption at rest.
  6. Executed BAAs with texting vendors and their subcontractors, including breach-notification timelines and return or disposal of PHI at termination.

Risk analysis comes before launch. As Allison Kwon of CM Health Law notes, HIPAA sets no frequency for risk assessments, but guidance says risk analysis and management should happen as new technologies are planned, not only after rollout.

A few related points from the same sources:

  • Business associates must sign BAAs with their own subcontractors before sharing PHI, per HHS.
  • A peer-reviewed analysis in PMC advises minimizing data collection to what is strictly necessary and watching tracking technologies so health data is not shared unintentionally, especially for advertising.
  • Your IT team or provider matters here. For device management, encryption and vendor review, a provider such as IT support for dental offices shows what managed security and unified communications setup covers for a small practice.

What changed recently

Two developments are worth knowing:

  • CMS on secure texting. In 2024, CMS stated that texting patient information and orders among hospital and critical access hospital staff is permissible through a HIPAA-compliant secure texting platform. The Joint Commission’s FAQ adds that platforms should be secure, encrypted and routinely assessed. This concerns staff-to-staff messaging, not marketing or patient reminders.
  • A proposed Security Rule update. The Federal Register published a proposal on January 6, 2025, to strengthen cybersecurity for electronic PHI. Check HHS for its current status.

Building on encrypted channels, access controls and audit logs now puts you in good shape whichever way final rules land.

Where the leads leak

Most practices that struggle with texting do not struggle with HIPAA first. They struggle with speed and follow-up. The inquiry comes in at 7 PM, nobody replies until morning, and the patient books elsewhere. Or the practice avoids texting out of caution and relies on voicemail.

A minimal-PHI workflow solves both. The first text is generic and instant. The booking happens in a few replies. Anything clinical moves to a portal or a staff call. Our medical ads management with AI follow-up page shows how we connect ad leads to that follow-up, and the AI appointment setter explainer covers the booking side.

Perspective: build the message rules first

We build lead generation, AI follow-up and CRM as one system, because most leaks happen between vendors: the ad platform, the form, the texting tool and the CRM each hold a piece of the lead.

For healthcare-adjacent businesses, that same handoff is where texting rules get tested. A reminder template written by one team, a chatbot configured by another and a CRM automation from a third rarely agree on what a message may contain.

Our approach is to settle the message rules first: what the first text says, what a reminder includes, which reply keywords the patient can use, and where a conversation goes to a person. Then we build the ads, the AI agents and the CRM around those rules, and our team books the appointments. One partner covers the whole path, so nothing falls through the cracks.

Since 2022 we have worked with 300+ businesses, and our campaigns go live in days, not quarters. For a practice, the result we aim for is simple: fast, short, minimal-PHI texts that book the visit.

MediaBloom

Put it to work with MediaBloom

If you want patient texting, reminders and AI follow-up running without adding front-desk workload, we build and run it for you. We set up the AI agents, the CRM pipelines and automations, and the ad campaigns that feed them, and our team books the appointments. See HIPAA-compliant AI for medical practices and health systems for how this looks in a practice, or start at mediabloom.us.

Mediabloom

For database reactivation, our Reactivation AI contacts past patients and inquiries by text and call, and books the ones who respond.

FAQ

Is it HIPAA compliant to text patient information?

It depends on the content. A text with only a name, venue and appointment time does not violate HIPAA. If the text contains PHI, it must go through a HIPAA-compliant messaging service covered by a BAA, unless the patient has requested or authorized otherwise. Anything sensitive belongs in a patient portal.

Can patients ask me to text them?

Yes. Under 45 CFR §164.522(b), you must honor a reasonable request for confidential communication by alternative means, including SMS. Warn the patient of the risks, offer a compliant alternative and document the warning.

Do chatbots and voice bots need a BAA?

If they collect, store or transmit PHI, the Security Rule applies and every vendor touching that PHI needs a BAA, including the language-model provider. Keep the bot’s scope narrow, minimize what it collects and hand off to staff for urgent or clinical questions.

What should an appointment reminder include?

The date and time, the provider’s first and last name and the location. Leave out diagnoses, treatment details, balances and test results, and give that information through a portal.

Does HIPAA apply to my business?

HIPAA applies to covered entities and their business associates. Whether you fall into either group is a question for your compliance officer or healthcare attorney, and the answer decides how much of this guide you need.

Mediabloom
Discuss Your Patient Texting Workflow
Contact MediaBloom to discuss AI systems and follow-up workflows for your practice, including how message rules fit into the process.

Sources

About the writer
JJ

John Jahshan

Founder and CEO, MediaBloom
Fort Myers, Florida Writes on AI voice agents, Speed-to-lead automation

John Jahshan is the founder and CEO of MediaBloom. He works directly with agencies, operators, and enterprise teams to design and deploy AI revenue systems — voice agents, speed-to-lead automation, reactivation campaigns, and ads management — that turn attention into booked appointments and signed deals. He writes about the operator playbooks, engineering decisions, and partnership models behind the systems MediaBloom ships for clients.

AI voice agentsSpeed-to-lead automationRevenue operationsPartnership programs
Newsletter

Get the MediaBloom newsletter.

One email per week. Research, launches, and operator playbooks. Zero fluff.

Ready to see MediaBloom in action?

Talk to our team about deploying AI across your funnel.