CMS calculates your RAF three times for one payment year. See every submission deadline through PY 2028 and what to do before each one closes.
CMS calculates a Medicare Advantage plan’s risk scores three times for a single payment year. The initial run uses twelve months of dates of service ending the June before the payment year begins. The mid-year run uses the full prior calendar year. The final run reconciles that same calendar year about thirteen months after it ends. Each run can change what a plan is paid for the same members and the same year.
Nothing submitted after 8 PM ET on a deadline date reaches that run. Data submitted after an initial deadline lands in the mid-year run, and data submitted after a mid-year deadline lands in the final reconciliation.
Most risk adjustment teams work against the final run. It is the number finance reports and the one everyone remembers. It also arrives after every chance to change it has passed.
Every Deadline Through PY 2028
| Risk score run | Dates of service | Submission deadline |
|---|---|---|
| PY 2027 initial | Jul 1, 2025 to Jun 30, 2026 | Friday, Sep 4, 2026 |
| PY 2026 final | Jan 1, 2025 to Dec 31, 2025 | Monday, Feb 1, 2027 |
| PY 2027 mid-year | Jan 1, 2026 to Dec 31, 2026 | Friday, Mar 5, 2027 |
| PY 2028 initial | Jul 1, 2026 to Jun 30, 2027 | Friday, Sep 3, 2027 |
| PY 2027 final | Jan 1, 2026 to Dec 31, 2026 | Monday, Jan 31, 2028 |
Source: CMS HPMS memo, Deadline for Submitting Risk Adjustment Data for Use in Risk Score Calculation Runs for Payment Years 2026, 2027, and 2028.
The pattern holds year to year. Initial deadlines fall on the first Friday in September before the payment year. Mid-year deadlines fall on the first Friday in March. Final deadlines close about thirteen months after the dates of service year ends.
Build an internal cutoff two to three weeks ahead of each CMS date. Files submitted at the deadline leave no room to resolve validation errors or rejections, and a rejected file submitted on the deadline counts for nothing.
What Happens After the Final Deadline
Under 42 CFR 422.310(g), once the final risk adjustment data submission deadline passes, a plan can still submit data to correct overpayments. It cannot submit diagnoses for additional payment.
That asymmetry is the whole reason the calendar matters. Corrections that reduce your risk score remain available indefinitely. Corrections that increase it expire on a published date.
The Mistake Is Reading These as Reports Instead of Deadlines
Each run is a snapshot of what CMS had received by a date. Read as a report, it describes performance. Read as a deadline, it says how much time is left to change the result.
A team that compares the initial run against the prior year has roughly six months before the mid-year deadline to find and submit what is missing. A team that waits for the final run is reading a settled number. The analysis is identical in both cases. The only difference is when it happens.
Two CMS reports carry the detail. The Monthly Membership Report, or MMR, shows member-level risk scores and payment month to month, so you can watch movement between runs. The Model Output Report, or MOR, shows the specific HCCs CMS recognized for each member, which tells you which conditions are missing rather than only how much the score moved.
See your RAF movement across all three runs.
What to Do at Each Run
After the initial run. Compare your initial risk scores to the same population’s initial scores from the prior payment year. Then pull the MOR and list every chronic HCC recognized last year and not recognized now. Chronic conditions do not resolve, so each one is a missing encounter, a missing diagnosis on an encounter you submitted, or a diagnosis CMS did not treat as risk eligible. You have until the first Friday in March to fix them.
After the mid-year run. Take that same list and check which conditions appeared and which did not. The ones still missing have now failed twice. For each, pull the MAO-002 report to confirm whether the encounter was accepted and the MAO-004 report to confirm whether the diagnosis was treated as risk eligible. That answer tells you whether you need a corrected encounter or a chart that was never coded.
Before the final deadline. Submit corrections for everything traced in the previous step, then confirm acceptance rather than submission. A correction submitted in the final weeks and rejected looks like completed work and produces nothing.
After the final run. Count the conditions your coders confirmed during the year that CMS never recognized, and sort them by provider, encounter type, and diagnosis. Anything that clusters will fail the same way next year unless the cause is fixed.
The 2027 Mid-Year Run Changes What Counts
Beginning with the PY 2027 mid-year risk score run, CMS will exclude diagnoses identified through unlinked chart review records from Medicare Advantage risk score calculations. That deadline is March 5, 2027, which is earlier than most plans assume when they hear that the change applies to the 2027 payment year.
Per CMS guidance issued May 7, 2026, CMS will exclude all remaining unlinked diagnoses and reissue the applicable MAO-004 reports starting with that run. Plans will see the effect in their own reporting rather than only in payment.
A chart review diagnosis now has to tie back to an encounter CMS accepted. A condition found late with no qualifying encounter behind it has no path to payment, no matter how well the chart supports it.
V28 compounds this. The model removed a large share of diagnosis codes from risk-adjustment mapping and re-based the values, so fewer conditions carry payment and each missing one weighs more against a smaller base.
How Invent Health Tracks the Cycles
Invent Health runs risk adjustment as one connected loop rather than separate tools that integrate, and it starts with analytics, not coding.
Risk Analytics decides what is worth working. Suspect logic runs across historical, lab, pharmacy, comorbidity, and chart-derived signals, drawing on EMR data through CCD and FHIR. Conditions are ranked by how much they move the score and how likely they are to close this year. Internal capture is validated against CMS-recognized HCCs in the MOR, and RAF progression is tracked across the initial, mid-year, and final runs using the MMR, so movement between runs is visible while there is still time to act.
The Coder Workbench confirms the condition is real. AI-assisted coding reads the clinical documentation, shows the supporting evidence, and recommends ICD-10-CM codes for a certified coder to confirm and sign. It recommends and never assigns. The NLP detects supporting evidence with 85 percent accuracy out of the box and reaches 90 percent as it learns from coder feedback, and the Coder Workbench averages 95 percent coding accuracy across more than 100,000 charts coded.
Encounter Submissions is built to carry that confirmed diagnosis the rest of the way, into 837 files for Medicare and Edge Server XML for ACA, so the identity of the condition holds through submission.
Quality Analytics looks at the same member on the same platform, so risk and quality work from one view of that member rather than two.
Because the three run on one platform, a condition missing from the MOR traces back to the chart and the coder that produced it, which turns a RAF gap into a specific list of conditions to correct before the next deadline.
Start With the Run You Have Now
Pull your most recent MOR and the prior year’s MOR for the same members. List every chronic HCC recognized last year and not recognized now. That list is your RAF gap expressed as conditions rather than dollars, and every item on it can still be worked until the final deadline for that payment year passes.
Frequently asked questions
How many times does CMS calculate risk scores for a payment year?
Three times. An initial run, a mid-year run, and a final reconciliation run. Each uses the risk adjustment data CMS received by that run’s submission deadline, so a plan’s risk scores and payment can change between runs for the same members.
When are the CMS risk adjustment submission deadlines?
Initial deadlines fall on the first Friday in September before the payment year, mid-year deadlines on the first Friday in March, and final deadlines about thirteen months after the dates of service year ends. The PY 2027 mid-year deadline is March 5, 2027, and the PY 2027 final deadline is January 31, 2028.
What dates of service does each risk score run use?
The initial run uses twelve months ending June 30 before the payment year. The mid-year and final runs both use the full prior calendar year, with the final run reconciling it after a longer submission window.
What happens to data submitted after a deadline?
Data submitted after an initial deadline is included in the mid-year run. Data submitted after a mid-year deadline is included in the final reconciliation run. Nothing submitted after 8 PM ET on a deadline date is reflected in that run.
Can a plan submit diagnoses after the final deadline?
Under 42 CFR 422.310(g), a plan can submit data after the final deadline to correct overpayments, but cannot submit diagnoses for additional payment. Corrections that lower a risk score stay available; corrections that raise it do not.
What is the MMR report in Medicare Advantage?
The Monthly Membership Report shows member-level enrollment, risk scores, and payment month to month. It is how a plan watches risk score movement across the initial, mid-year, and final runs instead of seeing only the settled result.
What is the MOR report?
The Model Output Report shows the specific HCCs CMS recognized for each member. It answers which conditions are missing from a risk score, where the MMR answers how much the score moved.
How do you use the initial run to find problems early?
Compare initial risk scores to the same population’s initial scores from the prior year, then pull the MOR and list chronic HCCs recognized last year and missing now. Chronic conditions do not resolve, so each one points to a submission or coding failure you can still fix.
When does the unlinked chart review exclusion take effect?
Beginning with the PY 2027 mid-year risk score run, with a submission deadline of March 5, 2027. CMS guidance issued May 7, 2026 states that remaining unlinked diagnoses will be excluded and applicable MAO-004 reports reissued starting with that run.
How far ahead of a CMS deadline should a plan submit?
Two to three weeks. Submitting at the deadline leaves no time to resolve validation errors or rejections, and a file rejected on the deadline date does not count toward that run.
Why do RAF shortfalls get explained after the fact?
Because teams work against final reconciliation, which arrives after the correction window has closed. The same analysis run against the initial and mid-year reports finds the same gaps while they can still be fixed.
How does Invent Health track risk adjustment payment cycles?
Internal capture is validated against CMS-recognized HCCs in the MOR, and RAF progression is tracked across the initial, mid-year, and final runs in the MMR. Because coding and analytics share a platform, a missing condition traces back to the chart and coder that produced it.