164.308(a)(7)(i) Contingency Plan (Standard)
Establish policies for responding to emergencies that damage ePHI systems. NIST recommends contingency planning per SP 800-34 with business impact analysis driving recovery priorities.
Source: HIPAA Security Rule, 164.308(a)(7)(i). The statement above is our statement of the clause, read from the published text and cited so you can check it against the official text, not the instrument verbatim. Open HIPAA Security Rule in the compliance library.
Applies to covered entities and business associates. An addressable specification can be met by a documented, reasonable alternative.
These are the artefacts auditors commonly ask for on this requirement, our guidance rather than text from the standard. Your assessor decides what is sufficient in your context, and asks for samples across the period when a report covers one.
system holds itEvidence a system already holds
none for this control
periodic reviewEvidence produced at each review
- Business impact analysis · Document repository
governing documentDocuments that govern the control
- Contingency plan · Policy repository / GRC workspace
- Recovery time and point objectives · Policy repository / GRC workspace
- Plan distribution list · Policy repository / GRC workspace
First move
Common gaps auditors find
- BIA not performed
- RTO and RPO undefined
- Plan stored only on impacted systems
Do this for your whole sheet
Paste the rows you run your controls from and get this mapping for every control at once, with the periodic-review ones flagged and a first move per row. No account for the first run.
Build my evidence sheet164.308(a)(6)(ii) Response and Reporting (Required) · 164.308(a)(7)(ii)(A) Data Backup Plan (Required)