Sample identity and custody
Retain the identifiers, source, dates and context needed to distinguish the sample and follow it through the process.
How a Laboratory Information Management System can support traceability, equipment-data imports, authorised review, reporting and ISO/IEC 17025-aligned laboratory controls without misrepresenting software as accredited.
SANAS accreditation applies to a laboratory or other conformity assessment body and the activities listed in its accredited scope. A LIMS supports the records, traceability and controlled workflow used by the laboratory.
The laboratory remains responsible for its competence, approved methods, personnel, equipment, quality system, validation and reporting. Software should preserve those controls and make their evidence easier to retain and review.
The laboratory’s capability depends on its complete technical and management system. The LIMS should support that system without being mistaken for it.
Laboratory personnel, methods, equipment and technical decisions remain central to valid results.
Processes must be applied consistently and protected from inappropriate influence or uncontrolled change.
Accreditation applies to the activities listed in the laboratory’s approved scope, not every possible test or software feature.
Samples, tests, source data, review, changes and reports should remain identifiable and retrievable.
The laboratory should verify that configured software behaves correctly for the approved workflow it supports.
Permissions, master data, methods, reports and system changes require ongoing governance after go-live.
The client is not named in this public overview, but the operational use demonstrates that dMS can be configured around demanding laboratory controls rather than remaining a theoretical feature list.
This is an implementation claim, not a claim that SANAS accredits or endorses the dMS software product.
Real sample, result, review and reporting workflows are supported in day-to-day laboratory use.
The laboratory validates the implementation and governs changes according to its own quality system.
Accreditation should always be verified against the laboratory’s current SANAS certificate and scope.
The correct configuration depends on the laboratory, but these controls are common areas for implementation and validation.
Retain the identifiers, source, dates and context needed to distinguish the sample and follow it through the process.
Apply the correct result structure, units, limits and controlled definitions for the relevant laboratory activity.
Map and verify exported datasets so that imported values reach the correct samples, tests and fields without uncontrolled recapture.
Separate capture, review, authorisation and administration responsibilities according to the laboratory’s approved workflow.
Retain sufficient evidence to understand the source, status and authorised changes affecting laboratory information.
Produce reports and Certificates of Analysis from authorised sample, test, specification and result information.
Accredited laboratory implementation is not a generic software installation. It requires controlled decisions by the laboratory and the implementation team.
Identify samples, methods, test definitions, equipment sources, roles, review stages and authorised outputs.
Build master data, permissions, imports, specifications, reports and COA formats around the approved process.
Test representative manual and imported results, limits, calculations, status logic and output.
Obtain responsible laboratory approval and train each user according to their authorised role.
Review future changes to methods, imports, master data, permissions and reports before operational use.
Clear distinctions matter because accreditation, implementation and software capability are related but not interchangeable.
No software product is presented here as SANAS approved or accredited. SANAS accreditation applies to the laboratory or other conformity assessment body and the activities listed in its accredited scope. dMS LIMS is in operational use at a client laboratory operating under SANAS accreditation and supports the controlled workflows used by that laboratory.
No. Accreditation depends on the laboratory’s competence, methods, personnel, equipment, quality system, records and implementation. A LIMS can support those controls but cannot guarantee accreditation.
ISO/IEC 17025 does not prescribe the use of a named LIMS product. A laboratory may use controlled systems suited to its work. Where a LIMS is used, the laboratory should validate and control the configured system so that it supports approved methods, traceability, review and reporting.
Yes. Configured import profiles can map exported instrument or equipment datasets into the appropriate samples, tests and result fields, subject to verification against the actual export structure.
Yes. The LIMS can produce controlled Certificate of Analysis output from authorised sample, test, specification and result information.
The client laboratory remains responsible for validating the configured implementation against its approved procedures, methods, data-integrity controls, permissions, reports and accredited scope.
Review the sample structures, equipment exports, methods, specifications, permissions, reports and Certificates of Analysis that the implementation must control.