# CMS NPI Organization Search - Hospitals Clinics & Providers (`zhucl1006/nppes-org-provider-search`) Actor

Search CMS NPPES for organization (NPI-2) providers — hospitals, clinics, FQHCs, home health, dental practices — by state, city, ZIP, taxonomy, or name. Public API, no key required.

- **URL**: https://apify.com/zhucl1006/nppes-org-provider-search.md
- **Developed by:** [leo zhu](https://apify.com/zhucl1006) (community)
- **Categories:** AI, Lead generation, Other
- **Security:** Limited permissions
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $2.00 / 1,000 organization results

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

### What does CMS NPI Organization Search do?

**CMS NPI Organization Search** queries the official [CMS NPPES NPI Registry API](https://npiregistry.cms.hhs.gov/api-page) (version 2.1) for **organization providers (NPI-2)** — hospitals, clinics, FQHCs, home health agencies, dental practices, and other Type 2 NPIs. It is a structured **NPPES API** / **NPI lookup** alternative that returns clean JSON to an Apify dataset.

This Actor defaults to **organizations only** (`enumeration_type=NPI-2`). It does **not** scrape individual clinician (NPI-1) profiles, and it **never** exports authorized official personal names or personal phone numbers.

### Why use this Actor?

Use it to build healthcare lead lists, enrich CRM records, monitor facility footprints by city/state/ZIP, or power analytics on hospital and clinic networks — without downloading multi‑GB NPPES flat files.

**Features**

- Public CMS API — **no API key** and no login
- Organization-only search (NPI-2)
- Filters: **state**, **city**, **postal_code**, **organization_name**, **taxonomy** (preset or custom)
- Taxonomy presets: Hospital, Home Health, FQHC, Dental
- Pagination with polite rate limiting (NPPES max ~1,200 records per query)
- Structured output: NPI, name, status, primary taxonomy, LOCATION address, business phone, dates, NPPES URL
- Privacy-safe: authorized official PII is omitted
- Runs on Apify: scheduling, API, webhooks, integrations, monitoring

### What data can CMS NPI Organization Search extract?

| Field | Type | Description |
| --- | --- | --- |
| `npi` | string | 10-digit National Provider Identifier |
| `name` | string | Organization legal / business name |
| `status` | string | NPPES status (e.g. `A` = Active) |
| `taxonomy` | string | Primary taxonomy description |
| `taxonomy_code` | string | Primary taxonomy code |
| `address` | string | Practice LOCATION street address |
| `city` / `state` / `postal_code` | string | LOCATION city, state, ZIP |
| `phone` | string | Organization business phone (LOCATION) |
| `enumeration_date` | string | Date the NPI was enumerated |
| `last_updated` | string | Last update date in NPPES |
| `nppes_url` | string | Link to the provider in the NPPES registry UI |

### How to search NPPES organizations

1. Open the Actor in [Apify Console](https://console.apify.com) or the Store page.
2. Set a **state** (e.g. `CA`) and a **city** (e.g. `Oakland`), or a ZIP / organization name.
3. Pick a **taxonomy preset** (Hospital / Home Health / FQHC / Dental) or enter a custom taxonomy description.
4. Set **limit** (default `20` for a fast Store auto-test; up to `1200`).
5. Click **Start** and download results as JSON, CSV, Excel, or HTML.

### How much will it cost?

This Actor calls a free public government API. Platform cost is mainly Apify compute. Typical small searches (tens of organizations) finish in seconds on 256–1024 MB. Larger paginated pulls stay under a few minutes. Pay-per-event pricing (if enabled by the publisher) charges per organization result — check the pricing tab on the Store page.

### Input

See the **Input** tab for the full form. Main fields:

- `state` — two-letter abbreviation (default `CA`)
- `city` — practice city (default `Oakland`)
- `postal_code` — ZIP / ZIP+4 (wildcards like `946*` supported by CMS)
- `taxonomy_preset` — `Hospital` | `Home Health` | `FQHC` | `Dental`
- `taxonomy_description` — custom taxonomy text (overrides preset)
- `organization_name` — name search with optional trailing `*`
- `limit` — max records (default `20`, max `1200`)
- `updated_since` — optional ISO date; ignored gracefully if the public API has no update filter

**Note:** NPPES requires more than `enumeration_type` alone (and more than `state` alone). Always combine state with city, ZIP, taxonomy, or organization name.

#### Taxonomy preset mapping

| Preset | NPPES taxonomy_description |
| --- | --- |
| Hospital | General Acute Care Hospital |
| Home Health | Home Health |
| FQHC | Federally Qualified Health Center |
| Dental | Dentist |

### Output

You can download the dataset in JSON, HTML, CSV, or Excel.

Example item:

```json
{
  "npi": "1174705362",
  "name": "INPATIENT CONSULTANTS OF CALIFORNIA, INC.",
  "status": "A",
  "taxonomy": "Hospitalist",
  "taxonomy_code": "208M00000X",
  "address": "350 HAWTHORNE AVE, #2320",
  "city": "OAKLAND",
  "state": "CA",
  "postal_code": "946093108",
  "phone": "510-655-4000",
  "enumeration_date": "2007-11-29",
  "last_updated": "2007-11-29",
  "nppes_url": "https://npiregistry.cms.hhs.gov/provider-view/1174705362"
}
```

### Tips

- Start with a **city + taxonomy preset** for fast, relevant lists.
- Raise `limit` gradually; CMS caps skip at 1000 (about 1200 rows per query shape).
- For nationwide coverage, run multiple Actor tasks by state or ZIP prefix and merge datasets.
- Prefer LOCATION address fields already mapped by this Actor when enriching maps or outreach tools.

### FAQ & disclaimer

#### Is an API key required?

No. The [NPPES Read API](https://npiregistry.cms.hhs.gov/api-page) is public.

#### Does this include individual doctors (NPI-1)?

No. This Actor is scoped to **organizations (NPI-2)** only.

#### Are authorized official names exported?

No. Personal authorized-official name and phone fields from NPPES are intentionally omitted.

#### Source & accuracy

Data comes from CMS NPPES. An NPI does not guarantee that a provider is licensed or credentialed. Always verify critical decisions against primary sources.

> Our Actors are ethical and do not extract private user data beyond what CMS publishes in the public NPPES registry for organizations. Personal authorized-official fields are excluded. You should not process personal data unless you have a legitimate reason. If unsure, consult your counsel. GDPR and other privacy laws may apply depending on your use case.

#### Support

Open an issue on the Actor's **Issues** tab, or call the Actor via the **API** tab for programmatic runs and scheduling.

# Actor input Schema

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

Two-letter US state abbreviation (e.g. CA, NY, TX). Cannot be the only search criterion — combine with city, ZIP, taxonomy, or organization name.

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

City name for the practice LOCATION address (e.g. Oakland).

## `postal_code` (type: `string`):

5-digit ZIP or ZIP+4. Trailing wildcards like 946\* are supported by the NPPES API (min 2 characters before \*).

## `taxonomy_preset` (type: `string`):

Quick taxonomy filter for common organization types. Mapped to NPPES taxonomy descriptions. Ignored if taxonomy_description is set.

## `taxonomy_description` (type: `string`):

Free-text NPPES taxonomy description search (overrides taxonomy_preset). Examples: "General Acute Care Hospital", "Home Health", "Federally Qualified Health Center", "Dentist".

## `organization_name` (type: `string`):

Organization name search. Trailing wildcards allowed (min 2 characters, e.g. Kaiser\*). Matches LBN, DBA, and other name types.

## `limit` (type: `integer`):

Max organization records to return. NPPES allows up to 200 per request and skip up to 1000 (≈1200 total per query). Capped at 1200.

## `updated_since` (type: `string`):

Optional ISO date for incremental sync (e.g. 2024-01-01). The public NPPES Read API v2.1 does not document a last_updated filter — if unsupported, this field is ignored gracefully.

## Actor input object example

```json
{
  "state": "CA",
  "city": "Oakland",
  "taxonomy_preset": "Hospital",
  "limit": 20
}
```

# Actor output Schema

## `organizations` (type: `string`):

Dataset of NPI-2 organization providers matching the search

# 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 = {
    "state": "CA",
    "city": "Oakland",
    "taxonomy_preset": "Hospital",
    "limit": 20
};

// Run the Actor and wait for it to finish
const run = await client.actor("zhucl1006/nppes-org-provider-search").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 = {
    "state": "CA",
    "city": "Oakland",
    "taxonomy_preset": "Hospital",
    "limit": 20,
}

# Run the Actor and wait for it to finish
run = client.actor("zhucl1006/nppes-org-provider-search").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 '{
  "state": "CA",
  "city": "Oakland",
  "taxonomy_preset": "Hospital",
  "limit": 20
}' |
apify call zhucl1006/nppes-org-provider-search --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,zhucl1006/nppes-org-provider-search"
        }
    }
}
```

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/0WFfEIoiEPayhh3lE/builds/IMJuMy4NtbYbQNTAq/openapi.json