What is in Arc A
- What "OOS" actually means — vocabulary, the OOS/OOT distinction, and the scope of FDA's OOS guidance
- United States v. Barr Laboratories — the 1993 decision that built the two-phase investigation framework still in use today
- The two-phase investigation framework — what Phase I and Phase II actually require, and when one escalates into the other
- 21 CFR 211.192 — the regulatory anchor for this entire course, read clause by clause
Each module ends with a knowledge check. This arc lays the foundation for the rest of the course — the Phase I laboratory investigation and the valid/invalid OOS distinction (Arc B), the Phase II full-scale investigation and disposition decision (Arc C), conclusive root cause and CAPA effectiveness (Arc D), and enforcement case studies (Arc E).
Every substantive statement in this course carries one of two marks, the same convention used throughout the Veritas curriculum. Requirement means the statement is traceable to a named clause of a regulation, a guidance document, or a holding of a decided case, cited where it appears. Practice means it is established, defensible industry convention — the way competent quality units actually operate — but not language written into a regulation or a court's holding itself.
This distinction matters more than usual in this course. Whether an OOS result may be invalidated, and what a CAPA has to include before it counts as valid, are among the most heavily scrutinized distinctions in pharmaceutical quality — get the requirement/practice line wrong here and you risk exactly the kind of unsupported invalidation the warning letters in Arc E were written about.
What "OOS" actually means
Before this course can explain how to investigate an OOS result properly, it has to be precise about what the term covers — and, just as importantly, what it does not.
A1.1 Defining OOS
Practice An out-of-specification (OOS) result is a test result that falls outside the specifications or acceptance criteria established in the marketing application, a compendial monograph, or an approved written procedure. The term itself is industry and FDA-guidance vocabulary rather than a phrase defined by name in 21 CFR — the regulation that actually creates the investigation obligation, 211.192, uses broader language, covered in Module A4. What makes a result OOS is its relationship to a specification, not how surprising it is, how it compares to history, or how confident the analyst feels about it.
A1.2 OOS versus OOT: two different signals
Practice An out-of-trend (OOT) result is a result that remains within specification but breaks from the product's established historical pattern — a stability timepoint drifting in a direction inconsistent with prior data for that batch or product, for example. An OOT result is not itself an OOS result and does not, by itself, trigger a 211.192 investigation in the way a specification failure does. It does, however, warrant its own evaluation, since a trend break can be an early signal of a problem that has not yet produced an outright failure.
- OOS — out-of-specification — a result outside the specification or acceptance criterion itself. Triggers the 211.192 investigation obligation covered in Module A4.
- OOT — out-of-trend — a result inside specification but inconsistent with the established historical pattern for that product or process. Not itself an OOS event; evaluated on its own terms, often as part of ongoing trend monitoring.
- Discrepancy — the broader term 211.192 actually uses, reaching any unexplained inconsistency in production and control records, of which a specification failure is one example. Covered in full in Module A4.
Practice A third term, atypical result (sometimes "aberrant" or "anomalous"), appears throughout the industry without one agreed meaning. Some firms use it as a plain synonym for the OOT concept just described. Others define it as its own, narrower category: a result that is within specification but unexpected, irregular, or otherwise abnormal in some way that is not necessarily a trend break at all — an unusual chromatographic peak shape or an unexpected color on a single, isolated result, with no history to compare it against. Still others use "atypical" as a broad umbrella term covering OOS, OOT, and any other unusual result that should not be ignored or rationalized away. None of these usages is wrong. What matters, whichever label a given SOP uses, is that the underlying result actually gets evaluated on its merits rather than the label doing the work of dismissing it.
A1.3 The scope of FDA's OOS guidance
Requirement FDA's Guidance for Industry: Investigating Out-of-Specification (OOS) Test Results for Pharmaceutical Production — originally issued in 2006 and current in its Level 2 revision, issued May 2022 — is scoped to chemistry-based laboratory testing of drugs regulated by CDER: active pharmaceutical ingredients, excipients, in-process materials, and finished drug products under 21 CFR Parts 210 and 211. It is one evolving document, not two separate guidances; "Level 2 revision" describes how substantially FDA revised its own prior version, not a newer document superseding an unrelated older one.
Because the guidance is built around chemistry-based testing, its treatment of outlier tests and retesting is written with chemical assays in mind. Biological and microbiological assay methods are treated differently — both by the guidance itself and, as Module A2 covers, by the case law that preceded it — specifically because biological assays carry a level of innate variability that chemical assays generally do not. Arc B returns to this distinction when it works through what invalidates an OOS result and what does not.
Module A1 — what "OOS" actually means
Six questions.
United States v. Barr Laboratories
Almost everything this course covers about how an OOS investigation is supposed to work traces back to a single 1993 federal court decision — one that predates FDA's own OOS guidance by more than a decade.
A2.1 The case
Requirement United States v. Barr Laboratories, Inc., 812 F. Supp. 458 (D.N.J. 1993), arose from FDA's action against a generic drug manufacturer over its handling of OOS test results. The court's opinion did far more than resolve that one dispute — it laid out, in detail, what a legally defensible OOS investigation actually requires, and it remains the reference point FDA's own later guidance was built on.
The court's central holding is the idea this entire course returns to again and again: an OOS result is not, by itself, proof that a batch failed. It is a trigger for an investigation. Only if that investigation cannot identify an assignable, documented cause — a genuine laboratory error, for example — does the result stand as a true, confirmed batch failure.
A2.2 The two-phase framework
Requirement The court described an informal Phase One review for a single OOS result — the analyst reports the result to a supervisor, and the two of them review the test notebook, the procedure, the calculations, and the equipment together — requiring, in the court's words, "more than a laboratory investigation consisting principally of retesting." Where Phase One does not resolve the matter, or where the failure is serious or recurring, the court described a formal Phase Two investigation: a full-scale inquiry reaching beyond the laboratory bench into the manufacturing process itself.
Practice This is not a coincidence of naming. FDA's own guidance, covered in Module A3, adopts essentially the same two-phase structure — Phase I and Phase II — and elaborates on it with specific documentation requirements. The vocabulary in the current guidance is the case law's vocabulary, formalized.
A2.3 Retesting, resampling, outlier tests, and averaging
Requirement The court held that retesting is proper "only after a failure investigation is underway," and it specifically rejected Barr's own rigid "two-out-of-three" retest procedure — the practice of retesting a fixed number of times and accepting the majority result — because it substituted a predetermined formula for the case-by-case scientific judgment an investigation actually requires.
Requirement On resampling — testing a new specimen entirely, rather than retesting the original sample — the court required "evidence, not mere suspicion" that the original sample was not representative of the batch before resampling could be justified.
“...the USP’s silence...with respect to chemical testing and outliers is prohibitory.”United States v. Barr Laboratories, Inc., 812 F. Supp. 458 (D.N.J. 1993).
Requirement The court held that outlier tests — a statistical method for excluding an extreme result from a data set — are not appropriate for chemical assays, reserving them for biological or antibiotic assays given their "substantial innate variability." On averaging, the court warned that relying on an average figure "without examining and explaining" the individual OOS results within it is "highly misleading and unacceptable," because averaging can "hide[]" the variability among individual test results that the investigation is supposed to be examining in the first place.
Module A2 — Barr Laboratories
Five questions.
The two-phase investigation framework
FDA's current OOS guidance turns Barr Laboratories's framework into a specific, documented procedure. This module works through what each phase actually requires.
A3.1 Phase I: the laboratory investigation
Requirement A single OOS result triggers an informal Phase I laboratory investigation, conducted by the analyst together with a supervisor. FDA's guidance describes a specific checklist of steps this investigation should cover:
- Discuss the test method with the analyst — confirm the analyst's knowledge of, and performance against, the correct procedure. Aimed at identifying analyst-level or procedural errors first.
- Examine the raw data — review chromatograms, spectra, and other instrumental output directly for anomalies, rather than relying only on the reported summary result.
- Verify the calculations — confirm that the arithmetic and any data transformations applied to the raw data are scientifically sound.
- Confirm instrument performance — check that the equipment used was functioning correctly at the time of testing.
- Confirm reference standards, solvents, and reagents — verify that these met their own quality control specifications before the test was run.
- Evaluate method performance — compare the result against the method's validation data and the product's own testing history.
- Document and preserve the assessment — fully record the Phase I review itself, regardless of outcome. This record is what later distinguishes a genuine investigation from an after-the-fact justification.
Requirement Where Phase I identifies a genuine, documented laboratory error, FDA's guidance is direct about the consequence: "In the case of a clearly identified laboratory error, the retest results would substitute for the original test result." Where Phase I does not identify an assignable cause, the matter is not resolved — it escalates.
A3.2 Phase II: the full-scale investigation
Requirement A formal Phase II investigation is triggered when Phase I does not identify an assignable cause, or when the failure is serious enough (or has recurred often enough) to warrant it. FDA's guidance specifies what a Phase II investigation must document:
| Element | Phase I — laboratory investigation | Phase II — full-scale investigation |
|---|---|---|
| Trigger | A single OOS result | Phase I finds no assignable cause, or the failure is serious/recurring |
| Conducted by | Analyst and supervisor | Quality unit, extending into manufacturing and other functions as needed |
| Scope | The test itself — method, data, calculations, instrument, standards | The manufacturing process and any other batches or products that may share the cause |
| Must document | The Phase I checklist review and its outcome | Reason for the investigation; manufacturing-process summary; documented cause assignment; prior-occurrence review; corrective actions |
| Possible outcome | Identified lab error → retest substitutes for original result | Confirmed batch failure, or an assignable non-lab cause with a corrective action plan |
Requirement Specifically, FDA's guidance requires a Phase II investigation to include: a clear statement of the reason for the investigation; a summary of the aspects of the manufacturing process that may have caused the problem; the results of a documentation review, with an assignment of actual or probable cause; the results of a review for prior occurrence of the same problem; and a description of the corrective actions taken.
Nothing in either phase treats retesting, resampling, or writing an investigation report as substitutes for actually finding a cause. Arc B works through exactly where that line sits — the difference between a Phase I review that legitimately identifies a laboratory error, and one that simply documents enough activity to make an inconvenient result disappear.
Requirement FDA's guidance and Barr Laboratories describe two phases, but they are not the only investigation framework in circulation. The UK's Medicines and Healthcare products Regulatory Agency (MHRA) has published its own OOS/OOT investigation guidance describing four stages: Phase Ia and Phase Ib (together covering the ground this module calls Phase I), Phase II, and a further Phase III — a synthesis stage that reviews the completed laboratory and manufacturing investigations together, determines whether other batches or products are affected, and drives the disposition decision and the resulting corrective and preventive action.
Practice Separately, and without a regulatory citation behind it, many firms' own internal SOPs use the same "Phase III" label for a different kind of escalation: what happens when a Phase II investigation still cannot identify a manufacturing-related root cause, and the matter moves to R&D for deeper technical characterization — identifying an unknown chromatographic peak, for example, or manufacturing pilot-scale batches to reproduce and study the failure under controlled conditions. This is a real, common practice, but it is a firm-level extension built on top of the two-phase framework described above, not a codified regulatory requirement in its own right, and it is not the same thing as MHRA's published Phase III even though the two share a name. Arc C returns to both versions in depth.
Module A3 — the two-phase framework
Six questions.
21 CFR 211.192
Every idea in this arc — OOS vocabulary, Barr Laboratories, the two-phase framework — ultimately exists to satisfy one regulation. This module reads it clause by clause.
A4.1 The text, in full
Requirement 21 CFR 211.192, titled "Production record review," reads as follows, in its entirety:
“All drug product production and control records, including those for packaging and labeling, shall be reviewed and approved by the quality control unit to determine compliance with all established, approved written procedures before a batch is released or distributed. Any unexplained discrepancy (including a percentage of theoretical yield exceeding the maximum or minimum percentages established in master production and control records) or the failure of a batch or any of its components to meet any of its specifications shall be thoroughly investigated, whether or not the batch has already been distributed. The investigation shall extend to other batches of the same drug product and other drug products that may have been associated with the specific failure or discrepancy. A written record of the investigation shall be made and shall include the conclusions and followup.”21 CFR § 211.192, Production record review.
A4.2 What each clause actually requires
- Quality control unit review before release — every production and control record, including packaging and labeling, must be reviewed and approved by the quality control unit against established written procedures before a batch is released or distributed. This is the gatekeeping function an OOS investigation ultimately feeds into.
- Two independent triggers — an "unexplained discrepancy" (the regulation's own example is a theoretical-yield percentage outside its established range) or a specification failure. An OOS test result is the most common trigger encountered in practice, but it is only one of two named categories.
- "Thoroughly investigated," regardless of distribution status — the obligation to investigate does not depend on whether the batch has already shipped. A batch already in commerce does not excuse or diminish the investigation requirement.
- Investigation must extend outward — to other batches of the same product, and to other products that may share the same cause. This is the regulatory basis for the "look-back" scope FDA warning letters routinely cite when a firm's investigation stopped at a single lot.
- A written record, with conclusions and followup — not merely a record that an investigation occurred, but one that states what was concluded and what was done as a result. This is the regulatory seed of the CAPA requirement Arc D builds on directly.
Practice Every idea covered so far in this arc is, in a real sense, an elaboration of this one paragraph. Barr Laboratories interpreted what "thoroughly investigated" has to mean in practice. FDA's Phase I/Phase II structure operationalizes it into a specific procedure. The distinction between OOS and OOT exists to identify, precisely, which results this regulation's investigation duty actually reaches.
Arc B goes inside Phase I in detail — what actually counts as an assignable cause, the difference between a valid and an invalid OOS result, and why "testing into compliance" is treated as a distinct, named violation rather than an aggressive-but-permissible strategy. Arc C does the same for Phase II and the disposition decision that follows it. Arc D is where this course directly takes up conclusive root cause and CAPA impact assessment — including whether every CAPA needs a monitoring and confirmation component. Arc E closes with enforcement case studies mapped to each of the ways this framework, in practice, breaks down.
Module A4 — 21 CFR 211.192
Five questions.