Diagnostic laboratories · copy only

Technical scoping, on a weeks-scale conversation

This is the agenda for a demo and technical scoping call with a lab director, molecular pathologist, lab operations lead, or diagnostics BD. It is not a service-level agreement and it does not promise a go-live date.

What the call covers

  1. Laboratory context. Diagnostic laboratory or hospital lab, the menu you want under your brand, and who signs a report.
  2. LIMS and webhook. Accession identifier, where a report-ready event should land, and the sandbox. Production keys come after that conversation, as the API page already describes.
  3. White-label. Domain, logo, report header and footer. The sample report in this packet is the layout under discussion.
  4. Sign-off. Decision-support, not diagnosis. Every interpretation is traced to evidence and signed off by a qualified human. The ordering clinician stays responsible for the clinical conversation.
  5. Modules. Multi-omic interpretation first (DNA, microbiome, blood). Clarity and Lens are the clinical and blood modules already on the platform. Wellness modules only if the laboratory asks for them.
  6. Commercial. Platform licensing plus a per-interpreted-report fee, from roughly $3–5 on top of the wet-lab you already run. A written quote is produced from the call. This page is not a price list.

Timing language already on the public site

The API page describes RESTful API onboarding in days (1–8 days) and white-label configuration in weeks (7–8 weeks). The FAQ describes a laboratory partnership cycle in months (3–6 months), including training and integration.

Those are the sentences already published. They are scoping inputs. They are not a contractual turnaround time. The call sets the calendar.

Diagnostic laboratories · Book the scoping demo · Proof packet