Does a website chatbot count as handling PHI?

Almost always, yes. The moment a patient types their name and a symptom, an appointment reason, or a medication into the chat, that exchange is protected health information. Even if you never intend to collect PHI, patients volunteer it — so the chatbot must be built to handle it as if it will.

What makes an AI chatbot HIPAA compliant?

There is no compliance badge a chatbot carries. Compliance comes from how it is built and contracted: a signed BAA with every vendor that touches PHI (the chatbot platform and the underlying AI model), encryption in transit and at rest, least-privilege access, no use of PHI to train models, audit logging, and a documented data flow reflected in your Security Risk Assessment.

Can I use a generic chatbot builder for my medical practice?

Only if the builder — and the AI model behind it — will sign a BAA covering your exact configuration, and you can control where conversation data is stored and whether it is used for training. Most consumer chatbot builders and off-the-shelf widgets cannot meet this bar, which is why healthcare chatbots are usually purpose-built.

Where does the conversation data go?

That is the central question. In a compliant build you know exactly where each message is stored, who can access it, how long it is retained, and that it is never sent to an AI model outside a BAA-covered, zero-retention endpoint. If a vendor cannot answer this precisely, the chatbot is not safe for a medical practice.

Do we still need a Security Risk Assessment if the vendor is compliant?

Yes. The vendor being BAA-covered handles their side; you are still responsible for your risk analysis. Adding a chatbot that touches PHI is a material change that must be reflected in a current Security Risk Assessment, including the data flow, the vendors involved, and the residual risk.

Healthcare July 13, 2026 8 min read · By Truvaldi

HIPAA-Compliant AI Chatbots: What Actually Makes One Compliant

A chatbot on a medical practice's website will collect protected health information whether you plan for it or not. Here's what separates a compliant build from a liability — and the questions to ask any vendor before you deploy one.

The assumption that gets practices in trouble

"Our chatbot doesn't handle PHI — it just answers general questions and books appointments." We hear this constantly, and it's almost never true in practice. Patients don't read your intended scope. They type what's on their mind: "I need to be seen for a rash that's spreading," "can Dr. Lee refill my sertraline," "I think my daughter has an ear infection." The instant that happens, your chatbot is processing PHI.

So the safe design assumption is the opposite of the common one: a website chatbot for a medical practice will handle PHI, and it must be built as if it will from day one.

The core question for any medical chatbot: when a patient types something sensitive, where does that message go, who can read it, how long is it kept, and is it ever sent to an AI model outside a BAA-covered boundary? If the vendor can't answer precisely, stop there.

What "HIPAA-compliant chatbot" actually means

As with any tool, there's no certification a chatbot carries. Compliance is a property of the architecture and the contracts behind it. A genuinely compliant medical chatbot has all of the following:

1. A BAA with every vendor in the chain

A chatbot is rarely one vendor. There's the chat platform, and there's the AI model generating responses. Both touch PHI, so both are business associates and both need a signed BAA. A chatbot platform that signs a BAA but pipes messages to a consumer AI model with no BAA is not compliant — the chain is only as strong as its weakest link.

2. Encryption in transit and at rest

Conversations must be encrypted end to end and encrypted wherever they're stored. Table stakes, but worth verifying rather than assuming.

3. Controlled, documented data flow

You should be able to draw the exact path a message takes: browser → chat platform → AI model → storage. Every hop is a BAA-covered system. Nothing forks off to analytics tools, marketing platforms, or a model endpoint that logs prompts for training.

4. No training on your data

The AI model must run against an endpoint with a contractual no-training, zero-retention guarantee. If patient messages could become training data, that's a disqualifying leak.

5. Least-privilege access and audit logging

Only authorized staff should be able to read conversations, access should be logged, and the whole system should produce an audit trail your compliance officer can actually use — not just the vendor's SRE team.

6. A place in your Security Risk Assessment

The chatbot, its data flow, and its vendors must appear in a current SRA. The vendor's compliance covers their side; your risk analysis is still your responsibility.

Why off-the-shelf widgets usually fail this test

Most website chatbot builders were designed for e-commerce and lead capture, not healthcare. They'll happily sign up a medical practice, but when you ask for a BAA covering both the platform and the underlying model, ask where conversation data lives, and ask whether prompts are used for training, the answers fall apart. That's not a knock on the tools — they're just built for a different risk environment.

This is why healthcare chatbots are typically purpose-built: it's the only reliable way to control every hop in the data flow and sign BAAs across the whole chain.

The vendor questions to ask before you deploy

Will you sign a BAA, and does it cover both your platform and the AI model behind it?
Where is conversation data stored, and for how long?
Is any conversation data used to train or improve models — yours or the model vendor's?
Is the AI model accessed through a zero-retention, BAA-covered endpoint?
Who can access conversations, and is that access logged?
Can you provide an audit trail suitable for an OCR inquiry?
What happens to the data if we cancel?

If the honest answers to those seven questions aren't all reassuring, the chatbot doesn't belong on a medical practice's website — no matter how good the demo looks.

Done right, it's a genuine asset

None of this means practices should avoid chatbots. A compliant, well-built assistant handles intake, answers common questions, and routes patients around the clock — reducing front-desk load and capturing inquiries after hours. The difference between an asset and a liability is entirely in the architecture: BAA-covered, least-privilege, audited, and documented in your risk assessment.

Need a chatbot your compliance officer will sign off on?

We build custom, HIPAA-aware AI assistants inside a BAA-covered boundary — with security review led by a CISSP-certified practitioner.

HIPAA-Compliant Chatbots Chatbots & AI Assistants