State-level GPCI review is a navigation layer for CMS payment localities. The actual payment adjustment is locality-based and component-specific, so state comparisons should always resolve to Work, PE, and MP GPCI values before calculating payment.
Locality is more specific than state
Some states have a single CMS locality, while larger states may contain multiple localities with distinct values. A state page helps find the right market, but the payment estimate should use the precise locality that applies to the city, county, or practice area being reviewed.
- Use state pages as an index.
- Use locality pages for calculation.
- Avoid averaging localities unless the analysis explicitly requires it.
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 RVU component has its own GPCI
GPCI is not one multiplier. Work GPCI adjusts work RVU, PE GPCI adjusts practice expense RVU, and MP GPCI adjusts malpractice RVU. The effect depends on the code's component mix, which is why two CPT codes can rank localities differently.
- Compare Work, PE, and MP separately.
- Keep CPT and setting fixed in comparisons.
- Use total RVU to evaluate the combined effect.
High PE or MP localities can change payment materially
Office services with higher non-facility practice expense can be sensitive to PE GPCI, while procedure-heavy services may show visible malpractice effects. A professional comparison should document the selected CPT, setting, locality, and participant status so the geography effect is clear.
- Model office services with the non-facility PE value.
- Check malpractice-heavy services separately.
- Document locality and setting with every estimate.