Free Network Build Assessment
Score your buildGuides, frameworks, and deep-dives for health plan network development teams: written for the people doing the actual builds.
CMS sets Medicare Advantage time-and-distance standards by provider type and county designation in 42 CFR 422.116 and the HSD Reference File. Here's how the standards work, where plans get them wrong, and how network ops teams should prepare their builds.
Read ArticleDual-eligible special needs plans have unique network requirements that sit at the intersection of Medicare and Medicaid standards. This playbook walks through a first-year D-SNP build from county selection to first submission.
Adequacy and access are often used interchangeably, but they measure different things, and failing one doesn't always mean failing the other. Understanding the distinction is critical for network ops teams managing CMS filings.
A failed adequacy review costs far more than staff time. For an applicant, it can cost the county. Here's what is at stake and how teams protect against it.
State Medicaid programs and CMS MA standards both set network requirements, but the standards, enforcement mechanisms, and filing cadences are very different. Here's a side-by-side breakdown for ops teams managing both.
Credentialing bottlenecks can derail a network build. These workflow patterns help contracting and credentialing teams stay in sync throughout the build cycle.
Not all counties are created equal. Some have abundant specialty providers; others are chronic adequacy gaps that require exception filings. A smart county selection strategy starts with adequacy modeling, not geography.
A single letter rarely gets a provider to answer. Sequenced, personalized outreach tied to a specific adequacy gap gives you a better shot. Here's the framework.
ACA marketplace network standards are set by CMS and enforced at the state level, and they differ significantly by state. This guide covers the essentials for issuers building or expanding Exchange networks.
A CMS filing date doesn't move. Your build timeline has to be engineered backwards from that date, accounting for credentialing cycles, adequacy modeling time, and contracting lead times. Here's how to build the plan.
Proven negotiation frameworks for moving providers from LOI to signed contract faster: without burning the relationship.
Rural counties are where network builds fail. Here are the strategies health plans use to meet adequacy when the provider supply is thin.
The most common errors network teams make in their annual adequacy filings, and exactly how to avoid each one.
Who does what in a network build? A practical guide to the roles, reporting lines, and tools each team member needs.
The connection between network quality, access to care, and Star ratings is direct, and most health plans underestimate it.
Bad provider data causes failed adequacy filings, wasted outreach, and compliance risk. Here's how to keep it clean.
Expanding into a new Medicaid market is a major undertaking. Here's how to plan the network build from day one.
Credentialing delays are the silent killer of network builds. Understanding the timeline is the first step to compressing it.
A failed adequacy review isn't the end, but how you respond matters a great deal. Here's the playbook.
Spreadsheets are free. But running a network build in Excel has costs that never show up in the tools budget. Here's where they hide, and how to work out your own number.
The HSD Reference File is the authoritative document CMS uses to set time-distance thresholds for Medicare Advantage network adequacy. Here's exactly what it contains and how to read it.
Outreach logs matter, but good-faith effort is not what wins a CMS exception. When a rural county lacks enough providers, here's what CMS actually asks for and how your documentation supports it.
A CMS deficiency notice isn't a denial, it's a request for corrective action. Here's how to respond effectively, what documentation CMS expects, and how to avoid repeat deficiencies.
Filing your adequacy submission isn't the end of your compliance obligation: CMS requires plans to maintain adequate networks year-round. Here's what ongoing monitoring looks like.
Provider network development drives every health plan's market entry and renewal strategy. This complete guide walks network development teams through the end-to-end build process: from county selection and HSD table planning to provider contracting and CMS submission.
Network adequacy is not a Star Ratings measure, but access runs through several of them. Poor access can show up in member experience scores, care gaps, and complaints. Here is how the connection works.
Telehealth's role in CMS network adequacy calculations has evolved significantly, but the rules are more restrictive than many plans assume. This guide clarifies exactly which telehealth arrangements satisfy adequacy standards and which do not.
Medicaid managed care network adequacy operates under a dual framework of federal minimum requirements and state-specific standards. Health plan teams navigating multi-state Medicaid portfolios need to understand exactly how these layers interact, and where state rules are stricter than CMS expects.
Provider directory rules for Medicare Advantage now have dates attached. This guide covers the accuracy requirements, a practical verification workflow, and the common failures health plan teams make.
There is no trustworthy national average for how long credentialing takes, so a rule of thumb won't protect your network build. This guide explains what drives the timeline, where it gets extended, and how to build a credentialing schedule that works.
Rural county Medicare Advantage network builds present provider supply constraints and exception request challenges that Large Metro builds rarely face. This playbook covers the strategies that work, and the common mistakes that waste time and budget.
Health plan teams evaluating network adequacy software need to look past polished demos to the workflow depth, data integration capabilities, and adequacy accuracy that determine real-world value. This guide covers the evaluation criteria that matter most.
Late CMS network adequacy filings rarely stem from a single catastrophic failure: they accumulate from a series of avoidable contracting process mistakes. These seven errors are the most common causes of filing delays in Medicare Advantage network builds.
The CMS HPMS network adequacy submission is complex, time-sensitive, and unforgiving of data errors. This step-by-step guide covers the preparation, data validation, and submission process that gives Medicare Advantage plans the best chance of a clean first submission.
Specialty provider shortages are the most common cause of Medicare Advantage network adequacy failures. Health plans can build systematic gap-filling strategies, rather than relying solely on direct contracting.
When CMS issues a network adequacy deficiency notice, plans have limited time and a specific process for appealing or responding. Understanding the appeals pathway, and how to build a compelling response, is essential for protecting your service area.
Provider outreach emails are easy to ignore, and a lot comes down to how the email is written and what it asks. These templates and principles will help you write ones that are worth a busy practice's time.
Dual Eligible Special Needs Plans meet the standard Medicare Advantage network rules, and their contract with the state Medicaid agency can add more. New plan teams need to understand where the requirements differ.
A Medicare Advantage network build is a complex, multi-threaded program with hard regulatory deadlines and no room for schedule drift. These project management practices help you file on time.
Federally Qualified Health Centers are among the most strategically important network partners for health plans serving Medicaid, Medicare Advantage, and Exchange populations. Understanding how FQHCs contribute to adequacy, and how to contract with them effectively, is essential for any plan building networks in underserved markets.
Many network teams still wait for an annual Call Letter to learn this year's adequacy standards. CMS doesn't publish them that way. Here's where the standards actually live, how they change, and what network ops teams should do before the filing window opens.
When the providers you need aren't available within CMS time-and-distance standards for a given specialty and county, plans can file an exception request. Here's what 42 CFR 422.116(f) requires, how to document it, and why so many get denied.
Building a compliant network is hard enough. Keeping it compliant year after year, as providers retire, close practices, or leave networks, is a separate operational challenge. Here are retention strategies network ops teams can use.
Dual Eligible Special Needs Plans must have a contract with the state Medicaid agency under 42 CFR 422.107 in every state where they operate. That contract runs on the state's timeline, and it can shape your network build.
Health plans that operate MA networks across multiple states face a coordination challenge that single-state plans don't: managing different filing windows, different state regulatory overlays, and different provider landscapes simultaneously. Here's how multi-state teams can stay on top of it.
CMS reviews Medicare Advantage contract networks on a triennial basis, and certain events can trigger a review sooner. Here's what triggers one, what gets checked, and how network ops teams can prepare before the call comes.
Fee schedule strategy isn't just a finance question, it's a network adequacy question. A fee schedule that lets recruiters make decisions quickly, without escalation, keeps negotiations moving. Here's how to structure your approach.
The time-and-distance standard that applies to any given county depends on how CMS designates that county: Large Metro, Metro, Micro, Rural, or CEAC (counties with extreme access considerations). Using the right designation for every county is fundamental to accurate adequacy modeling.
Launching a new Medicare Advantage or Medicaid managed care plan requires building a compliant provider network from scratch, on a deadline. This guide covers the unique challenges of a first-year build and how to avoid mistakes that can cost a new plan its adequacy review.
A network adequacy filing captures one point in time, but networks change throughout the year. Provider terminations, credentialing lapses, and practice relocations can erode adequacy between filings. Here's how to monitor continuously and respond before you have a material gap.
Before you submit to HPMS, your adequacy calculations need to survive CMS scrutiny. Here's how experienced network teams validate their adequacy scores before the filing window closes.
Bad provider data can sink an adequacy calculation. Here's how network teams build data quality systems that hold up.
Geographic analysis is the foundation of a defensible adequacy filing. Here's how network teams use GIS-style analysis to find gaps, prioritize recruitment, and document their coverage story.
CMS time-distance standards are scored against where beneficiaries live, county by county, and both the time and the distance limit must be met. Here's how the calculation actually works, and where internal models drift from CMS's results.
Not all specialties recruit at the same pace or price. A tiered contracting strategy lets you sequence outreach, allocate budget, and close the hardest providers before your filing window slams shut.
An enrollment freeze is one of the most severe sanctions CMS can impose on a Medicare Advantage plan. MedPAC says CMS has not used this authority for network adequacy, but the risks behind it are real. Here's how the framework works and how to stay well clear of it.
Section 1115 demonstrations create unique network obligations that differ substantially from standard Medicaid managed care requirements. Here's what network teams need to know when building or maintaining waiver program networks.
The technology you use for network build management will either compress your timeline or extend it. Here's a structured evaluation framework for health plan network teams selecting adequacy management software.
Delegated credentialing agreements can shorten your credentialing timeline during a network build, but only if structured correctly. Here's how to use delegation without creating compliance exposure.
Dual Eligible Special Needs Plans must satisfy both CMS network adequacy standards and state Medicaid agency requirements, and those two sets of standards don't always align. Here's how network teams navigate the overlap.
Contracted doesn't mean available. Panel management, tracking which providers are accepting new patients and keeping that data current, is one of the most underrated drivers of real-world network adequacy.
CMS time-distance standards are scored against where beneficiaries live, not against a county's center. Networks built without understanding member geographic distribution fail adequacy tests that county-center analysis said they would pass.
The MA bid and the network test run on separate CMS dates, and they share one list of counties. Here's what network teams need to understand about how those dates affect contracting strategy.
If your network build metrics are limited to 'contracts signed,' you're flying blind. Here's a KPI framework that tells you whether you'll pass adequacy review before your deadline, not after.
Counties with HRSA Health Professional Shortage Area (HPSA) designations are hard to build in, but the designation doesn't change CMS's standards. Here's what HPSA status does and doesn't do for your network build and your exception requests.
Hospital system contracting is the highest-stakes provider relationship in a network build. A single health system can provide, or block, dozens of specialty categories across multiple counties.
Networks change throughout the year: providers leave, practices close, groups restructure. CMS's rules and guidance set specific notices for significant network changes. Here's what triggers a notice to CMS, what members must be told, and when.
Independent Practice Association (IPA) contracts can simultaneously solve dozens of specialty gaps with a single agreement, or create single-point-of-failure network risk. Here's how to evaluate and structure IPA relationships in a network build.
CMS's time and distance rules and the Mental Health Parity and Addiction Equity Act (MHPAEA) ask different questions about a behavioral health network. Here's how the two frameworks differ and what each one looks at.
Network adequacy and Star Ratings are often run as separate workstreams. But adequacy decisions, which providers are in network and how accessible they are, shape the member experience and clinical measures your Star Rating draws on.
CMS applies five distinct sets of time-distance standards based on county designation. Understanding which standards apply where, and how county boundaries interact with member population, is the foundation of every accurate adequacy calculation.
CMS changes Medicare Advantage network adequacy requirements through rulemaking and the annual HSD Reference File, not through bulletins or Call Letters. Here's a plain-language guide to where the rules live, what is settled, and what network teams should verify before relying on any summary.
Contracting timelines slip in predictable places. Here's a stage-by-stage look at what drives each one, the published clocks that do exist, and how to build a schedule backward from CMS's dates.
Medicaid managed care network adequacy is governed at the state level within a federal floor set by 42 CFR 438.68. What that means in practice: every state has different standards, different filing processes, and different audit triggers. Here's how to navigate state variation.
Network builds are expensive projects that are easy to underbudget. Here's a cost framework covering staffing, technology, contracting incentives, and credentialing, and the questions to answer with your own numbers.
Medicare Advantage directories now have dated federal requirements: 30-day updates, an annual attestation, and a statute coming in 2028. Here's what the rules say and what compliance looks like in practice.
Many MA plans carve out specific benefits, dental, vision, behavioral health, pharmacy, to specialized vendors. But carve-outs don't eliminate adequacy obligations. Here's how CMS views carved-out benefits in the context of network adequacy.
Member grievances about provider access aren't just a customer service problem: they're a compliance signal, and a network access complaint can pull a CMS network review forward. Here's how to turn grievance data into network intelligence.
The credentialing committee is the final gate between a signed contract and a provider appearing in your network. Here's how to structure a health plan credentialing committee, how often it should meet, and what documentation it needs to function properly.
Launching a new Medicare Advantage plan is the most network-intensive build scenario a health plan team can face. You're building from zero, with no existing relationships, against established competitors who've been contracting in your target counties for years.
Passing a CMS network review starts a compliance obligation; it doesn't end one. Here's how to build a monitoring cadence, what to track, and what to do when a network change opens a gap.
Working backward from CMS's dates takes a detailed 12-month calendar. Here's one way to sequence provider recruitment, gap analysis, credentialing, and HSD uploads so the network is ready when CMS looks.
Primary care is the foundation of Medicare Advantage network adequacy, and the most complex to build correctly. Here's how CMS evaluates PCP adequacy, how panel capacity affects real access, and how to sequence recruitment to avoid last-minute gaps.
The MA application asks a plan to attest that its network meets 42 CFR 422.116 in every county. Here's what stands behind that statement, what to settle about who signs, which data errors to check first, and how to test your tables before you attest.
Building a network across 50+ counties simultaneously requires a disciplined sequencing strategy. Here's how to prioritize counties, coordinate outreach, and keep a complex multi-market build visible county by county.
A signed contract and a provider a member can actually see are different things. Here's how panel status, accepting-new-patients verification, and capacity fit alongside CMS's adequacy tests, and how network teams can keep a roster honest.
A CMS network adequacy deficiency notice is not the end of your filing, but the rounds that follow it are short. Here's what the notice means, how the HSD upload rounds work, what an exception needs, and how to organize your response.
Your PBP and your network adequacy filing must tell a consistent story to CMS. Service area elections, county-level coverage decisions, and bid timing all create interdependencies that network teams and bid teams must coordinate carefully to avoid compliance exposure.
CMS requires Medicare Advantage plans to demonstrate adequacy across more than a dozen specialist categories, each with its own time-and-distance standard by county type. Here's the comprehensive guide to specialty adequacy strategy, subspecialty counting, and exception management.
A Medicare Advantage network build is a significant investment. Here are the cost categories to budget, how to size each one from your own numbers, and how to frame the case for plan leadership.
Most health plan compliance teams spend months preparing their network adequacy filing, and relatively little time understanding what CMS does with it. This breakdown walks through what CMS has published about the review, from the automated check to the deficiency notice.
When a network changes mid-year, some notices to CMS and to members are not optional. This guide covers the events to watch, the notice rules we can source, how to test the result in HPMS, and how to protect current member care while you fix a gap.
Your HSD tables can pass while members can't get an appointment. Secret shopper testing is how that gets found: directory accuracy, wait times, whether anyone answers. Here's where it is required, what it tests, and how plans can prepare.
Small and startup MA plans face network adequacy requirements identical to those applied to national carriers: with a fraction of the leverage, staff, and brand recognition. This guide covers the strategies that give new entrants a realistic path to compliant, functional networks.
A network that isn't ready on CMS's calendar can cost you the county. Here's how to map CMS's dates to concrete internal milestones so your build and your bid land together.
Weak corrective action plans share the same flaws: vague root causes, milestones without owners, and timelines that don't hold up. This guide lays out a structure we recommend and how to build a CAP that closes deficiencies rather than prolonging them.
Telehealth does not count as a physical location in CMS network adequacy. What it earns is a 10 percentage point credit in 15 listed specialties. Here's exactly which specialties qualify, what the credit does and doesn't do, and how it interacts with exceptions.
Every provider on your active roster has a recredentialing date. When it passes without a decision, the provider may have to come off the roster, which can open an adequacy gap. Here's how to build a system that keeps every credential current.
If CMS asks how your network looked at a past date, your current roster won't answer the question. You need records made at the time. Here's how to build a dependable audit trail from day one.
New guides, CMS updates, and network build playbooks: delivered to your inbox twice a month. No fluff.
No spam. Unsubscribe any time.