> 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/str_calling_and_interpretation.md).

# Tertiary analysis of STR variants

## Short tandem repeats

*Short tandem repeats (STRs)* are genomic regions composed of repeated short DNA sequences. An increase in the number of repeats is a *repeat expansion*, and a decrease is a *repeat contraction*. Repeat expansions and contractions may alter gene expression or function.

The platform shows repeat counts per allele and highlights values that fall in normal, intermediate, pathogenic, or unknown ranges.

***

## STR variant processing

Each STR variant goes through the following steps. They determine whether the variant is called, whether it appears in the case, and how it is analyzed.

{% stepper %}
{% step %}

### Calling

The DRAGEN STR caller calls only the loci in the STR catalog it runs with. Loci outside that catalog are not called and do not reach Emedgene.

When Emedgene runs DRAGEN secondary analysis, STR calling runs only for whole-genome samples, and only if STR calling is enabled in the variant caller settings.
{% endstep %}

{% step %}

### STR catalog filtering (v100.40 and earlier)

On tertiary pipeline v100.40 and earlier, Emedgene excludes STR variants which are not in the DRAGEN v4.2 expanded variant catalog. This filter applies independently of secondary analysis pipeline, and DRAGEN version it used.

The catalog is in the following files.

{% file src="/files/lrw1ojHlbWkuXUGmUlKt" %}

{% file src="/files/Aq4LMvsMmyYQoQ9vRFfS" %}

From v100.41, this filter no longer applies.From v100.41, this filter no longer applies.
{% endstep %}

{% step %}

### Region of interest filtering

Emedgene keeps STR variants that fall within the case's [region of interest](https://help.bioinsight.illumina.com/emedgene/emedgene-analyze-manual/launching-analysis/creating_a_single_case/3.-case-info/case-type-and-region-of-interest/genomic_regions_by_case_type.md) and excludes the rest before annotation, so they do not reach test results.

{% hint style="success" %}
Research Genome cases have no default region of interest. To analyze loci outside the default region of interest, use a Research Genome case or a custom region of interest that includes them.
{% endhint %}
{% endstep %}

{% step %}

### Population data annotation

Variants are annotated with population data: the distribution of repeat counts in the gnomAD population and 1000 genome project data.
{% endstep %}

{% step %}

### Pathogenicity data annotation

Variants from gnomAD known disease-associated tandem repeat loci are annotated with their corresponding pathogenicity data: the repeat-count range for each significance class. For the list of loci, see [STR loci annotated with gnomAD pathogenicity data](https://help.bioinsight.illumina.com/emedgene/emedgene-analyze-manual/tertiary-analysis-pipeline/str_calling_and_interpretation/str-loci-annotated-with-gnomad-pathogenicity-data.md).
{% endstep %}

{% step %}

### AI Prioritization

Emedgene AI will prioritise only STR variants from [STR loci considered by AI Shortlist](https://help.bioinsight.illumina.com/emedgene/emedgene-analyze-manual/tertiary-analysis-pipeline/str_calling_and_interpretation/str-loci-considered-by-ai-shortlist.md).
{% endstep %}
{% endstepper %}

{% hint style="info" %}
Population and pathogenicity annotations can use different dataset versions, as shown on the **Versions** tab under [**Population Databases**](https://help.bioinsight.illumina.com/emedgene/emedgene-analyze-manual/reviewing_a_case/versions_tab.md#population-databases) and under [**Variant Databases**](https://help.bioinsight.illumina.com/emedgene/emedgene-analyze-manual/reviewing_a_case/versions_tab.md#variant-databases).
{% endhint %}

***

## Learn more

<table data-view="cards"><thead><tr><th></th><th></th><th></th></tr></thead><tbody><tr><td><strong>STR loci considered by AI Shortlist</strong></td><td>The genes that AI Shortlist considers for STR variants, with the disease-associated locus for each.</td><td><i class="fa-arrow-up-right-from-square">:arrow-up-right-from-square:</i> <a href="https://help.bioinsight.illumina.com/emedgene/emedgene-analyze-manual/tertiary-analysis-pipeline/str_calling_and_interpretation/str-loci-considered-by-ai-shortlist.md">Learn more</a></td></tr><tr><td><strong>STR loci annotated with gnomAD pathogenicity data</strong></td><td>The gnomAD loci that Emedgene annotates, with the repeat-count range for each significance class.</td><td><i class="fa-arrow-up-right-from-square">:arrow-up-right-from-square:</i> <a href="https://help.bioinsight.illumina.com/emedgene/emedgene-analyze-manual/tertiary-analysis-pipeline/str_calling_and_interpretation/str-loci-annotated-with-gnomad-pathogenicity-data.md">Learn more</a></td></tr><tr><td><strong>Default region of interest kits</strong></td><td>Default region of interest BED files by case type, with download links.</td><td><i class="fa-arrow-up-right-from-square">:arrow-up-right-from-square:</i> <a href="https://help.bioinsight.illumina.com/emedgene/emedgene-analyze-manual/launching-analysis/creating_a_single_case/3.-case-info/case-type-and-region-of-interest/genomic_regions_by_case_type.md">Learn more</a></td></tr><tr><td><strong>STR quality metrics</strong></td><td>Quality metrics and the overall quality rule for STR variants.</td><td><i class="fa-arrow-up-right-from-square">:arrow-up-right-from-square:</i> <a href="https://help.bioinsight.illumina.com/emedgene/emedgene-analyze-manual/variant_page/quality_section/quality-metrics-per-variant-type/str-quality-metrics.md">Learn more</a></td></tr><tr><td><strong>Versions tab</strong></td><td>Versions of the tools, data sources, and knowledge bases used to analyze a case.</td><td><i class="fa-arrow-up-right-from-square">:arrow-up-right-from-square:</i> <a href="https://help.bioinsight.illumina.com/emedgene/emedgene-analyze-manual/reviewing_a_case/versions_tab.md">Learn more</a></td></tr></tbody></table>


---

# 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/str_calling_and_interpretation.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.
