Skip to content
FonteumPublic-records evidence
Fonteum · Data · Exclusions

A provider clean on the federal list can still be excluded by a state.

The federal OIG LEIE covers exclusions from federal health programs. State Medicaid programs keep their own exclusion lists — and many state-excluded providers never appear on the federal list. Of 5,224 NPI-bearing providers on the state Medicaid exclusion lists Fonteum mirrors today, 3,109 (60%) do not appear on the federal LEIE by NPI — the exact gap a federal-only screen returns as a false clean. Aggregate-level, framed as a screening aid; cross-check any single record against the publishing agency.

Federal and state lists overlap — but not completely

State-list NPIs (13 represented jurisdictions)
5,224
distinct NPI-bearing providers across the currently loaded state lists
Also on federal LEIE
2,115
appear on both a state list and the federal exclusion list
State-only (missed by a federal-only screen)
3,109
60% of state-list NPIs do not appear on the federal LEIE by NPI

Overlap is matched by NPI. The federal LEIE records an NPI on only a minority of its entries (entity records typically lack one by source convention), so the federal-only figure is a floor on the true overlap, not a ceiling — the state-only share is therefore a conservative estimate of what a federal-only NPI screen misses.

State Medicaid exclusion coverage

22,917 state Medicaid exclusion records across 13 distinct state Medicaid jurisdictions · captured September 19, 2026. Each state page mirrors the published list as a screening aid, with NPI-matched records linked to their provider profile.

StateExclusion recordsWith NPI
New York8,9162,276
Pennsylvania6,7071,572
Ohio1,980732
Maryland1,605265
Georgia1,36936
Iowa1,270389
Washington244210
North Dakota19547
Mississippi193140
Montana17543
North Carolina166152
New Hampshire7651
Tennessee219

Coverage expands as additional state Medicaid exclusion lists are onboarded. A state with too few records to substantiate a dataset is held back from the index until its list is fully captured.

All 50 states and DC — the coverage ledger

Every U.S. jurisdiction, with its status stated plainly: loaded (records served with a dated capture), registered (a source module exists and ingest is queued), or not yet loaded. A jurisdiction marked not yet loaded is not represented as covered — absence here says nothing about any provider in that state.

JurisdictionStatusRecords
AlabamaNot yet loaded
AlaskaNot yet loaded
ArizonaNot yet loaded
ArkansasNot yet loaded
CaliforniaNot yet loaded
ColoradoRegistered — not yet loaded
ConnecticutNot yet loaded
DelawareNot yet loaded
District of ColumbiaNot yet loaded
FloridaNot yet loaded
GeorgiaLoaded · captured September 19, 20261,369
HawaiiNot yet loaded
IdahoNot yet loaded
IllinoisNot yet loaded
IndianaRegistered — not yet loaded
IowaLoaded · captured September 19, 20261,270
KansasRegistered — not yet loaded
KentuckyRegistered — not yet loaded
LouisianaRegistered — not yet loaded
MaineNot yet loaded
MarylandLoaded · captured September 19, 20261,605
MassachusettsRegistered — not yet loaded
MichiganRegistered — not yet loaded
MinnesotaNot yet loaded
MississippiLoaded · captured September 19, 2026193
MissouriRegistered — not yet loaded
MontanaLoaded · captured September 19, 2026175
NebraskaNot yet loaded
NevadaNot yet loaded
New HampshireLoaded · captured September 19, 202676
New JerseyNot yet loaded
New MexicoNot yet loaded
New YorkLoaded · captured September 19, 20268,916
North CarolinaLoaded · captured September 19, 2026166
North DakotaLoaded · captured September 19, 2026195
OhioLoaded · captured September 19, 20261,980
OklahomaNot yet loaded
OregonNot yet loaded
PennsylvaniaLoaded · captured September 19, 20266,707
Rhode IslandNot yet loaded
South CarolinaRegistered — not yet loaded
South DakotaNot yet loaded
TennesseeLoaded · captured September 19, 202621
TexasNot yet loaded
UtahNot yet loaded
VermontNot yet loaded
VirginiaNot yet loaded
WashingtonLoaded · captured September 19, 2026244
West VirginiaNot yet loaded
WisconsinNot yet loaded
WyomingNot yet loaded

13 of 51 jurisdictions loaded; 22 have registered source modules. States publish exclusion lists in different formats and cadences, so onboarding is per-source; the federal OIG LEIE applies in every state regardless of this table.

Common questions

Is the federal OIG LEIE the same as a state Medicaid exclusion list?
No. The OIG LEIE lists providers excluded from federal health programs (Medicare, Medicaid, and others). Each state Medicaid program also maintains its own exclusion list. The lists overlap but are not identical — a provider excluded by a state can be absent from the federal LEIE, and vice versa. A complete screen checks both.
What does 'excluded anywhere' mean?
On Fonteum, an 'excluded anywhere' check looks across the federal LEIE and 13 state Medicaid jurisdictions represented as of September 19, 2026: Georgia, Iowa, Maryland, Mississippi, Montana, North Carolina, North Dakota, New Hampshire, New York, Ohio, Pennsylvania, Tennessee, and Washington. It is not a nationwide state-list check. Because many state-excluded providers do not appear on the federal LEIE, a federal-only check can miss a state record.
Which states does Fonteum cover today?
Fonteum currently holds state Medicaid exclusion data for 13 state Medicaid jurisdictions represented as of September 19, 2026: Georgia, Iowa, Maryland, Mississippi, Montana, North Carolina, North Dakota, New Hampshire, New York, Ohio, Pennsylvania, Tennessee, and Washington. Other states are not represented as covered; each loaded state page is source-traced to the publishing agency, and the dated row count appears on this page.
Is this a determination that a provider is excluded?
No. Fonteum mirrors the published exclusion lists as a screening aid. Reinstatements and corrections can lag, and matching is by NPI where present. Always cross-check a specific record against the publishing agency before acting on it.

Scope and limitations

  • Screening aid, not a determination. Fonteum mirrors the published exclusion lists; it does not adjudicate exclusions.
  • Reinstatements and corrections can lag the published file. Cross-check any single record against the publishing agency before acting on it.
  • Federal/state overlap is matched by NPI. Records without an NPI are counted in the totals but cannot be cross-matched.
  • State coverage is limited to GA, IA, MD, MS, MT, NC, ND, NH, NY, OH, PA, TN, and WA. Absence of a state here does not imply a provider has no active match in that state.
Reviewed by Jennifer Montecillo, MD, medical reviewer. Non-practicing medical reviewer.About our reviewers →

What’s on file, by the numbers

Platform snapshot · 2026-09-19

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
9fresh 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