> 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/reviewing_a_case/phenotypic-match/phenotypic-match-models.md).

# Phenotypic match models

Proprietary phenotypic match models assess how closely a gene’s associated disease phenotype matches the proband’s phenotype profile. A degree of similarity is resembled by the phenotypic match score. The phenotypic match score indicates the degree of similarity between the proband’s phenotype set and the phenotype set of the best-matching gene-related disease.

If a gene is linked to multiple diseases, the model compares the proband’s phenotypes with each disease profile individually. The highest score determines the best match, and this disease is automatically displayed in the Evidence graph. The Phenomatch and Phenomeld scores shown in the variant table correspond to this best-matching disease, even if the associated disease is manually updated.

{% hint style="info" %}
**Note:** Case reanalysis causes Phenomatch/Phenomeld scores to be recalculated.
{% endhint %}

<table><thead><tr><th width="403.09088134765625">Phenotypic match model</th><th>Score interpretation</th></tr></thead><tbody><tr><td><strong>Phenomeld</strong> represents the cutting edge of phenotypic matching models from Emedgene. As an advanced iteration of Phenomatch – Powered by AI, it delivers superior gene prioritization.</td><td><p>The score ranges from 0 to 2:</p><ul><li>A score of 0 indicates no phenotypic match,</li><li>A score above 0.15 suggests a moderate match,</li><li>A score above 0.7 indicates a strong phenotypic match.</li></ul></td></tr><tr><td><strong>Phenomatch – Powered by AI i</strong>dentifies genes with disease phenotypes that <em>loosely</em> match the proband’s HPO terms.</td><td>The score ranges between 0 and 1 where 1 is the strongest match.</td></tr><tr><td><strong>Phenomatch – High Specificity</strong> identifies genes with disease phenotypes that <em>exactly</em> match the proband’s HPO terms.</td><td>The score ranges between 0 and 1 where 1 is the strongest match.</td></tr><tr><td><strong>Phenomatch with Unknown</strong> identifies genes of unknown significance based on indirect links to proband phenotypes. These links may include mouse models, gene families, pathways, and other functional associations.</td><td>The score ranges between 0 and 1 where 1 is the strongest match.</td></tr></tbody></table>

## 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="/emedgene/emedgene-analyze-manual/reviewing_a_case/phenotypic-match.md">Learn more</a></td></tr><tr><td><strong>Phenotypic match strength</strong></td><td>Interpret exact, indirect, and no-match phenotype relationships.</td><td><i class="fa-arrow-up-right-from-square">:arrow-up-right-from-square:</i> <a href="/emedgene/emedgene-analyze-manual/reviewing_a_case/phenotypic-match/phenotypic_match_strength.md">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="/emedgene/emedgene-analyze-manual/reviewing_a_case/phenotypic-match/phenotype-weights-v100.40.0+.md">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 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/reviewing_a_case/phenotypic-match/phenotypic-match-models.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.