Coordinate hospice emergency plans across home and inpatient care

Frame this document as a source-led configuration and assurance check: Coordinate hospice emergency plans across home and inpatient care. Only the official source and traced locations below supply facts. Confirm applicability before acting.

Source fact:

The official 42 CFR 418.113 – Emergency preparedness from Centers for Medicare & Medicaid Services via eCFR supports the following bounded statements:

• Under 42 CFR 418, the rule requires that the plan do the following: address patient population, including, but not limited to, the type of services the hospice has the ability to provide in an emergency; and continuity of operations, including delegations of authority and succession plans. The research record locates this support at 42 CFR 418.113(a)(3), read with 42 CFR 418.113(a) (eCFR anchor p-418.113(a)(3)).
• Under 42 CFR 418, the rule requires that the hospice develop and maintain an emergency preparedness training and testing program that is based on the emergency plan set forth in paragraph (a) of this section, risk assessment at paragraph (a)(1) of this section, policies and procedures at paragraph (b) of this section, and the communication plan at paragraph (c) of this section. The research record locates this support at 42 CFR 418.113(d) (eCFR anchor p-418.113(d)).

Only the traced statements above are asserted as source facts. Apply the review to essential functions, upstream providers, recovery sequences, alternate work paths, and tested recovery objectives after confirming that the source and deployed context match.

What the source does not establish

Hospice-specific federal condition of participation; home, inpatient, contracted, patient, caregiver, state, and survey requirements must be reconciled. A correct source interpretation can still be inapplicable to a particular design. Confirm identity, DNS, communications, facilities, suppliers, and the people authorized to invoke recovery, ownership, and change authority instead of treating documented behavior as a deployment guarantee.

Applicability questions

• For source statement 1 at 42 CFR 418.113(a)(3), read with 42 CFR 418.113(a) (eCFR anchor p-418.113(a)(3)), which observable configuration, record, or test can confirm applicability here?
• For source statement 2 at 42 CFR 418.113(d) (eCFR anchor p-418.113(d)), which observable configuration, record, or test can confirm applicability here?
• Which deployed instance of essential functions, upstream providers, recovery sequences, alternate work paths, and tested recovery objectives will be compared with the source, and why that instance?
• How will the review distinguish a source mismatch from a failure in identity, DNS, communications, facilities, suppliers, and the people authorized to invoke recovery?
• Who approves the conclusion, exception, test window, and rollback threshold?

DSE recommendation:

DSE recommends using the cited source as the evidence anchor for this decision. Begin by recording scope and current state before deciding whether a change is warranted. Record the source location, examined part of essential functions, upstream providers, recovery sequences, alternate work paths, and tested recovery objectives, observed and expected states, owner, and reason for deviation.

If the review warrants change, use a bounded implementation with prerequisites, test population, monitoring, abort criteria, and a rehearsed reversal. Sequence checks for identity, DNS, communications, facilities, suppliers, and the people authorized to invoke recovery and sanitize protected material before retention.

Verification and evidence

A reviewer should be able to retrace the decision from 42 CFR 418.113(a)(3), read with 42 CFR 418.113(a) (eCFR anchor p-418.113(a)(3)); 42 CFR 418.113(d) (eCFR anchor p-418.113(d)) through business-impact records, dependency maps, exercise results, recovery timings, and open corrective actions. Record what was collected, where, when, by whom, and which system or role it represents.

Record the decision even when no change is made, including uncertainty and the next trigger. Use safe testing conditions for disruptive work, preserve rollback proof, and revisit the conclusion after relevant platform, dependency, vendor, or ownership changes.

Official references

• 42 CFR 418.113 – Emergency preparedness — Centers for Medicare & Medicaid Services via eCFR