# New York Workers' Compensation Claims - Injury Records (`j0401/ny-workers-comp`) Actor

New York workers' compensation claims assembled since 2000 (public open data, 5.66M claims, anonymized): dates, age, gender, county, carrier, status and injury coded against both OIICS (BLS) and WCIO vocabularies, plus wage and hearing counts. No names.

- **URL**: https://apify.com/j0401/ny-workers-comp.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.03 / 1,000 ny workers' comp claim 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?

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

## New York Workers' Compensation Claims - Injury Records

Every workers' compensation claim the New York State Workers' Compensation Board
has assembled since 2000. **5.66 million claims**, anonymized, with the injury
coded against two standard vocabularies.

### Low cost

**From $0.00005 per record, down to $0.00003 at Gold.** Pay only for the records
you actually receive - the whole register stays queryable, you are never billed
for the scan behind it.

### What you get

One row per claim, with the injury, the adjudication path and the carrier
attached to it:

- **The event** - accident date, assembly date, age at injury, birth year,
  gender, ZIP and the county the injury happened in
- **The injury, coded twice** - against **OIICS** (BLS: event/exposure, injury
  source, nature, part of body, secondary source) *and* **WCIO** (the codes
  carriers use: cause, nature, part of body), each with the full description
- **The carrier** - name and type (private, SIF, self-insured public/private,
  special fund)
- **The path** - current status, highest process reached, whether an attorney or
  alternative dispute resolution was involved, hearing count and closed count
- **The money** - average weekly wage and the individual medical-fee region

🔴 **The worker is anonymous.** There is no name and no address - only age,
birth year, gender, ZIP and county. This is a record layer for injury-pattern
analysis, not for identifying a person.

### Filter it

- **Body part** - `oiicsPartOfBodyDesc="BACK"`, `"SHOULDER"`, `"FINGER"`.
- **Nature** - `oiicsNatureInjuryDesc="TRAUMATIC INJURIES TO BONES"`,
  `"TRAUMATIC INJURIES TO MUSCLES"`.
- **Event** - `oiicsEventExposureDesc="ASSAULTS"`, `"FALL ON SAME LEVEL"`,
  `"OVEREXERTION"`.
- **Industry** - `industryDescription="HEALTH CARE AND SOCIAL ASSISTANCE"`,
  `"CONSTRUCTION"`.
- **Carrier** - `carrierName="LIBERTY"`, `carrierType="SELF PUBLIC"`.
- **Where** - `county="KINGS"` (Brooklyn), `districtName="NYC"`.
- **Status** - `claimStatus="NO FURTHER ACTION"`, `"CASE CANCELLED"`.
- **When** - `accidentFrom="2025-01-01"`, or `recentDays=365`.

### Example inputs

**Back injuries in one county** - combine body part and county.

```json
{ "oiicsPartOfBodyDesc": "BACK", "county": "KINGS", "maxResults": 50 }
```

**Assaults and the injuries they cause** - two coded filters combined.

```json
{ "oiicsEventExposureDesc": "ASSAULTS", "oiicsNatureInjuryDesc": "TRAUMATIC INJURIES TO BONES", "maxResults": 50 }
```

**One carrier's recent claims** - carrier and window.

```json
{ "carrierName": "LIBERTY", "accidentFrom": "2024-01-01", "maxResults": 50 }
```

**Where the injuries land** - `mode=aggregate`.

```json
{ "mode": "aggregate", "groupBy": "oiicsPartOfBodyDesc" }
```

### Or roll it up

Set `mode=aggregate` and get a rolled-up count by **claim status**,
**carrier type**, **carrier name**, **claim type**, **gender**, **district**,
**injury county**, **industry**, **medical fee region**, **OIICS nature**,
**OIICS body part** or **WCIO cause**. Every group comes back - this mode is not
cut off by `maxResults`.

### Then read the pattern

- The most common injuries by body part, nature and industry.
- One carrier's claims by status and body part.
- Assaults vs. falls vs. overexertion, by county and district.
- Wage levels by industry and injury type.

### Example output

**One claim** - `oiicsPartOfBodyDesc=BACK`:

```json
{
 "platform": "ny-workers-comp",
 "source": "new-york-workers-compensation",
 "mode": "rows",
 "recordType": "claim",
 "claimId": "4086194",
 "accidentDate": "2015-09-02",
 "assemblyDate": "2015-09-04",
 "currentClaimStatus": "NO FURTHER ACTION",
 "carrierType": "1A. PRIVATE",
 "claimType": "WORKERS COMPENSATION CLAIM",
 "oiicsNatureInjuryDesc": "TRAUMATIC INJURIES TO BONES, NERVES, SPINAL CORD",
 "oiicsPartOfBodyDesc": "BACK, INCLUDING SPINE, SPINAL CORD",
 "wcioCauseOfInjuryDesc": "STRAIN OR INJURY BY - TWISTING",
 "averageWeeklyWage": "738.80",
 "hearingCount": "0"
}
```

**`mode=aggregate`, `groupBy=oiicsPartOfBodyDesc`** - one count row per body
part:

```
(blank)                                   4,513,492
BACK, INCLUDING SPINE, SPINAL CORD          213,642
MULTIPLE BODY PARTS                         163,035
LEG(S)                                      144,814
SHOULDER, INCLUDING CLAVICLE, SCAPULA       100,305
FINGER(S), FINGERNAIL(S)                     76,511
```

The `(blank)` group is the ~80% of older claims that predate OIICS coding -
roll-ups return it rather than hiding it.

### Notes on the data, from the source

- **This is an assembled-claim register, not a live feed.** A claim appears once
  the Board has built the case record, so `assemblyDate` lags the accident by
  weeks to years and is the true freshness signal.
- **The body-part and nature columns are blank on many rows.** About 80% of
  claims carry no OIICS body part - the older ones predate the coding. Blank is
  normal and is not "unknown"; the coverage is stated rather than implied.
- **`industryCode` is populated on ~84% of rows.** Same rule: blank means not
  recorded, not unclassified.
- **`sourceUpdatedAt` carries the newest assembly date**, the freshness signal
  an agent can read without running the actor.

# Actor input Schema

## `carrierName` (type: `string`):

Substring match on the insurance carrier.

## `carrierType` (type: `string`):

Substring match on the carrier type, e.g. 'PRIVATE', 'SELF PUBLIC'.

## `claimType` (type: `string`):

Substring match on the claim type, e.g. 'WORKERS COMPENSATION'.

## `claimStatus` (type: `string`):

Substring match on the current status, e.g. 'NO FURTHER ACTION'.

## `county` (type: `string`):

Substring match on the county where the injury happened, e.g. 'KINGS'.

## `districtName` (type: `string`):

Substring match on the WCB district office, e.g. 'NYC', 'LONG ISLAND', 'ALBANY'.

## `gender` (type: `string`):

Substring match on the recorded gender.

## `industryCode` (type: `string`):

Substring match on the industry code.

## `industryDescription` (type: `string`):

Substring match on the industry, e.g. 'HEALTH CARE AND SOCIAL ASSISTANCE' or 'CONSTRUCTION'.

## `oiicsEventExposureDesc` (type: `string`):

Substring match on the OIICS event/exposure, e.g. 'FALL ON SAME LEVEL' or 'ASSAULTS'.

## `oiicsNatureInjuryDesc` (type: `string`):

Substring match on the OIICS nature of injury, e.g. 'TRAUMATIC INJURIES TO BONES'.

## `oiicsPartOfBodyDesc` (type: `string`):

Substring match on the OIICS part of body, e.g. 'BACK'.

## `wcioCauseOfInjuryDesc` (type: `string`):

Substring match on the WCIO cause of injury.

## `wcioNatureOfInjuryDesc` (type: `string`):

Substring match on the WCIO nature of injury.

## `wcioPartOfBodyDesc` (type: `string`):

Substring match on the WCIO part of body.

## `minWage` (type: `number`):

Smallest average weekly wage.

## `maxWage` (type: `number`):

Largest average weekly wage.

## `minAge` (type: `integer`):

Youngest age at injury.

## `maxAge` (type: `integer`):

Oldest age at injury.

## `accidentFrom` (type: `string`):

Earliest accident date, YYYY-MM-DD.

## `accidentTo` (type: `string`):

Latest accident date, YYYY-MM-DD.

## `recentDays` (type: `integer`):

Only claims whose accident is within the last N days. 0 = off.

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

rows = records matching your filters (default). aggregate = one count row per group (see groupBy).

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

Which dimension to aggregate over (mode=aggregate). Blank = the default dimension. Every group is returned - aggregate mode is not cut off by maxResults.

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

Cap the number of records returned (0 = default 50). Records are charged individually; there is no per-run charge cap.

## Actor input object example

```json
{
  "carrierName": "",
  "carrierType": "",
  "claimType": "",
  "claimStatus": "",
  "county": "",
  "districtName": "",
  "gender": "",
  "industryCode": "",
  "industryDescription": "",
  "oiicsEventExposureDesc": "",
  "oiicsNatureInjuryDesc": "",
  "oiicsPartOfBodyDesc": "",
  "wcioCauseOfInjuryDesc": "",
  "wcioNatureOfInjuryDesc": "",
  "wcioPartOfBodyDesc": "",
  "accidentFrom": "",
  "accidentTo": "",
  "recentDays": 0,
  "mode": "rows",
  "groupBy": "currentClaimStatus",
  "maxResults": 50
}
```

# Actor output Schema

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

New York Workers' Compensation Claims - Injury Records records - 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/ny-workers-comp").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/ny-workers-comp").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/ny-workers-comp --silent --output-dataset

```

## MCP server setup

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

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/osZ1jzuSOoObGLdFF/builds/qKuIRC7X6sjXmoWKM/openapi.json