Skip to content
FonteumPublic-records evidence
NUCCReference dataObserved 2026-06-14

NUCC Health Care Provider Taxonomy

The Health Care Provider Taxonomy code set — grouping, classification, specialization, and display name per code. The same reference set NPPES uses to tag provider taxonomy. Reference code set; no NPI or entity linkage. Source: National Uniform Claim Committee · 2026-06-14

883
taxonomy codes
Catalog observation: 2026-06-14
Fonteum catalog observation · 2026-06-14
2001–2026
Temporal coverage
Nominal publisher cadence: semiannual
NUCC · 2026-06-14
CodeSystem
Illustrative mapping target
Example mapping · nucc-taxonomy/v1
Fonteum methodology

Illustrative FHIR CodeSystem mapping

How one record can be normalized.

Illustrative mapping
{
  "resourceType": "CodeSystem",
  "id": "nucc-taxonomy",
  "_source": "nucc-taxonomy",
  "_methodology": "nucc-taxonomy/v1",
  "concept": [{ "code": "207RA0201X", "display": "Allergy & Immunology Physician" }]
}

This example documents a normalized shape; it does not establish that a FHIR endpoint or bulk export is available for this catalog entry. When a record includes _source, _methodology, snapshot-date, or confidence fields, those fields are nullable and delivery surfaces can return different subsets. Published bulk files are listed separately in the bulk manifest.

Fields in this record

What each field in the illustrative CodeSystem mapping means.

The fields below are derived from the displayed illustrative FHIR CodeSystem mapping. When a record includes source-metadata fields (_source, _methodology, and a snapshot date), they describe that delivered record. Those fields are nullable and may be absent from a response; identity fields key the record and data fields carry the measured values.

Field-level documentation for NUCC Health Care Provider Taxonomy
FieldTypeRole
resourceTypestringIdentity
idstringIdentity
_sourcestringProvenance
_methodologystringProvenance
conceptarrayData

Dataset facts

Dataset facts for NUCC Health Care Provider Taxonomy
FieldValue
AgencyNational Uniform Claim CommitteeNUCC · 2026-06-14
CategoryReference data
Records883 taxonomy codes(catalog observation 2026-06-14)
Temporal coverage2001–2026
Publisher cadence (nominal)Semiannual
Load timingNo load-time guarantee; date shown is the catalog observation for this row count.
Catalog observation date2026-06-14
Illustrative FHIR mappingCodeSystem
Methodologynucc-taxonomy/v1
MeasuredGrouping, classification, specialization, display name, and section per taxonomy code
Upstream sourcewww.nucc.org

Get access

How to reach this dataset.

Dataset-specific delivery formats are confirmed during pilot review. This catalog entry does not promise a bulk file or FHIR endpoint. Pilot requests are reviewed within one business day; there is no charge during the pilot period.

What’s on file, by the numbers

Platform snapshot · 2026-08-11

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