Electronic lab notebook

{{Short description|Computer program designed to replace paper lab notebooks}}

An electronic lab notebook or electronic laboratory notebook (ELN) is a computer program designed to replace paper laboratory notebooks. Lab notebooks in general are used by scientists, engineers, and technicians to document research, experiments, and procedures performed in a laboratory. A lab notebook is often maintained to be a legal document and may be used in a court of law as evidence. Similar to an inventor's notebook, the lab notebook is also often referred to in patent prosecution and intellectual property litigation.

Electronic lab notebooks offer many benefits to the user as well as organizations; they are easier to search upon, simplify data copying and backups, and support collaboration amongst many users.{{cite conference |

title = A Collaborative Electronic Notebook |

first = James |

last = Myers |author2=Elena Mendoza |author3=Bonnie Hoopes |

journal = Proceedings of the IASTED International Conference on Internet and Multimedia Systems and Applications |

year = 2001

}}

ELNs can have fine-grained access controls, and can be more secure than their paper counterparts.{{cite conference |

last = Myers |

first = James |

year = 2003 |

journal = Proceedings of the 2003 International Symposium on Collaborative Technologies and Systems |

title = Collaborative Electronic Notebooks as Electronic Records:Design Issues for the Secure Electronic Laboratory Notebook (ELN) |

url = http://collaboratory.emsl.pnl.gov/resources/publications/papers/seceln(final1)1-22Nov.pdf |

access-date = 2011-12-12 |

archive-url = https://web.archive.org/web/20111015000043/http://collaboratory.emsl.pnl.gov/resources/publications/papers/seceln(final1)1-22Nov.pdf |

archive-date = 2011-10-15 |

url-status = dead }} They also allow the direct incorporation of data from instruments, replacing the practice of printing out data to be stapled into a paper notebook.{{Cite journal | last1 = Perkel | first1 = J. M. | title = Coding your way out of a problem | journal = Nature Methods | volume = 8 | issue = 7 | pages = 541–543 | year = 2011 | pmid = 21716280 | doi = 10.1038/nmeth.1631| s2cid = 13175560 | doi-access = free }}

Types

ELNs can be divided into two categories:

"Specific ELNs" contain features designed to work with specific applications, scientific instrumentation or data types.
"Cross-disciplinary ELNs" or "Generic ELNs" are designed to support access to all data and information that needs to be recorded in a lab notebook.
Lab Platforms that combine an ELN, LIMS, and scientific data management together, all-in-one configurable software environment.

Solutions range from specialized programs designed from the ground up for use as an ELN, to modifications or direct use of more general programs. Examples of using more general software as an ELN include using OpenWetWare, a MediaWiki install (running the same software that Wikipedia uses), WordPress,{{Cite journal |last1=Voegele |first1=Catherine |last2=Bouchereau |first2=Baptiste |last3=Robinot |first3=Nivonirina |last4=McKay |first4=James |last5=Damiecki |first5=Philippe |last6=Alteyrac |first6=Lucile |date=2013-05-03 |title=A universal open-source Electronic Laboratory Notebook |url=https://academic.oup.com/bioinformatics/article/29/13/1710/200295 |journal=Bioinformatics |volume=29 |issue=13 |pages=1710–1712 |doi=10.1093/bioinformatics/btt253 |pmid=23645817 |issn=1367-4803}} or the use of general note taking software such as OneNote as an ELN.{{Cite journal|date=2019-05-09|title=A quick guide for using Microsoft OneNote as an electronic laboratory notebook|doi=10.1371/journal.pcbi.1006918 |doi-access=free |last1=Guerrero |first1=Santiago |last2=López-Cortés |first2=Andrés |last3=García-Cárdenas |first3=Jennyfer M. |last4=Saa |first4=Pablo |last5=Indacochea |first5=Alberto |last6=Armendáriz-Castillo |first6=Isaac |last7=Zambrano |first7=Ana Karina |last8=Yumiceba |first8=Verónica |last9=Pérez-Villa |first9=Andy |last10=Guevara-Ramírez |first10=Patricia |last11=Moscoso-Zea |first11=Oswaldo |last12=Paredes |first12=Joel |last13=Leone |first13=Paola E. |last14=Paz-y-Miño |first14=César |journal=PLOS Computational Biology |volume=15 |issue=5 |pages=e1006918 |pmid=31071077 |pmc=6508581 |bibcode=2019PLSCB..15E6918G }}

ELN's come in many different forms. They can be standalone programs, use a client-server model, or be entirely web-based. Some use a lab-notebook approach, others resemble a blog. ELNs are embracing artificial intelligence and LLM technology to provide scientific AI chat assistants.

A good many variations on the "ELN" acronym have appeared.{{Cite web|url=https://www.labii.com/|title=Labii ELN & LIMS|date=2017-04-30|language=en-US|access-date=2017-04-30}}{{Cite web|url=http://cerf-notebook.com/articles/eln-glossary/|title=Lab Notebook (ELN) Glossary - CERF|date=2016-02-16|language=en-US|access-date=2016-08-20}} Differences between systems with different names are often subtle, with considerable functional overlap between them. Examples include "ERN" (Electronic Research Notebook), "ERMS" (Electronic Resource (or Research or Records) Management System (or Software) and SDMS (Scientific Data (or Document) Management System (or Software). Ultimately, these types of systems all strive to do the same thing: Capture, record, centralize and protect scientific data in a way that is highly searchable, historically accurate, and legally stringent, and which also promotes secure collaboration, greater efficiency, reduced mistakes and lowered total research costs.

Objectives

A good electronic laboratory notebook should offer a secure environment to protect the integrity of both data and process, whilst also affording the flexibility to adopt new processes or changes to existing processes without recourse to further software development. The package architecture should be a modular design, so as to offer the benefit of minimizing validation costs of any subsequent changes that you may wish to make in the future as your needs change.

A good electronic laboratory notebook should be an "out of the box" solution that, as standard, has fully configurable forms to comply with the requirements of regulated analytical groups through to a sophisticated ELN for inclusion of structures, spectra, chromatograms, pictures, text, etc. where a preconfigured form is less appropriate. All data within the system may be stored in a database (e.g. MySQL, MS-SQL, Oracle) and be fully searchable. The system should enable data to be collected, stored and retrieved through any combination of forms or ELN that best meets the requirements of the user.

The application should enable secure forms to be generated that accept laboratory data input via PCs and/or laptops / palmtops, and should be directly linked to electronic devices such as laboratory balances, pH meters, etc. Networked or wireless communications should be accommodated for by the package which will allow data to be interrogated, tabulated, checked, approved, stored and archived to comply with the latest regulatory guidance and legislation. A system should also include a scheduling option for routine procedures such as equipment qualification and study related timelines. It should include configurable qualification requirements to automatically verify that instruments have been cleaned and calibrated within a specified time period, that reagents have been quality-checked and have not expired, and that workers are trained and authorized to use the equipment and perform the procedures.

Regulatory and legal aspects

The laboratory accreditation criteria found in the ISO 17025 standard needs to be considered for the protection and computer backup of electronic records. These criteria can be found specifically in clause 4.13.1.4 of the standard."ISO/IEC 17025:2005 - General Requirements for the Competence of Testing and Calibration Laboratories." ISO - International Organization for Standardization. Web. 16 Nov. 2011. .

Electronic lab notebooks used for development or research in regulated industries, such as medical devices or pharmaceuticals, are expected to comply with FDA regulations related to software validation. The purpose of the regulations is to ensure the integrity of the entries in terms of time, authorship, and content. Unlike ELNs for patent protection, FDA is not concerned with patent interference proceedings, but is concerned with avoidance of falsification. Typical provisions related to software validation are included in the medical device regulations at 21 CFR 820 (et seq.)United States. Food and Drug Administration. Department of Health and Human Resources. 1 Food and Drugs - Subchapter H Medical Devices - Part 820 System RegCode of Federal Regulations - Title 2ulation. FDA.gov, 7 Oct. 1996. Web. . and Title 21 CFR Part 11.United States. Food and Drug Administration. Department of Health and Human Resources. Code of Federal Regulations - Title 21 Part 11 Electronic Records; Electronic Signatures. FDA.gov. Authority: 21 U.S.C. 321-393; 42 U.S.C. 262., 20 Mar. 1997. Web. 16 Nov. 2011. . Essentially, the requirements are that the software has been designed and implemented to be suitable for its intended purposes. Evidence to show that this is the case is often provided by a Software Requirements Specification (SRS) setting forth the intended uses and the needs that the ELN will meet; one or more testing protocols that, when followed, demonstrate that the ELN meets the requirements of the specification and that the requirements are satisfied under worst-case conditions. Security, audit trails, prevention of unauthorized changes without substantial collusion of otherwise independent personnel (i.e., those having no interest in the content of the ELN such as independent quality unit personnel) and similar tests are fundamental. Finally, one or more reports demonstrating the results of the testing in accordance with the predefined protocols are required prior to release of the ELN software for use. If the reports show that the software failed to satisfy any of the SRS requirements, then corrective and preventive action ("CAPA") must be undertaken and documented. Such CAPA may extend to minor software revisions, or changes in architecture or major revisions. CAPA activities need to be documented as well.

Aside from the requirements to follow such steps for regulated industry, such an approach is generally a good practice in terms of development and release of any software to assure its quality and fitness for use. There are standards related to software development and testing that can be applied (see ref.).

Electronic lab notebook

Types

Objectives

Regulatory and legal aspects

See also

References

Further reading