CMS Care Compare Provider Quality Tracker – Healthcare Quality API

A CMS Care Compare API wrapper and healthcare-quality feed that pulls provider quality data from CMS's provider-data datastore — hospitals, nursing homes, home health and more — and normalizes each into a clean record: facility, location, overall rating and quality measures. Point it at any Care Compare dataset by ID. Use it to build a provider-quality comparison tool, a payer network-quality feed, or health-system strategy datasets.

Who uses it

Payers and health plans assessing network quality, health-system strategy and market-intelligence teams, patient-facing comparison products, and healthcare researchers.

Why this is worth charging for

CMS Care Compare data underpins star ratings and quality benchmarking, but it lives across many datastore datasets with dataset-specific field names. This actor normalizes facility identity, location and overall rating across dataset types and returns the remaining quality measures intact, so you can compare and monitor providers without wrangling each dataset's schema.

Output

Each dataset item is one normalized record:

{
  "datasetId": "xubh-q36u",
  "facilityId": "010001",
  "facilityName": "SOUTHEAST HEALTH MEDICAL CENTER",
  "address": "1108 ROSS CLARK CIRCLE",
  "city": "DOTHAN",
  "state": "AL",
  "zip": "36301",
  "phone": "(334) 793-8701",
  "overallRating": "4",
  "measures": {
    "hospital_type": "Acute Care Hospitals",
    "emergency_services": "Yes"
  },
  "source": "CMS Care Compare"
}

Input

Field	Description
datasetId	CMS provider-data dataset ID. Default xubh-q36u = Hospital General Information. Use other IDs for nursing home, home health, etc.
state	Filter facilities by state, e.g. CA.
filterProperty	Optional additional column to filter on, e.g. hospital_type.
filterValue	Value for the extra filter field.
pageSize	Rows per page.
maxPagesToScan	Pages per run.
onlyNewSinceLastRun	Recommended for schedules — skips records already returned by a previous run using persisted state, so you're only charged for genuinely new items.
maxItems	Stop after this many normalized records.

Pricing (Pay-Per-Event)

• query — $0.02, charged once per run for the API query/poll.
• provider-record — $0.01 per normalized record pushed. This is the primary event.
• apify-actor-start (Apify-managed) — covers baseline compute per run.

A statewide hospital pull returns hundreds of facilities per run for a couple dollars. Snapshot the full dataset periodically to track rating changes over time.

Source & reliability

Data comes from the official data.cms.gov/provider-data datastore. Facility identity and location are normalized across dataset types; remaining quality measures are preserved. No key or proxies required. Run npm test for the offline self-test covering the normalizer, including edge cases and missing-field handling.

FAQ

Which providers are covered?

Any CMS Care Compare dataset — hospitals (default), nursing homes, home health, dialysis and more. Set datasetId to switch.

How do I find other dataset IDs?

Browse data.cms.gov/provider-data; each dataset's API path ends in its ID, which you paste into datasetId.

---

Need the rest of the record on these companies?

This actor returns one source. KYB Company Data Enrichment takes a company name and returns what the public record says about it across up to nine sources — state business registries, UCC lien filings, tax warrants and WARN layoff notices, the FMCSA motor-carrier census, the CMS NPI Registry, USAspending federal awards, EPA ECHO compliance, SEC EDGAR filings and CourtListener federal dockets.

Every enriched field carries its source and its match confidence. Only matches above the accept threshold are merged — anything weaker is surfaced as a suggestion and never folded into the record, because a false join is worse than returning nothing.

---

SEO keywords: CMS Care Compare API, hospital quality data, nursing home rating API, healthcare quality scraper, provider star rating feed, Medicare quality data