Check any provider against the OIG List of Excluded Individuals and Entities (LEIE), with structured results and screenshot evidence for your audit file. One check per run, on the official federal source, no login required.
Go-live in as little as 30 minBrowser agentPublic source
We map your process, volume, and exception paths, then recommend a practical first scope.
Building internally? Read the docs →
Overview
A browser agent runs the search a credentialing coordinator runs today: it opens the OIG’s official online searchable database, enters the provider’s name, reads the results, and returns a clear status: found, not_found, or multiple_matches. A not_found run is a successful clean check, not a failure.
You provide a first and last name. NPI, date of birth, and specialty are optional, and are used to qualify which match likely corresponds when common names return several records.
How Asteroid runs this workflow
A roster or single-provider request arrives, Asteroid searches the OIG LEIE, classifies the result, and files the evidence back to your screening status, and a possible match routes to a person for identity confirmation, because the agent never clears an ambiguous result on its own.
How it actually runs
Each check returns: the status, the match count and details, the echo of exactly what was searched, the evidence screenshot, and when the check ran. That record is your answer to an auditor’s “show me the screening for this provider, on this date.”
A provider roster or single-provider screening request is ready
Delivered to your screening status
The clear or possible-match result lands with its exclusion detail, evidence screenshot, and UTC timestamp: the per-provider record an auditor asks for, feeding the monthly pass.
Possible match needs identity confirmation: All matching records return with exclusion type, dates, and the screenshot attached; a person confirms identity once. Per OIG guidance, a name match is never treated as a confirmed exclusion.
Closing the loop
Nobody on your team reads this JSON. Your system does. Each run delivers its record wherever the work already lives, and the loop closes on its own: requests in, records back, no one in the middle.
▸ run triggered · request received from your system▸ agent working the source…{ "source": "OIG LEIE", "status": "found", "checked_at": "2026-07-16T14:02:11Z", "result": { "excluded": true, "match_count": 1, "matches": [ { "name": "SAMPLE, JOHN A", "npi": "1•••••••21", "exclusion_type": "1128(a)(1)", "exclusion_date": "2019-08-20", "reinstatement_date": null, "address": { "city": "DALLAS", "state": "TX" } } ] }, "evidence_screenshot_url": "https://…/evidence/run_8f3a….png"}OIG’s own guidance is that a name match is not a confirmed identity: confirming that a listed exclusion is actually your provider requires SSN verification, which a search cannot do. This workflow reports matches faithfully and never claims confirmed identity. An exclusion tool that turns a name search into a definitive “excluded” verdict is overclaiming, and that overclaim becomes your compliance problem, not the vendor’s.
When a match or multiple matches come back, the record routes to a person with the full detail attached. Identity confirmation stays a human decision, made once, with evidence, instead of a re-search.
At scale
Exclusion screening has tightened to a monthly cadence for many practices, and a state audit catching a manual gap is a common reason teams look for automation in the first place. This check is a single-purpose primitive built to run in bulk: a CSV of your roster in, one structured record per provider out, exceptions queued for review.
It composes with the SAM.gov federal exclusion check and the state Medicaid exclusion check for full screening coverage. Full-list screening is part of the credentialing and verification workflow library, alongside license verification and NPI checks.
Human in the loop
Screening runs execute on HIPAA-compliant, SOC 2 Type II infrastructure, and every check leaves a timestamped record of what was searched and what came back, which is the artifact a state auditor actually asks for. Details on the security page.
Multiple matches on a common name.
All matches are reported with detail; a person confirms identity.
A found result.
Exclusion is a hiring and billing decision. The agent delivers the evidence; it never makes the call.
Site errors or downtime.
The run returns an explicit error status rather than a silent pass. A screening program never records a check that didn’t happen.
Questions
This check is one workflow in the credentialing & verification workflow library. Every skipped screening cycle is a gap an auditor can find. Automating the cycle is cheaper than explaining the gap.
Disclaimer
Third-party names, including government agencies and registries, are used only to identify systems commonly involved in healthcare operations workflows. Asteroid is not affiliated with, endorsed by, sponsored by, or certified by those third parties unless expressly stated. Workflow availability depends on customer authorization, account permissions, configuration, and applicable system terms.
We use cookies for analytics and advertising. You can opt out or manage your choices anytime.