Electric note books

The Electric Notebook

2009-06-10T09:36:00.000-07:00

It's an Electric Notebook. No, what does it really look like. I've kept a notebook for years. I used it mostly for work so I can keep track of what I've ...lincoln.midcoast.com/~ian/notebook.html - Cached - Similar pages -

Ease of Use

2009-06-05T02:12:00.000-07:00

The first key to ease of use and wide acceptance of the electronic notebook is to not deviate too far from the functionality of the basic paper notebook. The initial goal would be to reproduce standard practice in an electronic format. Standard practice for a notebook varies from a single researcher jotting down personal thoughts to a group of scientists recording instrument settings and results. It does not make sense to burden the basic notebook design with features that may never be used and just serve to complicate the user interface.
The second key to ease of use is create an interface that provides intuitive entry of information. A researcher should be able to figure out how to use the electronic notebook without having to read a user manual. The electronic notebook should provide quick and simple methods for inputing text and sketches just like paper notebooks. It should also provide common methods of computer input such as cut/paste, drag/drop, and insert file.
The information that needs to be input into a notebook varies from project to project and researcher to researcher. The desire to have any type of information easy to enter requires that the input interface be expandable. In DOE2000 we proposed to use object oriented technology to provide this expandability. We called these NObs (notebook objects). Objects are entered into the notebook. There could be text objects, sketch objects, figure objects, file objects, video objects, etc... The notebook user or third parties could extend the type of objects supported in order to customize a particular notebook. Our present research involves using XML to define our multi-object entries.
Electronic Notebook Demonstration to Vice President Gore

Electronic lab notebook

2009-06-05T02:08:00.000-07:00

An electronic lab notebook (also known as electronic laboratory notebook, or ELN) is a software program designed to replace paper laboratory notebooks. Lab notebooks in general are used by scientists 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 are a fairly new technology and offer many benefits to the user as well as organizations. For example electronic lab notebooks are easier to search upon, support collaboration amongst many users, and can be made more secure than their paper counterparts.
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.
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.
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.) and 21 CFR 11. 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.