# TX Medical Board Licenses - Physicians, PAs & Allied (`j0401/tx-tmb-licenses`) Actor

Texas Medical Board licenses (public open data, 511k records, refreshed daily): the state's physician register (185,801 Physician Licenses) plus physician assistants, residents, radiologic technologists and more. Name, license number, degree, status, discipline, board action and practice address.

- **URL**: https://apify.com/j0401/tx-tmb-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

from $0.06 / 1,000 tx medical 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.
Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have.

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

## TX Medical Board Licenses - Physicians, PAs & the Allied Register

The Texas Medical Board publishes its **entire licensure file** - every license the board has ever issued, refreshed daily - as open data. This actor turns that file into a **charged-per-record physician and practitioner lookup**.

**Built for:** hospital and clinic credentialing (verify a physician's live license and any board action before granting privileges), healthcare staffing and locum agencies, malpractice and payer credentialing teams, medical-device and pharma sales territory work, and workforce analysis of Texas medicine.

### What it covers

**511,438 licenses**, refreshed ~daily. This is the *whole board*, not only doctors - the file spans the board's full credential vocabulary:

| License lane | Records |
|---|---|
| Physician License | 185,801 |
| Physician-in-Training Permit (residents) | 103,587 |
| Physician Full Temporary License | 44,021 |
| Medical Radiologic Technologist (General) | 42,075 |
| Institutional Permit | 29,288 |
| Respiratory Care Practitioner | 24,063 |
| Physician Assistant License | 20,744 |
| Radiologic Technologist / Acupuncturist / Medical Physicist / Surgical Assistant / ... | the long tail |

The **physician lane is the headline**: 185,801 licenses, one row per license number, no duplicates. Of those, **168,306 are MDs and 17,476 are DOs**.

Each record carries the practitioner's identity and the license's own terms:

- **license number** (e.g. `C2582`, `W8893`) and the **license type**
- **degree** (MD / DO / PA / PIT / MRT / RCP / ...) and year of birth
- **registration status** and its date - the board's own vocabulary
- **disciplinary status** and the **live board action**: 7,850 physician rows carry a current board-action date and the order's text (`current_board_action_description`)
- **practice address, city, state and ZIP** - 90.8% of physician rows carry a street address, 85% a city

The physician line-up is Texas-weighted but not Texas-only: Houston (15,610 active), Dallas (9,304), San Antonio (6,700), Austin (5,143), Fort Worth (3,110) - and out-of-state physicians who hold Texas licenses.

### The board's own live flag

`currently_licensed` is the board's Y/N stamp - **201,396 records are live right now**, 112,800 of them physicians. `active` mode hands you that slice; `activeOnly` filters any other query the same way.

The trap is the *other* status column. `registration_status` looks like the status field until you read its values: the board spells the same non-renewal state **four different ways** (`CANC NON-RENEWAL`, `CANCELLED FOR NONRENEWAL`, `CANCELLED NON-RENEWAL`, `CANCELLED,DID NOT RENEW`), and the file mixes the whole board's permits into one `registration_status` vocabulary. Filtering it with a substring silently returns the wrong set. This actor matches the exact vocabulary and uses the board's `currently_licensed` flag for the live slice, which agrees with `registration_status='ACTIVE'` to the row on the physician lane (107,690 = 107,690).

### Typical questions

- "Is **license `C2582`** live, and is there any **board action** against it?"
- "Every **actively licensed physician** in **Houston**."
- "All **physicians with a current board action** - the disciplinary pipeline."
- "**Physician Assistants** licensed in Texas."
- "Who is licensed under **degree DO** in Austin?"
- "**Renewal pipeline**: every physician license expiring in 2026."
- "Aggregate the register by **license type**, **degree**, **status**, or **practice state**."

### Inputs

| Input | What it does |
|---|---|
| `mode` | `active` (live slice, default) / `rows` (any license) / `aggregate` |
| `licenseType` | a lane: `physician` / `physician assistant` / `resident` / `radiologic technologist` / ... |
| `degree` | exact code: MD / DO / PA / PIT / MRT / RCP / ... |
| `status` | the board's registration status, exact |
| `discipline` | NONE / SEE PREVIOUS ORDER / UNDER BOARD ORDER / SUSPENDED BY BOARD / ... |
| `boardActionOnly` | only licenses with a live board-action record |
| `licenseNumber` | exact license number - a full profile lookup |
| `name` / `city` / `state` | holder filters (name & city fuzzy, state exact) |
| `issuedFrom/To`, `expiresFrom/To` | issue and expiration windows |
| `groupBy` | aggregate over licenseType / degree / status / discipline / state / expirationYear |
| `maxResults` | cap records (default 200) |

**Default run = 200 live licenses, most recently issued first** (mode defaults to `active`) - fast for the daily auto-test. For a targeted query add a filter; for a broad view use `aggregate` (a handful of summary rows, not a 511k-row dump).

### Low cost

**From $0.0001 per record** - billed only for the rows you use, at the low end of the store. A credentialing check on one physician, or a whole disciplinary sweep, costs pennies.

The board's file reads like a straightforward export until you try to filter it. **The status field is not one field but two** - a `registration_status` whose vocabulary mixes the board's entire permit system and spells a single non-renewal outcome four ways, sitting beside the `currently_licensed` flag that actually answers "is this person practising". **The discipline story is split across three columns** - a `disciplinary_status` flag, a separate `license_status` carrying licensure actions under board order, and the board-action text itself, which is populated on only 4% of physician rows and is the *only* place an order's substance lives. **The file is the whole board, not the physician register** - a naive "doctors" read drags in residents, radiologic technologists and respiratory therapists, and a `Physician%` prefix quietly merges Physician Licenses with Physician-in-Training permits and temporary lanes. Normalizing all of that into a register where a `licenseType` / `degree` / `discipline` query returns exactly the physicians you mean is the actual product. Every pull is integrity-checked against the file's known shape, so a degraded source fails loudly instead of returning bad rows.

### Source

- [Texas Open Data: Texas Medical Board licenses](https://data.texas.gov/dataset/Texas-Medical-Board/tm3v-pfq9) - the TMB's published licensure file. Reflects the board's record as of each refresh; not a verification of any practitioner's current standing. `specialties` is sparsely published and on no physician rows, so it is carried but never a headline.

# Actor input Schema

## `mode` (type: `string`):

active = currently-licensed records (the board's live flag), the default view. rows = licenses matching your filters, active or not (turn activeOnly on to restrict). aggregate = one count row per group (see groupBy).

## `licenseType` (type: `string`):

A license lane, e.g. 'physician', 'physician assistant', 'pa', 'resident', 'radiologic technologist', 'respiratory', 'acupuncturist', 'surgical assistant'. Blank = every type. 'physician' isolates the 185,801 Physician Licenses (exactly - not the training or temporary lanes).

## `degree` (type: `string`):

Credential code, exact: MD, DO, PA, PIT (resident), MRT, RCP, ... Blank = any.

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

The board's registration status, exact (49 values): ACTIVE, DECEASED, TEXAS RETIRED, CANCELLED BY REQUEST, EXPIRED, NOT ACTIVE, TEMPORARILY SUSPENDED, DELINQUENT, RENEWAL, ... Blank = any.

## `discipline` (type: `string`):

The board's discipline flag, exact: NONE, SEE PREVIOUS ORDER, UNDER BOARD ORDER, SUSPENDED BY BOARD, CANCELLED BY BOARD, COMPLAINT DISMISSED, ... Blank = any.

## `boardActionOnly` (type: `boolean`):

When on, returns only licenses carrying a live board-action record (a disciplinary order text). The physician lane carries 7,850 such rows.

## `licenseNumber` (type: `string`):

Exact license number, e.g. 'C2582' or 'W8893' - a full profile lookup.

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

License holder name (fuzzy), matched against first or last name, e.g. 'SMITH'.

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

Practice-address city (fuzzy). Physicians carry a ~85% populated practice city.

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

Two-letter practice state (e.g. TX).

## `activeOnly` (type: `boolean`):

When on, returns only records the board flags as currently licensed. Tip: mode=active is the shortcut that turns this on.

## `issuedFrom` (type: `string`):

Only licenses issued on/after this date (YYYY-MM-DD).

## `issuedTo` (type: `string`):

Only licenses issued before this date.

## `expiresFrom` (type: `string`):

Only licenses expiring on/after this date - e.g. a renewal pipeline.

## `expiresTo` (type: `string`):

Only licenses expiring before this date.

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

Which dimension to aggregate over. licenseType -> the credential mix; degree -> MD vs DO vs PA; status -> how many are active vs lapsed; discipline -> the board-action mix; state -> where physicians practise; expirationYear -> renewal volume ahead.

## `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 has at most a few hundred groups.

## Actor input object example

```json
{
  "mode": "active",
  "licenseType": "",
  "degree": "",
  "status": "",
  "discipline": "",
  "boardActionOnly": false,
  "licenseNumber": "",
  "name": "",
  "city": "",
  "state": "",
  "activeOnly": false,
  "issuedFrom": "",
  "issuedTo": "",
  "expiresFrom": "",
  "expiresTo": "",
  "groupBy": "licenseType",
  "maxResults": 50
}
```

# Actor output Schema

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

Texas medical license records 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/tx-tmb-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/tx-tmb-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/tx-tmb-licenses --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,j0401/tx-tmb-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/gDgER6ev6xlNjQzHE/builds/RAlEZINh719BOEeP3/openapi.json