Version 1.0 · Effective 5 August 2026 · Published by Terra Enabling Developers, Inc.
•
VERBATIM— mandated by an upstream provider or by law. Deploy exactly as printed; populate only bracketed slots where instructed. Deviation is a breach of your agreement with Terra, and Terra cannot agree variations.
•
REQUIRED CONTENT— the substance and every named entity are mandatory; you may adapt the wording to your application's style.
•
TERRA REQUIRED— mandated by Terra (not by an upstream provider or by law). Deploy as printed; Terra may agree a variation in writing.
| Question | If yes |
| Do you have UK end users? | All of §2, §3, §4, §5, §6 |
| Does your menu include genetic testing? | Genetic testing is not currently offered for UK clinical services — contact Terra before enabling any genetic flow; additional consent modules will be supplied |
| Slot | Populate with |
| [COMPANY NAME, COMPANY NUMBER, COMPANY ADDRESS AS APPLICABLE] / [COMPANY NAME] / [COMPANY] | Your legal entity (name; company number and registered address where the slot calls for them) |
| [description of services - e.g. …] | A plain description of your service |
| [Company consents if applicable] | Your own consent items, if any — as separate tick-boxes; do not intermix them with the Thriva wording |
| [COMPANY DPO contact details] | Your DPO or privacy contact |
| [COMPANY PRIVACY POLICY] | An active link to your privacy notice |
1.
Display the following Thriva-supplied text to the end user with their results — VERBATIM
2.
Acknowledgment gate — TERRA REQUIRED Before results are shown, the end user acknowledges readiness by an affirmative action — a checkbox (or equivalent) that un-gates the results view. On that action, call Terra's results-acknowledgment endpoint and promptly display the results in full. Never trigger the acknowledgment from webhook receipt, result retrieval, or any other backend event — it must evidence the end user's own action. If results remain unacknowledged, the laboratory provider's clinicians may contact the end user directly (see §2(a)).
3.
Escalation messages — VERBATIM Display the escalation message for each result exactly as supplied, keyed to the escalation level Terra delivers:
| Escalation level | Required copy (verbatim — do not paraphrase) |
| Very High | Please speak to a medical professional about this result as soon as possible. We recommend you do this today. |
| High | Please contact your GP within 24 hours to discuss the result. |
| Medium | Please contact your GP within 7 days to discuss your result. |
| Low | Please contact your GP for a routine appointment to discuss this result. |
| Very Low | We advise monitoring this result. If you experience any symptoms it is recommended that you speak to your GP. |
4.
Faithful rendering — REQUIRED CONTENT Display biomarker values, units, and reference ranges exactly as delivered, and display any doctor-written results report in full and unaltered.
5.
Display results in accordance with Terra's Results Display and Clinical Escalation Requirements — in full, unaltered, with escalation messages reproduced verbatim.
•
For every consent captured under §3, keep a record clearly setting out: who consented (name/identifier); when they consented (timestamp); what they were told (a confirmation of the consent wording version shown); and how consent was obtained (digitally or in person). Keep these records secured and in a machine-readable format.
•
Provide the records to Terra on reasonable request connected to a provider requirement, audit, or regulatory inquiry, and in the format and at the intervals reasonably requested.
•
Withdrawals: where an end user withdraws consent, inform Terra without delay so the withdrawal can be passed to the laboratory provider; if consent is withdrawn before the service is performed, the service cannot be performed.
•
Your consent-capture flow will be reviewed as part of your go-live demonstration, and these checks may be renewed at regular intervals.
•
Annually, and on Terra's reasonable request, attest in writing that your consent and disclosure flow conforms to this document and your agreement with Terra.
•
Keep your links (your privacy notice; the Thriva privacy notice URL inside the §3 wording; Terra's end-user disclosures page) pointing at the current versions.
•
Eligibility (18+). Enforce an age gate at checkout confirming the end user is at least eighteen (18) years of age, and do not offer testing to, or collect samples from, anyone under eighteen (18). The 18+ tick-box inside the §3 wording complements this gate; it does not replace it.
•
Capacity and identity. Implement appropriate systems and controls to ensure the services are not purchased or accessed by any individual who lacks capacity to consent, and not used or accessed by anyone other than the individual who provided the consent (self-order only — the §3 wording's self-order confirmation complements these controls).
•
Safeguarding contact. Where you are required to have a named Safeguarding Lead, share that person's contact details with Terra for provision to the laboratory provider, and cooperate promptly with any safeguarding check, investigation, or referral.
•
End-user details. Capture accurate end-user contact details, sex, and date of birth at order, and keep them current — they feed the provider's clinical-escalation and safeguarding processes.
•
Result-minimal notifications. Notifications sent outside the authenticated application (push, SMS, or email) must not contain result values, panel names, or health conditions; limit them to a readiness message and a secure login link. Result content is shown only after login and the §4 acknowledgment.
•
Rights-request routing. Route data-subject requests (including subject access requests) affecting the laboratory provider's processing to Terra promptly on receipt.
•
Do not edit, paraphrase, truncate, or restyle any [VERBATIM] block — the §3 wording may not be amended without the laboratory provider's prior written agreement, obtained via Terra.
•
Do not drop a named entity from a [REQUIRED CONTENT] block.
•
Do not bundle the §3 consent into your terms of service or any other acceptance, and do not satisfy any capture with a passive link, pre-ticked box, or inferred acceptance.
•
Do not fire the results acknowledgment from your backend.
•
Do not offer testing to, or collect samples from, anyone under eighteen (18), anyone whose capacity to consent is in doubt, or anyone ordering for a third party.
•
Do not import US-style liability releases, claims waivers, or results-timing elections into UK end-user flows — they are omitted from this document by design.
| Requirement | Source |
| §3 consent wording (mandatory verbatim) | Laboratory provider's Data Protection, Consent and Safeguarding Policy, Annex "Precedent Wording" (contractually incorporated; "should not be amended without our prior written agreement") |
| §2(a) privacy-notice disclosures | Laboratory provider contract conditions (downstream privacy notices must clearly disclose sub-processor sharing and independent-controller direct contact, naming the provider) |
| Lawful basis architecture | Testing consent: UK GDPR Art. 9(2)(a) (explicit consent — the §3 wording) + common-law confidentiality consent. Provider's urgent-contact basis (asserted by the provider as independent controller): Art. 9(2)(h) + DPA 2018 Sch 1 Pt 1 ¶2 — your flow owes disclosure (§2(a)), not a further consent |
| §4 results display copy | Provider-supplied patient-facing Disclosure Text (contract display-text mechanism) + Client Display Requirements (escalation copy, faithful rendering) |
| §5 records / withdrawals / go-live review | Provider's Data Protection, Consent and Safeguarding Policy (consent capture, records, withdrawals, evidence of compliance) |
| Why no release or claims waiver | Consumer Rights Act 2015 (incl. ss. 62, 65): consumer exclusions for negligence-caused death or personal injury are void; unfair-terms risk contaminates adjacent blocks |
| Third-party enforcement of end-user acknowledgments | Contracts (Rights of Third Parties) Act 1999 (the End User Agreement clause above); scope deliberately excludes releases (none exist in UK flows) and arbitration/class terms |
| Contractual carrier | The consent provision of your Order or Schedule (for customers on Terra's standard clinical agreement, Clinical Services Schedule §§C4 and C6A); Terra's Results Display and Clinical Escalation Requirements |
Cookie Preferences
Crunch Time: Embrace the Cookie Monster Within!
We use cookies to enhance your browsing experience and analyse our traffic. By clicking “Accept All”, you consent to our use of cookies according to our Cookie Policy. You can change your mind any time by visiting out cookie policy.