Is ChatGPT HIPAA Compliant? A 2026 Guide for Clinicians and Health Tech Teams

Short answer: ChatGPT itself is not "HIPAA compliant" out of the box. OpenAI will handle protected health information (PHI) consistent with a Business Associate Agreement (BAA) for customers on certain healthcare-oriented ChatGPT offerings and for BAA-eligible API endpoints, but only after you sign that agreement and configure the deployment the way it requires. OpenAI's HIPAA guide ties its BAA to ChatGPT for Healthcare, ChatGPT for Clinicians, and Regulated workspaces. ChatGPT Free and Plus are not among them, so PHI does not belong there.

Last reviewed October 1, 2026 against the regulations and vendor documentation listed under Sources and primary references.

This guide explains, in 2026, what HIPAA actually requires of an AI tool, which OpenAI products can be made compliant, what a clinician or health-tech team has to do operationally, and how to keep PHI from leaking when staff inevitably reach for ChatGPT in a browser tab.

What HIPAA actually requires of an AI tool

The Health Insurance Portability and Accountability Act (HIPAA) is implemented by three rules:

• Privacy Rule — defines PHI and the conditions under which it may be used or disclosed.
• Security Rule — defines administrative, physical, and technical safeguards for electronic PHI (ePHI).
• Breach Notification Rule — defines what counts as a breach and the timelines for reporting it.

For an AI provider to handle PHI on your behalf, three things must be true:

1. The provider qualifies as a business associate because it creates, receives, maintains, or transmits PHI on behalf of a covered entity for a regulated function or activity.
2. You have a signed Business Associate Agreement (BAA) with the provider that contractually extends HIPAA obligations to them and meets the content requirements of 45 CFR 164.504(e).
3. The provider's product, in the configuration you actually use, supports the Security Rule's technical safeguards: access control, audit controls, integrity, authentication, and transmission security, with encryption an addressable specification.

A covered entity may disclose PHI to a business associate only after obtaining satisfactory assurance that it will safeguard the information, documented in a written contract (45 CFR 164.502(e)). Without that, sending PHI to a vendor is an impermissible disclosure, even if the vendor is "secure" in a general sense.

Where OpenAI's products stand on HIPAA in 2026

What follows comes from OpenAI's own documentation as of October 1, 2026: its HIPAA configuration guide for Codex and its API data-controls page.

• ChatGPT for Healthcare, ChatGPT for Clinicians, and Regulated workspaces. OpenAI's guide says that customers on one of these who have an applicable BAA have PHI handled consistent with that BAA. The guide is written for Codex, but these are the ChatGPT-side offerings it names. It also states that OpenAI does not train on ChatGPT Enterprise data.
• The OpenAI API. The data-controls page refers to a "Business Associate and Healthcare Addendum" and to "BAA-eligible endpoints." API abuse-monitoring logs are retained for up to 30 days by default. For customers with the addendum, OpenAI says BAA-eligible endpoints can process PHI even where data is retained, once the organization is provisioned with the retention setting the agreement names.
• Where coverage stops. The guide says the BAA does not cover Codex cloud, and that OpenAI's BAA "doesn't make another vendor a HIPAA-compliant destination." A connector that sends PHI to a third party needs its own agreement with that third party.

Plan-by-plan eligibility changes, and OpenAI's help center is the authoritative list. Check it for your specific plan, whether that is Enterprise, Edu, a business workspace, or an individual plan, before any PHI goes in. Individual consumer plans such as Free and Plus are not named in OpenAI's HIPAA guide or API documentation.

This matters because the URL is the same. A clinician sitting at chat.openai.com cannot tell from the interface whether the account they are logged into is the personal Plus account they pay for, an organization workspace covered by a BAA, or somewhere in between. Operationally, the question "is this HIPAA-compliant?" is really "which account am I in right now, and does a BAA cover it?"

What a HIPAA-aligned ChatGPT deployment looks like

A healthcare organization that wants to use ChatGPT or the OpenAI API for clinical or operational workflows typically needs to:

1. Sign a BAA with OpenAI through its enterprise sales process. The BAA must cover the specific product and the specific endpoints your workforce uses.
2. Configure retention the way your BAA requires. OpenAI retains API abuse-monitoring logs for up to 30 days by default. Its Zero Data Retention and Modified Abuse Monitoring controls remove customer content from those logs but need OpenAI's prior approval (API data controls). OpenAI's Codex guide adds that API-key usage is covered only if the BAA lists the relevant API services as an Eligible Service and OpenAI has provisioned your organization with the retention setting it names (HIPAA guide).
3. Restrict workforce access to the BAA-covered tenancy. Block consumer ChatGPT at the network level or via an SSO policy that forces sign-in to the enterprise tenant.
4. Enforce least privilege in any agentic or tool-using configurations — limit the data sources the model can read and the tools it can call.
5. Log access in a way that satisfies the Security Rule's audit-control standard. OpenAI's guide says usage authenticated through ChatGPT produces audit records kept for up to 30 days and retrievable through its Compliance API, so plan to export them. On the API you instrument logging on your side.
6. Train the workforce specifically on what may and may not be sent (workforce training is required). A signed BAA does not authorize pasting any PHI, only PHI that the user is otherwise permitted to disclose.
7. Document everything (risk assessment, BAA, configuration, training records), because the Security Rule requires written policies and records of required actions and assessments, retained for six years (45 CFR 164.316(b)).

This is a real project, not a checkbox. Steps 3 and 6 are the easiest to underestimate.

The "shadow ChatGPT" problem

Even with an enterprise contract, a common HIPAA exposure in 2026 is workforce members using consumer ChatGPT for clinical or administrative tasks because it is faster than the sanctioned tool. A Wolters Kluwer Health survey of 518 providers and administrators, fielded by CITE Research in December 2025, found that 40 percent had encountered an unauthorized AI tool at work and nearly 20 percent admitted to using one. One in 10 said they had used an unauthorized tool for a direct patient-care use case, and half pointed to a need for faster workflows.

Two technical controls help materially:

• Device-level redaction. Locke 1.0 detects PHI categories (names, dates, MRNs, diagnoses, drug names) locally and replaces them with one-way placeholders before the prompt leaves the device. Even when staff use a non-sanctioned account, the unmasked PHI never crosses the wire. Reversible tokenization is planned shortly after 1.0.
• Egress monitoring for AI domains. Add chat.openai.com, claude.ai, gemini.google.com, and similar destinations to your DLP and CASB rules. Treat traffic to these domains the same way you treat traffic to a personal cloud-storage provider.

Both controls are additive, not substitutes for a BAA — they reduce the size and severity of the problem when the policy is bypassed.

Examples: what is and is not allowed

The lines below assume a covered entity has a signed BAA with OpenAI for ChatGPT Enterprise. Without that BAA, the answer to every example is "no, this is an unpermitted disclosure."

The pattern: keep PHI inside the BAA boundary, or remove PHI before the request leaves your device.

Frequently asked questions

Does signing a BAA make ChatGPT HIPAA compliant?

A BAA is necessary but not sufficient. Compliance requires the BAA plus the Security Rule's administrative, physical, and technical safeguards in your configuration and operation. OpenAI's BAA covers their part; the rest is yours.

Is ChatGPT Plus HIPAA compliant if I only use it for de-identified data?

If the data is genuinely de-identified under HIPAA's Safe Harbor or Expert Determination methods, it is no longer PHI and HIPAA does not apply. The risk is that "de-identified" is harder than it looks. Safe Harbor requires removing 18 categories of identifiers and that you have no actual knowledge that what remains could identify the person. Expert Determination requires a qualified expert to determine, and document, that the risk of identification is very small. If you cannot document one of the two methods, treat the data as PHI.

What about ChatGPT memory and Projects?

For BAA-covered tenancies, OpenAI publishes guidance on which features are eligible. As of 2026, ChatGPT Enterprise admins can disable memory and uploaded-file retention as part of the workspace configuration. Confirm the current eligibility list with your account team before turning these features on for clinical workflows.

Can a doctor use Microsoft Copilot or Gemini with PHI instead?

The same logic applies: BAA required, configuration required, workforce policy required. Microsoft's HIPAA page lists Microsoft Copilot and Copilot Chat among the in-scope Office 365 services, and Google's HIPAA guide lists the Gemini app and Gemini in Google Workspace as covered by the Google Cloud BAA. Each vendor's eligibility list and feature scope is different. Read the BAA, not the marketing.

What if my staff already pasted PHI into a personal ChatGPT account?

Treat it as a presumed breach. Investigate the account's data settings (history, training opt-in) and document the disclosure. Under 45 CFR 164.402, an impermissible disclosure is presumed to be a breach unless you can demonstrate a low probability that the PHI has been compromised, based on a risk assessment of at least four factors: the nature and extent of the PHI involved and the likelihood of re-identification; who received it; whether it was actually acquired or viewed; and how far the risk has been mitigated. Document that assessment. If you cannot show low probability, notify affected individuals without unreasonable delay and no later than 60 days after discovery (45 CFR 164.404), and notify HHS (45 CFR 164.408): at the same time for breaches of 500 or more individuals, otherwise in an annual submission within 60 days after the end of the calendar year.

Your exposure does not depend on leadership knowing. A covered entity is liable for violations by workforce members acting within the scope of their agency, and a breach is treated as discovered when any workforce member other than the person who caused it knows of it, or would have with reasonable diligence.

How does Locke relate to HIPAA when staff use ChatGPT?

Locke is not a covered entity or business associate; it is a privacy layer that runs entirely on the user's device and never receives PHI. By detecting PHI categories on-device and replacing them with one-way placeholders before the prompt leaves the device, Locke materially reduces the surface where PHI can leak — including to non-BAA accounts. It is complementary to a properly executed BAA program, not a substitute for one.

A short HIPAA + ChatGPT checklist

• Decide which AI products your workforce may use for PHI, and which are blocked.
• Sign a BAA with each approved provider, covering the specific products and endpoints in use.
• Configure the retention controls your BAA specifies, such as Zero Data Retention or Modified Abuse Monitoring.
• Block or proxy consumer-tier endpoints at the network and identity layers.
• Deploy a local-first redaction tool to every browser used by clinical and administrative staff.
• Add AI-bound traffic to your DLP, CASB, and audit-log review.
• Train staff specifically on what may and may not be sent — and verify with periodic walk-throughs, not just attestations.
• Re-assess annually; vendor product lines and feature eligibility change frequently.

The bottom line

In 2026, "Is ChatGPT HIPAA compliant?" is the wrong question. The right questions are: which OpenAI product am I using, do I have a BAA covering that product, is the configuration aligned with the Security Rule, am I sure my workforce is in the BAA-covered tenancy, and what happens when they aren't? Get those right and ChatGPT becomes a useful tool inside a HIPAA program. Skip any one of them and you are running on luck.

Sources and primary references

Reviewed October 1, 2026. Regulations are cited to the eCFR. Vendor statements are cited to the vendor's own documentation as it read on that date; vendors revise these pages, so confirm before relying on them.

• 45 CFR 160.103, definition of business associate — who counts as a business associate, including subcontractors.
• 45 CFR 164.502(e), disclosures to business associates — satisfactory assurance, documented in a written contract.
• 45 CFR 164.504(e), business associate contracts — what the contract must contain.
• 45 CFR 164.312, technical safeguards — access control, audit controls, integrity, authentication, transmission security.
• 45 CFR 164.316, documentation — written policies and six-year retention.
• 45 CFR 164.514, de-identification — Safe Harbor and Expert Determination.
• 45 CFR 164.402 to 164.410, breach notification — the presumption of breach, the four-factor assessment, and notification deadlines.
• 45 CFR 160.402(c), agency liability — liability for workforce members and business associates acting within the scope of agency.
• Wolters Kluwer Health survey press release, January 22, 2026 — 518 healthcare professionals, fielded December 2025.
• OpenAI, HIPAA configuration guide (Codex) — which ChatGPT offerings and API services the BAA applies to, and what it excludes.
• OpenAI, API data controls — abuse-monitoring retention, Zero Data Retention, Modified Abuse Monitoring, and the Business Associate and Healthcare Addendum.
• Microsoft, HIPAA and HITECH offering — Copilot and Copilot Chat among in-scope Office 365 services.
• Google Cloud, HIPAA compliance guide — Gemini app and Gemini in Google Workspace under the Google Cloud BAA.

Related HIPAA guides

• Is Claude HIPAA Compliant?
• Is Gemini HIPAA Compliant?
• Is Microsoft Copilot HIPAA Compliant?
• Is GitHub Copilot HIPAA Compliant?
• Is Perplexity AI HIPAA Compliant?
• HIPAA-Compliant AI: A Complete Checklist for 2026