Apply NFPA 99 risk categories 1-4 to determine medical gas system requirements for a facility
domain: nfpa.org · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Confirm the four NFPA 99 risk categories: Category 1 (failure likely to cause major injury or death), Category 2 (failure likely to cause minor injury), Category 3 (failure unlikely to cause injury but may cause patient/caregiver discomfort), Category 4 (failure has no impact on patient care)
Confirm category assignment is based on a documented, defined risk-assessment procedure (NFPA 99 Chapter 4) applied per system/space — not automatically determined by building occupancy type or facility label alone
Confirm the risk assessment should consider factors such as patient population/acuity, procedures performed, anesthesia/sedation levels used, and equipment/systems involved, and reference an accepted risk-assessment methodology (NFPA 99 Annex A cites examples such as ISO/IEC 31010, NFPA 551, and SEMI S10)
Confirm the assigned category then drives the specific technical requirements (redundancy, alarm monitoring, testing frequency, system components) applicable to that space/system under the rest of NFPA 99
Confirm and document the risk assessment in the facility's records, since NFPA 99 requires the categorization procedure itself to be documented, not just the resulting category
Known gotchas
A higher category is not automatically 'safer to over-assign' — voluntarily installing Category 1 provisions where a lower category would apply can exempt the need for a full risk assessment, but confirm this exception's exact wording against the current edition before relying on it
Category assignment must be documented per system, not assumed wholesale for an entire building based on its general classification (e.g., 'hospital' vs. 'clinic')
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?