> For the complete documentation index, see [llms.txt](https://help.connected.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.connected.illumina.com/emedgene/emedgene-analyze-manual/reviewing_a_case/phenotypic-match/phenotypic_match_strength.md).

# Phenotypic match strength

Each phenotype observed in the proband is compared to the phenotypic profile of the selected disease. Based on how closely each proband phenotype matches the disease phenotype profile, a similarity level is assigned.

On the [Evidence page](/emedgene/emedgene-analyze-manual/reviewing_a_case/evidence_page.md) and in the Variant page [Summary tab](/emedgene/emedgene-analyze-manual/variant_page/summary_section.md), each HPO term listed for the proband is marked with an icon that shows how similar it is to the phenotypes reported for the disease.

## Phenotypic similarity levels

<img src="/files/tjf6rLpkZe267ARZewv5" alt="" data-size="original">**Exact match**

The proband phenotype is exactly the same as one listed in the disease’s clinical description.

![](/files/4pRy7z97DFNdhaQmnMYs)**Match by ascendance/descendance**

The proband phenotype is a direct ancestor or descendant of a disease phenotype in the Human Phenotype Ontology (HPO) hierarchical tree, up to 7 steps apart.

<img src="/files/RAcQSnjwwTHVGjMkPNCa" alt="" data-size="original">**Indirect match**

The proband phenotype lies within a 4-step range in the HPO graph from the disease phenotype but is not its direct ancestor or descendant. While indirect match may highlight potential connections, we advise users to interpret it carefully because it may include phenotypes from different branches of the HPO ontology that are not biologically related.

![](/files/QEeV2s3BVf1lTDE1EaNG)**No match**

The proband phenotype does not appear in the disease’s phenotype list and is not connected to it within the range of match by ascendance/descendance and indirect match.

## Learn more

<table data-view="cards"><thead><tr><th></th><th></th><th></th></tr></thead><tbody><tr><td><strong>Phenotypic match</strong></td><td>Overview of phenotypic match scoring, use cases, and related pages.</td><td><i class="fa-arrow-up-right-from-square">:arrow-up-right-from-square:</i> <a href="/pages/Nl3wTB3tS4WifWcXMiEK">Learn more</a></td></tr><tr><td><strong>Phenotypic match models</strong></td><td>Review the available scoring approaches and their score ranges.</td><td><i class="fa-arrow-up-right-from-square">:arrow-up-right-from-square:</i> <a href="/pages/1zGgR9anzOmdOcGBbssn">Learn more</a></td></tr><tr><td><strong>Phenotype weights (v100.40.0+)</strong></td><td>Adjust phenotype weights to refine live <strong>Phenomeld</strong> prioritization.</td><td><i class="fa-arrow-up-right-from-square">:arrow-up-right-from-square:</i> <a href="/pages/ti4PJF5K4tgafQc5rzdA">Learn more</a></td></tr></tbody></table>


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://help.connected.illumina.com/emedgene/emedgene-analyze-manual/reviewing_a_case/phenotypic-match/phenotypic_match_strength.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.