Skip to content
Today's snapshot: 113,537 providers tracked
fonteum
ResearchToolsFonteumPricingCoverageMethodologyTrustAbout
DATA · MAY 8, 2026

Compliance posture

We don’t sell ranking and don’t accept payment to move a provider up the list. For final hire decisions, verify licensing, insurance, and references directly with the applicable licensing or credentialing body.

No bulk-licensing source family is currently ingested for this vertical. Hire-time checking still routes through the body named above.

Methodology · Corrections log · Editorial policy

fonteum

Healthcare provider data, traced to source.


RESEARCH

  • Research hub
  • Data platform
  • For health-tech
  • Pricing
  • Press kit

NETWORK

  • Coverage
  • Healthcare graph

ABOUT

  • Mission
  • Methodology
  • Editorial policy
  • Corrections log
  • Security
  • SLA
  • Support
  • Refresh cadence
  • Terms
  • Contact

SUBSCRIBE

The monthly research digest. One email, first of each month. Unsubscribe anytime.


© 2026 FONTEUM RESEARCH · DATA SNAPSHOT MAY 8, 2026 · BUILT WITH CARE

  • X
  • LINKEDIN
  • PRESS
Methodology/Dialysis Facility Quality by State (CMS Care Compare)
METHODOLOGY · v2026.05.0

Dialysis Facility Quality by State (CMS Care Compare)

State-level rollups of CMS Care Compare dialysis-facility ratings.

Version v2026.05.0Last refreshed April 1, 2026Cadence Quarterly (matches CMS Care Compare release cadence).
Audit PackResearch studySources registryCorrections log

What this methodology is

This page is the public, versioned methodology for the Dialysis Facility Quality by State (CMS Care Compare) dataset. It documents how every figure on the matched Fonteum Research study, /api/v1 endpoint, and Audit Pack was constructed — from registered public-source ingest through aggregation rules to the rendered output. It exists so buyers can satisfy auditor questions by linking to a single durable URL.

Every section below is the source of truth. Where the methodology differs from the underlying source's own description (for example: which taxonomies count, how Type-1 vs Type-2 NPIs are treated, how density per 100k is computed), the rule lives here, not in the source. Methodology versions (v2026.05.0 today) increment when those rules change; data refreshes within a methodology version are tracked separately under refresh historyand surface as the “Last refreshed” banner above.

Source provenance

Source families
CMS Care Compare datasets (public)
Spatial resolution
Facility (point) + state rollups.
Temporal coverage
CMS quarterly Care Compare release (current snapshot 2026-04-01).
Refresh cadence
Quarterly (matches CMS Care Compare release cadence).
Snapshot scope
7,700 facilities across 51 states + DC; snapshot dated April 1, 2026.

The Fonteum sources registry holds the canonical entry for each source family — Tier classification, ToS posture, refresh schedule, and live-vs-pending status: /sources.

Reproducibility statement

An independent researcher with access only to the public sources listed above can recreate this dataset by following these steps. Discrepancies between an independent reproduction and the published figures belong in /corrections-log; we publish them when they arise.

1. Pull the CMS Care Compare Dialysis Facility dataset from data.cms.gov/provider-data/dataset/23ew-n7w9. 2. Bucket by state. 3. Compute per-state count + rating distribution. 4. Publish state rollups with methodology link to the original CMS dataset.

Limitations

Limitations are surfaced explicitly, not buried. Each item below is a constraint a buyer’s compliance team should review before relying on the dataset for a specific use case.

  • Each CMS measure carries its own published limitations; readers should review the CMS dataset documentation linked in the methodology for measure-specific caveats. We do not modify CMS's published measure values, only re-aggregate to state-level rollups.
  • Sampling-based measures (e.g. patient-experience surveys) carry confidence bands CMS publishes alongside the values. State-level rollups average across facilities and do not preserve those bands; for facility-specific decisions, reference the original CMS Care Compare record.
  • Date alignment: state rollups are computed from the CMS file's published reporting period, not the file release date. The reporting period typically lags the release date by 6-12 months per CMS convention.

Field schema

Every field surfaced from this dataset on the API and rendered surfaces. Source, refresh cadence, and confidence are recorded per field, not per dataset.

FieldDescriptionSourceRefreshConfidence
facility_ccnCMS Certification Number for the dialysis facility.CMS Care Compare — Dialysis Compare ↗Quarterly1.0 (verbatim)
stateFacility state (USPS code).CMS Care Compare — Dialysis Compare ↗Quarterly1.0 (verbatim)
ratingCMS dialysis-facility rating where published.CMS Care Compare — Dialysis Compare ↗Quarterly1.0 (verbatim)

Version history

Every methodology version bump is recorded here with the change rationale. Data-only refreshes (no methodology change) appear as same-version entries with a refresh date.

VersionReleasedWhat changed
v2026.05.0currentMay 6, 2026Initial Audit Pack release. Methodology, provenance map, reproducibility statement, and limitations stack baselined.

Cite this methodology

For procurement attachments, audit responses, footer attribution, or academic use. Pick a format and copy.

Fonteum. (2026). Dialysis Facility Quality by State (CMS Care Compare) (v2026.05.0) [Dataset]. Directory Ventures, LLC. https://fonteum.com/methodology/dialysis-quality

Downloads & cross-references

Download methodology PDF (v2026.05.0)View Audit Pack →
  • Research study → the editorial findings + charts
  • JSON methodology metadata — for programmatic ingestion
  • Download per-state CSV
  • Download per-state JSON

Methodology questions: methodology@fonteum.com. Data corrections: /corrections-log. B2B inquiries: api@fonteum.com.

This page is the durable URL a buyer’s compliance officer can link from their product. The version pinned at the URL (v2026.05.0) is the active methodology; historical versions remain accessible at the same URL with prior-version content available in the Version history table.