CMS 2026 Physician Fee Schedule: Assess Your Revenue Impact
Review the two 2026 Medicare conversion factors, scope the efficiency adjustment, and build a service-mix analysis using official CMS files and local assumptions.
The 2026 Medicare Physician Fee Schedule cannot be reduced to a single across-the-board percentage change. The conversion factor matters, but so do the applicable payment pathway, relative value units, locality, setting, service mix, and other adjustments.
For a revenue-cycle team, the useful output is a reproducible comparison for its own services. This guide identifies selected final-rule facts and proposes an analysis workflow. It is not a fee quote, a complete coding update, or a prediction for any practice's collections.
Start with the final rule, not the proposal
CMS issued the CY 2026 PFS final rule on October 31, 2025, with policies effective on or after January 1, 2026. Its fact sheet reports two conversion factors, rounded below. Qualifying alternative payment model participants and nonqualifying practitioners do not use the same factor. CMS final-rule fact sheet.
| CY 2026 category | Rounded conversion factor reported by CMS |
|---|---|
| Qualifying APM participant | $33.57 |
| Nonqualifying APM participant | $33.40 |
CMS also finalized a -2.5% efficiency adjustment to work RVUs and corresponding intraservice physician time for specified services, with exemptions. It is not a universal 2.5% cut to every payment. Check the applicable code files and exemption list rather than applying it again to already adjusted values.
Use the CMS-1832-F publication and supporting files as the release record for this rule. Preserve the actual version used in your calculation. A preliminary table, a later correction, and a final production file should not be treated as the same input.
Define which revenue you are analyzing
Separate Original Medicare professional payments from Medicare Advantage contracts and commercial arrangements. A payer contract that refers to a Medicare schedule may use a particular year, percentage, locality, or amendment. Do not assume it automatically adopts the current schedule.
Identify the billing entities and practitioners in scope, the relevant APM status, service locations, and place-of-service mix. Record who verified each assumption. If participation status or contract language is unresolved, create separate scenarios instead of choosing whichever produces the more favorable result.
Keep professional and facility components distinct where relevant. A service delivered in one setting may not have the same practice-expense treatment as the same service delivered elsewhere. Use the actual configuration in the payment data rather than a generic organization-wide average.
Build a service-level comparison
Start with a historical utilization extract your finance and coding teams approve. Retain the reporting period, code version, modifiers, units, setting, and locality fields needed for the intended comparison. Limit access to claim-level data and publish only appropriate aggregates.
For each eligible service, compare the old and new allowed amounts under a consistent set of assumptions. Then multiply the difference by the same baseline service volume. This isolates a rate effect; it does not predict changes in visits, utilization, patient mix, or collections.
Fixed-volume rate effect = sum of (new modeled allowed amount − old modeled allowed amount) × baseline units
Keep the unmodeled population visible. Services without a comparable rate, deleted or newly introduced codes, missing modifiers, and incomplete locality information belong in an exception table. Dropping them silently makes the result look more complete than it is.
Separate the financial questions
A good presentation distinguishes at least three views:
- Rate-only view: What changes when the same service mix is priced under the two sets of assumptions?
- Operating scenario: What changes when expected volume, staffing, setting, or service mix also changes?
- Collection view: What amount is actually collected, after the applicable contractual and operational effects?
Use clear labels on each table. A modeled allowed amount is not the same as a submitted charge, a payment remittance, or net cash. Explain which adjustments are included and which remain outside the model.
Ask finance to challenge the largest contributors to the result. A few high-volume or high-value services may explain much of the modeled difference, but that should emerge from your data, not from an assumed specialty impact percentage.
Test operational changes before rollout
Review charge-master or fee-table imports with coding, billing, and system owners. Confirm effective-date handling and preserve the previous version for historical services and corrections. Do not apply a new schedule solely because a claim is submitted after the implementation date.
Use representative approved test cases to check service-date boundaries, modifiers, units, locations, and practitioner classifications. Include a case that should remain on the older configuration. Reconcile a sample of calculated amounts against the official reference and your contract interpretation before accepting the import.
When an amount differs, investigate rounding, stale files, default locality, service setting, and adjustment order. Document the cause and the corrected configuration; avoid adding a manual override merely to force a desired total.
Monitor what actually happens
After the configuration is in use, compare expected and observed amounts on a defined sample of adjudicated claims. Track unresolved differences separately from confirmed underpayments. A difference in the first remittance may require more information before it supports a recovery claim.
Maintain a change log with the source file, implementation date, configuration owner, test evidence, and unresolved questions. The RCM dashboard data dictionary can help keep modeled and observed measures separate in reporting.
Prepare the next review without inventing its outcome
Assign responsibility for checking subsequent CMS corrections and future rulemaking. Label proposed policies as proposed until a final action supports a change. Do not carry forward a draft's projected percentage as a confirmed payment update.
Your final decision packet should contain the source versions, scope, assumptions, modeled service mix, exceptions, and acceptance evidence. That gives operations a defensible implementation plan and gives finance a result it can reproduce. For help evaluating the workflow, contact QuickIntell without including patient data.
Public-reference check: September 6, 2026. Selected regulatory facts and original implementation recommendations are not comprehensive legal, coding, or financial advice. No customer outcome or credentialed review is asserted.