Vendor agreements & evidence
AI vendor BAA checklist: what to verify before PHI reaches an AI tool
A BAA sets what a vendor may do with PHI. For AI tools, also check training and product-improvement use, prompts, outputs and logs, subcontractors, model changes, and exit terms. A signed BAA is evidence of a contract, not evidence of safe use. Review each point with counsel.
When an AI vendor is a business associate
HHS describes a business associate as a person or entity that performs functions or activities on behalf of a covered entity, or provides certain services to one, involving access to protected health information. A subcontractor that handles PHI for another business associate is also a business associate. See the HHS sample business associate agreement provisions, published January 25, 2013.
The HHS guidance on HIPAA and cloud computing applies the same idea to cloud services. It says a cloud provider that creates, receives, maintains or transmits ePHI for a covered entity is a business associate, even when it stores only encrypted data and holds no key. Many AI tools run on cloud services. Send edge cases to counsel.
The checklist: 16 checks before PHI reaches an AI vendor
Work down the table with the vendor on the call and record the evidence you receive. RUAIH means the Joint Commission and CHAI guidance on the Responsible Use of AI in Healthcare. Some rows are HIPAA contract requirements. Others come from voluntary guidance or good practice, and the table says which.
| # | Check: what to ask the vendor | Why it matters | Evidence to request | Source |
|---|---|---|---|---|
| 1 | Contracting entity and covered services match the AI product and the features you use. | A BAA may name a different product than the one you use. | Order form. Product and feature list attached to the BAA. | Your own contract review; see 45 CFR 164.502(e)(2) |
| 2 | The BAA states permitted and required uses and disclosures of PHI. | The contract, not the vendor's marketing, sets what the vendor may do. | BAA section on permitted uses. | 45 CFR 164.504(e)(2)(i) |
| 3 | No use or disclosure beyond the contract or the law. | This clause is the main limit on secondary use. | BAA clause and any data processing addendum. | 45 CFR 164.504(e)(2)(ii)(A) |
| 4 | Training, fine-tuning, evaluation and product-improvement use of PHI, de-identified data, outputs and local performance data is defined. | Vendors may want data to improve models. Silence leaves it open. | Written statement of what the vendor does and does not do with each data type. | RUAIH element 3 (permitted uses, including "rights around model outputs, local performance data, and monetization of data") |
| 5 | Only the minimum necessary data is sent to the tool. | Prompts and uploads can carry more PHI than the task needs. | Data flow diagram. Field list sent to the vendor. | RUAIH element 3 (data minimization) |
| 6 | Re-identification of de-identified data is prohibited. | Combined data can identify people again. | Contract clause. | RUAIH element 3 (prohibition of re-identification) |
| 7 | The vendor uses safeguards and meets the Security Rule for ePHI. | Security Rule duties flow to business associates by contract. | Security assessment, encryption and access control summary. | 45 CFR 164.504(e)(2)(ii)(B) and 45 CFR 164.314(a)(2)(i)(A) |
| 8 | Prompts, outputs, transcripts, embeddings and logs: where they live, how long, and how they are deleted. | Ask where prompts, outputs and logs live. They often hold PHI. | Retention schedule. Deletion procedure. Storage regions. | Your risk analysis; see HHS cloud guidance |
| 9 | Subcontractors, such as model hosts and cloud providers, agree to the same restrictions. | The model host may be a separate company that sees PHI. | Subcontractor list. Flow-down clause. | 45 CFR 164.504(e)(2)(ii)(D) and 45 CFR 164.502(e)(1)(ii) |
| 10 | The vendor reports unauthorized uses, security incidents and breaches, with a stated time window. | You cannot respond to what you do not hear about. | Incident clause. Contact path. Notice window. | 45 CFR 164.504(e)(2)(ii)(C), 45 CFR 164.314(a)(2)(i)(C) and 45 CFR 164.410(b) |
| 11 | Access controls apply, and access logs are reviewed. | Support staff should not see PHI by default. | Role list. Log review procedure. | RUAIH element 3 ("regularly auditing access logs") |
| 12 | You hold audit rights over the vendor. | Without audit rights, security claims stay unverified. | Audit clause. Most recent third-party assessment. | RUAIH element 3 (audit rights) |
| 13 | The vendor supports individual rights: access, amendment and accounting of disclosures. | Patients can ask for their records, and you must be able to answer. | Procedure and response time. | 45 CFR 164.504(e)(2)(ii)(E) to (G) |
| 14 | The vendor makes its books and records on PHI available to HHS. | This is a required contract term. | BAA clause. | 45 CFR 164.504(e)(2)(ii)(I) |
| 15 | PHI is returned or destroyed at termination, and you can terminate for a material violation. | Exit terms decide whether data stays in a model or a log. | Return and destruction clause. Termination clause. | 45 CFR 164.504(e)(2)(ii)(J) and 45 CFR 164.504(e)(2)(iii) |
| 16 | AI-specific terms sit beyond the BAA: model change notice, who monitors performance, validation evidence for the intended use, and the input variables in patient care decision support tools. | A BAA does not address model updates or whether the tool works for your patients. | Change notification clause. Validation summary. Monitoring plan. Input variable list. | RUAIH element 4, 45 CFR 92.210(b) and HSCC appendices F and G |
On row 10, the regulation sets an outer limit. A business associate must notify the covered entity of a breach of unsecured PHI "without unreasonable delay and in no case later than 60 calendar days after discovery." Many hospitals negotiate a shorter window, which is a contract term, not a legal requirement.
The Health Sector Coordinating Council guide on AI third-party risk offers more depth. Its appendices include sample contract language (E), sample BAA language (F) and vendor assessment questions (G).
Evidence status labels
Mark each row with one of three labels, matching the sample assessment.
- Documented: you hold a source document that answers the check.
- Not located in reviewed materials: the answer is absent from what you reviewed. This does not mean the term is missing from the agreement, and it does not mean the law requires it.
- Applicability needs review: the check may not apply. Counsel or the privacy owner decides.
What a BAA does not cover
A BAA governs how a vendor handles PHI. It does not show that the tool is accurate, fair across patient groups, stable over time, or a good fit for the workflow. It does not control what an AI agent does at runtime. Those questions need separate review, such as AI vendor intake and review.
A BAA also does not replace your own risk analysis. HHS says a covered entity that engages a cloud provider should understand the environment well enough to conduct its own risk analysis and set risk management policies, as well as enter into appropriate BAAs. For tools staff adopt without approval, see shadow AI in hospitals. For agents that act in your systems, see least privilege for AI agents and tamper-evident audit trails.
Worked example (fictional)
Three fictional vendors each offer a note drafting feature for the same workflow. The privacy owner fills in the register. These vendors and findings are invented to show the labels.
| Vendor | BAA covers this feature | Subcontractors listed | Training use terms | Next action |
|---|---|---|---|---|
| Northwind Scribe | Documented | Documented | Not located in reviewed materials | Add the training use question to the vendor call. |
| Lakeside Summarizer | Documented | Not located in reviewed materials | Applicability needs review | Ask which model host handles prompts. Counsel to review scope. |
| Harbor Triage Chat | Not located in reviewed materials | Not located in reviewed materials | Not located in reviewed materials | Hold PHI use until a BAA covering this feature is located. |
Harbor Triage Chat stays off PHI until the team finds a BAA that covers the feature. The register does not rank vendors.
Free template: clause language and register columns
This is a starting point for counsel review, not legal advice. Do not paste it into a contract unchanged. Bracketed items need your decision.
Sample clause language
STARTING POINT FOR COUNSEL REVIEW. NOT LEGAL ADVICE. 1. Scope. This Agreement covers [product, features, versions] only. 2. Permitted uses. Vendor may use or disclose PHI only to provide the services described in [order form], or as required by law. 3. AI training and product improvement. Vendor will not use PHI, or data derived from PHI, to train, fine-tune, evaluate or improve any model without Hospital's prior written consent. [Counsel: decide treatment of de-identified data, outputs and local performance data.] 4. Re-identification. Vendor will not re-identify de-identified data or attempt to contact individuals. 5. Prompts, outputs and logs. Vendor will store prompts, outputs, transcripts, embeddings and logs only in [regions], for no longer than [period], and delete them on request. 6. Subcontractors. Vendor will list every subcontractor that handles PHI, including model hosts, and bind each to the same restrictions in writing. 7. Incidents. Vendor will report any unauthorized use or disclosure, security incident or breach to Hospital without unreasonable delay and within [period] of discovery. 8. Access and audit. Vendor will restrict PHI access by role, review access logs regularly, and allow Hospital to audit compliance. 9. Model changes. Vendor will give Hospital [period] notice before material changes to models, data handling or subcontractors. 10. Validation and monitoring. Vendor will document how the tool was tested and validated for the intended use. The parties will agree in writing who monitors performance. 11. Exit. At termination, Vendor will return or destroy all PHI, including copies in logs and backups where feasible.
Register columns (CSV header)
Copy this line into a spreadsheet. Keep patient information out of it.
vendor,product_and_feature,data_types,baa_on_file,baa_covers_this_product,training_use_terms,subcontractors_listed,log_retention,incident_window,audit_rights,exit_terms,open_questions,owner,next_action,source_reference
For a request-by-request tracker, use the free evidence worksheet.
Frequently asked questions
Does every AI vendor need a BAA?
No. A BAA is needed when the vendor creates, receives, maintains or transmits PHI on your behalf. HHS describes a business associate in those terms. If no PHI reaches the tool, a BAA may not apply, but confirm that with counsel and verify that no PHI can reach it.
Does a BAA cover de-identified data?
HIPAA treats information that meets the de-identification standard as not individually identifiable (45 CFR 164.502(d)(2)). A BAA therefore may not govern it unless the contract says so. The Joint Commission and CHAI guidance still advises contractual guardrails, including a ban on re-identification. Ask counsel how to word this.
Can a hospital use a consumer AI tool with PHI?
Not without a business associate arrangement that meets the contract rules when the tool handles PHI for the hospital. Consumer terms of service rarely include the required provisions. Block PHI in unapproved tools by policy and check for shadow AI use. Send specific cases to counsel.
What should a BAA say about training AI models?
The contract must state permitted uses, and the vendor may not use PHI beyond them. State plainly whether training, fine-tuning, evaluation or product improvement is allowed. The HSCC guide includes sample language that bars AI training with PHI without the covered entity's prior written consent. Treat it as an example for counsel.
Who should own BAA review for AI tools?
Privacy or compliance usually owns the BAA, with legal counsel, security and procurement as reviewers. Name one accountable owner per vendor in your register. Route AI-specific questions such as validation and monitoring to the group that runs AI intake.
Is a signed BAA enough to approve an AI tool?
No. A signed BAA is evidence of a contract, not evidence of safe use. It does not test accuracy, bias, drift or how an agent behaves at runtime. Keep the BAA, your security review and your clinical evaluation as separate records.
Sources and scope
Examples are fictional. This guide is not legal advice and does not certify any vendor. There is no official HIPAA certification. Ask counsel which sources apply to you.
- HHS, Sample Business Associate Agreement Provisions (January 25, 2013)
- HHS, Guidance on HIPAA and Cloud Computing
- 45 CFR 164.504(e)(2), business associate contract requirements
- 45 CFR 164.502(d) and (e), de-identified information and disclosures to business associates
- 45 CFR 164.314(a), Security Rule business associate contracts
- 45 CFR 164.410(b), timeliness of business associate breach notice
- 45 CFR 92.210, patient care decision support tools (Section 1557)
- Joint Commission and CHAI, Responsible Use of AI in Healthcare, elements 3 and 4 (PDF)
- Health Sector Coordinating Council, AI third-party risk guide (PDF)