> For the complete documentation index, see [llms.txt](https://docs.welkinhealth.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.welkinhealth.com/care/getting-started/insights.md).

# Insights

## Overview

The Insights section of the Welkin Care Portal provides visibility into patient population metrics, outcome trends, and workflow performance. Access to Insights is controlled by role permissions configured in Designer.

## What Insights Include

Insights contains a set of system reports that cannot be customized. Available report sections include:

* **Patients**
* **Territories**
* **Assessments**
* **Calendar**
* **Encounters**
* **Tasks**
* **Export Data**

Each section has its own breakdown of analytics — some reports display as lists, others as pie, line, or bar graphs. Graphs are interactive and allow you to drill down further.

## Exporting Data

Where export is available within individual reports, a download icon appears on the right side of the report screen. This lets you export specific report data as a CSV file.

For a full data export, navigate to the **Export Data** section and click **Request to export all Insights data**. The system will generate a zipped CSV file folder. This may take a few moments depending on your database size.

Once the export is ready, click **Download** to save the file. If the export file has expired, you will see the message **"The export file is no longer available. Please generate a new export."** — click **Request to export all Insights data** again to create a fresh export.

## Notes

* Insights data reflects activity within your role's data access scope
* All reports in Insights are system reports and cannot be customized
* For more advanced analytics, your organization may use the Sisense integration; see [Sisense Change Requests](https://docs.welkinhealth.com/integrations/analytics-sisense/sisense-change-requests)


---

# 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://docs.welkinhealth.com/care/getting-started/insights.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.