> 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/annotations-from-organization-databases.md).
# Annotations from organization databases
Annotations from organization databases appear in various parts of the platform, each showing certain details.
### Historic and noise databases
#### Variant table
* Allele frequency—in "\[Organization DB] AF (%)" column
* Allele count—in "\[Organization DB] AF (#)" column
#### Variant page
* **Summary tab** :arrow-right-long: **Population summary card**
* Allele count—in "Allele count" field
* Hom/Hemi count—in "Hom/Hemi count" field
* The last 10 samples—in "Last 10 samples" field
* **Population statistics tab** :arrow-right-long: **Organization DBs**
* Allele frequency—in "Allele frequency" column
* Allele count—in "Allele count" column
* Hom/Hemi count—in "# of Homozygotes" column
* Allele number—in "Total" column
* **Visualization tab** :arrow-right-long: **Population data**\
"\[Organization DB]" tracks display variants from organization databases. Left-click a variant in a track to review variant details:
* Allele frequency
* Allele count
* Allele number
* Het count
* Hom/Hemi count
* The last 10 samples
### Curated databases
#### Variant table
* Color-coded "\[Organization DB]" badge based on **pathogenicity** in the Curated DB—"Known variants" column
#### Variant page
* **Summary tab** :arrow-right-long: **Clinical significance card**\
Color-coded "\[Organization DB]" badge based on **pathogenicity** in the Curated DB
* **Clinical significance tab** :arrow-right-long: **Clinical significance card**\
Color-coded "\[Organization DB]" badge based on **pathogenicity** in the Curated DB
---
# 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/annotations-from-organization-databases.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.