FIELD GUIDE / STRONG
Practice address review for provider-directory teams
Mailing and practice addresses differ, providers can have several locations, and suite or ZIP formatting creates false changes. This guide applies the work to directory refresh files and taxonomy drift.
CHECK YOUR ROSTER
Upload your directory refresh file and compare locations with public NPPES practice addresses.
The same validator used on the homepage: local checksum checks, live public NPPES lookup, cautious differences, and clean export.
A defensible workflow
- 01
Identify the source address type and location ID.
- 02
Select NPPES practice rather than mailing fields.
- 03
Normalize street, unit, city, state, and ZIP. Retain directory_npi as operational context.
- 04
Separate format-only and geographic differences.
- 05
Flag meaningful changes instead of overwriting.
| Roster input to retain | Public NPPES evidence to append |
|---|---|
| display_name | entity type |
| specialty | last updated date |
| city | practice address |
| ZIP | last update |
Why this matters for provider-directory teams
Directories accumulate stale locations, taxonomy drift, duplicate profiles, and Type 1/Type 2 confusion. For practice address review, Mailing and practice addresses differ, providers can have several locations, and suite or ZIP formatting creates false changes.
In practice address review for provider-directory teams, taxonomy drift changes how a result should be interpreted. A public location does not prove that a provider currently accepts patients there.
FICTIONAL OPERATIONAL EXAMPLE
Phoenix in the directory, Scottsdale in NPPES
A fictional directory lists Morgan Rivera in Phoenix while the selected public practice location says Scottsdale.
The row retains a local location ID and publication date.
Flag the geography for review; do not overwrite or infer patient availability.
Common errors in this workflow
- 01ZIP+4 treated as a different ZIP
- 02multi-location provider reduced to one address
- 03punctuation-only mismatch escalated
- 04secondary taxonomy treated as primary
REVIEW GUIDANCE
Use the result as evidence, not a verdict.
Treat location differences as evidence to investigate, not automatic corrections. Preserve taxonomy drift as a separate consideration for provider-directory teams.
A practice location does not prove availability, affiliation, service area, or licensure jurisdiction. 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. Treat location differences as evidence to investigate, not automatic corrections.
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.