Healthcare Provider Data API - CMS Hospital & Nursing Home
Pricing
from $14.00 / 1,000 results
Healthcare Provider Data API - CMS Hospital & Nursing Home
Query official CMS provider data for hospitals, nursing homes, dialysis facilities, hospices, home health agencies and rehab centers. Filter by state, city, ZIP or county for star ratings, hospital data and hospice records, with no API key.
Pricing
from $14.00 / 1,000 results
Rating
0.0
(0)
Developer
Joseph McRell
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
22 minutes ago
Last modified
Share
CMS Healthcare Provider Search
Search official CMS healthcare provider datasets by provider type, state, city, ZIP, county or name. Export normalized facility records without an API key. This Actor turns official CMS Provider Data Catalog APIs into bounded, structured datasets for analysis, enrichment, monitoring, and AI-agent workflows.
What data can I extract?
65 flat columns per provider, normalized across seven CMS directories that do not share a column vocabulary:
- Identity and contact -
ccn,name,legal_name,address,city,state,zip,county,phone,latitude,longitude,urban_location,cms_region,esrd_network. - Classification -
provider_type,subtype,ownership,certification_date,data_processing_date. - Corporate structure -
chain,chain_owned,chain_facility_count,chain_average_star_rating,ownership_changed_last_12_months,resides_in_hospital,continuing_care_retirement_community. - Capacity and services -
beds,stations,average_daily_residents,services_offered,emergency_services,late_shift,birthing_friendly. - Ratings -
star_ratingplus the nursing-home componentshealth_inspection_rating,staffing_rating,quality_measure_rating,longstay_quality_rating,shortstay_quality_rating. - Inspections and enforcement -
last_health_inspection_date,inspection_over_2_years_ago,health_deficiencies,weighted_health_survey_score,infection_control_citations,abuse_flag,special_focus_status,number_of_fines,total_fines_usd,number_of_payment_denials. - Staffing -
nurse_staffing_hours_per_resident_day,rn_staffing_hours_per_resident_day,nursing_staff_turnover_pct,rn_turnover_pct,administrator_departures. - Comparative outcomes -
timely_care_pct,readmission_performance,hospitalization_performance,patient_survival_performance,patient_infection_performance, and the hospital measure countsmortality_measures_better/_worse,safety_measures_better/_worse,readmission_measures_better/_worse.
Every row carries every column, so the dataset exports as one rectangular CSV. A column CMS does not publish for a given directory is null rather than absent. Download results as JSON, CSV, Excel, XML, or access them through the Apify API.
Input example
{"provider_types": "hospital","state": "TX","city": "Houston","max_items": 100}
max_items is a hard output and billing ceiling. The default input is intentionally limited to 10 records so Store tests and first runs stay inexpensive.
Output example
One real record from the input above, with the columns CMS does not publish for hospitals omitted for brevity:
{"provider_type": "hospital","ccn": "450068","name": "MEMORIAL HERMANN - TEXAS MEDICAL CENTER","address": "6411 FANNIN","city": "HOUSTON","state": "TX","zip": "77030","county": "HARRIS","phone": "(713) 704-3700","ownership": "Voluntary non-profit - Private","subtype": "Acute Care Hospitals","star_rating": 4.0,"emergency_services": "Yes","birthing_friendly": "Y","mortality_measures_better": 1,"mortality_measures_worse": 0,"safety_measures_better": 4,"safety_measures_worse": 0,"readmission_measures_better": 2,"readmission_measures_worse": 2}
Nursing-home rows additionally carry staffing hours, turnover, fines, inspection dates and the five-star components; dialysis and home-health rows carry services_offered and the comparative outcome columns. The dataset schema documents every field with a title, type, description, and example so humans and AI tools can inspect the contract before running it.
Use with AI agents and MCP
Apify's hosted MCP server can discover and call this Actor. A suitable agent request is:
Find up to 100 hospitals in Houston, Texas with CMS identifiers, addresses, phone numbers and facility attributes.
Use this exact Actor input:
{"provider_types": "hospital","state": "TX","city": "Houston","max_items": 100}
The Actor succeeds with a nonempty default dataset and exposes its default dataset through the top-level Output schema.
Pricing and cost control
Output is billed per result at $0.02 per result (about $20.00 per 1,000 results), plus a $0.0005 Actor-start charge billed once per gigabyte of memory at run start. Use max_items to cap both output volume and charges. The price shown on the Apify Store listing is authoritative.
Use max_items to cap returned and billable records. Invalid input is rejected before unnecessary work wherever possible.
Common use cases
- Source-specific research and market intelligence
- Structured exports for spreadsheets, warehouses and BI systems
- Entity enrichment and monitoring pipelines
- Retrieval and data collection by AI agents
Reliability
The Actor uses bounded pagination, retries transient upstream failures, deduplicates records where the source exposes stable identifiers, and fails explicitly when the source cannot provide usable output. Production default-input canaries verify a nonempty structured dataset in under five minutes.
Limitations and responsible use
- Coverage, field availability and update timing are controlled by the upstream public source.
- Optional fields can be null or absent when the source does not publish them.
- This Actor does not bypass authentication, access controls, CAPTCHAs, or source rate limits.
- Customers remain responsible for lawful use, applicable source terms, and restrictions on downstream decisions.
FAQ
What is the best way to run this CMS healthcare provider search Actor?
Start with the 10-record default, inspect the dataset, then increase max_items and narrow the available filters for your use case.
Do I need my own API key?
No external API key is required unless the Input tab explicitly says otherwise. Apify credentials are used normally when invoking the Actor through Apify APIs or MCP.
Can an AI agent call it?
Yes. The strict input schema acts as the tool signature, and the dataset plus Output schemas describe the returned records.
Can I export the results?
Yes. Apify datasets support JSON, CSV, Excel, XML and API retrieval.
Support and changes
Open an issue on the Actor page with a redacted input and run ID. See ./CHANGELOG.md for contract and maintenance updates.