Delivery & enabling technology · Case study

qHTS: automate the evidence, then measure the workflow

The NIH titration-screening example shows why a richer experiment can matter more than a throughput ranking.

ClarusBIOTECH REVIEW

Read, listen & keep

Download article

Narration has not been recorded for this article’s current text. The written article is available to download.

Clarus Biotech Review · 9/30/2026 · 2 min read

Revised September 30, 2026 · Historical case analysis

Automated pipetting workflow paired with a conceptual computational network for laboratory data integration
Conceptual editorial composite. Automated pipetting workflow paired with a conceptual computational network for laboratory data integration. Not experimental imagery; biological scales are illustrative.
Browse the case and research collection
THE DOCUMENTED RECORD

Dates, outcomes, and decision boundaries

Historical observations. Context identifies the population, period, or accounting basis.
MeasureReported resultContext & source
Publication2006NIH quantitative screening example [1]
Library scaleMore than 60,000 compoundsPyruvate-kinase experiment [1]
Titration design7 or more concentrationsConcentration–response information [1]
Plate format1,536 wellsWorkflow-specific experimental format [1]

The study does not supply a current instrument price or a demonstrated return on investment for an LNP laboratory. The suggested metrics require a representative workflow test.

The 2006 NIH quantitative high-throughput screening study provides a laboratory-automation example with a defined scientific output. Inglese and colleagues tested a titration-based screen using pyruvate kinase. The method generated concentration–response information for more than 60,000 compounds rather than treating each compound as a single-point measurement. [1]

Start with the information required

The workflow used seven or more concentrations and a 1,536-well format. Its purpose was to characterize biological activity, potency, and response patterns across the library. The authors' comparison with a single-concentration screen identified an important false-negative problem. The benefit therefore concerned the information returned by the experimental design, not just the number of plates handled. [1]

Measure usable output instead of machine motion

A procurement scorecard should define what constitutes an acceptable concentration–response result, how controls behave, and which failures require repetition. Plate throughput alone can rise while interpretable output falls. For an EV or LNP development laboratory, the corresponding output might be a reproducible characterization record; that is a different workflow and needs its own demonstration.

Put integration burden into the cost model

Include sample preparation, compound or reagent management, calibration, data processing, service, staff intervention, and reruns. A robot that moves material rapidly may still move the bottleneck into assay interpretation or data reconciliation. The original scientific paper does not provide a turnkey procurement budget for a modern configured workstation.

Make the investment decision falsifiable

Ask a supplier to demonstrate the intended workflow with representative samples and predefined acceptance criteria. Compare cost per accepted result, operator intervention, and recovery from a failed run. The qHTS example illustrates a successful research workflow, while the transfer to another laboratory remains a validation task. Vendor rankings should follow that task definition rather than substitute for it.

Source adaptation: the stored automation scorecard inspired the procurement lens. This public NIH case replaces time-sensitive vendor rankings with a specific assay-design example.

CLARUS OPERATING ANALYSIS

What to measure for the next decision

Suggested planning KPIs—not reported outcomes from the historical program.
DimensionKPI to collectDecision use
Quality-adjusted throughputAccepted response curves per runUse predefined assay and control criteria.
ReliabilityInterventions and reruns per accepted resultCount recovery effort rather than ignoring failed runs.
Operating costFully configured cost per accepted resultInclude service, consumables, and interpretation.

THE NEXT VALUE INFLECTION

What would change the decision

Ask a supplier to demonstrate the intended workflow with representative samples and predefined acceptance criteria. Compare cost per accepted result, operator intervention, and recovery from a failed run. The qHTS example illustrates a successful research workflow, while the transfer to another laboratory remains a validation task. Vendor rankings should follow that task definition rather than substitute for it.

Explore more in Delivery & enabling technologyConnect this perspective to Value Inflection EngineeringVisit BioClarus Consulting

Editorial record

Prepared by Clarus Biotech Review editorial team. Updated 10/1/2026.

Publication relationship: ClarusReview is connected to BioClarus Consulting. No article-specific sponsorship is recorded.

Report a correction
Reading list & subscriptions
CLARUSREVIEW COMMUNITY

Discuss this paper

Open full discussion

Share evidence, ask a question, or offer a professional perspective. Community guidelines

Loading discussion…