|You can find a listing of all LIS vendors — and by extension, the features their products offer — on the LIS vendor page.|
The LIS has traditionally been utilized in clinical, pathology, and medical research laboratories as well as numerous public health institutions. Yet as laboratory demands have changed and technological progress has continued, the functions of a LIS have also changed, with the distinction between a LIS and a laboratory information management system (LIMS) fading as some LIMS vendors have adopted the case-centric information management normally reserved for a LIS..
Despite the blurring of distinction between a LIS and a LIMS, the LIS generally continues to feature the following:
- patient management, including admission date, admitting physician, ordering department, specimen type, etc.
- patient data tracking
- decision support, including comparisons of lab orders with their respective ICD codes
- quality assurance of ordered tests
- workload and management reporting
Of course, there are LIS features that are difficult to categorize or simply contribute to the whole of the LIS rather than add a function. For example, multilingual support allows users to interact with the LIS in more than one language. Some functionality may also overlap several research phases, making it difficult to firmly classify.
The features described below come from an analysis of freely available LIS product information on vendor websites. An attempt was made to discover the features most utilized in vendors' LIS products and collect information on those features for each LIS. Not every possible feature is referenced here; some LIS products fill specific niches, utilizing unique functionality to solve a specific problem.
That said, keep in mind the categorization of features below is very loose. It may be viable to argue a feature belongs under a different section or multiple sections. For the purposes of organizing this information in an uncomplicated manner, however, some liberty has been taken in the categorizing of features.
- 1 Experiment, patient, and data management
- 1.1 Sample login and management
- 1.2 Sample tracking
- 1.3 Sample and result batching
- 1.4 Task and event scheduling
- 1.5 Option for manual result entry
- 1.6 Multiple data viewing methods
- 1.7 Configurable templates and forms
- 1.8 Data and trend analysis
- 1.9 Data and equipment sharing
- 1.10 Data mining
- 1.11 Customizable fields and/or interface
- 1.12 Query capability
- 1.13 Import data
- 1.14 Internal file or data linking
- 1.15 External file or data linking
- 1.16 ELN support or integration
- 1.17 Export to MS Excel
- 1.18 Raw data management
- 1.19 Data warehouse
- 1.20 Project and/or task management
- 1.21 Test, experiment, and/or trial management
- 1.22 Inventory management
- 1.23 Document and/or image management
- 1.24 Patient and case management
- 1.25 Workflow management
- 1.26 Specification management
- 1.27 Customer, supplier, and physician management
- 1.28 Billing and revenue management
- 2 Quality, security, and compliance
- 3 Reporting, barcoding, and printing
- 4 Base functionality
- 4.1 Administrator management
- 4.2 Modular
- 4.3 Instrument interfacing and management
- 4.4 Mobile device integration
- 4.5 Third-party software integration
- 4.6 Alarms and/or alerts
- 4.7 Work-related time tracking
- 4.8 Voice recognition system
- 4.9 External monitoring
- 4.10 Messaging
- 4.11 Commenting
- 4.12 Multilingual
- 4.13 Network-capable
- 4.14 Web client or portal
- 4.15 Online or integrated help
- 4.16 Software as a service delivery model
- 4.17 Usage-based cost
- 5 References
Experiment, patient, and data management
To hide the contents of this section for easier reading of other sections, click the "Collapse" link to the right.
Sample login and management
Sample login and management — often referred to as accessioning or specimen management — is an important component of the clinical laboratory, whether it's a molecular pathology lab testing samples for disease indicators or a contract lab running pharmacokinetic and biomarker analysis on samples from a clinical trial. As such, researchers and technicians who work in these types of labs are unable to complete their tasks without an effective method of managing samples. The process of sample management and accessioning includes, but is not limited to:
- storing related sample information, including demographics, dates, and external links
- creating and documenting viewable sample container schemas with name and status
- assigning sample access rights
- assigning custom sample ID or accessioning numbers based on a specification
- applying additional processing to the sample before storage and/or analysis
Additional functionality that could potentially fall under this feature:
- barcoding or RFID tagging of samples
- defining sample points and series
- creating data associations for samples - such as pedigree for sample/aliquot relationships or relationships based on experiment, etc.
- issuing sample receipts
After sample reception and its initial handling procedures, many LIS can then track sample location as well as chain of custody. Location tracking usually involves assigning the sample to a particular freezer, oven, or other location, often down to the granular level of shelf, rack, box, row, and column. The process of tracking a sample has become more streamlined with increasing support of 2-D barcode or radio-frequency identification (RFID) technology. While handwritten labels were the norm, now barcode and RDIF support in a LIS can "tie together a vast amount of information, clearly relating each sample to a specific case." Other event tracking such as freeze and thaw cycles that a sample undergoes in the laboratory may also be required. As each laboratory's needs for tracking additional data points can vary widely, many modern LIMS and LIS have implemented extensive configurability to compensate for varying environments.
The functionality of sample tracking strongly ties into the audit trail and chain of custody features of a LIS.
Sample and result batching
What is batching? The United States Environmental Protection Agency (EPA) defines a batch as "a group of samples which behave similarly with respect to the sampling or testing procedures being employed and which are processed as a unit." This definition can be applied to many laboratories which handle large quantities of samples for some form of analysis or processing. A LIS that has the ability to check in, link, and track groups of samples across one or multiple facilities is valuable to such laboratories. Additionally, batching the analysis results of multiple samples or groups of samples gives laboratories more flexibility with how they manage their data. Batching also offers the benefit of mimicking the production groups of samples while also capturing quality control data for the entire group.
Task and event scheduling
Within the context of a LIS, the ability to schedule a task or event is a natural extension of how work was done in a laboratory before the advent of data management systems. Sample processing, data analysis, equipment maintenance, and case management follow-ups are assigned to technicians and other personnel. Outpatient scheduling is another aspect of some clinical atmospheres, better handled with computerized scheduling functionality. While these tasks have in the past been performed without the LIS, a modern data management system can now optimize those tasks and provide additional scheduling functionality to streamline the operation of a lab. Some LISs like Elekta AB's IntelliLab include a scheduling calendar for recurring test orders, rules-based orders, and pre-defined selection lists. Additional functionality within this feature group includes the ability to configure automated assignments of experiment requests, establish recurring events, and in most cases, create printable reports.
Examples of tasks and events that can feasibly be scheduled in a LIS include:
- production of reports
- creation and sending of e-mails and alerts
- maintenance of equipment
- assignment of accessioning tasks to technicians
- scheduling outpatient visits
Option for manual result entry
While many LIS vendors tout the ability of their product to automate the entry of sample analysis results into LIS' or other databases, the need for manual data entry of analysis results still exists. This feature is important to laboratories obtaining analysis results from multiple sources, including non-digital paper-based results and instruments that can't be connected to the LIS. Additional functionality associated with this feature includes a customizable spell-check dictionary and the ability to add comments, notes, and narratives to many of the data items in the LIS.
Multiple data viewing methods
Hospitals, physicians, and clinical research facilities produce reams of data, and the LIS exists to help organize and distribute that data to the necessary entities. Additionally, even before the existence of the LIS, scientists have had a corresponding need for visually representing that data for clearer analysis and hypothesis creation. Today a LIS can not only collect and analyze data, but it also can represent that data in reports, graphs, gradients, and spreadsheets. Depending on the LIS, more than one way to visually represent the data may exist.
This category ties in with the custom templates and forms functionality apparent in some LIS, providing both custom and standardized ways to present information across a healthcare or medical research enterprise.
Configurable templates and forms
Similar to an electronic laboratory notebook (ELN), a template in a LIS is a functionality item which allows users to increase the productivity and quality of their work by allowing for the creation of a standardized analysis page, patient page, or reporting process across a healthcare or medical research enterprise. These templates allow researchers to maintain more consistent data representation for similar tasks in the LIS and save time by not needing to manually input common data outputs or recreate experiments. Templates and forms typically utilize a wide field library, and the data that is posted to those template fields can also be normalized to a specific standard. Types of templates that may be created include those for renal and blood pressure analysis, patient demographics, test ordering, and department-level reports.
Data and trend analysisdata analysis plays an important role in their operations, helping clinicians and researchers make better sense of their collected data and reach valuable conclusions about them. While this important phase of laboratory work has often been done externally from the LIS, it's now more common to see basic analysis tools being included. Such tools allow raw data to be imported directly to the LIS, which then can store, process, and display it in a shareable form. Vendors may include data analysis functionality by simply including Microsoft Excel compatibility or providing advanced reporting tools, or they may take a more advanced approach by programming and including their own custom data and trend analysis tools in their informatics software. As sample analysis is increasingly an important part of most if not all laboratories, such functionality — which has often come in the form of a separate application or analysis device — will likely continue to merge into software like LIS, LIMS, and other laboratory informatics solutions.
Data and equipment sharing
Aside from data storage and sample registration, a modern LIS's major contribution to the laboratory is aiding in the sharing of test results, reports, and patient data with other entities across the clinical and research enterprise. Rather than pieces of information becoming misplaced or locked away in a physician's office or pathology lab, the LIS makes it easier to test results and increase the efficiency of patient-doctor-lab collaboration in general. Yet data is more than just test results; it also can come in the form of charts, reports, policy and procedure, and other documents. Additionally, the need for controlling who has access to those types of data is also an important consideration. As such, this feature is at least partially tied to other features like document management and configurable security.
Data mining, in the field of computational science, involves "the process of discovering interesting and useful patterns and relationships in large volumes of data" and includes three computational steps: model-learning, model evaluation, and model usage. As informatics software allows both research and clinical laboratories to collect and manage increasing quantities of data, a corresponding demand for tools capable of modeling that data is appearing. For example, public health laboratories may wish to utilize data mining for statistical analysis and surveillance of populations for specific diseases. LIMSs like LabWare LIMS and LISs like Orchard Harvest are examples of laboratory informatics software which incorporate data mining and reporting tools.
Customizable fields and/or interface
As thorough as some user interface (UI) developers may be in adding relevant fields and interface options for end users, there are at times options that are either omitted or unanticipated. This has traditionally required the end user to contact the vendor and ask if the needed option(s) can be added in the next release. However, many modern LIS vendors have responded instead by adding functionality that gives end users and/or LIS administrators more control over the user interface.
Aspects of the LIS's user interface that are often customizable by the end user include:
- report interface and display
- patient profile display
- project and experiment display
Note in many cases an interface may be customized through the use of templates and forms, and as such, this functionality may be closely tied to the configurable templates and forms functionality.
As was the case before the advent of databases and electronic data management solutions, today researchers must search through test results, patient notes, and other types of data to better draw conclusions from experiments, diagnose patient illnesses, and plan pharmaceutical research activities. Whereas this used to mean browsing through laboratory notebooks, Excel spreadsheets, or Access databases, now powerful query tools exists within data management tools like the LIS and ELN. A flexible search algorithm can be implemented to allow users to search a dataset by patient name (full or partial) or by any accessioning number. Or more advanced query tools may be implemented to collate and search across multiple datasets.
Query functionality often includes the ability to:
- search both transactional data and archived data tables
- search multiple databases via an application programming interface (API) or open database connectivity (ODBC) connection
- filter and sort data
- collate queried data for further analysis and visualization
- create ad-hoc queries
Data can originate from numerous places in the laboratory. The ability to import that data into a LIS can be beneficial, especially when an instrument can't be connected or external clients collaborating on a project need to submit relevant data. Of course instrument interfacing allows for even more importation options. Additional data validation procedures may be applied to the imported data to guarantee information homogeneity. For the LIS, one of the common sources of importing data is a separate electronic medical record (EMR) system, for collecting patient data and test orders.
- linking a sample batch to a test or sample preparation methodology
- linking a test process to a particular experiment
- linking a report to a sample batch
- linking a group of experiment results to a raw data file
- linking multiple images to a patient record
- linking all experiment results with the correct reporting test methods
This feature allows research collaborators using a LIS to link together data and files housed in the database with data, files, and customers outside the LIS's domain. Examples include:
- linking to an external practice management or electronic medical record (EMR) system using an an HL7-compliant interface
- linking one public health data source with others to pool demographic and medical information for better disease modeling
- linking to separate clinical trial laboratory data files within a report
ELN support or integration
The functionality of a LIMS and an ELN began to blur in the 2000s, with both types of software incorporating features from the other. It has been more common to see a LIMS take on some sort of ELN support (or vice versa), but less common in the LIS. Though uncommon, some LIS may include some sort of integration or compatibility with an ELN, and thusly this functionality is at least mentioned.
Export to MS Excel
While Microsoft Excel has long been used within the laboratory setting, a slow shift towards relational databases and LIMS occurred in the late 1990s and early 2000s. Additional concerns with the difficulties of Excel's validation and compliance with FDA 21 CFR Part 11 and other regulations have led many labs to turn to data management solutions that are easier to validate. Nevertheless, laboratories continue to use Excel in some fashion, and thus Excel integration or data exportation in Excel format is a real need for LIS customers. LISs with this feature allow raw, processed, or imported data to be exported in the Excel format for further analysis and dissemination elsewhere in the LIS or externally from it.
Raw data management
While not described as a feature on most LIS vendor websites, a few indicate their product is capable of managing (import, export, editing, etc.) data in its raw format for future analysis and dissemination.
An LIS's data warehouse serves the important function of storing, extracting, and managing the data that laboratories, physician offices, and other facilities produce for the purposes of analysis, reporting, and dissemination, typically separate from the primary storage database. Data warehouses also offer the benefit of speeding up queries, making queries and data mining more user-friendly, and smoothing out data gaps.
Project and/or task management
Project and task management within a LIS typically involves the scheduling of tasks to technicians and organizing associated tasks into a more cohesive unit for better tracking and management. While the functionality of task and event scheduling can also be found in project and task management, many LISs include functionality beyond scheduling that warrants the addition of the project and/or task management feature. This functionality includes:
- job allocation and rescheduling
- instrument workload tracking
- pending workload verification
- project- and experiment-based workflow management
- sample, batch, and document linking
- work template sharing
- recurring event management
See also: Patient and case management
Test, experiment, and/or trial management
Specimen or sample test management is a common component of a LIS, while experiment and research trial management functionality is a component of some LISs, often limited to those that are designed to help manage clinical trials. Test, experiment, and trial management can cover a wide variety of tasks, from setting up the design of a clinical trial to specimen task assignments, from ordering tests for patients to planning trial experiments. Note: this may also be referred to as "order management" with some vendors.
It's worth noting this functionality category may seem broad in scope and include other functionality listed on this page, including workflow management and project and task management. Its inclusion when reviewing software functionality is primarily to indicate when a vendor or project team indicates the existence of specific test, experiment, or trial management tools in their software.
Laboratories use a wide array of inventory, from reagents to glassware, from radiopharmaceuticals to laboratory baths. With that comes the need to know how much/many and the frequency of use. For this, some LIS products (especially those for pathology labs) now offer limited or full-featured inventory management functionality, which may include the ability to:
- register the origin and demographics of incoming materials.
- track used and in-use items via barcodes or RFID tags.
- track inventory reduction based on usage and shipping out of the lab.
- create alerts for when items reach a certain stock level.
- calculate inventory cost and fluctuation.
- manage transportation and routing.
- manual incrementing/decrementing of items.
- track location and usage of laboratory equipment.
- track location and usage of reagents.
- assign storage locations.
- track forensic evidence.
It should be noted electronic equipment may also be considered inventory, and thus there is likely some functionality crossover with instrument management features.
Document and/or image management
- upload and index documents.
- add images and photos inline to a patient or case entry.
- enforce version control.
- provide full text searches.
- export to PDF, XML, or other relevant formats.
- add documents as attachments.
Patient and case management
The laboratory information system (LIS) has played an important role in the case management tasks of patient-centric and clinical laboratories. LIS products have included patient or case management tools suitable for the clinical, public health, and veterinary industries, as well as the fields of law enforcement and forensic science. Functionality seen in the patient and case management feature includes:
- case accessioning and assignment
- disease tracking
- trend analysis
- clinical history follow-up
- out-of-range result alerts
- document and result association
- evidence control
- study management
- collating of patient data across multiple spectrum
Workflow managementWorkflow management is common in the laboratory, acting as a graphical representation of planned sequential steps to either automate or clarify a process or experiment within the lab. Separate standards-based workflow management systems (in the form of a software component) have traditionally performed this task. However, in the 2000s vendors began incorporating workflow management functionality into their laboratory informatics software, reducing customization headaches in the process.
Modern commercial and open-source LIS solutions recognize clinical laboratory workflow often has its own share of requirements, requiring specific workflow management functionality, including:
- managing the request cycle within a laboratory
- organizing and executing diagnostic testing
- managing specific chemistry- and biology-related procedures
- defining activity attributes
- managing automation tools to better workflows
- re-route samples based on changes to a process
- dynamically modifying workflow in case of future changes
- receiving notification of changes to the workflow
Specification (spec) management is vital to not only the manufacturing and research industries but also to a host of other laboratories requiring precise measurements and infallible test methods. Just as the ASTM offers standards and specs for laboratory informatics software, so too do users have standards and specs for their laboratory.
Spec management has primarily been seen in a manufacturing execution system (MES) or a LIMS, but occasionally a LIS may appear which includes such functionality. With spec management in place, laboratories can then:
- enforce standard operating procedures and business rules.
- create specs down to a project or sample level.
- validate recipes and procedures.
- accept or reject sample batches.
- document internal and external spec history.
Customer, supplier, and physician management
Unless a laboratory is conducting internalized independent research, in most cases it will do business with external entities such as contract labs, physician offices, equipment providers, and reagent suppliers. In some cases, even internal employees may be considered a customer, necessitating documentation of who is using the system and in what ways. For a veterinary lab, the customer may be the animal and handler. For a forensic lab the customer may be more complex: internal staff, university staff, police departments, and maintainers of nationwide crime databases may all at some point act as customers. In these cases, documenting these various points of contact and linking them to tests, equipment, and patients becomes vital. Managing demographics, complaints, correspondence, and history are all feasible with customer, supplier, and physician management functionality. This process is often made simpler through the use of a more context-neutral entity creation system, which allows for more flexible management of contacts.
This feature may also be referred to as contact management, an address book module, or a customer service module.
Billing and revenue management
While the finances of a laboratory are important, they've typically been handled separately as a business process. However, some LISs include additional functionality to make handling financial transactions and documentation of all sorts possible within the LIS. In theory, such functionality brings the possibility of keeping more of a laboratory's data centrally located and queryable. This feature may include:
- payment processing
- expense reporting
- price quotes
- revenue management
- workload tracking of billable hours
- bill of materials
- sales team and client management
- profitability analysis
- medical necessity checks
Quality, security, and compliance
To hide the contents of this section for easier reading of other sections, click the "Collapse" link to the right.
The topic of whether or not a LIS meets regulatory compliance is often a complex one. While Title 21 CFR Part 11 has arguably had the largest influence on an electronic data management system's compliance, other influential standards have shaped the way laboratory informatics systems handle and store data. Other compliance-based codes, standards, and regulations include:
- Classified data
- Freedom of information legislation (various)
- GALP and GAMP
- Health Level 7
- ISO/IEC 17025
- ISO 9000/9001
- ISO/TS 16949
- TNI and NELAP
- Title 40 CFR Part 3
With so many codes, standards, and regulations, LIS consumers are advised to contact vendors with their user requirements and ask how the vendor's software meets and/or exceeds those requirements.
The quality management functions of a LIS allow users to maintain a level of necessary quality across many of the functions in a laboratory. Some of the activities quality assurance / quality control functionality allows for includes:
- force random review of cases by second pathologist before case verification
- receive and process QC results from laboratory analyzers
- create user rules
- set up custom alerts and flags for out-of-range results
- observe standard deviations in outcome research
- review and sign off on data electronically
- delta checking
As document and file management plays an important role in clinical and research laboratories, it only makes sense to collate and store all the associated data for future reference, including documentation relating to individual training and performance. Changes to laboratory techniques, scientific understanding, and business practices force lab technicians and researchers to learn, reevaluate, and demonstrate competency in order to maintain quality levels in the laboratory. Evaluations can frequently extend beyond staff members, however. Clinics, visit types, vendors, or test species can also be tracked and evaluated based on custom criteria. The performance evaluation functionality of a LIS makes this possible.
That functionality typically includes the ability to maintain training records and history, and also to link that training to a technique or piece of equipment. Afterwards, the staff member, vendor, etc. can be marked as competent or certified in the equipment, knowledge, or process. Periodical assessment of the training and its practical effectiveness can later be performed. Productivity of an entity or process can also be gauged over a certain date range based on tracked time, pre-determined milestones, or some other criteria.
Audit trail21 CFR Part 11 mandate "computer systems (including hardware and software), controls, and attendant documentation" utilize electronic signatures and audit trails, LIS developers must put serious thought into how their software handles audit trail functionality. The audit trail — documentation of the sequence of activities that have affected an action — must be thorough and seamlessly integrated into the software.
Information recorded in the audit trail typically includes:
- operator code
- time stamp
- case number
- accessioning number
- transaction type
- amount and quantity prior to change
- user notes
Chain of custody
The chain of custody (COC) of an item is of varying importance, depending on the type of laboratory. A highly regulated laboratory that works under Code of Federal Regulation or other guidelines makes tracking COC a vital part of its operations. This is especially true in forensic labs, which depend on continuous accountability of their evidence collection, retention, and disposal procedures. As with an audit trail, a laboratory depends on recorded information like user ID, time stamp, and location ID to maintain a robust and accurate COC. Barcodes and RFID tags, inventory management, and configurable security roles all play an important part in maintaining chain of custody.
Configurable roles and security
Many roles exist within the clinical and research setting, each with its own set of responsibilities. And just as the role an individual plays within the laboratory may change, so may the responsibilities associated with each role. This sort of change necessitates a flexible and configurable security system, one that allows for the placement of individual LIS users into standardized security roles which provide role-specific access to certain functionality. Additionally, as responsibilities change within roles, that same flexible configuration is necessary for assigning or restricting access to specific functionality for each existing or newly created role.
Of course, roles aren't always assigned on an individual level. Often large groups of individuals may need to be assigned to roles, necessitating group assignments for security purposes. For example, a group of hospital laboratory trainees may not be given access to the inventory management functionality of the system through a custom "Trainees" group role, while the head of the lab may be given the "Administrator" role, which allows that individual to access a much broader spectrum of the LIS's functionality.
For the purposes of describing LIS functionality, "data normalization" specifically refers to the process of ensuring incoming/imported data into the LIS is standardized to the same format of existing data.
Here's an example to better explain this issue. When a LIS is initially configured, in most if not all cases a clear standard can be set for how logged test results and their associated measurements pre- and post-analysis are recorded in the system. Perhaps all temperatures will be recorded in Celsius to three decimal places. If temperature data imported from a spreadsheet or a lab instrument is not in this format, the LIS can normalize the incoming data to match the standard already set for existing temperature data. This ensures consistency within the database and typically leads to better data validation efforts later on.
Note: Some LIS developers may include data normalization functionality within what they may refer to as data validation functionality. The line between these two may be blurred or not exist at all.
Note: This functionality shouldn't be confused with the process of validating the application itself, which is an entirely different process partially falling under regulatory compliance and involves the process of ensuring "the software is performing in a manner for which it was designed."
The existence of this functionality in a LIS indicates the software has the ability to protect the integrity and authenticity of its housed data through the use of a variety of technologies which makes data unreadable except to those possessing a key/right/etc. to unlock/read the data. This functionality is especially vital to the web-enabled LIS, which transfers information over the Internet in a client-server relationship. As a wide variety of encryption technologies exist, it's generally a good idea to consult with the developers of a LIS to determine the strengths and weaknesses of their employed encryption methods.
Version control is a form of safeguard which helps preserve data integrity and thus ties in with the topic of regulatory compliance. This is typically done by creating a modifiable new version of a piece of information rather than allowing the original to be modified. Such versioning may be applied to a wide variety of digital information housed in the LIS, including templates, training certifications, instrument logs, specifications, and process and procedure (P&P) documentation. Information tracked with such revisions includes attributes like user name, time the edit was made, and what exactly was edited. This also benefits those managing audit trails and chains of custody.
Other LIS vendors may employ a different form of version control called file locking, which simply puts the affected information into a read-only mode for users while someone else is busy editing it. Another popular strategy is to, rather than locking the file, allow multiple people to edit a piece of information, later merging the various edits. Potential LIS buyers may need to inquire with developers to determine what type of versioning scheme is used in the vendor's software.
Automatic data backup
The existence of this piece of functionality in a LIS usually means information contained in one or more associated databases or data warehouses can be automatically preserved in an additional backup file. The save location for that file as well as the scheduled backup time is configurable, typically through the administrative module of the software.
While not common at all, a few LIS may allow users to monitor the environmental conditions of not only sample storage containers but also the entire laboratory itself. Attributes like humidity, air quality, and temperature may be monitored to ensure sample storage units and experiments maintain desired conditions. This monitoring may be done by treating the storage container as a device, which must be interfaced with the LIS. Alarms may be able to be configured to notify staff if a storage container's environmental attributes go beyond a certain threshold.
Reporting, barcoding, and printing
To hide the contents of this section for easier reading of other sections, click the "Collapse" link to the right.
Reporting often provides useful information representation for gaining a clearer picture of collected data and potential trends. At a minimum, a number of pre-configured report templates typically come standard with a LIS. However, other systems are more flexible than others, offering the ability to customize reports in numerous ways. The most popular attributes of custom reporting include custom headers, custom information placement, charts, pivot tables, and multiple output formats.
Note: Some LIS vendors may offer custom reporting as an option as an added cost, depending on the level of customization required.
Synoptic reporting is a specific type of reporting applicable to pathology and other associated laboratories. Synoptic reporting essentially involves a structured, pre-formatted "checklist" of clinically and morphologically relevant data elements (ideally passed to a relational database where they are efficiently organized, searched, and retrieved), with the intent of making reporting more efficient, uniform, and relevant to internal and external researchers. This style of reporting has the advantage of obviating the need for transcription services, reducing specimen turnaround time, and prioritizing the presentation of large amounts of diagnostic information.  Some LISs, especially those oriented towards pathology, may include this specialized functionality. In some cases, a configurable templates or form may be utilized to structure a report in a synoptic format, providing similar functionality to a separate synoptic reporting module.
Today's software almost universally offers the ability to print reports and other materials, so this feature may seem a bit redundant to list. Nonetheless, printer support is a feature worth confirming when considering a piece of laboratory informatics software.
The label — typically affixed to a sample container or piece of equipment — is a vital part of many laboratory operations. Identifying information such as sample number, batch number, and barcodes are printed on such labels to ensure optimize managing the location of items in a lab. As such, numerous LISs allow users to design and print labels directly from the software.
Barcode and/or RFID support
Barcodes offer many advantages to laboratory techs handling samples, including more accurate data input, tighter sample/instrument associations, tighter sample/study associations, and more room for human-readable information on a label. Given such advantages, many laboratory informatics developers have integrated barcode support into their software, including support for symbologies like Code 128, Code 39, and Interleaved 2 of 5. Aside from printing options, a LISmay also offer support for a variety of barcode readers.
Additionally, some LIS include the ability to handle radio-frequency identification (RFID) tags, which have several advantages over a more traditional label-based approach to accessioning.
Barcode support and label support are typically found together in LIS software, but not always, thus their separation into two features.
Export to PDF
A LIS with this feature is able to collect and save information into a Portable Document Format (PDF).
Export to MS Word
A LIS with this feature is able to collect and save information into a Microsoft Office Word format.
Export to HTML or XML
A LIS with this feature is able to collect and save information into a HyperText Markup Language (HTML) and/or Extensible Markup Language (XML) format.
A LIS with this feature is able to connect with a fax machine and send information to it via manual input, automatically, and/or at scheduled intervals.
A LIS with this feature is able to integrate with and use the electronic mail information exchange method to send reports, alerts, and more manually, automatically, and/or at scheduled intervals.
The administrator management tools of a LIS allows researchers to set up the software most optimally for the facility and its projects. Through the administrator management interface, other features may be accessed like setting up user roles and scheduling automatic data backups.
Like report printing, administrator management is nearly ubiquitous in laboratory informatics software, generally considered a mandatory feature. However, for the purposes of being thorough, it's important to point out its existence.
This feature indicates that a LIS has an intentional modular design, which separates some functionality into manageable components of the overall system. Generally speaking, a modular design allows for 1. the structured addition of new functionality to a LIS and 2. the limiting of overall effects on the system design as new functionality is added.
Instrument interfacing and management
In laboratories there are instruments, and with those instruments comes scientific measurements which produce data. It's therefor natural a researcher would want to connect those instruments to a laboratory information system, which is already organizing and storing laboratory data for hospitals and medical research facilities. This sort of interfacing is typically handled with instrument-to-software interfaces, which started out as merely data-transfer mechanisms. Later that interface mechanism became much more robust as a data management tool, though often at great expense with heavy involvement from third parties. Today, "vendors can act as single source providers of the entire instrument interfacing solution,", providing a cheaper and smoother solution to laboratory informatics customers. In the clinical laboratory setting, a LIS vendor may have additional considerations to make, such as Health Level 7 (HL7) triggers, messages, and segments transported across communication interfaces.
Mobile device integration
While not ubiquitous by any means, LIS developers are increasingly including support for mobile devices in their software, usually in the form of a separate mobile version of the software. Research and development labs, for example, potentially can put mobile technology to use in the laboratory as remotely monitoring a lab or using mobile phone microscopy. Those uses aside, the relatively simple action of recording and reviewing laboratory research results while on the move or at a conference gives researchers flexibility, and LIS developers like McKesson are beginning to include that functionality.
Third-party software integration
A few LIS vendors either incorporate third-party software into their product or they provide the means to integrate the LIS with other applications. The most typical integration involves simply communicating with common authoring tools like Microsoft Word, allowing users to work directly from the third-party application and then transferring the information to the LIS.
Alarms and/or alerts
Alarms and alerts in a LIS can be automatic or scheduled, and they can come in the form of an e-mail, a pop-up message, or a mobile text message. For example, when a test result goes out-of-range, an automatic warning message can appear on the screen of the lab analyst responsible for the test. Another example: a scheduled alert can be e-mailed to a lab technician every month indicating a piece of laboratory equipment needs routine maintenance. Both scenarios represent a tiny fraction of the possible implementation of alarms and alerts in a LIS, highlighting how powerful (yet easy to take for granted) this feature is.
This feature specifically refers to a LIS' ability to track the amount of time an employee spends at work in general (for payroll purposes) or on more specific projects and tasks (as part of an employee work evaluation program). May also be referred to as "workload tracking" or "workload tracking."
Voice recognition system
A LIS with this feature allows some functions of the software (for example, accessing test results) to be accessed via voice commands.
This feature allows clients and/or collaborators outside the laboratory to monitor the status of experiments, test results, and more via an online web portal or, less commonly, as activity alerts sent via e-mail or SMS.
The messaging feature of a LIS may refer to one of two (or both) things:
- a built-in instant messaging system that allows users to converse with each other through text messages real-time
- an SMS text messaging integration that allows the users or the LIS itself to send messages or alerts to one or more user's mobile or smart phone
Clinical data collection and research collaboration require data sharing and communication tools to be most effective. One of the collaborative communication features of some LISs is commenting on test results, patient records, or study protocols.
If a LIS is listed as multilingual, its an indication the software interface can be configured to display more than one language depending on the preference a user or administrator chooses. Some LIS interfaces can only be displayed in one of two languages (English or German, for example), while others come configured with support for dozens of languages.
This feature is perhaps archaic and/or obvious, but it is mentioned nonetheless. It's generally applied to a non-web-based LIS installed over a local or wide-area computer network, essentially indicating the LIS is not an isolated application, but rather one that can interface with other instances or other networked instruments.
Web client or portal
A LIS with a web client or portal is either a web-based LIS (one that is not installed on every computer, but rather is hosted on a server and accessed via a web browser) or a non-web-based LIS with an included portal to access it via the Internet.
Online or integrated help
This indicates a LIS has help infrastructure integrated into the software, support documentation via the vendor's website, or both.
Software as a service delivery model
This indicates the software can be licensed and utilized via the software as a service (SaaS) delivery model.
While rare, some software vendors allow potential clients to license and utilize the vendor's software under a usage-based cost model. An example of this model in use is Bytewize AB's O3 LimsXpress, which has a cost directly related to the amount of samples processed each month.
- "Quick Start Guide to Laboratory Information System (LIS) Implementation" (PDF). Association of Public Health Laboratories. http://www.aphl.org/aphlprograms/global/initiatives/Documents/LISQuickStartGuide.pdf. Retrieved 27 April 2013.
- Hice, Randy (01 July 2009). "Swimming in the Clinical Pool: Why LIMS are supplanting old-school clinical LIS applications". STARLIMS' Laboratory Informatics Blog. http://blog.starlims.com/2009/07/01/swimming-in-the-clinical-pool-why-lims-are-supplanting-old-school-clinical-lis-applications/. Retrieved 27 April 2013.
- "How Do I Find the Right LIMS — And How Much Will It Cost?" (PDF). Laboratory Informatics Institute, Inc. http://files.limstitute.com/share/lbgprofiles/findlims.pdf. Retrieved 27 April 2013.
- "Laboratory Information Systems". Biohealthmatics.com. 10 August 2006. http://www.biohealthmatics.com/technologies/his/lis.aspx. Retrieved 27 April 2013.
- Leonard, Debra G. B.; Bagg, Adam, ed. (2007). Molecular Pathology in Clinical Practice (Illustrated ed.). Springer. p. 567. ISBN 0387332278. http://books.google.com/books?id=Z2YNhh51SmQC&pg=PA567. Retrieved 27 April 2013.
- "PPD - Clinical Trial Sample Management". Pharmaceutical Product Development, LLC. http://www.ppdi.com/Services/Laboratories/Central-Labs/Operational-Excellence/Specimen-Management.aspx. Retrieved 27 April 2013.
- Esteridge, Barbara H.; Reynolds, Anna P.; Walters, Norma J. (2000). Basic Medical Laboratory Techniques (4th, revised ed.). Cengage Learning. p. 8. ISBN 0766812065. http://books.google.com/books?id=qMgAbOHSlsMC&pg=PA8&lpg=PA8. Retrieved 27 April 2013.
- Murthy, Tal; Brian Hewson (01 September 2010). "Effective Forensic Sample Tracking and Handling". American Laboratory. http://new.americanlaboratory.com/914-Application-Notes/506-Effective-Forensic-Sample-Tracking-and-Handling/. Retrieved 10 February 2012.
- Muntean, Edwarda; Nicoleta Munteanb; Tania Mihăiescua; Radu Mihăiescuc (2008). "LIMS use in laboratory data management" (PDF). ProEnvironment/Promediu 1 (2): 19–23. http://journals.usamvcluj.ro/index.php/promediu/article/download/2835/2696.
- "Batch Sizes And QC Questions". U.S. EPA. 27 July 2011. http://www.epa.gov/osw/hazard/testmethods/faq/faqs_qc.htm. Retrieved 27 April 2013.
- "Elekta - Laboratory Information System". Elekta AB. http://www.elekta.com/healthcare-professionals/products/elekta-software/clinical-laboratory/laboratory-information-system.html. Retrieved 27 April 2013.
- Park, Seung Lyung; Pantanowitz, Liron; Sharma, Gaurav; Parwani, Anil Vasdev (March 2012). "Anatomic Pathology Laboratory Information Systems: A Review" (PDF). Advances in Anatomic Pathology 19 (2): 81–96. doi:10.1097/PAP.0b013e318248b787. http://bpa-pathology.com/uploads/file/docs/Anatomic%20Pathology%20Laboratory%20Information%20Systems%20-%20A%20Review%20-%20SLPark%20et%20all.%20-%20Adv%20Anat%20Pathol%202012.pdf. Retrieved 27 April 2013.
- Macneil, Rory (2011). "The benefits of integrated systems for managing both samples and experimental data: An opportunity for labs in universities and government research institutions to lead the way". Automated Experimentation 3 (2). doi:10.1186/1759-4499-3-2. http://www.aejournal.net/content/3/1/2.
- "data mining". Encyclopædia Britannica. Encyclopædia Britannica, Inc. http://www.britannica.com/EBchecked/topic/1056150/data-mining. Retrieved 29 April 2013.
- Sepulveda, Jorge L.; Young, Donald S. (05 Decemeber 2012). "The Ideal Laboratory Information System". Archives of Pathology and Laboratory Medicine preprint. PMID 23216205. http://www.ncbi.nlm.nih.gov/pubmed/23216205. Retrieved 29 April 2013.
- "LabWare LIMS - Public Health". LabWare, Inc. http://www.labware.com/LWCLWeb.nsf/lp/en0203. Retrieved 29 April 2013.
- "Orchard Software - Data Mining". Orchard Software Corporation. http://www.orchardsoft.com/product/h_dataMining.html. Retrieved 29 April 2013.
- "LabDAQ Laboratory Information System (LIS)". CompuGroup Medical AG. http://cgmus.com/products--solutions/laboratory/labdaq_lis.aspx. Retrieved 29 April 2013.
- Foster, Kerry (February 2006). "Which comes first - the EMR or LIS?" (PDF). ADVANCE for Medical Laboratory Professionals. Merion Matters. http://www.orchardsoft.com/news_links/WhichComesFirstEMRorLIS.pdf. Retrieved 29 April 2013.
- Elliot, Michael H. (December 2006–January 2007). "The state of the ELN Market". Scientific Computing World. http://www.scientific-computing.com/features/feature.php?feature_id=50. Retrieved 04 May 2011.
- Elliot, Michael H. (October 2011). "Informatics Convergence Presents Opportunities and Challenges". Scientific Computing. http://www.scientificcomputing.com/articles-IN-Informatics-Convergence-Presents-Opportunities-and-Challenges-111111.aspx. Retrieved 25 February 2012.
- Williams, Robert W. (2003). "Managing Your Lab Data Flux: Getting Beyond Excel" (PDF). The Bioinformatics of Brains: From Genes and Proteins to Behaviors. Washington, DC: Society for Neuroscience. http://www.sfn.org/skins/main/pdf/ShortCourses/2003/sc1_9.pdf. Retrieved 17 February 2012.
- Howard, David A.; David Harrison (2007). "A Pragmatic Approach to the Validation of Excel Spreadsheets – Overview" (PDF). Pharma IT 1 (2): 30–35. http://www.spreadsheetvalidation.com/pdf/Excel_Spreadsheet_Validation_Overview.pdf.
- Vannest, Jeff (11 February 2011). "Advantages of a Data Warehouse". LABVANTAGE Solutions, Inc. http://www.labvantage.com/blog/?p=79. Retrieved 12 February 2013.
- "Workflow Management Coalition Terminology & Glossary" (PDF). Workflow Management Coalition. February 1999. pp. 9. http://www.wfmc.org/standards/docs/TC-1011_term_glossary_v3.pdf. Retrieved 20 February 2012.
- Maxwell, Glen (1 November 2003). "Using Workflows in LIMS to Reduce Customization". Scientific Computing and Instrumentation. http://www.scientificcomputing.com/using-workflows-in-lims-to-reduce.aspx. Retrieved 20 February 2012.
- Feist, Kelly (22 July 2011). "Harnessing Laboratory Information Systems to Support Increased Capacity and Staff Productivity". LabCompare. http://www.labcompare.com/10-Featured-Articles/19389-Harnessing-Laboratory-Information-Systems-to-Support-Increased-Capacity-and-Staff-Productivity/. Retrieved 29 April 2013.
- "ASTM E1578 - 06 Standard Guide for Laboratory Information Management Systems (LIMS)". ASTM International. http://www.astm.org/Standards/E1578.htm. Retrieved 22 February 2012.
- "Horizon Lab Financials". McKesson Corporation. http://www.mckesson.com/en_us/McKesson.com/For%2BHealthcare%2BProviders/Hospitals/Laboratory%2BSolutions/Horizon%2BLab%2BFinancials.html. Retrieved 29 April 2013.
- "ELN Reduces Regulatory Compliance Costs" (PDF). Labtronics Inc. January 2005. http://www.vialis.ch/fileadmin/files/imgs/pdf/Newsletter/q2-09/ELN_LAB.pdf. Retrieved 12 February 2013.
- Price, Michael (17 August 2012). "How an ELN Mitigates the Risks Associated with Regulatory Compliance". KineMatik Ltd. http://www.kinematik.com/blog/bid/207452/How-an-ELN-Mitigates-the-Risks-Associated-with-Regulatory-Compliance. Retrieved 12 February 2013.
- Proffitt, Allison (22 February 2012). "ELN Excellence: The New Lab Notebooks". BioIT World. http://www.bio-itworld.com/2012/02/22/eln-excellence-new-lab-notebooks.html. Retrieved 12 February 2013.
- Owens, S.R.; Dhir, R.; Yousem, S.A.; Kelly, S.M.; Piccoli, A.; Wiehagen, L.; Lassige, K.; Parwani, A.V. (June 2010). "The development and testing of a laboratory information system-driven tool for pre-sign-out quality assurance of random surgical pathology reports". American Journal of Clinical Pathology 133 (6): 836–41. doi:10.1309/AJCPLN9DU9LNXSXA. http://www.ncbi.nlm.nih.gov/pubmed/20472840. Retrieved 29 April 2013.
- "Netlims - AutoQuality". NeTLIMS NJ, LLC. http://www.netlims.com/lis_software_autoquality.asp. Retrieved 29 April 2013.
- "CLIN1 Laboratory Quality Control Software". Clin1, LLC. http://www.clin1.net/Quality_Control.htm. Retrieved 29 April 2013.
- "Electronic Code of Federal Regulations - Title 21: Food and Drugs - Part 11: Electronic Records; Electronic Signatures". U.S. Government Printing Office. http://ecfr.gpoaccess.gov/cgi/t/text/text-idx?c=ecfr&sid=5ff3a0efed913ef8fae9e225869688a2&rgn=div5&view=text&node=21:220.127.116.11.7&idno=21. Retrieved 02 March 2012.
- Jones, Andrew; Craig Valli (2008). "Chapter 1: An Introduction to Digital Forensics". Building a Digital Forensic Laboratory: Establishing and Managing a Successful Facility. Butterworth-Heinemann. pp. 11. ISBN 1856175103. http://books.google.com/books?id=F5IU7XXKwCQC.
- "Quality Assurance - Data Management" (PDF). Stable Isotope Ratio Facility for Environmental Research (SIRFER) at the University of Utah. http://sirfer.utah.edu/qaqc.pdf. Retrieved 07 May 2012.
- Hitchcock, Noel (2005). "Chapter 10: Efficient utilization of LIMS data and integration with mining process management systems". In Dessureault, Sean D.; Rajive Ganguli; Vladislav Kecojevic; Jami Girard Dwyer. Application of Computers and Operations Research in the Mineral Industry. Taylor & Francis. pp. 85–88. doi:10.1201/9781439833407.ch10. ISBN 9780415374491. http://www.crcnetbase.com/doi/abs/10.1201/9781439833407.ch10.
- Turner, Elizabeth; Jojean Bolton (2001). "Required steps for the validation of a Laboratory Information Management System". Quality Assurance 9 (3–4): 217–224. PMID 12553085. http://www.ncbi.nlm.nih.gov/pubmed/12553085.
- Amin, Waqas; Sirintrapun, S. Joseph; Parwani, Anil V. (August 2010). "Utility and applications of synoptic reporting in pathology" (PDF). Open Access Bioinformatics 2010 (2): 105–12. doi:http://dx.doi.org/10.2147/OAB.S12295. http://www.dovepress.com/getfile.php?fileID=7293. Retrieved 29 April 2013.
- Gilles, Clarence (1 July 2008). "Bar Code and Sample Tracking: It All Starts with the Label". Scientific Computing. http://www.scientificcomputing.com/bar-code-and-sample-tracking.aspx. Retrieved 8 May 2012.
- Davidowitz, Hanan (31 July 2012). "Use of Radio Frequency Identification (RFID) for Sample Tracking". American Laboratory. http://www.americanlaboratory.com/913-Technical-Articles/118171-Use-of-Radio-Frequency-Identification-RFID-for-Sample-Tracking/. Retrieved 29 April 2013.
- Pavlis, Robert (May/June 2004). "Trends in instrument-to-LIMS interfacing". Scientific Computing World. http://www.scientific-computing.com/features/feature.php?feature_id=88. Retrieved 8 May 2012.
- DeHeer, Larry (1 October 2009). "Instrument Interfacing - The Great Paradox of LIMS?". LIMSfinder.com. http://www.limsfinder.com/BlogDetail.aspx?id=33851_0_2_0_C. Retrieved 8 May 2012.
- "Section 3: Clinical and Administrative Domains - HL7 Version 2.7 Standard: Chapter 13 - Clinical Laboratory Automation". HL7. http://www.hl7.org/implement/standards/product_brief.cfm?product_id=203. Retrieved 29 April 2013.
- "Mobile Devices: On the Move from Laboratories to Clinics". Society for Laboratory Automation and Screening. 02 July 2012. http://www.eln.slas.org/story/1/69-mobile-devices-on-the-move-from-laboratories-to-clinics. Retrieved 13 February 2013.
- "Horizon MobileCare Phlebotomy". McKesson Corporation. http://www.mckesson.com/en_us/McKesson.com/For%2BHealthcare%2BProviders/Hospitals/Laboratory%2BSolutions/Horizon%2BMobileCare%2BPhlebotomy.html. Retrieved 29 April 2013.
- "Modern web based Lims from 10 Euro cent/sample". Bytewize AB. http://www.bytewize.com/o3lims-xpress/prices/?lang=en. Retrieved 8 May 2012.