Skip to content
FonteumThe Graph

GUIDE · EXCLUSION & SANCTIONS SCREENING

Is this party barred — anywhere, provably.

One bridge across the federal lists and Fonteum's supported state Medicaid lists currently loaded: the OIG LEIE and state Medicaid lists for healthcare, and SAM.gov debarment for federal contracting. This guide routes to the data, the studies, and the workflow that turn a roster into a dated, source-cited screen.

The short answer

What is exclusion and sanctions screening?

Exclusion screening is checking a person or organization against the government lists of parties barred from federal programs — and keeping a dated record of the check. In healthcare, that means the OIG LEIE, SAM.gov, and each state's Medicaid exclusion list; in federal contracting, it means SAM.gov debarment and suspension. A party barred in one place can stay active in another — which is exactly the gap a single-list check misses.

Fonteum screens OIG LEIE, SAM.gov, and the currently loaded state Medicaid lists for GA, IA, MD, MS, MT, NC, ND, NH, NY, OH, PA, TN, and WA, returning an excluded-anywhere signal, and displays the source file and best available source-date field for supported matches — the record an audit asks for. This hub is where the healthcare and federal-contracting sides meet. Fonteum does not claim coverage of the other states. For source boundaries, read the definitions of OFAC, a sanctions list, and list-based sanctions.

Common questions

Answers in one line each

What lists should a healthcare exclusion screen cover?
A complete healthcare screen covers two federal lists — the OIG LEIE and SAM.gov — plus every applicable state Medicaid exclusion list. A party barred by one state can stay off the federal LEIE, so a multi-state roster has to clear each jurisdiction, not just the federal pair.
How is exclusion screening different in federal contracting?
Federal contracting screens against SAM.gov suspension and debarment rather than the healthcare LEIE, and the bar is procurement-wide. The mechanic is similar — check the party against the government's list and keep a dated, source-cited record. Cross-vertical questions route through this hub.
How often does OIG recommend exclusion screening?
OIG says providers are not generally required by statute or regulation to check the LEIE, but recommends checking before employing or contracting and periodically afterward. Because OIG updates the LEIE monthly, it says monthly screening best minimizes potential liability. Applicable state, contract, and program rules can impose their own cadence.
What does an excluded-anywhere screen mean?
On Fonteum today, it means one check resolves a party against the federal LEIE, SAM.gov, and supported loaded state Medicaid lists, and flags a hit on any of those sources. It is not a claim of nationwide state-list coverage. A separate integrity layer reports OIG Corporate Integrity Agreements and CMS civil-money-penalty records when an NPI-linked record is available. Matches expose the source and observation fields available on the response.
START HERE

Screen the first 25 NPIs against the currently loaded lists — free.

Screen the first 25 unique ten-digit NPI inputs on demand across OIG LEIE, SAM.gov, and the supported state Medicaid lists currently loaded by Fonteum. The free result stays on screen; no artifact, email, or monitoring is created.

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