GVP Module VI: Clinical Trials and ICSR Management

Introduction

Clinical trials generate substantial safety information, but not all clinical-trial safety information is managed through the same pharmacovigilance pathway.

This distinction is fundamental to understanding the relationship between GVP Module VI and the EU clinical-trial safety framework.

A clinical-trial report must first be considered in the context of the regulatory framework under which the trial is conducted. The applicable rules determine what must be reported, by whom, to which system and within what timeframe.

The practical mistake to avoid is treating every adverse event arising in a clinical trial as an ordinary post-authorisation ICSR.

1. The Regulatory Boundary

GVP Module VI historically distinguished clinical trials within the scope of the former Clinical Trials Directive from the post-authorisation pharmacovigilance system.

The EU clinical-trial framework has since transitioned to Regulation (EU) No 536/2014 and the Clinical Trials Information System (CTIS). The current EMA framework requires sponsors to report SUSARs through EudraVigilance, while other clinical-trial safety information follows the applicable Clinical Trials Regulation pathways.

The regulatory framework therefore has to be established before the operational ICSR pathway is selected.

2. Adverse Event, Adverse Reaction and SUSAR

These terms should not be treated as interchangeable.

An adverse event is a clinical occurrence during a clinical trial that does not necessarily have a causal relationship with the investigational medicinal product.

A suspected adverse reaction involves a suspected causal relationship.

A SUSAR is a suspected unexpected serious adverse reaction and is subject to specific clinical-trial reporting requirements.

The classification therefore involves several independent questions:

Clinical event
      ↓
Is a relationship suspected?
      ↓
Is the reaction serious?
      ↓
Is it unexpected according to the applicable reference information?
      ↓
Does the clinical-trial reporting framework require SUSAR reporting?

3. Sponsors and MAHs Have Different Regulatory Roles

The sponsor is responsible for the safety reporting obligations arising from the clinical trial under the Clinical Trials Regulation.

The marketing authorisation holder has pharmacovigilance responsibilities for its authorised medicinal products under the EU pharmacovigilance legislation.

For products and trials that involve both organisations, the interface between these responsibilities must be explicitly governed.

A contract or safety agreement should not obscure the underlying regulatory responsibilities.

4. SUSAR Reporting to EudraVigilance

For clinical trials under the current EU Clinical Trials Regulation, sponsors report SUSARs to EudraVigilance.

EMA describes EudraVigilance as the reporting destination for SUSARs, while other safety information such as unexpected events affecting the benefit-risk balance is handled through CTIS according to the applicable requirements.

This illustrates why "clinical-trial safety information" and "SUSAR" should not be used as synonyms.

5. Post-Authorisation Clinical Trials

A clinical trial can be conducted after a medicinal product has received a marketing authorisation.

The existence of a marketing authorisation does not by itself determine which clinical-trial safety framework applies.

The organisation must establish the legal and procedural framework applicable to the specific study, including whether the trial falls within the Clinical Trials Regulation and what reporting obligations arise from it.

6. Why the Interface Matters to the MAH

Safety information from clinical trials can be relevant to the ongoing benefit-risk evaluation of an authorised medicinal product even when the immediate reporting obligation belongs to the trial sponsor.

The MAH therefore needs appropriate mechanisms to receive and evaluate clinically important safety information that may affect its pharmacovigilance system.

The interface should cover escalation of emerging safety concerns, reconciliation of relevant information and appropriate incorporation of trial information into aggregate safety evaluation.

7. Clinical-Trial Data in the Pharmacovigilance System

Not every clinical-trial adverse event should be copied into the MAH's post-authorisation ICSR database simply because the product is authorised.

The organisation should establish which information must be transferred, which information is relevant to aggregate safety evaluation and which information requires individual-case processing under the applicable pharmacovigilance requirements.

This should be defined prospectively in the safety governance framework.

8. Reference Safety Information

The unexpectedness assessment for a SUSAR depends on the applicable reference safety information for the investigational medicinal product.

The relevant reference document and version should therefore be controlled.

The MAH's authorised-product information and the clinical-trial reference safety information are related but should not be assumed to be identical for every regulatory purpose.

9. Blinding and Unblinding

Clinical trials can generate safety information while treatment assignment remains blinded.

The sponsor should apply the applicable clinical-trial rules governing when unblinding is necessary for safety reporting and ensure that the integrity of the trial is protected while fulfilling safety obligations.

Unblinding should therefore be treated as a controlled safety process rather than an informal case-processing decision.

10. Follow-Up of SUSARs

A SUSAR may require follow-up as additional information becomes available.

The sponsor should have processes for obtaining clinically relevant information, transmitting follow-up information through the applicable reporting pathway and maintaining traceability between the initial and follow-up reports.

Follow-up information may also be relevant to the MAH's broader safety assessment where the medicinal product is authorised.

11. Inspection Perspective

Clinical-trial safety interfaces are particularly vulnerable to organisational ambiguity.

Inspectors may examine whether:

• the sponsor understands its SUSAR obligations;
• safety responsibilities are clearly assigned;
• agreements between sponsor and MAH are operational rather than merely contractual;
• safety information is transferred appropriately;
• reference safety information is controlled;
• follow-up is effective;
• and reconciliation or escalation mechanisms work in practice.

The next chunk will examine the Clinical Trials Regulation in more detail, sponsor/MAH interfaces, SUSAR workflows, post-authorisation trials, safety agreements and difficult clinical-trial scenarios.

11. Clinical-Trial Safety Reporting Under the Current EU Framework

For clinical trials governed by Regulation (EU) No 536/2014, the sponsor has specific safety-reporting responsibilities. Suspected unexpected serious adverse reactions (SUSARs) are reported electronically to EudraVigilance through the clinical-trial reporting pathway.

This is distinct from the MAH's post-authorisation pharmacovigilance responsibilities. The fact that a medicinal product is already authorised does not, by itself, convert every adverse reaction arising in a clinical trial into an ordinary post-authorisation ICSR for processing under GVP Module VI.

EMA describes the clinical-trial reporting framework as covering SUSARs, unexpected events affecting the trial benefit-risk balance, urgent safety measures, serious breaches and annual safety reports. These categories have different reporting pathways and should not be conflated. citeturn0search7turn0search25

12. EudraCT, CTIS and the EudraVigilance Clinical-Trial Pathway

The European clinical-trial systems need to be distinguished carefully because their roles have changed over time.

EudraCT was the EU clinical-trial database established under the earlier clinical-trial framework. With the application of Regulation (EU) No 536/2014, the EU clinical-trial application and supervision framework moved to the Clinical Trials Information System (CTIS). EudraCT therefore remains relevant principally to the legacy clinical-trial population and historical records rather than as the current application system for new EU/EEA trials.

For trials under the current Clinical Trials Regulation, SUSAR reporting is routed through EudraVigilance's clinical-trial functionality (EVCTM). This should not be confused with EVPM, the EudraVigilance module used for post-authorisation individual case safety reports.

The practical architecture is therefore:

CURRENT CLINICAL TRIAL
        │
        ├── SUSAR
        │      ↓
        │    EVCTM
        │
        └── Other reportable trial safety information
               ↓
              CTIS

POST-AUTHORISATION PV ICSR
        │
        ↓
      EVPM

EMA's EudraVigilance documentation distinguishes the clinical-trial and post-authorisation reporting functions. The distinction is important when designing interfaces, training staff and interpreting EudraVigilance data.

13. SUSARs and EudraVigilance

Under the Clinical Trials Regulation, sponsors report SUSARs to EudraVigilance. EMA's current sponsor guidance states that sponsors no longer routinely report SUSARs directly to Member States; EudraVigilance provides the central electronic reporting route, with national rerouting available through the system. citeturn0search25

The clinical-trial reporting pathway therefore has its own regulatory ownership and operational controls.

14. The Role of the Sponsor

The sponsor is responsible for the clinical-trial safety reporting obligations applicable to the trial.

The sponsor must maintain appropriate systems for:

• receiving safety information from investigators and other sources;
• medical assessment;
• determining whether expedited reporting criteria are met;
• maintaining appropriate records;
• submitting SUSARs through the required EudraVigilance pathway;
• and managing follow-up.

EMA's EudraVigilance framework recognises sponsors of clinical trials as distinct reporting stakeholders alongside MAHs and regulatory authorities. citeturn0search1turn0search5

15. The MAH and Sponsor May Be Different Organisations

A medicinal product may have an MAH while the clinical trial is sponsored by another legal entity.

This creates an important governance issue: the organisation responsible for the MAH pharmacovigilance system and the organisation responsible for the clinical trial may have different regulatory roles.

Contracts and safety agreements should therefore clearly define information exchange, escalation, reconciliation and responsibilities where the two organisations interact.

The existence of a safety agreement does not transfer statutory responsibilities that remain with the legally responsible party.

16. Post-Authorisation Clinical Trials

A clinical trial may be conducted after marketing authorisation.

The regulatory status of the product therefore does not, by itself, determine whether the trial safety information is governed by the clinical-trial safety framework.

The former GVP Module VI explicitly illustrated this distinction: certain post-authorisation interventional clinical trials remained within the clinical-trial safety framework rather than being treated as ordinary GVP VI post-marketing ICSRs. citeturn0search23

Under the current EU framework, the applicable Clinical Trials Regulation and the characteristics of the study must be considered rather than relying on the label "post-authorisation" alone.

17. Clinical Trial Versus Non-Interventional Study

The distinction between an interventional clinical trial and a non-interventional post-authorisation study is important.

The regulatory framework, reporting obligations and applicable GVP modules can differ according to the study design and legal classification.

A study should therefore be classified based on its actual design and applicable legislation rather than its commercial or operational name.

18. SUSAR Versus Other Unexpected Events

The Clinical Trials Regulation distinguishes SUSARs from other unexpected events that may affect the benefit-risk balance of a clinical trial.

An unexpected event affecting the trial benefit-risk balance is not simply another name for a SUSAR. EMA specifically identifies these as separate reporting categories with different reporting destinations: SUSARs go to EudraVigilance, while relevant unexpected events are reported through CTIS. citeturn0search7

This distinction is important when designing safety workflows and training personnel.

19. Reference Safety Information

Assessment of whether a suspected adverse reaction is unexpected requires reference to the applicable reference safety information in the clinical-trial framework.

The organisation should therefore maintain appropriate control over the relevant reference information and its version history.

The reference used for a clinical-trial SUSAR assessment should not be assumed to be identical to the reference information used for every post-authorisation pharmacovigilance assessment.

20. Blinding and Unblinding

Clinical-trial safety systems must account for the effect of treatment blinding on safety assessment and reporting.

The applicable regulatory and protocol procedures should determine when unblinding is required or permitted for safety reporting.

The PV and clinical-development functions should have clearly defined interfaces so that safety reporting is not delayed by uncertainty about who may access treatment allocation information.

21. Follow-Up of SUSARs

Follow-up should seek clinically meaningful information that can improve the assessment of the reported reaction and the patient's outcome.

Follow-up systems should maintain traceability between the original report and subsequent information, including material changes to the case.

Where information is exchanged between the sponsor and an MAH, the process should make clear which organisation owns each action and how completion is demonstrated.

22. Reconciliation Between Clinical and PV Systems

Where a sponsor and MAH maintain separate safety databases, reconciliation controls may be necessary.

The purpose is not necessarily to duplicate every record in both systems, but to ensure that information requiring action by the other organisation is transmitted accurately and within the applicable timeframe.

Reconciliation should address, as appropriate:

• case identifiers;
• report dates;
• serious cases;
• SUSAR status;
• follow-up information;
• product and study identifiers;
• and transmission status.

23. Inspection Perspective

Inspectors can examine whether the sponsor's safety system is capable of identifying and reporting SUSARs correctly and whether interfaces with other PV functions are controlled.

Potential evidence includes:

• safety-management procedures;
• investigator reporting processes;
• SUSAR assessment records;
• EudraVigilance transmission records;
• reconciliation records;
• safety agreements;
• training records;
• follow-up documentation;
• and records demonstrating management of significant safety information.

The existence of a written procedure is not sufficient if the organisation cannot demonstrate that the process works in practice.

The next chunk will address difficult clinical-trial scenarios, sponsor/MAH interfaces, post-authorisation studies, inspection failure modes and practical examples.

23. Difficult Scenario: A SUSAR in a Post-Authorisation Trial

A medicinal product may already have a marketing authorisation when it is studied in a clinical trial. That fact does not by itself determine the safety-reporting pathway.

The study's legal and methodological classification must first be established. Where the trial falls under the Clinical Trials Regulation, the sponsor's clinical-trial safety obligations continue to apply, including the applicable SUSAR reporting process.

The MAH should therefore avoid a simplistic rule that every adverse reaction involving an authorised product belongs in EVPM.

24. Difficult Scenario: The Same Product Has Trial and Post-Authorisation Cases

The same medicinal product can generate cases through both clinical-trial and post-authorisation sources.

This does not mean that the two reporting streams should be merged operationally. EVCTM and EVPM serve different regulatory functions, and the source and applicable framework determine the appropriate pathway.

The MAH's global safety system should nevertheless be capable of recognising clinically relevant information across both streams when performing broader safety surveillance.

25. Difficult Scenario: A Trial Is Blinded

A suspected serious reaction may be reported while treatment allocation remains blinded.

The sponsor should follow the applicable regulatory and protocol procedures for maintaining the integrity of the trial while ensuring that safety reporting requirements are met. Unblinding should not be performed simply as an administrative convenience, nor should uncertainty about allocation prevent a report that is required by the applicable rules.

The clinical and safety functions should have predefined responsibilities for these situations.

26. Difficult Scenario: Pregnancy in a Clinical Trial

Pregnancy occurring during a clinical trial requires assessment under the applicable clinical-trial safety framework and protocol requirements.

The information should not automatically be treated as a SUSAR merely because pregnancy occurred. The sponsor should assess the circumstances and any adverse pregnancy outcome against the applicable reporting criteria.

EMA's clinical-trial Q&A also distinguishes collection of pregnancy and medication-error information from expedited SUSAR reporting and emphasises assessment of associated harm or adverse outcomes. citeturn0search23

27. Difficult Scenario: Medication Error or Misuse in a Trial

Medication errors, misuse, abuse and uses outside the protocol can occur in clinical trials.

The sponsor should collect and assess these circumstances according to the Clinical Trials Regulation and applicable guidance. They should not automatically be treated as SUSARs solely because the exposure circumstance occurred.

Where a serious adverse outcome occurs and the relevant expedited reporting criteria are met, the event may require SUSAR reporting. The distinction between the medication-use circumstance and the clinical consequence should remain explicit.

28. Difficult Scenario: Unexpected Event Affecting the Benefit-Risk Balance

An unexpected event may affect the benefit-risk balance of the trial without being a SUSAR.

Examples can include an unexpected increase in the incidence of serious adverse reactions that are themselves expected, or new information that changes the safety assessment of the investigational medicinal product.

Such information follows the applicable CTIS pathway rather than being automatically converted into a SUSAR report. EMA explicitly identifies unexpected events affecting the trial benefit-risk balance as a reporting category separate from SUSARs. citeturn0search0

29. Difficult Scenario: Clinical-Trial Case Also Relevant to the MAH

A SUSAR may contain information that is important to the MAH's wider safety evaluation of an authorised product.

The existence of the clinical-trial reporting pathway does not remove the need for appropriate information exchange where the MAH needs the information for its pharmacovigilance responsibilities.

The parties should define how relevant information is transferred, reconciled and incorporated into the broader safety assessment without creating inappropriate duplicate regulatory submissions.

30. Difficult Scenario: Sponsor Uses a CRO

A sponsor may delegate operational activities to a contract research organisation.

Delegation of tasks does not eliminate the sponsor's regulatory responsibilities. The sponsor should maintain appropriate oversight of the CRO's safety activities, including training, case handling, reporting, reconciliation, quality management and inspection readiness.

The safety agreement should identify responsibilities clearly enough that a failure cannot be attributed merely to an ambiguous division of work.

31. Inspection Failure Mode: Unclear Sponsor–MAH Interface

A weak interface may result in uncertainty about who receives a report, who assesses it, who submits it and who performs follow-up.

An inspection-ready system should be able to demonstrate the complete information flow from source to regulatory submission and subsequent follow-up.

32. Inspection Failure Mode: Confusing EVCTM and EVPM

The distinction between the clinical-trial and post-authorisation EudraVigilance modules is not merely technical.

EMA describes EVCTM as the module dedicated to SUSARs from clinical trials and EVPM as the module dedicated to post-authorisation ICSRs. citeturn0search1

Incorrect classification can indicate weaknesses in regulatory understanding, database configuration, training or oversight.

33. Inspection Failure Mode: Weak Reconciliation

Where multiple systems are involved, inspectors may expect evidence that safety information is transferred completely and accurately.

A reconciliation process should have a defined scope, frequency, ownership, investigation process and documented resolution of discrepancies.

A spreadsheet showing that reconciliation was performed is not sufficient if unexplained discrepancies remain unresolved.

34. Inspection Failure Mode: Treating Procedures as Evidence of Effectiveness

A sponsor or MAH may have detailed written procedures but still be unable to demonstrate that they work.

Useful evidence includes actual case records, submission acknowledgements, reconciliation results, training records, deviation records, CAPA and quality-control results.

35. Current-System Considerations

The EU clinical-trial environment is now predominantly governed by the Clinical Trials Regulation and CTIS. EMA states that, from 31 January 2025, new EU/EEA clinical-trial applications and modifications are handled through CTIS, while EudraCT remains relevant for legacy functions and certain third-country files. citeturn0search3

This makes version-aware procedures essential. A procedure that simply says "submit clinical-trial cases to EudraCT" is not adequate for the current system.

36. Practical Governance Model

A robust governance model should define at least:

Investigator / trial source
          ↓
Clinical-trial safety function
          ↓
Medical assessment
          ↓
SUSAR determination
          ↓
EVCTM submission where applicable
          ↓
Sponsor oversight / reconciliation
          ↓
MAH interface where relevant
          ↓
Broader safety evaluation

Separately, post-authorisation sources follow the applicable EVPM pathway.

The exact organisational allocation of tasks can vary, but regulatory accountability and interfaces should remain clear.

37. What Good Looks Like

A mature system:

• correctly classifies the study and applicable regulatory framework;
• distinguishes SUSARs from other trial safety information;
• distinguishes EVCTM from EVPM;
• maintains current CTIS and EudraVigilance processes;
• clearly allocates sponsor, CRO and MAH responsibilities;
• controls blinded and unblinded safety information;
• reconciles relevant systems;
• maintains evidence of reporting and follow-up;
• and can demonstrate effective operation during inspection.

38. Final Principles

1. A clinical-trial case is not automatically a post-authorisation ICSR merely because the product is authorised.
2. Current EU clinical trials are governed principally through the Clinical Trials Regulation and CTIS.
3. SUSARs are reported to EudraVigilance through the clinical-trial pathway.
4. EVCTM and EVPM serve different regulatory purposes.
5. EudraCT is now principally a legacy system for EU/EEA trials, with limited continuing functions.
6. SUSARs and unexpected events affecting the trial benefit-risk balance are distinct reporting categories.
7. Sponsor, CRO and MAH responsibilities must be clearly defined.
8. Delegating operational activities does not eliminate the sponsor's regulatory accountability.
9. Reconciliation and traceability are important controls where systems and organisations interact.
10. Current, version-controlled procedures are essential because the EU clinical-trial infrastructure has changed substantially.

Key Takeaways

Clinical-trial pharmacovigilance in the EU requires understanding both the regulatory framework and the system architecture. The central distinction is not simply "clinical trial versus post-marketing"; it is the applicable legal framework, study classification, safety-information category and corresponding reporting pathway.

For current EU trials, CTIS is the clinical-trial application and supervision system, while SUSARs are reported to EudraVigilance through the clinical-trial reporting pathway. EVPM remains the post-authorisation ICSR module. EudraCT should be treated primarily as a legacy system in the EU/EEA context. citeturn0search0turn0search1turn0search3

References

1. European Parliament and Council. Regulation (EU) No 536/2014 on clinical trials on medicinal products for human use.
2. European Medicines Agency. Reporting safety information on clinical trials under the Clinical Trials Regulation.
3. European Medicines Agency. EudraVigilance system overview — EVPM and EVCTM.
4. European Medicines Agency. Clinical Trials Information System (CTIS) — Sponsor Handbook and current implementation guidance.
5. European Medicines Agency. EudraCT — current status and transition to CTIS.
6. European Commission. EudraLex Volume 10 — Clinical trials guidelines and questions and answers, where applicable to the relevant trial framework.
7. European Medicines Agency. Questions and answers on CTIS and the Clinical Trials Regulation — safety/SUSAR topics.
8. European Medicines Agency. Good Pharmacovigilance Practices (GVP), Module VI — Collection, management and submission of reports of suspected adverse reactions to medicinal products, including the applicable clinical-trial interface provisions.

Regulatory Note

This article distinguishes the current Clinical Trials Regulation framework from the legacy Directive 2001/20/EC/EudraCT framework. Clinical-trial safety requirements and EudraVigilance functionality have evolved over time; procedures should therefore be maintained against the current applicable legislation and EMA implementation guidance.

The distinction between EVCTM and EVPM is a system and regulatory distinction. It should not be interpreted as meaning that information received through clinical-trial safety processes is irrelevant to the MAH's broader pharmacovigilance system. Appropriate information exchange and safety evaluation may still be required according to the applicable responsibilities and arrangements.

The practical examples in this article are illustrative and are not presented as descriptions of specific inspection cases unless an authoritative source is expressly identified.