Sign in

API Modules · CMS-0057F

Five FHIR API surfaces

Every API your payer exposes for member, provider, and B2B use cases. Auth, metering, and observability are shared across all surfaces.

Modules

Click a module to see endpoints, profiles, and quickstart.

Patient AccessLive
42 CFR 422.119(a) · USCDI v3Third-party app developers building member-facing apps.

Members sign in with their payer account; your app reads their claims, clinical data, and coverage via FHIR. SMART App Launch 2.0.0 with patient/*.read.

Read the docs →
Provider DirectoryLive
42 CFR 422.120 · Da Vinci Plan-Net 1.2.0Care navigation, search, and directory apps.

Public, no-auth FHIR endpoints for in-network providers, organizations, locations, networks, plans, and endpoints. CMS-0057F mandates public read.

Read the docs →
Provider AccessLive
42 CFR 422.121 · PDex STU 2.1.0Provider-facing tools and EHR integrations.

Treating providers pull member clinical and claims data through bulk and resource-level FHIR APIs.

Read the docs →
Payer-to-PayerLive
42 CFR 422.119(c) · Da Vinci PDex 2.1.0Payer engineering teams handling enrollment data exchange.

Bulk FHIR transfer between payers with member-match, consent, and provenance preserved end to end.

Read the docs →
Prior AuthorizationBeta
42 CFR 422.122 · Da Vinci CRD / DTR / PASProvider workflow tools and EHR vendors.

Da Vinci CRD, DTR, and PAS surfaces for coverage requirements discovery and electronic prior authorization.

Read the docs →