Texas does not have one Medicare payment rate. It has multiple CMS payment localities — Austin, Beaumont, Brazoria, Galveston, and several others — and each one carries its own Work GPCI, Practice Expense (PE) GPCI, and Malpractice (MP) GPCI values. If you’re trying to estimate Medicare reimbursement for a CPT code performed in Texas, the state name alone isn’t enough information. You need the specific locality tied to the county where the service was rendered.
Why Texas Has More Than One GPCI Value
The Geographic Practice Cost Index (GPCI) exists because the cost of running a medical practice — staff wages, office rent, malpractice insurance — is not uniform across the country, or even within one state. CMS assigns a GPCI value to each of the three RVU components (work, practice expense, and malpractice) for every payment locality.
Texas is divided into several distinct fee schedule localities, each tied to specific counties. Travis County (Austin) sits in locality 31, Jefferson County (Beaumont) sits in locality 20, and Brazoria County has its own designation as well. A rural Texas county and a major metro county can carry meaningfully different GPCI values, which is why the GPCI calculator should be run at the locality level, not the state level, whenever the output will inform an actual payment or compensation decision.
The Three GPCI Components
| Component | Applies To | What It Reflects |
|---|---|---|
| Work GPCI | Work RVU | Relative cost-of-living and opportunity cost differences for physician work by area |
| PE GPCI | Practice Expense RVU | Local office rent, staff wages, equipment, and supply costs |
| MP GPCI | Malpractice RVU | Regional differences in professional liability insurance premiums |
Each GPCI multiplies only its matching RVU component — Work GPCI never touches the PE RVU, and PE GPCI never touches the MP RVU. Blending them into a single “Texas adjustment factor” produces an inaccurate estimate, because the three components don’t move at the same rate across localities.
The Medicare Payment Formula
CMS calculates the Medicare Physician Fee Schedule (MPFS) national payment amount for a CPT or HCPCS code using this formula:
Payment = [(Work RVU × Work GPCI) + (PE RVU × PE GPCI) + (MP RVU × MP GPCI)] × Conversion Factor
Each RVU component is geographically adjusted before the totals are summed, and only then is the result multiplied by the Conversion Factor (CF) — a single national dollar-per-RVU figure set annually by CMS. This is the calculation logic behind RVUinUSA’s Medicare reimbursement calculator: the tool applies locality-specific GPCI to each component separately, then applies the applicable CF, rather than treating the whole calculation as one flat multiplier.
The 2026 Conversion Factor Change
Starting with calendar year 2026, CMS uses two separate conversion factors instead of one, as required by the statute passed in 2025:
| Conversion Factor Type | CY 2026 Value | Change from CY 2025 ($32.35) |
|---|---|---|
| Qualifying APM participant (QP) | $33.57 | +$1.22 (+3.77%) |
| Non-qualifying APM participant (non-QP) | $33.40 | +$1.05 (+3.26%) |
Source: CMS CY 2026 Physician Fee Schedule Final Rule (CMS-1832-F).
This split matters for any Texas-based payment estimate built after January 1, 2026. Which CF applies depends on whether the billing physician or group is a Qualifying Alternative Payment Model (APM) participant that year — not on which Texas locality is used. If you’re running numbers through a CPT RVU calculator, confirm which CF the tool defaults to before comparing results across time periods, since a QP/non-QP mismatch will make otherwise identical CPT codes look like they pay differently for reasons that have nothing to do with geography.
Worked Example: Austin Locality vs. a Comparison Locality
To isolate the geographic effect, the CPT code, place of service, and QP status must stay fixed while only the locality changes. The illustrative numbers below are example inputs only — not published CMS RVU or GPCI values for any specific code — and are meant to show how the formula behaves, not to represent an actual current payment.
Assume a hypothetical CPT code with:
- Work RVU: 1.00
- PE RVU: 1.20
- MP RVU: 0.10
- Non-QP conversion factor: $33.40 (CY 2026)
| Locality (illustrative) | Work GPCI | PE GPCI | MP GPCI | Calculated Payment |
|---|---|---|---|---|
| Locality A (example) | 1.00 | 0.95 | 0.90 | [(1.00×1.00)+(1.20×0.95)+(0.10×0.90)] × 33.40 = $74.48 |
| Locality B (example) | 1.02 | 1.05 | 1.10 | [(1.02×1.00)+(1.20×1.05)+(0.10×1.10)] × 33.40 = $79.83 |
The roughly $5.35 gap between the two example localities comes entirely from GPCI differences, because the CPT code, RVU inputs, and conversion factor were held constant. This is the discipline a real comparison needs: change one variable — locality — at a time. Running the same exercise with actual current-year RVU and GPCI data through a proper wRVU calculator or locality-specific GPCI tool will produce a defensible estimate; hand-waving a single “Texas multiplier” will not.
Where wRVU-Based Compensation Diverges from Medicare Payment
This is the point where Texas GPCI content most often goes wrong. Work RVU (wRVU) is the same underlying value used in both Medicare payment and physician compensation calculations, but what happens to it afterward is completely different.
| Medicare Payment Path | Physician Compensation Path | |
|---|---|---|
| Uses Work RVU | Yes | Yes |
| Applies Work GPCI | Yes | No — compensation plans typically use national (unadjusted) wRVU |
| Applies PE RVU and MP RVU | Yes | Not usually part of a wRVU compensation formula |
| Applies CMS Conversion Factor | Yes | No — replaced by an employer-negotiated dollar-per-wRVU rate |
| Governed by | CMS rules | Employment or physician compensation agreement |
A hospital or group in Austin might pay a physician $45 per wRVU. That $45 rate has no fixed relationship to the $33.40 (or $33.57) CMS conversion factor — it’s a number negotiated in the compensation plan, often benchmarked against MGMA or AMGA survey data. Treating “wRVU × Medicare CF” as an employee’s paycheck calculation, or treating “wRVU × compensation rate” as a Medicare claim payment, is one of the most common conceptual errors in this space, and it’s worth checking any compensation model against a dedicated physician compensation calculator rather than reusing a Medicare payment tool for both purposes.
Building a Reliable Texas Locality Workflow
A defensible Texas payment or compensation estimate follows a fixed sequence rather than mixing tools:
- Identify the exact county and confirm which CMS locality it falls under (Austin locality 31, Beaumont locality 20, etc.).
2. Pull the Work, PE, and MP GPCI values for that specific locality — not a statewide average.
- Pull the CPT or HCPCS code’s Work RVU, PE RVU (facility or non-facility, matching the actual site of service), and MP RVU for the applicable data year.
- Apply the formula: geographically adjust each component, sum them, then multiply by the correct CY 2026 conversion factor (QP or non-QP).
- Record the CPT code, locality, data year, site of service, and CF type alongside the resulting number so it can be reproduced or audited later.
Skipping step 5 is how spreadsheets full of unexplained numbers end up in a compensation dispute six months later. Documenting the assumptions is not optional if the output will support a contract negotiation, productivity review, or payer discussion.
What This Estimate Cannot Tell You
A GPCI-adjusted Medicare payment figure describes one payer’s fee schedule logic — it is not a commercial payer’s allowed amount, not a full practice revenue forecast, and not a substitute for reading the actual physician compensation agreement. Commercial insurers frequently use their own fee schedules that reference, but don’t copy, the Medicare RVU structure, and many contract a percentage of the Medicare rate rather than adopting it directly. Practice expense assumptions also shift materially between facility and non-facility settings, so a number pulled for a hospital-based service will not transfer cleanly to an office-based version of the same CPT code.
For coding compliance questions, payer-specific contract terms, or the legal interpretation of a compensation agreement, the GPCI and RVU calculations here should inform the discussion — not replace review by a qualified biller, contracts specialist, or compensation consultant.