GPCI values are Medicare geographic adjustment factors used in Physician Fee Schedule payment estimates. They are locality-based, not simply state-based, and they adjust work, practice expense, and malpractice RVU components separately. A state page is useful for navigation, but the payment estimate should use the exact CMS locality that applies to the city, county, or market being modeled.
GPCI is locality-based
CMS payment localities are the operational unit for GPCI adjustment. Some states have one locality, while others have multiple localities with different Work, PE, and MP values. California is a clear example: a statewide average would hide meaningful differences between localities. For professional modeling, use the state page to find the locality, then use the locality page or calculator for the actual estimate.
- Use states for navigation, not as a substitute for locality selection.
- Use exact locality values when modeling a city, county, or practice market.
- Do not average localities unless the analysis explicitly requires an aggregate view.
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.
- Code input
- CPT/HCPCS
- Setting input
- Facility or office
- Output
- Adjusted total RVU
Each GPCI component adjusts a different RVU input
GPCI is not one geography multiplier. Work GPCI applies to work RVU, PE GPCI applies to the selected facility or non-facility practice expense RVU, and MP GPCI applies to malpractice RVU. This component-level adjustment matters because different CPT codes have different component mixes. An office E/M code may be more sensitive to PE GPCI, while a procedure with higher malpractice RVU may show a different pattern.
- Work GPCI adjusts the work RVU component.
- PE GPCI adjusts the selected practice expense RVU.
- MP GPCI adjusts the malpractice RVU component.
How state comparisons should be built
A defensible state comparison holds the CPT code, setting, participant status, and volume constant. Then it changes only the locality. If the code mix changes across states, the result reflects both geography and clinical service mix. If QPP status changes at the same time, the result also includes a policy assumption. Clean comparisons isolate one variable so finance, billing, and compensation users can interpret the result correctly.
- Hold CPT or code mix constant across localities.
- Use the same facility or non-facility setting in every scenario.
- Keep non-QPP and QPP/APM status labeled separately.
Why PE and MP values can move the estimate
Users often focus on Work GPCI because work RVU is familiar from physician compensation. Medicare payment, however, includes practice expense and malpractice components. For office-heavy services, a locality with higher PE GPCI can materially affect the non-facility estimate. For procedure-heavy services or specialties with higher professional liability assumptions, MP GPCI can also contribute to the final payment difference.
- Office-based services can be sensitive to PE GPCI.
- Procedure-heavy services can show meaningful MP effects.
- The final estimate depends on the CPT component mix, not just the locality name.
Use GPCI carefully in contract analysis
GPCI affects Medicare payment estimates, but physician compensation contracts may use work RVU without geographic payment adjustment. A practice may consider geography when setting salaries or rates, but that is a compensation policy decision, not the same as the Medicare GPCI formula. When reviewing a contract, separate Medicare locality payment from annual wRVU targets, dollars-per-wRVU rates, and local market salary assumptions.
- Medicare GPCI changes payment estimates, not automatically contract credit.
- Compensation plans may use national wRVU values without GPCI adjustment.
- Local market salary review should be modeled separately from Medicare payment.
Recommended workflow
Start at the state page to identify relevant localities, open the locality page for Work, PE, and MP values, then run a CPT-specific GPCI calculator with a fixed code and setting. For broader analysis, repeat the same scenario across localities or use bulk calculation with the same code mix. Keep the locality name in any copied result so the estimate remains traceable.
- Find the locality before calculating payment.
- Use CPT-specific estimates instead of reading one GPCI value in isolation.
- Save locality, setting, and conversion factor assumptions with the result.