Difference between revisions of "LIS feature"

From LIMSWiki
Jump to navigationJump to search
(→‎Data mining: Added content.)
m (Text replacement - "\[\[Technidata SAS(.*)" to "[[Vendor:Technidata SAS$1")
 
(84 intermediate revisions by 2 users not shown)
Line 1: Line 1:
{{ombox
{{ombox
| type      = notice
| type      = notice
| image    = [[Image:Emblem-important-yellow.svg|40px]]
| style    = width: 960px;
| style    = width: 960px;
| text      = This article should be considered a work in progress and incomplete. In some cases, information has been copied and pasted from another article for formatting purposes, with plans to modify the content to the article topic. Consider this article incomplete until this notice is removed.
| text      = '''You can find a listing''' of all LIS vendors—and by extension, the features their products offer—on the [[:Vendor:LIS vendor|LIS vendor page]].
}}
{{ombox
| type      = notice
| style    = width: 960px;
| text      = '''You can find a listing''' of all LIS vendors — and by extension, the features their products offer — on the [[:LIS vendor|LIS vendor page]].
}}
}}


[[File:Hospital Laboratory.JPG|thumb|300px|Thousands of hospital laboratories like this one benefit from the use of a laboratory information system.]]A '''LIS feature''' is one or more pieces of functionality that appear within a [[laboratory information system]] (LIS).
[[File:Hospital Laboratory.JPG|thumb|300px|Thousands of hospital laboratories like this one benefit from the use of a laboratory information system.]]An '''LIS feature''' is one or more pieces of functionality that appear within a [[laboratory information system]] (LIS).


The LIS has traditionally been utilized in clinical, pathology, and medical research laboratories as well as numerous public health institutions.<ref name="APHLandLIS">{{cite web |url=http://www.aphl.org/aphlprograms/global/initiatives/Documents/LISQuickStartGuide.pdf |title=Quick Start Guide to Laboratory Information System (LIS) Implementation |format=PDF |publisher=Association of Public Health Laboratories |accessdate=27 April 2013}}</ref> Yet as laboratory demands have changed and technological progress has continued, the functions of a LIS have also changed, with the distinction between a LIS and a [[laboratory information management system]] (LIMS) fading as some LIMS vendors have adopted the case-centric information management normally reserved for a LIS.<ref name="starlimsBlogLIS">{{cite web |url=http://blog.starlims.com/2009/07/01/swimming-in-the-clinical-pool-why-lims-are-supplanting-old-school-clinical-lis-applications/ |title=Swimming in the Clinical Pool: Why LIMS are supplanting old-school clinical LIS applications|author=Hice, Randy |publisher=STARLIMS' Laboratory Informatics Blog|date=01 July 2009 |accessdate=27 April 2013}}</ref><ref name="HowDoIFindLII">{{cite web |url=http://files.limstitute.com/share/lbgprofiles/findlims.pdf |format=PDF |title=How Do I Find the Right LIMS — And How Much Will It Cost? |publisher=Laboratory Informatics Institute, Inc |accessdate=27 April 2013}}</ref>.
The LIS has traditionally been utilized in clinical, pathology, and medical research laboratories as well as numerous public health institutions.<ref name="APHLandLIS">{{cite web |url=https://www.aphl.org/aboutAPHL/publications/Documents/GH-2019May-LIS-Guidebook-web.pdf |format=PDF |title=Laboratory Information Systems Project Management: A Guidebook for International Implementations |publisher=Association of Public Health Laboratories |date=May 2019 |accessdate=18 March 2020}}</ref> Yet as laboratory demands have changed and technological progress has continued, the functions of an LIS have also changed, with the distinction between an LIS and a [[laboratory information management system]] (LIMS) fading as some LIMS vendors have adopted the case-centric information management normally reserved for an LIS.<ref name="starlimsBlogLIS">{{cite web |url=http://blog.starlims.com/2009/07/01/swimming-in-the-clinical-pool-why-lims-are-supplanting-old-school-clinical-lis-applications/ |archiveurl=https://web.archive.org/web/20100119015222/http://blog.starlims.com/2009/07/01/swimming-in-the-clinical-pool-why-lims-are-supplanting-old-school-clinical-lis-applications/ |title=Swimming in the Clinical Pool: Why LIMS are supplanting old-school clinical LIS applications|author=Hice, R. |work=Laboratory Informatics Blog |date=01 July 2009 |archivedate=19 January 2010 |accessdate=18 March 2020}}</ref><ref name="HowDoIFindLII">{{cite web |url=http://files.limstitute.com/share/lbgprofiles/findlims.pdf |archiveurl=https://web.archive.org/web/20150626125210/http://files.limstitute.com/share/lbgprofiles/findlims.pdf |format=PDF |title=How Do I Find the Right LIMS — And How Much Will It Cost? |publisher=Laboratory Informatics Institute, Inc |archivedate=26 June 2015 |accessdate=18 March 2020}}</ref>.


Despite the blurring of distinction between a LIS and a LIMS, the LIS generally continues to feature the following<ref name="biohealth">{{cite web |url=http://www.biohealthmatics.com/technologies/his/lis.aspx |title=Laboratory Information Systems |publisher=Biohealthmatics.com |date=10 August 2006 |accessdate=27 April 2013}}</ref>:
Despite the blurring of distinction between an LIS and a LIMS, the LIS generally continues to feature the following<ref name="AStaffCritical15">{{cite web |url=https://www.elitecme.com/resource-center/laboratory/critical-features-of-the-lis/ |title=Critical Features of the LIS |author=ADVANCE Healthcare Network Staff |date=30 July 2015 |accessdate=18 March 2020}}</ref><ref name="FutrellWhat17">{{cite web |url=https://www.mlo-online.com/continuing-education/article/13009013/whats-new-in-todays-lis |title=What's new in today's LIS? |author=Futrell, K. |work=Medical Laboratory Observer |date=23 January 2017 |accessdate=18 March 2020}}</ref>:


* patient management, including admission date, admitting physician, ordering department, specimen type, etc.
*patient management, including admission date, admitting physician, ordering department, specimen type, etc.
* patient data tracking
*specimen management and tracking
* decision support, including comparisons of lab orders with their respective [[ICD-9]] codes
*configurable decision support, including comparisons of lab orders with their respective [[International Statistical Classification of Diseases and Related Health Problems|ICD]] codes
* quality assurance of ordered tests
*quality assurance of ordered tests
* workload and management reporting
*workload and management reporting


Of course, there are LIS features that are difficult to categorize or simply contribute to the whole of the LIS rather than add a function. For example, [[#Multilingual|multilingual support]] allows users to interact with the LIS in more than one language. Some functionality may also overlap several research phases, making it difficult to firmly classify.  
Of course, there are LIS features that are difficult to categorize or simply contribute to the whole of the LIS rather than add a function. For example, [[#Multilingual|multilingual support]] allows users to interact with the LIS in more than one language. Some functionality may also overlap several research phases, making it difficult to firmly classify.  
Line 36: Line 30:
===Sample login and management===
===Sample login and management===


Sample login and management — often referred to as [[Accessioning (medical)|accessioning]] — is an important component of the clinical laboratory, whether it's a molecular pathology lab testing samples for disease indicators or a contract lab running pharmacokinetic and biomarker analysis on samples from a clinical trial.<ref name="MolPath">{{cite book |url=http://books.google.com/books?id=Z2YNhh51SmQC&pg=PA567 |title=Molecular Pathology in Clinical Practice |editor=Leonard, Debra G. B.; Bagg, Adam |publisher=Springer |edition=Illustrated |year=2007 |page=567 |isbn=0387332278 |accessdate=27 April 2013}}</ref><ref name="PPDiClinTrial">{{cite web |url=http://www.ppdi.com/Services/Laboratories/Central-Labs/Operational-Excellence/Specimen-Management.aspx |title=PPD - Clinical Trial Sample Management |publisher=Pharmaceutical Product Development, LLC |accessdate=27 April 2013}}</ref> As such, researchers and technicians who work in these types of labs are unable to complete their tasks without an effective method of managing samples. The process of sample management and accessioning includes, but is not limited to<ref name="LabTechBook">{{cite book |url=http://books.google.com/books?id=qMgAbOHSlsMC&pg=PA8&lpg=PA8 |title=Basic Medical Laboratory Techniques |author=Esteridge, Barbara H.; Reynolds, Anna P.; Walters, Norma J. |publisher=Cengage Learning |edition=4th, revised |year=2000 |page=8 |isbn=0766812065 |accessdate=27 April 2013}}</ref><ref name="MolPath" />:
Sample login and management—often referred to as [[Accessioning (medical)|accessioning]] or specimen management—is an important component of the clinical laboratory, whether it's a molecular pathology lab testing samples for disease indicators or a contract lab running pharmacokinetic and biomarker analysis on samples from a clinical trial.<ref name="MolPath">{{cite book |url=https://books.google.com/books?id=Z2YNhh51SmQC&pg=PA567 |title=Molecular Pathology in Clinical Practice |editor=Leonard, Debra G. B.; Bagg, Adam |publisher=Springer |edition=Illustrated |year=2007 |page=567 |isbn=0387332278 |accessdate=18 March 2020}}</ref><ref name="PPDiClinTrial">{{cite web |url=https://www.ppd.com/our-solutions/ppd-laboratories/central-lab/capabilities/ |title=PPD - Central Lab Capabilities |publisher=Pharmaceutical Product Development, LLC |accessdate=06 January 2022}}</ref> As such, researchers and technicians who work in these types of labs are unable to complete their tasks without an effective method of managing samples. The process of sample management and accessioning includes, but is not limited to<ref name="LabTechBook">{{cite book |url=https://books.google.com/books?id=qMgAbOHSlsMC&pg=PA8&lpg=PA8 |title=Basic Medical Laboratory Techniques |author=Esteridge, B.H.; Reynolds, A.P.; Walters, N.J. |publisher=Cengage Learning |edition=4th, revised |year=2000 |page=8 |isbn=0766812065 |accessdate=18 March 2020}}</ref><ref name="MolPath" />:


* storing related sample information, including demographics, dates, and external links
*storing related sample information, including demographics, dates, and external links
* creating and documenting viewable sample container schemas with name and status
*creating and documenting viewable sample container schemas with name and status
* assigning sample [[LIS_feature#Configurable_roles_and_security|access rights]]
*assigning sample [[LIS_feature#Configurable_roles_and_security|access rights]]
* assigning custom sample ID or accessioning numbers based on a specification
*assigning custom sample ID or accessioning numbers based on a specification
* applying additional processing to the sample before storage and/or analysis
*applying additional processing to the sample before storage and/or analysis


Additional functionality that could potentially fall under this feature:
Additional functionality that could potentially fall under this feature:


* [[LIS_feature#Barcode_support|barcoding]] or RFID tagging of samples
*[[LIS_feature#Barcode_support|barcoding]] or RFID tagging of samples
* defining sample points and series
*defining sample points and series
* creating data associations for samples - such as pedigree for sample/aliquot relationships or relationships based on experiment, etc.
*creating data associations for samples, such as pedigree for sample/aliquot relationships or relationships based on experiment, etc.
* issuing sample receipts
*issuing sample receipts


===Sample tracking===
===Sample tracking===


[[File:Laboratory oven for samples-01.jpg|thumb|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.<ref name="ForensicSamp">{{cite web |url=http://new.americanlaboratory.com/914-Application-Notes/506-Effective-Forensic-Sample-Tracking-and-Handling/ |author=Murthy, Tal; Brian Hewson |title=Effective Forensic Sample Tracking and Handling |publisher=American Laboratory |date=01 September 2010 |accessdate=10 February 2012}}</ref>
[[File:Laboratory oven for samples-01.jpg|thumb|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 actions are being performed on it. Enter the sample tracking feature. Without it, many problems arise. In the [[Forensic laboratory|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.<ref name="ForensicSamp">{{cite web |url=https://www.americanlaboratory.com/914-Application-Notes/506-Effective-Forensic-Sample-Tracking-and-Handling/ |title=Effective Forensic Sample Tracking and Handling |author=Murthy, T.; Hewson, B. |work=American Laboratory |date=01 September 2010 |accessdate=13 March 2020}}</ref>


After sample reception and its initial handling procedures, many LIS can then track sample location as well as [[LIS feature#Chain of custody|chain of custody]]. Location tracking usually involves assigning the sample to a particular freezer, oven, or other location, often down to the granular level of shelf, rack, box, row, and column. The process of tracking a sample has become more streamlined with increasing support of 2-D [[LIS_feature#Barcode and/or RFID support|barcode]] or radio-frequency identification (RFID) technology. While handwritten labels were the norm, now barcode and RDIF support in a LIS can "tie together a vast amount of information, clearly relating each sample to a specific case."<ref name=ForensicSamp /> Other event tracking such as freeze and thaw cycles that a sample undergoes in the laboratory may also be required. As each laboratory's needs for tracking additional data points can vary widely, many modern LIMS and LIS have implemented extensive configurability to compensate for varying environments.<ref name="PP0102">{{cite journal |journal=ProEnvironment/Promediu |year=2008 |volume=1 |issue=2 |pages=19–23 |title=LIMS use in laboratory data management |author=Muntean, Edwarda; Nicoleta Munteanb; Tania Mihăiescua; Radu Mihăiescuc |url=http://journals.usamvcluj.ro/index.php/promediu/article/download/2835/2696 |format=PDF}}</ref>
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 [[LIMS_feature#Barcode_support|barcode]] and radio frequency ID (RFID) technology.<ref name="VaniotisHow18">{{cite web |url=https://blog.labtag.com/rfid-labels-in-the-lab |title=How RFID Labels Can Smarten Up Your Laboratory |author=Vaniotis, G. |work=Labtag Blog |date=19 July 2018 |accessdate=13 March 2020}}</ref> While handwritten labels were the norm, barcode and RFID support in an LIS can "tie together a vast amount of information, clearly relating each sample to a specific case."<ref name="ForensicSamp" /> 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 LIS have implemented extensive configurability to compensate for varying environments.<ref name="PP0102">{{cite journal |title=LIMS use in laboratory data management |journal=ProEnvironment/Promediu |author=Muntean, E.; Munteanb, N.; Mihăiescua, T.; Mihăiescuc, R. |volume=1 |issue=2 |pages=19–23 |year=2008 |url=http://journals.usamvcluj.ro/index.php/promediu/article/view/2835}}</ref>


The functionality of sample tracking strongly ties into the [[LIS feature#Audit trail|audit trail]] and chain of custody features of a LIS.
The functionality of sample tracking strongly ties into the [[LIS feature#Audit trail|audit trail]] and chain of custody features of an LIS.


===Sample and result batching===
===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."<ref name="EPABatch">{{cite web |url=http://www.epa.gov/osw/hazard/testmethods/faq/faqs_qc.htm |title=Batch Sizes And QC Questions |publisher=U.S. EPA |date=27 July 2011 |accessdate=27 April 2013}}</ref> This definition can be applied to many laboratories which handle large quantities of samples for some form of analysis or processing. A LIS that has the ability to check in, link, and track groups of samples across one or multiple facilities is valuable to such laboratories. Additionally, batching the analysis results of multiple samples or groups of samples gives laboratories more flexibility with how they manage their data. Batching also offers the benefit of mimicking the production groups of samples while also capturing quality control data for the entire group.
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."<ref name="EPABatch">{{cite web |url=https://archive.epa.gov/epawaste/hazard/web/html/faqs_qc.html |title=Batch Sizes And QC Questions |publisher=U.S. EPA |date=04 April 2016 |accessdate=13 March 2020}}</ref> 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===
===Task and event scheduling===


Within the context of a LIS, the ability to schedule a task or event is a natural extension of how work was done in a laboratory before the advent of data management systems. Sample processing, data analysis, equipment maintenance, and case management follow-ups are assigned to technicians and other personnel. Outpatient scheduling is another aspect of some clinical atmospheres, better handled with computerized scheduling functionality. While these tasks have in the past been performed without the LIS, a modern data management system can now optimize those tasks and provide additional scheduling functionality to streamline the operation of a lab. Some LISs like [[Elekta AB]]'s IntelliLab include a scheduling calendar for recurring test orders, rules-based orders, and pre-defined selection lists.<ref name="ILAbout">{{cite web |url=http://www.elekta.com/healthcare-professionals/products/elekta-software/clinical-laboratory/laboratory-information-system.html |title=Elekta - Laboratory Information System |publisher=Elekta AB |accessdate=27 April 2013}}</ref> 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.
Within the context of an LIS, the ability to schedule a task or event is a natural extension of how work was done in a laboratory before the advent of data management systems. Sample processing, data analysis, equipment maintenance, and case management follow-ups are assigned to technicians and other personnel. Outpatient scheduling is another aspect of some clinical atmospheres, better handled with computerized scheduling functionality. While these tasks have in the past been performed without the LIS, a modern data management system can now optimize those tasks and provide additional scheduling functionality to streamline the operation of a lab. Some LIS will include, for example, a scheduling calendar for recurring test orders, rules-based orders, and pre-defined selection lists. Additional functionality within this feature group includes the ability to configure automated assignments of experiment requests, establish recurring events, and in most cases, create printable reports.


Examples of tasks and events that can feasibly be scheduled in a LIS include:
Examples of tasks and events that can feasibly be scheduled in an LIS include:


* production of reports
*production of reports
* creation and sending of e-mails and alerts
*creation and sending of e-mails and alerts
* maintenance of equipment
*maintenance of equipment
* assignment of accessioning tasks to technicians
*assignment of accessioning tasks to technicians
* scheduling outpatient visits
*scheduling outpatient visits


===Option for manual result entry===
===Option for manual result entry===


While many LIS vendors tout the ability of their product to automate the entry of sample analysis results into LIS' or other databases, the need for manual data entry of analysis results still exists. This feature is important to laboratories obtaining analysis results from multiple sources, including non-digital paper-based results and instruments that can't be connected to the LIS. Additional functionality associated with this feature includes a customizable spell-check dictionary and the ability to add comments, notes, and narratives to many of the data items in the LIS.
While many LIS vendors tout the ability of their product to automate the entry of sample analysis results into an LIS or other 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 LIS. Additional functionality associated with this feature includes a customizable spell-check dictionary and the ability to add comments, notes, and narratives to many of the data items in the LIS.


===Multiple data viewing methods===
===Multiple data viewing methods===


Hospitals, physicians, and clinical research facilities produce reams of data, and the LIS exists to help organize and distribute that data to the necessary entities. Additionally, even before the existence of the LIS, scientists have had a corresponding need for visually representing that data for clearer analysis and hypothesis creation. Today a LIS can not only collect and analyze data, but it also can represent that data in reports, graphs, gradients, and spreadsheets. Depending on the LIS, more than one way to visually represent the data may exist.  
[[Hospital]]s, physicians, and clinical research facilities produce reams of data, and the LIS exists to help organize and distribute that data to the necessary entities. Additionally, even before the existence of the LIS, scientists have had a corresponding need for visually representing that data for clearer analysis and hypothesis creation. Today an LIS can not only collect and analyze data, but it also can represent that data in reports, graphs, gradients, and spreadsheets. Depending on the LIS, more than one way to visually represent the data may exist.  


This category ties in with the [[#Configurable templates and forms|custom templates and forms]] functionality apparent in some LIS, providing both custom and standardized ways to present information across a healthcare or medical research enterprise.
This category ties in with the [[#Configurable templates and forms|custom templates and forms]] functionality apparent in some LIS, providing both custom and standardized ways to present information across a healthcare or medical research enterprise.
Line 87: Line 81:
===Configurable templates and forms===
===Configurable templates and forms===


Similar to an [[electronic laboratory notebook]] (ELN), a template in a LIS is a functionality item which allows users to increase the productivity and quality of their work by allowing for the creation of a standardized analysis page, patient page, or reporting process across a healthcare or medical research enterprise. These templates allow researchers to maintain more consistent data representation for similar tasks in the LIS and save time by not needing to manually input common data outputs or recreate experiments. Templates and forms typically utilize a wide field library, and the data that is posted to those template fields can also be [[LIS feature#Data normalization|normalized]] to a specific standard. Types of templates that may be created include those for renal and blood pressure analysis, patient demographics, test ordering, and department-level reports.<ref name="AnPathRev">{{cite journal |journal=Advances in Anatomic Pathology |year=March 2012 |volume=19 |issue=2 |pages=81–96 |title=Anatomic Pathology Laboratory Information Systems: A Review |author=Park, Seung Lyung; Pantanowitz, Liron; Sharma, Gaurav; Parwani, Anil Vasdev |doi=10.1097/PAP.0b013e318248b787 |url=http://bpa-pathology.com/uploads/file/docs/Anatomic%20Pathology%20Laboratory%20Information%20Systems%20-%20A%20Review%20-%20SLPark%20et%20all.%20-%20Adv%20Anat%20Pathol%202012.pdf |format=PDF |accessdate=27 April 2013}}</ref>
Similar to an [[electronic laboratory notebook]] (ELN), a template in an LIS is a functionality item which allows users to increase the productivity and quality of their work by allowing for the creation of a standardized analysis page, patient page, or reporting process across a healthcare or medical research enterprise. These templates allow researchers to maintain more consistent data representation for similar tasks in the LIS and save time by not needing to manually input common data outputs or recreate experiments. Templates and forms typically utilize a wide field library, and the data that is posted to those template fields can also be [[LIS feature#Data normalization|normalized]] to a specific standard. Types of templates that may be created include those for renal and blood pressure analysis, patient demographics, test ordering, and department-level reports.<ref name="AnPathRev">{{cite journal |title=Anatomic Pathology Laboratory Information Systems: A Review |journal=Advances in Anatomic Pathology |author=Park, S.L.; Pantanowitz, L.; Sharma, G.; Parwani, A.V. |volume=19 |issue=2 |pages=81–96 |year=March 2012 |doi=10.1097/PAP.0b013e318248b787 |pmid=22313836}}</ref>


===Data and trend analysis===
===Data and trend analysis===


[[File:Analyse residus.png|thumb|260px|left|Some ELNs allow users to analyze experiment data with built-in software tools.]] Sample experimentation and [[Data analysis|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.
[[File:Analyse residus.png|thumb|260px|left|Some LISs allow users to analyze patient test results or clinical research data with built-in software tools.]] For public health centers and pharmaceutical research centers alike, [[data analysis]] plays an important role in their operations, helping clinicians and researchers make better sense of their collected data and reach valuable conclusions about them. While this important phase of laboratory work has often been done externally from the LIS, today's LIS commonly has basic data analysis tools included. Such tools allow raw data to be imported directly to the LIS, which then can store, process, and display it in a shareable form. Vendors may include data analysis functionality by simply including Microsoft Excel compatibility or providing advanced reporting tools, or they may take a more advanced approach by programming and including their own custom data and trend analysis tools in their informatics software. As data analysis has become increasingly vital, such functionality—which has often come in the form of a separate application or analysis device—continues to end up in software like LIS, LIMS, and other [[laboratory informatics]] solutions.<ref name="AE0302">{{cite journal |title=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 |journal=Automated Experimentation |author=Macneil, R. |volume=3 |issue=1 |page=2 |year=2011 |doi=10.1186/1759-4499-3-2 |pmid=21707999 |pmc=PMC3146905}}</ref>
 
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),"<ref name=PLoS0506>{{cite journal|journal=PLoS Computational Biology |year=2009 |volume=5 |issue=6 |title=Managing and Analyzing Next-Generation Sequence Data |author=Richter, Brent G.; David P. Sexton |url=http://www.ploscompbiol.org/article/info%3Adoi%2F10.1371%2Fjournal.pcbi.1000369 |doi=10.1371/journal.pcbi.1000369}}</ref>, today data management options like [[Scilligence Corporation#Scilligence ELN|Scilligence ELN]] are starting to emerge, offering the ability to perform specialized analytical tasks for the researcher.<ref name="ScillELNHome">{{cite web |url=http://www.scilligence.com/web/eln.aspx |title=Scilligence ELN |publisher=Scilligence Corporation |accessdate=07 February 2013}}</ref>
 
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.<ref name=AE0302>{{cite journal|journal=Automated Experimentation |year=2011 |volume=3 |issue=2 |title=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 |author=Macneil, Rory |doi=10.1186/1759-4499-3-2 |url=http://www.aejournal.net/content/3/1/2}}</ref>


===Data and equipment sharing===
===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 [[ELN feature#Document creation and management|document management]] and [[ELN feature#Configurable roles and security|configurable security]].
Aside from data storage and sample registration, a modern LIS's major contribution to the laboratory is aiding in the sharing of test results, reports, and patient data with other entities across the clinical and research enterprise. Rather than pieces of information becoming misplaced or locked away in a physician's office or pathology lab, the LIS makes it easier to test results and increase the efficiency of patient-doctor-lab collaboration in general. However, 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 [[LIS feature#Document creation and management|document management]] and [[LIS feature#Configurable roles and security|configurable security]].


===Data mining===
===Data mining===


Data mining, in the field of computational science, involves "the process of discovering interesting and useful patterns and relationships in large volumes of data" and includes three computational steps: model-learning, model evaluation, and model usage.<ref name="DataMEnBrit">{{cite web |url=http://www.britannica.com/EBchecked/topic/1056150/data-mining |work=Encyclopædia Britannica |title=data mining |publisher=Encyclopædia Britannica, Inc |accessdate=29 April 2013}}</ref> As informatics software allows both research and clinical laboratories to collect and manage increasing quantities of data, a corresponding demand for tools capable of modeling that data is appearing.<ref name="IdealLIS">{{cite journal |journal=Archives of Pathology and Laboratory Medicine |year=05 Decemeber 2012 |volume=preprint |url=http://www.ncbi.nlm.nih.gov/pubmed/23216205 |title=The Ideal Laboratory Information System |author=Sepulveda, Jorge L.; Young, Donald S. |pmid=23216205 |accessdate=29 April 2013}}</ref> For example, public health laboratories may wish to utilize data mining for statistical analysis and surveillance of populations for specific diseases. [[Laboratory information management system|LIMSs]] like [LabWare, Inc.#LabWare LIMS|LabWare LIMS]] and LISs like [[Orchard Software Corporation#Orchard Harvest|Orchard Harvest]] are examples of [[laboratory informatics]] software which incorporate data mining and reporting tools.<ref name="LWDM">{{cite web |url=http://www.labware.com/LWCLWeb.nsf/lp/en0203 |title=LabWare LIMS - Public Health |publisher=LabWare, Inc |accessdate=29 April 2013}}</ref><ref name="OSDM">{{cite web |url=http://www.orchardsoft.com/product/h_dataMining.html |title=Orchard Software - Data Mining |publisher=Orchard Software Corporation |accessdate=29 April 2013}}</ref>
Data mining, in the field of computational science, involves "the process of discovering interesting and useful patterns and relationships in large volumes of data" and includes three computational steps: model-learning, model evaluation, and model usage.<ref name="DataMEnBrit">{{cite web |url=https://www.britannica.com/technology/data-mining |work=Encyclopædia Britannica |title=data mining |publisher=Encyclopædia Britannica, Inc |accessdate=18 March 2020}}</ref> As informatics software allows both research and clinical laboratories to collect and manage increasing quantities of data, a corresponding demand for tools capable of modeling that data is appearing.<ref name="IdealLIS">{{cite journal |title=The Ideal Laboratory Information System |journal=Archives of Pathology and Laboratory Medicine |author=Sepulveda, J.L.; Young, D.S. |volume=137 |issue=8 |pages=1129–40 |year=2013 |doi=10.5858/arpa.2012-0362-RA |pmid=23216205}}</ref> For example, public health laboratories may wish to utilize data mining for statistical analysis and surveillance of populations for specific diseases. LIS like [[Vendor:Technidata SAS|Livextens]] and [[Vendor:Orchard Software Corporation#Orchard Harvest|Orchard Harvest]] are examples of [[laboratory informatics]] software which incorporate data mining and reporting tools.<ref name="TDS_Anal">{{cite web |url=https://www.technidata-web.com/tdanalytics |title=TD Analaytics Livextens |publisher=Technidata SAS |accessdate=18 March 2020}}</ref><ref name="OSDM">{{cite web |url=https://www.orchardsoft.com/solutions/orchard-harvest/ |title=Orchard Harvest |publisher=Orchard Software Corporation |accessdate=06 January 2022}}</ref>


===Customizable fields and/or interface===
===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.
As thorough as some user interface (UI) developers may be in adding relevant fields and interface options for end users, there are at times options that are either omitted or unanticipated. This has traditionally required the end user to contact the vendor and ask if the needed option(s) can be added in the next release. However, many modern LIS vendors have responded instead by adding functionality that gives end users and/or LIS administrators more control over the user interface.  


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


* notebook interface and display
*report interface and display
* chemical drawing methods and display
*patient profile display
* sharing options
*project and experiment display
 
Increasingly, today's vendors tend to refer to their systems as being "configurable" rather than "customizable."<ref name="ASLIMSCustom">{{cite web |url=https://www.autoscribeinformatics.com/resources/blog/lims-customization-vs-configuration |title=LIMS Customization vs Configuration |publisher=Autoscribe Informatics, Inc |date=08 March 2015 |accessdate=13 March 2020}}</ref><ref name="PromiumTheBeni">{{cite web |url=https://www.promium.com/resources/news-articles/the-benefits-of-a-configurable-off-the-shelf-lims-cots/ |title=The Benefits of a configurable COTS LIMS |publisher=Promium, LLC |accessdate=13 March 2020}}</ref> For example, vendors such as Autoscribe Informatics include screen editing and other tools that administrators can user to configure the various screens, data fields, nomenclature, etc. of the solution.<ref name="ASLIMSCustom" />
 
Note in many cases an interface may be customized through the use of templates and forms, and as such, this functionality may be closely tied to the [[#Configurable templates and forms|configurable templates and forms]] functionality.


===Query capability===
===Query capability===


[[File:Query word.jpg|thumb|240px|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 [[Laboratory information management system|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)|SMARTS]] language.<ref name="EspFeats">{{cite web |url=http://chembytes.com/index.php/espresso/features |title=Espresso ELN Key Features |publisher=ChemBytes |accessdate=12 February 2013}}</ref>
As was the case before the advent of databases and electronic data management solutions, today researchers must search through test results, patient notes, and other types of data to better draw conclusions from experiments, diagnose patient illnesses, and plan pharmaceutical research activities. Whereas this used to mean browsing through laboratory notebooks, Excel spreadsheets, or Access databases, now powerful query tools exists within data management tools like the LIS and [[electronic laboratory notebook|ELN]]. A flexible search algorithm can be implemented to allow users to search a dataset by patient name (full or partial) or by any accessioning number. Or more advanced query tools may be implemented to collate and search across multiple datasets.


Query functionality often includes the ability to:
Query functionality often includes the ability to:


* search both transactional data and archived data tables
*search both transactional data and archived data tables
* search multiple databases via an application programming interface (API) or open database connectivity (ODBC) connection  
*search multiple databases via an application programming interface (API) or open database connectivity (ODBC) connection
* filter and sort data
*filter and sort data
* collate queried data for further [[ELN feature#Data and trend analysis|analysis]] and [[ELN feature#Multiple data viewing methods|visualization]]
*collate queried data for further [[LIS feature#Data and trend analysis|analysis]] and [[LIS feature#Multiple data viewing methods|visualization]]
* create ad-hoc queries
*create ''ad hoc'' queries


===Import data===
===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 [[ELN feature#Instrument interfacing and management|instrument interfacing]] allows for even more importation options. Additional [[ELN_feature#Data validation|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 Technologies, Inc.|Agilent]]'s OpenLAB ELN.<ref name="OLELNFeats">{{cite web |url=http://openlabeln.chem.agilent.com/LP=31 |title=OpenLAB ELN's easy-to-use, Web-based interface makes it easy to create and modify experiments |publisher=Agilent Technologies, Inc |accessdate=12 February 2013}}</ref>
Data can originate from numerous places in the laboratory. The ability to import that data into an LIS can be beneficial, especially when an instrument can't be connected or external clients collaborating on a project need to submit relevant data. Of course [[LIS feature#Instrument interfacing and management|instrument interfacing]] allows for even more importation options. Additional [[LIS_feature#Data validation|data validation]] procedures may be applied to the imported data to guarantee information homogeneity. For the LIS, one of the common sources of importing data is a separate [[electronic medical record]] (EMR) or [[electronic health record]] (EHR) system, for collecting patient data and test orders.<ref name="PatelHowLabs19">{{cite web |url=https://www.mlo-online.com/information-technology/ehrs/article/21106468/how-labs-can-benefit-from-lis-to-ehr-connectivity |title=How labs can benefit from LIS to EHR connectivity |author=Patel, S. |work=Medical Laboratory Observer |date=24 September 2019 |accessdate=18 March 2020}}</ref>


===Internal file or data linking===
===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:
[[File:Linking-Open-Data-diagram 2007-09.png|thumb|300px|Many informatics systems allow for internal linking of data; however, entities outside of the system often need to access the data housed within. An LIS is often capable of such external data linking.]]This feature allows research collaborators using an LIS to link together sample batches, reports, protocols, results, and more, providing greater contextual clarity to projects and datasets. Examples include:


* linking a sample batch to an experiment or sample preparation methodology
*linking a sample batch to a test or sample preparation methodology
* linking a test process to a particular experiment
*linking a test process to a particular experiment
* linking a report to a sample batch
*linking a report to a sample batch
* linking a group of experiment results to a raw data file
*linking a group of experiment results to a raw data file
* linking multiple images to a notebook entry
*linking multiple images to a patient record
* linking all experiment results with the correct reporting test methods
*linking all experiment results with the correct reporting test methods


===External file or data linking===
===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:
This feature allows research collaborators using an LIS to link together data and files housed in the database with data, files, and customers outside the LIS's domain. Examples include:


* linking to external research data sources hosted on the Internet<ref name="KalabELNPDF">{{cite web |url=http://www.chem.agilent.com/Library/slidepresentation/Public/Save%20Time%20Capture%20Share%20Data_ELN%20v4%200.pdf |title=Introduction to Kalabie Electronic Lab Notebook - September, 2009 |publisher=Agilent Technologies, Inc |date=September 2009 |format=PDF |page=9 |accessdate=12 February 2013}}</ref>
*linking to an external practice management or electronic medical record (EMR) system using an an [[Health Level 7|HL7]]-compliant interface
* linking external data sources with internal laboratory execution methods<ref name="NugenELNPDF">{{cite web |url=http://www.waters.com/webassets/cms/library/docs/720002133en.pdf |title=NuGenesis ELN - Take Control of Your Laboratory Workflow |publisher=Waters Corporation |date=2012 |format=PDF |page=7 |accessdate=12 February 2013}}</ref>
*linking one public health data source with others to pool demographic and medical information for better disease modeling
* linking an ELN to an external LIMS or other laboratory informatics solution<ref name="BioITNewELNS">{{cite web |url=http://www.bio-itworld.com/2012/02/22/eln-excellence-new-lab-notebooks.html |title=ELN Excellence: The New Lab Notebooks |author=Proffitt, Allison |publisher=BioIT World |date=22 February 2012 |accessdate=12 February 2013}}</ref>
*linking to separate clinical trial laboratory data files within a report


===ELN support or integration===
===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.<ref name="SciCompWorld1">{{cite web|url=http://www.scientific-computing.com/features/feature.php?feature_id=50|author=Elliot, Michael H.|title=The state of the ELN Market |publisher=Scientific Computing World |date=December 2006–January 2007 |accessdate=04 May 2011}}</ref><ref name="SciCompELN">{{cite web|url=http://www.scientificcomputing.com/articles-IN-Informatics-Convergence-Presents-Opportunities-and-Challenges-111111.aspx |author=Elliot, Michael H. |title=Informatics Convergence Presents Opportunities and Challenges |publisher=Scientific Computing |date=October 2011 |accessdate=25 February 2012}}</ref> The result today is some LIMS either include traditional ELN functionality or link physical laboratory notebook references to data in the LIMS.<ref>{{cite web_short|url=http://www.labware.com/LWWeb.nsf/lp/en040109 |title=LabWare Electronic Lab Notebooks |publisher=LabWare, Inc. |accessdate=17 February 2012}}</ref>
The functionality of solutions such as an LIS and LIMS began to blur with that of an [[electronic laboratory notebook|ELN]] in the 2000s, with both types of software incorporating features from the other.<ref name="SciCompWorld1">{{cite web|url=https://www.scientific-computing.com/feature/state-eln-market?feature_id=50 |author=Elliot, M.H. |title=The state of the ELN Market |work=Scientific Computing World |date=December 2006–January 2007 |accessdate=17 March 2020}}</ref><ref name="SciCompELN">{{cite web |url=http://www.scientificcomputing.com/articles-IN-Informatics-Convergence-Presents-Opportunities-and-Challenges-111111.aspx |archiveurl=https://web.archive.org/web/20160417085757/https://www.scientificcomputing.com/articles/2011/11/informatics-convergence-presents-opportunities-and-challenges |author=Elliot, Michael H. |title=Informatics Convergence Presents Opportunities and Challenges |publisher=Scientific Computing |date=October 2011 |archivedate=17 April 2016 |accessdate=17 March 2020}}</ref> More than a decade later, the ELN has become more distinct in purpose and functionality and is typically sold as a stand-alone solution. However, some vendors such as [[Vendor:Genohm SA|Genohm]] have decided to integrate ELN functionality into their solution in order to provide greater flexibility to researchers.<ref name="GenohmHome">{{cite web |url=https://www.genohm.com/ |title=SLIMS: Manage your lab data in one place |publisher=Genohm SA |accessdate=17 March 2020}}</ref> While it has been more common to see this sort of melding in a LIMS, it has been less common in the LIS. Yet some LIS may include some sort of integration or compatibility with an ELN, and thusly this functionality is at least mentioned.


===Export to MS Excel===
===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.<ref name=WilliamsExcel>{{cite web|url=http://www.sfn.org/skins/main/pdf/ShortCourses/2003/sc1_9.pdf |author=Williams, Robert W. |title=Managing Your Lab Data Flux: Getting Beyond Excel |work=The Bioinformatics of Brains: From Genes and Proteins to Behaviors |publisher=Washington, DC: Society for Neuroscience |format=PDF |date=2003 |accessdate=17 February 2012}}</ref> 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.<ref name=PragmaticExcelIntro>{{cite journal|journal=Pharma IT |year=2007 |volume=1 |issue=2 |pages=30–35 |title=A Pragmatic Approach to the Validation of Excel Spreadsheets – Overview |author=Howard, David A.; David Harrison |format=PDF |url=http://www.spreadsheetvalidation.com/pdf/Excel_Spreadsheet_Validation_Overview.pdf}}</ref> 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.
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.<ref name="WilliamsExcel">{{cite web|url=http://www.sfn.org/skins/main/pdf/ShortCourses/2003/sc1_9.pdf |archiveurl=https://web.archive.org/web/20100616100719/http://www.sfn.org/skins/main/pdf/ShortCourses/2003/sc1_9.pdf |format=PDF |author=Williams, R.W. |title=Managing Your Lab Data Flux: Getting Beyond Excel |work=The Bioinformatics of Brains: From Genes and Proteins to Behaviors |publisher=Society for Neuroscience |date=2003 |archivedate=16 June 2010 |accessdate=17 March 2020}}</ref> 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.<ref name="PragmaticExcelIntro">{{cite journal |title=A Pragmatic Approach to the Validation of Excel Spreadsheets – Overview |journal=Pharma IT |author=Howard, D.A.; Harrison, D. |volume=1 |issue=2 |pages=30–35 |year=2007 |url=http://www.spreadsheetvalidation.com/pdf/Excel_Spreadsheet_Validation_Overview.pdf |format=PDF}}</ref> Several decades later, some laboratories continue to use Excel in some fashion, and thus having an LIS capable of handling Excel data remains useful. In particular, selecting and exporting the LIS' data (from test results to quality control charts) into a format such as Excel may further data visualization, insights, and dissemination for some users.<ref name="MSCExcel">{{cite web |url=https://www.msc-lims.com/demo/excelinterface.html |title=Excel Interface |publisher=Mountain States Consulting, LLC |accessdate=17 March 2020}}</ref><ref name="OLCL_LIMSQual">{{cite web |url=https://www.onlims.com/product/quality-control-qaqc/ |title=LIMS Quality Control QA/QC |publisher=Online LIMS Canada Limited |accessdate=17 March 2020}}</ref>


===Raw data management===
===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.
While not described as a feature on most LIS vendor websites, a few indicate their product is capable of managing (import, export, editing, etc.) data in its raw format for future analysis. This raw data is typically implied to be originating from instruments that interface with the LIS, which in itself is not unusual. That raw data may remain housed in instruments, getting transformed into reportable data in the LIS, but presumably most LIS are also capable of housing the raw instrument data as well.<ref name="SSLisa">{{cite web |url=http://www.sigmaplot.co.uk/products/lisa/index.php |title=LISA.lims - The Premier LIMS Solution |publisher=Systat Software, Inc |accessdate=06 January 2022}}</ref> Clinical research labs may also turn to [[scientific data management system]]s to better manage their raw data sources.<ref name="CSolsTheVal19">{{cite web |url=https://www.csolsinc.com/blog/the-value-of-a-scientific-data-management-system-sdms/ |title=The Value of a Scientific Data Management System (SDMS) |author=CSols, Inc |date=25 July 2019 |accessdate=17 March 2020}}</ref>


===Data warehouse===
===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.<ref name="LVAdvantages">{{cite web |url=http://www.labvantage.com/blog/?p=79 |title=Advantages of a Data Warehouse |author=Vannest, Jeff |publisher=LABVANTAGE Solutions, Inc |date=11 February 2011 |accessdate=12 February 2013}}</ref>
an LIS' [[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.<ref name="HarrisWhatIs18">{{cite web |url=https://blog.panoply.io/what-is-a-data-warehouse-a-tutorial-for-beginners |title=What Is A Data Warehouse? A Tutorial For Beginners |author=Harris, J. |work=Panoply Blog |publisher=Panoply Technologies, Inc |date=20 September 2018 |accessdate=17 March 2020}}</ref>


===Project and/or task management===
===Project and/or 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 [[ELN feature#Task and event scheduling|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:
Project and task management within an LIS typically involves the scheduling of tasks to technicians and organizing associated tasks into a more cohesive unit for better tracking and management. While the functionality of [[LIS feature#Task and event scheduling|task and event scheduling]] can also be found in project and task management, many LIS include functionality beyond scheduling that warrants the addition of the project and/or task management feature. This functionality includes:


* job allocation and rescheduling
*job allocation and rescheduling
* instrument workload tracking
*instrument workload tracking
* pending workload verification
*pending workload verification
* project- and experiment-based [[ELN feature#Workflow management|workflow management]]
*project- and experiment-based [[LIS feature#Workflow management|workflow management]]
* sample, batch, and document [[ELN feature#Internal file or data linking|linking]]
*sample, batch, and document [[LIS feature#Internal file or data linking|linking]]
* work template sharing
*work template sharing
* recurring event management
*recurring event management


See also: [[ELN feature#Experiment management|Experiment management]]
See also: [[LIS feature#Patient and case management|Patient and case management]]


===Experiment and/or trial management===
===Test, experiment, and/or trial management===


Experiment and research management functionality is a vital component of most ELNs, and it can cover a wide variety of tasks, from notebook entries to task assignments. From designing an experiment to recording the results in the notebook, It's worth noting this functionality category may seem broad in scope and include other functionality listed on this page, including [[ELN feature#Workflow management|workflow management]] and [[ELN feature#Project and task management|project and task management]]. Its inclusion when reviewing software functionality is primarily to indicate when a vendor or project team indicates the existence of specific experiment management tools in their software.
Specimen or sample test management is a common component of an LIS, while experiment and research trial management functionality is a component of some LIS, often limited to those that are designed to help manage clinical trials. Test, experiment, and trial management can cover a wide variety of tasks, from setting up the design of a clinical trial to specimen task assignments, from ordering tests for patients to planning trial experiments. '''Note''': this may also be referred to as "order management" with some vendors.
 
It's worth noting this functionality category may seem broad in scope and include other functionality listed on this page, including [[LIS feature#Workflow management|workflow management]] and [[LIS feature#Project and task management|project and task management]]. Its inclusion when reviewing software functionality is primarily to indicate when a vendor or project team indicates the existence of specific test, experiment, or trial management tools in their software.


===Inventory management===
===Inventory management===


[[File:ELISA pic.jpg|thumb|240px|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 [[Reagent|reagents]] to glassware, from [[Radiopharmacology|radiopharmaceuticals]] to [[Laboratory bath|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:
Laboratories use a wide array of inventory and equipment, from [[Reagent|reagents]] and [[Radiopharmacology|radiopharmaceuticals]] to glassware and [[Laboratory bath|laboratory baths]]. With that comes the need to know how much/many and the frequency of use. For this, LIS solutions include some sort of inventory management functionality.


* register the origin and demographics of incoming materials
*register origin, demographics of incoming materials
* track used and in-use items via [[ELN feature#Barcode support|barcodes]]
*track used and in-use items via barcodes or RFID
* track inventory reduction based on usage and shipping out of the lab
*track inventory reduction based on usage and shipping out of the lab
* create alerts for when items reach a certain stock level
*create alerts for when items reach a certain stock level
* calculate inventory cost and fluctuation
*calculate inventory cost and fluctuation
* manage transportation and routing
*manage transportation and routing
* manual incrementing/decrementing of items
*manual incrementing/decrementing of item counts
* track location and usage of laboratory equipment
*track location and usage of laboratory equipment
* track location and usage of reagents
*assign storage locations
* assign storage locations
*track forensic evidence
* track forensic evidence
 
It should be noted electronic equipment may also be considered inventory, and thus there is likely some functionality crossover with [[ELN feature#Instrument interfacing and management|instrument management]] features.


===Document and/or image management===
===Document and/or image 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:
[[File:Process and data modeling.svg|thumb|320px|Standard operating procedures, workflow diagrams, and business models can all be handled effectively with document management functionality.]]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 an LIS 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:


* upload and index documents
*upload and index documents of most any file type and size
* add images and photos inline to a notebook entry
*enforce [[LIS feature#Version control|version control]]
* enforce [[ELN feature#Version control|version control]]
*provide full text search
* provide full text searches
*convert and/or export to PDF or other relevant formats
* export to PDF, XML, or other relevant formats
*add documents as attachments to other analyses, files, projects, etc. in the system
* add documents as attachments


===Patient and case management===
===Patient and case management===


The [[laboratory information system]] (LIS) has played an important role in the case management tasks of patient-centric and clinical laboratories. However, some LIMS have gained case management functionality, effectively blurring the lines between LIS and LIMS.<ref>{{cite web|url=http://blog.starlims.com/2009/07/01/swimming-in-the-clinical-pool-why-lims-are-supplanting-old-school-clinical-lis-applications/|title=Swimming in the Clinical Pool: Why LIMS are supplanting old-school clinical LIS applications|author=Hice, Randy |publisher=STARLIMS' Laboratory Informatics Blog|date=01 July 2009|accessdate=09 May 2011}}</ref>. 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:
The LIS has played an important role in the case management tasks of patient-centric and clinical laboratories. LIS products have included patient or case management tools suitable for the clinical, public health, and veterinary industries, as well as the fields of law enforcement and forensic science. Functionality seen in the patient and case management feature includes:


* case accessioning and assignment
*case accessioning and assignment
* disease tracking
*disease tracking
* trend analysis
*trend analysis
* clinical history follow-up
*clinical history follow-up
* out-of-range result [[LIMS feature#Alarms and/or alerts|alerts]]
*out-of-range result [[LIS feature#Alarms and/or alerts|alerts]]
* document and result association
*document and result association
* evidence control
*evidence control
* study management
*study management
*collating of patient data across multiple spectrum


===Workflow management===
===Workflow management===


[[File:Workflow IA.png|left|thumb|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.<ref name="WfMC1">{{cite web |url=http://www.wfmc.org/standards/docs/TC-1011_term_glossary_v3.pdf |title=Workflow Management Coalition Terminology & Glossary |publisher=Workflow Management Coalition |pages=9 |format=PDF |date=February 1999 |accessdate=20 February 2012}}</ref> However, in the 2000s vendors began incorporating workflow management functionality into their laboratory informatics software, reducing customization headaches in the process.<ref name="SciCompWF">{{cite web |url=http://www.scientificcomputing.com/using-workflows-in-lims-to-reduce.aspx |title=Using Workflows in LIMS to Reduce Customization |author=Maxwell, Glen |publisher=Scientific Computing and Instrumentation |date=1 November 2003 |accessdate=20 February 2012}}</ref>  
[[File:Workflow IA.png|left|thumb|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 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.<ref name="WfMC1">{{cite web |url=http://www.wfmc.org/standards/docs/TC-1011_term_glossary_v3.pdf |archiveurl=https://web.archive.org/web/20150314125903/http://www.wfmc.org/standards/docs/TC-1011_term_glossary_v3.pdf |format=PDF |title=Workflow Management Coalition Terminology & Glossary |publisher=Workflow Management Coalition |pages=9 |date=February 1999 |archivedate=14 March 2015 |accessdate=06 January 2022}}</ref> However, in the late 2000s [[laboratory informatics]] vendors began incorporating workflow management functionality into their software, reducing the headaches that customization of a solution often brought.<ref name="SciCompWF">{{cite web |url=http://www.scientificcomputing.com/using-workflows-in-lims-to-reduce.aspx |archiveurl=https://web.archive.org/web/20090807034051/http://www.scientificcomputing.com/using-workflows-in-lims-to-reduce.aspx |title=Using Workflows in LIMS to Reduce Customization |author=Maxwell, G. |work=Scientific Computing |date=1 November 2003 |archivedate=07 August 2009 |accessdate=17 March 2020}}</ref>  


Modern commercial and open-source ELN solutions often feature workflow management functionality, including<ref name="AITELNWorkflows">{{cite web |url=http://aitbioscience.com/wp-content/uploads/Using-Electronic-Lab-Notebook-Functionality-for-Validating-Electronic-Lab-Notebook-Workflows.pdf |title=Using Electronic Lab Notebook Functionality for Validating Electronic Lab Notebook Workflows |author=Beato, Brian D.; Grever, Timothy P. ; Branstrator, Laurel E. |publisher=AIT Bioscience |format=PDF |accessdate=12 February 2013}}</ref><ref name="LCAddOn">{{cite web |url=http://labcollector.com/index.php/eln-add-on-newhtml |title=LabCollector's Electronic Lab Notebook (ELN) |publisher=AgileBio |accessdate=12 February 2013}}</ref><ref name="KalabELNPDF" /><ref name="BioITNewELNS" />:
Modern commercial and open-source LIS solutions recognize clinical laboratory workflow often has its own share of requirements, requiring specific workflow management functionality, including<ref name="WFLIS">{{cite web |url=http://www.labcompare.com/10-Featured-Articles/19389-Harnessing-Laboratory-Information-Systems-to-Support-Increased-Capacity-and-Staff-Productivity/ |archiveurl=https://web.archive.org/web/20150921215023/http://www.labcompare.com/10-Featured-Articles/19389-Harnessing-Laboratory-Information-Systems-to-Support-Increased-Capacity-and-Staff-Productivity/ |title=Harnessing Laboratory Information Systems to Support Increased Capacity and Staff Productivity |author=Feist, K. |work=LabCompare |date=22 July 2011 |archivedate=21 September 2015 |accessdate=18 March 2020}}</ref>:
{{flowlist |
*managing the request cycle within a laboratory
*organizing and executing diagnostic testing
*managing specific chemistry- and biology-related procedures
*defining activity attributes
*managing automation tools to better workflows
*re-routing samples based on changes to a process
*dynamically modifying workflow in case of future changes
*receiving notification of changes to the workflow
}}


* managing the request cycle within a laboratory
===Specification management===
* 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


===Specification management===
[[Specification (technical standard)|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 International|ASTM]] offers standards and specs for LIS<ref name="ASTM_LIMS">{{cite web |url=https://www.astm.org/Standards/E1578.htm |title=ASTM E1578 - 18 Standard Guide for Laboratory Informatics |publisher=ASTM International |accessdate=17 March 2020}}</ref>, so too do LIS users have standards and specs for their laboratory.


[[Specification (technical standard)|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 International|ASTM]] offers standards and specs for LIMS<ref name=ASTM_LIMS>{{cite web |url=http://www.astm.org/Standards/E1578.htm |title=ASTM E1578 - 06 Standard Guide for Laboratory Information Management Systems (LIMS) |publisher=ASTM International |accessdate=22 February 2012}}</ref>, so too do LIMS users have standards and specs for their laboratory. With spec management in place within the LIMS, laboratories can then:
Spec management has primarily been seen in a manufacturing execution system (MES) or a [[laboratory information management system]] (LIMS), but occasionally an LIS may appear which includes such functionality. With spec management in place, laboratories can then:


* enforce standard operating procedures and business rules
*enforce standard operating procedures and business rules
* create specs down to a project or sample level
*create specs down to a project or sample level
* validate recipes and procedures
*validate recipes and procedures
* accept or reject sample batches
*accept or reject sample batches
* document internal and external spec history
*document internal and external spec history


Note that some of the functionality of spec management may cross over into the realm of [[LIMS feature#QA/QC functions|quality control]] and [[LIMS feature#Data validation|data validation]].
Note some of the functionality of spec management may cross over into the realm of [[LIS feature#QA/QC functions|quality control]] and [[LIS feature#Data validation|data validation]].


===Customer, supplier, and physician management===
===Customer, supplier, and physician management===


Unless a laboratory is conducting internalized independent research, in most cases it will do business with external entities such as contract labs, 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.
Unless a laboratory is conducting internalized independent research, in most cases it will do business with external entities such as contract labs, physician offices, equipment providers, and reagent suppliers. In some cases, even internal employees may be considered a customer, necessitating documentation of who is using the system and in what ways. For a veterinary lab, the customer may be the animal and handler. For a forensic lab the customer may be more complex: internal staff, university staff, police departments, and maintainers of nationwide crime databases may all at some point act as customers. In these cases, documenting these various points of contact and linking them to tests, equipment, and patients becomes vital. Managing demographics, complaints, correspondence, and history are all feasible with customer, supplier, and physician management functionality. This process is often made simpler through the use of a more context-neutral entity creation system, which allows for more flexible management of contacts.


This feature may also be referred to as contact management, an address book module, or a customer service module.
This feature may also be referred to as contact management, an address book module, or a customer service module.
Line 261: Line 257:
===Billing and revenue management===
===Billing and revenue 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:
While the finances of a laboratory are important, they've typically been handled separately as a business process. However, some LIS include additional functionality to make handling financial transactions and documentation of all sorts possible within the LIS. In theory, such functionality brings the possibility of keeping more of a laboratory's data centrally located and queryable. This feature may include<ref name="ILAbout">{{cite web |url=http://www.elekta.com/healthcare-professionals/products/elekta-software/clinical-laboratory/laboratory-information-system.html |archiveurl=https://web.archive.org/web/20120422205830/http://www.elekta.com/healthcare-professionals/products/elekta-software/clinical-laboratory/laboratory-information-system.html |title=Elekta - Laboratory Information System |publisher=Elekta AB |archivedate=22 April 2012 |accessdate=18 March 2020}}</ref><ref name="McKessHori">{{cite web |url=http://www.mckesson.com/en_us/McKesson.com/For%2BHealthcare%2BProviders/Hospitals/Laboratory%2BSolutions/Horizon%2BLab%2BFinancials.html |archiveurl=https://web.archive.org/web/20130521025202/http://www.mckesson.com/en_us/McKesson.com/For+Healthcare+Providers/Hospitals/Laboratory+Solutions/Horizon+Lab+Financials.html |title=Horizon Lab Financials |publisher=McKesson Corporation |archivedate=21 May 2013 |accessdate=18 March 2020}}</ref>:


* payment processing
*payment processing
* expense reporting
*expense reporting
* price quotes
*price quotes
* revenue management
*revenue cycle management
* workload tracking of billable hours
*workload tracking of billable hours
* bill of materials
*bill of materials
* grant management
*sales team and client management
*profitability analysis
*medical necessity checks


</div>
</div>
Line 281: Line 279:
===Regulatory compliance===
===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.<ref name="LTELNCompPDF">{{cite web |url=http://www.vialis.ch/fileadmin/files/imgs/pdf/Newsletter/q2-09/ELN_LAB.pdf |title=ELN Reduces Regulatory Compliance Costs |publisher=Labtronics Inc |date=January 2005 |format=PDF |accessdate=12 February 2013}}</ref><ref name="KMHowELN">{{cite web |url=http://www.kinematik.com/blog/bid/207452/How-an-ELN-Mitigates-the-Risks-Associated-with-Regulatory-Compliance |title=How an ELN Mitigates the Risks Associated with Regulatory Compliance |author=Price, Michael |publisher=KineMatik Ltd |date=17 August 2012 |accessdate=12 February 2013}}</ref><ref name="BioITNewELNS" /> Other compliance-based codes, standards, and regulations include:
The topic of whether or not an LIS meets regulatory compliance is often a complex one. While Title [[21 CFR Part 11]] has arguably had the largest influence on an electronic data management system's compliance, other influential standards have shaped the way laboratory informatics systems handle and store data. Other compliance-based codes, standards, and regulations include:


* [[ASTM International|ASTM]]  
*[[ASTM International|ASTM]] standards
* [[The American Society of Crime Laboratory Directors/Laboratory Accreditation Board|ASCLD/LAB]]  
*[[The American Society of Crime Laboratory Directors/Laboratory Accreditation Board|ASCLD/LAB]] crime lab accreditation
* Classified data
*Freedom of Information Act
* Freedom of information legislation (various)
*[[Good Automated Laboratory Practices|GALP]] and [[Good Automated Manufacturing Practice|GAMP]]
* [[Good Automated Laboratory Practices|GALP]] and [[Good Automated Manufacturing Practice|GAMP]]  
*[[Health Insurance Portability and Accountability Act|HIPAA]]
* [[Health Insurance Portability and Accountability Act|HIPAA]]
*[[Health Level 7]]
* [[Health Level 7]]
*[[International Statistical Classification of Diseases and Related Health Problems|ICD]]
* [[ISO/IEC 17025]]
*[[ISO/IEC 17025]]
* [[ISO 9000|ISO 9000/9001]]
*[[ISO 9000|ISO 9000/9001]]
* [[ISO/TS 16949]]
*[[ISO/TS 16949]]
* [[ODBC]]
*[[ODBC]]
* [[The NELAC Institute|TNI]] and [[The NELAC Institute#National Environmental Laboratory Accreditation Program|NELAP]]  
*[[The NELAC Institute|TNI]] and [[The NELAC Institute#National Environmental Laboratory Accreditation Program|NELAP]] enviromnental lab accreditation
* Title [[40 CFR Part 3]]
*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.
With so many codes, standards, and regulations, it can be challenging for potential LIS 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 LIS 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.


===QA/QC functions===
===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.<ref name="ChemBioArtQA">{{cite web |url=http://chembionews.cambridgesoft.com/Articles/Default.aspx?articleID=740 |archiveurl=http://web.archive.org/web/20110722165349/http://chembionews.cambridgesoft.com/Articles/Default.aspx?articleID=740 |title=Why doesn’t a Traditional Electronic Laboratory Notebook work in a QA/QC lab? - ELN Requirements for Quality Assurance and Quality Control |author=Bolton, Steve |publisher=CambridgeSoft Corporation |archivedate=22 July 2011 |accessdate=12 February 2013}}</ref><ref name="WhyDoesn'tArt">{{cite journal |url=http://connection.ebscohost.com/c/articles/18473960/why-doesnt-traditional-electronic-laboratory-notebook-work-qa-qc-lab |title=Why Doesn't a Traditional Electronic Laboratory Notebook Work in a QA/QC Lab? |author=Pavlis, Robert |journal=Scientific Computing & Instrumentation |volume=22 |issue=10 |year=September 2005 |page=31}}</ref> Some vendors have created ELN modules or separate software solutions (like [[laboratory execution system]]s [LES]) to address the specific needs of QA/QC labs, while other vendors have simply included an ELN add-on to their LIMS.<ref name="AccelLES">{{cite web |url=http://accelrys.com/products/process-management-and-compliance/lab-execution-system/index.html |title=Accelrys Lab Execution System |publisher=Accelrys, Inc |accessdate=12 February 2013}}</ref><ref name="AgaramQA">{{cite web |url=http://www.agaram.co.in/n/index.php/products/logilab.html |title=Agaram - Logilab |publisher=Agaram Instruments (P) Ltd |accessdate=12 February 2013}}</ref><ref name="LIMSELNIntLab">{{cite web |url=http://theintegratedlab.com/2010/03/lims-and-elns-again-and-again/ |title=LIMS and ELNs again, and again… |author=Trigg, John |publisher=John Trigg |date=29 March 2010 |accessdate=12 February 2013}}</ref><ref name="QAELNArtMetrick">{{cite web |url=http://www.thefreelibrary.com/QA%2FQC%3A+ELNs+have+come+a+long+way%3A+realizing+the+full+potential+of...-a0272245303 |title=QA/QC: ELNs have come a long way: realizing the full potential of today's electronic laboratory notebooks |author=Metrick, Gloria |publisher=Scientific Computing |date=01 January 2011 |accessdate=12 February 2013}}</ref>
The quality management functions of an LIS allow users to maintain a level of necessary quality across many of the functions in a laboratory. Some of the activities quality assurance / quality control functionality allows for includes<ref name="RandomQAPaper">{{cite journal |title=The development and testing of a laboratory information system-driven tool for pre-sign-out quality assurance of random surgical pathology reports |journal=American Journal of Clinical Pathology |author=Owens, S.R.; Dhir, R.; Yousem, S.A. et al. |volume=133 |issue=6 |page=836–41 |year=June 2010 |doi=10.1309/AJCPLN9DU9LNXSXA |pmid=20472840}}</ref><ref name="NLQC">{{cite web |url=http://www.netlims.com/lis_software_autoquality.asp |archiveurl=https://web.archive.org/web/20111220065137/http://www.netlims.com/lis_software_autoquality.asp |title=Netlims - AutoQuality |publisher=NeTLIMS NJ, LLC |archivedate=20 December 2011 |accessdate=18 March 2020}}</ref><ref name="Clin1">{{cite web |url=https://clin1mobile.net/quality-control |title=CLIN1 Laboratory Quality Control Software |publisher=Clin1, LLC |accessdate=18 March 2020}}</ref>:
 
*force random review of cases by second pathologist before case verification
*receive and process QC results from laboratory analyzers
*create user rules
*set up custom alerts and flags for out-of-range results
*observe standard deviations in outcome research
*review and sign off on data electronically
*delta checking


===Performance evaluation===
===Performance evaluation===


As [[ELN feature#Document creation and management|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.  
As prevalent as [[LIMS feature#Document creation and management|document management]] has become in clinical and research laboratories, it makes sense that the LIS 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 an LIS makes this possible.  


That functionality typically includes the ability to maintain training records and history, and also to link that training to a technique or piece of equipment. Afterwards, the staff member, vendor, etc. can be marked as competent or certified in the equipment, knowledge, or process. Periodical assessment of the training and its practical effectiveness can later be performed. Productivity of an entity or process can also be gauged over a certain date range based on [[ELN feature#Work-related time tracking|tracked time]], pre-determined milestones, or some other criteria.
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 [[LIMS feature#Work-related time tracking|tracked time]], pre-determined milestones, or some other criteria.


===Audit trail===
===Audit trail===


[[File:Syvalidate screen.jpg|thumb|left|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 trail|audit trails]]<ref>{{cite web |url=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 |title=Electronic Code of Federal Regulations - Title 21: Food and Drugs - Part 11: Electronic Records; Electronic Signatures |publisher=U.S. Government Printing Office |accessdate=02 March 2012}}</ref>, 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.  
[[File:Syvalidate screen.jpg|thumb|left|280px|Whether validating an instrument's data or an entire LIS, maintaining an audit trail is an important part of [[21 CFR Part 11]] compliance.]] As laws and regulations like Title [[21 CFR Part 11]] mandate "computer systems (including hardware and software), controls, and attendant documentation" utilize electronic signatures and [[Audit trail|audit trails]]<ref name="FDA21CFR11">{{cite web |url=https://www.accessdata.fda.gov/scripts/cdrh/cfdocs/cfcfr/CFRSearch.cfm?CFRPart=11 |title=Title 21: Food and Drugs - Chapter 1: Food and Drug Administration, Department of Health and Human Services, Subchapter A: General - Part 11: Electronic Records; Electronic Signatures |publisher=U.S. Food and Drug Administration |accessdate=18 March 2020}}</ref>, LIS developers must put serious thought into how their software handles audit trail functionality. The audit trail—documentation of the sequence of activities that have affected an action—must be thorough and seamlessly integrated into the software, and it has become a mandatory feature for labs operating in regulated environments.<ref name="McDowallHowCan16">{{cite web |url=https://rx-360.org/wp-content/uploads/2018/08/How-Can-LIMS-Help-Ensure-Data-Integrity-by-R.D.-McDowall-2016.pdf |format=PDF |title=How Can LIMS Help Ensure Data Integrity? |author=McDowall, R.D. |work=LC-GC Europe |date=June 2016 |accessdate=18 March 2020}}</ref>
 


Information recorded in the audit trail typically includes:
Information recorded in the audit trail typically includes:
{{flowlist |
*operator code
*time stamp
*location
*case number
*accessioning number
*transaction type
*amount and quantity prior to change
*user notes (e.g., reason for change)
*in some cases, data in temporary memory<ref name="LVData19">{{cite web |url=https://www.labvantage.com/data-integrity-is-here-what-does-it-mean-for-cmos/ |title=Data Integrity is Here. What Does it Mean for CMOs? |author=LabVantage Solutions |work=LabVantage Blog |date=14 September 2019 |accessdate=18 March 2020}}</ref>
}}
<br />


* operator code
===Chain of custody===
* time stamp
* location
* case number
* transaction type
* amount and quantity prior to change
* user notes


<br />
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 laboratory|forensic labs]], which depend on continuous accountability of their evidence collection, retention, and disposal procedures.<ref name="JonesBuild09">{{cite book |url=https://books.google.com/books?id=F5IU7XXKwCQC |title=Building a Digital Forensic Laboratory: Establishing and Managing a Successful Facility |chapter=Chapter 1: An Introduction to Digital Forensics |author=Jones, A.; Valli, C. |page=11 |year=2009 |publisher=Butterworth-Heinemann |isbn=9781856175104}}</ref> At its core, the COC strives to answer at least these five questions<ref>{{Cite journal |last=Tomlinson |first=J. J. |last2=Elliott-Smith |first2=W. |last3=Radosta |first3=T. |date=2006 |title=Laboratory Information Management System Chain of Custody: Reliability and Security |url=http://www.hindawi.com/journals/jamc/2006/074907/abs/ |journal=Journal of Automated Methods and Management in Chemistry |language=en |volume=2006 |pages=1–4 |doi=10.1155/JAMMC/2006/74907 |issn=1463-9246 |pmc=PMC1903459 |pmid=17671623}}</ref>:


===Chain of custody===
#Where is my sample or specimen now?
#Who possess my sample or specimen now?
#When did that individual take possession of my sample or specimen?
#Where has my sample or specimen been?
#Who has been in possession of my sample or specimen?


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.<ref>{{cite book |title=Building a Digital Forensic Laboratory: Establishing and Managing a Successful Facility |chapter=Chapter 1: An Introduction to Digital Forensics |author=Jones, Andrew; Craig Valli |url=http://books.google.com/books?id=F5IU7XXKwCQC |pages=11 |year=2008 |publisher=Butterworth-Heinemann |isbn=1856175103}}</ref> 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. [[ELN feature#Barcode support|Barcodes]], [[ELN feature#Inventory management|inventory management]], and [[ELN feature#Configurable roles and security|configurable security roles]] all play an important part in maintaining chain of custody.
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. [[LIS feature#Barcode support|Barcodes]], [[LIS feature#Inventory management|inventory management]], and [[LIS feature#Configurable roles and security|configurable security roles]] all play an important part in maintaining chain of custody.


===Configurable roles and security===
===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.  
Many roles exist within the clinical and research setting, each with its own set of responsibilities. And just as the role an individual plays within the laboratory may change, so may the responsibilities associated with each role. This sort of change necessitates a flexible and configurable security system, one that allows for the placement of individual LIS users into standardized security roles which provide role-specific access to certain functionality. Additionally, as responsibilities change within roles, that same flexible configuration is necessary for assigning or restricting access to specific functionality for each existing or newly created role.  


Of course, roles aren't always assigned on an individual level. Often large groups of individuals may need to be assigned to roles, necessitating group assignments for security purposes. For example, a group of laboratory trainees may only be given read-only access to the [[ELN feature#Experiment management|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.
Of course, roles aren't always assigned on an individual level. Often large groups of individuals may need to be assigned to roles, necessitating group assignments for security purposes. For example, a group of hospital laboratory trainees may not be given access to the [[LIS feature#Inventory management|inventory management]] functionality of the system through a custom "Trainees" group role, while the head of the lab may be given the "Administrator" role, which allows that individual to access a much broader spectrum of the LIS's functionality.


===Data normalization===
===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.  
For the purposes of describing LIS functionality, "data normalization" specifically refers to the process of ensuring data that moves into the LIS is formatted in a standardized way, matching the format of existing LIMS 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 [[ELN feature#Data validation|data validation]] efforts later on.
Here's an example to better explain this issue. When an LIS 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 LIS can normalize the incoming data to match the standard already set for existing LIS temperature data. This ensures consistency within the LIS 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.
''Note'': Some LIS developers may include data normalization functionality within what they may refer to as "data validation" functionality. The line between these two may be blurred or not exist at all.


===Data validation===
===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.<ref name="SIRFERQA">{{cite web |url=http://sirfer.utah.edu/qaqc.pdf |title=Quality Assurance - Data Management |publisher=Stable Isotope Ratio Facility for Environmental Research (SIRFER) at the University of Utah |accessdate=07 May 2012 |format=PDF}}</ref><ref name="CompMinIndBook">{{cite book |title=Application of Computers and Operations Research in the Mineral Industry |chapter=Chapter 10: Efficient utilization of LIMS data and integration with mining process management systems |author=Hitchcock, Noel |editor=Dessureault, Sean D.; Rajive Ganguli; Vladislav Kecojevic; Jami Girard Dwyer |url=http://www.crcnetbase.com/doi/abs/10.1201/9781439833407.ch10 |pages=85–88 |year=2005 |publisher=Taylor & Francis |isbn=9780415374491 |doi=10.1201/9781439833407.ch10}}</ref>
[[File:Scheme reconciliation.jpg|thumb|300px|In an LIS, data and data models can be forced through a validation process to remove errors and reconcile that those data and models.]]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.<ref name="SIRFERQual">{{cite web |url=http://sirfer.utah.edu/qaqc.pdf |archiveurl=https://web.archive.org/web/20111117174948/http://sirfer.utah.edu/qaqc.pdf |format=PDF |title=Quality Assurance - Data Management |publisher=Stable Isotope Ratio Facility for Environmental Research (SIRFER) at the University of Utah |archivedate=17 November 2011 |accessdate=18 March 2020}}</ref><ref name="HitchcockEffic05">{{cite book |title=Application of Computers and Operations Research in the Mineral Industry |chapter=Chapter 10: Efficient utilization of LIMS data and integration with mining process management systems |author=Hitchcock, N. |editor=Dessureault, S.D.; Ganguli, R.; Kecojevic, V.; Dwyer, J.G. |pages=85–88 |year=2005 |publisher=Taylor & Francis |isbn=9780415374491}}</ref>


''Note'': This functionality shouldn't be confused with the process of validating the application itself, which is an entirely different process partially falling under [[ELN feature#Regulatory compliance|regulatory compliance]] and involves the process of ensuring "the software is performing in a manner for which it was designed."<ref name="QAJournValid">{{cite journal |journal=Quality Assurance |year=2001 |volume=9 |issue=3–4 |pages=217–224 |title=Required steps for the validation of a Laboratory Information Management System |author=Turner, Elizabeth; Jojean Bolton |pmid=12553085 |url=http://www.ncbi.nlm.nih.gov/pubmed/12553085}}</ref>
''Note'': This functionality shouldn't be confused with the process of validating the application itself, which is an entirely different process partially falling under [[LIS feature#Regulatory compliance|regulatory compliance]] and involves the process of ensuring "the software is performing in a manner for which it was designed."<ref name="TurnerReq01">{{cite journal |title=Required steps for the validation of a Laboratory Information Management System |journal=Quality Assurance |author=Turner, E.; Bolton, J. |volume=9 |issue=3–4 |pages=217–224 |year=2001 |pmid=12553085 |doi=10.1080/713844028}}</ref>


===Data encryption===
===Data encryption===


[[File:Public key encryption.svg|thumb|220px|In an ELN files can be encrypted and then read by only someone who has the specific key or rights to do so.]]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.  
The existence of this functionality in LIS software generally indicates the LIS 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 computing|cloud-based]] software offerings managing data in transit and at rest.<ref name="Al-IssaEhealth19">{{cite journal |title=eHealth Cloud Security Challenges: A Survey |journal=Journal of Healthcare Engineering |author=Al-Issa, Y.; Ottom, M.A.; Tamrawi, A. |volume=2019 |at=7516035 |year=2019 |doi=10.1155/2019/7516035 |pmid=31565209 |pmc=PMC6745146}}</ref> As a wide variety of encryption technologies exist, it's generally a good idea to consult with the developers of an LIS to determine the strengths and weaknesses of their employed encryption methods.


===Version control===
===Version control===


Version control is a form of safeguard which helps preserve data integrity and thus ties in with the topic of [[ELN feature#Regulatory compliance|regulatory compliance]]. This is typically done by creating a modifiable new version of a piece of information rather than allowing the original to be modified. Such versioning may be applied to a wide variety of digital information housed in the 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 [[ELN feature#Audit trail|audit trails]] and [[ELN feature#Chain of custody|chains of custody]].
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 LIS, including test methods, 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 [[LIS feature#Audit trail|audit trails]] and [[LIS feature#Chain of custody|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.
Some LIS vendors may choose to 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.<ref name="MonkeyTheVal17">{{cite web |url=https://corengen.wordpress.com/2017/01/23/the-value-of-a-control-file-when-writing-data-files/ |title=The value of a control file when writing data files |author=Monkey, S. |work=ShortStories: Tales from software development |date=23 January 2017 |accessdate=18 March 2020}}</ref> 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 LIS buyers may need to inquire with developers to determine what type of versioning scheme is used in the vendor's software.


===Automatic data backup===
===Automatic data backup===


The existence of this piece of functionality in an ELN usually means information contained in one or more associated databases or [[ELN feature#Data warehouse|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 [[ELN feature#Administrator management|administrative module]] of the ELN.
The functionality of automatic data backup in an LIS usually means information contained in one or more associated databases or [[LIS feature#Data warehouse|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 [[LIS feature#Administrator management|administrative module]] of the LIS. As cloud-based LIS have slowly increased in number, scheduled cloud-to-cloud data backups of software data are becoming more practical.<ref name="TsyktorHowTo17">{{cite web |url=https://www.apriorit.com/dev-blog/492-build-data-backup-service-saas |title=How to Build a Data Backup Service for SaaS |author=Tsyktor, V. |work=Apriorit Dev Blog |date=30 December 2017 |accessdate=18 March 2020}}</ref>


===Environmental monitoring===
===Environmental monitoring===


Some LIMS like [[Core Informatics, LLC#Core LIMS|Core LIMS]] and [[Oracle Corporation#Oracle Health Sciences LabPas|Oracle Health Sciences LabPas]] allow users to monitor the environmental conditions of not only sample storage containers but also the entire laboratory itself.<ref>{{cite web |url=http://www.corelims.com/features.htm |title=Core LIMS Features & Components |publisher=[[Core Informatics, LLC]] |accessdate=07 May 2012}}</ref><ref>{{cite web |url=http://www.oracle.com/us/industries/life-sciences/health-sciences-labpas-ds-396097.pdf |title=Oracle Health Sciences LabPas |publisher=[[Oracle Corporation]] |date=2011 |accessdate=07 May 2012 |format=PDF}}</ref> 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 [[Novatek International#NOVA-LIMS|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.<ref>{{cite web |url=http://ntint.com/prod-envmon.shtml |title=Environmental Monitoring Program |publisher=[[Novatek International]] |accessdate=07 May 2012}}</ref>
While not common, a few LIS may allow users to monitor the environmental conditions of not only sample storage containers but also the entire laboratory itself. Attributes like humidity, air quality, and temperature may be monitored to ensure sample storage units and experiments maintain desired conditions. This monitoring may be done by treating the storage container as a device, which must be interfaced with the LIS. Alarms may be able to be configured to notify staff if a storage container's environmental attributes go beyond a certain threshold.


</div>
</div>
Line 378: Line 393:
===Custom reporting===
===Custom reporting===


Reporting may not be as vital in an ELN as a LIMS, but it still is useful for gaining a clearer picture of collected data and potential trends. At a minimum, a number of pre-configured report templates typically come standard with an ELN. However, other systems are more flexible than others, offering the ability to customize reports in numerous ways. The most popular attributes of custom reporting include custom headers, custom information placement, charts, pivot tables, and multiple output formats.
Reporting is a vital part of an LIS, 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 LIS. However, some LIS 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 ELN vendors will offer custom reporting as an option as an added cost, depending on the level of customization required.
Note: Some LIS vendors will offer custom reporting as an option as an added cost, depending on both the base reporting functionality of the LIS and the level of customization required.


===Synoptic reporting===
===Synoptic reporting===


 
Synoptic reporting is a specific type of reporting applicable to pathology and other associated laboratories. Synoptic reporting essentially involves a structured, pre-formatted "checklist" of clinically and morphologically relevant data elements (ideally passed to a relational database where they are efficiently organized, searched, and retrieved), with the intent of making reporting more efficient, uniform, and relevant to internal and external researchers. This style of reporting has the advantage of obviating the need for transcription services, reducing specimen turnaround time, and prioritizing the presentation of large amounts of diagnostic information. <ref name="SynRepoPaper">{{cite journal |title=Utility and applications of synoptic reporting in pathology |journal=Open Access Bioinformatics |author=Amin, W.; Sirintrapun, S.J.; Parwani, A.V. |year=2010 |volume=2010 |issue=2 |page=105–12 |doi=10.2147/OAB.S12295}}</ref> Some LIS, especially those oriented towards pathology, may include this specialized functionality. In some cases, a [[#Configurable templates and forms|configurable templates or form]] may be utilized to structure a report in a synoptic format, providing similar functionality to a separate synoptic reporting module.


===Report printing===
===Report printing===


Today's software almost universally offers the ability to print reports and other materials, so this feature may seem a bit redundant to list. Nonetheless, printer support is a feature worth confirming when considering a piece of laboratory informatics software.
Today's LIS 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===
===Label support===


The label — typically affixed to a sample container or piece of equipment — is a vital part of many laboratory operations.<ref name="SCLabel">{{cite web |url=http://www.scientificcomputing.com/bar-code-and-sample-tracking.aspx |title=Bar Code and Sample Tracking: It All Starts with the Label |author=Gilles, Clarence |publisher=Scientific Computing |date=1 July 2008 |accessdate=8 May 2012}}</ref> Identifying information such as sample number, batch number, and barcodes are printed on such labels to ensure optimize managing the location of items in a lab. As such, some ELNs allow users to design and print labels directly from the software.
The label—typically affixed to a sample or evidence container—is a vital part of the sample tracking process.<ref name="SCLabel">{{cite web |url=http://www.scientificcomputing.com/bar-code-and-sample-tracking.aspx |archiveurl=https://web.archive.org/web/20101218190848/http://www.scientificcomputing.com/bar-code-and-sample-tracking.aspx |title=Bar Code and Sample Tracking: It All Starts with the Label |author=Gilles, C. |work=Scientific Computing |date=1 July 2008 |archivedate=18 December 2010 |accessdate=18 March 2020}}</ref> 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 LIS allow users to design and print labels directly from the software.


[[File:Code barres.png|thumb|left|The word "Wikipedia" encoded in Code 128 and Code 39]]
[[File:Code barres.png|thumb|left|The word "Wikipedia" encoded in Code 128 and Code 39]]
===Barcode and/or RFID support===
===Barcode and/or RFID support===


Barcodes offer many advantages to laboratory techs handling samples, including more accurate data input, tighter sample/instrument associations, tighter sample/study associations, and more room for human-readable information on a label.<ref name="SCLabel" /> Given such advantages, many laboratory informatics developers have integrated barcode support into their software, including support for symbologies like Code 128, Code 39, and Interleaved 2 of 5. Aside from printing options, an ELN may also offer support for a variety of barcode readers.
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.<ref name="SCLabel" /> As such, LIS developers have integrated barcode support into their laboratory information systems, including support for symbologies like Code 128, Code 39, and Interleaved 2 of 5. Aside from printing options, a LIS may also offer support for a variety of barcode readers.


Barcode support and [[ELN feature#Label support|label support]] are typically found together in ELN software, but not always, thus their separation into two features.
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.<ref name="CSolsTheHidden18">{{cite web |url=https://www.csolsinc.com/blog/hidden-power-barcodes/ |title=The Hidden Power of Barcodes |publisher=CSols, Inc |date=08 February 2018 |accessdate=18 March 2020}}</ref> With these apparent advantages, some LIMS vendors have also added support for RFID-fed sample information.
 
Barcode/RFID support and [[LIS feature#Label support|label support]] are typically found together in LIS software, but not always, thus their separation into two features of a LIS.


===Export to PDF===
===Export to PDF===


An ELN with this feature is able to collect and save information into a Portable Document Format (PDF).
An LIS with this feature is able to collect and save information into a Portable Document Format (PDF).


===Export to MS Word===
===Export to MS Word===


An ELN with this feature is able to collect and save information into a Microsoft Office Word format.
An LIS with this feature is able to collect and save information into a Microsoft Office Word format.


===Export to HTML or XML===
===Export to HTML or XML===


An ELN with this feature is able to collect and save information into a HyperText Markup Language (HTML) and/or Extensible Markup Language (XML) format.
An LIS 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===
===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.
An LIS with this feature is able to connect with a fax machine and send information to it via manual input, automatically, and/or at scheduled intervals. However, with the declining popularity of the fax machine<ref name="HaigneyTheFax18">{{cite web |url=https://www.theatlantic.com/technology/archive/2018/11/why-people-still-use-fax-machines/576070/ |title=The Fax Is Not Yet Obsolete |author=Haigney, S. |work=The Atlantic |date=18 November 2018 |accessdate=18 March 2020}}</ref>, this feature is starting to disappear from modern LIS.


===Email integration===
===Email integration===


An ELN with this feature is able to integrate with and use the electronic mail information exchange method to send reports, alerts, and more manually, automatically, and/or at scheduled intervals.
An LIS with this feature is able to integrate with and use the electronic mail information exchange method to send reports, alerts, and more manually, automatically, and/or at scheduled intervals.


</div>
</div>
Line 431: Line 449:
===Administrator management===
===Administrator management===


The administrator management tools of an ELN allow researchers to set up the ELN most optimally for the facility and its projects. Through the administrator management interface, other features may be accessed like setting up [[ELN feature#Configurable roles and security|user roles]] and scheduling [[ELN feature#Automatic data backup|automatic data backups]].
The administrator management tools of a LIMS allow lab technicians and researchers to set up the LIS most optimally for the laboratory. Through the administrator management interface of a LIS, other features may be accessed like setting up [[LIS feature#Configurable roles and security|user roles]] and scheduling [[LIS feature#Automatic data backup|automatic data backups]].


Like [[ELN feature#Report printing|report printing]], administrator management is nearly ubiquitous in laboratory informatics software, generally considered a mandatory feature. However, for the purposes of being thorough, it's important to point out its existence.   
Like [[LIS feature#Report printing|report printing]], administrator management is nearly ubiquitous in LIS software, generally considered a mandatory feature. However, for the purposes of being thorough, it's important to point out its existence.   


===Modular===
===Modular===


This feature indicates that an ELN 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 an ELN and 2. the limiting of overall effects on the system design as new functionality is added.
This feature indicates that an LIS has an intentional modular design, which separates some functionality into manageable components of the overall system. Generally speaking, a modular design allows for 1. the structured addition of new functionality to an LIS and 2. the limiting of overall effects on the system design as new functionality is added.


===Instrument interfacing and management===
===Instrument interfacing and management===


[[File:Electron Microscope.jpg|thumb|240px|An [[electron microscope]] could potentially be connected to an ELN via instrument interfacing.]]In laboratories there are instruments, and with those instruments comes scientific measurements which produce data. It's therefor natural a researcher would want to connect those instruments to an electronic laboratory notebook, which is already organizing and storing laboratory data for projects and collaborations. This sort of interfacing is typically handled with instrument-to-software interfaces, which started out as merely data-transfer mechanisms. Later that interface mechanism became much more robust as a data management tool, though often at great expense with heavy involvement from third parties.<ref name="SciCompInstr">{{cite web |url=http://www.scientific-computing.com/features/feature.php?feature_id=88 |title=Trends in instrument-to-LIMS interfacing |author=Pavlis, Robert |publisher=Scientific Computing World |date=May/June 2004 |accessdate=8 May 2012}}</ref> Today, "vendors can act as single source providers of the entire instrument interfacing solution,"<ref>{{cite web |url=http://www.limsfinder.com/BlogDetail.aspx?id=33851_0_2_0_C |title=Instrument Interfacing - The Great Paradox of LIMS? |author=DeHeer, Larry |publisher=LIMSfinder.com |date=1 October 2009 |accessdate=8 May 2012}}</ref>, providing a cheaper and smoother solution to laboratory informatics customers.
Laboratories depend on 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 for hospitals and medical research facilities. This sort of interfacing is typically handled with instrument-to-LIS interfaces, which started out as merely a data-transfer mechanism. By the 2000s, that interface mechanism became much more robust as a data management tool, though often at great expense with heavy involvement from third parties.<ref name="PavlisTrends04">{{cite web |url=http://www.scientific-computing.com/features/feature.php?feature_id=88 |archiveurl=https://web.archive.org/web/20150910043807/http://www.scientific-computing.com/features/feature.php?feature_id=88 |title=Trends in instrument-to-LIMS interfacing |author=Pavlis, R. |work=Scientific Computing World |date=May/June 2004 |archivedate=10 September 2015 |accessdate=18 March 2020}}</ref> This eventually meant that "vendors [could] act as single source providers of the entire instrument interfacing solution,"<ref name="DeHeerInstrument09">{{cite web |url=https://www.blazesystems.com/white-papers/instruments/ |title=Instrument Interfacing - The Great Paradox of LIMS? |author=DeHeer, L. |publisher=Blaze Systems Corporation |date=1 October 2009 |accessdate=07 January 2022}}</ref>, providing a cheaper and smoother solution to LIS customers. Today, instrument interfacing is integral to an LIS and is considerably easier to do than prior decades.<ref name="CurtisBeni19">{{cite web |url=https://astrixinc.com/benefits-and-best-practices-for-integrating-laboratory-instruments-with-lims/ |title=Benefits and Best Practices for Integrating Laboratory Instruments with LIMS |author=Curtis Jr., D. |work=Astrix Lab Informatics Blog |date=12 December 2019 |accessdate=18 March 2020}}</ref> In the clinical laboratory setting, an LIS vendor may also have additional considerations to make, such as [[Health Level 7]] (HL7) triggers, messages, and segments transported across communication interfaces.<ref name="HL7Auto">{{cite web |url=http://www.hl7.org/implement/standards/product_brief.cfm?product_id=203 |title=Section 3: Clinical and Administrative Domains - HL7 Version 2.7 Standard: Chapter 13 - Clinical Laboratory Automation |publisher=HL7 |accessdate=18 March 2020}}</ref>
 
The ability to calibrate and schedule maintenance for interfaced instruments may also be included in this category.


It should be noted that some ELN vendors take the approach of creating ELN integration with a [[laboratory information management system]] (LIMS), letting the LIMS handle the instrument interfacing duties. Such functionality is not exclusive; an ELN may be able to interface both with laboratory instruments and with a LIMS. This built-in interface functionality is usually conducted with the help of a [[Parsing|parsing engine]], which helps translate machine data into a formatted and manipulable format, often customized by the ELN vendor.<ref name="AgaramLogi">{{cite web |url=http://www.agaram.co.in/n/index.php/products/logilab.html |title=AGARAM: LogiLab ELN |publisher=Agaram Instruments (P) Ltd |accessdate=16 April 2013}}</ref><ref name="LimsLink">{{cite web |url=http://www.labtronics.com/lims_interfacing.htm |title=PerkinElmer: LimsLink |publisher=PerkinElmer Inc |accessdate=16 April 2013}}</ref><ref name="IA">{{cite web |url=http://www.inductiveautomation.com/;jsessionid=F54A01880FB07A1FF12A43D2BB616D49?wicket:bookmarkablePage=:com.inductiveautomation.website.pages.mes.IgnitionInterfaceModuleParsingPage |title=Inductive Automation: Parsing - A Powerful Built-In Parsing Tool |publisher=Inductive Automation |accessdate=16 April 2013}}</ref>
[[File:Mobile device on display at the Media Markt Sontplein, Groningen (2019) 13.jpg|thumb|right|In some cases mobile devices like these may access and utilize an LIS, typically through a Web portal or special mobile version of the software.]]


===Mobile device integration===
===Mobile device integration===


While not ubiquitous by any means, ELN developers are increasingly including support for mobile devices in their software, usually in the form of a separate mobile version of the software. Research and development labs potentially can put mobile technology to use in the laboratory as remotely monitoring a lab or using mobile phone microscopy.<ref name="SLASMobileDevs">{{cite web |url=http://www.eln.slas.org/story/1/69-mobile-devices-on-the-move-from-laboratories-to-clinics |title=Mobile Devices: On the Move from Laboratories to Clinics |publisher=Society for Laboratory Automation and Screening |date=02 July 2012 |accessdate=13 February 2013}}</ref> Those uses aside, the relatively simple action of recording and reviewing laboratory research results while on the move or at a conference gives researchers flexibility, and ELN developers like [[Rescentris, Inc.|Rescentris]] are beginning to include that functionality.<ref name="BioITNewELNS" /> And where the options aren't simply appealing, some entities like the University of California – San Francisco are making their own mobile-friendly ELN application.<ref name="UCSFELN">{{cite web |url=http://open-proposals.ucsf.edu/itcontest/proposal/158 |title=A Paperless Electronic Lab Notebook for UCSF |author=Nguyen, Khang |publisher=University of California – San Francisco |date=27 July 2012 |accessdate=13 February 2013}}</ref>
Some LIS vendors tout support for mobile devices using their laboratory information 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 clinicians the ability to collect data in the field, approve results remotely, and manage clinical trial and experiement workflow on the fly.<ref name="RyanMobile19">{{cite web |url=https://www.thermofisher.com/blog/connectedlab/mobile-lims-applications-in-the-laboratory/ |title=Mobile LIMS Applications in the Laboratory |author=Ryan, M. |work=The Connected Lab |publisher=Thermo Fisher Scientific |date=28 August 2019 |accessdate=18 March 2020}}</ref>


===Third-party software integration===
===Third-party software integration===


Some ELN vendors either incorporate third-party software into their ELN (e.g. [[Agilent Technologies, Inc.|Agilent]]'s integration of Surety's AbsoluteProof<ref name="AgiSurety">{{cite web |url=http://www.agilent.com/about/newsroom/presrel/2010/20apr-ca10024.html |title=Agilent Technologies Integrates Surety's AbsoluteProof Service into OpenLAB Electronic Lab Notebook, Enhances Data Integrity, Protection |publisher=Agilent Technologies, Inc |date=20 April 2010 |accessdate=13 February 2013}}</ref>) or they provide the means to integrate the ELN with other applications. [[Labtronics Inc.|Labtronics]]' Nexxis ELN is such an example, integrating with other laboratory informatics software, stats packages, and molecular drawing programs.<ref name="SciCompWoNexxisArt">{{cite web |url=http://www.scientific-computing.com/products/product_details.php?product_id=835 |title=Nexxis ELN 5.0 |publisher=Scientific Computing World |date=12 May 2010 |accessdate=13 February 2013}}</ref> Other ELNs like [[Evolvus Pvt. Ltd.|Evolvus]]' Electronic Lab Notebook simply communicate with common authoring tools like Microsoft Word, allowing users to work directly from the third-party application and then transferring the information to the ELN.<ref name="EvoELN">{{cite web |url=http://www.evolvus.com/Informatics/ElectronicLabNotebook.html |title=Electronic Lab Notebook |publisher=Evolvus Pvt. Ltd |accessdate=13 February 2013}}</ref>
A few LIS vendors either incorporate third-party software into their product or they provide the means to integrate the LIS with other applications. The most typical integration involves simply communicating with common authoring tools like Microsoft Word, allowing users to work directly from the third-party application and then transferring the information to the LIS. More recently, integrations with other software systems such as an EHR system have become more common, typically using some sort of [[application programming interface]] (API).
 
In some situations, a third-party application like [[Labtronics Inc.|Labtronics]]' LimsLink is simply used to integrate one piece of software with another piece of software or an instrument.


===Alarms and/or alerts===
===Alarms and/or alerts===


Alarms and alerts in an ELN can be automatic or scheduled, and they can come in the form of an e-mail, a pop-up message, or a mobile text message. For example, when an experiment result goes out-of-range, an automatic warning message can appear on the screen of the research team responsible for the experiment. Another example: a scheduled alert can be e-mailed to a lab technician every month indicating a piece of laboratory equipment needs routine maintenance. Both scenarios represent a tiny fraction of the possible implementation of alarms and alerts in an ELN, highlighting how powerful (yet easy to take for granted) this feature is.
Alarms and alerts in an LIS can be automatic or scheduled, and they can come in the form of an e-mail, a pop-up message, or a mobile text message. For example, when a test result goes out-of-range, an automatic warning message can appear on the screen of the lab analyst responsible for the test. Another example: a scheduled alert can be e-mailed to a lab technician every month indicating a piece of laboratory equipment needs routine maintenance. Both scenarios represent a tiny fraction of the possible implementation of alarms and alerts in an LIS, highlighting how powerful (yet easy to take for granted) this feature is.


===Work-related time tracking===
===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).
This feature specifically refers to an LIS' ability to track the amount of time an employee spends at work in general (for payroll purposes) or on more specific projects and tasks (as part of an employee work evaluation program). May also be referred to as "workload tracking" or "workload tracking."


===Voice recognition system===
===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.
An LIS with this feature allows some functions of the software (for example, accessing test results) to be accessed via voice commands.


===External monitoring===
===External monitoring===
Line 471: Line 489:
This feature allows clients and/or collaborators outside the laboratory to monitor the status of experiments, test results, and more via an online web portal or, less commonly, as activity alerts sent via e-mail or SMS.
This feature allows clients and/or collaborators outside the laboratory to monitor the status of experiments, test results, and more via an online web portal or, less commonly, as activity alerts sent via e-mail or SMS.


[[File:Example of Telecommunication Presence Information.png|thumb|left|An instant messaging client built into an ELN often makes it easier to collaborate.]]
[[File:Example of Telecommunication Presence Information.png|thumb|left|An instant messaging client built into an LIS often makes it easier to collaborate.]]
===Messaging===
===Messaging===


The messaging feature of an ELN may refer to one of two (or both) things:
The messaging feature of an LIS may refer to one of two (or both) things:
 
{{flowlist |
* a built-in instant messaging system that allows users to converse with each other through text messages real-time
*a built-in instant messaging system that allows users to converse with each other through text messages real-time, or
* an SMS text messaging integration that allows the users or the ELN itself to send messages or alerts to one or more user's mobile or smart phone
*SMS text messaging integration that allows users or the LIMS itself to send messages or alerts to a user's mobile or smart phone.
}}


===Commenting===
===Commenting===


Research collaborations require data sharing and communication tools to be most effective. One of the collaborative communication features of an ELN is commenting. Many ELNs like [[BiochemLab Solutions]]' Electronic Lab Notebook and [[LabArchives, LLC]]'s LabArchives ELN allow users to comment on experiment results, observations, and conjectures as well as allow for linking to and from comments.<ref name="BioChemELN">{{cite web |url=http://biochemlabsolutions.com/ELN/ELN.html |title=Electronic Lab Notebook ELN - Download |publisher=BiochemLab Solutions |accessdate=13 February 2013}}</ref><ref name="LAFeats">{{cite web |url=http://www.labarchives.com/features.php |title=LabArchives Online Lab Notebook - Features & Benefits |publisher=LabArchives, LLC |accessdate=13 February 2013}}</ref>
Clinical data collection and research collaboration require data sharing and communication tools to be most effective. One of the collaborative communication features of some LIS is commenting on test results, patient records, or study protocols.


===Multilingual===
===Multilingual===


If an ELN is listed as multilingual, its an indication the software interface can be configured to display more than one language depending on the preference a user or administrator chooses. Some ELN 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.
If an LIS is listed as multilingual, its an indication the software interface can be configured to display more than one language depending on the preference a user or administrator chooses. Some LIS interfaces can only be displayed in one of two languages (English or German, for example), while others come configured with support for dozens of languages.


===Network-capable===
===Network-capable===


This feature is perhaps archaic and/or obvious, but it is mentioned nonetheless. It's generally applied to a non-web-based ELN installed over a local or wide-area computer network, essentially indicating the ELN is not an isolated application, but rather one that can interface with other instances or other networked instruments.
This feature is perhaps archaic and/or obvious, but it is mentioned nonetheless. It's generally applied to a non-web-based (on-premises) LIS installed over a local or wide-area computer network, essentially indicating the LIS is not an isolated application, but rather one that can interface with other instances or other networked instruments.


===Web client or portal===
===Web client or portal===


An ELN with a web client or portal is either a web-based ELN (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 ELN with an included portal to access it via the Internet.
A LIS 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 LIS with an included portal to access it via the internet.


===Online or integrated help===
===Online or integrated help===


This indicates an ELN has help infrastructure integrated into the software, support documentation via the vendor's website, or both.
This indicates an LIS has help infrastructure integrated into the software, support documentation via the vendor's website, or both.


===Software as a service delivery model===
===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 indicates the software can be licensed and utilized via the [[software as a service]] (SaaS) delivery model. This typically constitutes a LIS vendor having a "cloud-based" offering.


===Usage-based cost===
===Usage-based cost===


While rare, some software vendors allow potential clients to license and utilize the vendor's software under a usage-based cost model. An example of this model in use is Bytewize AB's [[Bytewize AB#O3 Lims and O3 LimsXpress|O3 LimsXpress]], which has a cost directly related to the amount of samples processed each month.<ref name="O3Prices">{{cite web |url=http://www.bytewize.com/o3lims-xpress/prices/?lang=en |title=Modern web based Lims from 10 Euro cent/sample |publisher=[[Bytewize AB]] |accessdate=8 May 2012}}</ref>
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 [[Vendor:Bytewize AB#O3 Lims and O3 LimsXpress|O3 LimsXpress]], which has a cost directly related to the amount of samples processed each month.<ref name="BWO3X">{{cite web |url=https://www.bytewize.com/o3limsxpress |title=O3 LimsXpress |publisher=Bytewize AB |accessdate=18 March 2020}}</ref> You may also see this sort of usage-based cost on some cloud-based LIMS.


</div>
</div>
Line 511: Line 530:


==References==
==References==
{{Reflist|2}}
{{Reflist|3}}


[[Category: Laboratory informatics]]
[[Category: Laboratory informatics]]

Latest revision as of 01:16, 5 April 2024

Thousands of hospital laboratories like this one benefit from the use of a laboratory information system.

An LIS feature is one or more pieces of functionality that appear within a laboratory information system (LIS).

The LIS has traditionally been utilized in clinical, pathology, and medical research laboratories as well as numerous public health institutions.[1] Yet as laboratory demands have changed and technological progress has continued, the functions of an LIS have also changed, with the distinction between an LIS and a laboratory information management system (LIMS) fading as some LIMS vendors have adopted the case-centric information management normally reserved for an LIS.[2][3].

Despite the blurring of distinction between an LIS and a LIMS, the LIS generally continues to feature the following[4][5]:

  • patient management, including admission date, admitting physician, ordering department, specimen type, etc.
  • specimen management and tracking
  • configurable decision support, including comparisons of lab orders with their respective ICD codes
  • quality assurance of ordered tests
  • workload and management reporting

Of course, there are LIS features that are difficult to categorize or simply contribute to the whole of the LIS rather than add a function. For example, multilingual support allows users to interact with the LIS in more than one language. Some functionality may also overlap several research phases, making it difficult to firmly classify.

The features described below come from an analysis of freely available LIS product information on vendor websites. An attempt was made to discover the features most utilized in vendors' LIS products and collect information on those features for each LIS. Not every possible feature is referenced here; some LIS products fill specific niches, utilizing unique functionality to solve a specific problem.

That said, keep in mind the categorization of features below is very loose. It may be viable to argue a feature belongs under a different section or multiple sections. For the purposes of organizing this information in an uncomplicated manner, however, some liberty has been taken in the categorizing of features.

Experiment, patient, and data management

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

 

Sample login and management

Sample login and management—often referred to as accessioning or specimen management—is an important component of the clinical laboratory, whether it's a molecular pathology lab testing samples for disease indicators or a contract lab running pharmacokinetic and biomarker analysis on samples from a clinical trial.[6][7] As such, researchers and technicians who work in these types of labs are unable to complete their tasks without an effective method of managing samples. The process of sample management and accessioning includes, but is not limited to[8][6]:

  • storing related sample information, including demographics, dates, and external links
  • creating and documenting viewable sample container schemas with name and status
  • assigning sample access rights
  • assigning custom sample ID or accessioning numbers based on a specification
  • applying additional processing to the sample before storage and/or analysis

Additional functionality that could potentially fall under this feature:

  • barcoding or RFID tagging of samples
  • defining sample points and series
  • creating data associations for samples, such as pedigree for sample/aliquot relationships or relationships based on experiment, etc.
  • issuing sample receipts

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 actions are being performed on 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.[9]

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.[10] While handwritten labels were the norm, barcode and RFID support in an LIS can "tie together a vast amount of information, clearly relating each sample to a specific case."[9] 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 LIS have implemented extensive configurability to compensate for varying environments.[11]

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

Sample and result batching

What is batching? The United States Environmental Protection Agency (EPA) defines a batch as "a group of samples which behave similarly with respect to the sampling or testing procedures being employed and which are processed as a unit."[12] 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 an LIS, the ability to schedule a task or event is a natural extension of how work was done in a laboratory before the advent of data management systems. Sample processing, data analysis, equipment maintenance, and case management follow-ups are assigned to technicians and other personnel. Outpatient scheduling is another aspect of some clinical atmospheres, better handled with computerized scheduling functionality. While these tasks have in the past been performed without the LIS, a modern data management system can now optimize those tasks and provide additional scheduling functionality to streamline the operation of a lab. Some LIS will include, for example, a scheduling calendar for recurring test orders, rules-based orders, and pre-defined selection lists. Additional functionality within this feature group includes the ability to configure automated assignments of experiment requests, establish recurring events, and in most cases, create printable reports.

Examples of tasks and events that can feasibly be scheduled in an LIS include:

  • production of reports
  • creation and sending of e-mails and alerts
  • maintenance of equipment
  • assignment of accessioning tasks to technicians
  • scheduling outpatient visits

Option for manual result entry

While many LIS vendors tout the ability of their product to automate the entry of sample analysis results into an LIS or other 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 LIS. Additional functionality associated with this feature includes a customizable spell-check dictionary and the ability to add comments, notes, and narratives to many of the data items in the LIS.

Multiple data viewing methods

Hospitals, physicians, and clinical research facilities produce reams of data, and the LIS exists to help organize and distribute that data to the necessary entities. Additionally, even before the existence of the LIS, scientists have had a corresponding need for visually representing that data for clearer analysis and hypothesis creation. Today an LIS can not only collect and analyze data, but it also can represent that data in reports, graphs, gradients, and spreadsheets. Depending on the LIS, more than one way to visually represent the data may exist.

This category ties in with the custom templates and forms functionality apparent in some LIS, providing both custom and standardized ways to present information across a healthcare or medical research enterprise.

Configurable templates and forms

Similar to an electronic laboratory notebook (ELN), a template in an LIS is a functionality item which allows users to increase the productivity and quality of their work by allowing for the creation of a standardized analysis page, patient page, or reporting process across a healthcare or medical research enterprise. These templates allow researchers to maintain more consistent data representation for similar tasks in the LIS and save time by not needing to manually input common data outputs or recreate experiments. Templates and forms typically utilize a wide field library, and the data that is posted to those template fields can also be normalized to a specific standard. Types of templates that may be created include those for renal and blood pressure analysis, patient demographics, test ordering, and department-level reports.[13]

Data and trend analysis

Some LISs allow users to analyze patient test results or clinical research data with built-in software tools.
For public health centers and pharmaceutical research centers alike, data analysis plays an important role in their operations, helping clinicians and researchers make better sense of their collected data and reach valuable conclusions about them. While this important phase of laboratory work has often been done externally from the LIS, today's LIS commonly has basic data analysis tools included. Such tools allow raw data to be imported directly to the LIS, which then can store, process, and display it in a shareable form. Vendors may include data analysis functionality by simply including Microsoft Excel compatibility or providing advanced reporting tools, or they may take a more advanced approach by programming and including their own custom data and trend analysis tools in their informatics software. As data analysis has become increasingly vital, such functionality—which has often come in the form of a separate application or analysis device—continues to end up in software like LIS, LIMS, and other laboratory informatics solutions.[14]

Data and equipment sharing

Aside from data storage and sample registration, a modern LIS's major contribution to the laboratory is aiding in the sharing of test results, reports, and patient data with other entities across the clinical and research enterprise. Rather than pieces of information becoming misplaced or locked away in a physician's office or pathology lab, the LIS makes it easier to test results and increase the efficiency of patient-doctor-lab collaboration in general. However, data is more than just test results; it also can come in the form of charts, reports, policy and procedure, and other documents. Additionally, the need for controlling who has access to those types of data is also an important consideration. As such, this feature is at least partially tied to other features like document management and configurable security.

Data mining

Data mining, in the field of computational science, involves "the process of discovering interesting and useful patterns and relationships in large volumes of data" and includes three computational steps: model-learning, model evaluation, and model usage.[15] As informatics software allows both research and clinical laboratories to collect and manage increasing quantities of data, a corresponding demand for tools capable of modeling that data is appearing.[16] For example, public health laboratories may wish to utilize data mining for statistical analysis and surveillance of populations for specific diseases. LIS like Livextens and Orchard Harvest are examples of laboratory informatics software which incorporate data mining and reporting tools.[17][18]

Customizable fields and/or interface

As thorough as some user interface (UI) developers may be in adding relevant fields and interface options for end users, there are at times options that are either omitted or unanticipated. This has traditionally required the end user to contact the vendor and ask if the needed option(s) can be added in the next release. However, many modern LIS vendors have responded instead by adding functionality that gives end users and/or LIS administrators more control over the user interface.

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

  • report interface and display
  • patient profile display
  • project and experiment display

Increasingly, today's vendors tend to refer to their systems as being "configurable" rather than "customizable."[19][20] For example, vendors such as Autoscribe Informatics include screen editing and other tools that administrators can user to configure the various screens, data fields, nomenclature, etc. of the solution.[19]

Note in many cases an interface may be customized through the use of templates and forms, and as such, this functionality may be closely tied to the configurable templates and forms functionality.

Query capability

As was the case before the advent of databases and electronic data management solutions, today researchers must search through test results, patient notes, and other types of data to better draw conclusions from experiments, diagnose patient illnesses, and plan pharmaceutical research activities. Whereas this used to mean browsing through laboratory notebooks, Excel spreadsheets, or Access databases, now powerful query tools exists within data management tools like the LIS and ELN. A flexible search algorithm can be implemented to allow users to search a dataset by patient name (full or partial) or by any accessioning number. Or more advanced query tools may be implemented to collate and search across multiple datasets.

Query functionality often includes the ability to:

  • search both transactional data and archived data tables
  • search multiple databases via an application programming interface (API) or open database connectivity (ODBC) connection
  • filter and sort data
  • collate queried data for further analysis and visualization
  • create ad hoc queries

Import data

Data can originate from numerous places in the laboratory. The ability to import that data into an LIS can be beneficial, especially when an instrument can't be connected or external clients collaborating on a project need to submit relevant data. Of course instrument interfacing allows for even more importation options. Additional data validation procedures may be applied to the imported data to guarantee information homogeneity. For the LIS, one of the common sources of importing data is a separate electronic medical record (EMR) or electronic health record (EHR) system, for collecting patient data and test orders.[21]

Internal file or data linking

Many informatics systems allow for internal linking of data; however, entities outside of the system often need to access the data housed within. An LIS is often capable of such external data linking.
This feature allows research collaborators using an LIS to link together sample batches, reports, protocols, results, and more, providing greater contextual clarity to projects and datasets. Examples include:
  • linking a sample batch to a test or sample preparation methodology
  • linking a test process to a particular experiment
  • linking a report to a sample batch
  • linking a group of experiment results to a raw data file
  • linking multiple images to a patient record
  • linking all experiment results with the correct reporting test methods

External file or data linking

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

  • linking to an external practice management or electronic medical record (EMR) system using an an HL7-compliant interface
  • linking one public health data source with others to pool demographic and medical information for better disease modeling
  • linking to separate clinical trial laboratory data files within a report

ELN support or integration

The functionality of solutions such as an LIS and LIMS began to blur with that of an ELN in the 2000s, with both types of software incorporating features from the other.[22][23] More than a decade later, the ELN has become more distinct in purpose and functionality and is typically sold as a stand-alone solution. However, some vendors such as Genohm have decided to integrate ELN functionality into their solution in order to provide greater flexibility to researchers.[24] While it has been more common to see this sort of melding in a LIMS, it has been less common in the LIS. Yet some LIS may include some sort of integration or compatibility with an ELN, and thusly this functionality is at least mentioned.

Export to MS Excel

While Microsoft Excel had long been used within the laboratory setting, a slow shift towards relational databases and LIMS occurred in the late 1990s and early 2000s.[25] 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.[26] Several decades later, some laboratories continue to use Excel in some fashion, and thus having an LIS capable of handling Excel data remains useful. In particular, selecting and exporting the LIS' data (from test results to quality control charts) into a format such as Excel may further data visualization, insights, and dissemination for some users.[27][28]

Raw data management

While not described as a feature on most LIS vendor websites, a few indicate their product is capable of managing (import, export, editing, etc.) data in its raw format for future analysis. This raw data is typically implied to be originating from instruments that interface with the LIS, which in itself is not unusual. That raw data may remain housed in instruments, getting transformed into reportable data in the LIS, but presumably most LIS are also capable of housing the raw instrument data as well.[29] Clinical research labs may also turn to scientific data management systems to better manage their raw data sources.[30]

Data warehouse

an LIS' 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.[31]

Project and/or task management

Project and task management within an LIS typically involves the scheduling of tasks to technicians and organizing associated tasks into a more cohesive unit for better tracking and management. While the functionality of task and event scheduling can also be found in project and task management, many LIS include functionality beyond scheduling that warrants the addition of the project and/or task management feature. This functionality includes:

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

See also: Patient and case management

Test, experiment, and/or trial management

Specimen or sample test management is a common component of an LIS, while experiment and research trial management functionality is a component of some LIS, often limited to those that are designed to help manage clinical trials. Test, experiment, and trial management can cover a wide variety of tasks, from setting up the design of a clinical trial to specimen task assignments, from ordering tests for patients to planning trial experiments. Note: this may also be referred to as "order management" with some vendors.

It's worth noting this functionality category may seem broad in scope and include other functionality listed on this page, including workflow management and project and task management. Its inclusion when reviewing software functionality is primarily to indicate when a vendor or project team indicates the existence of specific test, experiment, or trial management tools in their software.

Inventory management

Laboratories use a wide array of inventory and equipment, from reagents and radiopharmaceuticals to glassware and laboratory baths. With that comes the need to know how much/many and the frequency of use. For this, LIS solutions include some sort of inventory management functionality.

  • register origin, demographics of incoming materials
  • track used and in-use items via barcodes or RFID
  • 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 item counts
  • track location and usage of laboratory equipment
  • assign storage locations
  • track forensic evidence

Document and/or image management

Standard operating procedures, workflow diagrams, and business models can all be handled effectively with document management functionality.
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 an LIS 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:
  • upload and index documents of most any file type and size
  • enforce version control
  • provide full text search
  • convert and/or export to PDF or other relevant formats
  • add documents as attachments to other analyses, files, projects, etc. in the system

Patient and case management

The LIS has played an important role in the case management tasks of patient-centric and clinical laboratories. LIS products have included patient or case management tools suitable for the clinical, public health, and veterinary industries, as well as the fields of law enforcement and forensic science. Functionality seen in the patient and case management feature includes:

  • case accessioning and assignment
  • disease tracking
  • trend analysis
  • clinical history follow-up
  • out-of-range result alerts
  • document and result association
  • evidence control
  • study management
  • collating of patient data across multiple spectrum

Workflow 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 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.[32] However, in the late 2000s laboratory informatics vendors began incorporating workflow management functionality into their software, reducing the headaches that customization of a solution often brought.[33]

Modern commercial and open-source LIS solutions recognize clinical laboratory workflow often has its own share of requirements, requiring specific workflow management functionality, including[34]:

  • managing the request cycle within a laboratory
  • organizing and executing diagnostic testing
  • managing specific chemistry- and biology-related procedures
  • defining activity attributes
  • managing automation tools to better workflows
  • re-routing samples based on changes to a process
  • dynamically modifying workflow in case of future changes
  • receiving notification of changes to the workflow

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 ASTM offers standards and specs for LIS[35], so too do LIS users have standards and specs for their laboratory.

Spec management has primarily been seen in a manufacturing execution system (MES) or a laboratory information management system (LIMS), but occasionally an LIS may appear which includes such functionality. With spec management in place, laboratories can then:

  • enforce standard operating procedures and business rules
  • create specs down to a project or sample level
  • validate recipes and procedures
  • accept or reject sample batches
  • document internal and external spec history

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

Customer, supplier, and physician management

Unless a laboratory is conducting internalized independent research, in most cases it will do business with external entities such as contract labs, physician offices, equipment providers, and reagent suppliers. In some cases, even internal employees may be considered a customer, necessitating documentation of who is using the system and in what ways. For a veterinary lab, the customer may be the animal and handler. For a forensic lab the customer may be more complex: internal staff, university staff, police departments, and maintainers of nationwide crime databases may all at some point act as customers. In these cases, documenting these various points of contact and linking them to tests, equipment, and patients becomes vital. Managing demographics, complaints, correspondence, and history are all feasible with customer, supplier, and physician management functionality. This process is often made simpler through the use of a more context-neutral entity creation system, which allows for more flexible management of contacts.

This feature may also be referred to as contact management, an address book module, or a customer service module.

Billing and revenue management

While the finances of a laboratory are important, they've typically been handled separately as a business process. However, some LIS include additional functionality to make handling financial transactions and documentation of all sorts possible within the LIS. In theory, such functionality brings the possibility of keeping more of a laboratory's data centrally located and queryable. This feature may include[36][37]:

  • payment processing
  • expense reporting
  • price quotes
  • revenue cycle management
  • workload tracking of billable hours
  • bill of materials
  • sales team and client management
  • profitability analysis
  • medical necessity checks

 

Quality, security, and compliance

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

 

Regulatory compliance

The topic of whether or not an LIS meets regulatory compliance is often a complex one. While Title 21 CFR Part 11 has arguably had the largest influence on an electronic data management system's compliance, other influential standards have shaped the way laboratory informatics systems handle and store data. Other compliance-based codes, standards, and regulations include:

With so many codes, standards, and regulations, it can be challenging for potential LIS 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 LIS 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.

QA/QC functions

The quality management functions of an LIS allow users to maintain a level of necessary quality across many of the functions in a laboratory. Some of the activities quality assurance / quality control functionality allows for includes[38][39][40]:

  • force random review of cases by second pathologist before case verification
  • receive and process QC results from laboratory analyzers
  • create user rules
  • set up custom alerts and flags for out-of-range results
  • observe standard deviations in outcome research
  • review and sign off on data electronically
  • delta checking

Performance evaluation

As prevalent as document management has become in clinical and research laboratories, it makes sense that the LIS 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 an LIS makes this possible.

That functionality typically includes the ability to maintain training records and history, and also to link that training to a technique or piece of equipment. Afterwards, the staff member, vendor, etc. can be marked as competent or certified in the equipment, knowledge, or process. Periodical assessment of the training and its practical effectiveness can later be performed. Productivity of an entity or process can also be gauged over a certain date range based on tracked time, pre-determined milestones, or some other criteria.

Audit trail

Whether validating an instrument's data or an entire LIS, maintaining an audit trail is an important part of 21 CFR Part 11 compliance.
As laws 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[41], LIS developers must put serious thought into how their software handles audit trail functionality. The audit trail—documentation of the sequence of activities that have affected an action—must be thorough and seamlessly integrated into the software, and it has become a mandatory feature for labs operating in regulated environments.[42]

Information recorded in the audit trail typically includes:

  • operator code
  • time stamp
  • location
  • case number
  • accessioning number
  • transaction type
  • amount and quantity prior to change
  • user notes (e.g., reason for change)
  • in some cases, data in temporary memory[43]


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.[44] At its core, the COC strives to answer at least these five questions[45]:

  1. Where is my sample or specimen now?
  2. Who possess my sample or specimen now?
  3. When did that individual take possession of my sample or specimen?
  4. Where has my sample or specimen been?
  5. Who has been in possession of my sample or specimen?

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 clinical and research setting, each with its own set of responsibilities. And just as the role an individual plays within the laboratory may change, so may the responsibilities associated with each role. This sort of change necessitates a flexible and configurable security system, one that allows for the placement of individual LIS users into standardized security roles which provide role-specific access to certain functionality. Additionally, as responsibilities change within roles, that same flexible configuration is necessary for assigning or restricting access to specific functionality for each existing or newly created role.

Of course, roles aren't always assigned on an individual level. Often large groups of individuals may need to be assigned to roles, necessitating group assignments for security purposes. For example, a group of hospital laboratory trainees may not be given access to the inventory management functionality of the system through a custom "Trainees" group role, while the head of the lab may be given the "Administrator" role, which allows that individual to access a much broader spectrum of the LIS's functionality.

Data normalization

For the purposes of describing LIS functionality, "data normalization" specifically refers to the process of ensuring data that moves into the LIS is formatted in a standardized way, matching the format of existing LIMS data.

Here's an example to better explain this issue. When an LIS 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 LIS can normalize the incoming data to match the standard already set for existing LIS temperature data. This ensures consistency within the LIS database and typically leads to better data validation efforts later on.

Note: Some LIS developers may include data normalization functionality within what they may refer to as "data validation" functionality. The line between these two may be blurred or not exist at all.

Data validation

In an LIS, data and data models can be forced through a validation process to remove errors and reconcile that those data and models.
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.[46][47]

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

Data encryption

The existence of this functionality in LIS software generally indicates the LIS 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.[49] As a wide variety of encryption technologies exist, it's generally a good idea to consult with the developers of an LIS 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 LIS, including test methods, 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.

Some LIS vendors may choose to 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.[50] 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 LIS buyers may need to inquire with developers to determine what type of versioning scheme is used in the vendor's software.

Automatic data backup

The functionality of automatic data backup in an LIS usually means information contained in one or more associated databases or data warehouses can be automatically preserved in an additional backup file. The save location for that file as well as the scheduled backup time is configurable, typically through the administrative module of the LIS. As cloud-based LIS have slowly increased in number, scheduled cloud-to-cloud data backups of software data are becoming more practical.[51]

Environmental monitoring

While not common, a few LIS may allow users to monitor the environmental conditions of not only sample storage containers but also the entire laboratory itself. Attributes like humidity, air quality, and temperature may be monitored to ensure sample storage units and experiments maintain desired conditions. This monitoring may be done by treating the storage container as a device, which must be interfaced with the LIS. Alarms may be able to be configured to notify staff if a storage container's environmental attributes go beyond a certain threshold.

 

Reporting, barcoding, and printing

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

 

Custom reporting

Reporting is a vital part of an LIS, 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 LIS. However, some LIS 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 LIS vendors will offer custom reporting as an option as an added cost, depending on both the base reporting functionality of the LIS and the level of customization required.

Synoptic reporting

Synoptic reporting is a specific type of reporting applicable to pathology and other associated laboratories. Synoptic reporting essentially involves a structured, pre-formatted "checklist" of clinically and morphologically relevant data elements (ideally passed to a relational database where they are efficiently organized, searched, and retrieved), with the intent of making reporting more efficient, uniform, and relevant to internal and external researchers. This style of reporting has the advantage of obviating the need for transcription services, reducing specimen turnaround time, and prioritizing the presentation of large amounts of diagnostic information. [52] Some LIS, especially those oriented towards pathology, may include this specialized functionality. In some cases, a configurable templates or form may be utilized to structure a report in a synoptic format, providing similar functionality to a separate synoptic reporting module.

Report printing

Today's LIS 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 or evidence container—is a vital part of the sample tracking process.[53] 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 LIS allow users to design and print labels directly from the software.

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

Barcode and/or RFID support

Barcodes offer many advantages to laboratory techs handling samples, including more accurate data input, tighter sample/instrument associations, tighter sample/study associations, and more room for human-readable information on a label.[53] As such, LIS developers have integrated barcode support into their laboratory information systems, including support for symbologies like Code 128, Code 39, and Interleaved 2 of 5. Aside from printing options, a LIS 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.[54] 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 LIS software, but not always, thus their separation into two features of a LIS.

Export to PDF

An LIS with this feature is able to collect and save information into a Portable Document Format (PDF).

Export to MS Word

An LIS with this feature is able to collect and save information into a Microsoft Office Word format.

Export to HTML or XML

An LIS 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

An LIS with this feature is able to connect with a fax machine and send information to it via manual input, automatically, and/or at scheduled intervals. However, with the declining popularity of the fax machine[55], this feature is starting to disappear from modern LIS.

Email integration

An LIS with this feature is able to integrate with and use the electronic mail information exchange method to send reports, alerts, and more manually, automatically, and/or at scheduled intervals.

 

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 and researchers to set up the LIS most optimally for the laboratory. Through the administrator management interface of a LIS, other features may be accessed like setting up user roles and scheduling automatic data backups.

Like report printing, administrator management is nearly ubiquitous in LIS 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 an LIS has an intentional modular design, which separates some functionality into manageable components of the overall system. Generally speaking, a modular design allows for 1. the structured addition of new functionality to an LIS and 2. the limiting of overall effects on the system design as new functionality is added.

Instrument interfacing and management

Laboratories depend on 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 for hospitals and medical research facilities. This sort of interfacing is typically handled with instrument-to-LIS interfaces, which started out as merely a data-transfer mechanism. By the 2000s, that interface mechanism became much more robust as a data management tool, though often at great expense with heavy involvement from third parties.[56] This eventually meant that "vendors [could] act as single source providers of the entire instrument interfacing solution,"[57], providing a cheaper and smoother solution to LIS customers. Today, instrument interfacing is integral to an LIS and is considerably easier to do than prior decades.[58] In the clinical laboratory setting, an LIS vendor may also have additional considerations to make, such as Health Level 7 (HL7) triggers, messages, and segments transported across communication interfaces.[59]

The ability to calibrate and schedule maintenance for interfaced instruments may also be included in this category.

In some cases mobile devices like these may access and utilize an LIS, typically through a Web portal or special mobile version of the software.

Mobile device integration

Some LIS vendors tout support for mobile devices using their laboratory information 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 clinicians the ability to collect data in the field, approve results remotely, and manage clinical trial and experiement workflow on the fly.[60]

Third-party software integration

A few LIS vendors either incorporate third-party software into their product or they provide the means to integrate the LIS with other applications. The most typical integration involves simply communicating with common authoring tools like Microsoft Word, allowing users to work directly from the third-party application and then transferring the information to the LIS. More recently, integrations with other software systems such as an EHR system have become more common, typically using some sort of application programming interface (API).

Alarms and/or alerts

Alarms and alerts in an LIS can be automatic or scheduled, and they can come in the form of an e-mail, a pop-up message, or a mobile text message. For example, when a test result goes out-of-range, an automatic warning message can appear on the screen of the lab analyst responsible for the test. Another example: a scheduled alert can be e-mailed to a lab technician every month indicating a piece of laboratory equipment needs routine maintenance. Both scenarios represent a tiny fraction of the possible implementation of alarms and alerts in an LIS, highlighting how powerful (yet easy to take for granted) this feature is.

Work-related time tracking

This feature specifically refers to an LIS' ability to track the amount of time an employee spends at work in general (for payroll purposes) or on more specific projects and tasks (as part of an employee work evaluation program). May also be referred to as "workload tracking" or "workload tracking."

Voice recognition system

An LIS with this feature allows some functions of the software (for example, accessing test results) to be accessed via voice commands.

External monitoring

This feature allows clients and/or collaborators outside the laboratory to monitor the status of experiments, test results, and more via an online web portal or, less commonly, as activity alerts sent via e-mail or SMS.

An instant messaging client built into an LIS often makes it easier to collaborate.

Messaging

The messaging feature of an LIS may refer to one of two (or both) things:

  • a built-in instant messaging system that allows users to converse with each other through text messages real-time, or
  • SMS text messaging integration that allows users or the LIMS itself to send messages or alerts to a user's mobile or smart phone.

Commenting

Clinical data collection and research collaboration require data sharing and communication tools to be most effective. One of the collaborative communication features of some LIS is commenting on test results, patient records, or study protocols.

Multilingual

If an LIS is listed as multilingual, its an indication the software interface can be configured to display more than one language depending on the preference a user or administrator chooses. Some LIS interfaces can only be displayed in one of two languages (English or German, for example), while others come configured with support for dozens of languages.

Network-capable

This feature is perhaps archaic and/or obvious, but it is mentioned nonetheless. It's generally applied to a non-web-based (on-premises) LIS installed over a local or wide-area computer network, essentially indicating the LIS is not an isolated application, but rather one that can interface with other instances or other networked instruments.

Web client or portal

A LIS with a web client or portal is either a web-based 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 LIS with an included portal to access it via the internet.

Online or integrated help

This indicates an LIS has help infrastructure integrated into the software, support documentation via the vendor's website, or both.

Software as a service delivery model

This indicates the software can be licensed and utilized via the software as a service (SaaS) delivery model. This typically constitutes a LIS vendor having a "cloud-based" offering.

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.[61] You may also see this sort of usage-based cost on some cloud-based LIMS.

 

References

  1. "Laboratory Information Systems Project Management: A Guidebook for International Implementations" (PDF). Association of Public Health Laboratories. May 2019. https://www.aphl.org/aboutAPHL/publications/Documents/GH-2019May-LIS-Guidebook-web.pdf. Retrieved 18 March 2020. 
  2. Hice, R. (1 July 2009). "Swimming in the Clinical Pool: Why LIMS are supplanting old-school clinical LIS applications". Laboratory Informatics Blog. Archived from the original on 19 January 2010. https://web.archive.org/web/20100119015222/http://blog.starlims.com/2009/07/01/swimming-in-the-clinical-pool-why-lims-are-supplanting-old-school-clinical-lis-applications/. Retrieved 18 March 2020. 
  3. "How Do I Find the Right LIMS — And How Much Will It Cost?" (PDF). Laboratory Informatics Institute, Inc. Archived from the original on 26 June 2015. https://web.archive.org/web/20150626125210/http://files.limstitute.com/share/lbgprofiles/findlims.pdf. Retrieved 18 March 2020. 
  4. ADVANCE Healthcare Network Staff (30 July 2015). "Critical Features of the LIS". https://www.elitecme.com/resource-center/laboratory/critical-features-of-the-lis/. Retrieved 18 March 2020. 
  5. Futrell, K. (23 January 2017). "What's new in today's LIS?". Medical Laboratory Observer. https://www.mlo-online.com/continuing-education/article/13009013/whats-new-in-todays-lis. Retrieved 18 March 2020. 
  6. 6.0 6.1 Leonard, Debra G. B.; Bagg, Adam, ed. (2007). Molecular Pathology in Clinical Practice (Illustrated ed.). Springer. p. 567. ISBN 0387332278. https://books.google.com/books?id=Z2YNhh51SmQC&pg=PA567. Retrieved 18 March 2020. 
  7. "PPD - Central Lab Capabilities". Pharmaceutical Product Development, LLC. https://www.ppd.com/our-solutions/ppd-laboratories/central-lab/capabilities/. Retrieved 06 January 2022. 
  8. Esteridge, B.H.; Reynolds, A.P.; Walters, N.J. (2000). Basic Medical Laboratory Techniques (4th, revised ed.). Cengage Learning. p. 8. ISBN 0766812065. https://books.google.com/books?id=qMgAbOHSlsMC&pg=PA8&lpg=PA8. Retrieved 18 March 2020. 
  9. 9.0 9.1 Murthy, T.; Hewson, B. (1 September 2010). "Effective Forensic Sample Tracking and Handling". American Laboratory. https://www.americanlaboratory.com/914-Application-Notes/506-Effective-Forensic-Sample-Tracking-and-Handling/. Retrieved 13 March 2020. 
  10. Vaniotis, G. (19 July 2018). "How RFID Labels Can Smarten Up Your Laboratory". Labtag Blog. https://blog.labtag.com/rfid-labels-in-the-lab. Retrieved 13 March 2020. 
  11. Muntean, E.; Munteanb, N.; Mihăiescua, T.; Mihăiescuc, R. (2008). "LIMS use in laboratory data management". ProEnvironment/Promediu 1 (2): 19–23. http://journals.usamvcluj.ro/index.php/promediu/article/view/2835. 
  12. "Batch Sizes And QC Questions". U.S. EPA. 4 April 2016. https://archive.epa.gov/epawaste/hazard/web/html/faqs_qc.html. Retrieved 13 March 2020. 
  13. Park, S.L.; Pantanowitz, L.; Sharma, G.; Parwani, A.V. (March 2012). "Anatomic Pathology Laboratory Information Systems: A Review". Advances in Anatomic Pathology 19 (2): 81–96. doi:10.1097/PAP.0b013e318248b787. PMID 22313836. 
  14. Macneil, R. (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 (1): 2. doi:10.1186/1759-4499-3-2. PMC PMC3146905. PMID 21707999. https://www.ncbi.nlm.nih.gov/pmc/articles/PMC3146905. 
  15. "data mining". Encyclopædia Britannica. Encyclopædia Britannica, Inc. https://www.britannica.com/technology/data-mining. Retrieved 18 March 2020. 
  16. Sepulveda, J.L.; Young, D.S. (2013). "The Ideal Laboratory Information System". Archives of Pathology and Laboratory Medicine 137 (8): 1129–40. doi:10.5858/arpa.2012-0362-RA. PMID 23216205. 
  17. "TD Analaytics Livextens". Technidata SAS. https://www.technidata-web.com/tdanalytics. Retrieved 18 March 2020. 
  18. "Orchard Harvest". Orchard Software Corporation. https://www.orchardsoft.com/solutions/orchard-harvest/. Retrieved 06 January 2022. 
  19. 19.0 19.1 "LIMS Customization vs Configuration". Autoscribe Informatics, Inc. 8 March 2015. https://www.autoscribeinformatics.com/resources/blog/lims-customization-vs-configuration. Retrieved 13 March 2020. 
  20. "The Benefits of a configurable COTS LIMS". Promium, LLC. https://www.promium.com/resources/news-articles/the-benefits-of-a-configurable-off-the-shelf-lims-cots/. Retrieved 13 March 2020. 
  21. Patel, S. (24 September 2019). "How labs can benefit from LIS to EHR connectivity". Medical Laboratory Observer. https://www.mlo-online.com/information-technology/ehrs/article/21106468/how-labs-can-benefit-from-lis-to-ehr-connectivity. Retrieved 18 March 2020. 
  22. Elliot, M.H. (December 2006–January 2007). "The state of the ELN Market". Scientific Computing World. https://www.scientific-computing.com/feature/state-eln-market?feature_id=50. Retrieved 17 March 2020. 
  23. Elliot, Michael H. (October 2011). "Informatics Convergence Presents Opportunities and Challenges". Scientific Computing. Archived from the original on 17 April 2016. https://web.archive.org/web/20160417085757/https://www.scientificcomputing.com/articles/2011/11/informatics-convergence-presents-opportunities-and-challenges. Retrieved 17 March 2020. 
  24. "SLIMS: Manage your lab data in one place". Genohm SA. https://www.genohm.com/. Retrieved 17 March 2020. 
  25. Williams, R.W. (2003). "Managing Your Lab Data Flux: Getting Beyond Excel" (PDF). The Bioinformatics of Brains: From Genes and Proteins to Behaviors. Society for Neuroscience. Archived from the original on 16 June 2010. https://web.archive.org/web/20100616100719/http://www.sfn.org/skins/main/pdf/ShortCourses/2003/sc1_9.pdf. Retrieved 17 March 2020. 
  26. Howard, D.A.; Harrison, D. (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. 
  27. "Excel Interface". Mountain States Consulting, LLC. https://www.msc-lims.com/demo/excelinterface.html. Retrieved 17 March 2020. 
  28. "LIMS Quality Control QA/QC". Online LIMS Canada Limited. https://www.onlims.com/product/quality-control-qaqc/. Retrieved 17 March 2020. 
  29. "LISA.lims - The Premier LIMS Solution". Systat Software, Inc. http://www.sigmaplot.co.uk/products/lisa/index.php. Retrieved 06 January 2022. 
  30. CSols, Inc (25 July 2019). "The Value of a Scientific Data Management System (SDMS)". https://www.csolsinc.com/blog/the-value-of-a-scientific-data-management-system-sdms/. Retrieved 17 March 2020. 
  31. Harris, J. (20 September 2018). "What Is A Data Warehouse? A Tutorial For Beginners". Panoply Blog. Panoply Technologies, Inc. https://blog.panoply.io/what-is-a-data-warehouse-a-tutorial-for-beginners. Retrieved 17 March 2020. 
  32. "Workflow Management Coalition Terminology & Glossary" (PDF). Workflow Management Coalition. February 1999. pp. 9. Archived from the original on 14 March 2015. https://web.archive.org/web/20150314125903/http://www.wfmc.org/standards/docs/TC-1011_term_glossary_v3.pdf. Retrieved 06 January 2022. 
  33. Maxwell, G. (1 November 2003). "Using Workflows in LIMS to Reduce Customization". Scientific Computing. Archived from the original on 07 August 2009. https://web.archive.org/web/20090807034051/http://www.scientificcomputing.com/using-workflows-in-lims-to-reduce.aspx. Retrieved 17 March 2020. 
  34. Feist, K. (22 July 2011). "Harnessing Laboratory Information Systems to Support Increased Capacity and Staff Productivity". LabCompare. Archived from the original on 21 September 2015. https://web.archive.org/web/20150921215023/http://www.labcompare.com/10-Featured-Articles/19389-Harnessing-Laboratory-Information-Systems-to-Support-Increased-Capacity-and-Staff-Productivity/. Retrieved 18 March 2020. 
  35. "ASTM E1578 - 18 Standard Guide for Laboratory Informatics". ASTM International. https://www.astm.org/Standards/E1578.htm. Retrieved 17 March 2020. 
  36. "Elekta - Laboratory Information System". Elekta AB. Archived from the original on 22 April 2012. https://web.archive.org/web/20120422205830/http://www.elekta.com/healthcare-professionals/products/elekta-software/clinical-laboratory/laboratory-information-system.html. Retrieved 18 March 2020. 
  37. "Horizon Lab Financials". McKesson Corporation. Archived from the original on 21 May 2013. https://web.archive.org/web/20130521025202/http://www.mckesson.com/en_us/McKesson.com/For+Healthcare+Providers/Hospitals/Laboratory+Solutions/Horizon+Lab+Financials.html. Retrieved 18 March 2020. 
  38. Owens, S.R.; Dhir, R.; Yousem, S.A. et al. (June 2010). "The development and testing of a laboratory information system-driven tool for pre-sign-out quality assurance of random surgical pathology reports". American Journal of Clinical Pathology 133 (6): 836–41. doi:10.1309/AJCPLN9DU9LNXSXA. PMID 20472840. 
  39. "Netlims - AutoQuality". NeTLIMS NJ, LLC. Archived from the original on 20 December 2011. https://web.archive.org/web/20111220065137/http://www.netlims.com/lis_software_autoquality.asp. Retrieved 18 March 2020. 
  40. "CLIN1 Laboratory Quality Control Software". Clin1, LLC. https://clin1mobile.net/quality-control. Retrieved 18 March 2020. 
  41. "Title 21: Food and Drugs - Chapter 1: Food and Drug Administration, Department of Health and Human Services, Subchapter A: General - Part 11: Electronic Records; Electronic Signatures". U.S. Food and Drug Administration. https://www.accessdata.fda.gov/scripts/cdrh/cfdocs/cfcfr/CFRSearch.cfm?CFRPart=11. Retrieved 18 March 2020. 
  42. McDowall, R.D. (June 2016). "How Can LIMS Help Ensure Data Integrity?" (PDF). LC-GC Europe. https://rx-360.org/wp-content/uploads/2018/08/How-Can-LIMS-Help-Ensure-Data-Integrity-by-R.D.-McDowall-2016.pdf. Retrieved 18 March 2020. 
  43. LabVantage Solutions (14 September 2019). "Data Integrity is Here. What Does it Mean for CMOs?". LabVantage Blog. https://www.labvantage.com/data-integrity-is-here-what-does-it-mean-for-cmos/. Retrieved 18 March 2020. 
  44. Jones, A.; Valli, C. (2009). "Chapter 1: An Introduction to Digital Forensics". Building a Digital Forensic Laboratory: Establishing and Managing a Successful Facility. Butterworth-Heinemann. p. 11. ISBN 9781856175104. https://books.google.com/books?id=F5IU7XXKwCQC. 
  45. Tomlinson, J. J.; Elliott-Smith, W.; Radosta, T. (2006). "Laboratory Information Management System Chain of Custody: Reliability and Security" (in en). Journal of Automated Methods and Management in Chemistry 2006: 1–4. doi:10.1155/JAMMC/2006/74907. ISSN 1463-9246. PMC PMC1903459. PMID 17671623. http://www.hindawi.com/journals/jamc/2006/074907/abs/. 
  46. "Quality Assurance - Data Management" (PDF). Stable Isotope Ratio Facility for Environmental Research (SIRFER) at the University of Utah. Archived from the original on 17 November 2011. https://web.archive.org/web/20111117174948/http://sirfer.utah.edu/qaqc.pdf. Retrieved 18 March 2020. 
  47. Hitchcock, N. (2005). "Chapter 10: Efficient utilization of LIMS data and integration with mining process management systems". In Dessureault, S.D.; Ganguli, R.; Kecojevic, V.; Dwyer, J.G.. Application of Computers and Operations Research in the Mineral Industry. Taylor & Francis. pp. 85–88. ISBN 9780415374491. 
  48. Turner, E.; Bolton, J. (2001). "Required steps for the validation of a Laboratory Information Management System". Quality Assurance 9 (3–4): 217–224. doi:10.1080/713844028. PMID 12553085. 
  49. Al-Issa, Y.; Ottom, M.A.; Tamrawi, A. (2019). "eHealth Cloud Security Challenges: A Survey". Journal of Healthcare Engineering 2019: 7516035. doi:10.1155/2019/7516035. PMC PMC6745146. PMID 31565209. https://www.ncbi.nlm.nih.gov/pmc/articles/PMC6745146. 
  50. Monkey, S. (23 January 2017). "The value of a control file when writing data files". ShortStories: Tales from software development. https://corengen.wordpress.com/2017/01/23/the-value-of-a-control-file-when-writing-data-files/. Retrieved 18 March 2020. 
  51. Tsyktor, V. (30 December 2017). "How to Build a Data Backup Service for SaaS". Apriorit Dev Blog. https://www.apriorit.com/dev-blog/492-build-data-backup-service-saas. Retrieved 18 March 2020. 
  52. Amin, W.; Sirintrapun, S.J.; Parwani, A.V. (2010). "Utility and applications of synoptic reporting in pathology". Open Access Bioinformatics 2010 (2): 105–12. doi:10.2147/OAB.S12295. 
  53. 53.0 53.1 Gilles, C. (1 July 2008). "Bar Code and Sample Tracking: It All Starts with the Label". Scientific Computing. Archived from the original on 18 December 2010. https://web.archive.org/web/20101218190848/http://www.scientificcomputing.com/bar-code-and-sample-tracking.aspx. Retrieved 18 March 2020. 
  54. "The Hidden Power of Barcodes". CSols, Inc. 8 February 2018. https://www.csolsinc.com/blog/hidden-power-barcodes/. Retrieved 18 March 2020. 
  55. Haigney, S. (18 November 2018). "The Fax Is Not Yet Obsolete". The Atlantic. https://www.theatlantic.com/technology/archive/2018/11/why-people-still-use-fax-machines/576070/. Retrieved 18 March 2020. 
  56. Pavlis, R. (May/June 2004). "Trends in instrument-to-LIMS interfacing". Scientific Computing World. Archived from the original on 10 September 2015. https://web.archive.org/web/20150910043807/http://www.scientific-computing.com/features/feature.php?feature_id=88. Retrieved 18 March 2020. 
  57. DeHeer, L. (1 October 2009). "Instrument Interfacing - The Great Paradox of LIMS?". Blaze Systems Corporation. https://www.blazesystems.com/white-papers/instruments/. Retrieved 07 January 2022. 
  58. Curtis Jr., D. (12 December 2019). "Benefits and Best Practices for Integrating Laboratory Instruments with LIMS". Astrix Lab Informatics Blog. https://astrixinc.com/benefits-and-best-practices-for-integrating-laboratory-instruments-with-lims/. Retrieved 18 March 2020. 
  59. "Section 3: Clinical and Administrative Domains - HL7 Version 2.7 Standard: Chapter 13 - Clinical Laboratory Automation". HL7. http://www.hl7.org/implement/standards/product_brief.cfm?product_id=203. Retrieved 18 March 2020. 
  60. Ryan, M. (28 August 2019). "Mobile LIMS Applications in the Laboratory". The Connected Lab. Thermo Fisher Scientific. https://www.thermofisher.com/blog/connectedlab/mobile-lims-applications-in-the-laboratory/. Retrieved 18 March 2020. 
  61. "O3 LimsXpress". Bytewize AB. https://www.bytewize.com/o3limsxpress. Retrieved 18 March 2020.