If your organization is sizing the economics of the CMS ACCESS Model, one question decides more than any other: once a beneficiary is aligned to you, what can you still bill Medicare fee-for-service for that person?
There are two rules in CMS's documents that bear on it. They sit four pages apart in the same PDF, they both exist to stop Medicare paying twice for the same care, and one of them is scoped for the same condition while the other is not. They are different instruments with different force, and the difference is the whole answer.
Everything below is quoted from CMS with the page number attached, so you can check us in one click rather than taking our word for it.
From the ACCESS Request for Applications, version 1.1, page 33:
> To preserve model integrity and prevent duplicative Medicare payments, ACCESS Participants and their affiliated entities may not submit Medicare FFS claims (directly, or indirectly through another organization for which they provide contracted services) for aligned beneficiaries during active care periods. Medicare claims processing systems will incorporate automatic controls that suppress FFS billing from ACCESS Participants for aligned beneficiaries during their care periods.
Note the noun that clause attaches to. It is the beneficiary. There is no qualifying condition, no track, no service category — and the certification an officer actually signs, at page 50 of the same document, uses the same words:
> ☐ I certify that neither our organization nor our financially affiliated entities will bill Medicare fee-for-service for aligned beneficiaries during an ACCESS care period
CMS's Technical FAQ states the scope rule in the plainest words it uses anywhere:
> The FFS Exclusion applies at the beneficiary level for a given ACCESS participant.
And the ACCESS model page puts the same rule in operational terms:
> ACCESS Participants and their affiliated entities may not submit Medicare Fee-For-Service (FFS) claims … for other services furnished to their ACCESS-aligned beneficiaries during an active care period. Only ACCESS G-codes may be billed for aligned beneficiaries during active care periods.
One wording note, because you will meet it: the RFA and the signed certification say bare "for aligned beneficiaries," while the FAQ and the model page say "for other services." Read absolutely literally, the RFA's phrasing would bar the ACCESS G-codes themselves, which cannot be the intent — so "other services" is the operative reading and the RFA is blunt rather than contradictory. We are flagging it rather than smoothing it over, because if you open only the RFA you will see a stricter string than the one we just quoted and reasonably wonder who softened it.
Four pages earlier, at RFA pages 29–30, a different mechanism appears:
> Each clinical track includes a Substitute Spend List identifying services considered substitutes if provided by another Medicare entity for the same condition. … CMS will compare each participant's Substitute Spend Rate (SSR) — the percentage of aligned beneficiaries who did not receive listed substitute services from other Medicare providers or suppliers for the same condition during their ACCESS care period — to a defined Substitute Spend Threshold (SST) … This adjustment applies only to payments made to ACCESS Participants. Care provided by non-ACCESS entities for services on the Substitute Spend List will continue to be reimbursed under standard Medicare payment rules.
That is a genuinely condition-scoped rule, and the phrase "for the same condition" appears in it twice on one page. But look at what it does. It does not prohibit anything. It observes what other Medicare entities bill for a listed set of services, and prices that back to the participant as a payment adjustment — a capped one, per the same passage, and one that touches only the participant's own payments.
Side by side:
| FFS Exclusion | Substitute Spend Rate | |
|---|---|---|
| Who it binds | the Participant and its affiliated entities | other Medicare entities' activity, priced back to the Participant |
| Scope | the beneficiary — all other services | the same condition — a listed set of services |
| Force | hard prohibition, with automatic claims suppression | a capped downward payment adjustment |
| Where | RFA p.33 | RFA pp.29–30, Appendix E |
If you are modelling ACCESS economics from the phrase "for the same condition," it is worth checking which of these two you have in hand. They are four pages apart, they use similar language about duplicate payment, and only one of them stops a claim.
We left this half out of our own first reading of the rule, and leaving it out makes an accurate summary practically wrong for a large group of readers.
It does not restrict the beneficiary. From the same RFA paragraph, page 33:
> Restrictions do not limit beneficiary choice in seeking care from other health care providers, with any applicable payment adjustments applied to Medicare payments rather than restrictions on beneficiary access.
It does not capture the patient's other doctors. CMS's page for primary care providers and referring clinicians answers this directly:
> Does referring a patient to ACCESS change my relationship with them? No. Your patient can continue to see you and any other health care provider that accepts Medicare.
That page also confirms a referring clinician does not need to apply to or enroll in the model to refer patients or to bill the model's Co-Management Payment — CMS built a paid path for clinicians who stay outside it. The amounts are on that CMS page; we are not going to restate them here, because payment figures move and you should read them from the source that sets them.
And reassignment alone does not make a clinician an affiliate. The affiliation definition at RFA p.33 includes reassignment relationships under 42 CFR § 424.80, which reads alarmingly if you stop there. The Technical FAQ does not stop there:
> In the case of reassignment relationships, the exclusion applies only to organizations, not to individual clinicians. An individual clinician who reassigns billing rights to an organization does not, by that reassignment alone, become an affiliate for purposes of the FFS Exclusion.
If you are a clinician who has been told that reassigning billing rights to an ACCESS participant will end your other Medicare billing, that sentence is the one to read — and it is CMS's, not ours.
Two practical consequences, and neither of them is a reason for alarm.
The unit of analysis is the patient, not the diagnosis. If you model the exclusion per condition, you will count revenue from a beneficiary's non-track services that the exclusion does not permit you to bill during an active care period. That is a sizing error in the direction that flatters participation, which makes it the expensive kind. The exclusion runs for the whole care period — CMS defines that as an Initial Period of 12 months plus any Follow-On Periods in 12-month increments (RFA footnote 36, p.51) — so an error here compounds over a year rather than a quarter.
Participation is scoped by patient, so it does not have to be all-or-nothing. CMS's own worked example on the model page makes this explicit for an ACO: the organization
> could offer ACCESS services (billed using ACCESS G-codes) to beneficiaries who are not aligned to its ACO, while continuing to bill traditional Medicare FFS claims for its ACO-aligned beneficiaries who are not enrolled in ACCESS.
The exclusion constrains which patients you align, not whether your organization can participate at all. That is a narrower and more workable constraint than the first reading suggests, and it is CMS narrowing it, not us.
We have read four CMS surfaces and they agree. We have not seen an ACCESS Participation Agreement — we looked and could not find one published for this model, which is not the same as its not existing. If CMS publishes one and it defines the exclusion differently, it would outrank the RFA and this post would need revising.
CMS has also moved an ACCESS parameter by web page before without reissuing the PDF. So the honest instruction is the same one we give on every dated question: check the Technical FAQ and the model page on the day it matters to you. Our reading here is current as of July 26, 2026.
And the ordinary disclaimer, which is not boilerplate on this particular topic: this is a summary of published CMS documents, not billing, legal, or financial advice. A scope question about what you may submit to Medicare is one to put to your own compliance counsel with the CMS text in front of them. We have given you the page numbers so that conversation can start from the source.
Stated plainly, so you can discount it: we build reporting infrastructure for ACCESS participants. The reason a billing-scope rule is on our blog is the enforcement mechanism CMS describes for it — Medicare's claims processing systems "will incorporate automatic controls that suppress FFS billing" (RFA p.33, quoted in full above). A rule enforced that way shows up in an organization's claims data, not only in the PDF that describes it. Rules that surface as data problems are the ones we work on.
That is not a pitch. Nothing in this post requires a vendor; all of it is free to read at the links below.
The ACCESS FFS Exclusion attaches to the beneficiary, not the condition: for an aligned beneficiary in an active care period, an ACCESS Participant and its affiliated entities may not bill Medicare FFS for other services, directly or indirectly. The condition-scoped language you may be thinking of belongs to the Substitute Spend Rate four pages earlier — a capped payment adjustment, not a prohibition. And the exclusion does not restrict the beneficiary, does not capture their other providers, and does not capture an individual clinician by reassignment alone.
If you want to walk your own panel and billing setup against this, we are happy to do it with you: [email protected].
---
Outcome Rail builds reporting infrastructure for participants in the CMS ACCESS Model. This post summarizes publicly published CMS documents and is not legal, financial, billing, or clinical advice. It states no measure target values and makes no claim about clinical outcomes. CMS decides payment.
Sources: CMS ACCESS Request for Applications (PDF) — v1.1, last modified 2026-02-12; FFS Exclusion and affiliation definition p.33, Substitute Spend Rate pp.29–30, certification §5 item 32 p.50, care-period definition fn.36 p.51 · ACCESS Technical FAQ — What is the Fee-for-Service Exclusion? · CMS ACCESS Model page — ACO and overlap FAQ block · ACCESS for Primary Care Providers and Referring Clinicians. All four fetched 2026-07-26.
Device, lab, and PROM data in; compliant FHIR submissions out — validity windows, cadence clocks, and provenance rules enforced before CMS ever sees the bundle. We're onboarding a small founding cohort of design partners this quarter.