Emergency Mode Operation Plan: Emergency mode operation when systems are down

45 CFR 164.308(a)(7)(ii)(C) sets the expectation for emergency mode operation plan. The text is brief; the evidence it implies is not, and the difference between the two is where most remediation time goes.

What the rule says

Establish (and implement as needed) procedures to enable continuation of critical business processes for protection of the security of electronic protected health information while operating in emergency mode.

That is the operative language of 45 CFR 164.308(a)(7)(ii)(C). Read it closely: it describes an outcome to achieve, not a product to buy, which is why two practices of the same size can satisfy it in different ways and both be right.

This is a required implementation specification. 45 CFR 164.306(d)(2) gives no documented-alternative route: you implement it, or you have a finding.

What this looks like in practice

In an assessment, 45 CFR 164.308(a)(7)(ii)(C) is not one question. It resolves into several, and each one is really asking for a different artifact:

• Mutual aid or reciprocal arrangements with peers or service providers to support emergency access to critical systems
• Maintain a business continuity plan to sustain critical operations during an emergency
• Maintain documented manual workaround procedures for critical workflows when systems are unavailable

Ownership usually sits with the security official, though the evidence is often produced by someone else, which is where the trail breaks. A control that works but has no owner tends to stop working the month the person who quietly maintained it changes roles.

Who this applies to

Every covered entity and every business associate, at any size. 45 CFR 164.306(b) allows flexibility of approach, so a two-provider practice and a hospital system may implement this differently and both comply. What flexibility does not allow is skipping the decision: the smaller the organization, the more the written reasoning carries the weight, because there is no scale of operation to make the control self-evident.

Building it, in order

The sequence below is the order that produces evidence as a by-product rather than as a separate documentation exercise:

1. Assess the organization's ability to sustain operations in emergency mode and identify gaps that would require external support.
2. Where gaps exist, establish mutual aid agreements with peer organizations covering temporary use of systems, emergency access to records, or use of physical facilities.
3. Establish documented arrangements with cloud or managed service providers for emergency provisioning of computing environments.
4. Identify which arrangements depend on pre-positioned configurations, credentials, or data replication to be effective within recovery time targets.
5. Exercise these arrangements at least once every two years and retain the agreements and exercise records for the six-year period 45 CFR 164.316(b)(2)(i) requires.
6. Upload the mutual aid agreements and most recent exercise records.

What else this satisfies

The same evidence answers more than one framework. The questions behind 45 CFR 164.308(a)(7)(ii)(C) also map to NIST CSF RC.RP-01, RC.RP-04; ISO 27001 A.5.30; SOC 2 A1.2; NIST 800-53 CP-2, CP-7; HITRUST 12.a, 12.c; PCI DSS 12.10. That matters for scoping: if you are working toward SOC 2 or an ISO certification alongside HIPAA, this control is one piece of work and several answers, provided the artifact is written once and referenced rather than rewritten per framework.

Evidence an assessor asks for

For this requirement the artifact types that satisfy it are agreement, plan, and procedure. The distinction matters more than it looks: a policy states what you intend to do, a procedure states how, and a record proves it happened on a date. Auditors ask for all three, and a practice that has written the first two often has nothing for the third.

Date every artifact and keep the superseded versions. 45 CFR 164.316(b)(2)(i) requires documentation be retained for six years from the date of its creation or the date when it last was in effect, whichever is later, so a policy you replaced two years ago is still part of the record.

Where this usually goes wrong

This requirement carries critical weight in an assessment, which means a gap here tends to surface as a high finding rather than an observation. The usual cause is drift: the control was implemented once, the environment changed, and nothing re-checked it. A dated review on a fixed cadence is cheaper than the remediation.

What to do about it

• Produce the artifact, not the intention. For 45 CFR 164.308(a)(7)(ii)(C) that means the executed agreement, with the signature date on it, a written plan naming who does what, and evidence it was tested, and a step-by-step procedure someone unfamiliar with the task could follow. If the only evidence is that someone knows how this works, you have a practice and not a record.
• Put a name on it. Your security official should be recorded as the owner. A control with no owner stops working the month the person who quietly maintained it changes roles, and nobody notices.
• Review it on a fixed date, not when you remember. This requirement carries critical weight in an assessment, so a gap here surfaces as a high finding rather than an observation. Put the review on the calendar with an owner, and keep the dated output of each one.
• There is no documented-alternative route here. This one is required, so a risk-based decision not to do it is not available. If you cannot implement it as written, that is a finding to remediate rather than a position to document.

Work backward from the evidence. Decide what artifact would prove emergency mode operation plan to someone who does not already trust you, then build the control that produces it. Programs built in that order tend to stay current, because the artifact goes stale visibly.

References

• 45 CFR 164.308(a)(7)(ii)(C), in 45 CFR 164.308 on eCFR. Quoted text verified against the eCFR snapshot of 2026-01-01.
• The Required and Addressable designations are defined at 45 CFR 164.306(d).
• Crosswalk references in this post are our own mapping and are not verified against the published text of those standards.
• This post describes what a requirement asks for and what evidence documents it. It is not legal advice, and your counsel owns the conclusion. State law may impose stricter obligations (45 CFR 160.203).