Guide
Patient record pages
Two public pages carry the record to the person holding the medicine. Both live on verify.veritura.co: the host printed QR codes point at, maintained permanently: and both are written in plain language for a patient, not an operator.
The unit record: /u/<serial>#
This is the page a scanned seal opens. It answers, in order:
- Is this the real thing? The headline verdict, live at scan time, with the medicine and batch directly under it. A serial that was never issued, or was altered, does not resolve at all: there is no page to counterfeit against.
- Is anything wrong with its batch? Any notice or recall standing on the batch appears here, at scan time: not as of printing.
- What does the paperwork say? The certificate values Veritura transcribed from the laboratory paperwork, with the note that the source certificate stays with the pharmacy.
- Who do I call? The dispensing pharmacy, with an optional tap-to-call contact set in Settings.
- Recall alerts: an optional email signup; see privacy.
The three headline states#
| State | Headline | When |
|---|---|---|
| Green | "This vial is on record" | The serial resolves and nothing stands against its batch. |
| Amber | "There is a notice on this vial's batch" | A hold or notice stands on the batch; the page says what kind and who to contact. |
| Red | Recalled | A recall stands on the batch. The page leads with it. |
The passport record: /verify/<share>#
The Evidence Passport's share link opens the released, document-side record for one order: the product, the batch, the order reference, its status, the supply chain (who made it, who dispensed it: shown once when they are the same pharmacy), and the transcribed test rows. A link whose record was never released answers exactly that: no released record exists for this link. Share links are minted by passport issuance.
Privacy#
- Scanning sends Veritura nothing about the patient: no account, no login, no identifiers.
- The recall-alert signup keeps the email and the vial's code, nothing else: never a name, never a prescription.
- Order references printed on labels are opaque by construction: entries that look like patient information are refused at mint time.
Building a native experience#
The pages are powered by two unauthenticated endpoints: GET /api/verify-unit-public and GET /api/customer-passport/<share_id>: documented in public records. A pharmacy app may render its own verification view from them; the boundary language must survive the rendering.