Arca
Skip to content
Tools
Tools

E2B(R3) ICSR Viewer

When a patient has a side effect, the drug company or regulator writes it up as an individual case safety report and sends it to others as E2B(R3) XML, a format built for computers. Open one here to read each case in plain terms and see what a safety reviewer would query.

Open individual case safety reports from partners, CROs or a regulator's gateway. Read each case, see when drugs were given against when reactions began, and find what a safety reviewer would query.

Open E2B(R3) safety reports

Drop ICSR XML files, a folder of them, or a ZIP anywhere on this page, or choose them.

Read in this browser tab; nothing is uploaded. ICH E2B(R3) HL7 messages, single or batched.
  • Read every case

    Seriousness, patient age and sex, suspect drugs, reactions with their MedDRA codes, outcome and sender, one row per case.

  • See drug against reaction

    Doses, routes, indications, action taken, rechallenge and causality, with a timeline of exposure against onset.

  • Check what a reviewer checks

    Minimum case criteria, seriousness, impossible dates and FDA's regional elements, each tied to its guide section.

About this data

What it reads

E2B(R3) is the ICH standard for exchanging individual case safety reports. Each report is an HL7 version 3 message: who sent it and when (sections N and C), the patient (D), the reactions (E), tests (F), drugs (G) and the narrative (H). A batch can carry many reports. FDA, the EMA and PMDA all take reports in this format, with their own regional additions; FDA's are the elements numbered FDA.*.

The viewer reads the element numbers of the ICH E2B(R3) Implementation Guide (version 5.03, July 2025) and FDA's Regional Implementation Guide for E2B(R3) (August 2024). Dechallenge is not a separate element in E2B(R3): it shows as the action taken with the drug (G.k.8) against the reaction's outcome (E.i.7). Rechallenge is G.k.9.i.4.

The checks

Each check says which section of which guide it rests on. The FDA checks run only on cases addressed to FDA: a ZZFDA batch receiver (N.1.4), or a CDER or CBER message receiver (N.2.r.3).

  • Identifiable patient (ICH E2B(R3) IG ยง3.3.1 and section D). A valid report needs one identifiable patient: at least one element in section D (initials, age, sex, date of birth and so on) holding a value or masked.
  • Identifiable reporter (ICH E2B(R3) IG ยง3.3.1 and C.2.r). A valid report needs one identifiable reporter: a primary source (C.2.r) with at least one of name, address or telephone, country or qualification.
  • At least one reaction (ICH E2B(R3) IG ยง3.3.1 and E.i). A valid report needs at least one adverse event or reaction (E.i).
  • Suspect or interacting drug (ICH E2B(R3) IG ยง3.3.1 and G.k.1). A valid report needs one suspect or interacting drug, and G.k.1's business rule says every ICSR holds at least one drug characterised as suspect, interacting or not administered.
  • All six seriousness criteria (ICH E2B(R3) IG E.i.3.2a to E.i.3.2f). All six seriousness criteria are required for every reaction, each either true or nullFlavor NI. A non-serious reaction carries NI in all six; false is not an allowed value.
  • Seriousness matches the criteria (ICH E2B(R3) IG E.i.3.1 and E.i.3.2). E.i.3.1 records whether the reporter called the term serious (codes 3 and 4) or not (1 and 2); E.i.3.2 records which seriousness criteria apply. A term coded serious with no criterion true, or non-serious with one, is contradictory.
  • Expedited case has a serious reaction (ICH E2B(R3) IG C.1.7; ICH E2A ยงIII.A). C.1.7 says the case meets the local criteria for an expedited report. Under ICH E2A, expedited reporting is for reactions that are both serious and unexpected, yet no reaction has a seriousness criterion (E.i.3.2aโ€“f, or FDA's required intervention) set to true.
  • No dates in the future (ICH E2B(R3) IG ยง3.3.6; FDA regional guide ยง5.3). Dates cannot refer to the future. A date counts as future when it is later than the report's date of creation (C.1.2), or than today for the creation and transmission dates themselves.
  • Suspect drug started before the reaction (Timing check on E.i.4 and G.k.4.r.4 (not a guide rule)). A suspect or interacting drug whose first start date (G.k.4.r.4) is later than the onset of a reaction it is linked to (E.i.4). The guide allows this, but a drug started after a reaction began cannot have caused it unless it made it worse, so reviewers query it. Dates are compared only to the precision both give.
  • Batch and message receivers match (FDA regional guide ยง4.1.5 and ยง4.1.7). Postmarketing messages to CDER go in a batch to ZZFDA; IND and IND-exempt BA/BE messages (CDER_IND, CBER_IND, CDER_IND_EXEMPT_BA_BE) go to ZZFDA_PREMKT. ZZFDATST and ZZFDATST_PREMKT are the test equivalents.
  • C.1.7 is true or false (FDA regional guide ยง4.2.3.1). FDA does not accept nullFlavor NI for C.1.7 in initial submissions and rejects them; the value must be true or false.
  • FDA local criteria report type (FDA regional guide ยง4.2.3.1). FDA requires a coded FDA.C.1.7.1 Local Criteria Report Type (15-Day, 7-Day, 5-Day, 30-Day or non-expedited) on every ICSR.
  • FDA report type agrees with C.1.7 (FDA regional guide ยง4.2.3.1). An expedited case (C.1.7 true) takes a 15-, 7- or 5-Day report type; a non-expedited one takes non-expedited or 30-Day.
  • Combination product indicator (FDA regional guide ยง4.2.3.1 and table 4). For postmarketing ICSRs FDA's report type depends on FDA.C.1.12, the Combination Product Report Indicator, so the guide expects it on every postmarketing report.
  • IND numbers (FDA regional guide ยง4.2.3.4 and ยง4.2.3.6). IND safety reports require FDA.C.5.5a, the IND where the event occurred, and FDA.C.5.6.r, cross-reported INDs (nullFlavor NA when there are none).
  • Race and ethnicity (FDA regional guide ยง4.2.4.1). FDA asks for patient race (FDA.D.11.r.1) and ethnicity (FDA.D.12), with nullFlavor NI when unknown.
  • One MedDRA version (FDA regional guide ยง5.5). A single MedDRA version should be used for every MedDRA-coded element in one ICSR.

The sample

The sample loads nine of FDA's own example E2B(R3) instances, published with its regional guide, and a synthetic batch for examplumab, a fictional drug. FDA's examples were written to show structure, so their dates do not always agree: several give a date of creation in 2014 for a report first received in 2022, which the date check flags. The second examplumab case was built with gaps for the checks to find.

Frequently asked questions

Are my safety reports uploaded?
No. The page reads the files inside your browser tab. Nothing is sent to Arca or anyone else, and pressing Clear or closing the tab releases them.
Which files can it open?
ICH E2B(R3) messages: HL7 batches (MCCI_IN200100UV01) holding one or more ICSRs (PORR_IN049016UV), single messages, and ZIP files of either. E2B(R2) files (ichicsr) are recognised but not read.
Why does it not show patient initials or reporter names?
A case list is often shared or pasted into a tracker. The viewer shows whether initials (D.1) were given or masked, but never their value, and leaves out record numbers, date of birth and the names of reporters and senders. The CSV export leaves them out too.
Why are reactions shown as MedDRA codes?
E2B(R3) carries the MedDRA lowest level term code (E.i.2.1b) and the term the reporter used (E.i.1). MedDRA's term names are licensed, so the viewer shows the code as given beside the reported term rather than looking the code up.
Does this replace FDA's validator or my safety database?
No. It runs the checks a reviewer makes first and says what each rests on. It does not validate against the XML schema or FDA's full business rules; FDA's E2B(R3) validator and your safety system do that.
Logos are each company's own site icon, matched by name through Wikidata.Company names and logos identify the companies in public FDA and registry records and do not imply endorsement.