Blaze Systems Corporation
A LIMS feature is one or more pieces of functionality that appear within a laboratory information management system (LIMS).
The LIMS is an evolving concept, with new features and abilities being introduced every year. As laboratory demands change and technological progress continues, the functions of a LIMS will also change. Yet like the automobile, the 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:
Of course, there are LIMS features that are difficult to categorize under any of these phases. Such features often contribute to the entire LIMS and how it's utilized. For example, multilingual support appears in LIMS like Assaynet's Assaynet LIMS and SLCLAB Informática's ALFA21, allowing users to interact with the LIMS in more than one language. Some functionality may also overlap several laboratory phases, making it difficult to firmly classify.
The features described below come from an analysis of freely available LIMS product information on vendor websites. An attempt was made to discover the features most utilized in vendors' LIMS products and collect information on those features for each LIMS. Not every possible feature is referenced here; some LIMS 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.
Sample, inventory, 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 accessioning and management is one of the core functions a modern LIMS is tasked with, whether it's in a manufacturing, water treatment, or pharmaceutical laboratory. As such, researchers who work in these types of labs are unable to complete their experiment-based goals without an effective method of managing samples. The process of sample management for experiments includes, but is not limited to:
Additional functionality that could potentially fall under this feature:
Sample trackingforensic world, for example, many samples are linked to a criminal investigation. In this case, misidentification, contamination, or duplication can become significant issues: a lost sample is essentially missing evidence, while a duplicated sample can render it useless as evidence.
After sample reception and its initial handling procedures, many LIMS can then track sample location as well as chain of custody. 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. The process of tracking a sample has become more streamlined with increasing support of barcode and radio frequency ID (RFID) technology. While handwritten labels were the norm, barcode and RFID support in a LIMS 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 have implemented extensive configurability to compensate for varying environments.
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 LIMS 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 LIMS, 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. Workloads are assigned to technicians, maintenance schedules are created and followed, and research deadlines must be observed. While these tasks have in the past been performed without LIMS, a modern data information management system can now optimize those tasks and provide additional scheduling functionality to streamline the operation of a lab. Autoscribe Ltd., for example, offers a scheduling module for its LIMS that allows users to automatically schedule multiple jobs, data backups, alarms, and reports. Some LIMS like LabWare, Inc.'s LabWare LIMS offer multiple types of schedulers that match to the particular functions of a research laboratory. Additional functionality within this feature includes the ability to configure automated assignments of analysis requests, establish recurring events, and in most cases, create printable schedules.
Examples of tasks and events that can feasibly be scheduled in a LIMS include:
Option for manual result entry
While many LIMS vendors tout the ability of their product to automate the entry of results into the LIMS database, 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 LIMS. Additional functionality associated with this feature includes a customizable spell check dictionary and the ability to add comments, notes, and narratives to most anything in the LIMS.
Multiple data viewing methods
Laboratories produce data, and LIMS exist to help manage that data. Additionally, even before the existence of LIMS, scientists have had a corresponding need for visually representing data. Today, a LIMS can not only collect and analyze data from samples, but it also can represent that data in reports, graphs, gradients, and spreadsheets. Depending on the LIMS, more than one way to visually represent the data may exist.
Some laboratory information management systems take a specialized approach to data views. For example, Biomatters Ltd.'s Geneious offers multiple methods of viewing complicated sequence analysis data, including 3-D structuring and representations of plasmid vectors, as well as other next-generation sequencing (NGS) activities.
Data and trend analysisanalysis play an important part of laboratory informatics, helping laboratories make better sense of their experiments and reach valuable conclusions about them. While this important phase of laboratory work has often been done externally from the LIMS, it's now common to see data analysis tools being included. Such tools allow raw instrument data as well as other imported and internal LIMS data to be analyzed, which then can be stored, processed, and reported on. Additionally, built-in calculations and functions used in the analysis are usually definable and editable for further flexibility, and custom calculations and functions are often able to be made by the end user.
As with the feature "multiple data viewing methods," data and trend analysis is also increasingly important in laboratories that have specialized data management needs. When even in 2009 genetic scientists in large- and medium-sized sequencing and core centers were voicing concerns about "a lack of adequate vendor-supported software and laboratory information management systems (LIMS)" that had the necessary analytical features, today's data management options, like the previously mentioned Geneious, readily offer data analysis tools for a diverse array of laboratory types.
Data and equipment sharing
Aside from data storage and sample registration, a modern LIMS' major contribution to the laboratory is aiding in the sharing of experiment results, reports, and other data types with those who need it most. Rather than pieces of information becoming misplaced or forgotten in laboratory notebooks, the LIMS makes it easier to share sample test results and increase the efficiency of collaboration inside and outside the laboratory. Yet data is more than just sample test results; it also comes in the form of charts, reports, policy and procedure documents, and other document types. Additionally, the need for controlling who has access to these and other 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.
Customizable fields and/or interface
As thorough as some user interface (UI) developers may be in adding relevant fields and interface options for LIMS 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, modern LIMS vendors have responded instead by adding functionality that gives end users and/or LIMS administrators more control over the user interface, including the addition and customization of user fields and inputs.
Aspects of the LIMS' user interface that are becoming more customizable by the end user include:
Increasingly, today's vendors tend to refer to their systems as being "configurable" rather than "customizable." Vendors such as Autoscribe Informatics will include screen editing and other tools that administrators can user to configure the various screens, data fields, nomenclature, etc. of the LIMS.
Query capabilityAbbott's STARLIMS and Mountain States Consulting's MSC-LIMS allow for queries of attached metadata like user ID, project number, task number, sample type, location, and collection date. Finally, as LIMS continue to include both sample management and experimental data management functionality, queries become more powerful in general as now sample and experiment can be matched together in one database.
Query functionality often includes the ability to:
Data can originate from numerous places in the laboratory. The ability to import that data into a LIMS can be beneficial, especially when an instrument can't be connected or an external client provides a data feed independent of the LIMS. Some LIMS may even allow users to cross-reference laboratory nomenclature from received data sources with the recipient's. And 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. Some LIMS may also allow for the import of non-normalized legacy data tables and integration with LIMS data tables to form a single unified database.
However, potential buyers should ensure the LIMS vendor is clear in how their system manages data imports. For example, products such as AgileBio's LabCollector may limit imports to a particular format such as CSV files. In particular, data migrations require extra vigilance from the potential buyer, who should confirm the LIMS vendor's ability to cleanly, completely, and reliably import your data into a new system.
This feature allows LIMS users to link together reports, protocols, sample results, and more, providing greater contextual clarity to projects. Examples include:
This feature allows LIMS users to link together data and files in the LIMS with data, files, and customers outside the domain of the LIMS. Examples include:
ELN support or integration
As a software replacement for more traditional paper , the electronic laboratory notebook (ELN) has been important to laboratory functions. Yet the lines between ELN and LIMS began to blur in the 2000s, with both types of software incorporating features from the other. More than a decade later, the ELN has become more distinct in purpose and functionality and is typically sold as a stand-alone solution. Despite this, some vendors such as Genohm have integrated ELN functionality into their LIMS in order to provide greater flexibility to researchers. Other vendors such as Core Informatics (part of Thermo Fisher Scientific) choose to keep the ELN as a separately managed solution but one that can easily integrate with a LIMS solution.
Export to MS Excel
While Microsoft Excel had 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 ultimately led many labs to turn to data management solutions that are easier to validate. Several decades later, some laboratories continue to use Excel in some fashion, and thus having a LIMS capable of handling Excel data remains useful. In particular, selecting and exporting the LIMS' data (from test results to quality control charts) into a format such as Excel may further data visualization, insights, and dissemination for some users.
Raw data management
While not described as a feature on most LIMS vendor websites, a few indicate that their LIMS is capable of managing (import, export, editing, etc.) data in its raw format for future analysis. This raw data is typically implied to be originating from instruments that interface with the LIMS, which in itself is not unusual. That raw data may remain housed in instruments, getting transformed into reportable data in the LIMS, but presumably most LIMS are also capable of housing the raw instrument data as well. Labs may also turn to scientific data management systems to better manage their raw data sources.
A LIMS' data warehouse serves the important function of storing, extracting, and managing the data that laboratories produce for the purposes or analysis, reporting, and process management, 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.
Deadline control is functionality within a LIMS that allows users to manage and be notified of events that occur within the laboratory. With this functionality users can also be notified of upcoming deadlines on anything from sample analysis to license renewal.
Note that this functionality may also feasibly fall under the task and event scheduling or alarms features. As deadline control seems to be advertised as a notable feature by only a few vendors, it seems even more likely that this functionality is practically considered part of scheduling or alarms.
There are many types of businesses that produce goods, and in most cases there is a research and development (R&D) laboratory involved at some point in the process. This is especially true in the pharmaceutical and chemical industries, where production measurements such as yield, volume, activity, and impurity are vital. As LIMSs have already recorded such information during tests and analysis, the addition of production control functionality seems natural. Some LIMS take a very active approach to this. For example, 2nd Sight Solutions' OhNo! features production control as major functionality for the synthesis of radiopharmaceuticals. Other LIMS may have less pronounced production functionality, while still offering the ability to track the production process in and out of the lab. And yet other LIMSs like dialog's diaLIMS offer robust production-based functionality but as a module or add-on to the base LIMS software.
The types of functionality that may fall under this feature include:
Finally, in production environments the LIMS is often referenced in conjunction with a manufacturing execution system (MES). The MES is used for tracking and documenting how raw materials are transformed into finished products, as well as optimizing the various workflows in the production processes. The MES may either interface with a LIMS for quality testing, management, and statistical analysis, or the MES may actually contain a LIMS module.
Project and/or task management
Project and task management within a LIMS typically involves the scheduling of tasks to workers 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 LIMS include functionality beyond scheduling that warrants the addition of the project and/or task management feature. This functionality includes:
Inventory managementreagents and radiopharmaceuticals to glassware and laboratory baths. With that comes the need to know how much/many and the frequency of use. For this, LIMS solutions include some sort of inventory management functionality.
Document creation and management
Standard operating procedures (SOPs), specifications, safety manuals and protocols, regulatory files, certificates, reports, graphs, images, and receipts are all collected and used in the average laboratory. With a LIMS already designed to manage and store sample and experiment data, it makes sense to include functionality to create, import, export, and manage other sorts of data files. As sample and experimental data can be indexed, queried, and linked, so too can documents. Functionality of a typical document management system includes the ability to:
The laboratory information system (LIS) has played an important role in the clinical case management tasks of patient-centric and clinical laboratories. However, LIMS begun taking on clinical functionality such as case management around the late 2000s, which began to effectively blur the lines between an LIS and a LIMS.. Since then, many more self-proclaimed LIMS products have emerged in the clinical, public health, and veterinary industries, areas that have historically been served by LIS software. This has resulted in numerous LIMS options that offer clinical functionality such as case management. When also taking into consideration the fields of law enforcement and forensic science, case management plays an important role in some LIMS. Functionality seen in the case management feature includes:
Workflow managementWorkflow management is common in the laboratory, acting as a graphical representation of planned sequential steps to either fully or partially automate a process within the lab. Separate standards-based workflow management systems (in the form of a software component) have traditionally performed this task. However, in the late 2000s LIMS vendors began incorporating workflow management functionality into their LIMS software, reducing the headaches that customization of a LIMS often brought.
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 ASTM offers standards and specs for LIMS, so too do LIMS users have standards and specs for their laboratory. With spec management in place within the LIMS, laboratories can then:
Customer and supplier management
Unless a laboratory is conducting internalized independent research, in most cases it will do business with external entities such as contract labs, sample providers, 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 samples, equipment, and tests becomes vital. Managing demographics, complaints, correspondence, and history are all feasible with customer 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.
While the finances of a laboratory are important, they've typically been handled separately as a business process. However, some LIMS include additional functionality to make handling financial transactions and documentation of all sorts possible within the LIMS. In theory, such functionality brings the possibility of keeping more of a laboratory's data centrally located and queryable. This feature may include:
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 LIMS 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 LIMS and other systems handle and store data. Other compliance-based codes, standards, and regulations include:
With so many codes, standards, and regulations, it can be challenging for potential LIMS buyers to fully vet whether a vendor's solution meets regulatory requirements, let alone helps labs meet the regulations and standards that affect them. In truth, most reputable vendors today have regulatory compliance well considered for their LIMS solutions, which are often purpose-built. However, it is ultimately up to the potential buyer to confirm that the vendor's solution complies to activities within their industry. Buyers 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 LIMS allow users to maintain a level of necessary quality across many of the activites in a laboratory. From running quality assurance tests to ensuring employed researchers are proficient at certain tasks, the QA/QC functionality of a LIMS is largely responsible for the output of consistent data and manufactured products in and out of the lab.
As prevalent as document management has become in LIMS, it makes sense to that the LIMS should also provide functionality to collate and store all the documentation associated with employee training and certification. Changes to laboratory techniques, scientific understanding, and business practices force 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 LIMS 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, LIMS 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, and it has become a mandatory feature for labs operating in regulated environments.
Information recorded in the audit trail typically includes:
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, 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 laboratory 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 LIMS users into defined security roles which provide role-specific access to certain LIMS functionality. Additionally, as responsibilities change within roles, that same flexible configuration is necessary for assigning or restricting access to certain LIMS 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 laboratory trainees may only be given read-only access to the sample login and sample tracking functionality of the system through a custom "Trainees" group role, while the head researcher of the lab may be given the "Administrator" role, which allows that individual to access most if not all of the LIMS' functionality.
For the purposes of describing LIMS functionality, "data normalization" specifically refers to the process of ensuring data that moves into the LIMS is formatted in a standardized way, matching the format of existing LIMS data.
Here's an example to better explain this issue. When a LIMS is initially configured, in most if not all cases a clear standard can be set for how logged samples and their associated measurements pre- and post-analysis are recorded in the system. Perhaps all temperatures will be recorded in Celsius to two decimal places. If temperature data imported from a spreadsheet or a lab instrument is not in this format, the LIMS can normalize the incoming data to match the standard already set for existing LIMS temperature data. This ensures consistency within the LIMS database and typically leads to better data validation efforts later on.
Note: Some LIMS 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.
For the purposes of describing LIMS functionality, "data validation" specifically refers to the process of ensuring existing data in the LIMS—either pre-analysis or post-analysis—sufficiently meets any number of standards or thresholds set for sample login, sample analysis, or any other data management process in the LIMS. This validation process may be completely automatic and system-based, or it may also include additional steps on the part of the user base utilizing additional LIMS functionality, including verification of standard operating procedures (SOPs), QC samples, and QA approval.
Note: This functionality shouldn't be confused with the process of validating the LIMS 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 LIMS software generally indicates the LIMS 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 users or systems possessing a key/right/etc. to unlock/read the data. This functionality has been important for the web-enabled LIMS, which transfers information over the internet in a client-server relationship, and it has become an increasingly vital part of cloud-based software offerings managing data in transit and at rest. As a wide variety of encryption technologies exist, it's generally a good idea to consult with the developers of a LIMS to determine the strengths and weaknesses of their employed encryption methods.
Version control is a form of safeguard which helps preserve data integrity. 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 LIMS, including test methods, training certifications, instrument logs, specifications, and process and procedure (P&P) documentation. In LIMS like LabWare LIMS, reference data can also be versioned while also retaining the original relationship between samples and test results, including the version of reference data current at the time lab testing is performed. 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. Another popular strategy is to, rather than locking the file, allow multiple people edit to a piece of information, later merging the various edits. Potential LIMS 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 functionality of automatic data backup in a LIMS 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 LIMS. As cloud-based LIMS have taken hold, scheduled cloud-to-cloud data backups of software data are becoming more practical.
Some LIMS like Core LIMS and Matrix Gemini 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. Alarms may be able to be configured to notify staff if a storage container's environmental attributes go beyond a certain threshold. Manufacturers utilizing a LIMS like NOVA-LIMS may also be able to employ more advanced environmental tracking features in the plant to guarantee a more consistent, higher quality product is created.
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 is a vital part of a LIMS, as it allows users to gain a clearer picture of collected data and potential trends. At a minimum, a number of pre-configured report styles come standard with a LIMS. However, some LIMS 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 (such as branding), charts, pivot tables, and multiple output formats.
Note: Some LIMS vendors will offer custom reporting as an option as an added cost, depending on both the base reporting functionality of the LIMS and the level of customization required.
Today's LIMS 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 LIMS software.
The label—typically affixed to a sample or evidence container—is a vital part of the sample tracking process. Identifying information such as sample number, batch number, and barcodes are printed on such labels to ensure optimized sample management and more precise sample data. As such, some LIMS allow users to design and print labels directly from the software.
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. As such, LIMS developers have integrated barcode support into their laboratory information management systems, including support for symbologies like Code 128, Code 39, and Interleaved 2 of 5. Aside from printing options, a LIMS may also offer support for a variety of barcode readers.
Radio-frequency identification (RFID) technology has also made inroads into the laboratory. Like barcode labels, RFID tags can be placed on samples and get read when exposed to active RFID scanning devices. This technology has some advantages over barcodes in that direct line of sight isn't required, the scanning and tracking process is more automated, and more data can be encoded. With these apparent advantages, some LIMS vendors have also added support for RFID-fed sample information.
Barcode/RFID support and label support are typically found together in LIMS software, but not always, thus their separation into two features of a LIMS.
Export to PDF
A LIMS with this feature is able to collect and save information into a Portable Document Format (PDF).
Export to MS Word
A LIMS with this feature is able to collect and save information into a Microsoft Office Word format.
Export to HTML or XML
A LIMS with this feature is able to collect and save information into a HyperText Markup Language (HTML) and/or Extensible Markup Language (XML) format.
A LIMS 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. However, with the declining popularity of the fax machine, this feature is starting to disappear from modern LIMS.
A LIMS with this feature is able to integrate with and use the electronic mail information exchange method to send reports, alerts, and more via manual input, automatically, and/or at scheduled intervals.
The administrator management tools of a LIMS allow lab technicians to set up the LIMS most optimally for the laboratory. Through the administrator management interface of a LIMS, other features may be accessed like setting up user roles and scheduling automatic data backups.
Like report printing, administrator management is nearly ubiquitous in LIMS 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 LIMS 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 LIMS and 2. the limiting of overall effects on the system design as new functionality is added.
Instrument interfacing and management This eventually meant that "many LIMS vendors [could] act as single source providers of the entire instrument interfacing solution,", providing a cheaper and smoother solution to LIMS customers. Today, instrument interfacing is integral to LIMS and is considerably easier to do than prior decades.
The ability to calibrate and schedule maintenance for interfaced instruments may also be included in this category.
Mobile device integration
Some LIMS vendors tout support for mobile devices using their laboratory information management system. This feature has become increasingly common with the advent of first the web-based LIMS, followed by the cloud-based LIMS. This has given technicians the ability to collect data in the field, approve results remotely, and manage experiment workflow on the fly.
Alarms and/or alerts
Alarms and alerts are an integral part of a LIMS. They 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. When the results for a sample analysis go out out of range, an automatic warning message can appear on the screen of the technician responsible for the analysis. A scheduled alert can be e-mailed to a lab technician every month indicating a piece of laboratory equipment needs routine maintenance. If the LIMS is equipped with environmental monitoring, an alert can be sent in the form of an SMS text message to the head researcher if the temperature inside a freezer unexpectedly rises. All of these scenarios represent a tiny fraction of the possible implementation of alarms and alerts in a LIMS, highlighting how powerful (yet easy to take for granted) this feature is.
This feature specifically refers to a LIMS' 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).
Voice recognition system
A LIMS with this feature allows some functions of the LIMS (for example, accessing sample analysis results) to be accessed via voice commands.
This feature allows clients outside the laboratory to monitor the status of sample batches, test results, and more via an online web portal or, less commonly, as activity alerts sent via e-mail, fax, or SMS.
If a LIMS is listed as multilingual, its an indication the LIMS interface can be configured to display more than one language depending on the preference a user or administrator chooses. Some LIMS 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 (on-premises) LIMS installed over a local or wide-area computer network, essentially indicating the LIMS is not an isolated application, but rather one that can interface with other instances of the LIMS or other networked instruments.
Web client or portal
A LIMS with a web client or portal is either a web-based LIMS (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 LIMS with an included portal to access it via the internet.
Online or integrated help
This indicates a LIMS has help infrastructure integrated into the software, support documentation via the LIMS 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. This typically constitutes a LIMS vendor having a "cloud-based" offering.
While rare, some LIMS 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. You may also see this sort of usage-based cost on some cloud-based LIMS.
|Oct 12, 2009||Instrument Interfacing - The Great Paradox of LIMS?|
|Mar 16, 2009||Blaze Systems Issues Systems Integration White Paper|
|Mar 06, 2009||Blaze Systems Issues Barcode Labeling White Paper|
|No News found.|
|No Job Posts found.|
|No Webinars found.|