# FDA BMIS Clinical Research Entity Search (`quartz_apple_dnx/fda-bmis-clinical-research-entity-search`) Actor

Search FDA's quarterly BMIS archive for clinical investigators, CROs, and IRBs by identifier, name, site, location, type, or receipt date.

- **URL**: https://apify.com/quartz_apple_dnx/fda-bmis-clinical-research-entity-search.md
- **Developed by:** [Piven Core](https://apify.com/quartz_apple_dnx) (community)
- **Categories:** 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 fda bmis source 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

## FDA BMIS Clinical Research Entity Search

Search FDA's quarterly **Bioresearch Monitoring Information System (BMIS)** for clinical investigators, contract research organizations (CROs), and institutional review boards (IRBs).

Use it for **clinical-research data discovery, FDA submission-reference research, site/investigator research, CRO/IRB lookup, and structured BMIS workflows**.

**Independent tool. Not affiliated with or endorsed by the U.S. Food and Drug Administration (FDA).**

### Common use cases

- Find BMIS rows by FDA reviewer/investigator identifier
- Search investigator names
- Search study sites / organizations
- Filter clinical investigators, CROs, or IRBs
- Filter by city, state, country, or FDA receipt date
- Export structured BMIS data without manually downloading and parsing FDA's quarterly archive

### What you get

Each billable row preserves one FDA BMIS source entry and can include:

- BMIS investigator/reviewer identifier
- surname, first name, middle initial, and convenient full name
- rank/title and degree
- site / organization
- street address
- city, state/region, postal code, country
- FDA receipt date
- entity type
- exact applied search
- source archive/file provenance and capture timestamp

FDA can list the same person or organization multiple times because a new source row is created when it is referenced in another qualifying submission. **V1 intentionally preserves those repeated source rows.**

### Try it

```json
{
  "investigatorNumber": "708594",
  "receiptDateFrom": "2017-10-31",
  "receiptDateTo": "2017-10-31",
  "maxRows": 1
}
```

The current quarterly FDA archive resolves that fixture to **JIHAD ABBAS — Toledo, OH — CI — receipt date 2017-10-31**.

### Pricing

Only successfully saved BMIS source rows are billed. Legitimate zero-result and budget-limit summary rows are free. Source/download failures remain failures.

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

Public release is a separate decision.

### Source / provenance

FDA BMIS information page:

`https://www.fda.gov/drugs/drug-approvals-and-databases/bioresearch-monitoring-information-system-bmis`

Current quarterly archive:

`https://www.fda.gov/media/189929/download?attachment=`

The 2026-08-31 archive verified during the source gate contains roughly **1.86 million structurally valid rows** in a tilde-delimited text file.

The Actor streams the archive rather than loading the 239 MB decompressed text file into memory.

### Source conventions

FDA uses `NG` for some unavailable/not-given values; the Actor exposes those as null.

FDA documents `01-JAN-1900` as an invalid/missing date convention; the Actor exposes that receipt date as null.

The original source type is preserved as `sourceEntityType`. Common documented types CI, CRO, and IRB are normalized directly; unexpected source codes are exposed as `entityType=OTHER` rather than guessed.

### Important limitations

BMIS is **not a comprehensive list of everyone participating in clinical research**.

Presence in BMIS does not mean FDA approval, endorsement, inspection, compliance, professional quality, or suitability. Absence does not establish the opposite.

This Actor does not:

- confirm that a name belongs to a particular real-world person;
- make employment, credentialing, insurance, credit, housing, immigration, or other high-impact eligibility decisions;
- create a risk/compliance score;
- deduplicate separate FDA submission references;
- provide medical or legal advice.

Verify identity and relevant official FDA records before acting on BMIS information.

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

## `investigatorNumber` (type: `string`):

Optional exact BMIS INVN identifier. Store prefill uses 708594.

## `nameQuery` (type: `string`):

Optional case-insensitive contains search across BMIS first, middle, and surname fields.

## `site` (type: `string`):

Optional case-insensitive contains search on the BMIS SITE field.

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

Optional city contains search.

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

Optional exact BMIS state code such as OH, TX, or FL.

## `country` (type: `string`):

Optional exact BMIS country code such as USA, MEX, or NLD.

## `entityType` (type: `string`):

Optional FDA BMIS type: CI (clinical investigator), CRO, or IRB.

## `receiptDateFrom` (type: `string`):

Optional earliest FDA receipt date in YYYY-MM-DD format. Store prefill narrows the fixture to 2017-10-31.

## `receiptDateTo` (type: `string`):

Optional latest FDA receipt date in YYYY-MM-DD format. Store prefill narrows the fixture to 2017-10-31.

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

Hard cap on saved billable BMIS source rows.

## Actor input object example

```json
{
  "investigatorNumber": "708594",
  "receiptDateFrom": "2017-10-31",
  "receiptDateTo": "2017-10-31",
  "maxRows": 1
}
```

# 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 = {
    "investigatorNumber": "708594",
    "receiptDateFrom": "2017-10-31",
    "receiptDateTo": "2017-10-31",
    "maxRows": 1
};

// Run the Actor and wait for it to finish
const run = await client.actor("quartz_apple_dnx/fda-bmis-clinical-research-entity-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 = {
    "investigatorNumber": "708594",
    "receiptDateFrom": "2017-10-31",
    "receiptDateTo": "2017-10-31",
    "maxRows": 1,
}

# Run the Actor and wait for it to finish
run = client.actor("quartz_apple_dnx/fda-bmis-clinical-research-entity-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 '{
  "investigatorNumber": "708594",
  "receiptDateFrom": "2017-10-31",
  "receiptDateTo": "2017-10-31",
  "maxRows": 1
}' |
apify call quartz_apple_dnx/fda-bmis-clinical-research-entity-search --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,quartz_apple_dnx/fda-bmis-clinical-research-entity-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/14OTGW8g4NUdmwVCe/builds/mLVLSPj0BmsS5ox5b/openapi.json