GVP Alignment — Keeping the PSMF and Company Practice in Sync

GVP — Good Pharmacovigilance Practices — is the set of EMA guidelines the PSMF exists to demonstrate compliance with. The PSMF isn’t valuable simply because it describes a system; it’s valuable because that description can be measured against a defined standard, and GVP is that standard. A PSMF that’s internally coherent but doesn’t actually align with GVP expectations fails its purpose regardless of how well-written it is.

The harder, more persistent challenge isn’t initially aligning the PSMF with GVP — it’s keeping that alignment as the underlying system changes. This is what practitioners call PSMF drift, and it happens gradually and almost invisibly: a safety database migration happens and Section IV isn’t updated for months. A team reorganisation changes reporting lines and Section II still reflects the old structure. A new outsourced literature-monitoring vendor comes on board and Section III doesn’t mention them. None of these are dramatic failures individually — they’re the ordinary erosion that happens when operational change outpaces documentation discipline.

The fix isn’t a single comprehensive PSMF rewrite every few years — it’s treating the PSMF as a genuinely living document, the same framing Module 9 applied to the RMP, with an active list of update triggers: any database change, any significant organisational restructuring, any new or discontinued data source, any material change to core PV processes should trigger a PSMF review and update as a matter of routine, not as a response to an upcoming inspection.

This connects directly back to the QPPV’s ongoing responsibilities from Lesson 11.2: part of genuinely owning PV system oversight is actively noticing when operational reality and the PSMF’s description of it have started to diverge, and initiating the update before an inspector, an auditor, or a new team member trying to learn the system from the document discovers the gap first. A PSMF review triggered reactively, only once an inspection is announced, is exactly the pattern that produces the rushed, incomplete updates inspectors are trained to notice.