IT systems · Practical guide

Validating eLabJournal: tracing an experiment back to its protocol

An eLabJournal experiment links a sample and a result. Which protocol version was used, was a local change intentional and where is the original measurement file? Trace these relationships before choosing the supplier evidence and local tests needed for the actual laboratory process.

Table of contents

At a glance

How do you validate eLabJournal for your laboratory process?

Define which laboratory records eLabJournal should hold and which decisions depend on them. Identify the version, deployment model, add-ons and connected systems. Test links between protocol template, experiment, sample, file and assessment, including corrections and access. Use supplier evidence within its scope. An electronic laboratory notebook does not by itself turn research into a GMP activity.

  • eLabJournal is part of the eLabNext documentation line within the current SciSure environment; Labfolder is a standalone ELN.
  • Draft version and experiment-specific processing must remain distinguishable.
  • A sample link does not imply automatic quantity posting or subject-matter release.
  • Release channel, add-ons, and full data export fall within the system boundary.

Research and GMP application based on the decision to differentiate

Start with a specific test and its result recipient. Is the documentation intended for exploratory research, method development, or a quality-related decision in routine operations? These purposes may coexist within the same laboratory. Describe which data will be used for downstream applications and at which stage a technical evaluation will take place.

This article considers human medicinal product GMP as a defined regulatory application scenario. The current EudraLex index references Annex 11 and Chapter 4 as of January 2011. Annex 11 is a GMP guideline for computerised systems. GLP, clinical research, and medical devices require separate classification; manufacturer statements for these areas do not supersede them.

A meaningful first requirement might be: The reviewer can determine which sample was tested according to which instruction and which original data support the reported result. From this, you develop your review process. Whether the laboratory notebook serves as the primary recording system, supplementary documentation, or recipient of results significantly alters the scope and priorities.

Sources: [1] [2] [3]

Product line, release channel, and utilized components to be documented

The previous eLabNext web address now redirects to SciSure. The technical support still uses eLabNext and describes the eLabJournal-related ELN functionalities. Maintain the name of the actually deployed product in the system inventory. The shared vendor framework does not make eLabJournal and Labfolder functionally equivalent or interchangeable validation objects.

The release notes document V2.92.0 for EU and US cloud on September 30, 2026. Dedicated installations follow their own deployment dates. This information therefore does not show a uniform current state of all installations. Capture your actual version including add-ons and operating form.

SciSure describes cloud, private cloud, and on-premises deployment models. Clarify in your contract which party is responsible for updates, backup, recovery, and access management. The following internal matrix helps distribute the required evidence. This is not a claimed standard license and does not constitute a complete product listing.

Own matrix for eLabJournal documentation pathway
ComponentSubject matterPreceding note on the need for clarification of the evidence
Protocol template Specified work steps and parameters Version and operational usability
Experiment section Actual documented execution Local changes and template used
Sample linking Material used or produced Identity, Direction and Historical Context
Measurement file / Evaluation Basis of the reported results Source, assignment, and processing status
Signatur-Add-on Expected confirmation Installed Scope, Roles, and Significance
Hosting / Export Availability and subsequent use Operator responsibilities and readable, complete scope

Sources: [4] [5] [6]

The protocol template and execution are distinct objects.

The assistance describes new protocols initially as drafts. They can only be shared or used as templates after finalization. For your operation, it is additionally necessary to determine when such a template may be used professionally. The technical action "Finalize" does not automatically equate to internal approval.

When inserting a procedure section, a reference is established to the version of the protocol in use. Modifications to this section pertain to the current experiment and, according to the manufacturer, do not alter the original protocol version. This distinction is particularly relevant for audit purposes: a deviation in a single experiment must not be perceived as an unchanged execution of the original protocol.

Plan a trial using version 1, then systematically update the template and initiate a second trial. Compare both versions. Independently evaluate the restart function, which allows dynamic values to be reset. Prior to doing so, define when a restart is technically justified and ensure that previously documented execution and corrections remain traceable.

Sources: [7] [8] [3]

Distinguish Used Samples, Generated Samples and stock

A Sample Section can link used or experiment-generated samples. The manufacturer distinguishes between Used Samples and Generated Samples; the sample displays its associated experiments. This enables documentation of relationships. Whether the correct sample was selected and the direction was accurately specified remains part of the technical assessment.

Archiving and removal from a section are distinct actions. The manufacturer's guide explicitly states that an archived sample continues to appear within the Sample Section. Verify this distinction using a previously documented execution: a subsequent inventory status must not obscure the historical sample identity.

From the linking of a sample, no conclusive automatic consumption booking is established. When quantities are relevant, specify the leading quantity field or the separate inventory procedure. Verify units, partial withdrawals, and repeated entries. The same applies to generated samples: a relationship alone does not prove physical production, analytical suitability, or release.

Sources: [9] [2]

Original data, experiment logs, and section history are linked

Assign the actual required source data to each result statement. This may include a device measurement file, a processed analysis, and supplementary observations. Identify the primary storage location and the path to the laboratory notebook. An embedded image may facilitate presentation, but it does not constitute evidence that all data relevant to the analysis are fully retained.

The manufacturer support document separates the experiment log for general changes, such as personnel involved and status, from the log of individual sections. For certain section types, it also includes a version history. A restored version is treated as a new version with the corresponding timestamp. This description should not be unverifiedly applied to every file type or additional module component.

A suitable test case corrects a file that was initially incorrectly assigned. The examiner should be able to determine which reference existed originally and how the correct assignment was made. Check content and meaning, not only the number of log lines. The desired traceability extends to the system in which the original measurement and, if necessary, its evaluation were made.

Sources: [10] [11] [3]

Further reading:

Example: two samples taken from a single specimen

This example does not represent a completed product release. Probe A-17 initially contains 120 µl. Experiment E-17 uses protocol P-4 version 1 and documents sequential withdrawals of 30 µl and 20 µl. The corresponding measurement files are named E17-1 and E17-2. Both must be retained as separate measurements and correctly assigned to the respective experiment.

The independently calculated required volume is 120 − 30 − 20 = 70 µl. An input of 0.02 ml corresponds to 20 µl. The following verification does not assume built-in automatic volume subtraction; it instead validates the actually implemented volume pathway, whether within the system, via an interface, or through a manually controlled regulated step.

For each error scenario, the same documented initial state is restored or a distinct, uniquely identified data record is created. The protocol template, access rights, and file contents remain under control. An appropriate closing statement not only confirms that 70 µl is displayed, but also verifies that sample, execution, measurements, and volume changes are logically consistent.

Own required matrix for E-17; manufacturer automation is not required
Case / SituationActionIndependently established expected resultTo be investigated error
Normal case: A-17, 120 µl Withdraw and document 30 µl and 20 µl. Remaining 70 µl; two correct measurement files Wrong sample or omitted withdrawal
Unit case: A-17, 120 µl 30 µl and 0.02 ml are documented Remaining 70 µl after clear conversion 0.02 is incorrectly treated as µl
Repeat under normal circumstances Initiate a second quantity change again No unobserved additional withdrawal Additional 20 µl would reduce residue to 50 µl.
File error Replace E17-2 with a file from another test. Inappropriate reference identified and reviewed, corrected Hidden file name masks other origin
Template change Provide P-4 Version 2 for the new study. E-17 remains attributable to the applicable current state. A new template changes how earlier work appears
Archived sample A-17 to be archived upon completion Historical reference in E-17 remains understandable Archiving with removal of the relation mistakenly overlooked

Sources: [8] [9] [2]

Define signing authority and the meaning of the signature in the actual process

Name the individuals who perform experiments, add data, evaluate results, and modify configurations. In a small laboratory, personnel may undertake multiple responsibilities. What is critical is determining whether independent review of your procedure is required and whether potential conflicts of interest or unauthorized changes need to be prevented. A mere job title does not provide sufficient evidence for this.

The signature workflow add-on describes project-specific signature and witness processes involving selected individuals or roles. Verify its actual installation and configuration. For each used approval, define whether it specifically relates to, for example, execution, technical review, or another decision. A button does not replace this intended meaning.

Test a valid user role change, an invalid confirmation attempt, and a revoked access. Additionally, evaluate the handling of a subsequent required correction. Electronic signature requirements arise from the specific process and regulatory domain. Not every research note requires an electronic signature by default, and the designation of research does not exempt a genuinely regulated record from its associated requirements.

Sources: [12] [2]

Verify exportability with the required data volume.

Define prior to export what must be traceable thereafter: execution, protocol reference, samples used and generated, relevant files, corrections, and evaluations. A readable closing report may constitute part of this. Whether structured data or original files are required additionally depends on their significance and the intended subsequent audits.

The release notes for V2.92.0 indicate a correction for scientific special characters in XML and JSON ELN exports. This gives rise to a specific, standalone test: for example, use "µl" and a scientific identifier containing a Greek character, then compare the display and interpretation before and after the intended export. The mere presence of an exported file is insufficient for this validation.

Verify access using the intended future reader role and appropriate tools. Also define actions to be taken at contract end or upon departure of the original user. The required retention period is derived from the purpose of recordkeeping and applicable requirements; product functionality neither automatically determines the retention period nor ensures an adequate archiving solution.

Sources: [5] [3] [2]

Further reading:

Supplier documentation and amendments referenced on your traceability pathway

Request documentation for the actually deployed version and scope. Map requirements, covered functions, configuration, test conditions, results, and known limitations to one another. An appropriate vendor package may include usable evidence, but it does not inherently cover all aspects and is not generally limited to unconfigured standard functions.

Prioritize remaining in-house inspections at the transition points of your laboratory. An add-on, a modified sample field type, or a new export pathway may have implications beyond a simple change in display. Describe affected data and error scenarios prior to defining the required test scope. A blanket full revalidation after each update cannot be inferred therefrom.

For existing installations, a clear and traceable configuration state and selected historical data sets can provide support. Compare open and closed experiments, as well as typical corrections. Document the gaps that need to be addressed and the resulting operational decisions. Public assistance does not substitute for verification of your actual installation.

Sources: [5] [6] [2]

Establish a functional start with Laboratory, QA, and IT teams

The department must be able to explain the study, its data, and the subsequent decisions. QA will identify the applicable regulatory requirements and required controls; IT and system owners will provide information on operations, access rights, interfaces, and recovery procedures. The supplier will provide version-specific details. Additionally, agree on who will determine technical acceptance and any remaining limitations.

A clear pilot process is prioritized during an introduction. In the existing environment, historical documentation and established exception routes are supplemented. During a change, the affected segment is critical. Effort and duration are particularly influenced by the number of source documents, add-ons, raw data pathways, and pre-existing usable evidence. Without such information, a general time or cost estimate is largely unreliable.

  • Define the specific laboratory process and state the allowable use of the results.
  • Product status, hosting, add-ons, and responsible operators to be documented.
  • Provide protocol versions and rules for local modifications.
  • Explain sample identities, volume routes, units, and original files.
  • Roles and the importance of testing and signatures are agreed.
  • Prepare test data sets with initial state and independent desired state.
  • Assign supplier documentation to own requirements and open items.
  • Plan export, recovery, modification, and future access.

Sources: [2] [6]

Project experience and collaboration

Keep the experiment, sample and original file linked

With your laboratory, we select an experiment with a known protocol, samples and original files. We examine what execution actually records and which relationships must survive retrieval. For limited research use, the first priority may be defining the intended use. Where the electronic lab notebook supports quality decisions, we plan suitable evidence and operating rules. We examine withdrawals, newly created samples and inventory separately. A sample link alone does not establish complete quantity tracking.

Frequent Questions about eLabJournal Documentation

Is eLabJournal today the same as SciSure or Labfolder?

SciSure is today's provider and platform context. The eLabNext help continues to describe the eLabJournal-related functions. Labfolder remains a separately named ELN product line. Therefore, do not incorporate its workflow behavior or license scope into your eLabJournal consideration. The actual application, its version and the contractual and technical components are decisive.

Sources: [4] [13]

Do we need to perform GMP validation for all research studies?

No. The key issue is whether and for what purpose records are used in a GMP process. Exploratory research and an electronic record serving as the basis for a GMP quality decision have distinct requirements. Later data transfers must also be described. If an originally exploratory dataset is subsequently used for regulatory purposes, its suitability for this purpose must be assessed; the original storage location does not automatically confer release.

Sources: [2] [3]

Which eLabJournal version should be included in our validation documentation?

Record the version you actually run, its relevant add-ons, configuration and deployment model. The cloud release history lists V2.92.0 on 30 September 2026. Dedicated installations follow separate schedules. Ask the system owner to confirm the version in your environment and link the evidence for that version.

Sources: [5]

Does a corrected procedure also alter the original document version?

The assistance describes modifications to the inserted Procedure Section as study-specific; these changes do not alter the original document. However, verify the specific historical context and traceability of the amendment. A change to the document itself constitutes a separate action. Test both approaches independently to ensure that a previous study does not inadvertently appear to have been conducted according to the updated procedure.

Sources: [8]

Is the amount automatically deducted when a sample is linked?

The Sample Section Help establishes links between used and generated samples, but does not provide general automated consumption tracking. Determine how volumes are actually managed within your facility. If they are decision-critical, verify aliquot withdrawals, units, repetitions, and corrections against an independent volume target. A correct sample linkage and an accurate remaining balance are distinct forms of validation evidence.

Sources: [9]

What happens to an archived sample request?

With manufacturer support, an archived sample remains listed in the Sample Section. Removal from the section requires a separate action. At the conclusion of an experiment, verify whether the identity and relevance of the reference remain clearly traceable. The mere presence of a link does not confirm that all information required for your future evaluation will remain accessible.

Sources: [9]

Does the experiment log serve as a complete record of changes?

Not without evaluation of the required scope. The support distinguishes between general process changes and section-specific changes. For certain sections, a version history is also available. Assign specific, relevant changes to the corresponding validation evidence and integrate external measurement or evaluation systems. A large volume of existing log entries does not prove their completeness nor their technical clarity.

Sources: [10] [11] [2]

Does every experiment require a witness?

An additional review shall be defined for the specific process, not solely due to the use of an electronic laboratory notebook. The signature workflow add-on enables project-specific assignment of individuals or roles. Determine whether a witness is required and what he or she shall confirm. Subsequently, review the selected configuration including delegation, access revocation, and any necessary corrections.

Sources: [12] [2]

What documents and personnel do we need prior to project start?

The following are required: at least a clear process, actual system scope, representative protocols and data pathways, as well as available supplier documentation. Laboratory personnel, QA, and IT must be able to contribute their respective decisions. A responsible individual for technical acceptance must be designated. A large number of template variations, unknown add-ons, and unclear original data locations increase the effort required for clarification; therefore, a fixed project duration cannot be generally inferred.

Sources: [2] [6]

Can an export provide sufficient evidence of future readability?

A successfully generated export serves as a starting point. Compare scope, characters, units, linkages, and required original files against the predefined expected specifications. Open it under the anticipated future conditions. Additionally assess protection, access, and recovery capabilities over the required duration. The release correction for special characters highlights the need for explicit verification of format and meaning.

Sources: [5] [3] [2]

Sources and review date

As of October 6, 2026. The functional descriptions refer to the specified eLabNext help pages and Release Notes. Cloud and Dedicated setups, as well as add-ons, may differ. SciSure platform specifications do not constitute proof of individual license scope.

  1. European Commission: EudraLex Volume 4
  2. EU GMP Annex 11: Computerised Systems
  3. EU GMP Chapter 4: Documentation
  4. SciSure: Platform and Origin
  5. 2026 eLabNext Release Notes
  6. SciSure Hosting Options
  7. Adding Protocols
  8. Procedure Section
  9. Sample Section
  10. Experiment Log
  11. Restoring Section Versions
  12. Signature workflow | Add-on
  13. Labfolder by SciSure

Sources checked: .

Daniel Herrmann, Daniel Herrmann Consulting

Daniel Herrmann Consulting

Review the eLAB Journal audit trail purposefully

We support you in integrating laboratory processes, data flows, and existing evidence, and in defining appropriate tests for your specific facility.

  • Computer system validation →

    Bring your GxP systems into validated operation, from laboratory software, MES and eQMS to ERP. We define the scope, plan risk-based tests using GAMP 5 and hand the evidence to QA for release.

Send a project enquiry Customer testimonials →