> 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/phenotype-weights-v100.40.0+.md).

# Phenotype weights (v100.40+)

By default, all proband phenotypes have the same 1× weight in **Phenomeld** score calculation.

Use phenotype weights to focus **Phenomeld** prioritization on the phenotypes most relevant to the primary case question.

A proband may have multiple documented phenotypes. If all phenotypes carry the same weight, **Phenomeld** may prioritize genes linked to secondary or incidental findings over genes that match the core presentation.

In v100.40 and newer, you can change the weight of any proband phenotype to adjust its effect on **Phenomeld** gene prioritization.

* Emphasize phenotypes that represent key features of the suspected condition and reduce or exclude the impact of less relevant phenotypes on Phenomeld scoring.
* Add additional phenotypes and set their impact on Phenomeld scoring.

{% hint style="info" %}
You can do this:

* On v100.40 and later, in **Quick Filters** > [**Phenomatch filters**](/emedgene/emedgene-analyze-manual/reviewing_a_case/analysis-tools-tab-beta-v100.39.0+/filters_presets_panel/filters/quick-filters/phenomatch_filters.md) in **Advanced** mode.
* On v100.41 and later, also in **Query Builder** > [**Phenomatch filters**](/emedgene/emedgene-analyze-manual/reviewing_a_case/analysis-tools-tab-beta-v100.39.0+/filters_presets_panel/filters/query-builder-v100.40+/filter-list-for-query-builder.md#phenomatch-filters).
  {% endhint %}

Use the following weighting factors to control how each phenotype affects **Phenomeld** scoring:

<table><thead><tr><th width="133">Weight</th><th>Effect</th></tr></thead><tbody><tr><td><strong>Critical</strong></td><td>Applies a very high weight.</td></tr><tr><td><strong>Strong</strong></td><td>Applies an increased weight.</td></tr><tr><td><strong>Standard</strong></td><td>Applies the default weight.</td></tr><tr><td><strong>Negative</strong></td><td>Applies a negative weight.</td></tr><tr><td><strong>Ignore</strong></td><td>Applies zero weight and excludes the phenotype from the <strong>Phenomeld</strong> score calculation.</td></tr></tbody></table>

After you update phenotype weights or add additional phenotypes:

* **Phenomeld** scores are recalculated.
* Genes are re-ranked according to the recalculated **Phenomeld** scores.
* Updated scores appear in the **Weighted Phenomeld** column in the variant table.

Adjusted phenotype weights and additional phenotypes are available only for the current user session. If you close and reopen the case, the adjustments are not retained.

Adjusted phenotype weights affect **Phenomeld** scoring only. AI-based rankings, including the **AI Shortlist**, remain unchanged.

The **Weighted Phenomeld** score is not included in reports or exports.

## 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 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="/emedgene/emedgene-analyze-manual/reviewing_a_case/phenotypic-match/phenotypic-match-models.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>Phenomatch filters in the Quick Filters</strong></td><td>Apply phenotype weights and additional phenotypes in the <strong>Quick Filters</strong>.</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/analysis-tools-tab-beta-v100.39.0+/filters_presets_panel/filters/quick-filters/phenomatch_filters.md">Learn more</a></td></tr><tr><td><strong>Phenomatch filters in the Query Builder</strong></td><td>Apply phenotype weights and additional phenotypes in the <strong>Query Builder</strong>.</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/analysis-tools-tab-beta-v100.39.0+/filters_presets_panel/filters/query-builder-v100.40+/filter-list-for-query-builder.md#phenomatch-filters">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/phenotype-weights-v100.40.0+.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.