GVP Module I Explained: Pharmacovigilance Systems and Quality Systems

Introduction

GVP Module I is the foundation of the European Union's good pharmacovigilance practice framework for understanding how a marketing authorisation holder's pharmacovigilance system should be organised and controlled.

The subject is broader than having a collection of pharmacovigilance procedures. A pharmacovigilance system consists of people, responsibilities, processes, systems, data, quality controls, governance and records working together to ensure that pharmacovigilance obligations can be fulfilled reliably.

Module I therefore asks a fundamental question:

How is the pharmacovigilance system designed and controlled so that required safety activities are performed effectively and consistently?

That question is central to QPPV oversight and to pharmacovigilance inspections.

A useful conceptual model is:

EU legal requirements
        ↓
GVP expectations
        ↓
PV system design
        ↓
People + processes + systems + data
        ↓
Quality controls
        ↓
Evidence and oversight
        ↓
Continuous improvement

The purpose of this article is not to reproduce Module I. It explains how to understand its requirements and translate them into a functioning, inspectable pharmacovigilance system.

1. Where Module I Fits in GVP

Module I addresses pharmacovigilance systems and their quality systems.

It provides the system-level foundation for many of the activities described in other GVP modules.

For example:

• Module VI addresses individual case safety reports;
• Module VII addresses periodic safety update reports;
• Module IX addresses signal management;
• Module V addresses risk-management systems;
• Module XV addresses safety communication;
• Module XVI addresses risk-minimisation measures.

Module I asks how the organisation's overarching pharmacovigilance system supports and controls these activities.

This makes Module I fundamentally different from a process-specific module. It is concerned with the architecture and quality of the system as a whole.

2. The Pharmacovigilance System Is More Than Its Documentation

A common implementation error is to equate the pharmacovigilance system with its documentation.

The PSMF, SOPs, work instructions, training records and quality documents describe and support the system, but they are not the system itself.

The distinction can be represented as:

Actual pharmacovigilance operations
              ↓
People + processes + systems + controls
              ↓
Evidence generated by those operations
              ↓
Controlled documentation describing the system

An organisation can therefore have an apparently complete documentation set while still having a weak pharmacovigilance system.

For example, an SOP may require reconciliation every month, but if reconciliations are routinely late or ineffective, the existence of the SOP does not demonstrate compliance.

3. The Purpose of the Quality System

The quality system provides the structure through which pharmacovigilance activities are performed consistently and controlled for quality.

A useful way to think about it is that the quality system should reduce dependence on individual memory or informal workarounds.

It should establish:

• defined responsibilities;
• standardised processes;
• appropriate training;
• quality controls;
• documented records;
• escalation mechanisms;
• deviation management;
• CAPA;
• audit and inspection mechanisms;
• and management oversight.

The quality system should make the desired behaviour the normal operating state.

4. The Quality Cycle

A functioning pharmacovigilance quality system can be represented as a cycle:

Plan
 ↓
Perform
 ↓
Check
 ↓
Identify weaknesses
 ↓
Correct / improve
 ↓
Verify effectiveness
 ↓
Plan again

This is why quality management should not be reduced to document approval.

The critical question is whether the controls are capable of detecting and correcting failures before they become significant regulatory or patient-safety problems.

5. Proportionality

Pharmacovigilance systems should be appropriate to the nature and scale of the organisation and its products while remaining capable of fulfilling applicable requirements.

A multinational organisation with hundreds of products, numerous vendors and multiple regulatory procedures may require substantially more complex controls than a small MAH with a limited portfolio.

That difference does not mean that one system is compliant and the other is not.

The important question is whether each system has controls proportionate to its risks and sufficient to achieve the applicable regulatory objectives.

Proportionality should therefore be applied to how the requirement is implemented, not used to justify omission of a required pharmacovigilance activity.

6. Key Elements of a PV Quality System

A practical Module I implementation normally addresses several connected elements:

These elements should function as one system rather than as separate compliance programmes.

7. Written Standards

Written standards provide a controlled description of how important pharmacovigilance activities are to be performed.

Depending on the activity and organisation, these can include:

• policies;
• SOPs;
• work instructions;
• system procedures;
• templates;
• forms;
• controlled guidance;
• and quality-system records.

The documentation hierarchy should be understandable to the people who use it.

A procedure that is technically complete but impossible for an operational user to follow is a weak control.

8. Responsibilities Must Be Clear

Ambiguous responsibility is a frequent source of pharmacovigilance failure.

A process should make clear:

• who performs the activity;
• who reviews it;
• who approves it where applicable;
• who receives escalations;
• who monitors performance;
• and who has overall oversight.

Responsibility should not depend on knowing which individual happens to perform the task at a particular time.

Role-based accountability provides continuity when personnel change.

9. Training and Competence

Personnel involved in pharmacovigilance should have appropriate education, training, experience and/or qualifications for their responsibilities.

Training is therefore a system control, not merely an HR activity.

A useful distinction is:

Training assigned
      ↓
Training completed
      ↓
Knowledge acquired
      ↓
Competence demonstrated
      ↓
Competence maintained

Completion of a training course does not automatically prove that an individual can perform a complex pharmacovigilance activity correctly.

The depth of competence assessment should be proportionate to the role and risk.

10. Documentation and Traceability

A strong quality system allows an activity to be reconstructed after it has occurred.

For a significant process, an organisation should normally be able to establish:

• what was done;
• when it was done;
• by whom;
• using which information or system;
• what review occurred;
• what decision was made;
• and what happened if something went wrong.

This is the essence of traceability.

It becomes particularly important when the organisation needs to reconstruct a historical safety or regulatory decision.

11. Management Responsibility

Pharmacovigilance quality is not solely the responsibility of the PV department.

Management has an important role in ensuring that the system has appropriate resources, governance and escalation mechanisms.

A quality system cannot reliably compensate for persistent structural problems such as:

• insufficient staffing;
• inadequate system capacity;
• uncontrolled outsourcing;
• unclear responsibilities;
• or chronic failure to address known weaknesses.

Management oversight is therefore part of the system's ability to remain effective.

12. The QPPV's Perspective

The QPPV needs visibility across the pharmacovigilance system sufficient to identify material compliance and safety risks.

This does not mean that the QPPV personally performs or reviews every activity.

Instead, the QPPV should have appropriate mechanisms to understand:

• whether critical processes are functioning;
• whether significant deviations are occurring;
• whether important quality problems are being escalated;
• whether CAPAs are effective;
• whether vendors are performing adequately;
• and whether the system remains compliant as the organisation changes.

The QPPV's role is therefore closely connected to effective system oversight.

13. Module I and the Other GVP Modules

Module I should be viewed as the quality-system foundation supporting the other GVP activities.

For example:

Module I
  │
  ├── Module VI → ICSR processes
  ├── Module VII → PSUR processes
  ├── Module IX → Signal management
  ├── Module V → Risk management
  ├── Module VIII → PASS
  ├── Module XV → Safety communication
  └── Module XVI → Risk minimisation

The detailed requirements for each activity are addressed in the corresponding modules. Module I provides the system-level controls that allow those activities to operate consistently.

The next chunk will examine how Module I requirements become operational controls, how outsourcing and critical processes fit into the quality system, and what evidence a QPPV or inspector should expect to see.

15. The Pharmacovigilance System as an Integrated System

GVP Module I is easiest to understand when the pharmacovigilance system is treated as an integrated system rather than a collection of independent procedures.

The system includes:

• organisational structures;
• responsibilities and accountability;
• processes and procedures;
• people and competence;
• computerised systems and data;
• quality controls and assurance activities;
• records and documentation;
• resources;
• compliance management;
• and governance and oversight.

A weakness in one component can affect several others. For example, an inadequate vendor process may create data-quality problems, which may then affect case processing, signal detection, aggregate reporting and QPPV oversight.

This systems perspective is central to applying Module I effectively.

16. Quality Planning

Quality planning is the first part of the quality cycle.

The organisation should establish structures and plan integrated, consistent processes capable of achieving the applicable quality objectives.

In practical terms, quality planning should answer questions such as:

• What pharmacovigilance activities are required?
• Who performs them?
• What expertise is required?
• What systems support them?
• What resources are necessary?
• What controls are needed?
• What interfaces exist between functions?
• What risks could prevent the required outcome?

Planning should occur when the system is established and whenever significant changes are introduced.

17. Quality Adherence

Quality planning has little value if the organisation does not perform activities according to the defined requirements.

Quality adherence means that assigned tasks and responsibilities are actually carried out in accordance with the applicable requirements and procedures.

Evidence can include:

• completed case records;
• documented assessments;
• approved reports;
• training records;
• review records;
• system audit trails;
• meeting records;
• reconciliations;
• and other contemporaneous records.

The emphasis should be on evidence of actual performance rather than evidence that a procedure exists.

18. Quality Control and Quality Assurance

Quality control and quality assurance have related but different functions.

Quality control generally focuses on monitoring and evaluating whether individual processes or outputs meet defined requirements.

Quality assurance provides broader confidence that the structures and processes have been appropriately established and are operating effectively.

Examples of controls can include:

• case quality checks;
• report review;
• reconciliation;
• automated validation;
• data-quality monitoring;
• timeliness monitoring;
• process-level review;
• and quality indicators.

Audit provides an independent assurance mechanism and is addressed separately in GVP Module IV.

19. Quality Improvement

The quality cycle is incomplete if the organisation only detects problems.

Where deficiencies are identified, the system should be capable of correcting and improving the relevant structures and processes.

Sources of improvement can include:

• deviations;
• CAPA;
• audit findings;
• inspection findings;
• quality indicators;
• recurring errors;
• vendor performance problems;
• system incidents;
• regulatory changes;
• and lessons learned.

The objective is not simply to close individual findings but to improve the reliability of the underlying process.

20. Responsibilities Must Be Defined

A pharmacovigilance system should make responsibilities clear enough that important activities cannot fall between organisational boundaries.

Responsibility should be distinguishable from execution.

For example, a vendor may execute a PV activity while the MAH retains responsibility for ensuring that the activity is appropriately controlled.

Similarly, a local affiliate may collect safety information while central Pharmacovigilance controls the subsequent process.

A practical responsibility model should identify:

• accountable function;
• operational owner;
• supporting functions;
• escalation route;
• QPPV oversight;
• and management governance where appropriate.

21. Resource Management

A compliant pharmacovigilance system requires adequate resources.

Resources include more than headcount. They can include:

• appropriately qualified personnel;
• training;
• technology;
• validated or otherwise appropriately controlled systems;
• external expertise;
• facilities;
• data access;
• and financial resources.

A process that consistently fails because it is under-resourced is a system problem, not simply an individual performance problem.

22. The Relationship Between Workload and Quality

Workload should be considered as part of pharmacovigilance quality management.

For example, persistent case backlogs can indicate:

• inadequate staffing;
• ineffective triage;
• unexpected increases in reporting volume;
• vendor capacity problems;
• system limitations;
• or weak management controls.

A KPI showing that a backlog exists is useful, but management should also understand why it exists and whether the system can recover without compromising quality.

23. Training and Competence

Personnel performing pharmacovigilance activities should have appropriate qualifications, training and experience for their responsibilities.

Training should cover both the regulatory expectations relevant to the role and the organisation's actual processes.

A strong training system should address:

• initial training;
• role-specific training;
• procedural changes;
• regulatory changes;
• system changes;
• refresher training where appropriate;
• and evidence of completion and, where relevant, effectiveness.

The organisation should avoid equating completion of an electronic training assignment with proof that the employee is competent to perform a complex safety activity.

24. Documentation and Record Management

Documentation provides evidence of how the pharmacovigilance system operates and how decisions were made.

Records should be sufficiently complete, accurate, traceable and accessible to support the relevant activity and regulatory requirements.

Important records may include:

• procedures and controlled documents;
• case records;
• safety assessments;
• signal evaluations;
• RMP records;
• aggregate reports;
• regulatory correspondence;
• training records;
• quality records;
• audit and inspection records;
• vendor records;
• and governance documentation.

The retention period and specific requirements depend on the applicable legislation and organisational procedures.

25. Compliance Management

Compliance management should allow the organisation to identify whether pharmacovigilance requirements are being met and to respond when they are not.

A useful compliance process links:

Requirement
    ↓
Process
    ↓
Control
    ↓
Measurement
    ↓
Deviation / issue
    ↓
Impact assessment
    ↓
CAPA / remediation
    ↓
Effectiveness verification

This is stronger than a periodic declaration that the department is "GVP compliant".

26. Critical Interfaces

Many serious pharmacovigilance problems occur at interfaces between functions rather than entirely within one function.

Important interfaces include:

• Pharmacovigilance ↔ Regulatory Affairs;
• Pharmacovigilance ↔ Medical Information;
• Pharmacovigilance ↔ Clinical Development;
• Pharmacovigilance ↔ Quality;
• Pharmacovigilance ↔ Supply Chain;
• central PV ↔ affiliates;
• MAH ↔ vendors;
• and QPPV ↔ senior management.

Each interface should have defined responsibilities, information flows, timelines and escalation mechanisms.

27. Outsourced Pharmacovigilance Activities

Outsourcing can change who performs an activity without eliminating the need for MAH oversight.

The quality system should therefore address contracted and subcontracted activities appropriately.

Useful controls include:

• qualification and due diligence;
• contractual responsibilities;
• safety-data exchange agreements;
• service-level expectations;
• quality requirements;
• performance indicators;
• reconciliation;
• issue escalation;
• audits where appropriate;
• CAPA;
• and governance review.

The degree of oversight should be proportionate to the criticality and risk of the outsourced activity.

28. Computerised Systems

Computerised systems are part of the operational pharmacovigilance environment and can directly influence the quality of PV outputs.

Relevant considerations include:

• intended use;
• access controls;
• data integrity;
• audit trails where applicable;
• interfaces;
• change control;
• system availability;
• backup and recovery;
• data migration;
• and appropriate validation or other documented assurance activities.

The precise controls depend on the system and its intended use.

A system should not be considered compliant simply because it has been validated historically. Significant changes, interfaces, data migrations and changes in intended use may require further assessment.

29. Business Continuity

Critical pharmacovigilance activities should remain capable of operating when normal processes or systems are disrupted.

Business-continuity planning should consider credible scenarios such as:

• major system outage;
• loss of a key vendor;
• loss of facilities;
• cyber or technology incidents;
• widespread staff unavailability;
• loss of critical data access;
• or other major operational disruption.

The objective is not to eliminate every possible disruption but to ensure that critical safety activities can continue or recover within appropriate timeframes.

30. Quality Indicators and Performance Metrics

Metrics can help management identify whether important processes are performing as intended.

Examples may include:

• case-reporting timeliness;
• case-processing backlog;
• report submission timeliness;
• literature-monitoring performance;
• signal-management timeliness;
• aggregate-report timeliness;
• training completion;
• overdue CAPA;
• vendor performance;
• and reconciliation performance.

Metrics should be selected because they provide meaningful information about process performance.

A large collection of metrics does not necessarily create better oversight.

31. Quality Indicators Are Not Automatically Quality

A metric can look satisfactory while the underlying process remains weak.

For example, a high on-time case-processing rate may coexist with poor medical quality if the metric measures only completion date.

Similarly, 100% training completion does not demonstrate that employees perform correctly.

Good governance therefore combines quantitative metrics with qualitative information, trend analysis, deviations, audit results, inspection findings and other evidence.

32. QPPV Oversight Under Module I

The QPPV should have sufficient visibility of the pharmacovigilance system to identify material compliance and quality risks.

This does not require the QPPV to personally review every operational record.

Instead, effective oversight can be supported by:

• governance meetings;
• quality and compliance dashboards;
• escalation procedures;
• audit and inspection results;
• significant deviations and CAPA;
• vendor performance information;
• signal and aggregate-report governance;
• regulatory intelligence;
• and periodic system reviews.

The QPPV should be able to distinguish isolated operational events from evidence of systemic weakness.

33. What a Good Module I System Looks Like

A practical test of the system is whether the organisation can answer six questions for every critical pharmacovigilance activity:

1. Who is responsible?
2. How is the activity performed?
3. What system or data supports it?
4. How is quality or timeliness controlled?
5. What happens when it fails?
6. How does the QPPV or management obtain appropriate oversight?

If any answer is unclear, the organisation should investigate whether the gap is one of responsibility, process design, resources, system capability, quality control or governance.

The final chunk will address Module I inspection findings and practical failure patterns, then provide References and the Regulatory Note.

33. A Practical Module I Control Model

A useful way to operationalise GVP Module I is to connect each major expectation to an accountable control.

The purpose of such a model is not to create another checklist. It is to establish a traceable relationship between regulatory expectations and the actual functioning of the system.

34. The PSMF as a System-Level View

The PSMF is particularly important because it provides a structured description of the pharmacovigilance system.

It should be consistent with the system that actually operates.

A common weakness is allowing the PSMF to become a static document maintained separately from operational reality. Changes in organisational structure, vendors, systems, products or important processes can make an apparently complete PSMF inaccurate.

A mature system therefore treats PSMF maintenance as part of change governance rather than as an annual document exercise.

35. QPPV Oversight Should Be Risk-Based

The QPPV cannot personally inspect every transaction performed by a large pharmacovigilance organisation.

Effective oversight therefore depends on information that is sufficiently accurate, timely and meaningful to identify material weaknesses.

Useful information can include:

• important quality issues;
• overdue regulatory activities;
• significant case-reporting problems;
• signal-management concerns;
• aggregate-reporting issues;
• vendor failures;
• audit findings;
• inspection findings;
• significant CAPA;
• and emerging systemic risks.

The QPPV should be able to distinguish isolated operational events from evidence of a systemic control weakness.

36. Quality Indicators Are Not the Whole Quality System

Quality indicators can help demonstrate whether important processes are performing as expected.

However, a process can meet a numerical target while still having significant weaknesses.

For example, a case-processing timeliness metric may appear acceptable while data quality, duplicate management or medical assessment quality is poor.

Quality indicators should therefore be interpreted with other information, including quality-control results, deviations, complaints, audits and inspection findings.

37. Designing Effective Controls

A useful control should answer three questions:

1. What failure are we trying to prevent or detect?
2. How will the control identify that failure?
3. What happens when the control identifies it?

For example, a reconciliation is useful only when discrepancies are investigated and resolved through a defined process.

Similarly, a KPI is useful only when unexpected performance leads to appropriate investigation or escalation.

A control without an effective response mechanism may provide the appearance of governance without providing meaningful risk reduction.

38. Preventive and Detective Controls

PV systems generally use both preventive and detective controls.

Preventive controls can include:

• controlled access;
• mandatory system fields;
• workflow restrictions;
• training prerequisites;
• standardised processes;
• and automated validation.

Detective controls can include:

• quality checks;
• reconciliations;
• sampling;
• metrics;
• audits;
• and periodic reviews.

Strong systems use the appropriate combination rather than relying exclusively on one control type.

39. Systemic Failure Versus Individual Error

A single human error does not necessarily demonstrate that the pharmacovigilance system is defective.

The investigation should consider whether the error resulted from:

• individual oversight;
• inadequate training;
• unclear instructions;
• excessive workload;
• system design;
• insufficient quality control;
• vendor management;
• or another systemic factor.

Repeated similar errors are particularly important because they can demonstrate that the control environment is not reliably preventing or detecting the failure.

40. Inspection Perspective: Show the System, Not Just the Documents

During an inspection, presenting an SOP may answer the question "What should happen?"

It does not necessarily answer:

• What actually happened?
• How often did it fail?
• How was failure detected?
• What did management do?
• How did the QPPV know?
• Was the corrective action effective?

A strong inspection response therefore connects policy, execution and evidence.

Requirement
    ↓
Procedure
    ↓
Execution
    ↓
Control
    ↓
Exception
    ↓
CAPA
    ↓
Oversight

41. Common Module I Weaknesses

Documented system, weak implementation

The procedures appear comprehensive but operational evidence does not demonstrate consistent execution.

Fragmented responsibilities

Different departments perform parts of the same PV process without a clear end-to-end owner.

Ineffective QPPV escalation

Important issues are technically reported somewhere in the organisation but do not reach the QPPV in a timely or meaningful way.

Vendor oversight based only on contracts

The organisation can demonstrate contractual arrangements but cannot demonstrate effective monitoring of actual performance.

Metrics without action

Performance indicators are reported but deteriorating performance does not trigger investigation or corrective action.

CAPA focused on immediate correction

The organisation corrects the individual event without addressing the underlying systemic cause.

PSMF disconnected from reality

The PSMF describes an older or idealised system rather than the system actually operating.

Training treated as the control

Training is repeatedly assigned instead of addressing process, system or workload problems.

42. A Module I Inspection Exercise

Consider the following scenario.

A vendor repeatedly submits safety information late. The MAH's monthly KPI remains below its escalation threshold because the reporting method averages performance across several activities.

A superficial assessment might conclude that the vendor is performing acceptably.

A stronger Module I assessment asks:

• Are individual serious or time-critical failures being identified separately?
• Is the KPI appropriately designed?
• Is the escalation threshold risk-based?
• Has the QPPV been informed of material failures?
• Are repeated deviations being investigated?
• Has vendor capacity been assessed?
• Has CAPA addressed the root cause?
• Is the effectiveness of CAPA being demonstrated?

The example illustrates why quality-system effectiveness cannot be reduced to one aggregate metric.

43. Building a Module I Self-Assessment

A practical self-assessment can be organised around seven questions:

1. Structure: Is the PV system appropriately organised?
2. Responsibility: Are accountability and interfaces clear?
3. Execution: Are required activities actually performed?
4. Control: Are important failures detected?
5. Correction: Are failures appropriately investigated and corrected?
6. Oversight: Does management and the QPPV receive meaningful information?
7. Effectiveness: Can the organisation demonstrate that controls work?

Evidence should be sampled rather than relying solely on written assertions.

44. Relationship With Other GVP Modules

Module I should not be studied independently.

It provides the system-level foundation for other GVP activities.

Examples include:

• Module II for the pharmacovigilance system master file;
• Module III for inspections;
• Module IV for audits;
• Module V for risk-management systems;
• Module VI for individual case safety reports;
• Module VII for periodic safety reporting;
• Module IX for signal management;
• and Module XVI for risk-minimisation measures.

A weakness in the Module I quality system can therefore manifest as failures in any of these downstream activities.

45. What Good Module I Governance Looks Like

A mature system has a clear relationship between regulatory requirements and operational controls.

The organisation can explain:

What is required?
      ↓
Who is accountable?
      ↓
How is it performed?
      ↓
How is it controlled?
      ↓
What evidence exists?
      ↓
How is failure handled?
      ↓
How does the QPPV know?

The objective is not zero deviations. The objective is a system that identifies meaningful failures, responds proportionately and learns from recurring problems.

46. Key Takeaways

1. GVP Module I provides the system-level foundation for EU pharmacovigilance quality management.
2. The pharmacovigilance system is broader than its SOP library or PSMF.
3. The MAH remains responsible for the effectiveness of its pharmacovigilance system even when activities are outsourced.
4. QPPV oversight depends on timely, reliable and meaningful information rather than personal control of every operational task.
5. Quality indicators are useful but should be interpreted with other quality-system evidence.
6. Preventive and detective controls should be designed around actual failure modes.
7. Repeated individual errors may indicate systemic weaknesses requiring root-cause analysis.
8. Deviations and CAPA should be used to improve the system, not simply to close individual events.
9. Inspection readiness requires evidence that the documented system operates effectively in practice.
10. The PSMF should accurately reflect the pharmacovigilance system that actually exists.
11. Module I connects directly with the other GVP modules; system weaknesses can therefore appear as failures in individual PV activities.
12. Effective Module I governance is demonstrated through traceability from requirement to implementation, control, evidence and QPPV oversight.

References

1. European Medicines Agency. Good Pharmacovigilance Practices (GVP), Module I — Pharmacovigilance systems and their quality systems. Current version and applicable revisions should be consulted for live regulatory use.
2. European Parliament and Council. Directive 2001/83/EC, as amended. Community code relating to medicinal products for human use and EU pharmacovigilance obligations.
3. European Parliament and Council. Regulation (EC) No 726/2004, as amended. Union procedures for authorisation and supervision of medicinal products and relevant pharmacovigilance provisions.
4. European Commission. Commission Implementing Regulation (EU) No 520/2012, as amended. Detailed rules concerning pharmacovigilance activities under the EU pharmaceutical framework.
5. European Medicines Agency. Good Pharmacovigilance Practices — Modules II, III, IV, V, VI, VII, IX and XVI. Related modules providing detailed requirements for connected components of the pharmacovigilance system.
6. European Medicines Agency. Pharmacovigilance post-authorisation and inspection guidance. Current supporting regulatory information and procedural material.

Regulatory Note

This article is an educational and operational interpretation of GVP Module I. It does not reproduce the GVP guideline and does not constitute legal advice.

GVP Module I and the underlying EU legislative framework may be revised. Before using a requirement for a live compliance decision, verify the current GVP version, applicable legislation, effective dates and any transitional provisions.

The precise implementation of a pharmacovigilance quality system should be proportionate to the organisation, products, activities and risks while remaining capable of meeting applicable legal and regulatory requirements. Examples and inspection-oriented scenarios in this article are educational unless an authoritative source is specifically identified.