Signal Management During Pharmacovigilance Inspections

Introduction

Signal management is routinely examined during pharmacovigilance inspections because it contributes directly to the identification, evaluation and management of safety concerns associated with medicinal products. Through signal management activities, organisations evaluate whether new risks, or new aspects of known risks, may affect the benefit‑risk balance of their products.

Inspectors are generally less interested in the existence of a particular statistical methodology than in whether the organisation can demonstrate a systematic and scientifically justified approach to signal management. Inspection discussions therefore frequently focus on governance, documentation, decision‑making and oversight.

Signal management findings are often associated with process weaknesses rather than scientific disagreement. An inspector may not challenge a medical judgement regarding a signal assessment but may question whether the assessment was adequately documented, appropriately reviewed or escalated through established governance processes.

For this reason, organisations should view signal management not only as a scientific activity but also as a regulated process that must be demonstrable, traceable and consistently implemented.

Why Inspectors Review Signal Management

Signal management occupies an important position within the pharmacovigilance system because it influences many downstream activities.

Outputs from signal management may affect:

• Product information
• Risk Management Plans (RMPs)
• Periodic Safety Update Reports (PSURs/PBRERs)
• Additional pharmacovigilance activities (targeted follow‑up, pharmacoepidemiology)
• Risk minimisation measures
• Regulatory communications and safety directives

Consequently, inspectors often regard signal management as an indicator of the organisation's ability to identify and manage emerging safety concerns. Demonstrable traceability from detection to decision and action is a key inspection theme.

Regulatory Expectations — Context for Inspections

Regulatory expectations for signal management differ by jurisdiction but share common principles of written procedures, governance, documentation and timely action.

Key regulatory references include:

• EMA GVP Module IX — Signal Management (primary EU reference)
• EMA GVP Module I — Pharmacovigilance Systems and Their Quality Systems
• EMA GVP Module III — Pharmacovigilance Inspections
• Commission Implementing Regulation (EU) No 520/2012
• ICH guidance (E2E, E2C(R2)) and CIOMS recommendations
• National regulations (e.g., FDA guidance on safety surveillance and signal detection) for local markets

Inspectors expect organisations to demonstrate that:

• Signal management is defined in procedures and implemented consistently.
• Methodologies are scientifically justified and proportionate to product risk and data volume.
• Procedures include governance, roles and responsibilities, decision‑making thresholds and escalation pathways.
• Documentation enables reconstruction of the assessment pathway and decisions taken.
• The QPPV (or legally responsible person) retains visibility and the authority to escalate.

The methodology used for detection (disproportionality, automated algorithms, manual review) is less likely to be the focus than the ability to explain and justify that methodology and its integration into the governance framework.

Inspection Focus Areas

Inspectors frequently probe several common themes when reviewing signal management:

• Signal detection processes and data sources
• Validation criteria and validation records
• Signal assessment methodology and evidence synthesis
• Documentation practices and audit trails
• Governance arrangements and committee oversight
• Escalation pathways and timelines for significant findings
• QPPV oversight and visibility
• Integration of signal outputs into benefit‑risk evaluation and RMPs
• Control of outsourced activities and vendor oversight

The overarching question often posed by inspectors is: “Can the organisation demonstrate, from recorded evidence, how a potential observation progressed to a decision and any resulting action?”

Practical Governance for Inspection Readiness

A defensible governance model aligns roles, authorities, and documentation to ensure inspection‑grade traceability.

Core elements of governance:

• Written SOP(s) for signal management that reference GVP Module IX and local requirements.
• Defined roles: signal owner (scientific lead), initial reviewer(s), medical assessor, safety scientist/statistician, QPPV, head of safety, pharmacovigilance quality unit (PV QU), and relevant business unit representatives.
• Formal committees: Signal Evaluation Committee (or Safety Review Group), Safety Risk Governance Committee, and PV Quality Review Board — charters that define membership, quorum, escalation triggers and decision types.
• Escalation thresholds: pre‑defined criteria for immediate notification to QPPV and senior management (e.g., evidence of fatal outcomes, class effects, unexpected clusters, regulatory interest, or serious public health impact).
• Outsourcing controls: contracts, technical specifications, performance indicators, evidence of oversight (vendor reports, quality reviews, periodic audits).
• Record retention: policies for storage and retrieval of assessment records, minutes, and supporting documents.

Inspection relevance: inspectors will request committee charters, SOPs, membership lists, conflict of interest declarations, and minutes demonstrating how signals were reviewed and decisions made.

Documentation and Traceability — Inspection Relevance

Documentation should permit reconstruction of:

• How a signal was detected and by whom
• What validation criteria were applied and why
• Which data were reviewed (ICSRs, clinical trial data, literature, registries)
• What analyses were performed (disproportionality, temporal patterns, stratified reviews)
• Which alternative explanations were considered
• The medical and statistical rationale for conclusions
• Governance approvals and subsequent actions
• Regulatory communications and follow‑up monitoring

Typical documents inspectors will request:

• Signal detection logs
• Validation worksheets
• Full signal assessment reports (including annexed case narratives and analysis outputs)
• Literature review outputs and search strategies
• Minutes of relevant safety committees and sign‑off forms
• QPPV communications and escalation records
• Updated RMP/PSUR extracts and decision packages
• Evidence of vendor deliverables where activities were outsourced

Poor documentation is a frequent inspection finding even when the scientific judgement itself was reasonable. Therefore, the principle of "document what you would like to be able to demonstrate to an inspector" is useful.

Escalation and Emerging Safety Issues

Escalation processes should be explicit and demonstrable.

Key inspection areas:

• What constitutes a significant signal or emerging safety issue (ESI)
• Timelines for initial notification (internal and regulatory where required)
• Roles required for onward escalation (medical director, QPPV)
• Mechanisms for rapid convening of multi‑disciplinary review (telephone, e‑meet)
• Decision points that trigger regulatory reporting or urgent risk minimisation

Regulatory context: GVP IX and certain national laws require timely communication with regulators when new risks are identified. Inspectors will examine how the organisation decided to notify regulators and whether timelines and procedures were followed.

Integration with Benefit‑Risk Evaluation

Signals must be integrated into the broader benefit‑risk framework:

• Linkage to PSUR/PBRER evaluations, with cross‑referencing in documentation
• Consideration in RMP updates and planning of additional activities (e.g., pharmacoepidemiology)
• Inclusion in periodic management and clinical safety reviews
• Evidence that actions (label changes, communications) were implemented and monitored

Inspectors will look for cross‑references between signal assessments and other documents (PSUR extracts, RMP change logs, product information amendments) to confirm integrated decision making.

Common Inspection Findings (Condensed)

Recurring deficiencies include:

• Inadequate documentation preventing reconstruction of the assessment pathway
• Weak validation records and unexplained closures of potential signals
• Poorly defined governance and unclear decision authorities
• Delayed or nonexistent escalation of significant signals
• Insufficient QPPV visibility of critical safety information
• Incomplete integration of signals into RMPs and periodic reporting

Most findings reflect process control issues rather than disagreement over scientific conclusions.

Inspection Readiness — Operationalising Demonstrability

Inspection readiness is achieved through routine operation of an inspection‑grade system, not ad‑hoc preparation. The organisation should be able to present complete records that explain how a signal was handled from detection to action.

The following sections convert high‑level guidance into operational detail: an actionable inspection‑readiness checklist and a fully worked signal assessment example with supporting documents and an escalation timeline.

Operational Inspection‑Readiness Checklist (Operational, Inspectable Items)

This checklist converts expectations into demonstrable artefacts. It is organised by theme and lists the minimum items inspectors typically request. Retain, index and make retrievable all listed artefacts for a product portfolio sample period (e.g., last 24 months or since product launch).

1. Governance and Procedures
2. Current SOP(s) for signal management, validated and version controlled (include change history).
3. Signal Evaluation Committee charter (membership, quorum, chair, escalation authority).
4. QPPV role description, authority statement and delegation log.
5. Organogram showing safety governance structure and reporting lines.

6. Evidence of conflict of interest declarations for committee members.

7. Signal Detection and Validation Records

8. Signal detection logs for the requested timeframe (dated entries, identifier, detector).
9. Raw outputs from detection tools (disproportionality tables, statistical run outputs).
10. Validation worksheets/logs with dates, validators’ names, and rationale for closure or progression.

11. Audit trail showing any changes to detection algorithms or thresholds (with justification).

12. Signal Assessment Documentation

13. Complete signal assessment reports (including summary, methods, data sources, analysis, conclusions, and recommendations).
14. Annexed individual case narratives (redacted to maintain confidentiality where necessary) showing key cases that drove the signal.
15. Literature review search strategy, search terms, results and appraisal of quality.
16. Aggregate analyses: tables, forest plots, time‑to‑onset diagrams, stratified disproportionality analyses.
17. Causality assessments (individual and aggregate) and rationale.

18. Decision log linking assessment outcomes to actions.

19. Governance Approvals and Communication

20. Minutes of relevant safety committee meetings (Signal Evaluation Committee, PV Executive).
21. Signed decision forms or electronic approvals that document who approved what action and when.
22. Evidence of QPPV notifications and sign‑off (emails, formal memos).

23. Regulatory communication records (notifications, type of communication, date sent, agency acknowledgement).

24. Action and Follow‑Up Documentation

25. Updated RMP extracts or RMP change submissions (with tracking of amendments).
26. Changes to product information (SmPC, PIL) drafts and final submissions.
27. Implementation evidence for risk‑minimisation measures (educational materials, DHPC drafts).

28. Monitoring plans or requested pharmacoepidemiology protocols and timelines.

29. Quality and Oversight Artefacts

30. PV Quality Unit review reports or assessments of the signal management process.
31. Internal audit reports related to signal management and corrective action plans.
32. Training records for staff carrying out signal management activities.

33. Vendor oversight records (monthly/quarterly reports, KPIs, audits) where activities are outsourced.

34. Timeline and Traceability

35. A single "Signal Master File" for each significant signal that collates all items above and provides a chronological timeline (detection→validation→assessment→decision→action→follow‑up).

36. Index of document locations and document control numbers for the signal file.

37. IT and Data Integrity Evidence

38. Evidence of system validation for detection tools (validation plans/execution reports).
39. Audit trails from safety databases demonstrating time stamps, user IDs, and changes to records.

40. Back‑up and retention policies confirming availability of records for inspection.

41. Sample Artefacts (to have ready, not exhaustive)

42. Example of 1–2 fully worked signal case files (complete with the master file described above).
43. A redacted individual case safety report (ICSR) that was central to a signal assessment, including follow‑up documentation.
44. Minutes from the PV committee showing decisioning on at least one significant signal.

Inspection relevance: present the master file (item 7) first when responding to an inspector's request — it acts as a navigational map for all associated documents.

Worked Example: Fully Documented Signal Assessment (Operational Demonstration)

The following worked example demonstrates how to convert high‑level process requirements into a demonstrable, inspection‑grade assessment. All data and product names are hypothetical and anonymised for illustrative purposes.

Executive summary

A potential signal of acute liver injury (ALI) was detected for Product A (oral small molecule, authorised for chronic autoimmune disease). Detection originated from a signal screening in the global spontaneous reporting database showing a growing cluster of serious hepatic events temporally associated with Product A. A formal signal assessment was initiated, culminating in a decision to update the RMP and notify regulators. This worked example contains the detection record, validation worksheet, full assessment, supporting documents list and an escalation timeline demonstrating governance and QPPV involvement.

1. Detection (Day 0)

• Detection method: Weekly disproportionality screening using Empirica Signal (disproportionality algorithm: reporting odds ratio (ROR) with shrinkage).
• Trigger: ROR for "acute liver injury / hepatic failure" for Product A exceeded the pre‑defined threshold (lower 95% CI > 1.5) and case count ≥ 5 within 90 days.
• Detection record (Signal Log Entry #2025‑ALI‑001):
• Date/time detected: 2025‑03‑02 09:18
• Detector: Signal Engineer (Vendor X) automated report; initial review flagged by in‑house safety scientist.
• Initial case count: 7 ICSRs from three countries, two with fatal outcome.
• Action: Create signal master file and commence validation.

Supporting artifact: Exported disproportionality output (PDF) with highlighted rows and detection thresholds (Document: "2025‑03‑02_Disprop_Output_ProductA.pdf").

2. Validation (Day 0–3)

• Objective: Confirm signal is not an artefact of coding, duplicate reports, or exposure misclassification.
• Validation worksheet completed (Document: "2025‑03‑05_Validation_Worksheet_2025‑ALI‑001.docx") with:
• Duplicate review: 2 ICSRs consolidated; de‑duplication performed per SOP.
• Case completeness: 3/7 cases lacked sufficient lab data but included clinical diagnosis consistent with ALI.
• Temporal plausibility: onset interval ranged 7–42 days post‑start.
• Alternate explanations: concomitant hepatotoxic drugs in 2 cases (both with strong alternative causality); viral hepatitis excluded in 4 where tests were done.
• Decision: Progress to full signal assessment (validated by safety scientist and medical lead).

Escalation: QPPV emailed on Day 3 with summary and recommendation for assessment (attached "2025‑03‑05_QPPV_Notification_Email.msg").

Inspection relevance: Validation worksheet documents rationale for progression — inspectors will verify the worksheet and cross‑check with ICSRs.

3. Scoping and Data Collection (Day 4–14)

Data sources compiled:

• All ICSRs for Product A to date (exported from global safety database).
• Clinical trial safety databases: pooled exposure data (N=2,300) with no prior ALI signal reported.
• Literature search: MEDLINE/Embase search (search terms: "ProductA", "drug class", "hepatotoxicity", "acute liver injury") for 2000–2025; PRISMA flow chart included.
• Market exposure estimate: estimated 150,000 patient‑years globally.

Supporting artifacts: - "2025‑03‑10_Literature_Search_Strategy.docx" — search strings, databases, date ranges. - "2025‑03‑12_ProductA_Exposure_Data.xlsx" — regional sales and exposed patient estimates.

Inspection relevance: Provide search strategy and exposure calculations to demonstrate systematic evidence collection.

4. Aggregate Analysis (Day 15–25)

Analyses performed and results:

• Disproportionality re‑run with stratification by age, gender and reporter region:
• Overall ROR: 2.9 (95% CI 1.8–4.4)
• Higher ROR in patients >65 years: 4.5 (95% CI 2.3–8.9)
• Time‑to‑onset analysis:
• Median onset 21 days (IQR 10–30)
• Temporal clustering noted within 4–42 days
• Outcome severity:
• 2 fatal cases, 3 requiring hospitalisation and liver transplant evaluation.
• Clinical trial review:
• No confirmed ALI cases in clinical development (exposure limited).
• Dechallenge/rechallenge:
• Positive dechallenge in 4 cases (improvement after stopping drug); one possible positive rechallenge (bilirubin increase on re‑exposure) — follow‑up evidence documented.

Supporting artifacts: - "2025‑03‑22_Aggregate_Analysis_Tables.pdf" — stratified RORs, TTO plots. - Case narrative annexes: redacted ICSRs (Documents: "ICSR‑001_redacted.pdf" through "ICSR‑007_redacted.pdf").

Inspection relevance: Inspectors will examine both aggregate outputs and underlying ICSRs to ensure analysis is reproducible and supported by case evidence.

5. Clinical Assessment and Causality (Day 26–30)

Medical assessment conclusions:

• Strengths of association:
• Consistent temporal pattern and positive dechallenge in multiple cases.
• Disproportionality signal robust across strata and not explained by a single country or reporter bias.
• Weaknesses / alternative causes:
• Concomitant hepatotoxins in 2 cases — these were evaluated and judged less likely to explain the full clinical picture in at least one severe case.
• Background incidence of ALI in the target population estimated low but not negligible.
• Overall causality (aggregate): Possible to Probable association (per modified WHO causality at aggregate level).
• Recommended actions:
• Escalate to Signal Evaluation Committee for discussion.
• Initiate planning for RMP update and targeted pharmacoepidemiology (feasibility assessment).
• Prepare regulator notification package (provisional) pending committee decision.

Supporting artifact: - "2025‑03‑30_Medical_Assessment_Report_ProductA_ALI.docx" — includes rationale, evidence summary, and recommendation.

Inspection relevance: The medical assessment demonstrates structured reasoning; inspectors will check for completeness and that alternative explanations were considered.

6. Governance Review and Decision (Day 31–45)

Sequence of governance interactions:

• Day 31: Signal Evaluation Committee (SEC) convened (minutes: "2025‑04‑01_SEC_Minutes.docx"):
• Attendees: Medical lead (chair), safety scientist, epidemiologist, PV QU representative, regulatory affairs, QPPV (attendee).
• Discussion: Reviewed assessment and aggregate data. Consensus to classify as "signal under evaluation" with high priority.

• Actions assigned: regulatory affairs to draft CHMP notification package; epidemiology to scope a pharmacoepidemiology study; PV QU to initiate quality check of signal file.

• Day 38: QPPV review and sign‑off on proposed regulatory communication strategy (email evidence: "2025‑04‑08_QPPV_Signoff.msg").

• Day 45: Senior Safety Review Committee approved:

• Immediate submission of expedited notification to regulatory authorities (EU and other major markets).
• Update to RMP routine review and initiation of targeted risk minimisation planning.

Supporting artifacts: - SEC minutes, sign‑off emails, action item tracker (with owners and due dates).

Inspection relevance: Inspectors will examine minutes, action items and evidence of QPPV sign‑off to confirm oversight and timely escalation.

7. Regulatory Notification (Day 46–52)

Regulatory communication:

• Day 46: Initial trans‑mission of signal notification to EMA (e.g., PSUR/Signal reporting mechanism per local requirements). Package included:
• Executive summary
• Medical assessment report
• Selected redacted case narratives
• Aggregate analysis outputs
• Proposed next steps (RMP update and pharmacoepidemiology)
• Day 52: EMA acknowledged receipt and requested additional information on exposure estimates and planned study protocol.

Supporting artifacts: - "2025‑04‑16_EMA_Signal_Submission.zip" (manifest listing included in master file) - Acknowledgement email/receipt from regulator ("2025‑04‑22_EMA_Acknowledgement.msg").

Inspection relevance: Inspectors will verify that regulatory communications were made and that packages included sufficient supporting evidence.

8. Follow‑Up Actions (Day 53–120)

• RMP update: Drafted and reviewed (Document: "2025‑05‑10_RMP_Update_Draft.docx"), then submitted per regulatory timelines.
• Pharmacoepidemiology: Feasibility study initiated (protocol in preparation; epidemiologist assigned).
• Labeling: Safety label change considered; drafting of SmPC wording options for hepatic events initiated with regulatory affairs.
• Monitoring: Increased targeted monitoring of hepatic events in safety database (daily review for 30 days, then weekly).

Action tracking: - Action tracker shows due dates, owners and status updates (Document: "2025‑06‑20_Action_Tracker.xlsx").

Inspection relevance: Inspectors expect evidence that the planned actions were implemented and that follow‑up monitoring is occurring.

9. Outcome and Status (6 months post detection)

• Status: Ongoing monitoring with pharmacoepidemiology study initiated; RMP updated; regulatory agencies engaged; label update under consideration.
• Evidence of continuous oversight: Quarterly safety report included the signal description, status and planned activities. PV QU conducted a quality review of the signal file and closed corrective actions from initial process review.

Supporting artifacts: - Finalised RMP extract, interim pharmacoepidemiology protocol, quarterly safety committee minutes.

Inspection relevance: Inspectors will assess whether the organisation followed through on actions and whether documentation supports the claimed outcome.

10. Signal Master File Contents (index)

For inspection presentation, the signal master file included:

• Cover page with signal identifier, product name, signal owner, and high‑level timeline.
• Detection exports and validation worksheet.
• Medical assessment report (signed and dated).
• Aggregate analysis outputs and statistical run files.
• Redacted ICSRs (with case identifiers and follow‑up chronology).
• Literature review documents and PRISMA flow.
• Meeting minutes (Signal Evaluation Committee, Senior Safety Review).
• QPPV sign‑off and escalation emails.
• Regulatory submission package and responses.
• Action tracker and RMP change documentation.
• Quality oversight report and internal audit extract.
• Index referencing document control numbers and secure storage locations.

Inspection relevance: Presenting a single master file with indexed content expedites inspection review and demonstrates process control.

Escalation Timeline (Illustrative, Inspectable Timestamps)

Inspectors typically request chronology and timeliness evidence. The following timeline demonstrates expected documentation at each step.

• Day 0 (2025‑03‑02 09:18) — Automated detection; vendor report exported (timestamped file).
• Day 0 (2025‑03‑02 14:30) — Safety scientist initial review; signal log entry created (with user ID and timestamp).
• Day 3 (2025‑03‑05 10:45) — Validation worksheet completed and signed by validator (electronic signature and audit trail).
• Day 3 (2025‑03‑05 11:00) — QPPV notified by formal email; email saved in signal master file.
• Day 15 (2025‑03‑17 16:20) — Aggregate analyses completed; files saved in controlled repository.
• Day 26 (2025‑03‑28 09:00) — Medical assessment report completed and PDF executed (version controlled).
• Day 31 (2025‑04‑01 14:00) — Signal Evaluation Committee meeting held; minutes uploaded with attendance list and action items.
• Day 38 (2025‑04‑08 09:12) — QPPV sign‑off email on regulatory strategy.
• Day 46 (2025‑04‑16 10:05) — Regulatory submission transmitted; receipt confirmation logged.
• Day 53 (2025‑04‑23 15:00) — RMP update drafted and routed for approval.
• Day 90 (2025‑06‑01) — Pharmacoepidemiology study protocol submitted to internal governance for approval.
• Day 120 (2025‑07‑01) — PV QU quality review completed and logged.

Inspection relevance: For each timestamp, provide the artefact with metadata (file properties, database audit trail) to demonstrate authenticity and timeliness.

Supporting Document Templates and Artefacts (Practical Implementation)

Suggested templates that should be part of operating documentation (inspectors may request to see examples):

• Signal Log Template (fields: Signal ID, Product, Date detected, Detector, Initial case count, Priority level, Owner).
• Validation Worksheet Template (fields: Case review summary, duplication check, lab data, temporal plausibility, alternative causes, decision).
• Signal Assessment Report Template (sections: Executive summary, Background, Methods/data sources, Aggregate analysis, Case narratives, Causality assessment, Conclusion, Recommendations).
• Meeting Minutes Template (attendance, declarations, summary of discussion, decisions, action items, sign‑off).
• Action Tracker Template (action, owner, due date, status, evidence of completion).
• Regulatory Submission Checklist (cover letter, executive summary, case narratives, analyses, exposure data, proposed actions).
• Master File Index Template (signal ID, list of documents with locations and control numbers).

Implementation detail: Each template should be under version control, and there should be an SOP referencing the mandatory templates and minimum content expectations.

Control of Outsourced Signal Activities — Evidence to Provide

When activities are outsourced (e.g., signal detection algorithms managed by vendor):

• Contractual evidence: Master service agreement and technical annex describing deliverables, detection thresholds, change control procedures.
• Oversight evidence: Monthly/quarterly vendor performance reports, meeting minutes, issue logs.
• Data transfer evidence: Secure transfer logs and file integrity checks.
• Validation evidence: Documented acceptance testing and periodic re‑validation of vendor tools.
• Complaint/issue escalation: Records showing how vendor discovery of signals is routed to the company.

Inspection relevance: Outsourcing does not remove regulatory responsibility. Inspectors will look for documentary evidence of oversight and control.

Governance and Quality Oversight — Practical Considerations

• PV Quality Unit (PV QU) responsibilities: periodic reviews of signal management quality, trend analysis of detection outcomes, and audits focused on documentation completeness and timeliness.
• Metrics and Key Performance Indicators (KPIs): median time from detection to validation; median time from validation to medical assessment; proportion of validated signals progressed to committee review; proportion of actions completed on time.
• Management reporting: quarterly safety governance reports summarising signal activity, status of high‑priority signals, and deferred actions.
• Training: records of competence for signal assessors and committee members (medical, statistical, regulatory).

Inspection relevance: Inspectors may request KPI reports, PV QU minutes confirming quality activities, and training records tied to signal management roles.

Inspection Tips (Document‑Focused)

• Provide the signal master file first; it acts as a map and reduces time and friction during inspection.
• Ensure all documents have metadata (author, date, version) and that audit trails from electronic systems are extractable.
• Where redaction is necessary for confidentiality, provide a redaction log and original file under appropriate confidentiality arrangements if requested.

Key Takeaways (Reinforced with Operational Focus)

• Inspections emphasise demonstrability: show the record, not only the rationale.
• Prepare master files for significant signals that collate detection, validation, assessment, governance decisions, regulatory communications and follow‑up.
• Use standard templates, version control and auditable systems to ensure inspection‑grade documentation.
• Governance, escalation and QPPV visibility are as important — if not more — than the precise choice of detection algorithm.
• Control and document outsourced activities with the same rigour as internal processes.

References

1. EMA Good Pharmacovigilance Practices (GVP) Module IX – Signal Management.
2. EMA Good Pharmacovigilance Practices (GVP) Module III – Pharmacovigilance Inspections.
3. EMA Good Pharmacovigilance Practices (GVP) Module I – Pharmacovigilance Systems and Their Quality Systems.
4. Commission Implementing Regulation (EU) No 520/2012.
5. Regulation (EC) No 726/2004.
6. Directive 2001/83/EC.
7. CIOMS VIII Practical Aspects of Signal Detection in Pharmacovigilance.
8. ICH E2E Pharmacovigilance Planning.
9. ICH E2C(R2) Periodic Benefit‑Risk Evaluation Report.