QPPV & the Pharmacovigilance System Master File
The EU pharmacovigilance framework rests on two structural anchors that make an abstract "safety system" concrete and inspectable: a **Qualified Person Responsible for Pharmacovigilance (QPPV)** — a named individual who is personally accountable for the whole system — and a **Pharmacovigilance System Master File (PSMF)** — a single maintained document that describes it. Together they answer the two questions a regulator asks first: *who is responsible?* and *how does the system actually work?* This page explains what each is, why accountability can be delegated in tasks but never in responsibility, and how the PSMF functions as the map an inspection reads. It sits alongside the [ICSR](/topics/icsr-expedited-reporting) and [signal management](/topics/signal-management) explainers, which cover the processes the QPPV is accountable for; the EU good-pharmacovigilance-practice modules define the requirements.
What an explainer is not
A topic explainer is SPEQ’s synthesis of what a practice involves, cited to the standards that govern it. It does not reproduce their text, and it does not determine which of them apply to your product or process.
[ POSITION IN THE FRAMEWORK ]
7 DIMENSIONS · 17 LINKSEU pharmacovigilance rests on a named accountable person, the QPPV, and a single living map, the PSMF: tasks delegate but responsibility does not, and a stale PSMF means a company cannot state how its own safety system works.
06 · QUALITY MATURITY — QPPV & THE PHARMACOVIGILANCE SYSTEM MASTER FILE, REACTIVE TO ADAPTIVE
The QPPV is a name on a form with no real oversight; the PSMF describes an idealised or historical system, its logbook untended.
A QPPV is appointed and a PSMF exists to the required structure, but delegation to affiliates and vendors runs with little visibility back to them.
The QPPV has genuine, documented oversight of all safety-data sources; the PSMF reflects the live system with a maintained change logbook and annexes.
PV agreements, system performance, and delegated-activity assurance are actively tracked; the PSMF is kept current as the system changes, CAPA visible.
The empowered QPPV steers the system on real performance data; the PSMF is a working map any inspection reads as an accurate description of the system.
SPEQ’s shared five-stage progression, labelled synthesis — not the FDA QMM rating scale. Where does your organization sit? Score your quality system →
07 · REGULATORY & EVIDENCE
GOVERNING STANDARDS · 1
Derived from the 1 standard SPEQ maps to this subject, across 1 regulatory body: EMA.
RECORDS & OBJECTIVE EVIDENCE
- QPPV appointment and their notification to the authorities and EudraVigilance
- A PSMF covering the QPPV, structure, data sources, systems, processes, and annexes
- The PSMF change logbook tracking modifications to the system
- Pharmacovigilance agreements defining delegated tasks and safety-information flow
- Evidence of QPPV oversight of delegated activities and system performance
COMMON INSPECTION FINDINGS
- A figurehead QPPV without oversight of or authority over the system
- A PSMF describing an idealised or historical rather than the live system
- The PSMF logbook not tracking changes to the system
- Delegation to vendors or affiliates with no reliable line back to the QPPV
- An out-of-date organisational chart or databases listed in the PSMF
The QPPV: pharmacovigilance built around a person
A defining feature of the EU system is that it names a *person*, not just a function. The marketing-authorisation holder must have a QPPV who resides and operates in the EU/EEA and is personally responsible for the establishment and maintenance of the pharmacovigilance system — with sufficient authority to influence its performance, permanent availability, and their identity notified to the authorities and EudraVigilance. The point of naming an individual is accountability that cannot dissolve into an organisation chart: there is always a specific human answerable for whether the system detects and acts on safety signals.
This is why the QPPV must have genuine **oversight** of the whole system rather than a title on a document. A QPPV who cannot see across the sources of safety data, the case-processing operation, the signal-management activity, and the risk-management commitments — or who lacks the authority to change them — is a figurehead, and "figurehead QPPV" is a recognised inspection finding. Many companies also appoint a local/national contact person for pharmacovigilance in individual member states, but that role supports, and does not replace, the single accountable QPPV.
Delegation of tasks, not of responsibility
The QPPV cannot personally perform every pharmacovigilance activity, and the framework does not expect it — tasks are routinely delegated to teams, affiliates, and vendors. What cannot be delegated is the *responsibility*: the QPPV remains accountable for the system as a whole regardless of who performs the work. This is the same principle that governs outsourcing everywhere in GxP, sharpened to a single named person — you can hand off the doing, never the answerability.
Making that real requires that delegation be documented and overseen, not assumed. Where activities are performed by third parties or affiliates, the tasks, the responsibilities, and the flow of safety information must be defined (typically in pharmacovigilance agreements), and the QPPV must have oversight sufficient to be assured they are actually done. The failure mode is delegation without visibility — a case-processing vendor or an affiliate handling local reports with no reliable line back to the QPPV — which leaves the accountable person accountable for a system they cannot see.
The PSMF: the single map of the system
The Pharmacovigilance System Master File is the one document that describes the pharmacovigilance system the QPPV is responsible for — a single, maintained, accurate description that a company uses to run its system and a regulator uses to understand and inspect it. Its structure is defined: it covers the QPPV and their responsibilities, the organisational structure, the sources of safety data, the computerised systems and databases used, the pharmacovigilance processes, the system’s performance and quality system, and a set of annexes (including a logbook of changes). The PSMF is meant to reflect the system *as it currently is*, which is the property that makes it useful and the property most often found lacking.
The characteristic PSMF finding is exactly that gap: a master file that describes an idealised or historical system rather than the live one — an out-of-date organisational chart, databases no longer used, processes since changed, or a logbook that has not tracked the changes. Because the PSMF is the reference an inspection works from, a stale PSMF is not merely a documentation slip; it means the company cannot accurately state how its own safety system works, which undermines confidence in everything the system produces. Keeping it current — with change history and, where relevant, CAPA visible — is the discipline that turns the PSMF from a filed document into a working map.
Why a person and a map, together
The QPPV and the PSMF are deliberately complementary: one supplies accountability, the other supplies transparency, and neither works alone. A named accountable person without an accurate description of the system has responsibility but no reliable instrument to exercise or demonstrate it; a detailed master file with no single accountable owner describes a system nobody is answerable for. The EU framework pairs them so that responsibility and the description of what one is responsible for stay bound together.
For practitioners the practical reading is that these are not paperwork obligations to satisfy once but the two things an inspection tests hardest — is there a real, empowered, informed QPPV, and does the PSMF truthfully describe the running system? A pharmacovigilance system can have competent case processing and signal detection and still fail inspection on these structural anchors, because they are what make the rest verifiable. They are the frame that holds the safety processes accountable.
FREQUENTLY ASKED
What is a QPPV?
The Qualified Person Responsible for Pharmacovigilance — a named individual, residing and operating in the EU/EEA, personally responsible for establishing and maintaining a marketing-authorisation holder’s pharmacovigilance system. The QPPV must have sufficient authority to influence the system, be permanently available, and be notified to the authorities and EudraVigilance. Naming a person creates accountability that cannot dissolve into an organisation chart.
Can the QPPV delegate their responsibilities?
They can delegate tasks but not responsibility. Pharmacovigilance activities are routinely performed by teams, affiliates, and vendors, but the QPPV remains accountable for the system as a whole. Delegation must be documented (typically in pharmacovigilance agreements) and genuinely overseen — delegation without visibility, where the QPPV cannot see whether delegated work is actually done, is a recognised failure mode.
What is the Pharmacovigilance System Master File (PSMF)?
A single, maintained document describing the pharmacovigilance system: the QPPV and their responsibilities, organisational structure, sources of safety data, computerised systems, pharmacovigilance processes, system performance and quality system, and annexes including a change logbook. It is what a company uses to run its system and a regulator uses to inspect it, so it must reflect the system as it currently is.
Why is an out-of-date PSMF a serious problem?
Because the PSMF is the reference an inspection works from, a stale master file — an outdated org chart, databases no longer used, processes since changed — means the company cannot accurately state how its own safety system works. That undermines confidence in everything the system produces, which is why a PSMF describing an idealised or historical rather than live system is a characteristic pharmacovigilance finding.