> 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/workbench-and-pipeline-updates/new-in-emedgene-v100_41/v100_41_patches.md).
# V100.41 Patches
| Patches | Date |
|---|
| V100.41.100 | October 7, 2026 |
### V100.41.100 Update (October 7th, 2026)
#### Features
* Analysis Tools | Added the ability for labs to include a numeric and sortable customized data field. Only one custom data field – text or numeric, is possible per case.
* Analysis Tools, Variant Page | Visualization | The default BAM/CRAM track settings for TRA/INV/BND variants have been optimized. The view is now grouped by Chimeric, shows soft clips and colors by Pair Orientation and Insert Size.
#### Fixed Issues
* Pipeline | Fixed gnomAD annotations for INV variants.
* Lab Tab | Case validation | Fixed issues where cases could get the wrong quality status - failed or warning.
* Lab Tab | Improved error messages for gene coverage.
* Genome View | Fixed multiple issues with visualization and colocation plots.
* Analysis Tools | Preset Filters | Fixed an issue where preset count wasn’t working for cases in retention.
* Analysis Tools | Fixed an issue where analysis tools table loaded variants before Preset Filters were loaded.
* Analysis Tools, Variant Page | Fixed a performance issue with IGV that caused Emedgene application to crash when adjusting zoom.
* Variant Page | For CNVs with multiple Curate annotations, the variant interpretation now allows the import of any of those interpretation texts.
* \[Hotfix August 30, 2026] Variant Page | Gene interpretation and Notes sections will not automatically load for CNVs as this can cause cases to fail.
* Variant Page | Connected Variants | Fixed multiple issues for display of SNV, CNV from the TruPath MRJD caller when selecting Hap connections. The Connected Variants only displays 50 variants, but this is a live query for every connection type or copy.
* Curate | Fixed an issue where gene curations without a status were excluded from annotation.
* Curate | Fixed an issue in Article curation module where variants disappeared from the UI, and only appeared on refresh.
* Curate | Improved error messaging for adding variants with c. nomenclature.
* Organization Settings | Case Settings | Additional information fields | Restricted the number of custom fields to 50.
* Network | Resolved an issue where network creation failed due to missing POC.
* API | Curate Export | Fixed an issue where export was not returning all variants.
* API | Swagger | Fixed API call to download gene lists.
* DRAGEN Array Integration | Fixed an issue with a sample ID mismatch.
* General performance improvements for Preset Filters, APIs.
* Propagations from 100.40.300.
---
# 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/workbench-and-pipeline-updates/new-in-emedgene-v100_41/v100_41_patches.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.