# CMS Hospital Price Transparency Enforcement Search (`quartz_apple_dnx/cms-hospital-price-transparency-enforcement`) Actor

Search CMS-published Hospital Price Transparency compliance-review actions by case ID, hospital, state, city, action, or action date. Returns factual source-linked records.

- **URL**: https://apify.com/quartz_apple_dnx/cms-hospital-price-transparency-enforcement.md
- **Developed by:** [Piven Core](https://apify.com/quartz_apple_dnx) (community)
- **Categories:** Business, Developer tools
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

$0.25 / 1,000 cms hospital price-transparency enforcement rows

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/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
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.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

## 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.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

## CMS Hospital Price Transparency Enforcement Search — Official Outcomes

Search official CMS **Hospital Price Transparency Enforcement Activities and Outcomes** without manually navigating the CMS data portal.

Use it for **hospital compliance-review research, regulatory monitoring, healthcare-market intelligence, journalism, consulting, and structured CMS data pipelines**.

**Independent tool. Not affiliated with or endorsed by the Centers for Medicare & Medicaid Services (CMS) or HHS.**

### Common use cases

- Look up an exact CMS enforcement case ID
- Search enforcement history by hospital/location name
- Filter CMS actions by state or city
- Find action types such as Warning Notice
- Restrict results to an action-date range
- Export a bounded structured dataset with source provenance

### What you get

Each billable row represents one CMS-published action following a Hospital Price Transparency compliance review and includes:

- CMS case ID
- hospital or hospital-location name
- address
- city and state
- CMS-published action/outcome
- deterministic normalized action category
- action date
- exact applied search
- CMS dataset identifier and request URL
- capture timestamp

### Try it

```json
{
  "caseId": "1",
  "maxRows": 25
}
```

The current CMS dataset resolves case 1 to **Arkansas Heart Hospital** and returns its published enforcement lifecycle: **Warning Notice** (2021-05-18), **CAP Request** (2021-10-27), and **Closure Notice** (2022-05-25). The production gate rechecks this fixture live before release.

### Input

Filter by:

- exact CMS case ID
- hospital/location name contains
- exact state code
- city contains
- action/outcome contains
- action-date range
- maximum saved rows, 1–5,000

Leave search fields blank to browse the current CMS-published dataset.

### Pricing

Only successfully saved enforcement rows are billed. Legitimate zero-result and budget-limit summary rows are non-billed. Source/API failures remain failures.

Private candidate target: **$0.25 per 1,000 enforcement rows**, subject to the live economics benchmark and final Store market recheck.

Public release is a separate decision.

### Source / provenance

Dataset series:

`6a3aa708-3c9d-411a-a1a4-e046d3ade7ef`

Latest-data API:

`https://data.cms.gov/data-api/v1/dataset/6a3aa708-3c9d-411a-a1a4-e046d3ade7ef/data`

CMS publishes the series as public government data and describes it as information on actions taken after Hospital Price Transparency compliance reviews.

### Important limitations

This Actor reports **historical CMS-published actions**. CMS states that the dataset may not reflect every enforcement activity and that an action is relevant as of the date it occurred.

A Warning Notice, closure, corrective-action event, monetary penalty, or other historical record must **not** be interpreted as proof of a hospital's current compliance or noncompliance.

Likewise, absence from this dataset or from a filtered result is not a compliance determination.

The Actor does not:

- provide legal or regulatory advice;
- predict future enforcement;
- create a compliance or risk score;
- determine whether a hospital currently satisfies 45 CFR Part 180.

### About Piven Core

Built and maintained by **Piven Core** — focused data APIs and automation utilities for reliable, production-ready workflows.

Learn more: https://pivencore.com

# Actor input Schema

## `caseId` (type: `string`):

Optional exact CMS case ID. Store prefill uses case 1.

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

Optional case-insensitive contains search on CMS hospital/location name.

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

Optional exact 2-letter state or territory code.

## `city` (type: `string`):

Optional case-insensitive contains search on city.

## `action` (type: `string`):

Optional case-insensitive contains search on the CMS-published action/outcome text, such as Warning Notice.

## `actionDateFrom` (type: `string`):

Optional earliest CMS action date in YYYY-MM-DD format.

## `actionDateTo` (type: `string`):

Optional latest CMS action date in YYYY-MM-DD format.

## `maxRows` (type: `integer`):

Hard cap on saved billable enforcement rows.

## Actor input object example

```json
{
  "caseId": "1",
  "maxRows": 25
}
```

# Actor output Schema

## `results` (type: `string`):

No description

## `summary` (type: `string`):

No description

# 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 = {
    "caseId": "1",
    "maxRows": 25
};

// Run the Actor and wait for it to finish
const run = await client.actor("quartz_apple_dnx/cms-hospital-price-transparency-enforcement").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 = {
    "caseId": "1",
    "maxRows": 25,
}

# Run the Actor and wait for it to finish
run = client.actor("quartz_apple_dnx/cms-hospital-price-transparency-enforcement").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 '{
  "caseId": "1",
  "maxRows": 25
}' |
apify call quartz_apple_dnx/cms-hospital-price-transparency-enforcement --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,quartz_apple_dnx/cms-hospital-price-transparency-enforcement"
        }
    }
}
```

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/zNMV9OwUazeZMMe8Z/builds/R1QKjDImS0pRqEWqO/openapi.json