Free resource · checked Nov 22, 2026

HIPAA compliant AI tools: is ChatGPT or Claude HIPAA compliant?

ChatGPT and Claude are HIPAA compliant only on plans where the vendor signs a Business Associate Agreement (BAA) and you switch on the right settings. ChatGPT Business and Claude Team do not offer a BAA. The matrix below shows every tool and plan, checked against each vendor's own page.

  • The matrix: AI tools and plans, BAA yes or no
  • Admin switches to turn on, by vendor
  • Where the BAA boundary sits when AI touches your EHR
  • 8-step rollout and a one-page staff policy

ISO 27001:2022 certified4.7 on Clutch (12 reviews)We sign BAAsSOC 2 in progressTrust center

Need it built into your product? See our HIPAA compliant software development and AI agents for healthcare.

What is inside

9 pages, sent to your inbox

The PDF holds everything on this page in a printable form, plus the engineering notes.

AI Tools BAA Matrix page 2 previewAI Tools BAA Matrix page 3 previewAI Tools BAA Matrix page 4 previewAI Tools BAA Matrix page 5 previewAI Tools BAA Matrix page 6 preview

The short answers

The short answers

Which AI tools sign a BAA in 2026?

OpenAI signs for ChatGPT Enterprise, Edu, ChatGPT for Healthcare and the API. Anthropic signs for Claude Enterprise after the owner enables HIPAA, and for HIPAA-ready API orgs. Microsoft covers Microsoft 365 Copilot by default. Google covers Gemini in Workspace and the generative AI services on its Google Cloud covered list. AWS covers Bedrock. Sources: each vendor's HIPAA page, linked in the matrix.

Is ChatGPT Business or Claude Team HIPAA compliant?

No. OpenAI says it does not offer a BAA for ChatGPT Business (OpenAI help article 8660679), and Anthropic says Team and individual plans cannot enable HIPAA (Claude help article 13296973).

Is a BAA enough?

No. Features outside the BAA (connectors, web search, memory) stay uncovered, and you still need access control, audit logs, a risk analysis and a staff policy under 45 CFR 164.308(a)(1)(ii)(A), 164.308(a)(5)(i), 164.312(a)(1) and 164.312(b).

The matrix

AI tools BAA matrix: which plans sign a BAA

A tool is safe for patient data only on a plan where the vendor signs a BAA, with the settings in the third column. Each row links to the vendor page it came from. A tool that is not listed is not covered by this page: ask that vendor for a BAA in writing.

Tool and planSigns a BAAWhat you must set, and what is not coveredPrice noteSource
OpenAI
ChatGPT Free / PlusNoNot eligible.n/aVendor page
ChatGPT Business (was Team)NoOpenAI: "We do not offer a BAA for ChatGPT Business."n/aVendor page
ChatGPT Enterprise / EduEnterprise onlyThrough sales. Excluded: improved memory, internet in Canvas, browser use in the cloud, scheduled tasks and more.Not publicVendor page
ChatGPT for Healthcare / for CliniciansYesSales-led (Healthcare) or in-product flow (Clinicians). Same feature exclusions.Not publicVendor page
OpenAI APIYesSelf-serve switch after API history. Needs Modified Retention. Cannot be turned off. Only listed endpoints.UsageVendor page
CodexYes, with setupCovered with an eligible ChatGPT account. The BAA does not cover running the Codex local client on your machines.With planVendor page
Anthropic
Claude Free / Pro / Max / TeamNo"Team plans and individual plans can't enable HIPAA."n/aVendor page
Claude EnterpriseYes, with setupPrimary Owner must switch on HIPAA and accept the BAA. Excluded: connectors and MCP, Enterprise Search, Claude in Chrome, Skills, mobile app, Docs/Slides/Design betas.Not publicVendor page
Claude APIYesHIPAA-ready org through sales. Covered models need 30-day retention, not zero data retention. Batch, Files and Skills APIs not covered.UsageVendor page
Claude CodeYes, with setupEnterprise sign-in with the HIPAA configuration, or an API key with zero data retention. Cloud sessions and gateways not covered.With planVendor page
Claude CoworkPartlyDesktop local mode with HIPAA configuration only. Cloud mode and connectors not covered.With planVendor page
Google
Gemini in Workspace / Gemini app (work)YesUnder the Workspace BAA. Some features are blocked once signed. Third-party add-ons not covered.Workspace priceVendor page
Google Cloud generative AI (Agent Platform)YesGoogle Cloud BAA. Google's covered-services list names "Generative AI on Agent Platform", "Gemini Enterprise Agent Platform" and "Vertex AI Workbench instances".UsageVendor page
Gemini Developer API / AI StudioNoNot on Google Cloud's covered-services list.n/aVendor page
Microsoft
Microsoft 365 Copilot / Copilot Chat (work)YesBAA by default in the Product Terms. Web search queries are not covered: turn off web grounding for PHI work.LicenseVendor page
Azure OpenAI / AI FoundryYesAzure BAA by default in the Product Terms.UsageVendor page
AWS
Amazon BedrockYesHIPAA eligible (list updated Nov 16, 2026). Accept the BAA in AWS Artifact.UsageVendor page
Healthcare app builders
SpecodeYes, with setupPlatform BAA after a $3k penetration test; hosting BAA with Convex.From $250/moVendor page
Knack HIPAAYesBAA with all HIPAA plans.From $159/moVendor page
BlazeYesProduction plan and up. Sandbox is no PHI.From $750/moVendor page
VertiComplyYesBAA on request on paid plans.From $89/moVendor page
App builders and hosting
v0 (Vercel)NoVercel API Terms forbid processing PHI through v0.n/aVendor page
Vercel hostingYesSelf-serve add-on on Pro.$350/mo + $20 ProVendor page
CursorEnterprise onlyPrivacy Mode must be on and locked org-wide.Not publicVendor page
SupabaseYesPaid add-on on Team and Enterprise only. Not on Free or Pro.Team from $599/mo; add-on price not publishedVendor page
NetlifyEnterprise onlyBAA for enterprise customers.Not publicVendor page
RenderYesScale or Enterprise workspace. Extra 20% on usage. No PHI in logs or static sites.20% usage feeVendor page
AptibleYesProduction plan.$499/mo + usageVendor page

Vendor prices are list prices on vendor pages on Nov 22, 2026, excluding usage. A private enterprise deal can differ. Last checked Nov 22, 2026.

Five mistakes we see most

In the vendor terms we read, most gaps sit in the plan or the settings.

  • Using a team plan. ChatGPT Business and Claude Team look like business plans but do not offer a BAA. Sources: OpenAI, Anthropic.
  • Assuming the whole product is covered. Connectors and MCP in Claude, web search in Microsoft Copilot and improved memory in ChatGPT sit outside the BAA. Sources: Anthropic, Microsoft, OpenAI.
  • Signing but not switching on. Claude Enterprise needs the Primary Owner to enable HIPAA. Cursor needs Privacy Mode locked. OpenAI API needs Modified Retention. Sources: Anthropic, Cursor, OpenAI.
  • Building on a prototype tool without a BAA. Vercel's API terms forbid processing PHI through v0, even though Vercel hosting offers a BAA. Sources: Vercel API Terms, Vercel Pro plan.
  • Stopping at the BAA. You still need a risk analysis, access control, audit logs and a staff policy (45 CFR 164.308(a)(1)(ii)(A), 164.312(a)(1), 164.312(b), 164.308(a)(5)(i)).

Admin switches to check, by vendor

A signed BAA covers you only once these settings are on.

VendorWhere the switch isWhat to confirmSource
OpenAI APISettings › Organization › General › HIPAA compliance support › EnableModified Retention on. Only listed endpoints in use. Cannot be undone.Vendor page
Claude EnterpriseOrganization settings › Data and privacy › HIPAA (Primary Owner)BAA accepted. Connectors, Chrome, Skills and mobile off for PHI users.Vendor page
Claude CodeEnterprise sign-in with the HIPAA configuration, or API key with zero data retentionNo cloud sessions, gateways or web fetch on PHI repos.Vendor page
Microsoft 365 CopilotAdmin center: web grounding for CopilotWeb search off, or PHI kept out of prompts that search.Vendor page
CursorEnterprise admin › Privacy ModeEnabled and locked for the whole organization.Vendor page
SupabaseTeam or Enterprise plan › HIPAA add-on › mark projects as HIPAASecurity Advisor clean. Connection logging on.Vendor page

Eight steps to roll out AI under HIPAA

A BAA is required before patient data goes in (45 CFR 164.502(e)), but it is not enough on its own. The rollout steps below rest on 45 CFR 164.308, 164.312 and 164.502.

  1. 1. Pick the plan
    Choose a plan from the matrix that offers a BAA. Move staff off personal and team accounts. A BAA must be in place before PHI goes in (45 CFR 164.502(e)).
  2. 2. Sign and switch on
    Accept the BAA and turn on the HIPAA setting: Enterprise HIPAA mode (Anthropic), Modified Retention (OpenAI), locked Privacy Mode (Cursor). Sources: the vendor pages in the matrix.
  3. 3. Turn off what is not covered
    Disable connectors, web search, memory and add-ons outside the BAA, or keep PHI out of them. Sources: the exclusions on the Anthropic, Microsoft and OpenAI pages in the matrix.
  4. 4. Control access
    Single sign-on, roles, remove leavers. Access only for people granted it (45 CFR 164.312(a)(1)).
  5. 5. Log and review
    Keep admin audit logs and review them on a schedule (164.312(b), 164.308(a)(1)(ii)(D)).
  6. 6. Send the minimum
    De-identify or summarize. Never paste a whole chart when a summary works (164.502(b)).
  7. 7. Add it to your risk analysis
    A new AI tool is a change to assess (164.308(a)(1)(ii)(A)).
  8. 8. Write the staff policy
    Which tool, which account, what may be pasted, and sanctions (164.308(a)(5)(i), (a)(1)(ii)(C)).

When you want it done for you

Compliant AI Workspace Setup

We set up Claude or ChatGPT for your team under a BAA: plan and contract check, HIPAA settings, connector review, data map, audit log routine, staff policy and a risk analysis entry. You own every document.

Integrations we have delivered: athenahealth, eClinicalWorks, and an Epic SMART on FHIR patient-facing app.

You own the code: everything we build lives in your repositories.

Price: fixed-scope quote after a scoping call.

The call: a 30-minute technical review with a Nirmitee engineer, not a sales pitch. No patient data needed.

Book the setup call

Read next

Read next on nirmitee.io

Go deeper on the engineering behind this guide.

From our work: AI medical scribing with EHR integration, an AI scribing tool that captures clinical fields from the visit and writes them into the EHR. To have this built into your product, see our HIPAA compliant software development and AI agents for healthcare.

Questions teams ask

Frequently asked questions

Short answers with the source for each.

Is ChatGPT HIPAA compliant?

Only on ChatGPT Enterprise, Edu, ChatGPT for Healthcare or Clinicians, and the OpenAI API, where OpenAI signs a BAA. ChatGPT Free, Plus and Business are not eligible. Features such as improved memory stay outside the BAA. Sources: OpenAI help articles 8660679 and 20001069.

Is Claude HIPAA compliant?

Claude Enterprise is covered once the Primary Owner switches on HIPAA and accepts the BAA, and the Claude API is covered for HIPAA-ready orgs set up through sales. Claude Free, Pro, Max and Team cannot enable HIPAA. Connectors, MCP, Claude in Chrome, Skills and the mobile app are excluded. Sources: Claude help article 13296973 and Anthropic privacy article 8114513.

Does OpenAI sign a BAA for the API?

Yes. It is a self-serve switch after API history, it needs Modified Retention, it cannot be turned off, and only listed endpoints are covered. Source: OpenAI help article 8660679.

Is any AI tool HIPAA certified?

No. HHS does not certify software, so no AI tool is HIPAA certified; Microsoft and VertiComply say the same on their own HIPAA pages. What matters is a signed BAA (45 CFR 164.502(e)), the right plan and settings, and your own safeguards.

Can we build a patient app on v0?

No. Vercel's API Terms forbid processing PHI through the v0 API (section 5). Vercel hosting itself offers a BAA as an add-on on Pro (Vercel Pro plan docs). For any other builder, ask the vendor for a signed BAA before PHI goes in.

What should we ask an AI vendor beyond the BAA?

Where data is stored and processed, which subprocessors see prompts, which audits cover the AI service, and how long prompts and outputs are kept. Ask for each in writing; the matrix does not cover residency or audits. This list is our recommendation.