The plan decides before the feature does
For HIPAA-covered entities and their business associates, protected health information must be processed through an appropriately covered service with a Business Associate Agreement (BAA). As of November 2026, the self-serve team plans that most teams start on do not qualify.
| Vendor | Team plan with patient data? | Route to a BAA |
|---|---|---|
| OpenAI | No BAA for ChatGPT Business | Sales-managed ChatGPT Enterprise or Edu; HIPAA-eligible products include ChatGPT for Healthcare, ChatGPT for Enterprise with Regulated Workspace and ChatGPT for Clinicians |
| Anthropic | Team and individual plans cannot enable HIPAA | HIPAA-ready Claude Enterprise; the Primary Owner accepts the BAA in organization settings |
| xAI | Business page lists HIPAA, plan not specified | Confirm with xAI sales |
Which collaboration features a BAA covers
This is where shared projects and memory come in. Coverage is per feature, not per product.
OpenAI. Its list of functionality covered in HIPAA-eligible ChatGPT workspaces includes creating and managing projects, sharing projects (also via workspace links), sharing chats in the workspace, workspace agents, skills, and “Use shared memory”, when the feature is enabled for the member’s role. OpenAI adds that a feature’s availability does not by itself decide whether a particular use or connected third-party service is covered.
Anthropic. Features fall into three groups: covered by the BAA, available but not covered, and disabled. The help center names Claude Code and Cowork in local mode as covered only after the Primary Owner applies a separate configuration, and cloud features such as Cowork in the cloud as not available after that configuration. For everything else, including memory and projects, it points to the Implementation Guide for HIPAA Entities on its Trust Center as the authoritative list.
A setup that works for a care team
- Split the knowledge. Check protocols, checklists, referral criteria, letter templates and team agreements for patient-identifying information before sharing them. Only material verified to contain no patient data belongs in the non-patient knowledge layer, in a shared project or document on a plan your organization approves.
- Keep patient-specific work in the covered workspace only, and only in features your BAA covers.
- Check memory explicitly. Personal memory carries details from one chat into the next. In a covered workspace, confirm that memory is covered; elsewhere, make sure nobody discusses patients at all.
- Watch the connectors. A connected app or third-party service is a separate question from the BAA with the AI vendor.
- Write down which tool is for what, and repeat it at onboarding. A personal account used “just this once” is the easiest way for patient data to end up outside the agreement.
The common misunderstanding
Teams treat “HIPAA compliant” as a label on a product. It is an agreement plus a configuration plus your own use. A signed BAA does not make every feature in the interface safe for patient data, and OpenAI states that accepting one does not by itself make your use compliant.
What this means for a healthcare team
The knowledge a care team most needs to share, how we do things here, is usually not patient data at all. Yet it ends up in the same personal chats as patient questions, or stays in senior staff’s heads. Separating the two makes the shared part easier to share and the sensitive part easier to protect. For the Dutch view on patient data in ChatGPT, see patiëntgegevens in ChatGPT in de zorg; for data handling on business plans, does ChatGPT Team train on your data.
Where Bombos fits
Bombos is a plugin that gives every AI tool a team uses one shared memory for team knowledge and learned rules, such as protocols and working agreements, with a trace to where each answer comes from. For healthcare the relevant option is running it standalone on your own server, so you decide where that memory lives. Patient data rules still apply to whatever you put in; one person can try it first with their own agents on non-patient work.
Related questions
Is ChatGPT Business HIPAA compliant?
OpenAI states it does not offer a BAA for ChatGPT Business. A BAA for ChatGPT requires a sales-managed Enterprise or Edu account; eligible individual clinicians can use the separate ChatGPT for Clinicians flow.
Can we use Claude Team with patient data?
Not under HIPAA. Anthropic's help center states that Team plans and individual plans (Free, Pro, Max and Ultra) cannot enable HIPAA. Only the Primary Owner of an Enterprise organization can accept the BAA and enable it.
Does signing a BAA make our use of AI compliant?
No. OpenAI says plainly that accepting a BAA does not by itself make your use compliant; you remain responsible for configuration and your own obligations. Features outside the BAA can still be visible in the product.
What about Grok?
xAI lists HIPAA among its compliance claims on its business page, without saying which plan or under what agreement. Ask xAI sales in writing before any protected health information goes in.
