If you run an aligned panel under the CMS ACCESS Model, there is a paragraph you have probably had quoted at you. If you got it from us, you got it one sentence short.
The paragraph is in CMS's ACCESS Model Payment Amounts and Performance Targets document, on page 7, under Baseline Reporting. It is three sentences long. The version we were quoting was the first two. The third one changes what the first two mean.
Here it is whole.
> Valid baseline OAP Measures must be submitted within 60 days of alignment via the Data Reporting Application Programming Interface (API). If baseline data are not received within this timeframe, the beneficiary will be unaligned, and the ACCESS Participant may not provide services under the model. If reporting was delayed and the ACCESS Participant wishes to initiate care, the ACCESS Participant must resubmit the beneficiary for alignment via the Alignment API.
Three sentences, three jobs. The first sets a deadline: valid baseline Outcome-Aligned Payment (OAP) Measures, within 60 days of alignment, through the Data Reporting API. The second states the consequence, and it is severe and worth taking seriously — the beneficiary is unaligned and you may not provide services under the model.
The third states a remedy. CMS names the mechanism, names which API it runs through, and names the condition under which you would use it.
A summary that stops after sentence two does not merely omit a detail. It converts a recoverable situation into a terminal one.
Read it narrowly, because it rewards narrow reading.
CMS says that if reporting was delayed and you wish to initiate care, you must resubmit the beneficiary for alignment via the Alignment API. Two things follow directly from the words on the page:
It is a different API from the one you missed. Baseline measures go through the Data Reporting API. Re-alignment goes through the Alignment API. If your integration has one of those and not the other, the remedy sentence is describing a door you have not built.
It is a required step, not an automatic one. The verb is must resubmit. Nothing in the sentence suggests the beneficiary drifts back on their own, and nothing suggests the clock you missed simply resets in place.
And here is what the sentence does not say, which matters just as much: it does not say the remedy is free, and it does not say it is instant. Between the unalignment and the re-alignment you may not provide services under the model for that beneficiary. That interval is real and CMS states it in sentence two.
So the honest shape of a miss is: not a cliff, not a shrug. It is an interruption with a defined way out and a cost while you are out of it.
(One clause in this section rests on our own inference rather than a CMS sentence — see the note at the end about what we are still checking.)
CMS describes how payment attaches in two places, and both are worth reading before you size a miss.
Page 4, Payment Frequency:
> CMS will issue monthly payments equal to one-twelfth of the Medicare portion of the annual OAP allowed amount for valid monthly claims submitted by ACCESS Participants.
Page 7, End-of-Period Reporting:
> Payment is limited to months for which ACCESS claims are submitted.
Payment is claim-driven and month-by-month. That is the frame to size a miss in: the months you cannot bill because you may not provide services under the model, plus the work of putting the beneficiary back through alignment.
We are deliberately not drawing the further conclusion. The obvious next question is whether months already paid can be recovered by CMS after a later unalignment. We have a view internally. We are not publishing it, because it is a claim about something CMS's text does not address in this paragraph, and a negative claim — this cannot happen to you — is exactly the kind that reads as reassuring, gets quoted back at us, and is the most expensive thing to be wrong about in this business. If your finance team needs that answer, it is a question for CMS, not for a vendor blog.
What we will say is the direction of the arithmetic: the cost of a missed baseline that CMS's paragraph clearly describes is forward-looking. It is about months you cannot bill going forward and a re-alignment you have to perform. Size that first.
There is a genuinely open question underneath this and it is more consequential than the remedy itself.
The Outcome Attainment Rate is an organisation-level ratio. So it matters whether a beneficiary who was administratively unaligned for a missed baseline still sits in its denominator. CMS enumerates cohorts on page 6, carefully:
> Beneficiaries who relocate outside an ACCESS Participant's licensed service area and beneficiaries who become ineligible during the Care Period are excluded from the numerator and denominator of the OAR calculation. Beneficiaries who initiate unalignment or who are lost to follow-up remain in the denominator.
Four named cohorts. Two out, two in. Administrative unalignment for a missed baseline is in neither list.
That is not an oversight we spotted. In the ACCESS Request for Applications, version 1.1, page 53, footnote 38 — the only place the word denominator appears in all 63 pages — CMS defers denominator exclusions to a future guidance document. The silence is dated and deliberate.
The tempting inference is that an unaligned beneficiary completed no care period and therefore cannot be in a denominator of care periods. It is a reasonable inference. It is also exactly the kind of reasonable inference that stops people from going and checking, so we are not going to make it for you. If you are modelling attainment at the organisation level, treat this as unspecified and watch for the guidance document.
This is the part we would rather not write, which is why it is here rather than in a footnote.
Our own materials described this consequence as terminal. In one place we said a missed Day-60 baseline meant a beneficiary you cannot keep. In another we said it stopped the full payment for that beneficiary. Neither of those is a CMS sentence. CMS says the beneficiary is unaligned, that you may not provide services under the model, and that you resubmit them for alignment via the Alignment API — and it says the third part in the same paragraph as the first two.
Two things about how that happened, because the mechanism is more useful than the apology.
The error ran toward the threat, not away from it. We described the consequence as worse than CMS does. That direction has no natural adversary: an overstated risk reads as appropriately cautious, so no internal check fires on it. Every review we run asks whether a claim oversells the product. None of them asked whether a claim oversold the danger.
We already knew the right answer, in writing, several times over. The correct sentence — may not provide services under the model until re-alignment — was sitting in our own published posts and our own annotated rules document while the truncated version sat on our home page. We did not fail to learn the fact. We learned it, wrote it down correctly, and never propagated it backwards into the copy written earlier.
The corrections are written and have been through our claim review. We are not going to tell you which of our pages have caught up by the time you read this, because that depends on a deploy and we would rather give you something checkable: the paragraph is on page 7 of the Payments PDF, linked below. If you find a page of ours that still ends it early, it is wrong and the PDF is right.
Three things, none of which require anything from us.
1. Quote the whole paragraph. If a baseline deadline appears in your internal runbook, your board deck, or the slide someone made for the clinical team, check whether the remedy sentence is in it. A workflow written from the two-sentence version has no branch for a beneficiary who can come back. 2. Check that you can reach the Alignment API, not just the Data Reporting API. The remedy runs through a different endpoint from the deadline you would be recovering from. 3. Do not build an attainment model that assumes a position on the denominator question. CMS has said it will specify this later. Until then, know which way your model leans and how much it costs you if it leans wrong.
We have quoted one CMS document for the mechanism — the Payments PDF — and one RFA footnote for the denominator deferral. We have not read the ACCESS Participation Agreement; we looked and could not find one published for this model, which is not the same as its not existing. If one is published and defines any of this differently, it would outrank both documents quoted here and this post would need revising.
We have not settled whether payments already made can be recovered in circumstances outside this paragraph, and we have said so above rather than leaving it to be inferred.
CMS has moved ACCESS parameters by web page before without reissuing a PDF. So the standing instruction is the same one we give on every post: check the model page and the Technical FAQ on the day it matters to you. Our reading is current as of July 27, 2026.
And the ordinary disclaimer, which is not boilerplate here: this is a summary of published CMS documents, not legal, financial, billing, or clinical advice. CMS decides eligibility, alignment and payment. We have given you the page numbers so your own review can start at the source rather than at us.
Stated plainly, so you can discount it: we build reporting infrastructure for ACCESS participants, and a deadline with a remedy behind it is a different engineering problem from a deadline with a cliff behind it. A cliff needs a warning. A remedy needs a path — detect the miss, know which API to hit, know that the interval is costing you, restart cleanly. That is the kind of thing we work on.
It is also how we found our own error, which is a fair summary of what our week looks like.
That is not a pitch. Nothing in this post requires a vendor; all of it is free to read at the link below.
CMS's Day-60 baseline paragraph is three sentences. Sentence one sets the deadline. Sentence two says the beneficiary is unaligned and you may not provide services under the model. Sentence three says you resubmit the beneficiary for alignment via the Alignment API. A missed baseline is an interruption with a defined way out, not a beneficiary you have permanently lost — and our own copy said otherwise until this week. What CMS has not specified is whether that beneficiary stays in your OAR denominator; it has committed in writing to specifying it later.
If you want to walk your own baseline workflow against the full paragraph, 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 Model Payment Amounts and Performance Targets (PDF) — p.4 Payment Frequency, p.6 Outcome Attainment (OAR cohorts), p.7 Baseline Reporting, p.7 End-of-Period Reporting; document re-fetched in full 2026-07-26, Effective Period July 5 2026 – December 31 2027 · CMS ACCESS Request for Applications (PDF) — v1.1, p.53 fn.38 (denominator exclusions deferred to future guidance) · CMS ACCESS Model page · ACCESS Technical FAQ.
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.