> 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_workbench_228.md).

# Change log workbench 2.28

## **Features:**

* Support for interpreting STRs - annotation with 1K genomes and gnomAD, custom visualization, related cases
* Support for interpreting SV deletions and duplications. ACMG automated classification tool applies to SV del/dups.
* Emedgene Curate supports gene curation - save and view gene interpretations, save preferred transcripts.
* Emedgene Curate - new private networking component for opted in laboratories
* ACMG classification improvements
* In analysis tools disease column, hover to view see all related diseases
* New Filter under Variant Effect, Advanced, Curate - select pathogenicity
* View allele frequency full decimal number
* Var Page | Quality Tab | Add tooltip for quality parameter threshold
* Var Page | Option to import variant interpretation summary from Curate
* Header update - added Illumina logo

## **Bug fixes:**

* Export variant to Curate bug fix
* Organization Settings | Management | Fix broken create group and add users link
* Analysis Tools | Filters | Compound heterozygous filter now supports CNV del/SNV
* Analysis Tools | Filters | ACMG | VUS renamed Uncertain
* Reporting | View reports for past cases even if template has been archived
* API | Fixed error where case type wasn’t saved


---

# 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_workbench_228.md?ask=<question>&goal=<user_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.