Document Automation
Product features
By practice area
By company size
Contract Review
PRODUCT FEATURES
Resources
LearN
Case Studies
Pricing
Gavel Exec reviews and redlines contracts inside Microsoft Word, checked against your own playbook. Start with 25 free queries, no credit card required.
Review a business associate agreement (BAA) in two passes. First confirm every term that 45 C.F.R. 164.504(e) and 164.314(a) require under the Health Insurance Portability and Accountability Act (HIPAA). Then negotiate what the rules leave open: how fast the vendor reports a breach, whether it may de-identify data or train models, where data sits, and who pays.
Last reviewed November 16, 2026. This playbook is general information for lawyers, not legal advice for a specific matter. Gavel publishes it and makes Gavel Exec.
The Department of Health and Human Services (HHS) publishes sample BAA provisions and suggests the parties may add "a stricter timeframe for the business associate to report a potential breach." Under 164.504(e)(2) and 164.314(a)(2), the BAA must:
Gavel's business associate agreement template sets out these terms.
Every position below is the covered entity's: a provider, health plan or clearinghouse handing PHI to a vendor. A business associate will often find the fallback column signable. Holland & Hart's 2023 list of BAA terms gives vendor asks such as being liable "for only the acts or omissions of its own agents and employees" and limiting "liability for costs in responding to breaches."
The third seat is a business associate signing with its own subcontractor, such as a host or model provider, which 164.502(e)(1)(ii) requires in writing. Take the covered entity's seat for that contract and keep each downstream term as tight as the upstream promise: a vendor owing 72 hours' notice cannot accept 30 days from its host.
General services terms are in the MSA playbook; other contracts are in the playbooks library.
Sixteen issues for a mid-sized provider buying a service that holds identifiable patient data.
| Issue | Preferred position | Acceptable fallback | Escalate or walk away if | Why it matters |
|---|---|---|---|---|
| Permitted uses | Only the services in a named schedule, limited to the minimum necessary; management and administration uses only on the 164.504(e)(4) conditions. | The vendor's standard purposes if each is tied to a listed service. | "Any lawful purpose" or "to improve our products". | A BAA may not authorize uses the covered entity could not make (164.504(e)(2)(i)); minimum necessary binds vendors (164.502(b)). |
| Data aggregation | None, unless the service is analytics for the covered entity. | For the covered entity's health care operations only; outputs never identify it or its patients to other customers. | Combined data feeds products sold to others. | 164.504(e)(2)(i)(B). |
| De-identification | Prohibited except to perform the services. | Expert determination only, with a copy of the report, no re-identification and no sale. | Any method for any purpose, or vendor owns all de-identified data. | HHS: a business associate may de-identify only as its BAA authorizes. |
| AI model training | No training, fine-tuning or testing on PHI or anything derived from it, except a model used only for this covered entity. | Training on expert-determined de-identified data with written consent, withdrawable on 30 days' notice. | Training rights sit in online or AI terms that override the BAA. | A general model serves the vendor's own purpose. |
| Safeguards and evidence | Security Rule compliance plus encryption at rest and in transit, multi-factor authentication, annual risk analysis and an annual System and Organization Controls (SOC) 2 Type II report or equivalent. | Security Rule compliance plus an annual questionnaire and a risk analysis summary. | "Commercially reasonable" security with no reference to the Security Rule. | 164.314(a)(2)(i)(A); a pending HHS proposal would add annual written verification. |
| Breach reporting clock | First notice within 72 hours after discovery; all 164.410(c) information within 10 days. | 10 business days; complete information within 30 days. | 60 days, no number at all, or a clock that starts on "confirmation". | The vendor's 60 days can consume the covered entity's own 60. |
| Suspected breaches and security incidents | Suspected breaches and successful incidents on the breach clock; the covered entity runs the risk assessment; standing notice covers unsuccessful pings and port scans. | Vendor's written risk assessment, which the covered entity may overrule. | Vendor reports only what it decides is a breach. | 164.314(a)(2)(i)(C) covers any security incident; an impermissible use is presumed a breach. |
| Agency status | Vendor is an independent contractor; the covered entity cannot control how it performs. | Same, with instructions limited to outcomes and deadlines. | The services agreement gives day-to-day direction of vendor staff. | 160.402(c) agent liability; 164.404(a)(2) imputed knowledge. |
| Breach costs and notices | Vendor pays notices, call center, 24 months of credit monitoring, forensics and regulator response for breaches at it or its subcontractors; covered entity controls notices. | Costs up to the BAA's separate cap; vendor may send notices on approved text. | "Cooperation" only, at the covered entity's expense. | HIPAA assigns the notice duty and is silent on cost. |
| Subcontractors | Each signs an agreement at least as protective as the BAA; hosting and model providers listed; 30 days' notice of additions; vendor answers for them. | List on request; notice within 30 days after an addition. | Flow-down only "where commercially practicable". | 164.502(e)(1)(ii); 164.504(e)(5). |
| Offshore access and storage | PHI stored, processed and accessed only in the United States unless the covered entity consents in writing. | Logged remote support from listed countries; no storage abroad. | Storage or access "in any region". | HHS: overseas storage "may increase the risks". |
| Indemnity | Vendor covers third-party claims, penalties, settlements and breach costs caused by it or its subcontractors. | Mutual, each party for its own breach. | None, or for "gross negligence" only. | HIPAA is silent on cost recovery, so the contract is the dependable route. |
| Liability cap | BAA obligations and indemnity sit outside the services cap. | Separate cap no lower than the required cyber policy limit. | BAA claims under a 12-month-fees cap. | California allows $1,000 nominal damages per patient (Civ. Code 56.36(b)). |
| Cyber insurance | $5 million per claim, kept 3 years after termination, covering notification costs and insurable fines. | $2 million for a small vendor or low data volume. | No coverage, or an unencrypted-device exclusion. | Insurance funds the indemnity. |
| Termination and exit | Covered entity may end the BAA and services agreement for a material violation; export within 30 days, then certified destruction. | 60 days; backups destroyed in rotation within 90 days. | Deletion "under vendor's retention policy", or fees continue after the BAA ends. | 164.504(e)(1)(ii) and (e)(2)(ii)(J). |
| Precedence and state law | BAA prevails over all vendor terms on PHI; prompt amendment for rule changes; Part 2 and California riders where relevant. | BAA prevails except on fees; signed amendments within 30 days of a rule change. | Vendor amends the BAA by posting. | Proposed Security Rule changes would require BAA revisions. |
45 C.F.R. 164.410(b) requires a business associate to report a breach "without unreasonable delay and in no case later than 60 calendar days after discovery of a breach." The covered entity then owes individuals notice within the same outer limit, per the HHS breach notification summary. In sequence, the two clocks can leave patients waiting four months.
They can also overlap: 164.404(a)(2) treats a breach as known to the covered entity once a workforce member or "agent of the covered entity (determined in accordance with the federal common law of agency)" knows of it. Holland & Hart advises confirming the vendor acts "as an independent contractor," and notes that deadlines are fine "so long as such conditions do not establish an agency relationship."
State law can be faster. California's Health and Safety Code 1280.15(b) gives licensed clinics, health facilities, home health agencies and hospices "15 business days" after detection to report unauthorized access to the state and the patient. Kelli Fleming of Burr & Forman recommends "no more than a 10-day notice period."
Covered entity draft.
Business Associate will notify Covered Entity in writing within seventy-two (72) hours after it discovers, as described in 45 C.F.R. 164.410(a)(2), any Breach of Unsecured Protected Health Information, any suspected Breach, or any Security Incident resulting in unauthorized access to Protected Health Information. The first notice will state what is then known, and Business Associate will deliver everything listed in 45 C.F.R. 164.410(c) within ten (10) days after discovery. Business Associate performs this Agreement as an independent contractor and is not Covered Entity's agent.
Where to settle.
Business Associate will report any Breach of Unsecured Protected Health Information to Covered Entity within ten (10) business days after discovery and will complete the information required by 45 C.F.R. 164.410(c) within thirty (30) days after discovery.
Vendors say they cannot report until forensics finish, which Promise Legal calls "a stall tactic." Accept phased information and hold the first-notice date; California facilities should stay at 72 hours.
Vendors ask to combine data across clients, strip identifiers, and build models from the result. 164.501 defines data aggregation as combining PHI from more than one covered entity for analyses relating to their health care operations, so a benchmarking product sold to others falls outside it.
Once data is de-identified, "it is no longer considered protected health information," according to HHS's de-identification guidance. The same guidance says a covered entity may use a business associate to de-identify PHI "only to the extent such activity is authorized by their business associate agreement," so the control point is the act of de-identifying. Expert determination under 164.514(b)(1) requires a documented finding that "the risk is very small."
For identifiable data, a BAA cannot authorize uses the covered entity could not make, and a model built for all customers serves the vendor's own purpose. If a model developer pays for PHI, the sale ban in 164.502(a)(5)(ii) applies too.
Covered entity draft.
Business Associate will not de-identify Protected Health Information except as necessary to perform the Services, and will not use Protected Health Information or data derived from it, including de-identified data, to train, fine-tune, test or improve any artificial intelligence model other than one used solely to perform the Services for Covered Entity. Business Associate will impose the same restriction on each Subcontractor that provides model services.
Where to settle.
Business Associate may de-identify Protected Health Information only under 45 C.F.R. 164.514(b)(1), will give Covered Entity the expert's written determination before any use, will not attempt to re-identify any individual, and will not sell or license the data. Training models offered to other customers on that data requires Covered Entity's written consent, which Covered Entity may withdraw on thirty (30) days' notice for data not yet used.
Each downstream party handling PHI for the vendor needs its own written agreement, which for an AI product means at least the cloud host and the model provider. HHS's cloud computing guidance says "Lacking an encryption key does not exempt a CSP from business associate status," so a cloud service provider (CSP) holding only encrypted data still counts.
HIPAA has no offshore ban. HHS warns that storing electronic PHI overseas "may increase the risks and vulnerabilities to the information." A Lathrop GPM checklist notes covered entities may bar subcontractors "outside of the U.S. or not subject to jurisdiction in U.S. courts."
HIPAA does not say who pays. Discussing HHS's 2019 fact sheet, Jones Day noted that business associates "may also be liable to covered entities through contractual liability," and the contract is the covered entity's most dependable route to recover breach costs.
The cap is where a BAA leaks when it sits as an exhibit to a services agreement capped at a year of fees. Under California's Confidentiality of Medical Information Act (CMIA), Civil Code 56.36(b) lets a patient recover "nominal damages of one thousand dollars ($1,000)" for negligent release in violation of the act, without proving actual damages. Under 56.10(c)(3), a billing, claims management or data processing vendor may not further disclose what it receives "in a way that would violate this part." Melissa Krasnow's IRMI commentary asks "whether a party has and will have cyber liability insurance coverage," and in what amounts.
Covered entity draft.
Business Associate will defend, indemnify and hold harmless Covered Entity from third-party claims, regulatory penalties and settlements, and reasonable breach response costs (notices, call center, twenty-four (24) months of credit or identity monitoring, and forensic investigation) arising from a breach of this Agreement or of HIPAA by Business Associate or its Subcontractors. No limitation of liability in the Services Agreement applies to this Section. Business Associate will maintain network security and privacy liability insurance of at least [$5,000,000] per claim, covering notification costs and, where insurable, regulatory fines, during the term and for three (3) years after it.
Where to settle.
Each party will indemnify the other for losses arising from its own breach of this Agreement. Business Associate's liability under this Agreement is separate from and in addition to the cap in the Services Agreement, and is limited to the per-claim insurance limit this Agreement requires Business Associate to carry.
Expect a request for mutual indemnity. Accept it for the covered entity's own failures and keep the carve-out from the services cap; tying the cap to the policy limit funds the promise.
164.504(e)(2)(ii)(J) requires return or destruction "if feasible." Where conditions "make the return or destruction of the information infeasible," protection extends to what is kept and further use is limited to those reasons. Promise Legal flags "as soon as practicable" as setting no real deadline, and HHS's cloud guidance tells covered entities to make sure the BAA and service level agreement "do not prevent the entity from accessing its ePHI."
Export comes first, then destruction. Because 164.504(e)(1)(ii) requires a covered entity that knows of a pattern of material breach to take reasonable steps to cure it and, if those fail, terminate where feasible, the BAA's termination right should end the services agreement too.
Covered entity draft.
Within thirty (30) days after termination, Business Associate will return all Protected Health Information to Covered Entity in [format], then destroy all remaining copies, including those held by Subcontractors, and certify the destruction in writing. Any Protected Health Information Business Associate believes it cannot feasibly return or destroy will be described in the certificate with the reason, will remain subject to this Agreement for as long as it is kept, and will be used or disclosed only for that reason.
Where to settle.
Business Associate will complete return and destruction within sixty (60) days after termination, except that backups will be destroyed in normal rotation within ninety (90) days and remain subject to this Agreement until then.
Expect "infeasible" to be claimed for every backup and analytics copy; make the vendor list each category.
A BAA implements HIPAA for PHI. A DPA implements Article 28 of the General Data Protection Regulation (GDPR) for personal data processed for a controller. A telehealth company with EU patients needs both.
| Point | BAA (HIPAA) | DPA (GDPR Article 28) |
|---|---|---|
| Vendor's breach notice | Without unreasonable delay and no later than 60 calendar days after discovery | Processor notifies "without undue delay after becoming aware"; the controller tells the regulator within 72 hours where feasible |
| Subcontractors | Written "satisfactory assurances"; no customer approval required | Needs "prior specific or general written authorisation of the controller" |
| Audit | Records open to HHS; customer audit by contract only | Processor must "allow for and contribute to audits, including inspections" |
| End of contract | Return or destroy if feasible | Delete or return "at the choice of the controller" |
| De-identified data | Outside HIPAA once de-identified under 164.514 | Pseudonymized data stays personal data (Recital 26) |
When both apply, use one agreement with HIPAA and GDPR schedules and take the stricter term on each point. The DPA playbook covers Article 28 and transfers.
| Vendor or buyer | What changes in the BAA | Why |
|---|---|---|
| Cloud host or storage provider | A BAA is needed even for encrypted storage without the key; put region and export terms in the order form if the BAA is fixed. | HHS cloud guidance: agreements must not "prevent the entity from accessing its ePHI." |
| Billing or revenue cycle company | The issues become aggregation across clients and exit. Claims data is needed after termination for payer appeals, so transition precedes destruction. | Aggregation is limited to the covered entity's health care operations (164.501). |
| AI vendor (ambient scribe, chatbot, coding assistant) | Training ban, the model provider listed as a subcontractor with its own BAA, retention limits for prompts, audio and outputs, and expert determination only. | Promise Legal: business associates have "no HIPAA authority to use PHI for product development or AI model training." |
| Substance use disorder program under 42 C.F.R. Part 2 | A Part 2 rider: no use in proceedings against patients without consent, or a court order and subpoena; breach notice covers Part 2 records. | HHS Part 2 page: compliance "was required by February 16, 2026." |
| California provider or health app | Shorter clock for licensed facilities and indemnity that reaches state claims under the CMIA. | Health and Safety Code 1280.15(b); Civil Code 56.06: app makers "shall be deemed to be a provider of health care." |
| Small practice vs health system | A small practice on vendor paper should spend its asks on the breach clock, the training ban and export. A health system issues its own BAA with insurance, audit, an offshore ban and annual safeguard verification. | Leverage; HHS proposed "written verification at least once every 12 months", with final action projected for July 2027 (McDermott). |
Gavel Exec is AI contract review and drafting software for Microsoft Word. Paste the table above into a spreadsheet, or upload a checklist or signed BAAs (.docx, PDF or .csv), and it generates playbook rules from them; see how playbooks work in Gavel Exec. In Word, it marks up the vendor's BAA as priority-ranked tracked changes, explains each change and flags missing terms.
Benchmarking, in the web app, marks each provision on-market, off-market or missing. Pricing is $160 per user per month or $1,740 per user per year; every user starts with 25 free queries and no credit card.
What must a business associate agreement include?
Under 45 C.F.R. 164.504(e) and 164.314(a), it must limit uses and disclosures, require safeguards, require reports of improper uses, security incidents and breaches, and bind subcontractors to the same terms. It must also support patient rights, open records to HHS, require return or destruction of PHI at termination if feasible, and let the covered entity terminate for a material violation.
How long does a business associate have to report a breach under HIPAA?
No later than 60 calendar days after discovery, and without unreasonable delay, under 45 C.F.R. 164.410(b). HHS's sample provisions allow a stricter timeframe, and practitioners recommend 10 days or fewer, because the covered entity's own 60-day deadline may already be running.
What is the difference between a BAA and a DPA?
HIPAA requires a BAA when a vendor handles protected health information for a covered entity or business associate. GDPR Article 28 requires a DPA when a processor handles personal data for a controller, so a vendor handling PHI for a covered entity and GDPR-covered data for a controller needs both.
Can a business associate use PHI to train AI models?
Only as the BAA permits, and a BAA cannot authorize uses the covered entity itself could not make. A business associate may also de-identify PHI only if its BAA authorizes it, so the covered entity controls training on de-identified data too.
Does a cloud provider that stores only encrypted PHI need a BAA?
Yes. HHS guidance says that lacking an encryption key does not exempt a cloud service provider from business associate status and obligations.
What happens if PHI cannot be returned or destroyed when a BAA ends?
The business associate must extend the BAA's protections to the retained PHI and limit further use to the reasons that make return or destruction infeasible. Ask for a written description of what is kept and why.
Related reading: the DPA playbook, a HIPAA BAA template, and how to build a contract playbook.
AI contract review and redlining in Microsoft Word, checked against your own playbook, with the reasoning behind each change.