A Single Missing HIPAA Requirement Cost This Health Plan $6.85 Million

In 2023, the Office for Civil Rights (OCR) settled with Premera Blue Cross for $6.85 million after a breach exposed the ePHI of over 10.4 million people. The root cause wasn't some exotic cyberattack. It was a failure to conduct a thorough risk analysis — a single HIPAA requirement that Premera had neglected for years.

That's the thing about HIPAA. Every requirement matters. Miss one, and OCR has the authority to impose penalties that can cripple an organization financially and reputationally. I've watched it happen to hospitals, solo practices, and business associates alike.

This post breaks down every major HIPAA requirement your organization faces in 2026 — not in legal jargon, but in plain language tied to real enforcement actions. If you're a covered entity or business associate, this is your checklist.

What Exactly Is a HIPAA Requirement?

A HIPAA requirement is any obligation established by the Health Insurance Portability and Accountability Act and its implementing regulations that covered entities and business associates must follow. These requirements span four major rules: the Privacy Rule, the Security Rule, the Breach Notification Rule, and the Enforcement Rule.

HHS publishes the full regulatory text, but the practical requirements fall into categories: how you handle protected health information (PHI), how you secure electronic PHI (ePHI), how you train your workforce, and how you respond when things go wrong.

In my experience, organizations that treat each HIPAA requirement as a standalone compliance task — rather than a checkbox on a forgotten spreadsheet — are the ones that avoid enforcement actions.

The Privacy Rule: Controlling Who Sees PHI

The HIPAA Privacy Rule establishes the baseline HIPAA requirement for how covered entities use and disclose PHI. It applies to health plans, healthcare clearinghouses, and healthcare providers who transmit health information electronically.

Minimum Necessary Standard

You can only use or disclose the minimum amount of PHI needed for a specific purpose. I've seen clinics share entire patient charts with billing departments when only a diagnosis code was necessary. That's a violation — and OCR has pursued it.

Patient Rights

Patients have the right to access their medical records, request amendments, and receive an accounting of disclosures. In 2023, OCR launched its HIPAA Right of Access Initiative and has settled over 45 cases for failures to provide records in a timely manner. Penalties have ranged from $3,500 to $240,000.

Notice of Privacy Practices

Every covered entity must provide patients with a clear notice explaining how their PHI will be used. This isn't optional. It's a foundational HIPAA requirement that many small practices still treat as an afterthought.

The Security Rule: Where Most Organizations Fail

If the Privacy Rule tells you what to protect, the Security Rule tells you how. It applies specifically to ePHI and breaks down into three categories of safeguards: administrative, physical, and technical.

Administrative Safeguards

This is where OCR spends most of its enforcement energy. Administrative safeguards include:

  • Risk analysis: You must conduct a thorough, organization-wide assessment of risks to ePHI. Not once — regularly.
  • Risk management: Identified risks must be mitigated to a reasonable level.
  • Workforce training: Every member of your workforce who handles ePHI must receive HIPAA training. Not just clinicians — front desk staff, IT contractors, billing teams.
  • Security officer designation: Someone in your organization must be named as the person responsible for HIPAA security compliance.

The risk analysis requirement alone has triggered more OCR settlements than any other single provision. If you haven't completed one this year, you're already behind. Our HIPAA Introduction Training 2026 course walks your workforce through these obligations step by step.

Physical Safeguards

Physical safeguards cover facility access controls, workstation security, and device disposal. I've consulted with organizations that had airtight firewalls but left server rooms unlocked. OCR doesn't care how good your encryption is if someone can walk in and steal a hard drive.

Technical Safeguards

Technical safeguards include access controls, audit controls, integrity controls, and transmission security. Multi-factor authentication, encryption of data at rest and in transit, and automatic logoff are all part of meeting this HIPAA requirement.

The Security Rule uses the terms "required" and "addressable" for its implementation specifications. Addressable doesn't mean optional. It means you must implement the specification, implement an equivalent alternative, or document why it's not reasonable — and accept the risk in writing.

The Breach Notification Rule: What Happens After a Failure

When a breach of unsecured PHI occurs, the Breach Notification Rule dictates exactly what you must do and how fast you must do it.

Individual Notification

You must notify affected individuals within 60 days of discovering the breach. The notification must include a description of the breach, the types of information involved, steps individuals should take, and what your organization is doing in response.

HHS Notification

If the breach affects 500 or more individuals, you must notify HHS simultaneously and alert prominent media outlets in the affected state or jurisdiction. Breaches affecting fewer than 500 individuals must be reported to HHS annually.

The Breach That Didn't Have to Happen

In my experience, the majority of breaches stem from preventable causes: lost laptops without encryption, phishing emails that untrained staff clicked, or vendors who were never vetted with a business associate agreement. Every one of these traces back to a neglected HIPAA requirement upstream.

Business Associate Agreements: The Requirement Everyone Forgets

If a vendor, contractor, or subcontractor accesses PHI on your behalf, you need a business associate agreement (BAA) in place before they touch a single record. This isn't a best practice — it's a legal HIPAA requirement under 45 CFR § 164.502(e).

I've seen covered entities hand patient data to cloud storage providers, shredding companies, and IT consultants without a BAA. When a breach happens through that vendor, the covered entity shares liability. OCR has been clear on this: no BAA means no excuse.

Workforce Training: The Cheapest Fix With the Biggest ROI

Here's what I tell every organization I work with: workforce training is the single most cost-effective way to meet your HIPAA requirements. The Security Rule mandates it. The Privacy Rule implies it. And OCR looks for evidence of it in every investigation.

Training must cover PHI handling, security awareness, your organization's specific policies, and what to do when a breach is suspected. It must be documented, and it must be ongoing — not a one-time orientation video from 2019.

If your team handles patient data in Texas, you also face state-level obligations under HB 300. Our Texas Medical Records Privacy Act (HB 300) Training covers those additional requirements in detail.

OCR Enforcement: What Gets Investigated and What Gets Penalized

OCR investigates complaints filed by individuals and conducts compliance reviews. The enforcement data on HHS.gov tells a clear story: the most common findings involve failures in risk analysis, lack of workforce training, insufficient access controls, and missing BAAs.

Penalties range from $100 to $50,000 per violation, with a maximum of roughly $2 million per violation category per year. But the real damage is often reputational. A breach notification that hits the news can cost you patients, partnerships, and years of trust.

The Penalty Tiers

  • Tier 1: Didn't know and wouldn't have known — $100 to $50,000 per violation.
  • Tier 2: Reasonable cause, not willful neglect — $1,000 to $50,000 per violation.
  • Tier 3: Willful neglect, corrected within 30 days — $10,000 to $50,000 per violation.
  • Tier 4: Willful neglect, not corrected — $50,000 per violation.

Most OCR settlements I've studied fall in the Tier 2 and Tier 3 range — situations where the organization knew better or should have known better.

Your 2026 HIPAA Requirement Checklist

If you want a practical starting point, here's what every covered entity and business associate should verify right now:

  • Completed a current, comprehensive risk analysis.
  • Implemented a risk management plan addressing identified vulnerabilities.
  • Designated a privacy officer and a security officer.
  • Executed BAAs with every vendor that accesses PHI.
  • Trained all workforce members on HIPAA policies and procedures — and documented it.
  • Implemented access controls, encryption, and audit logging for ePHI systems.
  • Established and tested a breach notification response plan.
  • Updated the Notice of Privacy Practices to reflect current operations.

If any of those items are missing, you have a gap. Gaps become findings. Findings become settlements. Browse our full HIPAA training catalog to close the training gaps before OCR finds them for you.

The Bottom Line: Compliance Isn't a Project — It's a Posture

Every HIPAA requirement exists because someone, somewhere, failed to protect a patient's most sensitive information. The regulations aren't theoretical. They're built on real harm — identity theft, discrimination, financial ruin — experienced by real people.

Your organization doesn't need to be perfect. It needs to be diligent, documented, and demonstrably committed to protecting PHI. That's what OCR looks for. That's what patients deserve. And in 2026, that's the only standard that matters.