Signal management is where pharmacovigilance turns data into decisions. GVP Module IX describes it as a critical process, and inspectors treat it that way [1]. Since August 2025 the EU framework has also changed in ways that many procedures have not yet caught up with: all marketing authorisation holders (MAHs) with products authorised in the EEA must monitor EudraVigilance, and the standalone signal notification has gone [2][3].
This article summarises what a defensible MAH signal management process looks like today, from validation to documentation.
The legal framework in brief
Signal management is defined in Article 107h of Directive 2001/83/EC, Article 28a of Regulation (EC) No 726/2004 and Implementing Regulation (EU) No 520/2012, as amended by Implementing Regulation (EU) 2025/1466 [3]. The Implementing Regulation defines a signal as information from one or multiple sources suggesting a new potentially causal association, or a new aspect of a known association, between an intervention and an event, judged to be of sufficient likelihood to justify verificatory action (Art 19(1)) [4]. The EU process comprises signal detection, validation, confirmation, analysis and prioritisation, assessment, and recommendation for action (Art 21(1)) [4].
GVP Module IX Rev 1 remains the current guidance. EMA has stated that an update aligned with the amended Implementing Regulation was scheduled for the second quarter of 2026 [2]; at the time of writing, Rev 1 is still the version published on the EMA GVP page [5].
What changed in 2025
Implementing Regulation (EU) 2025/1466 changed two provisions with immediate effect from its entry into force in August 2025 [2][3]:
- EudraVigilance monitoring for all MAHs. The 2018 pilot, limited to a list of active substances, ended. All MAHs with products authorised in the EEA shall monitor EudraVigilance data and use them together with other sources (Art 18(2)) [2][4].
- No standalone signal notifications. Article 21(2) was deleted. MAHs are no longer expected to submit validated signals via the standalone signal notification form. Signals from all sources, including EudraVigilance, are handled within the MAH's own signal management process, with actions taken through variations and PSURs [2].
EMA expects MAHs to describe these changes in their procedures, including how EudraVigilance data will be monitored, at which step they are used, and how often, proportionate to the product's risk and characteristics. EMA also expects EudraVigilance data to be used during the validation and evaluation stages [2].
Procedures that still describe the 30-day standalone notification in GVP Module IX Rev 1, section IX.C.4.3, are out of date.
Signal validation
Validation asks whether the available documentation contains sufficient evidence of a new potentially causal association, or a new aspect of a known association, to justify further analysis (IR Art 21(1)) [4]. GVP Module IX section IX.B.3 groups the considerations into three areas [1]:
| Area | What to consider (GVP IX.B.3) |
|---|---|
| Previous awareness | Whether the association is already in the product information, or has been assessed in the initial application, RMP, PSUR or another procedure |
| Strength of evidence | Number of cases after removing duplicates and how many are supportive (temporal association, de- or rechallenge, no alternative cause); cases in context of exposure; related MedDRA terms; consistency; data quality; recognised case definitions such as Brighton Collaboration or RegiSCAR; dose-reaction; biological plausibility; disproportionality where applicable |
| Clinical relevance and context | Seriousness, severity, outcome and reversibility; new insight on a known reaction; interactions; vulnerable populations; patterns of use such as overdose, misuse, off-label use or medication errors |
A signal is then validated, meaning further analysis is justified, or non-validated, meaning the evidence at that point does not warrant it [1]. Non-validated is not the same as closed for ever. Record what new information would reopen it.
New aspects of a known association count. Module IX gives changes in frequency, distribution (for example by sex, age or country), duration, severity or outcome as examples [1]. A labelled reaction that is becoming more severe or more frequent can still be a signal.
Prioritisation
Prioritisation runs throughout the process, not only after validation. Module IX lists factors including severity, seriousness, outcome and reversibility; potential for prevention; exposure and estimated frequency; exposure in vulnerable populations; consequences of stopping treatment and availability of alternatives; the likely extent of regulatory action; and whether the signal may apply to the whole class [1]. Signals that could attract media or public concern, such as events after mass immunisation, may deserve particular attention.
The practical point is that prioritisation drives timelines. A high-priority signal may need interim risk minimisation before the assessment is complete [1].
Assessment and outcomes
Assessment evaluates a validated signal using all available evidence to decide whether there is a new risk or a changed known risk [1]. Additional sources may include clinical trial data, literature on similar cases and on the class, epidemiology of the event and underlying disease, non-clinical findings, larger datasets such as EudraVigilance, healthcare databases and information from other regulators [1].
The outcomes, and the routes MAHs should use, now look like this:
| Outcome | What the MAH does |
|---|---|
| Refuted signal | Document the rationale; present it in the next PSUR if within the reporting interval [1] |
| New or changed risk needing product information or RMP change | Submit a variation; MAHs must keep product information up to date (Reg 726/2004 Art 16(3); Dir 2001/83/EC Art 23(3)) [3] |
| Signal concluded or ongoing during a PSUR interval | Present in the PSUR signal sections (15 and 16 of the EU PSUR format); use "late-breaking information" if after the data lock point [1][6] |
| Emerging safety issue | Notify the competent authorities where the product is authorised and EMA (P-PV-emerging-safety-issue@ema.europa.eu) no later than 3 working days after establishing that the definition is met [1][3] |
For signals detected through EudraVigilance, Module IX Rev 1 sets a benchmark of submitting a variation within 3 months of completing the assessment for an important risk, and within 6 months otherwise [1]. Until the revised module is published, this remains a sensible internal standard.
An emerging safety issue is a safety issue considered to require urgent attention by the competent authority because of a potential major impact on the benefit-risk balance or on patients' or public health. Examples are an unexpectedly increased rate of fatal or life-threatening events in a study, a spontaneous or literature signal that may lead to a contraindication, restriction or withdrawal, and major safety-related regulatory action outside the EU [1].
Documentation: what an inspector will look for
GVP Module IX section IX.B.5 sets out quality requirements that translate directly into inspection questions [1]:
- A tracking system with an audit trail recording dates, analyses, decisions and rationale for every step, allowing timeliness to be confirmed.
- Documented procedures, including the rationale for detection methods and periodicity, and the decision tree used internally.
- Assigned roles for documentation, quality control, review and CAPA.
- Trained staff, specifically in signal management for their role.
- PSMF description of the signal management process, with performance indicators in the PSMF annex where used.
- Record management that keeps decisions traceable, consistent with IR Article 12 [4].
A useful self-test is to select three closed signals and ask a colleague who was not involved to reconstruct, from the records alone, why each decision was taken and when. If that is not possible, the process is not yet inspection-ready.
Practical recommendations
- Update procedures for EudraVigilance monitoring and the removal of standalone notifications, and state where in the process EudraVigilance data are used.
- Define validation criteria explicitly, mapped to IX.B.3, so that decisions are reproducible across reviewers.
- Record non-validated signals with the same discipline as validated ones.
- Link the signal tracker to PSUR, RMP and labelling workflows so that conclusions reach the right procedure.
- Watch for the revised GVP Module IX and plan a procedure update when it is published.
If you would like an independent review of your signal management process or help assessing a specific signal, contact us.
Sources
- GVP Module IX Rev 1: Signal management (EMA)
- EMA Q&A on Implementing Regulation (EU) 2025/1466 and conclusion of the MAH EudraVigilance signal detection pilot, EMA/243145/2025 Rev 2, 28 January 2026 (EMA)
- EMA Questions and answers on signal management, EMA/261758/2013 Rev 5, 19 January 2026 (EMA)
- Implementing Regulation (EU) No 520/2012, consolidated version 12.02.2026 (EUR-Lex)
- Good pharmacovigilance practices (GVP) overview page (EMA)
- GVP Module VII Rev 1: Periodic safety update report (EMA)
This article is for information only and is not medical or regulatory advice.
Related services: signal management and benefit-risk assessment and PV system and inspection readiness.
Follow Safety Strategy on LinkedIn (opens in a new tab) for new articles and updates. Back to all news