A hospital in Oklahoma once argued that appointment schedules weren't protected by HIPAA. An employee had been sharing a physician's daily patient list with her cousin — a personal injury attorney — for over two years. When the Office for Civil Rights investigated, the hospital learned the hard way that HIPAA laws protect far more data than most organizations realize. The resulting corrective action plan cost them years of oversight and a complete overhaul of their workforce training program.

I've seen this confusion play out dozens of times. Organizations assume HIPAA only covers medical charts or lab results. That assumption creates blind spots — and blind spots create breaches. This guide breaks down exactly what HIPAA laws protect, who they apply to, and how real enforcement actions have defined the boundaries.

What HIPAA Laws Protect: The Short Answer

HIPAA laws protect a category of information known as protected health information (PHI). PHI is any individually identifiable health information that a covered entity or business associate creates, receives, maintains, or transmits. That definition is broader than you think.

PHI includes obvious things like diagnoses and treatment plans. But it also covers names, addresses, birth dates, Social Security numbers, email addresses, medical record numbers, health plan beneficiary numbers, and even full-face photographs — when those data points are connected to a healthcare service or payment.

When PHI exists in electronic form, it's called ePHI, and the HIPAA Security Rule layers on additional technical, administrative, and physical safeguards specifically for it. The full list of identifiers is published by HHS on its de-identification guidance page.

The 18 Identifiers That Make Health Data PHI

Under the Privacy Rule, there are 18 specific identifiers that, when linked to health information, turn ordinary data into PHI. Here's the full list:

  • Names
  • Geographic data smaller than a state
  • All dates (except year) related to an individual
  • Phone numbers
  • Fax numbers
  • Email addresses
  • Social Security numbers
  • Medical record numbers
  • Health plan beneficiary numbers
  • Account numbers
  • Certificate/license numbers
  • Vehicle identifiers and serial numbers
  • Device identifiers and serial numbers
  • Web URLs
  • IP addresses
  • Biometric identifiers
  • Full-face photographs and comparable images
  • Any other unique identifying number or code

Strip all 18 of these from a health dataset, and you've got de-identified data. Leave even one attached, and HIPAA's full enforcement framework applies.

Beyond Medical Records: The Data Most Organizations Overlook

In my experience, the most common compliance gaps have nothing to do with EHR systems. They involve the data flying around outside of them.

Billing records are PHI. Appointment reminders sent via text are PHI. Voicemails left with patient names and callback numbers are PHI. Explanation of Benefits documents are PHI. Even a simple spreadsheet tracking which patients owe copays — that's PHI.

I once worked with a physical therapy practice that was emailing patient intake forms to a personal Gmail account for "backup purposes." They didn't consider those forms PHI because they weren't clinical notes. They were wrong. Those forms contained names, dates of birth, insurance IDs, and descriptions of injuries. That's textbook PHI, and that email practice was a textbook HIPAA violation.

Verbal PHI Counts Too

HIPAA laws protect spoken information, not just written or electronic records. If a nurse discusses a patient's condition loudly enough for the waiting room to hear, that's a potential Privacy Rule violation. If a staff member confirms to a caller that a specific person is a patient at your facility without proper authorization, that's a disclosure of PHI.

The OCR has investigated complaints stemming from exactly these scenarios. Your workforce training needs to address verbal disclosures with the same seriousness as electronic ones.

Who Has to Follow These Rules? Covered Entities and Business Associates

HIPAA laws protect PHI by placing obligations on two categories of organizations: covered entities and business associates.

Covered entities include health plans, healthcare clearinghouses, and healthcare providers who transmit any health information electronically in connection with a HIPAA-covered transaction. If your organization bills insurance electronically, you're almost certainly a covered entity.

Business associates are vendors and contractors who handle PHI on behalf of a covered entity. Think: cloud hosting providers, billing companies, shredding services, IT consultants, and even attorneys who review medical records. Each one must sign a Business Associate Agreement and comply with applicable HIPAA rules.

HHS maintains a detailed page on covered entity and business associate definitions that every compliance officer should bookmark.

The $4.3 Million Lesson From MD Anderson

If you want to understand how seriously OCR enforces what HIPAA laws protect, look at the University of Texas MD Anderson Cancer Center case. OCR imposed a $4.3 million civil monetary penalty after three separate breaches involving unencrypted devices — a laptop and two USB drives — containing ePHI of over 33,000 individuals.

MD Anderson had written encryption policies on the books. They just never enforced them. The administrative law judge upheld the penalty, finding that MD Anderson had been "willfully neglectful" in failing to encrypt ePHI on portable devices despite years of internal recommendations to do so.

The takeaway: having a policy means nothing if your organization doesn't implement and enforce it. OCR looks at what you actually do, not what your compliance binder says.

What Rights Do Patients Get Under HIPAA?

HIPAA doesn't just restrict how organizations handle PHI. It also grants patients specific rights over their own information. These rights are enforceable, and OCR actively investigates complaints when patients report violations.

Key Patient Rights Under the Privacy Rule

  • Right to access: Patients can request copies of their medical records, and covered entities must respond within 30 days (or 60 with an extension).
  • Right to amend: Patients can request corrections to inaccurate PHI in their designated record set.
  • Right to an accounting of disclosures: Patients can ask for a log of certain disclosures made without their authorization.
  • Right to request restrictions: Patients can ask that certain disclosures be limited, and covered entities must honor restrictions on disclosures to health plans when the patient pays out of pocket in full.
  • Right to a Notice of Privacy Practices: Covered entities must provide a clear, written explanation of how they use and disclose PHI.

OCR settled with Cignet Health of Prince George's County for $4.3 million in 2011 — at the time the largest HIPAA penalty ever — largely because Cignet refused to provide 41 patients with access to their medical records and then failed to cooperate with the federal investigation. Patient access rights are not optional.

Breach Notification: What Happens When Protection Fails

When HIPAA protections fail and PHI is exposed, the Breach Notification Rule kicks in. Covered entities must notify affected individuals within 60 days of discovering a breach. If the breach affects 500 or more individuals, the organization must also notify HHS and prominent media outlets in the affected jurisdiction.

HHS publishes every large breach on its public Breach Portal — commonly called the "Wall of Shame." As of 2026, it lists thousands of breaches going back to 2009. Your organization does not want to appear on it.

Failure to provide timely breach notification is itself a HIPAA violation, separate from whatever caused the breach in the first place. I've seen organizations handle the initial breach reasonably well but then botch the notification timeline, compounding their liability.

State Laws Can Add Another Layer

HIPAA sets the federal floor, not the ceiling. Many states have enacted privacy laws that go further. Texas is a prime example. The Texas Medical Records Privacy Act (HB 300) imposes stricter consent requirements, higher penalties, and broader definitions of covered entities than federal HIPAA.

If your organization operates in Texas, federal HIPAA training alone won't keep you compliant. You need state-specific education. Our Texas Medical Records Privacy Act (HB 300) training course covers the differences between state and federal requirements in detail — because getting one right while ignoring the other still leaves you exposed.

Practical Steps to Protect What HIPAA Says You Must

Knowing what HIPAA laws protect matters only if you act on it. Here's what I tell every organization I work with:

  • Conduct a thorough risk analysis. Not a checklist — a real analysis of where PHI lives, how it moves, and what could go wrong. Update it annually.
  • Train every workforce member. Not just clinicians. Front desk staff, billing teams, IT contractors, volunteers — anyone who touches PHI needs role-specific training.
  • Encrypt ePHI everywhere. On laptops, USB drives, mobile devices, and in transit. The MD Anderson penalty made this non-negotiable.
  • Audit access logs regularly. Know who is looking at what. Snooping by curious employees is one of the most common breach causes.
  • Document everything. Policies, training records, risk assessments, incident reports. If OCR comes knocking, documentation is your defense.

Our full training catalog includes role-based courses designed to address these exact obligations — because generic training slides don't change behavior.

The Bottom Line on What HIPAA Laws Protect

HIPAA laws protect every piece of individually identifiable health information — written, electronic, or spoken — that flows through the American healthcare system. That scope is deliberately broad. It covers data you'd expect, like surgical records, and data you might not, like IP addresses in a patient portal log.

The organizations that avoid seven-figure penalties aren't the ones with the thickest policy manuals. They're the ones that train their people, encrypt their data, and treat compliance as an operational discipline rather than a paperwork exercise. That's the difference between reading about enforcement actions and being one.