Determine how medical gas outlet risk category is assigned differently (or not) between an ambulatory surgery center (ASC) and a hospital
domain: nfpa.org · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Confirm NFPA 99 assigns risk category (1-4) based on a documented risk assessment of the procedures and systems supported at a given space — not automatically based on whether the facility is labeled a 'hospital' or an 'ambulatory surgery center'
Confirm that an ASC performing full surgical procedures under general anesthesia is expected to meet the same Category 1 (or applicable) system requirements as a comparable hospital operating room, since the risk is tied to the procedure/anesthesia level, not the building type
Confirm hospital outpatient surgical departments are generally expected to meet provisions comparable to those applicable to ambulatory health care occupancies performing similar procedures, reflecting the risk-based (not occupancy-based) philosophy introduced in more recent NFPA 99 editions
Confirm the facility's own documented risk assessment (not a generic assumption) is what ultimately determines and justifies the category for each system/space in either a hospital or an ASC setting
Confirm with the state health facility licensing authority whether any state-specific ASC licensing rules impose additional or different category requirements beyond the base NFPA 99 risk-assessment approach
Known gotchas
Do not assume ASCs automatically get a lower category purely because they are not a hospital — the category follows the procedures/anesthesia risk performed there, which can require full Category 1 systems in an ASC just as in a hospital OR
State ASC licensing requirements may layer additional category or documentation requirements on top of the base NFPA 99 risk-assessment approach — confirm state rules in addition to the national code
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?