integrate with a payer Patient Access API under the CMS interoperability rule (Da Vinci / CARIN)

domain: payer-patient-access · 6 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗

Steps

  1. Discover the payer's Patient Access API endpoint; CMS-regulated payers must publish their FHIR R4 base URL and SMART configuration—look for it in their developer portal or via the CMS endpoint directory.
  2. Register your application with the payer's developer portal, requesting SMART scopes aligned with CARIN Blue Button IG (e.g. patient/ExplanationOfBenefit.read, patient/Coverage.read, patient/Patient.read).
  3. Implement the SMART on FHIR standalone launch flow so members can authenticate with their health plan credentials and grant your app access.
  4. After obtaining a token, retrieve ExplanationOfBenefit resources for claims history, Coverage for current plan details, and Patient for demographic data.
  5. Handle the CARIN BB profile-specific extensions on ExplanationOfBenefit (e.g. inNetworkProvider, adjudicationCategory) when parsing claim line items.
  6. For provider-facing workflows, explore the Da Vinci Payer Data Exchange (PDex) and Prior Authorization Support (PAS) IGs which use different resource types and flows.

Known gotchas

Related routes

Expose a CMS Interoperability Patient Access API conforming to CMS final rule requirements
hl7.org/fhir/us/carin-bb · 5 steps · unrated
Understand the CMS Interoperability and Patient Access final rule API requirements for payers
cms.gov · 6 steps · unrated
Implement a CMS Patient Access API (CMS-9115 / CMS Interoperability Rule) compliant FHIR endpoint that serves member claims, clinical, and formulary data to authorized third-party apps via SMART on FHIR
cms.gov · 5 steps · unrated

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?

We author + individually verify a route for your exact task within 24h. Custom route — $25 · Teams: Pilot — $750/mo · all plans