The Phone Call That Changed Everything for One Fitness App

A few years ago, I got a call from the CEO of a health and wellness app company. They'd been collecting sleep data, heart rate logs, and medication schedules from users. When a data breach exposed 40,000 records, they assumed they were HIPAA exempt and didn't bother with breach notification. Then HHS came knocking.

Turns out, they weren't exempt. They were a business associate of a covered entity — a regional health plan that had contracted them to run a wellness portal. That single wrong assumption nearly sank the company.

If you've ever Googled "HIPAA exempt" hoping to find out your organization doesn't need to comply, you're not alone. But the answer is more nuanced — and more dangerous to get wrong — than most people realize. This post breaks down exactly who qualifies as HIPAA exempt, who doesn't, and what happens when organizations guess incorrectly.

What Does HIPAA Exempt Actually Mean?

An entity is HIPAA exempt when it falls entirely outside the scope of HIPAA's Privacy, Security, and Breach Notification Rules. That means the organization is not a covered entity, not a business associate, and does not handle protected health information (PHI) on behalf of one.

HIPAA applies to three categories of covered entities: health plans, healthcare clearinghouses, and healthcare providers who transmit health information electronically in connection with certain transactions. If your organization doesn't fit any of those buckets — and doesn't serve one under contract — you're likely exempt.

But "likely" is the word that gets people in trouble.

Entities That Are Genuinely HIPAA Exempt

  • Life insurers — Life insurance companies are not health plans under HIPAA, even though they underwrite risk related to health.
  • Employers (in most cases) — Your company's HR department isn't a covered entity just because it manages employee health benefits. The health plan itself is covered; the employer sponsoring it generally is not.
  • Workers' compensation carriers — These operate under state law, not HIPAA.
  • Most schools and universities — Student health records are typically governed by FERPA, not HIPAA. The Department of Health and Human Services has clarified this distinction directly.
  • Law enforcement agencies — Police departments don't become covered entities by collecting medical information during investigations.
  • Consumer health apps (with caveats) — A fitness tracker that sells directly to consumers and has no relationship with a covered entity is generally HIPAA exempt. But the moment that app contracts with a hospital or health plan, the calculus changes entirely.

The Gray Zone: Where "HIPAA Exempt" Falls Apart

I've audited dozens of organizations that believed they were HIPAA exempt — until we traced their data flows. The pattern is almost always the same: a vendor, app developer, or consulting firm signs a contract with a hospital, insurer, or clinic. That contract involves access to PHI. Overnight, they become a business associate.

Under the HITECH Act and the 2013 Omnibus Rule, business associates are directly liable for HIPAA compliance. That includes IT companies managing ePHI on cloud servers, billing services processing claims, and even shredding companies destroying paper records containing PHI.

The $4.3 Million Mistake at MD Anderson

The University of Texas MD Anderson Cancer Center lost an unencrypted laptop and two thumb drives containing ePHI. OCR imposed a $4.3 million civil monetary penalty in 2018. MD Anderson argued aspects of enforcement didn't apply to them. An administrative law judge and the HHS Departmental Appeals Board disagreed.

The lesson: if you touch PHI and you're connected to a covered entity, claiming you're exempt won't hold up.

Five Signs Your Organization Is Not HIPAA Exempt

Here's the quick gut check I walk clients through:

  • You've signed a Business Associate Agreement (BAA). If a covered entity asked you to sign one, they believe you handle PHI on their behalf. You're not exempt.
  • You store, process, or transmit ePHI. Cloud hosting, data analytics, billing — all of it counts.
  • You provide services to a health plan, provider, or clearinghouse. Even if your core product has nothing to do with healthcare, the contractual relationship matters.
  • Your employees access patient records. Even temporary access during an implementation or migration pulls you under HIPAA's umbrella.
  • You transmit electronic transactions covered under HIPAA. Claims, eligibility inquiries, referral authorizations — if you send them electronically, you're likely a covered entity.

If any of these apply, your organization needs workforce training immediately. Our HIPAA training for nurses and clinical workflows covers the exact scenarios where staff unknowingly cross compliance lines.

Employers: The Most Misunderstood "Exempt" Category

I get this question constantly: "We're an employer with 200 employees. Are we HIPAA exempt?"

Usually, yes — with a critical exception. If your company sponsors a self-insured group health plan and your HR team has access to enrollment data, claims data, or any PHI flowing through that plan, then the health plan component of your organization is a covered entity.

That means you need firewalls between plan administration and employment decisions. You need policies. You need training. The employer itself may be exempt, but the health plan it sponsors is not.

This is exactly the kind of scenario where remote work compounds the risk. When HR staff handle plan enrollment from their kitchen tables, PHI security becomes exponentially harder. Our Working from Home and PHI training was built for this reality.

What About State Laws?

Even if your organization is genuinely HIPAA exempt, you're not off the hook for privacy obligations. State laws like the California Consumer Privacy Act (CCPA), the Texas Medical Records Privacy Act, and New York's SHIELD Act may impose overlapping — and sometimes stricter — requirements on health data.

Being HIPAA exempt doesn't mean being privacy-law exempt. It just means HIPAA's specific rules don't apply to you. That's a narrower safe harbor than most people think.

What Happens When You Wrongly Claim HIPAA Exemption

OCR doesn't accept "we didn't know" as a defense. Under HIPAA's tiered penalty structure, even "reasonable cause" violations start at $1,379 per incident (adjusted for inflation as of recent HHS updates). Willful neglect with no correction can reach $68,928 per violation, up to nearly $2.07 million per calendar year for identical provisions. These figures are published in the Code of Federal Regulations, 45 CFR Part 160, Subpart D.

And here's the part that really stings: if OCR investigates and finds you should have been compliant all along, they'll look at every year you weren't. That's not one penalty — it's compounding exposure for every year of noncompliance.

The Anthem Breach: A $16 Million Warning

In 2018, Anthem Inc. paid $16 million to settle HIPAA violations stemming from a breach affecting nearly 79 million individuals. While Anthem never claimed exemption, the case underscored how OCR treats organizations that fail to implement baseline safeguards. No risk analysis, no encryption, no monitoring — the fundamentals were missing. OCR's settlement announcement made clear that basic compliance failures carry the highest costs.

How to Determine Your HIPAA Status — Step by Step

Stop guessing. Run this analysis:

  • Step 1: List every entity you exchange health information with. Include vendors, partners, and clients.
  • Step 2: Determine whether any of them are covered entities (health plans, providers, clearinghouses).
  • Step 3: Review every contract for BAA language. If it's there, you're a business associate.
  • Step 4: Map your data flows. Where does PHI enter, live, and leave your systems?
  • Step 5: Consult legal counsel if there's any ambiguity. The cost of a legal opinion is a fraction of an OCR settlement.

Once you know your status, act on it. If you're a business associate, your workforce needs HIPAA training — including staff who use mobile devices to access ePHI. Our Mobile Devices and PHI course covers exactly that scenario with practical, role-based guidance.

The Bottom Line on Being HIPAA Exempt

Fewer organizations are truly HIPAA exempt than assume they are. The regulatory net is wide, and it stretches further every time a vendor signs a BAA, an app connects to a health plan portal, or an employee accesses a patient record from a personal laptop.

If you're genuinely outside HIPAA's scope, document why. Keep that analysis current. Revisit it every time your business relationships change.

And if there's even a shadow of doubt, treat it like you're covered — because OCR certainly will. Explore our full HIPAA training catalog to get your workforce compliant before that doubt turns into an investigation.