localis

Describe a service in plain words, or type a CPT/HCPCS code.

Medicare payment locality · Q2 2017 release

Salinas, Ca flag

Salinas, Ca CA Medicare Locality 64

MAC 01112 · Locality 64

This locality's GPCIs are mixed, so the net payment effect varies by code for the Q2 2017 Physician Fee Schedule. For nationally priced services, Medicare adjusts each code's work, practice-expense, and malpractice RVUs using these indexes.

Work GPCI
1.024
Adjusts the physician-work component for professional labor costs
Practice expense GPCI
1.083
Adjusts practice-expense inputs such as staff, rent, and services
Malpractice GPCI
0.610
Adjusts the malpractice component using liability-cost data

1.000 is the national baseline. Above raises that component; below lowers it. GPCIs are Medicare payment factors, not general cost-of-living or physician-compensation indexes.

Example rates in Salinas, Ca Copy link

National vs. Salinas, Ca office (non-facility) amounts for frequently reviewed codes, Q2 2017 (before sequestration). Conversion factor: 2017 standard (non-QP) physician conversion factor · $35.8887.

Code National Salinas, Ca Difference
99214 $108.74 $112.89 +3.8%
99213 $73.93 $76.82 +3.9%
99215 $146.43 $151.57 +3.5%
66984 $651.02 $676.66 +3.9%
99204 $166.16 $171.08 +3.0%
92014 $125.25 $131.62 +5.1%
97110 $33.02 $34.47 +4.4%
88305 $69.62 $73.31 +5.3%
97530 $35.53 $37.38 +5.2%
99203 $109.46 $112.99 +3.2%

Need a specific code or a facility rate? Use the rate calculator with this locality selected. Or start from your field's usual procedure mix on the specialty fee schedules.

Common questions Copy link

Why do Medicare rates in Salinas, Ca differ from the national amount?
For nationally priced Physician Fee Schedule services, Medicare adjusts each code's work, practice-expense, and malpractice RVUs by this locality's three GPCIs before applying the conversion factor. Local professional labor, office-input, and liability costs therefore move the final amount up or down. Salinas, Ca currently has mixed GPCI components, so the net payment effect varies by code for the Q2 2017 release.
How do I know if my address is in this locality?
Medicare payment localities are geographic fee-schedule areas, commonly defined with county boundaries. CMS uses the service-location ZIP code to map a claim to the applicable carrier and locality. Look up your ZIP to find your locality. A few ZIPs nationally span multiple localities and need ZIP+4 to resolve exactly.
Do commercial insurers or Medicare Advantage plans use this locality?
Original Medicare uses these PFS localities directly. Commercial and Medicare Advantage plans are not required to use the same locality structure. A contract may benchmark payment to Medicare, but its language controls the Medicare release, percentage, geographic basis, and other adjustments.
Does my locality affect what I owe as a patient?
For a particular covered service, a higher locality-adjusted allowed amount generally produces a higher percentage-based coinsurance amount. The effect depends on the code, the beneficiary's deductible, supplemental coverage, and other claim circumstances.
Why did my Medicare payment change even though I didn't change what I billed?
CMS publishes updated PFS files during the year. A code's amount can change because of conversion-factor, RVU, policy, or correction updates. GPCI policy values are generally established through annual rulemaking, although later files can contain corrections. See what changed each release.

Source & method Copy link

GPCIs and rates computed from the CMS Medicare Physician Fee Schedule Q2 2017 release (effective April 2017). Example amounts use the standard (non-QP) physician conversion factor ($35.8887) and apply this locality's GPCIs to nationally priced non-facility RVUs, before the ~2% sequestration cut. Releases are immutable: a rate retrieved for a past quarter always reflects that PFS release.

Did this answer your question about Salinas, Ca (CA)?

We're building this out in the open. Tell us what you were actually trying to work out and we'll either answer you directly or build the page that does.

Did this page answer your question?