The pharmacovigilance system master file (PSMF) is the single document that describes how a marketing authorisation holder runs its safety system — and it is almost always the first thing an inspector asks to see. A PSMF that is complete, current and instantly available signals a mature quality culture. One that is out of date can generate findings before the inspection has properly begun.
What the PSMF is, and where the obligation comes from
The PSMF is a detailed description of the pharmacovigilance system a marketing authorisation holder (MAH) operates for one or more authorised medicinal products. The concept is defined in Article 1(28e) of Directive 2001/83/EC, and the minimum requirements for its content and maintenance are set out in Commission Implementing Regulation (EU) No 520/2012. Practical expectations are described in the EMA’s Good Pharmacovigilance Practices (GVP) Module II. Together these establish the PSMF not as a marketing document but as the evidential backbone of a compliant safety system, reflecting the global availability of safety information for products authorised in the EU.
Structure: cover page, core and annexes
The document is conventionally built in three parts:
- Cover page — reference number, version and the responsible MAH.
- Main body (core) — the qualified person responsible for pharmacovigilance (QPPV) and their contact details, the organisational structure, sources of safety data, the computerised systems and databases used, the pharmacovigilance processes, and the quality system that governs them.
- Annexes — the supporting detail, such as contractual arrangements and delegated activities, lists of products and procedures. Annexes change far more often than the core and, in practice, carry most of the maintenance burden.
A logbook records every revision, giving a transparent history of what changed and when.
The requirements that catch companies out
- The PSMF must be located at the EU site where the MAH’s main pharmacovigilance activities are performed, or at the site where the QPPV operates.
- It must be permanently available to the QPPV and permanently available for inspection — including unannounced inspections, at the site where it is kept.
- On request from a competent authority, it must be provided within seven calendar days.
- It must be kept continuously up to date, not refreshed only in the run-up to an audit.
Common weaknesses
Most PSMF findings are avoidable. The recurring themes are annexes that have drifted out of step with reality — expired contracts, superseded QPPV deputy arrangements, stale system lists; logbook gaps that make the change history impossible to reconstruct; core text describing processes the organisation no longer actually follows; and, underneath all of these, no clear ownership for keeping the file current between formal reviews.
How PQRA helps
PQRA builds and maintains PSMFs that stand up to scrutiny. We author the core and annexes against the Implementing Regulation and GVP Module II, establish a disciplined change-control and logbook process, run gap assessments and mock inspections, and support the QPPV so the file is genuinely inspection-ready every day — not just on the day the inspector calls.
If you need to build a PSMF from scratch, bring an existing one back into shape, or prepare for an EOF or EMA pharmacovigilance inspection, get in touch with PQRA to discuss how we can support your safety system.
No responses yet