> 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/more-release-notes/new_in_emedgene_223_-jun_15-_2021.md).

# New in Emedgene 2.23 (Jun 15, 2021)

1. [Unified workflow for GRCh38 & GRCh37](#h_419c8648aa)
2. [*Cases tab:*](#h_b506767523) [new design and functionality](#h_b506767523)

***

## **Unified workflow for GRCh38 & GRCh37**

With gnomAD no longer releasing GRCh37 versions, we expect increased lab transitions to GRCh38. We have incorporated the two most requested GRCh38 features in this release, thus offering you complete support for GRCh38:

* A totally unified workflow for **tests running on different** [**reference genomes**](/emedgene/emedgene-analyze-manual/tertiary-analysis-pipeline/which_reference_genomes_can_i_use.md) **in the same organization**.
* A solution for historical data. Curated and historical **data are automatically lifted over on the fly** and made available as you perform your analysis (in either reference).

***

## ***Cases tab:***** new design and functionality**

The [*Cases tab*](broken://pages/deyVERpzgIGXl6ABgAut) has a brand new design, but more importantly - a new feature set:

* [**grouping**](/emedgene/emedgene-analyze-manual/getting_around_the_platform/cases_tab/browse_and_select_cases.md) cases by *Case Status,*
* refined case [**filtering**](/emedgene/emedgene-analyze-manual/getting_around_the_platform/cases_tab/browse_and_select_cases.md),
* **effortless** [**customization**](/emedgene/emedgene-analyze-manual/getting_around_the_platform/cases_tab/browse_and_select_cases.md) [of the Cases table view](/emedgene/emedgene-analyze-manual/getting_around_the_platform/cases_tab/browse_and_select_cases.md),
* and more!

![](https://1131024994-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FGCW0DnLlE7QjoZPNmKIi%2Fuploads%2Fgit-blob-3c171c5867fca6cc028a83907324a476a4f2b2e0%2Fnew_in_emedgene_223_-jun_15-_2021_1_unnamed.gif?alt=media)


---

# 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/more-release-notes/new_in_emedgene_223_-jun_15-_2021.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.