GVP Module VI: Follow-Up of Individual Case Safety Reports

Explains why follow-up is performed, how cases should be identified and prioritised, and how targeted follow-up can improve the scientific value of an ICSR without creating unnecessary burden.

Audio Lesson 15 min
Knowledge Assessment Test your understanding of this article. Take the assessment →

GVP Module VI: Follow-Up of Individual Case Safety Reports

Introduction

An individual case safety report rarely contains every piece of information that would be useful for pharmacovigilance assessment. A report may establish the minimum requirements for a valid ICSR while leaving important questions about the clinical course, diagnosis, exposure, concomitant medicines, medical history, outcome or causal relationship unanswered.

Follow-up is the controlled process of attempting to obtain additional information that can improve the scientific evaluation and management of the case.

The objective is not to make every case complete at any cost. Effective follow-up is purposeful, proportionate and documented. The organisation should be able to explain why additional information was sought, what information was prioritised, how the request was made and what happened when further information could not be obtained.

GVP Module VI places follow-up within the management of suspected adverse reactions. Current ICH E2D(R1) also provides the international framework for post-authorisation ICSR management. The practical implementation must therefore distinguish regulatory requirements from organisation-specific procedures and quality controls.

1. Why Follow-Up Matters

Additional information can materially change the interpretation of an ICSR.

For example, an initial report may state only:

Patient developed severe liver injury after starting Product X.

Follow-up may establish:

The additional information may strengthen, weaken or otherwise change the clinical interpretation.

2. A Valid Case Is Not Necessarily a Complete Case

This distinction is fundamental.

The organisation should not invalidate a report merely because clinically useful information is missing when the applicable minimum criteria for an ICSR are already satisfied.

Instead:

Minimum criteria satisfied
          ↓
Valid ICSR
          ↓
Identify important missing information
          ↓
Assess whether follow-up could add value
          ↓
Prioritise and attempt follow-up

The purpose of follow-up is therefore to improve the case, not to retrospectively create validity where none existed.

3. What Should Follow-Up Try to Establish?

The questions should be driven by the information needed for meaningful assessment.

Depending on the case, useful information may include:

Not every case requires every item.

4. Follow-Up Should Have a Defined Objective

A useful follow-up request starts with a question:

What uncertainty are we trying to resolve?

For example:

Case uncertainty Potential follow-up objective
Diagnosis unclear Obtain diagnostic findings and physician assessment
Seriousness uncertain Establish hospitalisation, disability, life-threatening status or other applicable criterion
Fatal case Establish circumstances, cause and relevant medical findings
Causality uncertain Obtain chronology, dechallenge/rechallenge and alternative causes
Outcome unknown Determine current clinical status
Reaction poorly described Obtain symptoms, diagnosis and objective findings
Exposure unclear Confirm product, dose, route and dates

This approach is preferable to sending the same lengthy questionnaire for every case.

5. Which Cases Should Be Considered for Follow-Up?

All valid cases should enter a controlled process, but not all cases necessarily warrant the same intensity of follow-up.

Factors that may increase the value or priority of follow-up include:

The organisation should define its prioritisation methodology in controlled procedures.

6. Filtering the Case Population

A practical system can use structured criteria to identify cases that require consideration for follow-up.

For example:

All valid ICSRs
       ↓
Critical information missing?
       ↓
Yes ───────────── No
 ↓                  ↓
Potential clinical   Routine case management
value from follow-up?
 ↓
Priority assessment
 ↓
Follow-up objective
 ↓
Targeted request

Database fields can support this process. Possible filters include seriousness, outcome, reaction term, missing laboratory results, missing diagnosis, absent causality information, signal relevance and special situations.

However, automated filtering should supportβ€”not replaceβ€”appropriate medical judgement.

7. Risk-Based Prioritisation

A useful prioritisation system considers both clinical importance and expected information value.

A serious case with a major unresolved question may warrant prompt follow-up.

Conversely, a non-serious case where the missing information is unlikely to change the assessment may have a lower priority.

The exact scoring model should not be presented as a regulatory requirement unless the applicable authority has specified one. Organisations may use different risk-based methodologies provided they remain scientifically justified and controlled.

8. Timing and Frequency

There is no scientifically useful universal rule that every case must be contacted at a fixed interval regardless of circumstances.

Timing should reflect the purpose of the follow-up and applicable regulatory requirements.

For example, a newly reported serious reaction requiring clarification may warrant prompt contact, whereas an outcome that is expected to become available after a defined clinical interval may justify a later targeted request.

Repeated attempts should also have a purpose. The organisation should avoid turning follow-up into an automatic sequence of contacts with no assessment of whether further information is likely to be obtained.

9. Follow-Up Is a Clinical and Operational Activity

Follow-up sits at the interface of medical assessment and PV operations.

The processor may identify missing information, while a physician or medically qualified reviewer may determine which information is most important to resolve the clinical uncertainty.

The process should therefore provide an escalation route when the significance of the missing information is unclear.

10. Targeted Rather Than Generic Requests

A targeted follow-up request is designed around the information missing from the particular case.

For example, a suspected drug-induced liver injury may require information about:

A generic request asking the reporter to "provide any additional information" may be less effective.

EMA has developed specific adverse-reaction follow-up questionnaires for certain reactions. Such tools should be used consistently with the current applicable EMA guidance and the organisation's controlled procedures.

11. The Reporter Is Usually the Most Important Follow-Up Source

The person who originally provided the information may be able to clarify the clinical facts and chronology.

Depending on the circumstances, follow-up may involve:

The organisation should use an appropriate and lawful route for obtaining additional information and should avoid unnecessary collection of personal information.

12. Follow-Up Does Not Mean Unlimited Data Collection

A common conceptual error is to equate a better case with a case containing every conceivable field.

The objective is information that improves the assessment.

Unnecessary requests can:

A mature PV system therefore asks the smallest useful set of questions capable of resolving the important uncertainty.

13. Documentation of Follow-Up

The case record should allow reconstruction of the follow-up history.

Depending on the process, this may include:

The evidence should be sufficiently detailed to demonstrate that follow-up was an active controlled process rather than an undocumented expectation.

The next chunk will examine unsuccessful follow-up, consent and privacy, targeted questionnaires in greater depth, serious and fatal cases, stopping rules, follow-up effectiveness and inspection scenarios.

14. Unsuccessful Follow-Up Attempts

A failed attempt to obtain additional information does not make a valid ICSR invalid.

The organisation should retain evidence of the attempts made and the information sought. The number and timing of attempts should follow a controlled, risk-based procedure rather than an arbitrary sequence applied without regard to the case.

For example, repeated attempts to obtain the outcome of a serious reaction may be justified when the information is likely to materially affect the case assessment. Repeatedly contacting a reporter for information that is unlikely to change the assessment may add little value.

15. When Should Follow-Up Stop?

A follow-up process should have a rational stopping point.

Possible considerations include:

The rationale should be documented where required by the organisation's procedures.

A stopping rule should not be confused with a regulatory permission to ignore important new information. If material information becomes available later, the case should be reassessed and updated as appropriate.

16. Serious Cases

Serious cases generally warrant particular attention because additional information can affect regulatory reporting, medical assessment, aggregate evaluation and risk management.

Examples include cases involving:

The follow-up objective should nevertheless remain case-specific. A serious case does not justify an indiscriminate request for every conceivable piece of information.

17. Fatal Cases

Fatal cases require particular care.

A report stating only that the patient died does not necessarily establish the cause of death.

Follow-up may seek, where appropriate and reasonably obtainable:

The distinction is critical:

Outcome = death is not equivalent to cause of death = adverse reaction.

A fatal outcome may be associated with an unrelated disease, an adverse reaction, another medicine, or an undetermined cause. The PV record should preserve that distinction.

18. Follow-Up for Signal-Relevant Cases

Follow-up may be particularly valuable when an individual case contributes to an emerging signal.

The objective can be to obtain information that helps distinguish competing explanations, characterize the reaction, establish a more precise phenotype or understand important risk factors.

The signal-management function and individual-case function should therefore have a defined interface.

A signal should not automatically trigger indiscriminate follow-up of every case. Follow-up should have a defined scientific objective.

19. Targeted Follow-Up Questionnaires

Targeted questionnaires can improve the quality of follow-up by translating a clinical question into specific information requests.

A good questionnaire should:

A questionnaire should not become a substitute for medical judgement.

20. Specific Adverse-Reaction Questionnaires

EMA has developed specific follow-up questionnaires for selected adverse reactions. These are particularly useful where structured clinical information is important for consistent assessment across cases.

The organisation should verify the current applicable EMA questionnaire and implementation status before embedding it into a procedure or electronic workflow.

The existence of a specific questionnaire does not mean that every case requires every question. The case context remains relevant.

Follow-up can involve obtaining additional personal and health information. The organisation should therefore apply the applicable legal and organisational requirements for privacy, confidentiality and data protection.

The principle of data minimisation is particularly relevant: information should be sought because it has a legitimate pharmacovigilance purpose, not simply because it could theoretically be useful.

Where consent or another legal basis is relevant to the contact or collection activity, the applicable framework should be followed. The organisation should not assume that a generic PV follow-up process automatically resolves every privacy or consent question.

22. Contacting Patients and Consumers

Patient or consumer follow-up may be appropriate in some circumstances, depending on the source, applicable law, organisational procedure and availability of a healthcare professional source.

The organisation should use appropriate communication methods and should avoid unnecessarily sensitive questions that do not contribute to the pharmacovigilance assessment.

The objective remains obtaining relevant safety information while maintaining appropriate confidentiality and respect for the individual.

23. Follow-Up of Literature Cases

A literature case may require follow-up through the publication author or another appropriate source when important information is missing.

The fact that the case was identified through literature does not change the fundamental objective of follow-up.

Where the publication describes a study-derived case, the organisation should also consider the appropriate study contact and the distinction between the literature source and the underlying case origin.

This is consistent with the distinction established in the dedicated Medical Literature Monitoring article in this series.

24. Follow-Up of Solicited and Study Cases

For cases originating in a PSP, clinical trial or other organised data-collection system, the organisation should understand the underlying data-collection process before initiating follow-up.

The relevant source may already have a structured mechanism for obtaining additional information. Duplicating that process unnecessarily can create inconsistent data and duplicate contacts.

The PV function should therefore define interfaces with clinical, study, programme and vendor teams.

25. Filtering for Follow-Up in the Safety Database

A practical implementation can combine structured database criteria with medical review.

For example:

CASE POPULATION
      β”‚
      β”œβ”€β”€ Serious? ────────────────┐
      β”œβ”€β”€ Fatal? ──────────────────
      β”œβ”€β”€ Important outcome missing? ─
      β”œβ”€β”€ Diagnosis unclear? ──────
      β”œβ”€β”€ Key clinical data missing? ─
      β”œβ”€β”€ Signal relevant? ────────
      └── Special situation? β”€β”€β”€β”€β”€β”˜
                    ↓
             FOLLOW-UP REVIEW
                    ↓
        Clinical value assessment
                    ↓
          Priority + objective
                    ↓
          Targeted follow-up

The exact rules should be validated and controlled. Automated flags can identify cases, but a system should not imply that an algorithm alone determines the clinical necessity of follow-up.

26. Example: Suspected Anaphylaxis

Initial report:

Patient developed swelling and breathing difficulty shortly after Product X. Treated in hospital and recovered.

Potential follow-up questions include:

A generic request for "all available information" is less targeted than a request designed around these uncertainties.

27. Example: Suspected Drug-Induced Liver Injury

Initial report:

Patient developed jaundice while taking Product X.

A clinically useful follow-up may seek liver chemistry values and dates, bilirubin, relevant investigations, concomitant medicines, alcohol or other exposures, underlying liver disease, treatment and outcome.

The objective is not simply to increase the number of populated database fields. It is to improve the clinical assessment.

28. Example: Serious Hospitalisation With Missing Diagnosis

Initial report states that the patient was admitted to hospital because of "severe symptoms" but does not describe the diagnosis.

Follow-up should focus first on establishing what happened clinically and why hospitalisation occurred.

The organisation should not assume that hospitalisation itself establishes the adverse reaction or its cause.

29. Example: Fatal Outcome With No Cause

Initial report:

Patient died during treatment with Product X.

The case may be valid, but the cause of death remains unknown.

A targeted request should attempt to establish the clinical circumstances and cause of death where reasonably possible. If the cause remains unknown after appropriate follow-up, the case should retain that uncertainty rather than assigning an unsupported adverse reaction.

30. Follow-Up Metrics

Useful metrics should measure process effectiveness, not merely activity volume.

Potential measures include:

Metrics should be interpreted carefully. A low response rate may reflect the source population rather than poor PV performance.

31. Inspection Perspective

An inspector may ask:

The strongest evidence is not a procedure stating that follow-up is performed. It is a sample of cases demonstrating that the organisation identified a clinical question, selected an appropriate follow-up strategy, documented the attempts and appropriately incorporated the response.

32. Common Failure Modes

Common weaknesses include:

The next chunk will consolidate the regulatory requirements, difficult inspection scenarios, governance model, references and Regulatory Note.

33. Governance of Follow-Up

Follow-up should be governed as part of the pharmacovigilance quality system rather than treated as an informal activity performed by individual case processors.

The organisation should define, as appropriate:

The procedure should be sufficiently specific to produce consistent decisions while allowing appropriate medical judgement.

34. Follow-Up and the Reporting Clock

Follow-up does not ordinarily postpone the processing of a valid ICSR that is already subject to reporting requirements.

Once the organisation has sufficient information to establish a valid report and the applicable reporting obligation is triggered, the organisation should not wait for completion of a preferred follow-up package before taking the required regulatory action.

New clinically relevant information obtained later should be assessed and, where applicable, submitted as follow-up information within the relevant regulatory framework.

This distinction is fundamental:

Valid report
    ↓
Reporting obligation assessed
    ↓
Required submission
    ↓
Follow-up continues where useful
    ↓
New information assessed
    ↓
Follow-up submission if applicable

35. Follow-Up and Seriousness

Follow-up and seriousness should not be confused.

A serious case may deserve higher follow-up priority, but seriousness itself does not define the questions that should be asked.

For example, if hospitalisation is already clearly documented, asking repeatedly whether the patient was hospitalised adds little value. The useful questions may instead concern diagnosis, clinical findings, treatment, outcome or causality.

This is one reason targeted follow-up is preferable to a universal checklist.

36. Follow-Up and Causality

Causality assessment can identify specific uncertainties that follow-up may resolve.

Examples include:

The follow-up request should identify the information that is actually missing rather than asking the reporter to repeat information already available.

37. Follow-Up and Outcome

Outcome information can be particularly important when the initial case describes an ongoing event.

A follow-up request may establish whether the patient:

The organisation should distinguish outcome from causal attribution. A change from "ongoing" to "fatal" does not by itself establish that the medicinal product caused the death.

38. Follow-Up and Duplicate Management

Follow-up information can arrive through a different source from the original report.

For example, a physician may provide additional information after a patient has separately submitted a report. The organisation should determine whether the information belongs to an existing case or represents a separate case.

Duplicate assessment should therefore operate continuously throughout the case lifecycle, including during follow-up.

39. Difficult Scenario: New Information Arrives Before Follow-Up Is Completed

A valid serious ICSR is submitted to EudraVigilance. Two days later, the reporter provides a laboratory result that materially changes the medical assessment.

The organisation should not wait until the planned follow-up cycle is complete. The new information should be assessed promptly and the case updated and submitted as required.

Follow-up is an iterative process, not a single transaction.

40. Difficult Scenario: Reporter Says No More Information Is Available

A reporter responds that the information supplied is all that is available.

The organisation should record the response and avoid treating the case as incomplete solely because preferred information is unavailable.

If the case remains clinically important, the organisation may consider whether another appropriate source can lawfully provide relevant information. That decision should be proportionate and documented.

41. Difficult Scenario: Repeated Non-Response in a Serious Case

A serious case contains substantial uncertainty and the reporter does not respond to several reasonable attempts.

The appropriate response is not an endless series of identical messages. The organisation should follow its controlled escalation and stopping process, consider whether another appropriate source exists, document the attempts and retain the uncertainty in the case.

If clinically material information subsequently becomes available, the case can be reassessed.

42. Difficult Scenario: Fatal Case With Only Death Reported

A report states only that a patient died while receiving Product X.

The case should not automatically be coded as an adverse reaction representing the cause of death merely because the outcome is fatal.

The organisation should seek appropriate information about the circumstances and cause of death where reasonably possible. If no cause can be established, the uncertainty should remain explicit.

This is both a medical-assessment issue and a data-quality issue.

43. Difficult Scenario: Follow-Up Questionnaire Is Too Broad

A generic questionnaire requests dozens of fields unrelated to the suspected reaction.

The organisation should assess whether the questionnaire is proportionate and clinically useful.

A broad questionnaire can reduce response quality, create unnecessary burden and increase collection of personal information without improving the safety assessment.

Targeted questions should be preferred where the clinical objective is known.

44. Difficult Scenario: Automated Follow-Up Flag

A safety database automatically flags every serious case for follow-up.

The flag is useful as a control, but it should not be interpreted as evidence that every flagged case requires the same questionnaire or number of contacts.

The workflow should provide a documented clinical review step that determines the actual follow-up objective.

45. Follow-Up Effectiveness

Effectiveness should be evaluated at more than one level.

Process effectiveness

Are cases identified and acted upon according to the defined process?

Response effectiveness

Do reporters respond, and are appropriate sources being approached?

Information effectiveness

Does the information obtained materially improve the case assessment?

Regulatory effectiveness

Are important new data incorporated and reported appropriately?

A high number of follow-up attempts is not evidence of effectiveness if those attempts rarely produce useful information.

46. What Inspectors May Sample

During an inspection, an authority may sample cases and reconstruct the follow-up lifecycle.

A useful internal inspection exercise is therefore to select cases across different categories:

For each sample, the organisation should be able to demonstrate a coherent rationale.

47. Inspection Finding Pattern: Procedure Without Effective Implementation

A procedure may state that serious cases are followed up within a defined period, while case records show inconsistent or undocumented implementation.

This illustrates the distinction between documented compliance and effective implementation.

An inspection-ready process requires both.

48. Inspection Finding Pattern: Activity Metrics Without Clinical Assessment

An organisation may report that it made thousands of follow-up attempts, but have no evidence that the cases were prioritised or that the requests were clinically targeted.

High activity does not demonstrate a high-quality process.

The organisation should be able to explain why a follow-up was initiated and what information it was intended to obtain.

49. Practical Follow-Up Control Checklist

Before considering a follow-up process effective, ask:

50. Relationship With Other Module VI Articles

Follow-up intersects with almost every major Module VI process.

G14 β€” Difficult ICSR Validity and Assessment Scenarios explains when a report is valid and how difficult minimum-criteria cases should be handled. G19 begins from that valid case and asks whether additional information should be sought.

G15 β€” Patient Support Programmes and Solicited Reports, G16 β€” Clinical Trials and ICSR Management and G18 β€” Other Organised Data Collection Systems and Solicited Sources address the source-specific interfaces that may affect how follow-up is performed.

G17 β€” Medical Literature Monitoring and Literature ICSRs addresses literature identification and case origin; G19 addresses obtaining additional information once a literature case has been identified.

G11 β€” Data Quality, Case Processing Controls and Reconciliation addresses follow-up as one element of case-quality control; G19 provides the detailed follow-up methodology.

Key Takeaways

References

  1. European Medicines Agency. Good Pharmacovigilance Practices (GVP), Module VI β€” Collection, management and submission of reports of suspected adverse reactions to medicinal products.
  2. European Medicines Agency. Guideline on good pharmacovigilance practices (GVP), Module VI β€” current revision and tracked-change versions where applicable.
  3. International Council for Harmonisation. ICH E2D(R1) β€” Post-Approval Safety Data: Definitions and Standards for Management and Reporting of Individual Case Safety Reports.
  4. European Medicines Agency. Specific Adverse Reaction Follow-up Questionnaire guideline and associated implementation material.
  5. European Medicines Agency. EudraVigilance guidance for individual case safety report management and electronic reporting.
  6. European Commission. Commission Implementing Regulation (EU) No 520/2012, as amended.
  7. European Parliament and Council. Directive 2001/83/EC, as amended.
  8. European Medicines Agency. Pharmacovigilance inspection guidance and publicly available inspection-related material relevant to case processing and follow-up controls.

Regulatory Note

This article is an educational explanation of follow-up of individual case safety reports within the EU pharmacovigilance framework. It does not replace current EU legislation, GVP Module VI, ICH E2D(R1), EMA follow-up questionnaires, EudraVigilance technical guidance, applicable data-protection requirements or an organisation's approved procedures.

Specific timelines, contact requirements and technical reporting rules should be verified against the current applicable regulatory and technical documents. Organisational procedures may impose additional controls provided that they remain consistent with applicable requirements.

The clinical examples in this article are illustrative. They are intended to demonstrate reasoning and control principles and are not presented as actual regulatory inspection cases unless a specific source is identified.

Revision History

Last reviewed: 2026-08-24