{
    "api_version": "1",
    "kind": "dse_post",
    "self": "https://update.dsesecurity.com/api/v1/posts/keep-labels-safety-data-sheets-and-training-synchronized-after-change/",
    "item": {
        "id": "https://update.dsesecurity.com/updates/keep-labels-safety-data-sheets-and-training-synchronized-after-change/",
        "slug": "keep-labels-safety-data-sheets-and-training-synchronized-after-change",
        "url": "https://update.dsesecurity.com/updates/keep-labels-safety-data-sheets-and-training-synchronized-after-change/",
        "alternate_urls": {
            "markdown": "https://update.dsesecurity.com/updates/keep-labels-safety-data-sheets-and-training-synchronized-after-change.md",
            "json": "https://update.dsesecurity.com/api/v1/posts/keep-labels-safety-data-sheets-and-training-synchronized-after-change/"
        },
        "title": "Keep labels, safety data sheets, and training synchronized after change",
        "summary": "Use 29 CFR 1910.1200 - Hazard Communication 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": "physical-security",
            "label": "Physical security",
            "alt": "Integrated video surveillance and controlled entry at a modern commercial facility.",
            "card_url": "https://update.dsesecurity.com/assets/editorial/physical-security-card.webp?v=1.8.20",
            "hero_url": "https://update.dsesecurity.com/assets/editorial/physical-security-hero.webp?v=1.8.20",
            "social_url": "https://update.dsesecurity.com/assets/editorial/physical-security-social-v2.jpg?v=1.8.20",
            "width": 2400,
            "height": 1350
        },
        "topics": [
            {
                "slug": "access-control",
                "name": "Access Control",
                "url": "https://update.dsesecurity.com/topic/access-control/"
            },
            {
                "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:26+00:00",
        "modified_at": "2026-08-27T13:04:10+00:00",
        "reviewed_on": "2026-08-26",
        "reading_minutes": 3,
        "word_count": 605,
        "potentially_affected": "Teams, systems, services, or facilities within the stated scope of 29 CFR 1910.1200 - Hazard Communication",
        "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": "29 CFR 1910.1200 - Hazard Communication",
            "url": "https://www.ecfr.gov/current/title-29/section-1910.1200",
            "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: Keep labels, safety data sheets, and training synchronized after change. 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-29/section-1910.1200\" target=\"_blank\" rel=\"noopener noreferrer\">29 CFR 1910.1200 &#8211; Hazard Communication</a> from Occupational Safety and Health Administration via eCFR supports the following bounded statements:</p>\n<ul>\n<li>Under 29 CFR 1910, in addition, this section requires distributors to transmit the required information to employers. (Employers who do not produce or import chemicals need only focus on those parts of this rule that deal with establishing a workplace program and communicating information to their workers.). The research record locates this support at <strong>29 CFR 1910.1200(b)(1) (eCFR anchor p-1910.1200(b)(1))</strong>.</li>\n<li>Under 29 CFR 1910, the rule requires that employers provide employees with effective information and training on hazardous chemicals in their work area at the time of their initial assignment, and whenever a new chemical hazard the employees have not previously been trained about is introduced into their work area. The research record locates this support at <strong>29 CFR 1910.1200(h)(1) (eCFR anchor p-1910.1200(h)(1))</strong>.</li>\n</ul>\n<p>Keep the evidence boundary at these traced claims. They support a review of critical rooms, power, cooling, water, fire protection, alternate sites, physical barriers, and documented recovery paths; they do not support conclusions outside the source&#8217;s stated conditions.</p>\n<h2>What the source does not establish</h2>\n<p>Federal workplace rule; classification, exemptions, multi-employer coordination, and state-plan requirements must be evaluated for the actual chemicals and work. Do not read the source as proof of implementation or permission to change production. Its guidance remains conditional on identity and access control, Windows DNS where networked services use it, time, communications, utilities, life-safety systems, vendors, and authorized responders and the environment&#8217;s recorded constraints.</p>\n<h2>Applicability questions</h2>\n<ul>\n<li>For source statement 1 at <strong>29 CFR 1910.1200(b)(1) (eCFR anchor p-1910.1200(b)(1))</strong>, which observable configuration, record, or test can confirm applicability here?</li>\n<li>For source statement 2 at <strong>29 CFR 1910.1200(h)(1) (eCFR anchor p-1910.1200(h)(1))</strong>, which observable configuration, record, or test can confirm applicability here?</li>\n<li>Which deployed instance of critical rooms, power, cooling, water, fire protection, alternate sites, physical barriers, and documented recovery paths 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 and access control, Windows DNS where networked services use it, time, communications, utilities, life-safety systems, vendors, and authorized responders?</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. Anchor the review in the cited section and keep observation separate from interpretation. Record the source location, examined part of critical rooms, power, cooling, water, fire protection, alternate sites, physical barriers, and documented recovery paths, observed and expected states, owner, and reason for deviation.</p>\n<p>Translate the conclusion into change control only after documenting dependencies, impact, test method, expected signals, failure signals, and restoration steps. Include identity and access control, Windows DNS where networked services use it, time, communications, utilities, life-safety systems, vendors, and authorized responders, while excluding secrets and sensitive personal or topology data from ordinary tickets.</p>\n<h2>Verification and evidence</h2>\n<p>Tie each conclusion back to <strong>29 CFR 1910.1200(b)(1) (eCFR anchor p-1910.1200(b)(1))</strong>; <strong>29 CFR 1910.1200(h)(1) (eCFR anchor p-1910.1200(h)(1))</strong> and to observable material such as facility inventories, inspection records, alarm and shutdown tests, maintenance history, recovery exercises, and corrective actions. Preserve provenance and stable identifiers without copying secrets into the evidence set.</p>\n<p>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.</p>\n<h2>Official references</h2>\n<ul>\n<li><a href=\"https://www.ecfr.gov/current/title-29/section-1910.1200\" target=\"_blank\" rel=\"noopener noreferrer\">29 CFR 1910.1200 &#8211; Hazard Communication</a> — Occupational Safety and Health Administration via eCFR</li>\n</ul>",
        "content_text": "Keep this document to one review outcome: Keep labels, safety data sheets, and training synchronized after change. Only the official source and traced locations below supply facts. Confirm applicability before acting.\nSource fact:\nThe official 29 CFR 1910.1200 – Hazard Communication from Occupational Safety and Health Administration via eCFR supports the following bounded statements:\n\nUnder 29 CFR 1910, in addition, this section requires distributors to transmit the required information to employers. (Employers who do not produce or import chemicals need only focus on those parts of this rule that deal with establishing a workplace program and communicating information to their workers.). The research record locates this support at 29 CFR 1910.1200(b)(1) (eCFR anchor p-1910.1200(b)(1)).\nUnder 29 CFR 1910, the rule requires that employers provide employees with effective information and training on hazardous chemicals in their work area at the time of their initial assignment, and whenever a new chemical hazard the employees have not previously been trained about is introduced into their work area. The research record locates this support at 29 CFR 1910.1200(h)(1) (eCFR anchor p-1910.1200(h)(1)).\n\nKeep the evidence boundary at these traced claims. They support a review of critical rooms, power, cooling, water, fire protection, alternate sites, physical barriers, and documented recovery paths; they do not support conclusions outside the source’s stated conditions.\nWhat the source does not establish\nFederal workplace rule; classification, exemptions, multi-employer coordination, and state-plan requirements must be evaluated for the actual chemicals and work. Do not read the source as proof of implementation or permission to change production. Its guidance remains conditional on identity and access control, Windows DNS where networked services use it, time, communications, utilities, life-safety systems, vendors, and authorized responders and the environment’s recorded constraints.\nApplicability questions\n\nFor source statement 1 at 29 CFR 1910.1200(b)(1) (eCFR anchor p-1910.1200(b)(1)), which observable configuration, record, or test can confirm applicability here?\nFor source statement 2 at 29 CFR 1910.1200(h)(1) (eCFR anchor p-1910.1200(h)(1)), which observable configuration, record, or test can confirm applicability here?\nWhich deployed instance of critical rooms, power, cooling, water, fire protection, alternate sites, physical barriers, and documented recovery paths will be compared with the source, and why that instance?\nHow will the review distinguish a source mismatch from a failure in identity and access control, Windows DNS where networked services use it, time, communications, utilities, life-safety systems, vendors, and authorized responders?\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. Anchor the review in the cited section and keep observation separate from interpretation. Record the source location, examined part of critical rooms, power, cooling, water, fire protection, alternate sites, physical barriers, and documented recovery paths, observed and expected states, owner, and reason for deviation.\nTranslate the conclusion into change control only after documenting dependencies, impact, test method, expected signals, failure signals, and restoration steps. Include identity and access control, Windows DNS where networked services use it, time, communications, utilities, life-safety systems, vendors, and authorized responders, while excluding secrets and sensitive personal or topology data from ordinary tickets.\nVerification and evidence\nTie each conclusion back to 29 CFR 1910.1200(b)(1) (eCFR anchor p-1910.1200(b)(1)); 29 CFR 1910.1200(h)(1) (eCFR anchor p-1910.1200(h)(1)) and to observable material such as facility inventories, inspection records, alarm and shutdown tests, maintenance history, recovery exercises, and corrective actions. Preserve provenance and stable identifiers without copying secrets into the evidence set.\nRetain 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.\nOfficial references\n\n29 CFR 1910.1200 – Hazard Communication — Occupational Safety and Health Administration via eCFR",
        "content_markdown": "Keep this document to one review outcome: Keep labels, safety data sheets, and training synchronized after change. Only the official source and traced locations below supply facts. Confirm applicability before acting.\n\n## Source fact:\n\nThe official [29 CFR 1910.1200 – Hazard Communication](https://www.ecfr.gov/current/title-29/section-1910.1200) from Occupational Safety and Health Administration via eCFR supports the following bounded statements:\n\n- Under 29 CFR 1910, in addition, this section requires distributors to transmit the required information to employers. (Employers who do not produce or import chemicals need only focus on those parts of this rule that deal with establishing a workplace program and communicating information to their workers.). The research record locates this support at 29 CFR 1910.1200(b)(1) (eCFR anchor p-1910.1200(b)(1)).\n\n- Under 29 CFR 1910, the rule requires that employers provide employees with effective information and training on hazardous chemicals in their work area at the time of their initial assignment, and whenever a new chemical hazard the employees have not previously been trained about is introduced into their work area. The research record locates this support at 29 CFR 1910.1200(h)(1) (eCFR anchor p-1910.1200(h)(1)).\n\nKeep the evidence boundary at these traced claims. They support a review of critical rooms, power, cooling, water, fire protection, alternate sites, physical barriers, and documented recovery paths; they do not support conclusions outside the source’s stated conditions.\n\n## What the source does not establish\n\nFederal workplace rule; classification, exemptions, multi-employer coordination, and state-plan requirements must be evaluated for the actual chemicals and work. Do not read the source as proof of implementation or permission to change production. Its guidance remains conditional on identity and access control, Windows DNS where networked services use it, time, communications, utilities, life-safety systems, vendors, and authorized responders and the environment’s recorded constraints.\n\n## Applicability questions\n\n- For source statement 1 at 29 CFR 1910.1200(b)(1) (eCFR anchor p-1910.1200(b)(1)), which observable configuration, record, or test can confirm applicability here?\n\n- For source statement 2 at 29 CFR 1910.1200(h)(1) (eCFR anchor p-1910.1200(h)(1)), which observable configuration, record, or test can confirm applicability here?\n\n- Which deployed instance of critical rooms, power, cooling, water, fire protection, alternate sites, physical barriers, and documented recovery paths 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 and access control, Windows DNS where networked services use it, time, communications, utilities, life-safety systems, vendors, and authorized responders?\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. Anchor the review in the cited section and keep observation separate from interpretation. Record the source location, examined part of critical rooms, power, cooling, water, fire protection, alternate sites, physical barriers, and documented recovery paths, observed and expected states, owner, and reason for deviation.\n\nTranslate the conclusion into change control only after documenting dependencies, impact, test method, expected signals, failure signals, and restoration steps. Include identity and access control, Windows DNS where networked services use it, time, communications, utilities, life-safety systems, vendors, and authorized responders, while excluding secrets and sensitive personal or topology data from ordinary tickets.\n\n## Verification and evidence\n\nTie each conclusion back to 29 CFR 1910.1200(b)(1) (eCFR anchor p-1910.1200(b)(1)); 29 CFR 1910.1200(h)(1) (eCFR anchor p-1910.1200(h)(1)) and to observable material such as facility inventories, inspection records, alarm and shutdown tests, maintenance history, recovery exercises, and corrective actions. Preserve provenance and stable identifiers without copying secrets into the evidence set.\n\nRetain 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.\n\n## Official references\n\n- [29 CFR 1910.1200 – Hazard Communication](https://www.ecfr.gov/current/title-29/section-1910.1200) — Occupational Safety and Health Administration 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/keep-labels-safety-data-sheets-and-training-synchronized-after-change/",
                "url": "https://update.dsesecurity.com/updates/keep-labels-safety-data-sheets-and-training-synchronized-after-change/",
                "isPartOf": {
                    "@id": "https://update.dsesecurity.com/#website"
                },
                "lastReviewed": "2026-08-26"
            },
            {
                "@type": "BreadcrumbList",
                "@id": "https://update.dsesecurity.com/updates/keep-labels-safety-data-sheets-and-training-synchronized-after-change/#breadcrumbs",
                "itemListElement": [
                    {
                        "@type": "ListItem",
                        "position": 1,
                        "name": "DSE Updates",
                        "item": "https://update.dsesecurity.com/"
                    },
                    {
                        "@type": "ListItem",
                        "position": 2,
                        "name": "Keep labels, safety data sheets, and training synchronized after change",
                        "item": "https://update.dsesecurity.com/updates/keep-labels-safety-data-sheets-and-training-synchronized-after-change/"
                    }
                ]
            },
            {
                "@type": [
                    "Article",
                    "TechArticle"
                ],
                "@id": "https://update.dsesecurity.com/updates/keep-labels-safety-data-sheets-and-training-synchronized-after-change/#article",
                "identifier": "https://update.dsesecurity.com/updates/keep-labels-safety-data-sheets-and-training-synchronized-after-change/",
                "url": "https://update.dsesecurity.com/updates/keep-labels-safety-data-sheets-and-training-synchronized-after-change/",
                "headline": "Keep labels, safety data sheets, and training synchronized after change",
                "description": "Use 29 CFR 1910.1200 - Hazard Communication to review this narrow operational decision without extending the source beyond its stated scope.",
                "abstract": "Use 29 CFR 1910.1200 - Hazard Communication to review this narrow operational decision without extending the source beyond its stated scope.",
                "articleBody": "Keep this document to one review outcome: Keep labels, safety data sheets, and training synchronized after change. Only the official source and traced locations below supply facts. Confirm applicability before acting.\nSource fact:\nThe official 29 CFR 1910.1200 – Hazard Communication from Occupational Safety and Health Administration via eCFR supports the following bounded statements:\n\nUnder 29 CFR 1910, in addition, this section requires distributors to transmit the required information to employers. (Employers who do not produce or import chemicals need only focus on those parts of this rule that deal with establishing a workplace program and communicating information to their workers.). The research record locates this support at 29 CFR 1910.1200(b)(1) (eCFR anchor p-1910.1200(b)(1)).\nUnder 29 CFR 1910, the rule requires that employers provide employees with effective information and training on hazardous chemicals in their work area at the time of their initial assignment, and whenever a new chemical hazard the employees have not previously been trained about is introduced into their work area. The research record locates this support at 29 CFR 1910.1200(h)(1) (eCFR anchor p-1910.1200(h)(1)).\n\nKeep the evidence boundary at these traced claims. They support a review of critical rooms, power, cooling, water, fire protection, alternate sites, physical barriers, and documented recovery paths; they do not support conclusions outside the source’s stated conditions.\nWhat the source does not establish\nFederal workplace rule; classification, exemptions, multi-employer coordination, and state-plan requirements must be evaluated for the actual chemicals and work. Do not read the source as proof of implementation or permission to change production. Its guidance remains conditional on identity and access control, Windows DNS where networked services use it, time, communications, utilities, life-safety systems, vendors, and authorized responders and the environment’s recorded constraints.\nApplicability questions\n\nFor source statement 1 at 29 CFR 1910.1200(b)(1) (eCFR anchor p-1910.1200(b)(1)), which observable configuration, record, or test can confirm applicability here?\nFor source statement 2 at 29 CFR 1910.1200(h)(1) (eCFR anchor p-1910.1200(h)(1)), which observable configuration, record, or test can confirm applicability here?\nWhich deployed instance of critical rooms, power, cooling, water, fire protection, alternate sites, physical barriers, and documented recovery paths will be compared with the source, and why that instance?\nHow will the review distinguish a source mismatch from a failure in identity and access control, Windows DNS where networked services use it, time, communications, utilities, life-safety systems, vendors, and authorized responders?\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. Anchor the review in the cited section and keep observation separate from interpretation. Record the source location, examined part of critical rooms, power, cooling, water, fire protection, alternate sites, physical barriers, and documented recovery paths, observed and expected states, owner, and reason for deviation.\nTranslate the conclusion into change control only after documenting dependencies, impact, test method, expected signals, failure signals, and restoration steps. Include identity and access control, Windows DNS where networked services use it, time, communications, utilities, life-safety systems, vendors, and authorized responders, while excluding secrets and sensitive personal or topology data from ordinary tickets.\nVerification and evidence\nTie each conclusion back to 29 CFR 1910.1200(b)(1) (eCFR anchor p-1910.1200(b)(1)); 29 CFR 1910.1200(h)(1) (eCFR anchor p-1910.1200(h)(1)) and to observable material such as facility inventories, inspection records, alarm and shutdown tests, maintenance history, recovery exercises, and corrective actions. Preserve provenance and stable identifiers without copying secrets into the evidence set.\nRetain 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.\nOfficial references\n\n29 CFR 1910.1200 – Hazard Communication — Occupational Safety and Health Administration via eCFR",
                "datePublished": "2026-08-27T12:12:26+00:00",
                "dateModified": "2026-08-27T13:04:10+00:00",
                "mainEntityOfPage": {
                    "@id": "https://update.dsesecurity.com/updates/keep-labels-safety-data-sheets-and-training-synchronized-after-change/"
                },
                "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/keep-labels-safety-data-sheets-and-training-synchronized-after-change/#primaryimage",
                    "url": "https://update.dsesecurity.com/assets/editorial/physical-security-social-v2.jpg?v=1.8.20",
                    "contentUrl": "https://update.dsesecurity.com/assets/editorial/physical-security-social-v2.jpg?v=1.8.20",
                    "width": 1200,
                    "height": 630,
                    "caption": "Keep labels, safety data sheets, and training synchronized after change"
                },
                "articleSection": [
                    "Access Control",
                    "Business Continuity",
                    "Cybersecurity"
                ],
                "keywords": [
                    "Access Control",
                    "Business Continuity",
                    "Cybersecurity",
                    "Playbook",
                    "Advisory priority"
                ],
                "genre": "Playbook",
                "about": [
                    {
                        "@type": "Thing",
                        "name": "Access Control",
                        "url": "https://update.dsesecurity.com/topic/access-control/"
                    },
                    {
                        "@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": 605,
                "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": "29 CFR 1910.1200 - Hazard Communication",
                    "url": "https://www.ecfr.gov/current/title-29/section-1910.1200"
                }
            }
        ]
    }
}