The boundary between an electronic laboratory notebook (ELN), a laboratory execution system (LES), and a laboratory information management system (LIMS) is not a fixed product category line. ASTM E1578 explicitly declines to define those boundaries because they continue to evolve and blur between tool types [1]. The practical distinction instead comes from what each system owns as its primary record, what it enforces during work, and what it reports after work. An ELN typically owns unstructured experimental narrative and flexible page content. An LES owns step-by-step procedural execution for repeated methods. A LIMS owns sample-centric lifecycle data and final result reporting. Vendor documentation shows these functions increasingly packaged together, which makes workflow boundaries a configuration decision rather than a purchase category decision [3][5][6].
Record Ownership Defines the Core Boundary
Record ownership is the most stable way to separate the three systems. A LIMS is traditionally sample-centric, meaning the information captured and managed is about the sample through its lifecycle [7]. That includes sample accessioning, tracking, inventory, instrument status, and result reporting against stored specifications [3][7]. The LIMS record is therefore the sample and its associated test results, not the narrative of how an analyst thought through an experiment. This ownership distinction matters when deciding which system should be the system of record for a given data element.
An ELN, by contrast, owns the scientist's experimental record. It supports storage and search of unstructured data, rich text, spreadsheet and PDF pages, and page links to samples, tests, or instruments [3]. The ELN can standardize workflow somewhat through templates so that the same sections and metadata are filled out for every experiment, but the primary record remains the notebook entry [7]. A LES owns procedural execution records for repeated manufacturing or quality control tests. It encapsulates standard operating procedures or work instructions so that each step is recorded and the analyst cannot move to the next step until the current step is completed [7].
Execution Enforcement Separates LES from ELN
The clearest functional boundary between an ELN and a LES is enforcement. An ELN provides structure and searchability, but it does not inherently prevent an analyst from skipping a step or recording an out-of-specification observation in free text. A LES enforces procedural execution during the testing process [7]. The software records each step and prevents progression until the current step is completed. Real-time checks on standards, reagents, or solutions can identify deviations such as a potentially expired reagent at the time of use and prevent the analyst from proceeding [7].
This enforcement boundary has a direct consequence for workflow design. If a laboratory needs to demonstrate that every analyst performed a repeated test identically, the procedural steps belong in a LES. If the laboratory needs to capture exploratory observations, hypotheses, or unstructured notes that do not map to a fixed sequence, those belong in an ELN. Agilent describes OpenLab Sync as combining LIMS, ELN, and LES capabilities in a single system, with guided workflow execution that captures how work is performed [5]. That packaging does not remove the boundary; it moves the boundary into configuration choices about which record type a given workflow step should create.
A Suggested Validation Scenario for Testing Boundaries
A laboratory could test its ELN, LES, and LIMS boundaries with a single buffer preparation and sample test scenario. The suggested scenario would begin with an analyst creating an unstructured ELN entry describing the experimental intent and linking it to the sample record. The analyst would then execute the buffer preparation in the LES, where the system states the required compounds and captures each weight electronically [6]. The LES would enforce step completion and check reagent status before allowing progression [7]. Finally, the LIMS would receive the sample result and check it against stored specifications before review, approval, and reporting [7].
The validation question is not whether each system can perform its assigned step, but whether the handoffs preserve ownership. The ELN should retain the narrative intent, the LES should retain the procedural execution record, and the LIMS should retain the authoritative sample result. If any system overwrites another system's record or if the same value is manually re-entered across systems, the boundary has failed. This scenario is a suggestion for evaluation, not a documented test result from any vendor.
Sample-Centric Reporting and Integration Boundaries
A LIMS boundary is most visible at the reporting and integration layer. The LIMS manages and tracks analysis requests, associated samples, test results, and other information required to issue the final certificate of analysis [6]. It can interface with standard lab instruments and integrate with systems such as an ERP, removing manual transcription and reducing human error [7]. Thermo Fisher's SampleManager documentation describes LIMS functionality for sample management, inventory, instrument management, resource management, analytical quality control, and reporting, alongside clinical data compatibility for receiving test requests and sending results in HL7 format [3].
The CDC job aid frames the LIMS as a system of systems, with device and software integration that can be unidirectional or bidirectional [4]. In that framing, an ELN is an alternative to paper notebooks, mobile applications allow offsite access, and a scientific data management system is a data warehouse for document management [4]. The integration boundary is therefore not about which system can store a value, but about which system owns the authoritative sample and result record that other systems reference. A LIMS can receive data from an ELN or LES, but the final reported result against a specification typically remains a LIMS function [7].
Deployment and Version Boundaries Remain Product-Specific
Deployment boundaries are documented differently across vendors and should not be generalized. Agilent states that OpenLab Sync offers flexible deployment options, running in the customer's own environment or in the cloud, with access through a web browser [5]. Agilent SLIMS is web-based, with no cost for client maintenance, and can be used with just a web browser from a client computer or on a tablet [6]. Thermo Fisher describes a native mobile app for SampleManager that allows users to access LIMS and LES features on a tablet regardless of network connectivity, with offline capabilities [3].
These deployment statements are vendor-specific claims about their own products. They do not establish a universal boundary between ELN, LES, and LIMS deployment models. A laboratory evaluating workflow boundaries should treat deployment as a separate decision axis from record ownership and execution enforcement. The same is true for version boundaries. Agilent lists OpenLab Sync current software version as v7.2 [5]. No comparable version information is supplied for the other products in the public documentation, so no cross-product version comparison can be made.
Unresolved Questions and Category Convergence
The source documentation leaves several boundary questions unresolved. ASTM E1578 states that the guide does not attempt to define the boundaries of laboratory informatics because they continue to evolve and blur between the different types of tools [1][2]. Agilent notes that the market has seen LIMS vendors adding ELNs to their portfolio and ELN vendors adding sample tracking and management capabilities to their products [6]. That convergence means a laboratory cannot assume that a product labeled LIMS lacks notebook functionality or that a product labeled ELN lacks sample tracking.
What remains unknown from the public documents is how specific implementations resolve conflicts when the same data element could be owned by two systems. For example, a buffer preparation weight captured in a LES may also need to appear in a LIMS sample record. The sources describe the capability to capture such data electronically and print labels [6], but they do not document a universal rule for which system remains authoritative when the LES and LIMS disagree. That resolution is a configuration and governance decision that must be made during implementation, not inferred from product category labels.
Sources & references
- E1578 Standard Guide for Laboratory Informatics - ASTM · store.astm.org
- E1578 Standard Guide for Laboratory Informatics - ASTM · www.astm.org
- SampleManager LIMS, SDMS, LES and ELN software · documents.thermofisher.com
- Laboratory Information Management System (LIMS) 'System of Systems' Job Aid — CDC · reach.cdc.gov
- Lab Execution System (LES), LIMS & ELN Software, OpenLab Sync | Agilent · www.agilent.com
- The best of LIMS & ELN in one software | Agilent SLIMS · explore.agilent.com
- Lab Systems Guide: ELN, LIMS, CDS, and LES | Technology Networks · www.technologynetworks.com
- LIS Integration Guide · aphl.org