Rare disease pedigree software: pedigrees in the diagnostic odyssey

Short version. In rare disease diagnosis, the pedigree is a tool for pattern-recognition that complements molecular analysis rather than replacing it. Consanguinity, affected-sibling patterns, and phenotype clustering across relatives narrow the candidate-gene space before sequencing; segregation analysis refines it after sequencing. Modern rare disease software supports either a phenotype-first workflow (HPO at the centre, with tools such as Phenotips) or a pedigree-first workflow (disease and family structure at the centre, with tools such as Evagene). This guide explains why the pedigree matters in rare disease, how HPO and OMIM complement each other, and where Evagene fits for teams whose workflow is pedigree-first or who want integrated AI-assisted interpretation.

The diagnostic odyssey and the role of the pedigree

"Diagnostic odyssey" is the term used across rare disease medicine for the long journey many patients and families undergo before reaching a diagnosis. It is not a single consultation, a single test, or a single specialty; it is often years of intermittent contact with a shifting set of services, tests that narrow candidates without confirming, and a slow accretion of phenotype detail. For the families living through it, the cost in time, uncertainty, and appropriate management is substantial.

Within that odyssey, the pedigree is one of the few tools that remains useful throughout. Early on, it helps triage: is this a one-off phenotype in an otherwise unremarkable family, or part of a pattern that suggests Mendelian inheritance? Mid-odyssey, it anchors molecular analysis: segregation of a candidate variant with disease across relatives strengthens or weakens the case for pathogenicity. Late in the odyssey, even when a molecular diagnosis is reached, the pedigree supports cascade testing and clinical management of relatives who may be affected, carriers, or at risk.

A precise, detailed, three- to four-generation pedigree also protects against cognitive shortcuts. Rare diseases are, individually, uncommon; clinicians rarely see two families with the same condition. The pedigree forces a clinician to confront the data rather than fit the family into an assumed pattern. Consanguinity detection, for example, is easy to miss in a quick history; a well-drawn pedigree surfaces it immediately and changes the differential toward autosomal recessive disease.

What a rare disease pedigree should capture

Beyond the usual elements of any clinical pedigree, rare disease practice benefits from several specific capture points.

• Consanguinity. First-cousin, second-cousin, or closer relationships between the proband's parents, grandparents, or earlier ancestors. Evagene detects consanguinity automatically using Wright's coefficient of inbreeding, which matters because the coefficient drives the prior probability of homozygosity at any given locus.
• Founder-population ancestry. Ethnic groups with founder mutations (Ashkenazi Jewish, French Canadian, Finnish, Old Order Amish, Afrikaner, and others) shift the pre-test probability for specific conditions. Record all four grandparents' ethnic origins.
• Affected-sibling patterns. Two affected siblings in a family with unaffected parents is a strong pointer to autosomal recessive inheritance. One affected parent and one or more affected children raises the probability of autosomal dominant inheritance, with reduced penetrance as a possibility.
• Ages of onset. Age at first feature, age at diagnosis, and progression notes. Many rare diseases have characteristic age-of-onset distributions.
• Early deaths. Stillbirths, neonatal deaths, infant deaths, childhood deaths. These sometimes represent unrecognised relatives with the same condition.
• Phenotype across relatives. Even subtle features in relatives — short stature, hearing loss, learning difficulty, unusual facial features — can cluster into a recognisable pattern that any one feature on its own does not.
• Reproductive history. Miscarriages, terminations for fetal abnormality, fertility difficulties.

All of this is structured data. A pedigree drawn on paper captures some of it; a clinical pedigree platform captures it in a form that drives downstream analysis and reporting.

HPO: the phenotype vocabulary of rare disease

The Human Phenotype Ontology (HPO) is the standard vocabulary for describing a rare disease phenotype in a machine-readable form. Maintained by the Monarch Initiative, it contains over 15,000 terms organised in a hierarchy that ranges from broad ("Abnormality of the nervous system") to specific ("Cerebellar atrophy," "Pontine hypoplasia"). Each term has a stable identifier (HP:0000001 for the root, for example) and defined parents in the hierarchy, so tools can reason about specificity.

The practical value of HPO is that it lets software match a patient's features against known phenotype-gene and phenotype-disease associations. A patient with ten HPO terms attached to their record can be queried against OMIM and Orphanet to suggest which Mendelian diseases best fit the combination. Tools such as Phenotips are built around this workflow: capture HPO terms during the consultation, generate a ranked candidate list for the clinical geneticist to review, and iterate as new phenotype detail emerges.

HPO and OMIM complement each other. OMIM is the catalogue of diseases with gene associations; HPO is the vocabulary that describes what patients look like clinically. HPO maintains explicit mappings from phenotype terms to OMIM entries so that phenotype-first tools can present candidate diagnoses. A good rare disease workflow uses both vocabularies — HPO to describe the patient, OMIM to enumerate candidate conditions — and structures the pedigree around both.

Phenotype-first vs pedigree-first workflows

In practice, rare disease services cluster around one of two centres of gravity.

Phenotype-first workflows start with the patient's features. The clinician elicits, codes, and refines HPO terms; the software suggests candidate genes or diseases; the family history and molecular results are layered on top. This is the workflow championed by tools such as Phenotips and is particularly strong in undiagnosed-disease programmes, paediatric rare disease services, and research settings where phenotyping depth is the rate-limiting step.

Pedigree-first workflows start with the family structure. The clinician builds a precise three- to four-generation pedigree with diagnoses, ages of onset, consanguinity, and ethnicity; the software flags inheritance patterns and computes risk; the phenotype is recorded as part of the proband's entry. This is the workflow of most cancer genetics services, cardiogenetics services, and reproductive genetics services, and it is the centre of gravity for Evagene.

Neither workflow is universally better. An undiagnosed-disease unit probably benefits more from HPO-first depth; a cancer genetics service probably benefits more from pedigree-first integration. Many rare disease services need both, and use one tool for each while keeping structural pedigree data in sync through GEDCOM or JSON.

Where Evagene fits in rare disease

Evagene is a pedigree-first platform. Its data model centres on the family structure, the disease catalogue (200+ conditions keyed to ICD-10 and OMIM), ethnicity, consanguinity, and the risk and inheritance analyses that run from those inputs. It does not currently offer native HPO phenotype capture at the depth of a dedicated phenotype-first tool; services whose rare disease workflow is HPO-centric will typically use a tool such as Phenotips for that layer.

Where Evagene adds value in rare disease is in three places.

Disease catalogue and Mendelian analysis. The curated catalogue of 200+ diseases with ICD-10 and OMIM codes maps directly to OMIM entries, so rare Mendelian conditions can be annotated in a structured form. The Mendelian inheritance calculator computes carrier and affection probabilities for autosomal dominant, autosomal recessive, and X-linked recessive conditions across the pedigree, which is the bread and butter of rare disease counselling.

AI-assisted clinical interpretation. Evagene's AI interpretation engine, driven by bring-your-own-key LLMs (Anthropic Claude, OpenAI GPT), generates structured interpretations that highlight features of the pedigree a clinician might want to consider — consanguinity, affected-sibling patterns, early deaths, features clustering across relatives. This is not a replacement for clinical judgement, and not a phenotype-to-gene engine in the HPO sense, but it is a drafting aid that helps a clinician work through a complex pedigree faster.

Modern platform surfaces. A REST API, webhooks, an MCP server with pedigree tools for Claude Desktop and Claude Code, and an embeddable viewer let a rare disease service build the pedigree into downstream workflows: research dashboards, multidisciplinary team tooling, patient portals. For a service building its own AI agents or tooling, Evagene's platform layer is unusually accessible.

Comparing rare disease tools: a short orientation

The rare disease pedigree software space clusters into three broad categories.

• HPO-first platforms. Phenotips is the leading example. Deep HPO phenotype capture, phenotype-to-gene suggestion, enterprise EHR integration. Best fit: undiagnosed-disease programmes and phenotype-driven rare disease diagnostics.
• Pedigree-first clinical platforms. Evagene, Progeny, TrakGene, and others. Family structure, disease catalogue, integrated risk models, reporting. Best fit: services where pedigree construction and disease-by-disease analysis dominate the workflow.
• Research and exploratory tools. Exomiser, AMELIE, and similar variant-prioritisation pipelines. Not pedigree software in the clinical sense, but commonly used in combination with pedigree data in rare disease research.

In practice, many rare disease services combine tools rather than using one exclusively. See our Phenotips vs Evagene comparison for a detailed side-by-side on one common pairing.

How Evagene supports rare disease workflows

For pedigree-first rare disease services, Evagene offers gesture drawing for fast pedigree construction during consultations, automatic consanguinity detection using Wright's coefficient of inbreeding, a curated 200+ disease catalogue keyed to ICD-10 and OMIM, and AI-assisted clinical interpretation using your own LLM keys. The Mendelian inheritance calculator supports autosomal dominant, autosomal recessive, and X-linked recessive conditions and surfaces affected-sibling and carrier patterns automatically. Batch risk screening can sweep the pedigree against the full disease catalogue with configurable thresholds, which is useful when the family presentation suggests a pattern but the clinician has not yet narrowed the differential.

Evagene also imports GEDCOM files from genealogy platforms, 23andMe raw data for SNP-based trait inference, and legacy pedigree images via OCR, so a rare disease service can bring in data from previous clinicians or from families' own records. Exports (PDF, PNG, SVG, GEDCOM) and four report types support onward communication with colleagues, laboratories, and families.

For services whose rare disease practice is primarily HPO-driven, a phenotype-first platform such as Phenotips will be a better day-to-day fit; Evagene can complement such a platform through shared structural data. For services whose practice is primarily pedigree-first, whose disease catalogue spans a broad set of conditions (not only those with deep HPO descriptions), or who want AI-assisted interpretation with bring-your-own-key LLMs, Evagene is built to be the primary tool.

Frequently asked questions

Related reading

• Phenotips vs Evagene: clinical pedigree software comparison
• Clinical genetics pedigree tool: from consultation to report
• Mendelian inheritance calculator
• Batch pedigree risk screening
• Hereditary cardiac pedigree
• Karyogram viewer online
• Pedigree OCR