Decision-support vs diagnosis
The compliance boundary lab buyers need before white-label interpretation - evidence trail, human sign-off, and why diagnosis language on a vendor deck is your risk.
When a diagnostic laboratory puts its name on a multi-omic report, the brand is signing the interpretation chain - not just the assay. Lab directors, molecular pathologists, lab operations leads, and diagnostics BD evaluating white-label interpretation need one sentence the room can share: what the vendor is allowed to claim, what the laboratory is responsible for, and where clinical responsibility stays.
That sentence is already public on the diagnostic laboratories page and in the laboratory proof packet:
This piece is the buyer-facing expansion of that boundary. It invents no accreditation, no customer logo, and no clinical claim beyond what the labs page, proof packet, and medical disclaimer already state.
1. Why the boundary matters to the laboratory brand
In a white-label arrangement, the partner laboratory keeps the client relationship and the wet-lab. The interpretation layer sits on top: DNA, microbiome, and blood read under the laboratory's brand, with the file returned into the LIMS. Your logo, colours, header, footer, and domain travel with the report.
That is the commercial upside - and the compliance exposure. A clinician or counsel who opens the report sees your name at the end of the claim chain. If the vendor's marketing says "diagnosis" while the contract (or the disclaimer) says "decision-support," the mismatch does not stay with the vendor. It lands on the laboratory that shipped the branded PDF.
Molecular pathologists feel this as sign-off workload and report language that must survive peer review. Lab operations feel it as accession discipline: nothing leaves the LIMS path without a recorded human review. Diagnostics BD feels it when a hospital or chain buyer asks whether the offer is a diagnostic product or an interpretation partnership. Lab directors own the quality system and what leaves under the laboratory name - so the boundary has to be boringly consistent before modules and price are debated.
2. What decision-support means operationally
On the labs page, decision-support is not a slogan. It is two operational commitments that sit on every report:
- Evidence trail - every interpretation traces to curated evidence. The public figure on the labs page and proof surfaces is 150,000 curated references behind interpretations (with 1,200+ validated biomarkers also stated on public proof surfaces). Citations belong in a report a clinician can open - not only in a vendor slide.
- Qualified human sign-off - every interpretation is reviewed and signed off by a qualified human before the report ships. Model QA is not report review. A pure-algorithm pipeline quietly shifts interpretive risk onto whoever receives the branded file.
The platform is an interpretation layer for laboratories that already run assays: your measurement, the reading, your brand on the report. Clarity (clinical modules already on the platform: gene panels, pharmacogenomics, and whole-exome interpretation) is released as decision-support for the ordering clinician. The Gene Box does not diagnose.
Where a platform-kernel noun is useful in scoping: Evolveme is the white-label interpretation layer named on the labs page. It is the stack noun for the partnership conversation - not a consumer storefront story.
The longer clinical frame - probabilistic genetics, no medical advice or diagnosis, PGx as informational support for prescribing conversations, full clinical context required, emergencies outside platform scope - lives on the medical disclaimer. Quote that page when a stakeholder needs the full statement; do not invent a shorter clinical policy in a deck.
3. What diagnosis language does to buyer risk
Diagnosis language on a vendor brochure is not a wording preference. In several markets, marketing copy helps define intended purpose. Diagnostic phrasing can reclassify how a product is read by a regulator, a hospital compliance officer, or a chain legal review - even when the contract quietly disclaims diagnosis.
Practical risk for the laboratory buyer:
- Brand mismatch - diagnostic claim in public copy, disclaimer in the footer, and your logo on the patient-facing PDF
- Sign-off ambiguity - "AI-powered diagnosis" in a deck while the operational path has no recorded human review
- Forwarding hazard - a sample layout treated as a real result because someone wanted a quick demo leave-behind
- Clinician conversation shift - the ordering clinician is still responsible for the clinical conversation; overclaiming language invites patients and referrers to treat the report as the clinical conclusion
Calm filter: if the vendor cannot say "decision-support, not diagnosis" in the same words on site, deck, contract, and report footer, stop the menu conversation until the language matches. Put that filter to every vendor - including us. The Five Questions piece already frames Q2 (who signs off) and Q4 (what marketing claims) the same way.
4. How to read vendor marketing (including ours)
Read public copy the way a Lab Director would before forwarding it to quality or legal:
| Signal | Prefer | Treat as a red flag |
|---|---|---|
| Intended purpose | Decision-support for the ordering clinician | "Diagnoses," "definitive," or "replaces the clinician" |
| Evidence | Citations in the report; curated base named with public figures only | "Proprietary algorithm" as the final answer; scraped bulk with no curation step |
| Sign-off | Qualified human review recorded before ship | "Fully automated" as a feature; "scientists validate the models" offered as report review |
| Sample assets | Branding / structure specimen; not a patient result | Sample PDF forwarded into a clinical channel as if it were live |
| Certifications | Exact published line, name / scope / status | Invented CAP, NABL, or other marks not on the public site |
| Timing / commercial | Published scoping bands; quote from the call | Timing stated as an SLA; customer logos or revenue as proof |
Compliance line to keep exact - copy it, do not paraphrase:
Full decision-support line as published with the compliance block:
Do not invent CAP, NABL, named laboratory customers, revenue figures, or service-level agreements. The labs page states what it does not add: named laboratory customers or accreditation counts beyond the published line. Founded in Mumbai in 2015; the engine powers reports for 39 partners across 11 countries - those figures are already public; do not expand them.
5. Proof packet and disclaimer leave-behinds
Use the files already built for this conversation. Nothing in the packet is a named customer, a revenue figure, or a clinical claim.
| File / page | Why it is on the table |
|---|---|
| Laboratory proof packet | Index of sample layout, example webhook JSON, scoping outline, compliance line |
| Sample partner-branded report | Branding and structure specimen only - Print → Save as PDF; must not be forwarded as a patient result |
| Compliance line | Exact certification + decision-support wording |
| Medical disclaimer | Longer clinical frame: not medical advice or diagnosis; ordering clinician responsibility; PGx informational |
| Lab Director technical scoping checklist | Sibling room agenda - sign-off and boundary section on the call |
| LIMS / API integration expectations | Sibling on sandbox, webhook, and timing-as-scoping-input (not SLA) |
| Five Questions | Vendor exam: evidence, sign-off, data, marketing claims, unit economics |
On the demo and technical scoping call, walk the partner-branded layout and the decision-support boundary with the people who sign reports. Brand files and who the qualified human sign-off is belong on the same agenda as accession and webhook destination.
Closing
If you evaluate white-label interpretation for a diagnostic laboratory and need the compliance boundary in writing before modules and price:
- Read the diagnostic laboratories page for the conversion path and published boundary
- Open the proof packet - sample layout as structure only; compliance line exact
- Keep the medical disclaimer as the longer clinical leave-behind
- Bring the Lab Director technical scoping checklist so sign-off is on the call agenda
- Book a demo and technical scoping with Lab Director, Molecular Pathologist, Lab Ops, and Diagnostics BD in the room
Decision-support, not diagnosis. Evidence on the report. A qualified human on the sign-off. The ordering clinician stays responsible for the clinical conversation.
FAQ
Does a white-label interpretation layer diagnose?
No. Decision-support, not diagnosis - every interpretation traced to evidence and signed off by a qualified human. The ordering clinician stays responsible for the clinical conversation. The Gene Box does not diagnose.
What should a Lab Director ask a vendor about sign-off and evidence?
Is a qualified human review recorded before a report ships? Where does each interpretation trace in a report a clinician can open? Is marketing language consistent with that boundary across site, deck, and contract? Put the same questions to every vendor - including us. See also Five Questions (/resources/five-questions-before-white-labeling-genetic-testing).
Can the sample partner-branded report in the proof packet be used as a patient result?
No. The sample layout is a branding and structure specimen. It is not a patient result and not a diagnosis. It must not be forwarded as either. The longer clinical frame is the medical disclaimer (/disclaimer).