TL;DR: A general-purpose LIS handles a specimen, a test, and a result. An NGS workflow has a specimen, a library, a plate, a run, a pipeline version, a variant call, an interpretation, and a report that may be reissued years later. CAP sets 18 accreditation requirements across that path. Most of what breaks is record-keeping, not sequencing.

  • One specimen becomes many tracked objects. A generic LIS models one.
  • Variant reporting is structured, versioned, and reissuable. Standard report templates are none of those.
  • CAP requires exception logs, version traceability, and documented data storage. These are LIS obligations, not bioinformatics ones.
  • A second system for molecular creates reconciliation work that scales with volume.
  • The question to answer before you expand the menu: can your current system hold the record, not can it store the file.

Labs rarely discover this during validation. They discover it eighteen months later, when a case needs reanalysis and nobody can establish which pipeline version produced the original call.

What is NGS Data Management?

NGS data management is the tracking and retention of every record a sequencing-based test generates, from specimen accession through final report, in a form that can be audited and reproduced. It is distinct from molecular laboratory testing generally, because the object count is higher and the retention obligations are longer.

What is the Difference Between NGS Analysis Software and an LIS?

Analysis software calls variants. An LIS holds the record of everything around that call: which specimen, which library, which plate well, which run, which pipeline version, who interpreted it, what was reported, and what changed afterward. Labs sometimes buy the first and assume it covers the second. It does not, and the gap only becomes visible under audit.

How Does Next Generation Sequencing Work in a Clinical Lab?

Nucleic acid is extracted, a library is prepared and barcoded, libraries are pooled onto a plate, the pool is sequenced, reads are aligned and variants called by a validated pipeline, and a pathologist or genomic scientist interprets and reports the findings. Each of those steps creates a record that has to survive.

Why Does a Generic LIS Break When You Add NGS?

Because it was designed around a one-to-one relationship between a specimen and a result. NGS is one-to-many at every stage, and the relationships have to stay intact for years.

Why Does Variant Reporting Break Standard Report Templates?

A variant report is structured data with an interpretation attached, not narrative text. It carries gene, transcript, coding change, classification, and evidence, and the classification can change when the literature changes. A template built for a narrative diagnosis stores the words but not the structure, so nothing can be queried, compared, or reissued cleanly later.

Why Does Specimen Tracking Fail at the Batch Level?

Because the tracked object stops being the specimen. Once libraries are pooled, the meaningful unit is a well on a plate in a run. A system that tracks accessions but not plates and runs cannot answer the question that matters after a failed run: which of these forty samples has to be repeated, and from what starting material.

What Does CAP Require That a Generic LIS Does Not Do?

CAP’s molecular pathology checklist carries 18 requirements specific to NGS, and it deliberately separates the wet bench process from the bioinformatics analysis. The items include documentation, validation, quality assurance, confirmatory testing, exception logs, monitoring of upgrades, variant interpretation and reporting, incidental findings, data storage, version traceability, and data transfer confidentiality. Read that list as a systems specification, because most of it is. See the CAP NGS laboratory standards.

Exception logs, upgrade monitoring, and version traceability are the three that generic systems most often cannot produce. They are also the three an inspector will ask for.

Do You Need a Second LIS for Molecular Testing?

It is the common answer and it is usually the wrong one. Running a separate molecular system alongside an anatomic pathology LIS means two accession schemes, two audit trails, and manual reconciliation whenever a case involves both. For a lab where a single case can carry histology and a somatic panel, that reconciliation is permanent work that grows with volume.

It also splits your operational reporting. Turnaround time across a combined case cannot be measured if the two halves live in different systems, which means the metric leadership cares about is the one you cannot produce.

What Should an LIS Handle in an NGS Workflow?

Three things, and none of them are sequencing.

Batch, Plate, and Library-level Tracking

The system should track the library and the plate position as first-class objects linked to the parent specimen, so a failed run resolves to a list of samples and their remaining material rather than a manual reconstruction from instrument logs.

Structured Variant Reporting and Reanalysis

Variants should be stored as structured fields with their classification and evidence, so a reclassification can be found, reviewed, and reissued. A lab that cannot query prior reports by variant cannot act when a classification changes.

Data Retention and Version Traceability

Every result should be traceable to the pipeline version and reference build that produced it, and retention should be documented rather than assumed. The CDC’s NGS quality guidance treats pipeline development and maintenance as part of the quality management system, alongside CLIA compliance. That framing is correct, and it makes version history a record-keeping requirement rather than an engineering detail.

What to Ask Before Adding NGS to Your Current LIS

Four questions, and ask them of the vendor rather than of your own team.

  • Can the system track a library and a plate position as objects linked to the parent specimen?
  • Are variants stored as structured fields, and can prior reports be queried by variant for reanalysis?
  • Can the system produce an exception log and a pipeline version history for an inspector without a database query?
  • If we run anatomic and molecular work on one case, does it stay one case, with one turnaround time?

A vendor who answers the fourth question by describing an integration is telling you it is two systems.

See What an NGS Workflow Looks Like on One Platform

NovoPath has built laboratory information systems for pathology labs since 1993, across anatomic, molecular, and veterinary work. Our molecular pathology LIS handles multi-test workflows including cytogenetics, genomics, and FISH, with batch processing, reflex testing, and structured reporting in the same platform that carries the lab’s anatomic pathology cases. One accession scheme, one audit trail, one turnaround time on a combined case.

Request a demo of NovoPath’s molecular pathology LIS and bring the four questions above.