Building a Pharmacovigilance System Master File That Survives Inspection

What does a PSMF have to contain?

The required content is defined and unglamorous: details of the QPPV including their contact information and a description of their responsibilities, the organisational structure of the holder, the location and nature of the safety databases and other computerised systems, the sources of safety data, written procedures, the contractual arrangements with third parties, and the quality system that governs all of it. Annexes carry the detail that changes most often, which is deliberate: the core document should be stable while the annexes absorb personnel and vendor churn. What trips holders up is not omission but drift, because each of those items is a factual claim with a date attached.

Why do inspectors start with the PSMF?

Because it is the only document that tells them what your system claims to be, which gives them a testable hypothesis. An inspector reads the PSMF and then goes looking for the difference between it and reality. If the file says the QPPV reviews signal detection output monthly, they will ask for twelve months of evidence. If it names a contract research organisation for case processing, they will ask for the safety data exchange agreement and check that the responsibilities in it match the ones described. If it lists a database, they will ask about validation and audit trail review. Every sentence in a PSMF is an invitation to produce evidence, which is why writing it aspirationally is so costly.

How do you keep it accurate?

By tying maintenance to the events that invalidate it rather than to a calendar. Personnel changes, a new contract, a database migration, a change in the deputy QPPV, a new product authorisation, a change in the affiliate network — each has to trigger an update, which means the PSMF owner has to be plugged into procurement, HR and regulatory rather than reviewing the document annually in isolation. Keep the change log meaningful: a version history showing one update per year across a period when the organisation demonstrably restructured tells an inspector the file is not maintained, before they have read a word of the content.

Frequently asked questions

Who owns the PSMF?

The marketing authorisation holder owns it, and the QPPV is responsible for ensuring it accurately reflects the system. In practice a named custodian maintains it day to day, but the accountability sits with the holder and the QPPV, not with the person doing the formatting.

How quickly must it be available to an inspector?

It must be available on request, and in practice that means immediately rather than after retrieval. A file that takes a day to assemble signals that the version described is not the version in use.

Do we need a PSMF if we have only one product?

Yes. The obligation attaches to holding a marketing authorisation, not to portfolio size. A single-product file is shorter, but it needs the same categories of content and the same maintenance discipline.

Sources

1. Good pharmacovigilance practices (GVP) Module II — Pharmacovigilance system master file, European Medicines Agency. ema.europa.eu
2. Commission Implementing Regulation (EU) No 520/2012, European Union. eur-lex.europa.eu

Pending scientific review. This briefing summarises published regulatory guidance and has not yet been signed off by a named subject-matter expert. Verify against the primary sources below before relying on it.

Is your PSMF a description or an aspiration?

We audit pharmacovigilance system master files against the system as it actually runs, and we tell you which sentences you cannot yet evidence.

Explore Pharmacovigilance ➔