Laboratory Information vs QMS: Who Owns Methods, Specs, and OOS

QC laboratories live in two systems whether anyone admits it. The laboratory information system (LIMS, ELN, CDS, or a well-built LMS) owns samples, sequences, raw chromatographic files, and instrument run logs. The QMS owns specifications as quality documents, change control, deviations, OOS investigations, CAPA, and the batch decision. When those two owners blur, you get a passing LIMS status and a failing certificate, or an OOS that exists only in email.

This article draws the boundary for quality directors and lab managers who are tired of reconciling spreadsheet exports at batch release.

What the laboratory system should own

Sample login: lot, stage (incoming, in-process, finished, stability, environmental). Aliquot tree and chain of custody. Instrument assignment and sequence. Raw data and metadata, including the CDS audit trail. Calculated results as generated by the validated method processing. Analyst and reviewer e-signatures on the analytical record. Instrument calibration and maintenance status at time of use, or a tight interface to the CMMS. Stability inventory and pull calendar if that is how you run the chamber program.

FDA's Part 11 and 21 CFR 211.68 expectations attach to this layer because this is where original records live. WHO TRS and PIC/S PI 041 talk about the same integrity problems. The lab system is the technical home of ALCOA+.

What the QMS should own

Approved specifications and methods as controlled documents (the effective method number, not the CDS processing method file). Method validation and verification protocols and reports. Change control when a method, spec, or instrument type changes. OOS and OOT investigations, including Phase I and Phase II as you defined them against FDA's Investigating Out-of-Specification (OOS) Test Results for Pharmaceutical Production guidance. Deviations that are not OOS (sample mishandling, missed pull). CAPA. Batch disposition and CoA issuance as a quality unit act. Supplier CoA qualification decisions. Training and competency to perform the method.

ISO/IEC 17025 labs add impartiality and method validation language that still needs a document-controlled home.

Specs: the classic fight

A specification is a quality document. Version 14 of a finished product assay 95.0-105.0% must be the version LIMS uses to flag pass/fail. If LIMS stores its own spec table, it is a copy. Copies drift.

Practical pattern: QMS document control owns the spec. An interface or controlled download loads limit sets into LIMS with the document number and revision. LIMS refuses to calculate a status if the revision does not match. Quality unit sees the same revision on the CoA.

Do not let an analyst edit LIMS limits for this lot without change control. That is a new spec.

Methods: two objects with the same name

Method ASM-104 is at least two objects: the controlled SOP or STP in the QMS (how to prepare, system suitability, calculations in words) and the CDS processing method and instrument method on the chromatography system.

Both need version alignment. When you tighten a system suitability plate count, you change both. Validation or verification lives in the QMS. The CDS file is a configuration item under the lab's computerized system validation.

GAMP 5 second edition still helps: the CDS is software; the STP is a process document. Category and intended use sit in the validation file, not in LIMS sample login.

OOS: who opens it, who closes it

FDA's OOS guidance expects an investigation before you retest, with a clear hypothesis, and a quality unit conclusion. The lab may discover the OOS when LIMS compares a result to the spec. Discovery is not disposition.

Recommended split: LIMS automatically flags a result outside limits, locks further testing on that sample except per SOP, and notifies the lab supervisor. The QMS holds the OOS record number, Phase I lab assessment, Phase II full investigation if needed, links to deviation and CAPA, and the quality unit conclusion. The batch record cannot be released while the OOS is open.

If Phase I finds an assignable laboratory error (wrong standard weight, documented), the lab system keeps the invalid result and the reason. The QMS OOS still closes with that conclusion so the quality unit sees the pattern. Hidden invalidations in LIMS only are how repeat pipette errors vanish.

OOT should follow the same path if your SOP says OOT is a quality record. Do not bury OOT in a LIMS dashboard no auditor is shown.

Release: CoA is a quality document

The CoA is issued by the quality unit against approved results. LIMS can generate the numbers. QMS or ERP with quality approval issues the certificate. If LIMS prints the CoA, treat that print as a controlled form and keep Part 11 controls on the template.

Identity testing of incoming (211.84) often sits across both: LIMS has the spectra; QMS has the reduced-testing protocol and the supplier file.

Interfaces that do not create a third system

A clean design is: spec revision and method number flow QMS to LIMS; result status and values flow LIMS to QMS or batch record; OOS ID flows QMS to LIMS so the sample page shows the investigation number; training status may flow QMS to LIMS to block untrained analysts.

Avoid a third spreadsheet because the interface is late. That spreadsheet becomes the real system.

Stability, environmental, and contract labs

Stability pulls belong in the lab calendar. OOS on a stability lot is still a QMS OOS and may become a field action. Environmental monitoring hits may start in LIMS and become QMS deviations when action limits fire. Contract lab CoAs are incoming data: the QMS owns qualification of the lab; LIMS may store the results if you transcribe them under a verified process.

Audit questions that expose a bad boundary

Show the effective spec revision for lot X. Now show the LIMS limit set. Do they match? Who can change a CDS processing method, and is that in change control? Point to the OOS for this failing assay. Is it in the QMS or only a LIMS comment? When did the quality unit see the result relative to when the analyst clicked approve?

If those answers take more than a few minutes, the boundary is wrong.

Practical ownership table

Sample and raw data: lab system, no copy as system of record. Spec limits: QMS document, controlled interface copy in LIMS. STP and SOP: QMS, CDS methods as configuration. Method validation report: QMS. OOS investigation: QMS, flag in LIMS. Instrument audit trail: lab and CDS, periodic review record in QMS. CoA: quality unit and QMS, numbers from LIMS. Batch disposition: QMS, status back to ERP.

Keep humans in the loop on OOS conclusions and spec changes. Intelligent assistance can surface duplicate OOS wording or a spec mismatch. It should not auto-close Phase II.

Labs that want methods, specs, and OOS in a validated quality platform with a defined LIMS boundary can review the model at cloudtheapp.com/demo.