Skip to content
FonteumPublic-records evidence

← All sources Healthcare graph

Medicare Physician & Service

Medicare Physician & Other Practitioners — by Provider and Service

Centers for Medicare & Medicaid Services (CMS) · Tier-2 · profile-enrichment (renders on matched profiles)

Research-only

The Medicare Physician & Other Practitioners by Provider and Service public-use file is procedure-level: one row per rendering NPI × HCPCS code × place of service for a data year. It reports beneficiaries, services, submitted charges, and Medicare allowed/payment amounts. Fonteum currently holds the latest published data year.

What Fonteum uses it for

How this source shows up on Fonteum.

Per-NPI procedure-level Medicare utilization and payment, available via the read API and the dataset page. The NPI -> entity-graph link is a separate, gated follow-up — this source writes no entity rows — so utilization does not yet render on individual provider profiles.

What this source does NOT mean

Service volume and payment are Medicare fee-for-service utilization facts — they are not a measure of clinical quality, appropriateness, or outcomes, and a higher volume is not 'better.' Utilization is not a Fonteum assessment of the provider.

What this dataset answers

Research and data questions this source supports.

  • Pull a provider's Medicare service mix — services, beneficiaries, and allowed/payment amounts per HCPCS code and place of service.
  • Build a utilization benchmark that compares a provider's procedure volume against specialty peers.
  • Research procedure-level Medicare spending by HCPCS code, place of service, and provider type.
  • Power a provider-data API that returns procedure-level Medicare utilization per NPI.

Dataset size: 9,781,673 provider × service rows (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

9 fields
npiRendering provider NPI
data_yearData year
hcpcs_codeHCPCS / CPT code
hcpcs_descriptionHCPCS description
place_of_servicePlace of service (facility / office)
total_beneficiariesDistinct beneficiaries
total_servicesTotal services
avg_medicare_allowed_amtAverage Medicare allowed amount
avg_medicare_payment_amtAverage Medicare payment amount
Limitations

What we can’t infer from this source.

  • Service volume and payment are utilization facts, not a quality, appropriateness, or outcome measure.
  • Annual cadence — the published data year lags the calendar year, and Fonteum holds the latest year only.
  • NPI-keyed, but the entity-graph cross-link is deferred — utilization does not render on individual provider profiles yet.
  • CMS suppresses low-volume cells; suppressed counts are stored as null, not zero.
Source metadata

Authority, license, publisher cadence.

Authority

Centers for Medicare & Medicaid Services (CMS)

Tier

Tier-2 · profile-enrichment (renders on matched profiles)

Publisher / configured cadence

Declared or configured cadence: Annual — CMS publishes one public-use file per data year. Not evidence of the latest loaded source date.

License

U.S. government public-domain works (17 U.S.C. § 105). Free to use with attribution. License ↗

Attribution requirement

Source: Centers for Medicare & Medicaid Services (CMS) — Medicare Physician & Other Practitioners by Provider and Service · Data Year {YYYY}

ToS & usage notes

What the source allows.

U.S. government public-domain works (17 U.S.C. § 105). CMS publishes the public-use file as a no-auth bulk CSV per data year at data.cms.gov. This source is intentionally isolated from the separate cms-provider-utilization puller; the two do not share state. 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

Procedure-level utilization (research-only)

Sample value

NPI 1234567890 · HCPCS 99213 · Office · 240 services · allowed $92.40

Provenance line

Source: CMS Medicare Physician & Other Practitioners (by Provider and Service) · Data Year 2024 · Methodology medicare-physician-service/v1 · Display rule: per-NPI × HCPCS — read API + dataset page; profile rendering deferred with the entity-graph link

How to access

Official API, bulk download, and Fonteum endpoints.

Frequently asked

Common questions about Medicare Physician & Service.

What is the Medicare Physician & Other Practitioners by Provider and Service file?
It is a CMS public-use file at the procedure level: one row per rendering NPI × HCPCS code × place of service for a data year. It reports distinct beneficiaries, total services, submitted charges, and Medicare allowed and payment amounts.
Which data year does Fonteum hold?
CMS publishes one file per data year; Fonteum holds the latest published data year (2024 in the current snapshot). As of the 2026-06-14 snapshot, the table holds 9,781,673 provider × service rows.
Does high service volume mean better care?
No. Service volume and payment are utilization facts, not a measure of clinical quality, appropriateness, or outcomes. A higher volume is not 'better,' and it is not a Fonteum assessment of the provider.
Why are some values blank?
CMS suppresses low-volume cells to protect beneficiary privacy. Fonteum stores suppressed counts as null, never as zero, so an absent value is not read as 'none.'
How is this different from the provider-utilization puller?
This source is intentionally isolated from the separate cms-provider-utilization pipeline — a different table and ingest — so the two do not share state. This one is procedure-level by provider and service.
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