Free Adequacy Audit

Get yours free
Blueprint
Rural MarketsCMS ComplianceNetwork Build

Rural Provider Strategy: What Actually Works in Frontier Counties

MW

Marcus Webb

Compliance & Regulatory Lead

August 30, 2024 6 min read

An honest assessment of frontier county adequacy — when exception documentation is the right strategy versus continued recruitment, how to identify willing rural providers, what FQHCs and RHCs contribute, and how to document good faith effort properly.

Frontier Counties Require a Different Framework

The dominant approach to frontier county network adequacy — treating it as the same problem as urban network adequacy, just harder — produces consistently poor outcomes. Plans recruit against a provider pool that does not exist, spend outreach resources on providers who will never contract, and arrive at the HPMS submission with a thin exception file built from an outreach campaign that was never designed to succeed. This is not a strategic failure specific to one plan. It is a sector-wide failure to accept what frontier county adequacy actually is.

Frontier counties — those classified as the most rural tier under CMS's county-type framework, typically corresponding to RUCC codes 7 through 9 — do not have the provider density that CMS's foundational adequacy standards assumed. The standards were built against an idealized market structure that does not exist in frontier markets. CMS acknowledges this reality through its time-distance standards for frontier counties, which are explicitly more permissive than the standards for urban and suburban counties, and through the exception mechanism that exists precisely for markets where compliant networks are genuinely not achievable.

The correct framework for frontier county adequacy has two tracks: recruit the rare providers who will contract, and build an exception documentation record for the counties where no provider will. Running both tracks simultaneously, from the beginning of the build cycle, is the only approach that produces a defensible HPMS submission.

What CMS Actually Expects in Frontier Markets

CMS's adequacy standards for frontier counties are calibrated to the available provider market, not to the standards applicable in suburban markets. Time-distance thresholds for frontier counties are substantially wider — in some specialties, CMS's frontier standards allow travel times of 60 to 90 minutes where the urban standard would require 30. This matters strategically: before building your outreach target list for frontier counties, verify which standard applies. Plans that model frontier counties against the wrong time-distance standard will either over-recruit in achievable markets or build weak exception cases for markets that are not actually deficient under the applicable standard.

For counties where no provider will contract even under the permissive frontier standards, CMS's exception process requires a documented demonstration of good faith effort and, in most cases, a description of alternative access arrangements for plan members. Good faith effort under CMS guidance means multiple documented outreach attempts across different channels over a sustained period — not a pro forma letter, but a traceable record that shows the plan genuinely tried to contract a provider and the market did not yield one.

CMS analysts reviewing frontier county exception requests are generally not surprised by the finding that no provider would contract. What they are evaluating is whether the plan made genuine effort and whether members in that county have a realistic pathway to care. Plans that can answer both questions affirmatively — with documentation — have a defensible exception. Plans that cannot have a deficiency problem.

Identifying Providers Who Will Contract in Frontier Markets

The providers most likely to contract in frontier markets are not the same providers who respond to standard outreach campaigns. The profile matters: rural providers who participate in Medicare Advantage networks tend to be independent practitioners, not health system employed physicians; they are often motivated by patient volume concerns rather than rate considerations; and they have a history of working with health plans, which is visible in PECOS enrollment data.

Effective frontier recruitment targets the right providers rather than all providers. Before launching outreach in a frontier county, cross-reference the target list against three signals: current Medicare FFS enrollment (providers enrolled in Medicare FFS are more likely to be comfortable with MA contracting), prior participation history with any MA plan (visible in plan data if you have it, or inferred from PECOS), and practice setting (independent and critical access hospital-affiliated providers are more accessible than large system-employed physicians who require health system contracting authority).

The outreach approach in frontier markets also differs from urban campaigns. Rural providers respond to relationship and community framing, not volume optimization arguments. The value proposition that works in an urban market — "access to a large MA patient panel" — is irrelevant in a county with 3,000 residents. The value proposition that sometimes works in frontier markets is simpler: community continuity (keeping patients in-network with a provider they already see), administrative support (credentialing assistance, simplified billing), and rate certainty over multi-year terms. Plans that approach frontier outreach with the same pitch deck they use in urban markets should not be surprised when it does not convert.

The Role of FQHCs and RHCs in Frontier Adequacy

Federally Qualified Health Centers and Rural Health Clinics occupy a specific and important position in frontier adequacy strategy. FQHCs and RHCs operate under federal designation requirements that make them permanent fixtures in the communities they serve — they are not going to close, relocate, or leave the market. For a plan building a network in frontier counties, an FQHC or RHC contract is one of the most durable adequacy arrangements available.

The contracting dynamic is different than with private-practice providers. FQHCs operate under Prospective Payment System rates for Medicaid and have different rate structures for Medicare Advantage — plans need to be prepared to negotiate against the PPS baseline rather than their standard fee schedule. RHCs have similar cost-based reimbursement structures that require a different rate model than the plan may use for standard primary care contracts.

Despite the contracting complexity, FQHC and RHC agreements contribute meaningfully to frontier adequacy in two ways: they satisfy primary care and some behavioral health adequacy requirements in counties where no alternative exists, and they signal to CMS that the plan has secured a stable, community-rooted provider relationship. In exception request packages for counties with only partial adequacy, an FQHC or RHC contract demonstrating primary care access significantly strengthens the narrative around specialty care gaps that could not be filled.

In frontier markets, the question is never whether the network will be perfect. It is whether the plan can demonstrate genuine effort, secure the providers who will contract, and document the rest honestly. That is the standard CMS actually applies, and it is achievable — but only if the plan stops treating frontier adequacy as a solvable recruitment problem and starts treating it as a documentation and relationship problem.

Plans that build this framework from the first month of the build cycle — segmenting frontier counties immediately, launching targeted outreach against the right provider profiles, engaging FQHCs and RHCs early, and building the exception documentation record in parallel — will file cleaner submissions and spend less time in deficiency remediation than plans that discover the frontier challenge in month ten. The providers are limited. The documentation and the strategy are entirely within the plan's control.

About the Author

MW

Marcus Webb

Compliance & Regulatory Lead · Blueprint

Marcus tracks CMS regulatory developments and helps Blueprint clients navigate network adequacy compliance. Before Blueprint, he served as a compliance officer at a top-10 Medicare Advantage payer.

Blueprint Platform

Ready to see Blueprint in action?

Schedule a demo to see how Blueprint handles the network adequacy challenges we write about — from gap analysis to HPMS submission.

Schedule a Demo