> 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/manage-reports.md).

# Manage reports

Update, share, delete, find, and compare reports.

<table data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>Using the report status</strong></td><td>The report status indicates the current stage of the report in the process.</td><td><a href="https://support.who-umc.org/vigiflow/manage-reports/using-the-report-status.md">Using the report status</a></td></tr><tr><td><strong>Updating an existing report in VigiFlow</strong></td><td>Level 1 organisations are also able to share the updates to VigiBase.</td><td><a href="https://support.who-umc.org/vigiflow/manage-reports/updating-an-existing-report-in-vigiflow.md">Updating an existing report in VigiFlow</a></td></tr><tr><td><strong>Sharing reports with VigiBase</strong></td><td>Level 1 organisations can share reports from VigiFlow to VigiBase.</td><td><a href="https://support.who-umc.org/vigiflow/export-data/sending-reports-to-vigilyze.md">Sending reports to VigiLyze</a></td></tr><tr><td><strong>Ensuring an ICSR meets minimum requirements for VigiBase submission</strong></td><td>ICSRs can be sent to VigiBase even if not assessed or complete.</td><td><a href="https://support.who-umc.org/vigiflow/manage-reports/minimum-requirements-for-vigibase-submission.md">Minimum requirements for VigiBase submission</a></td></tr><tr><td><strong>Deleting an ICSR</strong></td><td>ICSRs can be deleted from the "Report list".</td><td><a href="https://support.who-umc.org/vigiflow/manage-reports/deleting-an-icsr.md">Deleting an ICSR</a></td></tr><tr><td><strong>Finding follow-up reports</strong></td><td>Follow-up reports are only visible to level 1 organisations.</td><td><a href="https://support.who-umc.org/vigiflow/manage-reports/finding-follow-up-reports.md">Finding follow-up reports</a></td></tr><tr><td><strong>Comparing follow-up report content</strong></td><td>Use the compare feature to see what has been changed in a follow-up report.</td><td><a href="https://support.who-umc.org/vigiflow/manage-reports/comparing-follow-up-report-content.md">Comparing follow-up report content</a></td></tr></tbody></table>


---

# 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/manage-reports.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.
