> 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/export-data/sending-reports-to-vigilyze.md).
# Sending reports to VigiLyze
Once shared, the report will be accessible for analysis in VigiLyze alongside reports from other member organisations in the WHO Programme for International Drug Monitoring.
VigiLyze is updated twice a week, on Sundays and Wednesdays. When you share reports with VigiLyze, [some patient and reporter data](/vigiflow/export-data/data-masked-in-exports.md) will be masked in the shared copy.
### Share individual reports
When inside a report, you can share it using the **`Send copy`** button.
### Share multiple reports
Multiple reports can also be shared in one go, from the "**Report list**".
1. Select the reports to be sent to VigiLyze by clicking the box to the left of the Worldwide Unique ID.
2. Go to **reports selected** menu and choose **`Send copy`**.
The next section describes how to [send batches of reports to VigiLyze](/vigiflow/export-data/sending-batches-of-reports-to-vigilyze.md).
### VigiLyze status in Report list
The column VigiLyze in the “Report list” should be interpreted as this
* **Empty**: The report has not been shared with VigiLyze
* **Check mark** (✔): The report has been shared with VigiLyze
* **Exclamation mark** ( **!** ) : The latest version of the report hasn’t been shared.
{% hint style="info" %}
Explore training courses through our [Learning Management System](https://learning.who-umc.org/). Log in if you have a learner account or create a learner account by clicking **Enrol**.
Refer to the VigiFlow Introductory Course: “**Receiving and sharing reports**” section → “**Receive and share ICSRs**”
**Note**: VigiFlow online courses are only available to VigiFlow users. Check with your national regulatory authority for access.
{% 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/export-data/sending-reports-to-vigilyze.md?ask=&goal=
```
`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.