Regulations and compliance · Practical guide

Correcting an ICSR: amendment, nullification or retransmission?

A rejected report does not automatically invalidate a safety case. A coding error in a reaction does not automatically require nullification. Establish the cause and extent of the problem before choosing how to correct an ICSR in European post-authorisation pharmacovigilance for human medicines.

Table of contents

At a glance

When do we need an amendment, nullification or technical retransmission?

Decide whether there is new source information, an internal correction or a failed transmission. An amendment addresses certain corrections without new information. Follow-up is based on newly received information. Nullification invalidates the whole previously submitted case and is not a correction to an individual field. Technical retransmission depends on the actual error and recipient response. Document the decision and rationale together.

  • The reason for the change determines the workflow, not the button within the system.
  • An amendment without new information does not establish a new Day Zero.
  • Nullification pertains to the entire case report and is assigned a review pathway.

1. Determine the root cause of the error prior to incident reporting

An ICSR may be technically accurate and yet fail due to a technical rule. Similarly, a successfully received message may contain an internally erroneous content that is only identified later. Such situations require various corrective actions. Therefore, first clarify which content currently exists at which recipient and precisely what needs to be amended.

The scope is EU post-authorisation pharmacovigilance for human medicines. GVP Module VI describes amendment and nullification. ICH E2D(R1) explains, among other things, when the reporting clock starts for new information and internal corrections. Technical acceptance of an XML report does not establish its medical or regulatory accuracy.

Sources: [1] [2]

2. Four approaches to be clearly distinguished from one another

This dedicated matrix serves for triage. The final decision takes into account the specific report and the applicable EU regulations. A term such as 'correction' in a ticket is too vague for this purpose. Specify whether a source has provided new facts or whether the organization has reinterpreted or correctly processed existing information.

Several errors can occur simultaneously. For example, new information may necessitate a follow-up report, whose initial transmission may be technically rejected. Correcting the transmission does not automatically alter the professional classification of the report.

Own triage for a defective or modified ICSR
TriggerContextEvidence to retain
New relevant source information Assess follow-up Inbound, new information and case reference
Internal error with no new information Assessment of significance of amendment Cause, correction rationale and unchanged incoming references
Previously reported case demonstrably invalid Verify nullification Specific reason, sender authorization and affected case
XML or transfer rejected Technical Correction and Resubmission Error response, affected message and new confirmation

Sources: [1] [2] [3]

3. Amendment without invented new entry

Module VI, for example, describes an internal reassessment or correction where no new source information has been received. If the change significantly affects the medical evaluation, an amendment must be submitted. In contrast, newly received information is handled according to the follow-up rules, even if it corrects a previous statement.

For E2B(R3), GVP Module VI identifies the amendment flag and reason in C.1.11.1 and C.1.11.2 respectively. Retain the specified case and receipt details. Under ICH E2D(R1), an amendment without additional information does not establish a new Day Zero. Do not record an internal review as a new contact with the source.

Sources: [1] [2]

4. Do not interpret nullification as a deletion function

A nullification declares the previously submitted case as completely invalid. It applies not only to a single erroneous preversion. Module VI requires a specific, clear justification; general statements such as 'in error' do not adequately explain the root cause. The corresponding case remains traceable for audit purposes in sender and receiver database records.

The original sender organization and the actually transmitted identifiers are materially significant. The technical EU guideline further distinguishes between direct nullifications and specific nullification requests for cases transmitted differently. Consequently, there is no general right to remove external reports without authorization. A re-submission of a previously nullified case is not a simple reactivation; Module VI specifies new identifiers for such scenarios.

Sources: [1] [3]

5. Example: Three findings on a reporting day

In the example, a team evaluates three independent processes. In Case A, a medical error occurred during coding, despite the source document being correct. In Case B, a documented investigation confirms the incident was incorrectly reported. In Case C, the content remains unchanged, but the message was not processed.

The decision matrix does not specify the exact user interface of a product; it defines what evidence is required. A generic batch action of "retrieve all three and recreate" would obscure these distinctions and unnecessarily interrupt the chain of events in cases A and C.

Example: completed correction scenario
ActivityEstablished factExpected decision
A: Coding error Internal error; no new source; medical significance affected Amendment with grounds; no new Day Zero
B: entire case invalid Enlightenment evidences complete misreporting; own previous broadcast identified Nullify the case while preserving a traceable history
C: Message rejected AR Response; no data from the message received and imported Retransmit the entire corrected message again; monitor the response
Control point Three different root causes Three separate decisions; no common flat-rate withdrawal

Sources: [1] [2] [3]

6. Correctly handle partial and total errors

The EU-ICSR Guidance distinguishes between AE as a processing error with additional details and AR as rejection of the message without data transfer. At the case level, CA and CR indicate acceptance or rejection, respectively. Therefore, review both levels, rather than treating each warning or error message uniformly.

In AE, individual case reports may be affected; in AR, the guideline specifies the resubmission of the entire corrected transaction. Assign the correction to the actual error. A previously accepted case version must not inadvertently appear as new medical information. After resubmission, verify both the new response and the open reporting backlog.

Sources: [3]

7. Decision, correction, and consequences jointly documented

A robust correction record addresses four key questions: What was incorrect, on what basis is this determination made, which corrective action pathway was selected, and how was the outcome of that action verified? Link the prior shipment, decision record, updated content, and response. The justification must remain readable, even when a staff member later reviews only the current database snapshot.

In addition, assess whether the same error affects further cases, reports or evaluations. A correction of a single record does not necessarily resolve the cause in the mapping or workflow. The scope and priority of the further investigation depend on the actual findings; the article does not prescribe a general full review of each historical report.

Sources: [1] [2]

8. Verify corrections prior to closure

This dedicated checklist helps track a technically appropriate action all the way to the recipient. For smaller teams, a shared overview of open corrections is recommended. Within this overview, separately record the type of notification, affected recipient, and pending response.

A completed software change request is not sufficient to establish a conclusive endpoint if a required transmission has not been approved. Conversely, an accepted technical transmission does not obviate the need for an open medical evaluation. Both outcomes must be considered in the final release decision.

  • Is the new source or internal correction clearly defined?
  • Affected case, reporting status, and recipient identified?
  • Amendment, follow-up, and nullification justified differently?
  • No artificial new Day Zero for internal correction?
  • Is the reason for nullification specific, and has the sender arrangement been checked?
  • Has ACK been evaluated on the message and event level?
  • Evaluated for impact on other cases or analyses?

Sources: [1] [2] [3]

Project experience and collaboration

Distinguish correction, follow-up and nullification before submission

With your pharmacovigilance team, we work through prepared cases involving new information, an internal correction or an entirely invalid case. With the system team, we then trace identifiers, the rationale and the associated transmission. An error in one item may require a different route from a true nullification. We agree review and approval steps that make the decision traceable before submission and retain the case history.

Frequently asked questions about ICSR corrections

Is a rejected XML file automatically considered an invalid case?

No. A technical rejection may pertain to a valid content case. Investigate the error and submit the required corrected message. A technical failure alone does not justify the nullification of a medical case.

Sources: [3] [1]

When is a correction considered a follow-up instead of an amendment?

When new source information is received, the treatment depends on the follow-up rules. An amendment concerns certain changes without such a new input. The fact that the new information corrects an earlier statement does not make it a purely internal correction.

Sources: [1] [2]

Can the date of internal defect identification be considered a new Day Zero?

For an amendment without new information, no new deadline start date is required under ICH E2D(R1). Nevertheless, document the discovery and correction of errors, but do not confuse these internal events with the receipt of new case information.

Sources: [2]

Must every keystroke error be submitted as an amendment?

Not every minor change necessitates a new submission. Assess its impact on case evaluation and management. A seemingly small date error could, however, have medical relevance. The classification must be based on the specific content involved.

Sources: [1]

Can only an old case version be invalidated?

No. Individual case versions cannot be nullified; according to GVP VI.C.6.2.2.9, nullification applies to the entire case. If only specific fields need to be amended, the appropriate correction or follow-up procedure should be used instead. The already submitted versions remain traceable.

Sources: [1]

Does a nullified case disappear from the inspection path?

No. It should no longer be used as a valid case for scientific evaluation, but remains comprehensible for testing purposes. The nullification is a notification of its invalidity and not a certificate to delete all related supporting documents.

Sources: [1]

Can we simply reverse a nullification?

No. According to GVP VI.C.6.2.2.9, a nullified case cannot be reactivated. If a re-submission is required, it will receive a new sender identification number C.1.1 and a new global case number C.1.8. The link to the prior history remains traceable. Therefore, prior to nullification, carefully assess whether the entire case is indeed invalid or whether only corrections to data are required.

Sources: [1]

What distinguishes AE from AR?

AE flags errors that may require further processing of individual ICSRs. AR indicates rejection without extracted data. The guide outlines different resubmission options for such cases. Review the detailed response and the failure level, not just the general submission status.

Sources: [3]

Does CA demonstrate medical validity?

CA demonstrates the successful receipt of the ICSR through the described technical procedure. It does not replace a medical quality control of the contents. A technically accepted report may still require a justified correction or additional follow-up information.

Sources: [3] [1]

Which documents are most helpful for a small team?

A clear chain consisting of the original status report, specific finding, justified decision, corrected outcome, and recipient response. Assign responsibility and identify open actions. A lengthy file lacking this linkage does not resolve the critical evidentiary question.

Sources: [1] [3]

Sources and review date

Sources checked on 7 October 2026 include GVP Module VI Rev. 2, ICH E2D(R1) as implemented in the EU and the EU ICSR Guide Rev. 2. Also check current business rules and the actual system configuration. The case and tables are practical examples.

  1. EMA: GVP Module VI – Collection, Processing, and Reporting of Suspected CasesRev. 2, effective 28.07.2017; applicable from 22.11.2017; VI.B.7.2–3 and VI.C.6.2.2.7–9, page 22, 58–63
  2. EMA/ICH: E2D(R1) – Post-approval safety dataStep 5, 18.09.2025; EU Efficacy 18.03.2026; Section 5.2, Page 18: Follow-up and Amendment without a new Day Zero
  3. EMA: EU ICSR Implementation GuideEMA/51938/2013 Rev. 2, March 2021; I.C.2.1.8, p. 19–21; I.C.6.1.1, p. 98–99

Sources checked: .

Daniel Herrmann, Daniel Herrmann Consulting

Daniel Herrmann Consulting

Manage ICSR corrections from investigation findings to acceptance

We support you in translating correction types, system statuses, and recipient responses into traceable work processes and targeted review cases.

  • 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.

Send a project enquiry Customer testimonials →