Implement a 90-day provider directory verification workflow to comply with No Surprises Act health plan directory requirements
domain: healthcare · 6 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Confirm the obligation: the No Surprises Act requires health plans/issuers to verify and update online provider directory data (name, specialty, address, phone, network status) at least every 90 days, with no exemption by provider or facility category.
Build an outreach/attestation cycle that contacts each in-network provider or facility at least once every 90 days to confirm or correct directory data.
When a provider submits updated information, publish the correction to the public directory within 2 business days of receipt.
Define a documented non-response policy specifying how long an unverified listing may remain published before it is flagged as unverified or removed.
Log every verification attempt, response, and directory change for audit purposes, since both providers (up to $10,000 per violation) and plans (up to $100 per day per affected individual) face separate penalty exposure.
Reconcile the directory against claims and prior-authorization systems so members relying on published network status have a defensible basis if the directory was inaccurate.
Known gotchas
The 90-day cycle is a floor, not a ceiling — some state laws or internal plan policies require more frequent verification.
Provider-submitted updates must flow to the public directory within 2 business days regardless of where the plan is in its 90-day cycle — don't batch all updates to the quarterly cadence.
Silence from a provider is not compliance — plans need a documented non-response/removal policy rather than leaving stale, unverified listings published indefinitely.
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?