A CPT code’s RVU page exists to answer one specific question: given this procedure or service, what does Medicare pay, and how does that number change by location and setting? The relative value unit (RVU) data tied to a CPT code is not the payment amount itself — it’s the input that, combined with a geographic adjustment and a national conversion factor, produces a dollar estimate under the Medicare Physician Fee Schedule (MPFS).
Understanding a CPT-specific RVU page correctly means separating three things that get conflated constantly: the RVU value assigned to the code, the locality-adjusted payment estimate, and — if you’re looking at this from a compensation angle — the work RVU (wRVU) used in a physician’s employment contract. These are related but not interchangeable.
What a CPT Code’s RVU Actually Represents
Every CPT code that Medicare reimburses under the Physician Fee Schedule has three separate RVU components. Each one is priced independently, and each responds differently to geography.
| Component | What it measures | Sensitive to locality? |
|---|---|---|
| Work RVU (wRVU) | Physician time, skill, mental effort, and stress involved in performing the service | No — same nationwide |
| Practice Expense RVU (PE RVU) | Overhead: clinical staff time, equipment, supplies, and facility costs | Yes — differs by facility vs. non-facility setting and by locality |
| Malpractice RVU (MP RVU) | Liability insurance cost associated with the specific service’s risk profile | Yes — varies modestly by locality |
The total RVU for a CPT code is the sum of these three components before any geographic adjustment is applied. A code’s total RVU is fixed at the national level for a given year; what changes by location is how CMS’s Geographic Practice Cost Index (GPCI) scales each component before the conversion factor is applied.
One detail that trips up a lot of people using a CPT lookup tool: PE RVU is not a single number. CMS publishes a facility PE RVU and a non-facility PE RVU for most codes. A procedure performed in a hospital outpatient department (facility setting) has a lower PE RVU than the same code performed in a physician’s own office (non-facility setting), because in the facility setting the hospital — not the physician’s practice — absorbs most of the overhead. If a CPT page you’re reviewing shows only one PE RVU value without specifying the setting, that’s a gap worth flagging, because it directly affects the payment estimate.
From CPT Code to Medicare Payment: The Actual Formula
The relationship between RVU and payment follows this structure:
Medicare Payment = [(Work RVU × Work GPCI) + (PE RVU × PE GPCI) + (MP RVU × MP GPCI)] × Conversion Factor
Each RVU component is multiplied by its own GPCI value for the specific locality — not a single blended GPCI applied to the whole code. This is a common simplification error: treating GPCI as one number that scales total RVU, when in practice CMS applies three separate GPCI indices (work, practice expense, and malpractice) to their respective components.
The conversion factor (CF) is the dollar amount CMS assigns per RVU nationally, and it’s one of the few figures in this formula that changes on a predictable annual cycle. Starting with calendar year 2026, CMS finalized a structural change: instead of one national conversion factor, there are now two — one for clinicians participating in a qualifying Advanced Alternative Payment Model (APM), and one for everyone else. For CY 2026, the qualifying APM conversion factor is $33.5675, and the non-qualifying APM (standard MIPS-track) conversion factor is $33.4009, both effective January 1, 2026. That’s an increase of roughly 3.77% and 3.26% respectively over the CY 2025 conversion factor of $32.3465. This split conversion factor is a permanent feature of the fee schedule going forward under the current statutory framework, not a one-year adjustment, so any RVU calculator or lookup page needs to ask which track applies before returning a payment estimate.
Worked Example (Illustrative Values Only)
To show how the formula behaves, here’s a walk-through using illustrative RVU and GPCI figures — not the actual published values for any real CPT code, since those change annually and vary by code:
| Step | Illustrative value | Result |
|---|---|---|
| Work RVU | 1.50 | — |
| Work GPCI (example locality) | 1.02 | 1.50 × 1.02 = 1.530 |
| Non-facility PE RVU | 1.80 | — |
| PE GPCI (example locality) | 0.98 | 1.80 × 0.98 = 1.764 |
| MP RVU | 0.10 | — |
| MP GPCI (example locality) | 1.05 | 0.10 × 1.05 = 0.105 |
| GPCI-adjusted total RVU | — | 1.530 + 1.764 + 0.105 = 3.399 |
| Conversion factor (CY 2026, non-QP) | $33.4009 | — |
| Estimated Medicare payment | — | 3.399 × $33.4009 ≈ $113.55 |
This is the calculation logic a properly built CPT RVU calculator should run automatically once a user selects a code, a locality, and a facility or non-facility setting. Running this by hand for every code is exactly why a dedicated RVU calculator is useful — but it’s worth understanding the mechanics so the output isn’t treated as a black box.
Why Locality Changes the Same CPT Code’s Payment
Two physicians billing the identical CPT code in two different Medicare localities will not receive the same payment, because GPCI values differ by locality for all three RVU components. A locality with a high cost of practicing medicine (certain metro areas) will generally have GPCI values above 1.0, while lower-cost localities may have GPCI values below 1.0 for one or more components. This is why a representative locality comparison table is useful on a CPT-specific page — it lets a user see the range of payment outcomes before committing to a single locality in a full calculation. For precise figures, though, a representative table should be treated as a directional guide, not a substitute for running the exact locality through an RVU calculator or GPCI calculator, since even neighboring localities can have meaningfully different index values.
RVU Is Not Reimbursement — And wRVU Is Not Medicare Payment RVU
This distinction matters more than almost anything else on a CPT RVU page, because it’s the single most common source of confusion:
- Total RVU (work + PE + MP, GPCI-adjusted, multiplied by the conversion factor) is what produces an actual Medicare payment estimate for a claim.
- wRVU used in physician compensation models is a completely separate application of the same underlying work RVU value. Many employers pay physicians a fixed, contract-defined dollar rate per wRVU generated — but that compensation rate is set by the employer or contract, not by CMS, and it has no fixed mathematical relationship to what Medicare actually reimburses for the visit.
In other words, a physician can generate 1.50 work RVUs on a visit and be compensated under an employer’s formula of wRVU × contracted compensation rate, while the same visit’s actual Medicare reimbursement depends on the full GPCI-adjusted total RVU times the conversion factor — a different calculation entirely, often producing a different dollar figure. Anyone using a wRVU calculator for compensation modeling and a Medicare reimbursement calculator for payment estimation should expect these numbers to diverge, and that’s expected, not an error.
How to Use a CPT-Specific RVU Page Correctly
- Confirm the code and setting first. Coding and code selection should happen before payment modeling — a CPT RVU page is not a coding reference and shouldn’t be treated as guidance on which code to bill.
- Check the year. RVU values, GPCI figures, and the conversion factor are all updated on an annual cycle through CMS rulemaking. A page or calculator that doesn’t specify which year’s data it’s using should be treated cautiously.
- Identify facility vs. non-facility. This changes the PE RVU component and can shift the payment estimate meaningfully.
- Select the exact locality, not a representative or regional approximation, when the estimate needs to be precise.
- Run the numbers through an RVU calculator rather than manually recomputing GPCI-weighted totals, especially when comparing several codes or localities at once.
- Treat the output as an estimate. Modifiers, bundling edits, sequestration, MIPS payment adjustments, and secondary payer rules can all move the actual claim payment away from the baseline MPFS calculation.
Common Misreadings to Avoid
- Treating a single GPCI number as applying uniformly to the whole RVU total, rather than separately to work, PE, and MP components.
- Assuming the conversion factor is a fixed number that doesn’t change — it’s updated annually and, starting in 2026, splits by APM participation status.
- Using a wRVU-based compensation figure as a stand-in for what Medicare actually pays for the same service.
- Ignoring the facility/non-facility distinction on the PE RVU component, which can shift the payment estimate by a meaningful margin for procedure-heavy codes.
- Applying commercial payer logic to a Medicare-based RVU calculation — commercial payers frequently use their own fee schedules or a percentage-of-Medicare methodology, which is not identical to the MPFS formula itself.
For anyone regularly pulling CPT-level data, pairing the code lookup with a broader RVU calculator for quick recalculation, a GPCI calculator when comparing multiple localities side by side, and a separate wRVU calculator when the goal is modeling physician compensation rather than estimating a Medicare claim, keeps these three related but distinct questions from getting blended into one number that doesn’t actually answer any of them precisely.