The Pharmacovigilance Plan

If the Safety Specification defines the risk picture, the Pharmacovigilance Plan defines exactly how the organisation is going to monitor it going forward — and it has two tiers, echoing the routine-versus-additional structure the previous lesson introduced for risk minimisation measures. Routine pharmacovigilance activities are, in a real sense, everything this entire course has covered up to this module: spontaneous case collection and processing, MedDRA coding, causality and seriousness assessment, signal detection, and periodic aggregate reporting. These happen for essentially every marketed product, all the time, regardless of what’s in the Safety Specification.

Additional pharmacovigilance activities are specifically triggered by gaps the Safety Specification identifies that routine surveillance alone isn’t well suited to close — most commonly missing information (a population genuinely under-studied) or a potential risk that needs more targeted evidence before it can be confirmed or ruled out as an identified risk. Common examples include a dedicated post-authorisation safety study (PASS) designed specifically to investigate a particular concern, a pregnancy exposure registry systematically collecting outcome data that spontaneous reporting alone would capture too sparsely and unsystematically to be useful, or structured enhanced monitoring targeting a specific population identified as a missing-information gap.

The Pharmacovigilance Plan, in other words, is the RMP’s explicit, documented acknowledgment that routine surveillance — however well-run — isn’t always enough on its own to close every gap a careful Safety Specification identifies. A missing-information gap around pregnancy exposure, for instance, isn’t going to resolve itself through ordinary spontaneous reporting at a pace or with a data quality that’s actually useful; it needs a deliberately designed, targeted study built specifically to capture that population’s outcomes systematically.

This is also where the RMP connects most directly back to the practical machinery covered throughout the rest of this course — an additional PV activity generates the same kinds of cases, requiring the same coding discipline from Module 4, the same narrative quality from Module 5, and feeding into the same signal detection process from Module 7 as any other case, just collected through a more deliberately structured mechanism aimed at a specific, pre-identified gap rather than passive spontaneous reporting.