> 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/exports/export-an-overview.md). # Export an overview The overview can be exported for the summary of the current search and its associated results. #### To export the overview: 1. Perform the search. 2. Apply any relevant filters. 3. Select the export option. 4. Click Overview 5. Open or save the file. The export captures the overview of the current search as it exists at the time of export. #### When should I use the overview? Search overview exports are useful when you want to: * Document a search strategy * Share search results with colleagues * Record the scope of an analysis * Support investigation documentation Because the export reflects the current filters and settings, it can help reproduce a previous analysis. The Excel file contains the following sheets: Search criteria, Patient age, Patient sex, Countries, Drug, Reaction, Co-reported active ingredients, Reported preferred terms, Serious, Seriousness criteria, Fatal, Reporter qualification and VigiBase initial date. --- # 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/exports/export-an-overview.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.