E2B(R3) ICSR submissions start with a complete case

E2B(R3) ICSR submission is the sentence sponsors use when they mean "the electronic file the authority will accept." ICH E2B(R3) is a message standard. An individual case safety report is the medical and administrative content. Submission is the act of sending a valid message to the authority. Those are three layers. Tools that advertise E2B(R3) sometimes only mean they can export a file shaped like the standard. A file that never leaves the building is not a submission.

What the message is for

Regulators moved individual case exchange off paper and off older E2B releases onto E2B(R3). The message carries reporter, patient, reaction, drug, and narrative sections in a fixed structure so a receiving system can read them. FDA's electronic submissions gateway, and the equivalent paths in other regions, are how the message travels. The gateway checks that a sender is allowed to send. It does not check that the causality call was wise.

Small IND sponsors felt this when electronic IND safety reports stopped being optional. The operational guide on this site, what IND sponsors need for E2B(R3), walks through that change. The readiness checklist is the accompanying list. This page is the concept: what you are submitting, and what has to exist first.

The case is the product. The XML is the packaging.

E2B(R3) validation will reject a message with missing required elements. It will not reject a message whose serious box was guessed from a subject line. The elements that make a case worth sending are the same ones intake is supposed to capture, plus the decisions a qualified person has made:

• Reporter and patient, identifiable enough for a valid case, with the privacy limits your process already uses.
• Suspect product, dose, and dates.
• Reaction in the reporter's words, and a MedDRA term a coder is willing to stand behind.
• Seriousness, expectedness against a named reference document, and causality.
• The receipt date that starts the 7-day or 15-day discussion, if this is an expedited case.
• A narrative that matches the structured fields. When they disagree, the authority sees both.

Teams stall on the packaging because the case is still in email. Buying a gateway login does not create the case. The inbox is still the bottleneck at a lot of small biotechs.

Who actually sends it

A company that runs Oracle Argus, ArisGlobal LifeSphere, or Veeva Vault Safety often sends from that system, or from a safety CRO that runs one of them. Those products remain the system of record. AE Connect integrates the reviewed case with any safety database, including those.

A sponsor that has outsourced submissions should be able to name the vendor, the account, and the person who confirms a file was acknowledged. "We use a gateway" is not a control. The checklist is the blunter version of that question.

What AE Connect does with E2B(R3) concepts

The AE Connect workspace organizes a source document into the judgments an ICSR depends on: seriousness, a suggested MedDRA preferred term and system organ class, WHO-UMC causality, expectedness, whether reporting looks required, and a timeline. You accept or override each one. AE Connect integrates that reviewed case with any safety database. Oracle Argus, ArisGlobal LifeSphere, and Veeva Vault Safety remain the system of record.

Use it so seriousness is not invented from a PDF at midnight. AE Connect integrates the case with the safety database, which remains the system of record. AI case processing on this site means that draft, with a person on every field.