CMS ACCESS Model Creates 10-Year Revenue Stream for Chronic Care Tech

CMS Ties Medicare Revenue to Technology-Enabled Chronic Care

The CMS Innovation Center will launch the ACCESS Model (Advancing Chronic Care with Effective, Scalable Solutions) in July 2026, a voluntary 10-year payment program that pays Medicare Part B providers recurring revenue for using digital tools to manage chronic conditions. The duration is long enough to underpin multi-year IT investments, and the policy shifts remote patient monitoring, care coordination platforms, and patient engagement tools from cost centers to revenue-linked infrastructure.

ACCESS applies to physicians and outpatient organizations managing chronic disease panels under Medicare Part B. While CMS has not published per-patient rates, the model sits alongside existing chronic care management CPT codes that currently reimburse approximately $40–60 per patient per month. That economic frame gives buyers a predictable benchmark: technology that activates ACCESS-eligible workflows can be justified against PMPM reimbursement streams already familiar to finance teams.

The competitive landscape now favors vendors that can demonstrate CMS-aligned chronic care workflows and documentation out of the box. Remote patient monitoring platforms—Teladoc Health's Chronic Care suite, Omada Health, Cadence, Welldoc, and EHR-native RPM modules from Epic and Oracle Health—compete directly for ACCESS-eligible workflows. Population health and care coordination vendors including Epic Healthy Planet, Oracle Health's population health tools, and Azara Healthcare gain a clear revenue justification. AI-enabled care navigation platforms such as b.well's bailey health assistant become reimbursable if they enable ACCESS-compliant chronic care management.

Budget impact: CIOs and CFOs can now tie chronic-care IT spending directly to recurring Medicare revenue. Organizations that delay chronic-care infrastructure modernization risk missing a decade of incentivized payments and falling behind on chronic disease management benchmarks that CMS will measure. RFP language will increasingly require proven workflows for ACCESS use cases, audit-friendly documentation, and outcomes reporting aligned with CMS standards. Vendors unable to show compliant workflows or integrations face procurement risk in 2026–27 cycles.

ONC HTI-5 Rule Replaces EHR Function Checklists with API Certification

On December 22, 2025, the Office of the National Coordinator for Health IT released the HTI-5 Proposed Rule, which would withdraw or revise more than half of existing technical and interoperability requirements for certified EHR technology. The rule replaces prescriptive EHR functionality checklists with API-focused certification, aiming to improve patient access to electronic health information and unlock third-party AI innovation. The public comment period runs through February 27, 2026.

HTI-5 shifts the competitive landscape toward EHR platforms that can meet API-centric certification quickly and at scale. Core vendors—Epic, Oracle Health, MEDITECH, Allscripts/Veradigm, athenahealth, Greenway Health, AdvancedMD—must demonstrate FHIR API maturity and governance, not just clinical module coverage. API-first and FHIR-native platforms gain a clearer regulatory path. AI vendors whose products depend on structured, real-time EHR data access through APIs—Ambience Healthcare for documentation, CharmHealth's MCP server for safe EHR data exposure to AI agents, Greenway Health's Agentic AI Factory built with AWS—benefit from the rule's emphasis on interoperability over monolithic certification.

Platform strategy: Buyers must stress-test EHR and ancillary vendors on API maturity, FHIR coverage, and governance rather than clinical module checklists. This may accelerate EHR consolidation around Epic, Oracle Health, and MEDITECH, which already operate large third-party API ecosystems. Vendors slow to adapt face certification risk, which is material for organizations relying on certified EHR technology for incentive programs. Buyers will insert contract clauses around API availability, change management, and compliance with HTI-5-aligned standards.

Budgeting shift: HTI-5 gives CIOs a policy basis to reallocate budget from custom interfaces and point-to-point integrations toward standardized API infrastructure and FHIR app ecosystems. The rule also updates information blocking regulations to support third-party innovation, reducing the legal and technical friction that has historically made EHR data access expensive and slow.

What to Watch

ACCESS and HTI-5 are not isolated policy changes—they reinforce each other. ACCESS requires interoperable, tech-enabled chronic care workflows. HTI-5 makes those workflows easier to build and certify through APIs. Organizations that treat these as separate compliance exercises will waste budget on redundant integrations and miss the structural advantage: a certified, API-connected EHR that can plug into ACCESS-eligible chronic care platforms without custom work.

Vendors that cannot demonstrate both CMS workflow alignment and API-first architecture will face procurement headwinds starting in mid-2026. Buyers should require vendors to map their roadmaps to both ACCESS eligibility and HTI-5 API certification timelines in current contract negotiations. The 10-year ACCESS horizon and the >50% revision of EHR certification criteria represent a rare alignment of payment policy and technical standards—organizations that move early can justify infrastructure investments against a decade of predictable revenue.