Provider Access API

5 min read
Provider AccessCMSDa VinciFHIR API

Provider Access API

The Provider Access API is a CMS-mandated FHIR-based API through which payers must share member health data with in-network providers who have a treatment relationship with the member. The goal is to improve care coordination by giving providers access to claims, clinical, and coverage data across payers.

Regulatory Mandate

  • Required by CMS-0057-F (Interoperability and Prior Authorization Final Rule)
  • Compliance deadline: January 1, 2027
  • Applies to MA organizations, Medicaid/CHIP managed care, and QHP issuers

Required Data

Payers must share the following with in-network providers via FHIR API:

  • Claims and encounter data — Adjudicated claims including diagnoses, procedures, and costs
  • Clinical data — Conditions, medications, allergies, lab results, vital signs, procedures (USCDI data classes)
  • Prior authorization decisions — Status, approval/denial, and supporting information
  • Coverage information — Member's current coverage details

Consent Model

The Provider Access API uses an opt-out model:

  • Members are enrolled by default — their data is shared with treating providers unless they opt out
  • Payers must inform members of their right to opt out
  • Members can opt out at any time and at any level of granularity the payer supports
  • If a member opts out, the payer must stop sharing their data with providers through this API

This differs from the Patient Access API (member-initiated) and Payer-to-Payer API (member opt-in).

Technical Implementation

Standards

  • Da Vinci PDex IG — Primary implementation guide
  • US Core IG — Clinical data profiles
  • FHIR R4 — Base standard
  • SMART Backend Services — Server-to-server authorization (system-level access, no user login)

Provider Attribution

Payers must have a mechanism to determine which members are attributed to or have a treatment relationship with a given provider. This enables the provider to request data only for their patients.

Bulk FHIR Data Access

For providers managing large patient panels, the API must support FHIR Bulk Data operations:

  • $export — Asynchronous export of data for attributed members
  • NDJSON format for efficient data streaming

Benefits

  • Longitudinal patient view — Providers see the patient's complete clinical and claims history across all payers
  • Reduced duplication — Prevents redundant tests and procedures
  • Better care transitions — Hospital discharge data available to follow-up providers
  • Quality improvement — Supports quality measurement and value-based care programs

Ready to get started?

See how UnifyHealth can help your organization streamline healthcare data integration and meet CMS interoperability requirements.

Request a Demo
base44
Edit with Base44