QPP and non-QPP 2026 Medicare payment comparisons should be treated as conversion-factor scenarios, not as different CPT RVU schedules. The CPT code, work RVU, practice expense RVU, malpractice RVU, setting, and GPCI locality remain the same. The final multiplier changes when QPP/APM status applies. A professional comparison isolates that one variable so users can see the policy effect without mixing it with code or geography changes.
What changes between QPP and non-QPP
In RVUinUSA's 2026 model, non-QPP payment uses a conversion factor of $33.4009 and QPP/APM payment uses $33.5675. Those values are applied only after adjusted total RVU has been calculated. If the CPT code, setting, or locality changes at the same time, the result no longer answers the QPP-versus-non-QPP question. It becomes a mixed scenario that cannot be attributed to participant status alone.
- Non-QPP modeled conversion factor: $33.4009.
- QPP/APM modeled conversion factor: $33.5675.
- CPT RVU values and GPCI inputs should stay fixed in a clean comparison.
Use the same RVU inputs before comparing policy status
QPP and non-QPP comparisons should isolate the conversion factor. Do not change CPT code, setting, or locality inside the same comparison.
- RVU components
- Unchanged
- GPCI locality
- Unchanged
- Variable
- Conversion factor
Use identical RVU inputs first
A clean comparison starts by selecting one CPT or HCPCS code and one practice expense setting. Then apply the same GPCI locality to both scenarios. Only after adjusted total RVU is known should the non-QPP and QPP/APM conversion factors be applied. This structure makes the output auditable because the reader can see exactly which input changed.
- Use the same CPT or HCPCS code in both scenarios.
- Use the same facility or non-facility PE RVU selection.
- Use the same Work, PE, and MP GPCI locality values.
Why the difference can matter
The spread between the two 2026 modeled conversion factors is $0.1666 per adjusted total RVU. For a single low-RVU service, the dollar difference may be small. Across high-volume established visits, procedures, or an annual service-line forecast, the cumulative difference can become meaningful. That is why QPP/APM status should be documented in copied estimates, finance models, and physician compensation discussions when Medicare payment assumptions are being referenced.
- Small per-service differences can become material at annual volume.
- High-total-RVU services show larger dollar changes per encounter.
- Reports should label participant status instead of hiding it in the calculation.
Do not infer eligibility from the calculator
A calculator can model the dollar effect of QPP/APM status, but it should not decide whether a clinician or organization qualifies. Eligibility depends on CMS rules, reporting, organizational participation, and the period being reviewed. When status is uncertain, use non-QPP as the baseline and label any QPP/APM estimate as conditional until participation is confirmed.
- Use CMS or organizational sources to confirm participation status.
- Do not assume all clinicians in a group have the same QPP/APM treatment.
- Label conditional scenarios clearly in planning documents.
Keep Medicare payment separate from compensation
QPP/APM conversion factors are Medicare payment assumptions. They do not automatically change a physician's employment compensation. If a contract pays a dollars-per-wRVU rate, that rate is governed by the written agreement, not by the Medicare conversion factor unless the agreement explicitly ties compensation to it. Contract analysis should therefore model QPP and non-QPP only when the agreement or business question actually depends on Medicare payment.
- QPP/APM affects Medicare payment modeling, not automatically compensation.
- Employment contracts may use separate dollars-per-wRVU rates.
- Review the written formula before applying Medicare assumptions to compensation.
Recommended workflow
Use the CPT page or RVU calculator to confirm the code-level RVU inputs, then use the APM calculator for side-by-side payment comparison. If the purpose is planning or policy analysis, keep volume assumptions visible. If the purpose is a physician contract review, move from payment modeling into the contract analyzer only after identifying whether the agreement references Medicare payment, wRVU productivity, collections, or a custom formula.
- Confirm RVU components before comparing conversion factors.
- Use one locality and one setting for both scenarios.
- Move into contract tools only when compensation terms require that analysis.