> For the complete documentation index, see [llms.txt](https://documentation.opencrvs.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://documentation.opencrvs.org/v2.0/functional/markdown/aggregated-data.md).

# Aggregated Data

## Overview

As part of the **Functional Architecture**, the **Aggregate Data** section describes the aggregation and analytics module in OpenCRVS — how data from records and workflows is combined for reporting and statistics.

It is organised into the following modules:

* **Performance Views** — describes performance dashboards (for example, workload, timeliness, rejection rates, correction volumes) built using Metabase on top of aggregated data.
* **Vital Statistics Export** — explains how registered records are transformed into tabular exports and dashboards for vital statistics production and monitoring.
* **Person Centricity (backlog)** — shows how records can be linked around a person (for example, using UINs or probabilistic matching) to support person‑centric analytics and life‑course views.

Together, these modules describe how OpenCRVS data can be aggregated, visualised, and used for performance management and vital statistics, while keeping individual record data secure.


---

# 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://documentation.opencrvs.org/v2.0/functional/markdown/aggregated-data.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.