> 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/settings-and-customisation/personal-settings/change-report-date-settings.md).

# Change report date settings

VigiLyze can use different dates when displaying report trends and calculations.

#### To change the report date setting:

1. Open the User menu.
2. Open **Settings**.
3. Locate **Report date** settings.
4. Select the preferred date option.

*VigiBase initial date* is the date when the case first was entered into VigiBase.

*Initial receive date* is the date when the national pharmacovigilance centre first received the case from the primary source.

*Latest receive date* is the date when the national pharmacovigilance centre received the most recent information for the case (latest follow-up).

The selected date is used throughout the application where date-based analyses are displayed.

#### Why does this matter?

Changing the report date may affect:

* Trend graphs
* Date-based searches
* Timeline analyses
* Quantitative results

Different date types may produce different results depending on the reports available in the dataset.


---

# 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/settings-and-customisation/personal-settings/change-report-date-settings.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.