> 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/connected-insights/interpret-and-report/cm-cases-details/cm-merge-cases.md).

# Merge Cases

Connected Insights supports merging RNA and DNA cases with the same case subject. For instructions on how to change the case subject, refer to [Case Details](/connected-insights/interpret-and-report/cm-cases-details.md). Merge cases as follows.

1. Select the applicable case.
2. Select the **Overview** tab, and then select **Case Details** to open the Case Details pane.
3. Select **Related Cases**. All cases (including DNA, RNA, and DNA+RNA cases) with the same case subject display.
4. Select **Merge Cases**.
5. Configure the case as follows.\
   a. To merge a DNA case, select **Select DNA Case** and choose from a drop-down list with applicable DNA cases.\
   b. To merge an RNA case, select **Select RNA Case** and choose from a drop-down list with applicable RNA cases.\
   c. \[Optional] To change the case number, enter a new case ID.\
   d. Select the applicable definition from the Confirm Test Definition drop-down list.\
   This option defaults to the DNA case test definition.\
   e. Select the disease associated with the merged case.\
   This field can be the same or different disease from the one that is in the DNA and RNA cases that are you merging.
6. Select **Confirm**.
7. Make sure that the new case displays under the Case Timeline in the Case Details sidebar. When the merged case is selected, Connected Insights indicates that the case was created from merging the RNA and DNA cases.


---

# 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/connected-insights/interpret-and-report/cm-cases-details/cm-merge-cases.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.