Implement patient cost estimation using the AEOB (Advanced Explanation of Benefits) data exchange standard when it becomes effective under the No Surprises Act
domain: cms.gov · 6 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Monitor the CMS rulemaking timeline for the AEOB final rule, which as of mid-2026 remains in proposed rule stage; track the Federal Register for the final rule and effective date before implementing.
When finalized, implement the GFE-to-payer data exchange workflow: the convening provider sends the Good Faith Estimate to the patient's health plan using the FHIR-based GFE coordination workflow.
The payer adjudicates the GFE against the patient's benefits and generates an AEOB that includes the plan's estimated responsibility, the patient's estimated cost-sharing, and the provider network status.
Ensure the AEOB contains the required statutory elements: network status of the provider, the contracted rate or a description of how to find in-network alternatives, a good faith estimate of the plan's payment, the patient's estimated cost-sharing, and medical management disclaimers.
Deliver the AEOB to the patient prior to the scheduled service in the timeframe the final rule specifies; retain a copy for compliance documentation.
Test the end-to-end GFE-to-AEOB workflow in a sandbox environment, validating both the GFE FHIR resources and the AEOB FHIR resources against their respective published profiles.
Known gotchas
The AEOB requirement was not yet in final-rule enforcement status as of mid-2026; implementing based on the proposed rule risks building to specifications that change in the final rule.
The FHIR-based GFE coordination workflow for provider-to-payer exchange is being developed through the Da Vinci project; confirm which version and profile is referenced in the final rule before building against a specific IG version.
AEOBs must be generated even for services where the patient has not requested one if an appointment has been made; plans must build triggers that initiate AEOB generation from scheduling system events, not only from explicit patient requests.
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?