Laboratory information management system
A Laboratory Information Management System (LIMS), sometimes referred to as a Laboratory Information System (LIS) or Laboratory Management System (LMS), is a software-based laboratory and information management system that offers a set of key features that support a modern laboratory's operations. Those key features include — but are not limited to — workflow and data tracking support, flexible architecture, and smart data exchange interfaces, which fully "support its use in regulated environments." The features and uses of a LIMS have evolved over the years from simple sample tracking to an enterprise resource planning tool that manages multiple aspects of laboratory informatics.
The definition of a LIMS is somewhat controversial: LIMSs are dynamic because the modern laboratory's requirements are rapidly evolving and needs often vary significantly from lab to lab. Therefore, a working definition of a LIMS ultimately depends on the interpretation by the individuals or groups involved. Dr. Alan McLelland of the Institute of Biochemistry, Royal Infirmary, Glasgow highlighted this problem in the late 1990s by explaining how a LIMS is perceived by an analyst, a laboratory manager, an information systems manager, and an accountant, "all of them correct, but each of them limited by the users' own perceptions."
Historically the LIMS, LIS, and Process Development Execution System (PDES) have all performed similar functions. Historically the term "LIMS" has tended to be used to reference informatics systems targeted for environmental, research, or commercial analysis such as pharmaceutical or petrochemical work. "LIS" has tended to be used to reference laboratory informatics systems in the forensics and clinical markets, which often required special case management tools. The term "PDES" has generally applied to a wider scope, including, for example, virtual manufacturing techniques, while not necessarily integrating with laboratory equipment.
In recent times LIMS functionality has spread even farther beyond its original purpose of sample management. Assay data management, data mining, data analysis, and electronic laboratory notebook (ELN) integration are all features that have been added to many LIMS, enabling the realization of translational medicine completely within a single software solution. Additionally, the distinction between a LIMS and a LIS has blurred, as many LIMS now also fully support comprehensive case-centric clinical data.
- 1 History
- 2 Technology
- 3 Distinction between a LIMS and a LIS
- 4 Standards
- 5 See also
- 6 Further reading
- 7 References
Up until the late 1970s, the management of laboratory samples and the associated analysis and reporting were time-consuming manual processes often riddled with transcription errors. This gave some organizations impetus to streamline the collection of data and how it was reported. Custom in-house solutions were developed by a few individual laboratories, while some enterprising entities at the same time sought to develop a more commercial reporting solution in the form of special instrument-based systems.
In 1982 the first generation of LIMS was introduced in the form of a single centralized minicomputer, which offered laboratories the first opportunity to utilize automated reporting tools. As the interest in these early LIMS grew, industry leaders like Gerst Gibbon of the Federal Energy Technology Centre in Pittsburgh began planting the seeds through LIMS-related conferences. By 1988 the second-generation commercial offerings were tapping into relational databases to expand LIMS into more application-specific territory, and International LIMS Conferences were in full swing. As personal computers became more powerful and prominent, a third generation of LIMS emerged in the early 1990s. These new LIMS took advantage of the developing client/server architecture, allowing laboratories to implement better data processing and exchanges.
By 1995 the client/server tools had developed to the point of allowing processing of data anywhere on the network. Web-enabled LIMS were introduced the following year, enabling researchers to extend operations outside the confines of the laboratory. From 1996 to 2002 additional functionality was included in LIMS, from wireless networking capabilities and georeferencing of samples, to the adoption of XML standards and the development of Internet purchasing.
As of 2012, some LIMS have added additional characteristics that continue to shape how a LIMS is defined. Examples include the addition of clinical functionality, electronic laboratory notebook (ELN) functionality, as well a rise in the software as a service (SaaS) distribution model.
The LIMS is an evolving concept, with new features and functionality being added often. As laboratory demands change and technological progress continues, the functions of a LIMS will likely also change. Despite these changes, a LIMS tends to have a base set of functionality that defines it. That functionality can roughly be divided into five laboratory processing phases, with numerous software functions falling under each:
- the reception and log in of a sample and its associated customer data
- the assignment, scheduling, and tracking of the sample and the associated analytical workload
- the processing and quality control associated with the sample and the utilized equipment and inventory
- the storage of data associated with the sample analysis
- the inspection, approval, and compilation of the sample data for reporting and/or further analysis
There are several pieces of core functionality associated with these laboratory processing phases that tend to appear in most LIMS:
The core function of LIMS has traditionally been the management of samples. This typically is initiated when a sample is received in the laboratory, at which point the sample will be registered in the LIMS. Some LIMS will allow the customer to place an "order" for a sample directly to the LIMS at which point the sample is generated in an "unreceived" state. The processing could then include a step where the sample container is registered and sent to the customer for the sample to be taken and then returned to the lab. The registration process may involve accessioning the sample and producing barcodes to affix to the sample container. Various other parameters such as clinical or phenotypic information corresponding with the sample are also often recorded. The LIMS then tracks chain of custody as well as sample location. Location tracking usually involves assigning the sample to a particular freezer location, often down to the granular level of shelf, rack, box, row, and column. Other event tracking such as freeze and thaw cycles that a sample undergoes in the laboratory may be required.
Modern LIMS have implemented extensive configurability, as each laboratory's needs for tracking additional data points can vary widely. LIMS vendors cannot typically make assumptions about what these data tracking needs are, and therefore vendors must create LIMS that are adaptable to individual environments. LIMS users may also have regulatory concerns to comply with such as CLIA, HIPAA, GLP, and FDA specifications, affecting certain aspects of sample management in a LIMS solution. One key to compliance with many of these standards is audit logging of all changes to LIMS data, and in some cases a full electronic signature system is required for rigorous tracking of field-level changes to LIMS data.
Instrument and application integration
Modern LIMS offer an increasing amount of integration with laboratory instruments and applications. A LIMS may create control files that are "fed" into the instrument and direct its operation on some physical item such as a sample tube or sample plate. The LIMS may then import instrument results files to extract data for quality control assessment of the operation on the sample. Access to the instrument data can sometimes be regulated based on chain of custody assignments or other security features if need be.
Modern LIMS products now also allow for the import and management of raw assay data results. Modern targeted assays such as qPCR and deep sequencing can produce tens of thousands of data points per sample. Furthermore, in the case of drug and diagnostic development as many as 12 or more assays may be run for each sample. In order to track this data, a LIMS solution needs to be adaptable to many different assay formats at both the data layer and import creation layer, while maintaining a high level of overall performance. Some LIMS products address this by simply attaching assay data as BLOBs to samples, but this limits the utility of that data in data mining and downstream analysis.
Electronic data exchange
The exponentially growing volume of data created in laboratories, coupled with increased business demands and focus on profitability, have pushed LIMS vendors to increase attention to how their LIMS handles electronic data exchanges. Attention must be paid to how an instrument's input and output data is managed, how remote sample collection data is imported and exported, and how mobile technology integrates with the LIMS. The successful transfer of data files in spreadsheet and other formats, as well as the import and export of data to MySQL, PostgreSQL, and other databases is a pivotal aspect of the modern LIMS. In fact, the transition "from proprietary databases to standardized database management systems such as MySQL" has arguably had one of the biggest impacts on how data is managed and exchanged in laboratories.
Aside from the key functions of sample management, instrument and application integration, and electronic data exchange, there are numerous additional operations that can be managed in a LIMS. This includes but is not limited to:
- audit management
- fully track and maintain an audit trail
- barcode handling
- assign one or more data points to a barcode format; read and extract information from a barcode
- chain of custody
- assign roles and groups that dictate access to specific data records and who is managing them
- follow regulatory standards that affect the laboratory
- customer relationship management
- handle the demographic information and communications for associated clients
- document management
- process and convert data to certain formats; manage how documents are distributed and accessed
- instrument calibration and maintenance
- schedule important maintenance and calibration of lab instruments and keep detailed records of such activities
- inventory and equipment management
- measure and record inventories of vital supplies and laboratory equipment
- manual and electronic data entry
- provide fast and reliable interfaces for data to be entered by a human or electronic component
- method management
- provide one location for all laboratory process and procedure (P&P) and methodology to be housed and managed as well as connecting each sample handling step with current instructions for performing the operation
- personnel and workload management
- organize work schedules, workload assignments, employee demographic information, training, and financial information
- quality assurance and control
- gauge and control sample quality, data entry standards, and workflow
- create and schedule reports in a specific format; schedule and distribute reports to designated parties
- time tracking
- calculate and maintain processing and handling times on chemical reactions, workflows, and more
- show audit trail and/or chain of custody of a sample
- track a sample, a batch of samples, or a "lot" of batches through its lifecycle
A LIMS has utilized many architectures and distribution models over the years. As technology has changed, how a LIMS is installed, managed, and utilized has also changed with it.
The following represents architectures which have been utilized at one point or another:
A thick-client LIMS is a more traditional client/server architecture, with some of the system residing on the computer or workstation of the user (the client) and the rest on the server. The LIMS software is installed on the client computer, which does all of the data processing. Later it passes information to the server, which has the primary purpose of data storage. Most changes, upgrades, and other modifications will happen on the client side.
This was one of the first architectures implemented into a LIMS, having the advantage of providing higher processing speeds (because processing is done on the client and not the server). Additionally, thick-client systems have also provided more interactivity and customization, though often at a greater learning curve. The disadvantages of client-side LIMS include the need for more robust client computers and more time-consuming upgrades, as well as a lack of base functionality through a web browser. The thick-client LIMS can become web-enabled through an add-on component.
Although there is a claim of improved security through the use of a thick-client LIMS, this is based on the misconception that "only users with the client application installed on their PC can access server side information". This secrecy-of-design reliance is known as security through obscurity and ignores an adversary's ability to mimic client-server interaction through, for example, reverse engineering, network traffic interception, or simply purchasing a thick-client license. Such a view is in contradiction of the "Open Design" principle of the National Institute of Standards and Technology's Guide to General Server Security which states that "system security should not depend on the secrecy of the implementation or its components", which can be considered as a reiteration of Kerckhoffs's principle.
A thin-client LIMS is a more modern architecture which offers full application functionality accessed through a device's web browser. The actual LIMS software resides on a server (host) which feeds and processes information without saving it to the user's hard disk. Any necessary changes, upgrades, and other modifications are handled by the entity hosting the server-side LIMS software, meaning all end-users see all changes made. To this end, a true thin-client LIMS will leave no "footprint" on the client's computer, and only the integrity of the web browser need be maintained by the user. The advantages of this system include significantly lower cost of ownership and fewer network and client-side maintenance expenses. However, this architecture has the disadvantage of requiring real-time server access, a need for increased network throughput, and slightly less functionality. A sort of hybrid architecture that incorporates the features of thin-client browser usage with a thick client installation exists in the form of a web-based LIMS.
Some LIMS vendors are beginning to rent hosted, thin-client solutions as "software as a service" (SaaS). These solutions tend to be less configurable than on premise solutions and are therefore considered for less demanding implementations such as laboratories with few users and limited sample processing volumes.
Another implementation of the thin client architecture is the maintenance, warranty, and support (MSW) agreement. Pricing levels are typically based on a percentage of the license fee, with a standard level of service for 10 concurrent users being approximately 10 hours of support and additional customer service, at a roughly $200 per hour rate. Though some may choose to opt out of an MSW after the first year, it's often more economical to continue the plan in order to receive updates to the LIMS, giving it a longer life span in the laboratory.
A web-enabled LIMS architecture is essentially a thick-client architecture with an added web browser component. In this setup, the client-side software has additional functionality that allows users to interface with the software through their device's browser. This functionality is typically limited only to certain functions of the web client. The primary advantage of a web-enabled LIMS is the end-user can access data both on the client side and the server side of the configuration. As in a thick-client architecture, updates in the software must be propagated to every client machine. However, the added disadvantages of requiring always-on access to the host server and the need for cross-platform functionality mean that additional overhead costs may arise.
A web-based LIMS architecture is a hybrid of the thick- and thin-client architectures. While much of the client-side work is done through a web browser, the LIMS may also require the support of desktop software installed on the client device. The end result is a process that is apparent to the end-user through a web browser, but perhaps not so apparent as it runs thick-client-like processing in the background. In this case, web-based architecture has the advantage of providing more functionality through a more friendly web interface. The disadvantages of this setup are more sunk costs in system administration and reduced functionality on mobile platforms.
LIMS implementations are notorious for often being lengthy and costly. This is due in part to the diversity of requirements within each lab, but also to the inflexible nature of LIMS products for adapting to these widely varying requirements. Newer LIMS solutions are beginning to emerge that take advantage of modern techniques in software design that are inherently more configurable and adaptable — particularly at the data layer — than prior solutions. This means not only that implementations are much faster, but also that the costs are lower and the risk of obsolescence is minimized.
Distinction between a LIMS and a LIS
Up until recently, the LIMS and laboratory information system (LIS) have exhibited a few key differences, making them noticeably separate entities.
- A LIMS traditionally has been designed to process and report data related to batches of samples from biology labs, water treatment facilities, drug trials, and other entities that handle complex batches of data. A LIS has been designed primarily for processing and reporting data related to individual patients in a clinical setting.
- A LIMS may need to satisfy good manufacturing practice (GMP) and meet the reporting and audit needs of the regulatory bodies and research scientists in many different industries. A LIS, however, must satisfy the reporting and auditing needs of health service agencies e.g. the hospital accreditation agency, HIPAA in the US, or other clinical medical practitioners.
- A LIMS is most competitive in group-centric settings (dealing with "batches" and "samples") that often deal with mostly anonymous research-specific laboratory data, whereas a LIS is usually most competitive in patient-centric settings (dealing with "subjects" and "specimens") and clinical labs.
A LIMS covers standards such as:
- 21 CFR Part 11 from the Food and Drug Administration (United States)
- ISO/IEC 17025
- ISO 15189
- Good laboratory practice
- List of LIMS software packages
- Virtual research environment
- Laboratory informatics
- Electronic lab notebook
- 21 CFR 11
- Data management
- Scientific management
- Process Development Execution System
- Gibbon, G.A. (1996). "A brief history of LIMS" (PDF). Laboratory Automation and Information Management 32 (1): 1–5. doi:10.1016/1381-141X(95)00024-K.
- Wood, Simon (September 2007). "Comprehensive Laboratory Informatics: A Multilayer Approach" (PDF). American Laboratory. p. 1.
- Jones, John (2012). "The LIMS Book & Buyer's Guide". Laboratory Informatics Institute,Inc.
- "2011 Laboratory Information Management: So what is a LIMS?". Sapio Sciences. 28 July 2010. Retrieved 7 November 2012.
- Vaughan, Alan (20 August 2006). "LIMS: The Laboratory ERP". LIMSfinder.com. Retrieved 7 November 2012.
- McLelland, Alan (1998). "What is a LIMS - a laboratory toy, or a critical IT component?" (PDF). Royal Society of Chemistry. p. 1. Retrieved 7 November 2012.
- "How Do I Find the Right LIMS — And How Much Will It Cost?" (PDF). Laboratory Informatics Institute, Inc. Retrieved 7 November 2012.
- Gibbon, G.A. (1996). "A brief history of LIMS" (PDF). Laboratory Automation and Information Management 32 (1): 1–5. doi:10.1016/1381-141X(95)00024-K. Retrieved 7 November 2012.
- D. O. Skobelev, T. M. Zaytseva, A. D. Kozlov, V. L. Perepelitsa, and A. S. Makarova (2011). "Laboratory information management systems in the work of the analytic laboratory" (PDF). Measurement Techniques 53 (10): 1182–1189. doi:10.1007/s11018-011-9638-7. Retrieved 7 November 2012.
- Tomiello, Kathryn (21 February 2007). "Regulatory compliance drives LIMS". Design World. Retrieved 7 November 2012.
- Khan, Masood N.; Findlay, John W. (2009). "11.6 Integration: Tying It All Together". Ligand-Binding Assays: Development, Validation, and Implementation in the Drug Development Arena. John Wiley & Sons. p. 324. ISBN 0470041382. Retrieved 7 November 2012.
- Wood, Simon (September 2007). "Comprehensive Laboratory Informatics: A Multilayer Approach" (PDF). American Laboratory. p. 1. Retrieved 7 November 2012.
- "ASTM E1578 - 06 Standard Guide for Laboratory Information Management Systems (LIMS)". ASTM International. Retrieved 7 November 2012.
- O'Leary, Keith M. "Selecting the Right LIMS: Critiquing technological strengths and limitations". Scientific Computing. Retrieved 7 November 2012.
- "Guide to General Server Security" (PDF). National Institute of Standards and Technology. July 2008. Retrieved 2 October 2011.
- Royce, John R. (31 March 2010). "Industry Insights: Examining the Risks, Benefits and Trade-offs of Today’s LIMS". Scientific Computing. Retrieved 7 November 2012.
- Friedman, Bruce (4 November 2008). "LIS vs. LIMS: It's Time to Blend the Two Types of Lab Information Systems". Lab Soft News. Retrieved 7 November 2012.
- "LIMS/LIS Market and POCT Supplement". analytica-world.com. 20 February 2004. Retrieved 7 November 2012.