> 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-curate-manual/curate_variants/curate_variant_page/acmg-classification-card.md).

# ACMG classification card

## Card contents

The **ACMG classification card** on the [**Curate Variant page**](/emedgene/emedgene-curate-manual/curate_variants/curate_variant_page.md) lets you apply ACMG evidence tags, review the resulting score and classification, and manage tag details for the variant.

This card appears only for small variants, not copy number variants.

Use it to:

* Review the overall ACMG classification and score, plus per-tag details such as question answers, strength, user notes, and manual update history
* Activate or inactivate ACMG evidence tags, modify tag strength, and update tag notes

<figure><img src="https://1131024994-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FGCW0DnLlE7QjoZPNmKIi%2Fuploads%2Fgit-blob-9c670774c760da2537fa0add4b20a52218df75a1%2FACMG%20wide.gif?alt=media" alt=""><figcaption><p><strong>ACMG classification card</strong></p></figcaption></figure>

## ACMG score and classification calculation

The ACMG score and classification are calculated from the applied ACMG tags. When tags are added or updated, the card recalculates both values.

For SNV-specific ACMG logic, see [Logic behind ACMG classification of SNVs](/emedgene/emedgene-analyze-manual/variant_page/evidence_section/logic_behind_acmg_classification_of_snvs.md) and [ACMG SNV criteria evaluation](/emedgene/emedgene-analyze-manual/variant_page/evidence_section/acmg-snv-criteria-evaluation.md).

### Outdated ACMG schema warning

When working in **Curate**, **Emedgene** keeps track of the ACMG schema version used to calculate the ACMG score for each curated variant. Using an outdated schema may cause the classification to miss updated logic, use outdated strength definitions, or include tags that are no longer supported.

If a variant was curated with an older ACMG schema than the schema currently active in **Analyze**, a warning appears in the **ACMG classification card**. When this warning appears, you can:

* Sync the variant to the current ACMG schema on the **Curate Variant page** (v100.41 and later).
* Review and update the classification on the **Curate Variant page**.
* Review and update the classification on the **Variant page** in **Analyze**, and then send the changes to **Curate** with the [**Update**](/emedgene/emedgene-analyze-manual/variant_page/curate-actions-in-analyze/update-in-curate.md) **Curate** **action**.

### How to sync a variant to the current ACMG schema

From v100.41, you can sync a variant curated with an outdated ACMG schema to the ACMG schema currently used in your organization. The **Sync** button appears only for variants curated with an outdated schema.

Syncing keeps the existing ACMG curation for the variant:

* Tag status
* Tag strength
* Tag notes

{% hint style="warning" %}
Syncing deletes the answers to tag questions for the variant. If you need the answers, record them before you sync.
{% endhint %}

**Prerequisite:** To sync, you need to have proper [permissions](/emedgene/emedgene-analyze-manual/settings/user_roles/iam-scopes-emedgene-roles.md).

{% stepper %}
{% step %}
On the **Curate Variant page**, in the top-right corner of the **ACMG classification card**, select **Sync**.
{% endstep %}

{% step %}
In the confirmation popup, review the schema version the variant will be synced to, and then select **Apply**.
{% endstep %}
{% endstepper %}

**Result:**

* The variant uses the ACMG schema version currently used in your organization, and the outdated ACMG schema warning no longer appears.
* The sync is recorded in the [**Activities panel**](/emedgene/emedgene-curate-manual/curate_variants/curate_variant_page/activities-panel.md).

## ACMG data synchronization between Curate and Analyze

### How Curate ACMG data appears in Analyze

ACMG tags stored in **Curate** are automatically applied in the [**ACMG SNV Classification wizard**](/emedgene/emedgene-analyze-manual/variant_page/evidence_section/acmg_snv_classification_wizard.md) on the **Variant page** in **Analyze**. This includes:

* Tag status
* Answers to tag questions
* Tag strength
* Tag notes

ACMG classifications from **Curate** are marked with a **Curate icon** (<img src="https://1131024994-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FGCW0DnLlE7QjoZPNmKIi%2Fuploads%2Fgit-blob-a3bd5cc60f23cc89f5e07631084fee49ad38ec19%2Fimage%20(162).png?alt=media" alt="" data-size="line">).

### How to update Curate ACMG data from Analyze

After reviewing ACMG data in **Analyze**, you can send updates back to **Curate** through the [**Update**](/emedgene/emedgene-analyze-manual/variant_page/curate-actions-in-analyze/update-in-curate.md) **Curate** **action**. This keeps ACMG annotations synchronized across **Curate** and **Analyze**.

## ACMG data update traceability

The [**Activities panel**](/emedgene/emedgene-curate-manual/curate_variants/curate_variant_page/activities-panel.md) on the **Curate Variant page** logs ACMG data changes made in **Curate** and through the [**Update**](/emedgene/emedgene-analyze-manual/variant_page/curate-actions-in-analyze/update-in-curate.md) **Curate** **action** in **Analyze**.

* Tag activation and inactivation, tag strength changes, and overall classification updates are logged with specific messages.
* Changes to tag notes and question answers are logged as a general update "Variant ACMG tags were updated".
* ACMG schema syncs are logged as "ACMG tag schema was updated to *new version* from *previous version*".


---

# 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-curate-manual/curate_variants/curate_variant_page/acmg-classification-card.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.
