Table of contents
At a glance
How do you keep an ICSR follow-up report linked to the correct case?
Link new information to the existing case and its source. Distinguish original receipt, receipt of the latest information and the case versions actually submitted. Assess the medical or administrative significance before deciding on a follow-up report. An internal version counter does not replace the worldwide unique case identifier or verification of the recipient’s acknowledgement. Document supplementary information even when it does not require submission.
- Treating new information, internal correction and technical resubmission separately.
- In principle, case identification and original receipt are received at a follow-up.
- Understand the transmitted content, transfer status, and professional assessment together.
1. Define the current regulatory framework
The following considers safety incidents involving human medicinal products in the European post-authorization setting. An ICSR is a structured individual case safety report; not every received notification constitutes a new reportable case version. The determination is based on content, source, and applicable regional reporting criteria. Clinical SUSAR processes and veterinary medicinal procedures must be handled separately.
GVP Module VI remains currently in revision 2. Additional definitions and guidance from ICH E2D(R1), as implemented under the EU implementation strategy, apply concurrently. The general EU transition period ended on 18 September 2026; thereafter, the definitions and guidance from E2D(R1) shall be applied. Where E2D(R1) refers to regional requirements, GVP Module VI remains the governing document for the EU. Separate implementation rules, such as those for ongoing support programmes and technical E2B values, must be considered independently. The scientific introduction must not be conflated with the separate technical implementation of new E2B coding values. For this article, particular relevance applies to follow-up, case assessment, and reporting start date.
2. Separation of Incoming, Case History, and Shipping Documentation
The timing of database processing does not indicate when the organization received the information. Therefore, document the verifiable entry at the relevant point of contact, assign it to the appropriate case, and record the subsequent transmission. For a partner report, the partner's original entry date must also be considered in the evaluation. Any onward transmission must not obscure the actual information flow.
For follow-up notifications, Module VI specifically designates C.1.4 as the original entry date, C.1.5 as the date of most recent information, and C.1.8 as the globally unique case identifier. The original entry date and case identifier are retained in follow-up notifications; C.1.5 is updated upon receipt of new information. The initial or follow-up nature of the notification is recipient-based. The same status may represent a new occurrence for one recipient, even if another recipient has previously held prior versions.
3. Assess the content before creating the next version
The following internal reference guide distinguishes commonly confused scenarios. It is not a substitute for medical case evaluation. The key factor is not the length of a message: a single new assertion can alter the classification as serious or the assessment outcome. Conversely, a multi-page document may simply repeat already known information.
Document the rationale for decisions such that another qualified personnel can trace the decision pathway. A designation as non-material should refer specifically to the information and its impact. Administrative details may also be relevant, for example, a newly identified case number that enables a duplicate checking procedure.
| Input or finding | Assessment question | Expected workflow |
|---|---|---|
| New Hospital Report | Does it alter the medical assessment or classification as serious? | Review new information; if necessary, submit follow-up. |
| Additional identifier of a partner | Does it affect case assignment or duplicate management? | Link identification; assess impact on new status report |
| Repeated identical setup | Is actual new information contained? | Document dual entries; do not invent a new medical fact |
| Internal transmission error detected | Is new information available from the source? | Evaluate amendments or corrections separately |
| Only shipping failed | Which already specified content is missing at the recipient's end? | Investigate technical failures and verify the relevant communications. |
4. Example: Three contacts, one case, two reporting instances
In the example, a duly identified physician reports a suspected adverse reaction to a specific patient and medicinal product on October 1. The minimum required information is available. The case is assigned a stable internal identifier F-014 and the necessary electronic identifiers. On October 2, version V1 is submitted and its acceptance is reviewed.
On 4 October, a previously known finding is reported again. On 6 October, the first release report is issued, containing a significant new information relevant to evaluation. The following matrix defines the required expectations. The example does not establish a medical diagnosis nor a standardized deadline for any conceivable report.
| Step | Incident and Information | Expected state |
|---|---|---|
| 1 October: first receipt | F-014; four minimum information entries available | Original entry date: 1 October |
| 2 October: Shipping of V1 | First notification to the designated recipient | V1 content and associated acceptance confirmation available |
| 4 October: identical finding | No new information compared to V1 | Receipt documented; no artificial medical augmentation |
| 6 October: Release report | New relevant information; professionally assessed | C.1.5 on 6 October; original date and case identity retained |
| V2 Shipping | Complete updated version of the same case | New information identifiable; message and recipient response assigned |
5. Maintain consistent narrative text and structured fields
A follow-up report should identify the new information while keeping the case understandable. ICH E2D(R1) describes a coherent medical narrative. The patient's clinical timeline and the order in which information arrived may differ. Both may be needed to reconstruct the case.
Therefore, do not compare only two PDF outputs. Review the modified structured data, the narrative, assessments, and relevant document references. If contradictory information is identified, do not eliminate inconsistencies through an ungrounded selection appearing to resolve them. Document the source and the need for clarification. Any independent assessments must remain clearly identifiable and shall not be rewritten as statements attributed to the reporter.
6. Track the submitted status at the recipient site
A successful technical transfer and acceptance of content constitute distinct pieces of evidence. The EU-ICSR guideline distinguishes between gateway receipt confirmation and the technically and professionally processed message. A message may contain individual rejected case reports. Therefore, closure should not depend solely on a transmission status.
Assign recipient responses to the actual message and case status. An error in V2 must not go unnoticed simply because V1 was successfully accepted. When retransmitting, verify which reports are affected, what corrections have been made, and what response is subsequently available. Acceptance by EudraVigilance does not automatically confirm the medical quality of all provided information.
7. Define responsibilities at transfer points
For small teams, clear handovers are particularly important: Who reviews new documents, assesses their significance, determines the reporting category, and follows up on missing approvals? A single individual may assume multiple responsibilities, provided that authority, qualification, and the intended controls are appropriate. A specific signature combination cannot be universally derived from this.
Prioritize open tasks based on their significance. Proactively request missing information; document all attempts and results. A case with completed initial dispatch may still have open follow-up tasks. Conversely, not every contact attempt necessitates an immediate new submission. Discuss partner changes and migrations specifically, as these situations risk misalignment of existing case identifiers and recipient histories.
8. Checklist for the next follow-up report
Use this own checklist at a specific case version. It links incoming, decision-making, and outgoing elements. In the example, three contacts are documented, but only two distinct reporting events are intended. The identical documentation does not generate a third medical information.
During system validation, you should also simulate a delayed incoming entry and a rejected follow-up message. It is expected that the original data and open tasks remain visible. A simple version counter does not prove this functionality; what is essential is a traceable link between the records.
- Is new information and source clearly attributable to the existing case?
- Are original and latest information entries separately documented?
- Is the medical and administrative significance clearly evaluable?
- Are the case identifiers and relevant external identifiers available?
- Is the narrative, structured information, and documentation consistent?
- Is the recipient, shipping point, and response clearly linked?
- Are errors and open inquiries to be followed up with the responsible party?
Project experience and collaboration
Link new information to the correct version of the safety case
With case and system owners, we trace a follow-up from receipt to the relevant report version. We examine the unchanged worldwide case identifier, new information, timing and type of onward transmission. A simple addition may need different handling from medically relevant new information that changes the reporting assessment. We also test handover between organisations. The history must remain intelligible so a new report number is not mistaken for a new, independent case.
Frequently asked questions about ICSR Follow-up
Is every new message automatically followed up for submission?
No. New information is assigned to and evaluated within the case. The significance of the information is decisive for submission. An identical report or a trivial addition does not automatically result in a new ICSR submission. Nevertheless, the handling of the incoming data must remain transparent and traceable.
May we generate a new case identifier for each follow-up report?
No. During follow-up, the globally unique case identifier C.1.8 is retained (GVP VI.C.6.2.2.7). If another organization submits follow-up information, it continues to use the original global identifier, while employing its own reporting and sender identifier. A subsequent re-submission following nullification constitutes a separate process and is handled with new identifiers. Therefore, do not confuse the global case identity with a local reporting number.
Sources: [1]
Which date remains unchanged?
During routine follow-up, the original entry date retained in C.1.4 remains unchanged. C.1.5 documents the receipt of the most recent information. Do not confuse these values with the entry date or dispatch date. A justified correction to a previously erroneous date must be clearly documented and traceable.
Sources: [1]
Can a new partner identifier also be relevant on a site-specific basis?
Yes. Module VI provides new administrative information that may influence case management. An additional identifier could, for example, help detect duplicates. Therefore, evaluate the intended use and not merely whether a new medical event has been described.
Sources: [1]
Is an internal coding correction always considered a follow-up?
No. Without new source information, an internal correction may be classified as an amendment. Newly received information, on the other hand, is evaluated according to the follow-up rules. The key factors are the cause and content of the change, not the designation of a work process in your database.
Do we only need to send the new sentences in the narrative?
Does gateway approval suffice to close the task?
It documents the technical receipt, not only the acceptance of each case report. Check the associated processing response and process rejections. An earlier successful dispatch of the same case does not replace the response to the current follow-up report.
Sources: [4]
Must a complete checklist be re-evaluated each time a modification is made?
The scope of control should cover the specific change and its impact. New relevant medical information requires a different evaluation than an identical appendix. A clear rationale and effective controls are more useful than unchecked tick-boxes without reference to the specific case version.
What helps with incomplete follow-up data?
Does a validated safety system replace the case evaluation?
Sources and review date
Source date: 7 October 2026. GVP Module VI Rev. 2 is to be read in conjunction with ICH E2D(R1) and the EU Implementation Strategy 2026. Regional reporting criteria and current technical E2B guidelines remain to be assessed separately. Tables and case examples are considered standalone reference tools.
- EMA: GVP Module VI – Collection, Processing, and Reporting of Suspected CasesRevision 2, 28 July 2017, applicable from 22 November 2017. Sections VI.B.3–5, VI.B.7 and VI.C.6.2.2.6–8, pages 16–18, 21–22 and 58–61.
- EMA/ICH: E2D(R1) – Post-approval safety dataStep 5, 18.09.2025; EU Efficacy 18.03.2026; §§ 5.2, 6.2–6.5, p. 18, 20–22
- EMA: EU Implementation Strategy for ICH E2D(R1)EMA/11141/2026, 26.02.2026; PRAC 20.02.2026; § 2, S. 2: Efficacy, transition and separate technical implementation
- EMA: EU ICSR Implementation GuideEMA/51938/2013 Rev. 2, March 2021; I.C.2.1.8 and I.C.6, pp. 19–21, 97–99
Sources checked: .
Prepare follow-up reports with a clear case and traceability chain.
We support you in translating incoming pathways, case versions, and recipient acknowledgements into specific requirements and concrete controls.
- Computer system validation →
Bring your GxP systems into validated operation, from laboratory software, MES and eQMS to ERP. We define the scope, plan risk-based tests using GAMP 5 and hand the evidence to QA for release.

