What is a business associate agreement (BAA)?
A business associate agreement (BAA) is a contract required by HIPAA between a covered entity, such as a health plan or provider, and a business associate that creates, receives, maintains or transmits protected health information (PHI) on its behalf. It sets how the vendor may use PHI, how it must protect the data and what it must report.
For example, a clinic wants staff to use an AI assistant to draft visit summaries from doctors’ notes. The notes contain PHI, and the AI provider will receive and process them. Before any note is sent, the clinic needs a signed BAA with the provider, and the provider needs BAAs with any subcontractors that touch the data. Without one, sending PHI to the tool is likely an impermissible disclosure under HIPAA. This is a summary, not legal advice.
What a BAA must include
The HIPAA rules at 45 CFR 164.504(e) list the required terms. A BAA must:
- State the permitted and required uses and disclosures of PHI.
- Bar the business associate from using or disclosing PHI beyond the contract or the law.
- Require safeguards under the HIPAA Security Rule for electronic PHI.
- Require reports of uses or disclosures the contract does not allow, including breaches of unsecured PHI.
- Require subcontractors that handle PHI to agree to the same limits.
- Support individuals’ rights to access, amend and get an accounting of disclosures.
- Make internal records available to the Department of Health and Human Services (HHS).
- Require return or destruction of PHI when the contract ends, where feasible.
Who needs a BAA
Business associates include cloud hosts, billing companies, claims processors, IT support firms, transcription services and AI vendors that handle PHI for a covered entity. A business associate that hires a subcontractor to handle PHI needs a BAA with that subcontractor too. HHS treats a cloud provider that stores PHI as a business associate even when the data is encrypted and the provider has no key.
BAAs and AI tools
Not every AI product offers a BAA, and many offer one only on specific plans. In ChatGPT, only ChatGPT Enterprise, including ChatGPT for Healthcare, offers a BAA. Check the exact product and plan before any PHI flows, and read our guide to BAAs for ChatGPT and other LLMs.
Masking or tokenizing PHI before it reaches a model reduces exposure, but tokens can still be PHI. Many teams keep the BAA in place, and counsel decides whether one is needed.
How Protecto helps
Protecto detects PHI in prompts, documents and tool outputs and replaces it with consistent tokens before it reaches a model, so the AI provider receives less real patient data. When Protecto hosts or manages the service, or has access to the installed instance for support, upgrades or monitoring, Protecto is a business associate and signs a BAA before PHI flows. When Protecto runs in your environment with no Protecto access, Protecto does not receive PHI and is not a business associate. See HIPAA compliance with Protecto.
Frequently asked questions
Do I need a BAA to use ChatGPT with patient data?
Yes, if PHI goes into it. In ChatGPT, only ChatGPT Enterprise, including ChatGPT for Healthcare, offers a BAA, so other plans should not receive PHI.
Who signs a business associate agreement?
The covered entity and the business associate sign it. A business associate also signs one with each subcontractor that handles PHI.
Does tokenizing PHI remove the need for a BAA?
Not on its own. Tokens can still be PHI, many teams keep the BAA in place, and counsel decides based on the data flow.
Related terms
Protected health information (PHI) · HIPAA · HIPAA Safe Harbor method · Data processor · Tokenization