A small chiropractic office in Connecticut got hit with a $25,000 penalty not because they had a massive data breach — but because they didn't realize they were a covered entity in the first place. They assumed HIPAA only applied to hospitals. That assumption cost them five figures and a corrective action plan that consumed their entire front office for a year.

So according to HIPAA, which is a covered entity? This is one of the most searched compliance questions on the internet, and the answer determines whether your organization must follow every federal privacy and security rule that HHS enforces. Get it wrong, and you're operating outside the law without even knowing it.

According to HIPAA, Which Is a Covered Entity? The Direct Answer

HIPAA defines three categories of covered entities under 45 CFR § 160.103:

  • Health care providers who transmit any health information electronically in connection with a HIPAA-covered transaction (claims, eligibility checks, referrals, etc.)
  • Health plans, including health insurance companies, HMOs, employer-sponsored group health plans, Medicare, and Medicaid
  • Health care clearinghouses, which process nonstandard health information into standard formats (or vice versa)

If your organization falls into any of these three buckets, HIPAA's Privacy Rule, Security Rule, and Breach Notification Rule apply to you. Period. There's no opt-out, no size threshold, and no grace period.

The Health Care Provider Category Is Wider Than You Think

I've seen the same mistake dozens of times. A solo practitioner — a therapist, a dentist, a home health aide coordinator — assumes HIPAA is for "big hospitals." But the regulation doesn't care about your headcount. It cares about what you do and how you transmit information.

If you provide health care services and you transmit any health information electronically in connection with a covered transaction, you're in. That includes filing electronic claims to Medicare, sending electronic referrals, or checking a patient's insurance eligibility through an electronic portal.

Home Health Agencies: A Common Blind Spot

Home health care agencies almost always qualify as covered entities, yet I've walked into agencies where staff had never heard the term "PHI" spoken out loud. Aides carry patient records on personal phones. Intake coordinators text medication lists. Supervisors email care plans in unencrypted threads.

Every one of those actions involves electronic protected health information — ePHI — and every one creates liability. If your home health agency hasn't invested in role-specific training, our HIPAA training for home health care agencies addresses exactly these scenarios with practical, field-tested content.

Health Plans: From Blue Cross to Your Company's HR Department

When people hear "health plan," they picture a national insurance carrier. But HIPAA's definition goes much further. Employer-sponsored group health plans with 50 or more participants — or that use a third-party administrator — are covered entities too.

This means your HR team may be handling PHI every time they process an enrollment change, review a medical leave request tied to plan benefits, or coordinate with a plan administrator. The HHS FAQ on covered entities makes this explicit.

I worked with a mid-size manufacturing company that had no idea their self-insured health plan made them a covered entity. Their benefits coordinator had been storing claims data in a shared Google Drive folder — accessible to the entire HR department. That's the kind of exposure that triggers OCR investigations.

Health Care Clearinghouses: The Invisible Third Category

Clearinghouses are the least understood covered entity. These are organizations that sit between providers and payers, converting data from one format to another. Billing services, repricing companies, and community health information systems often qualify.

If your organization receives health information from another entity, processes it into a standard HIPAA transaction format, and forwards it — you're a clearinghouse. And you carry the full weight of HIPAA compliance on your shoulders.

The $4.3 Million Penalty That Proved OCR Means Business

In 2016, OCR settled with Advocate Health Care Network for $5.55 million — the largest HIPAA settlement at that time. The case involved multiple breaches affecting nearly 4 million individuals. Among the failures: Advocate hadn't performed an adequate risk analysis across all covered entity functions, and ePHI on unencrypted laptops was compromised.

This case reinforced a critical point. OCR doesn't just penalize breaches. They penalize the systemic failures that made breaches possible. Not understanding your status as a covered entity — and the obligations that come with it — is exactly the kind of systemic failure that draws enforcement action.

You can review OCR's enforcement results directly on the HHS Resolution Agreements page.

What About Business Associates?

Business associates aren't covered entities — but they're close cousins. A business associate is any person or organization that performs a function or activity involving PHI on behalf of a covered entity. Think: cloud storage providers, billing companies, IT managed service providers, shredding companies.

The HITECH Act extended direct liability to business associates, meaning they face their own OCR penalties. But the distinction matters. If you're trying to figure out whether your organization is a covered entity or a business associate, ask yourself: do I create or receive PHI as part of providing health care, health insurance, or health information processing? If yes, you're likely a covered entity. If you handle PHI only because a covered entity hired you to, you're a business associate.

Three Signs Your Organization Might Be a Covered Entity Without Realizing It

1. You Submit Electronic Claims

Even a single electronic claim submission to a payer makes a health care provider a covered entity. It doesn't matter if you also accept cash payments or primarily use paper records. One electronic transaction triggers the obligation.

2. You Administer a Group Health Plan

If your company sponsors a group health plan and your HR staff touches enrollment data, claims information, or eligibility details, your plan component is a covered entity. Ignoring this doesn't make it go away — it just means you're non-compliant.

3. You Convert Health Data Between Formats

If any part of your business involves receiving health care data in one format and outputting it in another — particularly for billing or claims — you may be functioning as a clearinghouse. Get a legal review. The stakes are too high to guess.

Your Workforce Training Obligation Starts at Covered Entity Status

The moment your organization qualifies as a covered entity, HIPAA's workforce training requirement kicks in. Under 45 CFR § 164.530(b), every member of your workforce must receive training on your policies and procedures related to PHI. That includes employees, volunteers, trainees, and anyone else under your direct control.

This isn't a one-time checkbox. Training must happen at onboarding and whenever material changes affect how your team handles PHI. I've seen OCR cite training failures in settlement after settlement — it's one of the most common deficiencies in corrective action plans.

If you're looking for workforce training that matches your specific operational risks, explore the full HIPAA training catalog at HIPAACertify to find role-specific courses built for real-world compliance.

The Bottom Line: Know What You Are Before OCR Tells You

According to HIPAA, a covered entity is a health care provider that transmits health information electronically, a health plan, or a health care clearinghouse. If you fit any of those definitions, you inherit the full scope of HIPAA obligations — privacy policies, security safeguards, breach notification procedures, business associate agreements, and ongoing workforce training.

I've watched organizations spend more money on post-breach lawyers than they would have spent on five years of proactive compliance. Don't be that organization. Figure out your covered entity status today, document it, and build your compliance program from that foundation.

Because OCR isn't going to ask whether you knew. They're going to ask what you did about it.