LIMS feature

From LIMSWiki
Jump to navigationJump to search
You can find a listing of all LIMS vendors — and by extension, the features their products offer — on the LIMS vendor page.

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[1]:

  • the reception and log in of a sample and its associated customer data
  • the assignment, scheduling, and tracking of the sample and the associated analytical workload
  • the processing and quality control associated with the sample and the utilized equipment and inventory
  • the storage of data associated with the sample analysis
  • the inspection, approval, and compilation of the sample data for reporting and/or further analysis

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 Inc.'s LIMS2010 and Two Fold Software's Qualoupe LIMS, 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 very 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 management is one of the core functions a modern LIMS is tasked with, whether it's in a manufacturing, water treatment, or pharmaceutical laboratory.[2] 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[2]:

  • storing related sample information, including aliquot numbers, dates, and external links
  • setting user alerts for sample status
  • creating and documenting viewable sample container schemas with name and status
  • assigning sample access rights
  • assigning custom sample ID numbers based on a specification

Additional functionality that could potentially fall under this feature:

  • utilizing a unique ID system
  • barcoding of samples
  • defining sample points and series
  • creating data associations for samples
  • issuing sample receipts

Sample tracking

Where's sample 20110512_122GJH? Sample tracking functionality will let you know which lab oven it's in.
For most laboratory personnel, knowing that a sample has arrived to the lab isn't good enough; they need to know where it's located and what is being done with it. Enter the sample tracking feature. Without it, many problems arise. In the forensic 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.[3]

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 2-D barcode technology. While handwritten labels were the norm, now barcode support in a LIMS can "tie together a vast amount of information, clearly relating each sample to a specific case."[3] 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.[4]

The functionality of sample tracking strongly ties into the audit trail and chain of custody features of a LIMS.

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."[5] 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 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.[6] Some LIMS like LabWare, Inc.'s LabWare LIMS offer multiple types of schedulers that match to the particular functions of a research laboratory.[7] 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:

  • registration of received samples into the system
  • production of reports
  • creation and sending of e-mails and alerts
  • maintenance of equipment
  • assignment of workloads to personnel

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 very specialized approach to data views. For example, Biomatters Ltd.'s Geneious and Geneious Pro offer multiple methods of viewing complicated sequence analysis data, including 3-D structuring and representations of plasmid vectors.[8]

Data and trend analysis

Some LIMS allow users to analyze sample data directly from the software.
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 LIMS, it's now more common to see basic analysis tools being included. Such tools allow raw data to be imported directly to the LIMS, which then can store, process, and report information about it. Additionally, 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),"[9], today data management options like the previously mentioned Geneious Pro are starting to emerge, offering the ability to perform specialized analytical tasks for the sequencing industry.[8]

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 LIMS and other data management solutions.[2]


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 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 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, some modern LIMS vendors have responded instead by adding functionality that gives end users and/or LIMS administrators more control over the user interface.

Aspects of the LIMS' user interface that are becoming more customizable by the end user include:[10][11][12]

  • system nomenclature
  • equations used in calculations
  • data and universal fields
  • appearance of the interface and/or menus
  • primary system language
  • the LIMS source code, especially if in a non-proprietary format

Query capability

Advanced query tools allow researchers to better complete project objectives.
As was the case before the advent of databases and electronic data management solutions, today researchers must search through sample results, experiment 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 a LIMS. Not only can data be searched for based on name, number, or vendor, LIMSs like eBioSys' eLab and Mountain States Consulting's MSC-LIMS allow for queries of attached meta-data like user ID, project number, task number, sample type, location, and collection date.[13][14] 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.[2]

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 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 like Bridge-Soft's QMS even allow to cross-reference laboratory nomenclature from received data sources with the recipient's.[15] 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. Additionally, some LIMS may allow for the import and integration of non-normalized legacy data tables with LIMS data tables into a single database.

Internal file or data linking

This feature allows LIMS users to link together reports, protocols, sample results, and more, providing greater contextual clarity to projects. Examples include:

  • linking a sample batch to a test or sample preparation methodology
  • linking a test process to a particular customer
  • linking a report to a sample batch
  • linking a group of test results to a raw data file
  • linking an image to a work order
  • linking all lab results with the correct reporting test method

External file or data linking

This feature allows LIMS users to link together data and files in the LIMS with data, files, and customers outside the scope of the LIMS. Examples include:

  • linking data files from chromatography equipment to synthesis data[16]
  • linking equipment ID with an external annotation database[17]
  • linking external standard operating procedure documents with an internal test specification[18]

ELN support or integration

As a software replacement for more traditional paper laboratory notebooks, 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.[19][20] The result today is some LIMS either include traditional ELN functionality or link physical laboratory notebook references to data in the LIMS.[21]

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.[22] 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.[23] Nevertheless, laboratories continue to use Excel in some fashion, and thus Excel integration or data exportation in Excel format is a real need for LIMS customers. LIMS with this feature allow raw, processed, or imported data to be exported in the Excel format for further analysis and dissemination.

Export raw data

While not described as a feature on most LIMS vendor websites, a few indicate that their LIMS is capable of maintaining and exporting data in its raw format for future analysis.

Data warehouse

A LIMS' data warehouse serves the important function of storing, extracting, and managing the data that laboratories crank out 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.[24]

Deadline control

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 considered part of scheduling or alarms.

Production control

There are many types of businesses that produce goods, and in most cases there is a research 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.[25] 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.[26]

The types of functionality that may fall under this feature include:

  • recipe management
  • consumable tracking
  • batch traceability
  • production planning
  • enterprise resource planning

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:

  • job allocation and rescheduling
  • instrument workload tracking
  • time tracking
  • pending workload verification
  • priority setting
  • project-based workflow management
  • sample, batch, and document linking
  • work list sharing
  • recurring event management

Inventory management

LIMS can help laboratories keep track of their stock of reagents and even streamline reordering of them.
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, most LIMS products now include some sort of inventory management functionality.
  • register origin, 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 that samples and electronic equipment may also be considered inventory, and thus there is likely some functionality crossover with the sample management and 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 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 document data. Functionality of a typical document management system includes the ability to:

  • upload and index documents
  • enforce version control
  • provide full text search
  • export to PDF or other relevant format
  • add documents as attachments

Case management

The laboratory information system (LIS) has played an important role in the case management tasks of patient-centric and clinical laboratories. However, some LIMS have gained case management functionality, effectively blurring the lines between LIS and LIMS.[27]. Self-proclaimed LIMS products have emerged in the clinical, public health, and veterinary industries, areas that have historically been served by LIS software. When also considering the fields of law enforcement and forensic science, case management has an increasingly important role in some LIMS. Functionality seen in the 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

Workflow management

Capturing workflow in the lab is becoming more commonplace for the LIMS.
Workflow 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.[28] However, in the 2000s LIMS vendors began incorporating workflow management functionality into their LIMS software, reducing the headaches that customization of a LIMS often brought.[29]


Modern commercial and open-source LIMS solutions often feature workflow management functionality, including[30][31][29]:

  • attribute definition of activities
  • definition of inputs and outputs of activities
  • assignment of documentation to activities
  • setting of quality control limits
  • dynamically modify workflow in case of future changes
  • receive notification of changes to the workflow
  • sending user-defined messages during the process


Specification management

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 LIMS[32], so too do LIMS users have standards and specs for their laboratory. With spec management in place within the LIMS, 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

Note that some of the functionality of spec management may cross over into the realm of quality control and data validation.

Customer 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, and equipment providers. 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.

Billing management

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:

  • payment processing
  • expense reporting
  • price quotes
  • revenue management
  • workload tracking of billable hours
  • bill of materials
  • grant management

 

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 a LIMS meets regulatory compliance is often a complex one. While Title 21 CFR Part 11 has arguably had the largest influence on a 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, LIMS 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 a LIMS allow users to maintain a level of necessary quality across many of the functions 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.

Common functionality includes[33][34]:

  • single or batch QA/QC tests
  • quality control charts and reports
  • proficiency testing
  • document management
  • instrument maintenance
  • data acceptance/rejection
  • certificates of analysis (COA)
  • data types defined by QC analysis

Performance evaluation

As document management becomes increasingly prevalent in LIMS, it only makes sense to also 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 sample data or an entire LIMS, 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[35], 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. 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.[36] 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 standardized 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.

Data normalization

For the purposes of describing LIMS functionality, "data normalization" specifically refers to the process of ensuring incoming/imported data into the LIMS is standardized to the same 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.

Data validation

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.[37][38]

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."[39]

Data encryption

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 possessing a key/right/etc. to unlock/read the data. This functionality is especially vital to the Web-enabled LIMS, 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 LIMS to determine the strengths and weaknesses of their employed encryption methods.

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 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.[40] 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.

The temperature of an open cryopreservation container may be monitored on a computer via a connection to a LIMS with environmental monitoring functionality.
Other LIMS 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 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 existence of this piece of functionality 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.

Environmental monitoring

Some LIMS like Core LIMS and Oracle Health Sciences LabPas allow users to monitor the environmental conditions of not only sample storage containers but also the entire laboratory itself.[41][42] 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.[43]

 

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

Report printing

Label support

Barcode support

Export to PDF

Export to MS Word

Export to HTML or XML

Fax integration

Email integration

 

Base functionality

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

 

Administrator management

Modular

Instrument interfacing and management

Mobile device integration

Alarms and/or alerts

Work-related time tracking

Voice recognition system

External monitoring

Messaging

Multilingual

Network capable

Web client or portal

Online or integrated help

Software as a service delivery model

Usage-based cost

 

References

  1. ↑ Skobelev, D.O.; T.M. Zaytseva; A.D. Kozlov; V.L. Perepelitsa; A.S. Makarova (2011). "Laboratory information management systems in the work of the analytic laboratory" (PDF). Measurement Techniques 53 (10): 1182–1189. doi:10.1007/s11018-011-9638-7. http://www.springerlink.com/content/6564211m773v70j1/. 
  2. ↑ 2.0 2.1 2.2 2.3 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. 
  3. ↑ 3.0 3.1 Murthy, Tal; Brian Hewson (1 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. 
  4. ↑ Muntean, Edwarda; Nicoleta Munteanb; Tania Mihăiescua; Radu Mihăiescuc (2008). "LIMS use in laboratory data management". ProEnvironment/Promediu 1 (2): 19–23. http://proenvironment.ro/promediu/article/view/2835. 
  5. ↑ "Batch Sizes And QC Questions". U.S. EPA. 27 July 2011. http://www.epa.gov/osw/hazard/testmethods/faq/faqs_qc.htm. Retrieved 11 February 2012. 
  6. ↑ "Matrix Gemini - Scheduler". Autoscribe Ltd.. http://www.autoscribe.co.uk/matrix-gemini/additional-modules/scheduler. Retrieved 11 February 2012. 
  7. ↑ "LabWare LIMS - Scheduler". LabWare Inc.. http://www.labware.com/LWWeb.nsf/lp/en040102. Retrieved 11 February 2012. 
  8. ↑ 8.0 8.1
  9. ↑ Richter, Brent G.; David P. Sexton (2009). "Managing and Analyzing Next-Generation Sequence Data". PLoS Computational Biology 5 (6). doi:10.1371/journal.pcbi.1000369. http://www.ploscompbiol.org/article/info%3Adoi%2F10.1371%2Fjournal.pcbi.1000369. 
  10. ↑
  11. ↑
  12. ↑
  13. ↑
  14. ↑
  15. ↑
  16. ↑
  17. ↑
  18. ↑
  19. ↑ 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. 
  20. ↑ 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. 
  21. ↑
  22. ↑ 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. 
  23. ↑ 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. 
  24. ↑ Vannest, Jeff (11 February 2011). "Advantages of a Data Warehouse". LABVANTAGE Solutions, Inc.. http://www.labvantage.com/blog/?p=79. Retrieved 17 February 2012. 
  25. ↑
  26. ↑
  27. ↑ Hice, Randy (1 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 09 May 2011. 
  28. ↑ "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. 
  29. ↑ 29.0 29.1 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. 
  30. ↑ Melo, Alexandre; Alessandra Faria-Campos; Daiane M DeLaat; Rodrigo Keller; Vinícius Abreu; Sérgio Campos (2010). "SIGLa: an adaptable LIMS for multiple laboratories". BMC Genomics 11 (Suppl 5): S8. doi:10.1186/1471-2164-11-S5-S8. http://www.biomedcentral.com/1471-2164/11/S5/S8. 
  31. ↑ "My laboratory has unique processes, Can X-LIMS work for me?". EthoSoft, Inc.. http://www.ethosoft.com/LIMS/XLIMSProductInfo/XLIMSFAQ/tabid/69/Default.aspx. Retrieved 20 February 2012. 
  32. ↑ "ASTM E1578 - 06 Standard Guide for Laboratory Information Management Systems (LIMS)". ASTM International. http://www.astm.org/Standards/E1578.htm. Retrieved 22 February 2012. 
  33. ↑ Paszko, Christine; Carol Pugsley (2000). "Considerations in selecting a laboratory information management system (LIMS)". American Laboratory 32 (18): 38–42. doi:10.1016/0169-7439(94)90006-X. http://www.mendeley.com/research/considerations-selecting-laboratory-information-management-system-lims/. 
  34. ↑ Hull, Carl; Bruce Wray; Ford Winslow; Mark Vilicich (2011). "Tracking and Controlling Everything that Affects Quality is the Key to a Quality Management System" (PDF). Combinatorial Chemistry & High Throughput Screening 14 (9): 772–780. doi:10.2174/138620711796957125. http://www.uniconnect.com/wp-content/uploads/2011/11/CCHTS-LIMS-Article.pdf. 
  35. ↑ "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:1.0.1.1.7&idno=21. Retrieved 02 March 2012. 
  36. ↑ 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. 
  37. ↑ "Quality Assurance - Data Management". Stable Isotope Ratio Facility for Environmental Research (SIRFER) at the University of Utah. http://sirfer.utah.edu/qaqc.pdf. Retrieved 07 May 2012. 
  38. ↑ 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. 
  39. ↑ 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. 
  40. ↑ "LabWare - Table Explorer". LabWare, Inc.. http://www.labware.com/LWWeb.nsf/lp/en041001. Retrieved 07 May 2012. 
  41. ↑ "Core LIMS Features & Components". Core Informatics, LLC. http://www.corelims.com/features.htm. Retrieved 07 May 2012. 
  42. ↑ "Oracle Health Sciences LabPas" (PDF). Oracle Corporation. 2011. http://www.oracle.com/us/industries/life-sciences/health-sciences-labpas-ds-396097.pdf. Retrieved 07 May 2012. 
  43. ↑ "Environmental Monitoring Program". Novatek International. http://ntint.com/prod-envmon.shtml. Retrieved 07 May 2012. 
Retrieved from "https://www.limswiki.org/index.php?title=LIMS_feature&oldid=8466"