Audit Findings and Classification in Pharmacovigilance

A practical guide to audit findings, finding classification, risk assessment, escalation and inspection readiness.

Audit Findings and Classification in Pharmacovigilance

Introduction

Audit findings are the primary outputs of pharmacovigilance audits.

They provide evidence regarding:

However, identifying findings is only the first step.

Organisations must also determine:

Finding classification provides this structure.

Without consistent classification, resources may be directed toward the wrong issues and significant risks may remain inadequately addressed.

What Is an Audit Finding?

An audit finding is a documented observation indicating that:

Findings should be:

Opinions are not findings.

Evidence is.

The Purpose of Finding Classification

Classification helps organisations determine:

A useful principle is:

Classification should reflect risk rather than auditor preference.

The goal is consistency.

Risk-Based Classification

Finding significance should generally reflect:

Patient Safety Impact

Could patients be harmed?

Regulatory Impact

Could non-compliance occur?

Data Integrity Impact

Could critical data become inaccurate or unavailable?

Systemic Impact

Is the issue isolated or widespread?

Detectability

Would the organisation identify the problem quickly?

These factors help determine severity.

Critical Findings

Critical findings represent the highest level of concern.

Typical characteristics include:

Examples may include:

Critical findings typically require immediate management attention.

Major Findings

Major findings indicate significant weaknesses that require remediation.

Examples may include:

Major findings may not represent immediate critical risk but still warrant prompt corrective action.

Minor Findings

Minor findings generally involve limited weaknesses.

Examples include:

Minor findings should not be ignored.

Multiple minor findings may indicate broader weaknesses.

Observations

Some organisations use observations rather than formal findings.

Observations may identify:

Observations help organisations improve before deficiencies become formal findings.

Finding Statements

Strong findings are clear and structured.

A useful format includes:

Requirement

What was expected?

Condition

What was observed?

Risk

Why does the issue matter?

Example:

Requirement:

Vendor audits should be conducted according to the approved audit programme.

Condition:

No vendor audit had been conducted during the previous three years.

Risk:

Significant vendor compliance deficiencies may remain unidentified.

This structure improves consistency.

Root Cause Considerations

Findings describe what happened.

Root cause analysis explains why it happened.

Examples include:

Process Design Failures

Controls are inadequate.

Training Deficiencies

Personnel do not understand requirements.

Resource Constraints

Insufficient personnel are available.

Governance Weaknesses

Oversight mechanisms are ineffective.

Technology Limitations

Systems fail to support compliance.

Strong remediation depends upon understanding root causes.

Systemic Versus Isolated Findings

A critical consideration is whether a finding is:

Isolated

Affects a single activity.

Systemic

Affects multiple activities.

Systemic findings often require greater management attention because their impact may extend beyond the audited area.

Repeat Findings

Repeat findings deserve particular scrutiny.

A repeat finding may indicate:

Inspectors frequently pay close attention to recurring issues.

Repeated deficiencies often suggest organisational learning failures.

Escalation Requirements

Classification frequently determines escalation.

Example:

Classification Typical Escalation
Critical Immediate senior management notification
Major Management review and CAPA
Minor Routine remediation
Observation Monitoring and improvement

The exact model varies by organisation.

The principle remains the same.

Findings and CAPAs

Findings should lead to action.

CAPAs provide the mechanism for:

A useful principle is:

Findings identify problems. CAPAs create improvement.

For additional discussion see:

[[audit-capas]]

Findings and Metrics

Finding trends can provide valuable governance information.

Examples include:

Number of Findings

Overall audit output.

Critical Findings

Highest-risk deficiencies.

Repeat Findings

Recurring weaknesses.

Closure Timeliness

Responsiveness of remediation activities.

Changes over time.

These metrics support management visibility.

The QPPV Perspective

Audit findings provide important assurance information.

Particularly relevant areas include:

The QPPV should generally have visibility regarding significant findings affecting the pharmacovigilance system.

Inspection Perspective

Inspectors frequently review:

Common questions include:

The quality of finding management often influences inspection outcomes.

Common Classification Mistakes

Several weaknesses occur repeatedly.

Severity Inflation

Everything becomes major.

Severity Deflation

Significant issues are minimised.

Inconsistent Classification

Similar findings receive different classifications.

Poor Risk Assessment

Impact is not evaluated appropriately.

Weak Documentation

Rationale is unclear.

These weaknesses reduce confidence in the audit programme.

Characteristics of Mature Finding Management

High-performing organisations generally demonstrate:

Consistent Classification

Standards are applied uniformly.

Risk-Based Assessment

Impact drives severity.

Effective Escalation

Important issues receive visibility.

Strong Root Cause Analysis

Causes are understood.

Sustainable Remediation

CAPAs prevent recurrence.

Continuous Learning

Findings improve the system.

These characteristics support stronger governance.

Key Takeaways

References

  1. EMA Good Pharmacovigilance Practices (GVP) Module IV – Pharmacovigilance Audits.
  2. EMA Good Pharmacovigilance Practices (GVP) Module I – Pharmacovigilance Systems and Their Quality Systems.
  3. EMA Good Pharmacovigilance Practices (GVP) Module III – Pharmacovigilance Inspections.
  4. Regulation (EC) No 726/2004.
  5. Directive 2001/83/EC.
  6. Commission Implementing Regulation (EU) No 520/2012.
  7. ICH Q9 Quality Risk Management.
  8. ICH E2E Pharmacovigilance Planning.

Last reviewed: 2026-06-11