The Chiropractor Who Thought HIPAA Didn't Apply to Him

A solo chiropractor in New England once told me, dead serious, that HIPAA only applied to hospitals. He ran a small cash-pay practice. No insurance billing. No electronic health records system. In his mind, he was invisible to federal regulators.

He was wrong. And when a patient complaint triggered an OCR investigation, he learned it the hard way — with a corrective action plan and a five-figure settlement. Understanding HIPAA who must comply isn't optional trivia. It determines whether your organization faces federal enforcement or not.

If you handle protected health information — PHI — in any capacity, there's a very good chance HIPAA applies to you. This post breaks down exactly who's covered, who gets pulled in through contracts, and who falls into the gray zones that trip people up every year.

What Is a Covered Entity Under HIPAA?

The HIPAA Privacy Rule defines three categories of covered entities. If your organization fits any one of them, every HIPAA rule applies to you — Privacy, Security, Breach Notification, all of it.

1. Health Care Providers Who Transmit Health Information Electronically

This is the category that catches people off guard. It's not limited to doctors and hospitals. Dentists, psychologists, chiropractors, pharmacies, nursing homes, and even physical therapists qualify — as long as they transmit any health information electronically in connection with a HIPAA-covered transaction.

What counts as a covered transaction? Claims, eligibility inquiries, referral authorizations, and coordination of benefits, among others. If you've ever submitted an electronic claim to a health plan, you're a covered entity. Period.

2. Health Plans

Health plans include health insurance companies, HMOs, employer-sponsored group health plans, Medicare, Medicaid, and military health programs like TRICARE. If you're a mid-size employer self-administering a group health plan, your plan is a covered entity even if the company itself isn't.

I've worked with HR directors who had no idea their self-funded health plan triggered HIPAA obligations separate from their company's general operations. That's a common and costly blind spot.

3. Health Care Clearinghouses

Clearinghouses process or facilitate the processing of health information from nonstandard into standard formats. Billing services and repricing companies often fall here. They sit between providers and payers, and HIPAA holds them fully accountable.

HHS provides a detailed breakdown of covered entity categories on their Covered Entities guidance page.

Business Associates: The Second Ring of Compliance

Here's where the compliance net gets wider. If your organization isn't a covered entity but you create, receive, maintain, or transmit PHI on behalf of one, you're a business associate. And since the HITECH Act and the 2013 Omnibus Rule, business associates are directly liable under HIPAA.

Common business associates include:

  • IT service providers and cloud hosting companies
  • Medical billing and coding firms
  • Attorneys and accountants with access to PHI
  • Shredding and document destruction companies
  • EHR vendors and health information exchanges
  • Answering services that handle patient calls

Every business associate must sign a Business Associate Agreement (BAA) with the covered entity. But signing the BAA isn't a formality — it's a binding legal obligation that makes HIPAA's Security Rule, parts of the Privacy Rule, and the Breach Notification Rule directly enforceable against the business associate by OCR.

Subcontractors Are Not Off the Hook

If a business associate hires a subcontractor who touches ePHI, that subcontractor is also considered a business associate under HIPAA. The chain doesn't break. I've seen organizations four layers deep in a vendor chain discover they needed HIPAA compliance programs they'd never built.

This cascading obligation is one of the most misunderstood aspects of HIPAA who must comply. If you're anywhere in the data supply chain, HIPAA follows you.

The $4.3 Million Wake-Up Call for Business Associates

In 2018, OCR settled with Fresenius Medical Care North America for $3.5 million after five separate breaches involving ePHI. The root cause? Failure to conduct enterprise-wide risk analyses. That same year, Cottage Health settled for $3 million after a misconfigured server exposed patient records.

These aren't hypotheticals. OCR publishes every resolution agreement and civil monetary penalty on its enforcement actions page. Browse it. It reads like a cautionary tale library.

Smaller organizations aren't immune either. In 2017, CardioNet agreed to a $2.5 million settlement after a laptop containing ePHI was stolen from an employee's car — a breach that exposed gaps in its risk analysis and policies.

Who Doesn't Have to Comply With HIPAA?

Not every organization that handles health-related data falls under HIPAA. Here's a quick snapshot of entities typically not covered:

  • Employers holding employee health data outside of a group health plan context
  • Life insurance companies (unless they also operate a health plan)
  • Workers' compensation carriers
  • Most schools and school districts (covered by FERPA instead)
  • Consumer health apps and wearable device companies — unless they act as business associates for a covered entity

But here's the trap: just because your organization isn't a covered entity today doesn't mean a single new contract or partnership can't pull you in tomorrow. I've watched fitness app startups become business associates overnight after signing a data-sharing deal with a hospital system.

Does HIPAA Apply to My Organization? A Quick Test

This is the question I get asked more than any other. Here's a simplified decision framework:

  • Do you provide healthcare and bill electronically? You're a covered entity.
  • Do you operate or administer a health plan? You're a covered entity.
  • Do you process health data between providers and payers? You're a clearinghouse — a covered entity.
  • Do you handle PHI on behalf of any covered entity? You're a business associate.
  • Do you subcontract for a business associate and access ePHI? You're also a business associate.

If you answered yes to any of those, HIPAA compliance isn't optional. Your workforce needs training, your systems need safeguards, and your policies need documentation. Our HIPAA Introduction Training 2026 course walks through these obligations step by step — especially useful for organizations just realizing they're in scope.

Workforce Training: Where Compliance Lives or Dies

Knowing you must comply is step one. Actually building a compliant operation is step two — and that starts with workforce training. HIPAA requires every member of your workforce (employees, volunteers, trainees, contractors under your direct control) to receive training on your policies and procedures related to PHI.

This isn't a suggestion. It's codified at 45 CFR Part 164, Subpart C. The Security Rule mandates security awareness training. The Privacy Rule mandates training on PHI handling. And the Breach Notification Rule demands your people know what to do when things go wrong.

I've reviewed dozens of OCR corrective action plans. Nearly every single one includes a mandatory training component. If your workforce can't articulate who must comply and why, your compliance program has a foundation problem.

For teams that need a solid grounding in HIPAA's core requirements, the HIPAA Fundamentals course covers the Privacy Rule, Security Rule, and enforcement structure in a format built for busy professionals.

State Laws Can Expand Who Must Comply

HIPAA sets the federal floor, not the ceiling. States like California (CCPA/CMIA), Texas, and New York have privacy laws that extend obligations beyond what HIPAA requires — and sometimes to entities HIPAA doesn't even cover.

If your organization handles health data in any state with enhanced privacy protections, you may face compliance obligations even if HIPAA technically doesn't apply to you. I always tell clients: check your state attorney general's website before assuming you're in the clear.

The Real Risk of Getting This Wrong

OCR's penalty tiers range from $137 to $68,928 per violation, with annual maximums reaching $2,067,813 per violation category — amounts adjusted for inflation and published annually by HHS. Criminal penalties enforced by the DOJ can include up to $250,000 in fines and 10 years in prison for knowingly obtaining or disclosing PHI under false pretenses.

But the financial hit is only part of it. Breach notification requirements mean your patients, clients, and the media may all learn about your failure. Reputational damage compounds fast in healthcare.

The question of HIPAA who must comply isn't academic. It's the threshold question that determines whether your organization needs policies, training, risk analyses, breach response plans, and BAAs — or faces consequences for not having them.

If you're not sure where your organization stands, start with training. Explore the full catalog at HIPAACertify.com and get your team aligned before OCR comes knocking.