---
title: The CMS ACCESS Interoperability Playbook | Metriport
description: A practical guide to HIE connectivity, FHIR reporting, and care coordination for CMS ACCESS Model participants. Download the playbook.
image: https://go.metriport.com/hubfs/access-requirements-key-image-v2.png
---

[![Metriport Logo Black](https://go.metriport.com/hubfs/Metriport%20Logo%20Black.png)](https://metriport.com)

[GET A DEMO](https://metriport.com/contact-us)

 FOR CMS ACCESS PARTICIPANTS

# The ACCESS Interoperability Playbook

### A practical guide to HIE connectivity, care coordination, and FHIR reporting for CMS ACCESS Model participants.

The ACCESS Model rewards outcomes. But outcomes can't be measured (or paid) without complete, auditable clinical data. This guide explains how the Health IT requirements work, why interoperability is foundational to compliance, and what you need to have in place before your patients are aligned.

 UNDERSTANDING THE REQUIREMENTS

## ACCESS includes three interoperability requirements

The ACCESS Model introduces three Health IT requirements. The challenge isn't any single one. It's making them work as a system.

REQUIREMENT 01

### Standardized APIs

FHIR-based APIs supporting patient and population services.

REQUIREMENT 02: THE BRIDGE

### HIE Connectivity

Bidirectional exchange across the geographies where you deliver care.

REQUIREMENT 03

### CMS Reporting

FHIR-based submission of outcomes and supporting clinical data.

![git-merge-icon](https://go.metriport.com/hs-fs/hubfs/git-merge-icon.png?width=20&height=20&name=git-merge-icon.png) HIE connectivity is the bridge that makes the APIs and reporting work together.

 

 INSIDE THE PLAYBOOK

## Four sections. Everything you need to know.

**01. The Rise of Value-Based Care**  
How outcome-aligned payment models led to ACCESS, and what the shift means for how participants prove results.

---

**02. The Three HIT Requirements**   
A clear explanation of what CMS requires for standardized APIs, HIE connectivity, and FHIR-based reporting, including the details that are easy to miss.

---

**03. The Compliance Checklist**   
Six concrete steps, organized by deadline, to help participants identify gaps and prioritize workstreams before key dates pass.

---

**04. The Data Imperative**   
Why incomplete patient records are a compliance liability, not just a clinical one, and how auditable data is the foundation of every ACCESS payment.

---

 

“Cercanos was built on value-based care, so when CMS announced ACCESS, we knew it was a perfect fit. Metriport was the obvious partner to work with: HIE connectivity, network reciprocity, and the clinical depth that value-based care requires.”

![Jaun Estrada MD](https://go.metriport.com/hubfs/Jaun%20Estrada%20MD.jpeg)

CEO & CO-FOUNDER, CERCANOS CARE Juan Estrada, MD

 

Cercanos Care is a CMS ACCESS first-cohort participant serving Hispanic communities across cardiometabolic and behavioral health.

 BUILT FOR IMPLEMENTATION

## Designed for teams building ACCESS infrastructure

 This guide was written for the people responsible for making ACCESS work in practice.

Health IT leaders

Heads of interoperability, CMIOs, and the leaders accountable for this data layer.

Engineering & ops

CTOs, CIOs, and technical founders building the connectivity and pipelines.

Compliance & strategy

Program owners and clinical operations leaders planning the path to compliance.

 KEY QUESTIONS ANSWERED

## Plan your path to compliance

✓  What does ACCESS require from an interoperability perspective?

---

✓  Do we need a national HIE connection?

---

✓  How does bidirectional exchange work under ACCESS?

---

✓  Can lab values come from an HIE?

---

✓  What data must be source-verifiable?

---

✓  What are the most common implementation gaps?

---

✓  How should digital health companies approach connectivity?

---

 

![ACCESS Playbook Cover](https://go.metriport.com/hs-fs/hubfs/ACCESS%20Playbook%20Cover.png?width=1545&height=2000&name=ACCESS%20Playbook%20Cover.png "ACCESS Playbook Cover")

 IMPLEMENTATION RESOURCE

## Download the ACCESS Interoperability Playbook

Get a practical guide to:

✓ ACCESS Health IT requirements

✓ HIE connectivity strategies

✓ Care coordination obligations

✓ FHIR reporting requirements

✓ Compliance planning

 FOR DIGITAL HEALTH ORGANIZATIONS

## Built for ACCESS participants

Drawn from CMS guidance, implementation specs, and lessons from the first ACCESS cohort.

Digital health platforms

Virtual care

Remote monitoring

Care management

Chronic care programs

AI-enabled care

 ABOUT METRIPORT

## Focused on the interoperability challenges behind ACCESS

The ACCESS Model depends on complete, auditable patient data and reliable care coordination workflows. Metriport provides a single FHIR-native API for accessing and exchanging clinical data across national and regional networks, helping organizations support outcomes measurement, care coordination, and CMS reporting requirements.

![Diagram of Metriport's FHIR-native API as a central hub: inbound data from EHRs, hospitals, labs, and pharmacies flows in, and outbound connections reach care teams, referring providers, CMS reporting, and digital health platforms.](https://go.metriport.com/hs-fs/hubfs/metriport-fhir-hub-diagram.png?width=2000&height=733&name=metriport-fhir-hub-diagram.png "Diagram of Metriport's FHIR-native API as a central hub: inbound data from EHRs, hospitals, labs, and pharmacies flows in, and outbound connections reach care teams, referring providers, CMS reporting, and digital health platforms.")

---

This guide is intended to support organizational readiness planning for the CMS ACCESS Model. It does not constitute legal, regulatory, or compliance advice. Organizations should review the official CMS ACCESS Model [documentation](https://www.cms.gov/priorities/innovation/files/access-rfa.pdf) and consult internal compliance stakeholders as appropriate.

![Metriport Logo White](https://go.metriport.com/hubfs/Metriport%20Logo%20White.png)

Metriport  
48 Colin P Kelly Jr St  
San Francisco, CA 94107

© 2026 Metriport All rights reserved [Privacy Policy](https://www.metriport.com/privacy-policy)

[Powered by Atlas - a B2B SaaS HubSpot theme](https://www.kalungi.com/atlas-hubspot-theme-for-b2b-saas-software)