Skip to content
FonteumPublic-records evidence

← All sources Healthcare graph

CMS Order & Referring

CMS Order and Referring

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

Research-only

The CMS Order and Referring file is the list of NPIs eligible to order and refer in Medicare, with a Y/N eligibility flag per benefit category (Part B, DME, Home Health, Power Mobility Devices, Hospice). One row per NPI, with last and first name. NPI is carried verbatim; the entity-graph cross-link is deferred.

What Fonteum uses it for

How this source shows up on Fonteum.

Per-NPI Medicare order/refer eligibility, 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 eligibility does not yet render on individual provider profiles.

What this source does NOT mean

Order-and-refer eligibility is a Medicare administrative authorization — it does not indicate quality, outcomes, board certification, or appointment availability, and absence is not a negative quality signal. Eligibility is not a Fonteum assessment of the provider.

What this dataset answers

Research and data questions this source supports.

  • Check whether an NPI is eligible to order and refer in Medicare, by benefit category (Part B, DME, Home Health, Power Mobility Devices, Hospice).
  • Build a claims-integrity check that validates the ordering/referring NPI on a claim is eligible for that benefit.
  • Cross-reference order/refer eligibility against the OIG LEIE to surface eligible-but-excluded providers for compliance research.
  • Power a provider-data API that returns Medicare order/refer eligibility flags per NPI.

Dataset size: 2,008,019 enrolled providers (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

8 fields
npiNPI (10-digit identifier)
last_nameLast name
first_nameFirst name
eligible_part_bEligible — Medicare Part B
eligible_dmeEligible — Durable Medical Equipment
eligible_hhaEligible — Home Health Agency
eligible_pmdEligible — Power Mobility Devices
eligible_hospiceEligible — Hospice
Limitations

What we can’t infer from this source.

  • Eligibility is a Medicare administrative flag, not a quality measurement.
  • NPI-keyed, but the entity-graph cross-link is deferred — eligibility does not render on individual provider profiles yet.
  • The file republishes roughly weekly; eligibility changes lag the live CSV by up to one publication cycle.
  • Absence from the file is not a negative signal — many providers are not order/refer-eligible by enrollment type.
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: Roughly weekly — CMS republishes the Order and Referring file under a release-dated path. Not evidence of the latest loaded source date.

License

U.S. government public-domain works. Free to use with attribution; explicit redistribution rights. License ↗

Attribution requirement

Source: Centers for Medicare & Medicaid Services (CMS) — Order and Referring · Snapshot {YYYY-MM-DD}

ToS & usage notes

What the source allows.

U.S. government public-domain works. CMS publishes the Order and Referring file as a no-auth bulk CSV at data.cms.gov with explicit redistribution rights. 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

Order/refer eligibility (research-only)

Sample value

NPI 1063717142 · Part B: Y · DME: Y · HHA: Y · Hospice: N

Provenance line

Source: CMS Order and Referring · Snapshot 2026-06-14 · Methodology cms-order-referring/v1 · Display rule: per-NPI eligibility — 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 CMS Order & Referring.

What is the CMS Order and Referring file?
It is the CMS list of NPIs eligible to order and refer in Medicare, with a Y/N eligibility flag per benefit category — Part B, Durable Medical Equipment, Home Health Agency, Power Mobility Devices, and Hospice. There is one row per NPI, with last and first name.
How often does it update and where is it published?
CMS republishes the file roughly weekly at data.cms.gov as a no-auth bulk CSV under a release-dated path. Fonteum resolves the live CSV by the stable dataset UUID and attests each snapshot. As of the 2026-06-14 snapshot, Fonteum holds 2,008,019 order/refer-eligible providers.
Does eligibility render on provider profiles?
Not yet. Order/refer eligibility is available via the read API and the dataset page, but the NPI → entity-graph link is a separate, gated follow-up, so eligibility does not yet render on individual provider profiles.
Is order/refer eligibility a quality signal?
No. Eligibility is a Medicare administrative authorization. It does not indicate quality, outcomes, board certification, or appointment availability, and absence from the file is not a negative signal — many providers are not order/refer-eligible by enrollment type.
How can I cite this data?
Use 'Source: Centers for Medicare & Medicaid Services (CMS) — Order and Referring' with the snapshot date. It is U.S. government public-domain data with explicit redistribution rights.
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-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