Is Claude Code HIPAA Compliant?
Last reviewed November 11, 2026
Is Claude HIPAA compliant? For a healthcare team, the answer depends on the agreement you signed, how your developers sign in, and where they use Claude. To answer “is Claude Code HIPAA compliant?” for your team, check the developer’s organization and configuration before sharing real records.
Protected health information (PHI) is individually identifiable health information protected by HIPAA. A business associate agreement (BAA) governs how a business associate handles PHI on behalf of a regulated organization. Zero data retention (ZDR) limits Anthropic’s storage of inputs and outputs under an approved arrangement, subject to documented exceptions.
Imagine two people building a remote-monitoring MVP. They can test its appointment flow with fictional records. When a developer needs to investigate a bug using real patient data, the account, surface and local handling of that data become part of the decision.
Can my developers use Claude Code with PHI?
Yes, in specific setups. As of November 11, 2026, Anthropic’s BAA covers local Claude Code in the terminal and the Claude Desktop Code tab for qualifying Enterprise organizations that apply the HIPAA configuration. It also covers local Code under an approved zero data retention arrangement. For a commercial Console API key, the organization that issued it needs a signed BAA and ZDR. Anthropic’s Claude Code BAA excludes IDE extensions, third-party cloud routes, gateways, and local MCP servers and connectors.
Key takeaways
- Start with the two documented coverage paths. Confirm whether your organization will apply the Enterprise HIPAA configuration or use Anthropic-approved ZDR for Claude Code.
- Confirm where developers will use Code. The covered local surfaces include the terminal and eligible Desktop Code tab. IDE extensions and third-party provider routes fall outside Anthropic’s coverage.
- Review every MCP connection separately. Local MCP servers and connectors sit outside Anthropic’s BAA even when your local Claude Code session qualifies.
- Assess the app’s data flows separately. Your coding tool’s BAA covers a defined service. The app still needs its own safeguards, applicable agreements, and risk analysis.
Claude Code BAA coverage at a glance
Use Anthropic’s BAA feature table to check the organization and client your developers use. A request labeled “Anthropic BAA HIPAA” or “Claude BAA HIPAA” needs both details. Ask your account team to confirm the Anthropic BAA terms for that organization.
| Surface or login route | Status | Conditions |
|---|---|---|
| Terminal | Covered | Both routes require an applicable BAA. Use a direct Anthropic connection and Enterprise sign-in with the HIPAA configuration, or eligible local Code with approved ZDR. |
| Claude Desktop Code tab | Covered | Local Code on an eligible configuration. With the Enterprise HIPAA configuration, an Owner must re-enable the tab. |
| Cowork in Claude Desktop | Covered | The Enterprise HIPAA configuration must apply, and an Owner must turn Cowork back on. Code ZDR alone does not cover Cowork. |
| VS Code and JetBrains extensions | Not covered | Outside the BAA even with the HIPAA configuration. |
| Bedrock, Google Cloud, Microsoft Foundry | Not covered | Outside Anthropic’s Claude Code BAA. Review the provider agreement for the actual service and feature. |
| LLM gateway or custom base URL | Not covered | The Enterprise configuration requires a direct connection to Anthropic. |
| Console API key with ZDR | Covered | The commercial Console organization issuing the key needs a signed BAA and ZDR. |
| Console API key without ZDR | Not covered | The key’s organization lacks the required Code configuration. |
| Code cloud sessions, Remote Control and mobile Code | Not available | Unavailable with the HIPAA configuration. Cloud Cowork is also unavailable with it. |
| Local MCP servers and connectors | Not covered | Outside Anthropic’s BAA even when used from covered local Code. |
Coverage checked November 11, 2026.
Two ways to get coverage
Claude Enterprise with the HIPAA configuration
When a buyer asks “is Claude Enterprise HIPAA compliant?”, explain which services your organization will use and how you’ll configure them. An Anthropic HIPAA BAA and Enterprise seats alone don’t put Claude Code in the covered configuration.
An eligible organization with an Anthropic account team must enable HIPAA and accept the BAA. Its Primary Owner then applies the separate Claude Enterprise HIPAA configuration. It applies across the organization to Code and Cowork.
An Owner can re-enable the Desktop surfaces after the configuration takes effect. Review the HIPAA-ready Enterprise plans with your account team.
Zero data retention
When Anthropic enables Claude zero data retention for a qualified Enterprise organization, its developers have a separate path for local Code.
For covered Code use with a commercial Console API key, the organization that issued it needs an applicable Claude BAA and ZDR. The Console web UI falls outside that key-based coverage.
Check zero data retention scope and API and data retention for the scope and legal or misuse exceptions.
Runtime API and coding organization
If production uses the first-party HIPAA-ready Claude API and your developers use the first-party ZDR route for Code, Anthropic requires separate organization IDs. A single first-party API organization cannot have both settings. Confirm the scope of the agreement for each organization and keep developers’ coding credentials separate from the app’s runtime credentials.

How to set up Claude Code for a HIPAA-ready organization
Assign an administrator on your development team to configure Claude Code and test it on a managed machine. The steps below apply to the Enterprise configuration. Start with Anthropic's setup guide and confirm the organization is eligible with your account team.
Apply the configuration. The Primary Owner opens Organization settings → Data and privacy and applies the HIPAA configuration. An Owner then re-enables the Code tab for desktop users and enables Cowork separately if the team needs it. Use Claude Code v2.1.285 or later and Claude Desktop v2.19675.0 or later for those clients.
Allow the direct connection. The native terminal needs outbound HTTPS on port 443. Allow api.anthropic.com for requests and claude.ai, claude.com, and platform.claude.com for sign-in. Include sso.claude.com if you use SSO and downloads.claude.ai for native updates.
The guide lists mcp-proxy.anthropic.com for connectors. A connection to that host does not place the connected service under the BAA. Check Desktop and installer network requirements separately.
Lock down login and retention. In managed settings, use forceLoginMethod: "claudeai" and set forceLoginOrgUUID to your Enterprise organization’s UUID. Set allowedProviders: ["anthropic"] to restrict provider routing. Set cleanupPeriodDays according to your endpoint retention policy. Anthropic’s example uses 30 days. Apply the separate Desktop sign-in policy where needed and test your access controls.
Verify a developer session. Restart and run /status. Look for HIPAA on the Organization configuration line. The footer should show HIPAA configured, or HIPAA on v2.1.285.
The configuration disables WebFetch, cloud sessions, Remote Control and feedback commands. Web Search remains available. Claude Code removes Anthropic credentials from child commands, hooks and MCP servers. Review credentials for GitHub and cloud providers separately.

Plan for local files and offboarding. Sessions can leave data on the device. The startup cleanup sweep does not clear every local path.
To remove project transcripts and auto memory on v2.1.288 and later, run claude purge --all --yes. On v2.1.285 through v2.1.287, run claude project purge --all --yes. The purge leaves some data, including the paste cache.
When a developer leaves, revoke their seat and follow your managed-device wiping procedure. Signing out alone leaves local data behind.
What Anthropic’s BAA doesn’t cover
For an Anthropic HIPAA compliance review, inventory the tools developers actually turn on. The BAA excludes VS Code and JetBrains extensions, along with provider and gateway routes. It also excludes the GitHub integration, skills and plugins, fast mode, and OpenTelemetry exports. Keep PHI out of those paths.
Cloud sessions, Remote Control, mobile Code and cloud Cowork are unavailable with the configuration.
Anthropic HIPAA coverage for local Code leaves local MCP servers and connectors outside the agreement. If your team is connecting Claude Code to a HIPAA-compliant backend, assess the connected system and its data flows under their own agreements.
Claude Code through Bedrock, Google Cloud or Foundry
If your team needs “private HIPAA compliant Claude” access through a cloud account, ask which service, model, features, and signed agreement the offer covers. Anthropic’s Claude Code BAA and Enterprise HIPAA configuration do not apply to Code routed through AWS Bedrock, Google Cloud or Microsoft Foundry.
Amazon Bedrock appears on the AWS HIPAA-eligible services list. If your architecture still says Google Cloud Vertex AI, confirm the current Gemini Enterprise Agent Platform service and feature scope using Google Cloud HIPAA guidance.
For Foundry, check Microsoft’s HIPAA guidance and your exact deployment. Claude model API access in Foundry has separate eligibility rules from Claude Code through Foundry.
Covered Models and retention
Check which model your organization needs and how long its inputs and outputs can be retained. Under a Claude HIPAA BAA, Anthropic allows eligible Covered Models such as Fable 5 in local Code with the Enterprise HIPAA configuration. The Covered Models policy describes the default minimum 30-day retention and exceptions.
Covered Models under a BAA explains that these models are unavailable with Code ZDR unless Anthropic expressly authorizes access. If you get an exception, confirm the organization, model, surface, retention and BAA scope in writing before sending PHI.
Plans with no BAA path
To answer “is Claude AI HIPAA compliant?” for a subscription your developer already has, check what Anthropic covers on that plan. Free, Pro, Max, Ultra and Team do not offer the Enterprise HIPAA arrangement. For a coding workflow that receives PHI, the answer to “is Claude Pro HIPAA compliant?” is no.
Your developers can still work on a healthcare product using fictional fixtures. Before granting access, review what they send in prompts and attached files. Check source code and debugging logs too.
Do you need any of this? Keep PHI out of the coding workflow
For healthcare founders, the first decision is whether the AI coding assistant will see patient data. A non-technical founder can ask for a risk assessment that follows information from the developer’s device to the assistant and any connected service.

Prototype with fictional records. A digital health startup can build a working demo with synthetic data created without patient information.
If a health tech startup uses real records to create de-identified data, follow HHS de-identification guidance. It describes Expert Determination and Safe Harbor. Removing names from electronic health records is insufficient. The same principle applies in telehealth app development and mental health app development.
Launch an MVP with real PHI. Map production and developer data flows as part of healthcare app development. You may keep the coding workflow on fictional fixtures while production handles PHI. If real patient data must reach the assistant, document the eligible coding route, agreements, and data security safeguards first.
Covered entities and business associates should check HHS HIPAA enforcement when assessing HIPAA violation penalties and their obligations.
Prepare for hospitals and payers. When investors ask about due diligence or enterprise customers send a security questionnaire, show the relevant agreements, which organization each data flow uses, and who reviews audit logs and access. If your next task is connecting Claude Code to a HIPAA-compliant backend, use that same data-flow inventory to scope the app’s production layer.
Budget for the workflow, not just the seat
When you budget for Claude Code HIPAA compliance, compare the public plan price with a quote for the account your team needs. To estimate “Claude HIPAA compliant pricing,” count seats and usage. Allow for the time your team spends administering the setup.
On November 11, 2026, Claude pricing listed general Enterprise at US$20 per seat per month, billed annually, plus usage at API rates. HIPAA-ready Enterprise uses separate Chat and Chat + Code seats. Ask your account team for a quote for the seat types you need.
| Cost | What to estimate |
|---|---|
| Seats and model usage | Confirm the eligible seat type, minimum commitment, and who needs Code. Estimate usage from a small pilot. |
| Engineering and operations | Include managed settings, endpoint cleanup, access reviews, and time to market. |
| Production safeguards | Budget separately for app hosting, monitoring, risk analysis, and any additional agreements. |
Use these categories to compare routes against your startup budget.
Six decisions before your developers use Claude Code
Use this Claude HIPAA compliance checklist before a developer sends real patient information.
- Decide whether Code needs PHI. Start from what developers must send to do the job.
- Name the people and systems involved. Assign someone to maintain the data-flow inventory and use HHS risk analysis guidance to assess the workflow.
- Confirm the agreement and configuration. Record the applicable BAA and whether the organization uses the Enterprise HIPAA configuration or approved ZDR for Code.
- Name the eligible surface. Test the terminal or Desktop Code tab with the intended login. Keep PHI out of IDE extensions and connected services outside scope.
- Enforce the setup. Deploy managed settings, check the organization in
/status, and document cleanup and offboarding. - Record the evidence. Assign an owner and record the review date. Note what to recheck when Anthropic changes its models or features.
How Specode can help
If your Claude Code HIPAA review shows that developers can work on fictional records, keep using them while you plan the launch. Use Specode’s healthcare builder to prototype with synthetic records. Pro supports guided production deployment and migration. Custom adds a dedicated team for builds and integrations that need more hands-on work.
The Specode MCP works with Claude Code, Codex and Cursor. Use synthetic records with its development backend because that environment sits outside your BAA. The Specode homepage lists Basic at $250/month for security tooling.
Frequently asked questions
Yes, for eligible services. To answer “can Claude be HIPAA compliant?” for Claude Code, confirm the BAA, organization and approved Enterprise HIPAA configuration or ZDR route. Verify the local surface before sending PHI.
Yes, for eligible customers. Anthropic’s BAA covers local Code under a qualifying Enterprise HIPAA configuration. It also covers eligible local Code with approved ZDR. For a commercial Console API key, the issuing organization needs a BAA and ZDR.
Enterprise offers HIPAA-ready plans for eligible organizations. To cover local Claude Code through the configuration route, enable HIPAA, accept the BAA, and have the Primary Owner apply the separate HIPAA configuration. Confirm the eligible surfaces for your account.
Anthropic covers Cowork in Claude Desktop when the Enterprise HIPAA configuration applies and an Owner re-enables Cowork. Cloud Cowork is unavailable with that configuration. Code ZDR alone does not cover Cowork.
No. Anthropic excludes the VS Code and JetBrains extensions even when the organization has the HIPAA configuration. Use an eligible local terminal or Desktop Code tab if the work requires PHI.
Yes, for work that keeps PHI out of the tool. Pro and Max do not provide a BAA for Claude Code. Use fictional fixtures and check what developers might paste from production into prompts or logs.
If the coding tool only gets fully fictional records, it doesn’t receive PHI. If you derive examples from real records, assess the de-identification method before sharing them.
Anthropic’s Claude Code BAA does not cover the Bedrock route. AWS lists Bedrock as a HIPAA-eligible service. Confirm your AWS BAA, the specific deployment and feature scope, and your handling of any local data.
Local MCP servers and connectors are outside Anthropic’s BAA. When connecting Claude Code to a HIPAA-compliant backend, verify the connected service’s agreement and what data the integration sends before enabling it.








