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 retain stage timestamps, structured handoffs, and a reviewable lineage 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. An NGS order also frequently arrives as a reflex from an upstream screen — a screening genotype or hotspot result that triggers confirmatory sequencing — in which case the molecular reflex testing rule generates the sequencing order automatically and carries the original specimen forward.
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 uses reusable instrument definitions and field mapping for instrument integrations, with Illumina among the documented molecular connections. The exact sequencer model, software version, transport, file format, and mapped fields are confirmed and validated for each interface. The configured connection can cover two directions:
- Outbound: download an instrument worklist from the operational plate so the integration can carry configured sample, well, index, and run fields without rekeying the plate assignment.
- Inbound: upload a supported result file and map configured results, QC flags, and comments back to the corresponding records. The fields returned depend on the instrument and the validated interface scope.
Mapped run and QC data stay linked to the plate or batch record, giving reviewers one traceable connection between instrument output and the specimens processed in that run.
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 API-triggered pipeline integration and structured genomic data management. The project-specific handoff can work in both directions:
- The LIS sends the identifiers and configured sample or panel context required by the validated pipeline trigger.
- When analysis completes, the agreed structured outputs can return to the LIS and remain linked to the originating accession, run, and preparation records.
That linkage keeps supported pipeline outputs connected to the laboratory record used for review and reporting.
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 supports configurable clinical reports with variant details and interpretive content, plus ACMG-guideline-based classification tools. The exact panel layout, included QC context, review fields, and approval steps are configured and validated against the lab’s reporting procedure.
QC review can be included in the configured approval workflow. Levey-Jennings charts and Westgard rule detection give the lab a structured way to review control performance and investigate shifts or trends under its validated QC procedure.
Stage 7: Turnaround Time and Operational Visibility
Across all of the above, the LIS also supports turnaround-time review. When the lab configures and records its stage transitions — received, extracted, library built, sequenced, analyzed, reviewed, signed — those timestamps can feed TAT dashboards and help teams identify where batches are waiting.
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 and NGS LIS configuration in LIMS IQ, 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 to review which panels, instruments, pipeline handoffs, and report formats can be configured or interfaced for your scope.