If you work with healthcare clients — or you are a covered entity or business associate yourself — sooner or later somebody is going to ask whether they can run protected health information through Claude. The answer involves a Business Associate Agreement, and the details matter more than the headline.
Short answer: yes, but only for specific products, and only after you turn it on
Anthropic does provide a BAA covering what it calls its “HIPAA-ready” services — the first-party Claude API, Claude in Microsoft Foundry, and Enterprise plans. What it does not do is cover consumer plans. Team plans and individual plans (Free, Pro, and Max) can’t enable HIPAA at all.
One of the things that’s important to understand here: a BAA with Anthropic is never on by default, even on Enterprise. Somebody has to go flip the switch.
How you actually get it
For Enterprise plans, this is now self-serve, which is a nice change from the old sales-and-legal dance:
- The Primary Owner — not just any Owner or Admin — signs in and goes to Organization settings > Data and privacy > HIPAA Compliance.
- Download and review the BAA, then the Implementation Guide.
- Click “Accept and enable HIPAA.” That click-to-accept is execution of the BAA — there’s no separate document to sign and return.
For the API, it’s a little different. Your Primary Owner signs a BAA and then has to contact your Anthropic rep or sales team to actually get PHI processing turned on.
The caveats, and there are several
This is where professional skepticism matters. The BAA is not a blanket.
- It’s a one-way door. Enabling HIPAA resets certain org settings back to defaults, and the change can’t be reversed from organization settings. Test your workflows first.
- The self-serve BAA is take-it-or-leave-it. It’s a standard agreement that can’t be modified. If your legal counsel wants redlines, you’re going through an account team.
- Covered does not equal available. Anthropic’s own tables distinguish three states: covered by the BAA, available but not covered, and disabled. Chat, projects, artifacts, voice, web search, and research are covered. But connectors/MCPs, Enterprise Search, Claude in Chrome, and Skills are usable while not being covered — meaning your people can happily pipe PHI into an uncovered feature and you’ve got a breach, not a compliance program.
- API feature gaps. The Batch API, Files API, Skills API, Code Execution, and Web Fetch are not covered and aren’t accessible to HIPAA-ready API orgs at all. If your developers built around Batch for cost reasons, that’s a redesign.
- Claude Code and Cowork need a second step. Enabling HIPAA alone doesn’t bring them under the BAA — the Primary Owner has to separately apply a HIPAA configuration to local mode, and that configuration is currently only available to orgs with an Anthropic account team. Without it, Claude Code is covered only if you have zero data retention enabled, which is limited to qualified accounts.
- Old BAAs don’t travel. If you signed an API BAA before December 2, 2025, it covers API usage only and does not extend to the HIPAA-ready Enterprise plan — you need a new agreement. Agreements signed after that date can cover both.
What I’d tell a client
The reality is that signing the BAA makes Anthropic a compliant business associate. It does not make your implementation compliant. Access controls, audit logging, workforce training, minimum necessary, retention and discovery — all of that stays squarely on your side of the table.
Practical next steps:
- Pull the Implementation Guide for HIPAA Entities from Anthropic’s Trust Center. It’s the authoritative, feature-by-feature list, and you’ll need to request access to view it. Read it before you click accept.
- Inventory which Claude surfaces your people actually use today. Chat is easy. Connectors, Chrome, and Claude Code are where things get sideways.
- Turn off or restrict every “available but not covered” feature, then write a short internal policy that says in plain English where PHI may and may not go.
- Update your HIPAA risk analysis and your vendor list. An auditor will ask.
- If you’re a CPA firm doing work for covered entities, remember you may be a business associate yourself. Your downstream BAA obligations don’t disappear because your AI vendor signed one.
The key takeaway
Anthropic will sign a BAA, and on Enterprise it’s a few clicks away — but it’s irreversible, it’s unmodifiable in self-serve, and it covers a defined subset of features. Read the Implementation Guide, lock down the uncovered features before you enable, and don’t mistake a vendor’s signature for a compliance program.
Sources
Information current as of November 5, 2026. Vendor compliance terms change — verify against the live articles before relying on this. This post is general information, not legal advice.
