Laboratory information management software is not one product but a family of informatics tools with overlapping functions. ASTM E1578 defines laboratory informatics as the specialized application of information technology aimed at optimizing laboratory operations, covering collection, storage, processing, analysis, reporting, and archiving of data [1]. The standard names six primary 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]. Selection requires a detailed analysis of a laboratory's requirements and should not be a simple product category decision [3]. This guide explains the documented distinctions, regulatory obligations, and a concrete evaluation approach.

Primary Tool Categories and Their Documented Boundaries

ASTM E1578 lists LIMS, LES, LIS, ELN, SDMS, and CDS as examples of primary laboratory informatics tools [1]. The standard explicitly declines to define the boundaries between these tools, noting that they continue to evolve and blur [1]. This is a meaningful caution for buyers: a vendor may label a product a LIMS while another vendor describes similar functionality as an LIS or LES. The standard focuses on functionality provided by laboratory informatics as a whole rather than enforcing rigid category definitions [1].

The APHL LIS Integration Guide treats LIS as covering both laboratory information system and laboratory information management system [6]. It describes an LIS as having functionality to support all the main functions of a laboratory and as nearly eliminating paper hand-written forms [6]. The guide also distinguishes central laboratory data repositories, which are data warehouses for analytical purposes such as dashboards, reports, CSV or Excel exports, and surveillance reporting, from systems used for communication [6]. A repository may require additional functionality and enhancements to exchange data [6].

Regulatory Requirements for Clinical Laboratory Systems

New York State's Clinical Laboratory Standards of Practice, effective February 12, 2026, require laboratories to have a system that manages information necessary to receive and track specimens and report results [4]. The information must be accurate, complete, and readily accessible, and the system may be manual, electronic, or a combination [4]. The standards require standard operating procedures for LIS that include quality goals, protection of personally identifiable information and protected health information, facility design requirements such as power protection, and written approval of procedures and LIS changes by the laboratory director [4].

The same standards require initial validation of system components and validation for changes, documentation of verification, maintenance requirements, a mechanism to ensure previous data is retrievable when the LIS is upgraded or replaced, tracking and audit trails, and steps to follow if the system is not functioning [4]. They also require a system to ensure that manually transcribed information, including test request information and test results, or electronically interfaced request information and results, are accurately transcribed [4]. Autoverification should include an acceptable range of outcomes [4].

A Hypothetical Evaluation Exercise for a Clinical Laboratory

Consider a clinical laboratory evaluating a replacement LIS. Using ASTM E1578's functional requirements checklist as a starting point, the evaluation team could map each requirement to the New York State standards: specimen receipt and tracking, result reporting, transcription accuracy, audit trails, data retrievability after upgrade, and downtime procedures [1][4]. The team would then ask each vendor to demonstrate, in a test environment, how the system handles a manually transcribed result that falls outside an acceptable autoverification range and how the audit trail records the correction [4]. This exercise is a suggestion, not a validated testing protocol.

The same team could separately evaluate whether a central laboratory data repository is needed for dashboards and surveillance reporting, recognizing that a repository may require additional functionality to exchange data [6]. The evaluation should document what remains unknown, such as how a vendor's system behaves under the laboratory's specific instrument mix or how previous data is retrievable after an upgrade, until those behaviors are demonstrated in the laboratory's own environment [4].

Forensic LIMS Functional Requirements

A National Institute of Justice guidance document describes functional requirements for a forensic LIMS that meets a modern forensic science service provider's needs and complies with accreditation standards for maintaining a chain of custody record and implementing security measures [8]. System administration requirements include user management with the ability to create, disable, and set permissions for each active user individually or as part of a defined user group [8]. Evidence submission functionality covers accepting or rejecting evidence submissions based on the laboratory's evidence submission guidelines [8].

The forensic guidance specifies data entry support for unique custom data fields that the laboratory specifies for its agency's customers, including voucher, date prepared, invoicing or assigned officer, department or command, charge, lab unit, evidence source, receiving location, receiving date, submitting agency case number, submitted by, number of packages, package description, notes, evidence item information, items, quantity, description, external package label, and currency or denomination [8]. Analytical report development must capture, process, and store detailed information from analytical procedures and modules, and reports should allow sufficient capture of data to support local, state, or federal reporting requirements [8].

Research LIMS Architecture and Infrastructure

NIST Technical Note 2216 describes a roadmap for LIMS at the NIST Material Measurement Laboratory. It states that effective introduction of LIMS early in the research life cycle provides direct support for planning and execution of experiments and accelerating research productivity [7]. The roadmap defines a set of research-oriented LIMS capabilities to guide implementation along with components to deliver those capabilities [7]. It anticipates that LIMS implementation will contribute to program areas such as artificial intelligence, biosystems, chemical informatics, additive manufacturing, and materials science [7].

The NIST roadmap identifies infrastructure resources including data transfer services for manual, automation, and tools for file movement between storage locations; a handle service that generates and resolves a standard persistent identifier; repository systems such as off-the-shelf solutions or established repository platforms; containerized deployments using Docker, Kubernetes, or virtual machine and cloud services; and solutions brokering through documentation and instructional guides [7]. It also notes that sub-LIMS, such as freezer systems and inventory and tracking systems, need to be accounted for, particularly those that will continue to involve manual inputs and operations [7].

Integration Patterns and Data Exchange

The APHL guide describes integration software, commonly called an integration server or integration engine, that listens for requests from external systems and can interact with its own internal software to store incoming data or retrieve information to send back to the requesting system [6]. It describes instrument integration in which data capture software retrieves data from an instrument and sends it directly to a central data exchange system or central laboratory data repository using cellular technology [6]. Results can then be accessed remotely by applications using standardized electronic interfaces, including laptops or handheld devices used by clinicians or remote laboratory staff [6].

The guide also describes LIS-to-LIS integration and notes that LIS are in an ideal position to provide timely information to case tracking systems, supporting the collection of critical data for epidemiological systems even though laboratories are not surveillance systems [6]. ASTM E1578 similarly covers the relationship and interactions between laboratory informatics tools and external systems in a given organization [3]. The standard provides high-level guidance for the integration of laboratory informatics and other software tools [1].