> 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/launching-analysis/creating_a_single_case/2.-family-tree/add_a_sample.md).

# Adding a sample

![](https://1131024994-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FGCW0DnLlE7QjoZPNmKIi%2Fuploads%2Fgit-blob-36f9e0f4f47e03eadb00e4b29b259692867d5b21%2Fadd%20a%20sample.png?alt=media)

You can choose one of the following options:

* **Existing sample**: Pick one of the samples already loaded on the platform
* **Upload new sample**: Upload files from your PC and enter sample name
* **Choose from storage**: Choose files from your cloud storage and enter sample name
* **No sample**: Postpone uploading files but proceed with case creation or skip uploading files for family members other than Proband

{% hint style="warning" %}

* The Add New Case flow does not validate that sample IDs are unique or that input files are uncorrupted. Please ensure sample IDs are unique and that input files are valid before creating the case.
* A case won't run if Proband sample files are missing. However, sample files are not mandatory for the rest of the family members (although highly recommended).
* When choosing an existing file path, the samples used may be cached from the original run. For a top-up flow please use a new file path.
* When you are loading sample files from your PC or choosing them from the storage, and there is more than one file per sample, please ensure that **all** the necessary files are simultaneously selected in the upload pop-up. You may only select one file type per case (i.e. you may not select both a .vcf and a .bam at the same time).
  {% 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/launching-analysis/creating_a_single_case/2.-family-tree/add_a_sample.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.