> 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/meddra-and-whodrug-licence-management.md).
# MedDRA and WHODrug licence management
### Manage MedDRA licences
To activate MedDRA searching and coding in data entry:
1. Open **Manage licences** from the **User menu** in the top-right corner.
2. Obtain your **MeDRA API key** or register for a new one using the link provided. Log in with your MedDRA credentials and copy the API key.
3. Enter your **MedDRA ID** and **API key**.
4. Click **Save**.
5. If validation is successful, a confirmation message appears and MedDRA fields become active in data entry.
{% hint style="info" %}
For support about MedDRA licences, contact MSSO directly through:
* web form available at
* email:
{% endhint %}
### Manage WHODrug licences
To activate WHODrug searching and coding in data entry:
1. Open **Manage licences** from the **User menu** in the top-right corner.
2. Enter your **WHODrug licence number** and click **Save**.
3. A confirmation message appears when validation is successful.
{% hint style="info" %}
For support about WHODrug licences, contact UMC directly using the web form available at: .
{% endhint %}
### Understand licence status indicators
* When a MedDRA or WHODrug licence expires or is not validated, searching and coding in the respective fields is **disabled** in data entry.
* Fields that use these dictionaries are labelled “**(MedDRA)**” or “**(WHODrug)**” when the licence is valid and available.
If coding functions stop working, open **Manage licences** from the **User menu** in the top-right corner to check your licence status and update your details.
---
# 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/meddra-and-whodrug-licence-management.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.
