Automated Verity Medicaid Exclusion File Updates
Every quarter, WebRun opens Verity Solutions, checks your current roster of prescribers and locations against what is listed on your HRSA Medicaid exclusion file in OPAIS, drafts the additions and removals in Google Sheets, and flags them for your compliance officer to review before the update is filed.
How do I keep my 340B Medicaid exclusion file up to date?
WebRun keeps your Medicaid exclusion file current every quarter. It checks your prescriber and location roster in Verity Solutions against what is filed in HRSA OPAIS, drafts every addition and removal in Google Sheets, and flags new locations as high priority since an unlisted one risks a duplicate discount, leaving the actual filing for your compliance officer to review and submit.
- Roster changes are checked against the exclusion file every quarter instead of only when a problem is found
- New locations get flagged as high priority since they carry the most duplicate discount risk
- Nothing is filed with HRSA without your compliance officer reviewing it first
Built for 340B compliance officers · covered entity program managers · Medicaid billing teams · hospital outpatient pharmacy
What does WebRun do on every run?
The exact actions WebRun takes, in order - in plain language, so you can adjust anything.
-
WebRun signs in and gets to work
Opens
app.verity-solutions.comin a real browser with your saved login - no setup, no API keys. -
1
Verity Solutions - check the current prescriber roster
verity-solutions.com
WebRun opens Verity Solutions to check the current prescriber roster. - Open Verity Solutions and pull the current roster of prescribers and locations billing Medicaid
- Note any prescriber or location added or removed since the last quarter
- Flag any new location that bills Medicaid fee-for-service directly
Done when The current Medicaid-billing roster has been pulled for the quarter.
-
2
HRSA OPAIS - compare against the filed exclusion list
hrsa.gov
WebRun opens HRSA OPAIS to compare against the filed exclusion list. - Open HRSA OPAIS and pull what is currently listed on your Medicaid exclusion file
- Compare it against the current roster from Verity Solutions
- Note every addition and removal needed to keep the file accurate
Done when Every difference between your current roster and the filed exclusion list has been identified.
-
3
Google Sheets - draft the update
google.com
WebRun opens Google Sheets to draft the update. - Draft the list of additions and removals for your compliance officer to review
- Flag any new location as high priority since an unlisted location risks a duplicate discount
- Leave the update in Sheets for your compliance officer. Never file the update with HRSA automatically
Done when Your compliance officer has a drafted, reviewed update ready to file with HRSA.
How is each run configured?
Secure by default
Connect once, stays signed in
WebRun signs in once and keeps each session in a persistent environment, so every run picks up right where it left off.
Every action is checked against this policy before it runs.
Questions, answered
Will it file the Medicaid exclusion file update with HRSA on its own?
No. It only drafts the additions and removals in Google Sheets. Your compliance officer reviews and files the actual update with HRSA.
Why does an unlisted new location matter?
A prescriber or location billing Medicaid that is missing from your exclusion file risks a duplicate discount on every claim it generates until the file is corrected, so new locations are flagged as high priority.
How often should the exclusion file be checked?
Quarterly at minimum, which is what this runs on, though it checks the full current roster each time rather than just what changed since the last run.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.