In 2023, a Maryland-based health system called MedStar paid $900,000 to settle allegations that it failed to provide patients with timely access to their own records. Not a massive data breach. Not a cyberattack. Just patients who couldn't get copies of their own medical charts. That single case tells you something crucial about what HIPAA laws protect — and it goes far beyond keeping hackers out of your network.

If you've ever searched "what do HIPAA laws protect," you probably expected a simple answer. The reality is layered, specific, and — in my experience advising covered entities — frequently misunderstood by the very people responsible for compliance.

HIPAA Laws Protect More Than You Think

Most people assume HIPAA is about keeping medical records confidential. That's partially right. But the scope is broader and more granular than most compliance officers realize on day one.

HIPAA laws protect what HHS calls protected health information (PHI) — any individually identifiable health information held or transmitted by a covered entity or its business associates. That includes obvious items like diagnoses, lab results, and prescription histories. It also covers information most people forget: billing records, appointment schedules, and even the fact that someone is a patient at your facility.

Here's the part that trips people up: PHI isn't limited to electronic data. Paper charts in a filing cabinet, verbal conversations between a nurse and a physician within earshot of a waiting room, faxes — all of it falls under the protection umbrella.

The Three Pillars: Privacy, Security, and Breach Notification

HIPAA's protections sit on three distinct rules, and each one guards something different.

The Privacy Rule: Who Can See What

The HIPAA Privacy Rule establishes national standards for when PHI can be used or disclosed. It gives patients the right to access their records, request corrections, and know who has looked at their information. It also limits how covered entities share data for marketing, fundraising, and research.

I've seen organizations treat the Privacy Rule like a suggestion. It's not. OCR enforces it aggressively, as MedStar learned.

The Security Rule: Locking Down ePHI

The Security Rule applies specifically to electronic protected health information (ePHI). It requires administrative, physical, and technical safeguards — think access controls, encryption, audit logs, and workforce training.

The distinction matters. A paper chart left on a reception desk is a Privacy Rule problem. A database without multi-factor authentication is a Security Rule problem. Both can cost you six or seven figures.

The Breach Notification Rule: When Things Go Wrong

When a breach of unsecured PHI occurs, covered entities must notify affected individuals, HHS, and in some cases, the media. Timelines are strict — 60 days from discovery for individual notifications. Miss that window and you've created a second violation on top of the first.

What Exactly Counts as Protected Health Information?

This is the question I get asked most, and it's a prime area for confusion. PHI includes any information that can identify a patient and relates to their health condition, treatment, or payment for care. HHS defines 18 specific identifiers that make health data individually identifiable:

  • Names
  • Dates (birth, admission, discharge, death)
  • Phone and 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
  • Web URLs and IP addresses
  • Biometric identifiers (fingerprints, voiceprints)
  • Full-face photographs
  • Geographic data smaller than a state
  • Any other unique identifying number or code

Strip all 18 identifiers and you have de-identified data, which HIPAA no longer covers. Leave even one in, and you're still in HIPAA territory.

The $5.1 Million Question: What Happens When Protections Fail?

In 2017, Memorial Healthcare System paid $5.1 million after employees accessed the ePHI of 115,143 individuals without authorization. The breach wasn't caused by an outside attacker. It was insiders — workforce members who had no legitimate reason to view those records.

That case illustrates a pattern I've seen repeatedly. The biggest HIPAA risks aren't sophisticated ransomware gangs. They're your own employees clicking where they shouldn't, sharing what they shouldn't, and storing PHI where it doesn't belong.

Your organization doesn't just need firewalls. It needs a culture where every staff member understands what HIPAA laws protect and why those protections exist.

Patient Rights: The Overlooked Protection

When people discuss what HIPAA laws protect, they usually focus on data security. But HIPAA also protects a bundle of patient rights that many covered entities handle poorly.

Right to Access

Patients can request copies of their PHI. You must provide them within 30 days. OCR has launched an entire Right of Access Initiative to enforce this, and settlements have ranged from $3,500 to $240,000 for individual violations.

Right to Request Amendments

If a patient believes their record contains an error, they can ask you to correct it. You can deny the request, but you must explain why in writing.

Right to an Accounting of Disclosures

Patients can ask for a list of every entity that has received their PHI outside of treatment, payment, and healthcare operations. Most small practices I've audited have no system for tracking this.

State Laws Add Another Layer

HIPAA sets a federal floor, not a ceiling. Many states impose stricter protections on specific types of health data. Texas, for example, enacted HB 300 — the Texas Medical Records Privacy Act — which expands training requirements and increases penalties beyond what HIPAA mandates.

If your organization operates in Texas, your workforce needs to complete Texas HB 300 training in addition to standard HIPAA education. Ignoring state-level requirements because you've checked the federal box is one of the most common compliance gaps I encounter.

Who Must Follow These Protections?

HIPAA applies to covered entities — health plans, healthcare clearinghouses, and healthcare providers who transmit any health information electronically. It also extends to business associates: any vendor, contractor, or partner that creates, receives, maintains, or transmits PHI on behalf of a covered entity.

Your cloud storage provider, your billing company, your shredding service — they're all business associates. Every one of them needs a signed Business Associate Agreement. I've audited organizations with 40+ vendors and not a single BAA on file. That's 40 separate HIPAA violations waiting to be discovered.

Practical Steps to Strengthen Your Protections

Knowing what HIPAA laws protect is step one. Operationalizing those protections is where the real work begins.

Train Every Member of Your Workforce

HIPAA requires workforce training, and OCR checks for it during every investigation. "We did a training three years ago" won't cut it. Annual, role-based training is the standard. Browse the full HIPAACertify training catalog to find courses matched to your organization's specific risks.

Conduct a Risk Analysis — Annually

The Security Rule requires a thorough risk analysis. Not a checkbox form. A genuine assessment of where ePHI lives, how it moves, and what threatens it. Most OCR enforcement actions cite the failure to conduct an adequate risk analysis as a contributing factor.

Document Everything

Policies, training records, BAAs, incident reports, risk analyses — if it isn't documented, it didn't happen. OCR investigators will ask for proof, and verbal assurances are worthless.

Build an Incident Response Plan

When a breach happens — not if — you need a tested plan. Who investigates? Who notifies patients? Who contacts HHS? Run tabletop exercises at least once a year so your team isn't learning the process during a crisis.

The Bottom Line for Your Organization

HIPAA laws protect patients' most sensitive information — their health data, their identities, and their rights to control who sees what. They also protect your organization from the kind of chaotic, unstructured data handling that leads to seven-figure settlements and front-page headlines.

The organizations that get this right don't treat HIPAA as a legal annoyance. They treat it as a framework for earning and keeping patient trust. And in a healthcare landscape where data breaches hit record numbers year after year, that trust is worth more than any compliance budget.