> For the complete documentation index, see [llms.txt](https://help.bioinsight.illumina.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.bioinsight.illumina.com/emedgene/emedgene-analyze-manual/tertiary-analysis-pipeline/how_are_mnvs_handled_on_the_platform.md).

# Processing multi-nucleotide variants

Unlike single-nucleotide variants (SNVs), a multi-nucleotide variant (MNV) represents a single event involving multiple consecutive bases. In Emedgene, small variants are recognized as those comprising an MNV if they are located within a 2-nucleotide distance.

{% hint style="warning" %}

## Limitations

Currently, Emedgene does not fully support MNV functionality. The following features are restricted:

* **Export to Curate**: Blocked because Curate does not support MNVs.
* **AI Shortlist**: MNVs are not included in the AI shortlist.
* **ACMG Classification**: Disabled for MNVs.
  {% endhint %}

## From v100.39.0 case pipeline onward:

Emedgene recognizes MNV as a distinct variant type and supports ingestion from VCF, annotation, and filtering.

Each MNV is represented and annotated as:

* An MNV itself (eg, AG>TC)
* Individual SNVs derived from the MNV (eg, A>T and G>C), for compatibility with existing tools and workflows

Both the MNV and its underlying SNVs display the "Suspected MNP" badge in the [Clinical significance tab](/emedgene/emedgene-analyze-manual/variant_page/clinical_significance_section.md).

## Up to v38.0 case pipeline:

During data processing, MNVs are split into consecutive SNVs. The resulting SNVs are annotated with **INFO** and **FORMAT** fields that mirror the original record.

SNVs that comprise an MNV display the "Suspected MNP" badge in the [Clinical significance tab](/emedgene/emedgene-analyze-manual/variant_page/clinical_significance_section.md).


---

# 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://help.bioinsight.illumina.com/emedgene/emedgene-analyze-manual/tertiary-analysis-pipeline/how_are_mnvs_handled_on_the_platform.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.