# Keep PACE participants connected to care during community disruption > Use 42 CFR 460.84 - Emergency preparedness to review this narrow operational decision without extending the source beyond its stated scope. - Canonical URL: https://update.dsesecurity.com/updates/keep-pace-participants-connected-to-care-during-community-disruption/ - Publisher: Detection Systems & Engineering (DSE Security) - Author: DSE Security Editorial Team - Published: 2026-08-27T12:12:06+00:00 - Modified: 2026-08-27T13:06:59+00:00 - Last reviewed by DSE: 2026-08-26 - Resource type: Playbook - DSE priority: Advisory - Topics: Business Continuity, Cybersecurity - Reading time: 3 minutes ## What you need to know Use 42 CFR 460.84 - Emergency preparedness to review this narrow operational decision without extending the source beyond its stated scope. ## Potentially affected Teams, systems, services, or facilities within the stated scope of 42 CFR 460.84 - Emergency preparedness ## DSE recommendation Compare the observed state with the cited official source, document applicability and exceptions, and test any approved change with rollback safeguards. ## Article Keep this document to one review outcome: Keep PACE participants connected to care during community disruption. Only the official source and traced locations below supply facts. Confirm applicability before acting. ## Source fact: The official [42 CFR 460.84 – Emergency preparedness](https://www.ecfr.gov/current/title-42/section-460.84) from Centers for Medicare & Medicaid Services via eCFR supports the following bounded statements: - Under 42 CFR 460, the rule requires that the PACE organization do all of the following: initial training in emergency preparedness policies and procedures to all new and existing staff, individuals providing on-site services under arrangement, contractors, participants, and volunteers, consistent with their expected roles. The research record locates this support at 42 CFR 460.84(d)(1)(i), read with 42 CFR 460.84(d)(1) (eCFR anchor p-460.84(d)(1)(i)). - Under 42 CFR 460, the rule requires that the PACE organization 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 460.84(d) (eCFR anchor p-460.84(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 PACE-specific federal requirement; participant needs, transportation, center operations, contracted care, medication, state agreements, and current CMS guidance require local planning. 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 460.84(d)(1)(i), read with 42 CFR 460.84(d)(1) (eCFR anchor p-460.84(d)(1)(i)), which observable configuration, record, or test can confirm applicability here? - For source statement 2 at 42 CFR 460.84(d) (eCFR anchor p-460.84(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. An implementation decision needs an owner, approved window, prechecks, observable outcome, stop authority, and rollback path. Validate identity, DNS, communications, facilities, suppliers, and the people authorized to invoke recovery before and after the test, and store only sanitized operational evidence. ## Verification and evidence A reviewer should be able to retrace the decision from 42 CFR 460.84(d)(1)(i), read with 42 CFR 460.84(d)(1) (eCFR anchor p-460.84(d)(1)(i)); 42 CFR 460.84(d) (eCFR anchor p-460.84(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. Retain the starting state, authorization, execution record, outcome, deviation, and final state as one review package. Move disruptive checks to an approved test path. Reopen the decision when versions, design, dependencies, ownership, or official guidance changes. ## Official references - [42 CFR 460.84 – Emergency preparedness](https://www.ecfr.gov/current/title-42/section-460.84) — Centers for Medicare & Medicaid Services via eCFR ## Primary reference - Name: 42 CFR 460.84 - Emergency preparedness - Authority: www.ecfr.gov - URL: https://www.ecfr.gov/current/title-42/section-460.84 - Source publication date: Not stated by the source ## Citation and use Preferred citation: “Keep PACE participants connected to care during community disruption,” DSE Security, https://update.dsesecurity.com/updates/keep-pace-participants-connected-to-care-during-community-disruption/ Publishing principles: https://update.dsesecurity.com/updates/dse-updates-editorial-methodology/ Usage and citation policy: https://update.dsesecurity.com/usage/ Copyright © 2026 Detection Systems & Engineering. All rights reserved.