A business associate agreement (BAA) is the written contract that HIPAA calls for between a covered entity and a vendor that creates, receives, maintains or transmits protected health information on its behalf1. A covered entity may share the information with the vendor if it obtains satisfactory assurance that the vendor will safeguard it, and the rule requires that assurance to be written down in a contract2.
We read HHS's guidance, the text of the rules and the Federal Register on November 10 and 11, 2026. Every figure below carries its source, and the software counts come from our own check of 28 tools, read on November 10 and 11, 2026. We are not lawyers. Read the rule and the agreement yourself, or ask your counsel how they apply to you.
Who counts as a business associate?
HHS describes a business associate as a person or organization that performs functions or activities on behalf of a covered entity that involve creating, receiving, maintaining or transmitting protected health information1. The test is what the vendor does with the information. A subcontractor that does those things on behalf of another business associate is a business associate too1.
The Security Rule carries that down the chain: the contract must provide that the business associate will ensure its subcontractors agree to comply with the applicable requirements3.
Is a cloud or AI vendor a business associate if the data is encrypted?
Yes, when it maintains patient information for you. HHS's cloud computing guidance says a cloud service provider (CSP) that stores only encrypted electronic protected health information (ePHI) and lacks an encryption key is still a business associate4. Encryption protects the data and leaves the vendor inside the definition.
The conduit exception does not change this. It is narrow and covers entities that provide mere courier services, such as the U.S. Postal Service or United Parcel Service, and their electronic equivalents, such as internet service providers5. The 2013 Omnibus Rule preamble puts the line at the transient or persistent nature of the opportunity to access the information5. HHS's cloud guidance says a CSP that maintains ePHI for storage has more persistent access and counts as a business associate, not a conduit, even if it never views the data4.
We think the same test reaches an AI vendor that receives or keeps patient information for a practice. An HHS statement that names AI vendors as business associates is NF; the nearest evidence is HHS's 2025 proposal, which says ePHI in AI training data, prediction models and algorithm data that a regulated entity maintains for covered functions is protected by the HIPAA Rules6.
When is a business associate agreement required?
The rule lets a covered entity disclose protected health information to a business associate, or allow one to create, receive, maintain or transmit it, if the entity obtains satisfactory assurance that the associate will appropriately safeguard it2. The assurance has to be documented in a written contract or other written agreement that meets 45 CFR 164.504(e)2. The agreement therefore belongs in place before the first disclosure.
HHS says a covered entity or business associate that uses a CSP to maintain ePHI without entering into a BAA with the CSP is in violation of the HIPAA Rules, and it cites 45 CFR 164.308(b)(1) and 164.502(e)4.
Two exits appear in the sources. The first is the conduit exception described above. The second is de-identified data: HHS's cloud guidance says a CSP is not a business associate if it receives and maintains only information de-identified by the processes the Privacy Rule requires4.
A cloud provider that was not told it holds ePHI has a separate protection. HHS says it may assert an affirmative defense under 45 CFR 160.410 if it corrects any non-compliance within 30 days of when it knew or should have known of the violation4. That defense is the provider's, and the practice's own duty to have an agreement stands.
What must a business associate agreement say?
The Privacy Rule sets the contents in 45 CFR 164.504(e)(2), which lists the implementation specifications that a contract between a covered entity and a business associate must meet3. The Security Rule adds 45 CFR 164.314(a)(2) for electronic information3. Use this list to check a draft or a vendor's form:
- It is written down, as a written contract or other written agreement or arrangement2.
- It establishes the permitted and required uses and disclosures of protected health information by the business associate3.
- It does not authorize the business associate to use or further disclose the information in a way that would violate the Privacy Rule if the covered entity did it. The rule allows two narrow exceptions, for the associate's proper management and administration and for data aggregation7.
- For electronic information, it provides that the business associate will comply with the applicable requirements of the Security Rule3.
- It provides that the business associate will ensure any subcontractors that handle electronic information agree to comply with the applicable Security Rule requirements3.
- It requires the business associate to report security incidents involving electronic information3.
These are the terms our sources quote, and both sections list more. Read 45 CFR 164.504 and 45 CFR 164.314 in full before you rely on this list. The resolution agreement with Women & Infants Hospital of Rhode Island cites both sections for one gap, the lack of satisfactory assurances from its business associate8.
Business associate agreement template and sample
HHS published its sample business associate agreement provisions on January 25, 20139. HHS says use of the sample provisions is not required for compliance with the HIPAA Rules and that the language may be changed to reflect the arrangement between the covered entity and the business associate9. It also says the sample language may not alone be sufficient to form a binding contract under state law9.
A sample from 2013 is dated, so check any template against the six items above and the current text of the two sections. We do not supply a template of our own; the wording is a job for the practice's counsel and the vendor's.
Some vendors publish a form that you accept as it stands. Google Cloud's BAA is one: Google's page says the person who accepts it represents and warrants that they have full legal authority to bind the customer and have read the agreement10. The same page says the BAA does not apply to any Google product, service or feature that is not a Covered Service10. Read a vendor's form for its list of covered services as well as for its terms.
What happens without a business associate agreement?
HHS reports these seven settlements in its press releases and resolution agreements. Each is a settlement of potential violations: the amount is what the entity agreed to pay, and none is a civil money penalty. The years run from 2016 to 2023, so every amount is dated.
| Entity | Year | Amount | What HHS says was missing | Source |
|---|---|---|---|---|
| North Memorial Health Care | 2016 | $1,550,000 | No agreement with a major contractor, and no organization-wide risk analysis | 11 |
| Raleigh Orthopaedic Clinic, P.A. | 2016 | $750,000 | No agreement before PHI of 17,300 patients went to a potential business partner | 12 |
| Women & Infants Hospital of Rhode Island (Care New England Health System) | 2016 | $400,000 | No satisfactory assurances from its business associate, September 23, 2014 to August 28, 2015 | 8,13 |
| Center for Children's Digestive Health | 2017 | $31,000 | No signed agreement with a records storage vendor before October 12, 2015; disclosures began in 2003 | 14 |
| Pagosa Springs Medical Center | 2018 | $111,400 | No written BAA with Google; PHI of at least 557 people disclosed | 15,16 |
| Advanced Care Hospitalists PL | 2018 | $500,000 | No BAA with a vendor it had not vetted | 17 |
| MedEvolve, Inc. (itself a business associate) | 2023 | $350,000 | No BAA with a subcontractor | 18 |
HHS says the North Memorial, Pagosa Springs and MedEvolve settlements also resolve other potential violations, so none of those amounts is the price of the missing agreement alone11,15,18. HHS's cloud guidance also says OCR entered a resolution agreement with a covered entity that stored ePHI of over 3,000 individuals on a cloud-based server without a BAA with the CSP4.
How many agreements OCR has reviewed, or how many of its cases turn on a missing one, is NF; the nearest evidence is the seven settlements above. An OCR settlement over a missing agreement with an AI vendor is NF; the nearest is Pagosa Springs' disclosure to Google, a cloud provider16.
How much is the penalty for a HIPAA violation?
HHS's inflation-adjustment table, published January 28, 2026, sets the civil money penalty for each of four culpability tiers; its figures are the 2025 adjusted amounts19. On October 21, 2026, HHS issued a notice that there will be no cost-of-living adjustment for 2026 and that it will continue to use the 2025 levels20. The table below is therefore the schedule in force as of this page's date.
| Tier | Violation due to | Per violation | Source |
|---|---|---|---|
| 1 | Entity did not know, and with reasonable diligence would not have known | $145 to $73,011 | 21 |
| 2 | Reasonable cause and not willful neglect | $1,461 to $73,011 | 19,21 |
| 3 | Willful neglect, corrected within 30 days | $14,602 to $73,011 | 19,21 |
| 4 | Willful neglect, not corrected within 30 days | $73,011 to $2,190,294 | 19,21 |
The same table sets a calendar-year cap of $2,190,29421. That is the regulation's ceiling19. HHS's April 30, 2019 notice of enforcement discretion says HHS applies a different annual limit to each of the four tiers: $25,000 for no knowledge, $100,000 for reasonable cause, $250,000 for corrected willful neglect and $1,500,000 for uncorrected willful neglect, before inflation adjustment22.
The two sources do not give one number. The 2026 table has a single cap, and the 2019 notice has four limits in 2019 dollars. The notice says the discretion is effective indefinitely22, and we did not check whether later rulemaking superseded it. The inflation-adjusted values of the four 2019 limits are NF; the nearest evidence is the 2026 table's single cap above.
Are business associates directly liable under HIPAA?
Yes, for some requirements. HHS's fact sheet on direct liability says Congress enacted the HITECH Act in 2009, making business associates of covered entities directly liable for compliance with certain requirements of the HIPAA Rules23. The fact sheet lists failing to enter into agreements with subcontractors that create or receive protected health information, and failing to comply with the implementation specifications for those agreements23.
OCR has acted on that. HHS reports that in 2023 MedEvolve, a business associate, agreed to pay $350,000 to settle potential violations that included failing to enter into an agreement with a subcontractor under 45 CFR 164.502(e)(1)(ii)18.
Liability runs in more than one direction. HHS's cloud guidance says its violation sentence covers a business associate that uses a CSP without an agreement, as well as a covered entity4. A vendor's agreement with you does not cover the vendors beneath it, because each of them is a business associate in its own right and needs its own1,3.
Does a business associate agreement cover AI tools?
A BAA covers an AI tool only as far as the agreement and its list of services reach10,24. The rules HHS applies to an AI tool are the rules it applies to other technology. In its January 6, 2025 proposal to update the Security Rule, HHS wrote that the rule was designed to be technology-neutral and continues to provide the foundation for protecting ePHI as technology changes25. The proposal also says a risk analysis must consider, among other things, the type and amount of ePHI an AI tool accesses, to whom the data is disclosed and to whom the output is provided6.
That update is a proposed rule. Comments closed on March 7, 2025, and it remains proposed as of November 202625. The Unified Agenda entry we read on November 10, 2026 lists the stage as long-term actions and the final action as 07/00/202726. That date is a target, and until a final rule issues the existing Security Rule stands.
HHS says OCR does not endorse, certify or recommend specific technology or products4. A vendor that describes itself as approved by HHS is describing something HHS says it does not do.
On that check, of 28 software tools small practices commonly use, 9 sign a business associate agreement without requiring a special tier, 15 sign one only on certain plans and 4 offer none, according to the vendors' own pages27. The four with none are Zapier, Calendly, Google Analytics and the Meta Pixel27. The 15 plan-gated tools include ChatGPT and Claude27, and 6 of the 15 do not publish the price of the qualifying plan27.
For what Microsoft Azure, Amazon Web Services Bedrock, Google Cloud, OhMD and Zoho each publish about their agreements, see BAA for AI. It compares what each publishes and does not rank them.
What a business associate agreement does not do
A signed agreement is necessary and never enough by itself. It covers what it says. Google's BAA does not apply to PHI that the customer creates, receives, maintains or transmits outside the Covered Services10. Google tells BAA customers not to use pre-GA offerings with PHI unless expressly noted28. AWS says services not on its list may be used, including in HIPAA Accounts, only if they do not process or store ePHI29. Which services and features a practice switches on is the practice's decision.
Configuration and compliance stay with the practice. Google says customers are responsible for ensuring that their environment and applications are properly configured and secured according to HIPAA requirements28. AWS says customers are responsible for ensuring their own HIPAA compliance when using any AWS service29. Microsoft says an organization is responsible for an adequate compliance program and for aligning its use of Azure with HIPAA and the HITECH Act24.
Risk analysis is a separate duty. HHS says the North Memorial settlement covered the lack of an organization-wide risk analysis as well as the missing agreement11. HHS's release on the Care New England settlement says the case illustrates the importance of reviewing and updating, as necessary, business associate agreements13.
No rule requires certification. HHS says no standard or implementation specification in the Security Rule requires a covered entity to certify its compliance30. It also says it does not endorse or otherwise recognize private organizations' certifications regarding the Security Rule, and that such certifications do not absolve covered entities of their legal obligations under it30. Both statements concern the Security Rule, which is part of HIPAA and not all of it.
How we handle business associate agreements
Our HIPAA-ready programs run under a signed business associate agreement with the practice and a signed agreement with each service in the chain, and we ask the practice to send no patient information until they are signed. Essentials costs $1,500 to set up and $699 a month per location after a compliance consultation31; Keegan Justis architects each program, and Mike Golliet and Kyle Grenier build it. A program is a compliance layer added to a plan31, our agreement covers our part of the work, and the practice stays responsible for its own compliance.
People also ask
What is the purpose of a business associate agreement?
It documents the satisfactory assurance a covered entity must obtain before a vendor handles protected health information for it. The contract sets what the vendor may do with the information and commits the vendor to safeguards2,3.
When is a business associate agreement required?
Before a covered entity discloses protected health information to a vendor that creates, receives, maintains or transmits it on the entity's behalf2. It is not required for a conduit, which is a mere courier or transmission service, or for a vendor that receives only de-identified information4,5.
What are the requirements for a HIPAA business associate agreement?
It must be in writing and establish the business associate's permitted and required uses and disclosures3. For electronic information it must also provide for Security Rule compliance, subcontractor agreements and security incident reporting3. Read both sections in full.
Is there a HIPAA business associate agreement template?
Yes. HHS published sample provisions on January 25, 20139. HHS says using them is not required and the language may be changed to fit the arrangement9. We supply no template of our own. Check any template against 45 CFR 164.504(e)(2) and 164.314(a)(2).
What makes a business associate agreement HIPAA compliant?
It contains what 45 CFR 164.504(e)(2) and, for electronic information, 164.314(a)(2) require3. HHS says no standard in the Security Rule requires a covered entity to certify its compliance30, so the test is the text of the agreement.
Do I need a business associate agreement with a subcontractor?
The business associate does. A subcontractor that handles the information for a business associate is itself a business associate1. HHS's direct liability fact sheet lists failing to enter into those agreements, and MedEvolve settled with OCR for $350,000 in 2023 over one18,23.
What happens if you do not have a business associate agreement?
HHS says a practice that uses a cloud provider to maintain ePHI without one is in violation of the HIPAA Rules4. HHS reports settlements over missing agreements from $31,000 to $1,550,00011,14. Civil money penalties run from $145 per violation in the lowest tier21 to $2,190,294 in the highest19.
Do AWS, Google Cloud and Microsoft offer a business associate agreement?
Each says it does. AWS says you review and accept its BAA, which it calls an addendum, in AWS Artifact32. Google says you opt in within one Google Cloud project33. Microsoft says there is no separate contract to sign for Azure24. See BAA for AI.
How to read this page: NF not found, ( ) our arithmetic on cited figures, and a small number points to a source below.
Sources
- HHS Office for Civil Rights. Business Associates Frequently Asked Questions (FAQs). U.S. Department of Health and Human Services, 2026. hhs.gov/hipaa/for-professionals/privacy/guidance/business-associates/i
- U.S. Department of Health and Human Services. 45 CFR 164.502 (Code of Federal Regulations, current text as reproduced by Cornell LII). Legal Information Institute, Cornell Law School (copy of the CFR), 2024. law.cornell.edu/cfr/text/45/164.502
- Office of the Federal Register and Office for Civil Rights. 45 CFR 164.314 - Organizational requirements. National Archives and Records Administration / Government Publishing Office, 2026. ecfr.gov/api/renderer/v1/content/enhanced/2026-11-05/title-45?part=164
- Office for Civil Rights. Guidance on HIPAA & Cloud Computing. U.S. Department of Health and Human Services, 2022. hhs.gov/hipaa/for-professionals/special-topics/cloud-computing/index.h Held through its record or abstract; passage not matched.
- Office for Civil Rights. Modifications to the HIPAA Privacy, Security, Enforcement, and Breach Notification Rules (Omnibus Final Rule). Office of the Federal Register, National Archives and Records Administration, 2013. federalregister.gov/documents/full_text/html/2013/01/25/2013-01073.htm
- HHS Office for Civil Rights. HIPAA Security Rule To Strengthen the Cybersecurity of Electronic Protected Health Information (notice of proposed rulemaking, 90 FR 898). Federal Register (govinfo.gov), 2025-01-06. govinfo.gov/content/pkg/FR-2025-01-06/pdf/2024-30983.pdf
- U.S. Department of Health and Human Services. 45 CFR 164.504 (Code of Federal Regulations, current text as reproduced by Cornell LII). Legal Information Institute, Cornell Law School (copy of the CFR), 2024. law.cornell.edu/cfr/text/45/164.504
- Office for Civil Rights. Women & Infants Hospital of Rhode Island Resolution Agreement and Corrective Action Plan. U.S. Department of Health and Human Services, 2016. hhs.gov/sites/default/files/9-14-16-wih-racap-1.pdf
- Office for Civil Rights. Business Associate Contracts: Sample Business Associate Agreement Provisions. U.S. Department of Health and Human Services, 2013. hhs.gov/hipaa/for-professionals/covered-entities/sample-business-assoc Held through its record or abstract; passage not matched.
- GCP HIPAA BAA | Google Cloud. Google Cloud, 2026. cloud.google.com/terms/hipaa-baa
- Office for Civil Rights. $1.55 million settlement underscores the importance of executing HIPAA business associate agreements. U.S. Department of Health and Human Services, 2016. hhs.gov/hipaa/for-professionals/compliance-enforcement/agreements/nort Held through its record or abstract; passage not matched.
- Office for Civil Rights. Raleigh Orthopaedic Clinic Resolution Agreement and Corrective Action Plan. U.S. Department of Health and Human Services, 2016. hhs.gov/hipaa/for-professionals/compliance-enforcement/agreements/rale Held through its record or abstract; passage not matched.
- Office for Civil Rights. HIPAA settlement illustrates the importance of reviewing and updating, as necessary, business associate agreements – September 23, 2016. U.S. Department of Health and Human Services, 2016. hhs.gov/hipaa/for-professionals/compliance-enforcement/agreements/wih/ Held through its record or abstract; passage not matched.
- Office for Civil Rights. No Business Associate Agreement? $31K Mistake – April 20, 2017. U.S. Department of Health and Human Services, 2017. hhs.gov/hipaa/for-professionals/compliance-enforcement/agreements/ccdh Held through its record or abstract; passage not matched.
- Office for Civil Rights. Colorado hospital failed to terminate former employee’s access to electronic protected health information. U.S. Department of Health and Human Services, 2018. hhs.gov/hipaa/for-professionals/compliance-enforcement/agreements/pago Held through its record or abstract; passage not matched.
- Office for Civil Rights. Pagosa Springs Medical Center Resolution Agreement and Corrective Action Plan. U.S. Department of Health and Human Services, 2018. hhs.gov/sites/default/files/pagosa-springs-medical-center-signed-ra-ca
- Office for Civil Rights. Florida contractor physicians' group shares protected health information with unknown vendor without a business associate agreement - December 4, 2018. U.S. Department of Health and Human Services, 2018. hhs.gov/hipaa/for-professionals/compliance-enforcement/agreements/ach/ Held through its record or abstract; passage not matched.
- Office for Civil Rights. MedEvolve, Inc. Resolution Agreement and Corrective Action Plan. U.S. Department of Health and Human Services, 2023. hhs.gov/hipaa/for-professionals/compliance-enforcement/agreements/mede Held through its record or abstract; passage not matched.
- U.S. Department of Health and Human Services. Annual Civil Monetary Penalties Inflation Adjustment (Federal Register document 2026-01688). Federal Register, 2025 adjustment, published 2026-01-28. public-inspection.federalregister.gov/2026-01688.pdf
- Office of the Assistant Secretary for Financial Resources. No Adjustment to HHS Civil Monetary Penalty Amounts for 2026. Office of the Federal Register, National Archives and Records Administration, 2026. federalregister.gov/documents/full_text/html/2026/10/21/2026-21524.htm
- Office of the Assistant Secretary for Financial Resources. Annual Civil Monetary Penalties Inflation Adjustment. Office of the Federal Register, National Archives and Records Administration, 2026. federalregister.gov/documents/full_text/html/2026/01/28/2026-01688.htm
- U.S. Department of Health and Human Services. Notification of Enforcement Discretion Regarding HIPAA Civil Money Penalties (84 FR 18151). Federal Register (govinfo.gov), 2019-04-30. govinfo.gov/content/pkg/FR-2019-04-30/pdf/2019-08530.pdf
- Office for Civil Rights. Direct Liability of Business Associates. U.S. Department of Health and Human Services, 2009. hhs.gov/hipaa/for-professionals/privacy/guidance/business-associates/f Held through its record or abstract; passage not matched.
- Microsoft. HIPAA - Azure Compliance | Microsoft Learn. Microsoft, ms.date 2023-04-05; updated_at 2024-10-10. learn.microsoft.com/en-us/azure/compliance/offerings/offering-hipaa-us
- Office for Civil Rights. HIPAA Security Rule To Strengthen the Cybersecurity of Electronic Protected Health Information. Office of the Federal Register, National Archives and Records Administration, 2025. federalregister.gov/documents/full_text/html/2025/01/06/2024-30983.htm
- HHS Office for Civil Rights. HHS/OCR RIN 0945-AA22: HIPAA Security Rule to Strengthen the Cybersecurity of Electronic Protected Health Information (Unified Agenda entry). Reginfo.gov (OIRA / GSA), 2026-11-10. reginfo.gov/public/do/eAgendaViewRule?pubId=202510&RIN=0945-AA22
- Technical Marketing. Which software will sign a HIPAA BAA? 28 common tools, checked. Technical Marketing, 2026-11. technicalmarketing.ai/reports/hipaa-baa-availability/ Our own data.
- HIPAA compliance on Google Cloud and Google Workspace. Google Cloud, 2026. docs.cloud.google.com/docs/security/compliance/hipaa
- Amazon Web Services. HIPAA Eligible Services Reference - Amazon Web Services (AWS). Amazon Web Services, 2026-10-15. aws.amazon.com/compliance/hipaa-eligible-services-reference/
- HHS Office for Civil Rights. Are we required to “certify” our organization’s compliance with the standards of the Security Rule?. U.S. Department of Health and Human Services, 2013-07-26. hhs.gov/hipaa/for-professionals/faq/are-we-required-to-certify-our-org
- Technical Marketing. HIPAA-ready programs. Technical Marketing, 2026-11. technicalmarketing.ai/hipaa/ Our own data.
- Amazon Web Services. HIPAA Compliance - Amazon Web Services (AWS). Amazon Web Services, 2026-11. aws.amazon.com/compliance/hipaa-compliance/
- Privacy compliance and records for Google Cloud. Google Cloud Platform Console Help, 2026. support.google.com/cloud/answer/6329727