# I'm interested in FinnGen rare variant phenotypes

The FinnGen project is fortunate to have >116k rare coding variants included, many of which are variants specific to the [Finnish population bottleneck](https://github.com/finngen-user-documentation/Draft_of_FG_Analyst_Handbook/blob/master/where-to-begin.../broken-reference/README.md). The section [Genotype Arrays Used](/finngen-data-specifics/red-library-data-individual-level-data/genotype-data/affymetrix-chip-and-its-design.md) describes the design and contents of the genotyping chip in more detail.

### Variants

One advantage of FinnGen is that Finnish clinicians can use FinnGen to check variants they may have found in screening Finnish families to help determine if they are causative. Since these are Finnish-specific variants, they are often not found in more international resources such as ClinVar.

Variants can be classified by their **frequency**:

* **Common variant** refers to variants **> 1%** and these will be most commonly found as imputed variants.
* **Low-frequency variant** refers to variants with **0.1-1%** frequency in the population. These are usually run on the chip but sometimes are common enough that they may also be [imputed](/background-reading/imputation.md).
* **Rare variant** usually refers to variants with **<0.1%** frequency in the population. These are usually available only in chip data.

(Ultra-rare variants are usually not present and FinnGen does not run gene-level burden tests such as SKAT-O. You can check [Genebass](https://genebass.org/) for burden information of ultra-rare variants in UKBB, although this does not contain FinnGen data, it will give you an idea of the values in other populations.)

### Available tools

Which tools are available depend on the frequency of the variant. Below is a map of tools.

Data availability:

* Green boxes = [green data access,](/faq/about-finngen-access-and-accounts/do-i-need-red-or-green-data-access.md)
* Red boxes = [red-level Sandbox access](/faq/about-finngen-access-and-accounts/if-i-already-have-green-data-access-how-do-i-apply-for-red.md).

<figure><img src="/files/r6HG1kPvhutNnIhctciR" alt=""><figcaption></figcaption></figure>

More about [Coding variant results including CHIP EWAS (Exome-Wide Association Scan)](/finngen-data-specifics/green-library-data-aggregate-data/core-analysis-results-files/chip-gwas.md) and Chip association browser <https://dev2.finngen.fi/>.

If you are interested in **all the coding variants in a particular gene**, you can go to [PheWeb](http://results.finngen.fi) and then just type in the name of your gene. At the bottom, you will see all the *imputed* variants and any associations they may have to FinnGen phenotypes. Here is what is shown for TSHR:

![Gene Level Table of coding variants from PheWeb](/files/nqshuaiEd3ePFNwcUu4K)

Currently, to work with rarer variants you will need red-level Sandbox access.

### How to work with rarer variants

* **Check genotyping quality via the** [**Cluster Plots**](/working-in-the-sandbox/working-with-genotype-data/cluster-plots.md). (You can find all the cluster plots from the [**green library**](/finngen-data-specifics/green-library-data-aggregate-data.md), but you will not be able to fix the calls or run a phenotypic analysis without red-level access.) Or use the [**Genotype Browser how to**](/working-in-the-sandbox/working-with-genotype-data/genotype-browser.md) to view cluster plots and [**Rare Variant Calling in V3**](/working-in-the-sandbox/working-with-genotype-data/rare-variant-calling-in-v3c.md) to fix calls manually.
* **Look** at your variant **in the public resource** [**Gnomad**](https://gnomad.broadinstitute.org/) and check that it has been seen in Finland and what its allele frequency is. This can help you estimate if you have the correct number of heterozygotes (Finnish allele frequency from Gnomad v2 [**number of individuals in current data freeze**](/finngen-data-specifics/finngen-data-freezes-and-releases.md) = roughly the number of copies/hets for a rare or low frequency variant)
* **Run** [**CodeWas**](/working-in-the-sandbox/which-tools-are-available/cohort-operations-tool-co/explore-code-and-endpoint-enrichments-with-co.md) with [**Cohort Operations tool**](/working-in-the-sandbox/which-tools-are-available/cohort-operations-tool-co.md) to see which medical codes and FinnGen endpoints the variant is associated with. Use of Cohort Operations needs no coding skills. The other option to explore medical codes and FinnGen endpoints association is to run a PheWAS (see the section [**Variant PheWas**](/working-in-the-sandbox/working-with-genotype-data/variant-phewas.md) and note also that we have a section on [**Interpreting rare-variant analysis results**](/working-in-the-sandbox/working-with-genotype-data/interpreting-rare-variant-analysis-results.md)). Running PheWAS requires some experience with R programming.
* See also [**General workflows for the most common analyses**](/working-in-the-sandbox/general-workflows-for-the-most-common-analyses.md) describing the most common workflows researchers are conducting in the Sandbox with the FinnGen. The methods described for **genotype variant analysis** suits also for exploring rare variants. These methods need no programming skills.

Using Sandbox requires red-level access.

![Gnomad variant display](/files/rmd1SCMDsrux9Vc13paM)


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.finngen.fi/where-to-begin.../im-interested-in-finngen-rare-variant-phenotypes.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
