The PSMF — What It Actually Contains

The Pharmacovigilance System Master File is exactly what its name suggests: a single, master document describing a company’s entire pharmacovigilance system, governed in the EU by GVP Module II and Commission Implementing Regulation (EU) No. 520/2012. It exists because a regulator evaluating whether a company’s PV system is adequate needs a comprehensive, current description of that system — not scattered SOPs, not tribal knowledge held by individual staff, one authoritative document.

That document breaks into six core sections, each answering a specific question about the system. It opens with the QPPV and deputy arrangements from Lesson 11.2 — who is accountable, and how absence is covered. It moves to the organisational structure: how the company’s PV function is actually built, including any outsourced activities to CROs or vendors, and the reporting lines that connect them. It then describes the sources of safety data — every channel through which case information enters the system, echoing the breadth Module 7 covered for signal sources, but here documented specifically as part of the company’s own operational description.

The fourth section covers computerised systems and databases — which validated safety database is in use (Module 10’s entire subject), how it’s maintained, and how access is controlled. The fifth, PV system processes, is where the actual operational description lives: how case processing, signal management, and risk management genuinely function in this specific company’s practice, not as a generic textbook description but as this company’s actual workflow. And the sixth, the quality system, closes the document by describing the audits, CAPA process, and training records that keep everything else in the PSMF honest — exactly the subject Module 12 unpacks in full depth.

The PSMF’s significance in practice is hard to overstate: it’s the first document a regulator requests at the start of a PV inspection, precisely because it’s meant to give an inspector a working understanding of the entire system before they observe a single case being processed. And that’s exactly why an inaccurate PSMF is genuinely dangerous rather than merely embarrassing — a document describing an idealised, aspirational process that operational reality has drifted away from doesn’t just fail to help an inspector, it actively misleads them about what the system actually does, which is precisely the failure mode Lesson 11.5 addresses directly.