Healthcare has spent years talking about moving beyond fee-for-service. But in chronic care, where success depends on early intervention, continuous monitoring, and coordinated teams, the model still breaks down. Prevention is undervalued, early action is underfunded, and the data needed to measure outcomes remains scattered across disconnected systems.
The CMS ACCESS Model brings those tensions into focus by tying reimbursement to measured chronic disease outcomes, not visits or billing activity. In practice, this means managing complex populations, combining digital and in-person care, and proving results with standardized data.
Direct Medicare beneficiary enrollment reinforces CMS’s push toward patient agency and technology-enabled care, while raising the bar for how data moves across organizations and tools.
Together, these shifts make it clear: outcomes-based care only works if data flows reliably across systems that weren’t built to work together. That’s the real challenge ACCESS exposes, and where interoperability moves from background concern to foundational requirement.
ACCESS makes interoperability operational, not optional
ACCESS is flexible about how care is delivered, but explicit about what must work underneath: automated, secure, and scalable data exchange. Manual reporting, file-based workflows, and one-off integrations won’t meet the bar.
In practice, organizations need to be able to:
- Integrate directly with CMS-hosted APIs for eligibility, enrollment, and reporting
- Support bi-directional clinical exchange through trusted networks to enable co-management
- Automate care coordination workflows, including electronic care plan updates
APIs define how data moves, but ACCESS also assumes something harder: that organizations which don’t already work together can trust and exchange data at scale. Frameworks like TEFCA provide that shared trust layer, enabling coordination without custom agreements.
While structured write-back into EHRs is not explicitly required under ACCESS, in practice it plays a critical role in effective care coordination. The ability to return updates directly into the patient’s chart helps ensure the full care team is working from the same, up-to-date information, reducing gaps, delays, and manual follow-up.
For many teams, the challenge isn’t accessing data; it’s operationalizing it inside real clinical workflows, especially where write capabilities lag behind read access.
What ACCESS changes for organizations already investing in interoperability
ACCESS doesn’t exist in isolation. It builds on years of federal investment in standardized APIs, FHIR-based exchange, and administrative simplification.
ACCESS makes technical expectations explicit. Organizations operating under this model will need to support:
- Clean, normalized, and timely data from many sources; not just EHRs, but devices, digital health tools, and payer systems
- Bi-directional data movement across EHRs, networks, analytics platforms, and care coordination tools
- Ongoing reporting, equity stratification, and compliance, introducing operational complexity, not one-time integration work
Teams that succeed under ACCESS won’t be the ones with the most integrations. They’ll be the ones that can integrate once, scale repeatedly, and adapt as requirements evolve, without rebuilding pipelines every time CMS adds a new data element, partner, or reporting expectation.
Turning ACCESS requirements into working infrastructure
ACCESS makes one thing clear: outcomes-based care only works when data moves automatically, securely, and at scale across a fragmented ecosystem. The policy shift matters, but the real work is operational.
Teams preparing for ACCESS should focus less on whether they can exchange data and more on how reliably that exchange works inside real clinical workflows.
Based on what we see across large-scale implementations, a few principles matter most.
What to prioritize, regardless of platform
- Design for APIs, not files
ACCESS assumes direct integration with CMS-hosted APIs for eligibility, enrollment, and reporting. Manual submissions and batch workflows introduce latency and risk that won’t scale. - Plan for effective data exchange early
In reality, read only data isn’t enough. Care coordination requires real time information exchange with EHRs so insights and care plans reach clinicians where they work. - Treat trust as infrastructure
ACCESS requires organizations that don’t already work together to exchange data at scale. Frameworks like TEFCA provide shared trust without custom agreements. - Normalize data upstream
Outcomes measurement and reporting depend on clean, consistent data. Normalizing HL7, X12, FHIR, and device data early reduces downstream complexity. - Build for change, not one-time compliance
ACCESS requirements will evolve. Invest in repeatable pipelines that adapt as measures, partners, and data sources change, without rebuilding.
If you’re already a Redox customer
The focus is on readiness and scale, not new integrations:
- Validate support to share with an HIE, TEFCA or qualifying network
- Validate support for bi-directional workflows and ideally write-back
- Identify gaps between current data flows and ACCESS reporting needs
- Extend pipelines to devices, digital health tools, and payer data
- Pressure-test observability before volumes increase
For teams considering ACCESS without an interop partner
Use ACCESS planning to stress-test your current approach:
- Are integrations point-to-point or designed to scale?
- How much manual work is required to onboard new data sources?
- Can structured updates flow back into clinical systems?
- How easily can you adapt as CMS requirements change?
Approached this way, ACCESS becomes less about compliance and more about building infrastructure that supports outcomes-based care long-term, regardless of the specific model.
Preparing for ACCESS starts now
CMS has already opened applications for the ACCESS Model, with an initial deadline of April 1, 2026 for the first cohort, followed by rolling admissions.
Organizations considering participation should be evaluating:
- Whether their current data infrastructure can support outcomes-based measurement
- How quickly they can integrate new partners and data sources
- What governance, reporting, and security requirements they’ll need to meet
Even for teams not applying immediately, ACCESS is a clear signal of where Medicare reimbursement is heading, especially for chronic care, digital health, and care coordination.
Whether you’re preparing an application or planning for future participation, ACCESS makes one thing clear: interoperability is no longer a background concern. It’s foundational to how healthcare moves forward.
Redox can help you assess readiness, close interoperability gaps, and build infrastructure that supports outcomes-based care over the long term.
If you’d like to discuss how CMS ACCESS intersects with your strategy, data, or operational roadmap, our team is here to help.