The EU PRAC Signal Management Process

The EU’s approach to signal management runs through PRAC — the Pharmacovigilance Risk Assessment Committee — which is the EMA body specifically responsible for assessing and managing signals across all centrally authorised products, and advising on signals for nationally authorised ones. Where the general principles covered earlier in this module (validation, prioritisation) apply universally, PRAC’s process is the specific EU institutional mechanism that operationalises them at a continental scale.

This module connects directly back to Module 2’s coverage of EU Regulation 2025/1466: one of that regulation’s structural changes was consolidating signal detection around EudraVigilance’s continuous monitoring capability, rather than requiring marketing authorisation holders to run a fully separate, standalone signal notification and tracking process alongside it. Before that consolidation, companies maintained their own parallel signal tracking that periodically reported into the EMA system; after it, EudraVigilance’s own continuous monitoring is the shared backbone that both EMA and marketing authorisation holders work from, with less duplicated, parallel infrastructure.

PRAC’s signals can originate from multiple directions: EMA’s own continuous EudraVigilance monitoring, signals raised by individual member state national competent authorities, and signals reported by marketing authorisation holders following their own validation processes as this module has described them. Once PRAC assesses a signal as validated and warranting action, the range of possible outcomes spans from a straightforward product information (label) update, to a formal request for additional data or studies from the marketing authorisation holder, up to triggering a full EU-wide referral procedure if the concern is serious enough to warrant a comprehensive benefit-risk re-evaluation.

For a PV professional working on the industry side, understanding PRAC’s process matters beyond EU-specific trivia — it’s a concrete, well-documented example of exactly the "validated signal to regulatory action" pipeline this module has been building toward conceptually, made specific and procedural, and it’s a natural point of comparison when Lesson 7.9 looks at how FAERS and VigiBase structure the equivalent process differently.