GPCI is used to adjust Medicare Physician Fee Schedule RVU components for geographic differences. The important limitation is that GPCI is assigned to a Medicare payment locality, not to a state average. A state is useful for finding possible records; the locality is the record used in the calculation.
This page is a navigation and methodology guide. It does not present one invented statewide GPCI number. When a state contains multiple localities, using an average can hide the exact Work, PE, and MP factors that produced an estimate.
State and locality answer different questions
| Label | Useful for | Not sufficient for |
|---|---|---|
| State | Filtering and finding possible Medicare localities | Choosing the exact Work, PE, and MP GPCI record |
| Medicare locality | Applying component-specific GPCI to a payment estimate | Choosing a CPT code or predicting a payer’s allowed amount |
GPCI is three component adjustments
GPCI is not one multiplier applied to a total RVU:
Adjusted total RVU =
(Work RVU x Work GPCI)
+ (Selected PE RVU x PE GPCI)
+ (MP RVU x MP GPCI)- Work GPCI adjusts the work RVU.
- PE GPCI adjusts the selected facility or non-facility practice-expense RVU.
- MP GPCI adjusts the malpractice RVU.
The GPCI Calculator is the fastest way to inspect the component values. The RVU Calculator combines them with a selected CPT code, setting, and conversion factor.
Examples of state-to-locality navigation
Use the state name to narrow the search, then open the relevant locality guide or calculator:
| State or area | Why a locality check matters | Related guide |
|---|---|---|
| California | Multiple locality records can produce different component factors. | California GPCI guide |
| Florida | The current site dataset distinguishes Fort Lauderdale, Miami, and Rest of Florida. | Florida GPCI guide |
| New York | City and surrounding-area records should be checked rather than treated as one state value. | New York GPCI guide |
| Texas | County-to-locality mapping can determine which record applies. | Texas GPCI guide |
These linked guides explain how to identify the applicable record. They should not be read as permission to substitute a state average for a known locality.
How to build a defensible comparison
- Record the practice or service location.
- Find the CMS Medicare locality that covers that location.
- Record Work, PE, and MP GPCI separately.
- Keep the CPT code and facility setting fixed when comparing localities.
- Use the same data year and conversion-factor status in every scenario.
- Save the locality name beside the copied result.
If the code mix changes between states, the result measures both geography and clinical mix. If QP status or setting changes too, the comparison contains additional variables and should be labeled accordingly.
GPCI is not a compensation adjustment
GPCI changes a Medicare payment estimate. A physician compensation plan may use work RVU without geographic adjustment, or it may use a separate market-based rate. Do not apply GPCI to a contract model unless the written agreement requires it.
For the difference between payment and compensation inputs, see wRVU vs Total RVU and the physician productivity benchmark guide.
FAQ
Does every state have one GPCI?
No. Some states have one locality and others have multiple Medicare localities. The applicable locality is the calculation record.
Can I calculate payment from the state name alone?
Not reliably when the state is split into multiple localities. Find the locality first, then apply its component GPCI values.
Which GPCI component matters most?
It depends on the CPT code and selected setting. Work, PE, and MP contributions should be reviewed separately.