AI StaffingAI Labor LawAI AdmissionsAI DSD & HRBlogLaunch Workspace
Back to the Blog
Compliance9 min read

OIG Exclusion Checks in Skilled Nursing: A Monthly Screening Workflow That Holds Up Under Audit

A practical workflow for skilled nursing operators who need to screen employees, agency staff, and contractors against OIG exclusions without turning the process into a spreadsheet fire drill.

Most exclusion-screening problems in skilled nursing do not start with a surveyor or an auditor. They start with a quiet operating assumption: "we checked that person at hire, so we are covered." That assumption breaks fast when agency staff rotate in, contractors change, names create false matches, or nobody can prove the monthly check happened.

This matters because OIG exclusion is not just a credentialing detail. The HHS Office of Inspector General says no Federal health care program payment may be made for items or services furnished, ordered, or prescribed by an excluded individual or entity, and that payment prohibition can reach the excluded person, the employer or contractor, and the provider where the services were furnished. (oig.hhs.gov)

For skilled nursing operators, that means exclusion screening is not only an HR task. It is a reimbursement-risk, staffing, agency-management, and documentation-readiness task. If the process lives in inboxes, one-off screenshots, and disconnected spreadsheets, teams usually discover the weakness only after the wrong shift has already been worked.

What an OIG exclusion check actually does

An OIG exclusion check compares a person or entity against the List of Excluded Individuals/Entities, or LEIE. OIG maintains that database and provides both an online searchable version and downloadable files for larger-scale screening. OIG also notes that the downloadable file does not include SSNs or EINs, so specific identity verification for potential matches has to be completed through the online search workflow. (oig.hhs.gov)

The practical operator takeaway is simple: a name-only pass is not enough if you hit a possible match. Your team needs a repeatable way to separate clean clears from records that need identity verification, documentation, and escalation.

Do skilled nursing facilities have to run monthly exclusion checks?

This is where teams often hear half the rule and miss the operating point. OIG says providers are not required by statute or regulation to check the LEIE, but it also says providers should check before employing or contracting with people and periodically recheck current employees and contractors. Because OIG updates the LEIE monthly, OIG states that monthly screening best minimizes potential overpayment and civil monetary penalty exposure. (oig.hhs.gov)

Separately, CMS requires State Medicaid agencies to check enrolled providers and certain related persons against federal databases, including the LEIE, no less frequently than monthly under 42 CFR 455.436. CMS also described those database checks as a first line of defense against improper Medicaid payments. That rule is directed at State Medicaid screening, not a blanket provider-side employee-screening mandate, but it reinforces why monthly exclusion status changes matter operationally. (cms.gov)

In plain English: even where a provider-side monthly employee check is not spelled out in a single federal command to the facility, monthly screening is still the defensible operating standard for skilled nursing teams that want to reduce repayment, penalty, and documentation risk. That is an operator recommendation, not legal advice, and facilities should align final policy with counsel, compliance leadership, payer contracts, and state-specific requirements.

Who skilled nursing teams should screen

OIG's 2013 bulletin is especially important here because it makes clear that the risk is not limited to direct bedside employees. OIG explains that providers should assess whether the item or service provided is directly or indirectly payable by a Federal health care program and screen accordingly. OIG specifically discusses employees, contractors, subcontractors, volunteers, staffing-agency clinicians, and even billing or coding contractors in that risk analysis. (oig.hhs.gov)

  • Employees on payroll, including licensed and non-licensed roles tied to reimbursable operations
  • Agency and registry staff, especially nurses and aides filling open shifts
  • Contract therapy, pharmacy, lab, transportation, billing, coding, and similar vendors where services connect to federally reimbursed care
  • Contractors or subcontractors whose work is operationally tied to patient-care delivery or claimable services
  • New hires before start date, plus current workers on a recurring monthly cycle

The biggest miss in skilled nursing is usually not the obvious full-time nurse on payroll. It is the rotating agency worker, the contractor screened by someone else but never validated, or the false sense that a credential file equals an exclusion check.

Why manual screening turns into a compliance blind spot

Manual exclusion checks tend to fail in four predictable ways.

  • The facility screens at hire but not monthly, so the process is technically present but operationally stale.
  • Agency staff are assumed to be screened by the vendor, but the facility cannot produce proof that screening actually happened.
  • Potential name matches are noted but never fully resolved and documented through identity verification.
  • HR, staffing, payroll, and compliance each own part of the process, so nobody owns the full audit trail.

That last point matters most. Exclusion screening is a cross-functional workflow. It affects who can work, who can stay scheduled, what vendor labor can be used, and whether documentation will hold up later. Once it is fragmented, the facility starts discovering risk after work has already been performed.

A monthly exclusion-screening workflow that actually works

The goal is not to create a heavier checklist. The goal is to create a monthly operating rhythm that produces three things every time: a complete population, a documented result, and a clear escalation path.

1. Lock the screening population before the month starts

Build one authoritative roster that includes active employees, pending hires, agency workers used during the period, and contractors or vendors that should be screened under your policy. If the roster is pulled from multiple systems, reconcile it before the screening cycle begins instead of after a match appears.

2. Run initial LEIE screening for the full population

Use the OIG online search for smaller volumes or the downloadable LEIE files for larger-volume workflows. OIG says the downloadable database is replaced monthly with the most current version, and supplemental files are also posted monthly. (oig.hhs.gov)

3. Resolve possible matches, not just exact matches

Potential matches should move into a separate review queue. Confirm identifiers, use the online search process when SSN or EIN verification is needed, and document why the record was cleared or escalated. A screened name without a resolved disposition is unfinished work, not a completed check. (oig.hhs.gov)

4. Capture proof the same day

OIG says providers should maintain documentation of the initial name search and any additional searches used to verify potential matches. In practice, that means keeping date, source, search result, reviewer, disposition, and supporting evidence together in one place. (oig.hhs.gov)

5. Hold schedulability until unresolved items are cleared

If a pending hire, contractor, or agency worker has an unresolved match, the safest operating move is to keep that person out of the schedulable cleared roster until the review is complete. This is where manual workflows usually break: the schedule gets built first, and the documentation gets chased later.

6. Validate vendor-side screening instead of assuming it

OIG says providers can rely on contractor screening only if they validate that the contractor is conducting the screening on the provider's behalf and retain supporting documentation. For skilled nursing, that means agency contracts and vendor onboarding should require screening cadence, proof format, escalation expectations, and response times for positive or possible matches. (oig.hhs.gov)

7. Keep an audit-ready monthly packet

Each monthly cycle should end with a stored packet or system record showing who was screened, when, against what source, what potential matches were reviewed, how they were resolved, and who approved exceptions. If you cannot reconstruct that path quickly, the process is not audit-ready.

What to do if you find a possible or confirmed match

Do not treat every search result as a confirmed exclusion, but do not treat it casually either. Separate "possible match" from "confirmed match," pause further workflow movement, verify identity, and escalate internally to compliance, HR, leadership, and legal counsel as appropriate. If the individual or entity is excluded, the next steps may involve immediate work-status decisions, payment review, vendor coordination, and potential self-disclosure analysis depending on the facts. OIG notes that reinstatement is not automatic when an exclusion period ends; the individual or entity must apply for reinstatement and receive written notice from OIG. (oig.hhs.gov)

The real risk is not only missing the name. It is discovering too late that nobody can prove the screening happened, the match was reviewed, or the worker should have been cleared to stay on the schedule.

Where skilled nursing operators usually need automation

Exclusion screening becomes expensive when it depends on memory, heroics, and month-end cleanup. The workflow touches onboarding, credentialing, staffing, payroll, vendor management, and audit readiness. That is exactly the kind of cross-functional process that looks manageable in a spreadsheet until the roster grows, agency use rises, or turnover picks up.

This is where an AI operating layer helps. Instead of asking HR, staffing, and compliance to chase disconnected follow-up, the system can keep one cleared roster, surface unresolved matches early, hold exceptions in view, and preserve the audit trail without making the team rebuild it from screenshots later.

If your facility is still handling OIG exclusion checks through scattered files and manual reminders, this is a good workflow to tighten before it becomes a survey question, a repayment problem, or a vendor-labor surprise. ePeople AI helps skilled nursing teams turn workforce-readiness and compliance follow-up into decision-ready action queues so cleared staff stay schedulable and unresolved risk does not stay hidden.

Frequently asked

Do skilled nursing facilities have to run OIG exclusion checks every month?

Federal guidance does not frame provider-side monthly employee screening as a one-line mandate in every circumstance, but OIG says providers should screen before employing or contracting with people and periodically recheck current employees and contractors. Because OIG updates the LEIE monthly, OIG says monthly screening best minimizes overpayment and CMP risk. Facilities should align final policy with counsel, payer contracts, and state-specific requirements.

Who should be included in a monthly LEIE screening workflow?

At a minimum, facilities should evaluate active employees, pending hires, agency staff, and contractors whose services are directly or indirectly connected to federally reimbursable care or operations. OIG's guidance makes clear the risk is not limited to direct bedside roles.

Is a license check the same as an OIG exclusion check?

No. A license verification confirms licensure status with the relevant board. An OIG exclusion check looks for exclusion from participation in Federal health care programs. A worker can be licensed and still require exclusion screening, so facilities should not treat those workflows as interchangeable.

What documentation should a facility keep after a monthly exclusion check?

Keep the screening date, screening source, screened population, reviewer name, result, any possible-match research, final disposition, and any vendor proof relied upon. The goal is to show not only that the check occurred, but that unresolved matches were reviewed and cleared or escalated appropriately.

Sources

ePeople.ai logo

Turn late visibility into an operating rhythm.

ePeople AI helps skilled nursing operators move from manual chasing to workflow-specific action queues across staffing, labor-law, credentialing, and admissions operations.

15-minute focused walkthrough · We respect your privacy — your information is never shared