HIPAA Breach Exceptions Explained: What Qualifies and When Notification Isn’t Required
Unintentional Access by Workforce Members
HIPAA recognizes a narrow exception when a workforce member, or someone acting under a covered entity’s or business associate’s authority, unintentionally accesses or uses protected health information (PHI) in good faith and within the scope of their duties. If the access does not result in further impermissible use or disclosure, it is not a reportable breach of unsecured protected health information.
To rely on this exception, you should confirm three points: the action was accidental, it occurred during legitimate job functions, and the information was not subsequently shared in a way that violates Privacy Rule compliance. Curiosity-based “snooping,” repeated mistakes, or any disclosure outside authorized channels will disqualify the event.
Covered entity obligations include immediate mitigation, documenting the facts, and reinforcing appropriate safeguards. Maintain an internal record of the event and corrective steps as part of your breach risk assessment program and overall compliance file retention.
Inadvertent Disclosure Between Authorized Persons
Another exception applies when a person authorized to access PHI at a covered entity or business associate inadvertently discloses it to another authorized person within the same organization or within an Organized Health Care Arrangement. Because both parties are permitted to handle the information, this limited misdirection is generally not a breach.
The key conditions are that both sender and recipient are authorized for the same or related information and that the recipient does not further use or disclose PHI in a manner not permitted by the Privacy Rule. You should still log the event, confirm containment, and, if appropriate, provide targeted training to prevent recurrence.
Good Faith Belief That Information Cannot Be Retained
A disclosure is not a breach if you have a good faith belief that the unauthorized recipient could not reasonably have retained the information. Classic examples include a sealed letter returned unopened to the sender or a chart handed to the wrong patient but immediately retrieved before it could be read or copied.
Good faith must be supported by facts. Act quickly to retrieve or secure the information, and document why retention was unlikely—such as the material being unreadable, promptly recovered, or otherwise inaccessible. If you cannot reasonably substantiate non-retention, proceed with a breach risk assessment.
Encryption Safe Harbor
When PHI is encrypted in accordance with recognized encryption standards, it is considered secured and therefore falls outside the breach notification requirements. In practical terms, a lost, stolen, or improperly accessed device or file may not trigger notification if the PHI was strongly encrypted and the keys were not compromised.
Data at Rest
Use strong, industry-accepted encryption for databases, servers, portable media, and endpoints. Full-disk encryption or file-level encryption should leverage validated cryptographic modules, with keys stored separately and protected by robust access controls. If a device is lost but the encryption and key management are sound, the incident typically involves no unsecured protected health information.
Data in Transit
Encrypt PHI transmitted over open networks using current protocols (for example, modern TLS) and disable deprecated cipher suites. Ensure emails carrying PHI are encrypted end to end or routed through secure portals, and verify that integrations and APIs enforce transport-layer encryption consistently.
Limits of Safe Harbor
Encryption safe harbor does not apply if decryption keys, passwords, or tokens were also exposed, if encryption was disabled or misconfigured, or if PHI was viewed on screen before encryption took effect. When in doubt, treat the event as involving unsecured protected health information and perform a breach risk assessment.
Ready to simplify HIPAA compliance?
Join thousands of organizations that trust Accountable to manage their compliance needs.
Risk Assessment for Breach Determination
HIPAA presumes an impermissible use or disclosure is a breach unless you demonstrate a low probability that PHI has been compromised. You do this through a documented, fact-specific breach risk assessment that weighs four required factors and any relevant mitigation steps.
The Four Required Factors
- Nature and extent of PHI involved, including types of identifiers and the likelihood of re-identification.
- The unauthorized person who used PHI or to whom the disclosure was made and their ability to re-identify or misuse it.
- Whether PHI was actually acquired or viewed, as opposed to merely exposed without evidence of access.
- The extent to which the risk has been mitigated, such as immediate retrieval, verified deletion, or reliable recipient attestations.
Your analysis should be objective, consistent, and well-documented. Incorporate technical logs, access reports, and mitigation evidence. This documentation supports Privacy Rule compliance and demonstrates due diligence if regulators review your decision-making.
Reporting Breaches Affecting Fewer Than 500 Individuals
If your assessment finds a reportable breach impacting fewer than 500 individuals, you must notify affected individuals without unreasonable delay and no later than 60 calendar days from discovery. Notices should explain what happened, what types of PHI were involved, what you are doing in response, steps individuals can take to protect themselves, and how to reach you.
Under the Notification timelines for small incidents, you must also log these breaches and report them to the Department of Health and Human Services annually—no later than 60 days after the end of the calendar year in which they were discovered. Media notice is not required for these smaller events, but covered entity obligations include retaining your breach risk assessment and all notices for the required recordkeeping period.
Media Notifications for Large Breaches
For breaches affecting more than 500 residents of a single state or jurisdiction, you must notify prominent media outlets serving that area without unreasonable delay and in no case later than 60 calendar days from discovery. This media notice should mirror the content of individual notifications and be coordinated with your overall response plan.
Large breaches also trigger expedited regulatory reporting through the HHS portal within the same 60-day outer limit, in addition to individual notices. Align your public statements, regulator reports, and remediation updates to ensure accuracy and consistency across all audiences.
Summary
HIPAA’s breach exceptions are intentionally narrow. Use them only when facts clearly fit the criteria, PHI is secured under strong encryption standards, or a documented breach risk assessment shows a low probability of compromise. When notification is required, follow the applicable timelines and fulfillment steps to maintain compliance and trust.
FAQs
What constitutes an unintentional access exception under HIPAA?
This exception applies when a workforce member (or someone under a covered entity’s or business associate’s authority) unintentionally acquires, accesses, or uses PHI in good faith, within the scope of their duties, and without further impermissible use or disclosure. Accidental, job-related access that is promptly contained can qualify, but intentional snooping or sharing does not.
When is breach notification not required due to encryption?
Notification is not required when the affected PHI was encrypted consistent with recognized encryption standards and the decryption keys were not compromised. Strong encryption for data at rest and in transit renders the PHI secured, meaning the incident does not involve unsecured protected health information.
How does a covered entity determine the risk of PHI compromise?
Perform a documented breach risk assessment that evaluates the nature and extent of PHI involved, who received or accessed it, whether it was actually acquired or viewed, and how effectively you mitigated the exposure. If the analysis supports a low probability of compromise, the incident is not a reportable breach; otherwise, follow notification requirements.
What are the notification requirements for breaches affecting fewer than 500 individuals?
You must notify each affected individual without unreasonable delay and no later than 60 calendar days after discovery, using plain language that explains the event, the PHI involved, your response, recommended protective steps, and contact information. You must also record these incidents and report them to HHS annually within 60 days after the end of the calendar year in which they were discovered.
Table of Contents
- Unintentional Access by Workforce Members
- Inadvertent Disclosure Between Authorized Persons
- Good Faith Belief That Information Cannot Be Retained
- Encryption Safe Harbor
- Risk Assessment for Breach Determination
- Reporting Breaches Affecting Fewer Than 500 Individuals
- Media Notifications for Large Breaches
- FAQs
Ready to simplify HIPAA compliance?
Join thousands of organizations that trust Accountable to manage their compliance needs.