FIELD GUIDE / MODERATE
NPI Type 1 vs Type 2: individuals and organizations
Type 1 and Type 2 records use different name fields and business meaning.
DIRECT ANSWER
Type 1 and Type 2 records use different name fields and business meaning.
How to interpret the evidence
For roster and enrollment teams, separating identifier structure, public evidence, and operational decisions prevents false confidence.
Treat approximate differences as review signals and keep malformed, not-found, and failed outcomes separate.
| Roster input to retain | Public NPPES evidence to append |
|---|---|
| raw NPI | entity type |
| source row ID | provider or organization name |
| provider or organization name | practice address |
| — | last updated date |
FICTIONAL OPERATIONAL EXAMPLE
A dentist and the group practice
A fictional roster has Morgan Rivera and North Mesa Dental LLC.
Each has a different NPI.
Compare each row with its matching entity type.
A defensible workflow
- 01
Preserve the original row and context.
- 02
Normalize and checksum locally.
- 03
Query NPPES with explicit failure states.
- 04
Compare relevant normalized fields.
- 05
Export evidence, flags, and timestamp.
Common errors in this workflow
- 01group NPI attached to clinician
- 02legal name compared with surname
- 03type used as employment proof
REVIEW GUIDANCE
Use the result as evidence, not a verdict.
Treat approximate differences as review signals and keep malformed, not-found, and failed outcomes separate.
NPPES is a public provider-identifier dataset. An NPI match does not establish licensure, credentials, exclusions, sanctions, enrollment, participation, eligibility, or good standing.
QUESTIONS
What reviewers usually need to know
What is the first step in entity-type comparison?
Preserve the raw value and run local format and checksum validation before remote lookup.
Does a successful match verify credentials?
No. It confirms public NPPES information at lookup time; other questions require other sources.
What if CMS is unavailable?
Keep the row, label the lookup failed, and retry. Do not call it not found.
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.