OIG Exclusion List Screening: Why Coding and Billing Teams Need to Check It Monthly
Most practice administrators know they are supposed to screen new hires against the OIG exclusion list. Far fewer treat it as a recurring operational task, and that gap is where civil monetary penalty exposure quietly builds.
The Office of Inspector General maintains the List of Excluded Individuals and Entities, commonly called the LEIE. Federal healthcare programs, including Medicare and Medicaid, prohibit payment for items or services furnished by, ordered by, or prescribed by anyone on that list. The critical word is anyone. The exposure is not limited to the person who walked into the exam room. It can attach to the ordering provider, the referring provider, and, depending on the facts, to the organization that submitted the claim. Coding and billing teams sit directly in that chain.
What the LEIE Actually Covers
The OIG issues exclusions under authority granted by the Social Security Act, primarily Sections 1128 and 1128A. Some exclusions are mandatory, triggered by convictions for program-related fraud, patient abuse, or felony drug offenses. Others are permissive, leaving the OIG discretion based on lesser offenses, license revocations, or other conduct the agency determines warrants removal from federal program participation.
An excluded individual or entity cannot:
- Furnish items or services reimbursable by any federal healthcare program
- Order or prescribe items or services reimbursable by federal healthcare programs
- Provide administrative or management services to organizations that bill federal programs
That last point catches many organizations off guard. A billing manager, a coder, or a practice administrator who has been excluded cannot work in a position that involves managing or directing services paid for by Medicare or Medicaid, even if they never personally touch a patient. If your organization employs or contracts with such a person and submits claims, you have a problem regardless of whether the clinical work was performed by someone clean.
Claims that reference an excluded ordering provider are similarly tainted. A physician who orders a diagnostic test has their NPI on that claim. If that physician is on the LEIE, the claim should not have been submitted. The fact that the rendering provider and the billing staff had no idea the ordering physician was excluded does not eliminate the liability under 42 CFR Part 1003, which governs civil monetary penalties for false claims to federal programs.
Why a One-Time Hire Screen Is Not Enough
New exclusions are added to the LEIE continuously. The OIG updates the list monthly, which is exactly why monthly screening has become the standard expectation in the compliance community, not an arbitrary best practice someone invented.
A physician who was in good standing when you credentialed them two years ago could have their license revoked in another state, face a conviction, or be excluded administratively without any automatic notice reaching your organization. The same is true for employed coders, contracted billers, and mid-level providers. The exclusion does not come with a certified letter to your compliance office. You find out by checking.
The OIG's guidance on compliance program effectiveness, including its various compliance program guidances issued for different provider types and the General Compliance Program Guidance released in 2023, consistently identifies exclusion screening as a concrete indicator of a functioning program. Regulators are not impressed by a policy that says "we screen at hire." They look for documented evidence of recurring screening.
State Medicaid programs maintain their own exclusion lists, separate from the federal LEIE. A provider could be excluded from your state's Medicaid program without appearing on the federal list. If your organization bills Medicaid, you need to check the applicable state list as well. Many practices discover this gap only after a state audit raises it.
The Connection to Coding and Billing
Revenue cycle teams often think of exclusion screening as an HR or credentialing function. In practice, the billing team is the last line of defense before a claim goes out the door.
When a claim is assembled, it includes rendering provider NPIs, ordering provider NPIs, and referring provider NPIs depending on the claim type. A coder or biller who has access to that information is in a position to flag anomalies, but only if the organization has given them the tools and the protocol to do so. Without a clear process connecting compliance screening results to the billing workflow, a claim for services ordered by an excluded provider can be submitted in the ordinary course of business with no one realizing the problem.
This is why exclusion screening is a shared responsibility. Human resources runs the initial screening at hire and manages the recurring schedule. Compliance maintains the records and handles escalations. Revenue cycle needs to know which providers are cleared to appear on claims and have a mechanism to hold claims when a provider's status is uncertain. These three functions have to communicate, or the exposure persists despite everyone believing someone else is handling it.
A periodic coding quality audit is one practical way to identify whether provider identifiers on submitted claims are consistent with current credentialing and exclusion records. Audits that sample claims across ordering, rendering, and referring provider fields can surface patterns that manual reviews miss.
For practices with employed physicians, your physician coding (ProFee) workflows should include a checkpoint confirming that every provider whose work generates a claim has been screened within the current billing period. That checkpoint does not need to be elaborate, but it does need to exist and be documented.
Practical Screening Mechanics
Checking the LEIE
The OIG provides a free online search tool at oig.hhs.gov and offers a downloadable database file updated each month. Large organizations with many providers often use the downloadable file to run automated batch comparisons. Smaller practices may use the online search tool manually. Either approach is acceptable as long as it is done consistently and the results are recorded.
Screen by name and by National Provider Identifier where available. Using both reduces the risk of missing a match and of generating false positives on common names.
Handling False Positives
Common names generate false positive matches. Finding a John Smith on the LEIE does not mean your employee John Smith is excluded. The resolution process matters. Compare date of birth, address history, NPI, and Social Security Number through your HR records to confirm or rule out a match before taking any action. Document the comparison and the conclusion. A false positive that is properly worked through and documented is evidence your process functions correctly. A false positive that is ignored or resolved informally is a liability.
Documenting the Process
Keep a log of every screening run: the date, the list checked (federal LEIE and any applicable state lists), the individuals and entities screened, who performed the screening, and the result. If no matches were found, record that. If a potential match was flagged and resolved as a false positive, record the resolution steps. This documentation is what you show a regulator, an accreditor, or a plaintiff's attorney when they ask whether your compliance program was actually functioning.
For teams building or strengthening these processes, our free Denial Prevention Checklist includes operational checkpoints that overlap with exclusion screening and claims submission controls, making it a useful starting point for revenue cycle staff who want a practical workflow reference.
What to Do When You Find a Real Match
If screening returns a confirmed match on a current employee, contracted provider, or any individual whose NPI appears on claims your organization is submitting, the response needs to be immediate and documented.
Stop submitting claims that reference that individual. If claims have already gone out during a period when the individual was excluded, identify the scope and preserve the records. Involve compliance counsel before making any voluntary disclosure or repayment decisions, because the timing and method of disclosure affects how regulators treat the situation. Do not allow the individual to continue in any role that touches federal program billing while the situation is being evaluated.
The OIG Self-Disclosure Protocol exists precisely for situations where an organization discovers it has submitted claims involving excluded individuals. Using it appropriately, with counsel, is generally viewed more favorably than waiting for the government to find the issue independently.
Exclusion Screening as Evidence of a Real Compliance Program
The OIG and the Department of Justice have been explicit that having a compliance program on paper is not sufficient. The question regulators ask during investigations and audits is whether the program was operational, whether people followed it, and whether it produced documentable results.
A recurring monthly screening schedule with complete logs answers that question directly. It is one of the most concrete, verifiable things an organization can produce to demonstrate that compliance is a function rather than a document in a drawer.
That framing matters for practice CFOs and revenue cycle directors who may view compliance as cost without clear return. Documented exclusion screening reduces the risk of civil monetary penalties, protects the organization in the event of an investigation, and contributes to the kind of billing integrity that supports claim acceptance rates. It also connects to broader coding and documentation practices reviewed in our posts on HIPAA compliance for remote coders and compliance risk assessment for coding teams, both of which address how compliance responsibilities extend into daily revenue cycle operations.
Strong exclusion screening also works best when paired with clean clinical documentation upstream. A CDI program support structure that keeps documentation accurate and complete reduces the number of claim exceptions your team has to resolve, giving compliance staff more bandwidth to focus on screening and monitoring rather than correcting avoidable errors.
OIG exclusion list screening is not a checkbox. It is a monthly operational task that belongs in your revenue cycle calendar alongside claim submission deadlines and denial follow-up cycles.
If your organization needs a structured review of how exclusion screening integrates with your current billing controls, contact the MedCodex team through our coding quality audit service to schedule an assessment.