The Margin for Error Is Closing for MA
The Margin for Error Is Closing: OBBBA and the End of the Chart-Chase Era in Medicare Advantage
Three structural shifts are arriving on the same calendar — a restructured Medicaid floor, a recalibrated risk model, and the most aggressive RADV audit posture in the program's history. Individually, each is manageable. Together, they make incomplete provider documentation a liability a plan can no longer afford to carry.
The Convergence
Three pressures, one calendar
The One Big Beautiful Bill Act (OBBBA, H.R. 1), signed July 4, 2025, does not cut Medicare Part A or B benefits directly. Its effect on Medicare Advantage is structural and indirect: it reshapes the Medicaid program that sits beneath the fastest-growing segment of MA. According to Congressional Budget Office estimates, the law is projected to reduce federal Medicaid funding by roughly $911 billion through 2034 and lower Medicaid enrollment by an estimated 10.3 million people. Most of the deepest financing cuts land after 2030 — but the operational disruption begins much sooner.
What makes this moment distinct is that OBBBA is not arriving alone. It coincides with the full operational rollout of the CMS-HCC V28 risk model and an audit regime that CMS has explicitly designed to clear its backlog and reach every eligible contract. For plans, these are not three separate workstreams. They are three pressures on the same underlying asset: the accuracy and defensibility of clinical documentation.
A restructured Medicaid floor
Work requirements and six-month redeterminations for expansion adults take effect January 1, 2027 — disruption driven largely by administrative churn, not true ineligibility.
A recalibrated risk model
V28 is now operational at 100% of payment for 2026, and the 2027 Advance Notice proposes further recalibration that would again compress risk scores.
An aggressive audit posture
CMS is moving to audit all RADV-eligible contracts, with PY2020 reviews beginning as early as February 2026, against an estimated ~$17B in annual overpayments.
Where It Lands Hardest
Dual-eligibles, D-SNPs, and the documentation layer
D-SNPs are the largest special-needs product and have been growing faster than conventional MA. OBBBA never names them — yet they sit directly in the path of its Medicaid provisions. Six-month redeterminations and work-and-community-engagement requirements will increase the frequency of eligibility verification, and historically that kind of administrative friction produces coverage loss among people who remain eligible. For a D-SNP, a dual member who loses Medicaid mid-year is not a static data point; it is a status change that touches deeming, enrollment, and the revenue attached to that member.
At the same time, provider-tax caps and tightened state financing rules are expected to pressure states' optional Medicaid spending — including the home- and community-based services that many dual-eligibles rely on. The result is a membership base that is more volatile and more administratively expensive to serve, layered on top of a risk model that pays less for the same documented illness. In that environment, the value a plan can capture per retained member-month depends almost entirely on how completely and defensibly that member's clinical picture is documented at the point of care.
The Strategic Shift
The chart-chase era is ending
The most consequential signal for risk adjustment is not in OBBBA at all — it is in the January 2026 payment rule, where CMS proposed excluding chart reviews from MA risk scoring beginning in 2027. The retrospective chart-chase model — sweep the charts after the fact, surface diagnoses, submit — has been the industry's default for a decade. If chart-review-sourced diagnoses no longer count toward risk scores, that entire workflow loses its economic foundation, and with it the inflated audit exposure it created.
What survives is documentation that was complete and encounter-grounded the first time.
This is the same root cause IQRP has argued from the start. Stars performance, clinical documentation integrity, and risk adjustment accuracy are managed in most plans as three separate functions with three separate budgets — but they share a single point of failure: incomplete provider documentation at the point of care. Plans pay a fragmentation tax to run them in parallel. OBBBA and the V28/RADV environment do not create that tax; they make it unaffordable. Every unsupported HCC is now simultaneously a RADV liability and forgone revenue under a tighter model — and soon, a diagnosis with no clean encounter trail may not count at all.
IQRP's Approach
Mitigation built on the source, not the sweep
IQRP's model is deliberately built for the environment now arriving: a FHIR-based clinical-data supplemental pipeline that grounds documentation in the encounter itself, rather than reconstructing it afterward.
Encounter-grounded, MEAT-defensible documentation
A FHIR-based supplemental pipeline sources diagnoses from clinical data and EDPS-eligible encounters — documentation built to withstand RADV's MEAT standard, and to retain value as chart-review-sourced capture is phased out of risk scoring.
One integrated view across Stars, CDI, and risk adjustment
By treating provider documentation as the shared root cause, IQRP collapses three siloed workstreams into a single pipeline — removing the fragmentation tax precisely when margins are thinnest.
Attribution and eligibility intelligence for a churning membership
Member-to-provider attribution and enrollment-span logic give D-SNP and dual-focused plans the data foundation to manage redetermination-driven churn and integration requirements, rather than absorb them as surprises.
Embedded delivery, outcome-anchored
IQRP works alongside a plan's quality, medical-management, and data teams — structured around measurable improvement in documentation quality, coding specificity, and submission accuracy rather than an implementation milestone.
The plans that prepare now will be the ones still capturing value in 2027.
IQRP partners with Medicare Advantage organizations, ACOs, and SNPs to build the documentation foundation this environment demands — defensible under audit, durable under V28, and resilient to a more volatile membership base. We'd welcome a conversation about where your documentation pipeline stands today.
Start a conversation →