> 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/variant-visualization/variant-visualization-tool/visualization-tracks/knowledge-base-tracks.md). # Knowledge base tracks These [visualization tracks](/emedgene/emedgene-analyze-manual/variant-visualization/variant-visualization-tool/visualization-tracks.md) add curated gene and region knowledge. ## OMIM The **OMIM** track displays genes linked to known genetic disorders. Use it to review disease associations, inheritance patterns, and access OMIM entries for deeper clinical context.

OMIM track.

## ClinGen The **ClinGen** track highlights genes or regions with clinically reviewed dosage sensitivity scores. The track uses color coding by evidence level. Use it to support pathogenicity and genomic stability assessment.

ClinGen track.

## Segmental Duplications The **Segmental Duplications** track shows long, highly similar DNA regions that occur in more than one place in the genome. Use this track to review CNVs in regions where duplicated sequence may affect interpretation. Select a region in the **Seg dup** track to view more information about that region: * **Chr:** Chromosome number * **Pos:** Genomic position * **End:** End position * **SVLEN:** Region length * **SVTYPE:** Structural variant type * **Type:** Region type, such as segmental duplication, centromere, telomere, or heterochromatin.

Segmental Duplications track.

## Decipher Known Variants The **Decipher Known Variants** track displays genotype and phenotype data from affected individuals in DECIPHER (Database of Chromosomal Imbalance and Phenotype in Humans using Ensembl Resources). Track color reflects the reported pathogenicity. {% hint style="info" %} This track is available with knowledgebases released after April 2026, regardless of pipeline version. {% endhint %} Select an entity in the **Decipher Known Variants** track to view details: * **Chr**: Chromosome number * **Start**: Start position * **End**: End position * **Strand**: Strand orientation * **Genotype**: Genotype reported for the affected individual * **Ref**: Reference allele * **Alt**: Alternate allele * **Variant\_type**: Variant type * **Variant\_class**: Variant classification * **SVTYPE**: Structural variant type (DEL or DUP) * **Length**: Variant length * **Inheritance**: Inheritance pattern * **Pathogenicity**: Reported pathogenicity * **Mean\_ratio**: Mean copy-number ratio reported for the CNV * **Contribution**: Reported contribution to the affected individual's phenotype * **Phenotypes**: Phenotypes reported for the affected individual

Decipher Known Variants track.

For DECIPHER data from unaffected individuals, see the **Decipher Population** track in [Population data tracks](/emedgene/emedgene-analyze-manual/variant-visualization/variant-visualization-tool/visualization-tracks/population-data-tracks.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/variant-visualization/variant-visualization-tool/visualization-tracks/knowledge-base-tracks.md?ask=&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.