IT systems · Practical guide

LabWare LIMS: testing specifications and master data

Master data can determine which test is scheduled and how its result is assessed. When a limit changes, trace its dependencies on product, method, unit, calculation and report. An isolated comparison of the changed field may miss the impact.

Table of contents

At a glance

How do you test specification changes in LabWare LIMS?

Define which samples and time periods a revised specification applies to. Compare limits, units, calculations and the link to the correct method. Existing results must not silently acquire a different meaning. Demonstrate the version and effective-date behaviour in your actual LabWare configuration.

Scope and Applicability

LabWare offers configurable laboratory processes. This article describes technical validation objectives, not a identical interface or guaranteed versioning functionality for each installation. Analytical method validation remains a separate responsibility.

Sources: [1] [2]

Consider ongoing samples and historical reports prior to action

Ongoing samples require a deliberate rule. Should the status valid at the time of registration apply, or a later professional amendment? This decision must be derived from the process and must be implementable and traceable for the affected cases. An automatic switch is neither inherently correct nor inherently incorrect.

Also review the historical report. If, upon re-creation, it reloads current master data, the report's conclusions may change. Therefore, the required evidence must demonstrate which specification and method actually applied during the original evaluation.

Sources: [1] [2]

Consider specifications, method, and results as interrelated components.

A specification defines the professional assessment. A method describes the intended investigation. A result arises within a specific context. Therefore, upon a change, it must be clarified which version applies to which sample and how historical decisions remain interpretable. A current limit value must not be inadvertently reinterpreted as a previous evaluation.

Capture the actually used LabWare objects, versions, and local rules. Manufacturer descriptions indicate platform capabilities but do not confirm your configured assignments. Specify product, test type, location, or other criteria that influence specification selection. A specification with the same name may be used differently in different contexts.

Distinguish professional master data management from technical administration. Both may be necessary, but require appropriate authorizations and controls. A technical administrator may modify a system configuration; the professional suitability of the new limit value does not follow from this action. Responsibilities should integrate these perspectives.

Sources: [1] [2]

Change and efficacy rules prior to amendment describe

Define when a new specification becomes valid. A relevant reference point may, for example, be the order receipt, sample receipt time, or another professionally justified basis. The article does not prescribe a universal time point. The selected rule must be unambiguously and verifiable within the actual process.

Define the handling of open investigations. An already initiated test may remain under the previous regulation or be transferred under controlled conditions. In the case of a defective previous specification, a more extensive evaluation may be required. Distinguish between planned technical changes and error corrections; both may have different implications for historical data.

Internal Work Aid: Transition Situations and Their Documentation
SituationCritical questionEvidence to produce
New assay after efficacy Which version is assigned? Check selection rule with known time point
Sample already open beforehand Is the current status still valid? Transition decision and actual reference
Historical Result Will the previous assessment be obtained? Reconstruction with original context
Corrected Specification Which prior activities may be affected? Justified Scope Assessment
Several applicable rules Which selection takes precedence? Test case for ambiguous matching

Sources: [1] [2]

Example: new limit and an already initiated sample

In the example, specification S-2 allows values up to and including 10.0 mg. From 1 November 2026, S-3 lowers the upper limit to include 9.5 mg. According to the process rule adopted here, the time of the sample installation decides on the assigned level. P-21 was previously created and remains under S-2, P-22 is created afterwards and receives S-3. Both samples receive the measured value 9.8 mg in the test. Thus, P-21 is inside, P-22 is outside the respective limit. This assignment rule is a default of the example, not a claimed LabWare default setting.

Verify the assigned specification, calculation, unit, and evaluation status against these independently defined target values. For P-22, exactly 9.5 mg is entered: the value falls within the included boundary. Perform an additional test at the temporal transition if such a transition is relevant in your configuration. Clearly define the time zone and professional time reference throughout.

Afterward, open a closed result under S-2. It should remain clearly understandable within the required context. Whether a re-evaluation is necessary depends on the reason for the change. A purely planned tightening and the correction of a previously incorrect limit must not be treated equivalently without proper assessment.

Internal assistance document: Test cases for P-21 and P-22
Test caseActionExpected finding
Before transition P-21 with 9.8 mg processed S-2: within the limit of 10.0 mg
After transition P-22 with 9.8 mg processed S-3: outside the limit of 9.5 mg
Limit value P-22 with exactly 9.5 mg to be verified S-3: within, inclusive of the boundary
Historical Access Open closed result Clear specifications and evaluation justifiable
Multivalent assignment Two appropriate contexts generate Selected priority or error rule applies
Unauthorised change Attempting to change critical limit value The permission boundary works

Sources: [1] [2]

Include calculations, units, and dependent templates

A specification change may involve more than a single numerical value. Verify unit, rounding rule, calculation method, reporting format, and potentially interface status. An accurate limit with an incorrect unit may lead to a wrong decision. A correct internal evaluation may be ambiguously presented in a report.

Capture commonly used master data. A method or calculation rule may serve multiple products. Therefore, changes to such items require a impact assessment extending beyond the initial case. Searching for visible forms alone may not identify all dependent outputs or automated workflows.

Evaluate appropriate failure scenarios. A missing specification should not be replaced by an inappropriate default rule. A non-existent method or invalid unit must have a clear clarification pathway. The exact system response shall be defined as a separate requirement and verified against the actual configuration.

Sources: [1] [2]

Link changes, testing, and release to traceability

The change record should show the old and new rules, the reason, affected uses and test scope. Identify who confirms the process requirement and who implements it in the system. A second-person review may be part of the procedure. The sequence of roles need not be identical for every master data item.

Document the actual status following takeover. A released change request does not prove that the correct specification is actively in use within the production context. Appropriate, objective controls confirm selection, critical values, and the intended efficacy linkage. Deviations are evaluated prior to any corresponding usage decision.

During a correction action, assess the potential historical scope. Which samples were evaluated using the incorrect rule? What decisions may be affected? The response must include data and professional judgment, not a blanket automatic re-evaluation of all results. Ensure the original state and justified corrections are clearly traceable.

Sources: [1] [2]

Operate and knowledge transfer aligned with specific nursing tasks

An internal master data owner should be able to explain how a new rule is selected and which dependent processes exist. Perform a planned version change and a failure scenario to demonstrate this capability. A sole training certificate demonstrating mask operation only provides limited evidence of this competence.

Maintain representative test cases for future changes. This includes transition scenarios, limit values, historical reviews, and unauthorized changes. The selection may vary depending on the source data type. The objective is a clear, actionable procedure that the department can realistically implement without treating each change as a full-scale new implementation project.

You will retain required historical context even during migration or decommissioning. Results without specification and method reference may lose their validity. Therefore, master data governance does not end with a new version; its context remains part of the later required data lifecycle.

Sources: [1] [2]

Draft: Specification Change and Historical Sample Verification

Prepare two batches to meet the intended efficacy time point. Define the rule by which a specification is assigned. This may vary depending on the process. The test should not retrospectively claim a desired standard effect, but rather demonstrate the actually established transition rule.

Link version selection and result evaluation. A correctly stored limit value is insufficient if it is incorrectly assigned to the wrong sample. Additionally, verify unit, comparison operator, and relevant dependent output. The historical sample should remain interpretable within the context required for its original decision.

When an erroneous old rule is in place, the historical scope is evaluated separately. A planned enhancement and a correction of faulty logic must not be treated equally without justification. Document the decision and, if necessary, any associated data or quality assessment with the responsible role.

Sample filling example – internal work aid
Area to assessExample entryExpected finding
Old rule S-2 sets an upper limit of 10.0, inclusive. The previously used specification is known.
New Regulation S-3 ab refers to efficacy-based justification. The transition is professionally defined.
Previous sample P-21 prior to the transfer. Proposed previous or formally revised assignment.
New assay P-22 following transfer. New selection rule is active.
Boundary case Value above and below the relevant limit. Operator, unit, and calculation are correct.
History Review the completed result again. The previously valid method and specification are available.

Sources: [1] [2]

Next steps

  • Identify the change and the process dependencies it affects.
  • Define efficacy and handling of ongoing samples.
  • Review new, ongoing, and historical cases.
  • Link clearance and proof of change with the master data.
Further reading:

Project experience and collaboration

Test the new specification against a sample already in progress

With the laboratory, we consider a sample already in progress when a specification changes. Before technical testing, we agree which limit, unit and method version should apply. These define expected cases for selection and effectiveness in your LabWare configuration. A single specification correction may need a narrow test. Where calculations, templates or historical results are affected, we trace those dependencies with their owners. The software should reflect an explicit business decision.

Frequent Questions on LabWare Specification Changes

Is master data management always considered a software change?

Not in the same technical form. It may nonetheless alter the intended system effect and requires appropriate control and verification.

Sources: [1] [2]

Is the four-eye principle enough for limit values?

A second person can check the accuracy of a critical manual entry. Annex 11 section 6 allows a second person or validated electronic means for this purpose. A second-person check of a limit does not establish that the sample was assigned the correct specification or that the specification was applied correctly. Test those effects through suitable functional cases. Intended use and risk determine what further evidence is needed.

Sources: [1] [2]

Must historical results be re-evaluated?

In the case of an error correction, it is necessary to assess whether historical results and decisions are affected. However, a specification introduced exclusively for future cases does not automatically trigger a reassessment of old results.

Sources: [1] [2]

Can a new specification automatically modify open samples?

Open samples require a clearly defined transition rule: Which version should be in effect at what time point for which sample? The technical implementation must be verified. A planned new instruction should be evaluated differently from a correction of an error. The actually used version must remain traceable for each sample.

Is the test of the modified limit value field sufficient?

Not always. Check dependent selections, unit, calculation, report, and interface, as applicable. A correctly stored value does not necessarily prove correct application to the intended sample. The impact assessment determines the additional scope and should take into account commonly used master data.

Why should a new specification be validated using open samples?

Since the treatment depends on the transitional rule, a test conducted only on newly created samples does not demonstrate whether ongoing investigations have been inadvertently redirected. Verify the intended time and version relationships. The decision must align with the reason for change and the actual laboratory process.

How do we identify common master data dependencies?

Track methods, calculations, and specifications to their actual usage. A rule may impact multiple products, reports, or interfaces. Identify these relationships in the impact assessment. Testing only the first requested product may fail to capture the combined effect.

Sources and review date

The sources form the technical framework. Tables, checklists and examples are own methodological derivations, not literal standard specifications. Manufacturer information is to be referred to the used version and configuration. Complementary targeted source reconciliation on 18.10.2026: Annex 11 no. 6 for the control of critical manual input; the concrete sample and number cases are own examples.

  1. European Commission: EU GMP Annex 11, Computerised Systems (2011)Current version as per EudraLex inventory as of 14.10.2026. Application, risks, operation, and data lifecycle; specific testing proposals are derived independently.
  2. LabWare: LIMS – Laboratory Information Management SystemSupplier source for product functionalities. Availability and behavior depend on version, edition, license, and configuration; no general compliance certification.

Sources checked: .

Daniel Herrmann, Daniel Herrmann Consulting

Daniel Herrmann Consulting

So your team can safely plan the next step.

We support you in assessing the current situation, clarifying responsibilities, and implementing appropriate evidence within operations. The type of support that is most effective depends on your system, your team, and the specific objective.

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