Skip to content
FonteumThe Graph

USE CASE · EXCLUSION & SANCTIONS SCREENING

Catch an excluded provider before they bill a federal claim.

Screen your workforce and vendor roster against OIG LEIE and the loaded federal and state exclusion lists. Completed checks expose their available source and observation fields; coverage and field availability vary by list.

68,055Source: OIG LEIE · As of 2026-05-08
LEIE exclusion recordsFederal + state listsNPI-keyedStale coverage fails closed

No PHI First 25 NPIs free $129 one-off certificate No monitoring

The compliance exposure

One missed exclusion is a false-claims problem.

Billing a federal program for items or services furnished by an excluded individual is an overpayment, and can carry civil monetary penalties under 42 U.S.C. §1320a-7a. OIG recommends checking before employing or contracting and periodically afterward; because the LEIE updates monthly, OIG says monthly screening best minimizes potential liability. A spreadsheet checked once at onboarding cannot show when a later check ran.

Per Fonteum's screening of every order- and referral-eligible NPI,

170Source: Fonteum research · As of 2026-07-12
currently match an active exclusion across federal and state lists — and most have been standing for over a year. Oversight gaps, not lag.

The developer pain

Stale CSVs and hand-rolled NPI matching.

The raw exclusion files ship as fixed-width and CSV with inconsistent name fields, no NPI on every row, and no record of when you last pulled them. Teams end up writing brittle fuzzy-matchers and cron jobs to re-download a file that changes monthly — and still have nothing dated to hand an auditor.

A single GET by NPI returns the match decision and the full source citation inline. The freshness of each list is a first-class field, so a behind-SLA source is a flag in the response, not a silent gap.

How it works

The lists screened, and how a match is decided.

Supported

State-list coverage

OIG LEIE, SAM.gov federal debarment, and the currently loaded state Medicaid exclusion lists — consulted together in one screen. The other states are not covered.

NPI

Match key

Deterministic NPI match where the source carries one; name + identifier corroboration where it does not. Displayed matches name their source list when available.

Fail closed

Coverage guard

A negative is returned only when serving coverage reconciles to comparable attested source artifacts; otherwise the result is indeterminate.

2

Screening layers

Excluded-anywhere (a hard exclusion in force) and compromised-anywhere (a sanction or monitoring flag short of exclusion) are returned separately.

Integration & workflow

One screen. Two ways in.

Developers screen by NPI over REST. Compliance teams can screen the first 25 NPIs on screen or buy the one-off certificate for up to 25 NPIs. The free workflow does not create an export.

GET /api/v1/exclusions/{npi}

curl https://fonteum.com/api/v1/exclusions/1356482946 \
  -H "Accept: application/json"

Response

{
  "npi": "1356482946",
  "checked_at": "2026-06-17",
  "excluded": true,
  "excluded_by": ["oig-leie"],
  "record_count": 1,
  "exclusions": [
    {
      "authority": "OIG LEIE",
      "exclusion_type": "1128(a)(1)",
      "excl_date": "2019-03-20",
      "reinstated": false
    }
  ],
  "compromised_anywhere": true,
  "sources": {
    "oig-leie": {
      "provenance": {
        "_source": "OIG LEIE",
        "_source_url": "https://oig.hhs.gov/exclusions/",
        "_snapshot": "2026-06-01",
        "_last_checked": "2026-06-17",
        "_methodology": "exclusions/v1",
        "_confidence": 1.0
      }
    }
  },
  "disclaimer": "Screening aid — re-confirm any match against the primary source list before acting."
}

Anonymous API screening is rate-limited to 100 requests/hour. The self-serve healthcare workflow separately checks the first 25 NPIs on screen.

Proof — not logos

Results identify the public source where the response supplies it.

68,055Source: OIG LEIE · As of 2026-05-08

Loaded LEIE rows

Production serving-table rows from the May 8, 2026 source release, checked July 12. Only the subset publishing NPI supports an exact NPI join; confirm against current OIG data.

oig.hhs.gov

Named source

Matches identify their originating federal or state list when the source plugin supplies that metadata; record-level links are not universal.

exclusions/v1

Methodology version

The version explains the calculation. Reproducing a past result also requires the retained input snapshot or row versions; methodology alone is insufficient.

Scoped

Attestation

Snapshot-attestation fields appear only where the export supplies a concrete object reference. No exclusion fact currently links deterministically to a witness signature.

“A screening aid is only as good as the date it was run. The date, the source, and the snapshot are the product.”

EXCLUSION & SANCTIONS

Screen the first 25 NPIs against the supported federal and state lists.

Questions

Before the security questionnaire.

Why not just run the OIG LEIE myself?

You can download the monthly LEIE file. What that does not give you is NPI-joined matching across the federal sources and Fonteum's currently loaded state lists at once, a dated record of when each check ran, and the source snapshot it ran against. Fonteum does not cover every state.

How often is the exclusion data refreshed?

OIG LEIE publishes monthly; SAM.gov and the supported state Medicaid lists currently loaded by Fonteum vary. Fonteum's loaded OIG release was dated May 8, 2026 when checked July 12, 2026. Confirm current status at the primary source before acting.

Do you screen against state Medicaid exclusion lists too?

Yes. Beyond OIG LEIE, Fonteum consults SAM.gov and the currently loaded state Medicaid exclusion lists for GA, IA, MD, MS, MT, NC, ND, NH, NY, OH, PA, TN, and WA. It does not claim coverage of the other states. Displayed matches name the source list and show a source-date field when available.

What audit fields can a screening result return?

The free workflow shows counts and matched-source breakdown on screen only. The $129 one-off certificate for up to 25 NPIs stores PDF and JSON artifacts in the customer's account after roster submission. Coverage and fields vary by source and response.

Do you store any patient data?

No. Screening runs against public federal and state records keyed by NPI. There is no PHI in the pipeline and none is required to run a roster scan or a single-provider check.

FONTEUM · EXCLUSION SCREENING

Screen the first 25 NPIs on public data only. No PHI.

What’s on file, by the numbers

Platform snapshot · 2026-07-22

13.4Mproviders & companiesProviders, organizations, owners, and facilities on file
26.2Msource-linked factsSource-linked field facts in the dated platform snapshot
90sources with dataDistinct snapshot source IDs with at least one positive record count
79fresh sourcesDistinct source IDs whose latest positive-data snapshot falls within the preceding 45 days
111sources integratedActive registry rows; integration does not establish a load
13state Medicaid jurisdictionsDistinct states represented in the state-exclusions serving table

Integrated, with-data, and fresh-observation counts are separate. No platform-wide source-completeness count is published. Completeness is source-specific and must be evaluated against the named source's expected scope. State coverage is a separate jurisdiction measure.

Source authority is record-specific

Use the issuer named on the record.

Fonteum spans federal, state, and global public publishers. A source page or returned record identifies its issuer and dataset where that metadata is available. A platform registry count does not assign every page to one authority or establish loaded, fresh, or complete coverage.

Browse source records and their stated limitations →

Reproducible by design

Inspect the evidence each published figure actually supplies.

Source and date

Research pages expose the named public file and observation date where those fields are available. Source-file SHA-256 coverage is separate; facts do not currently link deterministically to signatures.

Available derivation

Studies with a retained release and committed derivation link the SQL or method used. Other studies state the evidence and reproduction limits they actually have.

Daily observations

Dated table row-count observations can detect local drift. They do not imply that an upstream publisher released or Fonteum ingested new data that day.

Named medical review

Reviewed by Jennifer Montecillo, MD, medical reviewer. Non-practicing medical reviewer.

Read the full provenance and attestation methodology →

Request access