Documentation Was Always the Foundation. The ACCESS Model Just Made That Official

For years, health system leaders have heard that documentation matters mostly because it protects revenue and reduces clinician burden. Both are true. But the CMS Innovation Center's new ACCESS model changes the calculation more fundamentally. The model has been in effect since July 1, 2026, and CMS marked its public launch in September, timed to Health Aging Month, when the ACCESS Participation Directory went live on Medicare.gov and CMS leadership convened providers, payers, and clinical societies to walk through how it works.

Under ACCESS, Medicare no longer pays organizations primarily for the services they deliver. It pays them for whether patients get healthier, measured against guideline-informed targets for conditions like hypertension, diabetes, chronic kidney disease, musculoskeletal pain, depression, and anxiety.

That shift puts clinical documentation in a different position than it has occupied for most of the last two decades. Documentation is no longer just the record of what happened in a visit. Under an outcome-aligned payment structure, it becomes the evidence base an organization uses to demonstrate that a patient's blood pressure came down, that a PHQ-9 score improved, or that a chronic condition moved toward control.

For CIOs and CMIOs planning their organization's participation in ACCESS or watching how it reshapes value-based contracting more broadly, documentation infrastructure deserves a closer look than it has typically received.

What the ACCESS Model Asks of Health Systems

ACCESS organizes chronic disease management into four tracks, with partial recurring payments for managing a condition and full payment contingent on demonstrating measurable improvement or control across a participating organization's patient population. More than 150 organizations were accepted for the model's launch, with roughly 40 available in the participant directory as of the September public launch and more added on a rolling basis. CMS has said the model's reach will extend to roughly three in four Medicare beneficiaries as additional tracks for heart failure, COPD, and substance use disorders are added beginning spring 2027.

The Four ACCESS Tracks

• Early cardio-kidney-metabolic: hypertension, dyslipidemia, obesity, and prediabetes

• Cardio-kidney-metabolic: diabetes, chronic kidney disease, and atherosclerotic cardiovascular disease

• Musculoskeletal: chronic musculoskeletal pain

• Behavioral health: depression and anxiety, measured through tools like the PHQ-9 and GAD-7

Two design details matter most for health systems already managing InstaNote and InstaCode workflows.

First, ACCESS explicitly requires participating organizations to share care plans and updates with primary care and referring clinicians, and it introduces a new billing code for the co-management work that requires documented review activity.

Second, the behavioral health track ties payment to standardized, serial measurement rather than clinical judgment alone. In both cases, the requirement is the same: documentation has to be complete, structured, and available to the right people at the right time, not just accurate enough to support a single visit note.

Where InstaNote Fits

This is the part of the model that should feel familiar to any health system already running InstaNote. Ambient documentation was built to solve a narrower problem: giving clinicians back the time they lose to manual note-taking while producing a more complete, more accurate clinical record. That record, with documentation accuracy at 99% and providers reporting 90% satisfaction across DeliverHealth's platform, was already the raw material a health system needed to support quality reporting, risk adjustment, and value-based contracts. ACCESS simply raises the stakes for how consistently that raw material must be captured.

A hypertension track under ACCESS depends on a clinician documenting the blood pressure reading, the medication response, and the follow-up plan at every relevant encounter, not just the readings that happen to make it into a structured field. A behavioral health track depends on PHQ-9 and GAD-7 scores being captured consistently enough to show a trend line CMS will accept as evidence of improvement.

Health systems that rely on clinicians to manually document these details after the visit, often from memory, at the end of a long day, are introducing exactly the kind of variability that puts outcome-aligned payment at risk. Ambient documentation reduces that variability by capturing the encounter as it happens, so the chronic disease data an outcome-based model depends on is more likely to be complete and timely enough to support the co-management updates ACCESS now requires between primary care and participating organizations.

None of this requires a health system to treat InstaNote as an ACCESS-specific tool. It works the same way it always has. What changes is the value that consistent, complete documentation now carries. Under fee-for-service, a missed detail in a note was a compliance risk. Under ACCESS, a missed detail is a data gap that can affect whether an organization gets paid at all.

The Connection to Coding and to the Middle of the Revenue Cycle

DeliverHealth has positioned InstaNote and InstaCode around a four-step pipeline: capture, structure, code, execute. That pipeline sits deliberately in the middle of the revenue cycle, between the clinical encounter and claim submission, because documentation quality determines everything downstream. ACCESS makes that middle stretch more visible to health system leadership than it has been in years.

Outcome-aligned payment does not eliminate coding. Organizations still need accurate coding to establish the baseline conditions against which a patient is being tracked, and the new co-management billing code introduced under ACCESS is itself a coding requirement tied directly to documented review activity. What changes is that coding accuracy and documentation completeness are no longer separable concerns handled by different departments on different timelines.

A health system that captures a complete, structured encounter through InstaNote and carries that structure into coding through InstaCode is better positioned to support both the co-management billing ACCESS introduces and the outcome reporting the model's payment methodology depends on. A health system that manages those steps as disconnected processes will find the gaps between them harder to defend when CMS reviews whether a patient population actually improved.

What This Means for Planning

CIOs evaluating ACCESS participation, or evaluating how their existing value-based contracts will evolve alongside it, should treat documentation infrastructure as a planning input rather than an afterthought. A few practical questions are worth asking internally before committing to a track:

• Is chronic disease documentation consistent across the clinicians and care sites contributing to a given track?

• Does the documentation workflow support the kind of serial, structured measurement that behavioral health and cardio-metabolic tracks require?

• Can care plan updates reach primary care and referring clinicians in a form that supports the co-management billing ACCESS has built in, rather than as an unstructured note that has to be manually reviewed?

These are not new questions for organizations that have been building toward value-based care for years. What ACCESS does is attach a specific payment mechanism, a ten-year program horizon, and a defined set of clinical tracks to work that many health systems have approached more generally until now. That specificity is useful. It gives CIOs and CMIOs a concrete standard to plan against rather than a general direction to move toward.

DeliverHealth's platform, spanning documentation and coding across more than 550 health systems and 40,000 providers, was built around the premise that the middle of the revenue cycle is where clinical accuracy and financial accountability meet. The ACCESS model did not create that premise. It confirmed it and gave health systems a clear, near-term reason to make sure their documentation infrastructure is ready for what outcome-based payment actually requires.