> 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-drug-information-with-whodrug.md).

# Coding drug information with WHODrug

Coding drugs and vaccines with WHODrug enables users to find reports in searches and queries and allows for computer processing of cases (such as calculations of disproportionality).

How to code drug information with WHODrug:

1. When coding to WHODrug in VigiFlow, you can search for both trade names and active substances in the field *Drug name*. A drop-down list appears with results matching the search. You can also click the icon on the right of the field to access the more detailed WHODrug search, where you can see additional information such as MAH and dose forms.
2. If you are unable to find the correct match for your search or if you have information to add, use the field *Drug name as reported by initial reporte*r.

{% hint style="warning" %}
If you can’t find a specific pharmaceutical product in WHODrug, [contact UMC](mailto:support@who-umc.org) to suggest its inclusion in the dictionary.
{% 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/entering-and-structuring-data-in-reports/coding-drug-information-with-whodrug.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.