FIELD GUIDE / MODERATE
Duplicate NPI detection for multi-location clinics
The same NPI may repeat legitimately or may be tied to conflicting names, entities, or locations. This guide applies the work to clinic location rosters and site identifiers.
CHECK YOUR ROSTER
Upload your clinic location roster to deduplicate lookups while preserving every source row.
The same validator used on the homepage: local checksum checks, live public NPPES lookup, cautious differences, and clean export.
What the check needs to separate
The same clinician may appear at several sites, so identity and scheduling location cannot be collapsed. For duplicate npi detection, The same NPI may repeat legitimately or may be tied to conflicting names, entities, or locations.
In duplicate npi detection for multi-location clinics, site identifiers changes how a result should be interpreted. NPPES does not establish employment, availability, or privileges at a clinic.
| Roster input to retain | Public NPPES evidence to append |
|---|---|
| provider_name | practice address |
| clinician_npi | entity type |
| location ID | normalized NPI |
| row ID | public name |
FICTIONAL OPERATIONAL EXAMPLE
duplicate NPI detection in a fictional clinic location roster
During a fictional duplicate npi detection review, a clinic location roster contains 38 sites and 610 clinicians. One row for Avery Patel, NP / Fictional Lakeview Clinic reaches review because local address overwritten by one NPPES location.
For this duplicate npi detection review, the source retains provider_name, clinician_npi, provider_name for traceability.
Distinguish duplicate lookup keys from duplicate business records. The reviewer also checks site identifiers.
Common errors in this workflow
- 01format variants counted separately
- 02source rows deleted
- 03local address overwritten by one NPPES location
- 04leading zero removed
A defensible workflow
- 01
Group normalized identifiers without deleting rows.
- 02
Count source contexts.
- 03
Fetch each valid NPI once. Retain clinic_location_id as operational context.
- 04
Compare conflicting names and types.
- 05
Rejoin evidence to every row.
REVIEW GUIDANCE
Use the result as evidence, not a verdict.
Distinguish duplicate lookup keys from duplicate business records. Preserve site identifiers as a separate consideration for multi-location clinics.
Deduplication does not decide whether operational records should be merged. NPPES does not establish employment, availability, or privileges at a clinic.
QUESTIONS
What reviewers usually need to know
What should multi-location clinics do first?
Preserve the source row, normalize locally, and keep clinician_npi before comparing public fields.
Should a difference be corrected automatically?
Usually not. Distinguish duplicate lookup keys from duplicate business records.
What does an NPPES match establish?
It confirms public fields returned at lookup time. NPPES does not establish employment, availability, or privileges at a clinic.
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.