On October 31, 2025, CMS finalized the Calendar Year 2026 Medicare Physician Fee Schedule. Effective January 1, 2026, a new "efficiency adjustment" reduced work RVUs by 2.5% for approximately 7,700 non-time-based CPT codes — covering roughly 91% of services provided by physicians across all specialties.
If your compliance program operates on the rhythm most do — quarterly arrangement reviews, annual FMV refreshes, monthly OIG screenings — this change probably hasn't surfaced yet. The compensation in your physician contracts didn't change. The wRVU thresholds in your bonus structures didn't change. Your FMV opinions are still current.
But the math connecting those things changed. And in a year where the DOJ has already announced two medical-directorship enforcement actions in January and the FY25 False Claims Act recovery total hit a record $6.8B, that math matters operationally — not just to your compensation committee.
This post is for the chief compliance officer who has heard about the wRVU adjustment from someone in finance and hasn't yet figured out whether it's a Stark Law problem.
Short answer: it might be, for a meaningful subset of your arrangements. Long answer below.
What CMS actually changed
Three specific changes in the CY 2026 PFS Final Rule matter for arrangement compliance:
1. The efficiency adjustment. CMS reduced wRVUs by 2.5% on approximately 7,700 non-time-based codes — primarily surgical, procedural, imaging, diagnostic, and interventional services. Time-based codes (E&M visits, care management, behavioral health, telehealth) are exempt.
2. Conversion factor changes. The 2026 conversion factor is $33.4009 for non-APM-qualifying physicians (+3.26% from 2025) and $33.5675 for APM qualifying participants (+3.77%). Net Medicare reimbursement for many specialties goes up. But because the wRVU count decreases in parallel, the same clinical work now generates fewer wRVUs.
3. The compounding clause. CMS announced the efficiency adjustment will reapply every three years going forward, with no floor on how much a service could be devalued.
The aggregate effect is specialty-specific. According to public analysis, urology wRVUs decreased by roughly 2.57%, invasive-interventional cardiology by 2.32%, and diagnostic radiology by 2.30%. Specialties heavy on E&M coding — hematology/oncology, hospital medicine, internal medicine — saw essentially no change.
Why this is a Stark question, not just a finance question
Stark Law requires that physician compensation arrangements be at fair market value, not vary with the volume or value of referrals, and remain consistent with FMV across the life of the arrangement — not just at signing.
The wRVU adjustment creates three operational scenarios that compliance officers should treat as fresh review triggers:
Scenario A — wRVU-tied compensation arrangements. A physician on a $/wRVU model performing identical clinical work in 2026 now generates fewer wRVUs than in 2025. If the per-wRVU rate stays the same, the physician's total compensation drops. Some organizations are responding by raising the per-wRVU rate to maintain "shadow" 2025 compensation levels. That's a fair market value event. A per-wRVU rate that was at the 65th percentile in 2025 and is adjusted upward to maintain dollar-equivalent compensation may now be above the 75th percentile — without anyone having signed a new contract, written a new FMV opinion, or noticed.
Scenario B — productivity bonus thresholds. Many employment arrangements include bonus tiers triggered at specific wRVU thresholds (e.g., a 10% bonus at 6,500 wRVUs annually). Physicians who consistently cleared 6,500 wRVUs in 2025 may now fall short of 6,500 in 2026 doing the same clinical work. That can trigger compensation guarantees, retroactive bonus calculations, or contract renegotiations — each of which is a Stark documentation event.
Scenario C — quality-and-citizenship bonus structures. Arrangements that combine wRVU productivity with quality or citizenship bonuses may see the wRVU component fall while the bonus component stays constant. That changes the ratio of compensation components, which can affect whether the arrangement satisfies the volume-or-value test — particularly if the bonus structure was originally calibrated to be a small percentage of total compensation.
In all three scenarios, the underlying clinical work didn't change. The physician didn't change. The contract didn't change. But the arrangement's compliance posture potentially did.
The "documentation gap" the wRVU change exposes
Here is the structural compliance problem most organizations have not yet faced:
When CMS published the Final Rule on October 31, 2025, there was a 60-day window before the rule took effect on January 1, 2026. During that window, the responsible operational action was to inventory every arrangement with wRVU-sensitive structure, model the 2026 impact, and document either (a) "the arrangement remains within FMV under the new wRVU math" or (b) "the arrangement requires modification."
Many organizations did this exercise in their compensation committee. Far fewer organizations documented the analysis at the arrangement level in a way that would survive a Stark FCA investigation 18 months from now.
The DOJ does not subpoena compensation committee minutes. The DOJ subpoenas the file for a specific physician's specific arrangement and asks: when the rules changed, what did you do, and where is the contemporaneous record of the decision?
The Tenet/HMA case turned on FMV opinions that valued services that didn't actually exist. The Wheeling case turned on FMV opinions that should have existed but didn't. The 2026 wRVU adjustment creates a new variant: FMV opinions that existed at signing but no longer apply because the underlying measurement system changed.
Three questions to ask before Q3
Three specific questions every CCO should be able to answer about every wRVU-sensitive arrangement in their portfolio by the end of Q2 2026:
1. Which arrangements in our portfolio are wRVU-sensitive, and which 2026 codes affect them?
This sounds basic. In practice, it requires pulling every active physician employment contract, every PSA, and every medical directorship; identifying which contain wRVU-tied compensation components; cross-referencing those contracts to the codes the physicians actually bill; and confirming whether those codes are on the CMS efficiency adjustment list. For a health system with 200 physician arrangements, this is a 30-40 hour exercise the first time — and the answer must be reproducible if asked again.
2. For each affected arrangement, what is the documented Stark/FMV analysis of the 2026 change?
The right shape of the answer is a one-paragraph contemporaneous note tied to the arrangement file: "On [date], compensation committee/general counsel reviewed [arrangement] in light of the CY 2026 PFS efficiency adjustment. Modeled impact: [physician now generates X% fewer wRVUs in CY 2026 for equivalent clinical work]. Action: [no change / rate adjustment / contract amendment]. Supporting FMV analysis: [link to memo or refreshed opinion]. Reviewed by: [name, title, date]."
If you cannot produce that note for every wRVU-sensitive arrangement, you have a documentation gap that compounds every quarter.
3. If a per-wRVU rate was adjusted to offset the efficiency adjustment, what FMV opinion supports the new rate?
This is the highest-risk scenario. An organization that adjusted per-wRVU rates upward to preserve physician take-home compensation may have produced a structurally identical economic outcome to 2025 — but the per-wRVU rate is a new data point, and Stark's FMV requirement evaluates that data point on its own merits against market benchmarks. A 2025 FMV opinion that supported the prior per-wRVU rate does not automatically support a higher rate adjusted to offset CMS's efficiency cut. The opinion needs to be refreshed, or a memo needs to document why the original opinion still applies.
The honest framing
ArrowISE builds software that tracks arrangement-level documentation, FMV opinion currency, and compliance-event triggers like the wRVU adjustment. We won't pretend otherwise — that's why this post exists.
But the operational argument stands regardless of which tracking infrastructure you use: the 2026 wRVU adjustment is the kind of compliance event that does not announce itself as a compliance event. It arrives as a finance memo, a comp committee discussion, a "let's revisit the per-wRVU rate" conversation. The Stark documentation requirement attaches downstream of those conversations — and if the tracking system is not connected to the conversations, the documentation gets created late, incompletely, or not at all.
The cases that produced 2025's $5.7B in healthcare FCA recoveries did not turn on bad-faith conduct. They turned on the cumulative effect of small documentation gaps across many arrangements over many years. The 2026 wRVU change is exactly the kind of event that adds gaps to the file — quietly, in the absence of a tracking system that catches it.
Your healthcare counsel will tell you what the law requires. Your valuation firm will tell you what FMV looks like at the new rates. Neither of them is the system of record for whether you have actually done the documentation work for every affected arrangement.
That's the question the wRVU adjustment leaves on your desk.
Want to see how ArrowISE tracks compliance events like the wRVU adjustment at the arrangement level? Start a 30-day free trial or explore the Defensibility Index methodology.