{
    "api_version": "1",
    "kind": "dse_post",
    "self": "https://update.dsesecurity.com/api/v1/posts/coordinate-hospice-emergency-plans-across-home-and-inpatient-care/",
    "item": {
        "id": "https://update.dsesecurity.com/updates/coordinate-hospice-emergency-plans-across-home-and-inpatient-care/",
        "slug": "coordinate-hospice-emergency-plans-across-home-and-inpatient-care",
        "url": "https://update.dsesecurity.com/updates/coordinate-hospice-emergency-plans-across-home-and-inpatient-care/",
        "alternate_urls": {
            "markdown": "https://update.dsesecurity.com/updates/coordinate-hospice-emergency-plans-across-home-and-inpatient-care.md",
            "json": "https://update.dsesecurity.com/api/v1/posts/coordinate-hospice-emergency-plans-across-home-and-inpatient-care/"
        },
        "title": "Coordinate hospice emergency plans across home and inpatient care",
        "summary": "Use 42 CFR 418.113 - Emergency preparedness to review this narrow operational decision without extending the source beyond its stated scope.",
        "format": {
            "slug": "explainer",
            "name": "Explainer"
        },
        "priority": {
            "slug": "advisory",
            "name": "Advisory"
        },
        "featured": false,
        "image": {
            "theme": "continuity-recovery",
            "label": "Continuity & recovery",
            "alt": "Paired infrastructure paths converging on a stable recovered service.",
            "card_url": "https://update.dsesecurity.com/assets/editorial/continuity-recovery-card.webp?v=1.8.20",
            "hero_url": "https://update.dsesecurity.com/assets/editorial/continuity-recovery-hero.webp?v=1.8.20",
            "social_url": "https://update.dsesecurity.com/assets/editorial/continuity-recovery-social-v2.jpg?v=1.8.20",
            "width": 2400,
            "height": 1350
        },
        "topics": [
            {
                "slug": "business-continuity",
                "name": "Business Continuity",
                "url": "https://update.dsesecurity.com/topic/business-continuity/"
            },
            {
                "slug": "cybersecurity",
                "name": "Cybersecurity",
                "url": "https://update.dsesecurity.com/topic/cybersecurity/"
            }
        ],
        "author": {
            "name": "DSE Security Editorial Team",
            "url": "https://update.dsesecurity.com/#editorial-team",
            "type": "Organization"
        },
        "publisher": {
            "name": "Detection Systems & Engineering",
            "url": "https://dsesecurity.com/"
        },
        "published_at": "2026-08-27T12:12:08+00:00",
        "modified_at": "2026-08-27T13:06:58+00:00",
        "reviewed_on": "2026-08-26",
        "reading_minutes": 3,
        "word_count": 600,
        "potentially_affected": "Teams, systems, services, or facilities within the stated scope of 42 CFR 418.113 - 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.",
        "primary_source": {
            "name": "42 CFR 418.113 - Emergency preparedness",
            "url": "https://www.ecfr.gov/current/title-42/section-418.113",
            "published_on": null,
            "authority": "www.ecfr.gov"
        },
        "publishing_principles": "https://update.dsesecurity.com/updates/dse-updates-editorial-methodology/",
        "usage_info": "https://update.dsesecurity.com/usage/",
        "copyright_notice": "Copyright © 2026 Detection Systems & Engineering. All rights reserved.",
        "content_html": "<p>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.</p>\n<h2>Source fact:</h2>\n<p>The official <a href=\"https://www.ecfr.gov/current/title-42/section-418.113\" target=\"_blank\" rel=\"noopener noreferrer\">42 CFR 418.113 &#8211; Emergency preparedness</a> from Centers for Medicare &amp; Medicaid Services via eCFR supports the following bounded statements:</p>\n<ul>\n<li>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 <strong>42 CFR 418.113(a)(3), read with 42 CFR 418.113(a) (eCFR anchor p-418.113(a)(3))</strong>.</li>\n<li>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 <strong>42 CFR 418.113(d) (eCFR anchor p-418.113(d))</strong>.</li>\n</ul>\n<p>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.</p>\n<h2>What the source does not establish</h2>\n<p>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.</p>\n<h2>Applicability questions</h2>\n<ul>\n<li>For source statement 1 at <strong>42 CFR 418.113(a)(3), read with 42 CFR 418.113(a) (eCFR anchor p-418.113(a)(3))</strong>, which observable configuration, record, or test can confirm applicability here?</li>\n<li>For source statement 2 at <strong>42 CFR 418.113(d) (eCFR anchor p-418.113(d))</strong>, which observable configuration, record, or test can confirm applicability here?</li>\n<li>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?</li>\n<li>How will the review distinguish a source mismatch from a failure in identity, DNS, communications, facilities, suppliers, and the people authorized to invoke recovery?</li>\n<li>Who approves the conclusion, exception, test window, and rollback threshold?</li>\n</ul>\n<h2>DSE recommendation:</h2>\n<p>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.</p>\n<p>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.</p>\n<h2>Verification and evidence</h2>\n<p>A reviewer should be able to retrace the decision from <strong>42 CFR 418.113(a)(3), read with 42 CFR 418.113(a) (eCFR anchor p-418.113(a)(3))</strong>; <strong>42 CFR 418.113(d) (eCFR anchor p-418.113(d))</strong> 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.</p>\n<p>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.</p>\n<h2>Official references</h2>\n<ul>\n<li><a href=\"https://www.ecfr.gov/current/title-42/section-418.113\" target=\"_blank\" rel=\"noopener noreferrer\">42 CFR 418.113 &#8211; Emergency preparedness</a> — Centers for Medicare &amp; Medicaid Services via eCFR</li>\n</ul>",
        "content_text": "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.\nSource fact:\nThe official 42 CFR 418.113 – Emergency preparedness from Centers for Medicare & Medicaid Services via eCFR supports the following bounded statements:\n\nUnder 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)).\nUnder 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)).\n\nOnly 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.\nWhat the source does not establish\nHospice-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.\nApplicability questions\n\nFor 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?\nFor 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?\nWhich 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?\nHow will the review distinguish a source mismatch from a failure in identity, DNS, communications, facilities, suppliers, and the people authorized to invoke recovery?\nWho approves the conclusion, exception, test window, and rollback threshold?\n\nDSE recommendation:\nDSE 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.\nIf 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.\nVerification and evidence\nA 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.\nRecord 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.\nOfficial references\n\n42 CFR 418.113 – Emergency preparedness — Centers for Medicare & Medicaid Services via eCFR",
        "content_markdown": "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.\n\n## Source fact:\n\nThe official [42 CFR 418.113 – Emergency preparedness](https://www.ecfr.gov/current/title-42/section-418.113) from Centers for Medicare & Medicaid Services via eCFR supports the following bounded statements:\n\n- 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)).\n\n- 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)).\n\nOnly 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.\n\n## What the source does not establish\n\nHospice-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.\n\n## Applicability questions\n\n- 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?\n\n- 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?\n\n- 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?\n\n- How will the review distinguish a source mismatch from a failure in identity, DNS, communications, facilities, suppliers, and the people authorized to invoke recovery?\n\n- Who approves the conclusion, exception, test window, and rollback threshold?\n\n## DSE recommendation:\n\nDSE 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.\n\nIf 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.\n\n## Verification and evidence\n\nA 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.\n\nRecord 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.\n\n## Official references\n\n- [42 CFR 418.113 – Emergency preparedness](https://www.ecfr.gov/current/title-42/section-418.113) — Centers for Medicare & Medicaid Services via eCFR"
    },
    "json_ld": {
        "@context": "https://schema.org",
        "@graph": [
            {
                "@type": "Organization",
                "@id": "https://dsesecurity.com/#organization",
                "name": "Detection Systems & Engineering",
                "alternateName": "DSE Security",
                "url": "https://dsesecurity.com/",
                "logo": {
                    "@type": "ImageObject",
                    "url": "https://update.dsesecurity.com/assets/dse-logo-20260812.png?v=1.8.20"
                }
            },
            {
                "@type": "Organization",
                "@id": "https://update.dsesecurity.com/#editorial-team",
                "name": "DSE Security Editorial Team",
                "url": "https://update.dsesecurity.com/",
                "parentOrganization": {
                    "@id": "https://dsesecurity.com/#organization"
                }
            },
            {
                "@type": "WebSite",
                "@id": "https://update.dsesecurity.com/#website",
                "name": "DSE Updates",
                "alternateName": "DSE Security Knowledge Hub",
                "url": "https://update.dsesecurity.com/",
                "inLanguage": "en-US",
                "publisher": {
                    "@id": "https://dsesecurity.com/#organization"
                },
                "potentialAction": {
                    "@type": "SearchAction",
                    "target": {
                        "@type": "EntryPoint",
                        "urlTemplate": "https://update.dsesecurity.com/?q={search_term_string}"
                    },
                    "query-input": "required name=search_term_string"
                }
            },
            {
                "@type": "WebPage",
                "@id": "https://update.dsesecurity.com/updates/coordinate-hospice-emergency-plans-across-home-and-inpatient-care/",
                "url": "https://update.dsesecurity.com/updates/coordinate-hospice-emergency-plans-across-home-and-inpatient-care/",
                "isPartOf": {
                    "@id": "https://update.dsesecurity.com/#website"
                },
                "lastReviewed": "2026-08-26"
            },
            {
                "@type": "BreadcrumbList",
                "@id": "https://update.dsesecurity.com/updates/coordinate-hospice-emergency-plans-across-home-and-inpatient-care/#breadcrumbs",
                "itemListElement": [
                    {
                        "@type": "ListItem",
                        "position": 1,
                        "name": "DSE Updates",
                        "item": "https://update.dsesecurity.com/"
                    },
                    {
                        "@type": "ListItem",
                        "position": 2,
                        "name": "Coordinate hospice emergency plans across home and inpatient care",
                        "item": "https://update.dsesecurity.com/updates/coordinate-hospice-emergency-plans-across-home-and-inpatient-care/"
                    }
                ]
            },
            {
                "@type": [
                    "Article",
                    "TechArticle"
                ],
                "@id": "https://update.dsesecurity.com/updates/coordinate-hospice-emergency-plans-across-home-and-inpatient-care/#article",
                "identifier": "https://update.dsesecurity.com/updates/coordinate-hospice-emergency-plans-across-home-and-inpatient-care/",
                "url": "https://update.dsesecurity.com/updates/coordinate-hospice-emergency-plans-across-home-and-inpatient-care/",
                "headline": "Coordinate hospice emergency plans across home and inpatient care",
                "description": "Use 42 CFR 418.113 - Emergency preparedness to review this narrow operational decision without extending the source beyond its stated scope.",
                "abstract": "Use 42 CFR 418.113 - Emergency preparedness to review this narrow operational decision without extending the source beyond its stated scope.",
                "articleBody": "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.\nSource fact:\nThe official 42 CFR 418.113 – Emergency preparedness from Centers for Medicare & Medicaid Services via eCFR supports the following bounded statements:\n\nUnder 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)).\nUnder 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)).\n\nOnly 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.\nWhat the source does not establish\nHospice-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.\nApplicability questions\n\nFor 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?\nFor 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?\nWhich 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?\nHow will the review distinguish a source mismatch from a failure in identity, DNS, communications, facilities, suppliers, and the people authorized to invoke recovery?\nWho approves the conclusion, exception, test window, and rollback threshold?\n\nDSE recommendation:\nDSE 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.\nIf 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.\nVerification and evidence\nA 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.\nRecord 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.\nOfficial references\n\n42 CFR 418.113 – Emergency preparedness — Centers for Medicare & Medicaid Services via eCFR",
                "datePublished": "2026-08-27T12:12:08+00:00",
                "dateModified": "2026-08-27T13:06:58+00:00",
                "mainEntityOfPage": {
                    "@id": "https://update.dsesecurity.com/updates/coordinate-hospice-emergency-plans-across-home-and-inpatient-care/"
                },
                "inLanguage": "en-US",
                "isAccessibleForFree": true,
                "author": {
                    "@type": "Organization",
                    "name": "DSE Security Editorial Team",
                    "url": "https://update.dsesecurity.com/#editorial-team"
                },
                "publisher": {
                    "@id": "https://dsesecurity.com/#organization"
                },
                "image": {
                    "@type": "ImageObject",
                    "@id": "https://update.dsesecurity.com/updates/coordinate-hospice-emergency-plans-across-home-and-inpatient-care/#primaryimage",
                    "url": "https://update.dsesecurity.com/assets/editorial/continuity-recovery-social-v2.jpg?v=1.8.20",
                    "contentUrl": "https://update.dsesecurity.com/assets/editorial/continuity-recovery-social-v2.jpg?v=1.8.20",
                    "width": 1200,
                    "height": 630,
                    "caption": "Coordinate hospice emergency plans across home and inpatient care"
                },
                "articleSection": [
                    "Business Continuity",
                    "Cybersecurity"
                ],
                "keywords": [
                    "Business Continuity",
                    "Cybersecurity",
                    "Explainer",
                    "Advisory priority"
                ],
                "genre": "Explainer",
                "about": [
                    {
                        "@type": "Thing",
                        "name": "Business Continuity",
                        "url": "https://update.dsesecurity.com/topic/business-continuity/"
                    },
                    {
                        "@type": "Thing",
                        "name": "Cybersecurity",
                        "url": "https://update.dsesecurity.com/topic/cybersecurity/"
                    }
                ],
                "wordCount": 600,
                "timeRequired": "PT3M",
                "publishingPrinciples": "https://update.dsesecurity.com/updates/dse-updates-editorial-methodology/",
                "usageInfo": "https://update.dsesecurity.com/usage/",
                "copyrightHolder": {
                    "@id": "https://dsesecurity.com/#organization"
                },
                "copyrightNotice": "Copyright © 2026 Detection Systems & Engineering. All rights reserved.",
                "citation": {
                    "@type": "CreativeWork",
                    "name": "42 CFR 418.113 - Emergency preparedness",
                    "url": "https://www.ecfr.gov/current/title-42/section-418.113"
                }
            }
        ]
    }
}