# CMS Hospital Owners & Control Scraper API (`pink_comic/cms-hospital-owners-control`) Actor

Search CMS Hospital All Owners enrollment associations for ownership and operational/managerial-control evidence. Filter hospitals, owners, roles, percentages, dates, states, and classifications with source-linked caveats. Distinct from CHOW transactions.

- **URL**: https://apify.com/pink\_comic/cms-hospital-owners-control.md
- **Developed by:** [Ava Torres](https://apify.com/pink_comic) (community)
- **Categories:** Lead generation, Business, Automation
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $2.00 / 1,000 cms hospital owners & control scraper api evidence items

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

Learn more: https://docs.apify.com/platform/actors/running/actors-in-store#pay-per-event

## What's an Apify Actor?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.
Actors are written with capital "A".

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

## CMS Hospital Owners & Operational Control Scraper API

Search CMS **Hospital All Owners** enrollment associations by hospital, owner, role, geography, ownership percentage, date, and organization classification. Each paid row preserves the source identifiers, names, role, address, percentage, association date, classification flags, exact query URL, retrieval time, and bounded-query disclosure.

### Deterministic first run

```json
{"enrollmentId":"O20020812000015","maxCandidates":25,"maxResults":5}
```

This returns up to five current dataset associations for **SOUTHERN TENNESSEE MEDICAL CENTER LLC**, including Lifepoint ownership and/or operational/managerial-control evidence. Maximum default charge: **$0.0101** ($0.0001 start + up to 5 × $0.002 items).

### Filter examples

```json
{"hospitalName":"SOUTHERN TENNESSEE","ownerName":"LIFEPOINT","role":"CONTROL","state":"TN","maxCandidates":500,"maxResults":10}
```

Supported fields include `enrollmentId`, `associateId`, `hospitalName`, `ownerName`, `ownerType` (`I`/`O`), `role`, owner-address `state`, percentage range, association-date range, classification flags, sort, `maxCandidates`, and total `maxResults`. Exact IDs/type/state are sent to CMS server-side; text/range/classification filters run over the explicitly bounded candidate set.

### Evidence boundaries

This is CMS enrollment ownership-association evidence from dataset `029c119f-f79c-49be-9100-344d31d10344`, not Change of Ownership (CHOW) transaction data. CMS records can lag or change. They do not verify beneficial ownership, complete corporate lineage, legal title, licensure, good standing, or current control. Blank values remain blank and are never inferred. `NO_MATCH` means no row met the filters within the disclosed bounded query; it does not prove absence. `SOURCE_UNAVAILABLE` means CMS could not be read after bounded retries.

# Actor input Schema

## `enrollmentId` (type: `string`):

Exact CMS enrollment identifier.

## `associateId` (type: `string`):

Exact hospital associate identifier.

## `hospitalName` (type: `string`):

Case-insensitive hospital organization name substring.

## `ownerName` (type: `string`):

Case-insensitive individual or organization owner name substring.

## `ownerType` (type: `string`):

CMS owner type: individual (I), organization (O), or all.

## `role` (type: `string`):

Owner role code or role text substring.

## `state` (type: `string`):

Two-letter owner address state.

## `associationDateFrom` (type: `string`):

Earliest association date, YYYY-MM-DD.

## `associationDateTo` (type: `string`):

Latest association date, YYYY-MM-DD.

## `sortBy` (type: `string`):

Deterministic result sort.

## `minOwnershipPercentage` (type: `number`):

Minimum source-reported ownership percentage, 0-100.

## `maxOwnershipPercentage` (type: `number`):

Maximum source-reported ownership percentage, 0-100.

## `organizationClassifications` (type: `array`):

Require each selected CMS owner-classification flag to equal Y. Blank is not inferred as false.

## `maxCandidates` (type: `integer`):

Maximum CMS source rows scanned before local filters; bounds every query.

## `maxResults` (type: `integer`):

Total paid rows returned. Default five costs at most $0.0101 including start.

## Actor input object example

```json
{
  "enrollmentId": "O20020812000015",
  "associateId": "",
  "hospitalName": "",
  "ownerName": "",
  "ownerType": "",
  "role": "",
  "state": "",
  "associationDateFrom": "",
  "associationDateTo": "",
  "sortBy": "associate_id",
  "organizationClassifications": [],
  "maxCandidates": 25,
  "maxResults": 5
}
```

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {};

// Run the Actor and wait for it to finish
const run = await client.actor("pink_comic/cms-hospital-owners-control").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = {}

# Run the Actor and wait for it to finish
run = client.actor("pink_comic/cms-hospital-owners-control").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{}' |
apify call pink_comic/cms-hospital-owners-control --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,pink_comic/cms-hospital-owners-control"
        }
    }
}

```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/NEKYkz7TFnx4XvwXI/builds/Lv1JsR5ltzdVCthui/openapi.json