Previous All Posts Next

HIPAA Breach Notification Guide

Posted: March 27, 2026 to Compliance.

Understanding HIPAA Breach Notification Requirements

When a breach of unsecured Protected Health Information (PHI) occurs, the HIPAA Breach Notification Rule (45 CFR 164.400-414) requires covered entities and business associates to follow a strict notification process with specific timelines, content requirements, and reporting obligations. Getting breach notification wrong, whether through delayed reporting, incomplete notifications, or failure to notify at all, can result in penalties that exceed the penalties for the breach itself.

The Breach Notification Rule was established by the HITECH Act of 2009 and strengthened by the HIPAA Omnibus Rule of 2013. It applies to all covered entities (healthcare providers, health plans, and healthcare clearinghouses) and their business associates. Every organization that handles PHI must have a documented breach notification procedure that their workforce understands and can execute under pressure.

What Constitutes a Breach Under HIPAA

HIPAA defines a breach as the acquisition, access, use, or disclosure of PHI in a manner not permitted by the HIPAA Privacy Rule that compromises the security or privacy of the PHI. The key phrase is "compromises the security or privacy," which HIPAA presumes has occurred unless the covered entity can demonstrate a low probability that the PHI was actually compromised.

The Four-Factor Risk Assessment

When an impermissible use or disclosure occurs, you must conduct a risk assessment considering four factors to determine whether notification is required:

  1. The nature and extent of the PHI involved: What types of identifiers and clinical information were exposed? Social Security numbers, financial information, and clinical diagnoses carry higher risk than names and addresses alone.
  2. The unauthorized person who used the PHI or to whom it was disclosed: Was the recipient a covered entity or business associate with their own HIPAA obligations? Or was it an unknown third party or the general public?
  3. Whether the PHI was actually acquired or viewed: Can you demonstrate that the PHI was not actually accessed? For example, an encrypted laptop stolen but never powered on may not result in actual access.
  4. The extent to which the risk has been mitigated: What steps were taken to reduce the risk of harm? Did you obtain the recipient's written assurance that the PHI was destroyed? Did you recover the device?

If, after this assessment, you determine there is more than a low probability that PHI was compromised, you must proceed with breach notification. When in doubt, treat the incident as a reportable breach. The OCR has penalized organizations for concluding too liberally that incidents were not reportable.

Exceptions to the Breach Definition

Three scenarios are excluded from the breach definition:

  • Unintentional acquisition by a workforce member: Good-faith, unintentional access by an authorized person acting within the scope of their authority, provided the information is not further used or disclosed impermissibly
  • Inadvertent disclosure between authorized persons: Disclosure from one authorized person to another authorized person within the same covered entity or business associate, provided the information is not further used or disclosed impermissibly
  • Good-faith belief the recipient cannot retain the information: A disclosure where the covered entity has a good-faith belief that the unauthorized person could not reasonably retain the PHI (such as a misdirected fax to a number that did not answer)

Notification Timeline Requirements

Individual Notification: 60 Days

Covered entities must notify affected individuals without unreasonable delay and no later than 60 calendar days after discovering the breach. "Discovery" occurs on the first day the breach is known to the covered entity or, by exercising reasonable diligence, would have been known. This means that failing to investigate a suspicious incident does not extend your timeline.

Individual notification must be provided in written form by first-class mail (or email if the individual has agreed to electronic notice). The notification must include:

  • A brief description of what happened, including the date of the breach and the date of discovery
  • A description of the types of unsecured PHI involved (such as full name, Social Security number, date of birth, diagnosis, etc.)
  • Steps the individual should take to protect themselves from potential harm
  • A brief description of what the covered entity is doing to investigate, mitigate harm, and prevent future breaches
  • Contact information for the covered entity including a toll-free phone number, email address, postal address, or website

Media Notification: 60 Days (for Large Breaches)

If a breach affects 500 or more individuals in a single state or jurisdiction, the covered entity must notify prominent media outlets serving that state or jurisdiction within 60 days of discovery. This typically means issuing a press release to major news outlets in the affected area.

HHS Notification: Varies by Size

  • 500+ individuals: Notify the HHS Secretary within 60 days of discovery by submitting a breach report through the HHS breach portal (ocrportal.hhs.gov). These breaches are posted on the HHS "Wall of Shame" (officially the Breach Portal) and are publicly visible.
  • Fewer than 500 individuals: Notify the HHS Secretary within 60 days of the end of the calendar year in which the breach was discovered. These smaller breaches are logged annually rather than individually.

Business Associate Notification: 60 Days to Covered Entity

Business associates must notify the covered entity of a breach without unreasonable delay and no later than 60 days after discovery. However, BAAs frequently include shorter notification timelines. Many require notification within 24 to 72 hours. Check your specific BAA terms.

Building a Breach Notification Response Plan

Before a Breach: Preparation

  1. Document your breach notification procedures: Written procedures covering identification, assessment, containment, investigation, notification, and remediation
  2. Designate a breach response team: Include Privacy Officer, Security Officer, legal counsel, communications, IT, and executive leadership
  3. Prepare notification templates: Draft template letters, press releases, and HHS portal submissions that can be customized quickly during an actual breach
  4. Establish vendor relationships: Pre-negotiate relationships with breach response vendors including forensic investigators, notification mailing services, credit monitoring providers, and external legal counsel
  5. Train your workforce: Every employee must know how to report a suspected breach internally. The internal reporting chain determines when the 60-day clock starts.

During a Breach: Response

  1. Contain: Stop the breach immediately. Isolate affected systems, revoke compromised credentials, and prevent further unauthorized access.
  2. Investigate: Determine what PHI was involved, how many individuals are affected, how the breach occurred, and whether the PHI was actually accessed or viewed.
  3. Assess: Conduct the four-factor risk assessment to determine whether notification is required.
  4. Document: Maintain a complete investigation record including timeline, evidence, decisions, and rationale. This documentation is your defense if the OCR investigates.
  5. Notify: If notification is required, execute within the 60-day timeline. Do not delay notification to complete the investigation if you have sufficient information to notify.
  6. Remediate: Address the root cause to prevent recurrence. Update policies, retrain staff, patch systems, or adjust controls as needed.

Common Breach Notification Mistakes

  • Delayed internal reporting: The 60-day clock starts at discovery, not at the completion of investigation. Workforce members who delay reporting incidents to management trigger late notification.
  • Inadequate risk assessment: Organizations that conclude too aggressively that incidents are not reportable face enhanced penalties when the OCR disagrees
  • Incomplete notification content: Missing required elements in the notification letter violates the rule even if notification was timely
  • Failure to notify media: Organizations sometimes notify individuals and HHS but overlook the media notification requirement for large breaches
  • No documentation: Failing to document the risk assessment, investigation findings, and notification decisions leaves you unable to defend your actions

State Breach Notification Law Interactions

In addition to HIPAA, most states have their own breach notification laws that may impose additional or more stringent requirements. North Carolina's Identity Theft Protection Act (N.C.G.S. 75-65) requires notification without unreasonable delay. Some states like California, New York, and Texas have specific content and timing requirements that exceed HIPAA's. When a breach occurs, evaluate both HIPAA and applicable state law requirements and comply with whichever is more stringent.

Digital Forensics in HIPAA Breach Investigation

When a potential breach is discovered, digital forensics determines the scope, method, and timeline of the incident. The quality of your forensic investigation directly affects your ability to accurately identify affected individuals, satisfy the OCR's expectation of reasonable diligence, and defend your breach notification decisions if challenged.

Forensic Investigation Steps

A HIPAA breach forensic investigation typically involves evidence preservation (creating forensic images of affected systems before any remediation that might destroy evidence), log analysis (reviewing authentication logs, access logs, firewall logs, and system event logs to determine how the attacker gained access and what data was accessed), malware analysis (if malware was involved, analyzing the malware to understand its capabilities, data exfiltration methods, and command-and-control infrastructure), data exposure assessment (determining specifically what PHI was accessible to the attacker, which may differ from what PHI was actually exfiltrated), and timeline reconstruction (establishing when the breach began, when the attacker accessed specific data, and when the breach was contained).

Engaging Forensic Investigators

Most healthcare organizations do not have in-house digital forensics capabilities and need to engage external investigators. Establish a relationship with a forensic investigation firm before a breach occurs. During a breach, time is critical and starting from scratch with vendor selection adds days to your response timeline. Engage investigators through your legal counsel to preserve attorney-client privilege over the investigation findings. Forensic investigation costs range from $50,000 to $500,000 depending on the complexity and scope of the incident.

Breach Notification Under the Proposed HIPAA Security Rule Update

The proposed HIPAA Security Rule update (NPRM published late 2024) includes several provisions that would affect breach notification and incident response if finalized:

  • 72-hour system restoration requirement: Covered entities and business associates would be required to restore critical systems within 72 hours of an incident. This dramatically accelerates recovery expectations and requires robust disaster recovery infrastructure and testing.
  • Mandatory encryption: Encryption would change from an addressable specification to a required specification. This means the encryption safe harbor for breach notification becomes even more important because non-encrypted PHI would be a clear violation of the updated rule.
  • Annual compliance audits: Organizations would be required to conduct annual compliance audits and submit written verification to HHS. This creates additional documentation requirements for breach preparedness.
  • Enhanced incident response documentation: The proposed rule would require more detailed incident response plans with specific procedures for different types of incidents, tested at least annually.

While the proposed rule has not been finalized, organizations should begin preparing now. The 72-hour restoration requirement alone requires significant investment in backup infrastructure, recovery testing, and incident response automation. Organizations that wait for the final rule to begin preparing will face a compressed implementation timeline.

Breach Costs: What to Expect

Understanding the full financial impact of a HIPAA breach helps organizations justify investment in prevention and response readiness.

Direct Costs

  • Forensic investigation: $50,000 to $500,000 depending on complexity. Forensic investigators determine the scope, method, and timeline of the breach.
  • Legal fees: $100,000 to $1,000,000+ for breach response legal counsel, regulatory interaction, and potential litigation defense.
  • Notification costs: $1 to $5 per affected individual for printing, postage, and mailing breach notification letters. For a breach affecting 50,000 individuals, notification mailing alone costs $50,000 to $250,000.
  • Credit monitoring: $1 to $5 per person per month for 12 to 24 months. For 50,000 affected individuals, credit monitoring costs $600,000 to $6,000,000.
  • Call center: Breach notification letters generate calls from concerned individuals. Dedicated call center services cost $50,000 to $200,000 for the response period.
  • Regulatory penalties: OCR penalties range from $100 to $50,000 per violation with annual caps of $1.5 million per violation category. The actual penalty depends on the violation tier and the organization's compliance history.

Indirect Costs

  • Reputation damage: Patient attrition following a breach typically ranges from 5 to 7% according to the Ponemon Institute. For a practice with 10,000 patients and an average annual revenue of $500 per patient, losing 5% represents $250,000 in annual revenue.
  • Operational disruption: Staff time diverted from patient care to breach response, increased workload on IT and compliance teams, and potential system downtime during investigation and remediation.
  • Insurance premium increases: Cyber insurance premiums typically increase 25 to 100% following a breach claim.
  • Corrective action plan: OCR enforcement often includes mandatory corrective action plans lasting 2 to 3 years with ongoing monitoring costs and reporting obligations.

Average Breach Cost by Size

IBM's Cost of a Data Breach Report consistently ranks healthcare as the most expensive industry for breaches. The average healthcare breach cost in 2023 was $10.93 million. However, costs vary dramatically by breach size. Breaches affecting fewer than 500 individuals may cost $100,000 to $500,000 in total. Breaches affecting 500 to 10,000 individuals typically cost $500,000 to $5 million. Breaches affecting 10,000 to 100,000 individuals range from $2 million to $20 million. Large breaches affecting 100,000+ individuals can exceed $50 million in total costs.

Breach Notification Template Elements

Having a pre-drafted notification letter template significantly accelerates your response when a breach occurs. Your template should include these elements, with placeholders for incident-specific details:

  • Opening paragraph: Brief description of what happened, including approximate dates of the breach and discovery
  • Information involved: Specific types of PHI that were affected (names, dates of birth, Social Security numbers, medical record numbers, treatment information, insurance information, etc.)
  • What you are doing: Steps taken to investigate the breach, contain the damage, and prevent recurrence
  • What they should do: Specific recommended actions for affected individuals (review Explanation of Benefits statements, monitor credit reports, place fraud alerts, file identity theft reports if applicable)
  • Services offered: Description of credit monitoring or identity protection services you are providing, with enrollment instructions
  • Contact information: Toll-free phone number for the dedicated breach response line, email address, mailing address, and hours of availability
  • HHS complaint rights: Information about the individual's right to file a complaint with the HHS Secretary

Have your legal counsel review the template before a breach occurs so it can be customized and sent quickly when needed. The 60-day clock does not pause while you draft notification letters.

Need Help with HIPAA Breach Response?

Petronella Technology Group provides HIPAA compliance services including breach response planning, incident investigation, and security monitoring that detects breaches before they escalate. Schedule a free consultation or call 919-348-4912.

Frequently Asked Questions

Does encryption prevent a breach notification obligation?+
Yes, if the encryption meets NIST standards and the encryption key was not compromised. HIPAA's Breach Notification Rule applies to unsecured PHI. PHI is considered secured (and therefore not subject to breach notification) if it is encrypted with an algorithm consistent with NIST Special Publication 800-111. If an encrypted laptop is stolen but the encryption key was not compromised, no breach notification is required.
What happens if we miss the 60-day notification deadline?+
Late notification is itself a HIPAA violation subject to enforcement. The OCR has imposed penalties specifically for delayed notification even when the organization eventually notified affected individuals. Penalties range from $100 to $50,000 per violation depending on the tier, with a maximum of $1.5 million per violation category per year. Document any delays and the reasons.
Do business associates have their own notification obligations?+
Business associates must notify the covered entity of a breach within the timeframe specified in their BAA (or within 60 days if the BAA does not specify). The covered entity is then responsible for notifying affected individuals, media, and HHS. Business associates do not notify individuals directly unless the BAA specifically delegates that responsibility.
Is a ransomware attack a reportable breach?+
In most cases, yes. HHS issued guidance in 2016 stating that ransomware attacks presumptively constitute a breach because the attacker has accessed (encrypted) the PHI. You must conduct the four-factor risk assessment, but the presumption is that notification is required unless you can demonstrate a low probability that the PHI was actually viewed or exfiltrated, which is difficult to prove with ransomware.
Should we offer credit monitoring to affected individuals?+
HIPAA does not require offering credit monitoring, but it is considered a best practice and may be required under state breach notification laws. Offering credit monitoring demonstrates good faith and reduces the risk of lawsuits from affected individuals. The cost typically ranges from $1 to $5 per person per month. For breaches involving Social Security numbers or financial information, credit monitoring is strongly recommended.
Need help implementing these strategies? Our cybersecurity experts can assess your environment and build a tailored plan.
Get Free Assessment

About the Author

Craig Petronella, CEO and Founder of Petronella Technology Group
CEO, Founder & AI Architect, Petronella Technology Group

Craig Petronella founded Petronella Technology Group in 2002 and has spent more than 30 years working at the intersection of cybersecurity, AI, compliance, and digital forensics. He holds the CMMC Registered Practitioner credential (RP-1372) issued by the Cyber AB, is an NC Licensed Digital Forensics Examiner (License #604180-DFE), and completed MIT Professional Education programs in AI, Blockchain, and Cybersecurity. Craig also holds CompTIA Security+, CCNA, and Hyperledger certifications.

He is an Amazon #1 Best-Selling Author of 15+ books on cybersecurity and compliance, host of the Encrypted Ambition podcast (95+ episodes on Apple Podcasts, Spotify, and Amazon), and a cybersecurity keynote speaker with 200+ engagements at conferences, law firms, and corporate boardrooms. Craig serves as Contributing Editor for Cybersecurity at NC Triangle Attorney at Law Magazine and is a guest lecturer at NCCU School of Law. He has served as a digital forensics expert witness in federal and state court cases involving cybercrime, cryptocurrency fraud, SIM-swap attacks, and data breaches.

Under his leadership, Petronella Technology Group has served 2,500+ clients, maintained a zero-breach record among compliant clients, earned a BBB A+ rating every year since 2003, and been featured as a cybersecurity authority on CBS, ABC, NBC, FOX, and WRAL. The company leverages SOC 2 Type II certified platforms and specializes in AI implementation, managed cybersecurity, CMMC/HIPAA/SOC 2 compliance, and digital forensics for businesses across the United States.

CMMC-RP NC Licensed DFE MIT Certified CompTIA Security+ Expert Witness 15+ Books
Related Service
Achieve Compliance with Expert Guidance

CMMC, HIPAA, NIST, PCI-DSS — we have 80% of documentation pre-written to accelerate your timeline.

Learn About Compliance Services
Previous All Posts Next
Free cybersecurity consultation available Schedule Now