What Problem Does an RMP Actually Solve?

Step back and look at everything this course has covered so far as a pattern: MedDRA coding processes cases that have already arrived. Narrative writing documents events that have already happened. Causality assessment judges cases already reported. Signal detection analyses accumulated data. Aggregate reporting summarises an interval that’s already passed. All of it, however sophisticated, is fundamentally reactive — responding to safety information after it exists.

A Risk Management Plan is different in kind, not just in scope. Rather than responding to what’s already happened, an RMP is a living, forward-looking document specifically planning how a product’s known and potential risks will be characterised, monitored, and actively minimised — both before approval, informing what data still needs to be gathered, and throughout the product’s marketed life, as the risk picture evolves. GVP Module V, which governs RMPs in the EU, represents exactly this shift in orientation: pharmacovigilance isn’t only about detecting and reporting what happened, it’s equally about deliberately planning for what might happen and having a documented strategy ready before it does.

This reframing matters for how the rest of this module should be read. Every lesson from here forward describes something an organisation decides and commits to in advance — which risks warrant additional monitoring beyond routine surveillance, which risks warrant active intervention beyond a label warning, how the organisation will know whether those interventions are actually working. This module works through that structure the same way Module 8 worked through the PBRER: RMP structure first, each individual part in depth, then how the plan evolves over a product’s lifecycle and how the EU’s RMP approach compares to the US’s REMS system.