21 CFR 211.192
Every DSRV article whose Regulatory Snapshot cites 21 CFR 211.192: the enforcement case behind it, the inspection exposure it created, and what the desk would do about it.
- What has FDA cited under 21 CFR 211.192?
- 6 DSRV articles cite 21 CFR 211.192. Enforcement cases behind them: FDA Warning Letter CMS Case 732115 to ABS Corporation, July 23, 2026; Genzyme Ireland FDA Warning Letter, June 22, 2026; FDA inspectional focus on CAPA and investigation adequacy under 21 CFR §211.192, with pharmaceutical quality system expectations set by ICH Q10; FDA inspectional emphasis on investigation adequacy under 21 CFR §211.192, including OOS result invalidation without an assignable laboratory cause; Deviation and investigation documentation expectations under 21 CFR §211.192 and quality system review practice per ICH Q10; Recurring FDA 483 and warning-letter themes on inadequate investigations and CAPA effectiveness. Inspection exposure across them: 5 high, 1 moderate.
- What does DSRV recommend for 21 CFR 211.192?
- From the newest article (A Quality Unit That Averaged Away Its Own OOS Failures): The decisive control is whether the quality system forces failing data to be investigated before specifications, retest logic, or batch disposition can be changed. DSRV's matching service is the Investigation Defensibility Audit, delivered through controlled intake at /submit. DSRV is decision support, not legal advice; verify against the official source each article names.
- 4 min readHigh exposure
A Quality Unit That Averaged Away Its Own OOS Failures
FDA's July 2026 warning letter to ABS Corporation shows a Quality Unit that averaged out failing assay results, handwrote higher specification limits onto batch records during validation, and released product made with a raw material that had already failed retesting. The pattern is not sloppy paperwork. It is a Quality Unit deciding the answer before the test ran.
- Case
- FDA Warning Letter CMS Case 732115 to ABS Corporation, July 23, 2026.
- DSRV take
- The decisive control is whether the quality system forces failing data to be investigated before specifications, retest logic, or batch disposition can be changed.
- 7 min readHigh exposurecited as a tag
FDA Is Treating Discarded Evidence as a Quality Unit Failure
FDA's June 22, 2026 warning letter to Genzyme Ireland shows how undocumented retesting, discarded review artifacts, and canceled deviations now read as quality-unit governance failures. Small pharma quality teams should treat this as a warning that incomplete records are no longer a narrow documentation problem.
- Case
- Genzyme Ireland FDA Warning Letter, June 22, 2026
- DSRV take
- Inspection readiness is not having enough records after the fact — it is decision trails strong enough that FDA does not have to guess what the quality unit knew, reviewed, or allowed.
- 8 min readHigh exposure
CAPA Response Strategy: What FDA Expects to See
A strong CAPA is more than a corrective fix — FDA expects a defensible root cause, a systemic corrective and preventive action, and a real effectiveness check. Here is how to structure one that holds up.
- Case
- FDA inspectional focus on CAPA and investigation adequacy under 21 CFR §211.192, with pharmaceutical quality system expectations set by ICH Q10.
- DSRV take
- A CAPA is only as defensible as the system-level cause it targets and the predefined effectiveness check that proves the fix worked.
- 8 min readHigh exposure
Weak Root Cause vs. Defensible Investigation Logic
The difference between a closed deviation and a defensible one is the reasoning. We contrast shallow root-cause shortcuts with investigation logic that withstands a reviewer's scrutiny.
- Case
- FDA inspectional emphasis on investigation adequacy under 21 CFR §211.192, including OOS result invalidation without an assignable laboratory cause.
- DSRV take
- A reviewer reads an investigation backward from the conclusion - defensible logic documents the alternatives considered and why the evidence rules them out.
- 6 min readModerate exposure
Reviewer-Style Questions for Deviation Reports
Before a deviation report leaves your desk, run it past the questions a quality reviewer or inspector will ask. This checklist turns self-review into a defensibility test.
- Case
- Deviation and investigation documentation expectations under 21 CFR §211.192 and quality system review practice per ICH Q10.
- DSRV take
- Every "no" on a reviewer-style pre-flight check is a question you will eventually have to answer - better now, with the team and evidence at hand, than during an inspection.
- 9 min readHigh exposure
Usable Procedures Are Not Defensible Quality Decisions
Modern AI tools can make SOPs clearer and easier to follow. But inspectors do not cite companies for unclear formatting. They cite them for weak investigations, missing escalation logic, and decisions that cannot be traced to evidence. Usability and defensibility are different problems.
- Case
- Recurring FDA 483 and warning-letter themes on inadequate investigations and CAPA effectiveness.
- DSRV take
- Making an SOP easier to read does not make a quality decision defensible - defensibility comes from documented reasoning and traceable evidence.
Investigation Defensibility Audit
Bring the document that has to hold up under 21 CFR 211.192. DSRV maps the evidence, names the gaps, and routes judgment calls to human review. Controlled intake, no public file upload.
Regulatory intelligence and interpretation, not legal advice. Verify against the official FDA or ICH source each article names.