> 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

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