Laboratory testing software is a collection of informatics tools used to collect, store, process, analyze, report and archive data from laboratory operations and supporting processes [1]. The term does not identify a single application. ASTM E1578 describes 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) as distinct categories with overlapping but not identical functions [1]. A purchasing team that treats these as interchangeable will likely specify the wrong system. The practical question is which category matches the laboratory's workflow, what data must move between systems, and which functional requirements can be verified before purchase. This guide answers that question using primary documentation and a hypothetical evaluation example, while identifying what the sources do not establish.
The category distinction is the first specification decision
ASTM E1578 defines laboratory informatics as the specialized application of information technology aimed at optimizing laboratory operations [1]. The standard lists LIMS, LES, LIS, ELN, SDMS and CDS as tools used in today's laboratories and explains their evolution [1]. The guide is intended to educate new users, establish standard terminology, set minimum requirements for primary functions, and provide a functional requirements checklist that can guide purchase, upgrade or development [1][2]. The checklist is an example, not a certification, and the standard does not rank the categories or assign one category to a specific laboratory type.
The Veterans Affairs Laboratory Planning and Implementation Guide shows a different naming pattern. It describes the Laboratory package as part of the integrated Decentralized Hospital Computer Program Core Package, covering anatomic pathology, blood bank, chemistry, coagulation, hematology, microbiology, phlebotomy, serology, surgical pathology, toxicology, urinalysis, results reporting, test accessioning and ordering, auto instrument, quality control and workload recording [6]. This is a clinically oriented system designed to provide data to health care providers and other health care personnel [6]. The VA document does not use the ASTM category labels for its package, which illustrates that organizational terminology can differ from standards terminology even when the underlying functions overlap.
How orders, instruments and results move between systems
The APHL LIS Integration Guide describes a push and pull model for test orders and results. In one flow, an electronic medical record pushes a test order request to the LIS, the LIS receives the order, the laboratory conducts testing, and the LIS pushes test results back into the EMR [3]. A second flow shows the EMR pulling results from the LIS after a test results request [3]. The guide notes that peer-to-peer models, where one LIS directly contacts another LIS, exist but are less common than models with a central data exchange that forwards data to the correct LIS [3].
Instrument integration is a separate concern. The APHL guide states that instrument integration allows users to upload Excel files with prescribed forms, parse and show data inside them [3]. An instrument integration tool manages analyzers by showing and modifying connectivity to all analyzers [3]. The guide also distinguishes file transfer from APIs: reviewing whether data elements are known or vary, and how frequently the data set needs updating, determines whether to use file transfer, direct database connection or APIs that support transactional updates [3]. Large data sets may need file transfer or direct database connection options [3].
A functional requirements checklist before any demo
ASTM E1578 provides an example of a laboratory informatics functional requirements checklist that can be used to guide the purchase, upgrade or development of a laboratory informatics system [1]. The checklist can be adopted within the laboratory and integrated with existing systems [1]. A practical sequence is to list required functions by category, map each function to a data flow, and then ask vendors to demonstrate only the functions that are missing or uncertain. The APHL guide recommends reviewing data elements to be transferred and assessing whether they will be known or vary, as well as how frequently the data set needs updating [3]. This determines whether file transfer, direct database connection or APIs are appropriate [3].
A hypothetical evaluation workflow for a reference laboratory
Consider a hypothetical independent reference laboratory that receives orders from physician offices without EHR connectivity, runs chemistry and toxicology analyzers, and must return results to ordering providers. The evaluation team could begin with the ASTM E1578 functional requirements checklist to identify required functions rather than starting with vendor demonstrations [1]. The checklist is intended to guide specification, evaluation, cost justification, implementation, project management, training and documentation [1]. This hypothetical use is a suggestion for how to apply the standard; it does not describe an actual procurement.
The team would then map data flows. Orders from providers without EHR connectivity require a web portal or similar reception mechanism. The APHL guide describes a reception online platform where doctor or clinic staff collect samples, staff verify incoming specimens and match them with remotely logged testing requests, and the platform updates with LIS data in real time [3]. Testing instruments interface directly with the LIS database, automatically logging test results [3]. The team should also decide which coding standards each external system uses, because laboratories may need more than one set of standards depending on who they are communicating with [3].
Vendor claims require attribution and verification
CGM describes CGM LABDAQ as laboratory management software installed in physician offices, clinics, independent labs and hospitals [4]. The vendor states the system is designed to maximize reimbursements, support total connectivity, improve workflow and efficiency, and assist with HIPAA and CLIA compliance [4]. CGM also claims the software automates pre-analytic, analytic and post-analytic activities and that new AI summaries simplify custom rules and functions [4]. These are vendor claims, not independently verified outcomes. The source does not provide evidence that the software improves reimbursement or reduces errors in any specific laboratory.
CGM lists options including inventory management, workflow management, Lab IQ dashboards and CGM LABSIGN for electronic document approvals [4]. The vendor states CGM LABDAQ is built on an open-source, object-relational database and can be hosted onsite or in the cloud by CompuGroup Medical [4]. The source reports 4,000 labs served, 67 analyzer companies interfaced and 30 years of LIS experience [4]. These figures are vendor-reported and the source does not define the counting period or inclusion rules. A buyer cannot use them to predict performance in a specific laboratory.
Validation and retirement are part of the life cycle
ASTM E1578 states that the guide is intended to be used throughout the laboratory informatics life cycle, including specification, build or configuration, validation, use, upgrades and retirement or decommissioning [1]. The standard's audience includes end users, implementers, quality personnel, IT personnel, vendors, instrument vendors, funding approvers, applications support specialists and software test or validation specialists [1]. This breadth means a purchase decision should involve more than the laboratory manager and a vendor sales representative.
The VA guide adds a regulatory constraint. It states that prior to release of software, validation testing must be performed in accordance with the current requirements of the various accrediting and regulatory agencies [5]. The document does not specify which agencies apply to a given non-VA laboratory, and it does not provide a validation checklist that transfers to commercial settings. The ASTM guide provides guidance for validation and documentation but does not itself certify compliance [1]. Teams should treat validation requirements as organization-specific and confirm them with their own quality and regulatory personnel.
Sources & references
- E1578 Standard Guide for Laboratory Informatics - ASTM · store.astm.org
- E1578 Standard Guide for Laboratory Informatics - ASTM · www.astm.org
- LIS Integration Guide · aphl.org
- CGM LABDAQ Laboratory Information System | CGM · www.cgm.com
- Laboratory Planning and Implementation Guide - Veterans Affairs · www.va.gov
- Laboratory Planning and Implementation Guide · www.va.gov