Skip to content
FonteumPublic-records evidence
Screen 25 NPIs free →Buy $129 certificate →

NPI reference

One public-record page per National Provider Identifier

A /npi/<npi> page starts with the NPPES row for that identifier and adds held-source records only where those records publish the same NPI. Source and observation metadata appear where available. Stable URLs are built for citation by people, search engines, and AI agents. Each record is also available as JSON at /api/v1/npi/<npi>.

Don't have an NPI to hand? Look one up by name or specialty, or browse the provider directory. To change a submitted field, read how to update an NPI record in NPPES. For identifier scope, read what NPPES means in healthcare and why a PTAN is not the same as an NPI.

Sample NPI records

A stable sample of NPI citation pages drawn from the current tracked CMS NPPES specialty caches. State and specialty hubs expose the broader paginated provider-record directories.

What each record draws on

  • CMS NPPESRegistry identity, specialty taxonomy, practice location.
  • CMS PECOSMedicare enrollment record.
  • CMS Open PaymentsIndustry payments and transfers of value (Sunshine Act).
  • CMS Medicare Part DPrescribing volume and drug cost across the program.
  • CMS QPP / MIPSMerit-based Incentive Payment System quality score.
  • OIG LEIE + state MedicaidFederal exclusion status, plus the state Medicaid exclusion lists currently loaded for GA, IA, MD, MS, MT, NC, ND, NH, NY, OH, PA, TN, and WA. Other states are not covered.

All sources are U.S. government public-domain works (17 U.S.C. § 105). Exclusion data is a screening aid, not a legal or credentialing certification. Reviewed by Dr. Jennifer Montecillo, MD · corrections to hello@fonteum.com. See the methodology.

What’s on file, by the numbers

Platform snapshot · 2026-07-29

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