The Pharmacovigilance System Master File (PSMF): A Practical Guide for Pharma and Biotech Companies

For companies marketing medicines in the European Union, the Pharmacovigilance System Master File (PSMF) is a core regulatory requirement. The document provides regulators with a detailed overview of the pharmacovigilance system used by the marketing authorisation holder (MAH).

Despite being mandatory, many companies struggle with how to structure the PSMF and how detailed it needs to be.

This article explains the purpose of the PSMF, its regulatory background, and how companies can build a clear and compliant document.

What is a PSMF?

The Pharmacovigilance System Master File (PSMF) is a document that describes the pharmacovigilance system used by a company to monitor the safety of its medicines.

The requirement for a PSMF is defined in EU pharmacovigilance legislation and further detailed in EMA Good Pharmacovigilance Practice (GVP) Module II.

The PSMF must provide regulators with a clear understanding of:

• How the pharmacovigilance system is organised

• Which procedures and processes are implemented

• Who is responsible for PV activities

• How safety data is collected, assessed, and reported

The document must be maintained continuously and kept inspection-ready at all times.

Why the PSMF is Important

The PSMF is often one of the first documents inspected by regulators during pharmacovigilance inspections.

It acts as a central overview of the PV system, linking together procedures, systems, responsibilities, and oversight activities.

If the PSMF is incomplete or inconsistent with the actual pharmacovigilance system, this may lead to inspection findings.

For this reason, the PSMF should not simply be a regulatory formality but a living document that accurately reflects how the PV system operates.

Key Elements of a PSMF

Although the structure can vary, a typical PSMF contains several core sections.

Organisational Structure

This section describes the pharmacovigilance organisation within the company, including:

• The EU Qualified Person for Pharmacovigilance (QPPV)

• Key PV personnel

• Reporting lines and responsibilities

Clear governance structures help regulators understand how safety activities are managed.

Pharmacovigilance Processes

The PSMF must describe the processes used to manage pharmacovigilance activities, such as:

• Adverse event collection

• Case processing

• Signal detection

• Safety reporting

• Risk management activities

These processes are usually supported by Standard Operating Procedures (SOPs).

Computerised Systems

Companies must describe any computerised systems used in pharmacovigilance, including:

• Safety databases

• Signal detection tools

• Document management systems

Authorities may request information about system validation and data integrity.

Oversight of Partners and Vendors

Many pharmacovigilance activities are outsourced to CROs or service providers.

The PSMF should therefore explain:

• Which PV activities are outsourced

• How vendors are qualified and monitored

• How responsibilities are defined in contracts

Clear vendor oversight is an important part of regulatory expectations.

Maintaining the PSMF

The PSMF must always reflect the current pharmacovigilance system.

Companies therefore need processes to ensure the document is regularly updated when changes occur, such as:

• Organisational changes

• New products or marketing authorisations

• Changes to PV procedures

• Updates to safety databases or IT systems

Maintaining an accurate PSMF is essential for inspection readiness.

Common PSMF Challenges

Many companies encounter similar issues when developing their PSMF.

Overly complex documentation

Some companies adopt very large PSMFs based on big pharma templates, which can be difficult to maintain.

Inconsistencies between documents

Regulators often compare the PSMF with:

• SOPs

• training records

• safety database workflows

• contracts with vendors

If information differs between documents, this can lead to inspection findings.

Lack of clear structure

A well-structured PSMF should make it easy for inspectors to quickly understand the pharmacovigilance system.

Building a Practical PSMF

A good PSMF should be:

• Clear and structured

• Aligned with GVP Module II

• Consistent with internal procedures

• Easy to update when changes occur

For smaller pharmaceutical and biotech companies, it is particularly important to ensure that the document remains proportionate and manageable.

Pharmacovigilance Documentation Support

At OZQA, we support pharmaceutical and biotech companies with the development and maintenance of pharmacovigilance documentation, including:

• PSMF development

• Pharmacovigilance SOPs

• GVP compliance support

• Inspection readiness

Our focus is on practical and scalable pharmacovigilance systems that meet EU regulatory expectations.