# Poland NFZ Waiting Times (`athletic_chill/poland-nfz-waiting-times`) Actor

Returns NFZ-funded care waiting lists in Poland (kolejki, Terminy Leczenia) from the official API: provider, location, people waiting and wait reported. Takes a list of benefit names, with optional province and case type.

- **URL**: https://apify.com/athletic_chill/poland-nfz-waiting-times.md
- **Developed by:** [Serhii Shevchenko](https://apify.com/athletic_chill) (community)
- **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 waiting list 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?

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

## Poland NFZ Waiting Times

See how long the waiting lists are for NFZ-funded care in Poland, without clicking through the Terminy Leczenia site one search at a time. Give it a benefit and a province, and get every matching waiting list as clean data.

Useful for clinic groups comparing public waits in their region, healthcare analysts, journalists and researchers.

### What you get

Each result is one provider's waiting list:

| Field | Meaning |
|---|---|
| `benefit`, `caseType` | Benefit name in Polish, and stable or urgent |
| `provider`, `place` | Provider and unit |
| `address`, `locality`, `county` | Where it is |
| `awaiting`, `removed` | People on the list and people removed, as reported by the provider |
| `averagePeriod`, `reportedMonth` | Average wait in days, and the month those figures refer to |
| `predictedWait` | NFZ's predicted wait, such as `14 dni` |
| `situationAsAt` | Date the NFZ figures refer to |
| `source` | https://api.nfz.gov.pl/ |

### Input example

```json
{
  "benefits": ["ORTOPED", "KARDIOLOG"],
  "province": "07",
  "urgency": "stable",
  "maxRecords": 50
}
```

Each benefit search matches part of the name, so `ORTOPED` finds orthopedic clinics and wards. Give several to cover more in one run: **Maximum records** is shared across them, and a waiting list is returned once even if two searches match it.

### Provider contacts

Phone, email, website, NIP and REGON are left out unless you turn on **Include provider contacts and tax IDs**. Some providers are individual practices, so these fields can be personal data. You're responsible for your own legal basis for using them, and they aren't a mailing list.

### Pricing

You pay per record returned. Set **Maximum records** to control the cost of a run.

### Data source and limits

Data comes from the official NFZ API Terminy Leczenia, https://api.nfz.gov.pl/, and values are passed through unchanged. Figures are reported by providers and can be weeks old, so check `reportedMonth` and `situationAsAt`. This Actor is independent and isn't affiliated with or endorsed by NFZ. It isn't medical advice, and it isn't a way to book care.

Built with Claude, an AI, and tested against the live API.

# Actor input Schema

## `benefits` (type: `array`):

Parts of benefit names to search, in Polish capitals or lowercase, such as ORTOPED, KARDIOLOG or REZONANS. Each one is searched and duplicates are removed.

## `province` (type: `string`):

Leave empty for all of Poland.

## `urgency` (type: `string`):

Stable or urgent cases.

## `includeProviderContacts` (type: `boolean`):

Adds phone, email, website, NIP and REGON. Some providers are individual practices, so treat these fields as personal data where that applies.

## `maxRecords` (type: `integer`):

You pay per record, so this also caps the cost of a run.

## Actor input object example

```json
{
  "benefits": [
    "ORTOPED",
    "KARDIOLOG"
  ],
  "urgency": "stable",
  "includeProviderContacts": false,
  "maxRecords": 50
}
```

# Actor output Schema

## `queues` (type: `string`):

Provider, location, people waiting and reported wait.

# 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 = {
    "benefits": [
        "ORTOPED",
        "KARDIOLOG"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("athletic_chill/poland-nfz-waiting-times").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 = { "benefits": [
        "ORTOPED",
        "KARDIOLOG",
    ] }

# Run the Actor and wait for it to finish
run = client.actor("athletic_chill/poland-nfz-waiting-times").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 '{
  "benefits": [
    "ORTOPED",
    "KARDIOLOG"
  ]
}' |
apify call athletic_chill/poland-nfz-waiting-times --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,athletic_chill/poland-nfz-waiting-times"
        }
    }
}
```

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/Ry34QDWxYw0kOQMWM/builds/7W5PfNJgRHyILyezw/openapi.json
