Important Potential Risks

Introduction

Important Potential Risks are among the most difficult safety concerns to classify correctly within a Risk Management Plan (RMP). Unlike Important Identified Risks, a causal relationship has not been established. Unlike Missing Information, the concern relates to a specific potential adverse outcome rather than a gap in available data.

The category exists to capture safety concerns that may represent genuine risks but for which available evidence remains insufficient to confirm a causal association. The challenge for RMP authors is determining when the available evidence justifies inclusion as an Important Potential Risk, when it justifies reclassification to an Important Identified Risk, when it can be removed, and what evidence thresholds should drive those lifecycle decisions.

This article offers practical guidance, an inspection‑ready decision checklist, an evidence‑threshold table with example justifications and sample RMP wording, and governance and implementation considerations intended to support consistent, defendable regulatory submissions and responses during inspection.

Regulatory Concept

An Important Potential Risk is:

A risk for which there is some basis for suspicion of an association with the medicinal product, but where the available evidence is insufficient to establish causality.

Two elements are required:

Potential Risk + Importance = Important Potential Risk

Both an evidential signal (basis for suspicion) and an importance assessment (seriousness, public-health relevance or potential to change the benefit-risk balance) are required; neither alone suffices. Regulatory expectations are set out in EMA GVP Module V and related guidance: documentation should demonstrate the evidence considered, rationale for decisions, proposed pharmacovigilance measures, and planned reviews.

Position of Potential Risks in Risk Management

Potential risks sit between observation and confirmation:

Observation → Signal → Potential Risk → Identified Risk

Not every signal becomes a potential risk; not every potential risk becomes an identified risk. Many concerns are dismissed following further evaluation. The Important Potential Risk category ensures potentially important concerns receive appropriate attention while uncertainty remains.

Sources of Potential Risks

Potential risks commonly originate from:

• Signal management (spontaneous reports, disproportionality analyses)
• Clinical trial imbalances or unexpected events
• Non‑clinical findings with plausible human relevance
• Class‑effects observed with related products
• Scientific literature (case-series, pharmacovigilance reports)
• Post-authorisation study signals
• Regulatory assessments or partner submissions

Each source carries different evidentiary weight and should be recorded and assessed consistently.

When a Signal Should — and Should Not — Be a Potential Risk

Signals are observations requiring evaluation. Important Potential Risks are safety concerns judged sufficiently plausible and important to justify further activity. Common errors include automatic promotion of every signal into the Safety Specification, conflation with Missing Information, and retaining obsolete concerns. The core question is: does current evidence plus importance justify inclusion in the Safety Specification now, or should the concern be managed solely in the signal‑tracking process until more evidence accrues?

Importance: Clinical and Public Health Considerations

Importance is assessed by considering:

• Severity (life‑threatening, permanently disabling outcomes)
• Frequency potential and population exposure
• Impact on benefit‑risk balance and clinical decision‑making
• Potential to require risk minimisation measures
• Public‑health implications (e.g., paediatric use, pregnancy, widely used products)

A low‑severity or theoretical concern without plausible mechanism or impact often does not meet the ‘important’ threshold.

Risk Characterisation and Lifecycle Options

For each Important Potential Risk, document:

• Nature and description of the concern (preferred terms and definitions)
• Source(s) of evidence (case reports, studies, non‑clinical data)
• Plausibility and biological mechanism
• Susceptible populations and risk factors
• Available evidence and key uncertainties
• Planned additional pharmacovigilance and risk minimisation
• Review frequency and triggers for reclassification or removal

Possible lifecycle outcomes: retain as Important Potential Risk, reclassify as Important Identified Risk, remove from Safety Specification. Decisions must be periodically reviewed and justified.

Additional Pharmacovigilance and Risk Minimisation

Important Potential Risks commonly drive additional pharmacovigilance activities (PASS, registries, enhanced monitoring) intended to reduce uncertainty. Risk minimisation is less commonly justified for potential than identified risks, but can be proportionate where preliminary evidence suggests high severity and plausible causal link (e.g., temporary contraindications while evaluation proceeds). Any proposed measures should be backed by a rationale and commensurate with evidence and public health impact.

Common Regulatory Deficiencies

Regulators frequently identify:

• Excessive numbers of potential risks without clear prioritisation
• Weak scientific justification for inclusion
• Poorly documented decision-making and rationale
• Failure to remove obsolete potential risks after evidence accrues
• Confusion between Missing Information and Important Potential Risks
• Automatic promotion of signals without adequate evaluation

Inspection and regulatory reviewers expect structured, documented and defendable decision-making.

Inspection and Audit Considerations

Inspectors will typically examine:

• The evidence dossier supporting classification (signal validation, case narratives)
• Minutes and records of cross-functional risk review meetings
• SOPs governing signal-to-RMP escalation
• Causality assessments and expert panel opinions
• Protocols and reports for additional pharmacovigilance measures
• Documentation of periodic reviews, decisions, and timelines
• Communications with regulators and responses to questions
• How decisions were operationalised (e.g., labeling proposals, healthcare professional communications)

Being "inspection‑ready" requires preserved evidence, clear traceability from signal to decision, sign‑offs, and archival of decision records.

Inspection‑Ready Decision Checklist

Use this checklist when deciding to classify, retain, reclassify or remove an Important Potential Risk. Maintain the completed checklist and supporting evidence in the RMP decision file (electronic or paper) to ensure inspection readiness.

Checklist (core questions and documentation to attach):

1. Identification and description
2. Q: Is the event clearly defined (MedDRA PTs, case definition)?
3. Attach: definition document, list of terms used.
4. Source and validation of signal
5. Q: What source(s) generated the signal? (spontaneous reports, trials, literature, class effect)
6. Attach: signal validation report, signal detection output, search strategy.
7. Evidence summary
8. Q: What evidence supports an association? (number of cases, temporal relationship, biologic plausibility, dose‑response, dechallenge/rechallenge, epidemiologic data)
9. Attach: case series, line listings, study reports, literature copies.
10. Importance assessment
11. Q: Is the outcome serious or of public‑health significance? Could it affect benefit‑risk?
12. Attach: clinical impact assessment, epidemiology estimates, exposure data.
13. Alternative explanations
14. Q: Are there confounders, background incidence, comorbidity or concomitant medicines explaining the signal?
15. Attach: analysis of confounders, comparator data.
16. Weight of evidence and plausibility
17. Q: Does the totality of evidence (consistency, strength, temporality, plausibility) meet the threshold for potential risk?
18. Attach: causality narrative and grading against structured criteria (e.g., modified Bradford Hill).
19. Importance justification
20. Q: Why is the concern ‘important’ for risk management rather than a routine signal only?
21. Attach: rationale statement referencing clinical severity, exposure scope, or potential impact on benefit‑risk.
22. Proposed regulatory and risk management actions
23. Q: What additional PV study or measure is proposed? Is it proportionate?
24. Attach: PV plan, PASS protocol synopsis, timeline and milestones.
25. Review plan
26. Q: What are review triggers, timelines and decision points for reclassification/removal?
27. Attach: review schedule and criteria.
28. Governance and approvals
    • Q: Have relevant stakeholders (clinical safety lead, epidemiologist, medical affairs, regulatory affairs, QPPV) reviewed and signed off?
    • Attach: meeting minutes, approval sheet, version control note.
29. Consideration of label change and public communication
    • Q: Does the evidence warrant immediate communication to regulators or HCPs?
    • Attach: communication plan, draft label text if applicable.
30. Inspection readiness
    • Q: Is the complete decision package accessible, versioned, and archived?
    • Attach: file location and access instructions for inspection.

Minimum required documents to store with each decision: - Signal validation report - Case narratives/line listings and aggregated summaries - Structured benefit‑risk/causality narrative - Proposed PV/RMM activities and their rationale - Review and approval records with timestamps - Copy of previous reviews and decisions on the same concern (audit trail)

Retention and accessibility: - Keep the decision file readily accessible for the life of the product and at least the period required by applicable legislation. Ensure secure archiving and change control.

Evidence‑Threshold Matrix

This matrix assists teams to judge the strength of evidence and to map that evidence to decisions. Use the matrix as a decision aid, not an absolute rule: context, severity and potential public health impact can raise or lower thresholds.

Table A — Weighting of evidence types (relative contribution toward classification)

Table B — Decision thresholds and example actions

Notes on applying thresholds: - Severity and public health impact may lower thresholds for inclusion. For example, a single case of teratogenicity with biologic plausibility may justify temporary inclusion and rapid further investigation. - The existence of robust mechanistic data may elevate the weight of limited clinical reports. - Negative evidence (absence of signal in well‑designed studies with adequate follow‑up) is required for removal and should be documented in detail.

Decision Examples with Sample Wording

Below are concise, inspection‑oriented examples showing justificatory text and RMP wording for typical scenarios.

1. Hepatotoxicity (trial imbalance + post‑marketing reports)
2. Evidence summary: Phase III trial showed ALT >3×ULN imbalance (n=6 vs n=1), multiple post‑marketing reports with similar phenotype, non‑clinical hepatocellular degeneration observed.
3. Justification: "Given the trial imbalance and post‑marketing case series demonstrating consistent clinical pattern, plus supportive preclinical findings, severe hepatotoxicity meets the threshold for classification as an Important Potential Risk pending epidemiologic evaluation."

4. RMP wording: "Potential for severe hepatotoxicity has been identified based on clinical trial imbalances and post‑marketing reports. The potential association is plausible but remains unconfirmed. Planned additional PV activities include a retrospective cohort study and enhanced spontaneous report follow‑up."

5. Malignancy (class effect signal)

6. Evidence summary: Malignancy signal observed for other agents in same class; early spontaneous reports in the product registry inconsistent.
7. Justification: "The class effect for malignancy in products with the same mechanism justifies inclusion as an Important Potential Risk to ensure monitoring while available exposure increases."

8. RMP wording: "Potential increased risk of malignancy based on class‑effect observations. Currently insufficient evidence to establish causality for this product; active monitoring via a long‑term registry is planned."

9. Cardiovascular events (single case but plausible mechanism, high severity)

10. Evidence summary: Single well‑documented myocardial infarction temporally related to exposure in a young patient without risk factors; plausible pro‑thrombotic mechanism from preclinical models.
11. Justification: "Given the severity and biological plausibility, temporary classification as an Important Potential Risk is warranted pending targeted case ascertainment and epidemiologic evaluation."

12. RMP wording: "Potential increased risk of arterial thrombotic events based on a serious post‑marketing report and mechanistic evidence. Inclusion as an Important Potential Risk is temporary pending further investigation."

13. Pregnancy (lack of adequate data vs observed reports)

14. Evidence summary: Limited exposure data; a small number of congenital anomaly reports inconsistent in phenotype.
15. Justification: "Insufficient exposure data to determine risk; however, the seriousness of potential outcomes warrants retaining as Missing Information rather than an Important Potential Risk unless consistent signals emerge."
16. RMP wording: "Use in pregnancy is classified as Missing Information due to insufficient data on pregnancy outcomes. Spontaneous reports will be monitored closely; classification as Important Potential Risk will be reconsidered if consistent teratogenic signals emerge."

Practical Implementation Details

Operationalising decisions requires clear SOPs, data flows, templates and metrics.

1. SOP and process controls
2. Maintain a "Signal-to-RMP" SOP defining criteria, roles, timelines, and documentation required to escalate a signal to the RMP.
3. Define minimum evidence elements to be assembled before an RMP decision meeting (see checklist).

4. Set timelines for initial escalation (e.g., within X working days of signal validation) and for decision meetings (e.g., within 30 calendar days).

5. Roles and responsibilities

6. QPPV: accountable for RMP content and regulatory communications.
7. Safety Lead/Medical Expert: clinical interpretation, proposal for classification.
8. Epidemiologist/Statistical Expert: assessment of epidemiologic data, design of PASS.
9. Signal Detection Team: identification, validation, generation of line listings.
10. Regulatory Affairs: liaison with authorities, updates to RMP/labeling.

11. Governance Body (Safety Review Committee/Risk Management Team): multidisciplinary decision maker responsible for sign‑off.

12. Decision meeting

13. Use a structured agenda: evidence presentation, plausibility discussion, importance assessment, proposed activities, review triggers, and required approvals.
14. Record minutes with explicit decision outcomes, rationale, dissenting opinions (if any), and action items.

15. Use a decision template capturing the checklist items and links to supporting documents.

16. Documentation and traceability

17. Maintain a central RMP decision file with version control and audit trail (who approved, when, and why).
18. Link RMP entries to safety database tags (MedDRA terms and SMQ mapping) and to PASS/registry protocols.

19. Store meeting minutes, causality narratives, and signal analyses for inspection and for periodic review.

20. IT and database management

21. Tag and track events in safety database with flags indicating "Candidate Potential Risk," "Important Potential Risk," "Identified Risk," or "Removed."
22. Ensure reports and line listings for a concern can be generated rapidly for inspections.

23. Maintain a cross‑reference table between safety specification items and ongoing PV activities, with status indicators and next milestone dates.

24. Metrics and KPIs

25. Time from signal validation to RMP decision
26. Number of potential risks retained > 2 years without documented review/justification
27. Number of potential risks reclassified to identified or removed per year
28. PASS start and completion timelines vs planned

29. Audit findings related to RMP decision processes

30. Version control and change management

31. Changes to the Safety Specification require a documented change control request, impact assessment, and QPPV approval.
32. Maintain a change log summarising reasons for changes, dates, and linked documents.

Governance, Escalation and Senior Oversight

1. Governance structure
2. Establish a Risk Management Governance Group (or use an existing Safety Governance Committee) to oversee RMP decisions, ensuring cross‑functional representation (PV, clinical, regulatory, epidemiology, legal, commercial where relevant).

3. Define escalation routes for contested decisions or high‑impact issues to the Executive Safety Committee or Board where appropriate.

4. Sign‑off and accountability

5. All classification, reclassification and removal decisions should be signed off by named individuals (e.g., safety lead, QPPV, head of clinical), with recorded rationale.

6. Define delegated authority levels for routine changes vs changes needing senior approval.

7. External engagement

8. Document interactions with regulators regarding potential risks, including meeting minutes, requests for advice, and written agreements—these are inspection focal points.
9. Where possible, obtain written agreement with regulators for major changes (reclassification, removal) or for planned risk minimisation measures.

Inspection Relevance — What Inspectors Look For

Inspectors focus on whether decisions are justified, documented and traceable. Common inspection checkpoints:

• Can the team demonstrate how the decision was reached? (show the decision file and minutes)
• Is there a clear causality/importance narrative referencing specific evidence?
• Are the SOPs followed? (show the Signal-to-RMP SOP and timestamps)
• Are responsibilities and sign‑offs documented and appropriate?
• Are planned studies and measures actively managed and on schedule?
• Are reasons for retaining a potential risk (or removal) scientifically defensible and proportionate?
• Are communications to regulators and stakeholders recorded and consistent with the RMP?

Prepare inspection packs that include the checklist, evidence dossier, minutes, and the RMP excerpts that reflect the decision.

Quality Assurance and Audit

• Schedule periodic internal audits of RMP decision files to ensure completeness and adherence to SOPs.
• Include RMP decisions in routine pharmacovigilance quality metrics and management reviews.
• Use audit findings to refine the evidence thresholds and decision checklist.

Appendix: Quick Reference — Sample Decision Template (to be stored with each RMP decision)

• Title of potential risk:
• Date signal validated:
• Sources of evidence (list and link):
• Summary of evidence:
• Assessment of causality plausibility (short narrative):
• Assessment of importance (severity/exposure/BR impact):
• Proposed classification (IPR / Identified / Removed / Missing Information / Routine signal only):
• Proposed PV activities and timelines:
• Review triggers and next review date:
• Governance approvals (names, roles, signatures, dates):
• File locations and links to supporting documents:
• Inspection pack reference number:

Key Takeaways

• Important Potential Risks require both evidence of a possible association and an importance assessment; both elements must be documented.
• Use an inspection‑ready decision checklist and maintain a complete, versioned decision file with evidence, minutes and approvals.
• Apply a transparent evidence‑threshold approach; context and seriousness allow flexibility in thresholds but must be justified.
• Operationalise decisions with SOPs, clear roles, tracking mechanisms, and KPIs to demonstrate an auditable, scientifically‑based process to regulators and inspectors.
• Removal of potential risks requires robust negative evidence and documented regulatory agreement where appropriate.

References

1. EMA Good Pharmacovigilance Practices (GVP) Module V – Risk Management Systems.
2. EMA Risk Management Plan Template.
3. Commission Implementing Regulation (EU) No 520/2012.
4. ICH E2E Pharmacovigilance Planning.
5. EMA Guidance on Safety Concerns and Risk Management Planning.