Skip to content
FonteumPublic-records evidence
FINANCIAL DISTRESS · ISSUE 054
oig-leieOriginal Research

State Medicaid Exclusion Lists vs the Federal LEIE: The Gap

In the July 14, 2026 production observation, 3,188 of 4,949 NPI-identified providers excluded across 13 state Medicaid programs — 64.4% — carried no record on the federal OIG LEIE. Another 15,487 in-force state exclusion records had no NPI and could not be matched to the federal list by identifier.

BY FONTEUM LLC · JUNE 15, 2026 · 9 MIN READREVIEWED BY DR. JENNIFER MONTECILLO, MDSNAPSHOT 2026-07-14 · LAST UPDATED JULY 14, 2026
OIG LEIE · 2026-07-14
Share of state Medicaid exclusions invisible to federal screeningstate-exclusions · 2026-07
TN
88.9
NC
85.9
WA
84.8
IA
84
MD
84.1
MS
76.8
NH
72.5
NY
59.8
ND
59.6
PA
58.4
OH
53.9
MT
38.1
GA
22.9
Built on OIG LEIE · snapshot 2026-07-14 · reproducible · re-derive the figures yourself
Key findings
of NPI-identified providers excluded by a state Medicaid program (3,188 of 4,949) carry no record on the federal OIG LEIE
state-exclusions · CMS
state-excluded providers in the July 14, 2026 13-state production observation with no OIG LEIE record
state-exclusions · CMS
New York's invisibility share — 1,352 of 2,259 NPI-identified state-excluded providers are absent from the federal LEIE
state-exclusions · CMS
additional in-force state exclusion records carry no NPI at all — unmatchable to the federal list by identifier, reported separately
state-exclusions · CMS

The OIG List of Excluded Individuals and Entities — the LEIE — is the federal registry that screening programs treat as the master list of providers barred from Medicare, Medicaid, and other federal health programs. But it is not the only list. Every state Medicaid agency runs its own exclusion program, on its own authority and its own clock. When the two lists disagree, the disagreement is the story: a provider barred by a state but absent from the federal file is invisible to anyone who screens federally and stops there.

This study quantifies that gap from production as observed July 14, 2026. The query joins Medicaid exclusion lists from 13 states against the federal OIG LEIE on the National Provider Identifier; the underlying state table contains 22,917 raw records.

The gap, in one number

In the July 14 observation, 64.4% of NPI-identified state-excluded providers were missing from the federal list: 3,188 of 4,949 across the 13 states carried no matching OIG LEIE record. Put the other way, the join found an OIG record for 1,761 of the 4,949.

The breakdown by state shows the pattern is not a single-state artifact. The three largest-sample states sit between 54% and 60%; the newer, smaller-sample states run higher still, and only Georgia and Montana — on very small matchable samples — come in lower.

StateNPI-identified state-excludedNot on federal LEIEOn both listsShare invisible to federal screening
New York (OMIG)2,2591,35290759.8%
Pennsylvania (DHS)97356840558.4%
Ohio (ODM)67336331053.9%
Iowa (Medicaid)3132635084.0%
Maryland (MDH)2642224284.1%
Washington (HCA)2101783284.8%
North Carolina (DHHS)1491282185.9%
Mississippi (DOM)1381063276.8%
New Hampshire (DHHS)51371472.5%
North Dakota (HHS)47281959.6%
Montana (DPHHS)42162638.1%
Georgia (DCH-OIG)3582722.9%
Tennessee (TennCare)98188.9%
All 13 states4,9493,1881,76164.4%

The denominator throughout is NPI-identified, in-force state exclusions. A state exclusion counts as in force when it carries no reinstatement date, or a reinstatement date still in the future — the same test the federal side uses. The join is on NPI only, never on name.

Why federal-only screening misses these providers

The gap is structural, not a data error. State Medicaid agencies exclude providers under state authority for Medicaid-specific reasons, and a federal exclusion does not automatically follow. The OIG may adopt a state action under its permissive §1128(b) authority — most commonly §1128(b)(4) for a state license revocation, surrender, or suspension — but that adoption is discretionary and lagged. Many state bars never cross over at all, and those that do can take months to a year to appear on the federal file.

A second mechanism is timing. An exclusion is a trailing record on both sides, but the two trailing records do not move together. A provider can be terminated from a state Medicaid program well before — or entirely without — a parallel federal action. The federal CCN- and enrollment-side machinery moves on its own cadence, a pattern we documented in the lag between a termination event and CMS deactivation.

An exclusion is only as good as the list you check. Screen the federal LEIE alone and nearly two in three NPI-identified state-barred providers come back clean.

The companion fact from the federal side reinforces the point. As we found in who actually gets barred from Medicare and why, the single largest basis on the federal LEIE is itself a downstream record of state licensing discipline — §1128(b)(4) license actions are 41% of the list. The federal file is, in large part, a lagging echo of state decisions. The state lists are where many of those decisions land first.

How the gap differs by state

New York sets the ceiling among the large-sample states: 1,352 of its 2,259 NPI-identified state-excluded providers — 59.8% — have no federal record. Pennsylvania (58.4%) and Ohio (53.9%) follow closely. These three states carry the bulk of the matchable population and agree within six points, which is what gives the pooled 64.4% figure its weight: it is not the artifact of one outlier.

The newer states ingested into the ring push the pooled figure higher. Iowa, Maryland, Washington, North Carolina, and Mississippi all sit between 77% and 86% invisible — every one a clear majority — though each rests on a smaller matchable sample than the three anchor states. The direction is consistent across every state with a meaningful denominator: a majority of NPI-identified state bars have no federal counterpart.

Georgia's 22.9% and Montana's 38.1% sit apart because their matchable samples are tiny — only 35 of Georgia's 1,369 in-force records, and 42 of Montana's 175, carry an NPI. With denominators that small, the percentages are unstable and should be read as illustrative, not as evidence that those states' providers are better represented federally.

The July 14 study ring spans 13 states, from New York's 2,259 NPI-identified providers down to Tennessee's nine. It remains a loaded-coverage result, not a national estimate.

The providers with no NPI at all

In the July 14 observation, 15,487 in-force state exclusion records carried no NPI. Across the 13 states, 4,949 distinct NPIs sat inside 21,003 in-force records; the remainder named an excluded party with no identifier that maps to the federal list.

StateIn-force recordsWith no NPIDistinct NPI-identified providers
New York8,9166,6402,259
Pennsylvania4,9143,714973
Ohio1,9801,248673
Maryland1,6051,340264
Georgia1,3691,33335
Iowa1,149794313
Washington24434210
Mississippi19353138
New Hampshire762551
North Dakota19514847
Montana17513242
North Carolina16614149
Tennessee21129
All 13 states21,00315,4874,949

These records are excluded from the matchable denominator above, because matching them to the federal list would require a name match — and a name match is not a defensible identity assertion. We do not guess. But the practical implication is blunt: NPI-based federal screening cannot reach these parties at all, so they compound the gap rather than shrink it. The same limitation applies in reverse, and it is the reason the federal LEIE itself carries an NPI on only about one record in ten, as documented in the LEIE reference study.

What this means for screening compliance

A federal-LEIE-only screen is not a complete exclusion check, and the magnitude here puts a number on the shortfall: 64.4% of NPI-identified state-barred providers fall outside it. The OIG's own guidance is that a billing organization or contractor must screen against all applicable exclusion lists — federal and the relevant state Medicaid lists — before submitting claims or contracting, and on an ongoing basis. Billing for or contracting an excluded party in a federally billable role carries civil monetary penalty exposure under a "knew or should have known" standard.

The constructive read is that the two layers of lists do something neither does alone. The federal LEIE is national but lagging and NPI-sparse; the state lists are current and program-specific but jurisdictionally fragmented. Checked together, across frozen point-in-time snapshots, they close gaps in each other. Fonteum exposes both layers through a single NPI lookup — the state exclusion data and the federal OIG LEIE — so a "barred anywhere on the lists we hold" answer does not depend on which single list a screener happened to check. It is a screening aid: re-confirm any match against the primary source before acting. An absence becomes a no-match only when serving coverage reconciles to the latest comparable attested artifact; otherwise it is indeterminate and is not a clearance.

Methodology

Every figure is a direct join against two public, read-only Postgres tables as observed July 14, 2026: state_exclusions (22,917 raw records across 13 state Medicaid programs) and oig_leie_exclusions (the OIG monthly LEIE bulk download, release 2026-05-08, 68,055 records). The join key is the 10-digit NPI, trimmed of whitespace; a name is never used to assert a match.

A record is treated as in force when its reinstatement date is null or still in the future relative to the publish date — the same test the production exclusion lookup applies, and applied identically to both tables. The matchable denominator is the set of distinct, in-force, NPI-identified providers per state; records with no NPI are excluded from it and reported separately. The federally-invisible count is the subset of those NPIs with no row in oig_leie_exclusions. The exact SQL is in the reproducibility block below and the provenance methodology documents the source-provenance contract. Methodology version: exclusion-gap/v1.

Limitations

  • Thirteen-state loaded coverage, not national coverage. The 64.4% figure describes the 13 state programs loaded in production on July 14, not all state Medicaid programs.
  • NPI is the floor, not the ceiling. 15,487 in-force state records carry no NPI and cannot be matched to the federal list by identifier; they are reported separately, never guessed at by name.
  • Snapshot, not cumulative. Both lists are point-in-time. These figures reflect production as observed July 14, 2026.
  • Some states are small samples. Tennessee, Georgia, and Montana carry only 9, 35, and 42 NPI-identified records, so their per-state shares are illustrative, not stable; the newer mid-size states rest on smaller denominators than the three anchor states.
  • A compliance signal, aggregate-only. Exclusion counts are an enforcement and screening signal, never a measure of care quality. No individual excluded party is named, surfaced, or attached to any provider profile in this study.

Sources

Frequently asked questions

What is the federal–state exclusion gap?
It is the share of providers excluded by a state Medicaid program that carry no matching record on the federal OIG List of Excluded Individuals and Entities (LEIE). In the July 14, 2026 production observation, 3,188 of 4,949 NPI-identified state-excluded providers — 64.4% — were absent from the federal list.
Why would a provider be excluded by a state but not by the federal OIG?
State Medicaid agencies run their own exclusion programs and act on their own authority and timeline. A state can bar a provider for a Medicaid-specific reason — a state license action, a state fraud referral, an administrative termination — without an OIG exclusion ever following. The OIG can adopt many of these under its permissive §1128(b) authority, but adoption is discretionary and lagged, so a large standing set of state bars never reaches the federal list.
How many state-excluded providers does federal-only screening miss?
Among providers with an NPI in the July 14, 2026 13-state production observation, 3,188 of 4,949 — 64.4% — had no OIG LEIE record. New York accounted for 1,352 of them, Pennsylvania 568, and Ohio 363.
Does the gap change if you count federal exclusions that were later reinstated?
No. The OIG removes reinstated parties from the published LEIE, so the federal file is already a current-active snapshot. The 64.4% figure is identical whether or not an in-force filter is applied on the federal side.
What about state exclusions with no NPI?
A further 15,487 in-force state exclusion records carry no NPI at all. They cannot be matched to the federal list by identifier, so NPI-based federal screening cannot reach them either. They are excluded from the matchable denominator and reported separately rather than guessed at by name.
Which states are included, and why not all 50?
The July 14, 2026 observation includes New York, Ohio, Georgia, Pennsylvania, North Carolina, Maryland, Washington, Iowa, Mississippi, Montana, New Hampshire, North Dakota, and Tennessee. Production contains 22,917 raw records across those 13 states.
Can I reproduce these numbers?
Yes. Every figure is a direct join between the public state_exclusions and oig_leie_exclusions tables on NPI. The exact SQL is published in the reproducibility block below; each count resolves to specific rows in specific frozen snapshots, and no match is ever inferred from a name.

Who uses this data

The source data behind this study is public

Compliance teams, journalists, and researchers work from the same federal source families cited above — queried by NPI or facility identifier through Fonteum’s open dataset pages and API. Every figure traces to a frozen, downloadable snapshot you can reproduce yourself.

Datasets used

Reproducibility

Every claim, reproducible

The SQL
federal-state-exclusion-gap-2026.sql
-- The federal–state exclusion gap — fully reproducible query.
--
-- Question: how many providers excluded by a STATE Medicaid program are
-- invisible to FEDERAL-only screening — i.e. carry no record on the OIG LEIE?
--
-- Sources:
--   public.state_exclusions    — State Medicaid exclusion lists (13 loaded
--                                states as observed 2026-07-14).
--                                Public, read-only.
--   public.oig_leie_exclusions — OIG List of Excluded Individuals/Entities,
--                                federal monthly bulk download, release
--                                2026-05-08, 68,055 active records (7,025 with
--                                an NPI). Public, read-only.
--
-- Join key: NPI only (10-digit, btrim). We never match on name — a name match
-- is not a defensible identity assertion, so rows with no NPI are excluded from
-- the matchable denominator and reported separately (see no-NPI query below).
--
-- "In force" mirrors the production exclusion lookup (src/lib/exclusions): a row
-- is in force when reinstatement_date IS NULL OR reinstatement_date > today.
-- Applied to BOTH tables. Audit date basis: DATE '2026-07-14'.
--
-- Every headline figure in the study resolves to one of the rows below.

-- audit-claim: federal-gap-vector
WITH se_inforce AS (
  SELECT state,
         nullif(btrim(npi), '') AS npi
  FROM public.state_exclusions
  WHERE reinstatement_date IS NULL OR reinstatement_date > DATE '2026-07-14'
),
fed_inforce AS (
  -- Distinct federal NPIs in force. (The LEIE drops reinstated parties from the
  -- published file, so this set equals "any LEIE row by NPI" — the 64.4% gap is
  -- identical whether or not the in-force filter is applied on the federal side.)
  SELECT DISTINCT btrim(npi) AS npi
  FROM public.oig_leie_exclusions
  WHERE nullif(btrim(npi), '') IS NOT NULL
    AND (reinstatement_date IS NULL OR reinstatement_date > DATE '2026-07-14')
),
state_npi AS (              -- distinct NPI-identified, in-force provider per state
  SELECT DISTINCT state, npi FROM se_inforce WHERE npi IS NOT NULL
),
per_state AS (
  SELECT s.state,
         count(*)                                     AS matchable_providers,
         count(*) FILTER (WHERE f.npi IS NULL)        AS federally_invisible
  FROM state_npi s
  LEFT JOIN fed_inforce f USING (npi)
  GROUP BY s.state
),
overall_npi AS ( SELECT DISTINCT npi FROM se_inforce WHERE npi IS NOT NULL ),
overall AS (
  SELECT 'ALL'::text                                  AS state,
         count(*)                                     AS matchable_providers,
         count(*) FILTER (WHERE f.npi IS NULL)        AS federally_invisible
  FROM overall_npi o
  LEFT JOIN fed_inforce f USING (npi)
),
u AS ( SELECT * FROM per_state UNION ALL SELECT * FROM overall )
SELECT
  state,
  matchable_providers,                                              -- NPI-identified denominator
  federally_invisible,                                             -- NOT on the federal LEIE
  (matchable_providers - federally_invisible) AS on_federal_too,   -- caught by both
  round(100.0 * federally_invisible / nullif(matchable_providers, 0), 1)
                                              AS pct_invisible
FROM u
ORDER BY state;
--  state  matchable  invisible  on_federal_too  pct_invisible
--  ALL      4,949      3,188        1,761          64.4
--  NY       2,259      1,352          907          59.8
--  PA         973        568          405          58.4
--  OH         673        363          310          53.9
--  IA         313        263           50          84.0
--  MD         264        222           42          84.1
--  WA         210        178           32          84.8
--  NC         149        128           21          85.9
--  MS         138        106           32          76.8
--  NH          51         37           14          72.5
--  ND          47         28           19          59.6
--  MT          42         16           26          38.1   (small sample — see study)
--  GA          35          8           27          22.9   (small sample — see study)
--  TN           9          8            1          88.9   (small sample — see study)

-- Rows with NO NPI — excluded from the matchable denominator above and reported
-- separately. These in-force state exclusions cannot be matched to the federal
-- list by identifier at all, so federal NPI-based screening cannot reach them.
-- audit-claim: state-record-vector
SELECT
  coalesce(state, 'ALL')                                          AS state,
  count(*) FILTER (WHERE inforce)                                 AS inforce_rows,
  count(*) FILTER (WHERE inforce AND npi IS NULL)                 AS inforce_no_npi_rows,
  count(DISTINCT npi) FILTER (WHERE inforce AND npi IS NOT NULL)  AS inforce_distinct_npi
FROM (
  SELECT state,
         nullif(btrim(npi), '') AS npi,
         (reinstatement_date IS NULL OR reinstatement_date > DATE '2026-07-14') AS inforce
  FROM public.state_exclusions
) se
GROUP BY ROLLUP (state)
ORDER BY state NULLS LAST;
--  state  inforce_rows  inforce_no_npi_rows  inforce_distinct_npi
--  NY        8,916           6,640              2,259
--  PA        4,914           3,714                973
--  OH        1,980           1,248                673
--  MD        1,605           1,340                264
--  GA        1,369           1,333                 35
--  IA        1,149             794                313
--  WA          244              34                210
--  MS          193              53                138
--  NH           76              25                 51
--  ND          195             148                 47
--  MT          175             132                 42
--  NC          166              14                149
--  TN           21              12                  9
--  ALL      21,003          15,487              4,949

-- Raw source universes. These totals are deliberately separate from the
-- in-force, NPI-identified denominator above.
-- audit-claim: source-universes
SELECT
  (SELECT count(*) FROM public.state_exclusions) AS state_rows,
  (SELECT count(DISTINCT state) FROM public.state_exclusions) AS states,
  (SELECT count(*) FROM public.oig_leie_exclusions) AS leie_rows,
  (SELECT count(*) FROM public.oig_leie_exclusions
    WHERE nullif(btrim(npi), '') IS NOT NULL) AS leie_rows_with_npi;
-- state_rows 22,917 · states 13 · leie_rows 68,055 · leie_rows_with_npi 7,025
The snapshot
dataset_idstate-exclusions
snapshot_date2026-07-14
The JOINs
join key: state_exclusions.npi = oig_leie_exclusions.npi  -- 10-digit NPI, btrim, never a name match
in_force = reinstatement_date IS NULL OR reinstatement_date > DATE '2026-07-14'  -- applied to both tables
matchable = distinct in-force state NPI (non-empty); rows with no NPI excluded and reported separately
federally_invisible = matchable NPI with NO row in oig_leie_exclusions on the same NPI
share = federally_invisible / matchable  -- 3,188 / 4,949 = 64.4%
The pipeline version
methodology_versionexclusion-gap/v1

Reproduce this

Run the exact query against the frozen 2026-07-14.

-- The federal–state exclusion gap — fully reproducible query. -- -- Question: how many providers excluded by a STATE Medicaid program are -- invisible to FEDERAL-only screening — i.e. carry no record on the OIG LEIE? -- -- Sources: -- public.state_exclusions — State Medicaid exclusion lists (13 loaded -- states as observed 2026-07-14). -- Public, read-only. -- public.oig_leie_exclusions — OIG List of Excluded Individuals/Entities, -- federal monthly bulk download, release -- 2026-05-08, 68,055 active records (7,025 with -- an NPI). Public, read-only. -- -- Join key: NPI only (10-digit, btrim). We never match on name — a name match -- is not a defensible identity assertion, so rows with no NPI are excluded from -- the matchable denominator and reported separately (see no-NPI query below). -- -- "In force" mirrors the production exclusion lookup (src/lib/exclusions): a row -- is in force when reinstatement_date IS NULL OR reinstatement_date > today. -- Applied to BOTH tables. Audit date basis: DATE '2026-07-14'. -- -- Every headline figure in the study resolves to one of the rows below. -- audit-claim: federal-gap-vector WITH se_inforce AS ( SELECT state, nullif(btrim(npi), '') AS npi FROM public.state_exclusions WHERE reinstatement_date IS NULL OR reinstatement_date > DATE '2026-07-14' ), fed_inforce AS ( -- Distinct federal NPIs in force. (The LEIE drops reinstated parties from the -- published file, so this set equals "any LEIE row by NPI" — the 64.4% gap is -- identical whether or not the in-force filter is applied on the federal side.) SELECT DISTINCT btrim(npi) AS npi FROM public.oig_leie_exclusions WHERE nullif(btrim(npi), '') IS NOT NULL AND (reinstatement_date IS NULL OR reinstatement_date > DATE '2026-07-14') ), state_npi AS ( -- distinct NPI-identified, in-force provider per state SELECT DISTINCT state, npi FROM se_inforce WHERE npi IS NOT NULL ), per_state AS ( SELECT s.state, count(*) AS matchable_providers, count(*) FILTER (WHERE f.npi IS NULL) AS federally_invisible FROM state_npi s LEFT JOIN fed_inforce f USING (npi) GROUP BY s.state ), overall_npi AS ( SELECT DISTINCT npi FROM se_inforce WHERE npi IS NOT NULL ), overall AS ( SELECT 'ALL'::text AS state, count(*) AS matchable_providers, count(*) FILTER (WHERE f.npi IS NULL) AS federally_invisible FROM overall_npi o LEFT JOIN fed_inforce f USING (npi) ), u AS ( SELECT * FROM per_state UNION ALL SELECT * FROM overall ) SELECT state, matchable_providers, -- NPI-identified denominator federally_invisible, -- NOT on the federal LEIE (matchable_providers - federally_invisible) AS on_federal_too, -- caught by both round(100.0 * federally_invisible / nullif(matchable_providers, 0), 1) AS pct_invisible FROM u ORDER BY state; -- state matchable invisible on_federal_too pct_invisible -- ALL 4,949 3,188 1,761 64.4 -- NY 2,259 1,352 907 59.8 -- PA 973 568 405 58.4 -- OH 673 363 310 53.9 -- IA 313 263 50 84.0 -- MD 264 222 42 84.1 -- WA 210 178 32 84.8 -- NC 149 128 21 85.9 -- MS 138 106 32 76.8 -- NH 51 37 14 72.5 -- ND 47 28 19 59.6 -- MT 42 16 26 38.1 (small sample — see study) -- GA 35 8 27 22.9 (small sample — see study) -- TN 9 8 1 88.9 (small sample — see study) -- Rows with NO NPI — excluded from the matchable denominator above and reported -- separately. These in-force state exclusions cannot be matched to the federal -- list by identifier at all, so federal NPI-based screening cannot reach them. -- audit-claim: state-record-vector SELECT coalesce(state, 'ALL') AS state, count(*) FILTER (WHERE inforce) AS inforce_rows, count(*) FILTER (WHERE inforce AND npi IS NULL) AS inforce_no_npi_rows, count(DISTINCT npi) FILTER (WHERE inforce AND npi IS NOT NULL) AS inforce_distinct_npi FROM ( SELECT state, nullif(btrim(npi), '') AS npi, (reinstatement_date IS NULL OR reinstatement_date > DATE '2026-07-14') AS inforce FROM public.state_exclusions ) se GROUP BY ROLLUP (state) ORDER BY state NULLS LAST; -- state inforce_rows inforce_no_npi_rows inforce_distinct_npi -- NY 8,916 6,640 2,259 -- PA 4,914 3,714 973 -- OH 1,980 1,248 673 -- MD 1,605 1,340 264 -- GA 1,369 1,333 35 -- IA 1,149 794 313 -- WA 244 34 210 -- MS 193 53 138 -- NH 76 25 51 -- ND 195 148 47 -- MT 175 132 42 -- NC 166 14 149 -- TN 21 12 9 -- ALL 21,003 15,487 4,949 -- Raw source universes. These totals are deliberately separate from the -- in-force, NPI-identified denominator above. -- audit-claim: source-universes SELECT (SELECT count(*) FROM public.state_exclusions) AS state_rows, (SELECT count(DISTINCT state) FROM public.state_exclusions) AS states, (SELECT count(*) FROM public.oig_leie_exclusions) AS leie_rows, (SELECT count(*) FROM public.oig_leie_exclusions WHERE nullif(btrim(npi), '') IS NOT NULL) AS leie_rows_with_npi; -- state_rows 22,917 · states 13 · leie_rows 68,055 · leie_rows_with_npi 7,025

Download the data: SQL · JSON · CSV

Cite this study

Citation-ready for researchers and AI.

Fonteum Research Bureau (2026). State Medicaid Exclusion Lists vs the Federal LEIE: The Gap. OIG LEIE, snapshot 2026-07-14. https://fonteum.com/research/federal-state-exclusion-gap-2026

Check the chain

The cited snapshot identifies the federal file. Where an attestation is present, its file hash can be re-derived; figures are not individually signed.

1
Snapshot
state-exclusions · 2026-07-14
2
Supplied file hash
Not supplied
3
Snapshot attestation
Inspect supplied artifact
Figures are not individually signed · check it in Attest →

Federal source citations

  1. OIG LEIE · snapshot 2026-07-14 · federal source family · US-Government-Works

Fonteum LLC · June 15, 2026 · All figures trace to the frozen federal-data snapshot cited above.

What’s on file, by the numbers

Platform snapshot · 2026-07-30

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