Intelligence: We see what a single packet review cannot.

17 document-integrity signals. Lots re-matched every hour.

Book a demo See a live lot

Certificates with a signal, in a sample pharmacy's workspace: 15 certificates read in the last 30 days; certificate COA-BM-5584 has 2 signals of 7 read, 6 read with an answer and 1 not checked; certificates read a week over 37 days by supplier, the one open here marked; and the signal on this certificate: the laboratory can be checked, because the named lab is not in the reference registry and the document gives no other way to check it

Alone, a certificate can look perfect. Side by side, the repeats show.

Three things no single review can see, because each one looks only at the document in front of it.

The same file again

The same file, report ID or lot number turning up where it should not.

A changed template

A supplier's certificate layout that changed overnight, from one lot to the next.

Two certificates that disagree

Two certificates for one lot that disagree on the assay, the retest date or the laboratory.

Veritura reads every document as one body of evidence. What it finds is a signal for a person, never an accusation.

Read alone, read together. The same certificate, a different story.

Every document is read beside your workspace, compared by fingerprint across every Veritura account, and its lot re-matched to FDA enforcement records every hour.

One packet reviewRead together

Where it looksThe document in front of itEvery document in your workspace, and the supplier's own history

Who else holds itNot visibleA count of other Veritura accounts, and nothing more

When it checks FDAOnce, at readAt read, then every hour against openFDA enforcement records

Reused paperwork is the tell.

Every document is fingerprinted on arrival, so a second copy is caught the moment it lands, not at the next audit.

Fingerprinted on arrival.

The file's hash, its text and visual fingerprints, and the identifiers it carries.

Flagged the moment it lands.

Under another lot, supplier or date, both records are linked when the second copy lands, not at the next audit.

A signal, never an accusation.

Both records open side by side, for a person to judge.

Document-integrity signals on certificate COA-BM-5584, 6 read and 1 not checked: its dates agree with each other; edited after it was issued, not checked, because a text file carries no edit history; it matches the supplier's 3 earlier certificates on 4 features; the laboratory can be checked, a signal; no signs of a generated document; the same file or report ID is not on file for another account; and recall and enforcement records, a signal, with the note that the sample firm has no FDA record to look up — Every signal on one certificate, each with what it read and what it found. A signal is for a person to look at, never a verdict.

Five views, one body of evidence. Each raised for a person to judge.

Each runs on every document, without anyone asking.

Across every account, counts onlyHow many other accounts hold the same thing. Nothing else.

The last 30 days on a sample pharmacy's watch list: 17 lots in and 2 recalls caught, day by day; 6 sources, 2 of 6 checked, 1 found something, 4 operations in the shared network; and caught for you: batch ZN-2026-0929-01 of zinc sulfate 1 mg/mL with 4 Passports, and zinc sulfate lot ZS-0442 from Brookmere API Supply, both reported Oct 13 — Across the network, a count of operations and nothing more; for you, what was caught and when.

Strong identifiers compared.

The file hash, visual and text fingerprints, and the laboratory and report identity.

A count, and nothing more.

No other party's name, supplier, file, lot or order is ever shown, and nobody sees yours.

Visible without exposure.

A certificate sent to several pharmacies under different lots shows, without exposing any of them.

One lot, two certificatesEvery value that differs named, and neither document accused.

Side by side.

Two certificates for the same lot number that disagree: the assay, the retest date, the laboratory.

Neither accused.

The review names the conflict. A person decides which one holds.

Across accounts too.

On the monitoring cycle; each workspace sees only its own side.

Against the supplier's own historyA new document set against the supplier's earlier ones, across 11 features.

Certificates read a week over 37 days, by supplier: Tessaline 7, Brookmere 4, Aurora 2, Vellora 1 and 1 with no supplier named, with certificate COA-BM-5584 marked; beside it, this certificate: 6 of 7 signals read, the laboratory can be checked, a person looks at it, a signal is never a verdict and nothing is held by this page — Each certificate read against the supplier's own run of certificates, the one open here marked.

11 structural features.

Field order, label vocabulary, header, footer, date and units style, line shape, and the laboratory's details.

This supplier's own file.

A certificate template rarely changes from one lot to the next.

A change is a question.

Raised for a person to ask about, with the features that moved.

The public record keeps movingLots and suppliers on file re-matched to FDA enforcement every hour.

Monitoring on a sample pharmacy: 17 lots in the watch and 2 recall matches, lots added a week over 40 days by supplier with the recall matches marked; what matched: 2 raised, both declared or reported; and the note that the demo's sample lots stay out of the hourly re-match against FDA's enforcement records — Every lot on file in the watch, by supplier, and what matched and on what basis.

Every hour, not only at read.

Against openFDA enforcement records, across accounts by lot number.

A hit holds the lot.

And marks every Passport minted from it, so the signal reaches what has already gone out.

A person judges the match.

An identical re-match never reopens a dismissal a person already made.

The file's own bytesSeven findings read from the PDF itself, raised for a person.

Document integrity, 17 signals: the 7 read in the file on every read, each with what it reads and the files it applies to: edited after it was issued, made by an unexpected tool, the text layer disagrees with the page, font anomalies, unnatural number patterns, a dead or mismatched verification link and an unknown laboratory — The seven signals read from the file itself, and the kind of file each one can fire on.

Seven findings.

From a file created after the date it claims to an incremental edit stack.

A high contradiction holds the lot.

Such as a file created long after the issue date it prints.

The producing tool alone is never raised.

It is recorded, not held against the document.

Made, not issued. Thirteen signs Veritura reads for.

A certificate can be generated from nothing, by a template or by a language model. Each sign is raised for a person.

What the text gives away

Language-model boilerplate, an unfilled template placeholder, a sample disclaimer left in.

What a real issuer gets right

Where a fake slips: an impossible phone number, a ZIP code in the wrong state, a malformed accreditation number.

What measured data looks like

Uniformly round values, inconsistent units, an unregistered laboratory with no anchor.

Labelled as AI-made

A content-credentials manifest that says AI made it holds the lot on its own.

The page shows the results. The file shows how it was made.

Every file goes through the same pass. Each signal fires only where the file allows it: a page for a reused signature, a PDF for its edit history.

Every file's pass17document-integrity signals, fired only where the file allows

File internals7findings read from a PDF's own metadata

Made, not issued13signs a certificate was generated rather than issued

Supplier history11template features compared, from field order to email domain

A signal is a reason for a person to look, never a verdict. No signal is not proof a document is genuine.

The full detail.

Every signal, every sign of a generated document, and every source a document is read against.

The checks behind every read, in the methodology

The file itself 7 signals

PDF edit history: The file's incremental saves: a document changed after it was issued.
Producer and creator: The tool the PDF names as its producer or creator, recorded. The name alone is never raised.
Font anomaly: Fonts that change inside a field or a line where a genuine report would not.
Digit distribution: The spread of digits across the results, set against what measured values produce.
Text layer mismatch: A text layer that says something different from what the page image shows.
Dead or mismatched verify link: A verification link printed on the certificate that does not resolve, or resolves to something other than this lot.
Unknown laboratory: A testing laboratory that cannot be matched to a known one.

Across your records 10 signals

Lot collision: One lot number on documents that should not share it.
Cross-substance lot collision: One lot number used for two different substances.
Report ID collision: One report or certificate number on two different reports.
Document hash reuse: The identical file filed as evidence for something else.
Signature reuse: The same signature image found on other documents.
Stamp reuse: The same stamp image found on other documents.
Template mismatch: A layout that does not match the issuer's known template.
The same embedded image: An image embedded in the file that also sits in another record's file.
The same rendered page: A page that renders the same as a page already on another record.
The same picture of the page: An image or page that looks the same as one already on another record.

FDA records beside the 17

FDA recall match: The lot or firm matched in openFDA enforcement records.
FDA import alert match: The firm matched in FDA's import alert database.
FDA registration lookup: The named manufacturer's status in FDA's establishment registry.

Seven findings from the PDF's own bytes

Dates: Created after the date it claims; modified after creation with a re-save; a creation date in the future.
Tools and edits: An image-editor producer; an incremental edit stack; a creator and producer that disagree.
Attachments: Chromatography claimed with no trace attached.
What holds the lot: A high contradiction, such as a file created long after the issue date it prints. The producing tool's name alone is never raised; it is recorded, not held against the document.

Thirteen signs a certificate was made, not issued 13 signs

What the text gives away: Language-model boilerplate; an unfilled template placeholder; a sample disclaimer left in; contradictory sterility statements.
What a real issuer gets right: An impossible, placeholder or malformed phone number; a ZIP code in the wrong state; an accreditation number in the wrong format.
What measured data looks like: Uniformly round values; inconsistent units; an unregistered laboratory with no anchor; a content-credentials manifest that says AI made it, which holds the lot.
Where they come from: A certificate can be generated from nothing, by a template or by a language model. Each sign is raised for a person, and one of them holds the lot on its own.

What every document is read against

Sources: Your workspace, every Veritura account (counts only), the supplier's own history, openFDA enforcement, FDA warning letters and FDA import alerts. No affiliation or endorsement implied.
When: Public sources are consulted at read; openFDA enforcement records again on an hourly cycle.
A declared recall: A recall a person declares appears on the scan and Passport pages, attributed to whoever declared it, and emails every patient who saved a unit from the lot and every clinic desk on Veritura holding it.

A signal is a reason for a person to look, never a verdict on a document. No match in a public source is not proof of absence, and nothing leaves a lot until a named person has reviewed it.

Check a record yourself, with no account: verify a Passport or a Seal, or check an advertising claim. See the public tools

Questions, answered plainly.

The same file, report ID or lot number appearing where it should not: under another lot, another supplier, another substance or another date. Both records are linked and raised for a person to review side by side.

No. Strong identifiers are compared across every Veritura account, and each workspace sees only a count of the other accounts involved. No other party's name, supplier, file, lot or order is ever shown, and nobody sees yours.

At read, against openFDA enforcement, FDA warning letters, FDA import alerts, FDA's establishment and substance registries and its 503B list; and openFDA enforcement again every hour for lots and suppliers already on file. No match is a fact about the sources that answered, never a clearance.

No. A signal is a reason for a person to look. Veritura never calls a document forged, fake or fraudulent, and a document with no signal is not thereby proven genuine. Only the issuing laboratory's own recorded reply confirms a report.

Yes. A serial or a scan opens the public record with no account: the certificate's own lines, the supply chain by role and a fingerprint anyone can recompute. It holds no patient identity.

Still have questions? Talk to a person.