Determine the outlet/inlet testing sequence a verifier performs before a medical gas system is placed into use
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 general test sequence: initial pressure/leak test, cross-connection test, gas concentration/purity test, particulate/contaminant test, then terminal unit flow/pressure test — confirm exact ordering and full list against the current NFPA 99 edition text
Confirm the cross-connection test method: with all systems at atmospheric pressure, one system at a time is charged with nitrogen NF (commonly cited to 50 psig) while every other system/terminal is checked to confirm no test gas appears anywhere except the charged system
Confirm the gas concentration test analyzes each medical gas/medical air terminal for correct gas identity and concentration against NFPA 99 purity criteria, performed only after the cross-connection test passes
Confirm medical air is additionally tested for dew point and contaminants (oil, particulates, carbon monoxide, etc.) against NFPA 99 criteria
Confirm labeling/identification at each outlet/inlet is verified to match the correct system as part of the test sequence, and that all tests must be completed and documented in a verification report before the system is approved for patient use
Known gotchas
The cross-connection test must be performed before the gas concentration test — running them out of order invalidates the verification
This full battery of tests is the qualified verifier's (ASSE 6030) responsibility, distinct from the installer's own initial pressure test, which is witnessed but not a substitute for verification
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?