Using Medicaid FFS Benchmarks in Capitation Rate Development

Capitation rate development for Medicaid managed care almost always starts somewhere near the state’s fee-for-service (FFS) rates — they’re public, they’re state-endorsed, and they give actuaries a consistent reference point across a population. But treating FFS as a direct stand-in for expected managed care cost is a common and costly mistake. Here’s how FFS data fits into the process, and where it doesn’t.

Why FFS is the natural starting point

FFS rates have three properties that make them useful as a baseline input:

• They’re public and auditable. Unlike negotiated MCO contract rates, FFS rates are a matter of public record, which means the assumption underlying your model can be checked by anyone reviewing it — regulators included.
• They’re state-endorsed. A state’s own FFS rate reflects that state’s own determination of appropriate reimbursement, which carries weight in rate-adequacy reviews and network-adequacy discussions.
• They’re consistent within a state. FFS rates don’t vary by which plan a beneficiary happens to be enrolled in, giving you a stable reference point to build utilization and unit-cost assumptions on top of.

Where the translation breaks down

FFS-to-capitation isn’t a straight multiplication. A few reasons why:

• MCOs negotiate their own provider rates, which can run above or below FFS depending on network dynamics, provider leverage, and geography — and those negotiated rates aren’t public.
• Utilization patterns differ under managed care, where care management, prior authorization, and network design change utilization in ways FFS claims history doesn’t capture.
• Administrative and risk load aren’t in the FFS number at all — FFS reflects provider reimbursement only, not the full cost structure a capitation rate needs to cover.

Actuaries typically use FFS as one input among several — alongside historical utilization, trend factors, and program-specific adjustments — rather than the sole basis for a capitation rate.

A practical approach

A reasonable way to incorporate FFS benchmarks without over-relying on them:

1. Use FFS as a unit-cost anchor, not a final answer — apply it as the starting reimbursement assumption per service, then layer utilization and trend on top.
2. Track FFS changes over time, since a state increasing its FFS rate is often an early signal that capitation rates in that program will be revisited at the next rate-setting cycle.
3. Flag material FFS/actual-experience gaps — if your plan’s actual claims experience diverges significantly from FFS-benchmarked expectations, that’s worth investigating rather than assuming the benchmark is simply wrong.

Why current data matters here specifically

Capitation models built on stale FFS data compound the more the underlying rates have moved since your last refresh. A state can update its fee schedule mid-cycle, and if your model doesn’t reflect that until the next annual rate-setting exercise, the gap between your assumption and current reality only grows. This is one of the more concrete reasons actuarial teams monitor FFS rate changes continuously rather than pulling a fee schedule once a year and treating it as static — which is exactly the workflow MedicaidBench’s alerts and cross-state comparison tools are built to support.