OIG Exclusion List Screening is not a formality you file away after onboarding. It is a continuing control that keeps excluded people and entities out of federally reimbursable work, protects billing integrity, and reduces civil monetary penalty exposure when auditors review your files. If you run hiring, contracting, or credentialing for a medical practice, you need a process that starts before day one and continues every month after that.
Prerequisites: What You Need Before You Build an OIG Screening Program
Before you screen anyone, define the scope of your program in writing. A defensible process depends on clear coverage, assigned responsibility, reliable source lists, and documentation that proves each search happened on time. If those basics are missing, even a good search tool will not save you from preventable compliance gaps.
Define who must be screened
Start by treating screening as a business relationship control, not an employee-only task. Your onboarding program should cover employees, licensed independent practitioners, contractors, temporary staff, volunteers, owners, board members, and vendors whose work touches federal healthcare program billing or operations. That includes people who never bill directly but still influence claims, scheduling, ordering, prescribing, supervision, coding, or payment workflows.
The reason is simple. Exclusion exposure extends far beyond the person who sees the patient. A driver, dispatcher, biller, IT user, device delivery worker, or medical director can create the same repayment and penalty risk if the person is excluded and your organization still pays or relies on that work in a federally reimbursable setting. The legal test is broad enough that you should assume coverage unless your compliance policy specifically excludes a role after a documented risk review.
Identify the governing legal authorities
Your screening policy should be anchored in the Social Security Act, especially sections 1128 and 1156. Those provisions give the Office of Inspector General authority to exclude individuals and entities from participation in federal healthcare programs. Once excluded, a person or entity cannot be paid by Medicare, Medicaid, CHIP, TRICARE, and other federal healthcare programs for items or services furnished, ordered, or prescribed during the exclusion period.
The enforcement consequence is not limited to reimbursement denial. Civil monetary penalties apply when you hire, contract with, or otherwise use excluded parties. OIG guidance also expects organizations to use the same compliance discipline that supports a durable healthcare compliance program, because exclusion screening sits inside the larger obligation to prevent, detect, and correct federal program risk. If you ignore the screening requirement, you are no longer dealing with a paperwork issue, you are dealing with avoidable program exposure.
Assemble the screening tools and source lists
At a minimum, your onboarding program should check the OIG List of Excluded Individuals/Entities, known as the LEIE, and the relevant state Medicaid exclusion lists. The LEIE is the federal baseline, but it is not the full picture. State exclusion databases often move on their own schedule, and missing a state list leaves a gap that auditors recognize immediately.
Depending on your payer mix and risk profile, you should also maintain access to additional sanctions sources such as GSA/SAM and OFAC. Those lists serve different purposes, but they add another layer of verification when you are onboarding vendors, owners, or management entities. The point is not to create extra work for its own sake. The point is to avoid a false sense of clearance based on a single database search.
Establish internal roles and approval authority
A screening process fails when everyone assumes someone else is responsible. Assign one team to perform the search, a second person or function to review possible matches, and a specific approver who authorizes onboarding clearance. In smaller organizations, one person may perform more than one role, but the approvals still need to be separated by step and documented.
Escalation authority matters just as much. If a possible match cannot be resolved quickly, the case should move to compliance, legal counsel, or billing leadership before the person starts work. That stop point protects you from letting an unresolved hit slip into active status, which is exactly how avoidable overpayments start. If you already work with counsel who focuses on regulatory audits and overpayment demands, this is the point where that relationship earns its keep.
Build the documentation file structure
Your file structure should make the search easy to prove after the fact. Keep search dates, source list names, search results, match resolution notes, identity verification evidence, and onboarding authorization records in one consistent format. When possible, use the same naming convention for every person or entity so an auditor can trace the record without guessing.
Document retention is not a side issue. If you cannot show when the search happened, what was checked, who reviewed it, and why the person was cleared, you do not have a defensible screening record. You have a memory problem.
Step 1: Map Your Onboarding Workflow to Exclusion Screening Risk Points
A screening program is only as strong as the workflow behind it. You need to decide exactly where exclusion checks sit inside hiring, contracting, and credentialing so the process is automatic, not optional. That is the difference between real control and a policy no one follows under deadline pressure.
Identify every onboarding trigger
Screening must happen at more than one point. Use a pre-offer or pre-contract review for early risk detection, then repeat the check at conditional offer, pre-start clearance, recredentialing, contract renewal, and roster updates. You should also rescreen when a person changes name, legal entity, ownership status, or role in a way that changes exposure.
This structure matters because exclusions do not appear only when someone is first hired. They can arise later, after a disciplinary action, a criminal case, a state sanction, or an OIG administrative action. If you screen only once, you miss the period when the person becomes excluded after onboarding. That is why OIG expects monthly screening, not one-and-done checks.
Separate federally reimbursable work from non-billable work
Not every role carries the same exposure, but many more roles carry exposure than practices assume. Separate federally reimbursable work from tasks that never touch federal program funds. Someone who works entirely outside Medicare, Medicaid, CHIP, or TRICARE billing may sit outside your strictest payment risk zone, but once that person can influence claims, orders, referrals, supervision, or administrative operations, the exclusion analysis changes.
Write the distinction into your policy. That makes it easier to explain why certain workers require clearance before start and why others still require periodic screening even if they never touch patients directly. For vendors and contractors, the issue is even simpler: if the business relationship supports operations that feed federal billing, screen the party before access begins.
Align screening with credentialing and privileging
Exclusion screening should live beside license verification, sanctions review, and privileging, not behind them. A clean license does not clear a person for federal program participation, and a strong credential file does not fix an exclusion hit. Your onboarding package should be complete before privileges, system access, or billable duties start.
Put another way, exclusion screening is one piece of a larger control stack. It should travel with your employment contract review process for medical staff, because compensation, duties, supervision, and billing access all influence risk. If those documents are inconsistent with the screening result, your onboarding file is incomplete.
Set rules for provisional access
Provisional access needs strict limits. If your organization allows any work to begin before final clearance, the person should be blocked from federally reimbursable duties until screening is complete and approved. Do not rely on verbal assurances, manager discretion, or “temporary” access that later becomes permanent.
The cleanest rule is blunt: no clearance, no federally reimbursable work. That standard prevents confusion and avoids the common mistake of letting a new hire start “just for training” and then accidentally drift into billable activity. If you need a written stop rule for supervisors, this is where it belongs.
Step 2: Write a Clear Exclusion Screening Policy
A useful policy does more than restate the law. It tells staff exactly who to screen, when to screen, what to do with a hit, and how to document each decision. If the policy leaves judgment calls to frontline staff, expect inconsistent results and weak audit defense.
State the purpose and compliance standard
Your policy should state that its purpose is to prevent excluded individuals and entities from furnishing, ordering, prescribing, managing, or being paid for federally reimbursable services. That is the compliance standard. Not “try to catch obvious problems,” not “check when convenient,” and not “screen only after someone starts work.”
Use direct language. Exclusion creates repayment exposure, CMP risk, and downstream billing problems. The policy should say that clearly so no one confuses screening with administrative housekeeping.
Define the screening population
List every covered category in the policy. Include employees, licensed independent practitioners, contractors, temporary staff, volunteers, owners, board members, and vendors with operational access or billing-related functions. If your organization uses locum tenens physicians, agency nurses, agency medical assistants, or outsourced billing support, name those groups too.
The reason for specificity is practical. People do not follow vague policy language. They follow checklists that map to real job categories and real workflows. A policy that says “all workforce members” sounds broad, but it often fails because no one knows whether a particular consultant, courier, or part-time contractor belongs in scope.
Set the required screening cadence
The policy should require screening before start and at least monthly afterward. OIG states that the LEIE should be checked monthly, and that expectation should be the floor for your program. Any deviation from monthly monitoring should be documented, approved, and limited to a narrow operational reason.
Monthly review is not busywork. It is how you catch exclusions that arise after onboarding and how you keep pace with a moving sanctions list. If your practice runs on a monthly payroll or monthly roster cycle, fold screening into that same rhythm so no covered person falls out of the process.
Establish match-review and escalation rules
Your policy needs a defined path for possible matches. The reviewer should compare all available identifiers, pause onboarding while the match is unresolved, and escalate anything unclear to compliance or legal review. Billing leadership should be notified if the person already touched claims, orders, or services before the hit was detected.
Do not leave match resolution to the hiring manager. That role is too close to the staffing need and too far from the compliance risk. Use a structured review process with a documented disposition: clear no match, confirmed excluded match, or unresolved pending review. If you also maintain a formal voluntary disclosure workflow for compliance errors, connect it here so unresolved or discovered failures follow one legal path.
Address retention and audit standards
Retention rules should explain how long you keep screening records and what evidence belongs in the file. At a minimum, keep the search date, source list used, search output, reviewer, disposition, and any supporting identity evidence. If a match was investigated and cleared, keep the documents that show why the record was not the person or entity in your organization.
Your policy should also require periodic audit of retained records. An audit trail only helps if it is complete enough to prove the decision. If your organization uses external compliance support, this is a strong place to involve a general health law attorney who can pressure-test the policy against audit expectations before an investigator does.
Step 3: Screen Before the Person Starts Work or Contracted Services
Initial screening is where most organizations either build control or plant the seed for later trouble. If you clear the person before first work, you reduce the chance of a bad hire, a bad contract, or a bad chart entry that creates reimbursement exposure. If you delay the check until after access begins, the process has already failed.
Collect complete identity data
Gather full legal name, any aliases, date of birth, NPI, and TIN or FEIN where relevant before you search. For entities, capture exact legal name, DBA names, tax identifiers, and ownership data if available. If address history is available, keep it too, because it helps resolve ambiguous matches.
Incomplete identity data is the fastest way to miss a match or create a false alarm. A person named John Smith with no birth date or NPI is not ready for a reliable search. The search result may look clean, but the data quality makes that result weak.
Search the OIG LEIE using more than one identifier
Use both name-based and identifier-based searches when available. The LEIE is searchable online and through downloadable files, and a careful review uses more than one identifier to reduce false negatives. Match on exact name first, then compare DOB, NPI, and any available tax or address data.
The goal is not to find a record that looks close enough. The goal is to establish identity with enough confidence that you can defend the clearance decision later. If the records are ambiguous, do not force a quick yes. Hold the file until the identity is resolved.
Search state exclusion databases
State Medicaid exclusions must be checked separately. Do not assume the LEIE captures state action in real time or that your federal check eliminates state exposure. Many organizations miss this point, then discover that a state exclusion existed even though the federal list search appeared clean.
If your organization operates in multiple states, build the state review into a standard intake process rather than a one-off exception. State list checks are especially important for Medicaid-heavy practices, home health operations, long-term care providers, and any setting where state program billing represents a large part of revenue. The operational lesson is simple: federal screening is necessary, but it is not complete by itself.
Search other required sanctions sources
Depending on your risk profile, add GSA/SAM, OFAC, and other sanctions databases to the onboarding file. These sources serve different legal purposes from exclusion lists, but they add useful protection when you are onboarding entities with contracts, payment access, or administrative control. That matters when the person is not a direct clinician but still has access to systems, payments, or sensitive operations.
Broader sanctions review becomes especially important when onboarding touches referral arrangements or managed services. If a contract structure also raises fair market value or referral concerns, coordinate the screening review with Anti-Kickback Statute Compliance analysis so the relationship is lawful on both the payment and exclusion sides.
Document the pre-start clearance decision
At the end of the search, record one of three outcomes: cleared, hold, or unresolved. A cleared result should show the source list checked, the identifiers reviewed, the date of search, and the reviewer’s approval. A hold or unresolved result should show that access stayed closed until the issue was resolved.
Pre-start documentation should be crisp. An auditor should be able to tell in one pass whether the person was screened before work began. If that answer is not obvious, your process is too loose.
Step 4: Review Possible Matches and Resolve Them Before Clearance
A possible match is not a small issue. It is a hard stop until you verify identity. The reason is straightforward, an unresolved hit is enough to create risk if you let the person start working while you sort it out.
Pause onboarding immediately on a potential match
If a search returns a possible exclusion hit, stop onboarding for federally reimbursable duties immediately. Do not let the person start “while you check.” Do not give the contractor limited access. Do not rely on a manager’s informal review. Keep the person out of billable work until the issue is resolved.
This is the point where many programs fail. They treat the hit as a clerical annoyance instead of a compliance event. That decision is expensive when the record turns out to be a real exclusion or when a later audit shows the person worked while still under review.
Compare all available identifiers
Resolve the record by comparing date of birth, middle name, aliases, NPI, TIN or FEIN, address, specialty, and entity formation data where relevant. For entities, review ownership and business purpose. For individuals, compare prior names and license data. Use the full profile, not a single field.
The reason to be methodical is that LEIE matches often depend on ordinary-looking identifiers. A common name alone is not enough. A common name plus the same date of birth is very different. The search review should make that distinction explicit.
Request supporting documents when needed
If the match remains unclear, request documents that settle identity. Acceptable support includes government-issued ID, credentialing records, prior employment records, business formation documents, and signed attestations from the person or entity. Keep the request narrow and relevant to identity, not broader than needed.
Do not overcollect. The point is to verify the record, not to build a separate HR file. But do collect enough to explain why the cleared result is correct. That balance matters when you later need to prove why a potential hit was not the person you hired.
Escalate unresolved matches without delay
If the match still cannot be resolved, escalate to compliance, legal counsel, or billing leadership. The case should not sit in a manager’s inbox while the person begins work. A formal escalation path protects the organization and ensures the issue gets legal review before payment exposure grows.
Use a clear threshold for escalation. If identifiers conflict, if the names are too similar, or if the entity data is incomplete, route the case upward. A fast escalation is cheaper than an overpayment correction later.
Record the final disposition
Every match review should end with a written disposition. Clear no-match, confirmed excluded match, or pending unresolved status should all be documented with the reason, the reviewer, and the supporting evidence. If the hit is confirmed, record the stop-work decision and the date it took effect.
This record becomes your defense file. If a regulator asks why a person was cleared, the answer should already exist in the onboarding file. If the answer is not there, the file is incomplete.
Step 5: Prevent Billing, Ordering, and Supervisory Exposure During Onboarding
Screening is not just about deciding whether a person can start. It is also about keeping excluded people away from payment-sensitive functions. If you clear a person for work without controlling access, you have only solved half the problem.
Restrict access to scheduling and billing systems
Use role-based access controls so no one receives scheduling, billing, claims, or documentation access until screening is approved. If your system grants access automatically on hire date, change that process. The person should not see patient schedules, billing screens, or claim workflows until the screening file is complete.
That matters because accidental access often leads to accidental use. A new hire who can enter charges or edit appointments can create claims risk long before anyone notices a credentialing error. Align access with clearance, not with convenience.
Control ordering and prescribing privileges
Excluded practitioners cannot order, prescribe, or otherwise influence federally reimbursable services. That includes direct orders and indirect influence through protocols, standing instructions, or review functions. If the practitioner is excluded, the practice must block those functions until the matter is resolved or the person is removed from the workflow.
If your practice uses medical directors or supervising physicians, coordinate screening with medical director agreement compliance. A signed agreement does not override exclusion rules, and a proper order process does not fix a bad clearance decision.
Limit indirect involvement in management and administration
Exclusion risk reaches administrative and supervisory roles. A person can create exposure without touching a patient if the person manages claims, supervises staff, controls revenue cycle operations, or shapes decisions tied to federal program billing. That is why your screening scope should include back-office and management jobs, not just clinical jobs.
Do not assume “non-clinical” means “non-covered.” A biller with system access or a practice manager who reviews staffing, coding, or payment workflows still belongs inside your screening program. If the role affects federal reimbursement, the role belongs in scope.
Train supervisors on stop-work rules
Supervisors need a clear instruction: if screening is pending, no billable work begins. If a hit appears after work has started, stop the person from further federal program involvement immediately and notify compliance. Managers are not expected to adjudicate exclusion issues on the spot.
This stop-work rule should appear in the onboarding checklist and the supervisor handbook. Without that, a manager will try to “help” by keeping the person productive while the review continues. That is exactly how risk compounds.
Coordinate with payroll and contractor management
Payroll should not process compensation for work performed while a person is under exclusion review in a federally reimbursable role. Contractor management should not activate payment terms before clearance. If the person is later found excluded, you need a clean record of what was paid, when, and for what work.
That structure also helps if you must unwind a problem. The better your payment controls, the easier it is to quantify exposure and correct the file. If billing errors are already in motion, tie the response to Medicare billing audit readiness so the revenue cycle response is documented and complete.
Step 6: Build Monthly Ongoing Monitoring Into Your Onboarding Program
Monthly monitoring is where the program becomes real. Without it, onboarding screening is just a snapshot. OIG expects more than a snapshot, and so do auditors who look for continuous controls around federal program payment.
Recheck the LEIE every month
Use the monthly cycle as a mandatory control, not an optional reminder. OIG states the LEIE should be checked monthly, and your policy should mirror that requirement exactly. Every covered employee, contractor, and relevant business partner should be included in the monthly run.
The practical point is simple. A clean initial search does not protect you if the person becomes excluded next month. Monthly checking catches that change before it turns into claims exposure.
Monitor state lists on a recurring basis
State lists need recurring review on a schedule that matches your risk. Monthly is a sound baseline when your practice bills Medicaid heavily or operates in multiple states. At a minimum, the review should be frequent enough to catch changes before the next billing cycle produces avoidable exposure.
Keep the state list checks synchronized with your roster review. A federal-only monthly process is not enough if the state exclusion hit arrives first and remains invisible in your workflow. That gap is preventable.
Screen new hires, rehires, transfers, and contract renewals
Every staffing event creates a fresh risk point. New hires require initial clearance. Rehires need a new search. Transfers into a billable role need a new review. Contract renewals deserve a current check before the renewed term begins.
That rule matters because people often move between subsidiaries, practices, or departments without a new file being created. If your onboarding workflow does not catch the transfer, the person may slip into a billable role without a current exclusion review.
Use roster-based monitoring for all covered populations
Roster-based monitoring is the cleanest way to keep the program alive. Maintain an active list of everyone who needs screening, then run the list monthly against the applicable exclusion databases. Include employees, contractors, vendors with access, and any other covered business partner.
A single source of truth for the roster avoids drift. If the roster is inaccurate, your monitoring will be inaccurate. That is why roster maintenance is part of screening, not a separate HR task.
Record each monthly run
Each monthly file should show the date, database checked, reviewer, search method, and disposition. If a match occurs, add the resolution evidence. If the run was delayed, document why and how the backlog was corrected.
That file is your proof that screening continued after onboarding. Without it, you cannot show monthly compliance, and a one-time hire file will not carry the argument very far in an audit.
Step 7: Strengthen Match Accuracy With Better Data Governance
The best screening policy still fails if the data is dirty. False positives waste time, false negatives miss risk, and duplicate records create confusion about who was actually screened. Good data governance is not administrative polish, it is compliance infrastructure.
Standardize names and identifiers at intake
Use a standard format for legal names, suffixes, aliases, dates of birth, NPIs, and tax identifiers. Make it part of the onboarding form so the person who collects the data cannot skip fields casually. Standardized intake improves search quality and makes later audits easier to read.
The biggest mistake is allowing free-text entries to drive exclusion searches. One person types “Bob,” another types “Robert,” and the search results become unreliable. Standardization removes that noise.
Capture aliases and prior names
Ask for maiden names, former legal names, alternate spellings, and business aliases when relevant. These details matter more than most staff expect. Exclusion records often appear under an earlier name, and a search that ignores those names gives you a false sense of safety.
For entities, collect DBA names, parent-company names, and prior legal names if the business has reorganized. That level of detail is especially useful for contractors, staffing firms, and vendors that operate under multiple trade names.
Validate identifiers before search
Check the quality of DOB, NPI, and tax identifiers before you run the search. A wrong date of birth or transposed identifier creates the appearance of a no-match when the person is actually in the database under a different record. Validation before search reduces those errors.
If the source data comes from a recruiter or vendor, do not assume it is complete. Confirm it. A few minutes of validation beats a later investigation into why a miss happened.
Maintain a single source of truth for staff rosters
Duplicate rosters are a common failure point. If HR, credentialing, payroll, and department managers each maintain separate lists, the monthly exclusion run will miss someone. Use one controlled roster that feeds the screening process and reflects the current active population.
That roster should include start date, role, department, status, and contract term where relevant. If someone exits, retires, or transfers, the roster should show the change immediately. Without that discipline, monthly monitoring loses precision.
Control changes after onboarding
Any change to name, address, ownership, role, or contract structure should trigger review of the screening file. A new legal name or new entity name can change search results. A role change can also change whether the person has access to reimbursable functions.
Treat post-onboarding changes as screening events, not administrative footnotes. That habit keeps the file current and reduces the chance that a person falls out of the monitored population.
Step 8: Extend Screening Beyond Employees to the Full Business Relationship
If you only screen employees, you are missing a large part of the risk map. Exclusion exposure follows the business relationship, not just the payroll record. You need a wider lens.
Screen contractors and locum tenens staff
Contracted clinicians create the same exclusion risk as direct hires. Locum tenens physicians, agency nurses, traveling therapists, and independent contractors should all be screened before they start. Their contract status does not lower the compliance standard.
That matters because contract language often creates false confidence. A signed agreement does not neutralize exclusion risk. The person still cannot be paid for federal program work if excluded, and your organization still bears the exposure if the person participates.
Screen vendors with operational access
Vendors are not outside the screen just because they are not clinicians. Delivery staff, referral support companies, IT vendors, billing vendors, and device servicing contractors can all touch federally reimbursable operations. If they influence payment, documentation, access, or service delivery, screen them.
This is also where patient privacy controls intersect with exclusion screening. A vendor who can see patient data and influence reimbursement creates dual risk. One control set should not be blind to the other.
Screen volunteers and unpaid personnel where duties create risk
Unpaid status does not remove exclusion exposure. Volunteers who support patient-facing services, transport, documentation, or administrative functions tied to federal program work still belong in your risk review. If the person helps deliver or manage reimbursable care, screen the person.
Practices often assume “not paid” means “not relevant.” That assumption is wrong. The exclusion rules focus on participation in federally funded healthcare activity, not just compensation from payroll.
Screen owners, board members, and controlling persons where appropriate
Ownership and governance roles require attention because control can affect payment, management, and federal program participation. Screen owners, board members, and controlling persons where the relationship creates operational or billing risk. For closely held practices, this step should be routine.
The reason is not academic. If an excluded owner or manager participates in decisions that affect federal program business, the risk can spread beyond the person’s direct services. Governance screening closes that gap.
Screen referral and administrative partners
Referral entities, management companies, and administrative partners can create indirect exposure. If the business relationship touches referral flow, shared services, or management control, screen it before the relationship begins and at recurring intervals. That process pairs naturally with compliance review of referral arrangements so the business structure is lawful from more than one angle.
A clean onboarding program should not stop at the walls of your practice. It should cover the full business ecosystem that supports your federal program revenue.
Step 9: Document the File as if an Auditor Will Review It
If your screening file cannot survive an audit, it is not finished. Documentation is not an afterthought. It is the proof that your process operated as written and that the organization made reasonable, deliberate decisions.
Keep searchable proof of each screening event
Retain screenshots, export files, reports, or system logs that show the search was performed. The evidence should show the database checked, the date, and the identifiers used. If your system generates an automated confirmation, keep that too.
The proof must be easy to retrieve. If a compliance analyst has to rebuild the search from memory, the file is weak. Keep it in a format that can be produced quickly.
Record who reviewed the result
Every result should show the reviewer’s name, title, date, and approval authority. That accountability matters because it shows the decision was made by a person with responsibility, not dumped into a queue and forgotten. If a possible match was escalated, record who received it and when.
This also helps with segregation of duties. The person performing the search should not be the only person who can approve the clearance. A second set of eyes strengthens the record and reduces error.
Preserve match-resolution support
When a search produces a possible hit, keep the documents used to resolve it. That includes identity records, written comparisons, and any correspondence that supports the final conclusion. If you cleared a match because the DOB differed, say that and keep the evidence.
A later auditor should be able to follow the logic without guessing. The goal is to prove why the record was not a match, not just to say that someone looked at it.
Track onboarding hold and release decisions
If onboarding was paused, document the reason, the duration of the hold, and the evidence that justified release. If the person was denied clearance, document that too. The file should tell the complete story from initial screen to final decision.
That level of detail is especially important when a manager wants to move a person into work quickly. The hold record proves that the organization enforced the stop-work rule instead of making an informal exception.
Retain records for a defined period
Keep screening records long enough to satisfy legal, operational, and payer expectations. Your retention rule should align with your broader compliance and payroll record policies. If your organization operates under a Corporate Integrity Agreement, retention standards may be even stricter, so the local policy should never be looser than the governing obligation.
Short retention is a common mistake. If you destroy the record before a billing review or investigation surfaces, you lose the best evidence of good-faith compliance.
Step 10: Train Hiring Managers, Supervisors, and Compliance Staff
A screening program depends on people outside compliance. Hiring managers, supervisors, credentialing staff, and billing leaders need to understand the rule, the risk, and the stop-work requirement. If they do not, the process breaks in the exact place where speed matters most.
Train staff on what exclusion screening means
Teach staff that exclusion is a legal bar on participation in federal healthcare programs, not a staffing preference. Explain that an excluded person cannot be paid for items or services furnished, ordered, or prescribed under covered programs. Make the penalty exposure concrete so the rule is taken seriously.
Training should be specific, not vague. Staff need to understand that the issue affects Medicare, Medicaid, CHIP, TRICARE, and related program work. If they think the rule applies only to clinical hires, the program will fail.
Train staff on red-flag indicators
Teach staff to watch for incomplete identity data, inconsistent spellings, prior sanctions, unexplained employment gaps, or reluctance to provide standard onboarding information. Those are not proof of exclusion, but they are signals that the review needs attention. A good screening program treats those signals as triggers, not annoyances.
This training is especially useful for credentialing and HR teams that collect data before compliance review. If they know which details matter, they can prevent weak files from entering the queue. That saves time and reduces bad searches.
Train staff on stop-work procedures
Managers should know exactly what to do when clearance is pending or a match appears after work begins. The answer is immediate stop on federally reimbursable duties, notification to compliance, and no resumption until the issue is cleared. Anything less creates avoidable exposure.
Practice the response. A written rule is useful, but a rehearsal makes it real. If the team cannot explain the stop-work process in one sentence, retraining is overdue.
Train staff on confidentiality and escalation discipline
People need to know that exclusion review information is sensitive. Share it only with the staff who need it to resolve the issue. At the same time, do not let confidentiality become an excuse for silence. The right people must know quickly so the case can move.
That balance matters in small practices, where everyone knows everyone else. A narrow need-to-know process keeps the review professional and prevents gossip from substituting for compliance.
Re-train on a fixed schedule
Annual training alone is not enough if your policy or roster changes during the year. Use scheduled refreshers tied to audit findings, policy updates, and process changes. If your screening tool changes or if you add a new database, retrain the users before the next monthly run.
A program stays reliable when people remember the rule at the moment it matters. Regular training is how you keep that memory fresh.
Step 11: Audit Your Screening Program Before an External Auditor Does
Internal auditing is where you find the weak points before regulators do. A screening program can look good on paper and still miss people, dates, or records. Audits reveal whether the workflow actually runs as designed.
Reperform a sample of onboarding screens
Select a sample of new hires, contractors, and vendors, then rerun the screening check to confirm the original result. Compare the live search to the file documentation. If the result cannot be reproduced, the record needs correction.
This test shows whether your search logic, data entry, and retention method all work together. It also tells you whether the team is using the right databases and the right identifiers.
Compare rosters to completed screening files
Match your active roster against completed screening documentation. Look for people who started work, moved departments, or renewed contracts without a corresponding clearance file. This is one of the fastest ways to find missing records.
If you discover a gap, document the cause and fix the roster process. Missing files are often a sign of poor handoff between HR, credentialing, and compliance.
Review false positives and false negatives
Track how often the search returns a false alarm and how often the team misses a true issue. A high false-positive rate usually means the intake data is weak or the search logic is too loose. A false-negative event usually means the file was incomplete or the wrong database was checked.
The point of reviewing these patterns is corrective action. If the same mistake repeats, the process is the problem, not the person who ran the search.
Measure timeliness and backlog
Monitor the time from onboarding trigger to clearance. If the backlog grows, the screening program is no longer preventing risk in real time. Timeliness matters because a late review gives the person more opportunity to touch billable work before clearance.
Set a practical internal standard and hold the team to it. If searches regularly sit unreviewed, fix staffing, routing, or automation. Delay is itself a risk factor.
Correct policy and workflow gaps
Each audit finding should produce a process change. If the intake form lacks aliases, fix the form. If the monthly run skips contractors, fix the roster. If supervisors keep starting people before clearance, fix the stop-work rule and retrain the managers.
An audit without correction is theater. A real audit changes behavior, not just documentation.
Step 12: Respond Immediately if You Discover an Excluded Person Was Hired or Used
Discovery after the fact requires fast containment. Once you know an excluded person was hired, contracted, or used in a federally reimbursable role, the next few hours matter. Delay increases the scope of the problem.
Remove the person from federally reimbursable work
Stop the person from all covered duties immediately. That includes patient care, ordering, prescribing, billing, supervision, and administrative tasks tied to federal program services. If the person is a contractor or vendor, suspend the engagement until legal and compliance review is complete.
This is not a negotiable step. Containment comes first because every additional day of work can expand the overpayment and penalty exposure. The longer the person remains active, the more claims are at risk.
Assess the scope of affected services
Identify the dates, services, locations, and systems touched by the excluded person. Review orders, referrals, claims, supervision, and any administrative work that influenced payment. You need a clean scope statement before you can calculate exposure.
If the person worked in multiple settings or roles, break the review down by function. A broad “employment date range” is not enough to quantify the problem. The question is which reimbursable services were affected and when.
Quantify overpayment and billing exposure
Review claims associated with the exclusion period and estimate the amount paid or payable. This review should include direct services, downstream billing, and any claims influenced by the excluded person’s participation. If the person touched Medicare, Medicaid, or other federal program work, exposure can be substantial.
The financial risk is real. OIG enforcement continues to produce significant monetary impact, including exclusions, criminal actions, civil actions, and substantial recoveries. When excluded hires are involved, the amounts can escalate quickly, which is exactly why screening must happen before work starts.
Notify compliance, billing, and legal leadership
Escalate the issue to the internal leaders responsible for response and repayment. Billing needs to understand which claims are affected. Compliance needs the timeline and scope. Legal needs to assess disclosure and remediation options.
Keep the communication tight and factual. This is not the time for speculation. You need a controlled internal record that shows when the issue was identified, who was notified, and what containment steps were taken.
Consider self-disclosure and repayment pathways
If the issue created overpayments or broader program exposure, evaluate whether repayment, correction, or disclosure is required. The right path depends on the facts, but you should not wait for an auditor to define the problem for you. A timely review of your False Claims Act defense posture and related disclosure obligations protects the organization from compounding the original error.
If the situation is material or widespread, connect the remediation to a formal self-disclosure process. The goal is to fix the problem with the least additional damage. That requires prompt action, not delay.
Common Problems and How to Fix Them
Most screening failures are predictable. The same patterns keep appearing because organizations treat exclusion review as a task instead of a control. Once you know the failure modes, you can fix them permanently.
Problem: Screening only happens at hire
One-time screening misses new exclusions that arise after onboarding. The fix is monthly monitoring with a controlled roster and a documented monthly file. If your current process ends after the start date, it is incomplete.
Problem: Staff use incomplete identity data
Missing DOB, alias, NPI, or tax identifiers produces weak searches and unreliable results. Fix the intake form, require standard data fields, and validate the identifiers before search. Better data means fewer false matches and fewer missed hits.
Problem: Contractors bypass the screening queue
Decentralized contracting creates a back door. Close it by making contractor setup impossible until compliance clearance is recorded. If a department can engage a contractor without screening, your process is not controlled.
Problem: State lists are ignored
LEIE-only screening leaves state Medicaid exposure untouched. Add state exclusion databases to the monthly run and to every new engagement. If your practice operates in multiple states, build that requirement into the workflow from the start.
Problem: Positive matches are not escalated
If a hit sits unresolved while the person starts work, the review process has failed. Write a strict escalation rule and enforce it. Pending matches stay out of federal program work until resolved.
Problem: Records are too weak for audit defense
Screenshots alone are not enough if they do not show who reviewed the result and why the person was cleared. Build a complete file structure with search output, identity comparisons, approval records, and hold or release notes. If the file is complete, the explanation becomes easy.
Expected Outcome: A Defensible Medical Staff Onboarding Screening Program
A solid screening program gives you more than a clean checklist. It gives you a repeatable control that keeps excluded people out of federal program work, protects billing integrity, and produces a record you can defend in an audit. That is the standard you should aim for.
What a compliant onboarding file contains
A compliant file shows the screening population, the source lists checked, the date of each search, the reviewer, the clearance decision, and any supporting evidence used to resolve a match. It also shows monthly follow-up searches and any escalation notes. If a person was held, the file should show why and when the hold ended.
The file should be complete enough that a reviewer can reconstruct the decision without side conversations. That is the benchmark for defensibility.
What success looks like operationally
Operational success looks like simple habits repeated on time. New hires do not start billable work until cleared. Contractors cannot activate until screened. Monthly review runs on schedule. Possible matches stop the workflow until resolved. Billing, compliance, and HR all know their part.
The result is better than just avoiding a penalty. You also reduce overpayment risk, strengthen enrollment hygiene, and keep excluded parties away from Medicare, Medicaid, CHIP, and TRICARE reimbursement paths.
Next steps for policy maintenance
Maintain the policy as a live control, not a document on a shelf. Update source lists, retrain staff after process changes, audit roster completeness, and review any exclusion-related incidents for root cause. If your organization is large enough to need broader regulatory coordination, pair screening maintenance with broader audit and compliance oversight so correction work stays consistent across departments.
Once you understand how exclusion screening works in practice, the real question changes. It is no longer whether you checked the list once. It is whether your onboarding system prevents excluded people and entities from entering federal program work at all.
Frequently Asked Questions
How often should you perform OIG Exclusion List Screening?
You should screen before the person starts work and then every month afterward. OIG states that the LEIE should be checked monthly, and monthly review is the baseline for a defensible program.
Does OIG Exclusion List Screening apply to vendors and contractors?
Yes. If a vendor or contractor has access to federal program operations, billing, patient care, or administrative functions tied to reimbursement, that party belongs in your screening population.
What should you do if you find a possible match?
Stop onboarding or work assignment immediately for federally reimbursable duties, compare all identifiers, and escalate unresolved matches to compliance or legal review. Do not let the person start while the hit is still open.
Is the LEIE enough by itself?
No. The LEIE is the federal starting point, but you should also check state Medicaid exclusion lists and, when appropriate, other sanctions sources such as GSA/SAM and OFAC.
What happens if you hire an excluded person by mistake?
Remove the person from federal program work at once, review affected services and claims, quantify any overpayment exposure, and determine whether disclosure or repayment is required. Delay increases penalty risk.
How long should you keep screening records?
Keep them long enough to satisfy your legal, operational, and payer obligations. The record should include search proof, reviewer identity, match-resolution support, and the final clearance or hold decision.
A strong screening program is not complicated, but it is strict. If you make monthly OIG Exclusion List Screening part of onboarding discipline, you reduce the chance that a preventable hire turns into a billing problem, a repayment demand, or a CMP case.