> For the complete documentation index, see [llms.txt](https://docs.owkin.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.owkin.com/explore-and-analyse-data/data-analysis/cohort-clinical-description/population-overview.md).

# Population overview

Summarize patient numbers by condition, optionally broken down by dataset.

Summarize patient numbers by condition, optionally broken down by dataset.

## Patient count matrix (condition × dataset)

### Description

#### Analysis summary

Counts the patients available per condition, optionally broken down per dataset, to gauge cohort sizes before any deeper analysis.

#### Computation

Counts distinct patients per condition — and per dataset when a dataset column is given with more than one value — returning a count table; with exactly one condition, the count is returned as a sentence instead.

#### When to use

Use as the entry point of a multi-analysis report: it answers 'how many patients are there per condition (and per dataset)'. For per-variable breakdowns of those patients, use this module's multi-column summary mode.

#### Caveats

Counts are distinct patients per cell of the matrix; a patient appears once per condition it belongs to, not once overall.

### Input columns

<details>

<summary><code>input columns</code></summary>

| column      | type        | required | description                                                                                                                                                      |
| ----------- | ----------- | -------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| patient\_id | any         | required | Patient identifier.                                                                                                                                              |
| x\_group    | categorical | required | Condition name — becomes the row axis of the count matrix.                                                                                                       |
| y\_group    | categorical | optional | Dataset name — becomes the column axis of the count matrix. Optional: when absent or with a single unique value, a simpler single-column table (or a sentence f… |

</details>

### Visualizations

* `population_overview` How to read: A Markdown table with one row per condition and one column per dataset; each cell is the number of distinct patients with that condition in that dataset (blank when none). With a single dataset the table shrinks to condition → patient count, and with a single condition to a one-sentence count.


---

# 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.owkin.com/explore-and-analyse-data/data-analysis/cohort-clinical-description/population-overview.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.
