OIG LEIE Exclusion Screening — HHS Exclusion List Check avatar

OIG LEIE Exclusion Screening — HHS Exclusion List Check

Pricing

from $20.00 / 1,000 record screeneds

Go to Apify Store
OIG LEIE Exclusion Screening — HHS Exclusion List Check

OIG LEIE Exclusion Screening — HHS Exclusion List Check

Screen employees, providers, contractors and vendors against the HHS OIG List of Excluded Individuals/Entities (LEIE). Matches by NPI, name, date of birth or business name, and returns graded confidence so a surname collision is never reported as a confirmed exclusion.

Pricing

from $20.00 / 1,000 record screeneds

Rating

0.0

(0)

Developer

Malek H

Malek H

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

5 days ago

Last modified

Categories

Share

OIG LEIE Exclusion Screening — check employees & vendors against the HHS exclusion list

Screen your employees, providers, contractors and vendors against the HHS OIG List of Excluded Individuals/Entities (LEIE) — the federal healthcare exclusion list. Send a list of people or businesses, get back a graded match report.

Federal healthcare programs require exclusion screening monthly. Employing an excluded individual can trigger civil monetary penalties of up to $25,000 per item or service furnished, plus treble damages. This Actor automates that check.

What it does

  • Downloads the current LEIE database directly from oig.hhs.gov on every run (~84,000 exclusion records, refreshed monthly by OIG)
  • Screens each of your records by NPI, name + date of birth, name, or business name
  • Returns graded confidence for every hit, so you can separate a definite identifier match from a common-surname coincidence
  • Filters out reinstated parties by default
  • Reports the exact LEIE version used (leieLastUpdated) so every screening is auditable

Why the confidence grading matters

OIG's own guidance is explicit: a name match is a potential match, and must be verified against SSN or EIN before any adverse action is taken. A tool that returns a flat "excluded: true" on a surname collision will eventually cost someone their job by mistake.

So every result carries a highestConfidence value:

highestConfidenceMeaningexcluded
npi_exactNPI matched an excluded partytrue
name_dob_exactName and date of birth matchedtrue
business_exactBusiness name matched exactlytrue
name_exactFirst + last name matched, no DOB to confirmfalse — verify
business_fuzzyPartial business-name overlapfalse — verify
name_fuzzySurname + initial, or nickname variantfalse — verify
noneNo match in the current LEIEfalse

Records needing human confirmation are flagged with requiresManualVerification: true and a link to the official OIG search.

Input

{
"records": [
{ "firstName": "John", "lastName": "Smith", "npi": "1234567890" },
{ "firstName": "Maria", "lastName": "Garcia", "dateOfBirth": "19670412" },
{ "businessName": "Acme Home Health Services, Inc" }
],
"fuzzyThreshold": 0.85,
"includeReinstated": false
}
FieldTypeDefaultDescription
recordsarrayPeople and/or businesses to screen. Required.
records[].firstNamestringGiven name (individuals)
records[].lastNamestringSurname (individuals)
records[].npistring10-digit NPI. The strongest identifier available.
records[].dateOfBirthstringYYYYMMDD. Upgrades a name match to confirmed.
records[].businessNamestringEntity name (organizations)
fuzzyThresholdnumber0.850–1. Lower catches more, with more noise.
includeReinstatedbooleanfalseInclude parties already reinstated.

Any extra fields you pass on a record (employee ID, department, hire date) are echoed back untouched in input, so results reconcile against your HR system.

Output

One dataset item per screened record:

{
"input": { "firstName": "John", "lastName": "Smith", "npi": "1234567890" },
"screenedAt": "2026-07-29T04:30:00+00:00",
"leieLastUpdated": "Fri, 10 Jul 2026 12:35:14 GMT",
"leieRecordCount": 83665,
"matchCount": 1,
"highestConfidence": "npi_exact",
"excluded": true,
"requiresManualVerification": false,
"guidance": "Identifier-grade match. Treat as excluded and follow your compliance process.",
"matches": [
{
"lastName": "SMITH", "firstName": "JOHN", "npi": "1234567890",
"generalCategory": "INDIVIDUAL", "specialty": "NURSE",
"exclusionType": "1128a1", "exclusionDate": "20190315",
"state": "TX", "matchType": "npi_exact", "matchScore": 1.0
}
]
}

Export as JSON, CSV, or Excel, or pull it from the API for your compliance record.

Typical uses

  • Monthly workforce screening — run your full employee roster on a schedule
  • Pre-hire checks — screen candidates before an offer
  • Vendor and contractor due diligence — screen business entities
  • Payer / provider network validation — screen a provider roster by NPI

Data source

HHS OIG LEIEUPDATED.csv, a US Government work in the public domain. Downloaded fresh on every run; nothing is cached between runs, so you are always screening against the current list.

Limitations — read before relying on this

  • The LEIE is the federal exclusion list. It does not include state Medicaid exclusion lists or the SAM.gov debarment list. Full compliance programs screen those separately.
  • OIG updates the LEIE monthly, so an exclusion can be up to ~30 days old.
  • A name-only match is not proof of exclusion. Verify at exclusions.oig.hhs.gov using SSN/EIN before acting.
  • This Actor is a screening aid, not legal advice.