LIMS / API integration expectations for diagnostic laboratories

“Weeks not months” is the line laboratories hear when a vendor talks about LIMS and API integration. Lab directors, molecular pathologists, lab operations leads, and diagnostics BD need a sharper sentence: which path, which calendar language already on the public site, and what is not promised until accession mapping and brand files are agreed.

This piece is that sentence. It cites only the live API and white-label surface and the diagnostic laboratories page: REST and JSON, OAuth 2.0, sandbox, webhooks when a report is ready, HL7/FHIR R4-compatible exchange for EHR and LIS, and the published timing bands. Nothing here invents an SLA, a customer logo, or a production contract.

1. What "integration" means for a diagnostic laboratory

You keep the wet-lab, the accession, and the client relationship. The interpretation layer sits on top: DNA, microbiome, and blood read under your brand, with the file returned into the LIMS you already run.

Two published paths exist today (API page):

A laboratory can take either path, or both. The labs page leads with white-label multi-omic interpretation delivered into the LIMS by API and webhooks. The API page describes the same exchange for teams that want to embed intelligence without standing up the full branded surface on day one.

Public endpoint families already listed:

• /v1/samples
• /v1/reports/{id}
• Microbiome routes (gut samples, strains, prebiotics, diversity)
• Blood overlay (/v1/blood/overlay and related blood panel routes)

Auth and exchange language already published: REST and JSON, OAuth 2.0 with scoped API keys, webhooks for real-time delivery when reports are ready, HL7/FHIR R4-compatible data exchange for EHR and LIS.

The platform kernel noun used on the labs page is Evolveme - the white-label interpretation layer. That is the stack noun for this conversation. It is not a consumer storefront story.

2. Sandbox-first path - day 1 before production keys

The API page states the order plainly:

1. Sandbox access day 1 - exercise sample push, report pull, and webhook receipt against non-production keys
2. Onboarding call - map accession identifiers, webhook destination, and who signs reports
3. Production keys after that call - not before LIMS mapping is agreed

Do not exchange production credentials on a first scoping conversation. Bring the LIMS owner and whoever signs reports. The weeks-scale scoping outline is the agenda: laboratory context, LIMS and webhook, white-label brand files, sign-off boundary, modules, commercial frame.

Sibling checklist for the full room agenda: Lab Director technical scoping checklist.

3. Webhook into the LIMS you already run

The published event shape is a report-ready webhook for the accession in your LIMS. Lab operations care about three concrete fields on the call:

1. Accession identifier - what your LIMS already uses
2. Webhook destination - where the report-ready event should land
3. Report handle - how your stack pulls /v1/reports/{id} (or the equivalent delivery path you agree in scoping)

The example webhook JSON in the laboratory proof packet is shaped from those public endpoint names. It is an illustrative schema for the scoping conversation. It is not a production contract. It contains no credentials. Treat any vendor who hands you a "final" payload before sandbox testing the same way you would treat an unsigned SLA - useful as a draft, binding only after both sides agree the shape against your accession model.

HL7/FHIR R4-compatible exchange is the published language for EHR and LIS paths that need that envelope. Confirm on the call which envelope your LIMS actually accepts today - JSON webhook, HL7/FHIR, or both - rather than assuming the brochure path matches your middleware.

4. What "weeks not months" does - and does not - promise

Use only the sentences already on the public site:

Those bands are scoping inputs. They are not a contractual turnaround. They are not a go-live date. The scoping outline repeats the same caution: the call sets the calendar.

How to read the three bands without collapsing them:

• 1-8 days (API) - sandbox-to-first-production-key path for a RESTful cutover when accession mapping is clean and your team can consume JSON webhooks
• 7-8 weeks (white-label) - discovery → config → branding → UAT → launch for a partner-branded platform surface, with a dedicated project manager as the API page describes
• 3-6 months (partnership cycle) - the wider laboratory partnership window already published in the FAQ, including training and integration - useful for BD calendars, not a substitute for the API or white-label bands above

If a deck collapses all three into one "go live in two weeks" promise before LIMS mapping and brand files are agreed, treat that as a red flag - including if the deck is ours.

5. Red flags on an integration conversation

Calm filters a lab director can apply without inventing claims:

1. Production keys before sandbox - the published path is sandbox day 1, production keys after onboarding
2. Webhook treated as a signed contract on first contact - the proof-packet JSON is illustrative schema only
3. Timing stated as an SLA - published bands are scoping inputs; the call sets the calendar
4. Missing seats - no LIMS owner and no report sign-off in the room means accession and clinical boundary will be guessed
5. Diagnosis language - the interpretation layer is 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
6. Invented marks - cite only what is published: ISO 9001:2015 certified · pursuing ISO 13485 · GDPR compliant. Do not accept (or invent) CAP, NABL, or other marks that are not on the public site

Compliance line to keep exact:

6. Leave-behind links for the technical conversation

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

Closing

If you run a diagnostic laboratory and need a clear integration path into the LIMS you already operate:

1. Read the API and white-label page for endpoint and timing language
2. Open the proof packet - especially the example webhook JSON and scoping outline
3. Book a demo and technical scoping with Lab Director, Molecular Pathologist, Lab Ops, and Diagnostics BD in the room
4. Keep the diagnostic laboratories page as the conversion path for the partnership frame

Sandbox first. Webhook when the report is ready. Timing as scoping input - the call sets the calendar.

FAQ