Multi-source exclusion screening vs single-list checks
Screening only the OIG LEIE catches federally excluded providers but misses state Medicaid exclusions, SAM.gov debarments, and corporate-integrity flags. Fonteum screens the LEIE alongside additional federal and state exclusion source families, NPI-resolved, with a source-and-date stamp on every match — the LEIE alone lists active exclusions.
Published June 17, 2026 · Last reviewed June 2026 · Capability comparison — public facts only
From a single-list lookup to defensible, multi-source screening
| Capability | Single-list checks | Fonteum |
|---|---|---|
| Sources screened | One list — most often the OIG LEIE on its own. | The OIG LEIE plus additional federal and state exclusion source families in one pass. |
| State Medicaid exclusions | Not caught by an LEIE-only check; many providers are barred at state level only. | State Medicaid exclusion lists (e.g., Pennsylvania, North Carolina) screened alongside the LEIE. |
| Federal debarment | SAM.gov debarments sit outside a single OIG-list check. | SAM.gov exclusions and OIG corporate-integrity agreements screened in the same pass. |
| Identity matching | Name or NPI matched against one file, by hand or basic match. | NPI-resolved across providers, with the match basis recorded. |
| Match provenance | A hit, without which list, which version, or what date. | Source list, version, and snapshot date stamped on every match. |
| Refresh cadence | As current as your last manual pull. | OIG LEIE monthly ( exclusions); each source on its native cadence. |
| Point-in-time evidence | Hard to show what a list said on a past date. | As-of screening — re-derive the result the list would have returned on a past date. |
| Audit trail | A screenshot or CSV, with no integrity chain. | Attestation chain plus a downloadable evidence artifact. |
| Delivery | Manual lookups or one feed to wire in. | API, MCP server, bulk export, and free research datasets. |
Screening one list — most often the OIG LEIE — catches federally excluded providers but not state Medicaid exclusions, SAM.gov debarments, or corporate-integrity flags. Descriptions reflect the single-list screening pattern, not any single vendor.
What a single-list check leaves uncovered
One list is a floor, not the picture
Monthly OIG LEIE screening is the baseline expectation, and the LEIE lists excluded providers. But a provider barred by a state Medicaid program or debarred federally on SAM.gov can still clear an LEIE-only check. Breadth across exclusion sources is what closes that gap.
A match is only as useful as its provenance
A bare hit raises a question an LEIE-only screen cannot answer: which list, which version, on what date. Fonteum stamps each match with its source list, version, and snapshot date, so the result is defensible rather than a screenshot.
Screening is evidence, not just a yes or no
Compliance programs are judged on the trail, not the verdict. An NPI-resolved match against dated exclusion sources, wrapped in an attestation chain and exportable as an artifact, is the audit evidence a manual list lookup does not produce.
Compare other data capabilities
Provider data vs raw public files →
NPI-resolved, provenance-tracked records vs parsing bulk CSVs yourself.
Live provider data vs annual snapshots →
Continuously refreshed federal data vs paywalled annual snapshots.
Healthcare provider data platforms compared →
How sourcing model and provenance separate the category.
Common questions
- Is screening the OIG LEIE enough on its own?
- Monthly OIG LEIE screening is the federal baseline, but it is not complete. A provider barred only by a state Medicaid program, or debarred federally through SAM.gov, can still pass an LEIE-only check. Screening additional federal and state exclusion sources is what closes the gap a single list leaves open.
- What exclusion sources does Fonteum screen beyond the LEIE?
- Alongside the OIG LEIE, Fonteum screens SAM.gov exclusions, state Medicaid exclusion lists such as Pennsylvania Medicheck and North Carolina Medicaid, OIG corporate-integrity agreements, and CMS civil money penalties. Each is an exclusion or enforcement source family with its own cadence, joined to providers on the shared NPI identity backbone.
- How often is the exclusion data refreshed?
- Each exclusion source refreshes on its own cadence. Fonteum re-ingests the OIG LEIE monthly, the same cadence CMS and OIG publish, and tracks the other federal and state exclusion sources on their native schedules. Every match carries the snapshot date, so the screening result is tied to a known list version.
- Can I show what an exclusion list said on a past date?
- Yes. Fonteum retains dated snapshots of each exclusion source, so a screening result can be re-derived as of a past date rather than only the current list. That as-of capability matters when an auditor asks which version of a list a provider was screened against, and when.
- What makes a screening result audit-ready?
- An audit-ready result names the source list, its version, and the date, identifies the provider by NPI rather than name alone, and ships as an evidence artifact backed by an attestation chain. A single-list lookup that returns a yes or no, with no list version or date, leaves that trail to reconstruct later.
- Does Fonteum replace my credentialing workflow tool?
- No. Fonteum is the federal and state exclusion data tier those workflows consume, not the workflow itself. A credentialing platform handles task queues, re-credentialing schedules, and continuous monitoring; Fonteum supplies the NPI-resolved, dated, provenance-stamped exclusion data underneath. Teams pair the two rather than choosing one.
Screen against more than one list.
See the exclusion data at /data/oig-leie, browse the full source library at /sources, or request access.
- /data/oig-leie → The OIG LEIE exclusion dataset and refresh cadence.
- /sources → Every federal and state source family with tier and cadence.
- /data-provenance → How each match ties back to a dated source list.
- /data → Dataset catalog, export concepts, and pilot pricing.