Skip to content
FonteumPublic-records evidence

← All sources Research / economic / workforce

CMS Market Saturation

CMS Market Saturation & Utilization (State-County)

Centers for Medicare & Medicaid Services (CMS) · Tier-1 · research-only (never on individual profiles)

Research-only

The CMS Market Saturation & Utilization (State-County) file is a program-integrity monitoring dataset. Per county, state, and nation, and per provider/supplier service type, it reports how saturated the local market is with Medicare-enrolled providers and how Medicare fee-for-service utilization is distributed, plus the CMS enrollment-moratorium flag for the geography. It is geography + service-type keyed — there is no individual provider NPI.

What Fonteum uses it for

How this source shows up on Fonteum.

Tier-1 area-level context for /data and /research pages on provider supply and Medicare utilization by geography. Fonteum surfaces provider counts, beneficiary counts, average users per provider, and total payment per geography × service type, resolvable by FIPS.

What this source does NOT mean

Market saturation describes the supply of providers in a geography — it is not a quality measurement, not a statement about any individual provider, and a high or low saturation value is not a Fonteum judgment about access or care in that area.

What this dataset answers

Research and data questions this source supports.

  • Resolve a county or state FIPS to its provider counts, beneficiary counts, and total Medicare payment by service type.
  • Build a provider-supply map that surfaces where a service type is over- or under-represented relative to beneficiaries.
  • Identify geographies under a CMS enrollment moratorium for a program-integrity study.
  • Power an access-research surface combining market saturation with HRSA shortage-area designations.

Dataset size: 1,030,290 geography × 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

8 fields
reference_periodReference period
type_of_serviceProvider/supplier service type
aggregation_levelAggregation level (nation / state / county)
geo_fipsGeography FIPS (2- or 5-digit)
number_of_providersNumber of providers
number_of_ffs_beneficiariesMedicare FFS beneficiaries
total_paymentTotal Medicare FFS payment
moratoriumEnrollment-moratorium flag
Limitations

What we can’t infer from this source.

  • Geography + service-type keyed — there is no individual provider NPI and no entity-graph linkage.
  • Tier-1 — area-level research context only; never rendered on individual provider profiles.
  • Market saturation is a supply signal, not a quality or access measurement.
  • CMS suppresses small cells; suppressed counts are stored as null, not zero.
Source metadata

Authority, license, publisher cadence.

Authority

Centers for Medicare & Medicaid Services (CMS)

Tier

Tier-1 · research-only (never on individual profiles)

Publisher / configured cadence

Declared or configured cadence: Semiannual — CMS republishes the State-County file under a fresh 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) — Market Saturation & Utilization (State-County) · Snapshot {YYYY-MM-DD}

ToS & usage notes

What the source allows.

U.S. government public-domain works. CMS publishes the Market Saturation & Utilization State-County 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

Market saturation (area-level research context)

Sample value

County FIPS 06037 · Home Health · 142 providers · 38,400 FFS beneficiaries

Provenance line

Source: CMS Market Saturation & Utilization · Snapshot 2026-06-14 · Methodology cms-market-saturation/v1 · Display rule: geography-keyed — renders on dataset + research pages, never on individual profiles

How to access

Official API, bulk download, and Fonteum endpoints.

Frequently asked

Common questions about CMS Market Saturation.

What is the CMS Market Saturation & Utilization dataset?
It is a CMS program-integrity monitoring dataset. Per county, state, and nation, and per provider/supplier service type, it reports how saturated the local market is with Medicare-enrolled providers and how Medicare fee-for-service utilization is distributed, plus the CMS enrollment-moratorium flag for the geography.
Is this keyed to individual providers?
No. The dataset is geography + service-type keyed — there is no individual provider NPI and no entity-graph linkage. The read API resolves on FIPS (2-digit state or 5-digit county).
What is the enrollment moratorium flag?
CMS can impose a temporary moratorium on new Medicare enrollments for a provider type in a geography to combat fraud. The moratorium field flags whether such a moratorium applies; it is a program-integrity control, not a quality signal.
How often is the data published?
CMS republishes the State-County file semiannually at data.cms.gov as a no-auth bulk CSV. Fonteum resolves the live CSV by the stable dataset UUID and attests each snapshot. As of the 2026-06-14 snapshot, Fonteum holds 1,030,290 geography × service rows spanning reference periods from 2020 to 2025.
Is high market saturation good or bad?
Neither — it is a supply signal. Market saturation describes how many providers of a service type operate in a geography relative to beneficiaries. It is not a quality measurement and not a Fonteum judgment about access or care in that area.
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