Healthcare Data Breach Response for Medical Practices
Published · Last updated · 9 min read

When a medical practice suspects a breach of patient information, it must contain the incident, preserve evidence, run the HIPAA four-factor risk assessment and, if notification is required, notify affected patients without unreasonable delay and no later than 60 days after discovery. Breaches affecting 500 or more people also require notice to HHS and, in some cases, the media within the same 60 days.
Key takeaways
- Under HIPAA, an impermissible use or disclosure of protected health information is presumed to be a breach unless a documented four-factor risk assessment shows a low probability of compromise.
- Individual notice is due without unreasonable delay and no later than 60 calendar days after discovery; 60 days is an outer limit, not a target.
- Breaches of 500 or more people go to HHS within 60 days, and media notice is required when more than 500 residents of a state or jurisdiction are affected. Smaller breaches are logged and reported to HHS within 60 days after the end of the calendar year.
- Properly encrypted information is not "unsecured," so its loss generally does not trigger notification.
- State breach laws can impose shorter deadlines or extra notices, so check every state where affected patients live.
What counts as a data breach under HIPAA?
Under the HIPAA Breach Notification Rule at 45 CFR 164.400 to 414, a breach is generally an impermissible use or disclosure under the Privacy Rule that compromises the security or privacy of protected health information. The rule starts from a presumption: an impermissible use or disclosure is a breach unless the covered entity or business associate demonstrates a low probability that the information has been compromised.
There are three narrow exceptions: unintentional, good-faith access by a workforce member acting within their authority; inadvertent disclosure between people authorized to access the information at the same organization; and disclosures where you have a good-faith belief the recipient could not have retained the information. In each case, the information cannot be further used or disclosed improperly.
Notification duties apply only to unsecured protected health information. Information encrypted or destroyed according to HHS guidance is considered secured, which is one of the strongest reasons to encrypt laptops, mobile devices, backups and email.
What should a practice do in the first 24 hours?
- Contain the incident. Isolate affected computers from the network, disable compromised accounts, reset credentials and block the attacker's access. Do not power off or wipe systems before evidence is preserved unless needed to stop active harm.
- Activate your incident response plan. Bring in your security official, practice leadership, IT provider and legal counsel. Our guide to incident response planning covers roles and steps.
- Preserve evidence. Keep logs, emails, alerts and affected devices. Record a timeline of what was found, when and by whom.
- Call your cyber insurer early. Most policies require prompt notice and may require you to use approved forensic and legal firms.
- Keep patient care running. Switch to downtime procedures for scheduling, charting and prescriptions if systems are unavailable.
- Start the clock. A breach is treated as discovered on the first day it is known, or by exercising reasonable diligence would have been known, to any workforce member other than the person who caused it.
How do you decide whether notification is required?
Unless an exception applies or you choose to notify without one, you must complete and document a risk assessment of at least four factors:
- The nature and extent of the protected health information involved, including the types of identifiers and the likelihood of re-identification.
- The unauthorized person who used the information or to whom it was disclosed.
- Whether the information was actually acquired or viewed.
- The extent to which the risk has been mitigated.
If the assessment does not show a low probability of compromise, notification is required. You carry the burden of proof either way, so keep the assessment, the evidence behind it and the decision.
Ransomware deserves specific attention. HHS has said that when ransomware encrypts electronic protected health information, the encryption is itself an unauthorized acquisition, so the incident is presumed to be a breach unless the four-factor assessment shows a low probability of compromise. Modern ransomware groups usually steal data before encrypting it, which makes that showing harder.
What are the HIPAA breach notification deadlines?
- Individuals. Written notice by first-class mail, or email if the patient agreed, without unreasonable delay and no later than 60 days after discovery. It must describe what happened, what information was involved, steps patients should take, what you are doing in response and how to contact you.
- Substitute notice. If contact information is out of date for 10 or more people, post a notice on your website home page for 90 days or use major print or broadcast media, with a toll-free number active for at least 90 days.
- Media. For breaches affecting more than 500 residents of a state or jurisdiction, notify prominent media outlets serving that area within the same 60 days.
- HHS. For 500 or more people, report through the HHS breach portal within 60 days. For fewer than 500, keep a log and report no later than 60 days after the end of the calendar year in which the breaches were discovered.
- Business associates. A business associate must notify the covered entity without unreasonable delay and within 60 days of discovery, with the identity of affected individuals where possible.
Late notice is a finding on its own. In the Lehigh Valley Health Network settlement announced October 29, 2026, OCR cited late notification to individuals and HHS along with the absence of an accurate and thorough risk analysis.
How do state laws and other rules change the response?
HIPAA sets a federal floor. State breach notification laws may require notice to a state attorney general, shorter deadlines, credit monitoring offers or specific content, and they apply based on where the affected patients live, not where the practice is located. Practices with patients in several states should have counsel confirm every applicable law before notices go out.
Substance use disorder programs covered by 42 CFR Part 2 now have breach notification duties aligned with HIPAA under the 2024 final rule, which took effect for compliance on February 16, 2026. Cyber insurance policies, payer contracts and business associate agreements may add their own notice duties and deadlines as well.
What legal and financial risks follow a poor breach response?
OCR investigates breaches affecting 500 or more people, and a poor response often turns a single incident into a broad review of the practice's Security Rule program. OCR's resolution agreements commonly pair a payment with a corrective action plan monitored for two or three years. State attorneys general can bring their own actions, and patients may sue under state law.
The operational costs are often larger than any penalty: downtime and lost visits, forensic investigation, legal counsel, notification mailings, call center support, credit monitoring and the work of rebuilding systems.
How should practices recover and prevent the next breach?
- Restore from clean backups after confirming the attacker's access is gone, and change all credentials that may have been exposed.
- Close the root cause. Phishing, missing MFA, an unpatched system and a compromised vendor account are the most common causes in OCR cases.
- Update the risk analysis to reflect what the incident revealed, and record changes in your risk management plan.
- Review business associates involved in the incident and confirm their contracts require prompt reporting.
- Run a lessons-learned review and update the incident response plan, training and downtime procedures.
Preparation shortens every step above. Practices that already have tested backups, encryption, current contact lists, a named breach response team and a relationship with counsel and a forensic firm can make faster, better-documented decisions. Our article on ransomware defense for healthcare organizations covers prevention in more depth.
How can NorthStar help with healthcare breach response?
NorthStar helps medical practices prepare for and respond to security incidents: incident response planning, containment and recovery, evidence preservation, backup and restoration, and the security improvements OCR expects afterward. See our incident response services, HIPAA compliance services and healthcare IT services. Legal decisions about notification belong with your counsel; we support them with the technical facts.
Start with our free security check, read our guide to HIPAA risk assessments, or browse more healthcare resources.
What else do medical practices ask about data breach response?
Does a lost laptop always require breach notification?
No. If the laptop was encrypted in line with HHS guidance and the key was not compromised, the information is considered secured and notification is generally not required. Document the incident and your reasoning.
Can we wait until the investigation is finished before notifying patients?
Only within limits. Notice must go out without unreasonable delay and no later than 60 days after discovery. A law enforcement official can request a delay in writing, or orally for up to 30 days, but an internal investigation alone does not extend the deadline.
Who notifies patients if our business associate had the breach?
The covered entity remains responsible for making sure patients are notified, but it can delegate the notices to the business associate by agreement. Decide this in the business associate agreement before an incident happens.
Where do we report a breach to HHS?
Through the HHS Office for Civil Rights breach portal. Breaches of 500 or more people are posted publicly on that portal.
Sources
- HHS: Breach Notification Rule
- 45 CFR Part 164, Subpart D: Notification in the Case of Breach of Unsecured PHI
- HHS: Submitting Notice of a Breach to the Secretary
- HHS: Fact Sheet on Ransomware and HIPAA
- HHS: OCR settles ransomware investigation of Lehigh Valley Health Network (October 29, 2026)
Industry Resources
Healthcare Incident Response
NorthStar helps medical practices plan for incidents, contain and recover from them, and document the response OCR expects.
Learn More →About the author

Ken Satkunam, CISM
President & Founder, NorthStar Technology Group
Ken has spent over 25 years in IT leadership, serving in roles from technical support to CIO for organizations as large as 23,000 employees. He founded NorthStar Technology Group in 2000 to help regulated organizations build secure, compliant, and operationally resilient technology environments. Ken holds the Certified Information Security Manager (CISM) credential from ISACA and is the co-author of the Amazon best-seller "Cyber Attack Prevention." He has been quoted in industry publications including eWeek and DM News, and NorthStar has been recognized on the Inc. 5000 list in both 2024 and 2025.