Laboratory management software is not a single product category. The ASTM E1578 standard guide describes a set of related tools: laboratory information management systems (LIMS), laboratory execution systems (LES), laboratory information systems (LIS), electronic laboratory notebooks (ELN), scientific data management systems (SDMS), and chromatography data systems (CDS) [1]. Each tool addresses a different part of laboratory operations, from sample accessioning and instrument data capture to unstructured notes and raw file preservation. A laboratory may need several of these systems working together rather than one replacement for all of them [1]. The practical question for a healthcare technology buyer is which combination of functions matches the laboratory's testing workflows, regulatory record-keeping duties, and existing enterprise systems.

The Core Distinction: LIMS, LIS and the Broader Informatics Set

ASTM E1578 identifies LIMS, LES, LIS, ELN, SDMS and CDS as examples of primary laboratory informatics tools [1]. The standard does not define rigid boundaries between them. It states that the boundaries continue to evolve and blur, and it focuses on the functionality provided by laboratory informatics as a whole [1]. This matters for evaluation because a vendor may describe one product as combining capabilities that another vendor treats as separate modules.

A clinical setting illustrates the LIS distinction. The Veterans Affairs Laboratory V. 5.2 package is described as a clinically oriented application covering functional areas such as anatomic pathology, blood bank, chemistry, coagulation, hematology, microbiology, phlebotomy, serology, surgical pathology, toxicology, urinalysis, test accessioning and results reporting [3]. This package is part of an integrated hospital computer program and is designed to provide data to health care providers and other health care personnel [4]. The documentation does not present it as a general-purpose LIMS for research or manufacturing, but as a clinical laboratory package tied to a specific hospital computing environment.

Workflow Roles: Sample Management, Execution and Raw Data

A LIMS commonly handles sample management, accessioning and tracking, inventory management, instrument management, resource management, analytical quality control, statistical quality control, and reporting and data analytics [7]. Thermo Fisher Scientific describes its SampleManager software as comprising LIMS, SDMS, LES and ELN capabilities, with the SDMS portion focused on secure, long-term preservation and retrieval of raw instrument data and associated metadata [7]. The company states that SampleManager can connect with enterprise systems including ERP and MES [7].

The LES and ELN functions address different workflow moments. SampleManager's ELN supports storage and search of unstructured data and molecular structures, with page types including rich text, spreadsheet and PDF, full text search, templates, page links to samples or instruments, and the ability to pull values from instrument files into spreadsheet cells [7]. The same documentation describes barcode scanning and voice commands for stepping through methods such as sample tracking, inventory management and data recording [7]. These are vendor-described capabilities, not independently verified performance claims.

A Hypothetical Evaluation for a Hospital Reference Laboratory

Suppose a hospital reference laboratory receives orders from an EHR, runs chemistry and hematology tests, and must retain LIS records for two years. The evaluation team could first map the required functions using an ASTM-style checklist: order receipt, accessioning, instrument result capture, autoverification rules, result release, and record retention [1][5]. The team would then ask whether a clinical LIS package covers those functions or whether a LIMS with HL7 result messaging is needed. SampleManager documentation states that it can receive test requests and send results in HL7 format [7], but the team would need to verify the exact message types and interface configuration for its EHR.

The team should also separate raw instrument data from structured results. If the laboratory must preserve raw instrument files for the data lifecycle, an SDMS function may be required in addition to the LIS or LIMS [7]. The evaluation should document what the vendor provides for validation of system changes, because New York State standards require retaining validation records for new or revised software and hardware prior to use for specimen testing, reporting and record keeping [5]. This hypothetical is a suggested evaluation structure, not a tested implementation.

A Clinical LIS Example: Configuration and Record-Keeping

The VA Laboratory Planning and Implementation Guide shows how a clinical LIS is configured around specific files and fields. The July 2024 revision added block ordering to the accession area and File #60, the laboratory test file, and added a peripheral smear by pathologist scenario to that file [3]. The guide also describes an institution extra labels field and a number of labels subfield that can be configured for a specific lab test at a specific facility [3]. These details indicate that clinical LIS setup involves facility-specific test configuration rather than only generic software installation.

Regulatory record retention adds another layer. New York State Department of Health General Systems Standards, effective February 2026, require laboratories to retain LIS records for two years, including records related to validation of system changes and system maintenance required by the LIS manufacturer or established and validated by the laboratory [5]. The same standards define autoverification as software-based rules to verify test results prior to release and autorelease as an electronic system to release test results without intervention by laboratory staff [5]. These definitions matter when evaluating whether a system's result-release behavior fits the laboratory's quality management system.

Vendor Product Families and the Limits of Comparison

Thermo Fisher Scientific presents three LIMS products aimed at different settings. SampleManager is described as built for process development and manufacturing QA/QC, Watson LIMS for bioanalysis, and Core LIMS for R&D workflows [6]. Watson LIMS is described as helping manage bioanalytical studies from initiation through archival, with workflow steps for nonclinical and clinical bioanalytical studies, harmonization of laboratory processes across sites, and information exchange between sponsors and contract labs [6]. Core LIMS is described as a web- and cloud-based AWS environment with pre-built workflows, configurable data types and relationships, and a standards-based OData API [6].

These descriptions are vendor claims about intended use, not independent assessments of performance or compliance. The documentation does not provide comparative pricing or validated outcome data. It does state that Watson LIMS is used by 16 of the top 20 global pharma companies [6], but that adoption figure is a vendor claim and does not establish performance or compliance. A laboratory evaluating these products would need to confirm which functions are included in a specific edition, what validation evidence the vendor supplies, and how the product handles the laboratory's own instrument and enterprise system interfaces. The ASTM guide recommends using a functional requirements checklist to guide purchase, upgrade or development of a laboratory informatics system [1].