Electronic lab notebook

<h2 id="types">Types</h2>
ELNs can be divided into two categories:

<ul><li>"Specific ELNs" contain features designed to work with specific applications, scientific instrumentation or data types.</li>
<li>"<a href="/facts/Cross-disciplinary/pKoQHpYL">Cross-disciplinary</a> ELNs" or "Generic ELNs" are designed to support access to all data and information that needs to be recorded in a lab notebook.</li>
<li>Lab Platforms that combine an ELN, LIMS, and scientific data management together, all-in-one configurable software environment.</li></ul>
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 <a href="/facts/OpenWetWare/hU1km6p8">OpenWetWare</a>, a <a href="/facts/MediaWiki/MbkLUTor">MediaWiki</a> install (running the same software that Wikipedia uses), <a href="/facts/WordPress/mrrCX1Fx">WordPress</a>,<a class="footnote-ref" id="fnref:4" href="#fn:4">4</a> or the use of general note taking software such as OneNote as an ELN.<a class="footnote-ref" id="fnref:5" href="#fn:5">5</a><a class="footnote-ref" id="fnref:6" href="#fn:6">6</a>
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.<a class="footnote-ref" id="fnref:7" href="#fn:7">7</a> 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.

<h2 id="objectives">Objectives</h2>
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.

<h2 id="regulatory-and-legal-aspects">Regulatory and legal aspects</h2>
The laboratory accreditation criteria found in the <a href="/facts/ISO_17025/0KNHxUgT">ISO 17025</a> 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.<a class="footnote-ref" id="fnref:8" href="#fn:8">8</a>
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.)<a class="footnote-ref" id="fnref:9" href="#fn:9">9</a> and <a href="/facts/Title_21_CFR_Part_11/RGgQpjPq">Title 21 CFR Part 11</a>.<a class="footnote-ref" id="fnref:10" href="#fn:10">10</a> 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.).

<h2 id="see-also">See also</h2>
<ul><li><a href="/facts/List_of_ELN_software_packages/Nlh6lRqL">List of ELN software packages</a></li>
<li><a href="/facts/Data_management/Cykeqxc7">Data management</a></li>
<li><a href="/facts/Laboratory_informatics/Iq1DTLL2">Laboratory informatics</a></li>
<li><a href="/facts/Jupyter/sN94yfV5">Jupyter</a></li></ul>

<h2 id="further-reading">Further reading</h2>
<ul><li>Taylor, K. T. (2006). "The status of electronic laboratory notebooks for chemistry and biology". Current Opinion in Drug Discovery & Development. 9 (3): 348–353. <a href="/facts/PMID_(identifier)/JlHAvMHt">PMID</a> <a href="https://pubmed.ncbi.nlm.nih.gov/16729731">16729731</a>.</li>
<li>Rubacha, M.; Rattan, A. K.; Hosselet, S. C. (2011). <a href="https://doi.org/10.1016%2Fj.jala.2009.01.002">"A Review of Electronic Laboratory Notebooks Available in the Market Today"</a>. Journal of Laboratory Automation. 16 (1): 90–98. <a href="/facts/Doi_(identifier)/muM9Etpq">doi</a>:<a href="https://doi.org/10.1016%2Fj.jala.2009.01.002">10.1016/j.jala.2009.01.002</a>. <a href="/facts/PMID_(identifier)/JlHAvMHt">PMID</a> <a href="https://pubmed.ncbi.nlm.nih.gov/21609689">21609689</a>.</li>
<li>Schnell, Santiago (2015-09-10). <a href="https://www.ncbi.nlm.nih.gov/pmc/articles/PMC4565690">"Ten Simple Rules for a Computational Biologist's Laboratory Notebook"</a>. PLOS Computational Biology. 11 (9): e1004385. <a href="/facts/Bibcode_(identifier)/9HtdQSGB">Bibcode</a>:<a href="https://ui.adsabs.harvard.edu/abs/2015PLSCB..11E4385S">2015PLSCB..11E4385S</a>. <a href="/facts/Doi_(identifier)/muM9Etpq">doi</a>:<a href="https://doi.org/10.1371%2Fjournal.pcbi.1004385">10.1371/journal.pcbi.1004385</a>. <a href="/facts/ISSN_(identifier)/DPAflDvU">ISSN</a> <a href="https://search.worldcat.org/issn/1553-7358">1553-7358</a>. <a href="/facts/PMC_(identifier)/dX1zMt71">PMC</a> <a href="https://www.ncbi.nlm.nih.gov/pmc/articles/PMC4565690">4565690</a>. <a href="/facts/PMID_(identifier)/JlHAvMHt">PMID</a> <a href="https://pubmed.ncbi.nlm.nih.gov/26356732">26356732</a>.</li></ul>

<h2 id="references">References</h2>

<ol>
<li id="fn:1">Myers, James; Elena Mendoza; Bonnie Hoopes (2001). A Collaborative Electronic Notebook. Proceedings of the IASTED International Conference on Internet and Multimedia Systems and Applications. <a href="#fnref:1" class="footnote-back-ref">↩</a></li>
<li id="fn:2">Myers, James (2003). Collaborative Electronic Notebooks as Electronic Records:Design Issues for the Secure Electronic Laboratory Notebook (ELN) (PDF). Proceedings of the 2003 International Symposium on Collaborative Technologies and Systems. Archived from the original (PDF) on 2011-10-15. Retrieved 2011-12-12. <a href="https://web.archive.org/web/20111015000043/http://collaboratory.emsl.pnl.gov/resources/publications/papers/seceln(final1)1-22Nov.pdf" target="_blank">https://web.archive.org/web/20111015000043/http://collaboratory.emsl.pnl.gov/resources/publications/papers/seceln(final1)1-22Nov.pdf</a> <a href="#fnref:2" class="footnote-back-ref">↩</a></li>
<li id="fn:3">Perkel, J. M. (2011). "Coding your way out of a problem". Nature Methods. 8 (7): 541–543. doi:10.1038/nmeth.1631. PMID 21716280. S2CID 13175560. <a href="https://doi.org/10.1038%2Fnmeth.1631" target="_blank">https://doi.org/10.1038%2Fnmeth.1631</a> <a href="#fnref:3" class="footnote-back-ref">↩</a></li>
<li id="fn:4">Voegele, Catherine; Bouchereau, Baptiste; Robinot, Nivonirina; McKay, James; Damiecki, Philippe; Alteyrac, Lucile (2013-05-03). "A universal open-source Electronic Laboratory Notebook". Bioinformatics. 29 (13): 1710–1712. doi:10.1093/bioinformatics/btt253. ISSN 1367-4803. PMID 23645817. <a href="https://academic.oup.com/bioinformatics/article/29/13/1710/200295" target="_blank">https://academic.oup.com/bioinformatics/article/29/13/1710/200295</a> <a href="#fnref:4" class="footnote-back-ref">↩</a></li>
<li id="fn:5">Guerrero, Santiago; López-Cortés, Andrés; García-Cárdenas, Jennyfer M.; Saa, Pablo; Indacochea, Alberto; Armendáriz-Castillo, Isaac; Zambrano, Ana Karina; Yumiceba, Verónica; Pérez-Villa, Andy; Guevara-Ramírez, Patricia; Moscoso-Zea, Oswaldo; Paredes, Joel; Leone, Paola E.; Paz-y-Miño, César (2019-05-09). "A quick guide for using Microsoft OneNote as an electronic laboratory notebook". PLOS Computational Biology. 15 (5): e1006918. Bibcode:2019PLSCB..15E6918G. doi:10.1371/journal.pcbi.1006918. PMC 6508581. PMID 31071077. <a href="https://www.ncbi.nlm.nih.gov/pmc/articles/PMC6508581" target="_blank">https://www.ncbi.nlm.nih.gov/pmc/articles/PMC6508581</a> <a href="#fnref:5" class="footnote-back-ref">↩</a></li>
<li id="fn:6">Perkel, J. M. (2011). "Coding your way out of a problem". Nature Methods. 8 (7): 541–543. doi:10.1038/nmeth.1631. PMID 21716280. S2CID 13175560. <a href="https://doi.org/10.1038%2Fnmeth.1631" target="_blank">https://doi.org/10.1038%2Fnmeth.1631</a> <a href="#fnref:6" class="footnote-back-ref">↩</a></li>
<li id="fn:7">"Labii ELN & LIMS". 2017-04-30. Retrieved 2017-04-30."Lab Notebook (ELN) Glossary - CERF". 2016-02-16. Retrieved 2016-08-20. <a href="https://www.labii.com/" target="_blank">https://www.labii.com/</a> <a href="#fnref:7" class="footnote-back-ref">↩</a></li>
<li id="fn:8">"ISO/IEC 17025:2005 - General Requirements for the Competence of Testing and Calibration Laboratories." ISO - International Organization for Standardization. Web. 16 Nov. 2011. <http://www.iso.org/iso/Catalogue_detail?csnumber=39883>. <a href="http://www.iso.org/iso/Catalogue_detail?csnumber=39883" target="_blank">http://www.iso.org/iso/Catalogue_detail?csnumber=39883</a> <a href="#fnref:8" class="footnote-back-ref">↩</a></li>
<li id="fn:9">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. <http://www.accessdata.fda.gov/scripts/cdrh/cfdocs/cfcfr/cfrsearch.cfm?cfrpart=820>. <a href="http://www.accessdata.fda.gov/scripts/cdrh/cfdocs/cfcfr/cfrsearch.cfm?cfrpart=820" target="_blank">http://www.accessdata.fda.gov/scripts/cdrh/cfdocs/cfcfr/cfrsearch.cfm?cfrpart=820</a> <a href="#fnref:9" class="footnote-back-ref">↩</a></li>
<li id="fn:10">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. <http://www.accessdata.fda.gov/scripts/cdrh/cfdocs/cfcfr/cfrsearch.cfm?cfrpart=11>. <a href="http://www.accessdata.fda.gov/scripts/cdrh/cfdocs/cfcfr/cfrsearch.cfm?cfrpart=11" target="_blank">http://www.accessdata.fda.gov/scripts/cdrh/cfdocs/cfcfr/cfrsearch.cfm?cfrpart=11</a> <a href="#fnref:10" class="footnote-back-ref">↩</a></li>
</ol>

Electronic lab notebook open-in-new

Electronic lab notebook