> 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/getting_around_the_platform/cases_tab/case_details/family-tree.md).

# Family tree

The Family tree tab includes the following information:

* Pedigree diagram. Pedigree legend can be found [here](/emedgene/emedgene-analyze-manual/launching-analysis/creating_a_single_case/2.-family-tree/family_tree_legend.md).
* Sample details for each family member:
  * Phenotypes. For family members other than the test subject, phenotypes are categorized as:
    * Related—directly match one of the proband’s phenotypes
    * Unrelated—do not match any of the proband’s phenotypes
  * Medical Condition – Indicates whether the individual is considered Healthy or Affected in the case
  * Sex. Specified by the user
  * Age. Automatically calculated in years based on the provided date of birth
  * Maternal and Paternal [ethnicity](/emedgene/emedgene-analyze-manual/launching-analysis/creating_a_single_case/2.-family-tree/supported_parental_ethnicities.md)—ethnic background of the proband’s parents
  * BAM file location. Shown where relevant


---

# 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/getting_around_the_platform/cases_tab/case_details/family-tree.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.