Skip to content
FonteumThe Graph

The capability layer

APIREST + bulk accessMCP serverCallable by AI agentsFHIR R4 APIBulk exportAttestation & audit packReconciliationSource-vs-source diffsEntity graphSnapshotsPoint-in-time, bitemporal

By use case

Exclusion & sanctions screeningCredentialing & provider-data enrichmentAudit evidence & defensible programsProvider data for AI / RAGM&A & network diligence

By buyer

Compliance & riskDevelopers & AI teams

The differentiator

Coverage & sourcesThe catalogFreshnessMethodologyCare CompareFacility qualityBrowse all datasets →
Research

The dev on-ramp

DocsAPI referenceMCPQuickstartStatusChangelogSDKs & integrations
Pricing
Sign inTry the FHIR sandbox →Request access →

Platform

APIMCP serverFHIR R4 APIBulk exportAttestation & audit packReconciliationEntity graphSnapshots

Solutions

Exclusion & sanctions screeningCredentialing & provider-data enrichmentAudit evidence & defensible programsProvider data for AI / RAGM&A & network diligenceCompliance & riskDevelopers & AI teams

Data

Coverage & sourcesFreshnessMethodologyCare CompareBrowse all datasets →
Research

Developers

DocsAPI referenceMCPQuickstartStatusChangelogSDKs & integrations
Pricing
Sign inTry the FHIR sandbox →Request access →
  1. Fonteum
  2. /
  3. Glossary
  4. /
  5. Taxonomy Code
Healthcare 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.

Last updated: 2026-06-17Reviewed by: Dr. Jennifer Montecillo, MD — Gullas College of Medicine, 2019. Non-practicing medical reviewer.

How it’s used

  • CMS NPPES NPI Registry: every provider record in NPPES includes one or more taxonomy codes, with the primary code used to classify the provider's main specialty.
  • 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.

Related terms

  • NPI Number
  • NPPES
  • NUCC
  • Type 1 NPI
  • PECOS
  • Provider Enrollment

Authoritative sources

  • NUCC Health Care Provider Taxonomy code set↗
  • CMS: Provider taxonomy codes in NPPES↗
← All glossary terms

The substrate, by the numbers

44federal source familiesDistinct CMS, OIG, HRSA, FDA and peer datasets
35dataset pagesCitable, downloadable /data catalog pages
65reproducible studiesEach shipping the SQL behind its figures

Built on the authoritative federal record

The primary sources, named on every page.

These are the federal agencies whose public datasets Fonteum ingests and attributes — the issuing authorities, not customers or partners. Every figure on the site links back to one of them.

  • CMS
  • HHS-OIG
  • HRSA
  • FDA
  • NLM
  • NUCC
  • Census
  • BLS
  • BEA

See the full source registry, with license and refresh cadence for each →

Reproducible by design

Every figure traces to its federal source.

14-tuple provenance

Every rendered fact ties to a source URL, dataset ID, snapshot date, row key, and SHA-256 — the full chain-of-custody record.

Reproducible SQL

Each study ships the exact query behind its figures, run against the cited federal snapshot. Re-run it yourself.

Daily reconciliation

Published counts are reconciled against the upstream federal datasets on a daily cadence, with drift logged.

Named medical review

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

Read the full provenance and attestation methodology →

Two doors

Use the free API and open data

Query providers, facilities, sanctions, and quality scores — each field carrying its federal source. Self-serve, no call to start.

Explore the API →Browse the data catalog →

Talk to us

Managed pilots, enterprise terms, and audit-ready, signed attestation packages for compliance, risk, and research teams.

Talk to us →
Fonteum
Platform
Platform overviewAPIMCP serverFHIR R4 APIBulk exportAttestation & audit packReconciliationEntity graphSnapshots
Solutions
All solutionsExclusion & sanctions screeningCredentialing & enrichmentAudit evidenceProvider data for AI / RAGM&A & network diligenceCompliance & riskDevelopers & AI teams
Data & sources
Coverage & sourcesBrowse all datasetsFreshnessMethodologyCare CompareSanctionsOwnershipStaffingDeficienciesSpecial Focus Facilities
Developers
Developer hubDocsAPI referenceQuickstartStatusChangelogSDKs & integrationsWebhooks
Research
Research hubGlossaryComparisonsCitationsWhy Fonteum
Company
AboutPressCustomersPricingContactEditorial policyCorrections
Trust & legal
TrustQualitySecurityPrivacy policyTerms of serviceMedical disclaimer

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

© 2026 Fonteum LLC. All rights reserved.

·hello@fonteum.com

The U.S. healthcare graph AI can cite — every fact carries its source.

Request access→