Crashcart Start your free trial

HIPAA security for small practices

Can you text or email patients under HIPAA

Yes. HIPAA lets a practice email and text patients, as long as it uses reasonable safeguards and meets the Security Rule for anything it sends electronically. HHS says unencrypted email to patients is allowed for treatment if you limit what goes in it, and a patient who asks for their records by unencrypted email gets them after a short warning. No HIPAA rule is written for texting patients, so the same tests apply: what the message says, which app or vendor carries it, and whether your written policy covers it.

The rules below come from the HIPAA Privacy Rule, the Security Rule and HHS's own FAQs, which HHS numbers and keeps on its site. For everything else the Security Rule asks of a practice, see the full guide to the HIPAA Security Rule for small practices.

Is texting patients a HIPAA violation?

No. The Privacy Rule requires a practice to "reasonably safeguard" patient information (45 CFR 164.530(c)). It doesn't ban any way of communicating. The Security Rule doesn't either. HHS's FAQ 2006 says it "does not expressly prohibit the use of email for sending e-PHI" and allows patient information to travel over an open network "as long as it is adequately protected."

HHS's current FAQs don't address texting patients. On October 18, 2026 we collected every FAQ linked from the 42 category pages of HHS's HIPAA FAQ database, 452 in all, and searched the text of each. 18 mention email. Two mention text messaging, both from 2020 and both about the COVID-19 telehealth rules. None mentions SMS. HHS says some older FAQs were moved to an archive, and we didn't search that.

The closest match is FAQ 198, on answering machine messages. HHS says leaving appointment reminders is allowed, but practices "should take care to limit the amount of information disclosed," for example only the practice's name and number, what's needed to confirm the appointment, or a request to call back. A text reminder fits the same advice. "Your appointment with us is Tuesday at 2. Reply C to confirm" is fine. A text with a diagnosis or lab result needs more care.

What HHS says about emailing patients

FAQ 570 answers the email question directly. The Privacy Rule "does not prohibit the use of unencrypted e-mail for treatment-related communications between health care providers and patients," as long as the practice applies other safeguards, "such as limiting the amount or type of information disclosed." HHS's examples of safeguards are checking the address before sending and sending a first email to confirm the address.

The same FAQ covers patients who start the conversation. If a patient emails you, you can assume email is acceptable to them unless they've said otherwise. If you think they don't know the risks of unencrypted email, you can tell them and let them decide whether to keep going.

Provider-to-provider email is allowed too. FAQ 482 says treatment communications may happen "by phone, fax, e-mail, or otherwise," with safeguards that fit the method.

When a patient asks for unencrypted email or texts

Two different rights can put a patient's request in front of you.

Confidential communications. A provider "must accommodate reasonable requests" to receive communications "by alternative means or at alternative locations" (45 CFR 164.522(b)). You may ask for the request in writing. You may not ask why. FAQ 570 gives the example of a patient who wants appointment reminders by email instead of a postcard, and says you should go along with it if email is reasonable for your practice. It also works the other way. A patient who finds unencrypted email unacceptable should be offered something else, such as a more secure electronic method, mail or the phone.

The right of access. When a patient asks for an electronic copy of records you keep electronically, you must provide it "in the electronic form and format requested by the individual, if it is readily producible" (45 CFR 164.524(c)(2)(ii)), and you have 30 days to act on the request. FAQ 2060 says patients "have a right to receive a copy of their PHI by unencrypted e-mail" if they ask. Before sending, the practice "must provide a brief warning" that a third party could read the information in transit, and confirm the patient still wants it that way. If they say yes, you must send it. You can't make a patient accept an unsecure method, and you can't make them come to the office to pick up a copy they asked to have emailed.

Once you've warned the patient and they accept, the transmission is on them. FAQ 2061 says a practice isn't responsible for a disclosure in transit to the patient in that case, including breach notification. The same FAQ limits that to access requests. For every other message, a practice "may be liable for impermissible disclosures" in transit and is responsible for breach notification for unsecured transmissions.

A warning we'd use, read aloud or sent before the first message: "Regular email and text messages may not be encrypted on the way, so someone other than you could read them. Do you still want us to send your records this way?" Note the answer and the date in the chart.

Texting between staff and texting patients

The two get confused, but they raise different problems.

Texts between staff about a patient are part of your practice's own handling of patient information, and the Security Rule applies in full to the phones and apps involved. Each person needs their own login (164.312(a), unique user identification, required). Automatic logoff is addressable. The phones themselves are devices that hold patient information, so they belong in your risk analysis and under your device and media controls, including what happens to the messages when a phone is replaced (164.310(d)). A group text on staff's personal phones with patient names in it fails most of that. A messaging app the practice controls, with accounts it can turn off when someone leaves, passes most of it.

Texts to patients are mainly a Privacy Rule question. Limit what goes in the message, send it to the right number, and respect the patient's stated preference. The Security Rule still covers how you send it, as the next section explains.

Don't rely on the COVID-era leniency. FAQ 3024, still on HHS's site, lists iMessage, WhatsApp and Signal among products providers could use, but only under a notice of enforcement discretion for telehealth. HHS's telehealth page says those notices expired on May 11, 2023, and the transition period ended August 9, 2023.

What the transmission security standard requires

The Security Rule's transmission security standard says to "guard against unauthorized access to electronic protected health information that is being transmitted over an electronic communications network" (45 CFR 164.312(e)). Its two specifications, integrity controls and encryption, are both addressable. FAQ 2006 says the practice "must assess its use of open networks, identify the available and appropriate means to protect e-PHI as it is transmitted, select a solution, and document the decision."

So the practical work is a written decision for each way you send patient information: practice email, patient portal, appointment reminder service, staff messaging app, plain texts from the front desk phone. For each, write down what it may carry, whether it's encrypted on the way, and why that fits your practice.

Encryption in transit also matters after a mistake. HHS's guidance on unsecured PHI treats data in motion as secured when it's encrypted consistent with NIST SP 800-52 (TLS, the encryption between mail servers and between your browser and a website), or IPsec or SSL VPN guidance. If a message is intercepted on the way and it was encrypted that way, no breach notice is needed. Encryption doesn't help with a text sent to the wrong number, since the wrong person can read it.

For email, TLS between mail servers protects the trip. Crashcart, which runs IT for small offices, checks every week that email to a practice's domain travels encrypted. For a message that needs protection all the way to a Gmail or Yahoo inbox, Microsoft 365 offers Microsoft Purview Message Encryption, where the recipient opens the message through a portal. Check whether your plan includes it. The Microsoft 365 security settings post covers the rest, including blocking automatic forwarding to outside addresses.

When a texting or email vendor needs a BAA

The test is whether the vendor only carries the message or also keeps it.

HHS's audio-only telehealth guidance lists wireless carriers among telecommunication service providers and says a practice doesn't need a business associate agreement (BAA) with one that has "only transient access" to what it transmits, because it is a conduit. The same guidance says a practice "must enter into a BAA with a vendor that is more than a mere conduit," and gives the example of an app that stores recordings or transcripts in its own cloud. That guidance is about phone calls. We found no HHS guidance that applies it to text messages. Its footnotes point to HHS's cloud computing guidance for the same line between transient and persistent access, and a texting service that keeps your message history has persistent access.

That puts these vendors on the BAA side: an appointment reminder or patient texting service, a patient portal, a secure messaging app for staff, and the company that hosts your email. Each one stores patient information for you. Which vendors need a business associate agreement covers how Microsoft 365 and Google Workspace handle theirs. Get the signed agreement before the first patient message goes through a new service.

What to write in your texting and email policy

A one-page policy covers a small practice. It should answer:

  1. Which channels staff may use for patient information: practice email, the portal, the reminder service, the staff messaging app. Personal texting and personal email accounts are off the list.
  2. What each channel may carry. Reminders and "please call us" messages by plain text; results, diagnoses and records through the portal or encrypted email unless the patient asked otherwise.
  3. How staff confirm a number or address before the first message, such as a test message or reading it back to the patient.
  4. How the practice records a patient's preference, the warning given, and the date, for both confidential communication requests and access requests.
  5. Who handles electronic access requests, and how the 30-day clock is tracked.
  6. Which vendors carry patient messages, and where each signed BAA is kept.
  7. Rules for staff phones: their own login on the messaging app, a screen lock, and what happens to the app and its messages when someone leaves or a phone is replaced.
  8. What staff do when a message goes to the wrong person. That's an impermissible disclosure to assess under the HIPAA breach notification rules, so the policy names who gets told the same day.
  9. A yearly review, signed by the security official.

Keep each version for six years, like the rest of your HIPAA documentation.

This is general information, not legal advice. For your situation, ask your attorney.

More in this topic

Crashcart runs IT and security for small offices for $35 a computer a month. Start a 14-day free trial.