GVP Module VII: PSUR Inspection Findings and Common Deficiencies

Introduction

A PSUR can be submitted on time and still reveal weaknesses in the pharmacovigilance system. Inspection assessment therefore extends beyond whether a report exists or whether a deadline was met.

An effective inspection approach asks whether the organisation can demonstrate that the PSUR was produced from reliable data, subjected to appropriate scientific review, reconciled with other pharmacovigilance processes, and converted into appropriate action.

This article focuses on common deficiency patterns rather than presenting an alleged catalogue of regulatory findings. Examples are illustrative unless a specific authoritative inspection report is cited.

1. What Inspectors Are Really Testing

For PSUR-related processes, an inspector may be testing several underlying capabilities:

• regulatory awareness;
• completeness and accuracy of safety information;
• data integrity;
• scientific assessment;
• benefit-risk reasoning;
• quality control;
• cross-functional governance;
• QPPV oversight;
• submission compliance;
• and follow-through after regulatory assessment.

The central question is often not simply "Was the PSUR submitted?" but "Can the organisation demonstrate an effective process that produced a reliable PSUR and acted on what it learned?"

2. Deficiency Pattern: Incorrect Regulatory Scope

A fundamental weakness is failure to establish the correct PSUR reporting obligation.

Possible causes include:

• reliance on an obsolete regulatory calendar;
• failure to monitor the EURD list;
• incorrect substance mapping;
• failure to identify affected products;
• or incomplete regulatory-authorisation inventories.

A scientifically excellent PSUR prepared for the wrong reporting period or wrong regulatory scope remains a compliance problem.

3. Deficiency Pattern: Weak DLP and Submission Controls

The organisation should be able to demonstrate how the DLP and submission deadline were established and controlled.

Potential weaknesses include:

• manual calendars without adequate verification;
• unclear ownership;
• insufficient contingency planning;
• late escalation;
• or inability to demonstrate submission evidence.

A robust process should preserve evidence of the regulatory date, planned milestones, review status and actual submission.

4. Deficiency Pattern: Incomplete Data Sources

The PSUR depends on the quality and completeness of its underlying evidence.

Inspectors may examine whether relevant sources were systematically considered, including where applicable:

• spontaneous reports;
• literature;
• clinical studies;
• solicited sources;
• post-authorisation studies;
• signal-management outputs;
• risk-management activities;
• regulatory actions;
• and relevant external safety information.

The absence of a source from the final document should be explainable when that source is relevant to the product.

5. Deficiency Pattern: Poor Data Reconciliation

Different pharmacovigilance processes may contain apparently different numbers or classifications.

For example, an inspector may compare:

• case counts in the PSUR;
• safety-database outputs;
• signal-management records;
• aggregate-report tables;
• and regulatory submissions.

Differences do not automatically indicate an error. The important question is whether the organisation can explain them and demonstrate appropriate reconciliation.

6. Deficiency Pattern: Copy-Forward Without Meaningful Reassessment

Copy-forward can be useful for maintaining continuity, but it becomes problematic when previous conclusions are reproduced without evaluating new evidence.

Warning signs include:

• unchanged conclusions despite substantial new evidence;
• outdated references;
• obsolete risk descriptions;
• unresolved previous questions;
• or identical wording across reporting cycles without documented scientific reconsideration.

A PSUR should demonstrate cumulative safety evaluation rather than merely document the passage of another reporting interval.

7. Deficiency Pattern: Weak Benefit-Risk Evaluation

The benefit-risk section is vulnerable when it merely repeats safety findings without integrating them with clinical benefit.

Common weaknesses can include:

• no meaningful interpretation of important risks;
• failure to consider exposure;
• inadequate clinical context;
• unsupported statements that the balance remains favourable;
• failure to explain uncertainty;
• or failure to consider indication or population differences.

The conclusion should be traceable to the evidence and reasoning presented in the PSUR.

8. Deficiency Pattern: Signal Management and PSUR Are Disconnected

The PSUR should be coherent with the organisation's signal-management process.

Potential weaknesses include unexplained differences between:

• signals under evaluation;
• safety issues discussed in the PSUR;
• closed signals;
• and regulatory actions.

An inspector may ask why a significant signal is absent from the PSUR or why the PSUR describes a concern that does not appear in internal signal-management records.

The answer may be scientifically justified, but the rationale should be documented.

9. Deficiency Pattern: RMP and PSUR Are Not Reconciled

The PSUR and RMP have different purposes but should form a coherent safety-management system.

A PSUR identifying a new important concern should prompt consideration of whether the RMP requires updating.

Conversely, an important RMP concern should not disappear from periodic safety evaluation merely because it was discussed in an earlier cycle.

The organisation should be able to explain the relationship between the two documents and processes.

10. Deficiency Pattern: Regulatory Actions Are Not Fully Captured

Significant safety-related actions during the reporting interval should be systematically identified and assessed.

Potential weaknesses include:

• incomplete regulatory-action inventories;
• missing international actions;
• unclear action dates;
• failure to assess the significance of an action;
• or failure to carry regulatory outcomes into later PSURs.

Regulatory intelligence should therefore have a controlled interface with aggregate reporting.

11. Deficiency Pattern: Weak Quality Control

Quality control should be more than proofreading.

A meaningful QC process can address:

• numerical accuracy;
• completeness;
• source traceability;
• consistency between sections;
• scientific reasoning;
• tables and figures;
• references;
• product information;
• and regulatory requirements.

The organisation should retain evidence that appropriate QC occurred.

12. Deficiency Pattern: Insufficient Independence of Review

Where the same individual prepares and approves the scientific assessment without appropriate independent review, important errors may survive.

The exact review model depends on organisational structure and risk, but responsibilities should be sufficiently defined to ensure meaningful challenge.

A review signature without evidence of substantive review provides limited assurance.

13. Deficiency Pattern: Vendor Oversight Failure

A vendor may prepare analyses, tables, literature outputs or other PSUR content, but outsourcing does not transfer the MAH's regulatory responsibility.

Inspectors may therefore examine:

• vendor qualification;
• contractual responsibilities;
• specifications;
• QC;
• reconciliation;
• issue escalation;
• performance monitoring;
• and evidence that the MAH reviewed the output.

A vendor-produced table should remain traceable to its source and subject to appropriate MAH oversight.

14. Deficiency Pattern: Poor Version and Records Control

The organisation should know which PSUR version was reviewed, approved and submitted.

Potential weaknesses include:

• uncontrolled drafts;
• missing approval records;
• inability to reconstruct changes;
• inconsistent copies across functions;
• or incomplete retention of regulatory correspondence.

Version control is especially important when a PSUR undergoes multiple review cycles or regulatory clarification.

15. Deficiency Pattern: Regulatory Questions Not Integrated Into the System

Questions raised during a previous PSUR assessment can provide important information for subsequent reporting.

A recurring problem is treating regulatory questions as isolated correspondence rather than as part of the product's cumulative safety history.

The organisation should therefore determine whether previous assessment findings require follow-up in later PSURs.

Key Takeaways

PSUR inspection readiness is fundamentally about demonstrating an effective system rather than producing a compliant-looking document.

The major deficiency patterns arise when regulatory scope, source data, scientific assessment, quality control, governance and follow-up operate as disconnected activities.

The strongest organisations can trace important conclusions from source evidence through analysis and review to regulatory action and subsequent monitoring.

References

1. European Medicines Agency. Good Pharmacovigilance Practices (GVP), Module VII — Periodic Safety Update Report.
2. European Medicines Agency. Good Pharmacovigilance Practices (GVP), Module I — Pharmacovigilance Systems and Quality Systems.
3. European Medicines Agency. Periodic safety update reports (PSURs) and PSUR Single Assessment (PSUSA).
4. European Commission. Commission Implementing Regulation (EU) No 520/2012, as amended.
5. Directive 2001/83/EC, as amended.
6. Regulation (EC) No 726/2004, as amended.

Regulatory Note

This article is an educational explanation of common PSUR inspection weaknesses. It does not constitute a catalogue of confirmed regulatory inspection findings and does not replace current EU legislation, GVP guidance, EMA procedural requirements or the organisation's approved procedures.

Examples are illustrative unless an authoritative source is specifically identified.

16. Deficiency Pattern: Weak Literature and Study Integration

An inspector may examine whether literature, clinical studies, PASS and other relevant sources were systematically incorporated into the PSUR. The key issue is not simply whether a source appears in a table, but whether its safety implications were evaluated.

A robust process should establish what searches were performed, what study information was available, how relevant findings were assessed and how important results entered the benefit-risk evaluation.

17. Deficiency Pattern: Exposure Is Poorly Characterised

Safety interpretation depends on understanding the population exposed. Weak exposure estimates can make rates, trends and comparative interpretation unreliable.

Inspectors may ask how exposure was estimated, what assumptions were used, whether important markets or indications were excluded, and whether changes in utilisation were considered.

Where precise exposure cannot be established, the limitation should be acknowledged rather than hidden behind false precision.

18. Deficiency Pattern: Important Risks Are Listed but Not Reassessed

A safety specification or previous PSUR can contain important risks without demonstrating that their current status has been meaningfully evaluated.

The PSUR should consider whether new evidence changes the frequency, severity, clinical context, preventability or management of an existing risk.

19. Deficiency Pattern: Risk-Minimisation Implementation Is Confused With Effectiveness

An organisation may demonstrate that an additional risk-minimisation measure was distributed or implemented, but this does not by itself establish that the measure works.

Where effectiveness assessment is required, the PSUR should consider the available evidence and explain its implications.

20. Deficiency Pattern: Product Information Is Not Reconciled

The safety conclusions in the PSUR should be considered against the current reference product information.

Potential weaknesses include outdated safety wording, failure to identify relevant changes during the interval, or unexplained differences between the safety evaluation and the authorised information.

21. Deficiency Pattern: Previous Regulatory Commitments Are Forgotten

An inspector may trace a commitment from an earlier PSUR, assessment or regulatory procedure into the current reporting cycle.

The organisation should be able to show whether the commitment was completed, remained open, changed scope, or generated new evidence.

22. Deficiency Pattern: Scientific Judgement Is Not Documented

Some PSUR conclusions necessarily involve expert clinical judgement. The problem arises when important decisions cannot be reconstructed.

The record should provide enough reasoning to explain why evidence was considered sufficient, insufficient, reassuring, concerning or inconclusive.

23. Deficiency Pattern: No Clear Escalation Path

A process can identify a significant issue but still fail if nobody knows when it must be escalated.

Procedures should define escalation for material safety findings, regulatory questions, missed milestones, data-quality problems and disagreements affecting the final conclusion.

24. Deficiency Pattern: Metrics Create False Assurance

High on-time completion rates do not prove that PSURs are scientifically robust.

Useful oversight should combine timeliness with quality indicators such as major QC findings, recurring reconciliation issues, regulatory questions, late changes and CAPA trends.

Metrics should inform management review rather than replace scientific oversight.

25. Deficiency Pattern: CAPA Addresses the Symptom

Where a PSUR deficiency occurs, a CAPA that simply adds another review step may not address the underlying cause.

Root-cause analysis should consider whether the failure arose from inadequate process design, training, systems, data interfaces, ownership, vendor oversight or governance.

Effectiveness should then be tested rather than assumed.

26. Practical Inspection Scenario: Numbers Do Not Reconcile

An inspector identifies a difference between the number of cases in a PSUR table and the safety database.

The correct response is not necessarily to assume that one number is wrong. The organisation should explain the population, extraction date, inclusion criteria, duplicates, case status and any justified exclusions.

A controlled reconciliation should make the difference understandable and reproducible.

27. Practical Inspection Scenario: The PSUR Was Changed Late

A medically important change is introduced immediately before submission.

The organisation should be able to demonstrate who requested the change, what evidence supported it, who reviewed it, whether related sections were reassessed and which version was finally approved.

Late change does not automatically mean poor quality. Uncontrolled late change does.

28. Practical Inspection Scenario: Vendor Data Cannot Be Reproduced

If a vendor supplied a major analysis but neither the underlying dataset nor the methodology can be reconstructed, the MAH may have difficulty demonstrating data integrity.

Vendor oversight should therefore ensure appropriate access to source information, methods, specifications and quality records.

29. Practical Inspection Scenario: QPPV Cannot Explain the Conclusion

The QPPV does not need to personally perform every PSUR analysis. However, for significant safety issues, the QPPV should have sufficient understanding and oversight to challenge the adequacy of the process and conclusions.

An inability to explain the major safety issues, uncertainties or actions can indicate weak governance.

30. Practical Inspection Scenario: A Previous Finding Reappears

A recurring deficiency across successive PSURs suggests that the organisation's corrective action may not have been effective.

Inspectors may therefore examine whether previous CAPA addressed the true root cause and whether effectiveness was demonstrated.

Repeated occurrence should trigger escalation rather than another superficial correction.

31. The Minimum Inspection Evidence Set

A practical PSUR evidence package should allow reconstruction of:

Regulatory obligation
      ↓
Scope and DLP determination
      ↓
Source-data collection
      ↓
Analysis
      ↓
Scientific assessment
      ↓
QC and approval
      ↓
Submission
      ↓
Regulatory assessment
      ↓
Actions and follow-up

The exact records depend on the organisation, but the evidence should be coherent, attributable and retrievable.

32. QPPV Inspection Questions

Useful questions for QPPV oversight include:

• How do we know which PSURs are due?
• How do we know the source data are complete?
• How are significant discrepancies reconciled?
• How are important signals reflected in the PSUR?
• How are RMP implications assessed?
• How is scientific review challenged?
• How are vendors controlled?
• How are regulatory questions incorporated into later cycles?
• How do we know CAPA is effective?

These questions test system effectiveness rather than document appearance.

33. Final Inspection Checklist

Before an inspection, the organisation should be able to demonstrate:

• current regulatory scope;
• DLP and submission evidence;
• source-data traceability;
• reconciliation records;
• documented scientific assessment;
• benefit-risk rationale;
• QC and review evidence;
• regulatory correspondence;
• implementation of regulatory outcomes;
• RMP and product-information impact assessment;
• CAPA where deficiencies occurred;
• and QPPV oversight.

Key Takeaways

PSUR deficiencies often reveal weaknesses elsewhere in the pharmacovigilance system. The report is an output of multiple interconnected processes, so inspection readiness requires control of the entire evidence chain.

The most defensible system is one in which important numbers, conclusions and actions can be traced to evidence and reconstructed by an independent reviewer.

References

1. European Medicines Agency. Good Pharmacovigilance Practices (GVP), Module VII — Periodic Safety Update Report.
2. European Medicines Agency. GVP Module I — Pharmacovigilance Systems and Quality Systems.
3. European Medicines Agency. Periodic safety update reports (PSURs) and PSUSA.
4. European Commission. Commission Implementing Regulation (EU) No 520/2012, as amended.
5. Directive 2001/83/EC, as amended.
6. Regulation (EC) No 726/2004, as amended.

Regulatory Note

This article is an educational inspection-readiness guide. The examples are illustrative and should not be represented as confirmed inspection findings unless supported by an identified authoritative inspection source.

34. Building a PSUR Inspection-Ready System

Inspection readiness should be continuous rather than an activity performed immediately before an inspection.

A mature process continuously maintains:

• current regulatory obligations;
• controlled source inventories;
• traceable data;
• documented scientific reasoning;
• effective QC;
• regulatory correspondence;
• action tracking;
• and evidence of QPPV oversight.

The objective is that an inspection request can be answered from the normal quality system without reconstructing the history from individual employees' memories.

35. Inspection Readiness Is Different From Inspection Preparation

Inspection preparation can organise records and brief staff. Inspection readiness means that the underlying process is already controlled.

A polished inspection room cannot compensate for missing source data, unexplained discrepancies or undocumented decisions.

The strongest evidence is therefore ordinary operational evidence generated while the PSUR is being prepared and maintained.

36. Testing the Process With a Mock Inspection

A useful mock inspection can select one completed PSUR and ask an independent reviewer to reconstruct it from source records.

The reviewer should attempt to answer:

1. Why was this PSUR required?
2. How was the scope established?
3. What was the DLP?
4. What sources were used?
5. How were the important findings identified?
6. How was benefit-risk assessed?
7. Who reviewed and approved the report?
8. What regulatory feedback followed?
9. What actions resulted?
10. What evidence demonstrates completion?

Any unexplained gap becomes an improvement opportunity.

37. When a Deficiency Should Become CAPA

Not every isolated error requires CAPA. The organisation should use its quality system to determine significance, recurrence, systemic impact and risk.

Where a problem indicates a systemic weakness, CAPA should address the underlying cause and include measurable effectiveness criteria.

Examples of potentially systemic issues include recurring reconciliation failures, repeated missed regulatory milestones, repeated deficiencies in vendor output or persistent inability to reconstruct scientific decisions.

38. Common Root Causes

Recurring PSUR problems can arise from:

• fragmented ownership;
• inadequate process interfaces;
• poor regulatory intelligence;
• manual data transfers;
• unclear definitions;
• insufficient training;
• weak vendor governance;
• inadequate systems;
• excessive reliance on copy-forward;
• or insufficient scientific challenge.

The appropriate corrective action depends on the actual root cause.

39. The Role of the Quality System

PSUR controls should be connected to the broader pharmacovigilance quality system.

Relevant interfaces can include:

• document control;
• training;
• deviation management;
• CAPA;
• change control;
• vendor management;
• audit;
• management review;
• business continuity;
• and records management.

This is why a PSUR deficiency can be a symptom of a broader PV-system weakness.

40. What a Strong PSUR Process Looks Like

A strong process has a simple underlying logic:

Know the obligation
       ↓
Know the products and scope
       ↓
Know the evidence
       ↓
Know the limitations
       ↓
Evaluate the science
       ↓
Challenge the conclusion
       ↓
Control the final report
       ↓
Submit correctly
       ↓
Act on the outcome
       ↓
Learn for the next cycle

Each step should have accountable ownership and sufficient evidence.

41. Final Practical Test

A useful final test is to select any important statement in the PSUR and ask:

Can we show where this came from, why we interpreted it this way, who challenged it, and what happened because of it?

If the answer is yes, the organisation is much better positioned to demonstrate effective pharmacovigilance.

If the answer is no, the problem may be deeper than a missing document.

Key Takeaways

The strongest PSUR inspection systems do not depend on emergency preparation. They continuously preserve the evidence needed to reconstruct regulatory scope, source data, scientific reasoning, quality review, submission and follow-up.

Common deficiencies are most useful when treated as signals of process weakness rather than as isolated document errors.

The ultimate inspection objective is evidence of an effective pharmacovigilance system: reliable information, sound scientific judgement, controlled decisions and demonstrable follow-through.

References

1. European Medicines Agency. Good Pharmacovigilance Practices (GVP), Module VII — Periodic Safety Update Report.
2. European Medicines Agency. GVP Module I — Pharmacovigilance Systems and Quality Systems.
3. European Medicines Agency. Periodic safety update reports (PSURs) and PSUSA.
4. European Commission. Commission Implementing Regulation (EU) No 520/2012, as amended.
5. Directive 2001/83/EC, as amended.
6. Regulation (EC) No 726/2004, as amended.

Regulatory Note

This article is an educational explanation of PSUR inspection readiness and common deficiency patterns. It does not replace current EU legislation, GVP guidance, EMA procedural requirements, inspection reports, or an organisation's approved procedures.

Examples are illustrative unless an authoritative source is specifically identified.