HIPAA-compliant AI tools: which vendors will sign a BAA?

No AI tool is "HIPAA compliant" on its own. HIPAA compliance is a property of your organisation and the contracts it holds — and the contract that matters here is the Business Associate Agreement. A BAA is the gate, not the security posture. A vendor can hold SOC 2 Type 2, ISO 27001, and a spotless breach record, and still be the wrong place for protected health information, because none of those documents put the vendor on the hook for HIPAA obligations. The BAA does.

So the useful question is not "is this tool HIPAA compliant." It is: will this vendor sign a BAA covering the specific service, on the specific plan, that my people are actually using? That is what the table below answers for all 26 tools in the directory, with the vendor document behind each answer.

What each status means

• Yes — The vendor publicly documents that it signs BAAs covering the service.
• Enterprise- or plan-dependent — A BAA exists, but only on certain plans or by request — and feature coverage still has to be confirmed in writing.
• Not publicly documented — We could not verify a BAA from a primary source. Treat as "no BAA" until you hold a signed one.
• No — No BAA is available for this product or plan. PHI must not go near it.
• N/A — not a PHI system — The vendor does not offer the product for processing protected health information at all.

BAA status for 26 AI tools

Status assessed 29 July 2026. Each tool page carries its own assessment date and the full source list.

The three mistakes that actually cause the problem

1. Treating a certification as a substitute for a contract

This is the most common one, and it is usually made by someone technical and well-intentioned. A SOC 2 Type 2 report describes how a vendor operates its controls over a period of time. It says nothing about whether the vendor has accepted HIPAA obligations toward you, whether it will report a breach to you on HIPAA’s timeline, or whether it will restrict downstream use of PHI. Only the BAA does that. Certifications are evidence a vendor is competent; the BAA is evidence they are accountable.

2. Assuming the BAA covers the AI feature

Several vendors here support a BAA at the platform level while saying much less about the AI features layered on top. A BAA covering a productivity suite is not automatically a decision about an AI assistant that reads across that suite, and a vendor may enumerate specific AI features as covered while leaving others out. When you ask for the BAA, ask in the same email which named features it covers — and keep the answer.

3. Writing the policy for the tools on the BAA list, not the ones people use

The consumer-tier general assistants are, by a wide margin, where PHI actually leaks: someone pastes a patient message in to soften the wording, or a meeting bot auto-joins a clinical call because it auto-joins everything. Those tools sit at the bottom of this table for a reason. A HIPAA-aware AI policy has to name them explicitly and give staff an approved alternative for the same task, or the rule loses to convenience.

How to use this table

Take the rows marked Yes or Enterprise- or plan-dependent as your candidate list, not your approved list. For each candidate, get the signed BAA, confirm the plan and the named features it covers, and only then write it into your policy as permitted for PHI. Everything marked Not publicly documented should be treated exactly like No until a signed document says otherwise — the absence of a published BAA route is not a technicality you can argue around after an incident.

Frequently asked questions

Which AI tools are HIPAA compliant?

Strictly speaking, none — HIPAA compliance is a property of an organisation and its contracts, not of a software product. What varies between vendors is whether they will sign a Business Associate Agreement covering the service you intend to use. Of the 26 tools tracked here, 10 publish a BAA route (some only on specific plans or by request), 7 do not publicly document one, 8 state or clearly indicate they do not offer one, and 1 are not offered for PHI at all.

Does a SOC 2 report mean a tool is safe for PHI?

No. A BAA is the gate, not the security posture. A vendor can hold SOC 2 Type 2, ISO 27001 and every certification on the market and still be the wrong place for protected health information, because what makes PHI processing lawful for a covered entity or business associate is the contract that assigns HIPAA obligations to the vendor. Certifications tell you how carefully a vendor runs its systems; a BAA tells you who is legally on the hook when something goes wrong.

The vendor says it is “HIPAA compliant” on its marketing page. Is that enough?

No. Treat a marketing claim as a signal that a BAA route probably exists, then go and get the signed BAA — and check which plan and which features it covers. Several tools here support a BAA only on an enterprise plan, and at least one vendor covers specific AI features rather than the whole product. Until you hold the signed document naming the service you actually use, assume you are not covered.

What should our AI policy say about PHI?

Name the rule in one line: no protected health information may be entered into any AI tool that is not covered by a signed Business Associate Agreement held by the company, and list the tools that are. Then name the failure mode people actually hit — pasting a patient message into a general assistant to “clean up the wording,” or letting a meeting bot join a clinical call. The tools your staff reach for by default are almost never the ones on the BAA list.

Keep reading

• AI policy for healthcare teams: HIPAA, shadow AI, and what a policy has to cover →
• The full AI Tool Risk Directory — tier verdicts for all 26 tools →
• Check your existing AI policy for gaps in 30 seconds →
• Score your company’s shadow-AI exposure →