Key takeaways
- You can use AI with HIPAA data, but only through specific enterprise channels with a signed Business Associate Agreement (BAA). The consumer apps cannot be used with protected health information.
- ChatGPT.com, Claude.ai, and the Gemini app are off-limits for PHI. The enterprise APIs from Anthropic (Claude) and OpenAI, plus Azure OpenAI and Google Vertex AI, will sign a BAA and can be used.
- A compliant model is necessary but not sufficient. The data has to reach it through a compliant pipeline, and the vendor must agree not to train on your data.
- Used correctly, AI on PHI is genuinely useful: summarizing case notes, triaging intake, drafting communications, extracting data from documents, all with a human reviewing the output.
This is one of the most common questions I get from healthcare and home care teams right now, and it’s usually asked with a wince: “Can we even use ChatGPT for this, or is that a HIPAA problem?” The honest answer is more nuanced than yes or no.
So, is ChatGPT HIPAA compliant? The consumer version at ChatGPT.com is not, and you cannot put protected health information into it. But OpenAI’s enterprise API will sign a BAA, and so will Anthropic for Claude. So the real answer is: yes, you can use AI with HIPAA data, but only through the right door, with the right contract, and with the data flowing through a compliant pipeline. Use the wrong door and it’s a violation, even if the model itself is excellent.
Here’s how to tell the difference, vendor by vendor, and what you can actually build once you’re set up correctly.
Where the AI vendors stand
| Tool | Can it touch PHI? | Through what | The thing that catches people |
|---|---|---|---|
| ChatGPT.com (incl. Plus) | No | — | The brand signs a BAA, this product is not covered by it |
| OpenAI API | Yes | Enterprise agreement | Zero-retention has to be requested, not assumed |
| Claude.ai consumer app | No | — | Same brand as the API below, different answer |
| Anthropic API | Yes | Enterprise agreement | Coverage is the API, not the chat product |
| Gemini app | No | — | |
| Google Vertex AI | Yes | Google Cloud BAA | Only HIPAA-eligible services are covered |
| Azure OpenAI | Yes | Microsoft BAA | Usually the cleanest route for Microsoft shops |
| Consumer Copilot | No | — | “Copilot” names several products with different answers |
The pattern worth reading off that table: the brand name never tells you the answer. Every vendor in the “yes” column also sells a product in the “no” column, usually under the same name.
Why are the consumer apps off-limits?
The reason isn’t that the AI is unsafe. It’s contractual and architectural.
HIPAA requires a Business Associate Agreement with any vendor that handles protected health information (PHI) on your behalf. The consumer products, ChatGPT.com, Claude.ai, and the Gemini app, do not come with a BAA. That alone makes them non-compliant for PHI, regardless of how secure they are.
There’s a second problem with consumer tools: data handling. Consumer tiers may retain your inputs and, depending on settings, use them to improve the models. The moment patient data goes into a system that might train on it or retain it outside a compliant boundary, you’ve lost control of it in a way HIPAA doesn’t allow.
So the rule is simple: no PHI in any consumer AI app, ever. Not in ChatGPT, not in Claude.ai, not in the free Gemini or Copilot apps. If a team member is pasting patient details into ChatGPT to “draft a quick note,” that’s a breach waiting to happen, and it’s worth a clear internal policy.
What makes an AI tool HIPAA compliant?
Three things have to be true before AI can touch PHI:
- The vendor signs a BAA. This is the gate. No BAA, no PHI. (See our full explainer on BAAs.)
- You use a HIPAA-eligible product or tier. A vendor’s BAA usually covers specific products, not everything they offer. The enterprise API is covered; the consumer app on the same brand is not.
- Your data isn’t used for training. The agreement has to confirm your inputs won’t be used to train the model. Enterprise API agreements typically guarantee this; consumer terms typically don’t.
And one that catches people: the BAA has to cover the whole path the data takes, not just the model. If PHI passes through an automation tool, a database, or an email service on its way to or from the AI, each of those needs its own BAA too. One unsigned link breaks the chain.
Is ChatGPT HIPAA compliant?
Not the one you are thinking of. ChatGPT.com is not usable with PHI on any consumer tier, including Plus. There is no BAA covering it, and no setting inside it changes that.
OpenAI does sign, for the API under an enterprise agreement, with a zero-retention option available. That is a genuinely different product that happens to share a brand: different contract, different data handling, different answer.
So “is ChatGPT HIPAA compliant” has no single answer, and that is the entire trap. A team that hears “OpenAI signs BAAs” and starts pasting intake notes into the chat window has just breached, using a vendor that would have covered them one door over.
Is Claude HIPAA compliant?
Same split, same trap. The Claude.ai consumer app carries no BAA and must not receive PHI. Anthropic signs for its API under the appropriate enterprise agreement.
We build with Claude for compliance-heavy clients for exactly that reason: the API path is covered, documented, and behaves predictably about retention. The consumer app is a different product wearing the same name.
Is Gemini HIPAA compliant?
The Gemini app is not covered and must not receive PHI. Google Cloud Vertex AI, which serves the same underlying models, is covered under Google Cloud’s BAA for its HIPAA-eligible services.
Note the qualifier, because it does real work: the BAA covers HIPAA-eligible services, not everything in Google Cloud. Confirm the specific service you are calling is on that list before routing anything through it.
Is Microsoft Copilot HIPAA compliant?
This one needs the most care, because “Copilot” is a name Microsoft has attached to several different products. The consumer Copilot app is not usable with PHI.
Copilot offerings tied to a covered Microsoft 365 or Azure agreement under Microsoft’s BAA can be, depending on the specific product. Azure OpenAI Service is covered, and for teams already inside the Microsoft ecosystem it is usually the cleanest route.
Before you rely on any of it, establish which Copilot you actually mean and confirm the BAA scope in writing.
Vendor policies here move faster than anywhere else on this site. Confirm current terms in writing before you route PHI anywhere. Checked August 2026.
What you can actually do with AI on PHI
Once you’re set up correctly, the use cases are real and valuable. The ones we see deliver the most for healthcare and home care operations:
- Summarizing case notes and documents. Turn long intake packets, evaluations, or visit notes into structured summaries a clinician or case manager reviews.
- Intake triage and data extraction. Pull structured fields out of messy referral documents, faxes, and forms so they land in your system without manual re-keying.
- Drafting communications. Generate first drafts of client updates, status messages, or internal summaries, with a person approving before anything sends.
- Decision support. Surface the relevant history or flag the missing document, so the human makes a faster, better-informed call.
The constant across all of these: a human reviews the output. AI on PHI works as an assistant that drafts and surfaces, not an autonomous system that acts on patient data unsupervised. That’s both good practice and good risk posture.
The catch: a compliant model doesn’t make your pipeline compliant
This is where teams get a false sense of safety. You sign a BAA with Anthropic or OpenAI, and you assume you’re covered. But the model is one stop on the data’s journey.
Walk the actual flow. PHI leaves your database, maybe passes through an automation tool to get formatted, hits the AI API, comes back, and gets written somewhere or emailed to someone. Every one of those stops handles PHI, and every one needs its own BAA. The automation glue is the usual leak: tools like Zapier don’t sign BAAs, so routing PHI through them to reach a compliant model breaks compliance before the model ever sees the data.
So the right mental model is: a compliant AI vendor is necessary, not sufficient. You need the BAA with the model and a compliant path to and from it. The platform holding that data has to sign too, and most no-code tools will not. We lay out the full stack, layer by layer, in our guide to building a HIPAA compliant portal.
Frequently asked questions
Can I use ChatGPT Plus if I just don’t include names?
Risky and usually not worth it. PHI is broader than names, and de-identification done by hand is error-prone. The safe path is the enterprise API under a BAA, not careful pasting into a consumer app.
Does a BAA mean my data is private from the AI vendor?
A proper enterprise agreement confirms your data isn’t used for training and is handled under HIPAA terms. That is exactly why the BAA and the eligible tier matter: they are what create that guarantee.
Which AI vendors will sign a BAA?
As of August 2026: OpenAI for its API, Anthropic for its API, Google Cloud for Vertex AI’s HIPAA-eligible services, and Microsoft for Azure OpenAI. None of the consumer chat apps from those same companies are covered.
We’re a small practice. Is this realistic for us?
Yes. The enterprise API tiers are accessible, and the setup is mostly a one-time configuration. The harder part is usually the pipeline around the model, which is the part worth getting help with.
If you want to use AI on protected data without tripping a violation, the work is in designing the pipeline, not just picking the model.
That's the core of our [AI implementation work for compliance-heavy businesses](/services/ai-implementation), and it's what we build into [HIPAA-aware systems for healthcare and home care teams](/industries/healthcare). Start with the [BAA explainer](/blog/what-is-a-business-associate-agreement) and the [HIPAA portal guide](/blog/how-to-build-a-hipaa-compliant-portal), or [book a call](https://cal.com/catalytics-automation/catalytics-intro) and we'll map what your specific setup would need.