> 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/release-notes/change_log/change_log_pipeline_30.md). # Change log pipeline 30 ## Features * Feature | New XAI for CNVs and compound heterozygous SNV-CNV variants * Feature | New and more accurate phenotypic match model, Phenomeld * Feature | Support for DRAGEN 4.0 with ML for customers running their own DRAGEN and through Emedgene * Feature | Lab Page | Gene Coverage - Region coverage statistics will now be calculated based on the case’s kit associated BED file * Feature | Default BED files for coding regions, clinical regions (used for exome) and genomes were updated with latest RefSeq Curated and Gencode versions. * Feature | Re-including Polyphen annotation, and update to consider most severe value * Feature | Support for DRAGEN Force Genotyping caller ## Bug Fixes * Bug Fix | Quality metrics for duplications when CN > 3 --- # 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/release-notes/change_log/change_log_pipeline_30.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.