A compliance officer drafting an OIG exclusion screening policy document
EXCLUSION SCREENING

Build an OIG Exclusion Screening Policy

Aug 10, 2026· 8 min read ·Compliance ·NPI Data Services

Ask ten compliance teams whether they screen employees against the OIG exclusion list and all ten will say yes. Ask to see the written policy that defines who gets screened, against which lists, how often, and what happens when a name hits, and the room gets quiet.

That gap is the whole problem. When the OIG or a state Medicaid auditor comes asking, "we run the LEIE" is not an answer. A dated, written exclusion screening policy is. It is the document that proves the practice existed before the audit did, and it is the single cheapest piece of protection you can put between your organization and a civil monetary penalty. This is what belongs in it.

Why a written policy, not just a habit

The OIG has been explicit about what it expects. Its Special Advisory Bulletin on the Effect of Exclusion, updated May 9, 2013, tells providers to screen employees and contractors against the List of Excluded Individuals and Entities (LEIE) at the point of hire and each month afterward, and to keep documentation of every search performed (HHS-OIG Special Advisory Bulletin). The bulletin frames this as the way to "minimize" your exposure to penalties, not as a formality.

On the Medicaid side, CMS reinforced the same expectation. State Medicaid Director Letter #09-001, issued January 16, 2009, directs states to require their providers to screen all employees and contractors against the LEIE monthly to catch exclusions and reinstatements since the last search (CMS State Medicaid Director Letter #11-003 restates and builds on this). Those expectations were later codified in the Medicaid screening regulations at 42 CFR Part 455, Subpart E.

Here is the part that turns guidance into money. Under 42 CFR § 1003.210, the OIG can assess a civil monetary penalty of up to $20,000 for each item or service furnished by an excluded person (a base figure subject to annual inflation adjustment), plus an assessment of up to three times the amount claimed, on top of repaying what the program already paid. And liability attaches on a "knew or should have known" standard, not proof of intent. A written policy is how you show you took the "should have known" duty seriously and built a system to meet it. Our OIG exclusion screening best practices page breaks down the five pillars that policy has to cover.

The seven things every exclusion screening policy must define

A policy that just says "we will screen against the OIG list" is not a policy, it is a sentence. A defensible one answers seven questions in writing.

# Policy element What it must state
1 Scope Every category of person and entity in scope: employees, contractors, locum and temp staff, vendors, and governing-body members, not just the clinicians on your claims.
2 Lists Which databases you screen against: OIG LEIE (required), SAM.gov, and the Medicaid exclusion list for every state you operate in.
3 Frequency Pre-hire/pre-contract screening, then monthly rescreening to match the LEIE's monthly update cycle.
4 Matching method Match on name plus date of birth, not NPI alone, because most excluded individuals have no NPI on record.
5 Match resolution The exact steps to verify a potential hit and the action taken on a confirmed one, including stopping billing for that person's services.
6 Documentation What evidence you retain (who, which lists, when, the result) and for how long.
7 Ownership The role responsible for running screening, resolving matches, and reviewing the policy annually.

Get those seven on paper and you have moved from "we check the list" to a program an auditor can follow.

Scope: screen everyone in the chain

The most common policy failure is drawing the circle too small. The OIG's position is that payment is prohibited for items or services furnished, ordered, or prescribed by an excluded person, whether or not that person submits the claim. That sweeps in far more than your billing providers. The 2013 bulletin specifically calls out nurses supplied by a staffing agency, physician groups contracted to provide coverage, and billing and coding contractors as people who should be screened. Write your scope to cover the whole workforce and every vendor whose work touches federally reimbursed care.

Lists: the LEIE is the floor, not the ceiling

The LEIE is the federal system of record and your policy must name it as the primary source. But a mature policy also screens SAM.gov for government-wide debarments and each relevant state Medicaid exclusion list, because a provider barred by a state may not yet appear federally. Our guide to monthly exclusion screening explains why the cadence and the multi-list coverage go together: a clean federal check does not mean a clean state check.

Frequency: monthly, because the list moves monthly

The LEIE is refreshed monthly, generally by mid-month, with new exclusions added and reinstatements removed. A once-a-year check leaves an excluded hire undetected for up to eleven months, and every claim in that window is exposure. Your policy should tie rescreening to the monthly update so the gap never opens.

The free checklist

Print this, adapt the bracketed owners and retention period to your organization, and attach it to the policy as the operating procedure.

  • Pre-hire / pre-contract screen. Screen every individual and entity against the LEIE, SAM.gov, and applicable state lists before they start or sign.
  • Monthly roster rescreen. Re-check the full roster against the latest LEIE update every month; never let it slip a cycle.
  • Match on name + date of birth. Do not rely on NPI; most excluded individuals do not have one on file.
  • Verify before you act. Confirm a potential match against OIG's published identifiers before taking any adverse action; a name hit alone is not proof.
  • Act on a confirmed hit. Stop billing federal programs for that person's services immediately, and follow your policy's removal steps.
  • Document every run. Keep dated, exportable evidence of who was screened, against which lists, when, and the outcome.
  • Retain records. Hold screening documentation for your defined retention period ([recommend at least the applicable audit look-back]).
  • Assign an owner. Name the role accountable for running screening and resolving matches.
  • Review annually. Re-approve the policy each year and update it when lists, staff, or regulations change.

If you want the wider compliance context this policy sits inside, our OIG compliance program 101 walks through how exclusion screening fits alongside the other elements of an effective program.

Where policies quietly fail

Three failure modes account for most of the trouble, and none of them are exotic.

The first is the manual gap. A spreadsheet and a calendar reminder work until the person who owns them is on vacation, and a missed month is invisible until an auditor finds it. The second is scope creep in reverse, where the policy covers physicians but not the staffing-agency nurses and billing vendors who are actually the higher-frequency source of exclusions. The third is no paper trail: the screening happened, but nobody can prove it, so in an audit it did not happen. A written policy plus automated, logged screening closes all three.

Frequently asked questions

Is an exclusion screening policy legally required? No single statute says "adopt a written policy." But the OIG's Special Advisory Bulletin and CMS's Medicaid screening rules both direct providers to screen at hire and monthly and to document it, and penalties attach on a "should have known" standard. A written policy is the accepted way to demonstrate you met that duty.

How often does the policy need to require screening? Before hire or contracting, then monthly. The LEIE updates roughly monthly, so a monthly cadence ensures a new exclusion is caught within one cycle rather than sitting for a year.

Who has to be in scope? Employees, contractors, locum and temporary staff, vendors, and governing-body members, anyone who furnishes, orders, or prescribes items or services that a federal program might pay for. The OIG specifically flags agency nurses and billing contractors.

What documentation should the policy require us to keep? Dated evidence of who was screened, against which lists, on what date, and the result, including how any potential match was resolved. If you cannot produce it, an auditor treats the screening as if it never happened.

Can we automate policy compliance? Yes. Continuous monitoring lets you load your roster once and have it re-checked against each federal and state refresh automatically, with an exportable audit trail, which is what removes the manual-gap and paper-trail failure modes.

The bottom line

An exclusion screening policy is not busywork. It is the artifact that converts a good intention into a defensible program, and it is nearly free to produce. Define the seven elements, attach the checklist as your operating procedure, assign an owner, and review it every year. The organizations that get penalized almost never lacked the ability to screen. They lacked the written program that proved they did.

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. Use our tools as part of, not a substitute for, your own compliance program and counsel's guidance.

Ready to make your policy run itself? Start screening free and re-check your whole roster against the OIG LEIE, SAM.gov, and 50+ other sources every month, with the audit trail built in.

Sources

Related posts