Skip to content
FonteumPublic-records evidence
AUDIT PACK · v2026.05.0

Hospice Provider Availability by State (CMS Care Compare)

State-level rollups of CMS Care Compare hospice provider counts.

Methodology versionv2026.05.0
Last snapshot2026-04-01
Publisher cadenceQuarterly (matches CMS Care Compare release cadence).
Spatial resolutionFacility (point) + state rollups
Records5,300 providers
State coverage51 states + DC
Download Audit Pack (PDF) →Download Audit Pack (JSON) →Free. No login. Versioned. Cite in your audit response.

Looking for the public per-dataset methodology page (citations + version history) to link from your product? /methodology/hospice-availability

What's in this pack

  • 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).
  • Publisher cadence: Quarterly (matches CMS Care Compare release cadence).; this is not proof of the loaded snapshot's currency.
  • Scope: 5,300 providers across 51 states + DC. Snapshot date: 2026-04-01.

Documented field map

This manifest lists documented fields with source attribution, publisher cadence, and confidence definitions. Runtime records can expose a subset; record-level provenance values may be null or absent. Verbatim source values are confidence 1.0; Fonteum-derived metrics (per-100k, ranks) are 0.95 with the derivation logic below.

FieldSourcePublisher cadenceConfidence
provider_ccn
CMS Certification Number for the hospice provider.
CMS Care Compare — Hospice CompareQuarterly1.00 ✓
state
Hospice state (USPS code).
CMS Care Compare — Hospice CompareQuarterly1.00 ✓
provider_type
Hospice provider type (free-standing, hospital-based, home-health-based, etc.).
CMS Care Compare — Hospice CompareQuarterly1.00 ✓

Reproducibility statement

A buyer should be able to rerun the methodology against the same public source data and reconcile counts. Discrepancies belong in the corrections log; we publish them when they arise.

1. Pull the CMS Care Compare Hospice Compare dataset from data.cms.gov/provider-data/dataset/252m-zfp9.
2. Bucket by state.
3. Compute per-state count + provider-type breakdown.

Limitations

  • 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.

Version history

  1. v2026.05.0 · released 2026-05-06
    Initial Audit Pack release. Methodology, provenance map, reproducibility statement, and limitations stack baselined.

Compliance Q&A

The most common questions a procurement / compliance officer asks during evaluation. Answers cite source links so the response can be lifted directly into your internal audit document.

Q: What is the source of these facility-quality measures?

CMS Care Compare datasets, published quarterly at data.cms.gov/provider-data/. CMS itself publishes the measure definitions, sampling methodology, and known limitations; Fonteum Research re-aggregates state-level rollups without altering the underlying measure values.

Reference: https://data.cms.gov/provider-data/

Q: When was this dataset last updated?

Read the dated metadata on the particular study before using it. When checked 2026-07-12, supported Care Compare serving tables reported 2026-05-07 as their newest source date. CMS's publisher schedule does not prove a later Fonteum load completed.

Reference: https://fonteum.com/corrections-log

Q: Are CMS's own published limitations preserved?

The Limitations section summarizes the known caveats documented for this audit pack and links to the CMS source. It is not a promise that every caveat in every upstream document has been reproduced; consult the named CMS documentation before relying on a measure.

Reference: https://fonteum.com/methodology#limitations

Q: Can I reproduce these counts independently?

Yes — the reproducibility statement above lists the exact CMS dataset(s) ingested and the per-state aggregation logic. A buyer can rerun the methodology against the same Care Compare release and reconcile counts.

Reference: https://fonteum.com/corrections-log

Q: What is the licensing scope of this data?

CMS Care Compare data is public-domain federal information. Fonteum's aggregated rollups are licensed under our editorial-policy terms.

Reference: https://fonteum.com/terms

Need a customer-scoped Audit Pack?

Pilot, Standard, and Enterprise customers receive Audit Packs scoped to their delivery cadence and contracted dataset list. The methodology version is pinned to the snapshot delivered, so the artifact is durable across the contract period. Contact pilot@fonteum.com or request access at /pilot-intake.

Open the parent research study → · ← All Audit Packs

What’s on file, by the numbers

Platform snapshot · 2026-08-08

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