Laboratory information management systems

Abstract

Many analytical service laboratories are faced not only with increasing sample loads and testing demands, but also with growing record-keeping requirements. Reports to customers, legal archives, quality assurance records, good laboratory practice standards, regulatory oversight, workload justifications to management, and a host of other demands contribute to the paperwork explosion. When this paperwork is coupled with the logistical problems inherent in running a laboratory that must process thousands of samples, the stage is set for the acquisition of a laboratory information management system (LIMS).A LIMS is intended to help manage the daily workflow of the laboratory and act as a paperwork processor. Since 1983, when the functions and configuration of a typical LIMS were described by Dessy (1, 2), a number of

Architecture for a comprehensive laboratory information management system

“…Designed to meet the strategic requirements of managing and integrating both the data and information domains, the model provides a clear scope and functional definition of a LIMS and, we believe, compensates for the shortcomings of the literature definitions (1)(2)(3)(4). Furthermore, the model provides the flexibility and cohesive framework for any LIMS implementation.…”

Architecture for a Comprehensive Laboratory Information Management System

“…The current misconceptions regarding LIMS cannot be resolved by existing literature definitions (1)(2)(3)(4). Although these definitions are useful, a major weakness is their focus on the end results of a LIMS rather than consideration of the required functions and structure.…”