IT systems · Practical guide

SampleManager LIMS validation: from test request to approved result

A SampleManager LIMS result depends on the assigned tests, instrument data mapping and what the reviewer can see. Use the product's Inspection Plans, file imports and Chromeleon connection to trace those conditions. The checks give laboratory managers, QA and IT a common basis for defining validation scope.

Table of contents

At a glance

How do you validate SampleManager LIMS?

Validate SampleManager against the GMP laboratory workflows actually configured. Describe the test request, master data, data transfer, calculations and approval sequence. Test normal and failure cases, including outstanding partial tests and changed results. Match supplier evidence to the installed release. Document permissions, data retention and change control. A running LIMS alone does not demonstrate that the laboratory workflow produces the right result.

  • The workflow and master data determine which tests an order actually receives.
  • Inspection plan, authorization, and technical batch release decisions to be considered separately.
  • The File Sweeper and Chromeleon Link are specific test objects with individual components.
  • Original records, migration, and restoration based on complete procedures verify.

Define the scope of SampleManager LIMS, ELN, and LES in relation to Chromeleon

Thermo Fisher Scientific describes SampleManager as a LIMS with additional features for electronic laboratory notebook, controlled laboratory work, and scientific data management. This enables a laboratory to integrate multiple segments of its documentation chain. The specific components actually utilized by your project are determined by release, agreed equipment, configuration, and operating mode.

Chromeleon is an independent chromatography data system. The manufacturer documents a SampleManager–Chromeleon CDS link for bidirectional data exchange. A common vendor or existing connection does not constitute a single auditable object for both systems: sample data acquisition and chromatographic analysis must be separately defined, as must the LIMS task, result evaluation, and report generation.

This guide addresses pharmaceutical GMP processes for human medicinal products. Annex 11 applies to appropriately regulated activities; the additional Part 11 applicability follows the relevant documentation requirements and their electronic implementation. Other laboratory areas require their own assessment. A product brochure does not replace this determination.

Sources: [1] [4] [7] [8]

Workflow and master data determine the inspection task

The manufacturer's FAQ indicates that samples can be manually entered, scheduled via time-based workflows, or recorded through a manifest. The selected workflow controls subsequent processing steps. For validation, it is essential to document which incoming sample triggers specific testing requirements, specifications, and responsible personnel.

A dedicated query is: Do raw material samples undergo the same tests as stability samples, despite differing requirements? Specifically assess automated assignments that users may later notice only with difficulty. A correctly stored order may be technically incomplete if a required test was never established.

Link the requirements to the relevant master data and configurations. This includes, for example, sample type, tests, units, specifications, workflow, and report. Define which version is applicable to ongoing orders and specify how ongoing activities should be handled in the event of changes.

Sources: [2] [7]

Separate inspection plan and authorization deliberately.

SampleManager defines configurable Inspection Plans for data verification. Round Robin enables data review in any sequence; Linear establishes a fixed order. The manufacturer's FAQ differentiates between Authorization and outlines its impact on subordinate data elements. This mechanism warrants a dedicated validation scenario.

Therefore, clarify whether the selected sequence represents only a preferred workflow or is enforced by configuration. Investigate unauthorized release attempts, missing partial inspections, and the correction of already reviewed data. The elements captured during a higher-level action must align with the technical and professional scope of decision-making.

Own decision support tool for review and authorization
DecisionDefine for the actual processTargeted verification
Simultaneously or sequentially May inspectors work independently, or must an assessment be completed beforehand? Second reviewer starts before the first; compare actual behavior
Scope of the inspection A result, a test, or a complete sample request? Still pending subordinate elements remain visible
Authorization Which data are captured with this action? Review higher-level actions with mixed processing statuses
Correction When is a previous assessment required to be re-evaluated? Understand the amended value and previous review together.
Report Which professionally assessed status may be issued? Distinguish between draft and approved editions clearly

Sources: [2] [7]

Verify the ELN and LES against the same technical requirements.

The current product page lists for the ELN, among other features, linked texts, tables, and PDF content. The LES supports step-by-step method execution. Both capabilities serve distinct purposes: an attached instruction does not confirm that each required work step has been correctly performed.

Define your procedure to specify which inputs are recorded, which information is provided as supplementary documentation, and which values are included in the result calculation. Verify that a reviewer can identify the actually used method version and the associated records. A free-text comment should not inadvertently substitute for a missing mandatory entry.

For calculations within embedded tables, an independent calculation formula and appropriate target values are required. Specifically verify unit, factor, rounding, and empty inputs. When additional scripts or external calculation tools are used, their version, inputs, and result acceptance must be explicitly included within the scope; the platform designation alone does not cover these extensions.

Sources: [1] [7] [9]

Sweeper file transfer: incoming data has not yet produced a result

The manufacturer describes the File Sweeper as a configurable pathway for reading instrument files, extracting values, and assigning them to corresponding data fields. The version basis for 21.3 refers to enhanced processing of PDF and binary files. Verify which file formats and mappings your implemented intake pathway actually supports.

Crucial are the parser and mapping logic: Which field contains the sample identifier? Is a comma interpreted as a decimal separator or as a field delimiter? What unit is read versus what is stored? A transported numeric value is functionally incorrect if its intended meaning is lost.

A suitable internal failure test uses an initially incomplete file followed by its complete version. Define in advance how the process shall detect and handle this state. Additionally, verify duplicate files, unknown sample identifiers, modified columns, and failed transfers. A success notification must align with the actually usable data.

Sources: [2] [3] [7]

Further reading:

Test example: Unit change, open partial inspection and report

Example process, not performed as a product test: A sample requires identity confirmation and quantitative analysis. The instrument provides the quantitative value in mg/l; in the LIMS, this value shall be evaluated in µg/l. The upper example limit is 5.00 µg/l inclusive. The unrounded value is decisive, not the displayed value with two decimal places.

For this example workflow, the following additional requirements are specified: The final report may only be technically released after a complete evaluation of both assessments. A linear review shall be required prior to the second evaluation. These decisions must be demonstrably validated in your actual configuration; they are not assumed to be standard configuration settings.

Example: Test cases for data transfer and release sequence
Test caseSource data or actionExpected behavior in the example
Normal case 0.004 mg/l; both tests fully performed 4 µg/l; quantity within the limit; complete review possible
Boundary 0.005 mg/l 5 µg/l; inclusive example limit
Rounding trap 0.005001 mg/l 5.001 μg/l; outside, although display 5.00 possible
Missing unit Value 0.004, unitless No tacitly accepted conversion; clarification required
Open partial inspection Quantity assessed, identity verification missing No professionally authorized final report available for the entire sample
Incorrect sequence Second reviewer before first for linear design The specified sequence is implemented.
New entry The identical instrument file has been read once again. No undetected double processing or overwriting
Correction Evaluated result is professionally justified and amended Changes and implications on review and report traceability

Sources: [2] [7]

Demonstrate, on a component-specific basis, the presence of the Chromeleon Link component

The publicly available installation guide for WebAPI Service 2.0 describes two components: a REST-based WebAPI service for connectivity to the Chromeleon domain, and an add-in for result return. The guide covers the installation of the WebAPI service; it refers to additional documentation for the add-in and SampleManager integration.

Therefore, document separately the involved versions, service configurations, authorizations, and technical handovers. Review an order until the returned analysis is completed, and update or supplement any revised or retransmitted result status. The technical connection must support the desired professional timing of handover.

The procedure also mentions a potential performance impact in cases of rapidly changing user login data for service requests. If your usage scenario includes such dynamic user login data, a representative multi-user test should be included in the planning. This does not imply a general defect in all installations nor does it warrant a blanket recommendation for shared user accounts.

Chromatographic raw data, methods, and relevant evaluation histories shall be assessed separately. The LIMS result or a transferred report does not automatically demonstrate that all CDS records required for reconstruction have been fully imported.

Sources: [4] [5] [9]

Records, Audit Trail, and Recovery are linked

Define for a completed sample request the complete documentation: incoming data, testing activities, results, relevant appendices, method reference, changes, and release. A simple list of tables or file formats provides little value to the reviewer; the professional and technical context must be readily accessible.

Conduct a justified result correction as part of an independent review case, and subsequently assess whether the content, timing, responsible party, and rationale for the change are traceable and understandable. Define how relevant historical entries are to be incorporated into the prescribed review of the associated records. A technical logging function does not inherently perform this professional review.

During data migration and restore, the same complete process should be understood both before and after the intervention. Purposefully assess links to attachments and external measurement data. Public statements regarding SDMS functionalities do not constitute evidence that your specific file formats will remain readable and technically evaluable over the required period.

Sources: [9] [7] [1]

Further reading:

Project effort, Service Packs, and modified configurations

Before the project, the laboratory and QA should supply test plans, assessment rules, review sequence and complete anonymised examples. IT supplies the architecture, interfaces and operational responsibilities. The implementation partner explains standard functions, configuration and extensions. Unclear master data, varying local methods and undocumented parsers can take considerable time to resolve.

Capture, in addition to the main version, the Service Pack and interface version. The manufacturer's portal announced SampleManager 21.3 SP2 on 29 June 2026. This constitutes a concrete version reference, not a recommendation; no environment should be deployed without prior evaluation. Release notes, known issues, and actual usage determine the change assessment.

Review affected roles and open activities when an inspection plan is amended; for a parser, assess the previously supported instrument file types; for a new interface, evaluate the complete handover chain. Justify the scope and selection criteria for repeat inspections. Cloud operation may offload infrastructure responsibilities, but does not eliminate your professional judgment and release decision authority.

Sources: [6] [7] [1]

Checklist for a Robust SampleManager Verification

A thorough preparation enables informed decisions and verifiable examples. Use the list to proactively identify open items and assign them to laboratory, QA, IT, or implementation partners prior to test execution.

  • LIMS, ELN, LES, SDMS, and Chromeleon are described with their actually utilized scope.
  • Release, Service Pack, Add-ins, and interface components are clearly documented.
  • Incoming samples and workflow generate the technically appropriate tests and specifications.
  • Inspection plan, authorization, and report have a defined scope of decision-making.
  • Parser, units, mapping, and handling of duplicate files have been validated.
  • Limit values, rounding, missing data, and open sub-verification tests have been assessed.
  • Changes, signature implications, and required re-evaluation remain traceable.
  • Migration, restoration, and retrieval of complete processes have been practically verified.

Sources: [7] [9]

Project experience and collaboration

Trace the test order through to the decision on how the results can be used

With your laboratory leads, we follow a prepared SampleManager order through several individual tests. We identify the applicable master data and check how an outstanding or amended test result affects the assessment. Existing vendor evidence can be supplemented for a clearly defined workflow. Interfaces and in-house calculations need additional cases with independently established expected results. With IT and QA, we link the evidence to the intended use and subsequent retrieval. Your laboratory specialists retain responsibility for the scientific assessment of the results.

Frequently asked questions about SampleManager LIMS

Has SampleManager LIMS been validated by the manufacturer?

Supplier assessments can support your evidence, but do not automatically validate your specific laboratory process. Document the functions used and align existing documentation with your own requirements. In particular, configurations, calculations, interfaces, and release rules require a clear link to the intended use.

Sources: [7] [3]

What role does the Inspection Plan play?

The manufacturer specifies who must review data prior to its authorization. The described options allow for either a flexible or a predefined sequence. Professionally assess which sequence is required and validate that exact sequence, including the absence of review and unauthorized roles.

Sources: [2]

Is Authorization equivalent to Batch Release?

No. An authorized LIMS dataset describes a system state and its configured testing scope. The legally regulated certification and release of a medicinal product batch includes additional requirements and responsibilities. Clearly define which laboratory decision constitutes an action and which subsequent decisions take place outside the LIMS.

Sources: [2] [7] [10]

Why must the File Sweeper be considered separately?

A correctly transferred date container does not guarantee accurate interpretation. Parsers and mapping rules determine which value is assigned to which sample and unit. Review representative files and error scenarios such as missing identifiers, altered columns, and repeated imports. Document how unprocessed data remains visible.

Sources: [2] [3]

Does SampleManager replace Chromeleon CDS?

The manufacturer's documentation describes an integration of two applications. The documented link connects SampleManager with Chromeleon and supports result return. Separate the task, measurement, chromatographic analysis, and laboratory report by distinct workflows. Additionally, assess how relevant CDS original records remain accessible thereafter.

Sources: [4] [9]

Do all ELN attachments have to be validated individually?

Assess the role of an appendix within a process. A released instruction, a raw data record, and a calculation table present distinct requirements. Verify the reliable mapping and readability; if a table performs relevant calculations, appropriate validation evidence for its underlying logic must be provided. A general rule based solely on file extension is insufficient.

Sources: [1] [7]

What is essential when importing older sample data?

The values, definitions, and relationships required for the intended future use must be retained. For example, verify identifiers, units, status, and references to attachments. Define which processes are transferred and which are preserved in an accessible historical archive. A simple match in the number of data records is insufficient as quality evidence.

Sources: [7] [9]

Does a successful backup run suffice?

It has not yet been established that a complete laboratory procedure can be restored and made operational. Verify a restoration with results, attachments, history, and required external references. Identify who confirms technical restoration and subject-matter readability. The required scope shall follow your specific architecture and documentation chain.

Sources: [7] [9]

What information does QA need for a SampleManager update?

QA requires the relevant Release and Service-Pack status, manufacturer updates, known limitations, and assignment to their processes. Add configuration changes and results from justified revalidation exercises. Simply providing a version number neither indicates that no testing is required nor that all previous tests must be re-performed.

Sources: [6] [7]

What factors influence the effort required for a small laboratory?

Crucial factors include the number and diversity of methods, quality of master data, instrument formats, custom extensions, and clarity of release processes. Provide comprehensive example workflows and subject-matter experts early on. This enables reliable planning; user count alone does not justify the validation effort.

Sources: [7] [2]

Sources and review date

The linked manufacturer and regulatory sources were made available on 6 October 2026. Information regarding the WebAPI service refers to the instructions for version 2.0; version details for SampleManager will be specified separately. Example rules, test matrix, and checklist are operational aids and do not constitute completed product testing.

  1. Thermo Fisher Scientific: SampleManager LIMS Software
  2. Thermo Fisher Scientific: SampleManager LIMS Software — FAQs
  3. Thermo Fisher Scientific: Introducing SampleManager LIMS version 21.3
  4. Thermo Fisher Scientific: Digital Science Support — Announcements
  5. European Commission: EU GMP Annex 11, Computerised Systems
  6. FDA: Part 11, Electronic Records; Electronic Signatures — Scope and Application
  7. FDA: Data Integrity and Compliance With Drug CGMP — Questions and Answers
  8. European Commission: EU GMP Annex 16 — Certification by a Qualified Person and Batch Release

Sources checked: .

Daniel Herrmann, Daniel Herrmann Consulting

Daniel Herrmann Consulting

The appropriate tests for your SampleManager process determine

Daniel Herrmann Consulting supports you in defining laboratory procedures, assessing existing evidence, and implementing risk-based testing protocols in collaboration with your team.

  • 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 →