The Pharmacovigilance System Master File is one of the most operationally demanding documents in a Marketing Authorisation Holder’s compliance programme. It is not a document you create once and file. It is a living record of your pharmacovigilance system that must accurately reflect the actual state of your PV operations at any given moment. When a regulatory inspector asks to review your PSMF, they are not looking at a historical snapshot. They are assessing whether the document in front of them describes how your PV system actually works today.
This creates a persistent compliance challenge that many MAHs underestimate. Routine business events that trigger no immediate regulatory filing obligation can still leave your PSMF materially out of date within weeks if maintenance is not built into your standard operating procedures for those events. Three of the most common triggers for PSMF inaccuracy are licence variations, product transfers between MAHs, and MAH name or address changes. Each of these events touches multiple sections of the PSMF simultaneously and each is routinely handled in a way that updates the regulatory licence but leaves the PV documentation behind.
This guide provides a practical maintenance checklist for each of these three trigger events and explains what inspectors specifically look for when they examine PSMF currency following a business change.
What the PSMF Must Contain and Why Currency Matters
Before working through the specific checklists, it is worth being precise about what the PSMF is required to contain under EU GVP Module II, which sets the foundational requirements for PSMF content applicable across EMA, MHRA, and other authorities aligned with GVP standards.
The PSMF must include or reference:
- The identity and contact details of the Qualified Person for Pharmacovigilance and any local or national pharmacovigilance contact persons
- A description of the organisational structure of the MAH including the PV function and its relationship to other functions such as medical affairs, regulatory affairs, and quality
- The location of the safety database and confirmation of who is responsible for its operation and maintenance
- A description of the computerised systems and databases used in the pharmacovigilance system
- Reference to quality system documentation including SOPs relevant to PV activities
- Details of outsourced PV activities and the service providers performing them, with references to pharmacovigilance agreements
- A description of the aggregate reporting system and the products covered
- Details of ongoing and completed post-authorisation safety studies
- An audit history of the PV system
The PSMF also contains a product list as an annex, listing all medicinal products covered by the PV system along with their marketing authorisation numbers and the countries in which they are authorised. This annex is one of the most frequently outdated sections of a PSMF and one of the first things an inspector will cross-reference against the MAH’s actual authorisation portfolio.
The regulatory requirement is clear. The PSMF must be kept up to date and the MAH must be able to provide it to a competent authority on request within seven days. In practice, inspectors expect it to reflect the current state of the PV system on the day of the inspection, not the state it was in at the last scheduled update.
Trigger One: Licence Variation
A licence variation is one of the most common business events in pharmaceutical product lifecycle management, yet its impact on the PSMF is systematically underestimated. A variation changes something about the marketing authorisation, whether that is the indication, dosage form, strength, packaging, manufacturing site, or any other approved parameter. Each of these changes can have direct implications for the pharmacovigilance system and therefore for the accuracy of the PSMF.
The type of variation determines the specific PSMF sections affected, but every variation should trigger a formal PSMF impact assessment as part of the change control process. The following checklist covers the PSMF sections that most commonly require review and update following a licence variation:
- Product annex: If the variation results in a new product name, new marketing authorisation number, new country of authorisation, new dosage form, or new strength, the product list annex must be updated to reflect these changes. A variation that adds a new indication or extends an existing authorisation to a new market should also be captured here.
- Aggregate reporting obligations: A new indication, patient population, or dosage form may change the risk profile of the product and therefore the content expected in periodic safety update reports. The PSMF description of your aggregate reporting programme should reflect the current scope of what is being monitored and reported.
- Post-authorisation safety studies: Some variations, particularly those resulting from referral procedures or risk management plan updates, include conditions requiring new or updated post-authorisation safety studies. If a variation has generated a new PASS obligation, this must be reflected in the PSMF.
- Risk management plan integration: If the variation triggered an RMP update, the PSMF should reference the current version of the RMP and confirm that your PV system is configured to implement the risk minimisation measures it contains.
- Signal detection scope: A new indication or extended patient population may require updates to your signal detection methodology, particularly if the variation introduces a new therapeutic area where the background incidence of relevant adverse events differs significantly from the existing indication. The PSMF description of your signal detection process should reflect this.
- Labelling and product information: If the variation resulted in updates to the Summary of Product Characteristics or package leaflet, the PSMF should reference the current approved product information versions.
- SOP references: If the variation required updates to any PV-relevant SOPs, confirm that the PSMF references the current SOP versions rather than superseded ones.
A practical point worth emphasising: the PSMF product annex should be treated as a dynamic document with a formal update trigger built into every variation change control. Many MAHs update their regulatory tracking systems when a variation is approved but do not have a formal step in the change control process that routes a PSMF impact assessment to the PV team. Building this connection between the regulatory affairs and pharmacovigilance functions is one of the most effective structural improvements an MAH can make to their PSMF maintenance programme.
Trigger Two: Product Transfer Between MAHs
A product transfer, where a marketing authorisation moves from one MAH to another, is one of the most complex events a pharmacovigilance system has to manage. It is also one of the most common sources of PSMF inaccuracy because the transfer involves two separate organisations each of which needs to update their own PSMF, and the handover of pharmacovigilance responsibilities is not always cleanly documented or operationally complete at the point when the licence transfer takes effect.
For the receiving MAH, the PSMF must be updated to reflect the addition of the transferred product to the PV system. The following checklist covers the specific sections that require attention:
- Product annex: Add the transferred product with its marketing authorisation number, authorised countries, and the effective date of the MAH transfer. Confirm that the product is now covered by your PV system and that the entry in the product annex is consistent with the regulatory licence as transferred.
- QPPV responsibility confirmation: The QPPV named in your PSMF is responsible for oversight of pharmacovigilance for all products listed in the annex. Confirm that your QPPV has been formally briefed on the transferred product, its safety profile, any outstanding PASS obligations, and any open signals or ongoing regulatory commitments.
- Safety database: The safety database entry for the transferred product must reflect the new MAH. If individual case safety reports associated with the product were held in the previous MAH’s database, the transfer of that case history to your own safety database must be documented. Inspectors will look for evidence that ICSR history has been transferred completely and that no cases have been lost in the transition.
- Pharmacovigilance agreements: If you are outsourcing any PV activities for the transferred product to a third party, including the previous MAH under a transitional services agreement, the pharmacovigilance agreement with that party must be in place before the transfer effective date and referenced in the PSMF.
- Literature monitoring: Confirm that literature monitoring for the transferred product’s active substance has been added to your literature monitoring programme and that there is no gap period between the end of the previous MAH’s monitoring and the start of yours.
- Aggregate reporting calendar: Add the transferred product to your PSUR or PBRER schedule. Check whether the product is included in a worksharing procedure for aggregate reporting and if so confirm your obligations within that procedure.
- RMP transfer: If the product has an approved risk management plan, obtain the current approved version from the transferring MAH and confirm that your PV system is configured to implement the risk minimisation measures it requires. The PSMF should reference the current RMP version.
- Outstanding regulatory commitments: Review all outstanding regulatory commitments associated with the transferred product including PASS obligations, specific obligations, and any commitments made in response to PSUR or signal assessment procedures. These commitments transfer with the licence and the PSMF must reflect your system for managing them.
For the transferring MAH, the PSMF must be updated to remove the transferred product from the product annex from the effective date of the transfer, with appropriate documentation confirming the transfer and the handover of all pharmacovigilance obligations to the receiving MAH.
Trigger Three: MAH Name or Address Change
An MAH name change or registered address change is often treated as an administrative event with minimal compliance implications. In the context of the PSMF, this is a significant underestimation of the update work required. The MAH identity and address appear in multiple sections and referenced documents throughout the PSMF and in the regulatory submissions associated with it.
The following checklist applies to MAH name and address changes:
- PSMF cover page and header: Update the MAH name and address on the PSMF cover page and in any document header where the MAH identity is stated.
- QPPV contact details: If the QPPV’s contact address or the address at which the PSMF is held is affected by the change, update these entries. Regulators require the PSMF to be accessible within seven days of a request and the location stated in the PSMF must be accurate.
- Pharmacovigilance agreements: Review all pharmacovigilance agreements with third-party service providers and confirm whether the MAH name change requires formal contract amendments. Agreements that reference the old MAH name without an amendment in place create a documentary inconsistency that inspectors will note.
- Regulatory authority notifications: Confirm that all relevant regulatory authorities have been notified of the name or address change through the appropriate variation or notification procedure. The PSMF cannot accurately reflect the MAH identity until the regulatory record has been updated.
- Safety database system settings: Many safety database systems store the MAH name and address as system configuration parameters used in ICSR submissions and regulatory reports. Confirm that these system settings have been updated to reflect the new MAH name and that any pending or in-progress submissions use the correct MAH identity.
- SOP headers and document management system: SOPs and controlled documents that reference the MAH name in their headers or footers should be reviewed and updated through the document management system. Superseded documents with the old MAH name should be retired in the document management system to prevent their continued use.
- Product information documents: If the MAH name appears on the approved Summary of Product Characteristics or package leaflet, a variation to update these documents should be initiated in parallel with the PSMF update.
Building PSMF Maintenance Into Your Quality System
The most effective way to ensure PSMF currency is not to treat PSMF maintenance as a standalone activity but to embed PSMF impact assessment as a formal step in the change control, variation management, and business development processes that generate the events described above.
Practically this means:
- Every variation change control record should include a mandatory PSMF impact assessment step before the variation is submitted, with a defined owner in the PV team
- Every product acquisition or transfer should have a formal PV handover checklist that maps to the PSMF sections affected and confirms completion before the transfer effective date
- Every corporate event including name changes, address changes, mergers, and acquisitions should trigger a formal PSMF review as part of the corporate change management process
- The PSMF should have a defined review frequency independent of trigger events, with a minimum annual review conducted by the QPPV or a delegated PV manager, to catch any drift between the PSMF description and actual PV operations
One dimension of PSMF maintenance that is consistently underestimated is the review of referenced documents. The PSMF does not reproduce the content of SOPs, pharmacovigilance agreements, and other controlled documents in full. It references them. When those referenced documents are updated, superseded, or replaced, the PSMF references must be updated to point to the current versions. A PSMF that references superseded SOP versions is considered inaccurate even if the procedural content itself is correct.
How Quality and Vigilance Supports PSMF Maintenance and Compliance
At Quality and Vigilance, we work with Marketing Authorisation Holders at every stage of the pharmacovigilance system lifecycle, from initial PSMF construction through to ongoing maintenance, gap assessment, and inspection readiness review. We understand the operational pressures that lead to PSMF drift and we bring the independent perspective needed to identify inaccuracies that internal teams, working close to the document, may no longer see clearly.
Our PSMF review service assesses the currency and accuracy of every section of your PSMF against your actual PV operations, your current product portfolio, and the regulatory requirements applicable to your markets. We identify gaps, inconsistencies, and outdated references, and we provide a clear prioritised action plan to bring your PSMF to inspection-ready standard.
Whether you are preparing for a regulatory inspection, have recently experienced a product transfer or MAH change, or simply want confidence that your PSMF accurately reflects your PV system, our team is ready to support you.
Contact Quality and Vigilance today to arrange a PSMF gap assessment and ensure your pharmacovigilance documentation is inspection-ready before the regulator asks to see it.