PSMF Maintenance and Change Control

Introduction

Creating a Pharmacovigilance System Master File is relatively straightforward.

Maintaining it accurately over time is far more difficult.

Many organisations begin with a high-quality document.

Over time, however, the pharmacovigilance system evolves:

• Products are acquired.
• Products are divested.
• Vendors are replaced.
• Databases are upgraded.
• Organisational structures change.
• QPPVs change.
• Affiliates are added.

Unless maintenance activities evolve at the same pace, the PSMF gradually becomes less accurate.

This process is often subtle.

The document may remain largely correct while becoming progressively less representative of operational reality.

For this reason, experienced inspectors often view PSMF maintenance as a governance issue rather than a documentation issue.

The Real Objective of Maintenance

Many organisations approach maintenance incorrectly.

They focus on:

Updating the document.

The actual objective is different.

The objective is:

Ensuring the PSMF continuously reflects the pharmacovigilance system.

This distinction is important.

The goal is not document compliance.

The goal is system representation.

A perfectly formatted PSMF that no longer reflects reality provides little regulatory value.

Why PSMFs Become Outdated

The most common causes include:

• Lack of ownership
• Weak governance
• Poor change control
• Infrequent review
• Resource constraints
• Organisational complexity

Rarely does a PSMF become inaccurate because of a single major failure.

More commonly, numerous small changes accumulate over time.

Examples include:

• One missing vendor
• One outdated organisation chart
• One product not added
• One affiliate not updated

Individually these issues may appear minor.

Collectively they create inspection risk.

The PSMF Lifecycle

A useful way to view the PSMF is as a lifecycle rather than a document.

The lifecycle generally includes:

1. Creation
2. Review
3. Approval
4. Maintenance
5. Verification
6. Improvement

Many organisations invest heavily in stages 1–3.

The strongest organisations focus primarily on stages 4–6.

Ownership Models

One of the most important governance decisions concerns ownership.

Central Ownership Model

A single function owns the entire PSMF.

Advantages:

• Consistency
• Clear accountability

Challenges:

• Heavy workload
• Reliance on one team

Distributed Ownership Model

Different sections have different owners.

Examples:

Advantages:

• Greater expertise
• Better scalability

Challenges:

• Coordination complexity

Hybrid Model

Most mature organisations adopt a hybrid approach.

Central governance coordinates updates while subject matter experts maintain specific content.

Change Control and the PSMF

The strongest PSMF programmes are integrated into change control processes.

Whenever a significant change occurs, organisations should ask:

• Does the PSMF require updating?
• Does an annex require updating?
• Does the QPPV require notification?
• Does oversight documentation require revision?

This transforms maintenance from a reactive activity into a proactive governance process.

Changes That Should Trigger Review

Examples include:

Organisational Changes

• New departments
• Reporting line changes
• New affiliates
• Restructuring

Personnel Changes

• New QPPV
• New deputy QPPV
• New leadership roles

Vendor Changes

• New vendor onboarding
• Vendor termination
• Vendor mergers
• Scope changes

Product Changes

• Acquisitions
• Divestments
• New marketing authorisations
• Product withdrawals

Technology Changes

• Database migrations
• New safety systems
• System retirement
• Significant upgrades

Compliance Events

• Audits
• Inspections
• Significant CAPAs
• Major deviations

These events frequently require PSMF updates.

Review Frequencies

A common question is:

How often should a PSMF be reviewed?

There is no universally correct answer.

The appropriate frequency depends upon:

• Organisational size
• Complexity
• Change volume
• Outsourcing model

Typical approaches include:

The critical point is not frequency.

The critical point is effectiveness.

Annex Maintenance

Most maintenance effort involves annexes.

Commonly updated annexes include:

• Product inventories
• Vendor inventories
• Organisational charts
• Audit schedules
• Inspection histories

These sections often change far more frequently than the main body.

For additional information see:

[[psmf-annexes-guide]]

Maintaining Product Inventories

Product inventories often represent one of the largest maintenance burdens.

Common update triggers include:

• New products
• Withdrawn products
• Acquired products
• Divested products

Many organisations align inventory updates with Regulatory Affairs activities.

This improves consistency and reduces duplication.

Maintaining Vendor Inventories

Vendor inventories are another common source of findings.

Updates should occur when:

• New vendors are approved
• Existing vendors are terminated
• Services change
• Oversight models change

Strong organisations integrate vendor governance and PSMF governance.

The Role of Metrics

Metrics help prevent gradual deterioration.

Examples include:

• Overdue updates
• Missing reviews
• Inventory discrepancies
• Open governance actions

Metrics convert maintenance from a subjective activity into an objective one.

For additional information see:

[[psmf-metrics]]

QPPV Oversight

The QPPV does not necessarily maintain the PSMF personally.

However, regulators generally expect visibility regarding:

• Significant changes
• Major compliance risks
• Governance effectiveness
• Inspection readiness

The QPPV should have confidence that maintenance processes are functioning effectively.

For additional information see:

[[psmf-qppv-oversight]]

Inspection Perspective

Inspectors often review maintenance processes as carefully as the document itself.

Typical questions include:

• Who owns the PSMF?
• How are updates triggered?
• How are changes approved?
• How are inventories maintained?
• How is accuracy verified?

Inspectors are often less interested in a single outdated entry than in the process that allowed it to occur.

Signs of a Mature Maintenance Programme

Characteristics commonly include:

Clear Ownership

Responsibilities are documented and understood.

Change Control Integration

Updates are linked to operational change.

Routine Reviews

Review activities occur consistently.

Metrics

Quality is monitored objectively.

Governance

Senior oversight exists.

Inspection Readiness

The document remains current throughout the year.

The Biggest Mistake Organisations Make

The most common mistake is treating the PSMF as a document.

The PSMF is not simply a document.

It is a representation of the pharmacovigilance system.

When organisations focus exclusively on document maintenance, quality gradually deteriorates.

When organisations focus on maintaining alignment between the document and the system, quality tends to improve naturally.

Key Takeaways

• The objective of PSMF maintenance is to maintain alignment with operational reality.
• Most inaccuracies arise from accumulated small changes rather than major failures.
• Effective change control is one of the most important maintenance tools.
• Product inventories and vendor inventories require particular attention.
• Metrics and governance reviews help prevent gradual deterioration.
• Inspectors often assess maintenance processes as carefully as the document itself.
• Mature organisations treat PSMF maintenance as an ongoing governance activity rather than a periodic documentation exercise.

References

1. EMA Good Pharmacovigilance Practices (GVP) Module II – Pharmacovigilance System Master File.
2. EMA Good Pharmacovigilance Practices (GVP) Module I – Pharmacovigilance Systems and Their Quality Systems.
3. EMA Good Pharmacovigilance Practices (GVP) Module III – Pharmacovigilance Inspections.
4. Regulation (EC) No 726/2004.
5. Directive 2001/83/EC.
6. Commission Implementing Regulation (EU) No 520/2012.
7. EMA Questions and Answers on Pharmacovigilance System Master Files.