Türkçe 
English 
OOS stands for Out of Specification. It describes a quality-control test result that falls outside approved specification limits. In pharmaceutical, biotechnology, food-supplement, and other regulated manufacturing sectors, OOS management is critical to product quality, patient safety, process control, and batch-release decisions.
In Electronic Batch Record (EBR) systems, Out-of-Specification (OOS) management enables the association of quality control results with the relevant batch record, making out-of-limit values visible and linking them to deviation/CAPA processes. Thus, out-of-specification results are not limited to laboratory reports; they can be examined in conjunction with production records, process parameters, and quality assessment. The Centra Electronic Batch Record (EBR) solution contributes to the more traceable and audit-ready management of critical quality events such as OOS.
The Basic Logic of the OOS Concept
What is OOS?
OOS (Out of Specification) is when a test result falls outside the defined acceptance limits for a product. For example, if the result of a quality test such as active ingredient quantity, solubility, impurities, pH, microbiological load, sterility, moisture, or content uniformity exceeds the specification range, an OOS situation may occur. This result requires formal investigation as it can directly affect the product's conformity in terms of quality.
Why is OOS considered critical?
Because an out-of-specification result may indicate that the product does not meet safety, efficacy, or quality requirements. However, not every out-of-specification result automatically means product rejection. First, it should be investigated whether the nonconformity is due to a laboratory error, sample error, method problem, or actual process-related issue.
Under what circumstances does OOS occur?
OOS (Out of Specification) can be observed in final product quality control tests, intermediate product checks, stability tests, or raw material analyses. For example, tablet dissolution results below the limit, impurity values exceeding the upper limit, pH values outside the specification, or microbiological results not meeting the acceptance criteria are examples of OOS.
Is OOS only seen in the final product?
No. OOS (Out of Specification) can occur not only in final product testing, but also in raw material, semi-finished product, intermediate product, stability sample, or packaging material checks. Therefore, OOS management is important not only for the QC laboratory but for the entire quality system.
What is the difference between OOS and OOT?
OOS indicates that the result is outside the approved specification limits. OOT stands for "Out of Trend." In an OOT result, the value may still be within the specification, but it deviates from the expected trend based on historical data. Therefore, while OOS is a more direct indicator of nonconformity, OOT serves as an early warning.
Why should OOT be considered as important as OOS?
Because OOT (Out of Trend) can provide an early signal that OOS (Out of Specification) may occur in the future. For example, if the assay value consistently decreases over several batches even though it remains within the specification, this should be investigated in terms of process, raw material, or equipment.
How is OOS detected in the EBR system?
In the EBR system, OOS (Out of Specification) can be determined by comparing QC results against defined specification limits. Results can be transferred to the system via LIMS integration or entered by an authorized user. The system compares the entered value with the product, test method, and specification limits and can flag any out-of-limit results.
What are the advantages of automation in OOS detection?
Automation reduces manual comparison errors. The system can automatically indicate which value is inconsistent with which limit. This allows QA and QC teams to notice the problem faster and initiate the formal investigation process without delay.
How Does an OOS Result Affect Batch Release?
A batch with a confirmed OOS (Out of Specification) result cannot be released before the quality assessment is complete. First, an OOS investigation must be conducted to determine whether the result is laboratory-related or production/process-related, and its impact on product quality must be evaluated. It is not appropriate for the QP (Qualified Person) or the responsible manager to make a release decision before the investigation is complete.
Does OOS Always Result in Batch Rejection?
No. If OOS investigation confirms laboratory error and valid retesting procedures are applied, the result can be re-evaluated. However, if OOS is confirmed to be genuinely process or product-related, batch rejection, rework, or other quality actions may be considered.
Frequently Asked Questions About OOS Management
How is OOS investigation conducted?
OOS (Out of Specification) research is generally conducted in two stages. The first stage involves laboratory research. Sample preparation, instrument calibration, method application, standard solution, analyst error, and calculation are checked. If no laboratory error is found, the second stage examines the production process, raw materials, equipment, environmental conditions, and process parameters.
How does EBR contribute to this research?
EBR supports root cause analysis by displaying production data, process parameters, equipment usage, operator records, electronic signatures, and deviations specific to the batch where the OOS result occurred. Thus, the research is not solely dependent on laboratory results.
How is OOS connected to the deviation process?
The Outcome Stabilization (OS) result is typically opened as a formal deviation or quality incident within the quality system. This deviation record should be associated with the relevant batch, test result, QC report, production step, and CAPA actions, if any. Establishing this linkage within the EBR strengthens the traceability of the incident.
Why is deviation linkage important?
Because the auditor wants to see not only whether the OOS result was noticed, but also how it was investigated, what root cause was found, and what actions were taken. Establishing a clear link between batch registration, deviation, and CAPA makes this process defensible.
When will CAPA be activated as a result of OOS?
CAPA should be opened when the OOS result is due to a systemic, recurring root cause affecting product quality. For example, recurring nonconformities stemming from lack of method application, equipment problems, process variability, insufficient training, or raw material issues may necessitate CAPA.
Is CAPA mandatory for every OOS?
No. Not every OOS automatically requires CAPA. However, each OOS should be investigated and a reasoned assessment should be made as to whether CAPA is required. If CAPA is not enabled, the reason should be explained in the quality record.
How is OOS data used in ePQR?
OOS data is a critical indicator in ePQR and annual product quality assessment processes. The number of OOSs per product, test type, root cause distribution, repetition rate, CAPA effectiveness, and trend of change over the years can be examined. This analysis shows whether the process and quality control system are under control.
What does the OOS trend indicate?
An increase in the number of OOS (Out of Specification) occurrences in a particular product, even in equipment or test method, may indicate a systemic problem. This could point to a need for process improvement, method review, equipment maintenance, or training.
How does Centra support EBR OOS management?
Centra EBR can support OOS management with its features such as associating QC results with batch records, making out-of-limit values visible, electronic signatures, audit trails, deviation linkage, and reporting structures. This allows for faster detection, more accurate investigation, and stronger linkage of out-of-specification results to quality processes.
How to get started in digitizing OOS management?
Businesses must first determine which test results will be tracked via EBR or LIMS, how specification limits will be managed, and which deviation/CAPA flow will be triggered when an OOS occurs. Centra can be contacted via their information page to link OOS management with electronic batch records.
