Table of contents
At a glance
What do you need to validate in STARLIMS?
Demonstrate that the deployed STARLIMS components support the laboratory process from sample and test request through data extraction and calculation to the result decision. Define the product variant, configuration, interfaces and use. Trace the source document, sample, test, value and unit together. Importing a document successfully or obtaining a supplier package alone does not demonstrate that the entire chain works.
- The QM LIMS and the pre-configured SaaS solution QM Essentials have distinct, separately validated performance scopes.
- SDMS data extraction, LES execution, and LIMS result utilization constitute distinct validation objects.
- Reference values must remain independent of the specific extraction or calculation rule being evaluated.
- An approval of results neither replaces the evaluation of open findings nor a required batch certification.
1. Distinguish QM LIMS, QM Essentials, and their GMP application scope
STARLIMS describes a platform comprising Quality Manufacturing LIMS, SDMS, LES, ELN, and analysis components. The product name alone therefore provides limited insight into which component processes your records. R&D offerings such as Labstep ELN or solutions designed for other industries are not interchangeable designations for the quality laboratory system in use.
QM Essentials is offered as a pre-configured, subscription-based cloud-based LIMS for smaller and mid-sized batch-producing companies. Key features include Batch Login, Environmental Monitoring, and Outsourced Samples; Stability Studies and Advanced Analytics are described as optional add-ons. Specific components and customizations included in your agreement must be determined separately.
This article addresses the use of STARLIMS in the GMP quality laboratory for human medicinal products. The European Commission continues to reference Annex 11 in this context as of the January 2011 revision. Other intended uses, such as clinical diagnostics, as well as requirements from other markets, require separate evaluation. The name STARLIMS does not imply a general GAMP category nor a general exemption from validation.
2. Prepare a component card instead of a generic system scope
Start with an actually used inspection. Map out where the sample is placed, the work instruction is retrieved, the measurement result is generated, and the quality decision is made. Identify every media change. Even a raw data set stored outside of STARLIMS must be considered in this evaluation if it is required to understand the decision.
The following table serves as an internal planning aid. It outlines questions to be addressed regarding your environment, not a guaranteed license combination. A useful addition for each entry is the responsible point of contact and the specific evidence: configuration status, approved requirements, test documentation, or operating agreement.
| Component | Possible task | Question to test | Evidence needed |
|---|---|---|---|
| QM LIMS / QM Essentials | Probe, test instruction and result utilization | Which dataset drives the business decision? | Product variant, process description and configured status sequence |
| SDMS, if utilized | Document intake and data extraction | Which document and which regulation provide this result? | Input file, current regulatory status, and assignment documentation |
| LES, if used | Supervised execution of a laboratory instruction | Which valid instruction was in effect during data entry? | Work instruction, execution record, and handover |
| Instrument / CDS | Measurement and instrument-specific processing | Where are raw data, the method, and any potential re-evaluation stored? | Link to the complete instrument data set |
| ERP or other target system | Further material or quality decision | Which decision is transferred with which status? | Interface agreement and technical acceptance inspection |
3. Deriving the scope of the examination from the result decision
Specify requirements so that a laboratory responsible party can assess the desired behavior. For example: A result must be uniquely attributable to the specified sample and the intended test. An unknown unit must be resolved prior to further use. Any subsequent correction must be clearly traceable to the original entry.
Then assess the potential impact: an incomplete search filter has different consequences than a swapped result that influences a material selection decision. Consider existing controls and their demonstrated effectiveness. If no one knows whether incoming data is checked for duplicates, this represents a knowledge gap; there is no evidence to support a low risk.
Request suitable manufacturer documents and assign their coverage to your requirements. A proven standard process can save work. However, it may be possible to keep open customer-specific extraction rules, master data or interfaces. The risk decision should address precisely these gaps instead of discarding all supplier receipts or taking over unchecked.
4. SDMS: Associate the read result with its source
The official SDMS description mentions the collection and management of scientific documents as well as the extraction of data from instrument-related PDF files. This is a relevant product capability, but not yet a description of your specific extraction rule. Let us show you how a field is detected, the appropriate sample is determined and an unreadable or ambiguous file is treated.
Prepare a controlled set of typical source document examples. Intentionally vary sample identifiers, measurement values, decimal representation, page breaks, and units, to the extent such variations may occur in the intended operation. For each variant, clearly define in advance which incoming data is accepted, rejected, or held for clarification prior to testing. A blank or omitted field must not inadvertently generate a plausible default value without explicit indication.
Verify the complete objective outcome following transfer. A technical success status is insufficient as evidence for a professional assignment review. Retain the independent original record alongside the observed target state. The readability of a file does not constitute proof that all required instrumental raw data and metadata are included within it.
5. Example Calculation: Two samples, one extraction rule
Sample test case, no executed STARLIMS product test: The test file LAB-017 contains sample A17 with concentration test and 0.125 mg/mL, and sample B18 with the same test and 0.250 mg/mL. For the target process, the unit is defined as µg/mL. The independent calculation yields 0.125 × 1,000 = 125 and 0.250 × 1,000 = 250. Further dilution factors are explicitly not specified.
The released example requirement specifies that each unit must be converted exactly once and each sample must be uniquely assigned based on its identifier. A separately generated test input serves as a control mechanism. The unaltered original and pre-verified target values are retained. Whether STARLIMS fulfills the required control through configuration, integration, or an additional measure remains to be determined within the project. In the example scenario, only A17 and B18 are considered valid samples; X99 is not configured. A file with identical filename and unchanged content is considered a duplicate and must not generate a second professionally usable result set.
| Test case / Source | Rules and Assignments | Independent specified value | Expected treatment | Evidence for comparison |
|---|---|---|---|---|
| LAB-017, A17: 0.125 mg/mL | A17 → Content; mg/mL × 1,000 | 125 µg/mL at A17 | Transfer for intended results verification | Source line, manual invoice, target value and unit |
| LAB-017, B18: 0.250 mg/mL | B18 → Content; same rule | 250 µg/mL at B18 | No mixing with A17 | Both sample identifications and both result fields |
| Separate file with reversed line order | Records are still matched by identifier | A17 = 125; B18 = 250 µg/mL | No shift in sample values | Independent target value list and observed assignment |
| Separate file: A17 without unit | A reliable conversion cannot be established | No usable result from this entry | Clarification path; no implied acceptance | Input file, notification, and restricted further use |
| Repeated identical LAB-017 | Duplicate rule of the example process | A professionally applicable result set | Repetition detectable; no second valid statement | Number, identifiers and documented treatment |
| Separate file: unknown sample X99 | No existing sample can be identified unambiguously | No automatic assignment to A17/B18 | Clarification prior to result usage | Incorrect entry and unaltered existing results |
6. Check the LES implementation and method status together
STARLIMS describes LES as support for guided work instructions with integration into the LIMS. The manufacturer's side also mentions the review and approval of tests prior to release. For your validation, the key consideration remains which portion of the laboratory instruction is actually captured there and which steps occur outside of this system.
Select an instruction involving a professionally relevant decision, for example, an additional dilution following a predefined measurement result. Evaluate the normal path and the alternative path based on pre-defined inputs. Additionally, inquire about the handling of a disruption involving already captured values and which user is authorized to resume the procedure.
If the underlying work instruction changes, clarify the transition for new and ongoing tests. A current screen alone does not establish the previous execution status. The evidence should demonstrate which instruction was in effect and how a change was handled. The specific technical version binding is not fully visible from the public product pages and must be substantiated for your environment.
7. Separation of result verification, corrections, and releases
Describe what a reviewer should actually see prior to approval: result, unit, specification, source, relevant edits, and any remaining flags. Also specify who is authorized to change assignments. A user who corrects a flawed extraction rule does not automatically determine the usability of all previously accepted results.
A suitable audit case involves an allowable result correction following the first review. Can a subsequent reviewer understand the original entry, the corrected value, and the documented rationale? What implications does the correction have for an already prepared report or a previously shared document? The answer arises from your workflow and actual records.
Where electronic signatures are employed, evaluate the complete signing process and its linkage to the approved dataset. A laboratory result release must be distinguished from a material decision and, where legally required, from the quality authority (QP) certification of a medicinal product batch. Annex 16 outlines this independent certification and release process; a merely named LIMS status does not substitute for it.
8. Compare professional data transfers and accepted inventory data
When STARLIMS results or decisions are transferred to another system, both parties agree upon the meaning of the transfer. Does a message contain a preliminary measurement value, a verified result, or a final laboratory decision? Identify the actual fields transferred, their units, and the conditions for use within the target system.
Plan a rejected dataset and a repeat after correction for your integration pathway, while also monitoring the existing target state. Ensure that a retrospectively accepted older result set does not inadvertently override a more recent decision if this contradicts the intended workflow. The specific sequence logic must be defined, not inferred from the product name.
When transferring data from an older system, a sum comparison is merely an initial step. Select additional, justified comparisons for sample, test, method reference, status, and historical changes. Document which information is intentionally retained within the accessible legacy system. Such a segmentation must include clear references and responsibilities; a well-structured final report does not close a gap in the historical record.
9. Manage product, platform, and rule changes under control
An official STARLIMS article describes QM 12.3 SP1 on Technology Platform 12.4. This article is a documented version example, no proof of the latest version in October 2026. It shows why the name of the LIMS alone does not suffice as a version specification. Keep your actual application, platform, extensions and extraction rules separately.
Upon a change, first identify the affected data pathways and decisions. A new instrument layout may require different tests than a modified approval process. Utilize appropriate existing documentation where possible and supplement it with a justified assessment of the impact. The selection should clearly indicate which previous assumptions remain valid and which require new validation.
In addition to operational availability, recovery and historical readability are essential. A viable recovery test demonstrates not only the successful restart of the system but also a traceable, selected process with the necessary references. For long-term data retention, the data volume and retention period are determined based on the actual intended use. A single PDF export or a generic annual retention period is not a general solution.
10. What should the Laboratory Manager, QA, and IT prepare prior to project start
The effort varies significantly depending on the number of truly distinct test procedures, input formats, and decision points. Ten instruments with the same controlled input format may require different handling compared to two devices generating highly variable reports. Ambiguous master data, required histories, and future exceptions further increase workload. User count alone therefore cannot serve as a reliable basis for estimation.
The Laboratory Manager provides technically representative test results and independent target values. QA determines decision pathways and evaluates open findings. IT and system owners clarify operational procedures, access controls, interfaces, and recovery processes; the supplier must demonstrate the actual functionality and delivery scope. Additionally, identify who has the authority to resolve technical conflicts between the intended process and product configuration.
- Product variant, modules, release, and platform version are documented for the intended environment.
- A real sample pathway with all inputs, decisions, and transfers is jointly described.
- Source data, extraction rules, units, and independent setpoints are available.
- Normal cases, ambiguities, erroneous entries, and repetitions have clear acceptance criteria.
- Review, correction, signature, and onward transfer are restricted by authorizations and history.
- Supplier documentation is assigned to requirements; remaining gaps in evidence are visible.
- Changes, restoration, retention, and data exit are managed by designated responsible parties.
Project experience and collaboration
Keep the sample, extracted value and decision on the result linked
With laboratory experts, we choose a known source document and trace sample, test, value and unit through to the intended use of the result. For a conversion, we calculate the expected value independently. Standard evidence may suffice where it covers the actual path. Custom extraction rules and calculations need additional cases. We also test a record with an incorrect assignment or missing information. Your authorised laboratory owners retain the scientific decision on the result.
Frequently asked questions about STARLIMS
Is QM Essentials to be treated the same as QM LIMS for validation purposes?
The fundamental question regarding suitability for your process remains the same, although the specific scope may vary. First, compare the proposed workflows and enhancements against your requirements. Then evaluate configuration, interfaces, and operational responsibility. Shared technical origin does not imply identical functionalities or equivalent coverage of a validation package. Document any differences in writing for your environment.
Must the SDMS and LES have separate validation projects?
Not mandatory. What is essential is a clear definition of the components and their interfaces. A joint project can be beneficial if the scope, responsibilities, and validation evidence remain transparent. Regardless of document structure, an auditor must be able to trace where a laboratory record is created, modified, and used. Separate documents are only helpful if they preserve these interrelationships.
Is a PDF that has been loaded sufficient as evidence of correct result transfer?
No. Compare the sample, test, numerical value, and unit in the target against an independent source. Additionally, verify whether the PDF contains the necessary context. Depending on the measurement process, further raw data or analysis steps may exist within an instrument system. The document and the fields extracted therefrom are distinct review objects requiring demonstrable linkage.
How are independent setpoints for a SDMS rule established?
Determine the expected results prior to testing from controlled source data. For a simple unit conversion, a separately verified manual calculation may suffice. Do not derive the target value from the same rule being tested. Maintain source, calculation, and assignment together to enable a second reviewer to detect discrepancies in the target.
What should happen with a doubly received instrument file?
First, determine whether the repetition is technically identical to a previous run or represents a new analysis. For identical repetitions, a controlled process must be implemented to prevent unintended secondary results or to ensure such results are clearly identifiable. In the case of a new analysis, the rationale and relationship to prior results must remain transparent. The specific technical function responsible for this must be defined and validated during integration.
Does an LIMS workflow replace the validation of the analytical method?
No. The referenced implementation addresses whether the intended operating procedure is correctly executed within your system environment. Whether the analytical method is suitable for its intended purpose and the instrument provides reliable measurements remains subject to further technical validation. Identify your interfaces within the project to ensure that a completed software workflow is not inadvertently used as evidence for the entire measurement method.
Is an approved STARLIMS result already a released medicinal product batch?
Not automatically. Identify the decision represented by a particular approval and who is authorised to make it. A laboratory result may inform a later decision. Certification of a finished medicinal product batch by a Qualified Person has its own regulated scope. Where a system records certification, its role, signature and record must fit that purpose.
Must every feature update be revalidated after each Service Pack?
The scope of the review aligns with the actual impact and available evidence. Refer to relevant amendment guidelines, identify affected processes, and assess the transferability of existing documentation. An amendment to instrument transfer may require targeted retesting of the data matrix; other areas may remain unchanged based on justification. Ensure that selection criteria, open issues, and decisions are clearly documented, rather than automatically testing all or none of the components.
What documentation should a small and medium-sized enterprise provide prior to a cost estimation?
Useful are product offerings and version status, a list of laboratory procedures, typical instrument files, decisions, and interfaces, as well as examples of complex exceptions. Supplement the existing inventory with data from migrating systems and current operational responsibilities. With these inputs, different testing pathways can be identified. If missing, the estimation should clearly state its assumptions and provide targeted clarification, rather than offering a seemingly precise duration.
What remains to be done regularly after a successful implementation?
Monitor changes to instrument formats, laboratory instructions, user roles, and interfaces, as well as incidents during ongoing operations. Assess whether existing validation evidence remains applicable. Additionally, evaluate the required recoverability and historical accessibility in alignment with your risk-based operating concept. An older closure report remains useful but does not replace a review of a subsequently modified data transfer or result usage.
Sources and review date
Supplier and regulatory sources were opened on 6 October 2026. Public product pages do not replace version-specific functional descriptions of your environment. QM 12.3 SP1 on platform 12.4 serves exclusively as a documented version example. Tables and calculation cases are standalone work aids; they are not executed product tests.
- STARLIMS: R&D Quality Manufacturing Informatics Platform
- STARLIMS: QM Essentials
- STARLIMS: Scientific Data Management System
- STARLIMS: Laboratory Execution System
- STARLIMS: LIMS Performance Improvements in QM Update
- European Commission: EudraLex Volume 4
- EU GMP Annex 11: Computerised Systems
- EU GMP Chapter 4: Documentation
- EMA: ICH Q9(R1) Quality Risk Management, Correction 2
- EU GMP Annex 16: Certification by a Qualified Person and Batch Release
Sources checked: .
Ensure traceability and accountability of laboratory decisions and their data pathways
Daniel Herrmann Consulting supports you in integrating STARLIMS processes, supplier documentation, and technical inspection cases into a traceable validation scope.
- 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.

