The Pitch That Keeps Coming Back
Every so often a health plan's IT leadership, sometimes with a consulting partner attached, presents a business case for building a proprietary network adequacy platform. The pitch is compelling: complete control over the data model, integration with existing systems, no vendor dependency, and a Year 1 estimate that looks favorable.
We make software in this space, so weigh our view accordingly. We think that pitch is usually incomplete, because the cost that matters most comes after Year 1. Here is what to check before you approve it. We don't quote prices, because we haven't found a public benchmark for them. Get real quotes, and have IT estimate the lines below.
What Year 1 Has to Cover
- Data sourcing: Network adequacy needs current provider data: NPI records, specialty classifications, practice locations. Those feeds have to be built and joined. Watch the county keys: HSD tables use SSA county codes, most other data uses FIPS, and they are different numbering systems.
- Geography logic: The standards are set by county, by specialty, and by CMS's five county designations (Large Metro, Metro, Micro, Rural and CEAC), with customized values for some county and specialty pairs. CMS measures both travel time and distance from representative beneficiary locations it doesn't share, and no current public CMS document says whether its software routes on roads or measures a straight line. Decide what you will measure and how you will label it.
- Counting rules: Primary care scores as a group of six codes, telehealth-only providers don't count toward the minimum, credits apply in some cases and not others, and a behavioral health provider can't sit in two buckets. Getting these wrong doesn't produce an error message. It produces a false pass.
Year 2 and Beyond: The Costs That Get Left Out
The structural issue with custom builds shows up after launch. Provider data changes constantly, so the pipelines need maintenance. And the standards themselves move. The 2026 HSD Reference File lists 6,862 county and specialty criteria changes from 2025. Rules change too: Clinical Psychology and Clinical Social Work became provider types for 2024, and Outpatient Behavioral Health was added for 2025.
Your budget needs recurring lines for:
- Engineering and data maintenance.
- Loading each year's Reference File and implementing rule changes before they apply.
- Integration upkeep as adjacent systems change.
A CFO who approves a build on Year 1 economics is funding a multi-year obligation. Make sure the business case says so.
What to Ask a Vendor
Buying doesn't remove the risk, so ask directly:
- Who loads each year's HSD Reference File, and when?
- How is distance measured, and is drive time measured at all?
- How does the tool label a pass it can't confirm against CMS's engine?
- Can you export your data and leave?
- Which lines of business does it actually score out of the box?
Whichever you choose, treat every internal pass as unconfirmed until CMS's Network Management Module agrees. We cover why in why your network passes internally and fails CMS.
When Building Makes Sense
There is a legitimate case for custom development: unusual multi-state, multi-line-of-business complexity where no vendor has the right data model. A plan managing MA, Medicaid, and commercial adequacy across many states with their own standards may genuinely have requirements no current vendor addresses.
If that isn't your plan, we think the better move is usually to buy, negotiate hard on terms and data access, and spend your engineering capacity elsewhere. Compete on what you do with your network, not on how you built the software to measure it.
The Blueprint team
Provider network build practice
Written by the people behind Blueprint, who between them have spent 30 years building provider networks for health plans: recruiting and contracting providers, chasing credentialing, and filing adequacy. Blueprint is new. The experience behind it isn't.