What Are EU Good Pharmacovigilance Practices (GVP)?

Introduction

Good Pharmacovigilance Practices, usually abbreviated GVP, are the European Union framework of guidance describing how pharmacovigilance should be conducted for medicines for human use.

GVP is not a single standard operating procedure and it is not a single document. It is a structured body of guidance covering the organisation, processes, systems and activities needed to monitor and manage the safety of medicines throughout their lifecycle.

For a marketing authorisation holder, GVP provides a practical framework for translating the legal pharmacovigilance obligations in EU medicines legislation into an operational pharmacovigilance system.

A useful way to understand the relationship is:

EU pharmaceutical legislation
          ↓
Legal pharmacovigilance obligations
          ↓
Good Pharmacovigilance Practices
          ↓
Company pharmacovigilance system
          ↓
SOPs / processes / systems / controls
          ↓
Operational evidence

The hierarchy matters. GVP guidance should not be treated as though every sentence creates a new statutory obligation independent of the underlying legislation. At the same time, GVP is highly important in regulatory practice because it explains how the EU pharmacovigilance framework is expected to operate.

1. Why GVP Exists

Medicinal products are used in populations much larger and more diverse than those normally studied before marketing authorisation.

Pre-authorisation clinical development provides important evidence about safety, but it cannot identify every adverse reaction, interaction, risk factor or long-term outcome that may emerge during widespread use.

Pharmacovigilance therefore continues after authorisation.

GVP provides a common European framework for activities such as:

• collection and management of safety information;
• individual case safety report management;
• signal management;
• risk management;
• periodic safety evaluation;
• additional monitoring;
• safety communication;
• pharmacovigilance system quality management;
• and oversight of the pharmacovigilance system.

The objective is not simply to collect adverse-event reports. The objective is to maintain an effective system capable of identifying, evaluating and responding to information that may change the benefit-risk balance of a medicine.

2. GVP Is a Framework, Not a Single Procedure

A common misunderstanding is to refer to "the GVP procedure" as though GVP were one operational process.

It is better understood as a collection of related modules and annexes addressing different aspects of pharmacovigilance.

The framework includes major topics such as:

The framework should therefore be read selectively according to the pharmacovigilance question being addressed.

3. The Legal Foundation

The EU pharmacovigilance system is established primarily through EU pharmaceutical legislation, including Directive 2001/83/EC and Regulation (EC) No 726/2004, as amended.

GVP was developed to provide guidance on the practical implementation of the pharmacovigilance requirements established in that legal framework.

This distinction is important when assessing compliance.

A regulatory professional should ask two separate questions:

1. What does the applicable law require?
2. How does current GVP guidance explain or operationalise that requirement?

The answer to the first question establishes the legal obligation. The answer to the second helps determine how the pharmacovigilance system should be designed and operated in the EU regulatory environment.

4. Who Uses GVP?

GVP is relevant to multiple organisations and functions.

The most obvious user is the marketing authorisation holder (MAH), because the MAH is responsible for operating an appropriate pharmacovigilance system for its authorised medicinal products.

However, GVP is also highly relevant to:

• QPPVs;
• pharmacovigilance physicians;
• case-processing teams;
• signal-management teams;
• safety scientists;
• regulatory affairs professionals;
• quality and compliance functions;
• auditors;
• inspectors;
• vendors providing PV services;
• and organisations supporting clinical or post-authorisation activities.

The same GVP requirement can therefore appear differently from the perspective of a system owner, an operational user, an auditor and an inspector.

5. GVP and the QPPV

The QPPV occupies a central position in the EU pharmacovigilance system.

The QPPV is responsible for establishing and maintaining oversight of the pharmacovigilance system in accordance with the applicable legal requirements.

GVP provides important practical context for that responsibility.

A QPPV should therefore understand not only individual GVP modules but also how they interact.

For example:

Safety information
       ↓
Case management / other data sources
       ↓
Signal management
       ↓
Risk evaluation
       ↓
Risk management
       ↓
Regulatory action
       ↓
Updated PV system

A mature QPPV does not manage these activities as isolated compliance silos. The value of GVP is partly in showing how the elements form an integrated pharmacovigilance system.

6. GVP and the Pharmacovigilance System

The pharmacovigilance system is the organisational structure through which pharmacovigilance activities are performed and controlled.

It includes people, processes, responsibilities, systems, data, quality controls and governance arrangements.

The system should be capable of performing the required activities consistently and should provide evidence that those activities have been performed appropriately.

This is why GVP compliance cannot be demonstrated merely by having a library of SOPs.

An organisation may have excellent written procedures but still have a deficient pharmacovigilance system if the procedures are not implemented effectively, responsibilities are unclear, data are unreliable or required activities are not performed on time.

7. GVP and the PSMF

The Pharmacovigilance System Master File (PSMF) provides an important source of documented information about the pharmacovigilance system.

It describes the system and its key components, allowing the organisation and authorities to understand how the pharmacovigilance system is structured and controlled.

The PSMF should not be confused with the entire pharmacovigilance system.

The distinction is:

Pharmacovigilance system = actual system
PSMF = controlled description/evidence of that system

The PSMF is therefore one important component of GVP compliance, not a substitute for effective operational control.

8. GVP and Quality Management

GVP places strong emphasis on quality.

Quality in pharmacovigilance is not limited to the accuracy of individual case reports. It includes the ability of the system to consistently perform required activities, identify deviations and correct problems.

Important elements include:

• defined responsibilities;
• documented processes;
• training and qualification;
• quality controls;
• quality assurance;
• deviation management;
• CAPA;
• audit;
• inspection readiness;
• and management oversight.

The practical question is not merely whether a procedure exists, but whether the system reliably produces the intended outcome.

9. GVP and Proportionality

Not every pharmacovigilance system has exactly the same operational complexity.

The size and complexity of the system can depend on factors such as:

• number of products;
• geographic scope;
• product characteristics;
• risk profile;
• number and complexity of vendors;
• data sources;
• organisational structure;
• and the range of pharmacovigilance activities required.

A small organisation and a multinational MAH may therefore use very different operational architectures while both maintaining systems designed to meet the applicable requirements.

The important principle is that proportionality should not become an excuse for omitting a required activity.

10. GVP and Outsourcing

Many MAHs outsource significant portions of pharmacovigilance operations.

GVP does not make outsourcing equivalent to transferring regulatory responsibility.

A vendor may perform case processing, literature monitoring, signal detection, aggregate reporting or other activities, but the MAH remains responsible for ensuring that its pharmacovigilance system is appropriately controlled.

This requires effective oversight of:

• vendor qualification;
• contracts and safety data exchange arrangements;
• service levels;
• quality controls;
• deviations;
• CAPA;
• audit;
• performance monitoring;
• and escalation.

The principle is simple:

An outsourced activity remains part of the MAH's pharmacovigilance system.

11. GVP and Inspection Readiness

GVP is particularly important during pharmacovigilance inspections because inspectors assess not only whether the organisation knows the requirements but whether the system actually operates effectively.

Typical inspection questions may include:

• Who is responsible for this activity?
• What procedure governs it?
• How do you know the procedure is followed?
• What quality control exists?
• What happens when the process fails?
• How are deviations identified?
• How are CAPAs managed?
• How does the QPPV obtain oversight?
• What evidence demonstrates that the activity is effective?

This means that GVP knowledge should ultimately translate into inspectable evidence.

12. How to Read a GVP Module

A useful reading method is to avoid treating a GVP module as text that must simply be memorised.

Instead, identify five layers:

1. Scope — what activity or system component does the module address?
2. Expectation — what should the MAH or other party achieve?
3. Control — what process, system or governance mechanism makes the expectation reliable?
4. Evidence — what records demonstrate that the requirement is being met?
5. Inspection risk — what could an inspector challenge if the system is weak?

For example, a statement about timely case processing should lead to questions about workflow, responsibility, timestamps, quality controls, backlog management and escalation rather than simply being copied into an SOP.

13. GVP Is Best Used as an Operating Framework

The most useful way to use GVP is to translate it into operational questions.

For every important requirement, ask:

What must we achieve?
        ↓
Who is accountable?
        ↓
What process achieves it?
        ↓
What system/data supports it?
        ↓
What control verifies it?
        ↓
What evidence proves it?
        ↓
What happens when it fails?

This approach is particularly useful for QPPV oversight, audits and inspections.

The next chunk will map the current GVP structure in more detail, explain how to navigate modules and annexes, and distinguish guidance from the underlying legal requirements.

14. How the GVP Framework Is Organised

The GVP framework is organised into modules and annexes addressing different pharmacovigilance activities and system components.

The module structure is useful because it allows a user to identify the relevant part of the framework without treating GVP as one undifferentiated document.

The major modules address areas including:

• pharmacovigilance systems and their quality systems;
• the Qualified Person responsible for pharmacovigilance;
• pharmacovigilance inspections;
• pharmacovigilance audits;
• risk-management systems;
• collection, management and submission of individual safety reports;
• periodic safety reporting;
• signal management;
• additional monitoring;
• safety communication;
• and post-authorisation safety studies.

The framework also contains annexes that provide more specialised guidance and definitions.

15. Modules and Annexes Have Different Purposes

A module normally addresses a broad pharmacovigilance topic and explains the principles and expectations applicable to that topic.

An annex may provide more focused guidance, such as definitions, methodological detail or requirements associated with a specific activity or population.

The distinction is useful when designing a compliance framework.

A company should not assume that a requirement found in an annex is less important because the document is shorter or more specialised. Conversely, not every explanatory sentence should automatically be converted into a rigid internal control without considering its legal and operational context.

16. GVP Should Be Read With the Current Legislation

GVP should be read alongside the underlying EU legislation and not in isolation.

The principal legislative framework includes Directive 2001/83/EC and Regulation (EC) No 726/2004, together with subsequent amendments and other applicable EU legislation.

The practical hierarchy is important:

Applicable EU legislation
        ↓
Legally binding obligation
        ↓
GVP guidance
        ↓
Scientific / operational interpretation
        ↓
Company implementation

This does not mean that GVP is optional or merely informative in day-to-day compliance. It means that the legal basis of a requirement should be understood correctly.

17. How to Interpret GVP Language

When reading GVP, attention should be paid to the language used to express an expectation.

Terms such as should, expected, must, required, appropriate, proportionate and where applicable can have important contextual meaning.

The reader should therefore avoid extracting isolated sentences and treating them as universal rules.

A better method is to read the statement together with:

• its surrounding section;
• the scope of the module;
• definitions;
• applicable legislation;
• related GVP modules;
• relevant EMA or Commission guidance;
• and the circumstances of the product and pharmacovigilance system.

This is particularly important when translating GVP into SOP language.

18. Turning GVP Into Internal Requirements

A GVP requirement should normally pass through an interpretation step before it becomes an internal procedure.

For example:

GVP expectation
      ↓
Regulatory interpretation
      ↓
Internal requirement
      ↓
Process design
      ↓
SOP / work instruction
      ↓
System control
      ↓
Evidence

This prevents two opposite errors.

The first is under-implementation, where a general GVP expectation is not translated into an effective operational control.

The second is over-engineering, where an organisation creates unnecessary controls because a sentence has been interpreted more rigidly than the regulatory context requires.

19. What Inspectors Usually Care About

An inspection is rarely satisfied by showing that employees can locate the correct GVP paragraph.

Inspectors are interested in whether the pharmacovigilance system actually works.

For a requirement concerning timeliness, for example, an inspector may want evidence of:

• defined timelines;
• system timestamps;
• monitoring;
• escalation;
• deviations;
• root-cause analysis;
• CAPA;
• management oversight;
• and evidence that repeated failures are addressed.

The practical inspection question is often:

How do you know that your system consistently achieves the required outcome?

20. GVP and Evidence

Every major pharmacovigilance process should produce evidence appropriate to its importance.

Examples include:

The precise evidence depends on the activity and system architecture.

21. GVP and Computerised Systems

Modern pharmacovigilance depends heavily on computerised systems.

Case-management systems, signal-management tools, document systems, databases, safety-data exchanges and reporting platforms can all affect compliance.

GVP expectations therefore need to be implemented in a way that recognises system controls, data integrity, access management, audit trails, validation and change control where applicable.

A process can be procedurally compliant on paper while remaining vulnerable if the supporting system cannot reliably demonstrate what happened, when it happened and who performed the activity.

22. GVP and Data Quality

Good pharmacovigilance depends on reliable data.

Data quality concerns can arise at many points:

Source
  ↓
Collection
  ↓
Data entry
  ↓
Processing
  ↓
Coding / classification
  ↓
Analysis
  ↓
Regulatory reporting
  ↓
Decision-making

An error introduced early in the chain can affect downstream safety analysis.

Consequently, GVP compliance should not be assessed only at the final reporting step. Data quality controls should be considered throughout the process.

23. GVP and Metrics

Metrics can provide evidence that a process is operating effectively, but a metric is not itself proof of compliance.

For example, a high percentage of cases processed within the target timeline is useful information, but it may not reveal:

• quality problems;
• inappropriate exclusions;
• repeated manual workarounds;
• data-quality failures;
• or weaknesses in case triage.

Good pharmacovigilance governance therefore uses metrics together with quality indicators, audits, deviations, complaints, inspection findings and other evidence.

24. GVP and Management Oversight

Pharmacovigilance is not only an operational function.

Management needs sufficient information to understand whether the system is functioning effectively and whether material risks or resource constraints require intervention.

The QPPV and relevant governance bodies should therefore have access to information that permits meaningful oversight.

This can include:

• significant compliance deviations;
• serious or repeated quality failures;
• overdue activities;
• material vendor issues;
• important audit findings;
• inspection findings;
• emerging safety concerns;
• and significant resource or system limitations.

25. GVP and Vendors

Where pharmacovigilance activities are outsourced, the relevant GVP expectations remain part of the MAH's system requirements.

The organisation should be able to demonstrate not only that a vendor has a contract but that the outsourced process is actually controlled.

Useful evidence may include:

• qualification records;
• contracts and safety-data exchange agreements;
• service-level monitoring;
• quality reviews;
• reconciliations;
• audit results;
• CAPA records;
• issue escalation;
• and governance meetings.

The inspection question is not simply "Do you have a vendor?" but "How do you know the outsourced activity is performing as required?"

26. GVP and Deviations

A mature system assumes that failures will occasionally occur.

The presence of a deviation does not automatically demonstrate that the pharmacovigilance system is ineffective.

The important questions are whether the deviation was:

• detected promptly;
• assessed for impact;
• appropriately contained;
• investigated where necessary;
• corrected;
• followed by proportionate CAPA;
• and monitored for recurrence.

Repeated deviations of the same type can indicate a systemic weakness even when individual deviations have been closed.

27. GVP and CAPA

Corrective and preventive action should address the underlying cause rather than merely close the immediate event.

For example, if cases repeatedly miss a reporting deadline, retraining staff may not be sufficient if the underlying cause is an inadequate workflow, unclear responsibility or system configuration problem.

A strong CAPA assessment asks:

What failed?
   ↓
Why did it fail?
   ↓
Why did existing controls not detect/prevent it?
   ↓
What change will prevent recurrence?
   ↓
How will effectiveness be verified?

This approach connects GVP quality principles with practical system improvement.

28. GVP and Continuous Improvement

The pharmacovigilance system should evolve as products, evidence, technology, vendors, organisational structures and regulatory expectations change.

Continuous improvement does not mean changing procedures continuously without justification.

It means using appropriate evidence to identify where the existing system is no longer sufficiently effective or efficient and making controlled improvements.

Sources for improvement can include:

• audit findings;
• inspection findings;
• deviations;
• CAPA effectiveness reviews;
• metrics and quality indicators;
• vendor performance;
• new guidance;
• regulatory changes;
• and lessons learned from safety events.

29. A Practical GVP Compliance Model

For each major GVP expectation, an organisation can maintain a simple chain:

This model will be used throughout the subsequent GVP article series.

30. How This Article Series Will Use GVP

The articles in this section will not simply reproduce GVP modules in shorter form.

Each article will focus on what a pharmacovigilance professional needs to understand, implement, monitor and defend during an inspection.

Where appropriate, each article will cover:

1. the purpose and scope of the relevant GVP section;
2. the underlying legal context;
3. the important requirements;
4. practical implementation;
5. roles and responsibilities;
6. systems and data considerations;
7. quality controls and metrics;
8. QPPV oversight;
9. common failure modes;
10. inspection findings and inspection questions;
11. relevant GVP annexes and related guidance;
12. associated FAQs where authoritative material exists;
13. practical learning examples;
14. and cross-references to related QPPV.com articles.

This approach should make the GVP section useful as a working knowledge base rather than a simple regulatory summary.

31. Why the GVP Modules Should Be Studied Together

Although the modules are organised by topic, the underlying pharmacovigilance system is integrated.

A signal can originate from individual cases, literature, studies or other sources. The signal can change the safety specification, which can affect the RMP and aggregate reporting, which can ultimately result in regulatory action and changes to the product information.

Similarly, an inspection finding concerning one activity may reveal weaknesses elsewhere in the system.

Understanding these connections is therefore as important as understanding individual modules.

32. The Most Important Practical Question

The most useful question when studying GVP is not:

"What does this paragraph say?"

It is:

"What would I need to build, monitor and demonstrate in a real pharmacovigilance system to show that this expectation is being met?"

That question turns regulatory text into operational knowledge.

The final chunk will provide a consolidated map of the GVP framework, explain how to use the subsequent articles, identify the most important inspection and implementation themes, and provide References and the Regulatory Note.

33. A Practical Map of the GVP Framework

The GVP framework is easiest to use when its components are viewed as parts of one pharmacovigilance system rather than as independent regulatory subjects.

A simplified map is:

                    Pharmacovigilance system
                              │
          ┌───────────────────┼───────────────────┐
          │                   │                   │
       Quality              QPPV              Risk management
          │                   │                   │
      Audits /           Oversight          Safety specification
      inspections                               │
          │                                     ↓
          └──────────────→ Safety activities ←──┘
                              │
            ┌─────────────────┼─────────────────┐
            ↓                 ↓                 ↓
       Individual cases    Signals        Aggregate reports
            │                 │                 │
            └─────────────────┼─────────────────┘
                              ↓
                       Benefit-risk review
                              ↓
                    Regulatory action / safety
                       communication

The individual GVP modules provide the detailed expectations within this overall architecture.

34. How to Navigate GVP Efficiently

A regulatory professional does not normally need to read the entire GVP framework from beginning to end every time a question arises.

A more efficient approach is to start with the regulatory question.

For example:

The relevant module should then be read together with linked legislation and related GVP sections.

35. GVP Cross-References Matter

A requirement rarely exists in isolation.

For example, a safety signal can involve individual case processing, data quality, signal management, risk management, periodic reporting and regulatory communication.

When a GVP module points to another module, that cross-reference is often important to understanding the complete requirement.

The subsequent QPPV.com GVP articles will therefore include explicit cross-references rather than treating each module as a standalone topic.

36. Inspection Findings as a Learning Tool

Published or otherwise authoritative inspection findings can be particularly valuable when studying GVP because they show how apparently simple requirements fail in real systems.

A useful learning structure is:

GVP expectation
      ↓
Observed control weakness
      ↓
Inspection finding
      ↓
Potential patient / regulatory impact
      ↓
Root cause
      ↓
Corrective action
      ↓
Preventive control

Inspection findings should not be copied into a company's risk register simply because another organisation received the finding. They should be used to test whether an equivalent weakness could exist in the local system.

37. FAQs and Learning Examples

Where EMA, European Commission, CMDh or another authoritative EU source publishes a relevant FAQ or clarification, it can provide useful context for interpreting the GVP framework.

However, FAQs should be treated according to their source and status. An FAQ should not automatically be treated as equivalent to legislation.

Similarly, worked examples in the QPPV.com articles will be clearly identified as educational examples rather than regulatory precedents unless they are based on a published regulatory case.

38. GVP and Regulatory Change

GVP itself evolves.

Changes in legislation, scientific knowledge, regulatory experience and pharmacovigilance practice can result in revisions, addenda, updated guidance or changes to related regulatory documents.

A pharmacovigilance system should therefore have an appropriate process for regulatory intelligence and assessment of changes affecting its activities.

The key question is not simply:

"Have we read the new GVP document?"

It is:

"What changed, when does it apply, what activities are affected, and what evidence demonstrates that our system has adapted appropriately?"

39. Regulatory Change Impact Assessment

A practical impact assessment can examine:

1. the new or revised requirement;
2. applicable effective or implementation date;
3. affected products and procedures;
4. affected processes;
5. affected systems and data;
6. affected vendors;
7. training implications;
8. documentation changes;
9. quality-control implications;
10. and required verification.

This creates a bridge between regulatory intelligence and operational compliance.

40. What GVP Compliance Looks Like in Practice

A strong pharmacovigilance system should be able to demonstrate four things.

1. Understanding

The organisation understands the applicable regulatory expectations and their legal context.

2. Implementation

The expectations have been translated into appropriate processes, systems and responsibilities.

3. Control

The organisation monitors whether the processes are operating effectively.

4. Evidence

The organisation can demonstrate what happened, when it happened, who was responsible and how problems were addressed.

This can be represented as:

Understand → Implement → Control → Demonstrate

Failure at any one stage can create a compliance weakness.

41. What This Means for a QPPV

For the QPPV, GVP should ultimately support a defensible answer to one question:

Can I demonstrate that the pharmacovigilance system is capable of identifying, evaluating, communicating and managing safety information in accordance with applicable EU requirements?

That requires system-level oversight rather than detailed personal control of every operational activity.

The QPPV should be able to identify material weaknesses, understand their impact, ensure appropriate escalation and confirm that corrective action is effective.

42. What This Means for an Inspector

From an inspector's perspective, the same system can be examined from the opposite direction.

An inspector may start with an outcome and work backwards:

Regulatory outcome
      ↑
Decision / assessment
      ↑
Analysis
      ↑
Data
      ↑
Process
      ↑
System controls
      ↑
Governance

This is why traceability matters so much in pharmacovigilance.

A system should not merely produce a conclusion. It should be possible to reconstruct how the conclusion was reached and whether the underlying process was controlled.

43. The GVP Section on QPPV.com

The planned GVP section will progressively examine the framework at both module level and, where useful, subsection level.

The articles will deliberately avoid simply reproducing GVP text. Each article will explain what the requirement means operationally, how it can be implemented, what evidence should exist and what weaknesses are likely to attract regulatory attention.

The series will also cross-reference existing QPPV.com articles where those articles already cover a related subject in depth.

This should prevent unnecessary duplication while allowing GVP-specific analysis to remain focused on the regulatory source.

44. Final Takeaways

1. GVP is a structured EU pharmacovigilance guidance framework, not a single SOP or procedure.
2. The underlying legal obligations come from EU pharmaceutical legislation; GVP provides important guidance on implementation and good practice.
3. GVP should be interpreted in context and with the applicable legislation and current regulatory guidance.
4. Compliance means more than possessing SOPs: the system must operate effectively and generate appropriate evidence.
5. The QPPV's role is system-level pharmacovigilance oversight, supported by effective governance and escalation.
6. Outsourcing activities does not remove the MAH's responsibility for its pharmacovigilance system.
7. Data, computerised systems, quality management, metrics, vendors and CAPA are all part of practical GVP implementation.
8. Inspection readiness depends on demonstrating outcomes and traceability, not merely knowing the wording of GVP.
9. GVP modules and annexes should be read as connected components of one pharmacovigilance system.
10. Regulatory changes should be assessed for their operational impact rather than simply acknowledged.
11. Inspection findings and authoritative FAQs are valuable learning resources when their status and context are understood correctly.
12. The most useful way to study GVP is to translate each important expectation into implementation, control, evidence and oversight questions.

References

1. European Parliament and Council. Directive 2001/83/EC, as amended. Community code relating to medicinal products for human use and the principal legal framework for EU pharmacovigilance requirements.
2. European Parliament and Council. Regulation (EC) No 726/2004, as amended. Establishes Union procedures for the authorisation and supervision of medicinal products and relevant pharmacovigilance responsibilities.
3. European Medicines Agency. Good Pharmacovigilance Practices (GVP). Current GVP modules, annexes and related guidance for human medicines.
4. European Medicines Agency. Pharmacovigilance: post-authorisation. Current regulatory information concerning EU pharmacovigilance and GVP.
5. European Commission. Commission Implementing Regulation (EU) No 520/2012, as amended. Detailed rules concerning pharmacovigilance activities provided for in Regulation (EC) No 726/2004 and Directive 2001/83/EC.
6. European Medicines Agency. Pharmacovigilance inspection guidance and related materials. Current information relevant to inspection of pharmacovigilance systems.

Regulatory Note

This article is an educational introduction to the EU Good Pharmacovigilance Practices framework. It does not reproduce the GVP guidelines and does not constitute legal advice.

GVP should always be consulted in its current version together with the applicable EU legislation and other current regulatory guidance. Where legislation, a legally operative regulatory decision and guidance appear to differ in legal effect, the applicable legislation and legally operative decision take precedence.

The GVP framework is subject to revision. Readers should verify the current version, effective dates, transitional arrangements and applicable scope before using any requirement to make a live regulatory or compliance decision.

Inspection findings and examples discussed in this series will be identified according to their source. Educational examples should not be interpreted as regulatory precedents unless the underlying authoritative source is explicitly identified.