Inspection Hosting for QPPVs

Hosting a pharmacovigilance inspection is not primarily a logistical exercise. It is a controlled demonstration of how the pharmacovigilance system operates, how evidence can be retrieved, how deficiencies and risks are understood, and how the qualified person responsible for pharmacovigilance (QPPV) exercises system-level oversight.

The QPPV is a key regulatory contact point for pharmacovigilance inspections, but that does not mean the QPPV must personally coordinate every document request, answer every technical question or own every operational process. A well-run inspection distinguishes QPPV oversight from inspection operations while ensuring that the two remain connected.

Regulatory Framework and the QPPV's Role

The legal basis for pharmacovigilance inspections arises from EU pharmaceutical legislation, including Directive 2001/83/EC and Regulation (EC) No 726/2004. Good Pharmacovigilance Practices (GVP) Module III — Pharmacovigilance inspections describes how inspections may be announced or unannounced, routine or for-cause, system- or product-related, and on-site or remote.

GVP Module I describes the QPPV as the pharmacovigilance contact point for competent authorities and for pharmacovigilance inspections. It also requires the QPPV to maintain oversight of the functioning of the pharmacovigilance system, including its quality system.

These responsibilities need to be interpreted correctly. The QPPV should be able to explain the system, its significant risks, key controls, important deviations, relevant audit and CAPA history, major outsourced activities and the mechanisms through which important information reaches the QPPV. The QPPV does not need to perform every operational activity personally.

What inspectors may reasonably expect from the QPPV

An inspector may seek to establish whether the QPPV:

• understands the structure and scope of the pharmacovigilance system;
• has access to information necessary for oversight;
• is aware of significant compliance and safety issues;
• can explain how important issues are escalated;
• understands the status of significant audits, CAPAs and system changes;
• has appropriate visibility of outsourced pharmacovigilance activities;
• can obtain relevant evidence promptly; and
• can demonstrate that oversight is active rather than nominal.

The practical consequence is that inspection hosting should be organised around evidence, access, understanding and control.

Inspection Hosting Is a Team Activity

An inspection is most effective when operational responsibilities are separated clearly.

These titles are not prescribed by EU law or GVP. They are recommended operational roles that help prevent confusion, duplicated work and inconsistent communication.

Continuous Readiness Before Notification

The most reliable inspection preparation occurs before an inspection is announced. Continuous readiness means the pharmacovigilance system is already capable of demonstrating what it says it does.

For the QPPV, this requires particular visibility of:

• the current PSMF and its major changes;
• significant compliance metrics and trends;
• major or overdue CAPAs;
• important audit outcomes;
• significant vendor or affiliate issues;
• relevant computerised-system changes and failures;
• emerging or important safety concerns;
• important regulatory commitments; and
• known weaknesses in the pharmacovigilance system.

This is more useful than maintaining a large static “inspection pack” that can become outdated.

The PSMF as an inspection map

The pharmacovigilance system master file is often central to inspection preparation because it describes the pharmacovigilance system and points inspectors toward its supporting processes and records.

The practical question is not whether the PSMF has been reviewed on a company-defined fixed schedule. The regulatory question is whether it is current, accurate and reflective of the system. Changes in organisation, responsibilities, outsourced activities, systems, processes or significant quality-system information should be reflected through the applicable PSMF maintenance process.

A QPPV who can explain where supporting evidence is held and how the PSMF is maintained is in a stronger position than one who can merely state the document's latest approval date.

When the Inspection Is Announced

Most EU pharmacovigilance inspections are announced, although GVP Module III allows unannounced and short-notice inspections where appropriate. Once notification is received, preparation should be driven by the actual inspection scope, authority requests and logistical arrangements rather than by a generic template.

The first actions normally include:

1. confirming scope, dates, locations and inspection format;
2. identifying the regulatory and internal points of contact;
3. establishing the inspection team and decision routes;
4. reviewing the initial document request list;
5. confirming QPPV and SME availability;
6. identifying any scope-related known risks or open issues;
7. checking access to systems and controlled documents; and
8. establishing a request-tracking and escalation mechanism.

No universal EU requirement specifies that these steps must occur within a particular number of hours or days. The response should be proportionate to the notice period and the authority's stated expectations.

Preparing the QPPV

QPPV preparation should focus on current system knowledge, not memorisation.

A useful preparation review includes:

• major changes in the pharmacovigilance system since the last inspection;
• significant current compliance risks;
• important open and recently closed CAPAs;
• major audits and recurring issues;
• significant vendor and affiliate risks;
• important computerised-system changes;
• key safety and risk-management commitments;
• regulatory interactions likely to fall within inspection scope; and
• inconsistencies between documentation and current practice that need to be understood before the inspection begins.

The objective is not to create scripted answers. It is to ensure that the QPPV can explain the system accurately and knows where detailed evidence resides.

Document Requests and Evidence Control

Document handling is one of the most visible operational aspects of an inspection. Poor document control can create confusion even when the underlying pharmacovigilance process is sound.

A practical request tracker should record, as appropriate:

• the inspector's request identifier or an internally assigned reference;
• the exact request wording;
• date and time received;
• responsible owner or custodian;
• status;
• clarifications agreed with the inspector;
• submitted document name and version;
• date and time of submission; and
• outstanding follow-up items.

This is recommended operational practice rather than a mandated EMA template.

Quality control before submission

Before providing evidence, the inspection team should confirm that:

• the document is responsive to the request;
• the correct controlled version has been selected;
• the document has not been altered merely for inspection presentation;
• any redaction is justified and does not obscure information necessary for regulatory assessment;
• linked or referenced records can be retrieved if requested; and
• the submission can be traced back to the request.

A common failure mode is over-engineering the response. Inspectors usually need the underlying record, not a newly created narrative that paraphrases it. Explanatory cover notes can be useful where context is necessary, but they should not replace source evidence.

System Demonstrations and Data Retrieval

Pharmacovigilance inspections frequently include demonstrations of safety databases, document systems, signal-management tools, quality systems or reporting workflows.

The purpose of a demonstration is not simply to show that software exists. Inspectors may test whether the system supports the process described in procedures and the PSMF.

Useful preparation includes:

• confirming that appropriate users can access the relevant environment;
• understanding which functions and records may need to be demonstrated;
• ensuring that audit trails, workflow status and source records can be retrieved where relevant;
• preparing technical support without allowing support personnel to answer process questions on behalf of the responsible SME; and
• knowing how to distinguish live production data, test data, archived data and reporting extracts.

For remote inspections, GVP Module III recognises that interviews and document or system review may be conducted remotely when feasible. The specific technology and file-sharing arrangements should be agreed with the inspectorate rather than assumed internally.

Managing Interviews During the Inspection

Interviews are used to test whether the system described in documents is understood and operated in practice.

The QPPV interview usually focuses more heavily on oversight, governance, access to information and significant system risks than on low-level operational steps. Subject-matter experts may be asked for more detailed explanations of individual processes.

Preparation should therefore be role-specific.

During a QPPV interview

A strong answer normally does three things:

1. answers the question directly;
2. explains the relevant control or governance mechanism; and
3. identifies the supporting evidence when useful.

For example, if asked how significant case-processing compliance issues reach the QPPV, a credible response should explain the actual escalation route, the information reviewed, how significant deviations are distinguished from routine noise, and what action the QPPV can initiate.

The answer should reflect the organisation's real system. A polished but inaccurate answer is more damaging than a concise answer followed by a verified document or data retrieval.

When information is not immediately known

It is acceptable to verify a detail rather than speculate. A useful approach is to state what is known, identify what needs confirmation, and commit to provide the verified information through the inspection request process.

This protects both accuracy and traceability.

Daily Inspection Governance

Longer inspections benefit from a regular operating rhythm, particularly where multiple requests and interviews are running in parallel.

A daily internal review may cover:

• new inspector requests;
• overdue or complex retrieval items;
• themes emerging from interviews;
• apparent inconsistencies between documents and practice;
• potential findings or concerns raised by inspectors;
• commitments made during interviews;
• issues requiring QPPV or senior-management awareness; and
• preparation for the following day's scope.

This is internal good practice, not a legal requirement for a specific daily meeting format.

The QPPV does not need to chair every operational review. However, significant issues relevant to system oversight should reach the QPPV promptly enough for meaningful action.

Managing Emerging Concerns During Inspection

An inspection may identify a deficiency that the organisation had not previously recognised. The appropriate response depends on the nature and significance of the issue.

If there is a possible ongoing patient-safety, reporting or data-integrity risk, immediate containment may be necessary before the formal inspection report is issued. Examples might include checking whether safety reports remain unsubmitted, suspending an unreliable automated process, or initiating targeted reconciliation.

Containment should not be confused with final CAPA. The first task is to control ongoing risk; the second is to understand scope and root cause; the third is to design sustainable correction.

The QPPV should have visibility of significant pharmacovigilance-system deficiencies, particularly where they affect safety reporting, benefit-risk evaluation, regulatory commitments or the reliability of the system.

Working With Vendors and Affiliates During Inspection

Where pharmacovigilance activities are outsourced, inspectors may need evidence from third parties or local affiliates. The marketing-authorisation holder remains responsible for the pharmacovigilance system and should be able to obtain the information necessary to demonstrate oversight.

Inspection preparation should therefore confirm:

• who can provide vendor and affiliate records;
• whether contractual arrangements support timely access;
• how deviations and CAPAs are escalated;
• what performance information the MAH reviews;
• whether subcontracting is understood; and
• whether the PSMF accurately reflects major outsourced activities.

A common weakness is assuming that a vendor should independently defend its process. Inspectors may instead be testing whether the MAH understood the risk, monitored performance and acted when controls failed.

On-Site and Remote Inspection Differences

The regulatory objective is the same in either format: inspectors must be able to assess compliance and system effectiveness.

Remote inspection changes the operational risks. Document-transfer discipline, connection reliability, screen sharing, time-zone management and controlled access become more important. On-site inspection adds physical logistics, local records and face-to-face coordination.

Neither format changes the underlying QPPV responsibility for system oversight.

A hybrid inspection may combine both approaches, particularly when relevant activities or vendors are distributed across locations.

Practical Hosting Failure Modes

The following are illustrative failure modes, not published inspection findings.

Close-Out and Immediate Follow-Up

The closing meeting is an important transition point, but it is not necessarily the final regulatory conclusion. Inspectors may discuss observations or preliminary findings, while the formal inspection report and authority-specific response process follow later.

The inspection team should therefore distinguish clearly between:

• statements made during the closing meeting;
• formal findings in the issued inspection report;
• immediate containment already initiated;
• internal investigations and CAPAs; and
• commitments formally made to the authority.

Notes from close-out should be factual and should avoid upgrading preliminary comments into definitive findings before the authority does so.

After the inspection

Once formal findings are received, the organisation should move into the structured finding-management process described in [[inspection-findings]]. Significant findings should be assessed for scope and impact, root cause, containment, CAPA, implementation evidence and effectiveness verification.

The QPPV should retain visibility of findings that materially affect the pharmacovigilance system and should be able to understand the regulatory response, remediation status and any residual patient-safety or compliance risk.

Practical QPPV Hosting Checklist

The following is a quality aid, not an EU-prescribed checklist.

Before notification

1. Can the QPPV explain the current pharmacovigilance system and its major changes?
2. Are significant compliance risks, audits and CAPAs visible to the QPPV?
3. Is the PSMF current and consistent with operational reality?
4. Can evidence supporting major outsourced activities be retrieved?
5. Are escalation routes and deputy arrangements functional?

After notification

1. Has the actual inspection scope been understood?
2. Are inspection roles and decision routes clear?
3. Is every document request traceable from receipt to submission?
4. Are the QPPV and SMEs available for the relevant topics?
5. Have important known weaknesses within scope been reviewed before interviews begin?
6. Can relevant systems and records be demonstrated without uncontrolled workarounds?

During inspection

1. Are answers factual, role-appropriate and supported by evidence?
2. Are uncertainties verified rather than guessed?
3. Are new requests and commitments captured reliably?
4. Are significant emerging concerns escalated to the QPPV?
5. Is immediate containment initiated where an ongoing material risk is identified?
6. Are vendor and affiliate responses integrated with the MAH's oversight narrative?

Close-out and follow-up

1. Are preliminary inspector comments distinguished from formal findings?
2. Are authority-specific response commitments tracked?
3. Can the QPPV explain significant findings and remediation status after the inspection?

Key Takeaways

The QPPV is a central inspection contact and must demonstrate effective oversight of the pharmacovigilance system, but inspection hosting should not convert the QPPV into the operational owner of every request and document.

Strong hosting depends on accurate system knowledge, controlled evidence retrieval, role clarity, consistent interviews, prompt escalation and visible governance. The objective is not to create an artificial inspection presentation; it is to make the real pharmacovigilance system inspectable.

Most inspections are announced, but EU guidance permits unannounced and short-notice inspections. Remote inspections are also recognised. Continuous readiness is therefore more robust than event-specific preparation alone.

Document request trackers, daily internal reviews, interview preparation and defined inspection roles are useful operational controls, but they are not universally prescribed regulatory templates. They should support—not replace—the underlying requirements of an effective pharmacovigilance quality system.

References

1. European Medicines Agency. Guideline on good pharmacovigilance practices (GVP) Module I — Pharmacovigilance systems and their quality systems. EMA/541760/2011. https://www.ema.europa.eu/en/documents/scientific-guideline/guideline-good-pharmacovigilance-practices-module-i-pharmacovigilance-systems-and-their-quality-systems_en.pdf
2. European Medicines Agency. Guideline on good pharmacovigilance practices (GVP) Module II — Pharmacovigilance system master file (Rev. 2). EMA/816573/2011 Rev. 2.
3. European Medicines Agency. Guideline on good pharmacovigilance practices (GVP) Module III — Pharmacovigilance inspections. EMA/119871/2012 Rev. 1. https://www.ema.europa.eu/en/documents/scientific-guideline/guideline-good-pharmacovigilance-practices-module-iii-pharmacovigilance-inspections_en.pdf
4. European Medicines Agency. Pharmacovigilance inspection procedures: human. Current Union procedures for preparation, conduct, reporting and follow-up of pharmacovigilance inspections.
5. European Union. Commission Implementing Regulation (EU) No 520/2012, consolidated version current at 12 February 2026.
6. European Union. Directive 2001/83/EC, as amended.
7. European Union. Regulation (EC) No 726/2004, as amended.

Regulatory Note

This article distinguishes binding EU obligations, GVP guidance, Union inspection procedures and recommended operational hosting practices. As of 7 September 2026, EMA continues to list GVP Module I, Module II Rev. 2 and Module III Rev. 1 as the applicable published modules. EMA has also stated that GVP modules will be revised following amendments introduced by Commission Implementing Regulation (EU) 2025/1466; future revisions should be checked before a live inspection.