A medical billing company in Tennessee lost a laptop containing the ePHI of over 300,000 patients. The covered entity — a large health system — scrambled to respond. But the real nightmare wasn't the breach itself. It was the discovery that the BAA for HIPAA they'd signed with that billing company was four years old, missing required breach notification language, and had never been updated after the HITECH Act amendments. The health system ended up on the hook alongside its vendor.
I've watched this exact scenario unfold more times than I can count. Organizations treat the business associate agreement like a checkbox — something legal drafts once and stuffs in a drawer. That's a dangerous mistake. A BAA for HIPAA is the single most important contract you sign when sharing protected health information with any third party.
This post breaks down exactly what your BAA must contain, where organizations get it wrong, and what the Office for Civil Rights (OCR) actually looks for during investigations.
What Is a BAA for HIPAA, Exactly?
A Business Associate Agreement (BAA) is a legally binding contract between a covered entity and a business associate. It establishes exactly what the business associate can and cannot do with protected health information (PHI). Under the HIPAA Privacy Rule and the HIPAA Security Rule, covered entities — hospitals, health plans, healthcare clearinghouses — cannot share PHI with a vendor unless a valid BAA is in place.
The business associate could be your cloud hosting provider, your IT support company, your billing service, your shredding vendor, or even your email encryption platform. If they touch PHI in any form, you need a BAA.
HHS defines the relationship and requirements clearly in its official guidance on business associates. That page should be bookmarked by every compliance officer reading this.
The 8 Elements Every BAA Must Contain
I've reviewed hundreds of BAAs over the years. The ones that fail OCR scrutiny almost always miss one or more of these required provisions. Here's what the regulation demands:
1. Permitted Uses and Disclosures
The BAA must specify exactly how the business associate is allowed to use and disclose PHI. Vague language like "for business purposes" won't cut it. You need to tie uses directly to the services described in your underlying service agreement.
2. Prohibition on Unauthorized Use
The agreement must explicitly state that the business associate will not use or disclose PHI in any way that violates the HIPAA Privacy Rule. This sounds obvious, but I've seen BAAs that omit this clause entirely.
3. Safeguards Requirement
Your business associate must agree to implement appropriate administrative, physical, and technical safeguards to protect ePHI. This ties directly to the HIPAA Security Rule. If your vendor stores data in the cloud and has no encryption, your BAA should have flagged that problem before a breach does.
4. Breach Notification Obligations
This is the clause most often missing or outdated. The BAA must require the business associate to report any breach of unsecured PHI to the covered entity. The HHS Breach Notification Rule sets strict timelines. Your BAA should mirror them — or tighten them.
5. Subcontractor Accountability
If your business associate hires its own subcontractors who will access PHI, the BAA must require the business associate to ensure those subcontractors agree to the same restrictions. This is where chain-of-custody for PHI breaks down most often.
6. Access to PHI for Individuals
The BAA must ensure that the business associate makes PHI available to individuals who request it, supporting the covered entity's obligation under the HIPAA Privacy Rule's right of access.
7. Amendment of PHI
If the business associate maintains PHI in a designated record set, the BAA must require them to make amendments as directed by the covered entity.
8. Termination Provisions
The BAA must allow the covered entity to terminate the contract if the business associate violates a material term. It must also address what happens to PHI after termination — return it or destroy it, with no exceptions.
The $4.3 Million Mistake: When BAAs Go Wrong
In 2016, OCR settled with Advocate Health Care Network for $5.55 million — at the time one of the largest HIPAA settlements ever. Among the findings: Advocate failed to obtain satisfactory assurances in the form of a written BAA from a business associate that received access to ePHI. The missing BAA wasn't the only issue, but it was a central one.
More recently, in 2024, OCR settled with Inmediata Health Group for $250,000 after an investigation revealed PHI accessible via search engines. The downstream vendor relationships and BAA failures amplified the damage.
These aren't edge cases. OCR's enforcement actions consistently target BAA failures because they represent a fundamental breakdown in PHI governance. When I train compliance teams, I tell them: a missing or defective BAA is the easiest violation for OCR to prove.
Common BAA Mistakes I See Every Month
Here's where real organizations trip up — not in theory, but in practice:
- Using a generic template without customization. Every vendor relationship is different. Your cloud storage vendor and your medical transcription service handle PHI in fundamentally different ways. The BAA should reflect that.
- Never updating the BAA. The Omnibus Rule of 2013 changed BAA requirements significantly. If your agreement predates that, it's non-compliant. Period.
- Failing to track BAAs. You'd be stunned how many organizations can't produce a current list of all their business associates. If you can't find the BAA, it doesn't exist in OCR's eyes.
- Assuming SaaS vendors don't need one. If a SaaS platform stores, transmits, or processes PHI — even if they claim they "never look at it" — they're a business associate. You need a BAA for HIPAA compliance.
- Not training staff on what a BAA means operationally. Your workforce needs to understand that sharing PHI with a vendor who lacks a BAA is a violation, not just a paperwork issue. Our HIPAA Introduction Training 2026 course covers this exact scenario in practical terms.
Does Your Organization Actually Need a BAA?
If you're a covered entity — a healthcare provider who transmits any health information electronically, a health plan, or a healthcare clearinghouse — you absolutely need a BAA with every business associate that accesses PHI on your behalf.
But here's what catches people off guard: business associates also need BAAs with their own subcontractors. The Omnibus Rule made this explicit. If your billing company outsources coding to another firm, that firm needs a BAA too. The chain doesn't stop at the first vendor.
Even if you're a small practice with five employees, this applies to you. Your EHR vendor, your appointment reminder service, your cloud backup provider — all business associates, all requiring a valid BAA for HIPAA compliance.
How to Audit Your BAAs in 5 Steps
I recommend every organization do this exercise at least annually:
- Step 1: List every vendor, contractor, and service provider that touches PHI in any form.
- Step 2: Locate the signed BAA for each one. If you can't find it, flag it immediately.
- Step 3: Review each BAA against the 8 required elements listed above. Mark any gaps.
- Step 4: Check the date. If the BAA was signed before September 2013 and hasn't been updated, it needs revision now.
- Step 5: Verify that your business associates have extended BAA requirements to their subcontractors. Ask for documentation.
This audit takes a day or two for most small practices and a week for larger organizations. That time investment is trivial compared to the cost of an OCR investigation.
Training Your Workforce on BAA Obligations
The biggest gap I see isn't in legal departments. It's on the front lines. Office managers sign up for a new software tool. Marketing teams hire a mailing house. IT departments spin up a new cloud instance. None of them think to ask: "Does this vendor need a BAA?"
Workforce training must address this gap directly. Every employee who has any role in vendor selection or PHI handling should understand what triggers a BAA requirement. Our HIPAA Fundamentals course walks through real-world vendor scenarios and teaches staff exactly when to escalate a BAA question to compliance.
HHS has consistently emphasized that workforce training is not optional — it's a regulatory requirement under 45 CFR Part 164, Subpart C. That includes training on business associate relationships and the role of BAAs.
Your BAA Is Only as Strong as Your Follow-Through
Signing a BAA doesn't make you compliant. Enforcing it does. I've seen organizations with perfectly drafted agreements that never once verified whether their business associate was actually implementing the safeguards they promised.
Build BAA oversight into your compliance program. Request annual attestations. Include audit rights in the agreement. Require evidence of workforce training, encryption, and incident response capabilities from every business associate.
A BAA for HIPAA is not a one-time document. It's a living part of your compliance infrastructure. Treat it that way, and you'll be in a far stronger position the day OCR comes calling.
Ready to make sure your team understands their role? Explore our full HIPAA training catalog and build compliance from the ground up.