> 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/entering-and-structuring-data-in-reports/coding-adverse-event-information.md).

# Coding adverse event information

### Method 1

In the **`Reaction`** section, search for suitable terms in the field *Reaction/event (MedDRA)*.

### Method 2

If you don’t find the term when searching, click the list symbol on the right to browse the MedDRA hierarchy. Clicking the arrows expands levels of the dictionary, eventually leading to a list of LLTs.

If you are unsure and cannot find an adequate MedDRA term, you can use the free text field *Reaction/event as reported by initial reporter*. However, free text reactions cannot be searched in neither VigiFlow nor VigiLyze. The two fields can also be used in combination to reflect both the original report and its corresponding MedDRA term. 


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://support.who-umc.org/vigiflow/entering-and-structuring-data-in-reports/coding-adverse-event-information.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.