IT systems · Practical guide

Validating LabVantage LIMS: linking master data to laboratory workflows

A LabVantage LIMS workflow may finish successfully even if it uses the wrong specification version or omits a missing finding from the report. Use actual sample and result cases to test the master data, configured workflows and handover into routine use. The evidence should explain both the result and the decision taken.

Table of contents

At a glance

How do you validate LabVantage LIMS for GMP use?

Assess your actual laboratory workflows from the test request through master data, results, review, reporting and retention. Define requirements, assess risk and test relevant workflows, including failure cases. Account for the LabVantage version, configuration, connected systems and deployment model. Supplier documentation can support the assessment to the extent that it covers the intended use.

  • The scope of validation follows the established sampling procedures and the actually utilized modules.
  • Master data determines the significance of a result.
  • Configuration Management & Transfer supports change management processes, but does not replace professional technical assessment.
  • Sample release, result issuance, and subsequent material decision must be clearly attributable.

1. Define the boundaries of the LabVantage LIMS within the platform

LabVantage Solutions describes its LIMS as part of a laboratory informatics platform featuring functions for an electronic laboratory notebook (ELN), a laboratory execution system (LES), and a scientific data management system (SDMS). In a GMP laboratory, the scope is defined according to sample-specific workflows. Additional functions and modules are included when they support or provide evidence for the intended workflow.

Capture the used version, industry-specific pre-configuration, extensions, operating form and connected systems. The public product pages and curricula call functional areas, but no uniform configuration status for each customer project. Concrete rights, status transitions and available tools must therefore be confirmed in your environment.

GMP usage is determined based on the laboratory process. Annex 11 represents the corresponding EU-GMP reference for computerised systems. Part 11 covers electronic records and signatures within the relevant FDA application domain. Neither the product name nor the statement "for Life Sciences" supersedes this classification.

Sources: [1] [2] [6] [8]

Further reading:

2. Treat master data as rules for the process

LabVantage provides its own services for the creation and review of LIMS master data, including, among other elements, sample types, test methods, instruments, and reagents. For your project, this means that technical specifications must be translated into a clear, reviewable data structure.

Begin with a small number of representative methods. The laboratory responsible party shall define the intended statement, the configuration responsible party shall demonstrate its implementation, and the reviewer shall assess the alignment. Separate the technically existing master data set from its professional suitability for a specific application. The table below is an independent structuring aid and does not constitute a claim regarding pre-defined LabVantage object names.

Associate factual data with meaning in the process and provide verification evidence
Technical SpecificationKey questionOwn inspection aid
Sample type and test request What investigations are required for this purpose? Representative sample with expected test selection
Unit and number format What size is the value taken over? Comparison of Entry, Storage, and Output
Specification Which released status applies to the process? Probe before and after a planned change point
Qualified results document What, for example, does a value below the detection limit mean? Separate tracking of text annotations and numerical values
Review Rule What findings must be completely resolved prior to approval? Missing and atypical finding as a negative case
Report selection What results and indications appear to the recipient? Compare actual report with authorized release.

Sources: [4] [6]

3. Describe the workflow from order to decision-making

LabVantage identifies workflow designers and role-based interfaces as product features. However, a documented workflow alone does not constitute evidence that all relevant processing pathways are controlled. Describe how sample, test, and result are interconnected and at which points a person makes a decision.

Consider more than the standard workflow: delayed sample receipt, missing material, additional testing, discontinued investigation, or correction after review. Define which activities may continue and which require clarification. The actual status designations arise from your established process.

In addition, check an alternative operating path. If a user opens a task via an overview instead of the intended workflow, the control target should be reached. This is a test proposal of its own; no general statement is made that LabVantage allows or blocks such paths by default.

Sources: [1] [6]

4. Distinguishing numbers, qualified values and missing results

A value may be numeric, a qualified statement, or pending. These distinctions are relevant for evaluation. A report stating "less than 0.10 mg/L" signifies something different from a measured value of 0.10 mg/L. An empty field does not represent a measurement with a value of zero.

Example of a testing specification: A parameter has an inclusive upper limit of 0.10 mg/L. The unrounded value is compared. Thus, 0.10 falls within the limit, while 0.1001 falls outside. The qualified statement "< 0.10 mg/L" is retained as such and is not implicitly converted into an exactly measured numerical value. Whether this statement leads to a specific result decision must be defined by the analytical method.

Take this case only as a test concept. Allow the method responsible party to define the real rules for detection limit, quantitation limit, unit, and output. Then verify the same content in the input form, in the analysis, in the report, and during data transfer.

Sources: [4] [6]

5. Classify CMTs for controlled changes and transfers

The public LabVantage training program on Configuration Management & Transfer (CMT) outlines change mechanisms for configuration and master data. It includes, among other elements, Change Requests, Check-in and Check-out, Change Logs, as well as Import and Export functions. These elements demonstrate the system's functional scope; they do not establish a complete procedure for your system.

Therefore, separately specify who authorizes a technical change, who implements it technically, and who confirms successful acceptance. Importing a package is not solely justified by the fact that it has been imported; likewise, a CMT change protocol does not automatically constitute the complete handling history of a single laboratory result.

A suitable own test exercise concerns a modified specification. Keep track of the initial level and the target level, check affected dependencies and compare the transferred status with the test release. Determine how already ongoing orders are handled. A mere hook "Transport successfully" does not answer this technical transition question.

Sources: [3] [6]

6. Example: Specification change during ongoing testing

The example uses two test samples: Probe A was created before a released specification change, Probe B afterwards. The process manager decides in advance which level should apply. In addition, an outstanding result and a qualified value are prepared. These are own target tests, not run LabVantage tests.

The objective is to track the business decision across the entire chain. Document not only the master data change, but also its actual impact on test assignment, evaluation, review, and reporting.

Own inspection matrix for changes and result release
Test casePre-established expectationSupporting record
Probe A to be further processed following regulatory change. The professionally defined specification status remains identifiable. Sample collection, baseline status, and evaluation
Create new Probe B neu The proposed new site will be applied. Order and associated inspection requirements
Take qualified value Labeling, quantity, and unit retain their meaning. Input, stored content and report
Leave the required result open The intended verification cannot be overlooked despite the gap. Missing result and reaction
Change with routine account attempt Administrative changes are restricted by the defined permissions. User role and actual trial
After review, correct the finding. Correctness and any required re-evaluation are justifiable. History, Rationale and Current Status

Sources: [3] [6]

7. Interfaces and reports as part of the validation evidence are reviewed

The current technology overview identifies web services and data integration, along with JasperReports for reporting. For internal validation, it is essential to determine which of these pathways is actually utilized and where selection, assignment, or calculation occurs.

Prepare a concise, aligned data package for an interface, including sample identifier, test, result, qualification, and unit. Include a duplicate transmission, a termination, and an unknown test code. Clarify where a failure is detected and how the process proceeds after correction. These cases represent individual inspection proposals, not a description of a universal standard reaction.

In Reports, you should also verify the selected values in addition to the numerical data: Are there still pending tests within an apparently complete release? Are rejected results clearly communicated? Does the report, after correction, align with the officially confirmed data set? A technically generated PDF alone does not establish these relationships.

Sources: [2] [6] [7]

Further reading:

8. Results review, combine rights and approvals

LabVantage identifies electronic signatures and auditing as platform functions. Beyond that, the team requires clear definitions of responsibility and intent: which action confirms execution, which verifies inspection, and which authorizes the release of results?

Test permitted and unauthorized actions using representative accounts. Include deputies and technical accounts where they occur within the process. Allow a reviewer to trace a known correction case using the stored information. A technical login entry and a technical assessment of a change are distinct components.

In the drug-CGMP context, the FDA describes the evaluation and storage of legitimately rejected data. A corrected output should therefore not replace the view of the original process. The electronic confirmation remains to be considered with the respective confirmed data set. Moreover, a laboratory confirmation alone is not a comprehensive statement about the later material or batch decision.

Sources: [1] [7] [6]

Further reading:

9. Divide supplier documentation and internal responsibilities logically and effectively

LabVantage provides services for master data verification and validation, including automated testing. Please inquire about specific requirements, test protocols, expected outcomes, and open deviations. An automated test is as credible as its verification objective, input parameters, and the evaluation of its results.

For a SME, it is recommended to begin with a joint workshop at a representative sample process. The laboratory will explain methods and exceptions, QA will define the evaluation of evidence, IT will clarify operational procedures and handover responsibilities. A system owner will coordinate configuration, service providers, and outstanding decisions.

The key drivers are concrete: the number and diversity of processes, the quality of existing master data, different locations, custom workflows, reports, data migration, and integration points. Simulating simple examples early on highlights these differences. From this, a justified scope can be derived; blanket deadlines or a test package based solely on user count would overlook critical dependencies.

Sources: [5] [4] [6]

10. Operation, modifications, and data access to be permanently prepared

For product releases, modified master data, and new interfaces, the impact on the intended use is assessed. Derive appropriate regression tests from this evaluation. Prior to production deployment, verify the actual target state and document any open deviations together with the associated decisions.

Select a previous process with specification changes, corrections, and reporting for migration and recovery. Crucially, determine whether its original context remains understandable. For hosted operations, additionally clarify responsibilities and data provision. The following internal checklist assists in getting started; it is not a universal documentation package.

  • LIMS version, platform modules used, pre-configured settings, and operating mode to be specified.
  • Representative sample processes including exceptions describe.
  • Define primary data owners and approved method sources.
  • Treat numerical values, qualifications, units, and missing results separately.
  • Change release, CMT usage, and technical takeover assignment.
  • Review, correct, and report issuance to be jointly verified.
  • Interface errors, migration and subject-matter restore evidence to be prepared.
  • Link supplier documentation with internal requirements and remaining gaps.

Sources: [3] [2] [6]

Project experience and collaboration

Define the scope of the LIMS sample workflow with your team

A sample may pass through several systems and people before its result is used. With laboratory owners, we map the path and identify which tasks belong to LabVantage and which belong to connected applications. A suspect interface can be investigated directly. Where the overall relationships are unclear, we follow the sample process step by step. We document available evidence, open questions and responsibilities so your team can continue the work.

Frequent Questions on the Validation of LabVantage LIMS

Does LIMS validation also apply to ELN, LES, and SDMS from LabVantage?

Only to the extent that these functions are included in your reviewed sample workflow. LabVantage integrates LIMS functions with an electronic laboratory notebook (ELN), a laboratory execution system (LES), and a scientific data management system (SDMS). Document which of these you actually use and the associated data transfers. A reviewed sample workflow does not automatically validate the suitability of all other modules.

Sources: [1]

Is a manufacturer's LIMS description sufficient?

It outlines an intended functionality but does not yet demonstrate the suitability of your master data and operating procedures. Please provide the actual test certificates supplied and align them with your requirements. Additional testing will be tailored to the remaining risks and gaps in evidence of your established process.

Sources: [5] [6]

Why should master data be included in the validation strategy?

Source data influence, for example, which test is assigned and how a result is evaluated. A functioning application may generate incorrect conclusions due to inappropriate input specifications. Therefore, verify not only the completeness of import files but also the technical relevance based on representative methods and unambiguously expected outcomes.

Sources: [4] [6]

What does Configuration Management & Transfer cover?

The manufacturer describes CMT for controlled changes in configuration and master data as well as their transfer. The concrete proof depends on the configuration used. A technical takeover does not replace technical approval or effectiveness testing. Therefore, keep change decision, transferred status and evaluation together in the target system.

Sources: [3]

How do we handle a value below the detection limit?

Obtain the technical specification together with the value and unit. "Less than" does not represent an exact measured equality. The analytical method determines how this statement shall be evaluated and reported. Review the handling throughout entry, evaluation, reporting, and interface, based on a previously defined expectation.

Sources: [6] [4]

Must a new specification be applied to currently running samples?

Not mandatory. The specification level applicable to in-process samples is defined by your approved change management procedure. The LIMS must provide demonstrable evidence of implementing this rule. Test both an existing and a new order, document the assignment of each, and verify the subsequent reporting. A change date alone does not justify this decision.

Sources: [3] [6]

Can a report serve as the sole source for review?

A report may serve as a review basis if it provides a complete and sufficient audit context. For changes, additional histories, raw data, or origin information may be required. Use a known correction case to demonstrate traceability. A neatly formatted result sheet does not constitute evidence that all relevant data have been reviewed.

Sources: [7] [2]

Does automated testing take over the technical responsibilities of our laboratory?

The procedure can support repeatable testing steps. However, the purpose, expected statements, and evaluation of deviations must still be defined. Subject-matter experts should provide representative methods and edge cases. During supplier assessments, specifically verify that the data and configurations used actually cover the intended use.

Sources: [5] [6]

What level of involvement do we need as a small or medium-sized company?

You need accessible points of contact for methods, QA, and IT, as well as a coordinated system owner. Useful resources include current work instructions, master data sources, example reports, and interface scenarios. Unclear exceptions and inconsistent procedures increase workload. Address these issues prior to detailed planning, rather than retrieving decisions during test execution.

Sources: [4] [6]

What tests are advisable following an upgrade or migration?

Determine the scope based on changes and affected procedures. Typical internal audit checks include evaluation of existing and new orders, result transfers, reports, access rights, and historical data access. Document which previous evidence remains valid. A complete retesting of all tests is no more automatically justified than a blanket waiver of testing.

Sources: [6] [3]

Sources and review date

The basis is the publicly available LabVantage product pages, feature descriptions, CMT curriculum, and regulatory primary sources as of October 6, 2026. Public function overviews do not replace version-specific help or a current assessment of the own system configuration. Specific menu paths or universal status rules cannot be derived therefrom. Examples, tables, and checklists are independent review proposals and do not constitute completed product testing.

  1. LabVantage Solutions: LIMS – Laboratory Information Management System
  2. LabVantage Solutions: Technology – Architecture, Reporting, and Integration
  3. LabVantage Solutions: Configuration Management and Transfer Training Syllabus
  4. LabVantage Solutions: LIMS Master Data Creation and Management
  5. LabVantage Solutions: LIMS Validation Services
  6. European Commission: EU GMP Annex 11, January 2011 revision
  7. FDA: Data Integrity and Compliance With Drug CGMP – Questions and Answers, December 2018
  8. FDA: Part 11, Electronic Records; Electronic Signatures – Scope and Application

Sources checked: .

Daniel Herrmann, Daniel Herrmann Consulting

Daniel Herrmann Consulting

Determine the specific testing requirements for LabVantage LIMS

Daniel Herrmann Consulting supports you in logically aligning master data, laboratory processes, and existing documentation, and prioritizing open tasks.

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