# CMS Hospice Ownership Scraper API - Owners & Control (`pink_comic/cms-hospice-ownership-control-scraper`) Actor

Search CMS Hospice All Owners by enrollment, hospice organization, owner, role, type, and association date. Groups source owner rows into source-linked hospice enrollment items for provider-data research, ownership QA, and control-association review.

- **URL**: https://apify.com/pink\_comic/cms-hospice-ownership-control-scraper.md
- **Developed by:** [Ava Torres](https://apify.com/pink_comic) (community)
- **Categories:** Lead generation, Business, AI
- **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 hospice ownership scraper api - owners & contr 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 Hospice Ownership Scraper API - Owners & Control

Search the official **CMS Hospice All Owners** quarterly snapshot for provider-data research, hospice ownership QA, and review of source-reported ownership/control associations. The actor groups multiple owner rows into one paid hospice-enrollment item.

No API key, login, browser, or proxy is required.

### Search fields

- enrollment ID or hospice associate ID
- exact hospice organization name
- owner associate ID or source-published person/organization owner name
- owner type: individual or organization
- role code or role text (including managing-employee and operational/managerial-control associations)
- association date

`maxCandidates` bounds source owner rows. `maxResults` caps grouped enrollment items, not individual nested owners.

### Deterministic default

```json
{
  "organizationName": "HOSPITAL DISTRICT NO 1 OF DICKINSON COUNTY KANSAS",
  "maxCandidates": 1000,
  "maxResults": 1
}
```

This returns one enrollment item containing the current snapshot's source-reported owners/control associations. The bounded first run costs at most **$0.0021**: $0.0001 actor start plus one $0.002 dataset item.

### Other examples

```json
{"enrollmentId":"O20020813000008","maxResults":1}
```

```json
{"ownerType":"O","ownerRoleCode":"43","maxCandidates":1000,"maxResults":25}
```

```json
{"ownerName":"SALINA REGIONAL HEALTH CENTER","maxCandidates":1000,"maxResults":10}
```

### Output

Each found item includes hospice enrollment/associate identifiers, organization name, a deterministic nested `owners` array, owner count, source snapshot date, retrieval time, official dataset/API/query URLs, candidate-bound disclosure, coverage note, and interpretation caveat. Nested owner fields preserve source-published role, association date, percentage, organization/person professional name fields, address, entity-type indicators, and selected ownership classifications.

`NO_MATCH` and `SOURCE_UNAVAILABLE` are explicit evidence items rather than silent empty datasets (subject to the buyer's total charge cap).

### Evidence boundaries

CMS enrollment ownership/control associations are administrative snapshot evidence. They are **not**:

- a complete beneficial-ownership map;
- proof of current ownership or control after the snapshot date;
- licensure, accreditation, certification, or sanctions clearance;
- identity verification or proof that similar names identify the same person/entity;
- legal advice or a complete due-diligence report.

Individuals may appear in CMS's public data. This actor limits them to source-published professional ownership/control fields and does not enrich them. A missing record does not prove absence, non-enrollment, or lack of another identifier. Confirm consequential decisions with CMS and appropriate regulators.

### Official source

- [CMS Hospice All Owners dataset](https://data.cms.gov/provider-characteristics/hospitals-and-other-facilities/hospice-all-owners)
- Dataset ID: `e983965e-1603-4cb8-82b5-c40090e380d1`
- Current API distribution snapshot title/date: **Hospice All Owners: 2026-04-02**
- CMS catalog modified date: 2026-06-17
- CMS catalog cadence: quarterly

# Actor input Schema

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

Exact CMS hospice enrollment ID.

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

Exact CMS associate ID for the enrolled hospice organization.

## `organizationName` (type: `string`):

Exact source organization name.

## `ownerAssociateId` (type: `string`):

Exact source owner associate ID.

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

Person or organization owner name. Name matching is limited to source-published owner fields.

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

Optional owner type filter or result-control setting. See the README for source semantics and examples.

## `ownerRoleCode` (type: `string`):

Exact source role code, such as 42 or 43.

## `ownerRoleText` (type: `string`):

Exact source role text, such as OPERATIONAL/MANAGERIAL CONTROL.

## `associationDate` (type: `string`):

Exact source association date (YYYY-MM-DD).

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

Bound on source owner rows before deterministic enrollment grouping.

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

Total paid enrollment items. Each item can contain multiple owners.

## Actor input object example

```json
{
  "organizationName": "HOSPITAL DISTRICT NO 1 OF DICKINSON COUNTY KANSAS",
  "ownerType": "",
  "maxCandidates": 1000,
  "maxResults": 1
}
```

# 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 = {
    "organizationName": "HOSPITAL DISTRICT NO 1 OF DICKINSON COUNTY KANSAS",
    "maxCandidates": 1000,
    "maxResults": 1
};

// Run the Actor and wait for it to finish
const run = await client.actor("pink_comic/cms-hospice-ownership-control-scraper").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 = {
    "organizationName": "HOSPITAL DISTRICT NO 1 OF DICKINSON COUNTY KANSAS",
    "maxCandidates": 1000,
    "maxResults": 1,
}

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

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

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

```

## CLI example

```bash
echo '{
  "organizationName": "HOSPITAL DISTRICT NO 1 OF DICKINSON COUNTY KANSAS",
  "maxCandidates": 1000,
  "maxResults": 1
}' |
apify call pink_comic/cms-hospice-ownership-control-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "command": "npx",
            "args": [
                "mcp-remote",
                "https://mcp.apify.com/?tools=pink_comic/cms-hospice-ownership-control-scraper",
                "--header",
                "Authorization: Bearer <YOUR_API_TOKEN>"
            ]
        }
    }
}

```

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/48LeN3wgyujd2CsJc/builds/dBcdk5GuVH3M1Lu5U/openapi.json