All insights
CMS & Interoperability 7 min read August 11, 2026

CMS Interoperability and Patient Access: Building Around FHIR

Claims data may sit with a payer. Clinical data may sit inside an EHR. Laboratory results may live elsewhere.

HealthCheck Editorial Team
CMS & Interoperability

Patient access is becoming an API problem

Healthcare data has historically been organized around the systems that generate it.

Claims data may sit with a payer. Clinical data may sit inside an EHR. Laboratory results may live elsewhere.

Patients, however, increasingly expect their information to move with them.

CMS interoperability policy has been pushing healthcare toward a model in which patients can authorize applications to retrieve their information through standards-based APIs.

A central component is the CMS Patient Access API.

What is the CMS Patient Access API?

CMS requires impacted payers to make certain patient information available through a FHIR-based API that can be accessed by a third-party application chosen by the enrollee.

CMS identifies impacted organizations including Medicare Advantage organizations, Medicaid and CHIP programs and plans, and certain Qualified Health Plan issuers.

The required data includes claims and encounter information as well as clinical data maintained by the payer, including laboratory information in applicable circumstances.

Why FHIR?

FHIR provides a standardized way to represent healthcare information.

Rather than requiring every application to understand a unique payer data model, developers can work with common resource structures and implementation guides.

That can make patient-authorized healthcare data more portable.

What changed with CMS-0057-F?

CMS’s Interoperability and Prior Authorization Final Rule builds on the earlier Patient Access requirements.

Among other provisions, CMS requires impacted payers to add certain prior-authorization information to the Patient Access API by January 1, 2027. CMS also requires annual reporting of Patient Access API usage beginning in 2026.

The broader rule also establishes additional API requirements, including Provider Access and payer-to-payer exchange capabilities.

This is important because healthcare interoperability is evolving from a simple patient-download model toward a broader ecosystem of connected payer, provider and patient applications.

Patient access is more than displaying claims

A consumer application can technically retrieve healthcare data and still provide a poor experience.

The harder problem is making that information useful.

A modern healthcare platform may need to:

  • authenticate the patient
  • obtain consent
  • connect the payer
  • ingest FHIR resources
  • normalize terminology
  • reconcile duplicates
  • organize longitudinal information
  • distinguish claims from clinical data
  • update records
  • present understandable information
  • make that data usable in downstream care workflows

This is where infrastructure matters.

HealthCloudOS and patient-authorized data

HealthCloudOS is designed around a longitudinal healthcare-data model in which information from multiple authorized sources can become part of one patient context.

The objective is not simply:

Connect API → Download Data

It is:

Authorize → Retrieve → Normalize → Organize → Use

That patient context can potentially support:

  • health-record navigation
  • care preparation
  • medication review
  • diagnostic workflows
  • preventive reminders
  • AI-assisted record summarization
  • care coordination

CMS interoperability is expanding

CMS continues to emphasize FHIR-based interoperability as part of its broader health-technology strategy.

Its current Interoperability Framework calls for networks to provide or facilitate FHIR API access aligned with US Core and USCDI, including standardized terminology such as LOINC, RxNorm and SNOMED. It also references FHIR subscriptions, document attachments and record-locator functionality.

That direction points toward an ecosystem in which healthcare information becomes increasingly accessible through standards-based infrastructure.

Why consumer-facing platforms should care

Patient access APIs create an opportunity to redesign the patient experience around the individual instead of the institution.

A patient may have relationships with:

  • multiple providers
  • multiple laboratories
  • multiple pharmacies
  • one or more health plans

A healthcare platform can help turn those fragmented relationships into one coherent health story.

From patient access to patient agency

The ultimate objective of interoperability is not the API itself.

It is enabling patients and authorized healthcare services to make better use of information that already exists.

The technology foundation is increasingly clear:

FHIR + Authorization + Standardized Data + Connected Applications

The next challenge is building consumer and clinical experiences that can turn that access into action.

That is where HealthCheck is focused.

Editorial note: This article is educational and does not provide medical, legal, coding, or reimbursement advice. Requirements change; verify the rules that apply to the specific service, patient, professional, payer, and jurisdiction.