A hospital in North Texas discovered in 2018 that its billing vendor had been storing patient records on an unsecured cloud server for over a year. More than 300,000 individuals had their protected health information exposed. The kicker? The hospital had never signed a business associate agreement with that vendor. The result was a $4.3 million settlement with the Office for Civil Rights. That's the price of skipping paperwork most people assume is just a formality. So what is a HIPAA business associate agreement, and why does it carry that kind of financial weight? Let me walk you through everything you need to know — because I've watched organizations get blindsided by this more times than I can count.
What Is a HIPAA Business Associate Agreement, Exactly?
A business associate agreement — commonly called a BAA — is a legally binding contract between a HIPAA covered entity and any third party that creates, receives, maintains, or transmits protected health information (PHI) on its behalf. The covered entity could be a hospital, health plan, or healthcare clearinghouse. The business associate could be an IT vendor, a billing company, a shredding service, a cloud hosting provider, or even a law firm handling medical records.
The BAA spells out exactly what the business associate can and cannot do with PHI. It establishes permitted uses and disclosures, mandates safeguards, requires breach notification, and ensures that the business associate complies with applicable provisions of the HIPAA Privacy and Security Rules.
Without a signed BAA, a covered entity is in violation of HIPAA — even if the business associate never actually mishandles a single record. The agreement itself is the compliance requirement.
Why HHS Requires a BAA Before PHI Changes Hands
The Department of Health and Human Services doesn't treat the BAA as optional paperwork. Under 45 CFR § 164.502(e), a covered entity may not disclose PHI to a business associate without satisfactory assurances — in writing — that the business associate will appropriately safeguard the information.
The 2013 HIPAA Omnibus Rule tightened the screws further. It made business associates directly liable for HIPAA violations, not just contractually responsible. That means OCR can — and does — go after business associates independently.
I've seen small practices assume that a verbal agreement or a handshake with their IT guy is enough. It never is. OCR investigators look for signed, dated BAAs. If they don't find one, the penalty clock starts ticking immediately.
The $2.3 Million Mistake: Real Enforcement Actions
This isn't theoretical. OCR has collected millions from organizations that failed to execute proper business associate agreements.
- Raleigh Orthopaedic Clinic (2016): Paid $750,000 to settle allegations that it gave a business associate access to PHI on X-ray films without a BAA in place. HHS enforcement details here.
- North Memorial Health Care (2016): Settled for $1.55 million after OCR found it had failed to enter into a BAA with a major contractor that had access to the ePHI of 289,904 individuals.
- Care New England Health System (2019): Paid $400,000 in part because its BAAs had not been updated to reflect Omnibus Rule requirements.
Notice a pattern. These aren't exotic cybersecurity failures. They're paperwork failures — the most preventable kind of HIPAA violation.
What a BAA Must Include: The Non-Negotiable Elements
A compliant BAA isn't a one-page form letter. It needs specific provisions required by HIPAA regulations. Here's what your agreement must address:
Permitted and Required Uses of PHI
The BAA must describe exactly what the business associate is authorized to do with PHI. Vague language like "may use data as needed" won't survive an audit. Be specific: billing, claims processing, data hosting, analytics — whatever the scope is, name it.
Safeguards
The business associate must agree to implement appropriate administrative, physical, and technical safeguards to protect ePHI. This mirrors the requirements under the HIPAA Security Rule.
Breach Notification Obligations
The BAA must require the business associate to report any breach of unsecured PHI to the covered entity without unreasonable delay. Under HIPAA, business associates must report breaches within 60 days of discovery at the outside. Your BAA can — and should — set a shorter window. I typically recommend 10 business days.
If your team hasn't trained on what those first critical hours look like after a breach, our First 60 Minutes: Incident Response course walks through the exact steps to take before panic sets in.
Subcontractor Requirements
If your business associate hands PHI to a subcontractor, that subcontractor needs its own BAA. The agreement must require the business associate to pass down the same obligations. This is where compliance breaks down most often in my experience — three layers deep, nobody has a signed agreement.
Return or Destruction of PHI
When the contract ends, the BAA must specify that the business associate will return or destroy all PHI in its possession. If destruction isn't feasible, the agreement should require ongoing protections.
Individual Rights
The BAA must ensure the business associate makes PHI available to individuals who request access under the HIPAA Privacy Rule. It must also allow for amendments and provide an accounting of disclosures when required.
Who Counts as a Business Associate? It's Broader Than You Think
Most covered entities undercount their business associates. In my consulting work, I've walked into clinics that listed three or four vendors and left out a dozen more.
Here's a partial list of entities that almost always qualify as business associates:
- Electronic health record (EHR) vendors
- Cloud storage and hosting providers
- Medical billing and coding companies
- IT managed service providers
- Answering services that handle patient calls
- Shredding and document destruction companies
- Accountants with access to records containing PHI
- Consultants performing utilization review
- Lawyers reviewing medical records
- Health information exchanges
If an outside party touches PHI in any form — paper, electronic, verbal — you likely need a BAA. When in doubt, execute one.
Common BAA Mistakes That Invite OCR Scrutiny
Using a Template Without Customization
HHS provides sample BAA provisions on its website, and they're a solid starting point. But I've seen organizations copy-paste those provisions verbatim without tailoring them to the actual relationship. A BAA for a cloud hosting vendor should look different from one for a billing company. Specificity protects you.
Failing to Update Existing BAAs
The Omnibus Rule in 2013 expanded BAA requirements significantly. If your agreements haven't been reviewed since then, they're almost certainly non-compliant. I still find pre-Omnibus BAAs in active use during audits in 2026. That's a violation sitting in a filing cabinet.
Not Tracking Expiration and Renewal
BAAs aren't set-and-forget documents. When vendor contracts renew, the BAA should be reviewed and renewed alongside them. Lapsed BAAs are functionally the same as missing BAAs in the eyes of OCR.
Ignoring Workforce Training
A signed BAA means nothing if your staff doesn't understand what business associates are, why the agreements matter, or how to escalate concerns. Community health workers and frontline staff often interact with vendors daily. Our HIPAA Training for Community Health Workers covers these real-world scenarios in plain language.
Do Business Associates Need Their Own HIPAA Training?
Yes. Since the Omnibus Rule, business associates are directly subject to HIPAA enforcement. That means their workforce members need HIPAA training too — particularly around handling ePHI, recognizing phishing attacks, understanding social media risks, and knowing how to report a breach.
Social media is a growing blind spot. Business associate employees post about their work just like anyone else. One careless photo or status update can expose PHI. Our Social Media & PHI training addresses this head-on with scenarios your vendors will actually encounter.
Your BAA Checklist for 2026
Here's what I tell every client to do at least once a year:
- Inventory every vendor that touches PHI in any form.
- Verify a current, signed BAA exists for each one.
- Review each BAA against current Omnibus Rule requirements.
- Confirm subcontractor provisions are included.
- Set calendar reminders for renewal and review dates.
- Document everything. If OCR comes knocking, your paper trail is your defense.
A business associate agreement isn't a bureaucratic hoop. It's the single document that defines who is responsible when PHI goes sideways. Get it right, keep it current, and make sure every person in your organization understands why it matters. The organizations that treat BAAs as an afterthought are the ones writing seven-figure checks to HHS.