A Shredding Company Cost a Hospital System $800,000

In 2016, North Memorial Health Care of Minnesota paid $1.55 million to settle HIPAA violations — partly because they failed to have a business associate agreement with a contractor who transported and stored PHI-laden documents. The contractor was a business associate. North Memorial didn't treat them like one. That single oversight triggered an OCR investigation, a corrective action plan, and a seven-figure penalty.

If you've ever wondered what business associate HIPAA examples actually look like in practice, that story tells you everything. It's not theoretical. It's not a textbook exercise. Your vendors, your IT support, your billing company — they're probably business associates. And if you haven't locked down those relationships with proper agreements and oversight, you're carrying risk you can't see.

This post walks through the real-world examples, the enforcement actions, and the gray areas that trip up covered entities every year.

What Exactly Is a Business Associate Under HIPAA?

A business associate is any person or organization that performs functions or activities on behalf of — or provides services to — a covered entity that involve access to protected health information (PHI). The key word is access. If a vendor can see, touch, transmit, or store PHI as part of their work for you, HIPAA almost certainly considers them a business associate.

The HIPAA Privacy Rule and the 2013 Omnibus Rule made this definition broader than most people realize. HHS spells it out clearly on their business associate guidance page. Subcontractors of business associates are also covered — a detail that still surprises people in the field.

12 Business Associate HIPAA Examples You Should Know

I get asked constantly: "Is this vendor a business associate?" Here's a concrete list drawn from OCR guidance and real enforcement experience.

1. Medical Billing Companies

Any third-party biller handling claims with patient names, diagnoses, and insurance details is accessing PHI. Classic business associate.

2. IT Service Providers and Cloud Hosting

If your IT company manages servers that store ePHI or has remote access to systems containing patient data, they qualify. This includes cloud storage vendors like those hosting your EHR.

3. Shredding and Document Destruction Firms

The North Memorial case proved this. If a company handles documents containing PHI — even to destroy them — they're a business associate.

4. Answering Services

A medical answering service that takes patient calls and records messages containing symptoms, appointment details, or medications handles PHI directly.

When a law firm needs access to patient records for litigation, malpractice defense, or compliance work, that firm becomes a business associate.

6. Accountants and Auditors

If your CPA firm reviews billing records that include patient-identifiable information, they meet the threshold.

7. Third-Party Administrators (TPAs)

TPAs managing health plan claims, eligibility, or enrollment data for a covered entity are textbook business associates.

8. Health Information Exchanges (HIEs)

Organizations that facilitate electronic sharing of patient records across providers are handling PHI at scale.

9. Transcription Services

Medical transcriptionists — whether onshore or offshore — who convert dictated clinical notes into text are accessing detailed PHI.

10. Practice Management Software Vendors

If the vendor can access ePHI through their software (and most can, via support logins or backend access), they're a business associate.

11. Data Analytics Companies

Population health analytics firms that receive patient-level data from hospitals or health plans to build reports must be treated as business associates.

12. Community Health Workers With Organizational Affiliations

Here's one that catches people off guard. When a community health organization contracts with a covered entity to provide outreach, care coordination, or social determinant screenings — and their workers access patient records — that organization is functioning as a business associate. Training these workers on PHI handling is critical, which is why we built our HIPAA training for community health workers course specifically for this population.

The $2.3 Million Mistake: When Business Associate Agreements Don't Exist

In 2018, OCR settled with Advanced Care Hospitalists (ACH), a Florida physician practice, for $500,000 after PHI of over 9,000 patients was found on a medical billing company's unsecured server. ACH had no business associate agreement in place with the billing company. None.

That same year, Fresenius Medical Care North America agreed to pay $3.5 million following five separate breach incidents — some involving business associates who weren't properly managed. You can review OCR's full enforcement results on the HHS Resolution Agreements page.

The pattern in every case is the same: a covered entity assumes the vendor "knows what they're doing," skips the business associate agreement (BAA), and then discovers the hard way that OCR holds them responsible.

What Does a Business Associate Agreement Actually Require?

A BAA isn't a handshake or a clause buried in a master services agreement. Under 45 CFR § 164.504(e), it must include specific provisions:

  • How the business associate will use and disclose PHI
  • Safeguards the business associate will implement to prevent unauthorized use
  • Requirements for reporting breaches and security incidents
  • Obligations to return or destroy PHI at contract termination
  • The right of the covered entity (or HHS) to audit compliance
  • Requirements that subcontractors also agree to the same restrictions

Skip any of these elements, and your agreement may not satisfy OCR. I've reviewed BAAs for health systems that were missing breach notification timelines or subcontractor flow-down clauses. Those gaps create liability that shows up during investigations.

Who Is NOT a Business Associate?

This question matters just as much. Not every vendor you work with qualifies, and over-classifying creates unnecessary administrative burden.

Janitorial services that clean your office but don't access PHI — not a business associate. A plumber fixing a pipe in your server room — not a business associate, assuming they don't access systems. A conduit like the U.S. Postal Service or a courier that transports sealed packages without routine access to the contents — also excluded under HHS guidance.

The distinction hinges on whether the vendor has more than incidental contact with PHI. If they do, treat them as a business associate.

How Business Associate Breaches Affect Your Organization

Here's the part that keeps compliance officers up at night. Under the Breach Notification Rule, your business associate must notify you of a breach within 60 days. Then you bear the responsibility to notify affected patients, HHS, and — if over 500 individuals are affected — the media.

Your name is the one in the headline. Not your vendor's. In 2020, business associates were involved in a growing share of reported breaches listed on the HHS Breach Portal. That trend hasn't reversed.

This is precisely why workforce training matters at every level of your organization. Staff who manage vendor relationships need to understand what makes someone a business associate and what red flags to watch for. Our HIPAA training catalog includes courses designed for exactly this kind of operational awareness.

Three Steps to Lock Down Your Business Associate Relationships Today

Step 1: Inventory Every Vendor With PHI Access

Conduct a full vendor audit. Map every third party that touches PHI in any form — electronic, paper, or verbal. I've seen organizations discover 15 to 20 business associates they hadn't formally identified.

Step 2: Execute or Update Your BAAs

Don't rely on contracts signed in 2014. The regulatory landscape has shifted. Review every BAA for breach notification timelines, subcontractor provisions, and termination clauses. Update annually.

Step 3: Train Your Workforce on Vendor Risk

Your front desk staff, your IT team, your clinical leadership — they all interact with vendors. They need to know when PHI access triggers business associate obligations and when to escalate. This isn't just a compliance checkbox. It's how you prevent the next North Memorial.

Business Associate HIPAA Examples: The Bottom Line

Every covered entity works with business associates. Most have more than they've formally identified. The gap between the vendors on your list and the vendors who actually access PHI is where OCR finds violations and where breaches go undetected until it's too late.

Map your vendors. Execute proper BAAs. Train your people. The organizations that do this well don't just avoid fines — they build the kind of trust with patients and partners that compliance was always meant to create.