Most reporting deadlines cost you a submission. Two of the deadlines in the CMS ACCESS model can cost you considerably more than that — and both are easy to get wrong if you've mapped them onto a normal calendar.
Both come straight from CMS's "ACCESS Model Payment Amounts and Performance Targets" paper (p.7). Nothing below is our interpretation of intent — it's what the document says, and you should read it yourself.
A valid baseline OAP Measure must be submitted within 60 days of alignment, via the Data Reporting API. Per the Payment paper's baseline-reporting section, missing it doesn't just invalidate a submission — the beneficiary becomes unaligned, and the participant may not provide services under the model until re-alignment.
That makes this the harshest deadline in the model: it's the one that voids the care period itself. Every beneficiary you align starts this clock on day one, which means alignment volume and reporting capacity are coupled from the very first cohort. If your intake outruns your ability to capture and submit valid baseline measures, the model unwinds the alignments for you.
Note the word valid: the baseline measure has to clear the same validity rules as everything else — collection recency windows and permitted collection methods (the ACCESS RFA, Appendix C, governs methods). A submission that lands on day 45 with a stale or improperly-collected reading doesn't stop the clock.
The quarterly measure requirement is the easiest rule in the model to misread. Per the same page of the Payment paper, a valid quarterly measure must land 70 to 110 days after your previous submission — a rolling window anchored to your own prior submission, not a fixed calendar quarter and not a schedule anchored to the alignment date.
Two consequences follow directly from that anchoring:
Submitting early moves your next window earlier. Each submission resets the anchor, so an aggressive early submission compresses your entire future cadence. Batch submissions "ahead of schedule" and you have dragged every subsequent window forward — that's arithmetic, not an edge case.
There is also a too early: day 69 is outside the window, just as day 111 is. A calendar reminder set to "every 90 days from alignment" will drift out of the window within a few cycles.
One honesty note, because CMS makes the distinction: quarterly submissions are collected for monitoring and auditing rather than used directly to set the payment amount. But the Payment paper still treats timely quarterly submission as a hard requirement — it satisfies active care delivery and counts toward attainment — so treating it as optional is a mistake with billing consequences.
If you're an ACCESS participant, the minimum viable defense is a per-beneficiary submission ledger: alignment date, each submission date, and the computed next-window bounds (70/110 from the last submission, not from a calendar). If that ledger lives in someone's head or a spreadsheet nobody reconciles, the rolling window will eventually catch you.
This post is part of a series on the ACCESS deadline and validity rules, each traced to the CMS primary documents. Next up: the six validity windows that decide when a reading stops counting.
---
Outcome Rail builds reporting infrastructure for ACCESS participants. If you're working through these windows, we're happy to compare notes: hello@outcomerail.com.
Sources: CMS ACCESS Model Payment Amounts and Performance Targets (PDF), p.7 · ACCESS RFA (PDF), Appendix C · 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.