> 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/partek/partek-flow/user-manual/settings/components/library-file-management/adding-a-variant-annotation-database.md).

# Adding a Variant Annotation Database

Click the **+ Add variant annotations** button under the *Variant annotations* section header on the [library file management page](/partek/partek-flow/user-manual/settings/components/library-file-management/library-file-management-page.md).

If you are using a human - hg19 assembly, variant annotation databases from various sources will appear in the *Variant annotation* drop-down list (Figure 1). Available variant annotation database sources include:

* dbSNP
* Kaviar
* NHLBI Variant Server
* 1000 Genomes

Multiple versions of the above databases are available. For human - hg38, only dbSNP is currently available. This list is periodically updated.

![Figure 1. For human - hg19, automatic downloads of various variant annotation databases are available from the Partek repository](https://1384254481-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FJVEESmJAPppJ3ijFq5aR%2Fuploads%2Fgit-blob-111f8f3339ec226967eb5a989569cbc91bc9a6ce%2Fadd-var-anno-hg19.png?alt=media)

Choose a database from the drop-down list, select the **Download variant database** radio button and click **Create**.

If you prefer to add a custom variant annotation database, perhaps from another source or 'gold-standard' validated variants, choose **Add variant database** from the *Variant annotation* drop-down list (Figure 2). Name the variant annotation database by typing into the *Custom Name* box and click **Create**. Characters such as $ \* | \ : " < > ? / % cannot be used in custom names. A variant annotation database can be added from the *Partek Flow Server* or a *URL* download link. The behavior of each option is similar to when importing a reference sequence (see [*Adding a Reference Sequence*](/partek/partek-flow/user-manual/settings/components/library-file-management/adding-a-reference-sequence.md)). When browsing for files on the Partek Flow server, only the files with relevant file extensions will be visible (.vcf and various compressed formats).

![Figure 2. Add a custom variant annotation database](https://1384254481-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FJVEESmJAPppJ3ijFq5aR%2Fuploads%2Fgit-blob-f723fdf3f79708c60f1a2c0c173b59a2d5747bbe%2Fadd-var-anno-custom.png?alt=media)

## Additional Assistance

If you need additional assistance, please visit [our support page](http://www.partek.com/support) to submit a help ticket or find phone numbers for regional support.


---

# 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/partek/partek-flow/user-manual/settings/components/library-file-management/adding-a-variant-annotation-database.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.