1 · Nature and extent of the PHI
The types of identifiers involved and the likelihood the information could be re-identified, including how sensitive it is.
The HIPAA Breach Notification Rule requires covered entities and business associates to notify affected individuals, the Secretary of HHS, and sometimes the media after a breach of unsecured protected health information. Individuals must be notified without unreasonable delay and no later than 60 days after the breach is discovered.
The HIPAA Breach Notification Rule, codified at 45 CFR §§ 164.400-414, requires HIPAA covered entities and their business associates to provide notification following a breach of unsecured protected health information. It was strengthened by the HITECH Act and is enforced by the HHS Office for Civil Rights.
It is the third of the core HIPAA rules, alongside the Privacy Rule and the Security Rule. Where those two work to prevent incidents, the Breach Notification Rule governs what happens after one: how to decide whether an incident is reportable, and who must be told within what deadline.
A breach is, broadly, an impermissible use or disclosure of protected health information that compromises its security or privacy. The crucial nuance is the presumption: an impermissible use or disclosure is presumed to be a breach unless the organisation can demonstrate a low probability that the PHI was compromised.
The rule includes a few specific exceptions, such as certain good-faith, unintentional access by a workforce member acting within their authority, or an inadvertent disclosure between authorised people at the same organisation, provided the information is not further used or disclosed improperly. Outside those exceptions, you must run a risk assessment to rebut the presumption.
To rebut the presumption of a breach, you assess the probability that PHI was compromised using at least these four factors, and you must document the analysis.
The types of identifiers involved and the likelihood the information could be re-identified, including how sensitive it is.
Who used the PHI or to whom it was disclosed, and whether that person has an obligation to protect it (for example, another covered entity).
Whether the PHI was actually acquired or viewed, or whether only the opportunity existed (for example, a returned laptop confirmed never accessed).
The extent to which the risk to the PHI has been mitigated, for example through assurances of destruction or confidentiality from the recipient.
If, weighing these factors, you can show a low probability that the PHI was compromised, notification may not be required, but you must keep the documented assessment to defend that conclusion.
For a reportable breach of unsecured PHI, up to three audiences must be notified. The number of affected individuals and where they live drive which apply.
Written notice (usually first-class mail, or email if the individual agreed) describing the breach, the PHI involved, what individuals should do, and what the organisation is doing in response.
Breaches affecting 500 or more individuals must be reported to HHS without unreasonable delay and within 60 days. Breaches affecting fewer than 500 are logged and reported to HHS within 60 days of the end of the calendar year.
If a breach affects more than 500 residents of a state or jurisdiction, the organisation must also notify prominent media outlets serving that area, in addition to the individual notices.
A business associate that discovers the breach must notify the covered entity, which generally carries the obligation to notify individuals. Settle these responsibilities in the Business Associate Agreement before an incident, not during one.
The Breach Notification Rule applies only to unsecured PHI: protected health information that has not been rendered unusable, unreadable, or indecipherable to unauthorised people through a method specified in HHS guidance, principally encryption or proper destruction.
This creates a powerful incentive. If PHI is properly encrypted to the HHS standard and the decryption key was not also compromised, a breach of that data generally does not trigger notification at all. Encryption of ePHI at rest and in transit is, in effect, a safe harbor, which is one reason it is treated as a baseline even though it is technically an addressable specification under the Security Rule.
The cheapest breach to manage is the one you never have to report. Encrypting PHI to the HHS standard removes most lost-device and intercepted-data incidents from the notification obligation entirely.
Six steps that turn a chaotic incident into a defensible response. Build this workflow before you need it; the 60-day clock starts at discovery, not when you finish investigating.
Identify the incident, contain it, and preserve the facts: what happened, what PHI was involved, when it was discovered, and who was affected. The clock starts on discovery.
Assess whether the impermissible use or disclosure compromised the PHI using the four required factors. Document the analysis, the presumption is that it is a breach unless you can show a low probability of compromise.
If it is a reportable breach, determine who must be notified, individuals, HHS, and possibly the media, based on the number of people affected and where they are.
Send individual notices without unreasonable delay and no later than 60 days from discovery, report to HHS on the required timeline, and notify media where the 500-resident threshold is met.
If a business associate discovered the breach, it must notify the covered entity, which generally carries the obligation to notify individuals. Agree these responsibilities in the BAA in advance.
Keep the risk assessment, the notifications, and the timeline. In an investigation the burden of proof is on you to show either that notifications were made or that an exception applied.
RiskWatch keeps your HIPAA Privacy, Security, and breach-response workflows on one platform: a documented incident and risk- assessment process, BAA tracking, and the timestamped evidence trail OCR expects if a breach is investigated.
The questions compliance and security teams ask when an incident hits.
A documented incident and risk-assessment workflow, BAA tracking, and a timestamped audit trail across HIPAA's Privacy, Security, and Breach rules. 30-day free trial, no credit card.
No credit card required · 30-day free trial · Cancel anytime