> 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/understand-the-results/view-individual-reports.md).

# View individual reports

Detailed information can be reviewed for any report in the “Cases” tab.

To open a report:

1. Locate the report from the line listing.
2. Click the PDF icon on the left of the **Safety report ID**.
3. Opening a report will display its detailed Individual Case Safety Report view.

{% hint style="info" %}
The available information depends on the content of the report submitted.
{% endhint %}

The detailed view may include:

* Administrative information
* Patient information
* Seriousness information
* Drugs
* Reactions/Events
* Time to onset, dechallenge and rechallenge information
* Medical history, test and procedure
* Additional report details

#### Exporting individual reports

Reports can be exported as PDFs for review.

Multiple reports can be exported at the same time either as Case details or Line listing (See Exports section) .


---

# 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/understand-the-results/view-individual-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.