# BIG-register Verification - Dutch Healthcare Practitioners (`dariomory/big-register-verification-scraper`) Actor

Verify Dutch BIG-register healthcare practitioner registrations by BIG number or surname, including profession, specialisms, limitations, and registration status.

- **URL**: https://apify.com/dariomory/big-register-verification-scraper.md
- **Developed by:** [Dario Mory](https://apify.com/dariomory) (community)
- **Categories:** Automation
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $15.00 / 1,000 practitioner verifications

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/platform/actors/running/actors-in-store#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

## BIG-register Verification — Dutch Healthcare Practitioners

Verify whether a Dutch healthcare practitioner is registered in the **BIG-register**, the statutory register maintained by the Ministry of Health under the Wet BIG.

Employers, staffing agencies, and healthcare institutions are legally required to check BIG registration before someone practises a protected profession, and to re-check it periodically. This Actor turns that check into a batch operation.

### What it does

Give it BIG numbers or surnames. For each match it returns the practitioner's registration status, profession, specialisms, any practice limitations, and any disciplinary rulings.

| Field | Description |
|---|---|
| `registrationNumber` | The 11-digit BIG number |
| `mailingName`, `lastName` | Name as published in the register |
| `professionalGroup` | Resolved profession, e.g. `Arts`, `Verpleegkundige`, `Apotheker` |
| `isRegistered` | **The answer** — true only when the entry is neither ended nor struck off |
| `strikedOut` | Struck from the register |
| `registrationEnded` | Registration lapsed |
| `specialisms` | Registered specialisms |
| `limitations` | Restrictions on the practitioner's practice |
| `judgmentProvisions` | Disciplinary rulings recorded against the registration |
| `profileUrl` | Link back to the official register entry |

### Input

| Option | Description |
|---|---|
| `bigNumbers` | 11-digit BIG numbers to verify. Most reliable — one number identifies one practitioner. |
| `names` | Surnames to look up |
| `professionalGroup` | Restrict surname searches to one of 31 professions |
| `maxResultsPerName` | Cap on practitioners verified per surname |

**On surnames:** the register refuses overly broad searches rather than truncating them — a common surname alone returns nothing useful. Always pair a surname with a profession, or search by BIG number. When a search is refused, the Actor logs a warning naming the query instead of failing the run.

### Notes on cost and scope

Two lightweight JSON requests per practitioner, no browser and no proxy.

This Actor is built for **verification, not bulk extraction**. It looks up practitioners you already have a reason to check — a job applicant, a contracted locum, a staff roster. It deliberately does not enumerate the register, and the register's own API does not permit it: broad queries are rejected outright.

### Data protection

The BIG-register is a public statutory register and these fields are published by law so that employers and patients can verify practitioners. The records nonetheless describe identified individuals and include disciplinary information, so they are personal data under the GDPR. Use them for the purpose the register exists for — verifying professional registration — and retain only what that purpose requires.

### Output example

```json
{
  "registrationNumber": "29928279301",
  "mailingName": "A.A.J.H. Zwanenburg",
  "professionalGroup": "Arts",
  "isRegistered": true,
  "strikedOut": false,
  "registrationEnded": false,
  "specialisms": [],
  "limitations": [],
  "judgmentProvisions": [],
  "profileUrl": "https://zoeken.bigregister.nl/zoeken/bignummer?number=29928279301"
}
```

# Actor input Schema

## `bigNumbers` (type: `array`):

11-digit BIG registration numbers to verify, for example 29928279301.

## `names` (type: `array`):

Surnames to look up. A surname matching too many practitioners is rejected by the register; add a profession to narrow it.

## `professionalGroup` (type: `string`):

Restrict surname searches to one profession. Strongly recommended for common surnames.

## `maxResultsPerName` (type: `integer`):

Caps how many practitioners are verified per surname search.

## Actor input object example

```json
{
  "bigNumbers": [
    "29928279301"
  ],
  "names": [],
  "maxResultsPerName": 25
}
```

# Actor output Schema

## `results` (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 = {
    "bigNumbers": [
        "29928279301"
    ],
    "names": []
};

// Run the Actor and wait for it to finish
const run = await client.actor("dariomory/big-register-verification-scraper").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 = {
    "bigNumbers": ["29928279301"],
    "names": [],
}

# Run the Actor and wait for it to finish
run = client.actor("dariomory/big-register-verification-scraper").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 '{
  "bigNumbers": [
    "29928279301"
  ],
  "names": []
}' |
apify call dariomory/big-register-verification-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,dariomory/big-register-verification-scraper"
        }
    }
}

```

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/WLSeu7tVT3hezfngB/builds/MmjFbcZr56QwlutGb/openapi.json