PIVTR-D
SSector

Healthcare organizations

First moves
  1. Check patient safety impact first: electronic health record (EHR), medication dispensing, infusion pumps, lab, imaging, telemetry.Safety Officer
  2. Start downtime procedures on affected units and record the time.Operations
  3. Activate the Hospital Incident Command System (HICS) and form unified command with the cyber Incident Commander.Incident Commander
  4. Tell the Privacy Officer as soon as electronic protected health information (ePHI), Part 2 records or ransomware is suspected.Legal advisor
  5. Confirm with the Privacy Officer which rows apply; record in T1 who decided each clock started.Legal advisor
  6. Record the discovery date and who knew in T1; open T17 for the Department of Health and Human Services (HHS), media, state regulators and the Federal Trade Commission (FTC).Planning

Then work the page: Reporting obligations, Terms, Roles, What changes in each phase, Records, Who you work with.

This page is for responders at US HIPAA covered entities (providers that bill electronically, health plans and clearinghouses) and their business associates. Personal health record vendors and related entities outside HIPAA, including many health apps, follow the FTC rule. Substance use disorder programs under 42 CFR Part 2 follow the HIPAA breach rule, and state law adds clocks.

Patient safety comes first. A hospital runs downtime procedures, may divert ambulances, and manages the event under HICS. Ransomware that encrypts ePHI is presumed a breach, and the 60-day notice clock starts at discovery.

This page adds to the phase playbooks for scope, contain, eradicate and recover. Incident Command seats for this sector are on Command by incident type.

This sector page is an addition to the book. Primary sources checked: 45 CFR Part 164 Subpart C, Subpart D and 164.530; 45 CFR 160.103; HHS OCR breach notification pages; 16 CFR Part 318; 42 CFR 2.16; 42 CFR 482.15 and 489.24; 21 CFR 803.30; FDA medical device cybersecurity pages. Checked October 2026.

Reporting obligations

Counsel and the Privacy Officer confirm which rows apply. Record in T1 who decided that each clock started, and when. The notification deadlines table lists other regimes.

ObligationWho reports to whomClockStarts whenWhat the report contains
45 CFR 164.404, notice to individualsCovered entity to each affected individualWithout unreasonable delay, and no later than 60 calendar daysDiscovery: the first day any workforce member or agent, other than the wrongdoer, knew of the breach or would have known with reasonable diligenceIn plain language: what happened, with breach and discovery dates; the protected health information (PHI) involved; steps to take; what the entity is doing; a toll-free number, email, website or postal address. By first-class mail, or email if agreed. If 10 or more addresses fail, post on the website or in major media, with a toll-free number, for 90 days
164.406, notice to mediaCovered entity to prominent media outlets serving the state or jurisdictionSame as individualsDiscovery of a breach involving more than 500 residents of one state or jurisdictionThe same content as the individual notice
164.408, notice to HHS, 500 or moreCovered entity to HHS through the breach portal of the HHS Office for Civil Rights (OCR)At the same time as the individual noticeDiscovery of a breach affecting 500 or more individualsThe portal form. OCR posts and investigates these breaches
164.408, notice to HHS, fewer than 500Covered entity to HHS through the portalNo later than 60 days after the end of the calendar year of discoveryDiscovery. Keep a logOne portal report per breach
164.410, business associate noticeBusiness associate to the covered entity; subcontractor to business associateWithout unreasonable delay, and no later than 60 calendar days. A business associate agreement (BAA) may set lessIts own discovery, counting its workforce and agents. If it is the covered entity's agent under the federal common law of agency, the covered entity has knowledge the same day (164.404(a)(2)) and both clocks start together. For an independent contractor, the covered entity's clock starts when it is notifiedEach affected individual it can identify, and other available information the covered entity needs, sent as it arrives
164.314(a)(2)(i)(C), security incidentsBusiness associate to the covered entityAs the BAA setsAwareness of any security incidentAs the BAA sets
42 CFR 2.16(b), Part 2 recordsPart 2 program to individuals, HHS and the mediaThe HIPAA clocks aboveDiscovery of a breach of unsecured Part 2 recordsThe HIPAA content. Compliance with the 2024 final rule was required by February 16, 2026
16 CFR Part 318, FTC Health Breach Notification RulePersonal health record vendor or related entity outside HIPAA to individuals, the FTC and, for 500 or more residents of one state, the media. Its service providers tell the vendorWithout unreasonable delay, and within 60 calendar days. The FTC at the same time as individuals for 500 or more, or within 60 days after year end for fewerDiscovery of a breach of security, which includes an unauthorized disclosure such as sharing with an advertiserThe rule's content; the FTC's online form
California Health and Safety Code 1280.15(b)Licensed clinic, health facility, home health agency or hospice to the Department of Public Health and each patientNo later than 15 business daysDetection of unlawful or unauthorized access to, or use or disclosure of, a patient's medical informationAs the statute and the California Department of Public Health (CDPH) require. Patient notice goes to the last known address, or by email only if the patient agreed in writing
21 CFR 803.30, medical device reportingUser facility, such as a hospital, to the Food and Drug Administration (FDA), and to the manufacturer if known, for a death; to the manufacturer (or FDA if unknown) for a serious injury10 work daysBecoming aware of information, from any source, that reasonably suggests a device has or may have caused or contributed to a death or serious injuryThe medical device report (MDR) content in 21 CFR 803 Subpart C

Under 164.412 a law enforcement official's written statement delays notice for the period it names. An oral statement, documented with the official's name, delays it no more than 30 days unless a written one follows. Under 164.414 the entity must prove each notice went out on time, or that the event was no breach.

Encryption is the safe harbor. HHS treats PHI as secured when encrypted to NIST SP 800-111 at rest or SP 800-52, 800-77 or 800-113 in transit, with the key unbreached and kept apart from the data. PHI on media destroyed to SP 800-88 is also secured.

OCR's ransomware fact sheet (July 11, 2016) calls ransomware a security incident. It calls the encryption of ePHI by ransomware a breach, presumed until a four-factor assessment shows a low probability of compromise.

The Security Rule changes proposed January 6, 2025 (90 FR 898) would require restoring certain systems and data within 72 hours. They would also require business associates to tell covered entities within 24 hours of activating a contingency plan. They are still proposed in October 2026; the Fall 2025 Unified Agenda, released in July 2026, lists the rule as a long-term action with final action projected for July 2027.

The Cybersecurity and Infrastructure Security Agency (CISA) sent its final rule under the Cyber Incident Reporting for Critical Infrastructure Act (CIRCIA) to the Office of Management and Budget for review on October 1, 2026. CIRCIA reporting starts only after the final rule takes effect.

Sources: 45 CFR 164.304, 164.308, 164.314, 164.402 to 164.414; on agent and independent contractor discovery, the HHS preamble to the interim final breach rule, 74 FR 42740 at 42754, August 24, 2009; HHS guidance to render unsecured PHI unusable, unreadable, or indecipherable; OCR Fact Sheet: Ransomware and HIPAA, July 11, 2016; OCR breach portal; HHS Part 2 final rule fact sheet (February 8, 2024); FTC, Complying with FTC's Health Breach Notification Rule, and the amended rule published May 30, 2024; California Health and Safety Code 1280.15 as amended by AB 1755 (Stats. 2014, ch. 412), matching the current code text; Security Rule NPRM and HHS NPRM fact sheet; Unified Agenda, RIN 0945-AA22, as reported by Alston & Bird, July 10, 2026; Covington, CISA Submits Final CIRCIA Rule for OMB Review, October 8, 2026.

Terms

TermMeaningPIVTR-D equivalent
PHIProtected health information: individually identifiable health information kept or sent in any form, excluding employment and education recordsRestricted data scenario; regulated data in T2
ePHIPHI sent or kept in electronic media. The Security Rule covers ePHIRestricted data
Covered entityA health plan, a clearinghouse, or a provider that sends health information electronically in a HIPAA standard transactionnone
Business associateAnyone that creates, receives, maintains or sends PHI for a covered entity, including subcontractorsVendor; see the supply chain scenario
BAABusiness associate agreement. Sets the business associate's duty to report security incidents and breachesLegal basis in T19
Security incidentAttempted or successful unauthorized access, use, disclosure, change or destruction of information, or interference with system operations (164.304)Incident
BreachAcquisition, access, use or disclosure of PHI the Privacy Rule does not permit, which compromises its security or privacy. Presumed unless the four-factor assessment shows a low probability of compromise. Three narrow exceptions applyT16 notices
Four-factor assessmentThe 164.402 test: the PHI involved, who received it, whether it was acquired or viewed, and how far the risk was mitigatedRecorded with T17
Unsecured PHIPHI not encrypted or destroyed to the HHS guidancenone
DiscoveryWhen the 60-day clocks start; see the first tableA T1 KEY TIMES entry beside "detected"
LDSLimited data set: PHI without direct identifiers, shared under a data use agreement. Its breach still needs the four-factor assessmentnone
Minimum necessaryUse or disclose the least PHI needed. It limits what responders copy into tickets and chatEvidence handling
HIMHealth information management, keeper of the legal medical recordnone
EHR, EMRElectronic health record; electronic medical record. The main clinical systemCritical system in the containment triggers
Downtime proceduresPaper and manual processes for orders, charting, medication, lab and imaging while systems are downThe workaround in Recover
DiversionA hospital's request that emergency medical services (EMS) take ambulance patients elsewhere. A patient brought onto hospital property anyway has come to the emergency department under the Emergency Medical Treatment and Labor Act (EMTALA, 42 CFR 489.24)none
HICSHospital Incident Command System, the hospital form of the Incident Command System (fifth edition guidebook, May 2014, California EMS Authority)Incident Command organization
CMIO, CNIOChief medical and chief nursing information officers, the clinical leaders for clinical systemsnone
Clinical engineering, biomedMaintains medical devices and the device inventorynone
MDS2Manufacturer Disclosure Statement for Medical Device Security, a standard form on a device's security featuresnone
SBOMSoftware bill of materials. Section 524B of the Federal Food, Drug, and Cosmetic (FD&C) Act requires the manufacturer to give FDA one for each internet-capable cyber device in submissions filed on or after March 29, 2023. Ask the manufacturer for a copynone
405(d)The HHS program under section 405(d) of the Cybersecurity Act of 2015none
HICPHealth Industry Cybersecurity Practices, the 405(d) guide. The newest edition this page confirmed is from April 2023Preparation
HPH CPGsVoluntary HHS cybersecurity performance goals of January 24, 2024: 10 essential, 10 enhancedPreparation
Recognized security practicesNIST standards and 405(d) approaches. Under Public Law 116-321 (2021), OCR weighs them when in place for the prior 12 monthsnone
OCRHHS Office for Civil Rights, the HIPAA enforcerRegulator in T17
Breach portal ("wall of shame")OCR's public list of breaches of 500 or more, and the filing sitenone
Part 242 CFR Part 2, substance use disorder patient recordsRestricted data
HITECHThe 2009 act that created HIPAA breach notificationnone
HITRUSTA private certifiable security framework. It adds no reporting dutynone

Roles

Sector roleWhat they do in an incidentPIVTR-D or Incident Command seat
Privacy Officer (164.530(a))Runs the breach assessment and noticesTechnical Specialist beside the Legal advisor
Security Official (164.308(a)(2))Owns incident procedures and Security Rule recordsCISO
General counselPrivilege, law enforcement contact, notice decisionsLegal advisor
Compliance officerTracks clocks, the breach log and OCR lettersPlanning, beside the Legal advisor
Hospital incident commander (HICS)Commands patient care, diversion and staffingIncident Commander in unified command with the cyber Incident Commander
CMIO, CNIODecide when clinical systems go down and return, and whether data is fit for careOperations, clinical systems branch; approve T3 and T7 for clinical systems
Nursing supervisor (house supervisor)Senior on-site authority nights and weekends. Starts downtime and can command until the administrator on call arrivesInitial Incident Commander, then Operations
Clinical engineeringFinds and isolates affected devices with clinical approvalOperations, medical device group
Pharmacy, laboratory and imaging directorsRun department downtime and set service limitsOperations
Emergency managerRuns HICS forms and the incident action planPlanning
Revenue cycle leader, CFOClaims workarounds and payment reliefFinance/Admin

The Incident Command site uses NIMS ICS. Hospitals run HICS, which keeps the same Command and General Staff. Map the HICS seats this way.

HICS positionIncident Command seat
Incident CommanderIncident Commander
Public Information Officer, Liaison Officer, Safety OfficerPublic Information Officer, Liaison, Safety Officer
Medical/Technical Specialist: Legal Affairs, Risk Management, Medical StaffLegal advisor for Legal Affairs; Technical Specialists for the others
Operations Section Chief, with the Medical Care, Infrastructure, Security, HazMat, Business Continuity and Patient Family Assistance branchesOperations
Business Continuity Branch, IT Systems and Applications UnitOperations, IT restoration branch
Planning, Logistics (with the IT/IS Equipment and Communications units) and Finance/Administration Section ChiefsPlanning, Logistics, Finance/Admin
No standard HICS seat. The Health Sector Coordinating Council (HSCC) Operational Continuity-Cyber Incident (OCCI) checklist adds an Intelligence (IS/IT) Section ChiefIntelligence/Investigations

Sources: EMS Authority HICS FAQ and IT Systems and Applications Unit Leader job action sheet; HICS 2014 job action sheets for the Operations and Logistics sections; HICS organization chart, reproduced in the HICS appendixes; HSCC Cybersecurity Working Group, Operational Continuity-Cyber Incident (OCCI) checklist, version 1.1, May 2022.

What changes in each phase

Preparation

#ItemOwner
1Size the downtime plan for clinical systems offline four weeks or longerOperations
2Stock downtime kits on every unitOperations
3Agree cyber outage diversion criteria with the emergency department and the local EMS agency, naming who declares diversionIncident Commander
4Run a cyber attack as one of the two exercises a year that 42 CFR 482.15(d) requiresPlanning
5Keep a BAA register with each business associate's incident contact, reporting deadline and agent statusLegal advisor
6Map clearinghouse and e-prescribing dependencies, with a second clearinghouse or a manual billing pathFinance/Admin
7Keep a device inventory with location, MDS2, SBOM and the manufacturer's security contactOperations
8Record encryption status for laptops, removable media and backupsCISO
9Document recognized security practices, mapped to HICP or the NIST Cybersecurity FrameworkCISO
10Join Health-ISACLiaison
11Test OCR breach portal and CISA reporting access with named staffLiaison

Identification and verification

#ItemOwner
1Check patient safety impact first: EHR, medication dispensing, infusion pumps, lab, imaging, telemetrySafety Officer
2Start downtime procedures on affected units and record the timeOperations
3Activate HICS and form unified command with the cyber Incident CommanderIncident Commander
4Tell the Privacy Officer as soon as ePHI, Part 2 records or ransomware is suspectedLegal advisor
5Record the discovery date and who knew in T1Planning
6Check business associate involvement: whose system, whose data, whose clockIntelligence/Investigations
7Record the encryption state of affected systems at the time of the attackIntelligence/Investigations
8List affected devices and contact their manufacturersOperations

Response loop

#ItemOwner
1Get CMIO or CNIO approval in T3 before containing a clinical system or deviceIncident Commander
2Record diversion and elective case decisionsPlanning
3Tell EMS and the state health department of diversion as state rules requireLiaison
4Gather exfiltration evidence for the four-factor assessmentIntelligence/Investigations
5Write the four-factor assessment, or record that the breach is presumed, with counsel's decisionLegal advisor
6Document each law enforcement delay request with the official's name and the end dateLiaison
7Map breached records to individuals, states and Part 2 statusPlanning
8Send individual, media and HHS notices by day 60 at the latest, tracked in T17Legal advisor
9Confirm in writing any delegation of notice to a business associateLegal advisor
10Report device deaths and serious injuries under 21 CFR 803 within 10 work daysOperations
11Have clinical owners check restored orders, allergies and medication records before useOperations
12Enter downtime paper records back into the EHROperations
13Request payer and Medicare contractor relief when claims stopFinance/Admin

Debrief

#ItemOwner
1Update the Security Rule risk analysis with what the incident showedCISO
2Revise the downtime plan, diversion criteria and emergency planPlanning
3File breach records for six yearsLegal advisor
4Add breaches under 500 to the year's log for HHSLegal advisor
5Revise BAAs where reporting was late or unclearLegal advisor
6Review patient safety events from downtimeSafety Officer

Sources: The Joint Commission, Sentinel Event Alert 67, August 15, 2023, on planning for critical technology offline four weeks or longer; 42 CFR 482.15 (all-hazards emergency plan, documentation system that keeps records available, two exercises a year); 42 CFR 489.24(b); HSCC OCCI checklist; 45 CFR 164.530(j); OCR request for information on Public Law 116-321, April 6, 2022.

Records

RecordWhat changes
T1 Incident recordAdd discovery date and who knew, ePHI or Part 2 involvement, encryption state, business associates, downtime start and diversion status
T2 Triage briefAdd patient safety impact and the days left on the 60-day clock
T13 Law enforcement and insurer contactRecord any 164.412 delay: written or oral, the official's name, and the end date
T16 Notice to affected individuals or customersAdd the 164.404(c) elements: breach and discovery dates, and a toll-free number, email, website or postal address. Prepare substitute notice
T17 Regulator notification worksheetOne worksheet each for HHS, media by state, each state regulator or attorney general, and the FTC. Attach the four-factor assessment
T19 Vendor evidence and preservation requestCite the BAA. Ask for the affected individuals list and the business associate's incident report
HICS forms and downtime recordsJoin the incident record. Paper charts go to HIM

Keep breach and Security Rule documentation six years from creation or last effective date, whichever is later (164.530(j), 164.316(b)(2)).

Who you work with

BodyWhat they do for youHow to reach them
HHS Office for Civil RightsBreach reports and HIPAA enforcementThe breach portal at ocrportal.hhs.gov
HHS Administration for Strategic Preparedness and Response (ASPR)Coordinates the work of HHS as sector risk management agency. Runs the 405(d) program, which publishes HICP. HHS publishes the CPGs on its Cyber Gatewayaspr.gov, 405d.hhs.gov and hhscyber.hhs.gov
HHS Health Sector Cybersecurity Coordination Center (HC3)Published health sector threat briefs. Its hhs.gov pages redirect to tech.hhs.gov in October 2026, and this page could not confirm that it still publishesUse Health-ISAC and CISA for current alerts
Health-ISACMember threat sharing and peer contactThrough membership at health-isac.org
CISAIncident reports and technical helpcisa.gov/report
FBIInvestigation; may request notice delayThe local field office, or the FBI's Internet Crime Complaint Center (IC3)
FDAReceives device reports, and works with manufacturers on vulnerabilitiesForm FDA 3500A for mandatory reports; MedWatch Form FDA 3500 for voluntary reports, such as malfunctions
Device manufacturersUnder section 524B, a plan for postmarket vulnerabilities, updates and patches, and an SBOM given to FDA, for cyber devices submitted on or after March 29, 2023The security contact in the device inventory
Centers for Medicare & Medicaid Services (CMS) and Medicare Administrative Contractors (MACs)Payment relief when claims stop, as after Change HealthcareThe provider's MAC
State health department and local EMS agencyLicensing, diversion rules, patient movement, state health breach reportsThe emergency plan's communication plan
State attorneys generalEnforce state breach laws and can bring HIPAA actionsEach state's breach reporting page

Change Healthcare, a clearinghouse and business associate, is the reference case. Its attack was detected February 21, 2024, and it told OCR on July 31, 2025 that about 192.7 million individuals were affected.

OCR said covered entities stay responsible for notification, may delegate it, and owe nothing further when the business associate notifies correctly. UnitedHealth Group offered to notify on its customers' behalf.

On March 9, 2024, CMS offered accelerated and advance payments through the MACs. In May 2024 ransomware took Ascension's EHR offline and some of its hospitals diverted ambulances.

Sources: OCR Change Healthcare Cybersecurity Incident FAQs, reviewed August 13, 2025; CMS fact sheet, CHOPD accelerated and advance payments, March 9, 2024; UnitedHealth Group Form 10-Q, first quarter 2024 (detection date); Cybersecurity Dive, Ascension cyberattack, December 2024; ASPR, Healthcare and Public Health Cybersecurity and RISC 2.0 cyber module release, March 2026 (HHS as sector risk management agency); 405(d) program; HHS Cybersecurity Performance Goals; AHA, HHS releases updated HICP guide, April 17, 2023; AHA on the HHS CPGs, January 24, 2024; FDA, Cybersecurity in Medical Devices FAQs (section 524B, effective March 29, 2023; content current as of June 26, 2025); FDA Cybersecurity, updated July 6, 2026; 21 U.S.C. 360n-2 (section 524B); FDA, Medical Device Reporting (MDR).

Watch out
  • The 60 days are a ceiling. Notice is due without unreasonable delay, and discovery counts what any workforce member or agent knew or should have known.
  • Ransomware on a system that stores ePHI is presumed a breach. Full disk encryption gives no safe harbor for a system that was running and unlocked when attacked.
  • A covered entity stays responsible for notice when its business associate is breached. Get any delegation in writing.
  • Taking the EHR, pumps or imaging offline is a clinical decision. Clinical leaders approve it and downtime starts first, unless active destruction forces an immediate cut.
  • Runbooks that cite the 2025 Security Rule proposal's 24-hour and 72-hour requirements as law are wrong. The rule is still proposed.
Adapts material from Dynamic Incident Response: A Framework for Security Teams by Joshua Wright, © 2026 The Escal Institute of Advanced Technologies, Inc. d/b/a SANS Institute, licensed under CC BY 4.0. Figures reproduced under that license. Changes were made. Not published by, endorsed by, or affiliated with the SANS Institute.