QPPV Responsibilities

The Qualified Person Responsible for Pharmacovigilance (QPPV) is responsible for oversight of the marketing authorisation holder's pharmacovigilance system and acts as the central point of pharmacovigilance responsibility within the organisation.

Table of contents - Overview - Mapping: QPPV responsibilities → evidence, GVP modules & timelines - Oversight of the pharmacovigilance system - Regulatory context - Practical implementation and governance - Inspection relevance - Pharmacovigilance System Master File (PSMF) - PSMF — actionable, inspection‑ready checklist - Practical implementation details and governance - Inspection relevance - Inspection readiness - Pre‑inspection governance and ownership - Pre‑packaged inspection artefacts - Operational readiness and during inspection controls - Post‑inspection corrective actions and governance - Awareness of product safety issues - Operational mechanisms - Regulatory and inspection context - Vendor and partner oversight - Key evidence and risk‑based approach - Practical controls and inspection relevance - Governance and escalation - Structures, charters and reporting - Inspection perspective and expected evidence - Interactions with regulatory authorities - Evidence, timelines and record keeping - Practical perspective and implementation roadmap - Last reviewed: June 2026 - Related Guides

Overview

The QPPV role extends beyond operational pharmacovigilance activities. The position is primarily an oversight and governance role focused on ensuring that the pharmacovigilance system operates effectively, remains compliant and is capable of meeting regulatory expectations.

While day‑to‑day activities may be delegated to specialists, vendors or service providers, responsibility for oversight of the pharmacovigilance system remains with the QPPV. Effective performance requires clear documentation, active governance, demonstrable oversight of delegated activities, and continuous inspection readiness.

Mapping: QPPV responsibilities → evidence, GVP modules & timelines

The table below provides a concise cross‑walk to help QPPVs prioritise evidence collection, align to GVP, and meet inspection expectations. Timelines are a combination of statutory reporting requirements (where applicable), typical regulatory expectations and industry practice used to demonstrate inspection readiness. Where statutory timelines apply they are noted explicitly; other timelines are shown as typical expected timeframes for preparation, response and governance.

Notes on use: Use this table as a prioritisation and evidence‑linking tool. For each responsibility create a folder or PSMF hyperlink that bundles the identified evidence so inspectors can rapidly verify claims.

Oversight of the Pharmacovigilance System

One of the core responsibilities of the QPPV is to maintain oversight of the pharmacovigilance system. This includes maintaining awareness of the structure, processes, responsibilities and controls that support pharmacovigilance activities throughout the organisation.

The QPPV should be able to understand how safety information is collected, evaluated, escalated and reported within the pharmacovigilance system and be able to demonstrate that these processes are subject to a documented quality system.

Regulatory context - The requirement for a functioning pharmacovigilance system and a QPPV is established in Directive 2001/83/EC (as amended) and Regulation (EC) No 726/2004. Good Pharmacovigilance Practice (GVP) Module I sets the overall expectations for PV systems and their quality management. - The QPPV must ensure the PV system operates in accordance with applicable GVP Modules and national/regional legislation where products are authorised.

Practical implementation and governance - Maintain a PV quality management plan that maps organisational controls (SOPs, templates, KPIs) to regulatory requirements and PSMF sections. - Use a RACI matrix to crystalise responsibilities for key processes (case intake, triage, signal detection, RMP updates, aggregate reporting, vendor oversight). - Implement PV performance dashboards that show timeliness, completeness, database reconciliation rates, audit findings and CAPA status; distribute to PV governance committee and Senior Management monthly or quarterly depending on risk profile. - Ensure the QPPV or an authorised deputy signs off key changes (e.g., new systems, MA transfers, major outsourcing) and that approvals are captured in change control records.

Inspection relevance - Inspectors evaluate whether the QPPV has effective oversight, whether delegated tasks are controlled, and whether governance arrangements ensure patient safety and regulatory compliance. Evidence of oversight and escalation is frequently requested during PV inspections.

Pharmacovigilance System Master File (PSMF)

The QPPV is expected to maintain awareness of the content, location and operation of the PSMF. The PSMF provides a detailed description of the pharmacovigilance system and is a key document reviewed during inspections and regulatory assessments.

Although individual sections may be maintained by different functions, the QPPV should remain familiar with the overall content and status of the document.

PSMF — actionable, inspection‑ready checklist (items every QPPV must ensure exist, are current and accessible) 1. Master PSMF file and index - Evidence: Signed PSMF title page with version, effective date, and QPPV attestation; automated index mapping to GVP Module II section headings. 2. Table of contents aligned to GVP Module II - Evidence: Index demonstrates mapping of each PSMF section to GVP Module II clauses and internal SOPs. 3. PSMF version history and change control - Evidence: Version history log, change control records and rationale for changes. 4. QPPV details and contact information - Evidence: QPPV CV, legally binding appointment letter, contact details and evidence of registration/notification to competent authorities where required. 5. Organisation chart for PV (global and local) - Evidence: Organograms showing reporting lines and a RACI for PV tasks. 6. Description of the PV system and quality system - Evidence: PV quality management plan, SOP list and process maps. 7. List of authorised products and countries of authorisation - Evidence: Product list with MA numbers and safety information links. 8. Delegation of tasks and third‑party agreements - Evidence: Signed contracts/SLA/CRO agreements, delegation logs, oversight plans and vendor performance records. 9. Safety database(s) and data flow diagrams - Evidence: Data flow diagrams, validation reports, access control lists and UAT summaries. 10. ICSR processing and reporting processes - Evidence: SOPs, example redacted ICSRs, submission receipts and timeliness KPI reports. 11. Signal management and safety surveillance - Evidence: SOPs, signal logs and recent signal minutes. 12. Risk management system and RMPs - Evidence: RMPs, implementation plans and evaluation reports. 13. Aggregate reporting - Evidence: PSUR/PBRER list and submission history. 14. PASS - Evidence: Protocols, progress and final reports. 15. Pharmacovigilance audits and inspections - Evidence: Audit schedule, reports, inspection history and CAPA tracker. 16. Training and competence records - Evidence: Training matrix and completion records for QPPV and PV staff. 17. Business continuity and disaster recovery - Evidence: BCP for PV, test results and alternative arrangements for critical functions. 18. IT, validation and data integrity evidence - Evidence: IQ/OQ/PQ, audit trails and backup logs. 19. Local (national) requirements and specific files - Evidence: Country‑specific requirements mapping and local annexes. 20. Attachments and working documents repository - Evidence: SOPs, templates, escalation matrices and sample communications.

Practical implementation details - Maintain the PSMF as a living document in a controlled electronic repository with source documents and a published "inspection" PDF. Both should be traceable via change log for inspectors. - Implement a quarterly PSMF review owned by the QPPV or designated deputy, with documented sign‑off in an approvals log. For critical items (QPPV change, loss of key vendor, major system outage) update the PSMF immediately, ideally within 7–30 days. - Create a PSMF evidence pack: a curated bundle of the most commonly requested documents (QPPV CV/appointment, PSMF title page, SOP list, latest audit/inspection reports, selected ICSRs) prepared for rapid export. - Use a hyperlinked index that maps each PSMF section to supporting evidence artifacts and highlights currency status (current/superseded/archive). - For organisations with multiple MAHs or affiliates, maintain a master PSMF and local annexes; clearly indicate product and territory coverage.

Governance - The QPPV should chair or co‑chair periodic PV governance meetings that include review of PSMF status, open CAPAs, audit findings and inspection readiness. Meeting minutes should capture actions, owners and target completion dates. - Senior Management should receive regular PV system health reports referencing PSMF status and critical risks. Ensure that the PV governance charter defines decision rights for allocating resources to remediate PV risks.

Inspection relevance - Inspectors expect the PSMF to be accurate, complete and demonstrably linked to the operational PV system. In practice the PSMF is often the first document requested and it frames subsequent document requests; a well indexed PSMF accelerates inspection conduct and reduces follow‑up.

Inspection Readiness

Regulatory authorities may inspect the pharmacovigilance system to evaluate compliance with applicable requirements. QPPVs are frequently involved in inspection preparation, inspection management, responses to observations and oversight of corrective and preventive actions.

Inspection readiness is an organisational capability: systems, people, processes and evidence must be continuously inspection‑ready.

Regulatory context - GVP Module III provides guidance on pharmacovigilance inspections and expectations of competent authorities. Module IV addresses PV audits. The legal basis for inspections lies in Directive 2001/83/EC and Regulation (EC) No 726/2004.

Pre‑inspection governance and ownership 1. Inspection owner and team - Evidence: Named inspection owner (QPPV or delegate), inspection team roster and subject matter expert contact list. - Implementation: Maintain an on‑call inspection team rota; validate remote working and secure document sharing tools. 2. Inspection readiness program and schedule - Evidence: Inspection readiness plan, mock inspection calendar and readiness trackers. - Governance: Regular updates to PV governance committee and senior management; use a log to track regulator‑specific themes and historical requests.

Pre‑packaged inspection artefacts (ready‑to‑issue) 3. Pre‑packaged inspection evidence binder (electronic and/or printed) - Contents: Inspection version of PSMF, QPPV CV and appointment, organograms, SOP list, recent audit/inspection reports, redacted ICSRs with submission receipts, signal minutes, RMPs, PSURs/PBRERs, vendor contracts, validation reports, BCP evidence, training records. - Practical: Curate the binder periodically and refresh it immediately after major changes.

Operational readiness 4. Interview preparation and role briefs - Evidence: Briefing packs for interviewees, approved Q&A, mock interview scripts. - Implementation: Role play exercises, maintain repository of "known answers" aligned to SOPs and PSMF. 5. Systems and access - Evidence: Read‑only access set up for inspectors where permitted, validated remote meeting platforms, secure file transfer methods. - Security: Implement redaction protocols and logs for personal data. 6. Mock inspections and drills - Evidence: Reports from mock inspections, CAPA plans and closure verification. - Frequency: At least annually for core PV functions; more frequently after major changes or inspection findings.

During inspection: conduct and controls 7. Inspection management and logistics - Evidence: Opening and closing meeting minutes, daily briefings and consolidated document request log. - Implementation: Designate a single inspection liaison to control document flow and scheduling. 8. Real‑time evidence retrieval - Evidence: Document request tracking tool, screenshots of live systems where permitted, redaction logs. - Inspection relevance: Timely, controlled responses reduce scope creep and follow‑up inspections. 9. Interview records and witness statements - Evidence: Interview notes and Q&A logs showing consistency between documentary evidence and verbal responses.

Post‑inspection: corrective actions and closure 10. Observation management and CAPA - Evidence: Written responses to observations, root cause analyses, CAPA plans with owners and timelines, implementation and effectiveness verification evidence. - GVP reference: Module IV expectations for CAPA documentation and follow‑up. 11. Management reporting and escalation - Evidence: Senior management briefings, regulatory submissions (if applicable) and governance minutes referencing observation closure. - Implementation: Link CAPAs to PSMF updates and PV risk register. 12. Lessons learnt and continuous improvement - Evidence: Updated SOPs, training sessions, improved governance and adjusted mock inspection schedules.

Inspection readiness: practical implementation details - Maintain a “hot folder” of top‑requested documents that is refresh‑ready and automatically updated. - Use document control systems that can assemble inspection packs with embedded metadata and redaction capabilities. - Maintain an inspection log capturing historical requests and authority behaviours to tailor preparedness for specific regulators. - For cross‑jurisdiction operations, maintain a jurisdictional mapping showing inspectorates, local requirements and responsible MAHs. - Plan for QPPV absence: appoint a documented, authorised deputy with delegated authority for inspections and emergency regulatory interactions.

Inspection relevance and common findings - Inspectors commonly focus on timeliness and completeness of ICSR reporting, accuracy of the PSMF, evidence of vendor oversight, audit programmes, CAPA implementation and validated systems controls. - Common findings include outdated PSMF sections, unsigned/obsolete SOPs, insufficient vendor oversight evidence, incomplete CAPA evidence and inadequate BCP for PV systems.

Awareness of Product Safety Issues

QPPVs must maintain ongoing awareness of significant safety concerns affecting products under their remit. This includes emerging signals, important identified risks, ongoing regulatory commitments and compliance issues.

Operational mechanisms - Establish and chair a safety review forum (monthly or frequency determined by product risk) that covers new ICSRs, aggregate review highlights, signal updates and RMP commitments. - Maintain safety dashboards showing trends by product, seriousness, outcome and country. Link dashboards to PSMF and RMP evidence. - Implement a documented escalation process that defines thresholds for automatic escalation to the QPPV and PV governance committee (e.g., sudden increase in serious ADR reports, signals with potential broad public health impact).

Regulatory and inspection context - The QPPV should be able to present documented evidence of how safety issues are detected, triaged, assessed and escalated. Inspectors will look for traceability from case intake through signal assessment and any regulatory actions taken.

Vendor and Partner Oversight

Delegation of activities does not remove the need for appropriate oversight. QPPVs are expected to understand how outsourced activities are governed, monitored and controlled.

Key evidence and inspection focus - Maintain an up‑to‑date delegation log mapping delegated tasks to contract clauses, SOPs and oversight actions. - Evidence: Master service agreements, statements of work, qualification and acceptance records, periodic vendor performance reviews, meeting minutes and audit reports. - Inspectors seek to understand retained responsibilities and mechanisms assuring vendor performance, particularly for case processing, signal detection, safety database hosting and PASS execution.

Practical controls and governance - Risk‑based vendor governance: classify vendors by criticality (e.g., safety database host, case processor = high) and set oversight activities accordingly (audit frequency, KPIs, SLA penalties). - Establish vendor oversight plans: defined metrics (timeliness, quality), scheduled review meetings, documented corrective actions and demonstration of CAPA effectiveness. - Contractual clarity: ensure contracts specify regulatory reporting responsibilities, data ownership, audits rights, business continuity obligations and investigator timelines. - Onboarding and qualification: complete vendor qualification and risk assessment before start; retain qualification evidence in PSMF evidence pack. - Periodic audit: high‑criticality vendors audited on a schedule (annually or bi‑annually); low‑criticality vendors reviewed per risk assessment.

Inspection relevance - Inspectors will examine whether the MAH retains ultimate responsibility and whether oversight activities are proportionate and demonstrable. Lack of supplier audits or evidence of oversight is a common inspection observation.

Governance and Escalation

An important aspect of the role involves ensuring that significant pharmacovigilance issues are appropriately escalated and resolved within the organisation.

Structures, charters and reporting - Maintain a PV governance charter that defines remit, membership, decision rights, meeting frequency and escalation paths. The charter should also define the thresholds for escalation to executive management and the board. - Minute governance meetings: minutes should show decisions, actions, owners and target dates. Link actions to the CAPA tracker and PSMF updates. - Senior management reporting: provide concise PV risk dashboards and an annual PV system health report summarising PSMF status, audit findings, inspection outcomes and unresolved risks.

Inspection perspective and expected evidence - Inspectors expect to see documented escalation routes, evidence that significant risks were escalated and resources allocated for remediation. Evidence can include governance minutes, resource reallocation records and follow‑up status reports.

Interactions with Regulatory Authorities

The QPPV serves as an essential pharmacovigilance contact point for regulatory authorities. Interactions may include inspections, requests for information, regulatory commitments, safety communications or technical discussions.

Evidence, timelines and record keeping - Maintain a central repository for all regulatory correspondence and meetings related to pharmacovigilance. Evidence should include letters, emails, minutes, and follow‑up actions mapped to products or system issues. - Typical regulatory expectations: acknowledge formal regulatory requests promptly (within 2 business days), provide initial response or plan within 10–30 days and submit detailed responses/CAPA plans per authority timelines. - For inspection observations requiring regulatory notification, ensure the regulatory correspondence is cross‑referenced to the CAPA tracker and governance minutes.

Inspection relevance - Inspectors review the completeness and timeliness of regulatory interactions and whether commitments were met. Failure to document commitments or to provide evidence of completed actions is a common deficiency.

Practical Perspective and Implementation Roadmap

QPPVs should implement a pragmatic roadmap to make oversight tangible and demonstrable:

1. Baseline and prioritise
2. Complete a gap analysis against the mapping table above. Prioritise critical evidence (PSMF, QPPV appointment, ICSR timeliness reports, validated safety database).
3. Build an evidence architecture
4. Create an indexed electronic PSMF with a linked evidence pack and a "hot folder" of top‑requested documents for inspections.
5. Define governance cadence
6. Establish PV governance committee meetings (quarterly), a safety review forum (monthly), and an inspection readiness working group with clear owners.
7. Implement controls and monitoring
8. Deploy KPIs for ICSR timeliness, completeness, reconciliation and vendor performance. Report KPIs monthly to governance.
9. Test readiness and close gaps
10. Conduct mock inspections annually and follow up CAPAs with documented effectiveness checks.
11. Maintain continuity
12. Document deputy arrangements, ensure remote access to critical systems and test business continuity arrangements for PV.

Regulatory context - The QPPV role requires not only technical knowledge of pharmacovigilance but also an ability to operate within legal and regulatory frameworks across territories. Demonstrable governance and evidence trails are essential to satisfy competent authorities.

Inspection relevance - Demonstrable linkage between governance, documented controls and operational outputs (timeliness metrics, CAPA effectiveness, PSMF currency) forms the foundation of inspection readiness and successful regulatory interactions.

Practical examples of timelines and evidence flows (typical)

• ICSR expedited reporting: collect and triage within 24–72 hours of receipt; initial regulatory submission within statutory timelines (7 calendar days for life‑threatening/fatal; 15 calendar days for other serious cases); maintain evidence of submission (EV receipt) and database reconciliation monthly.
• PSMF updates: immediate update for critical changes (within 7–30 days); full PSMF review quarterly with documented sign‑off.
• Audit follow‑up: CAPA plan within 30 days of audit reporting; implementation and effectiveness verification within 90–180 days depending on severity.
• Inspection responses: acknowledge within 2 business days; provide a CAPA plan within 30 days; implement per plan with evidence of verification.

Practical perspective

Experienced QPPVs typically spend less time performing operational processing and more time focusing on oversight, governance, quality, inspection readiness and organisational risk management. The role requires both pharmacovigilance expertise and the ability to maintain visibility across complex processes involving multiple departments, vendors and stakeholders.

QPPVs should therefore lean on robust process mapping, clear delegation and proportional oversight — documenting both control design (what should happen) and control operation (evidence it did happen). Demonstrable links between the PSMF, SOPs, KPIs, audits and governance minutes form a coherent narrative inspectors expect to see.

Last reviewed: June 2026

Related Guides

• What is a QPPV?
• How to Become a QPPV