Diomni Enterprise Software — 0→1 Clinical Platform

01 — The problem

The division rebuilt its software for every assay.

Thermo Fisher's clinical qPCR business ran on a traditional model: each new diagnostic assay and each instrument got its own software, built more or less from scratch. That approach was slow, expensive, and duplicative — every launch re-paid the same design and development cost, and the customer experience drifted between products. To stay competitive in molecular diagnostics, the division needed something different: one clinical platform that could carry many assays and instruments without rebuilding the software each time.

The bar was high. This is regulated, in-vitro-diagnostic (IVD) software — a lab tech runs a patient sample through extraction, qPCR, analysis, QC, and interpretive reporting, and the interface has to make that end-to-end workflow fast, unambiguous, and audit-ready. Getting it wrong isn't a bad review; it's a delayed or misread clinical result.

02 — My role

Sole designer on the MVP; design lead as it scaled.

I came to this from the Clinical Sequencing Division (CSD). The R&D software leader who had spearheaded Genexus — CSD's clinical NGS platform — moved to Genetic Sciences to level up its software, and recruited me from CSD to bring those design practices across. Diomni is where that cross-pollination landed.

I was the sole designer on the 0-to-1 MVP — framing the product concept, designing the full workflow, and running the customer research that de-risked it. As the platform gained traction and the team grew, I led its design across successive releases, partnering with a second designer while my responsibilities expanded — and I set the reusable design standard the rest of the division would build on. Because the goal was a platform, not a one-off app, the real design problem was less "what does this screen look like" and more "what system lets one experience flex across many assays and instruments."

03 — The approach

Design the system once; configure it many times.

Diomni didn't start from a blank page. I built on two proven foundations — Thermo Fisher's qPCR research (RUO) design & analysis software and the clinical-diagnostics paradigm behind Genexus, CSD's NGS Dx platform — and synthesized them into a single clinical qPCR platform, then extended that into the reusable framework the division needed.

Instead of designing another assay-specific app, I designed a reusable platform framework: a single, multimode interface where a new assay or instrument is configured into the experience rather than rebuilt from zero. We proved it fast — the MVP was designed and delivered end-to-end in three months — then hardened it release by release into a full end-to-end clinical workflow. A few of the moves that made it work:

Reusable framework

One multimode UI that supports many assays and instruments through configuration — so each new launch reuses the design instead of re-paying for it, with far less development and testing effort.

End-to-end workflow

Extraction, assay selection, run, analysis, QC, and interpretive reporting unified into one guided flow, with results delivered to the lab information system.

Guided interpretation

Turned raw qPCR output into a clear clinical call and report — the interpretation step designed to reduce ambiguity and manual, error-prone hand-offs.

Built for regulation

Designed for IVD use from the start and carried through the platform's IVDR release — traceability and consistency treated as first-class requirements, not afterthoughts.

On the design system

Moved the platform onto the enterprise design system for a consistent look and faster delivery, aligning it with the broader Thermo Fisher software portfolio.

Research-led

Voice-of-customer and feasibility sessions — including a spearheaded listening lab for a later release — kept each iteration grounded in how clinical labs actually work.

04 — The work

The platform, end to end.

Diomni spans the full clinical qPCR workflow — extraction, run setup, analysis, and reporting — behind one consistent interface. A walk through the shipped platform, stage by stage.

A note on the visuals: these are design screens with representative, non-confidential content — dummy sample IDs and demo assays, never real patient data. The design decisions are the point.

Platform dashboard

The lab's home base — extraction and qPCR volumes, run completion, and a searchable sample list across every run, so a lab manager reads status at a glance.

Diomni dashboard — extraction and qPCR summary counts with a searchable samples table

View full size ↗

Extraction — run list

Every extraction run in one filterable list with clear status states. This same list pattern is reused across the platform, so nothing has to be relearned between steps.

View full size ↗

Extraction — plate setup

Laying out a 96-well extraction plate: name samples, set types and controls, add comments — a fast, keyboard-friendly grid with a guided three-step wizard beneath it.

Diomni extraction plate configuration grid with a three-step wizard

View full size ↗

qPCR — run list

The qPCR run list mirrors the extraction list exactly — one interaction model the whole platform shares. Learn it once, use it everywhere.

View full size ↗

qPCR — build the run

Assigning assay definitions and target-set groups across the plate — color-coded for fast scanning, with copy/paste and sample import to fill 96 wells quickly. This configurable model is what lets one platform carry many assays.

Diomni create-qPCR-run plate layout with color-coded assay definitions and target groups

View full size ↗

Results — run summary

A run resolved at a glance: control results, and call counts by test code — positive, negative, invalid, inconclusive — with flags surfaced. The reviewer's first read.

Diomni run summary with control results and call counts by test code

View full size ↗

Results — plate details & amplification

The analytical view: an interactive plate call-grid tied to the amplification plot, with a per-sample results table — where the reviewer confirms the science before signing out.

Diomni results details — 96-well call grid, amplification plot, and per-sample table

View full size ↗

Results — interpretive report

Turning results into an audit-ready clinical report: a live preview beside report settings, with sort and scope controls, e-sign, and send-to-LIS — the last mile most platforms leave manual.

Diomni report builder with a live report preview and report settings panel

View full size ↗

05 — Outcome

A new design standard, shipped.

The MVP proved the model in three months; successive releases turned it into a full end-to-end clinical platform and carried it through the IVDR release. Internally it was called a "crowning achievement" and became a new design standard for the division — the reference other teams built toward.

The business impact was efficiency and reach: one platform that supports multiple assays and instruments with far less development and testing effort than the old per-assay model, positioning the qPCR and diagnostics business for continued strategic growth.

→

Outcome: MVP delivered in 3 months · adopted as a division-wide design standard · carried through the IVDR release · one platform spanning multiple assays and instruments.

Currently open

Have a 0-to-1 platform to get right?

Design the system once, ship it fast, and make it hold up under real regulatory and workflow constraints. If that’s the problem in front of you, let’s talk — open to product design roles in biotech and complex software.

Email me Connect on LinkedIn