> For the complete documentation index, see [llms.txt](https://support.who-umc.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.who-umc.org/vigiflow-ereporting-for-industry/upload-e2b.md).

# Upload E2B

This module is intended for MAHs with databases capable of transmitting ICH E2B XML.

VigiFlow eReporting for Industry is based on the [ICH E2B standard](https://ich.org/page/e2br3-individual-case-safety-report-icsr-specification-and-related-files), which defines required data elements and the data element structure for ICSRs.

<table data-card-size="large" data-view="cards" data-full-width="false"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th><th data-hidden data-card-cover data-type="files"></th></tr></thead><tbody><tr><td><strong>How to upload an E2B XML</strong></td><td>Upload a report in E2B XML format</td><td><a href="/vigiflow-ereporting-for-industry/upload-e2b/how-to-upload-an-e2b-xml.md">How to upload an E2B XML</a></td><td></td></tr><tr><td><strong>How to upload follow-up and amendments</strong></td><td>Upload follow-ups and amendments for previously submitted reports</td><td><a href="/vigiflow-ereporting-for-industry/upload-e2b/how-to-upload-follow-up-and-amendments.md">How to upload follow-up and amendments</a></td><td></td></tr><tr><td><strong>How to upload nullifications</strong></td><td>Upload nullifications for previously submitted reports</td><td><a href="/vigiflow-ereporting-for-industry/upload-e2b/how-to-upload-nullifications.md">How to upload nullifications</a></td><td></td></tr></tbody></table>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://support.who-umc.org/vigiflow-ereporting-for-industry/upload-e2b.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.