Evidence question 03

A prediction score is one line of evidence, not the classification

Computational models can help prioritize and compare variants. They do not replace functional, case, segregation, population, or expert evidence.

For education and workflow evaluation only. This guide is not a diagnostic interpretation framework.

What a prediction contributes

Computational tools can estimate whether a change may affect a gene product. Their value depends on calibration, the variant type, the gene, and the threshold used for that evidence framework.

The ClinGen FH expert panel published specific use and thresholds for in silico prediction in LDLR interpretation. That is a reminder that the model name alone is not enough. Reviewers need to know how the output is being used.

Four questions for a computational result

01

What was predicted?

Separate a protein-impact prediction from a clinical classification. They answer different questions.

02

Was the tool calibrated?

Record the model, version, applicable variant class, and threshold used in the chosen framework.

03

Is the evidence independent?

Avoid counting several correlated models as if they were unrelated evidence sources.

04

What evidence can overrule it?

Functional results, population data, segregation, and case evidence may support or challenge the prediction.

Product boundary

CardioGen AI uses an AlphaMissense pathogenicity value as one input in its current four-gene model. The resulting score is internal, non-clinical model evidence and requires qualified review alongside independent evidence.

Make uncertainty inspectable

A review-ready result should show which computational signal was used, what it contributed, and why it did not settle the classification alone. That makes disagreement easier to review and later evidence easier to add.

Primary references

Evaluate the workflow

Bring one de-identified review path.

See where CardioGen AI fits, where it does not, and what your team would need to validate.
Request a focused demo