Sample report · fictional demo data
Sample pathology lab report, with a live QR verification page.
This is the report a patient and referring doctor receive from a lab on PathLab Software, built from the demo workspace. Every name, number and value on it is fictional sample data. The verification page it links to is real: open it, and you see exactly what a doctor, insurer or employer sees when they scan the QR.
Verification code SAMPLEDEMO · demo workspace · not a real patient record
SRI LAKSHMI DIAGNOSTICS
Sample data · fictional lab and patient
01-10-2026 · 10:42
Complete blood count
| Test | Result | Unit | Ref range |
|---|---|---|---|
| Haemoglobin | 10.8 L | g/dL | 12.0–15.5 |
| WBC | 7,400 | /µL | 4,000–11,000 |
| Platelets | 2.6 | lakh/µL | 1.5–4.0 |
| ESR (1st hour) | 28 H | mm/hr | 0–20 |
Delta: Hb ↓ from 11.2 (previous visit). Kindly correlate clinically.
Dr. S. Anand
Dr. S. Anand, MD Path
Signed electronically 10:42 · verify by QR
Sample data: fictional lab, patient, doctor and pathologist. Simplified preview; the full report is on the verification page.
How this report was produced and validated
Five steps happen before any report leaves the lab. Each one is recorded with the user and the time, and nothing reaches WhatsApp before step 4.
Register and barcode
The front desk registers the visit, records WhatsApp consent and prints a barcode such as LS-10234 for the tube.
Results in
Values arrive from the analyzer, matched by barcode, or are typed by the technician. Age- and sex-specific ranges, H/L flags, critical limits and a delta check against the last visit apply automatically.
Technician review
The technician checks flags and saves. A saved result is not a released result.
Pathologist validates and signs
Only a user with validate rights can release. The signer's name, title, registration number and time are recorded, and a SHA-256 fingerprint of the issued report is stored.
Deliver and log
The signed report and its verification link go to the patient (if consented) and to the referring doctor on WhatsApp; each send is logged against the report.
What the signature and QR code mean today
Plain answers, including what is not built yet.
| Element | What PathLab Software does | Status |
|---|---|---|
| Two-level validation | Technician saves; only a user with validate rights can sign and release. The app refuses to release otherwise. | Live |
| Electronic signature | Name, title, registration number and signing time of the logged-in pathologist printed on the report and kept in the audit trail. | Live |
| Report fingerprint | SHA-256 hash of the issued report stored at signing and shown (shortened) on the verification page. | Live |
| QR verification | QR and 10-character code open the lab's verification page with the report as stored; each check is counted. | Live |
| Amended reports | Re-validation marks the report Amended and re-signs it; the verification page shows the amended status. | Live |
| Digital signature certificate (DSC, PKI) | Cryptographic signing with the pathologist's Class 3 DSC. | Planned |
| PDF attachment on WhatsApp | Today the message carries the verification link, which opens a print-ready report the reader can save as PDF. A direct PDF attachment depends on the lab's WhatsApp provider set-up. | Partial |
What the receiving party can verify
A patient, referring doctor, insurer or employer who scans the QR can check the copy in hand against the issuing lab's record.
| Check | How | What it proves | What it does not prove |
|---|---|---|---|
| The report exists | Scan the QR or type the code at the lab's /verify page | A report with this code was issued by this lab | That the paper in hand has not been altered (compare the values) |
| Who signed and when | Signer, title and signing time on the page | Which user account released it, as recorded by the lab | A PKI-level identity check of the signer (DSC is planned) |
| The results match | Compare every value, unit and range with the page | Whether the copy matches the lab's stored report | That the result is clinically correct; that is the pathologist's and clinician's judgement |
| Current status | Status line: signed, sent or amended | Whether the lab has since amended the report | Why it was amended (ask the lab) |
| Integrity fingerprint | Shortened SHA-256 on the page | Which version of the report the lab issued | Anything on its own; it is a reference for the lab's audit trail |
Verification pages are not indexed by search engines, are rate-limited per IP address and are reached only through the code printed on the report. Results relate only to the sample received and must be read by a clinician.
Why we publish a sample instead of a screenshot
A screenshot proves nothing; a verification page you can open does. The sample report above is generated by the same code that signs reports for a live lab, from the demo workspace that new labs explore during the free trial. Because the demo uses fictional people and a fictional lab, the verification page carries a "Sample report · demo workspace" banner so nobody mistakes it for a real record.
If you run a lab, try the same flow on your own trial workspace: register a patient, enter or simulate analyzer results, validate as the pathologist and open the QR. See how reports reach WhatsApp, what the referring doctor receives, and the ISO 15189 records each step leaves behind.
Sample report questions
Is the sample report a real patient report?
No. It comes from the PathLab Software demo workspace: the laboratory, patient, referring doctor, pathologist, GSTIN and phone numbers are fictional sample data. The verification is real, though: the code, signer, time, status and SHA-256 fingerprint on the /verify page are read from the database exactly as they would be for a live lab.
Is the signature a digital signature certificate (DSC)?
Not yet. Today PathLab Software applies an electronic signature: only a logged-in user with validate rights can sign, and the signer's name, title, registration number and time are recorded, shown on the report and kept in the audit trail, with a SHA-256 fingerprint of the issued report. Signing with a Class 3 DSC (PKI) is planned.
What can a doctor, insurer or employer verify from the QR code?
Scanning the QR opens the issuing lab's verification page for that report. It confirms that a report with this code exists in the lab's records and shows the lab, patient name, age and sex, signer, signing time, status (signed, sent or amended) and the full results, so the reader can compare them with the copy in hand. It cannot confirm that the results are clinically correct.
What if a report was changed after it was issued?
If the lab re-validates a report, the verification page shows it as Amended with the new signing time, and the audit trail records who changed it. If someone edits a printed or PDF copy outside the lab, the values will not match the verification page, which is the point of checking.
Can anyone browse other reports from the verification page?
No. Each report has a random 10-character code that is only printed on that report and sent to the patient and referring doctor. The page is not indexed by search engines, guessing is rate-limited per IP address, and every verification is counted against the report.
Issue your own first verified report in the free trial
14 days, no card. We load your test master and report header during the free setup.