EVDAS and Signal Detection in Pharmacovigilance

Introduction

The EudraVigilance Data Analysis System (EVDAS) is one of the most important pharmacovigilance tools available to Marketing Authorisation Holders (MAHs) and regulators within the European Union.

While EudraVigilance serves as the repository for Individual Case Safety Reports (ICSRs), EVDAS provides the analytical environment that allows those reports to be explored, reviewed and assessed for potential safety concerns.

EVDAS plays a central role in signal detection activities and has become a key component of modern pharmacovigilance systems.

For many organisations, EVDAS outputs form part of routine signal management activities and contribute directly to compliance with Good Pharmacovigilance Practices (GVP) Module IX. For QPPVs, understanding EVDAS is important because signal detection represents one of the primary mechanisms through which previously unknown safety concerns are identified and evaluated.

What is EVDAS?

EVDAS stands for EudraVigilance Data Analysis System.

It is the analytical layer built upon EudraVigilance data.

EVDAS allows authorised users to:

• Analyse adverse reaction reports
• Review reporting trends
• Evaluate potential signals
• Generate signal detection outputs, including electronic Reaction Monitoring Reports (eRMRs)
• Support benefit-risk evaluation

Rather than creating new safety information, EVDAS helps users identify meaningful patterns within existing pharmacovigilance data.

In simple terms:

The two systems are closely connected but serve different functions.

Why Signal Detection Matters

Medicinal product safety profiles continue to evolve after approval.

Clinical trials are designed to establish efficacy and safety before authorisation, but they have limitations:

• Involve relatively small populations
• Exclude certain patient groups
• Operate for limited durations
• May not detect rare or delayed adverse reactions

As products enter real-world use, additional safety information becomes available. Signal detection activities aim to identify:

• New adverse reactions
• Changes in known adverse reactions
• Changes in severity
• Changes in frequency
• Emerging risk factors

Early identification of safety concerns helps protect patients and supports informed regulatory decision-making.

What is a Safety Signal?

A safety signal is information suggesting a potentially causal association between a medicinal product and an adverse event that warrants further investigation.

A signal is a hypothesis, not proof. It requires structured evaluation, typically progressing from detection to validation and, if justified, to detailed assessment and action.

Potential sources of signals include:

• Spontaneous reports
• Literature reports
• Clinical studies
• Epidemiological studies
• Regulatory findings
• EVDAS outputs

For a detailed discussion see: [[what-is-a-safety-signal]]

Signal Detection Within GVP Module IX — Regulatory Context

Signal management activities within Europe are governed primarily by EMA GVP Module IX (Signal Management). Key regulatory expectations include:

• A documented signal management system with defined roles and responsibilities.
• Processes that cover detection, validation, confirmation, analysis, prioritisation, assessment, decision-making and communication.
• Maintenance of records to support signal activities and decisions, including the rationale for closing or escalating signals.
• Periodic review of the effectiveness of the signal management system.

GVP IX emphasises that outputs such as EVDAS-derived eRMRs are detection tools and that statistical associations should be interpreted within a medical and scientific framework. Although GVP IX does not prescribe rigid timelines for every step, it requires that signals be handled in a timely manner and that documented processes define expected timeframes (SOPs or local service level agreements).

Electronic Reaction Monitoring Reports (eRMRs)

One of the most widely used EVDAS outputs is the electronic Reaction Monitoring Report (eRMR).

eRMRs provide structured summaries of reporting patterns within EudraVigilance. The reports are designed to help users identify potential safety concerns requiring further review.

Typical information may include:

• Drug-event combinations (decisions on preferred term [PT] level and grouped PTs)
• Reporting counts (cases, serious cases)
• Disproportionality measures (e.g., reporting odds ratio, proportional reporting ratio, Bayesian metrics where available)
• Time trends and changes over time
• Case listings and sample case narratives
• Filter and query metadata (date of extract, data lock point, inclusion criteria)

eRMRs are intended to support signal detection activities rather than replace scientific judgement. A statistical output alone does not establish a safety signal.

Disproportionality Analysis

Disproportionality analysis is a cornerstone of EVDAS-based signal detection. The underlying principle is straightforward: if a particular adverse event is reported disproportionately often for a specific medicinal product compared with a reference population (e.g., the rest of the EudraVigilance database), the association may warrant further investigation.

Common considerations:

• Choice of comparator (entire database, therapeutic class, product class)
• Minimum case count thresholds to reduce spurious associations
• Adjustment for confounders where possible (age, sex, concomitant drugs)
• Temporal patterns (sustained increases vs. transient spikes)
• Sensitivity analyses to investigate stimulated reporting

Statistical associations do not automatically indicate causality. Observed associations may reflect reporting bias, stimulated reporting, confounding, product utilisation patterns, or chance findings. Scientific assessment and clinical judgement are essential.

Signal Validation and Assessment

After a potential signal has been identified, the next steps are validation and, if appropriate, assessment.

Validation determines whether the available information justifies further evaluation. Typical validation questions include:

• Is the finding new or a change in frequency/severity of a known reaction?
• Is the association plausible (pharmacologically, temporally)?
• Is the evidence sufficient for escalation?
• Could confounding or reporting artefacts explain the pattern?

Validated signals that require deeper evaluation proceed to assessment, which may include:

• Case-level review and medical assessment
• Literature and preclinical data review
• Epidemiological analyses or pharmacoepidemiology studies
• Benefit-risk assessments
• Regulatory interaction and potential risk minimisation measures

Many statistical outputs will be filtered out at validation; this filtering is a critical workload management function and part of good governance.

QPPV Oversight and Governance

The Qualified Person Responsible for Pharmacovigilance (QPPV) is expected to maintain oversight of the signal management system. This includes:

• Ensuring documented procedures (SOPs) are in place and adequate
• Confirming roles, responsibilities and escalation routes are defined
• Reviewing evidence that signals are being detected and handled appropriately
• Ensuring adequate resource allocation and training
• Receiving summaries of key signal management outcomes and significant safety concerns

Governance should be explicit in the Pharmacovigilance System Master File (PSMF): where signal detection fits in the organisation, committee charters, committee membership and reporting lines should be defined and up-to-date.

Independence and conflict-of-interest management are pertinent for assessment committees, and the QPPV should ensure objective decision-making through appropriate governance structures.

Inspection Perspective and Relevance

Signal management activities are routinely reviewed during pharmacovigilance inspections by authorities such as EMA and national competent authorities. Inspectors commonly examine:

• SOPs covering EVDAS use, eRMR review and signal management
• Evidence that eRMRs are generated and reviewed according to documented schedules
• Traceability from detection through validation, assessment, decision and action
• Minutes and decisions of signal review meetings (SRTs, safety committees)
• Escalation records showing when and why a signal was escalated to the QPPV or executive committees
• Documentation demonstrating medical review and rationale for closure or progression
• KPIs and trend analysis demonstrating system effectiveness
• Training, role definitions and audit trails

Inspectors focus on practical evidence that the process functions effectively: documented reviews, timely decisions, appropriate escalation and oversight by the QPPV.

Practical Considerations for Organisations

Effective EVDAS governance commonly includes:

• Defined review schedules (daily/weekly eRMR generation and triage for new products; periodic targeted reviews for mature products)
• Documented responsibilities and SLAs (e.g., triage timeframe, validation timeframe)
• Signal review meetings with defined membership and charters
• Escalation procedures that specify triggers for QPPV or regulatory notification
• Training programmes for signal detection analysts, safety physicians, and committee members
• Compliance metrics (KPIs) and periodic effectiveness reviews
• Integration of EVDAS outputs with the overall signal management tracker and document repository (electronic system with audit trail)

These controls help ensure that signal detection activities remain consistent, defensible and inspection-ready.

Inspection-Ready Checklist for EVDAS/eRMR Signal Management

Below is a comprehensive inspection-ready checklist that organisations can use to demonstrate control and traceability in EVDAS-based signal management. The checklist is structured to align with inspector expectations and GVP Module IX requirements.

Administrative and governance artefacts - Current SOPs covering: - EVDAS access and user roles - eRMR generation parameters and frequency - Triage, validation and escalation processes - Signal review committee terms of reference - Documentation and record retention - PSMF entries that reference EVDAS processes and responsible persons - Organogram showing signal detection governance and escalation lines - Committee charters and approved membership lists - Training records for all personnel with eRMR responsibilities - Evidence of periodic internal audit or quality review of signal management processes

EVDAS output and extraction evidence - eRMR files with metadata: - Date and time of extract - EudraVigilance data lock point - Filters and inclusion/exclusion criteria - Version of EVDAS and report template - Archived copies (read-only) of eRMRs maintained in the QMS or signal tracker - Line-listings and case narratives extracted and saved alongside the eRMR

Triage and validation artefacts - Triage log (date/time received, reviewer, outcome: no further action / proceed to validation) - Initial triage worksheet with fields: aggregate metrics, minimum case counts, seriousness, temporal rise, geographic distribution, plausibility flags - Validation report or checklist completed by the medically-qualified reviewer - Documentation of confounding assessment and comparator choices - Decision rationale: validated / not validated; if not validated, reason for closure and monitoring plan

Escalation and assessment artefacts - Signal tracker entry with unique identifier, dates (detection, validation, escalation), status and responsible persons - Escalation memo or safety signal notification to QPPV / Safety Review Committee (SRT) - SRT meeting minutes with attendees, discussion points, assessment plan and actions - If relevant: draft regulatory communication or minutes of interactions with authorities - Evidence of linkage to RMP, PSURs, or cohorts for further study

Outcome documentation and follow-up - Final assessment report or signal assessment document with conclusions and recommended actions - Action log with owners, deadlines and verification of completion - Updates to risk management documentation (RMP, Product Information) with rationale and version control - Periodic monitoring reports for signals under review

Metrics and continuous improvement - KPI dashboard exports used for oversight (see KPI section below) - Trend analysis and periodic reports provided to governance bodies - Records of corrective actions following internal or regulatory inspections

Inspection presentation readiness - Pre-packaged inspection folder or electronic binder with the above items for a selected period (e.g., last 12 months), including a worked example (see section below) - Ability to demonstrate an audit trail from eRMR generation through to closure or escalation - Named point of contact who can walk inspectors through the workflow and show live systems or archived outputs

Worked Example: Step-by-Step Review, Documentation and Escalation for an eRMR

This worked example demonstrates a typical, inspection-ready workflow for handling a new signal identified in an eRMR. It shows practical steps, documentation, KPIs and roles. The example uses a hypothetical product "MedX" and an observed drug-event combination "Severe Skin Reaction (SSRx)" flagged by an eRMR.

Summary timeline (example) - Day 0: Weekly eRMR generated and uploaded to signal tracker - Day 1 (within SLA): Triage completed by Signal Detection Analyst - Day 3 (within SLA): Medical validation completed by PV Physician - Day 4: Decision to escalate to Signal Review Team (SRT) - Day 10: SRT assessment meeting and initial assessment report - Day 30: Outcome and recommended actions documented and implemented

Step 0 — Preparation and inputs - Materials available: - eRMR extract (saved PDF/CSV) with metadata (date, filters, DLP) - Line-listing of all ICSRs for MedX + SSRx (downloaded and redacted as required) - Product master data (indications, authorised population, concomitant meds) - Recent PSURs and RMP sections - Systems: - Signal tracker (unique ID created: SIG-2026-001) - Document repository with version control

Step 1 — Receipt and triage (Signal Detection Analyst) Action - Save the eRMR extract to the document repository and attach to SIG-2026-001 in the tracker. - Complete the Triage Worksheet within 3 working days.

Triage Worksheet (example fields) - eRMR ID / extract date: eRMR_2026-06-01 - Product: MedX (MAH: Acme Pharma) - Event PT: Severe skin reaction (SSRx) - Disproportionality metric: PRR = 3.1; lower bound 95% CI > 1 - Case count (EU): 12 cases in last 6 months - Serious cases: 6 (including 1 fatal) - Geographical distribution: 6 countries - Temporal trend: rising monthly counts over 3 months - Minimum case threshold exceeded: Yes - Known ADR in label: No / not in EU SmPC (check) - Initial triage outcome: Proceed to validation - Triage reviewer: Analyst name, date/time, electronic signature or user ID

Inspection relevance - Inspectors will expect the saved eRMR with metadata and the completed triage worksheet showing the logic for proceeding to validation.

Step 2 — Validation (PV Physician / Medical Reviewer) Action - Perform case-level review of the 12 ICSRs, focusing on: - Case narratives and clinical details - Time-to-onset relative to product exposure - Concomitant medications or alternative causes - Dechallenge/rechallenge information - Laboratory or biopsy evidence where available - Review background incidence of SSRx in the treated population if available - Run sensitivity checks using EVDAS (e.g., restrict to EU cases, restrict to serious only)

Validation Report (example fields) - Signal ID: SIG-2026-001 - Date received for validation: Day 1 - Medical reviewer: Dr. A (PV Physician), credentials - Summary of case-level findings: - 8 of 12 cases temporal plausibility (onset 3–21 days post-exposure) - 4 cases with clear alternative cause (concomitant antibacterial drugs known for skin reactions) - 3 cases with confirmed biopsy consistent with immune-mediated reaction - 2 cases where MedX was only suspect drug and outcome required hospitalisation - Assessment of reporting bias or stimulation: None evident; no known regulatory action or media attention - Comparator/contextual information: No similar pattern in therapeutic class reported - Validation conclusion: Validated — plausible and enough concern for escalation to SRT for formal assessment - Recommended immediate actions: Add to watchlist; request follow-up information for 5 cases with incomplete narratives - Validation reviewer sign-off: Dr. A name, date/time

Documentation and audit trail - Attach case summaries and redacted narratives to the validation report in the tracker. - Record follow-up requests in the case management system with deadlines and owners.

Inspection relevance - Inspectors will look for the medical reviewer’s rationale, evidence of case-level analysis and documented sign-off.

Step 3 — Escalation (Signal Detection Lead / Head of PV) Action - Following validation, prepare an escalation memo to the Signal Review Team and QPPV. - Update SIG-2026-001 status to "Escalated — SRT review required".

Escalation Memo (example fields) - Signal ID: SIG-2026-001 - Summary of detection and validation findings (1–2 paragraphs) - Rationale for escalation: number of serious cases, temporal plausibility, biopsy confirmation in some cases - Recommended SRT agenda items: - Review of case narratives and validation report - Consideration of immediate regulatory reporting obligations - Short-term risk minimisation vs. further data collection - Attachments: eRMR, validation report, case summaries - Escalation authoriser: Signal Detection Lead name, date/time

Inspection relevance - Inspectors expect to see an escalation memo with attachments and evidence that the QPPV or delegated signatory was notified.

Step 4 — SRT Assessment (Signal Review Team) Action - Convene SRT within defined SLA (e.g., within 7 working days). - Present validation report, case narratives and contextual data. - Document minutes, attendees, declared conflicts of interest and decisions.

SRT Meeting Minutes (example fields) - Date/time and location - Attendees and roles: PV Physician (Chair), Safety Data Scientist, Regulatory Affairs representative, Clinical Expert, QPPV (or delegate), Quality Assurance observer - Conflicts of interest: none declared - Discussion highlights: - Consensus that SSRx is clinically plausible and warrants further assessment - Request for targeted epidemiology assessment to estimate background rates - Decide to perform follow-up on all outstanding cases (5) and request additional lab/biopsy reports - Decisions and actions: - Action 1: Initiate expedited follow-up (owner: case management lead; due: Day 14) - Action 2: Prepare preliminary signal assessment report (owner: PV Physician; due: Day 10) - Action 3: Regulatory Affairs to prepare draft notification in case further action required (owner: RegAff; due: Day 12) - SRT conclusion: Signal remains under active assessment; escalate to QPPV for oversight if new serious data emerge - Minutes author: name, sign-off date

Inspection relevance - Inspectors will expect minutes showing multidisciplinary review, rationale for decisions and allocation of actions.

Step 5 — Assessment reporting and regulatory interface Action - Prepare a preliminary signal assessment report summarising: - Detection and validation findings - Case-level evidence and follow-up results - Literature and class data review - Proposed next steps (e.g., further pharmacovigilance, RMP change, epidemiological study) - Determine whether expedited reporting to authorities is required based on seriousness and regulatory requirements (e.g., serious unexpected ADRs may require submission in appropriate formats and timelines) - If regulatory interaction is necessary, prepare QPPV-signed correspondence with attachments

Signal Assessment Report (example fields) - Signal ID: SIG-2026-001 - Objective and scope of assessment - Data reviewed (eRMR date, number of ICSRs, follow-up outcomes) - Clinical assessment and causality considerations - Proposed risk minimisation or monitoring plan - Impact on RMP and product information - Recommendation: Continue active surveillance and initiate pharmacoepidemiology study; no immediate PSUR label change at this time - Approvals: PV Physician, Head of PV, QPPV (or delegated approval), date

Inspection relevance - Inspectors will look for formal assessment reports that document the scientific basis for decisions and any regulatory communication.

Step 6 — Actions, tracking and closure Action - Open required workstreams in project or signal tracking systems: - Follow-up completions - Epidemiology protocol development - Communication plan for health care professionals if required - Track completion of all actions in the signal tracker; update status periodically (e.g., Active — Under Investigation, Active — Under Study, Closed, Referred to Regulatory Authority) - Close the signal when criteria for closure are met and document rationale (e.g., insufficient evidence, confounding clarified, or signal confirmed and managed)

Closure record (example fields) - Signal ID: SIG-2026-001 - Final status: Active — Under Study (if ongoing) or Closed - Reason for closure: [if closed] - Date closed: date - Closures approved by: QPPV signature and date - Archive location of documents: repository path

Inspection relevance - Inspectors expect closure rationale, approvals and traceability to original detection artifacts.

KPIs and Suggested SLAs for eRMR-Based Signal Management

KPIs provide measurable evidence that the signal management system is functioning and can be a focus of inspection. Below are recommended KPIs, suggested thresholds (organisationally defined), and rationale. Organisations should define their own SLAs in SOPs in line with resources and product risk profiles.

Operational KPIs - eRMR generation adherence: % of scheduled eRMRs produced and archived on time (target: 100%) - Triage timeliness: % of eRMRs triaged within SLA (suggested SLA: 3 working days) (target: ≥95%) - Validation timeliness: median time from triage to validation decision (suggested target: ≤30 calendar days for non-complex cases; shorter for serious signals) - Escalation timeliness: % of validated signals escalated to SRT/QPPV within SLA (suggested SLA: 5 working days) (target: ≥95%) - SRT meeting frequency adherence: % of escalations addressed at SRT within SLA (suggested target: ≥90%)

Quality KPIs - % of eRMRs resulting in validation (validated vs closed at triage) - % of validated signals with documented medical review and sign-off (target: 100%) - Completeness of documentation: % of signal records with all required artifacts attached (eRMR, triage worksheet, validation report, SRT minutes) (target: ≥98%)

Outcome KPIs - Time from validation to regulatory notification when required (target defined per regulatory timelines) - % of validated signals that progress to formal assessment or study within 90 days - % of signals closed with documented rationale and QPPV approval (target: 100%)

Governance KPIs - Training completion rate for core signal detection staff (target: 100% annually) - Number of audit findings related to EVDAS/eRMR processes per year (target: trend toward zero)

Inspection relevance - Inspectors will expect a KPI dashboard and trend reports demonstrating oversight. Be prepared to explain KPI definitions, data sources, rationale for thresholds and action plans where targets are missed.

Roles and Responsibilities — Clear Assignments

The following table summarises commonly used roles and responsibilities in an EVDAS/eRMR signal management process. These should be captured in SOPs and in the PSMF.

Inspection relevance - Inspectors will expect that responsibilities are documented, that persons named in roles are traceable, and that segregation of duties and independence are managed for critical decisions.

Governance Considerations

Effective governance goes beyond procedures. Key elements include:

• Integration in the PSMF with up-to-date single-source references to all SOPs, committees and roles.
• A Signal Management Charter that defines committee remits, membership, quorum, conflict of interest declarations and escalation pathways.
• Version control and change management for SOPs and templates, with evidence of review and approval.
• Regular management reporting (monthly/quarterly) including KPI trends, outstanding actions and resource adequacy.
• A documented training curriculum and competence assessment for staff performing specialised tasks (medical review, statistical analysis).
• Periodic effectiveness reviews and simulation exercises (tabletop exercises for signal escalation) to verify readiness.
• Clear linkage to risk management plans (RMPs), PSUR/Periodic Safety Reports and regulatory submission processes.

Inspection relevance - Inspectors will review governance artefacts to assess whether the system can deliver consistent, auditable and timely action. Documented committee minutes, metrics and follow-up actions are central evidence.

Audit, Quality Assurance and Continuous Improvement

Quality assurance activities provide independent confirmation that the signal detection system operates as intended. Recommended practices include:

• Routine internal audits of EVDAS/eRMR processes and a corrective action plan with tracked closure.
• Periodic review of statistical thresholds and comparator strategies with documented rationale, aligned with current best practice (CIOMS/EMA guidance).
• Root cause analysis for significant missed signals or inspection findings.
• Continuous training updates reflecting changes in EVDAS functionality, regulatory expectations and internal process improvements.

Inspection relevance - Inspectors will expect to see evidence of QA activity, remediation of findings, and demonstrable improvements.

Key Takeaways

• EVDAS is the analytical environment built upon EudraVigilance data and supports structured signal detection via outputs such as eRMRs.
• eRMRs are detection tools; statistical signals require medical validation and structured assessment in line with GVP Module IX.
• Robust governance, documented SOPs, clear roles and responsibilities, and an auditable trail from detection to decision are essential for regulatory compliance and inspection readiness.
• An inspection-ready signal management system combines timely processes (triage, validation, escalation), complete documentation (eRMRs, triage worksheets, validation reports, SRT minutes), KPIs and demonstrated oversight by the QPPV.
• The worked example shows a practical, stepwise approach to review, documentation and escalation for an eRMR, and can be adapted to organisational SOPs and SLAs.

References

1. EMA Good Pharmacovigilance Practices (GVP) Module IX – Signal Management.
2. EMA EudraVigilance Data Analysis System (EVDAS) User Guide.
3. Regulation (EC) No 726/2004.
4. Directive 2001/83/EC.
5. Commission Implementing Regulation (EU) No 520/2012.
6. EMA Signal Management Guidance.
7. CIOMS Working Group VIII Practical Aspects of Signal Detection.
8. ICH E2E Pharmacovigilance Planning.