Calculators

How to Calculate wRVU Step by Step

Use CPT codes, GPCI localities, and conversion factors to estimate payment.

Reviewed
2026-06-29
Updated
2026-06-29
Source
CMS 2026 RVU and GPCI source context

Interpret then calculate

Keep the article as the explanation layer and move into the related tool only after the relevant CPT, locality, or benchmark assumption is clear.

Use when
You are reading about how to calculate wRVU and need to apply it to a concrete RVU workflow.
Source role
Hand-reviewed article copy plus related tool links keep assumptions traceable.
Boundary
This article is not the calculator output, coding advice, payer adjudication, or contract review.

A reliable wRVU workflow starts by separating two questions that are often mixed together: what work RVU is assigned to the CPT or HCPCS code, and what Medicare payment estimate results after practice expense, malpractice, GPCI, setting, and conversion factor assumptions are applied. Work RVU is a component. Payment is a formula result. RVUinUSA keeps those steps separate so users can audit the assumptions behind every number.

Start with a supported CPT or HCPCS code

The first step is code identification. RVU tools should not be used to choose a higher-paying code. They should be used after the coding basis is established through the appropriate documentation, payer, and compliance process. Once the code is selected, the CMS RVU dataset supplies work RVU, non-facility PE RVU, facility PE RVU, and malpractice RVU values. Adjacent codes can differ materially, so code-level review is more reliable than specialty averages.

  • Confirm the CPT or HCPCS code before using the RVU calculator.
  • Use code-level RVU values rather than generic specialty averages for payment modeling.
  • Compare adjacent codes only when each code is independently supportable.

How this connects to RVU payment

GPCI is applied component by component. A locality comparison is only meaningful when the CPT code, setting, and participant status stay fixed.

Locality-adjusted RVU formula
(Work RVU x Work GPCI) + (PE RVU x PE GPCI) + (MP RVU x MP GPCI)
Assumptions
Code input
CPT/HCPCS
Setting input
Facility or office
Output
Adjusted total RVU

Read work RVU as the productivity component

Work RVU represents the physician work component assigned to the service. It is the number most often used in productivity plans, benchmark comparisons, and contract thresholds. It does not include practice expense, malpractice expense, geographic adjustment, or the Medicare conversion factor. That is why wRVU can be useful for compensation analysis while still being insufficient for Medicare payment estimates.

  • Use wRVU for productivity and contract target context.
  • Do not estimate Medicare payment from work RVU alone.
  • Check whether the contract uses current-year or frozen RVU values.

Choose facility or non-facility setting

For many services, the same CPT code has one work RVU but different practice expense values depending on setting. Non-facility practice expense is often higher for office-based services because the professional payment carries more practice cost. Facility practice expense is often lower because resources may be paid through the facility side. The setting decision can materially change total RVU while leaving work RVU unchanged.

  • Select non-facility for office-based professional estimates when appropriate.
  • Select facility when the professional service is furnished in a facility context.
  • Never compare two scenarios unless the setting assumption is clearly labeled.

Apply GPCI values component by component

GPCI is not one geography multiplier. Work GPCI adjusts work RVU, PE GPCI adjusts the selected practice expense RVU, and MP GPCI adjusts malpractice RVU. The adjusted total RVU formula is: work RVU times Work GPCI, plus selected PE RVU times PE GPCI, plus MP RVU times MP GPCI. This component-level formula is why local payment can vary even when the same CPT code is used.

  • Apply Work GPCI only to work RVU.
  • Apply PE GPCI only to the selected facility or non-facility PE RVU.
  • Apply MP GPCI only to malpractice RVU.

Multiply by the correct conversion factor

After adjusted total RVU is calculated, multiply by the applicable conversion factor. In 2026, RVUinUSA models $33.4009 for non-QPP estimates and $33.5675 for QPP/APM estimates. This final step turns adjusted total RVU into a Medicare payment estimate. It does not change work RVU and should not be confused with a contract's dollars-per-wRVU rate.

  • Use non-QPP unless QPP/APM status applies.
  • Keep QPP and non-QPP estimates labeled separately.
  • Do not treat the Medicare conversion factor as a compensation rate unless the contract says so.

Document assumptions before using the result

A defensible RVU result should include the CPT code, RVU data year, setting, locality, participant status, conversion factor, and intended use. The same output can be misleading if reused for a different purpose. Billing analysis, physician productivity, contract negotiation, and service-line forecasting all use RVU data differently. Copying the number without the assumptions removes the audit trail.

  • Save the source year and conversion factor with the estimate.
  • Label whether the result supports payment, productivity, or contract review.
  • Recalculate when code, setting, locality, or participant status changes.

FAQs

Can I calculate Medicare payment from wRVU alone?

No. Medicare payment requires practice expense RVU, malpractice RVU, GPCI adjustment, setting, and the conversion factor.

Why does setting matter if work RVU is unchanged?

The practice expense RVU can differ between facility and non-facility settings, changing total RVU and payment while work RVU stays the same.

What is the safest RVU calculation workflow?

Confirm code, read RVU components, choose setting, apply GPCI, select participant status, multiply by the conversion factor, and keep assumptions attached.

Is wRVU a coding rule?

No. wRVU is a payment and productivity input after code selection; it does not determine whether a service is correctly coded.