Determine simplified Category 3 medical gas/vacuum requirements applicable to a typical dental office
domain: nfpa.org · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Confirm Category 3 applies to facility systems whose failure is not likely to cause patient/caregiver injury but may cause discomfort — the category commonly applicable to dental offices offering minimal or no sedation, using dental air (to drive handpieces) and dental vacuum (oral evacuation) only
Confirm Category 3 requirements are comparatively simpler — no requirement for continuous monitoring or advanced redundancy — while still requiring documented system classification, periodic review, and maintenance per manufacturer instructions
Confirm daily operational procedures still apply, such as a documented procedure for shutting off gas supply at cylinder valves at the end of each day
Confirm that if a dental office adds or increases sedation/general anesthesia services, an existing Category 3 system is not sufficient — the practice must reassess risk category and upgrade the system to meet Category 1 or 2 requirements as applicable
Confirm with the state dental board and/or AHJ whether any state-specific dental office code amendments apply on top of NFPA 99 base requirements
Known gotchas
Category 3 is tied to the level of sedation/anesthesia actually offered — a dental office cannot assume it stays Category 3 if it begins offering higher levels of sedation without reassessing and upgrading its gas system
'Simpler' does not mean 'unregulated' — Category 3 still requires documented classification, periodic review, and defined shutdown procedures, not a code exemption
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?