ELN feature

ELNs are designed to supplement or replace laboratory notebooks like these, often adding additional operational functionality in the process.

An ELN feature is one or more pieces of functionality that appear within an electronic laboratory notebook (ELN).

The ELN is an evolving concept, with new features and abilities being introduced every year. As laboratory demands change and technological progress continues, the functions of an ELN will also change. Yet like the dishwasher, the ELN tends to have a base set of functionality that defines it.

Electronic laboratory notebooks extend the functionality and efficiency of four central aspects of the researcher's activities:

• recording experimental and other types of research data
• providing organized and searchable structure to that data
• allowing the sharing of that data through collaborations or with internal or external individuals
• communicating with others about that data and research

Of course, there are ELN features that are difficult to categorize under any of these activities. Such features often contribute to the entire ELN and how it's utilized. For example, multilingual support allows users to interact with the ELN 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 ELN product information on vendor websites. An attempt was made to discover the features most utilized in vendors' ELN products and collect information on those features for each ELN. Not every possible feature is referenced here; some ELN 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.

Experiment, collaboration, and data management

To hide the contents of this section for easier reading of other sections, click the "Collapse" link to the right.

 

Chemical drawing and calculation

Chemical and/or spectrum file support

Reagents database

Task and event scheduling

Within the context of an ELN, 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. Experiments 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 ELN, a modern data management system can now optimize those tasks and provide additional scheduling functionality to streamline the operation of a lab. Some ELNs like Labtronics Inc.'s Nexxis ELN can schedule due dates on worksheets and experiments. 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 an ELN include:

• production of reports
• creation and sending of e-mails and alerts
• maintenance of equipment
• assignment of experiments to personnel

Option for manual result entry

While many ELN vendors tout the ability of their product to automate the entry of experiment results into the ELN 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 ELN. 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 ELN.

Multiple data viewing methods

Researchers produce reams of data, and the ELN exists to help organize and share that data. Additionally, even before the existence of the ELN, scientists have had a corresponding need for visually representing data. Today an ELN can not only collect and analyze data from experiments, but it also can represent that data in reports, graphs, gradients, and spreadsheets. Depending on the ELN, more than one way to visually represent the data may exist.

The ELN is particularly useful for displaying chemical structures and bonds in more than one way through built-in or integratable chemical structure drawing tools or through a document manager that can handle the placement of screenshots, sketches, or other images.

Configurable templates and forms

Data and trend analysis

Some ELNs allow users to analyze experiment data with built-in software tools.

Sample experimentation and analysis plays 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 ELN, it's now more common to see basic analysis tools being included. Such tools allow raw data to be imported directly to the ELN, which then can store, process, and display it in a shareable form. Additionally, chemical calculations and functions used in the analysis are typically definable and editable for further flexibility.

As with the feature "multiple data viewing methods," data and trend analysis is also increasingly important in laboratories that have very 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),", today data management options like Scilligence ELN are starting to emerge, offering the ability to perform specialized analytical tasks for the researcher.

As sample experimentation and data analysis are important parts 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 ELN, LIMS, and other laboratory informatics solutions.

Data and equipment sharing

Aside from data storage and sample registration, a modern ELN's major contribution to the laboratory is both in aiding in the sharing of experiment results, reports, and other research data with those who need it most and the documentation of vital evidence for potential patent interference cases. Rather than pieces of information becoming misplaced or forgotten in physical laboratory notebooks, the ELN makes it easier to share experiment results and increase the efficiency of collaboration inside and outside the laboratory. 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.

Customizable fields and/or interface

As thorough as some user interface (UI) developers may be in adding relevant fields and interface options for eln 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 ELN vendors have responded instead by adding functionality that gives end users and/or ELN administrators more control over the user interface.

Aspects of the ELN's user interface that are often customizable by the end user include:

• notebook interface and display
• chemical drawing methods and display
• sharing options

Query capability

An ELN's query tools may be as simple as looking up demographic data or finding specific strings of characters in research data.

As was the case before the advent of databases and electronic data management solutions, today researchers must search through experiment results, notes, and other types of data to better draw conclusions about their research. Whereas this used to mean browsing through laboratory notebooks, Excel spreadsheets, or Access databases, now powerful query tools exists within data management tools like ELN and LIMS. Not only can data be searched for based on name, number, or vendor, ELNs like ChemBytes' Espresso ELN allow for advanced queries of molecular patterns and properties associated with the SMARTS language.

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
• create ad-hoc queries

Import data

Data can originate from numerous places in the laboratory. The ability to import that data into an ELN 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. Additionally, some ELN may allow for the importation of other application data in other formats, including XML data like in Agilent's OpenLAB ELN.

Internal file or data linking

This feature allows research collaborators using an ELN to link together experiments, reports, protocols, results, and more, providing greater contextual clarity to projects. Examples include:

• linking a sample batch to an experiment 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 notebook entry
• linking all experiment results with the correct reporting test methods

External file or data linking

This feature allows research collaborators using an ELN to link together data and files housed in the database with data, files, and customers outside the ELN's servers. Examples include:

• linking to external research data sources hosted on the Internet
• linking external data sources with internal laboratory execution methods
• linking an ELN to an external LIMS or other laboratory informatics solution

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 ELN customers. ELNs with this feature allow raw, processed, or imported data to be exported in the Excel format for further analysis and dissemination elsewhere in the ELN or externally from it.

Raw data management

While not described as a feature on most ELN vendor websites, a few indicate that their notebooks are capable of managing (import, export, editing, etc.) data in its raw format for future analysis and dissemination.

Data warehouse

An ELN's 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.

Project and task management

Project and task management within an ELN typically involves the scheduling of tasks to researchers 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 ELNs 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: Experiment management

Inventory management

ELNs can assist researchers not only allocate reagents to particular experiments or stations but also track available quantities for future experiments.

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 ELN products now include 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
• 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
• 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 creation and management

Standard operation procedures, (SOPs), specifications, reports, graphs, images, and receipts are all collected and used in the average laboratory. With an ELN already designed to reference and store experiment data of all types, it makes sense to include functionality to create, import, export, and manage other sorts of data files. As experimental data can be indexed, queried, and linked, so too can document data. Functionality of a typical document management system includes the ability to:

• upload and index documents
• add images and photos inline to a notebook entry
• enforce version control
• provide full text searches
• export to PDF, XML, or other relevant formats
• add documents as attachments

Lab and group management

Experiment management

Workflow management

Capturing workflow in the lab is becoming more commonplace for laboratory informatics products.

Workflow 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 ELN solutions often feature workflow management functionality, including:

• managing the request cycle within a laboratory
• executing and review ELN workflow validations
• managing specific chemistry- and biology-related procedures
• creating and assigning unstructured experiment documentation
• defining activity attributes
• setting of quality control limits
• dynamically modifying workflow in case of future changes
• receiving notification of changes to the workflow

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 experiments, 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.

 

Quality, security, and compliance

To hide the contents of this section for easier reading of other sections, click the "Collapse" link to the right.

 

Regulatory compliance

The topic of whether or not an ELN 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:

• ASTM
• ASCLD/LAB
• Classified data
• Freedom of information legislation (various)
• GALP and GAMP
• HIPAA
• Health Level 7
• ISO/IEC 17025
• ISO 9000/9001
• ISO/TS 16949
• ODBC
• TNI and NELAP
• Title 40 CFR Part 3

With so many codes, standards, and regulations, ELN consumers are advised to contact vendors with their user requirements and ask how the vendor's software meets and/or exceeds those requirements.

QA/QC functions

The quality management functions of an ELN allow users to maintain a level of necessary quality across many of the functions in a laboratory. However, traditionally ELNs have been the domain of research and development (R&D) functions, in the process not giving much consideration to the needs of quality assurance and quality control (QA/QC) laboratories. Where R&D labs need flexibility and freedom, QA/QC labs require more structure in their ELN software. Some vendors have created ELN modules or separate software solutions (like laboratory execution systems [LES]) to address the specific needs of QA/QC labs, while other vendors have simply included an ELN add-on to their LIMS.

Performance evaluation

As document and file management plays an important role in electronic laboratory notebooks, it only makes sense 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 trail

Whether validating an instrument's data or an entire ELN, maintaining an audit trail is an important part of 21 CFR Part 11 compliance.

As codes and regulations like Title 21 CFR Part 11 mandate "computer systems (including hardware and software), controls, and attendant documentation" utilize electronic signatures and audit trails, ELN 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
• location
• case 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, 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 ELN 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 laboratory trainees may only be given read-only access to the experiment management 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 ELN's functionality.

Data normalization

For the purposes of describing ELN functionality, "data normalization" specifically refers to the process of ensuring incoming/imported data into the ELN is standardized to the same format of existing data.

Here's an example to better explain this issue. When an ELN is initially configured, in most if not all cases a clear standard can be set for how logged experiment 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 ELN 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 ELN 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.

Data validation

For the purposes of describing ELN 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 any given data management process. 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 ELN 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 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."

Data encryption

The existence of this functionality in an ELN generally 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 ELN, 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 an ELN to determine the strengths and weaknesses of their employed encryption methods.

Electronic signatures

Version control

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 ELN, 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 ELN 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 ELN 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 an ELN 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 ELN.

 

Reporting, barcoding, and printing

To hide the contents of this section for easier reading of other sections, click the "Collapse" link to the right.

 

Custom reporting

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, charts, pivot tables, and multiple output formats.

Note: Some LIMS vendors will offer custom reporting as an option as an added cost, depending on the level of customization required.

Report printing

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.

Label support

The label — typically affixed to a sample 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.

The word "Wikipedia" encoded in Code 128 and Code 39

Barcode 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 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 bar code readers.

Barcode 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.

Fax integration

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.

Email integration

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.

 

Base functionality

To hide the contents of this section for easier reading of other sections, click the "Collapse" link to the right.

 

Administrator management

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.

Modular

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

An entire room of gas chromatography instruments could potentially be connected to a LIMS via instrument interfacing.

In laboratories there are instruments, and with those instruments comes scientific measurements which produce data. It's therefor natural a lab technician would want to connect those instruments to a laboratory information management system, which is already organizing and storing laboratory data. This sort of interfacing is typically handled with instrument-to-LIMS 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, "many LIMS vendors can act as single source providers of the entire instrument interfacing solution,", providing a cheaper and smoother solution to LIMS customers.

Mobile device integration

While not incredibly common, a few LIMS developers are including support for mobile devices in their laboratory information management system. LabCollector, for example, extends its LIMS' functionality to Pocket PC or Windows CE devices equipped with wireless barcode scanners, allowing users to read or collect sample information while on the move. Future Technologies' DNA LIMS, designed for labs performing DNA analysis, has its own mobile version for technicians who need access but can't be in the lab.

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.

Work-related time tracking

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.

External monitoring

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.

Messaging

Instant messaging clients built into a LIMS often make it easier to collaborate.

The messaging feature of a LIMS may refer to one (or both) of two 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 LIMS itself to send messages or alerts to a user's mobile or smart phone

Multilingual

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.

Network-capable

This feature is perhaps archaic and/or obvious, but it is mentioned nonetheless. It's generally applied to a non-Web-based 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.

Usage-based cost

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.