CMS Hospital Enrollment Scraper - Locations & Identifiers avatar

CMS Hospital Enrollment Scraper - Locations & Identifiers

Pricing

from $1.80 / 1,000 results

Go to Apify Store
CMS Hospital Enrollment Scraper - Locations & Identifiers

CMS Hospital Enrollment Scraper - Locations & Identifiers

Collect official CMS Hospital Enrollments by state, city or organization. Export published identifiers and location fields with source status. No API key; no hospital quality ratings.

Pricing

from $1.80 / 1,000 results

Rating

0.0

(0)

Developer

Brandt May

Brandt May

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

3 days ago

Last modified

Categories

Share

Hospital enrollment records, organized — illustrative workflow

Hospital enrollment records, organized

Build a hospital enrollment and location research table from the official CMS data API. This Actor uses the Hospital Enrollments feed associated with the broader Care Compare ecosystem.

Open this Actor in Console · First run · Results · Cost · Full guide

Try this Actor

  1. Choose a small scope. Keep the existing TN state prefill and maximum of twenty-five records for a first sample. Add city or organization-name filters if you need a narrower slice.
  2. Run and review. Open the dataset for enrollment rows and the run's key-value-store SUMMARY for saved counts, source failures and incomplete coverage.
  3. Use the results. Export CSV or JSON and retain CMS Certification Numbers (CCNs) and National Provider Identifiers (NPIs) where published.

Read this before using the data: This feed contains enrollment records, not hospital quality ratings or a clinical recommendation. The classic Hospital General Information Care Compare dataset is not the source used here.

Result preview

The dataset view highlights these columns:

  • CMS certification number · ccn
  • National provider identifier · npi
  • Organization name · organizationName
  • Doing-business-as name · dbaName
  • City · city
  • State · state

Use the original source links and the field definitions below when interpreting the results. CSV works well for flat columns; JSON preserves nested values.

Usage and pricing

Base result rate on the FREE tier: $3 per 1,000 results. The Pricing tab shows your plan's result rate and any Actor Start charge. Set a small result limit for the first run; the requested limit is not a guarantee of that many results.


Full guide

Collect CMS Hospital Enrollments from the official data.cms.gov data API. No API key.

What it does

Fetches enrollment rows (CCN, NPI, organization, address, subgroups) from dataset id f6f6505c-e8b0-4d57-b258-e2b94133aaf2 via https://data.cms.gov/data-api/v1/dataset/.../data.

Honest scope

This Actor uses Hospital Enrollments, not the Hospital General Information Care Compare dataset. Its enrollment and location fields do not include hospital quality ratings.

Input

  • state — default TN
  • organizationContains / city — optional filters
  • maxResults / maxRunSeconds

Source updates

CMS can replace dataset identifiers or change availability. The source is listed as Hospital Enrollments in the CMS data catalog. Report source failures through Actor Issues.

Result accounting

Only real source records are written to the dataset. SUMMARY.total counts saved rows. A dataset spending cap stops further writes and sets SUMMARY.stoppedOnChargeLimit and SUMMARY.incomplete. Source failures and time limits are reported in the summary; they do not generate substitute result rows.

Help with your run

Open the Issues tab on this Actor with the run URL, the input field that caused trouble and what you expected to receive. Remove API keys and private information before posting.

Explore more Mayd-It Actors

Understand your run

Open Run report in the run’s Output tab for saved-record counts, reported source issues and limits, and suggested next steps. Use CSV export to take the saved results into a spreadsheet. The existing JSON results and detailed machine-readable summary remain available.

The report reflects this run’s recorded coverage. A successful run or a saved result does not establish that every possible source record was collected.