The moment your practice discovers a potential data breach, a clock starts.
Not a metaphorical clock — a real, regulatory one. Under the HIPAA Breach Notification Rule, covered entities must notify affected individuals “without unreasonable delay” and no later than 60 days following discovery of a breach. For breaches affecting more than 500 individuals, HHS must be notified simultaneously — and the incident becomes publicly listed on OCR’s breach portal.
But the 60-day window is not where practices lose ground. They lose ground in the first 72 hours.
The decisions made in the first three days determine whether a breach becomes a contained, documented, manageable incident — or an uncontrolled crisis that compounds at every stage. Delayed containment allows attackers continued access. Disorganized response destroys forensic evidence. Missed notification deadlines create independent HIPAA violations on top of the breach itself.
Does your practice know exactly what to do on Day 1?
If the honest answer is no — or not clearly enough — this is the framework your team needs before a breach happens, not after.
Before the Clock Starts: Why Preparation Determines Everything
The practices that handle breaches most effectively have one thing in common: they prepared before the breach occurred.
Incident response under pressure is not the same as incident response with a plan. When systems are down, staff are alarmed, and patients are calling — the capacity to think clearly about regulatory requirements, notification timelines, and forensic preservation collapses without documented procedures to follow.
The CISA Healthcare Cybersecurity guidance and the HHS Office for Civil Rights both emphasize that preparation — including documented response procedures and staff training — is itself a HIPAA compliance requirement under the Security Rule’s contingency planning standards.
What that preparation looks like in practice is a documented breach response plan that assigns specific roles, defines clear escalation paths, and walks your team through the exact steps the following framework covers.
Hour 0–4: Contain and Preserve
The first priority when a breach is detected is not notification. It is containment — stopping the unauthorized access from continuing — and preservation — protecting the forensic evidence that will be required for your investigation.
Activate Your Incident Response Team
The moment a potential breach is detected, your designated incident response lead must be notified immediately. This person — whether an internal IT lead, a compliance officer, or your managed IT provider — is responsible for coordinating the response from this point forward.
Do not attempt to handle a suspected breach through informal channels or individual judgment calls. Activate your documented response procedure and assign roles immediately.
Who should be notified within the first hour:
- Incident response lead or IT security contact
- Practice owner or managing physician
- Legal counsel (or healthcare compliance attorney)
- Cyber liability insurance carrier
Isolate Affected Systems
Once a breach is detected, affected systems should be isolated — not shut down.
This is a critical distinction. Powering off compromised systems destroys volatile forensic evidence, including memory data that may identify how the attacker gained access, what they accessed, and how long they were present. Isolate affected systems from the network to prevent further unauthorized access, but preserve them for forensic examination.
Immediate isolation steps:
- Disconnect affected devices from the network without powering them off
- Preserve system logs, access records, and audit trails
- Document the exact time of detection and every action taken from that moment forward
- Do not delete files, reconfigure systems, or attempt self-remediation
Assess the Initial Scope
While systems are being isolated, begin a preliminary assessment of what may have been affected. This initial scope review is not the full investigation — but it informs every decision that follows.
Initial scope questions:
- Which systems, applications, or data repositories were potentially accessed?
- What types of patient information are stored in those systems?
- Approximately how many patient records could be affected?
- Is the unauthorized access ongoing or has it been stopped?
Hour 4–24: Investigate and Assess
Once affected systems are isolated and the incident response team is activated, the focus shifts to a structured investigation of what actually occurred.
Engage Professional Forensic Support
Unless your internal team has specific healthcare cybersecurity forensic expertise, this is the stage at which external forensic support should be engaged. A qualified forensic investigator will:
- Analyze affected systems and logs to determine the attack vector
- Establish a timeline of unauthorized access
- Identify specifically what data was accessed, copied, or exfiltrated
- Preserve evidence in a forensically sound manner that will hold up in regulatory review
OCR investigations scrutinize the quality of a practice’s forensic response. A thorough, professionally conducted investigation is evidence of the reasonable efforts HIPAA requires — and is the foundation of every subsequent notification and regulatory communication.
Conduct a Formal Breach Risk Assessment
Not every security incident constitutes a reportable breach under HIPAA. The HHS Breach Notification Rule requires covered entities to conduct a four-factor risk assessment to determine whether impermissible use or disclosure poses a significant risk of financial, reputational, or other harm to affected individuals.
The four factors are:
- The nature and extent of the PHI involved, including the types of identifiers and the likelihood of re-identification
- Who accessed or used the information, or to whom it was disclosed
- Whether the PHI was actually acquired or viewed
- The extent to which the risk has been mitigated
This assessment must be documented. If the risk assessment concludes that a significant risk of harm exists, the incident is a reportable breach. If the assessment concludes the risk is low, the practice may qualify for an exception — but the documentation supporting that conclusion must be thorough and defensible.
Do not skip this assessment. OCR has consistently found that practices which fail to document a risk assessment following a security incident have violated the Breach Notification Rule — regardless of the actual risk level.
Hour 24–72: Notify and Document
Once the breach risk assessment confirms a reportable breach, notification obligations activate. The next 48 hours are defined by parallel tracks of notification, documentation, and regulatory communication.
Notify Affected Patients
Individual notification to affected patients is required without unreasonable delay and no later than 60 days after discovery. While the 60-day window gives your practice time to complete a thorough investigation before notifying, the clock started at detection — not at the conclusion of your investigation.
Individual notification must include:
- A brief description of what happened
- The types of PHI involved
- Steps individuals should take to protect themselves
- What your practice is doing to investigate and mitigate the breach
- Contact information for individuals with questions
For breaches affecting 500 or more individuals in a single state, notification to prominent media outlets in that state is also required.
Report to HHS
For breaches affecting 500 or more individuals, HHS must be notified simultaneously with individual notification — within 60 days of discovery. This notification is submitted through the HHS OCR breach reporting portal and becomes publicly listed.
For breaches affecting fewer than 500 individuals, HHS notification may be submitted annually — but must be submitted no later than 60 days after the end of the calendar year in which the breach occurred. Practices that wait for the annual window and miss the deadline face independent HIPAA violations.
HHS notification requires:
- Name and contact information of the covered entity
- Type of breach (hacking, unauthorized access, loss, theft, etc.)
- Location of breached information (laptop, EHR, email, etc.)
- Types of PHI involved
- Number of individuals affected
- Description of what happened
- Steps taken to mitigate harm and prevent recurrence
Notify Your Cyber Insurance Carrier
Most cyber liability policies require prompt notification following a breach — often within 24–72 hours of discovery. Delayed notification to your insurance carrier can result in denial of coverage for breach response costs, including forensic investigation, legal fees, and notification expenses.
Review your policy’s notification requirements and contact your carrier within the first 24 hours.
Document Everything
From the moment of detection through the conclusion of your response, every action, decision, and communication must be documented. This documentation serves multiple purposes: it demonstrates reasonable efforts to OCR, supports your forensic investigation, provides the factual basis for patient notifications, and establishes your firm’s timeline if regulatory proceedings or litigation follow.
Documentation to maintain:
- Incident detection log with exact timestamps
- All actions taken during containment and investigation
- Risk assessment findings and supporting evidence
- Copies of all notifications sent and dates transmitted
- HHS notification submission confirmation
- Post-incident remediation steps and timeline
Does Your Practice Have a Plan for Day 1?
The practices that navigate breaches most effectively aren’t the ones that respond best under pressure. They’re the ones that prepared before the pressure arrived.
At AI Managed IT Services, we help medical practices across greater Los Angeles build documented, tested breach response plans — so that when a security incident occurs, your team knows exactly who to call, what to do, and how to meet every regulatory deadline without confusion or delay.
When you’re ready to go further, our team offers a Breach Readiness Assessment — a structured review of your current incident response capability that confirms your team knows exactly what to do on Day 1, identifies gaps in your current plan, and ensures your practice is prepared to meet every HIPAA notification obligation without delay.

