Exclusion screening: the obligation is the evidence.

Exclusion screening is one of the few compliance activities where doing the work and being able to prove the work are almost entirely separate problems — and where the second one is what gets examined.

What the OIG actually recommends

In its Special Advisory Bulletin on the Effect of Exclusion from Participation in Federal Health Care Programs (May 2013), the OIG advises providers to screen employees and contractors against the List of Excluded Individuals/Entities, and states that checking the LEIE monthly best minimizes potential overpayment and civil monetary penalty liability.

Note the framing, because it is regularly misquoted in both directions. It is guidance on limiting exposure, not a blanket federal mandate that every provider screen monthly. It is also not merely a suggestion to be dismissed — it is the agency's stated view of what reduces your liability, which is exactly what gets cited when liability is being discussed.

The monthly cadence has a mechanical explanation worth knowing: the LEIE is updated monthly. Screening more often than the source changes generates records without generating protection.

Your own obligations may be stricter. State Medicaid agencies, your contracts and your own compliance program can each require a shorter interval or a wider scope, and those are the terms that actually bind you.

Which lists

• OIG LEIE — the federal exclusion list, searchable online and available as a downloadable file.
• SAM.gov — federal exclusion records covering a broader set of actions, including debarments that never appear on the LEIE.
• Applicable state or territorial lists — the ones most often screened once during implementation and then quietly dropped.

Scope is where programs actually fail

Almost every center screens its clinical providers. Fewer screen every employee. Fewer still screen the relationships through which an exclusion most often reaches an organization:

• Contracted vendors and their personnel
• Locum and temporary coverage
• Billing services and other administrative contractors
• Board members
• Anyone whose salary or services are paid, directly or indirectly, by a federal health care program

Scope should be written down and defended rather than assumed. “We screen everyone” is not a scope statement; it is a belief about a scope statement, and the two diverge the first time someone is onboarded through a route nobody mapped.

A name match is not an identification

The LEIE contains common names. A hit is a lead requiring resolution, not a finding. Resolution means comparing identifying details against the excluded party's record and reaching a documented conclusion — and the conclusion needs a person's name on it, because “the system cleared it” is not a determination anyone can defend.

The corollary matters just as much: a screening that returns nothing still needs a record. The absence of a hit is the result you will be asked to demonstrate, and it is the one most often not kept.

What a defensible record looks like

Treat the run as the unit, not the person. A screening run should record:

• The roster as it stood — who was in scope that month, not who is in scope now.
• Which lists were queried, and when.
• Every result, including the clean ones.
• Each hit's disposition, the reasoning, and the name of the person who made it.

The test to apply to your own program is simple and slightly uncomfortable: can you produce last December's run today? Not the current list — the run as it stood then. If producing it means re-screening today's roster against today's list, you do not have a record of December; you have a screening you performed in August and labelled December.

That is the whole argument for keeping screening in a system rather than a folder, and it is also why exclusion screening in RIEL stores the run rather than the outcome.