What is a Pharmacovigilance System Master File?

Juggling product safety rules across different countries can feel impossible. What’s required in the European Union often clashes with FDA expectations, creating serious compliance gaps. A well-structured pharmacovigilance system master file (PSMF) is the key to a unified strategy. This single document provides a coherent overview of your global psmf pharmacovigilance operations, satisfying various international authorities at once. It cuts down on redundant work and minimizes risk. This guide offers practical pharmacovigilance system master file solutions, showing you how to build and maintain a PSMF that meets strict EU requirements and serves as a solid foundation for global compliance.

Key Takeaways

Your PSMF is the definitive guide to your safety system: It’s a dynamic document, not a static file, that must always reflect your current processes to demonstrate regulatory compliance and a commitment to consumer safety.
Compliance depends on a well-defined team structure: While the Marketing Authorization Holder (MAH) holds the ultimate legal responsibility, the QPPV must have clear oversight, and every team member’s role must be documented to ensure accountability.
Stay audit-ready with proactive management habits: Establish a routine for updates, maintain a detailed change log for every modification, and conduct regular internal reviews to find and fix issues before an inspector does.

What is a Pharmacovigilance System Master File (PSMF)?

Think of the Pharmacovigilance System Master File, or PSMF, as the complete blueprint for your company’s drug safety operations. It’s a single, comprehensive document that details every aspect of your pharmacovigilance system—the people, processes, and technologies you use to monitor the safety of your medicines and detect any changes in their risk-benefit balance.

This isn’t just a file you create once and forget about. The PSMF is a living document that must accurately reflect your current safety monitoring practices. It serves as a central reference for your team and provides regulatory authorities with a clear, detailed overview of your entire system. Having a well-maintained PSMF demonstrates that your company is committed to patient safety and is prepared for inspections at any time. It’s your go-to guide for ensuring that safety information is consistently managed across your entire product portfolio.

History and Legal Basis of the PSMF

The PSMF isn’t a new concept; it has been a cornerstone of European pharmacovigilance for over a decade. The requirement for a detailed master file was first introduced into EU law in 2010. Since then, the regulations have become more stringent, with detailed guidelines established in 2012 through the Good Pharmacovigilance Practices (GVP) Module II. These guidelines have been refined over the years, with significant updates in 2013 and 2017 to clarify expectations and ensure that companies maintain a robust and transparent safety monitoring system. This evolution shows a clear trend toward greater accountability and a more structured approach to drug safety management across the EU.

EU Directive 2010/84/EU and GVP Module II

The legal mandate for the PSMF comes directly from EU Directive 2010/84/EU, which made it a non-negotiable requirement for any company holding a marketing authorization in the European Union. The directive’s goal is to ensure that companies have a comprehensive system in place to monitor drug safety and can prove it to regulators at a moment’s notice. GVP Module II provides the practical “how-to” guide, outlining exactly what information the PSMF must contain and how it should be organized. It requires the file to clearly demonstrate that all relevant safety information for medicines sold in the EU is accessible, regardless of where in the world that data originates.

Official Registration and Scope

A PSMF is more than just an internal document; it’s an officially registered file that is part of the broader European regulatory framework. Each PSMF must be logged with the European Medicines Agency (EMA), making it a formal component of your compliance record. This registration process ensures that regulators have a clear and immediate understanding of where your pharmacovigilance system is located and who is responsible for it. The scope of the PSMF is also flexible, allowing it to be adapted to different business structures, whether you are a single entity or part of a larger corporate group with multiple marketing authorizations.

Registration in the Article 57 Database

To be officially recognized, every PSMF in the EU is assigned a unique identification code. This code is generated by the EMA’s Eudravigilance system upon registration in the Article 57 database (also known as xEVMPD). Think of this as a license plate for your pharmacovigilance system. It provides a direct link between your authorized medicinal products and the master file that describes their safety oversight. This unique identifier must be kept up-to-date, ensuring regulators can always trace a product back to its corresponding safety system, which is critical during inspections and for routine oversight activities.

Ownership Flexibility and Global Adoption

The structure of a PSMF is surprisingly adaptable. A single Marketing Authorization Holder (MAH) can maintain several different PSMFs, perhaps for different product lines or regions. Conversely, multiple MAHs within the same parent company can share a single, centralized PSMF. This flexibility allows companies to design a system that best fits their operational reality. While the PSMF is an EU requirement, its framework has been adopted as a best practice in over 40 other countries. This global acceptance makes it a powerful tool for demonstrating a commitment to drug safety worldwide, helping you build a unified compliance strategy that satisfies multiple international authorities.

What Does a PSMF Actually Do?

At its core, the PSMF is designed to describe how your company, as a Marketing Authorisation Holder (MAH), monitors and ensures the safety of its medicines on the market. It’s a detailed guide that explains your entire drug safety system from top to bottom. The goal is to provide a transparent and thorough overview that proves you have a robust system in place for collecting, assessing, and acting on safety information. This document shows regulators that you are proactively managing the risks associated with your products and are fulfilling your legal and ethical obligations to protect public health.

Your Key to Regulatory Compliance

The PSMF is not just good practice; it’s a legal requirement for any company with medicines authorized in the European Union. Mandated by EU legislation, this file must be a permanent fixture in your regulatory compliance framework. It needs to be kept up-to-date at all times to reflect your current pharmacovigilance activities. More importantly, you must be able to provide it to national competent authorities for inspection within seven days of a request. This tight deadline means you can’t afford to let your PSMF become outdated. It must always be audit-ready, accurately detailing your global safety operations.

Where to Store Your PSMF and Who Needs Access

The location of your PSMF is strictly regulated. It must be physically located within the European Union or European Economic Area (EU/EEA). Typically, it’s housed either at the main site where your pharmacovigilance activities are performed or at the location where your Qualified Person for Pharmacovigilance (QPPV) operates. As the Marketing Authorisation Holder, your company is responsible for creating, maintaining, and registering the location of the PSMF with the regulatory authorities. This ensures that inspectors know exactly where to find it and can access it quickly when needed, making its physical placement a critical compliance point.

Why is the PSMF So Important?

Think of your Pharmacovigilance System Master File as more than just a regulatory requirement; it’s the backbone of your product safety strategy. A well-maintained PSMF demonstrates to authorities that you have a robust and reliable system for monitoring your products once they’re on the market. It’s your comprehensive proof that you’re not just meeting your legal obligations but are actively committed to consumer safety. This single source of truth provides a clear, auditable overview of your entire pharmacovigilance system, making inspections smoother and showing regulators you have everything under control. For any business in a regulated industry, from cosmetics to dietary supplements, the PSMF is a critical asset for building trust and ensuring long-term compliance.

The PSMF’s Role in Patient Safety

At its core, the PSMF is a commitment to public health. It serves as the official roadmap for your company’s entire pharmacovigilance system, detailing every process, person, and technology involved in monitoring product safety. This isn’t just about ticking a box for regulators; it’s about having a living framework that ensures you can effectively collect, assess, and act on adverse event data. By centralizing this information, the PSMF guarantees that your approach to safety monitoring is consistent, thorough, and always ready for inspection. It’s the document that proves your systems are designed to protect the people who use your products.

Meeting Regulatory Demands Worldwide

Operating in multiple markets means dealing with a complex web of different regulations. What’s required in the EU may differ from what the FDA expects. The PSMF helps you create a unified and coherent pharmacovigilance strategy that can satisfy various international authorities. It addresses the practical challenges companies face due to a lack of global legislative harmonisation by providing a single, comprehensive overview of your system. This allows you to manage your global safety operations more efficiently and demonstrate to any regulatory body that you have a solid, globally-consistent system in place, reducing redundancy and compliance risks.

A Prerequisite for New Medicine Applications

If you’re planning to bring a new medicine to market, your PSMF isn’t something you can put off until later. It’s a foundational document that must be complete and ready *before* you submit your application. This isn’t just a best practice; it’s a firm legal requirement for any company seeking authorization in the European Union. Regulatory bodies like the European Medicines Agency (EMA) can request your PSMF at any time, and you’ll have just seven days to provide it. Having a well-maintained file from the start shows regulators that your company is serious about patient safety and prepared for scrutiny, which helps make the entire application process smoother.

Strengthening Risk Management and Signal Detection

A strong PSMF is essential for proactive safety management. It ensures that all safety information for your products is accessible and transparent, which is fundamental for effective risk management and signal detection. By clearly outlining your processes for identifying potential safety issues, the PSMF shows that you have a system designed to catch problems early. This allows your team to respond to safety concerns quickly and decisively, protecting consumers and your brand’s reputation. It shifts your safety posture from reactive to proactive, giving you the tools to manage risks before they become major issues.

Understanding Rare Side Effects: The “Rule of 3’s”

One of the biggest challenges in pharmacovigilance is detecting side effects that are incredibly rare. Clinical trials, even large ones, may not have enough participants to catch an adverse event that only happens to one in ten thousand people. This is where a helpful statistical guideline known as the “Rule of 3’s” comes into play. It helps put study results into perspective. For example, if you conduct a study with 300 participants and none of them experience a particular side effect, you can’t conclude it doesn’t exist. The rule tells us you can only be 95% certain that the actual rate of that side effect in the general population is less than 1 in 100 (or 3 divided by 300). This highlights the statistical limitations of pre-market studies and underscores why ongoing, post-market safety monitoring is absolutely essential.

This statistical reality is precisely why your PSMF is so critical. Since clinical trials can’t possibly uncover every rare adverse event, your post-market surveillance system must be prepared to. The PSMF is the document that details exactly how your company will handle this responsibility. It outlines the procedures for collecting, analyzing, and acting on safety data from the real world, where millions of people might use your product. This makes the PSMF more than just a compliance document; it’s your active strategy for assessing the safety of your products over their entire lifecycle. It ensures you have a robust framework in place to detect those rare signals that pre-market studies are statistically unlikely to find, protecting both consumers and your company.

What Goes Inside a Pharmacovigilance System Master File?

Think of your Pharmacovigilance System Master File as the comprehensive blueprint for your product safety operations. It’s not just one document but a collection of detailed information that tells regulators exactly how you monitor and manage the safety of your products. Each section serves a specific purpose, and together, they create a complete picture of your commitment to pharmacovigilance. Let’s walk through the essential components you’ll need to include.

The Formal Structure: Main Body and Annexes

The PSMF isn’t just a single, massive document; it’s a logically organized file with two main components: the main body and the annexes. This structure is designed to provide a clear and accessible overview of your pharmacovigilance system. The main body tells the story of your safety operations—what you do and how you do it. The annexes provide the detailed evidence and documentation to back it all up. Think of it as a summary report with a full appendix of supporting data. Getting this structure right is the first step toward building a compliant and audit-ready PSMF that regulators can review efficiently.

The 7 Modules of the Main Body

The main body of the PSMF contains the core information about your company’s safety system. It’s divided into seven distinct sections, often called modules, that cover every critical aspect of your operations. These modules detail the role of the Qualified Person for Pharmacovigilance (QPPV), your organizational structure, how you collect and manage safety data, the computerized systems you use, and your standard operating procedures. It also includes information on how you measure your system’s performance and maintain quality control. This section gives inspectors a complete, high-level view of your entire pharmacovigilance framework.

The 9 Sections of the Annexes

While the main body provides the overview, the annexes deliver the specifics. These nine sections offer detailed, supporting information that corresponds to the modules in the main body. The annexes include logs of all your safety audits and inspections, a list of all your authorized medicinal products, details on your quality management system, and performance indicators. You’ll also find a log of any changes made to the PSMF itself, ensuring full transparency and traceability. The annexes are where the raw data and evidence live, proving that the systems described in the main body are functioning as intended.

Demonstrating Global Safety Data Availability

One of the most critical functions of the PSMF is to demonstrate that you have a handle on your product’s safety profile across the globe. If you market products in the EU, your PSMF must clearly show that all relevant safety information from every country where your product is sold is available to your QPPV. This isn’t just about having access to the data; it’s about proving you have a robust system to collect and centralize it effectively. This global oversight ensures you can detect safety signals and manage risks comprehensively, satisfying the stringent requirements of EU regulators.

Documenting Your Qualified Person for Pharmacovigilance (QPPV)

At the heart of your pharmacovigilance system is a dedicated expert, and your PSMF needs to introduce them properly. This section must clearly identify your Qualified Person for Pharmacovigilance (QPPV). You’ll need to provide their name, contact details, and a summary of their qualifications and responsibilities. This isn’t just a formality; it shows regulators that you have a competent, designated person overseeing your entire drug safety framework. The QPPV is ultimately accountable for ensuring the system functions correctly and complies with all legal requirements, making their role absolutely critical.

Outlining Your Pharmacovigilance System and Processes

This is where you lay out the operational details of your safety monitoring. The PSMF must provide a thorough summary of your pharmacovigilance system, explaining how your company handles every step of the process. This includes how you find, collect, analyze, and report adverse events and other safety-related information. You should describe the workflows, procedures, and methodologies you have in place. Essentially, this section acts as a high-level guide to your day-to-day safety operations, demonstrating a structured and reliable approach to managing product safety data from start to finish.

Integrating Quality Management and Training Records

A great system is only effective if your team knows how to use it. That’s why your PSMF must detail the training programs for all personnel involved in pharmacovigilance activities. This section should outline your training curriculum, frequency, and how you document it to ensure everyone is skilled and current on the latest regulations and internal procedures. It’s also where you describe your overarching quality management system, including procedures for audits, inspections, and corrective actions. This demonstrates to regulators that you’re committed to maintaining high standards through continuous improvement and staff competency.

Explaining Your Safety Database and Data Sources

Data is everything, and your PSMF needs to reflect that. This section must describe the computerized systems and databases you use to collect, process, and store pharmacovigilance data. You’ll need to explain the technical aspects in a clear way, covering details like the software used, data validation processes, and the security measures in place to protect sensitive information. The goal is to assure regulators that your data is accurate, reliable, and securely managed. This transparency builds confidence that your safety reporting is based on a solid and well-maintained technical foundation.

Assembling Your Annexes and Supporting Documents

The main body of the PSMF provides the overview, but the annexes are where you provide the proof. These appendices contain the specific, detailed information that supports the summaries in the core document. Common annexes include a list of all medicinal products covered by the PSMF, a log of all audits and inspections, and a record of any changes made to the PSMF itself (the change logbook). These supporting documents are vital for providing a complete and auditable record, allowing inspectors to easily find the evidence they need to verify your compliance.

Who Manages the PSMF?

Managing a Pharmacovigilance System Master File (PSMF) is a team sport. While one person has direct oversight, several key players are responsible for its creation, maintenance, and accuracy. The primary responsibility falls on the Marketing Authorization Holder (MAH), with operational management led by a Qualified Person for Pharmacovigilance (QPPV) and support from a wider team. Let’s break down who does what to keep your PSMF compliant and effective.

The MAH’s Core Responsibilities

The ultimate responsibility for the PSMF rests with the Marketing Authorization Holder, or MAH. This is the company that holds the license to market a medicinal product. If your company sells medicines in the European Economic Area (EEA), you are required to establish and maintain a PSMF. While you will delegate tasks to a specific person and team, the legal liability remains with the MAH. This means the company must ensure the system described in the PSMF is fully implemented and compliant with all regulatory requirements. Your PSMF is a direct reflection of your company’s commitment to patient safety, and regulators will hold the MAH accountable.

A Closer Look at the QPPV’s Duties

The Qualified Person for Pharmacovigilance (QPPV) is the lead supervisor for your drug safety operations. This individual is legally required to reside and work within the European Union and acts as the main contact for regulatory authorities. The QPPV has 24/7 responsibility for overseeing the entire pharmacovigilance system, ensuring all safety information is collected, evaluated, and reported correctly. The PSMF must clearly name the QPPV, outline their qualifications, and detail their responsibilities. A key part of their role is to have a complete overview of product safety profiles and emerging concerns, ensuring the information in the PSMF is always accurate.

Setting Clear Team Roles and Responsibilities

Beyond the MAH and QPPV, a successful pharmacovigilance system relies on a well-defined team. Your PSMF must act as a clear organizational chart, detailing the roles of everyone involved in safety monitoring. This includes staff responsible for case processing, signal detection, risk management, and quality assurance. The document should also describe how you manage any outsourced activities, such as work performed by contract research organizations (CROs) or other partners. Clearly defining these roles ensures there are no gaps in your safety processes and that everyone understands their duties. This detail is critical for smooth operations and for demonstrating control during a regulatory inspection.

Are You Facing These Common PSMF Challenges?

While the PSMF is a powerful tool for ensuring product safety and regulatory compliance, managing it isn’t always straightforward. It’s a dynamic, complex document that requires constant attention. Many companies, especially those expanding globally or managing diverse product lines, run into similar roadblocks. Understanding these common hurdles is the first step toward creating a more efficient and effective management strategy. From keeping documents current to integrating disparate data systems, each challenge presents a unique test for your pharmacovigilance team. Let’s walk through some of the most frequent issues you might face.

The Challenge of Keeping Documentation Current

One of the biggest challenges is treating the PSMF as a living document. It’s not a file you create once and store away; it needs to reflect the current state of your pharmacovigilance system. Regular updates are critical for compliance and effective risk management. However, with constantly evolving processes, personnel changes, and new product information, it’s easy for the PSMF to become outdated. An inaccurate PSMF can lead to inspection findings and, more importantly, can compromise your ability to monitor product safety effectively. Establishing a routine maintenance schedule and clear ownership for each section is key to keeping your documentation accurate and accessible when you need it most.

Managing a PSMF for Multiple Products

As your company grows, so does the complexity of your PSMF. Managing multiple product portfolios, especially across different countries, introduces a new layer of difficulty. The concept of the PSMF has been adopted and adapted outside of the EU, leading to variations in requirements. This creates significant challenges for the maintenance and management of your files. You may find yourself needing to maintain several versions of the PSMF to meet the specific demands of different regulatory bodies. Keeping track of these varying requirements for each product can quickly become overwhelming without a centralized and well-organized system in place.

Maintaining Compliance Across Different Regions

Handling the global regulatory landscape is a major hurdle. Pharmaceutical and life-science companies often face practical challenges because there is no single, harmonized PSMF standard across all jurisdictions. Different countries may interpret requirements differently, leading to inconsistencies that can create compliance risks and operational headaches. What passes muster in one region might not be sufficient in another. This forces companies to dedicate significant resources to tracking regulatory changes and adapting their PSMF accordingly. Without a clear strategy, you risk falling out of compliance in key markets, which can result in costly delays and penalties.

Dealing with Disconnected Data and Systems

Your PSMF is only as good as the data within it. A common struggle is effectively integrating data from various sources—such as safety databases, quality management systems, and clinical trial records—into one cohesive file. Many companies grapple with legacy systems or siloed departments, making it difficult to pull accurate, real-time information. Meeting complex pharmacovigilance compliance requirements and maintaining robust data integration is crucial for accurate reporting and signal detection. Without seamless integration, you risk inconsistencies and errors that can undermine the integrity of your entire pharmacovigilance system.

How to Master Your PSMF Management

Managing a Pharmacovigilance System Master File can feel like a huge task, but it doesn’t have to be a source of constant stress. With the right strategies, you can turn your PSMF from a compliance burden into a streamlined, audit-ready asset. It’s all about being proactive rather than reactive. By establishing clear processes for updates, documentation, and reviews, you can maintain control and ensure your system is always accurate and accessible. Let’s walk through four key practices that will help you master your PSMF management and stay ahead of regulatory expectations. These steps will help you build a robust framework that not only meets requirements but also supports your overall quality management system.

Knowing When to Update Your PSMF

Your PSMF is a living document, not a one-and-done project. Think of it as a real-time reflection of your pharmacovigilance system. According to industry experts, “Parts of the PSMF, especially the extra sections (annexes), must always be kept up-to-date.” This means you need a solid process for identifying when changes are necessary. Key triggers for an update include changes to your QPPV, significant modifications to your safety database, the addition of new products, or findings from recent audits. Establishing a regular review cycle—say, quarterly or semi-annually—is also a great practice to catch any smaller changes that might otherwise be missed. The goal is to ensure your PSMF accurately represents your current operations at all times, leaving no room for outdated information when an inspector calls.

Implementing a Structured Update Process

Knowing when to update is half the battle; how you update is what makes your system truly solid. The key is to formalize the process. Move away from informal reminders and create a clear standard operating procedure (SOP) that details every step of a PSMF update. This procedure should assign clear ownership for each section—for instance, the clinical team is responsible for product safety profiles, while HR handles personnel changes. By defining who is accountable for what, you ensure that critical information doesn’t get lost. This structured approach guarantees that every change is documented, reviewed, and implemented consistently, keeping your PSMF accurate and ready for inspection at all times.

Putting Strong Documentation Controls in Place

Every change to your PSMF, no matter how small, needs a clear and traceable record. This is where strong documentation controls become non-negotiable. As compliance specialists note, “All changes must be recorded in a logbook (Annex I) and approved by the QPPV.” This creates an essential audit trail that demonstrates accountability and oversight. Your change control process should clearly define who can request a change, who must review it, and who has the final authority for approval. Using a standardized change log helps maintain consistency and ensures that every modification is justified, documented, and signed off on, protecting your company and proving your commitment to good documentation practices.

Finding the Right Pharmacovigilance System Master File Solutions

Manually managing a PSMF with spreadsheets and scattered documents is a recipe for errors and inefficiency. Embracing technology can transform your process. The advice from industry leaders is to “Use automated systems, especially cloud-based ones, to manage and update the PSMF.” A dedicated, cloud-based platform provides a single source of truth, making it easier for your team to collaborate, track changes, and manage versions. These systems can also automate reminders for reviews and simplify the process of compiling information for auditors. This shift not only reduces the risk of human error but also frees up your team’s time to focus on more strategic pharmacovigilance activities instead of administrative tasks. It’s a smart move that makes your entire system more resilient and ready for inspection.

Examples of PSMF Software

Choosing the right software depends entirely on your company’s size, complexity, and budget. For large global corporations managing a high volume of cases, a system like Oracle Argus Safety is often the standard. On the other hand, a more modern, cloud-based solution like Veeva Vault Safety is a great fit for companies that want all their regulatory tools to connect seamlessly. For medium-sized businesses or research groups, options like ArisGlobal LifeSphere Safety use AI to automate tasks, while PV Works offers flexible solutions. If you’re a smaller company, startup, or consulting firm, simpler tools like BaseCon or MyPV provide user-friendly and cost-effective ways to handle case processing without the complexity of an enterprise-level system.

Key Software Features to Look For

When you’re evaluating different platforms, there are a few core features that can make a huge difference. Look for a system with strong automated reporting, which handles the entire process of submitting adverse event reports to the correct authorities. Another critical feature is signal detection; many modern tools use AI to help you spot potential safety issues early on. The software must also be built to follow global rules, ensuring compliance with standards from both the EU and the FDA. Finally, make sure it supports standardized data entry and integrates with major drug dictionaries. This ensures all your safety information is consistent and accurately coded, no matter where it comes from.

Practical Considerations: Cost and Implementation

Beyond features, you need to think about the practical side of things. Software costs can vary widely, with models ranging from a monthly or yearly subscription for cloud-based tools to a large, one-time fee for an on-premise license. Don’t forget to factor in the setup process. A massive system like Oracle Argus can take six to twelve months to fully implement, while cloud-based platforms are typically much faster to get up and running. You should also ask about ongoing maintenance. A good software solution should include regular updates to keep up with changing regulations, but you’ll want to confirm whether those are included in your subscription or require additional work from your team.

Stay Audit-Ready with Regular Reviews

You should never be scrambling to get your PSMF ready for an inspection. The best approach is to always be prepared. This means you must “Always keep the PSMF complete, consistent, and easy to access so it’s ready for any regulatory inspections.” The most effective way to do this is by conducting regular internal reviews or mock audits. These dress rehearsals help you identify gaps, inconsistencies, or areas of weakness before a real inspector does. Schedule periodic checks to test your system’s readiness and ensure all annexes are current and all links are functional. This proactive stance not only minimizes audit-day anxiety but also reinforces a culture of continuous improvement within your pharmacovigilance system.

Frequently Asked Questions

Is a PSMF only required for large pharmaceutical companies? Not at all. The requirement for a PSMF is tied to where you market your products, not the size of your company. If you are the Marketing Authorisation Holder (MAH) for any medicinal product sold within the European Union or European Economic Area, you are legally required to have a complete and up-to-date PSMF, regardless of whether you’re a startup or a global corporation.

How often should I be updating my PSMF? There isn’t a strict calendar schedule, because the PSMF should be treated as a real-time reflection of your safety system. You should update it whenever a significant change occurs. This could be a change in your QPPV, an update to your safety database, the findings from an audit, or even a major shift in your organizational structure. It’s best to have a process in place to review it regularly, but the key is to make updates as they happen.

What’s the biggest mistake companies make with their PSMF? The most common pitfall is treating the PSMF as a one-time project. Companies will invest a lot of effort to create it initially but then fail to maintain it. This “set it and forget it” approach is a direct path to non-compliance. An outdated PSMF is not only a red flag for inspectors but also a sign that your safety oversight may have critical gaps.

Do I need a PSMF if my company isn’t based in the EU? Yes, you likely do. The obligation is linked to where your products are authorized for sale. If your company, regardless of its headquarters’ location, holds a marketing authorization for a product in the EU/EEA, you must maintain a PSMF. Furthermore, the file itself must be physically located at a site within the EU/EEA, typically where your QPPV operates.

Can I hire a consultant to manage my PSMF for me? Absolutely. It’s very common to outsource the day-to-day management and maintenance of the PSMF to a specialized firm or consultant. However, it’s crucial to remember that while you can delegate the tasks, you cannot delegate the ultimate responsibility. As the Marketing Authorisation Holder, your company remains legally accountable for the accuracy and compliance of the PSMF.