Skip to content
FonteumPublic-records evidence
Fonteum Data GlossaryData Standards

Taxonomy Code: Definition and Healthcare Context

Full name: Healthcare Provider Taxonomy Code

A healthcare provider taxonomy code is a 10-character alphanumeric code that classifies a provider's type, classification, and specialization. Maintained by the National Uniform Claim Committee (NUCC), taxonomy codes are used in HIPAA transactions and stored in NPPES alongside each NPI record. A provider may have multiple taxonomy codes, with one designated as primary. The code structure groups providers hierarchically: individuals, non-individual practitioners, and suppliers, each subdivided by specialty.

Source file
Not reported
Published
Not reported
Retrieved
Not reported
Snapshot
Not retained for this reference page
Data as of
Not reported
Last updated: 2026-07-11Reviewed by: Dr. Jennifer Montecillo, MDGullas College of Medicine, 2019. Non-practicing medical reviewer.

How it’s used

  • CMS NPPES NPI Registry: an NPI record can carry one or more taxonomy codes, with one marked primary when the record supplies that designation; taxonomy fields can be missing or stale.
  • CMS PECOS Medicare Provider Enrollment: taxonomy codes in PECOS records determine Medicare enrollment category and payment rules.
  • CMS QPP MIPS: specialty groupings for MIPS reporting use NUCC taxonomy codes to assign eligible clinicians to the correct quality measure set.

Frequently asked questions

What is a taxonomy code?
A taxonomy code is a 10-character alphanumeric code maintained by NUCC that classifies a health care provider by type, classification, and specialization, such as 207Q00000X for Family Medicine.
Where do taxonomy codes come from?
Taxonomy codes are developed and maintained by the National Uniform Claim Committee (NUCC) and updated annually.
Can a provider have more than one taxonomy code?
Yes. A provider may have multiple taxonomy codes in NPPES, with one designated as the primary code for billing purposes.

What’s on file, by the numbers

Platform snapshot · 2026-08-30

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
16fresh 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