Short answer: No AI tool is HIPAA compliant on its own. What a vendor can do is sign a business associate agreement (BAA) and limit which of its features may touch protected health information. Today OpenAI offers a BAA for sales-managed ChatGPT Enterprise but says "We do not offer a BAA for ChatGPT Business". Anthropic offers one for Claude Enterprise once an owner turns on its HIPAA settings, the in-scope list for Microsoft's BAA names Microsoft Copilot, and Google's covers named Workspace features with Gemini. A broker still has to configure the tool and decide what staff may put in it.
When a broker needs a BAA at all
Not every benefits question involves protected health information (PHI). A plan design comparison or a renewal summary may have none. A census file with diagnoses, a claims history or enrollment records with health details can.
HHS describes a business associate as a person or organization that "performs certain functions or activities" for a covered entity "that involve creating, receiving, maintaining, or transmitting PHI", and adds that "A business associate also is any subcontractor that creates, receives, maintains, or transmits PHI on behalf of another business associate" (HHS). If your agency handles PHI for a group health plan client, the plan may treat you as its business associate. An AI vendor that then holds that PHI for you would be your subcontractor, which is why the vendor's BAA matters. Whether your work falls in that definition is a question for your compliance adviser.
Which AI vendors offer a BAA, in their own words
No product carries a HIPAA certificate you can rely on instead. Microsoft puts it plainly: "There's currently no certification standard that the Department of Health and Human Services approves to demonstrate compliance with HIPAA or the HITECH Act by a business associate." What vendors offer is a signed BAA and a list of covered features.
Read on November 13, 2026, from each vendor's own pages. No ratings.
| Vendor and plan | BAA offered? | What the vendor says you must still do |
|---|---|---|
| OpenAI, ChatGPT Business | No: "We do not offer a BAA for ChatGPT Business." | Not applicable |
| OpenAI, ChatGPT Enterprise | "For a BAA for a sales-managed ChatGPT Enterprise or Edu account, contact sales." | OpenAI says accepting a BAA does not, "by themselves, make your application HIPAA compliant" (OpenAI) |
| Anthropic, Claude Enterprise | Yes, once the organization's Primary Owner turns on HIPAA compliance in the "HIPAA-ready Claude Enterprise organization settings" and accepts the BAA | "Standard Claude Enterprise plans do not include BAA coverage without action from a Primary Owner", and some features are excluded. For Anthropic's own API, the Primary Owner "will need to sign a BAA and then reach out to your Anthropic contact or our Sales team to get this turned on" (Anthropic) |
| Microsoft Copilot and Copilot Chat (per Microsoft's in-scope list) | Microsoft "offers its covered entity and business associate customers a Business Associate Agreement that covers in-scope Microsoft services"; its in-scope list includes "Microsoft Copilot, Microsoft Copilot Chat" | Use only in-scope services (Microsoft) |
| Google Workspace with Gemini | Customers subject to HIPAA "must enter a Business Associate Amendment (BAA) with Google" | "Customers who have not signed a BAA with Google must not use PHI in Google Workspace or Cloud Identity services", and only listed features are covered (Google) |
Claude Team, ChatGPT's personal plans and most free tools have no BAA path in the pages we read, so keep PHI out of them.
Faradex is not in this table. Before any PHI goes into a tool not listed here, Faradex included, ask the vendor in writing whether it will sign a BAA.
What a BAA does not do for you
A signed BAA covers the vendor's side. Your agency still decides who may use the tool, which features stay switched off and what kind of file may go in. Two details from the vendors' own pages show why that matters:
- Anthropic says sending data to third parties through connectors "isn't covered under Anthropic's BAA", even on a HIPAA-ready plan.
- Google says "Third-party applications including add-ons are not included in the Included Functionality covered by the BAA."
So a broker who signs a BAA and then lets staff connect an outside add-on can end up outside the agreement without noticing.
A short plan for a benefits team
- Sort your AI uses into ones with PHI and ones without. Many tasks, such as drafting an open enrollment email, need none.
- For uses with PHI, pick a plan whose vendor will sign a BAA, and get it signed before anyone uploads a census.
- Turn on the vendor's HIPAA settings and switch off the features its BAA excludes.
- Strip identifiers that the task does not need. A rate comparison rarely needs names or member IDs.
- Record the BAA, the settings and the date in your vendor file, next to the due diligence the insurance data rules already ask for (vendor due diligence).
For the non-health side of agency work, see What is secure AI for an insurance agency?
This guide is general information, not legal or compliance advice. HIPAA questions about your agency's role belong with your compliance adviser.