NGS LIS Workflow: From Extraction to Signed Report

Next-generation sequencing labs run some of the most procedurally complex workflows in clinical and research diagnostics. A single accession can travel through eight or more wet-lab and dry-lab stages, touch three or four instruments, get pooled with dozens of unrelated samples, and only resurface days later as a VCF that still needs annotation, classification, and a clinically meaningful narrative. An NGS LIS that does not understand this pipeline shape ends up working against the lab. One built around it can compress turnaround time, reduce repeat work, and give directors a defensible audit trail from receipt to signed report.

This post walks through how LIMS IQ models an end-to-end molecular LIS workflow and where it plugs into the surrounding instrument and bioinformatics stack.

Stage 1: Accessioning the Molecular Order

Every NGS case starts the same way every other lab order does: receipt, demographics, requisition capture, and test selection. What changes for molecular is what comes downstream of that test code. When an oncology somatic panel, a hereditary cancer panel, or a syndromic respiratory NGS panel is ordered, the LIS needs to know which downstream library prep workflow, panel design, and reporting template to bind to that accession from the moment it lands.

LIMS IQ ties test codes to a configurable test catalog with method, specimen, and analyte definitions so accessioning staff do not have to remember which tests funnel into which kit. Specimen container, minimum volume, and rejection rules can be enforced at receipt rather than discovered in the prep room.

Stage 2: Extraction and Pre-Analytical Tracking

Once accessioned, samples enter extraction. Most NGS labs run nucleic acid extraction in racks or on a robotic platform, and they need the LIS to:

• Track which extraction protocol was used and on which instrument
• Capture extraction date, technologist, and any deviations
• Record yield and 260/280 / 260/230 ratios from the spec
• Flag samples that fail input quantity thresholds before they consume reagents downstream

Sample identifiers ride through this stage as barcoded labels. LIMS IQ supports barcode generation at accessioning and rescans at every transfer, so a tube moving from primary container to extraction plate to library plate carries a verifiable chain rather than a handwritten log.

Stage 3: Library Preparation and Plate Map Management

Library prep is where NGS workflow management gets meaningfully different from a chemistry LIS. A single library prep batch may include twenty-four or ninety-six samples, each indexed with a unique i5/i7 combination, all bound to one reagent kit lot.

The LIS responsibilities at this stage:

• Plate map management. Map each accession to a specific well on the prep plate, lock index assignments to wells, and prevent index collisions inside a sequencing pool.
• Reagent and kit lot tracking. Bind kit lot, enzyme lot, bead lot, and adapter lot to the batch so that any future investigation can pull every sample touched by a given lot.
• Control lot tracking. Positive controls, NTCs, and reference materials live alongside patient samples on the plate and are recorded with their own lot and expiry.
• Batch-level QC gates. Library quantification (Qubit, qPCR, TapeStation/Bioanalyzer fragment size) is captured per sample and per pool, with pass/fail thresholds that block release to the sequencer.

Because plate maps drive both wet-lab and bioinformatics, LIMS IQ exposes them as structured data, not just a printed grid.

Stage 4: Sequencing Run and Instrument Integration

When a pool is loaded, the LIS hands off to the sequencer. LIMS IQ supports instrument integration patterns for the platforms most NGS labs run, including Illumina (NextSeq, NovaSeq, MiSeq), Thermo Fisher Ion platforms, and Oxford Nanopore. Integration generally covers two directions:

• Outbound: sample sheet generation, with the plate map, indexes, and run parameters written in the format the instrument expects, eliminating the most common source of run failures.
• Inbound: run metadata returning to the LIS — run ID, flow cell, cluster density, %Q30, total reads per sample, and run status.

Run-level QC values land back on the batch record so a director can audit performance trends across runs and kits without exporting CSVs from the instrument.

Stage 5: Bioinformatics Pipeline Handoff

After sequencing, FASTQs move into the bioinformatics pipeline. The LIS does not run the pipeline, but it owns the metadata that the pipeline depends on: which sample is which, which panel design applies, which reference genome to use, and which report template to populate.

LIMS IQ supports the handoff in both directions:

• The LIS publishes the sample manifest and panel context that the pipeline consumes.
• When variant calling, annotation, and tertiary analysis complete, results — VCFs, coverage metrics, copy number calls, fusion calls — are imported back and reattached to the originating accession. They are not stored as orphan files; they become structured data tied to the order, the run, the prep batch, and the patient.

This is what makes “everything for one case is in one place” actually true at report-out time.

Stage 6: Variant Review and Structured Reporting

A clean VCF is not a report. Reportable findings depend on case context:

• Germline panels report inherited variants with ACMG-style classification and clinical significance.
• Somatic oncology panels report tumor-only or tumor/normal findings with tier classification, therapy associations, and clinical trial considerations.
• Syndromic infectious disease panels report organism detections with semi-quantitative results and antimicrobial resistance markers.

LIMS IQ binds each panel to its own report layout, including the controls and QC summary that should print on the report, the variants that should populate the table, and the boilerplate methodology block. Reviewers can confirm coverage thresholds, accept or reject individual variant rows, and add interpretive narrative before signing.

QC review is enforced as a gate. Levey-Jennings tracking for control performance over time helps the lab see drift before it becomes a recall conversation.

Stage 7: Turnaround Time and Operational Visibility

Across all of the above, the LIS is also a stopwatch. Each stage transition — received, extracted, library built, sequenced, analyzed, reviewed, signed — becomes a timestamp. That lets the lab compute true TAT distributions, identify where batches stall (often library prep queueing or bioinformatics handoff), and report performance to ordering clinicians and accreditors.

For molecular directors, dashboards over this data convert “we feel slow this month” into a defensible operations conversation.

Compliance Posture

Molecular labs running clinical assays have to meet the documentation expectations of CLIA and CAP, and they handle PHI under HIPAA. LIMS IQ is built so the LIS supports those programs as capability areas — audit trails, role-based access, validation documentation, controlled change management, and retention of QC and lot history are all first-class. Specific attestations remain the lab’s to earn, but the platform is designed to make that achievable rather than retrofit.

Bringing It Together

A working NGS LIS workflow is less about any single feature and more about whether the system can carry one identifier coherently from accessioning through extraction, plate map, pool, run, pipeline, and signed report — and surface the right structured data at the right step. That is the design center for the molecular ID solution and the NGS workflow configuration in LIMS IQ, both running on the broader cloud LIS platform.

If you are evaluating an NGS LIS — whether you are scaling from a single sequencer to a multi-platform lab, or replacing a system that was never designed for molecular — we would be glad to walk through your workflow stage by stage. Request a demo and we can map your panels, instruments, and report formats against what LIMS IQ supports out of the box.