FIELD GUIDE / MODERATE
NPI not-found review for provider-directory teams
One “invalid” bucket hides whether input is malformed, absent from results, or simply could not be checked. This guide applies the work to directory refresh files and publishable locations.
CHECK YOUR ROSTER
Upload your directory refresh file to separate malformed, not-found, and unavailable results.
The same validator used on the homepage: local checksum checks, live public NPPES lookup, cautious differences, and clean export.
DIRECT ANSWER
Directories accumulate stale locations, taxonomy drift, duplicate profiles, and Type 1/Type 2 confusion. For npi not-found review, One “invalid” bucket hides whether input is malformed, absent from results, or simply could not be checked.
How to interpret the evidence
In npi not-found review for provider-directory teams, publishable locations changes how a result should be interpreted. A public location does not prove that a provider currently accepts patients there.
Retry failures, correct malformed values, and investigate consistent zero-result responses separately. Preserve publishable locations as a separate consideration for provider-directory teams.
| Roster input to retain | Public NPPES evidence to append |
|---|---|
| specialty | last updated date |
| display_name | entity type |
| provider name | result count |
| row ID | normalized NPI |
FICTIONAL OPERATIONAL EXAMPLE
NPI not-found review in a fictional directory refresh file
During a fictional npi not-found review review, a directory refresh file contains 4,200 clinician and facility listings. One row for Morgan Rivera, DDS / North Mesa Dental reaches review because facility brand matched to an individual NPI.
For this npi not-found review review, the source retains specialty, display_name, specialty for traceability.
Retry failures, correct malformed values, and investigate consistent zero-result responses separately. The reviewer also checks publishable locations.
A defensible workflow
- 01
Check missingness and format.
- 02
Run checksum before lookup.
- 03
Record timeouts separately. Retain location_id as operational context.
- 04
Use not-found only for successful zero results.
- 05
Retain failures for retry.
Common errors in this workflow
- 01temporary failure made permanent
- 02timeout labeled zero results
- 03facility brand matched to an individual NPI
- 04mailing address published as a practice location
REVIEW GUIDANCE
Use the result as evidence, not a verdict.
Retry failures, correct malformed values, and investigate consistent zero-result responses separately. Preserve publishable locations as a separate consideration for provider-directory teams.
A zero-result response describes the public lookup at that time, not all administrative history. A public location does not prove that a provider currently accepts patients there.
QUESTIONS
What reviewers usually need to know
What should provider-directory teams do first?
Preserve the source row, normalize locally, and keep directory_npi before comparing public fields.
Should a difference be corrected automatically?
Usually not. Retry failures, correct malformed values, and investigate consistent zero-result responses separately.
What does an NPPES match establish?
It confirms public fields returned at lookup time. A public location does not prove that a provider currently accepts patients there.
Primary references: CMS National Provider Identifiers and the NPI Registry API documentation. Public provider-reported data should be read with its source date and limitations.