A Gym Owner Called Me About a HIPAA Violation

Last year, a gym owner in Texas called me in a panic. One of his employees had shared a member's health screening results with another staff member. The member found out and threatened to report a HIPAA violation. The gym owner wanted to know his liability.

My answer surprised him: HIPAA didn't apply to his gym at all. But the story illustrates why the question "is HIPAA only for medical" comes up constantly — and why the real answer is more nuanced than most people think.

HIPAA doesn't cover every organization that touches health information. It covers specific types of entities and their partners. If you don't fall into those categories, HIPAA's rules don't technically bind you. But if you do fall into them — even tangentially — the penalties are severe. Let me walk you through exactly who HIPAA covers, who it doesn't, and why the lines blur more often than you'd expect.

So Is HIPAA Only for Medical Providers? Not Exactly

Here's the short answer: No, HIPAA is not only for medical providers. But it's also not for everyone.

HIPAA applies to three categories defined by the U.S. Department of Health and Human Services (HHS):

  • Covered entities: Healthcare providers who transmit health information electronically, health plans, and healthcare clearinghouses.
  • Business associates: Any organization or person that performs services for a covered entity and handles protected health information (PHI) in the process.
  • Subcontractors of business associates: Added under the 2013 HIPAA Omnibus Rule, these parties inherit HIPAA obligations through their upstream contracts.

That second category — business associates — is where most of the confusion lives. And it's where organizations outside the traditional medical world get pulled into HIPAA compliance whether they expected it or not.

The Business Associate Trap

Think about every vendor that touches patient data on behalf of a hospital, clinic, or health plan. IT companies managing servers with ePHI. Shredding companies destroying paper records. Billing services processing claims. Courier services transporting lab results.

None of these are "medical" in the traditional sense. But every single one of them is subject to HIPAA's Privacy Rule, Security Rule, and Breach Notification Rule if they handle PHI on behalf of a covered entity.

I've seen this catch courier companies off guard more than anyone. If your drivers are transporting patient records between a hospital and an offsite lab, your organization needs HIPAA training specifically designed for medical couriers. No exceptions.

The $4.3 Million Wake-Up Call for a Non-Medical Company

In 2016, the Office for Civil Rights (OCR) settled with Advocate Health Care Network for $5.55 million after multiple breaches affecting roughly 4 million individuals. One of those breaches involved a business associate — a company providing support services, not direct patient care.

But the case that really drives this point home is Cignet Health of Prince George's County. OCR hit Cignet with a $4.3 million civil money penalty — the first ever of its kind — partly for willful neglect in failing to provide patients access to their records. The point isn't the medical nature of the entity. It's the handling of PHI.

OCR doesn't care whether you call yourself a tech company, a logistics firm, or a healthcare provider. If you handle PHI and you're contractually obligated as a business associate, you're in scope.

Who HIPAA Definitely Does Not Cover

Let's be equally clear about who falls outside HIPAA's reach. This matters because I regularly see organizations waste time and money on compliance frameworks that don't apply to them.

HIPAA does not cover:

  • Employers holding employee health information (unless they also operate a health plan)
  • Schools maintaining student health records under FERPA
  • Gyms and wellness apps that collect health data directly from consumers
  • Life insurance companies that aren't also health plans
  • Law enforcement agencies (though covered entities must comply with rules about disclosures to law enforcement)

That gym owner I mentioned? His business collected health data, but not as a covered entity or business associate. His liability existed under state privacy laws and consumer protection statutes — not HIPAA.

HHS has published a helpful breakdown of who qualifies as a covered entity that I recommend bookmarking.

The Gray Zone: When "Non-Medical" Companies Become HIPAA-Bound

Here's where I've seen the most costly mistakes in my consulting work. An organization operates for years believing HIPAA doesn't apply to them — until they sign a single contract with a hospital system.

Cloud Storage and SaaS Providers

If your company provides cloud hosting and a healthcare client stores ePHI on your servers, you're a business associate. Full stop. You need a Business Associate Agreement (BAA), and you need to comply with the HIPAA Security Rule. This caught dozens of small tech firms off guard after the Omnibus Rule took effect in 2013.

Answering Services and Call Centers

If your agents take after-hours calls for a physician's office and record patient names, symptoms, or callback information, that's PHI. Your staff needs workforce training on HIPAA privacy standards.

Courier and Transportation Services

I keep coming back to this one because it's so commonly overlooked. Medical couriers physically handle specimens, records, and prescriptions containing PHI daily. The risk of a breach — a lost package, a mislabeled specimen, a vehicle break-in — is real and constant.

CPAs who audit a hospital's financials might access billing data that contains patient information. Attorneys handling malpractice cases see PHI routinely. Both qualify as business associates when they access PHI to perform services for a covered entity.

What Happens When You Get It Wrong

The consequences split into two scenarios, and both are painful.

Scenario 1: You think HIPAA applies, but it doesn't. You spend thousands on unnecessary compliance infrastructure. Annoying, but recoverable.

Scenario 2: You think HIPAA doesn't apply, but it does. This is the career-ending mistake. OCR investigates after a breach, discovers you had no BAA in place, no workforce training, no risk analysis. Penalties under the HITECH Act can reach $1.5 million per violation category per year. And OCR has not been shy about enforcing against business associates directly.

In 2018, OCR settled with Fresenius Medical Care North America for $3.5 million after five separate breaches revealed systemic failures in risk analysis and risk management. The breaches involved laptops and USB drives — not sophisticated cyberattacks. Basic security hygiene failures.

How to Figure Out If HIPAA Applies to Your Organization

Ask yourself three questions:

  • Does your organization provide healthcare, operate a health plan, or function as a healthcare clearinghouse? If yes, you're a covered entity.
  • Does your organization handle, store, transmit, or have access to PHI on behalf of a covered entity? If yes, you're a business associate.
  • Does your organization perform services for a business associate that involve PHI? If yes, you're a subcontractor with HIPAA obligations.

If you answered yes to any of those, every member of your workforce who could come into contact with PHI needs documented HIPAA training. Our Annual Healthcare Privacy Bundle covers the Privacy Rule, Security Rule, and Breach Notification requirements in a single comprehensive program — exactly what OCR auditors look for in your training documentation.

The Bottom Line: HIPAA Follows the Data, Not the Industry

Stop thinking of HIPAA as a "medical" regulation. It's a data protection regulation that follows PHI wherever it goes. The moment your organization touches protected health information on behalf of a covered entity, HIPAA's requirements attach to you like a legal shadow.

I've watched OCR expand its enforcement footprint steadily over the past decade. Business associates now face the same penalties as covered entities. Ignorance of your status doesn't reduce your liability — it increases it, because OCR views it as willful neglect of your compliance obligations.

If you're unsure where your organization stands, start with a risk analysis. Get your workforce trained. And if your team handles biological materials alongside PHI, make sure they also complete bloodborne pathogens training for healthcare settings — because HIPAA compliance rarely exists in isolation from other regulatory requirements.

The question isn't really "is HIPAA only for medical." The real question is whether your organization handles PHI — and whether you've built the compliance program to prove it.