> 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/understand-your-data/supported-modalities.md).

# Supported modalities

As of March 2026, only the modalities below are supported by K-Pro Data Model:

* Clinical data
* Molecular data:
  * Bulk RNA seq
  * Single / nuclei cell RNA seq
  * Spatial transcriptomics (VisiumSD)
  * Whole Exome Sequencing
  * Proteomics
* Histology - slide annotation linked to a patient

{% hint style="info" %}
Extra modalities / technologies are available upon request. By default K-Pro expects to receive processed data (in the format of count matrixes for example for bulk and single cell data), however Owkin has also developed in-house processing pipeline that can process raw files for both bulk RNAseq, Chromium single-cell and Visium spatial sequencing.
{% endhint %}

#### Clinical data

Standard clinical data formats are supported (.csv, .tsv, .xlsx, …).

#### Molecular data

Here is a table of supported modalities and source formats.

| **Modalities**          | **Formats**                                                                                           |
| ----------------------- | ----------------------------------------------------------------------------------------------------- |
| Bulk RNAseq             | Count matrix (.txt / .tsv / .csv); AnnData (.h5ad)                                                    |
| Single cell RNAseq      | Matrix Market (.mtx + .tsv); HDF5 (.h5); AnnData (.h5ad); Seurat object (.rds)                        |
| Spatial transcriptomics | Matrix Market (.mtx + barcodes.tsv + features.tsv); HDF5 (.h5); AnnData (.h5ad); Seurat object (.rds) |
| WES / WGS               | VCF                                                                                                   |
| Proteomics              | Normalized intensity matrix (.txt / .tsv / .csv); AnnData (.h5ad)                                     |

#### Imaging data

Here is a table of supported modalities and formats.

| **Modalities**             | **Formats**                                 |
| -------------------------- | ------------------------------------------- |
| Histology (H\&E WSI)       | .tif, .tiff, .svs, .dcm, .svs, .ndpi, .mrxs |
| Immunohistochemistry (IHC) | .tif, .tiff, .svs, .dcm, .svs, .ndpi, .mrxs |

Note that Owkin developed several imaging processing pipelines that can be applied to imaging data, including:

* Cell segmentation and cell annotation via the [HIPE](https://arxiv.org/abs/2508.09926) model . Resulting cell-type quantifications are then saved (format: .csv) and used by K pro.
* IHC score extraction with proprietary models (*e.g.*, HER2 score, NMR, etc.). Resulting patient-level scores are then saved and used by K-pro.

Self Supervised Features extraction via [Foundation Models](https://arxiv.org/html/2501.16239v1#S4): slides are divided into tiles from which latent representations are computed, saved (format: .npy)


---

# 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/understand-your-data/supported-modalities.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.