CMS Dialysis Facility Compare Scraper

Extract dialysis facility listings, quality ratings, patient survey scores, and ESRD QIP metrics from the public CMS Provider Data API.

What does CMS Dialysis Facility Compare Scraper do?

CMS Dialysis Facility Compare Scraper turns public CMS dialysis datasets into clean Apify dataset rows.

It supports three CMS Provider Data API sources:

• 🏥 Dialysis Facility - Listing by Facility
• ⭐ Patient survey (ICH CAHPS) - Facility
• 📊 ESRD QIP - Complete QIP Data

Use it to collect dialysis facility names, CCNs, addresses, ownership flags, chain organizations, service capabilities, quality categories, survey ratings, and QIP performance fields.

Who is it for?

This actor is built for teams that monitor ESRD and dialysis facility data.

• 🧑‍⚕️ Healthcare analysts benchmarking quality and access
• 💼 Payers evaluating dialysis provider networks
• 📈 Consultants preparing market maps and facility scorecards
• 🏢 B2B healthcare vendors finding sales/account triggers
• ✅ Compliance teams tracking CMS quality-program data
• 🧪 Data teams enriching internal provider master files

Why use it?

CMS publishes dialysis data, but analysts often need a repeatable workflow.

This actor gives you:

• A simple input form for common dialysis filters
• Repeatable runs for state, city, ZIP, CCN, chain, and ownership monitoring
• JSON, CSV, Excel, and API exports through Apify datasets
• Optional raw CMS records when you need every source column
• A normalized output table for common business workflows

Data sources

The actor uses public CMS Provider Data API endpoints on data.cms.gov.

Input option	CMS dataset	Best for
facility	23ew-n7w9	Facility listing, addresses, ownership, services, ratings
patientSurvey	59mq-zhts	ICH CAHPS patient survey ratings
qipComplete	complete_qip_data	ESRD QIP scores and payment metrics

What data can you extract?

Typical output fields include:

Field	Description
ccn	CMS Certification Number
facilityName	Dialysis facility name
address	Street address
city, state, zipCode, county	Location fields
phone	Facility phone number
profitStatus	Profit or non-profit flag
chainOwned	CMS chain-owned flag
chainOrganization	Chain organization name
dialysisStations	Number of dialysis stations
fiveStarRating	CMS five-star rating when available
patientSurvivalCategory	Survival performance category
hospitalizationCategory	Hospitalization performance category
readmissionCategory	Readmission performance category
surveyOverallFacilityRating	ICH CAHPS facility rating
qipTotalPerformanceScore	ESRD QIP total performance score
sourceUrl	CMS source dataset page

How much does it cost to scrape CMS dialysis facility compare data?

This actor uses pay-per-event pricing.

• A small start fee is charged once per run.
• A per-record event is charged for each CMS dialysis record saved.
• You control cost with maxItems and filters.

Because the actor uses a public API and does not require a browser or proxies, runs are designed to be inexpensive and predictable.

Quick start

1. Open the actor on Apify.
2. Choose a CMS dialysis dataset.
3. Set maxItems.
4. Add filters such as state, city, ZIP, facility name, or CCN.
5. Run the actor.
6. Export results from the dataset as JSON, CSV, Excel, or through the Apify API.

Input options

Dataset

Use datasetType to choose the CMS source:

• facility for core facility listing and quality categories
• patientSurvey for patient experience ratings
• qipComplete for ESRD QIP metrics

Filters

You can filter by:

• State abbreviation
• City name
• ZIP code or ZIP prefix
• County/parish
• Facility name
• CMS Certification Number
• Chain-owned flag
• Profit/non-profit status
• Minimum or maximum dialysis stations

Raw record option

Set includeRawRecord to true when you need the full raw CMS API row in addition to normalized fields.

Example input: California dialysis facilities

{
  "datasetType": "facility",
  "state": "CA",
  "maxItems": 100
}

Example input: Los Angeles patient survey ratings

{
  "datasetType": "patientSurvey",
  "state": "CA",
  "city": "Los Angeles",
  "maxItems": 50
}

Example input: ESRD QIP records for a facility name

{
  "datasetType": "qipComplete",
  "facilityName": "dialysis",
  "state": "TX",
  "maxItems": 100,
  "includeRawRecord": true
}

Example output

{
  "datasetType": "facility",
  "datasetId": "23ew-n7w9",
  "datasetTitle": "Dialysis Facility - Listing by Facility",
  "ccn": "052345",
  "facilityName": "EXAMPLE DIALYSIS CENTER",
  "network": "18",
  "address": "123 MAIN ST",
  "city": "LOS ANGELES",
  "state": "CA",
  "zipCode": "90001",
  "county": "Los Angeles",
  "phone": "(555) 555-0100",
  "profitStatus": "Profit",
  "chainOwned": "Yes",
  "chainOrganization": "Example Chain",
  "dialysisStations": 24,
  "fiveStarRating": 4,
  "sourceUrl": "https://data.cms.gov/provider-data/dataset/23ew-n7w9",
  "scrapedAt": "2026-07-04T00:00:00.000Z"
}

Tips for better results

• Use state when you need a practical state-level export.
• Add city or zipCode to target a market area.
• Use ccn for exact facility checks.
• Use includeRawRecord only when you need all CMS columns because it makes output wider.
• For broad monitoring, schedule one run per state or region.

Common workflows

Network analysis

Collect dialysis facilities in a state or metro area, then compare ownership, chains, services, and quality categories.

Sales/account monitoring

Run scheduled searches for target markets and identify facilities by chain, ownership, size, or QIP/survey signals.

Compliance research

Export QIP or survey datasets and preserve the raw CMS record for audit trails.

Provider master enrichment

Match internal provider records by CCN, facility name, ZIP, and state, then enrich with CMS public fields.

Integrations

Use results with:

• Apify datasets
• Google Sheets exports
• BI tools such as Tableau, Power BI, or Looker
• CRM enrichment workflows
• Data warehouses
• Apify webhooks and schedules
• Zapier or Make scenarios

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-dialysis-facility-compare-scraper').call({
  datasetType: 'facility',
  state: 'CA',
  maxItems: 100,
});

const { items } = await client.dataset(run.defaultDatasetId).listItems();
console.log(items);

API usage with Python

from apify_client import ApifyClient
import os

client = ApifyClient(os.environ['APIFY_TOKEN'])
run = client.actor('automation-lab/cms-dialysis-facility-compare-scraper').call(run_input={
    'datasetType': 'facility',
    'state': 'CA',
    'maxItems': 100,
})
items = client.dataset(run['defaultDatasetId']).list_items().items
print(items)

API usage with cURL

curl -X POST "https://api.apify.com/v2/acts/automation-lab~cms-dialysis-facility-compare-scraper/runs?token=$APIFY_TOKEN" \
  -H 'Content-Type: application/json' \
  -d '{"datasetType":"facility","state":"CA","maxItems":100}'

MCP integration

Use this actor from Claude Desktop, Claude Code, or other MCP-compatible clients through Apify MCP.

MCP tool URL:

https://mcp.apify.com/?tools=automation-lab/cms-dialysis-facility-compare-scraper

Add it in Claude Code:

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

Claude Desktop JSON configuration:

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

Example prompts:

• "Extract CMS dialysis facilities in California and summarize the largest chains."
• "Find ICH CAHPS dialysis survey records for Los Angeles."
• "Get ESRD QIP records for Texas dialysis facilities and show low scoring facilities."

Scheduling

You can schedule the actor to run monthly or quarterly as CMS updates dialysis datasets.

Suggested schedules:

• Monthly state-level exports
• Quarterly QIP monitoring
• Weekly sales territory refreshes
• Ad hoc CCN checks during diligence or compliance reviews

Limitations

• The actor returns public CMS data as available from data.cms.gov.
• CMS fields vary by dataset; some output fields are null when the selected dataset does not contain that measure.
• Very broad filtered searches may scan multiple API pages before finding enough matches.
• This actor does not infer clinical conclusions; it exports source data for your analysis.

Legality and compliance

The actor uses public CMS Provider Data API endpoints. Always use the data according to CMS terms, Apify terms, and your organization's compliance requirements.

Public healthcare data can still be sensitive in context. Review downstream usage, retention, and sharing policies before combining it with other datasets.

FAQ

Does this scrape a website or use a browser?

No. It uses the public CMS Provider Data API directly.

Can I search by CMS Certification Number?

Yes. Use the ccn input with a full or partial CCN.

Why are some fields null?

CMS datasets contain different fields. For example, QIP records include payment and performance fields, while the facility listing includes service flags and stations.

Can I get every CMS source column?

Yes. Set includeRawRecord to true to include the full raw CMS API row.

What if my run returns zero records?

Try fewer filters first. For example, use only state and maxItems, then add city, ZIP, CCN, or name filters.

Related scrapers

Explore related Automation Lab healthcare data actors:

• https://apify.com/automation-lab/cms-hospital-compare-scraper
• https://apify.com/automation-lab/cms-hospice-compare-scraper
• https://apify.com/automation-lab/cms-nursing-home-compare-scraper
• https://apify.com/automation-lab/home-health-care-compare-scraper

Support

If you need a field from a CMS dialysis dataset that is not normalized yet, enable includeRawRecord first. If you still need help, open an Apify issue with the run URL and desired field.

Changelog

• Initial version: CMS dialysis facility listing, ICH CAHPS survey, and ESRD QIP Complete Data support.