> 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/vigilyze/searching-and-filtering/perform-and-and-or-searches.md).
# Perform AND and OR searches
By default, VigiLyze uses OR logic within a specific category, for example drugs or reactions. Between different categories AND logic is used.
An OR search provides reports matching any of the selected terms.
#### Example
Drug A OR Drug B
The search will retrieve all cases that contain Drug A, Drug B, or both, providing a broader set of results that includes reports where either search term is present.
#### Creating an AND search
To search reports that contain multiple terms:
1. Add the search terms.
2. Drag one term onto another.
3. Release the mouse button.
The search changes to AND logic.
**Example**
In the example above, we start with an OR search for *Tamoxifen* and *Tranexamic acid*.
By draging and dropping the *Tranexamic acid* onto *Tamoxifen* it becomes and AND search.
The search will retrieve all cases in which both *Tamoxifen* and *Tranexamic acid* are reported together in a same report. Applying both search terms narrows the results to cases containing both medicines.
The same approach can be used for reaction terms.
#### Returning to OR search
1\. Drag one term away from the other.
2\. Release the mouse button
The search will return to OR search
{% hint style="warning" %}
VigiLyze does not support NOT searches or exclusion criteria.
{% 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/vigilyze/searching-and-filtering/perform-and-and-or-searches.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.
