How to Automate Verity Solutions
Verity Solutions automates the 340B accumulation itself: Split Billing manages qualified use and replenishment, Contract Pharmacy and VHUB handle dispenses at outside pharmacies, and Compliance Manager stores the documentation self-audits need. Registries, state policy pages and manufacturer notices stay manual, and an agent like WebRun reads those on a schedule.
Written by
Elliot Nakamura
Platform writer
Reviewed by
Sofia Marchetti
Marketing operations
A 340B programme is a ledger with a pharmacy attached
Verity Solutions builds 340B programme management software for the covered entities that qualify for the federal discount: disproportionate share hospitals, community health centres, federally qualified health centres, and the retail pharmacies that dispense for them. Most of what it sells carries the Verity 340B name.
The programme runs on a simple promise and a complicated proof. A qualifying provider buys an outpatient drug at a discount, but only for a patient who meets the definition, prescribed by a provider the entity employs or contracts with, and dispensed at a registered site. The software decides which dispense met all of that, accumulates it, and orders the replacement unit at the 340B price.
So Verity sits between the pharmacy and the wholesaler keeping a running account of what qualified. The people in it are the programme manager, the buyers who release the orders, and a compliance lead who has to prove every saving was earned.
The proof of eligibility sits on federal and state pages
None of the facts that decide eligibility start inside Verity. They start on somebody else's website, and somebody in your pharmacy goes and gets them.
A coordinator opens the federal 340B database to check that a clinic is still registered, that a child site was added before it started accumulating, and that the annual recertification window has not quietly opened. Somebody pulls the Medicaid exclusion file to see which entities are carving in this quarter. Somebody reads a manufacturer's latest notice about which contract pharmacies it will still ship to and works out what it means for the four you use. Somebody signs into the wholesaler to confirm a new account was set up on 340B pricing before the first order went through it.
Each is a few minutes and a screenshot for the audit file. Together they are why a compliance lead's calendar is a wall of reminders.
Split Billing accumulates from your dispenses, not from the register
Verity does the hard part of this properly, and an entity using it as a reporting tool is leaving most of it unopened.
Verity 340B Split Billing manages qualified pharmaceutical usage and replenishment, which is the calculation the whole programme rests on. Contract Pharmacy captures eligible prescriptions filled at retail and independent pharmacies, and the VHUB gateway centralises order and accumulation across them. Compliance Manager stores 340B programme documentation and gives you tools for the self-audit requirements. UDS Reporting formats what a health centre has to file each year.
Every one of those works on data you already own: your dispenses, your accumulations, your documents.
What decides whether a dispense should have accumulated at all is held elsewhere. Registration status, child site listings and recertification dates sit in the federal database. Carve-in and carve-out rules sit with each state Medicaid agency, published as policy on its own pages. Restrictions on which contract pharmacies a manufacturer will supply sit in that manufacturer's notice, on that manufacturer's site, revised when it suits them. Not one of those bodies has a reason to send you a file.
Recertification runs to a federal deadline, not to yours
A register does not mind being opened every morning, and nobody in the pharmacy has to remember to do it.
The registration record for every site you accumulate against, checked against what you believe you registered: the authorising official, the address, the child sites, and the recertification window with the days left on it. A window missed is a year outside the programme, and it gets missed by exactly one person being on leave in August.
The Medicaid exclusion file read as each version publishes, compared against the entities and billing numbers you carve in for, so a change is noticed the week it lands instead of in a finding.
Manufacturer notices watched on the sites that publish them, with anything naming a contract pharmacy you actually use pulled out and put in front of the programme manager. Wholesaler accounts checked, so a purchase that should have priced at 340B and did not is caught inside the month. State Medicaid pharmacy pages read for the paragraph that changes what you may bill and where.
None of that needs an interface, an export or a developer. It needs somebody to open the page.
The attestation still has a person's name on it
Somebody in the pharmacy opens all of those pages by hand today, and the person doing it is normally the one who signs to say the programme was run correctly.
WebRun is an agent that drives a real Chrome browser, signed in the way your staff sign in. It opens the federal database, a state Medicaid policy page, a manufacturer's notice or your wholesaler's portal, reads what is on the screen, and brings it back as a list with the dates attached.
In a programme audited this closely the line does not move. Gathering runs unattended, on your schedule, in your own environment. Recertifying an entity, reversing a claim, adjusting an accumulation or writing to the audit file is prepared and waits for the person whose name is on the attestation.
Each workflow below names the sites it opens before it opens them.
Questions people ask
Could it recertify our entity or adjust an accumulation?
No. It reads registers and portals and reports what they say. Recertifying, registering a child site, reversing a claim or changing an accumulation stays with the programme manager and the authorising official, working in Verity exactly as they do now.
Our auditor wants evidence with a date on it. Does a run produce that?
Yes. Findings come back with the source and the date attached: the page that was opened, when it was read, and what it said. That is what an auditor is asking for, rather than somebody's recollection of having looked at the register in March.
Manufacturer restrictions change every few weeks. Can it keep pace?
That is the case it suits best. A notice page can be read every morning, and only the notices naming a contract pharmacy you actually use come back, so the programme manager sees the change in days instead of finding it in a remittance.
12 ready-made Verity Solutions workflows
Each one names the apps it touches and the exact steps it takes. Open one to read what it will do, then turn it on.
Want one of these running on your own Verity Solutions?
Show WebRun the process once and it will run it on schedule, in your own private browser environment.