CMS Hospice Compare Scraper

Export CMS Care Compare hospice provider, ZIP service-area, CAHPS survey, state, and national quality datasets from the public CMS Provider Data API.

Use this actor when you need repeatable hospice provider data without manually downloading CMS CSV files or rebuilding API pagination logic.

What does CMS Hospice Compare Scraper do?

CMS Hospice Compare Scraper collects structured records from CMS Provider Data hospice datasets.

It uses the public data.cms.gov API, not a browser session.

It can export provider listings, service ZIP rows, CAHPS survey rows, and aggregate quality tables.

Every row includes the CMS source dataset ID so you can audit where the data came from.

Optional raw records preserve CMS fields that may change over time.

Who is it for?

Healthcare market researchers use it to monitor hospice provider coverage by geography.

Referral networks use it to build provider directories and operational snapshots.

Compliance teams use it to track CMS identifiers, ownership, and quality measures.

Private equity and roll-up analysts use it to map fragmented hospice markets.

Local lead-generation teams use it to find hospice facilities by state, county, or ZIP.

Data engineers use it as a scheduled CMS hospice extractor for warehouses and BI tools.

Why use this actor?

CMS publishes useful data, but teams still need pagination, filters, normalized exports, and stable automation.

This actor wraps the CMS API in an Apify workflow that can be scheduled, integrated, and exported.

You can run small state pulls or larger recurring monitoring jobs.

You can keep raw CMS rows when downstream analysts need every original source column.

Supported CMS hospice datasets

The default mode exports general hospice provider information.

general_info exports the CMS Hospice General Information table.

provider_data exports provider-level quality data.

zip_data exports ZIP service-area rows.

provider_cahps exports provider CAHPS survey rows.

state_cahps exports state CAHPS aggregates.

national_cahps exports national CAHPS aggregates.

state_quality exports state quality aggregates.

national_quality exports national quality aggregates.

Data table

Field	Description
datasetMode	Selected dataset mode
datasetId	CMS Provider Data dataset identifier
datasetTitle	Human-readable CMS dataset name
cmsCertificationNumberCcn	Hospice CMS certification number when available
facilityName	Hospice facility/provider name
addressLine1	Street address line 1
addressLine2	Street address line 2
city	City or town
state	State abbreviation
zipCode	ZIP code
county	County/parish
telephoneNumber	Provider phone number
cmsRegion	CMS region
ownershipType	Ownership classification
certificationDate	CMS certification date
measureCode	CMS measure code for quality rows
measureName	CMS measure name
score	Published score value
footnote	CMS footnote text or code
measureDateRange	Measurement date or date range
sourceUrl	CMS API source URL
scrapedAt	Actor extraction timestamp
rawRecord	Original CMS row when enabled

How much does it cost to extract CMS hospice data?

This actor uses pay-per-event pricing.

There is a small run-start charge plus a per-record charge for each CMS hospice row saved to the dataset.

The default input is intentionally small so first runs stay inexpensive.

Current event prices:

Charge event	When it is charged	FREE	BRONZE	SILVER	GOLD	PLATINUM	DIAMOND
Run started	Once when the actor starts	$0.005	$0.005	$0.005	$0.005	$0.005	$0.005
Hospice record saved	Each CMS hospice row saved	$0.000022576	$0.000019631	$0.000015312	$0.000011779	$0.000010000	$0.000010000

Example cost estimates before Apify platform fees or plan-specific billing details:

Example run	Input pattern	Approximate actor charges
Arizona provider directory	general_info, AZ, 100 records	about $0.0073
Texas CAHPS export	provider_cahps, TX, 500 records	about $0.0148 on BRONZE
National quality benchmark pull	aggregate quality tables, 1,000 records	about $0.0246 on BRONZE

Use maxItems to cap spend on exploratory runs, then increase it for recurring exports once the fields match your workflow.

Input options

datasetModes chooses one or more CMS hospice tables.

states filters by two-letter state abbreviation.

zipCodes filters by ZIP code when the selected table has ZIP data.

counties filters rows by county name after data is returned from CMS.

providerCcns filters by CMS certification number.

maxItems caps the total number of rows saved across all selected datasets.

includeRawRecord keeps the original CMS row for audit and schema-change resilience.

Example input: Arizona provider directory

{
  "datasetModes": ["general_info"],
  "states": ["AZ"],
  "maxItems": 100,
  "includeRawRecord": true
}

Example input: Texas CAHPS rows

{
  "datasetModes": ["provider_cahps"],
  "states": ["TX"],
  "maxItems": 500,
  "includeRawRecord": false
}

Example input: national monitoring

{
  "datasetModes": ["national_cahps", "national_quality"],
  "maxItems": 1000,
  "includeRawRecord": true
}

Output example

{
  "datasetMode": "general_info",
  "datasetId": "yc9t-dgbk",
  "datasetTitle": "Hospice General Information",
  "cmsCertificationNumberCcn": "001500",
  "facilityName": "AGAVE HOSPICE AND PALLIATIVE CARE",
  "city": "PHOENIX",
  "state": "AZ",
  "zipCode": "85032",
  "county": "Maricopa",
  "ownershipType": "For-Profit",
  "sourceUrl": "https://data.cms.gov/provider-data/api/1/datastore/query/yc9t-dgbk/0"
}

How to run

Open the actor on Apify.

Choose one or more dataset modes.

Add state, ZIP, county, or CCN filters if needed.

Set maxItems based on the export size you want.

Run the actor and download the dataset as JSON, CSV, Excel, or through the API.

Scheduling tips

Schedule weekly or monthly runs to monitor changes in hospice provider data.

Use a state filter for regional monitoring.

Use provider CCNs for a watchlist of specific hospices.

Keep rawRecord enabled for warehouse ingestion jobs that must preserve every CMS field.

Integrations

Send results to Google Sheets for regional provider lists.

Load CSV exports into Airtable for operations teams.

Sync JSON records into Snowflake, BigQuery, or Postgres through Apify integrations.

Trigger webhooks when scheduled runs complete.

Use Apify datasets as a stable API for downstream dashboards.

API usage with Node.js

import { ApifyClient } from 'apify-client';

const client = new ApifyClient({ token: process.env.APIFY_TOKEN });
const run = await client.actor('automation-lab/cms-hospice-compare-scraper').call({
  datasetModes: ['general_info'],
  states: ['AZ'],
  maxItems: 100,
});
console.log(run.defaultDatasetId);

API usage with Python

from apify_client import ApifyClient

client = ApifyClient('APIFY_TOKEN')
run = client.actor('automation-lab/cms-hospice-compare-scraper').call(run_input={
    'datasetModes': ['general_info'],
    'states': ['AZ'],
    'maxItems': 100,
})
print(run['defaultDatasetId'])

API usage with cURL

curl -X POST 'https://api.apify.com/v2/acts/automation-lab~cms-hospice-compare-scraper/runs?token=APIFY_TOKEN' \
  -H 'Content-Type: application/json' \
  -d '{"datasetModes":["general_info"],"states":["AZ"],"maxItems":100}'

Use with AI agents via MCP

CMS Hospice Compare Scraper is available as a tool for AI assistants that support the Model Context Protocol (MCP).

Add the Apify MCP server to your AI client to access this actor and other Apify actors.

Setup for Claude Code

$claude mcp add --transport http apify "https://mcp.apify.com?tools=automation-lab/cms-hospice-compare-scraper"

Setup for Claude Desktop, Cursor, or VS Code

Add this actor-scoped MCP server URL to your MCP config file:

{
  "mcpServers": {
    "apify-cms-hospice": {
      "url": "https://mcp.apify.com?tools=automation-lab/cms-hospice-compare-scraper"
    }
  }
}

Your AI assistant will use OAuth to authenticate with your Apify account on first use.

Example prompts:

• "Use automation-lab/cms-hospice-compare-scraper to export Arizona hospice provider records from CMS."
• "Get national hospice CAHPS rows and summarize the measures for a benchmark memo."
• "Build a provider CCN watchlist from CMS hospice data and identify ownership fields."

Best practices

Start with one dataset mode until you confirm the field shape you need.

Use maxItems to control cost and export size.

Use state filters for large provider-level datasets.

Enable rawRecord when CMS column changes matter to your workflow.

Use aggregate national datasets for benchmark dashboards.

Troubleshooting

If a state run returns fewer records than expected, verify the selected CMS dataset actually has state values.

If ZIP filters return no rows, use zip_data or provider tables with ZIP columns.

If you need every CMS column, enable includeRawRecord.

If a run is slow, reduce selected datasets or add state/provider filters.

Legality

This actor reads public CMS Provider Data API endpoints.

Always use the exported data in accordance with CMS terms, Apify terms, and applicable healthcare data rules.

Do not treat scraped/public provider data as medical advice.

Verify critical compliance decisions against official CMS sources.

Related scrapers

Use these automation-lab actors for complementary healthcare, lead enrichment, and territory-planning workflows:

• NPI Registry Provider Scraper — enrich hospice organizations and clinicians with NPI registry identifiers and taxonomy data.
• Website Contact Finder — turn CMS provider websites into outreach-ready emails, phone numbers, and contact pages.
• Email Finder — find likely email addresses for provider domains after you build a hospice target list.
• Google Maps Lead Finder — expand CMS state exports with local map listings and territory-level business signals.
• ClinicalTrials.gov Studies Scraper — monitor healthcare research activity for adjacent market and compliance analysis.

Combine CMS hospice data with website and NPI enrichment when you need outreach-ready provider lists.

Combine state exports with map or local lead actors when you need local territory planning.

FAQ

Does this actor require a CMS login?

No. It uses public CMS Provider Data API endpoints.

Does it use a browser?

No. It is an API-first actor and does not need Playwright.

Can it preserve fields not listed in the schema?

Yes. Enable includeRawRecord to keep the original CMS row.

Can I export multiple tables in one run?

Yes. Select multiple datasetModes; rows include datasetMode and datasetId.

Can I monitor just one provider?

Yes. Add one or more CMS certification numbers in providerCcns.

Why are some fields null?

CMS hospice tables differ. Aggregate rows do not always have provider addresses, while provider rows do not always have measure scores.

Changelog

Initial version exports public CMS hospice datasets with filters, normalized fields, and raw CMS row preservation.