HHS OIG Exclusions List Scraper

Download and normalize the official HHS OIG List of Excluded Individuals/Entities (LEIE) current database and monthly supplement CSV files.

This actor is built for healthcare compliance, credentialing, staffing, vendor risk, and sanctions-monitoring teams that need repeatable access to structured HHS OIG exclusion data.

What does this actor do?

It fetches the public HHS OIG LEIE download page.

It discovers the current full database CSV.

It discovers recent monthly exclusion supplement CSV files.

It discovers recent monthly reinstatement supplement CSV files.

It downloads the selected files directly from HHS OIG.

It parses the official CSV layout.

It normalizes dates and placeholder values.

It applies optional state, name, and exclusion-type filters.

It saves clean records to the default Apify dataset.

Why use it?

HHS OIG exclusions are a common screening source for healthcare compliance workflows.

Manual CSV downloads are repetitive.

The source files contain legacy field names.

The same record layout appears across current and supplement files.

This actor turns those files into API-ready JSON.

It also records the source file and source URL for auditability.

Common use cases

Screen providers during credentialing.

Check vendors during onboarding.

Monitor excluded individuals and entities by state.

Track monthly exclusion additions.

Track monthly reinstatement files.

Enrich internal compliance databases.

Export HHS OIG LEIE data to BI tools.

Build recurring sanctions-monitoring jobs.

Input overview

The actor has a small input surface.

Use mode to choose source files.

Use maxItems to cap output volume.

Use states to filter by state code.

Use nameQuery to search names or business names.

Use exclusionTypes to filter by HHS exclusion code.

Use includeReinstatements for reinstatement supplement files.

Use maxSupplementMonths to control supplement history.

Mode: current

current downloads the latest full LEIE database file.

This is the best mode for full snapshot exports.

It is also the best mode for state or name searches against the current database.

The output record type is current.

Mode: supplements

supplements downloads monthly supplement files from the HHS OIG download page.

The newest supplement periods are processed first.

Exclusion supplement records are marked as supplement_exclusion.

Reinstatement supplement records are marked as supplement_reinstatement.

Use this mode for monitoring changes.

Mode: both

both processes the current database and supplement files in one run.

Use it when you want a current snapshot plus recent change files.

For large exports, increase maxItems enough to include all desired files.

Filtering by state

Set states to one or more two-letter codes.

Example: ["NY", "CA", "TX"].

The filter is applied after CSV parsing.

Leave it empty to keep all states.

Filtering by name

Set nameQuery to a provider, person, or entity fragment.

The search is case-insensitive.

It checks assembled full names and business names.

It is useful for targeted due-diligence checks.

Filtering by exclusion type

Set exclusionTypes to HHS OIG exclusion code values.

Example: ["1128a1", "1128b5"].

Leave it empty to include all codes.

Output fields

Each dataset item includes recordType.

Each item includes fullName.

Each item includes individual name fields.

Each item includes businessName when present.

Each item includes generalCategory and specialty.

Each item includes upin and npi when present.

Each item includes address, city, state, and ZIP.

Each item includes exclusion and reinstatement dates.

Each item includes waiver date and waiver state.

Each item includes source file metadata.

Date normalization

HHS OIG CSV dates are published as YYYYMMDD.

The actor converts valid dates to YYYY-MM-DD.

Zero-only placeholders become null.

This makes the output easier to sort and filter.

Source traceability

Every row includes sourceFile.

Every row includes sourceUrl.

Every row includes fetchedAt.

These fields help compliance teams prove where a record came from.

Example: current New York records

{
  "mode": "current",
  "maxItems": 100,
  "states": ["NY"]
}

Example: latest supplements

{
  "mode": "supplements",
  "maxItems": 250,
  "includeReinstatements": true,
  "maxSupplementMonths": 2
}

Example: name search

{
  "mode": "current",
  "maxItems": 50,
  "nameQuery": "MEHRAN"
}

Example output item

{
  "recordType": "current",
  "fullName": "#1 MARKETING SERVICE, INC",
  "businessName": "#1 MARKETING SERVICE, INC",
  "generalCategory": "OTHER BUSINESS",
  "specialty": "SOBER HOME",
  "city": "BROOKLYN",
  "state": "NY",
  "zip": "11235",
  "exclusionType": "1128a1",
  "exclusionDate": "2020-03-19",
  "sourceFile": "UPDATED.csv"
}

Pricing

This actor uses pay-per-event pricing.

A small run-start event covers fixed startup overhead.

An item event is charged for each dataset record produced.

The final live tiered prices are set during platform validation.

Performance notes

The actor uses direct HTTP requests.

It does not require Playwright.

It does not require login cookies.

It does not use proxies by default.

The current HHS OIG CSV is large, so highly selective name searches may scan many rows before finding matches.

Data source

The source is the public HHS OIG LEIE database and supplement downloads page.

The actor does not modify source data beyond normalization.

Users should review HHS OIG guidance for official interpretation of exclusion records.

Compliance note

This actor helps automate data retrieval.

It is not legal advice.

It does not decide whether a person or entity is eligible for any program.

Compliance teams should apply their own review policies.

Limitations

The actor depends on the public HHS OIG download page structure.

If HHS changes filenames or the CSV layout, the actor may need an update.

PDF-only profile correction files are not parsed.

The online search portal is not scraped.

Recommended scheduling

For current snapshot workflows, schedule weekly or monthly runs.

For supplement monitoring, schedule shortly after HHS OIG monthly updates.

For one-off checks, use nameQuery and a low maxItems.

Export formats

Apify datasets can be exported as JSON.

They can be exported as CSV.

They can be exported as Excel.

They can be consumed through the Apify API.

Integration ideas

Send results to a compliance database.

Compare new supplement rows against an internal provider list.

Join records with NPI registry data.

Trigger alerts for matching vendor names.

Archive monthly snapshots for audit history.

Troubleshooting

If no records appear, relax filters.

Check that state codes are two-letter abbreviations.

Check that exclusion type codes match HHS values.

Increase maxItems when using broad modes.

Use sourceFile to confirm which CSV produced a row.

Support

If the actor stops returning data, include the run ID and input in your report.

If you need additional fields from HHS OIG files, describe the target field and workflow.

If you need cross-source enrichment, consider combining this actor with NPI or CMS data actors.

Who is it for?

Healthcare compliance officers use it to review official exclusion records.

Credentialing teams use it before approving providers.

Vendor-risk teams use it before onboarding healthcare suppliers.

Staffing companies use it to monitor candidates and contractors.

Data teams use it to automate recurring LEIE ingestion.

API usage

You can run this actor from the Apify API or from Apify client libraries.

Node.js API example

import { ApifyClient } from 'apify-client';

const client = new ApifyClient({ token: process.env.APIFY_TOKEN });
const run = await client.actor('automation-lab/hhs-oig-exclusions-list-scraper').call({
  mode: 'current',
  maxItems: 20,
  states: ['NY'],
});
console.log(run.defaultDatasetId);

Python API example

from apify_client import ApifyClient
import os

client = ApifyClient(os.environ['APIFY_TOKEN'])
run = client.actor('automation-lab/hhs-oig-exclusions-list-scraper').call(run_input={
    'mode': 'current',
    'maxItems': 20,
    'states': ['NY'],
})
print(run['defaultDatasetId'])

cURL API example

curl -X POST 'https://api.apify.com/v2/acts/automation-lab~hhs-oig-exclusions-list-scraper/runs?token=YOUR_APIFY_TOKEN' \
  -H 'Content-Type: application/json' \
  -d '{"mode":"current","maxItems":20,"states":["NY"]}'

MCP

This actor can be used through Apify MCP integrations so assistants can run LEIE checks from chat-based workflows.

Example Claude setup command:

$claude mcp add apify -- npx -y @apify/actors-mcp-server --actors automation-lab/hhs-oig-exclusions-list-scraper

Example MCP server JSON configuration:

{
  "mcpServers": {
    "apify": {
      "command": "npx",
      "args": [
        "-y",
        "@apify/actors-mcp-server",
        "--actors",
        "automation-lab/hhs-oig-exclusions-list-scraper"
      ],
      "env": {
        "APIFY_TOKEN": "YOUR_APIFY_TOKEN"
      }
    }
  }
}

Example prompts for MCP usage

Example prompts showing MCP usage:

• "Use the Apify MCP server to run the HHS OIG Exclusions List Scraper for current NY records and return the first 20 matches."
• "With MCP, check the newest HHS OIG LEIE supplements and summarize reinstatement records."
• "Use MCP to search the current LEIE database for business names containing MEHRAN and provide source file metadata."

Use the same JSON input fields shown above.

For compliance assistants, keep maxItems low during interactive checks.

For scheduled ingestion, raise maxItems to match your downstream workflow.

Legality

The actor downloads public HHS OIG files.

The data is published by a U.S. government source.

Users are responsible for using the data according to their compliance policies.

Do not treat this automation as a substitute for official legal or regulatory advice.

FAQ

Does this actor scrape the online search portal?

No. It uses the official downloadable CSV files.

Does it include reinstatements?

Yes, when supplement mode is enabled and includeReinstatements is true.

Can I get all current records?

Yes. Use mode: "current" and set maxItems high enough for your export.

Why do some fields contain null?

HHS OIG uses blank or zero-only placeholders for unavailable data; the actor normalizes those values to null.

Does it need a proxy?

No. The source files are public HTTP downloads.

Related actors

Use this actor with NPI registry scrapers for provider enrichment.

Use it with CMS provider data actors for facility and organization screening.

Use it with company and sanctions data actors for vendor-risk workflows.

Use it as the HHS OIG source component in a broader healthcare-compliance pipeline.