Check a provider against a state’s own Medicaid exclusion and sanction list: found or not-found status with the sanction type and dates, an evidence screenshot, and a timestamp, as one structured record. The state layer of exclusion screening, built state by state.
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
Every state maintains its own Medicaid exclusion and sanction list, and it’s a genuinely different list from the federal ones: it carries state-level actions, exclusions, for-cause terminations, disbarments, that originate with the state’s own Medicaid program. A browser agent runs the check against the state’s official search: it enters the provider’s name, reads the results, and returns the same structured screening envelope as the OIG and SAM.gov checks, so all three layers of a screening program produce records in one shape.
The workflow is built per state, Louisiana today via the Louisiana Department of Health’s State Adverse Actions List search, and cloned state by state as coverage grows. A request for a state that isn’t built yet ends with a clear scoped error naming what’s supported, never a wrong answer dressed as a right one.
How Asteroid runs this workflow
A roster arrives for one or more state Medicaid exclusion sources, Asteroid searches each state's own list, captures any sanction finding with evidence, and returns a normalized result to your screening queue, with name-only matches and unclear source language routed to your compliance team.
How it actually runs
A not-found run is a successful clean check, on record with evidence, which is the thing an auditor actually asks for.
A provider roster is ready for one or more state Medicaid exclusion sources
Delivered to your screening queue
The state-specific result lands in the screening queue with its evidence and timestamp, normalized to the roster's record shape: one cadence and one queue across the OIG, SAM.gov, and state layers.
Name-only match or unclear state data: Every matching record returns with sanction type, dates, and the screenshot attached; a person confirms identity once, with the NPI as tiebreaker when the list shows one.
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.
{ "source": "LDH State Adverse Actions List", "status": "not_found", "checked_at": "2026-07-16T14:02:11Z", "result": { "excluded": false, "match_count": 0, "matches": [] }, "evidence_screenshot_url": "https://…/evidence/run_2c91….png"}The OIG list covers federal healthcare-program exclusions and SAM.gov covers government-wide debarment, but a for-cause termination or a sanction from a state Medicaid program lives on the state’s own list, and it can sit there without a matching federal entry. That’s why screening guidance treats the state list as its own required layer rather than a redundancy. A monthly pass that runs the OIG check and the SAM.gov check but skips the state layer has a gap exactly where the most local, most recent findings appear.
At scale
A single run checks one provider against one state’s list. As a program, the roster runs monthly alongside the OIG and SAM.gov checks, three lists, one cadence, one record shape, and the exceptions land with your compliance team with the state’s own wording and a screenshot attached. Screening is part of the credentialing and verification workflow library. The same state source answers a different question in the DSW registry check.
Human in the loop
Each state check runs on HIPAA-compliant, SOC 2 Type II infrastructure with per-run logs, so the monthly cadence is demonstrable rather than asserted. See the security page.
Multiple matches on a common name.
All matches are reported with detail; a person confirms identity, with the NPI as the tiebreaker when the list shows one.
A found result.
A state sanction is an employment and billing decision. The agent delivers the record and the evidence; the call is yours.
A state that isn’t built yet.
A clear scoped error naming what’s supported, never a silently skipped check.
Questions
The state Medicaid check is one workflow in the credentialing and verification workflow library. A screening pass that skips the state layer is a gap an auditor can find, and state auditors look at the state layer first.
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.