A Missing Signature Cost One Company $4.3 Million
In 2016, Advocate Health Care Network paid $5.55 million to settle HIPAA violations with HHS. Among the findings: the organization failed to obtain a HIPAA compliant business associate agreement from a vendor that had access to the electronic protected health information (ePHI) of roughly four million individuals. That wasn't the only issue — but it was the one that made the settlement historic.
I've reviewed hundreds of BAAs across health systems, clinics, and startups. Most of them are missing something. Sometimes it's a technicality. Sometimes it's a gaping hole that would make the entire agreement unenforceable in an OCR investigation.
If your organization shares PHI with any outside entity — a cloud provider, billing company, shredding service, even a remote transcriptionist — you need a BAA that actually holds up. Here's what that looks like in practice.
What Is a HIPAA Compliant Business Associate Agreement?
A business associate agreement is a legally binding contract between a covered entity and a business associate. It establishes what the business associate can and cannot do with protected health information. Under the HIPAA Privacy Rule and the HITECH Act, no covered entity may share PHI with a vendor or subcontractor unless a valid BAA is in place before that access begins.
A HIPAA compliant business associate agreement isn't just a form you download and sign. It must contain specific provisions required under 45 CFR § 164.504(e). Miss even one required element, and OCR can treat the agreement as if it doesn't exist.
Who Counts as a Business Associate?
If someone outside your workforce creates, receives, maintains, or transmits PHI on your behalf, they're a business associate. That includes IT vendors, cloud hosting providers, billing services, consultants with EHR access, answering services, and attorneys who handle cases involving patient information.
Even subcontractors of your business associates need their own BAAs. The 2013 Omnibus Rule made that crystal clear.
The 9 Elements Every BAA Must Include
I've seen BAAs that run two pages and BAAs that run forty. Length doesn't matter. What matters is whether these required provisions are present and specific:
- Permitted and required uses of PHI. The BAA must describe exactly what the business associate is allowed to do with the information.
- Prohibition on unauthorized use or disclosure. The agreement must explicitly bar the associate from using PHI in ways the contract doesn't allow.
- Safeguards requirement. The business associate must agree to use appropriate administrative, physical, and technical safeguards to protect ePHI.
- Reporting obligations. The associate must report any unauthorized use, disclosure, or security incident to the covered entity.
- Breach notification duties. Under the Breach Notification Rule, the business associate must notify the covered entity of any breach of unsecured PHI without unreasonable delay — and no later than 60 days after discovery.
- Subcontractor flow-down. The BAA must require the business associate to impose the same restrictions on any subcontractor that handles PHI.
- Access to PHI for individuals. The agreement must ensure the covered entity can fulfill individuals' rights to access their records.
- Amendment obligations. The associate must make PHI available for amendment when required.
- Termination provisions. The BAA must specify that the covered entity can terminate the contract if the business associate violates it, and that PHI must be returned or destroyed upon termination.
HHS publishes sample BAA provisions on their website. Use them as a starting checklist — but don't treat them as a fill-in-the-blank template. Your agreement needs to reflect your actual relationship with each vendor.
The Mistakes I See Most Often
Using One Generic BAA for Every Vendor
Your cloud hosting provider and your janitorial service have very different access to PHI. A single boilerplate BAA rarely captures the specific uses, safeguards, and termination terms each relationship demands. I've watched organizations fail OCR audits because their BAA language didn't match what the vendor actually did with patient data.
Forgetting Subcontractor BAAs
Your billing company hires a software vendor. That vendor processes claims data containing ePHI. If there's no subcontractor BAA in place, your organization is exposed — even though you never dealt with the subcontractor directly. The chain of accountability under HIPAA doesn't break just because you didn't know about it.
Treating the BAA as a One-Time Event
BAAs aren't "set it and forget it" documents. When a vendor's scope of work changes, when you adopt new technology, or when regulations evolve, your BAA needs to be reviewed and updated. I recommend reviewing every active BAA at least annually as part of your risk analysis process.
No Termination Follow-Through
The BAA says the business associate must return or destroy PHI when the relationship ends. But does your organization actually verify that happens? In my experience, fewer than 30% of covered entities I've consulted with have a documented process for confirming PHI destruction after vendor termination.
What Does OCR Actually Look for During an Investigation?
When OCR investigates a breach or complaint, one of the first things they request is a copy of the relevant BAA. They're checking several things:
- Does a signed BAA exist at all?
- Was it executed before the business associate gained access to PHI?
- Does it contain every element required by 45 CFR § 164.504(e)?
- Does the covered entity have a process for monitoring business associate compliance?
- Were breach notification timelines followed as outlined in the agreement?
In the case of North Memorial Health Care, OCR found that the organization gave a business associate access to the ePHI of 289,904 individuals without ever executing a BAA. The resulting settlement in 2016 was $1.55 million, plus a corrective action plan. The absence of a HIPAA compliant business associate agreement turned a data incident into a multimillion-dollar enforcement action.
You can review OCR's enforcement outcomes on the HHS Resolution Agreements page.
How Remote Work Makes BAAs Even More Critical
The shift to remote and hybrid healthcare work has multiplied the number of business associates most organizations rely on. Video conferencing platforms, remote desktop tools, cloud fax services, virtual scribes — each one potentially touches PHI and requires a valid BAA.
If your workforce includes remote employees or contractors, make sure they understand how BAAs affect their daily workflows. Our HIPAA training for remote healthcare workers covers the specific risks remote setups introduce, including how to verify vendor compliance before sharing ePHI.
For staff who handle PHI from home offices, the Working from Home & PHI course walks through practical safeguards that align with BAA requirements — like encryption, secure disposal, and access controls in non-clinical settings.
Do Community Health Workers Need to Know About BAAs?
Yes. Community health workers often operate in environments where PHI flows between organizations — social service agencies, public health departments, and community-based organizations. Many of these relationships technically require BAAs, but the agreements are often missing entirely.
If your organization employs or contracts with community health workers, they need role-specific training that covers how PHI is shared across organizational boundaries. Our HIPAA training for community health workers addresses these exact scenarios.
A Quick BAA Compliance Checklist for 2026
Use this as a quarterly gut check:
- Do you have a current, signed BAA with every vendor that touches PHI?
- Does each BAA include all nine required elements listed above?
- Are subcontractor BAAs in place for downstream vendors?
- Have you reviewed and updated BAAs in the last 12 months?
- Do you have documented proof of PHI return or destruction when vendor relationships end?
- Is your workforce trained on what a business associate relationship means and why it matters?
If you answered "no" or "I'm not sure" to any of those, you have a gap that OCR could turn into a finding.
The Bottom Line on Business Associate Agreements
A HIPAA compliant business associate agreement is not a formality. It is the legal mechanism that extends HIPAA's protections to every outside party that handles your patients' data. Without one — or with a defective one — your covered entity bears the liability.
I've seen organizations spend six figures defending themselves after a breach that a solid BAA could have prevented — or at least mitigated. Get your agreements reviewed. Train your workforce on what business associate relationships actually require. And never assume the template you downloaded three years ago still meets today's regulatory expectations.
Your patients trust you with their most sensitive information. Make sure every vendor in your chain has earned that trust in writing.