Implementation guide, Platform
How to share a test report securely and let anyone verify it
- Author
- PureField
- Published
- Updated
Sharing a test report securely means opening only the issued, signed report to the person you chose, with a password and expiry where needed. The recipient checks on the laboratory's verification page that it is genuine and current. If the report is amended or withdrawn, the link and the verification page say so, and a forwarded copy can still be checked.
How does a report verification page work?
A verification page tells anyone whether the report in their hands is one the laboratory issued, and whether it is valid today. In general:
- When the report is issued, its content is sealed and a digest (hash) is computed from it; a short form of the digest is printed on the report as its verification code.
- The report carries a verification address and a QR code; the QR code opens the page with the report's details filled in.
- The page shows the report's status: valid, amended or withdrawn.
- The recipient uploads the PDF they hold and compares it with the file the laboratory issued; a single changed byte shows the file was altered.
Because the verification page is public, it should show only the status, the laboratory, the issue time and the sample description. The results stay in the report itself, with the person you gave it to; that boundary is what protects customer information (§4.2).
When should you use a password and an expiry?
Narrow the sharing to whoever will see the report; when a report contains personal data, use a password and an expiry together. Example choices:
| Case | Validity | Password |
|---|---|---|
| QR code on a package, open to consumers | No expiry, or 1 year | None; the report holds no personal data |
| Customer forwarding to its own customer | 30 or 90 days | Yes |
| Auditor or regulator | 7 or 30 days | Yes |
| Report naming a patient or an employee | 1 or 7 days | Yes |
| Tender file | 30 or 90 days, by the tender timetable | Depending on who will open the file |
Send the password by a different route from the link: if the link goes by e-mail, give the password by phone or in a separate e-mail. Whoever receives the link can pass it on; an expiry limits that risk over time, and revoking the link closes it at once.
What happens when a report is amended or withdrawn?
An issued report stays exactly as issued; §7.8.8 asks for the correction in a further document that states the changed information and, where appropriate, the reason, with the new report referring to the one it replaces. If the report is too wrong to correct, it is withdrawn under the nonconforming work process (§7.10) and the customer is notified where necessary.
The real work is in the copies already out there: the first report may have gone by e-mail, onto a package or into a tender file. So:
- Let the QR code and the share link open the current revision of the report number, rather than one fixed file, and say that an amendment exists.
- Let the verification page show the old revision as "amended" and a withdrawn report as "withdrawn".
- Let the link to a withdrawn report open a page saying the report is no longer valid, in place of the report.
- Notify the customer; if they know who they passed the report to, they should tell them too.
How do you handle uncontrolled copies?
An uncontrolled copy is any copy the laboratory can no longer follow after sending: a forwarded attachment, a printed page, a PDF added to another file. Its validity is read from the verification page, not from the file itself.
- Put the report number and page number on every page (for example 2 / 5), so that a loose page shows which report it belongs to (§7.8.2.1 d).
- Include the statement that the report may not be reproduced except in full, and the verification address.
- Ask recipients to verify a report before using it, especially when the report is old.
- On your side, label every link with who it was given to, and revoke links whose job is done.
What does KVKK mean for a report that contains personal data?
If a report names a patient or an employee, or holds health information about a person, what you are sharing is personal data, and you narrow the sharing accordingly.
- Health data is a special category of personal data (KVKK Article 6); share such reports through a password-protected, short-lived link.
- The data controller takes the technical and organisational measures needed to prevent unlawful access to personal data (Article 12). Sending the password on a separate channel, setting an expiry and revoking finished links are examples of such measures.
- Attach only reports free of personal data to public links such as a package QR code.
- Word a withdrawal reason so that it contains no personal data and no other customer's name; the customer may be shown the reason.
Evidence
- ISO/IEC 17025 (2017 edition)
- Confidentiality §4.2.1, review and authorization of results and retention of reports §7.8.1, report content and the note on partial reproduction §7.8.2.1, amendments to reports §7.8.8, notifying the customer and recalling work in nonconforming work §7.10.1, protection of the laboratory information management system §7.11.3. Source: iso.org
- Law No. 6698 on the Protection of Personal Data (KVKK)
- Health data as a special category of personal data (Article 6) and data security obligations (Article 12). Source: kvkk.gov.tr
To see the share link and the verification page on a sample report, request a PureField LIMS account.
Frequently asked questions
Does the verification page show the results in the report?
Can a share link's expiry be extended?
What does the QR code show after a report is amended?
How can I tell that the PDF I hold has not been altered?
From which networks does a share link open?
Related links
- PureField LIMSReport verification, share links and assessor access.
- Report share linksvalidity, password, QR code and the opening log.
- Sharing evidence in a remote accreditation assessmentLeast privilege, separate channels, time limits and a view log.
- How to run a vertical auditTracing one report back to sample receipt.
- ISO/IEC 17025 document controlControlled and uncontrolled copies.
