> 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/emedgene-analyze-manual/settings/management/test-statuses.md).

# Case statuses

In the Case statuses card, you can tailor how case statuses appear and function to better align with your workflow:

* Create custom [case statuses](/emedgene/emedgene-analyze-manual/reviewing_a_case/case_status.md) to reflect your team's specific processes
* Remove unused statuses to keep the list clean and relevant. Only statuses that are not currently assigned to any case can be removed
* Rearrange the order of statuses by drag-and-drop to match your preferred case interpretation flow. The updated order is reflected in:
  * The Status field dropdown in the Cases table
  * The top bar of the individual case page

{% hint style="warning" %}
After making changes, scroll down and click **Save**!
{% endhint %}

## Stale Days

![](https://1131024994-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FGCW0DnLlE7QjoZPNmKIi%2Fuploads%2Fgit-blob-14f3c41b4aa578dccc4373cb9be16602da3ca70c%2Fimage%20\(54\).png?alt=media)

Define the number of days that must pass without the case being finalized for it to be classified as "stale" and subsequently factored into the Stale Cases statistics on the Dashboard.

{% hint style="warning" %}
After making changes, scroll down and click **Save**!
{% endhint %}


---

# 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/emedgene-analyze-manual/settings/management/test-statuses.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.