← Back to blog

HIPAA Breaches: Definition, Examples, Deadlines and Response

November 9, 2026
HIPAA Breaches: Definition, Examples, Deadlines and Response

A HIPAA breach is, generally, an impermissible use or disclosure of protected health information (PHI) under the Privacy Rule that compromises the security or privacy of that information. HHS describes it that way, and the regulation adds that any acquisition, access, use or disclosure of PHI not permitted by the Privacy Rule is presumed to be a breach unless the organization can show a low probability that the PHI was compromised. Below we walk through what qualifies, what does not, how the risk assessment works, who must be told and when, and how to prepare so a bad day does not become a bad year.

Skypher
Handle Security Reviews With Less Friction
Skypher uses AI to help teams respond to security questionnaires, with support for multiple formats and integrations with TPRM platforms.
Visit Skypher

TL;DR

  • A HIPAA breach is an impermissible acquisition, access, use or disclosure of PHI that is presumed reportable unless you document a low probability of compromise or one of three exceptions applies.
  • For unsecured PHI, individuals must be notified without unreasonable delay and no later than 60 days after discovery. HHS must be notified too, on a timeline that depends on whether 500 or more people are affected.
  • Properly encrypted or destroyed PHI is not "unsecured," so the notification duty does not apply to it.
  • Business associates must notify the covered entity, and state laws can add stricter requirements.
  • Penalties rise with the level of culpability, and the annual maximum per violation now exceeds $2 million.

Table of Contents

What is a breach of HIPAA?

The definition lives in 45 CFR 164.402, and three ideas inside it matter most.

  1. Impermissible. The use or disclosure is not allowed under the Privacy Rule. Sharing a chart with a treating physician for care is permitted. Sending it to the wrong recipient is not.
  2. Unsecured PHI. The notification duty applies to PHI that has not been rendered unusable, unreadable or indecipherable to unauthorized people.
  3. Compromise. The incident is presumed to be a breach unless a risk assessment shows a low probability that the information was compromised.

The presumption is the part teams most often miss. You do not wait for proof that data was misused. You start from "this is a breach" and work backward to show it is not. CMS summarizes the same logic in its HIPAA basics guide for providers: any use or disclosure not permitted under the Privacy Rule is considered a breach unless a risk assessment shows a low probability of compromise.

Breach, violation and security incident are not the same thing

Every reportable breach involves a HIPAA problem, but not every HIPAA violation is a reportable breach. A HIPAA Journal explainer notes that an event may be a violation without meeting the breach definition, in which case the notification rule does not apply unless an exception is involved. Think of it this way:

  • A violation is a failure to follow a HIPAA requirement, such as missing a risk analysis or a workforce training.
  • A security incident is an attempted or successful unauthorized event affecting systems, such as a blocked intrusion.
  • A breach is an impermissible use or disclosure of unsecured PHI that you cannot show has a low probability of compromise.

The distinction shapes your paperwork. Violations need corrective action, security incidents need documentation and review, and breaches trigger the notification clock.

Examples of HIPAA breaches

The categories below are the ones compliance teams see over and over. They are illustrations of how the definition applies, not statistics.

  • Hacking and ransomware. An attacker gets into a network, an email account or a vendor's system and copies or encrypts patient records.
  • Unauthorized access by staff. An employee opens a neighbor's or coworker's chart with no job-related reason. The access is impermissible even if nothing is shared further.
  • Misdirected communications. A billing statement, fax or email with PHI goes to the wrong person.
  • Lost or stolen devices. An unencrypted laptop, phone or USB drive with patient data disappears.
  • Improper disposal. Paper records or old drives are thrown out without approved destruction.
  • Vendor failures. A business associate's misconfigured storage or compromised account exposes data it holds for a covered entity.

At scale, the numbers are large. The HIPAA Journal's healthcare data breach statistics report that in 2023, 725 breaches were reported to the HHS Office for Civil Rights (OCR), with more than 133 million records exposed or impermissibly disclosed. OCR also publishes the list of breaches affecting 500 or more individuals, which is worth browsing to see how real incidents are described.

The three exceptions

The regulation carves out three situations that are not breaches, even though PHI was used or disclosed improperly. Per 45 CFR 164.402:

  1. Good-faith workforce access. An unintentional acquisition, access or use by a workforce member or person acting under authority, made in good faith and within the scope of their authority, with no further impermissible use or disclosure.
  2. Inadvertent internal disclosure. An inadvertent disclosure by an authorized person to another authorized person at the same covered entity, business associate or organized health care arrangement, with no further impermissible use or disclosure.
  3. No reasonable ability to retain. A disclosure where the entity has a good-faith belief that the unauthorized recipient could not reasonably have retained the information.

Write down why an exception applies. If OCR ever asks, the burden of showing that you met your obligations sits with you, and a short, dated incident note is far easier to defend than a recollection.

The four-factor risk assessment

If no exception applies, you can still avoid notification by demonstrating a low probability of compromise. The regulation requires you to weigh at least these four factors:

FactorQuestion to answer
Nature and extent of the PHIWhat identifiers were involved, and how likely is re-identification?
The unauthorized personWho received or accessed it, and are they bound by HIPAA or similar obligations?
Acquisition or viewingWas the PHI actually acquired or viewed, or only exposed to the opportunity?
MitigationHow far have you reduced the risk, for example through assurances the data was destroyed?

A fax of lab results sent to another covered entity that promptly confirms deletion looks very different from the same fax sent to a stranger's home. Document your reasoning for each factor. If the honest conclusion is that you cannot show low probability, treat the event as a breach and move to notification.

When PHI is not "unsecured": the encryption safe harbor

Notification applies only to unsecured PHI. HHS guidance on the breach safe harbor explains two ways to get PHI out of that category:

  • Encryption. The data is rendered unusable, unreadable or indecipherable through an algorithmic process that meets the HIPAA Security Rule standard, and the decryption key is stored separately from the data.
  • Destruction. Paper, film and similar media are shredded or destroyed so PHI cannot be read or reconstructed, and electronic media are sanitized following the specified approaches. Redaction does not count as destruction.

In practice, this means a lost laptop with properly encrypted storage and a separately held key is generally not a notifiable event, while the same laptop unencrypted almost certainly is. Documented key management and approved disposal are the details that decide it, and the same discipline shows up in any mature enterprise security program. For the technical safeguards behind this, see our guide to the HIPAA Security Rule for businesses.

Who must be notified, and by when

The timelines come straight from the HHS Breach Notification Rule. The AHIMA breach management toolkit reiterates that the covered entity is ultimately responsible for making sure each notice goes out.

WhoWhatDeadline
Affected individualsWritten noticeWithout unreasonable delay, no later than 60 days after discovery
HHS Secretary, 500 or more affectedBreach report via OCR portalWithout unreasonable delay, no later than 60 days
HHS Secretary, fewer than 500 affectedBreach report, can be batchedNo later than 60 days after the end of the calendar year in which the breaches were discovered
MediaNotice to prominent outlets when more than 500 residents of a state or jurisdiction are affectedSame timeline as individual notice
Covered entity (from a business associate)Notice of breachWithout unreasonable delay, no later than 60 days from discovery

The 60 days is an outer limit, not a target. Waiting until day 59 when you knew everything on day 10 can itself be a problem.

How to deliver individual notices

HHS says individual notices go by first-class mail, or by email if the person agreed to electronic notice. If contact information is out of date for 10 or more individuals, you must provide substitute notice, either a website posting for at least 90 days or major print or broadcast media, along with a toll-free number that stays active for at least 90 days.

Substitute notice thresholds and durations

Business associates

A business associate that discovers a breach tells the covered entity, which then handles the individual, HHS and media notices. Contracts often tighten the clock. One federal business associate agreement template from IHS, for example, requires reporting of unauthorized uses or disclosures within thirty days. Shorter contractual windows give the covered entity room to meet its own 60-day limit, which is the governance point AHIMA stresses.

Business associates

State laws can add more

HIPAA is a floor. AHIMA's toolkit advises reviewing state law to determine the full set of obligations, and many states set their own notice content, timing or regulator-notification requirements. Check the states where your patients or customers live before you finalize any notice.

A practical response plan

When you suspect a breach, the order of operations matters more than speed alone.

  1. Contain. Cut off access, recover devices, revoke credentials, and ask recipients of misdirected data to delete it.
  2. Preserve evidence. Keep logs, emails and device images before anything is overwritten.
  3. Start the clock record. Note the date and time of discovery. The 60 days run from discovery, not from when your investigation ends.
  4. Assess. Check the three exceptions, then run the four-factor assessment and write it down.
  5. Notify. If it is a reportable breach, send individual notices, file with HHS, and notify media where required. Loop in your legal counsel and, where relevant, your cyber insurer.
  6. Fix the cause. Update policies, retrain staff, and tighten access controls. Our data privacy best practices for B2B teams cover the habits that prevent repeats.

What a breach can cost

OCR enforces the Privacy, Security and Breach Notification Rules, and consequences scale with culpability. According to the HIPAA Journal's report on the 2026 inflation adjustment, the maximum penalty for a HIPAA violation as of January 28, 2026 is $2,190,294, with four tiers that rise from unknowing violations to willful neglect that is not corrected. Figures are adjusted every year, so confirm the current amounts before you cite them internally. The American Medical Association's overview of HIPAA violations and enforcement also covers criminal penalties for knowing misuse. For how investigations unfold, read our piece on HIPAA enforcement for compliance officers.

The regulatory fine is only part of the picture. Customers and partners ask hard questions after an incident, usually in the form of security questionnaires, and the quality of your answers affects deals as much as the fine does.

Our perspective

We see HIPAA breaches from an unusual angle: the questionnaires that arrive afterward. When a healthcare organization or one of its vendors has an incident, or simply wants to prove it has none waiting to happen, security and compliance teams get asked the same things again and again. How is PHI encrypted? Who has access? What is your breach notification process? Where is the evidence?

Our view is that most breach exposure is a knowledge problem before it is a technology problem. The policies exist, the encryption exists, the business associate agreements exist, but the answers are scattered across documents, tickets and people's heads. When a team cannot answer quickly and consistently, mistakes follow: a stale answer to a customer, an inconsistent statement to an auditor.

That is why we built Skypher around a single, versioned knowledge base and a retrieval-based AI that drafts answers from your own approved content, with a confidence score so reviewers know where to look first. We believe your breach response story, your safeguards and your evidence deserve to be told the same way every time, and a platform that keeps them current is a strong foundation for that.

Gaspard

Make your answers audit-ready

If your team fields HIPAA and security reviews from health system customers, our Questionnaire Automation Tool helps you respond from your approved content in whatever format the questionnaire arrives, with real-time collaboration for the whole team.

Skypher

Pair it with a customizable Trust Center so customers can see your security posture up front, and see the pricing page for how to get started. Teams that also handle diligence requests can look at DDQ automation.

Reducing the odds of a breach

You cannot prevent every incident, but you can shrink the list of ways one happens.

  • Run and document a risk analysis. A structured HIPAA assessment shows where PHI lives and where it is exposed.
  • Encrypt by default. Laptops, phones, backups and transmissions. It turns many losses into non-events for notification purposes.
  • Limit and review access. Role-based permissions and regular audit-log reviews catch snooping early.
  • Train and retrain. Short, role-specific sessions work better than one annual marathon. Our guide to HIPAA training videos can help you structure them.
  • Manage vendors. Maintain business associate agreements with clear reporting windows and ask for evidence of safeguards.
  • Rehearse. Run a tabletop exercise on a ransomware scenario and a misdirected-email scenario so the first real response is not the first practice.

FAQ

What is the most common type of HIPAA breach?

By volume of incidents, hacking and IT incidents against healthcare organizations and their vendors dominate the reports to OCR, while unauthorized access and misdirected disclosures make up much of the remainder. The HIPAA Journal statistics page breaks the causes down by year. Your own risk analysis will show which category is most likely for you.

Is every HIPAA violation a breach?

No. A violation is any failure to meet a HIPAA requirement, while a breach is an impermissible use or disclosure of unsecured PHI that you cannot show has a low probability of compromise or fit within an exception. Violations that are not breaches still need corrective action and documentation.

How long do we have to report a HIPAA breach?

Individuals must be notified without unreasonable delay and no later than 60 days after discovery. For breaches affecting 500 or more people, HHS gets notice on the same timeline, while smaller breaches can be reported to HHS within 60 days after the end of the calendar year. State law or your contracts may set shorter windows.

Does encryption mean we never have to report?

Encryption that meets the HIPAA Security Rule standard, with the key stored separately, takes PHI out of the "unsecured" category, so the notification rule does not apply to it. If the key was exposed along with the data, treat the event as a potential breach and assess it.

Sources