# WA Health Care Professional Licenses & Credentials (`j0401/wa-professional-licenses`) Actor

Washington health-care provider credentials (2.45M, WA Dept of Health): nurses, physicians & surgeons, physician assistants, pharmacists, counselors, EMTs. Verify active licenses, screen for regulatory action (actionTaken / revoked), or analyze the workforce. Defaults to ~556k active.

- **URL**: https://apify.com/j0401/wa-professional-licenses.md
- **Developed by:** [Wenhao Yang](https://apify.com/j0401) (community)
- **Categories:** Business
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

$1.00 / 1,000 wa professional license records

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?

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

## WA Health Care Professional Licenses (`wa-professional-licenses`)

Pull **Washington health-care provider credentials** - **2.45 million records from the WA Department of Health** (free public open data), covering **every credential DOH has issued**: registered nurses (RN), licensed practical nurses (LPN), nursing assistants (CNA), **physicians & surgeons**, physician assistants, pharmacists, counselors, EMTs, dentists, and dozens more - including the full historical record, not just who's active today.

This is the public record behind the DOH's license lookup, packaged for **verification and screening**: does this person hold an active license? Has regulatory action been taken against a credential? How big is WA's nursing workforce?

Built for **employers and staffing firms verifying licenses, credentialing and compliance teams, healthcare recruiters, insurers, regulators, researchers and market-intelligence users**.

### What this data is

Each record is **one credential**:

| Field | Meaning |
|---|---|
| `credentialType` | e.g. `Registered Nurse License`, `Physician And Surgeon License`, `Physician Assistant License`, `Pharmacist License`, `Counselor Registration`, `Emergency Medical Technician Certification` |
| `status` | `Active` / `Expired` / `Suspended` / `Revoked` / `Terminated` / `Pending`... |
| `lastName` / `firstName` | License holder |
| `credentialNumber` | e.g. `RN.RN.61687583.MSL` |
| `birthYear` | Holder's birth year |
| `firstIssued` / `lastIssued` / `expiration` | Issuance and expiry dates |
| `actionTaken` | `Yes` / `Pending` / `No` - regulatory action against the license |

> **Note on status**: the corpus is the *full history* (1.5M expired records). The tool **defaults to `Active`** (~556k live licenses) - the useful slice. Set `status=all` to search everything, or filter to a specific state like `Revoked` or `Suspended`.

### Typical questions it answers

- **Is this nurse's license active?** - `name=Miller` + `credentialType=Registered Nurse` (defaults Active).
- **Physicians with regulatory action** - `credentialType=Physician And Surgeon` + `actionTaken=Yes`, or `status=Revoked`.
- **Has this credential number been sanctioned?** - `credentialNumber=...` + `status=all`.
- **How big is WA's active nursing workforce?** - aggregate by `credentialType` -> RN 107k, CNA 59k, physicians 31k active.
- **Workforce / license-status mix** - aggregate by `status` -> Active vs Expired vs Suspended.

### Aggregate mode

Turn on **`aggregate`** and it rolls up counts over the **whole 2.45M-record corpus instantly**:

| Output field | Meaning |
|---|---|
| `key` | The credential type or status |
| `credentials` | Number of records in that group |
| `pctOfTotal` | Share of the (filtered) total |

Group by `credentialType` (the workforce mix) or `status` (how many are active / under action).

### Inputs (all optional)

| Input | What it does |
|---|---|
| `credentialType` | Substring on type: `Registered Nurse`, `Physician And Surgeon`, `Counselor`... |
| `status` | Substring on status. **Default `Active`**; `all` = full history |
| `name` / `lastName` / `firstName` | Holder name (substring) |
| `credentialNumber` | Credential number (substring ok) |
| `actionTaken` | `Yes` / `No` / `Pending` - regulatory action |
| `aggregate` + `groupBy` | Roll up by `credentialType` / `status` -> credentials + share |
| `maxResults` | Cap records (default 200) |

### Low cost

**From $0.001 per record** - with a per-run charge cap so even a full-corpus aggregate can't surprise-bill.

The credential corpus is **2.45 million rows** - every credential the state has issued, active or long-expired. The subtle part is **status semantics**: WA's own status values nest inside each other (`Active`, `Inactive`, `Retired Active`, `Expired - Active MSL`), so a naive "active" text match quietly pulls in ~12k credentials that are anything but active. We match the source's exact status vocabulary instead of substring-guessing, so an "active nurses in WA" query returns active nurses - and the profile fields (credential number, status, expiry) carry the real granularity behind the count.

### Data source & freshness

- **Source**: [data.wa.gov - WA Health Care Provider Credential](https://data.wa.gov/) (`qxh8-f4bd`, Socrata SODA API, free public, no login). The same public data DOH's license lookup shows.
- **Update cadence**: refreshed as DOH issues / renews / sanctions credentials.
- **Coverage**: DOH-regulated health-care professions in Washington state.

# Actor input Schema

## `credentialType` (type: `string`):

Only credentials of this type (substring, case-insensitive). E.g. "Registered Nurse", "Physician And Surgeon", "Physician Assistant", "Pharmacist", "Counselor", "EMT".

## `status` (type: `string`):

Only credentials whose status contains this (substring). Default "Active" (the ~556k live licenses). Set to "all" for the full historical record, or use e.g. "Revoked", "Suspended", "Expired", "Pending".

## `name` (type: `string`):

License holder's last or first name (substring). E.g. "Allen" or "Miller".

## `lastName` (type: `string`):

License holder's last name (substring).

## `firstName` (type: `string`):

License holder's first name (substring).

## `credentialNumber` (type: `string`):

Exact credential number (substring ok), e.g. "MD.MD.00024759" or "RN.RN.61687583.MSL".

## `actionTaken` (type: `string`):

Only credentials with this regulatory-action flag. Yes = action taken against the license (17k records). Screening flag for verification.

## `aggregate` (type: `boolean`):

When on, returns one summary record per group (see groupBy) with credential count and share — instead of individual licenses.

## `groupBy` (type: `string`):

Which dimension to aggregate over. credentialType -> the workforce mix (RNs vs physicians vs pharmacists); status -> how many are active/expired/suspended.

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

Cap the number of records pushed (0 = up to ~10k per run; each record is metered individually, so there is no per-run charge cap). An aggregate over all 2.45M has at most a few hundred groups.

## Actor input object example

```json
{
  "status": "Active",
  "aggregate": false,
  "groupBy": "credentialType",
  "maxResults": 50
}
```

# Actor output Schema

## `recordsUrl` (type: `string`):

Washington health-care provider credentials or aggregates - as JSON

## `datasetUrl` (type: `string`):

No description

## `runUrl` (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 = {};

// Run the Actor and wait for it to finish
const run = await client.actor("j0401/wa-professional-licenses").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("j0401/wa-professional-licenses").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 j0401/wa-professional-licenses --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,j0401/wa-professional-licenses"
        }
    }
}
```

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/jzL65rdhGf2ucCDWq/builds/n9756LAYsVhyVdGEj/openapi.json