A payer compliance team reviewing a network exclusion-screening dashboard across Medicare Advantage and Medicaid lines
CASE STUDY

Health plan automates roster sanction checks

Sep 11, 2026· 6 min read ·Compliance ·NPI Data Services

Illustrative composite — anonymized; not a named customer. Metrics are realistic modeled outcomes, not a guarantee.

Health Plan Sanction Screening: A Roster Case Study

Most compliance programs fail at exclusion screening for the same undramatic reason: the calendar. CMS tells Medicare Advantage and Part D sponsors to check their people and their downstream entities against federal exclusion lists before a contract begins and every month after (42 CFR Part 422; CMS Managed Care Manual, Ch. 21). The OIG refreshes the List of Excluded Individuals and Entities monthly (OIG Exclusions Program). But most payers run a quarterly batch and lean on annual attestations from their delegated groups. That mismatch — a monthly duty answered on a quarterly clock — is where the exposure lives.

Here is how a mid-sized regional health plan rebuilt its health plan sanction screening so the gap between the deadline and the check stopped being a quarter wide.

The problem: a monthly rule met on a quarterly clock

Call the payer Cascade Health Plan (a composite). Cascade runs a Medicare Advantage line and a Medicaid managed care contract across three states, with a network of roughly 28,000 contracted providers plus its own staff, board members, and a chain of first-tier, downstream, and related entities (FDRs) — delegated medical groups, a pharmacy benefit manager, and a claims vendor.

Its screening looked like most payers' does before they rebuild it. A compliance analyst exported the network roster and searched names against the OIG's online exclusions database once a quarter; SAM.gov and a couple of the largest state Medicaid lists were checked the same way, by hand; and FDRs were asked to screen their own people and send back an attestation once a year.

Three problems were baked into that, and none of them were the analyst's fault.

The cadence didn't match the rule. A provider excluded in February could sit undetected until the April batch — two months of care delivered and claims paid. CMS treats skipping a monthly cycle as the violation, whether or not anyone excluded turns up that month. (We walk through exactly why an annual or quarterly rhythm falls short in why monthly exclusion screening beats an annual check.)

The FDR layer was a blind spot. CMS makes the sponsor responsible for confirming its downstream entities screen on the same schedule — and liability does not transfer with an attestation. A once-a-year signature from a delegated group said nothing about the biller it hired in March.

The state coverage was partial. Because Medicaid is administered state by state, a provider reinstated federally can stay barred on a single state's list. Checking two of three states by hand left a real hole on the Medicaid line.

The stakes are not theoretical. An exclusion is a payment prohibition: no federal program will pay for any item or service an excluded person furnishes, orders, or prescribes, directly or through a delegated network (OIG background). On top of repaying every tainted dollar, the OIG can assess civil monetary penalties of up to roughly $20,000 per item or service (a base figure before annual inflation adjustment) plus treble the amount claimed (42 CFR Part 1003) — imposed directly on the contracting organization. In May 2025, 19 skilled nursing facilities paid a combined $1,565,374.11 to settle OIG allegations that they employed people they should have known were excluded (HHS-OIG, May 29, 2025). At a payer's claim volume, where one excluded group can generate thousands of separately countable penalties, that arithmetic runs far higher.

The solution: one continuous roster for the whole network

Cascade moved its network, its staff, and its FDR chain onto a single continuously monitored roster with exclusion screening for health plans. The workflow change was small; the operational change was not.

  1. One roster, every party. Contracted providers, delegated groups, the PBM, the claims vendor, employees, and board members went onto the same list — so the FDR layer was watched on the identical monthly schedule instead of self-reported once a year.
  2. Continuous re-screening. Every name is re-checked on each source refresh, and a newly contracted provider is screened the day it is added — which is what "before a contract begins, then monthly" actually requires, without a manual batch job.
  3. Beyond the LEIE. The same roster is diffed against 50+ federal and state sources — SAM.gov, OFAC, the Medicare Opt-Out list, the CMS Preclusion inputs, and every state Medicaid exclusion list — which is the point of true healthcare sanctions screening: the LEIE is the floor, not the ceiling, and a payer whose entire book is government-funded care needs all-state coverage as a baseline.
  4. Match carefully, verify before acting. Matching runs on the full identifier set together — NPI, name, city, state, ZIP — never one field alone, with a name-plus-location fallback when a source record carries no NPI. Every possible match is surfaced with its source record for a human to confirm; nobody is auto-flagged.

The result

The goal was to make screening genuinely monthly and stop spending compliance days on manual searches.

Measure Before (manual) After (continuous)
Screening cadence Quarterly batch Every OIG / source refresh
FDR / downstream coverage Annual attestation On the same monthly roster
Sources checked OIG LEIE + partial states 50+ federal & all-state
Analyst time per cycle Days of manual searching Review-only: a few hours
Detection lag on a new exclusion Up to ~3 months Same-cycle alert
Proof for a CMS program audit Screenshots Time-stamped screening log

The measurable win: quarterly days of hand-searching collapsed to a few hours of reviewing and verifying flagged matches — on the order of an 85–90% reduction in hands-on screening time, with the FDR chain finally covered on the same clock as everyone else.

The result that mattered more never showed up on a timesheet. Within the first months on continuous monitoring, an alert surfaced a clinician inside a delegated medical group who had been newly excluded mid-quarter — exactly the case the old quarterly-plus-annual-attestation process would have missed until claims had already gone out. Cascade paused claims tied to that provider, notified the delegated group, and kept a clean claim stream. Under the old process, that is a stack of non-payable claims and a hard question at the next program audit.

What a payer should take from this

  • Match the cadence to the rule. The obligation is monthly and continuous; a quarterly batch builds in a detection lag CMS treats as the violation.
  • Screen the whole chain. FDRs are the sponsor's exposure, and an annual attestation is not a substitute for confirming the downstream check happened.
  • All-state Medicaid is the floor. Federal reinstatement doesn't clear a state bar; a government-funded book needs every state list, every cycle.
  • Keep the evidence, verify before acting. A time-stamped log is your good-faith proof at audit — and a name match is a lead to confirm, never a verdict.

Provider Signals is not a consumer reporting agency and this is not FCRA-regulated data; nothing here is legal advice. NPI Data Services is not affiliated with or endorsed by any government agency.

Stop answering a monthly rule on a quarterly clock. Start screening free and monitor your entire network — providers, staff, and FDRs — against the OIG LEIE and 50+ federal and state sanction lists, continuously.

Related posts

Compliance

Nursing Home Exclusion Screening Avoids a CMP

How a five-building skilled-nursing group replaced a once-a-year LEIE check with monthly nursing home exclusion screening — and caught an excluded aide before payroll did.

Aug 14, 2026 · 6 min read