Purpose of the Template
Recent healthcare incidents reveal a common pattern: LifeTouch Health, MPOWERHealth Holdings, and Geisinger each faced data breaches affecting thousands. The takeaway isn't about negligence but about the need for a coordinated response plan. Your team needs a written plan that aligns detection, scoping, and notification. This template serves as an incident response timeline and decision log for Business Associate compliance teams. It tracks every date relevant to the Breach Notification Rule and assigns an owner to each step.
Prerequisites
Before using this template, ensure you have:
- A current inventory of systems that store or transmit Electronic Protected Health Information (ePHI), including email.
- Executed Business Associate Agreements with notification deadlines for each Covered Entity.
- A pre-negotiated retainer or panel arrangement with a third-party digital forensics firm.
- Named contacts at each Covered Entity for security incident notices.
- Legal counsel identified for privilege decisions on forensic engagement.
If your Business Associate Agreements have shorter notification windows than the regulatory limit, those contract terms govern your timeline. Confirm these before customizing the template.
The Template
Copy this into your incident management system or a controlled shared document. Fill in one record per incident.
SECTION 1: INCIDENT HEADER
- Incident ID: [assign]
- Incident lead: [name, title]
- HIPAA Compliance Officer notified: [date/time]
- Legal counsel notified: [date/time]
- Status: [Open / Contained / Scoping / Notifying / Closed]
SECTION 2: DETECTION AND CONTAINMENT
- Date/time first indicator observed: [ ]
- Indicator type: [network disruption / suspicious email activity / alert / external report / other]
- Date/time discovered by a workforce member or agent: [ ]
- Containment actions taken and timestamps: [ ]
- Affected account(s) or system(s) secured: [Y/N, date]
SECTION 3: FORENSIC INVESTIGATION
- Forensic firm engaged: [name, date]
- Engagement directed through counsel: [Y/N]
- Evidence preserved (logs, images, mailbox exports): [Y/N, location]
- Unauthorized access confirmed: [Y/N/Undetermined, date]
- Possible exfiltration of files: [Y/N/Undetermined]
- Forensic summary received: [date]
SECTION 4: DATA REVIEW AND SCOPING
- Data sets reviewed: [mailbox / file shares / databases]
- Data elements present: [names, dates of birth, medical record numbers, diagnoses, treatment information, Social Security numbers, financial data, insurance information, other]
- Individuals affected, by Covered Entity: [count]
- Date PHI exposure confirmed: [ ]
- Low-probability-of-compromise assessment completed: [Y/N, date, reviewer]
SECTION 5: NOTIFICATION TRACKER
| Recipient | Obligation source | Deadline | Date sent | Owner |
|---|---|---|---|---|
| Covered Entity customer(s) | BAA / 45 CFR 164.410 | [ ] | [ ] | [ ] |
| Affected individuals (if delegated) | 45 CFR 164.404 | [ ] | [ ] | [ ] |
| Office for Civil Rights (OCR) (if delegated) | 45 CFR 164.408 | [ ] | [ ] | [ ] |
| State regulators (e.g., attorney general) | State law | [ ] | [ ] | [ ] |
| Media (if applicable) | 45 CFR 164.406 | [ ] | [ ] | [ ] |
SECTION 6: REMEDIATION AND LESSONS LEARNED
- Root cause: [ ]
- Security Rule safeguards updated: [list]
- Risk analysis updated: [date]
- Offer to individuals (e.g., identity theft protection): [Y/N, terms]
- Post-incident review held: [date]
Customizing the Template
Section 2: Detection Benchmark
Record the first indicator and discovery date separately. For HIPAA, a breach is considered discovered on the first day it is known, or should have been known, to the entity. Capturing both timestamps helps clarify when the clock started.
Section 3: Forensic Arrangement
Decide in advance whether forensic engagement runs through counsel and note it here. If you only handle mailbox-only incidents, you can trim the exfiltration fields, but keep them for network events.
Section 4: Scoping Timelines
The gap between identifying an incident and confirming PHI exposure can be long. Build interim checkpoints into your copy, like a "scoping status update" line for your incident lead to complete on a fixed schedule.
Section 5: Contractual Deadlines
Replace the deadline column with terms from each Business Associate Agreement. If you notify on behalf of Covered Entities, keep the individual, OCR, and media rows. If not, delete them and rely on the Covered Entity row. Add a row for each state relevant to the affected population.
Email Incidents
For incidents like Geisinger's, limited to one mailbox, add a field in Section 4 for "mailbox retention period reviewed" to determine how far back exposed messages reach.
Validation Steps
- Run a Tabletop Exercise
Walk a mock incident through all six sections with your HIPAA Compliance Officer, IT security lead, and legal counsel. Note any field nobody can fill. - Test the Contacts
Confirm each Covered Entity notice contact and your forensic firm's after-hours number work. - Check Your Dates
Have counsel verify that Section 5 deadlines match contract language. - Audit a Past Event
Retrofit a prior security incident into the template to see if any date was undocumented. - Review Annually
Tie the template review to your Security Rule risk analysis to keep it current.
A completed record is also evidence. If OCR asks how you detected, scoped, and notified, this document is your answer. HIPAA Breach Notification Rule





