The document states that OpenAI can execute a Business Associate Agreement with API customers who require HIPAA compliance coverage, enabling use of the API in contexts involving protected health information.
This analysis describes what OpenAI's agreement states, permits, or reserves. It does not constitute a legal determination about enforceability. Regulatory applicability and practical outcomes may vary by jurisdiction, enforcement context, and individual circumstances. Read our methodology
This provision establishes that API-based deployments handling protected health information may be eligible for BAA coverage, which is a prerequisite for using a third-party vendor under HIPAA. The provision specifies API deployments; compliance teams should confirm whether ChatGPT Enterprise or other product tiers are also within scope of the BAA.
Interpretive note: The provision specifies API customers; whether the BAA extends to ChatGPT Enterprise or other product tiers is not explicitly addressed in this document and should be confirmed with OpenAI directly.
Narrowed scope from general 'customers' to specifically 'API customers' and removed mention of 'HIPAA-eligible services' in favor of direct BAA signing capability.
View full change record →Under this provision, healthcare organizations using OpenAI's API can request a BAA before processing protected health information. The provision is scoped to API customers; organizations using ChatGPT Enterprise should independently confirm BAA availability for that product tier.
How other platforms handle this
At Ledger, earning and maintaining our users' trust is a top priority. That's why we are deeply committed not only to protecting your privacy and securing your personal data, but also to being fully transparent about how we handle it.
If you are located in the European Economic Area, Switzerland, or the United Kingdom, you have the right to access, correct, or erase your personal data; the right to restrict or object to our processing of your personal data; the right to data portability; and, where our processing is based on your...
We may display advertisements on our Services and those advertisements may be targeted to your interests based on your personal information. We may share your personal information with advertising partners for interest-based advertising purposes. You may opt out of interest-based advertising by visi...
Monitoring
OpenAI has changed this document before.
Receive same-day alerts, structured change summaries, and monitoring for up to 25 platforms.
"For API customers who require a Business Associate Agreement (BAA) for HIPAA compliance, we are able to sign a BAA.— Excerpt from OpenAI's OpenAI Enterprise Privacy
(1) REGULATORY LANDSCAPE: This provision engages the Health Insurance Portability and Accountability Act (HIPAA), specifically the requirements for Business Associate Agreements under 45 CFR Part 164, Subpart E. The relevant enforcement authority is the U.S. Department of Health and Human Services Office for Civil Rights. Where covered entities or business associates transmit PHI through OpenAI's API without an executed BAA, they may be in violation of HIPAA's safeguard and business associate requirements. (2) GOVERNANCE EXPOSURE: High for healthcare organizations or any enterprise customer whose API use involves PHI. The document discloses BAA availability but does not describe the scope of permitted uses of PHI under the BAA, or whether OpenAI's model infrastructure satisfies HIPAA's technical safeguard requirements. Without a BAA in place, API use involving PHI is not permissible under HIPAA. (3) JURISDICTION FLAGS: All US-based covered entities and business associates are subject to HIPAA BAA requirements. State-level health privacy laws (such as Washington My Health MY Data Act or California CMIA) may impose additional obligations beyond HIPAA, and the BAA scope should be evaluated against those frameworks as well. (4) CONTRACT AND VENDOR IMPLICATIONS: Healthcare procurement teams should execute the BAA prior to any API deployment involving PHI. The BAA should be reviewed to confirm it addresses permitted uses, safeguard obligations, breach notification timelines, and sub-contractor flow-down requirements. Teams should also assess whether OpenAI's sub-processors are covered by equivalent BAAs, as required under HIPAA's business associate chain requirements. (5) COMPLIANCE CONSIDERATIONS: Compliance teams should document BAA execution in their HIPAA vendor management records and conduct a risk analysis of OpenAI's technical safeguards prior to transmitting PHI. The scope of the BAA (API only vs. other products) should be confirmed in writing, and any use of fine-tuning or retrieval-augmented generation features involving PHI should be explicitly addressed in the agreement.
Full compliance analysis
Regulatory citations, enforcement risk, and due diligence action items.
Free: track 1 platform + weekly digest. Monitor: 25 platforms + same-day alerts. No credit card required.
Compliance Governance Intelligence
Need to monitor specific governance provisions?
Compliance includes provision-level monitoring, governance timelines, regulatory mapping, and audit-ready analysis.
Built from archived source documents, structured governance mappings, and historical version tracking.
This provision establishes that API-based deployments handling protected health information may be eligible for BAA coverage, which is a prerequisite for using a third-party vendor under HIPAA. The provision specifies API deployments; compliance teams should confirm whether ChatGPT Enterprise or other product tiers are also within scope of the BAA.
Under this provision, healthcare organizations using OpenAI's API can request a BAA before processing protected health information. The provision is scoped to API customers; organizations using ChatGPT Enterprise should independently confirm BAA availability for that product tier.
No. ConductAtlas is an independent monitoring service. We are not affiliated with, endorsed by, or sponsored by OpenAI.