HIPAA guide
HIPAA compliant chatbot: what it takes.
A chatbot is HIPAA compliant only when every part that touches patient data is covered. That means a signed business associate agreement (BAA) with the chatbot vendor and with the AI model provider behind it, no PHI sent to website tracking tags, and access controls and logging for chat transcripts. A BAA with one vendor does not cover the others.
Checked November 10, 2026. Not legal advice.
What has to be true before patient data goes in.
Sign a BAA with each vendor in the chain
The chatbot platform, the AI model provider and the host may each handle PHI. HHS says business associate contracts must require subcontractors with access to PHI to agree to the same restrictions.
Decide what the bot may ask
HHS says tracking tools on unauthenticated pages where people schedule appointments or use a symptom checker may have access to PHI. A bot that asks about symptoms is collecting health information, so limit questions to what the task needs.
Keep tracking tags off chat pages
Ad pixels and analytics on a page where patients type health details can send that information to the tag vendor. HHS says tracking vendors that receive PHI must sign a BAA.
Protect transcripts
The Security Rule asks for access control, audit controls and transmission security for ePHI. Apply a retention rule to chat logs and restrict who can read them.
Your options, and what each needs.
| OpenAI API | An organization admin accepts the BAA in the API Platform; self-serve needs established API usage, and OpenAI lists eligible endpoints such as /v1/chat/completions and /v1/responses. |
|---|---|
| Claude API or Claude Enterprise | The Primary Owner signs Anthropic's BAA for a HIPAA-ready organization or accepts it for Enterprise; some API features are outside it. |
| Amazon Lex and Bedrock on AWS | Accept the AWS BAA yourself in AWS Artifact; AWS lists Amazon Lex and Amazon Bedrock as HIPAA eligible services. |
| Salesforce Einstein Bots | Covered under the Salesforce Business Associate Addendum via your account representative, but Salesforce bars submitting PHI to or using PHI in Einstein Bots utterance records. |
Where this usually goes wrong
- Embedding a chat widget from a vendor with no BAA on a page where patients type symptoms
- Running ad pixels or analytics on the same page as the chat
- Storing transcripts indefinitely with no retention rule
- Assuming the AI model vendor's BAA also covers the chat widget or the host
This page reports what the vendor publishes and is not legal advice. Vendors change their terms, so check the sources below before you rely on it.
HIPAA compliant chatbot: common questions.
Can an AI chatbot book appointments for a clinic?
Yes, if every vendor that touches patient details has a BAA and the setup follows each vendor's HIPAA configuration. Check what the page tracks and what the bot stores before launch.
Does HIPAA require encryption of chat messages?
The Security Rule's transmission security standard requires technical measures to guard against unauthorized access to ePHI sent over a network. HHS lists encryption as an addressable specification, which means you assess it, document your decision and implement what is reasonable.
Questions people search
Can I use ChatGPT or Claude as a HIPAA-ready website chatbot?
Only through the routes that have a BAA, and the widget and host need coverage too. OpenAI accepts a BAA for its API, and Anthropic for the Claude API and Enterprise plans. Plans with no BAA available, such as ChatGPT Business or Claude Team, cannot hold patient information. A BAA with the model provider does not cover the widget.
Does the page a chatbot sits on change the HIPAA risk?
Yes. HHS warns that tracking tools on public pages where people book appointments or use a symptom checker may reach patient information. An ad pixel or analytics tag on the same page as the chat can send what a visitor types to the tag vendor, so keep tracking tags off those pages unless a BAA covers them.
What does a HIPAA-ready chatbot cost?
HIPAA-Ready Essentials costs $1,500 to set up, then $699 a month for one location. It is the compliance layer: it puts your chat assistant and text reminders on HIPAA-eligible services under a signed BAA chain, with usage billed at standard rates. A voice agent is a separate add-on. A compliance consultation comes first, and Keegan Justis designs it while only Mike Golliet and Kyle Grenier build it.
Can a chatbot ask patients about symptoms?
A bot that asks about symptoms is collecting health information, so the minimum necessary standard applies: ask only what the task needs. For booking, that can be a name, a phone number and a time. Anything clinical should pass to your staff. Restrict who can read the transcripts and set a retention rule for them.
- HHS: Business Associate Contracts (sample provisions)
- HHS: Use of Online Tracking Technologies by HIPAA Covered Entities and Business Associates
- HHS: Summary of the HIPAA Security Rule
- HHS: HIPAA Security Series 4, Technical Safeguards
- Salesforce: Business Associate Addendum and HIPAA Covered Services restrictions
- HubSpot Knowledge Base: Store sensitive data in HubSpot
- AWS: HIPAA Eligible Services Reference
More HIPAA guides
Find out what AI says about you.
A free 20-minute call. We ask the assistants your customers' questions and show you where you come up today.
No pitch unless you ask for one.