GVP Module VI: ICSR Follow-Up and Medical Review

Introduction

The initial report is often incomplete. Important information about a patient's clinical course may become available only after the first case has been received and processed.

Follow-up is therefore an essential part of ICSR management. It should not be treated as an administrative exercise in which every case receives identical requests for information.

A mature process asks three questions:

What is missing?
      ↓
Could the information materially change the case?
      ↓
What is the appropriate follow-up action?

The objective is to improve the quality and clinical usefulness of the case while maintaining appropriate regulatory timelines.

1. Why Follow-Up Matters

Follow-up can change the interpretation of an ICSR substantially.

New information may establish:

• a more precise diagnosis;
• seriousness;
• outcome;
• additional exposure information;
• relevant laboratory results;
• concomitant medicines;
• medical history;
• or a different clinical chronology.

Some follow-up information can also change whether a case requires regulatory action.

2. Follow-Up Is Risk Based

Not every case requires the same intensity of follow-up.

A practical approach is to prioritise information that could materially affect:

• patient safety assessment;
• case validity;
• seriousness;
• reporting requirements;
• causality assessment;
• signal evaluation;
• or the understanding of an important safety concern.

The organisation should define its criteria in controlled procedures.

3. Initial Medical Review

Medical review should identify clinically important gaps in the initial report.

The reviewer should consider:

• whether the clinical chronology is coherent;
• whether the reaction is sufficiently characterised;
• whether seriousness is established;
• whether outcome information is available;
• and whether additional information could change the assessment.

4. What to Request

Follow-up questions should be specific and clinically meaningful.

Potential information requests include:

• exact onset date;
• dose and exposure dates;
• relevant medical history;
• diagnostic investigations;
• treatment provided;
• clinical outcome;
• rechallenge or dechallenge information;
• concomitant medicines;
• and relevant laboratory results.

The request should reflect the information gap rather than use an unnecessarily broad questionnaire.

5. Follow-Up and Timelines

Follow-up should operate alongside regulatory case processing.

If an ICSR already meets the applicable criteria for reporting, the organisation should not necessarily delay submission while waiting for information that is useful but not required for the initial report.

The process should distinguish information needed for regulatory validity from information that improves clinical completeness.

6. Follow-Up Attempts

A controlled process should document follow-up attempts.

Relevant records can include:

• date of attempt;
• communication method;
• information requested;
• recipient or source where appropriate;
• response;
• and resulting case action.

Documentation should allow an inspector to distinguish an unsuccessful follow-up attempt from a failure to attempt follow-up.

7. Medical Review of Follow-Up

New information should not simply be appended to the case without assessment.

The reviewer should determine whether it changes:

• seriousness;
• outcome;
• diagnosis;
• causality;
• coding;
• expectedness where applicable;
• narrative;
• or the overall clinical interpretation.

The case should be updated in accordance with the organisation's controlled process.

8. Follow-Up and Case Narrative

The narrative should remain clinically coherent after an update.

If follow-up substantially changes the chronology, the narrative should reflect the new evidence rather than merely adding disconnected sentences.

9. Follow-Up and Coding

New information can require changes to coded data.

For example, a previously vague clinical event may later receive a confirmed diagnosis.

The organisation should assess whether structured terminology needs to be updated and whether the change affects downstream analysis.

10. Follow-Up and Seriousness

Follow-up may establish a seriousness criterion that was not known initially.

Examples include later confirmation of:

• hospitalisation;
• prolonged hospitalisation;
• life-threatening illness;
• disability;
• or death.

The organisation should reassess the case when such information becomes available.

11. Follow-Up and Outcome

Outcome information can be clinically important even when it does not alter the initial reporting decision.

For serious reactions, an eventual recovery, recovery with sequelae, ongoing condition or fatal outcome can materially affect the safety assessment.

The next chunk will cover follow-up prioritisation, medical judgement, special situations, case updates, escalation and practical follow-up scenarios.

12. Prioritising Follow-Up

Follow-up priorities should reflect the potential clinical and regulatory impact of the missing information.

High-priority follow-up may be appropriate where additional information could affect:

• validity;
• seriousness;
• outcome;
• causality;
• an important medical event;
• or a regulatory reporting decision.

The organisation should define criteria that allow consistent prioritisation across products and teams.

13. Follow-Up of Serious Cases

Serious cases may warrant particular attention because additional information can materially change the clinical assessment.

Examples include clarification of hospitalisation, life-threatening illness, disability, congenital anomaly, or death.

The follow-up process should remain proportionate and clinically focused.

14. Follow-Up of Fatal Cases

When a case involves death, follow-up may be important to establish the cause of death, chronology, relevant medical history and the relationship between the suspected reaction and the outcome.

The organisation should avoid implying causality simply because death occurred after exposure.

15. Follow-Up of Important Medical Events

A clinically important event may require clarification even when it does not fall neatly into another seriousness category.

Medical review should determine what additional information could meaningfully change the assessment and whether follow-up is justified.

16. Follow-Up of Special Situations

Special situations can require specific follow-up considerations.

Examples include:

• pregnancy exposure;
• breastfeeding exposure;
• overdose;
• medication error;
• misuse;
• abuse;
• off-label use;
• occupational exposure;
• and lack of efficacy where applicable.

The follow-up objective should reflect the safety question associated with the special situation.

17. Pregnancy Exposure

Pregnancy reports can require follow-up information about gestational timing, maternal exposure, pregnancy outcome and relevant infant or fetal information.

Follow-up should be clinically appropriate and should recognise that important outcomes may become available only later in the pregnancy or after birth.

18. Medication Errors

Where a medication error is reported, follow-up may clarify what occurred, whether the medicine reached the patient, whether a clinical consequence occurred and what corrective action was taken.

The organisation should distinguish the medication error itself from any resulting adverse reaction.

19. Lack of Efficacy

Where lack of efficacy is reported, follow-up may establish the indication, treatment duration, dose, disease severity, adherence and clinical outcome.

Whether the event is reportable or requires follow-up depends on the applicable product and regulatory context.

20. Medical Judgement

Medical review should focus on the clinical significance of new information rather than simply completing database fields.

A medical reviewer may need to reassess the chronology and determine whether the new information changes the interpretation of the case.

The reasoning should be documented according to the organisation's procedures.

21. Follow-Up and Causality

Follow-up can provide information relevant to causality, such as:

• temporal relationship;
• dechallenge;
• rechallenge;
• alternative causes;
• concomitant medicines;
• and objective findings.

The new evidence should be considered as a whole rather than treated as proof based on one isolated factor.

22. Follow-Up and Duplicate Detection

New information can also reveal that a case is a duplicate of another report.

Follow-up information should therefore be considered during duplicate reassessment where relevant.

This illustrates why follow-up is part of the complete case lifecycle rather than a separate administrative activity.

23. Follow-Up After Regulatory Submission

A case can require follow-up after the initial ICSR has already been submitted.

If material new information is obtained, the organisation should assess the case and determine whether an updated submission is required under the applicable reporting framework.

The relationship between the original and subsequent submissions should remain traceable.

24. Follow-Up Closure

The organisation should have criteria for closing a follow-up cycle.

Closure does not necessarily mean that every desired field has been completed.

A follow-up attempt may be closed when reasonable attempts have been made and no further information is obtainable, provided the applicable procedure and regulatory expectations have been satisfied.

25. Escalation

Cases should be escalated when follow-up identifies information that may have broader safety significance.

Potential triggers include:

• unexpected serious outcomes;
• unusual clinical patterns;
• clusters of similar cases;
• new diagnostic findings;
• or information relevant to an emerging safety concern.

The case-processing workflow should connect with signal-management processes where appropriate.

26. Follow-Up and Signal Management

A single case may provide information relevant to a potential signal, while repeated follow-up across several cases can reveal a pattern.

Case processors and medical reviewers should therefore know how to escalate information that may require broader safety assessment.

27. Vendor Follow-Up

Where follow-up is outsourced, the MAH should define the vendor's responsibilities and oversight requirements.

Controls may include:

• follow-up criteria;
• timelines;
• approved communication methods;
• escalation rules;
• quality review;
• metrics;
• and reconciliation.

The MAH should retain appropriate oversight of the process.

28. Follow-Up Metrics

Useful metrics can include:

• percentage of cases requiring follow-up;
• follow-up attempt completion;
• response rate;
• time to follow-up;
• time to incorporation of material information;
• overdue follow-up actions;
• and cases where follow-up changed seriousness or outcome.

Metrics should be interpreted with the product and case mix in mind.

29. Practical Example: Hospitalisation Confirmed Later

An initial report describes a reaction but does not establish hospitalisation. Follow-up confirms that the patient was admitted because of the reaction.

The case should be medically reassessed, the seriousness classification updated where appropriate and the applicable regulatory reporting consequences determined.

30. Practical Example: Outcome Changes

An initial case records the outcome as unknown. Follow-up later confirms complete recovery.

The case should be updated with the new information and the narrative should remain consistent with the clinical chronology.

The next chunk will cover difficult follow-up scenarios, inspection findings, governance, practical end-to-end examples, final principles, References + Regulatory Note.

31. Difficult Scenario: No Response to Follow-Up

A report contains enough information to establish a valid ICSR, but clinically important details remain unavailable despite repeated attempts to obtain them.

The organisation should document the attempts, assess the information already available and avoid treating the absence of a response as evidence for an unreported clinical outcome.

The case should remain an accurate representation of what is known.

32. Difficult Scenario: Follow-Up Changes the Diagnosis

An initially reported symptom is later diagnosed as a specific medical condition.

The new diagnosis should be medically reviewed and incorporated into the case where appropriate. The coded terms, narrative and medical assessment should remain internally consistent.

33. Difficult Scenario: Follow-Up Reveals a Different Outcome

A case initially records an ongoing reaction. Later information confirms complete recovery.

The case should be updated to reflect the new outcome, while preserving the chronology of the original and follow-up information.

34. Difficult Scenario: Follow-Up Reveals Death

A subsequent source reports that the patient died after the initial report.

The organisation should establish the clinical chronology, assess the cause and circumstances of death, reassess the case medically and determine whether an updated regulatory submission is required.

Death following exposure should not automatically be interpreted as death caused by the medicinal product.

35. Difficult Scenario: Follow-Up Creates a Duplicate

Additional information identifies that an apparently unique case corresponds to another case already present in the database.

The organisation should perform duplicate assessment, preserve relevant source information and manage the records according to the controlled duplicate process.

This demonstrates why follow-up and duplicate management cannot be treated as completely independent workflows.

36. Difficult Scenario: Follow-Up Identifies a Signal

Follow-up provides unusual clinical information that appears in several cases involving the same product.

The information should be escalated through the organisation's signal-management pathway where appropriate.

Case processing should not become isolated from broader safety surveillance.

37. Inspection Considerations

An inspector may ask:

• How do you decide which cases require follow-up?
• What information do you request?
• How do you prioritise serious cases?
• How are follow-up attempts documented?
• How do you prevent follow-up from delaying required submissions?
• Who performs medical review?
• How are material changes incorporated into the case?
• How are follow-up cases reconciled with duplicate and signal processes?

The organisation should be able to demonstrate consistent application of its procedures.

38. Inspection Risk: Mechanical Follow-Up

A process that sends the same generic questionnaire to every report may produce substantial activity without improving safety information.

Follow-up should be targeted to clinically meaningful information gaps.

39. Inspection Risk: Follow-Up Delays Reporting

A case may be held while personnel attempt to obtain additional information even though the available information already satisfies the applicable reporting criteria.

The organisation should demonstrate that follow-up and regulatory timelines are managed as parallel activities when appropriate.

40. Inspection Risk: Follow-Up Not Reflected in the Case

Another weakness occurs when responses are received but are not incorporated correctly into the safety database.

The organisation should have controls ensuring that material follow-up information reaches the case record, medical review and any required downstream processes.

41. Governance

Follow-up should be governed through the pharmacovigilance quality system.

Governance should address:

• prioritisation criteria;
• responsibilities;
• communication methods;
• medical review;
• escalation;
• vendor management;
• quality control;
• metrics;
• and change control.

42. Training

Training should emphasise that follow-up is a clinical information-gathering activity rather than a checklist exercise.

Personnel should understand which missing information can materially change the case and how to escalate uncertainty.

43. Practical Example: Seriousness Established During Follow-Up

An initial report describes an adverse reaction without a seriousness criterion. Follow-up confirms that the patient required hospitalisation because of the reaction.

The case is reassessed, the seriousness information is updated and the organisation determines the appropriate regulatory action.

The follow-up source and date remain traceable.

44. Practical Example: Pregnancy Outcome

A pregnancy exposure is reported without an outcome. Several months later, follow-up provides the pregnancy outcome and relevant neonatal information.

The case is updated and medically reviewed. The organisation assesses whether the new information affects the safety assessment or any required reporting.

45. Practical Example: Laboratory Result Changes Interpretation

A case initially contains a nonspecific symptom. Follow-up provides laboratory results supporting a specific diagnosis.

The medical reviewer reassesses the clinical interpretation, updates the narrative and evaluates whether coding or other structured data should change.

46. What Good Looks Like

A mature follow-up process:

• identifies clinically meaningful information gaps;
• prioritises cases according to risk;
• uses focused questions;
• operates without unnecessarily delaying required reporting;
• documents every meaningful attempt;
• incorporates responses accurately;
• triggers medical reassessment when appropriate;
• connects with duplicate and signal-management processes;
• and remains inspection-ready.

47. Final Principles

1. Follow-up should improve clinically and regulatorily meaningful information.
2. Follow-up should be proportionate to the potential significance of the missing information.
3. Serious and medically important cases may require particular attention.
4. Follow-up should not unnecessarily delay a required ICSR submission.
5. Unsuccessful follow-up should be documented accurately.
6. New information should be medically assessed rather than merely appended.
7. Follow-up can change seriousness, outcome, diagnosis, coding or causality assessment.
8. Follow-up can reveal duplicates or information relevant to signal management.
9. Pregnancy and other special situations may require longitudinal follow-up.
10. Outsourced follow-up requires appropriate MAH oversight.
11. Follow-up processes should be measured for effectiveness, not merely activity.
12. Current GVP requirements and applicable legislation should govern the final regulatory decision.

Key Takeaways

• Follow-up is an integral part of ICSR lifecycle management.
• The best follow-up is targeted, clinically meaningful and risk based.
• Medical review determines whether new information changes the interpretation of the case.
• Follow-up should run in parallel with regulatory timelines where necessary.
• A follow-up response can change seriousness, outcome, diagnosis, coding, duplicate status or signal relevance.
• Good documentation demonstrates both what was requested and what was ultimately learned.

References

1. European Medicines Agency. Good Pharmacovigilance Practices (GVP), Module VI — Collection, management and submission of reports of suspected adverse reactions to medicinal products. Primary EU guidance for follow-up and ICSR management.
2. European Medicines Agency. GVP Module IX — Signal management. Relevant where follow-up information contributes to signal detection or assessment.
3. European Medicines Agency. GVP Module V — Risk management systems. Relevant where case information contributes to ongoing risk evaluation.
4. European Parliament and Council. Directive 2001/83/EC, as amended. EU legal framework for medicinal products for human use and pharmacovigilance.
5. European Parliament and Council. Regulation (EC) No 726/2004, as amended. Union framework for authorisation and supervision of medicinal products and relevant pharmacovigilance obligations.
6. International Council for Harmonisation. ICH E2D — Post-Approval Safety Data Management: Definitions and Standards for Individual Case Safety Reports. Relevant to ICSR follow-up and case-management concepts.

Regulatory Note

This article is an educational and practical explanation of ICSR follow-up and medical review under the EU pharmacovigilance framework. It does not replace the current GVP Module VI, applicable EU legislation, EudraVigilance requirements or organisation-specific procedures.

Follow-up requirements and technical expectations can depend on the case, product, source and applicable regulatory framework. Current EMA guidance and applicable legislation should be verified before changing a live process.

The practical examples are illustrative and are not descriptions of specific regulatory inspection cases unless an authoritative source is explicitly identified.