{
    "api_version": "1",
    "kind": "dse_post",
    "self": "https://update.dsesecurity.com/api/v1/posts/protect-dialysis-patients-when-treatment-sites-or-utilities-fail/",
    "item": {
        "id": "https://update.dsesecurity.com/updates/protect-dialysis-patients-when-treatment-sites-or-utilities-fail/",
        "slug": "protect-dialysis-patients-when-treatment-sites-or-utilities-fail",
        "url": "https://update.dsesecurity.com/updates/protect-dialysis-patients-when-treatment-sites-or-utilities-fail/",
        "alternate_urls": {
            "markdown": "https://update.dsesecurity.com/updates/protect-dialysis-patients-when-treatment-sites-or-utilities-fail.md",
            "json": "https://update.dsesecurity.com/api/v1/posts/protect-dialysis-patients-when-treatment-sites-or-utilities-fail/"
        },
        "title": "Protect dialysis patients when treatment sites or utilities fail",
        "summary": "Use 42 CFR 494.62 - Emergency preparedness to review this narrow operational decision without extending the source beyond its stated scope.",
        "format": {
            "slug": "playbook",
            "name": "Playbook"
        },
        "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:11:56+00:00",
        "modified_at": "2026-08-27T13:06:59+00:00",
        "reviewed_on": "2026-08-26",
        "reading_minutes": 3,
        "word_count": 612,
        "potentially_affected": "Teams, systems, services, or facilities within the stated scope of 42 CFR 494.62 - 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 494.62 - Emergency preparedness",
            "url": "https://www.ecfr.gov/current/title-42/section-494.62",
            "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>Keep this document to one review outcome: Protect dialysis patients when treatment sites or utilities fail. 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-494.62\" target=\"_blank\" rel=\"noopener noreferrer\">42 CFR 494.62 &#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 494, the rule requires that if elected, the unified and integrated emergency preparedness program do all of the following: include integrated policies and procedures that meet the requirements set forth in paragraph (b) of this section, a coordinated communication plan and training and testing programs that meet the requirements of paragraphs (c) and (d) of this section, respectively. The research record locates this support at <strong>42 CFR 494.62(e)(5), read with 42 CFR 494.62(e) (eCFR anchor p-494.62(e)(5))</strong>.</li>\n<li>Under 42 CFR 494, the rule requires that the dialysis facility develop and maintain an emergency preparedness training, testing and patient orientation 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 494.62(d) (eCFR anchor p-494.62(d))</strong>.</li>\n</ul>\n<p>The source support ends with the statements listed above. Use them to examine essential functions, upstream providers, recovery sequences, alternate work paths, and tested recovery objectives in the applicable environment, not to imply a wider guarantee.</p>\n<h2>What the source does not establish</h2>\n<p>ESRD-facility federal condition; water, power, treatment schedule, patient education, alternate facilities, transport, clinical decisions, state law, and survey guidance require detailed 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.</p>\n<h2>Applicability questions</h2>\n<ul>\n<li>For source statement 1 at <strong>42 CFR 494.62(e)(5), read with 42 CFR 494.62(e) (eCFR anchor p-494.62(e)(5))</strong>, which observable configuration, record, or test can confirm applicability here?</li>\n<li>For source statement 2 at <strong>42 CFR 494.62(d) (eCFR anchor p-494.62(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. Make the source, asset scope, owner, and expected outcome explicit in the review record. 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>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.</p>\n<h2>Verification and evidence</h2>\n<p>Evidence should let another reviewer reproduce this decision. Retain observations beside the traced locations <strong>42 CFR 494.62(e)(5), read with 42 CFR 494.62(e) (eCFR anchor p-494.62(e)(5))</strong>; <strong>42 CFR 494.62(d) (eCFR anchor p-494.62(d))</strong>. Favor business-impact records, dependency maps, exercise results, recovery timings, and open corrective actions, linked to stable identifiers, time, and operator.</p>\n<p>Close the review only when the evidence, exception handling, resulting action, and after-state are linked. Schedule a new review after material technical, organizational, incident, or source changes; today&#8217;s observation is not a continuing guarantee.</p>\n<h2>Official references</h2>\n<ul>\n<li><a href=\"https://www.ecfr.gov/current/title-42/section-494.62\" target=\"_blank\" rel=\"noopener noreferrer\">42 CFR 494.62 &#8211; Emergency preparedness</a> — Centers for Medicare &amp; Medicaid Services via eCFR</li>\n</ul>",
        "content_text": "Keep this document to one review outcome: Protect dialysis patients when treatment sites or utilities fail. Only the official source and traced locations below supply facts. Confirm applicability before acting.\nSource fact:\nThe official 42 CFR 494.62 – Emergency preparedness from Centers for Medicare & Medicaid Services via eCFR supports the following bounded statements:\n\nUnder 42 CFR 494, the rule requires that if elected, the unified and integrated emergency preparedness program do all of the following: include integrated policies and procedures that meet the requirements set forth in paragraph (b) of this section, a coordinated communication plan and training and testing programs that meet the requirements of paragraphs (c) and (d) of this section, respectively. The research record locates this support at 42 CFR 494.62(e)(5), read with 42 CFR 494.62(e) (eCFR anchor p-494.62(e)(5)).\nUnder 42 CFR 494, the rule requires that the dialysis facility develop and maintain an emergency preparedness training, testing and patient orientation 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 494.62(d) (eCFR anchor p-494.62(d)).\n\nThe source support ends with the statements listed above. Use them to examine essential functions, upstream providers, recovery sequences, alternate work paths, and tested recovery objectives in the applicable environment, not to imply a wider guarantee.\nWhat the source does not establish\nESRD-facility federal condition; water, power, treatment schedule, patient education, alternate facilities, transport, clinical decisions, state law, and survey guidance require detailed 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.\nApplicability questions\n\nFor source statement 1 at 42 CFR 494.62(e)(5), read with 42 CFR 494.62(e) (eCFR anchor p-494.62(e)(5)), which observable configuration, record, or test can confirm applicability here?\nFor source statement 2 at 42 CFR 494.62(d) (eCFR anchor p-494.62(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. Make the source, asset scope, owner, and expected outcome explicit in the review record. 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.\nAn 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.\nVerification and evidence\nEvidence should let another reviewer reproduce this decision. Retain observations beside the traced locations 42 CFR 494.62(e)(5), read with 42 CFR 494.62(e) (eCFR anchor p-494.62(e)(5)); 42 CFR 494.62(d) (eCFR anchor p-494.62(d)). Favor business-impact records, dependency maps, exercise results, recovery timings, and open corrective actions, linked to stable identifiers, time, and operator.\nClose the review only when the evidence, exception handling, resulting action, and after-state are linked. Schedule a new review after material technical, organizational, incident, or source changes; today’s observation is not a continuing guarantee.\nOfficial references\n\n42 CFR 494.62 – Emergency preparedness — Centers for Medicare & Medicaid Services via eCFR",
        "content_markdown": "Keep this document to one review outcome: Protect dialysis patients when treatment sites or utilities fail. Only the official source and traced locations below supply facts. Confirm applicability before acting.\n\n## Source fact:\n\nThe official [42 CFR 494.62 – Emergency preparedness](https://www.ecfr.gov/current/title-42/section-494.62) from Centers for Medicare & Medicaid Services via eCFR supports the following bounded statements:\n\n- Under 42 CFR 494, the rule requires that if elected, the unified and integrated emergency preparedness program do all of the following: include integrated policies and procedures that meet the requirements set forth in paragraph (b) of this section, a coordinated communication plan and training and testing programs that meet the requirements of paragraphs (c) and (d) of this section, respectively. The research record locates this support at 42 CFR 494.62(e)(5), read with 42 CFR 494.62(e) (eCFR anchor p-494.62(e)(5)).\n\n- Under 42 CFR 494, the rule requires that the dialysis facility develop and maintain an emergency preparedness training, testing and patient orientation 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 494.62(d) (eCFR anchor p-494.62(d)).\n\nThe source support ends with the statements listed above. Use them to examine essential functions, upstream providers, recovery sequences, alternate work paths, and tested recovery objectives in the applicable environment, not to imply a wider guarantee.\n\n## What the source does not establish\n\nESRD-facility federal condition; water, power, treatment schedule, patient education, alternate facilities, transport, clinical decisions, state law, and survey guidance require detailed 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.\n\n## Applicability questions\n\n- For source statement 1 at 42 CFR 494.62(e)(5), read with 42 CFR 494.62(e) (eCFR anchor p-494.62(e)(5)), which observable configuration, record, or test can confirm applicability here?\n\n- For source statement 2 at 42 CFR 494.62(d) (eCFR anchor p-494.62(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. Make the source, asset scope, owner, and expected outcome explicit in the review record. 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\nAn 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.\n\n## Verification and evidence\n\nEvidence should let another reviewer reproduce this decision. Retain observations beside the traced locations 42 CFR 494.62(e)(5), read with 42 CFR 494.62(e) (eCFR anchor p-494.62(e)(5)); 42 CFR 494.62(d) (eCFR anchor p-494.62(d)). Favor business-impact records, dependency maps, exercise results, recovery timings, and open corrective actions, linked to stable identifiers, time, and operator.\n\nClose the review only when the evidence, exception handling, resulting action, and after-state are linked. Schedule a new review after material technical, organizational, incident, or source changes; today’s observation is not a continuing guarantee.\n\n## Official references\n\n- [42 CFR 494.62 – Emergency preparedness](https://www.ecfr.gov/current/title-42/section-494.62) — 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/protect-dialysis-patients-when-treatment-sites-or-utilities-fail/",
                "url": "https://update.dsesecurity.com/updates/protect-dialysis-patients-when-treatment-sites-or-utilities-fail/",
                "isPartOf": {
                    "@id": "https://update.dsesecurity.com/#website"
                },
                "lastReviewed": "2026-08-26"
            },
            {
                "@type": "BreadcrumbList",
                "@id": "https://update.dsesecurity.com/updates/protect-dialysis-patients-when-treatment-sites-or-utilities-fail/#breadcrumbs",
                "itemListElement": [
                    {
                        "@type": "ListItem",
                        "position": 1,
                        "name": "DSE Updates",
                        "item": "https://update.dsesecurity.com/"
                    },
                    {
                        "@type": "ListItem",
                        "position": 2,
                        "name": "Protect dialysis patients when treatment sites or utilities fail",
                        "item": "https://update.dsesecurity.com/updates/protect-dialysis-patients-when-treatment-sites-or-utilities-fail/"
                    }
                ]
            },
            {
                "@type": [
                    "Article",
                    "TechArticle"
                ],
                "@id": "https://update.dsesecurity.com/updates/protect-dialysis-patients-when-treatment-sites-or-utilities-fail/#article",
                "identifier": "https://update.dsesecurity.com/updates/protect-dialysis-patients-when-treatment-sites-or-utilities-fail/",
                "url": "https://update.dsesecurity.com/updates/protect-dialysis-patients-when-treatment-sites-or-utilities-fail/",
                "headline": "Protect dialysis patients when treatment sites or utilities fail",
                "description": "Use 42 CFR 494.62 - Emergency preparedness to review this narrow operational decision without extending the source beyond its stated scope.",
                "abstract": "Use 42 CFR 494.62 - Emergency preparedness to review this narrow operational decision without extending the source beyond its stated scope.",
                "articleBody": "Keep this document to one review outcome: Protect dialysis patients when treatment sites or utilities fail. Only the official source and traced locations below supply facts. Confirm applicability before acting.\nSource fact:\nThe official 42 CFR 494.62 – Emergency preparedness from Centers for Medicare & Medicaid Services via eCFR supports the following bounded statements:\n\nUnder 42 CFR 494, the rule requires that if elected, the unified and integrated emergency preparedness program do all of the following: include integrated policies and procedures that meet the requirements set forth in paragraph (b) of this section, a coordinated communication plan and training and testing programs that meet the requirements of paragraphs (c) and (d) of this section, respectively. The research record locates this support at 42 CFR 494.62(e)(5), read with 42 CFR 494.62(e) (eCFR anchor p-494.62(e)(5)).\nUnder 42 CFR 494, the rule requires that the dialysis facility develop and maintain an emergency preparedness training, testing and patient orientation 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 494.62(d) (eCFR anchor p-494.62(d)).\n\nThe source support ends with the statements listed above. Use them to examine essential functions, upstream providers, recovery sequences, alternate work paths, and tested recovery objectives in the applicable environment, not to imply a wider guarantee.\nWhat the source does not establish\nESRD-facility federal condition; water, power, treatment schedule, patient education, alternate facilities, transport, clinical decisions, state law, and survey guidance require detailed 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.\nApplicability questions\n\nFor source statement 1 at 42 CFR 494.62(e)(5), read with 42 CFR 494.62(e) (eCFR anchor p-494.62(e)(5)), which observable configuration, record, or test can confirm applicability here?\nFor source statement 2 at 42 CFR 494.62(d) (eCFR anchor p-494.62(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. Make the source, asset scope, owner, and expected outcome explicit in the review record. 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.\nAn 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.\nVerification and evidence\nEvidence should let another reviewer reproduce this decision. Retain observations beside the traced locations 42 CFR 494.62(e)(5), read with 42 CFR 494.62(e) (eCFR anchor p-494.62(e)(5)); 42 CFR 494.62(d) (eCFR anchor p-494.62(d)). Favor business-impact records, dependency maps, exercise results, recovery timings, and open corrective actions, linked to stable identifiers, time, and operator.\nClose the review only when the evidence, exception handling, resulting action, and after-state are linked. Schedule a new review after material technical, organizational, incident, or source changes; today’s observation is not a continuing guarantee.\nOfficial references\n\n42 CFR 494.62 – Emergency preparedness — Centers for Medicare & Medicaid Services via eCFR",
                "datePublished": "2026-08-27T12:11:56+00:00",
                "dateModified": "2026-08-27T13:06:59+00:00",
                "mainEntityOfPage": {
                    "@id": "https://update.dsesecurity.com/updates/protect-dialysis-patients-when-treatment-sites-or-utilities-fail/"
                },
                "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/protect-dialysis-patients-when-treatment-sites-or-utilities-fail/#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": "Protect dialysis patients when treatment sites or utilities fail"
                },
                "articleSection": [
                    "Business Continuity",
                    "Cybersecurity"
                ],
                "keywords": [
                    "Business Continuity",
                    "Cybersecurity",
                    "Playbook",
                    "Advisory priority"
                ],
                "genre": "Playbook",
                "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": 612,
                "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 494.62 - Emergency preparedness",
                    "url": "https://www.ecfr.gov/current/title-42/section-494.62"
                }
            }
        ]
    }
}