Lab Director technical scoping checklist

A pilot call is not a product tour. It is the session where a lab director, molecular pathologist, lab operations lead, and diagnostics BD decide whether a white-label interpretation layer can sit on the wet-lab and LIMS you already run - under your brand, with a qualified human on the report.

This checklist is the agenda for that call. Every item maps to a file or page already live: the laboratory proof packet, the weeks-scale scoping outline, and the API and white-label surface. Nothing here invents a certification, a customer logo, or a go-live date.

1. Who is in the room - and what they own

Bring the people who own the work, named the way the work is named:

• Lab Director - the menu, the quality system, and what leaves the laboratory under your name
• Molecular Pathologist - interpretation workload and the report that waits while clinical findings are routed to a qualified human
• Lab operations - accession, report standardisation, and getting the file back into the LIMS
• Diagnostics BD - partner-branded multi-omic offer for chains and hospital labs

If one of those seats is empty, someone else will guess - and the guess will break later. Put the missing owner on the calendar before you debate modules.

2. Laboratory context: menu under your brand

Ask (and answer) before demos scroll:

1. Diagnostic laboratory or hospital lab?
2. Which assays already run in-house - and which interpretation menus you want under your brand first?
3. Who is qualified to sign a report today?
4. Is the first wedge separate DNA, microbiome and blood reports under the laboratory's brand (the laboratory's doctors keep the final say), clinical modules already on the platform (Clarity / Lens), or both?

Keep wellness modules off the default ask unless the laboratory requests them. Diagnostic-lab deployments lead with the interpretation layer, not a consumer kit story.

3. LIMS and webhook - sandbox first

The published integration path is REST and JSON, OAuth 2.0, a sandbox, and webhooks when a report is ready. HL7/FHIR R4-compatible exchange is described for EHR and LIS integration. Public endpoint families on the API page include /v1/samples, /v1/reports/{id}, microbiome routes, and blood overlay.

On the call, map:

1. Accession identifier - what your LIMS already uses
2. Webhook destination - where a report-ready event should land
3. Sandbox - test before production keys (the API page: sandbox access day 1; production keys after onboarding)

Do not exchange production credentials on a first scoping call. The example webhook JSON in the proof packet uses public endpoint names. It is an illustrative schema for the conversation - not a production contract and not a credential.

4. White-label: brand files that must be real

White-label is not a logo pasted on a PDF. Confirm you can supply:

• Domain (or subdomain) for the patient / practitioner surfaces
• Logo, colour palette, typography
• Report header, footer, and cover expectations
• Language needs already listed publicly (English, Arabic, Turkish, and more)
• Tonality by role - patient-facing vs clinician-facing depth

The sample partner-branded report in the proof packet is the layout under discussion. Open it, Print → Save as PDF. It is structure only: not a patient result and not a diagnosis. Do not forward it as either.

5. Routing clinical findings and the decision-support boundary

State this boundary early:

Ask the vendor (including us):

1. Are clinical findings routed to a qualified human before a report ships?
2. Where does each interpretation trace in the report a clinician can open?
3. Is marketing language consistent with that boundary across site, deck, and contract?

Compliance line already published: ISO 9001:2015 certified · pursuing ISO 13485 · GDPR compliant. Cite it exactly. Do not invent CAP, NABL, or other marks that are not on the public site.

6. Timing language already published - not an SLA

Use only the sentences already on the public site:

Those are scoping inputs. They are not a contractual turnaround. The call sets the calendar. If a deck promises a go-live date before LIMS mapping and brand files are agreed, treat that as a red flag - including if it is ours.

7. Commercial scope without turning the page into a price list

Commercial terms are agreed on the pilot call. A written quote is produced from the call. This checklist is not a price list.

Ask what surrounds the headline number: setup, minimums, volumes you actually run, and exit terms for your accumulated report history. Bring your real volumes; do not model from brochure volumes.

8. Proof packet leave-behind (open these in the meeting)

Nothing in the packet is a named customer, a revenue figure, or a clinical claim.

Closing

If you run a diagnostic laboratory and want the interpretation layer under your brand:

1. Open the proof packet
2. Book a pilot call with the seats above
3. Read the diagnostic laboratories page for the conversion path

Building under your brand? Start at labs - then bring this checklist to the call.

FAQ