Additional Pharmacovigilance Activities

Introduction

The purpose of a Risk Management Plan (RMP) is not merely to catalogue safety concerns; it is to ensure that important risks and uncertainties are managed and progressively reduced across the product lifecycle. Routine pharmacovigilance provides the foundation of safety monitoring, but it is not always sufficient to resolve specific knowledge gaps. Additional Pharmacovigilance Activities are deliberate, hypothesis-driven actions implemented when further information is required to characterise a safety concern, reduce uncertainty or support ongoing benefit–risk evaluation.

These activities are amongst the most scrutinised sections of modern RMPs because they represent concrete commitments by the Marketing Authorisation Holder (MAH) to generate additional safety information, often under regulatory oversight. This article provides practical guidance on selection, justification, governance and inspection-readiness for Additional Pharmacovigilance Activities, with an actionable checklist and a mapping table linking common safety concerns to study types plus sample RMP justification text.

Routine Versus Additional Pharmacovigilance

Understanding the distinction is foundational.

• Routine pharmacovigilance: ICSR collection, signal management, literature surveillance, aggregate safety review and periodic reports (PSURs/PBRERs). These activities apply to most products and generally do not require bespoke justification in the RMP.
• Additional pharmacovigilance: Activities undertaken because routine measures are insufficient to answer a defined question. Examples include PASS, registries, drug utilisation studies, enhanced follow-up and targeted safety surveillance.

Fundamental principle: every additional activity should answer a specific, traceable question related to an Important Identified Risk, Important Potential Risk, or Missing Information.

Regulatory Basis and Inspection Relevance

Within the EU, Additional Pharmacovigilance Activities are described within the Pharmacovigilance Plan component of the RMP (GVP Module V and Module VIII; Commission Implementing Regulation (EU) No 520/2012). Several regulatory points are relevant:

• Activities must be traceably linked to specific safety concerns or gaps in knowledge.
• Study design must be appropriate to the question; regulators expect scientific justification for method choice, population, endpoints and sample size.
• Where activities are regulatory commitments (imposed PASS, agreed study obligations), MAHs must track progress and report deviations.
• Inspectors routinely examine the rationale, governance, progress tracking, contractual arrangements, data integrity and how study results affected risk management decisions.

Inspection focus frequently includes: documentation showing linkage between concern and study; protocol and statistical analysis plan (SAP); governance records (steering committee, DSMB where relevant); timelines and milestones; regulatory communications (protocol notifications, interim reports); final study report and impact on RMP/SmPC. Be prepared to demonstrate decision-making using study outputs (e.g., RMP modification, risk minimisation changes, labelling updates).

Fundamental Logic for Additional Activities

The logic should be explicit and documented:

Safety Concern → Knowledge Gap → Additional Activity → Expected Outcome → Criteria for Success/Closure

If this chain is not explicit, the necessity of the activity will be questioned during regulatory review or inspection.

Common Objectives

Additional Pharmacovigilance Activities aim to:

• Characterise or quantify risks
• Identify risk factors or susceptible subpopulations
• Evaluate clinical outcomes and severity
• Assess utilisation patterns and effectiveness of risk minimisation
• Reduce uncertainty to support benefit–risk decisions

Define objectives before initiating an activity; they should be outcome-based and measurable where possible.

Types of Additional Pharmacovigilance Activities

• Post‑Authorisation Safety Studies (PASS): interventional or non-interventional, including database studies.
• Registries: disease, product, exposure or pregnancy registries for long-term observation and specialised populations.
• Pregnancy registries: long-term programmes to evaluate maternal, fetal and neonatal outcomes.
• Drug Utilisation Studies (DUS): to describe prescribing patterns, off‑label use and adherence to risk minimisation measures.
• Enhanced follow‑up: targeted questionnaires and structured clinical follow-up for specific events.
• Observational studies: cohort, case–control, self‑controlled case series for incidence, comparative safety and risk factors.
• Pharmacokinetic/pharmacodynamic (PK/PD) studies: when physiological differences (e.g., renal impairment) may alter exposure and risk.
• Risk minimisation effectiveness studies: to measure whether risk minimisation measures result in desired behavioural or clinical change.

Select the study type that most directly answers the scientific question; avoid “shopping” for complex or resource-intensive methods when a simple, robust design will suffice.

Selecting and Justifying the Appropriate Activity

Selection should be driven by the scientific question and feasibility. Key considerations:

• Precise definition of the safety question and measurable endpoints.
• Epidemiology: expected incidence/prevalence and effect size.
• Data availability and quality: registries, electronic health records (EHR), claims databases.
• Confounding and bias considerations and planned methods to mitigate them.
• Ethical and data protection constraints: consent, GDPR, secondary data use permissions.
• Timelines: time to accrual, expected data maturity and regulatory reporting requirements.
• Resources and governance capacity: internal project team, external CROs, steering committees.

Regulatory justification must be concise, evidence-based and translated into RMP text that links the activity to the specific safety concern and expected regulatory or clinical outcome.

Practical Implementation Checklist (Inspection‑Ready)

Use this checklist as an operational guide and to prepare inspection evidence. For each additional activity, maintain a dossier that aligns with the checklist.

1. Define the scientific question
2. Explicitly state the safety concern, knowledge gap and hypothesis.

3. Define primary and secondary endpoints, success criteria and decision thresholds.

4. Select and document study design rationale

5. Explain why the design (registry, cohort, case–control, database study, PK/PD) is appropriate.

6. Provide references or precedents supporting design choice.

7. Feasibility assessment

8. Data sources, expected sample size, recruitment rate, key assumptions and contingency plans.

9. Preliminary data searches (e.g., database counts) and their outputs.

10. Protocol and statistical analysis plan (SAP)

11. Finalised protocol with objectives, endpoints, eligibility, data collection, analysis methods and handling of confounding.

12. SAP with primary analyses, sensitivity analyses and multiplicity control.

13. Governance and roles

14. Steering committee membership and charters.
15. Sponsor and CRO agreements, delegated activities and oversight arrangements.

16. DSMB plan when needed, including stopping rules.

17. Regulatory interactions

18. Documentation of regulatory commitments, notifications, approvals and meeting minutes.

19. Protocol submission/notification timelines and responses.

20. Ethics and data protection

21. Ethics committee approvals, consent forms where applicable, data protection impact assessment, GDPR compliance, data sharing agreements.

22. Contracts and third‑party oversight

23. Signed contracts (CRO, data providers, registries) and evidence of oversight meetings and audits.

24. Quality assurance and data integrity

25. Data management plan, monitoring plan, data validation and query resolution procedures.

26. Source data verification approach for non-interventional studies where applicable.

27. Timelines, milestones and tracking

    • Detailed Gantt chart with recruitment, interim analyses, data lock and final report dates.
    • Regular progress reports and KPI tracking (recruitment rates, data completeness, query rates).

28. Interim analyses and signal management

    • Pre-specified interim analyses, criteria for early termination or protocol amendment and process for urgent safety signals.

29. Reporting and dissemination

    • Interim and final study reports, registration (e.g., EU PAS Register, clinicaltrials.gov), publications and plans to update the RMP/SmPC/etc.

30. Lifecycle and closure criteria

    • Clear criteria for study completion, modification or discontinuation and evidence to support closure of the activity within the RMP.

31. Archive and inspection dossier

    • Complete study master file (SMF), protocol, SAP, CSR, regulatory correspondence, final dataset disposition and SOPs—ready for inspection.

Inspection evidence to have readily available: protocol final and draft versions with sign‑offs, SAP, monitoring reports, minutes of governance meetings, interim/final reports, regulatory correspondence and documentation showing how findings were considered for RMP updates and risk minimisation activities.

Governance and Oversight

Robust governance ensures scientific integrity and regulatory compliance.

• Roles and responsibilities
• QPPV: strategic oversight, knowledge of high‑level commitments, understanding of study outcomes and their impact on product safety.
• Clinical safety lead / PV study lead: responsible for operational oversight and regulatory interactions.
• Sponsor legal entity: accountable for the study and regulatory commitments.
• Steering Committee: provides scientific oversight; membership should include independent experts where appropriate.

• DSMB/Independent Data Monitor: recommended for interventional studies or where safety monitoring is critical.

• SOPs and processes

• SOPs must define processes for study initiation, protocol amendments, deviations, urgent safety reporting and record retention.

• Change control and versioning: maintain a clear audit trail for protocol/SAP amendments and approvals.

• Contracts and delegation

• Clear delegation of duties in the delegation log; CRO oversight and audit rights must be documented.

• Data sharing agreements should include terms for access, retention and transfer, aligned with data protection laws.

• Data quality and integrity

• Data management, validation and audit trails are essential. Even for non‑interventional studies, ensure traceability between source records and analytic datasets.

• Maintain a defined process for issue escalation and resolution.

• Resource planning

• Budgeting must include contingency for slow recruitment, prolonged follow‑up and regulatory requests for additional analyses.

Lifecycle Management and Criteria for Discontinuation

Additional activities should be time‑bound with measurable milestones. Outcomes may be:

• Achievement of objectives and closure of activity in the RMP (documented evidence and RMP update).
• Modification or escalation (refinement of objectives, change in design, additional analyses).
• Replacement by alternative approach (e.g., switched to database study due to slow registry recruitment).
• Discontinuation when activity no longer justified (document rationale, interim findings, and regulatory agreement where relevant).

Closure documentation for inspection should include final report, data set descriptor, rationale for termination (if early), minutes showing RMP/Risk minimisation updates and proposed SmPC changes.

Common Regulatory Deficiencies and How They Appear in Inspections

Typical deficiencies observed in reviews and inspections include:

• Activities lacking a clearly defined scientific question or endpoints.
• Weak linkage between activity and the specific safety concern.
• Inadequate feasibility assessment or unrealistic timelines.
• Poorly documented governance, delegation or oversight.
• Failure to notify competent authorities when legally required.
• No predefined criteria for success or closure; activities remain indefinitely in the RMP.
• Final study reports not used to update the RMP, SmPC or risk minimisation actions.

During inspection, regulators probe both scientific justification and operational controls. Ensure traceability from question to decision and provide documentation demonstrating how outputs informed risk management.

Characteristics of Well‑Designed Activities

Well‑designed activities demonstrate:

• Clear, measurable objectives and endpoints.
• Direct linkage to safety concerns and expected regulatory outcomes.
• Appropriate, justifiable methodology with mitigation for bias and confounding.
• Feasibility assessment and realistic timelines.
• Defined governance, with documented roles, SOPs and oversight.
• Predefined criteria for success and action plans for inconclusive results.
• Transparent reporting, registration and dissemination plans.

Practical Examples: Mapping Common Safety Concerns to Study Types (Inspection‑Ready Table)

The following table maps common safety concerns to recommended study types, key design considerations and sample RMP justification text. Use the sample text as a template; tailor language to the specific product, population and regulatory context.

Notes on using the table: - Adapt sample justification wording to reflect the product, population and national regulatory requirements. - For studies that are regulatory commitments, include the timeline and interim report schedule in RMP text. - Ensure the dossier includes feasibility evidence and power/sample size justification referenced in the RMP.

Sample RMP Justification: Structure and Language

Regulators expect concise, clear RMP statements. Use the following structure:

1. Statement of concern (one sentence)
2. Specific knowledge gap(s) (one sentence)
3. Proposed activity and design (one sentence)
4. Primary objective and expected outcome (one sentence)
5. Timelines and success/closure criteria (one sentence)

Example consolidated text for an RMP: "A potential increased risk of severe hepatic injury has been identified as an Important Potential Risk due to limited post‑marketing exposure. To quantify this risk and identify risk factors, a non‑interventional multi‑database PASS (cohort and nested case–control analyses) will be conducted using validated hepatic injury criteria. The primary objective is to estimate incidence rates of severe hepatic injury among users of [product] and to evaluate patient-level risk factors. Interim analyses will be provided annually with final reporting within 36 months of study initiation. The study will be considered successful if the upper bound of the 95% CI for the incidence rate excludes a clinically meaningful increase compared with historical comparators; otherwise, additional analyses or risk minimisation will be considered."

This structure helps inspectors rapidly see the rationale, method, objective and decision criteria.

Implementation Details: Practical Steps and Timing

• Phase 1 (Preparation – 3–6 months): Define question, feasibility, select design, draft protocol outline, perform preliminary database counts or recruitment projections, set up governance structures.
• Phase 2 (Start‑up – 1–6 months): Finalise protocol/SAP, obtain ethics and regulatory notifications/approvals, sign contracts, set up data flows and registry infrastructure, register study.
• Phase 3 (Execution – variable): Recruit/enrol/accrue cases, perform interim QC, conduct interim analyses per plan, maintain governance meetings and regulatory reporting.
• Phase 4 (Analysis/Reporting – 3–12 months): Final data cleaning, primary/sensitivity analyses, final study report (CSR), dissemination (public registry, publications) and RMP updates.
• Phase 5 (Closure/Integration – 1–6 months): Document closure, archive SMF, update RMP/SmPC and risk minimisation materials based on findings, and close regulatory commitments.

Adjust timelines by study complexity and recruitment feasibility. Include contingency planning for slow accrual. For pregnancy registries and long‑term follow‑up studies, plan for multi‑year timelines and interim reporting to regulators.

Inspection Preparation: Documents and Evidence to Have Ready

For each activity maintain an inspection package containing: - Protocol and SAP (all versions) with approval signatures and dates. - Feasibility assessments and sample size calculations. - Regulatory correspondence (notifications, responses, meeting minutes). - Ethics approvals and consent forms. - Steering committee and DSMB charters and minutes. - Contracts and delegation logs. - Progress reports, monitoring reports and KPI dashboards. - Interim analysis plans and results (if performed). - Final study report/CSR and dataset disposition statement. - Evidence of registration (EU PAS Register, clinicaltrials.gov). - Evidence of impact on RMP/SmPC/risk minimisation (minutes, revised documents). - Archiving and data retention plans.

Inspectors will often ask for justification of design choices, evidence of independence in governance, and demonstration that findings were used to inform product risk management.

Integration with Risk Management and Decision Making

Project outputs must be used to inform product safety management:

• Predefine decision points in the protocol and RMP that describe actions based on possible outcomes (e.g., confirm, refine or refute risk; need for additional studies; implementation of risk minimisation).
• Map study outcomes to specific RMP updates (e.g., change status of risk from Potential to Identified; remove or modify Missing Information entries).
• Document decisions in governance minutes and regulatory submissions; regulators and inspectors will expect to trace decisions to supporting evidence.

Governance: Oversight of Regulatory Commitments

For regulatory commitments, MAHs should maintain an obligation register with: - Description of the obligation - Origin (e.g., CHMP opinion, Commission decision) - Timelines and deliverables - Responsible roles and escalation pathways - Status updates, delays and mitigations - Evidence of submission and acceptance

Internal audit and management oversight of this register minimise risk of non‑compliance and support inspection responses.

Key Takeaways

• Additional Pharmacovigilance Activities must be question‑driven, proportionate and appropriately governed.
• Regulatory expectations focus on clear linkage of activities to safety concerns, robust scientific design, feasibility evidence, governance and demonstrable use of results.
• Practical readiness for inspection requires a complete study master file, governance documentation, regulatory correspondence and traceability from study results to RMP decisions.
• Use the provided checklist and mapping table to prepare clear, concise RMP text and to design studies that are scientifically and operationally defensible.

References

1. EMA Good Pharmacovigilance Practices (GVP) Module V – Risk Management Systems.
2. EMA Good Pharmacovigilance Practices (GVP) Module VIII – Post‑Authorisation Safety Studies.
3. EMA Risk Management Plan Template.
4. Commission Implementing Regulation (EU) No 520/2012.
5. ICH E2E Pharmacovigilance Planning.
6. CIOMS IX Practical Approaches to Risk Minimisation.