A front-desk employee at a large health system accidentally emails a spreadsheet of 836 patient names, Social Security numbers, and diagnosis codes to the wrong clinic. Within 48 hours, the Office for Civil Rights is involved, the media picks it up, and the organization faces a seven-figure investigation. That scenario is not hypothetical — it is exactly the kind of event that answers the question what is a HIPAA breach in the most painful way possible.

If you work at a covered entity or business associate, you need to understand not just the textbook definition but the real-world mechanics: what triggers a breach, who you have to notify, how fast, and what the penalties look like when you get it wrong. This post breaks it all down.

Under the HIPAA Breach Notification Rule (45 C.F.R. §§ 164.400–414), a breach is the acquisition, access, use, or disclosure of protected health information (PHI) in a manner not permitted by the Privacy Rule that compromises the security or privacy of that PHI.

That is the federal definition straight from HHS. But here is the part most people miss: the law presumes that any impermissible use or disclosure of PHI is a breach unless your organization can demonstrate a low probability that the information was actually compromised.

To make that determination, you have to conduct a four-factor risk assessment looking at:

  • The nature and extent of the PHI involved (types of identifiers, clinical data)
  • The unauthorized person who used or received the PHI
  • Whether the PHI was actually acquired or viewed
  • The extent to which the risk has been mitigated

If you cannot prove that all four factors tilt in your favor, you have a reportable breach on your hands. Period.

Breaches Most Organizations Never See Coming

When people ask what is a HIPAA breach, they usually picture a hacker breaking into a server room. That does happen. But I have seen far more breaches caused by everyday human error.

The Misdirected Fax That Cost $100,000

Faxing PHI to the wrong number is still one of the most common breach causes I encounter. A single wrong digit sends a patient's lab results to a stranger's machine. If you cannot retrieve that document and confirm it was destroyed, you likely have a breach.

The Lost Laptop with Unencrypted ePHI

A workforce member leaves an unencrypted laptop in a rental car. Even if no one ever opens it, the HIPAA Breach Notification Rule treats that as a presumed breach because the ePHI was potentially accessible. Had the device been encrypted to NIST standards, it would qualify for the encryption safe harbor and would not be a reportable breach at all.

The Vendor Who Waits Nine Months to Tell You

Business associates are required to report breaches to the covered entity without unreasonable delay and no later than 60 days after discovery. But I have worked cases where vendors sat on a breach for the better part of a year. That delay does not excuse the covered entity from its own notification obligations — it just compresses the timeline into a crisis. Our case study on a vendor breach reported nine months late walks through exactly how to handle that scenario.

Breach vs. Incident vs. Violation: Why the Labels Matter

These three terms are not interchangeable, and mixing them up can derail your response.

A security incident is any attempted or successful unauthorized access to ePHI. Not every incident is a breach. A firewall log showing a blocked intrusion attempt is an incident — but no PHI was actually exposed.

A violation is any failure to comply with a HIPAA standard, whether or not PHI was exposed. Using a non-compliant texting platform is a violation even if no breach ever results from it.

A breach specifically involves PHI that was impermissibly accessed, used, or disclosed in a way that compromises its security or privacy. It triggers formal notification requirements that violations and incidents alone do not.

Getting this distinction right in the first minutes of an event determines your entire response trajectory. That is why I recommend every workforce member complete our First 60 Minutes: Incident Response training before they ever face a real event.

The $4.3 Million Wake-Up Call from OCR

HHS enforcement data shows that breach-related penalties can be devastating. In 2023, OCR settled with Banner Health for $1.25 million following a 2016 breach that affected nearly 2.81 million individuals. The investigation revealed that Banner Health had failed to conduct an adequate risk analysis and had insufficient monitoring of its health information systems.

Even larger, Advocate Medical Group paid $5.55 million in 2016 — at the time one of the largest HIPAA settlements ever — after breaches involving unencrypted laptops and an unauthorized third party accessing ePHI. The root causes were not sophisticated cyberattacks. They were basic security failures: no encryption, no physical safeguards, no adequate risk analysis.

OCR publishes every settlement and civil money penalty on its breach enforcement page. If you have not reviewed it recently, spend twenty minutes there. It will change how you prioritize compliance spending.

Who Do You Notify — and How Fast?

Once you have determined that a breach occurred, the clock starts. Here is the notification framework:

Individuals Affected

You must notify every affected individual in writing without unreasonable delay, and no later than 60 calendar days from the date you discovered the breach. The notice must include a description of the breach, the types of PHI involved, steps the individual should take, what your organization is doing in response, and contact information.

HHS / OCR

If the breach affects 500 or more individuals, you must notify HHS at the same time you notify individuals — within that 60-day window. For breaches affecting fewer than 500 people, you can report annually, but most compliance officers I know report immediately anyway to avoid losing track.

Media

If 500 or more residents of a single state or jurisdiction are affected, you must issue a press release to prominent media outlets in that area. This is the notification requirement that triggers the most organizational anxiety — and the one that makes senior leadership suddenly care about HIPAA.

For the full regulatory text on these requirements, see 45 C.F.R. Part 164, Subpart D at the Cornell Law Institute.

What Happens When a Patient Calls About a Breach Letter

Here is a scenario your staff is probably not prepared for. A patient receives a breach notification letter — maybe from your organization, maybe from one of your business associates — and calls your front desk demanding answers.

That call is a compliance event. What your receptionist says in the next two minutes can either reassure the patient and demonstrate your organization's accountability, or it can create additional liability.

Your workforce needs scripted, rehearsed language for exactly this situation. Our case study on handling a patient call about a breach letter provides a realistic walkthrough that every patient-facing employee should complete.

Three Things That Do Not Count as Breaches

The Breach Notification Rule includes three specific exceptions. These are not loopholes — they are narrowly defined carve-outs:

  • Unintentional access by a workforce member acting in good faith. A nurse accidentally opens the wrong patient's chart, realizes the mistake, and closes it immediately. As long as the access was within the scope of their authority and the information is not further used or disclosed, this is not a breach.
  • Inadvertent disclosure between authorized persons. Two employees at the same covered entity, both authorized to access PHI, accidentally share information with each other. If the information is not further disclosed impermissibly, this exception applies.
  • Good-faith belief that the recipient cannot retain the information. You fax PHI to the wrong number, but the recipient immediately tells you they shredded it without reading it and you have a reasonable belief that is true.

These exceptions are fact-specific. Document your analysis thoroughly every single time you apply one.

Your Breach Response Checklist for 2026

Based on the enforcement trends I am tracking this year, here is what every covered entity and business associate should have locked down right now:

  • A written incident response plan that names specific people, not just titles
  • Encryption on every device that touches ePHI — laptops, phones, USB drives, all of it
  • Business associate agreements that include concrete breach notification timelines shorter than the 60-day maximum
  • Annual workforce training that covers breach identification, not just general HIPAA awareness
  • A tested process for conducting the four-factor risk assessment within 24 hours of discovering a potential breach
  • Pre-drafted notification letter templates reviewed by legal counsel

If any of those items are missing from your program, you are not ready for a breach. You are just hoping one does not happen.

The Bottom Line on HIPAA Breaches

A HIPAA breach is not an abstract compliance concept. It is a specific, legally defined event that triggers mandatory notifications, potential penalties, and real reputational damage. OCR does not care whether you meant to expose PHI. They care whether you had the safeguards, the training, and the response plan to prevent and manage it.

Start by making sure every person in your workforce — from the C-suite to the front desk — can answer the question what is a HIPAA breach and knows exactly what to do in the first hour after one is discovered. Explore our full HIPAA training catalog to build that readiness across your organization.