Skip to content
FonteumPublic-records evidence

← All sources Research / economic / workforce

NUCC Taxonomy

NUCC Health Care Provider Taxonomy

National Uniform Claim Committee (NUCC) · Tier-1 · research-only (never on individual profiles)

Research-only

The Health Care Provider Taxonomy code set is the official classification of provider type, classification, and area of specialization, maintained by the National Uniform Claim Committee. It is the same reference set NPPES uses to tag provider taxonomy on every NPI and that appears on the X12 837 claim. One row per taxonomy code; the hierarchy is grouping → classification → specialization.

What Fonteum uses it for

How this source shows up on Fonteum.

Tier-1 reference code set for resolving a taxonomy code to its grouping, classification, specialization, and display name — used to label NPPES-sourced taxonomy across research and data surfaces, and queryable per code. There is no NPI or entity linkage; this is a code set, not a provider record.

What this source does NOT mean

A taxonomy code classifies a provider type — it is not a credential, a license, a quality measurement, or a statement that any specific provider holds that classification. The code set is reference data, not a Fonteum assessment of any provider.

What this dataset answers

Research and data questions this source supports.

  • Resolve a NUCC taxonomy code (e.g. 207RA0201X) to its grouping, classification, specialization, and display name.
  • Label NPPES-sourced provider taxonomy codes with human-readable specialty names across research and data surfaces.
  • Build a specialty filter for a provider directory using the grouping → classification → specialization hierarchy.
  • Power a reference API that returns the full taxonomy record for a code.

Dataset size: 883 taxonomy codes (2026-06-14 snapshot)

Fields used

Per-field display contract.

Fields listed below show their configured `display_allowed` flag from the §94 provenance schema. Fields marked write-locked are captured for audit and are not rendered on profile pages.

Research-only — never on profiles

6 fields
codeNUCC taxonomy code (10-character)
groupingGrouping (top level)
classificationClassification (second level)
specializationSpecialization (third level)
display_nameDisplay name
sectionSection (Individual / Non-Individual)
Limitations

What we can’t infer from this source.

  • Reference code set — there is no NPI, no provider record, and no entity-graph linkage.
  • Tier-1 — reference/research context only; never rendered as a provider claim on individual profiles.
  • NUCC revises the code set twice a year; codes can be added, deprecated, or redefined between versions.
  • A taxonomy code is a classification, not a credential or license.
Source metadata

Authority, license, publisher cadence.

Authority

National Uniform Claim Committee (NUCC)

Tier

Tier-1 · research-only (never on individual profiles)

Publisher / configured cadence

Declared or configured cadence: Semiannual — NUCC publishes version YY.0 (effective July 1) and YY.1 (effective January 1) each year. Not evidence of the latest loaded source date.

License

Public NUCC Health Care Provider Taxonomy code set — published free for public use by the National Uniform Claim Committee, no reuse restriction.

Attribution requirement

Source: National Uniform Claim Committee (NUCC) — Health Care Provider Taxonomy · Version {VV.V}

ToS & usage notes

What the source allows.

The NUCC Health Care Provider Taxonomy is published free for public use on nucc.org as a version-stamped CSV; there is no reuse restriction beyond attribution to the National Uniform Claim Committee. Snapshot and attestation fields must be read from the specific artifact; no provenance fact currently links deterministically to a signature.

Sample provenance

What a single field looks like in the graph.

This worked example shows the provenance shape used when a surfaced field has populated source, last-checked, display-rule, and confidence metadata. Individual fields may omit unavailable values.

Field

Taxonomy code (reference)

Sample value

207RA0201X · Allopathic & Osteopathic Physicians · Internal Medicine · Allergy & Immunology

Provenance line

Source: NUCC Health Care Provider Taxonomy · Snapshot 2026-06-14 · Methodology nucc-taxonomy/v1 · Display rule: reference code set — resolves a taxonomy code to its labels, never an asserted provider claim

How to access

Official API, bulk download, and Fonteum endpoints.

Frequently asked

Common questions about NUCC Taxonomy.

What is the NUCC Health Care Provider Taxonomy?
It is the official code set that classifies a provider's type, classification, and area of specialization, maintained by the National Uniform Claim Committee (NUCC). It is the same reference set NPPES uses to tag provider taxonomy on every NPI and that appears on the X12 837 claim. There is one row per taxonomy code.
How is the taxonomy structured?
Each code maps to a three-level hierarchy: grouping (e.g. Allopathic & Osteopathic Physicians), classification (e.g. Internal Medicine), and specialization (e.g. Allergy & Immunology), plus a human display name and a section (Individual or Non-Individual).
Is this linked to individual providers?
No. This is a reference code set — there is no NPI, no provider record, and no entity-graph linkage. It resolves a code to its labels; it does not assert that any specific provider holds that classification.
How often is the code set updated?
NUCC publishes two versions a year — YY.0 effective July 1 and YY.1 effective January 1. Fonteum resolves the current version-stamped CSV newest-first and attests each snapshot. As of the 2026-06-14 snapshot, Fonteum holds 883 taxonomy codes.
Is a taxonomy code a credential?
No. A taxonomy code is a classification, not a credential or license. Holding a code in NPPES is self-reported by the provider and does not assert board certification or licensure — confirm credentials with the relevant state board.
Related

Related sources in the graph

See also
  • /sources → The generated source-catalog subset — documented datasets Fonteum cites.
  • /data-provenance → The provider graph — pipeline diagram, source-family clusters, field-level provenance examples, display rules.
  • /methodology → Documented sourcing, publisher cadence, observed freshness, and corrections policy.
  • /editorial-policy → Independence, sourcing, conflicts, corrections, retractions.

What’s on file, by the numbers

Platform snapshot · 2026-08-14

13.4Mproviders & companiesProviders, organizations, owners, and facilities on file
26.2Msource-linked factsSource-linked field facts in the dated platform snapshot
90sources with dataDistinct snapshot source IDs with at least one positive record count
72fresh sourcesDistinct source IDs whose latest positive-data snapshot falls within the preceding 45 days
111sources integratedActive registry rows; integration does not establish a load
13state Medicaid jurisdictionsDistinct states represented in the state-exclusions serving table

Integrated, with-data, and fresh-observation counts are separate. No platform-wide source-completeness count is published. Completeness is source-specific and must be evaluated against the named source's expected scope. State coverage is a separate jurisdiction measure.

Source authority is record-specific

Use the issuer named on the record.

Fonteum spans federal, state, and global public publishers. A source page or returned record identifies its issuer and dataset where that metadata is available. A platform registry count does not assign every page to one authority or establish loaded, fresh, or complete coverage.

Browse source records and their stated limitations →

Reproducible by design

Inspect the evidence each published figure actually supplies.

Source and date

Research pages expose the named public file and observation date where those fields are available. Source-file SHA-256 coverage is separate; facts do not currently link deterministically to signatures.

Available derivation

Studies with a retained release and committed derivation link the SQL or method used. Other studies state the evidence and reproduction limits they actually have.

Daily observations

Dated table row-count observations can detect local drift. They do not imply that an upstream publisher released or Fonteum ingested new data that day.

Named medical review

Reviewed by Jennifer Montecillo, MD, medical reviewer. Non-practicing medical reviewer.

Read the full provenance and attestation methodology →

Request access