In 2018, a medical imaging company called MedImages paid HHS $100,000 after losing unencrypted patient records. They weren't a hospital. They weren't a doctor's office. They were a business associate — and they learned the hard way that HIPAA's reach extends far beyond the exam room. If you've ever asked who must comply with HIPAA, the answer is broader and more specific than most people realize.
I've spent years watching organizations get blindsided by this question. They assume HIPAA only applies to doctors and insurance companies. Then OCR comes knocking, and suddenly the IT vendor, the billing service, or the cloud storage provider is staring down a six-figure penalty.
Let's break this down — entity by entity, with no ambiguity.
Who Must Comply with HIPAA? The Two Main Categories
HIPAA's requirements land on two groups: covered entities and business associates. That's it. If your organization falls into either bucket, you're on the hook for the full weight of the Privacy Rule, the Security Rule, and the Breach Notification Rule.
But within those two categories, the variety of organizations is staggering. Let me walk you through each one.
Covered Entities: The Core of HIPAA's Reach
The HHS definition of a covered entity includes three types of organizations. Every single one must comply fully with HIPAA regulations.
1. Health Care Providers Who Transmit Electronically
This is where most people stop thinking — doctors, hospitals, dentists, chiropractors, nursing homes, pharmacies. But here's the detail that trips people up: a health care provider only becomes a covered entity if they transmit any health information electronically in connection with a HIPAA-standard transaction.
In practice, that covers almost every provider in the country. If your office submits electronic claims, sends electronic referrals, or checks eligibility electronically, you're a covered entity. The solo practitioner who bills Medicare electronically is held to the same standard as a 500-bed hospital system.
2. Health Plans
Health plans include health insurance companies, HMOs, employer-sponsored group health plans, Medicare, Medicaid, and military health programs like TRICARE. If your organization pays for or arranges medical care, HIPAA applies to you.
I've seen mid-size employers shocked to learn that their self-funded group health plan makes them a covered entity. They thought HIPAA was their insurer's problem. It wasn't.
3. Health Care Clearinghouses
Clearinghouses are the middlemen. They process nonstandard health information into standard formats (or vice versa) for other entities. Think billing services that convert claims data before sending it to payers. They handle massive volumes of protected health information (PHI), and they're fully subject to HIPAA.
Business Associates: The Category That Catches People Off Guard
Here's where enforcement has accelerated dramatically over the past several years. A business associate is any person or organization that performs a function or activity on behalf of a covered entity that involves access to PHI.
The list is long:
- IT service providers who manage systems containing ePHI
- Cloud hosting companies storing patient records
- Medical billing and coding companies
- Law firms that access PHI for legal services
- Shredding and document destruction companies
- Accountants who access PHI during audits
- Revenue cycle management firms
- Answering services that take patient messages
And it goes further. If a business associate hires a subcontractor who also touches PHI, that subcontractor becomes a business associate of the business associate. They need their own Business Associate Agreement (BAA), and they're directly liable under HIPAA.
I've reviewed contracts for organizations that had no idea their data was flowing through three or four downstream vendors — all of whom needed BAAs and none of whom had them.
The $2.3 Million Lesson from Chiropractic Economics
In 2020, OCR settled with CHSPSC LLC, a management company providing services to hospital operator Community Health Systems. The settlement? $2.3 million. CHSPSC was a business associate. Hackers had exploited their systems and accessed the PHI of over six million individuals. OCR found longstanding, systemic noncompliance with the HIPAA Security Rule — failures in risk analysis, information system activity reviews, and access controls.
The takeaway: being a business associate doesn't mean lighter obligations. OCR treats you with the same seriousness it treats a hospital.
Who Doesn't Have to Comply with HIPAA?
This is the question that actually clarifies things. HIPAA does not apply to:
- Employers accessing employee records (outside of their group health plan)
- Life insurers
- Workers' compensation carriers
- Most schools and school districts (FERPA applies instead)
- Law enforcement agencies
- Consumer health apps that aren't connected to a covered entity
- Gym and fitness trackers collecting health data independently
The critical distinction: it's not about whether you handle health information. It's about whether you're a covered entity or a business associate of one. A fitness app might collect your heart rate data every day and never fall under HIPAA — because it has no relationship with a covered entity.
What Exactly Does Compliance Require?
If your organization must comply with HIPAA, here's the operational reality. You need:
- A thorough risk analysis — not a checkbox exercise, but a genuine assessment of every place PHI lives, moves, and could be exposed
- Written policies and procedures covering the Privacy Rule, Security Rule, and Breach Notification Rule
- Workforce training — every member of your staff who touches or could touch PHI must receive HIPAA training, and it must be documented
- Business Associate Agreements with every vendor who accesses PHI
- Incident response and breach notification procedures that meet the 60-day reporting window to HHS and affected individuals
- A designated Privacy Officer and Security Officer
If you're building or refreshing your training program, our HIPAA training catalog covers every role from front-desk staff to compliance officers — structured around what OCR actually enforces.
State Laws Can Expand Your Obligations
HIPAA sets the federal floor. Many states go further. California, Texas, New York, and Massachusetts all have health privacy laws that impose additional requirements on organizations handling health information. Your organization might comply fully with HIPAA and still violate state law.
I've consulted with practices that operated in multiple states and discovered — mid-audit — that their breach notification timeline in one state was 30 days, not the 60 days HIPAA allows. That's the kind of detail that turns a manageable incident into a regulatory crisis.
The Workforce Training Gap That OCR Keeps Punishing
Here's a pattern I see repeatedly in OCR resolution agreements: the organization had policies on paper but never trained their people. In the 2019 settlement with the University of Rochester Medical Center — $3 million — one of OCR's key findings was the failure to manage ePHI on portable devices. Staff weren't trained. Devices weren't encrypted. The policies existed but lived in a binder no one opened.
Workforce training isn't optional decoration. It's a requirement under 45 CFR Part 164, Subpart C of the Security Rule. And it's one of the first things OCR examines after a breach report.
If your staff hasn't completed documented HIPAA training this year, you're exposed. Our role-based HIPAA training courses are built to close exactly this gap — with documentation you can produce if OCR ever asks.
How to Determine If Your Organization Must Comply
Ask yourself three questions:
- Does your organization provide, pay for, or facilitate health care?
- Do you transmit health information electronically in any standard transaction?
- Do you access, store, process, or transmit PHI on behalf of an entity that does?
If you answered yes to any of those, you almost certainly need to comply with HIPAA. And "almost certainly" isn't a phrase that holds up well in an OCR investigation. When in doubt, operate as if HIPAA applies. The cost of compliance is a fraction of the cost of a breach.
The Expanding Scope: What's Changed Recently
HHS has made clear that the definition of who must comply with HIPAA isn't shrinking. Telehealth vendors, health information exchanges, and organizations using AI tools that process PHI are all firmly within scope. The pandemic-era enforcement discretion for telehealth has ended. If your platform handles ePHI, you need a BAA, you need encryption, and you need trained staff.
I've watched organizations assume that because they were "just a tech company," HIPAA didn't apply. Then a breach happened, and OCR didn't care about their self-description. OCR cared about their function — and their function was processing PHI.
Your Next Step
If you're reading this and you're not sure whether your organization falls under HIPAA — or you know it does but haven't built a real compliance program — start with the fundamentals. Conduct your risk analysis. Get your BAAs in order. And train your workforce.
Browse the full HIPAA training catalog at HIPAACertify.com to find courses matched to your organization's size, type, and risk profile. Because knowing who must comply with HIPAA is only useful if you actually do it.