CMS ACCESS Model API
0.9.0 - ci-build
CMS ACCESS Model API
0.9.0 - ci-build
CMS ACCESS Model API - Local Development build (v0.9.0) built by the FHIR (HL7® FHIR® Standard) Build Tools. See the Directory of published versions
| Official URL: https://dsacms.github.io/cmmi-access-model/ | Version: 0.9.0 | |||
| Draft as of 2026-03-06 | Computable Name: CMSAccessAPI | |||
Welcome to the CMS ACCESS Model API Implementation Guide. This comprehensive guide covers all APIs for the CMS ACCESS (Advancing Chronic Care with Effective, Scalable Solutions) Model.
The ACCESS Model aims to modernize chronic condition management across Medicare by testing a value-based payment system that prioritizes health outcomes, clinical accountability, and patient empowerment. It enables care organizations to use a wide range of technology-supported tools — including virtual care, remote monitoring, digital therapeutics, and coordinated team-based services — that are often difficult to bill under traditional fee-for-service Medicare.
For more information about the CMS ACCESS Model, please see the ACCESS Model website.
This IG consolidates guidance for all ACCESS Model APIs into a single comprehensive resource, providing:
This Implementation Guide covers four primary APIs: the Eligibility API, the Alignment API, the Unalignment API, and the Data Reporting API (to be added in a subsequent release of this IG).
This API allows participants to quickly determine if a patient meets the basic eligibility criteria for participation in the ACCESS model.
Key Operations:
$check-eligibility - Submit eligibility check request$submission-status - Check status of eligibility requestLearn more about the Eligibility API in the ACCESS API Operations Manual.
This API aligns eligible patients to participants within specific ACCESS Model tracks. When a patient is aligned to an ACCESS Model track, a subscription is created to provide event notifications related to the patient to the participant. This subscription will provide information on the patient’s status throughout the ACCESS Model and provide valuable reminders.
Key Operations:
$align - Submit alignment request$submission-status - Check status of alignment requestAdditional Features:
Learn more about the Alignment API in the ACCESS API Operations Manual.
This API allows a participant to manually unalign a patient from the ACCESS Model track due to specific approved reasons such as patient relocation or loss of contact.
Key Operations:
$unalign - Submit unalignment request$submission-status - Check status of unalignment requestLearn more about the Unalignment API in the ACCESS API Operations Manual.
This API allows a participant to submit required data reporting information for patients aligned to the ACCESS Model to support program evaluation and performance measurement.
Key Operations:
$report-data - Submit data report$submission-status - Check status of data submissionAll APIs support the following ACCESS Model tracks:
[base] - replace these with your actual API endpointAPI Developers: Review the Operations Manual for detailed implementation patterns, then examine the operation definitions in Artifacts.
Integration Architects: The Operations Manual contains sequence diagrams showing the asynchronous pattern and system interactions.
QA/Testing Teams: Use the example instances in Artifacts to understand expected responses, and see the Testing Guide in the Operations Manual for test scenarios.
Compliance/Security Teams: The Operations Manual includes Security Considerations for authentication, TLS requirements, and data handling practices.
This IG assumes familiarity with:
Core FHIR Concepts:
US Core Profiles:
Additional FHIR Resources (for Data Reporting API):
Subscriptions (for Alignment API):
Security:
These are the contributing organizations which drive the guidance in this IG:
For more information contact Dave Hill (david.h[at]globalalliantinc.com).
There are no Global profiles defined
Package hl7.fhir.uv.extensions.r4#5.2.0 This IG defines the global extensions - the ones defined for everyone. These extensions are always in scope wherever FHIR is being used (built Mon, Feb 10, 2025 21:45+1100+11:00) |
Package hl7.fhir.uv.extensions.r4#1.0.0 This IG defines the global extensions - the ones defined for everyone. These extensions are always in scope wherever FHIR is being used (built Sun, Mar 26, 2023 08:46+1100+11:00) |
Package hl7.fhir.uv.bulkdata#2.0.0 FHIR based approach for exporting large data sets from a FHIR server to a client application (built Fri, Nov 26, 2021 05:56+1100+11:00) |
Package hl7.fhir.uv.sdc#3.0.0 The SDC specification provides an infrastructure to standardize the capture and expanded use of patient-level data collected within an EHR. |
Package ihe.formatcode.fhir#1.1.0 Implementation Guide for IHE defined FormatCode vocabulary. (built Thu, Feb 24, 2022 16:55-0600-06:00) |
Package hl7.fhir.us.core#6.1.0 The US Core Implementation Guide is based on FHIR Version R4 and defines the minimum conformance requirements for accessing patient data. The Argonaut pilot implementations, ONC 2015 Edition Common Clinical Data Set (CCDS), and ONC U.S. Core Data for Interoperability (USCDI) v1 provided the requirements for this guide. The prior Argonaut search and vocabulary requirements, based on FHIR DSTU2, are updated in this guide to support FHIR Version R4. This guide was used as the basis for further testing and guidance by the Argonaut Project Team to provide additional content and guidance specific to Data Query Access for purpose of ONC Certification testing. These profiles are the foundation for future US Realm FHIR implementation guides. In addition to Argonaut, they are used by DAF-Research, QI-Core, and CIMI. Under the guidance of HL7 and the HL7 US Realm Steering Committee, the content will expand in future versions to meet the needs specific to the US Realm. These requirements were originally developed, balloted, and published in FHIR DSTU2 as part of the Office of the National Coordinator for Health Information Technology (ONC) sponsored Data Access Framework (DAF) project. For more information on how DAF became US Core see the US Core change notes. (built Fri, Jun 30, 2023 14:02+0000+00:00) |
Package hl7.fhir.us.carin-bb#2.1.0 CARIN Consumer Directed Payer Data Exchange (CARIN IG for Blue Button®) (built Tue, Feb 18, 2025 17:31+0000+00:00) |
Package hl7.fhir.uv.tools.r4#0.9.0 This IG defines the extensions that the tools use internally. Some of these extensions are content that are being evaluated for elevation into the main spec, and others are tooling concerns (built Tue, Dec 16, 2025 23:18+1100+11:00) |
This is an R4 IG. None of the features it uses are changed in R4B, so it can be used as is with R4B systems. Packages for both R4 (cms.fhir.us.access.r4) and R4B (cms.fhir.us.access.r4b) are available.
This publication includes IP covered under the following statements.
