HIPAA and AI chat widgets: what your practice needs in place
If patients can type names, symptoms or appointment details into a chat widget on your site, the vendor is very likely handling protected health information for your practice, and HIPAA calls for a signed business associate agreement before that happens. A privacy policy notice, a promise to strip identifiers, or encryption on its own does not replace the agreement.
When a chat widget becomes a HIPAA question
HIPAA protects health information that identifies a person. A chat box on a practice website collects exactly that, usually within the first message. A typical opener reads something like "Hi, my name is Dana, I need to see someone about my knee." A name plus a reason for seeking care is identifiable health information, and HHS has said that such information collected on a covered entity's website generally counts as protected health information even when the person is not yet a patient.
HHS comes close to naming this case directly. Its list of business associate examples includes a third party chatbot on a provider's patient portal that handles patients' information for services such as symptom assessment, reminders and appointment scheduling. A chat widget on your public website that collects the same information is doing the same job. A vendor that creates, receives, maintains or transmits protected health information on your behalf is a business associate, and you need a business associate agreement before you disclose that information to it.
A bot that only shows buttons for hours and directions, with no free text box, may never receive anything identifiable. Most AI chat is the opposite: it invites people to type, and they will.
This page is general information, not legal advice. Your compliance officer or a healthcare attorney should review the specific tool and contract.
What the agreement has to cover
A business associate agreement is not a formality. HHS describes what it must do:
- Spell out what the vendor may and may not do with the information
- Bar any other use or disclosure, except as the agreement allows or law requires
- Require the vendor to safeguard the data under the Security Rule
- Require the vendor to report security incidents, including breaches, to you
- Require the vendor to return or destroy the information when the contract ends, where feasible
The chain matters too. A business associate must have its own agreement in place with any subcontractor that handles the data for your practice. An AI chat product often depends on a hosting company and a separate AI model provider. Ask which subcontractors touch your transcripts and whether each one is covered.
One exception gets misread. The conduit exception covers services that only transmit information, like a courier, with at most temporary storage. HHS says it does not apply to entities that access the information regularly to perform a service. A chat vendor that stores, reads and processes conversations is not a conduit.
Does ChatGPT recommend your practice?
The Surge Score measures five things about your practice website: how often ChatGPT, Gemini and Perplexity recommend you, your PageSpeed, your structured data, your indexing and your reviews, each with its evidence and date. Free.
Three substitutes that do not work
Practices sometimes hear that they can skip the agreement. Be wary of these three arguments.
"It is covered in our privacy policy." In its guidance on online tracking, HHS says a covered entity cannot disclose protected health information to a tracking vendor based only on telling people about it in a privacy policy or terms of use.
"The vendor removes identifiers before saving anything." The same guidance says it is not enough for a tracking vendor to agree to remove or de-identify the information after receiving it. The agreement still has to be in place. That guidance was written about tracking vendors, and it is sensible to apply the same reasoning to a chat vendor that receives the raw conversation.
"Everything is encrypted." HHS cloud guidance says a provider that stores only encrypted health information, even without the key, is still a business associate. Encryption reduces risk. It does not change the vendor's status.
A banner asking patients not to type health information does not solve the problem either. Patients type it anyway, because they came to ask about their health.
The second vendor hiding inside the chat
Many chat tools report events to analytics or advertising platforms: chat opened, lead captured, appointment requested. Some pass along the page address or parts of the conversation. Session replay scripts, which HHS describes as recording mouse movements, clicks and typing, can capture a chat as it is written.
HHS guidance says tracking on public pages where people schedule appointments or use a symptom tool may reach protected health information, and that a tracking vendor receiving it is a business associate. In 2024 a federal court vacated one part of that guidance, about pairing an IP address with a visit to a public page about a health condition. Information a patient types to request care is a different situation, so do not read that ruling as permission to send chat content to ad platforms.
If your marketing reports count chat leads, have them counted without the content of the conversation. See tracking technology and patient privacy and HIPAA safe analytics.
A twenty minute check of the chat you have now
You can learn most of what you need this afternoon.
- Find the contract or online terms for your chat tool and search for the words business associate. If there is no signed agreement, call the vendor today.
- Ask the vendor in writing which subcontractors receive transcripts, including any AI model provider, and whether each is covered by an agreement.
- Ask your web person to open your site with the browser's developer tools showing network traffic, start a chat using an obviously fake name and reason, and list every outside domain that receives data. Anything other than the chat vendor needs an explanation.
- Find out where transcripts are stored, who on your team can read them, and how long they are kept.
- Check whether chat leads are sent to Google, Meta or other ad platforms as conversions, and what the event contains.
- Add the tool to your HIPAA risk analysis, the same way you would a new EHR module.
If step 1 or step 3 turns up a problem, turn off free text entry until it is fixed.
Questions to settle before launch
A signed agreement is the floor. These configuration and contract questions decide how much risk you are actually carrying:
- Training. Is your patients' conversation data used to train models for the vendor or its other customers? Get the answer in the contract, not a sales email.
- Retention. How long are transcripts kept, and can you set a shorter period or delete on request?
- Location. Where is the data stored and processed? HHS notes that storing health information overseas can raise its own risks to weigh in your risk analysis.
- Access. Which vendor staff can read transcripts, and is that access logged?
- Minimum collection. The chat should ask only for what the task needs. Scheduling rarely needs a Social Security number or a full insurance member ID in the first message.
- Destination. Transcripts that matter clinically or administratively should land in your EHR or front desk queue, not sit in a vendor dashboard.
For the bigger picture on what does and does not apply to your website, see HIPAA on your website. For what chat should and should not say, see AI chat on a medical website.
Checklist
- A business associate agreement with the chat vendor is signed before patients use the tool
- Subcontractors that touch transcripts, including the AI model provider, are named and covered
- No analytics, ad pixel or session replay script receives chat content
- Transcript retention, location and deletion terms are written into the contract
- The chat asks only for the details needed to book or route a request
- The tool is listed in your HIPAA risk analysis
Frequently asked
Do I need a business associate agreement for a chatbot that only answers general questions?
If the bot has a free text box, assume patients will type identifying health details into it, and treat the vendor as a business associate. A purely button based bot that never accepts typed messages may not receive protected health information, but confirm that with your compliance lead rather than assuming.
Is a HIPAA compliant badge on a vendor's website enough?
No. A badge is a marketing claim. What protects your practice is a signed business associate agreement, the right subcontractor coverage, and a configuration on your site that does not leak conversations to other tools. Ask for the agreement and read it.
What if my chat vendor will not sign a business associate agreement?
Then it should not receive patient information. Either switch to a vendor that will sign, or limit the tool to fixed buttons with no typed input and send patients to a secure form, your phone line or your scheduler for anything personal.
Can chat transcripts go into the medical record?
They can, and for anything clinically relevant they often should, so the care team sees what the patient said. Decide which conversations get filed, who reviews them, and how they reach the chart, rather than leaving them in the vendor's system by default.
Sources
- Business Associates Frequently Asked Questions, U.S. Department of Health and Human Services
- Guidance on HIPAA and Cloud Computing, U.S. Department of Health and Human Services
- Use of Online Tracking Technologies by HIPAA Covered Entities and Business Associates, U.S. Department of Health and Human Services, Office for Civil Rights
Book a strategy call with the team.
Twenty minutes. We'll walk through the specific opportunities in your market and what a MedPracticeGrowth engagement would look like for your practice.