CMS Medicare Facility Leads avatar

CMS Medicare Facility Leads

Pricing

$5.00 / 1,000 facility records

Go to Apify Store
CMS Medicare Facility Leads

CMS Medicare Facility Leads

Official CMS facility lists: home health, hospice, nursing homes, dialysis and certified ASCs. Phone/address where supplied, no email. Exact organizational-owner joins for home health/hospice with explicit coverage gaps. Dated snapshots, not alerts.

Pricing

$5.00 / 1,000 facility records

Rating

0.0

(0)

Developer

Yanai Ron

Yanai Ron

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

7 days ago

Last modified

Categories

Share

One facility lookup/export Actor for home health agencies, hospices, nursing homes, dialysis facilities and certified ambulatory surgical centers (ASCs). Uses official public CMS snapshots, without a CMS API key. No patient data. Price: $0.005 per output facility ($5 per 1,000).

Input

{
"facilityTypes": ["hospice", "home_health"],
"state": "AZ",
"name": "hospice",
"includeOwnership": true,
"maxRecords": 100
}
  • facilityTypes: any nonempty selection of home_health, hospice, nursing_home, dialysis, asc. Default: all five, in that order.
  • state: optional two-letter state/territory code. city: optional exact city, case-insensitive.
  • name: optional case-insensitive facility-name substring. ccn: optional exact CMS identifier, as a string to preserve leading zeroes. ASC IDs can contain letters.
  • includeOwnership: default true. Enriches home health and hospice only.
  • maxRecords: global output cap, 1-100,000, default 1,000. Types run in input order, not round-robin. The first type can fill the entire cap. Select a single type for a focused list.

One output item and one pricing event per facility-type + CCN. Hospice quality-measure rows are collapsed before output; owners and enrollment rows are nested and do not incur separate record events. CSV/JSON exports are available from the Apify dataset.

Output

Each item includes ccn, facilityType, businessName, phone, address, addressLine2, city, state, zip, county, country, ownershipType, legalBusinessName, chainName, and available starRating, certifiedBeds, dialysisStations. Missing fields are null. Email is always null: none is sourced here. Star-rating scales and definitions differ by facility type; they are not comparable clinical advice.

Provenance includes sourceUrl, sourceDownloadUrl, sourceModified and, when available, sourcePeriod. CMS metadata modification dates are not a claim that each facility was checked on that date. No claim of real-time active status is made for the Provider Data Catalog lists. ASCs must be provider type 11 and have CMS status Certified in the iQIES snapshot.

For home health and hospice, enrollments preserves enrollment ID, NPI and legal business name. organizationOwners contains only organizational associates (TYPE - OWNER = O), with role, reported percentage and association date. A managerial-control relationship is not necessarily equity ownership, and percentages must not be summed across roles or enrollments. Private-equity/REIT flags mean CMS reported Y, not a verified negative when false. Individual owners, their names and all owner addresses are omitted. Facility registered contacts may still be residential or personal.

ownershipStatus makes gaps explicit:

  • matched_organization_owner: exact CCN -> enrollment ID -> organizational associate match.
  • matched_enrollment_no_organization_owner: matched enrollment but no organizational associate returned; this may mean individual-only ownership.
  • unmatched_ccn: no matching enrollment in the ownership snapshot. No name-based guess is made.
  • not_available_for_type: enrichment is not offered for this facility type.
  • not_requested: enrichment disabled.

Ownership provenance includes its period, modification date and source URL. Different CMS source snapshots can disagree. This is a lookup/lead-list product, not an ownership certification, change alert, exhaustive facility directory, or permission to contact people.

Sources and audit (2026-10-14)

TypeOfficial sourceSnapshot metadata modifiedFacilities
Home healthhttps://data.cms.gov/provider-data/dataset/6jpm-sxkc2026-05-2712,460
Hospicehttps://data.cms.gov/provider-data/dataset/252m-zfp92026-08-076,669
Nursing homeshttps://data.cms.gov/provider-data/dataset/4pq5-n9py2026-09-3014,690
Dialysishttps://data.cms.gov/provider-data/dataset/23ew-n7w92026-06-167,490
ASCshttps://data.cms.gov/provider-characteristics/hospitals-and-other-facilities/provider-of-services-file-internet-quality-improvement-and-evaluation-system2026-08-10, Q2 20266,640

Total: 47,949 facility-type/CCN records, not deduplicated across types. Hospice source: 453,492 measure rows collapsed to 6,669 facilities; no conflicting facility name/state/address found within CCN. Snapshot counts change and are not coverage guarantees.

Home health exact enrollment matches: 11,254/12,460; organizational associates: 4,460/12,460. Hospice: 5,696/6,669 and 3,007/6,669 respectively. These gaps are expected and visible in output, not silently filled.

Ownership and enrollment discovery: https://data.cms.gov/data.json . Select the latest snapshot period (not merely latest metadata modification) and require matching ownership/enrollment periods. Ownership snapshot: Q3 2026; owners modified 2026-08-19, enrollments 2026-07-27. These quarterly series have existed since 2023, not a new 2026 release.

Reliability and cost

Sources are resolved at runtime. CSV parsing is streamed, including the large iQIES roster, with explicit UTF-8/Windows-1252 decoding. Missing required headers, HTTP failures and mismatched ownership/enrollment periods fail the run instead of fabricating data. Up to three request attempts, each bounded to 180 seconds. Source interruption midway through a file fails rather than silently returning an incomplete list. Network/file scans can dominate the cost of small filtered requests; maxRecords caps output, not source scanning.

Unit tests are offline. Weekly/manual CI runs a small live smoke against all five types and real ownership joins. No persistent baseline, delta mode, scheduling or alerts. An Actor can be called through Apify's MCP integration after deployment; no separate MCPize listing or MCP server is published by this code.

npm ci
npm test
npm run smoke:cms

Release status

Published on Apify Store on 2026-10-14 after offline tests, live source checks, one cloud build and five cloud smoke runs. Updates to cloud code are deployed from a tested source snapshot; this Actor has no automatic GitHub rebuild hook.