Free Network Build Assessment
Score your buildBad provider data can sink an adequacy calculation. Here's how network teams build data quality systems that hold up.
Some network adequacy failures aren't genuine access gaps. They come from inaccurate provider data that makes the network look smaller or less accessible than it actually is. Providers listed at wrong addresses produce wrong time-distance results. Specialty errors leave providers out of the categories they should be filling. These are data problems, not network problems, and they are preventable.
The inverse problem is equally serious: errors that inflate your counts by including providers who are not genuinely available, such as lapsed contracts or closed practices. CMS's Provider Supply file and its claims data give reviewers their own picture of who is practicing where.
This guide describes five categories of provider data errors, the governance that prevents them, and the workflows that keep provider data accurate through the year.
Every network ops team should actively manage these five categories of error.
Wrong specialty codes are the most technically complex. CMS scores 29 provider types and 14 facility types using its own HSD specialty codes, and the notes in the HSD Reference File add limits. A nurse practitioner, for example, counts toward primary care only in a narrow case set out in those notes. Errors compound over time as providers add credentials, change practice focus, or update their NPPES records without telling your plan.
Stale addresses are the most operationally impactful error for adequacy calculations. Because time-distance standards are calculated from where beneficiaries live to provider practice locations, a provider address that is even a few miles off can change whether a county clears adequacy threshold. Multi-site practices and hospital system affiliates are particularly prone to address drift: satellite offices open and close, practices relocate within the same metropolitan area, and these changes rarely generate a proactive notification to every contracted health plan.
Duplicate NPI entries occur when the same provider is registered under multiple practice locations in your provider database and each entry appears as a separate provider in your adequacy count. Duplicate NPIs are common in large network databases that were assembled through acquisitions of prior plan networks or through data migrations between credentialing systems. They inflate apparent network size and create reconciliation problems.
Incorrect accepting-new-patients status is hard to discover without direct provider contact. Panel status changes often, as providers open and close panels based on their patient volume, staffing levels, and practice economics, and plan systems rarely keep up. If your data on this is old, you are probably relying on some providers who can no longer take your members.
Missing panel information is a related but distinct problem. Panel information includes not just open/closed status but also the specific insurance products a provider is enrolled to serve, the age ranges and patient populations the practice is equipped to handle, and the appointment availability that determines whether a provider is functionally accessible. Incomplete panel data reduces the precision of your adequacy calculation and creates member access problems when the directory doesn't accurately reflect what the provider can offer.
Preventing provider data errors requires a defined validation workflow that runs continuously, not just at submission time. The workflow has three layers: point-of-entry validation, periodic reconciliation, and event-triggered updates.
Point-of-entry validation runs at the moment a new provider is added to your system. At minimum, it should confirm that the submitted NPI is active in NPPES, that the taxonomy code matches the specialty category being claimed, and that the practice address geocodes to a location within your service area. Catching errors here stops them at the source, before they reach the adequacy calculation.
Periodic reconciliation runs on a defined cadence: quarterly for most data fields, monthly for high-priority fields like panel status and credentialing currency. Reconciliation involves pulling a current extract from NPPES and comparing it against your provider database field by field. Discrepancies in address, taxonomy, or enumeration status trigger a review workflow that either updates the record or flags it for manual investigation. Quarterly NPPES reconciliation, run consistently, prevents the accumulation of address drift and taxonomy errors that compound into material adequacy problems at submission time.
Event-triggered updates occur when a defined event, a provider contract renewal, a re-credentialing completion, a returned provider attestation, or a change notification from a provider group, triggers a specific record review. Event triggers are more responsive than periodic reconciliation because they update the record at the moment something changes, rather than waiting for the next scheduled batch run. Implementing event triggers requires that your contract management system, credentialing system, and provider database have defined integration points or manual hand-off protocols.
The National Plan and Provider Enumeration System is the registry for NPI status, taxonomy codes, and practice location data. A record there is only as current as the provider keeps it, so treat it as a check, not as the truth.
CMS makes NPPES data available for download and through its NPI Registry. Network ops teams should establish a regular NPPES reconciliation process that compares their provider database against the current NPPES file for the following fields: NPI enumeration status (active vs. deactivated), primary taxonomy code, secondary taxonomy codes, practice location addresses (line 1, city, state, zip), and provider last name or organization name for identity verification.
When NPPES reconciliation identifies a discrepancy, the response protocol should distinguish between three categories: discrepancies where NPPES appears correct and your record is stale (update your record and document the change); discrepancies where your record appears correct and NPPES is outdated (contact the provider or group to update their NPPES enumeration, and document that outreach); and discrepancies that cannot be resolved without provider contact (flag the record for attestation follow-up and exclude the provider from the adequacy calculation until resolved).
A practical note on NPPES reconciliation scope: large network databases with thousands of providers make full-field reconciliation resource-intensive. If you need to triage the reconciliation effort, prioritize providers in counties that are near the adequacy threshold, providers in hard-to-fill specialties, and providers whose records have not been updated in a long time.
Provider attestation is the process by which health plans ask providers to confirm that the information on file, such as address, accepting-new-patients status, specialty, and practice hours, is current and accurate.
The rules set the pace. Under 42 CFR 422.111(m), MA plans make 30-day directory updates and an annual attestation for plan years beginning on or after January 1, 2026, and a 2026 law adds 90-day verification starting in plan year 2028. So you need a way to receive and process changes between attestation cycles.
Logistics matter too. Provider groups with large rosters may attest in bulk if you send a pre-populated data file that needs only corrections and a signature rather than a blank form. Asking through provider relations staff who know the practice can also work better than an email to a generic practice address. Blueprint's provider portal can collect documents and answers from a practice.
CMS's automated check scores what you upload. It can't confirm your own contract records, or tell you whether a provider is really accepting new patients. Those are the areas where your internal data quality process is the only check you have.
Screen for exclusions yourself too. Blueprint's roster check screens against OIG exclusion and Medicare opt-out lists, and both are also reasons CMS's guidance recognizes on an exception request.
A provider data governance policy formalizes the rules, responsibilities, and processes that maintain data quality in your network database. It is both an operational document and a record of how your plan manages provider data accuracy.
A complete provider data governance policy should define: data ownership (which team or role is accountable for each data field), update triggers (what events require a record update and on what timeline), validation rules (what checks run at point of entry and on what schedule), reconciliation cadence (how often each field is reconciled against external sources), attestation requirements (frequency and process for provider self-attestation), and escalation protocols (what happens when a data quality issue is discovered that may affect adequacy calculations).
The policy should also define data retention. Maintaining an archived snapshot of your provider database at each submission milestone, with a clear record of what changed between snapshots and why, makes it much easier to answer questions about a past submission.
Assign a named data governance owner, typically a senior analyst or manager in network operations, who is accountable for the policy's execution. Data governance policies that lack clear ownership tend to drift over time as staff turns over and institutional knowledge erodes. The governance owner should conduct an annual policy review to incorporate regulatory changes, lessons learned from the most recent submission cycle, and any audit findings that revealed gaps in the existing process.
Blueprint automates the network build workflows described in this article: from adequacy modeling to provider outreach tracking. See it with your state and line of business.