> 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/vua/setting-language.md).
# Setting language
Several language settings are available in VigiFlow eReporting for Industry to support different dictionaries and needs. Each setting controls a specific part of the platform.
* **User interface language:** sets the language used for buttons, menus, and other interface elements.
* **Native language:** prepopulates free text fields intended to capture information as reported in the original source language, such as *Reaction or event as reported by the primary source*.
* **EDQM language:** determines the language used for pharmaceutical dose form and route of administration, based on EDQM terminology.
* **WHODrug language:** sets the language applied to all WHODrug fields.
* **MedDRA language:** sets the language used for all fields based on MedDRA terminology.
{% hint style="info" %}
*Please note that built‑in browser translation features should not be used as they may interfere with the interface.*
{% endhint %}
---
# 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/vua/setting-language.md?ask=&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.
