> 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/annotation/faqs/annotator-vs-data-update.md). # Understanding Annotation updates Updating the Annotation Engine vs updating Annotation Data Sources ### Background Updates to DRAGEN Annotation can be broadly categorized into two categories: * Annotation Engine update * Annotation Data Source update Understanding the nature of these two types of updates is key when it comes to updating annotation. ### Annotation Engine update The annotator is the engine that contains logic for core annotations such as computing `variant consequences`, `HGVS` notations, mapped positions (e.g. `CDNA`, `CDS`, `protein` positions), detecting `gene fusions`, etc., and perform annotation lookups from external data sources such as `dbSNP`, `gnomAD`, `ClinVar`, `OMIM`, etc. also known as supplementary annotations (SA). Update to the annotator entails new features or bugfixes to the compute or lookup mechanism. This is completely independent of the data update such as updating `dbSNP` from v154 to v155. In other words, the same annotator can annotate with `dbSNP v154` and `dbSNP v155` when provided with the appropriate data files. ### Annotation Data Source update The annotator uses data from various sources (listed in [Introduction](/annotation/introduction/readme.md)). For example, gene models used for core annotations are obtained from `RefSeq` and `Ensembl`. Supplementary annotations come from various sources such as `dbSNP`, `gnomAD`, `ClinVar`, `OMIM`, etc. Any of these data can be updated without updating the annotator as long as the file formats are compatible. ### Update scenarios Let us look at a few update scenarios. | Requirement | What needs to be updated /added | Suggested action | | -------------------------------- | ----------------------------------- | ---------------------- | | New transcripts and gene symbols | Cache files from RefSeq and Ensembl | Run DataManager | | Update ClinVar | ClinVar SA files | Run DataManager | | New external annotation | New SA files required | Submit feature request | | New annotation feature | Annotation Engine | Submit feature request | --- # 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/annotation/faqs/annotator-vs-data-update.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.