Retrieve a Medicare beneficiary's Part A, B, and D claims history using the CMS Blue Button 2.0 FHIR API
domain: bluebutton.cms.gov · 6 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Register a developer account and application in the Blue Button 2.0 sandbox
Implement OAuth 2.0 authorization code flow so a beneficiary can grant your app access to their claims data
Use the v2 FHIR R4 endpoints, based on the CARIN Consumer Directed Payer Data Exchange implementation guide, to query ExplanationOfBenefit, Coverage, and Patient resources
Test end-to-end flows against synthetic sandbox data before requesting production access
Follow the production access user guide to move from sandbox to live beneficiary data
Use the provided Node/Python SDKs to manage OAuth token refresh
Known gotchas
v1 (STU3) is limited to bug-fix maintenance -- new integrations should build on v2 (FHIR R4), not v1
Data is scoped to what CMS has adjudicated for Medicare Part A/B/D, not real-time eligibility or supplemental/Medigap coverage
Production access is a distinct approval step beyond sandbox registration, and every data pull is gated by beneficiary-granted OAuth consent, not open account-level access
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?