LEIE Overlay

HHS OIG List of Excluded Individuals/Entities (LEIE) matches overlaid onto CMS Medicare Physician PUF utilization rows, joined on normalized NPI only. A match is a sanctioned-list flag / investigative lead for further review — not proof that a utilization row is improper, and not an accusation. Public data only (no PHI).

Payment construct: Utilization payment is the sum of line-level Medicare payment (Avg_Mdcr_Pymt_Amt × Tot_Srvcs at provider×HCPCS) for that NPI × service year.

Attribution: CMS Medicare Physician PUF + HHS OIG LEIE.

LEIE × utilization rows

846

Distinct NPIs

443

Sum payment (all years)

$118,390,529

CA/MN rows

120

Overlay by service year

Loading...
No Results

By state (latest service year)

Loading...

California & Minnesota

No Results

Highest-payment LEIE matches (latest year)

No Results

NPI coverage of the exclusion list

This overlay can only see LEIE entries that carry an NPI. Many excluded parties — especially older exclusions (NPIs became mandatory in 2007–2008) and many non-physician individuals — are listed without one, so the match counts above are a floor, not a complete count of excluded parties appearing in Medicare data. Name-only matching is intentionally not used.

LEIE records with an NPI

10.6%
Big Value
error

Excluded 2008+ with an NPI

18.2%

Of 84,093 LEIE records, 8,924 ( 10.6% ) have a usable NPI ( 8,743 distinct NPIs). Among currently excluded parties (no reinstatement or waiver date) the share is error ; the OIG file lists only current exclusions, so these are nearly identical. For exclusions dated 2008 or later it is 18.2% .

No Results

Soft methodology

Item Detail
Join Normalized 10-digit NPI only (name-only matches unused)
NPI coverage Only LEIE entries with an NPI can match — see coverage share above; overlay counts are a floor
Sources CMS Physician PUF utilization × OIG LEIE
Framing Sanctioned-list overlay / investigative lead — not a finding about billing propriety
Timing Exclusion date may fall after or before the service year; interpret carefully