The short answer
No AI model is HIPAA compliant by itself. HIPAA applies to covered entities and their business associates, and compliance depends on how protected health information is handled. The useful question is whether Anthropic will sign a business associate agreement for the way you plan to use Claude, and what you must configure to stay inside it.
As of November 2026, Anthropic's published documentation says it offers a BAA for what it calls HIPAA ready services. These include its first party API through a HIPAA ready API organization and HIPAA ready Claude Enterprise plans. Consumer plans are not among those services, and neither are features Anthropic lists as excluded.
What the Anthropic BAA covers
Anthropic's help center lists covered features in detail, and the list changes over time, so treat it as the source of truth rather than any summary, including this one. At the time of writing, the documentation describes coverage for core chat features on HIPAA ready Enterprise plans, such as chat, projects in chat and artifacts in chat, once an organization owner activates HIPAA settings and accepts the BAA.
For the API, the documentation describes BAA coverage for a HIPAA ready API organization and lists which API features are eligible. Some API features and beta products are listed as not covered. Third party connectors and MCP integrations are described as outside the BAA, because data flows to another vendor.
Claude Code and Cowork have their own conditions. Anthropic describes coverage only in local mode on HIPAA ready Enterprise plans with a specific HIPAA configuration applied, and it lists cloud sessions as not covered.
Claude through cloud providers
Claude is also available through cloud platforms such as Amazon Bedrock. In that case your agreement is usually with the cloud provider, and you rely on that provider's list of HIPAA eligible services and its BAA. AWS lists Amazon Bedrock among its HIPAA eligible services. Confirm the current list and your signed agreement before sending PHI.
What your organization still has to do
A BAA is necessary but not sufficient. You still need to include the use in your security risk analysis, limit access through single sign on and roles, decide what data may be entered, set retention to match your policies, and train staff on what is and is not allowed.
You also need to make sure people use the covered workspace. A clinician who pastes notes into a personal Claude account is outside your BAA no matter what your enterprise agreement says. Clear acceptable use rules and approved alternatives reduce that risk.
A practical checklist
Confirm the exact product, plan and features you will use. Get the BAA executed and stored with your compliance records. Apply every configuration the vendor requires. Turn off or block features that are not covered. Route access through your identity provider. Log usage where your policy requires it. Review the vendor's documentation at least quarterly, because coverage lists change.
Selah Digital is an Anthropic partner and SOC 2 Type 2 certified (2025 report). We help healthcare organizations choose eligible configurations and set up the controls around them, but we are not your lawyers, so involve your privacy officer and counsel in the final decision.