Quality Risk Management — How Much Evidence Is Enough

ICH Q9(R1) as a loop, not a form: the risk-management toolbox (FMEA, FTA, HACCP, HAZOP, risk ranking and filtering, Ishikawa/PHA), FMEA in action, and how a risk assessment becomes a control strategy — worked through the nitrosamine risk assessments.
A banner titled 'Quality Risk Management — How Much Evidence Is Enough?' with the tagline 'Focus Effort. Control What Matters. Protect Patients.' and the note that ICH Q9(R1) is a science- and risk-based approach to identify, evaluate, control, and review risks across the product lifecycle. Panels: (1) The One Idea — the two governing principles: risk evaluation is grounded in scientific knowledge and links to patient protection; effort, formality, and documentation are proportionate to risk, with a note that risk management focuses budget on failures that would actually hurt a patient without gold-plating the rest; (2) The ICH Q9(R1) Process — a continuous four-stage loop around 'Quality Risk Management': Risk Assessment (identify, analyze, evaluate — what could go wrong, how likely, how severe, is it acceptable), Risk Control (reduce or accept — change the design, implement controls, accept residual risk), Risk Communication (share and discuss with all stakeholders), Risk Review (monitor and revise when new information emerges) — captioned as a living process across the product lifecycle, not a form to be filed; (3) From Risk Assessment to Control Strategy — a five-step vertical flow (understand the product and process per Q8/Q9/Q10; identify and assess risks — CQAs, method parameters, process steps; implement controls — method design, robustness, specifications, monitoring; control strategy — the planned set of controls that assures quality and performance; lifecycle management — review and adapt per Q12/Q14) paired with its outputs (CQAs and CPPs, analytical method controls, specifications under Q6, the stability program under Q1, monitoring and continued verification, regulatory submissions) and the quote that risk management turns knowledge into decisions, and decisions into patient protection; (4) Hazard vs. Risk — a hazard is the potential to cause harm ('this solvent is toxic'), risk is the probability of that harm and its severity ('at the residual level detected by this method, exposure is under 1% of the PDE'), with the reminder that formality is a dial, not a switch — one page or a full FMEA can both be appropriate if justified by the risk; (5) Risk-Management Toolbox — a table of six tools: FMEA/FMECA (failures of a process or method built from many steps, the workhorse in analytical development), fault tree analysis/FTA (working backward from one defined failure, good for OOS root-cause work), HACCP (identifying and controlling critical points, origin in food safety, useful in manufacturing), HAZOP (deviations from design intent, a guided-word approach common in process/engineering), risk ranking and filtering (comparing many risks across a portfolio, useful for site- and portfolio-level decisions), Ishikawa (fishbone)/PHA (structuring a first-pass hazard identification, often the front end of an FMEA); (6) FMEA in Action, an analytical-method example — a table walking five steps (sample preparation, chromatography, detection, data analysis, system suitability) each with a failure mode, its effect on the patient/decision, Severity, Occurrence, Detection, the resulting RPN, and a corrective action, with the reminder that RPN = Severity × Occurrence × Detection, a high Detection score means poorly detected (the scale runs backward), and every action gets a re-score to confirm risk reduction; (7) Worked Example — Nitrosamine Risk Assessment, a real-world QRM case walking six numbered steps (identify the hazard — potent mutagenic carcinogens present in multiple products, triggered by the valsartan recalls; analyze the risk — synthetic route, nitrite sources, secondary amines, recovered solvents, water, confirmatory testing; evaluate the risk against acceptable-intake thresholds; control the risk — route changes, nitrite scavengers, tighter ppb-level specifications; communicate — share with regulators, document decisions, meet deadlines like EMA Article 5(3); review — ongoing monitoring and periodic reassessment as new information emerges), beside a chemical structure of NDMA (N-nitrosodimethylamine) and a chromatogram showing sensitive LC–MS/MS detection at nanogram levels, with the note that the ability to detect a nitrosamine at its acceptable intake was a fundamental part of the risk conclusion — an analytical issue; (8) A Typical Risk Matrix — a 5×5 severity-by-occurrence grid color-coded from green (low risk, acceptable) through yellow (medium risk, consider action) to red (high risk, needs action); (9) Key Takeaways — use scientific knowledge to focus effort on what matters for the patient; match the level of effort and documentation to the level of risk; risk management is a loop — assess, control, communicate, and review; FMEA is powerful but has limitations, don't over-trust the number; a control strategy is the output of risk management, not a separate exercise; (10) Connection to Other ICH Guidelines — a six-box chain: Q8 Development (build knowledge and design quality into the product), Q9 Risk Management (identify, evaluate, control, and review risks), Q10 Lifecycle (a lifecycle approach to quality), Q12 Change Management (manage changes based on risk), Q14 Analytical Development (method design, MODR, and control strategy), Q6/Q1 Specifications & Stability (numeric risk decisions); (11) For Discussion — five questions: where to draw the line between a hazard and a risk in analytical work; how to determine the right level of formality for a given decision; which failure modes in the FMEA example concern you most and why; how the nitrosamine case illustrates the importance of analytical detection; how a risk assessment translates into method design and specification. Footer: 'Science + Risk-Based Decisions = Better Medicines for Patients,' Temple University branding, and the tagline 'All science ultimately serves people.'

The one idea

Two principles govern quality risk management: the evaluation of risk is grounded in scientific knowledge and ultimately links to protection of the patient; and the level of effort, formality, and documentation is proportionate to the level of risk.

Every analytical decision spends a finite budget of time, money, and attention. Risk management is how you point that budget at the failures that would actually hurt a patient, and stop gold-plating the ones that wouldn’t. It is the machinery behind “scientifically justified” — the phrase that appears in almost every ICH guideline and is doing a lot of quiet work.

The ICH Q9 framework

ICH Q9(R1)Quality Risk Management (the R1 revision, adopted 2023, added guidance on subjectivity, the hazard-versus-risk distinction, formality, and risk-based decision-making). The process is a loop, not a form:

StageWhat happensAnalytical example
Risk assessment — identificationWhat could go wrong?A co-eluting degradant is not resolved from the API
Risk assessment — analysisHow likely, how severe, how detectable?Estimate occurrence from forced-degradation data; severity from the degradant’s qualification threshold; detection from method specificity
Risk assessment — evaluationIs that acceptable against defined criteria?Compare against a risk threshold agreed before the assessment
Risk control — reductionChange the design to lower likelihood or raise detectionSwitch to an orthogonal column; add a peak-purity check
Risk control — acceptanceSome residual risk is accepted, explicitly and on the recordDocument the residual and the justification
Risk communicationThe assessment and decisions are shared with everyone who acts on themThe control strategy, the filing, the SOP
Risk reviewRevisit when something changesA new impurity at month 9 of stability reopens the assessment

Two ideas from Q9(R1) matter for the analyst:

  • Hazard is not risk. A hazard is the potential to cause harm; risk combines the probability of that harm with its severity. “This solvent is toxic” is a hazard statement; “at the residual level this method can detect, the exposure is X% of the PDE” is a risk statement.
  • Formality is a dial, not a switch. A one-line rationale, a risk-ranking table, and a full cross-functional FMEA are all valid quality risk management — the guideline asks you to match the formality to what is at stake, and to say why.

The toolbox

Each tool below gets its own full walkthrough — mechanics, a worked analytical example, and where it breaks down:

ToolBest forNotes
FMEA / FMECAFailures of a process or method built from many stepsThe workhorse in analytical development — full walkthrough →
Fault tree analysis (FTA)Working backward from one defined failure to its contributing causesGood for OOS root-cause work
HACCPIdentifying and controlling critical points in a processOrigin in food safety; maps well to manufacturing
HAZOPDeviations from design intent, guided-word by guided-wordMore common in process/engineering than in the QC lab
Risk ranking and filteringComparing many risks that don’t share a scalePortfolio-level and site-level decisions
Ishikawa (fishbone) / PHAStructuring a first-pass hazard identificationOften the front end of an FMEA

FMEA in action

Failure Mode and Effects Analysis decomposes a method or process into steps, and for each step asks: what could fail (failure mode), what would that do (effect), why would it happen (cause), and how would we catch it (controls). Each mode is scored:

Risk Priority Number = Severity × Occurrence × Detection

  • Severity — how bad the effect is for the patient or the decision (a wrong release decision scores high; a re-run scores low).
  • Occurrence — how often the cause is expected to produce the failure.
  • Detection — how likely the existing controls are to catch it before it matters. High detection score = poorly detected — this scale runs backward, and it is where most FMEAs go wrong.

Modes with a high RPN, or a high severity regardless of RPN, get an action; then the mode is re-scored to show the action worked. The number is easy to game and easy to over-trust — see the full FMEA walkthrough for a worked multi-failure-mode example and the known weaknesses worth teaching so students don’t over-trust it.

From risk assessment to control strategy

A control strategy is the planned set of controls — derived from current product and process understanding — that assures performance and quality. It is the output of risk management, not a separate exercise:

  • Attribute risk assessment decides which quality attributes are critical (CQAs) and therefore need a specification and a method.
  • Method risk assessment (an FMEA against the analytical target profile) decides which method parameters need to be controlled, and how tightly — this is where a robustness study is a risk-control activity, not a validation checkbox.
  • The specification (Q6) and the stability program (Q1) are risk decisions in numeric form.
  • Under the analytical procedure lifecycle, what counts as a reportable change to a method is set by the risk it carries.

Worked example — nitrosamine risk assessments. Between 2018 and 2023 every marketing authorization holder had to assess every product for the risk of N-nitrosamine impurities (NDMA, NDEA, and drug-specific nitrosamines), triggered by the valsartan recalls. The assessment is a textbook QRM: identify the hazard (potent mutagenic carcinogens), analyze the risk (synthetic route, nitrite sources, secondary amines, recovered solvents, water; then confirmatory testing), control it (route changes, nitrite scavengers, tightened limits at ppb levels), and communicate it (to the agency, on a deadline). It also shows the analyst’s exposure directly: the risk conclusion depended entirely on whether a method existed that could see a nitrosamine at its acceptable intake — a detection problem.


Source note. Risk management is anchored in ICH Q9(R1), with ICH Q8(R2), Q10, and Q14. FMEA methodology follows IEC 60812 and the AIAG-VDA FMEA handbook. The nitrosamine case follows the EMA/FDA guidance and Article 5(3) referral outcomes. (Instructor: confirm the Q9(R1) adoption date and current EMA nitrosamine guidance revision.)


FMEA in Detail — Scoring, Scaling, and Where It Breaks

Failure Mode and Effects Analysis worked end to end on an HPLC assay method: the RPN formula, a full failure-mode table with a before/after action, why detection runs backward, and the known weaknesses that make RPN easy to over-trust.

Fault Tree Analysis — Working Backward From a Failure

FTA starts from a failure that already happened and works backward through AND/OR logic to its contributing causes — the standard tool for an OOS root-cause investigation, and the mirror image of FMEA’s forward-looking approach.

HACCP — Critical Control Points, Borrowed From Food Safety

Hazard Analysis and Critical Control Points asks a narrower question than FMEA: not every failure mode in a process, but where the few points are whose failure directly threatens the patient — worked through a sterile-fill bioburden-control example.

HAZOP — Deviations From Design Intent

Hazard and Operability study asks, guided word by guided word, what happens if a process parameter is too much, too little, reversed, or accompanied by something unintended — a process/engineering tool applied here to a chromatography example.

Risk Ranking and Filtering — Comparing Risks That Don't Share a Scale

When risks come from different processes, products, or sites and don’t share a common scale, risk ranking and filtering normalizes them against weighted criteria to build one prioritized list — worked through a site quality council’s quarterly resourcing decision.

Ishikawa / Fishbone / PHA — Structuring the First Pass

Before an FMEA can score failure modes, it needs a reasonably complete list of them — fishbone diagrams and Preliminary Hazard Analysis are how that list gets brainstormed systematically, worked through an unexpected-peak example that feeds directly into an FMEA.