164.308(a)(7)(i) Contingency plan
What the standard requires
Standard: Contingency plan. Establish (and implement as needed) policies and procedures for responding to an emergency or other occurrence (for example, fire, vandalism, system failure, and natural disaster) that damages systems that contain electronic protected health information.
Quoted verbatim from 45 CFR Part 164 (eCFR, as in force 2026-01-01), which is in the public domain.
Maps to 2 controls in 2 other frameworks
| Framework | Control |
|---|---|
| HITRUST CSF v11 | 12.a.01 Business continuity program integrates information security requirements |
| NIST Cybersecurity Framework (1.1, legacy) | PR.IP-9 Response and recovery plans in place |
Mappings are CMDash’s own, seeded with the product and shown on both frameworks they connect. In the product they mean evidence you attach here also counts against the controls listed above.
Integrations that carry evidence for this family
These connectors produce data relevant to HIPAA Security Rule’s Administrative Safeguards family, which is the granularity CMDash publishes — there is no pre-built per-control mapping, and claiming one would be inventing it. You decide which evidence answers which control.
In CMDash this control is a row with an owner, a status, uploaded evidence kept with its full history, and an export an assessor can read.