Use the Medicare payment locality, not the state label, when a GPCI-adjusted RVU estimate needs to be reproducible. A state is a navigation value. The locality is the record that supplies the Work, PE, and MP GPCI factors used in the payment formula.
This distinction matters because one state can contain several localities with different practice-expense and malpractice factors. A calculator that accepts only a state name cannot identify the correct record when the state is split.
State and locality answer different questions
| Input | What it is useful for | What it cannot establish by itself |
|---|---|---|
| State | Navigation, filtering, and identifying possible localities | The exact Work, PE, and MP factors for a practice location |
| Medicare locality | Selecting the component-specific GPCI records for payment modeling | The correct CPT code or payer-specific allowed amount |
Florida shows why the distinction matters
The 2026 dataset contains three Florida locality records:
| Locality | Work GPCI | PE GPCI | MP GPCI |
|---|---|---|---|
| Fort Lauderdale | 1.000 | 1.013 | 1.808 |
| Miami | 1.000 | 1.041 | 2.529 |
| Rest of Florida | 1.000 | 0.956 | 1.503 |
The state name alone cannot tell the calculator whether Miami or Rest of Florida applies. The user must select the locality that matches the practice or service location.
A controlled comparison with CPT 99213
Hold the code, setting, and conversion factor constant. With CPT 99213, the 2026 database uses a work RVU of 1.30, a non-facility PE RVU of 1.46, an MP RVU of 0.09, and a non-QP conversion factor of USD 33.4009.
| Locality | Non-facility estimate | Difference from Rest of Florida |
|---|---|---|
| Rest of Florida | USD 94.56 | Baseline |
| Fort Lauderdale | USD 98.26 | +USD 3.70 |
| Miami | USD 101.79 | +USD 7.23 |
The difference is produced by the component-specific locality factors, especially the MP GPCI in this example. It is not a difference in the CPT code or in the physician’s work RVU.
How the locality enters the formula
Adjusted total RVU =
(Work RVU x Work GPCI)
+ (Selected PE RVU x PE GPCI)
+ (MP RVU x MP GPCI)Because the components are multiplied separately, there is no generally valid shortcut that applies one state-wide factor to the total RVU. A shortcut can hide which part of the estimate changed.
When a state appears to work
Some states may have one locality record in a particular dataset. That does not make state and locality conceptually identical. The correct workflow is still to select the locality record and retain its name and data year. This keeps the estimate auditable if CMS later changes the locality map.
Recommended workflow
- Start with the state only to locate the possible locality records.
- Match the practice address, county, or service market to the applicable Medicare locality.
- Choose the CPT code and facility or non-facility setting.
- Use the GPCI Calculator to inspect Work, PE, and MP factors.
- Use the RVU Calculator with the selected locality and keep the assumptions visible.
FAQ
Can I choose GPCI by state?
Use the state to find the locality, but use the locality record for the actual Work, PE, and MP factors.
Why can two practices in one state receive different estimates?
They may be assigned to different Medicare payment localities with different GPCI values.
Does locality selection determine the CPT code?
No. Locality selection adjusts a selected code; it does not replace coding, documentation, or payer review.