Specify seamless resinous flooring for healthcare clinical spaces
domain: fgiguidelines.org · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Specify a seamless, non-porous resinous system (epoxy or urethane-based) with integral coved wall base in clinical/patient-care areas to meet infection-control cleanability expectations referenced in facility design guidance (e.g., the FGI Guidelines for Design and Construction of Hospitals) — verify the current edition and specific flooring language at fgiguidelines.org before citing a requirement.
Coordinate chemical resistance selection with the facility's actual disinfectant/sanitizer protocol (quaternary ammonium, bleach-based, hydrogen peroxide, etc.), since resinous coatings vary in resistance to specific disinfectant chemistries.
Confirm current facility-engineering requirements for static-dissipative or conductive flooring in specific rooms (e.g., operating rooms) rather than applying an old blanket rule, since the historical driver — flammable anesthetic gases — has diminished with modern anesthesia agents in many facilities.
Plan installation phasing and cure downtime carefully in occupied or partially occupied healthcare facilities, since VOC off-gassing during cure can be a real infection-control and occupant-comfort concern in active clinical space.
Select slip resistance (per current ANSI A326.3 DCOF classification) appropriate to wet areas like patient bathing rooms, balancing slip safety against cleanability.
Known gotchas
Don't assume every operating room still requires conductive flooring — that requirement was tied to flammable-anesthetic-gas risk that has diminished with modern agents; confirm the current facility engineering requirement rather than applying an outdated blanket rule.
Verify the current FGI Guidelines edition and specific flooring language directly at fgiguidelines.org rather than citing a remembered requirement, since editions are periodically updated.
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?