FIELD GUIDE / STRONG
Taxonomy audit for provider-directory teams
Providers may report multiple taxonomies, one is primary, and local specialty vocabularies rarely map one-to-one. This guide applies the work to directory refresh files and recurring refreshes.
CHECK YOUR ROSTER
Upload your directory refresh file to compare taxonomy codes and specialty descriptions.
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 taxonomy audit, Providers may report multiple taxonomies, one is primary, and local specialty vocabularies rarely map one-to-one.
How to interpret the evidence
In taxonomy audit for provider-directory teams, recurring refreshes changes how a result should be interpreted. A public location does not prove that a provider currently accepts patients there.
Check the primary flag, secondary codes, local mapping, and update date before escalating. Preserve recurring refreshes as a separate consideration for provider-directory teams.
| Roster input to retain | Public NPPES evidence to append |
|---|---|
| directory_npi | practice address |
| location_id | primary taxonomy |
| taxonomy code | descriptions |
| NPI | — |
FICTIONAL OPERATIONAL EXAMPLE
taxonomy audit in a fictional directory refresh file
During a fictional taxonomy audit review, a directory refresh file contains 4,200 clinician and facility listings. One row for Morgan Rivera, DDS / North Mesa Dental reaches review because mailing address published as a practice location.
For this taxonomy audit review, the source retains directory_npi, location_id, directory_npi for traceability.
Check the primary flag, secondary codes, local mapping, and update date before escalating. The reviewer also checks recurring refreshes.
A defensible workflow
- 01
Retain the local specialty and code.
- 02
Retrieve all reported NPPES taxonomies.
- 03
Identify primary without discarding secondary codes. Retain display_name as operational context.
- 04
Compare codes before descriptions.
- 05
Route differences for contextual review.
Common errors in this workflow
- 01description compared instead of code
- 02local specialty assumed equivalent
- 03mailing address published as a practice location
- 04facility brand matched to an individual NPI
REVIEW GUIDANCE
Use the result as evidence, not a verdict.
Check the primary flag, secondary codes, local mapping, and update date before escalating. Preserve recurring refreshes as a separate consideration for provider-directory teams.
Taxonomy does not establish licensure, board certification, competence, or scope. 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. Check the primary flag, secondary codes, local mapping, and update date before escalating.
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.