Introduction
A patient replies to your reminder: “Yes, see you Tuesday.” A minute later, a second message arrives: “The new medication is making me dizzy. Should I stop taking it?”
The channel hasn’t changed. It’s the same text thread from the practice number, maybe on a phone the patient shares with family. But the conversation has. What started as scheduling now carries a symptom, a medication, and a question that needs a clinician, and it’s sitting in an inbox that may not be built for any of that.
That moment is where most texting problems start. HIPAA doesn’t stop you texting patients or colleagues, but it does set rules for how protected health information (PHI) is protected, who can see it, and which tools you use. This guide explains those rules, what to do when a routine text turns clinical, and what to put in your texting policy.
For the wider requirements behind them, see What Is HIPAA Compliance?
Key Takeaways
- HIPAA doesn’t ban texting. It sets rules for how patient information is protected when you text.
- Ordinary SMS and iMessage lack the access controls and audit logs HIPAA expects, so they shouldn’t carry clinical information.
- Appointment reminders count as treatment communications and can go by text, as long as they leave out clinical details.
- Patients can ask to receive unencrypted texts. Warn them of the risk first and document their choice.
- Clinicians can text patient information, and now orders, through a secure texting platform that meets their organization’s policies.
- A texting policy should cover what happens when a routine text turns clinical, not just which app staff may use.
Is Texting HIPAA Compliant?
Texting can be HIPAA compliant, but ordinary texting usually isn’t. HIPAA doesn’t name approved apps or ban SMS. It requires that PHI be protected with appropriate safeguards and that vendors acting as business associates sign a Business Associate Agreement (BAA).
In practice, that splits texting into two kinds. A simple appointment reminder is still PHI, but HIPAA allows it as a treatment communication, so it can go by ordinary text if it’s limited to what the reminder needs. Messages with clinical details should go through a secure platform built for healthcare (see our comparison of HIPAA-compliant texting apps), unless a patient has knowingly chosen otherwise.
Why Ordinary SMS and iMessage Fall Short
Standard SMS travels unencrypted through phone carriers and sits on their systems and on every device it reaches. Nobody controls who can read it once it’s sent, there’s no audit trail of who accessed it, and a lost or shared phone exposes everything on it.
iMessage is end-to-end encrypted between Apple devices, but encryption isn’t the whole test. Apple doesn’t sign a BAA for its consumer messaging, your organization has no admin control over accounts or devices, and messages fall back to unencrypted SMS whenever the other person isn’t on iMessage. WhatsApp has the same gap: strong encryption, but no BAA.
Texting Patients: What HIPAA Allows
Appointment reminders and routine messages
HHS treats appointment reminders as part of treatment, so you don’t need a patient’s written authorization to send them. Keep them to what the reminder needs to work: the patient’s first name, the date and time, the practice name and how to confirm or reschedule. Leave out the reason for the visit, test names and anything that hints at a condition. “Your appointment at Lakeside Clinic is on Tuesday at 10am” is fine; “your HIV test follow-up is Tuesday” is not.
Remember where the text lands. A reminder can appear on a lock screen or a shared family tablet before the patient opens it, so write every reminder as if someone else will read the preview.
When patients ask for unencrypted texts
Patients have the right to ask you to communicate with them in a particular way, and HIPAA expects reasonable requests to be honored. If a patient wants clinical information by ordinary text, you can send it, provided you’ve warned them that unencrypted messages can be read by others and they still prefer it. HHS has confirmed this approach for email, and the same principle is widely applied to texts. Record the warning and their choice in their file, and keep using a secure channel for anyone who hasn’t opted in.
Agreeing to appointment texts isn’t the same choice. A patient who signed up for reminders hasn’t chosen to receive test results or medication advice by ordinary SMS. That needs its own warning and its own record.
Consent to text
Separately from HIPAA, automated texts to patients fall under the Telephone Consumer Protection Act (TCPA), which has its own consent and opt-out rules. Capture each patient’s texting consent and preferred channel at registration, and include a simple way to opt out in automated messages.
Texting Between Clinicians and Staff
Clinicians texting each other about patients is where the biggest risks sit, because these messages are almost always full of PHI. Organizations should ban ordinary SMS for patient information and give staff a secure texting platform instead.
The risk often starts with a forward. A receptionist screenshots the patient’s dizziness question and texts it to the prescribing doctor’s personal phone. The patient’s name, medication and symptom are now on an unmanaged device, outside any audit trail, and missing from the record. A secure platform lets staff hand the conversation over instead of copying it out.
Texting orders used to be off-limits even on secure platforms. That changed in February 2024, when CMS updated its guidance for hospitals and critical access hospitals: care teams can now text patient information and orders through a HIPAA-compliant secure texting platform, as long as they meet Medicare’s Conditions of Participation. The Joint Commission followed in June 2024 for the organizations it accredits. Computerized order entry is still the preferred route. Your platform needs secure sign-on, encryption, delivery receipts and time stamps, and texted orders need a reliable way into the patient record.
What You Can and Can’t Put in a Text
Information becomes PHI when it identifies a patient and relates to their health, care or payment. That’s why a question like “is texting a patient’s name a HIPAA violation?” has no single answer. A first name in an appointment reminder is a permitted disclosure. The same name sent by SMS to a colleague alongside a diagnosis is PHI on an unsecured channel.
A safe default for any text that might leave a secure platform: include only what the message needs to do its job, never pair identifiers with clinical details, and move anything clinical into a secure channel or a call.
When a Routine Text Turns Clinical
Most practices plan the texts they send. Fewer plan for the replies. When a patient answers a reminder with a symptom, a medication question, or a photo, four things need to happen.
- Recognize the change. Whoever monitors replies should know what clinical content looks like: symptoms, medications, results, and a photo of a rash or a wound.
- Move it to a secure channel. Don’t continue a clinical conversation over ordinary SMS. Reply with a short, non-clinical message that moves the patient to your secure app or portal or offers a call: “Thanks for letting us know. A nurse will contact you through our secure app today. If you feel very unwell, call 911.”
- Route it to the right person. The front desk shouldn’t answer a medication question. Hand the conversation, not a screenshot, to the nurse or clinician who can.
- Keep it in the record. The question and the clinical answer belong in the patient’s chart, whichever channel they arrived on.
Set patients’ expectations too. Say in your texting consent and your automated messages how quickly you reply, that texts aren’t monitored around the clock, and where to go with an urgent concern. A patient who texts about chest pain at 9 p.m. and waits for a reply is a clinical risk, not just a compliance one.
For how practices route, hand off, and close patient messages day to day, see our guide to secure patient messaging.
Secure Texting vs SMS
A HIPAA-compliant texting platform closes the gaps SMS leaves open. Look for:
- a vendor that signs a BAA
- encryption in transit and at rest
- unique logins for every user, ideally with multi-factor authentication
- role-based access, so staff see only the conversations they should
- audit logs of who sent and accessed which messages
- remote wipe and message retention controls for lost devices and departing staff
Under the current Security Rule, encryption is an “addressable” specification rather than an absolute requirement, but in practice every credible secure texting platform encrypts. HHS proposed in December 2024 to make it mandatory. For the full set of controls, see What Are HIPAA Technical Safeguards?
Teams building texting into their own app can use the HIPAA compliance checklist for telehealth apps, including how to keep PHI out of push notifications.
Building a HIPAA Texting Policy
A written policy turns these rules into daily practice. It should cover:
- which platform staff must use for PHI, and a ban on personal SMS and consumer apps for patient information
- what may go in appointment reminders and other automated texts
- who monitors replies to automated texts and how quickly they respond
- what staff do when a reply raises a clinical question or sounds urgent
- how patients opt in, choose their channel, and request or decline unencrypted texts
- when clinicians may text orders, and how texted orders reach the record
- retention, deletion, and what happens when a device is lost or an employee leaves
- training and regular checks that staff are following the policy
Review the policy whenever you add a new texting tool or workflow, and include texting in your HIPAA risk analysis.
Conclusion
Texting is too useful to ban and too risky to leave unmanaged. Most of the work isn’t choosing an app. It’s deciding what happens when a reminder thread turns into a clinical conversation: who sees it, where it moves, and how it reaches the record. Keep PHI off ordinary SMS, keep reminders minimal, respect patients’ choices, and give staff a secure platform that’s easier to use than their personal phones.
Designing that handoff, from a text notification to a secure conversation with the right clinician, is where messaging infrastructure matters. Teams building it into their own product can use the QuickBlox HIPAA-compliant chat API and SDKs. If you’d rather launch a branded messaging app without building one, look at Q-municate.
Additional Resources
These guides go deeper on secure messaging and the wider compliance picture.