Platform: One record, from the certificate to the patient.
Decided by a person. Carried to the patient.
One lot, PY-2026-0922-01, on one page: the ingredient lot behind it, its results against the printed limit, the pharmacist's signed release and the 4 Passports it issued. Brennick Compounding is a sample pharmacy; its suppliers, people, lots and figures are invented.
Checked at the door, forgotten by release.
That is the gap an inspector finds. Veritura reads the paperwork behind every lot you receive and keeps it as one record, from the certificate to the patient.
In, checked, decided, carried. One record the whole way.
Documents come in, are checked against the law and FDA's records, are decided by a named person, and travel with the order to the patient.
Every check, in the methodology- Documents come in
A dropped set, email to your workspace, a supplier's standing link, a lot-number fetch or the API.
Each file kept by its bytes, on its lot - Checked against the law
Up to twenty named checks in four groups, against section 503A, FDA's lists, ICH and USP, every value cited to its line.
One verdict, in words - A person decides
Nothing leaves a lot until a named person has reviewed it, and the server enforces that on every path.
A signed decision: who, when and why - Carried to the patient
Each order gets an Evidence Passport, the record a patient or clinic opens by scanning the Seal on the label.
A record anyone can verify, no account
Veritura reads the paperwork. It never tests, grades or endorses the medicine itself.
Four places today. One record with Veritura.
Most pharmacies keep the certificate in one place, the supplier file in another, the release in a log and the patient's paperwork nowhere.
One record, seen from every side.
A lot, its supplier, its orders and its Passports are one record, so an inspector's question has one answer and a recall still reaches every Passport issued from the lot.
A recall a person declares reaches every clinic desk on Veritura holding the lot, and shows on every Passport issued from it.
The full trail for an inspector, the Passport for a buyer, plain words on the label.
The server refuses a Passport, a Seal or a shipment from an unreviewed lot on every path.
Six parts, one lot. Each passes something to the next.
Lot BM-5520, Cyanocobalamin USP from Brookmere API Supply, from the day its certificate arrives to the day a patient scans the label.
IntakePasses on every file, kept as received and filed to its lot.
Dropped as a whole set, emailed to your workspace's own address, sent through a supplier's standing link, fetched by lot number, or posted to the API.
Each file is identified by its bytes and filed to its own lot.
Word files, HTML, empty files and anything over 8 MB are refused, and the refusal says why.
VerificationPasses on one verdict, every value cited to its line.
The certificate itself, the substance, the published limits and outside sources.
Under USP <85>, ICH Q3C and ICH Q3D, with the substance checked against section 503A, FDA's 503A lists and FDA's registries.
Verified, Verified where checked, Your call or Not verified, with what failed and how to pass.
The supplier filePasses on a file that ClearGate reads at order time.
One file per supplier, and requests drafted from what is open.
Qualified is refused while a gap is open, and the decision is one a named person signs.
Suppliers and lots are re-matched hourly against FDA enforcement records, and ClearGate reads the file at order time.
The decisionPasses on a cleared lot a named person has reviewed.
A delivery goes through nine receiving gates and lands in one of four dispositions, from documentation release ready to hold for human review.
ClearGate screens each order on four lines of evidence, called rails, against the policy you set, and returns Allow, Review or Hold.
The rule lives on the server, so an unreviewed lot is refused on every path, the API included.
Passport and custodyPasses on a record anyone can verify, with no account.
A cleared lot a person reviewed issues an Evidence Passport per order, signed by hand or released under your saved policy, and a serialized Seal for each unit.
The certificate's own lines, the release gates, and a fingerprint they can recompute in their own browser.
Released, shipped, received, administered or recalled: each line is chained to the one before it. A recall a person declares reaches every clinic desk on Veritura holding the lot.
The agentsPasses on a morning briefing and a rehearsed inspection.
Vera AI reads overnight: every lot that needs a person, each finding cited to its line, and Passports lined up for one signature.
By default Vera drafts and a person sends; she never makes a first contact or a release on her own.
Cato AI rehearses the inspection on your own records, in a surveyor's order, and counts what is confirmed, checked, shown in person, still to collect and missing. He never scores.
Checked at the door. Kept through release. Shown to the patient.
The whole system, in detail.
For the reader who wants the whole system before a call.
Every check, in the methodologyThe nine links from manufacturer to patient
- The chain under every verdict
- Under every certificate's verdict, the review shows the lot's chain and the one next step: manufacturer, supplier, certificate, received, lot decision, preparation, Passport, shipment, patient.
- Each link
- Verified, open or the pharmacist's call, and each says what closes it.
- What the patient sees
- The same nine steps in plain words, with no score and no patient identity.
Every way a document gets in 5 ways
- Upload
- A PDF, a photo (PNG, JPEG or WebP) or a plain-text certificate, up to 8 MB, one at a time or as a whole set.
- Email-in
- Every workspace has its own email-in address; mail sent to it files under that workspace, and mail to an unknown address is ignored.
- A supplier's standing link
- Each supplier gets a standing link with no account, no login and no cost.
- Fetched by lot number
- Where a supplier publishes its certificates, one can be fetched by lot number from that public library, and the record says it was fetched from the supplier's site.
- API
- Documents can also be sent by API.
What runs on every file
- Up to twenty named checks
- Behind the verdict, in four groups, against section 503A, FDA's 503A lists, ICH Q7, Q3C and Q3D, USP <85> and <1111>, FDA's registries and the certificate's own arithmetic.
- Six FDA records on every read
- openFDA enforcement, FDA warning letters, FDA import alerts, FDA's registration records, FDA's 503B outsourcing facility list and FDA's substance registry.
- Document integrity
- A pass of seventeen signals, seven in the file and ten across your records, beside seven findings from the PDF's own metadata and thirteen signs of a generated document. Findings are signals for a person, never verdicts.
Release, and who controls it
- A named person first
- Nothing leaves a lot until a named person has recorded what they checked and relied on.
- Eight refusals
- The server refuses a Passport, a Seal or a shipment for any of eight reasons, including a recall signal, an open hold, no 503A route and no person review.
- By hand, by default
- A workspace that saves the Standard or Lenient policy lets a reviewed, cleared lot release its Passports on a policy Allow; Strict keeps every release with a person.
Run it from your own system API
- POST /v1/check
- Reads a document.
- POST /v1/cleargate
- Returns one decision per order.
- POST /v1/passports
- Issues from a cleared lot.
- POST /v1/seal-batches
- Mints serialized Seals.
- POST /v1/eligibility
- Answers whether a substance may be compounded for a facility type.
- Webhooks and plan
- Webhooks are signed with an HMAC. API access is on the Operations plan.
Preparations, and reminders from the record
- Preparations, not only certificates
- A compounding record is a document too. A preparation becomes a lot on your workspace, with each ingredient bound to its own lot by the record, so the Passport for a compounded preparation lists every ingredient with its lot, its supplier, whether a person reviewed it and its own results.
- Run-out reminders
- When an order arrives with a days-supply figure, the run-out date is computed at issue, and the patient whose saved unit is bound to that order can be reminded before the window closes, under your pharmacy's name and contact, with your own reorder link.
- Beyond-use dates
- A beyond-use date on the record is relayed the same way to patients who saved a unit from the lot. It is supply arithmetic on what your system recorded, never dosing.
The method 5 steps
- Intake
- Documents arrive by upload, email, a supplier's door or the API, and are kept as received, with their fingerprint.
- Check
- Up to twenty named checks against the statute, the published limits and FDA's records, each finding cited to its line.
- Decide
- Nothing leaves a lot until a named person has reviewed it, and every decision keeps who, when and why.
- Issue
- A cleared lot issues signed Passports per order and a serialized Seal for each unit.
- Watch
- Lots and suppliers on file are re-matched hourly against FDA enforcement records after release.
Why this exists
- Every ingredient needs valid paperwork
- Federal law requires that bulk substances used in compounding be accompanied by a valid certificate of analysis, and names no method for establishing that a certificate is valid. Every pharmacy, facility, clinic, and platform in the chain is left to decide for itself. That gap is the whole reason an independent evidence layer exists.
- The statute
- The requirement appears in the federal compounding provisions for both 503A pharmacies and 503B outsourcing facilities. Validity is required. A way to establish it is not described.
- A public example
- In 2026 the FDA published a warning letter to a bulk supplier on its own published lists, describing relabelled active ingredient and altered manufacturing and retest dates. A buyer who checked the list and received a certificate still held a document that did not say what it appeared to say.
- What buyers already do
- A large telehealth provider gave each subscriber the certificate of analysis behind their medication, from a QR code included in each shipment, and reported thousands of subscribers opening it every month. The demand for the record is not the question. Who checks it is.
What the record never claims
- No testing, no approvals
- Veritura reads documents and the public record. It does not test medicine, approve suppliers, recommend purchases or make medical, legal, safety or FDA-approval determinations, and Verified by Veritura is never a certification.
- No proof of absence
- No match in a public source is a fact about the sources that answered, never proof of absence.
- Not for sale
- Suppliers cannot pay for a better result.
Veritura checks and connects the paperwork behind an order. Nothing leaves a lot until a named person has reviewed it.
Find the page written for your side of the chain.
The same record serves everyone who handles the medicine. Each side sees what it needs, and nothing it should not.
Receiving, certificates, supplier files and release, on one record an inspector can follow.
Pictured: a pharmacy's next dates, from a recall response to two beyond-use dates.
A free desk: receive by code, see the paperwork behind each unit, and be reached when a lot is recalled.
Pictured: a clinic's desk, with one recall to acknowledge and 7 vials on the shelf.
A Passport on every order from every partner pharmacy, by API.
Pictured: a platform's partner pharmacies, never ranked, with what differs and what is due.
Questions, answered plainly.
A lot, its supplier, its orders and its Passports are the same record seen from different sides. Every status stays attached to the document and the person behind it, so a recall published months later still reaches every Passport issued from that lot.
Nothing leaves a lot until a named person has reviewed it. By default release is by hand. Save the Standard or Lenient policy and a reviewed, cleared lot releases its Passports on a policy Allow; Strict keeps every release with a person.
The certificate's own lines from a fixed list of fourteen fields, the supply chain by role, the published release gates, and a fingerprint they can recompute in their own browser. No score, and no patient identity.
For the copy file, a pharmacy's orders, patient references and the prescriber's words stay in its own browser and a file it saves; the server never receives them. A Passport carries an order reference, never a name, and a reference that reads like patient text is refused. A patient who chooses to save the medicine leaves an email, kept until they delete it. A patient emailed their Passport has that address kept as a recall contact for the batch, used only for recall notices about it, until a year after its use-by date, with an opt-out in every email.
Yes. Documents, ClearGate decisions, Passports, Seals and eligibility each have an API route, with HMAC-signed webhooks, on the Operations plan.
No. Verified is a statement about the paperwork: every check that could run passed. It is never an approval of a supplier or a statement about the medicine.
Still have questions? Talk to a person.