> 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/getting-started/the-quantitative-view.md). # The Quantitative view The Quantitative view provides an aggregated overview of reporting data organised by drug-reaction combination. Rather than focusing on individual reports, the Quantitative view focuses on combinations of drugs and reactions. \ It can be used to: * Review large numbers of combinations * Focus on combinations with increased reporting * Apply quantitative filtering criteria * Prioritise combinations for further assessment ### Drug-reaction combinations table The drug-reaction combinations table is the main component of the Quantitative view. \ Each row represents a drug-reaction combination and may include information such as: * Number of reports * Disproportionality measures * Latest report date * Number of reporting organisations * Other quantitative metrics Columns can be customised and sorted. #### Filtering results The Quantitative view includes filtering options that allow you to focus on: * Specific drugs * Drug groups * Reactions * Important Medical Events * Custom groups * Investigation status #### Reviewing underlying reports From the Quantitative view, you can move directly to the Qualitative view and review the reports that contribute to a selected drug-reaction combination. \ This supports quantitative review and qualitative assessment within the same workflow. --- # 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/getting-started/the-quantitative-view.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.