Malpractice RVU (MP RVU) is the professional liability component of the Medicare Physician Fee Schedule’s relative value unit structure — it’s the third input, alongside work RVU and practice expense RVU, that CMS uses to calculate total RVU for a CPT or HCPCS code. It is not a physician’s actual malpractice insurance premium, and it is not part of most wRVU-based compensation formulas. It’s strictly a payment-side variable that feeds into the Medicare reimbursement calculation.
What Malpractice RVU Actually Measures
CMS assigns every CPT and HCPCS code three separate RVU values under the Resource-Based Relative Value Scale (RBRVS):
| Component | What it captures |
|---|---|
| Work RVU | Physician time, skill, effort, and judgment required to furnish the service |
| Practice Expense (PE) RVU | Overhead — staff, supplies, equipment, and clinical space needed to deliver the service |
| Malpractice (MP) RVU | Professional liability insurance cost associated with furnishing that specific service |
MP RVU is built from specialty-level professional liability insurance premium data that CMS collects and aggregates, then allocates across services based on the relative liability risk of the clinical activity involved. That means MP RVU reflects a service-level liability assumption, not an individual physician’s actual premium, claims history, or state-specific malpractice environment. Two physicians performing the identical CPT code get the identical MP RVU input, even if their actual insurance costs differ substantially by specialty, state, or carrier.
For most evaluation and management (E/M) codes, MP RVU is a small fraction of total RVU — often under 5%. For surgical, obstetric, and other invasive or higher-liability procedure codes, the malpractice share of total RVU is typically larger, sometimes reaching into the double digits as a percentage of the total. This isn’t a fixed rule for every code; it depends on how CMS’s liability data classifies the specific service.
Where MP RVU Sits in the Total RVU Formula
Total RVU for a code is the sum of all three components, and each component is adjusted separately by its own Geographic Practice Cost Index (GPCI) before the components are combined:
National (unadjusted) Total RVU = Work RVU + PE RVU + MP RVU
Locality-adjusted Total RVU = (Work RVU × Work GPCI) + (PE RVU × PE GPCI) + (MP RVU × MP GPCI)
The critical detail — and one that’s easy to get wrong when building a payment estimate by hand — is that each RVU component is multiplied only by its matching GPCI. MP RVU is never multiplied by Work GPCI or PE GPCI, and Work RVU is never multiplied by MP GPCI. Collapsing all three GPCIs into a single blended locality multiplier will produce an inaccurate estimate, because Work, PE, and Malpractice GPCIs frequently move independently of each other in the same locality. A metro area can have a Work GPCI close to the national average of 1.000 while carrying a materially higher or lower MP GPCI, driven by that area’s professional liability insurance market rather than its labor costs.
From Total RVU to Medicare Payment
Total RVU alone is not a dollar amount. To translate RVUs into an actual payment estimate, CMS applies a conversion factor (CF) — a dollar figure updated annually (and, starting in CY 2026, split into two separate rates depending on participation status) that converts RVUs into a payment amount:
Estimated Medicare Payment = GPCI-adjusted Total RVU × Conversion Factor
For context on how much the conversion factor can move year to year: CMS set the CY 2025 conversion factor at $32.35, down about 2.83% from the CY 2024 rate of $33.29. For CY 2026, CMS finalized two separate conversion factors as required by statute — $33.57 for qualifying Advanced Alternative Payment Model (APM) participants and $33.40 for everyone else, both increases from the CY 2025 figure. This is exactly why MP RVU, GPCI values, and conversion factors should always be treated as year-specific inputs rather than fixed constants — a payment estimate built on last year’s conversion factor will be off even if every RVU value is correct.
Illustrative Calculation (Example Values Only)
The numbers below are illustrative values used only to show the mechanics of the formula; they are not official CMS RVU data for any specific CPT code.
| Step | Example Value |
|---|---|
| Work RVU | 1.50 |
| PE RVU | 0.90 |
| MP RVU | 0.10 |
| Work GPCI (example locality) | 1.02 |
| PE GPCI (example locality) | 0.98 |
| MP GPCI (example locality) | 1.15 |
| GPCI-adjusted Total RVU | (1.50 × 1.02) + (0.90 × 0.98) + (0.10 × 1.15) = 1.53 + 0.882 + 0.115 = 2.527 |
| Conversion Factor (example) | $33.40 |
| Estimated Medicare Payment | 2.527 × $33.40 ≈ $84.40 |
Notice how the MP GPCI of 1.15 in this example is meaningfully higher than the Work and PE GPCIs — this is the kind of divergence that makes locality-specific malpractice adjustment worth checking separately rather than assuming it tracks the same trend as work or overhead costs.
Why MP RVU Rarely Shows Up in Physician Compensation
This is the point where a lot of RVU content goes wrong, so it’s worth stating plainly: MP RVU is a Medicare payment input, not a compensation input.
| Context | Which RVU applies |
|---|---|
| Medicare Physician Fee Schedule payment | Work RVU + PE RVU + MP RVU (all GPCI-adjusted) |
| Typical wRVU-based physician compensation plan | Work RVU only |
| Practice-level revenue or productivity reporting | Depends on the contract — some use total RVU, most compensation formulas use wRVU |
Most employed-physician compensation agreements are built around work RVU, dollars-per-wRVU rates, and productivity thresholds — not total RVU and not malpractice RVU specifically. A physician generating wRVUs under a compensation contract isn’t being credited for the malpractice liability component of the codes they bill; that component exists purely to help CMS calculate what Medicare pays the practice, not what the practice pays the physician. If a compensation agreement does reference total RVU explicitly, the written contract terms — not a general assumption about RVU methodology — determine whether MP RVU factors into the calculation. Confusing wRVU-based compensation with Medicare’s RVU-based reimbursement methodology is one of the most common errors in physician compensation discussions, and MP RVU is a clear example of a component that belongs to one side of that distinction and almost never the other.
When MP RVU Actually Moves the Number
MP RVU’s practical impact depends on two variables working together: how large the code’s MP RVU is relative to its total RVU, and how far the locality’s MP GPCI diverges from 1.000 (the national average).
- Low-impact scenario: A routine office visit E/M code with a small MP RVU, billed in a locality where MP GPCI is close to the national average — the malpractice component barely moves the final payment estimate.
- Higher-impact scenario: A surgical or obstetric CPT code with a proportionally larger MP RVU, billed in a locality where MP GPCI is well above or below 1.000 — the malpractice adjustment can shift the estimate by a visible margin, especially when that shift is compared against a different locality’s numbers for the same code.
This is a useful checkpoint when comparing Medicare payment estimates for the same CPT code across two different metro areas or states: if the difference looks larger or smaller than expected based on cost-of-living intuition alone, checking the MP GPCI specifically (rather than assuming all three GPCIs move together) usually explains the gap.
Using This in a Calculator Workflow
To get an accurate locality-adjusted estimate rather than a rough approximation, a Medicare payment calculation needs four separate inputs pulled at the CPT/HCPCS code level: Work RVU, PE RVU, MP RVU, and the three matching GPCI values for the target locality, plus the current-year conversion factor. Looking up a CPT code’s Work RVU, PE RVU, and MP RVU individually on a CPT RVU reference page — rather than only viewing a pre-summed total — makes it easier to spot when the malpractice component is unusually large relative to the rest of the code’s RVU profile.
For actual estimation, running the values through an RVU calculator or Medicare reimbursement calculator handles the GPCI-matching logic automatically, which avoids the common manual-math error of applying a single blended GPCI to all three components. A GPCI calculator focused specifically on locality comparisons is also useful when the goal is isolating how much of a payment difference between two areas comes from the malpractice adjustment versus the work or practice expense adjustments.
For compensation-related questions — how much a physician should be paid per wRVU, or how total RVU compares to work RVU under a specific contract — that’s a separate analysis from the Medicare payment estimate above, and it depends on the specific dollars-per-wRVU rate and crediting rules in the employment agreement rather than on MP RVU or the conversion factor at all. Keeping these two workflows — Medicare payment estimation and wRVU compensation analysis — separate is the single most useful habit for avoiding the reimbursement-versus-compensation confusion that comes up repeatedly in RVU discussions.