genoDraw vs Evagene: an honest pedigree software comparison

Short version. genoDraw is a free academic web tool for constructing pedigree diagrams using standardised human pedigree nomenclature, with a notable emphasis on integration with biomedical vocabularies. It was described in a PubMed-indexed 2020 publication and takes a graph-based editing approach. Its strength is representational rigor — clean, standardised pedigrees that integrate cleanly with ontology-based annotation, which matters in research publishing. Evagene is a clinical-grade pedigree management platform with gesture drawing, a 200+ disease catalogue coded to ICD-10 and OMIM, integrated BayesMendel cancer risk models, Mendelian inheritance analysis, AI clinical interpretation via bring-your-own-key (BYOK) LLMs, a REST API, webhooks, and an MCP server for AI agents. For research figures with rigorous nomenclature, genoDraw is strong. For end-to-end clinical workflow, Evagene is the fit.

This is an honest comparison. All genoDraw claims are drawn from the 2020 publication and the product's public materials as of April 2026.

How the two products position themselves

genoDraw is positioned as a rigorous, academic web tool for constructing pedigree diagrams that use standardised human pedigree nomenclature, integrated with biomedical vocabularies. The product uses graph-based editing — a representation closer to the underlying data model than to a freehand canvas — and its scholarly provenance means the nomenclature choices are defensible against reviewer critique. It is free. Its natural audience is research geneticists who need pedigrees in papers and supplementary materials, clinical researchers producing figures for trials and publications, and anyone who prefers a tool whose methodology has a visible citation.

Evagene is positioned as clinical-grade pedigree management for precision medicine. Its audience is clinicians, genetic counsellors, clinical researchers, and teams building AI-augmented clinical workflows. Its pedigree canvas uses gesture drawing for speed during consultations; its disease annotation is coded to ICD-10 and OMIM across a 200+ disease catalogue; its risk modelling runs BRCAPRO, MMRpro, and PancPRO directly on the pedigree; its AI layer uses the service's own LLM keys (Anthropic Claude, OpenAI GPT), encrypted at rest with Fernet, to draft structured clinical reports. The platform surface — REST API, webhooks, MCP server (11 tools), embeddable pedigree viewer, Analysis Templates — is a first-class part of the product.

The dividing line is purpose. genoDraw answers "how do I make a nomenclature-correct, vocabulary-integrated pedigree for a paper or research record?" Evagene answers "how do I run a clinical service end-to-end, from drawing through risk modelling to AI-assisted reporting and integration with other systems?" Both answers are legitimate; they are simply answers to different questions.

Feature-by-feature comparison

The matrix below compares publicly advertised features. A tick means the feature is publicly advertised; a dash means it is not publicly listed.

Matrix compiled from publicly available product pages, the 2020 PMC publication describing genoDraw, and product material as of April 2026. "—" indicates the capability is not publicly advertised and does not necessarily mean it is absent.

Pedigree construction: graph-based vs gesture canvas

genoDraw uses graph-based editing. The pedigree is modelled explicitly as a graph of nodes and relationships, and the editing interface exposes that structure. For users comfortable with the graph metaphor — and for researchers whose mental model of a family tree is already a graph — this is clean and precise. It also makes correct standardised nomenclature easier to enforce, because the structure is explicit.

Evagene uses a canvas with gesture drawing. The clinician draws the pedigree as they would on paper, but the software standardises symbols automatically based on recorded sex and affected status, applies consistent spacing, and offers keyboard shortcuts for common operations. The intended use case is live construction during consultation — the clinician talks to the patient and the pedigree grows on screen without breaking the conversation.

Neither is universally better. A graph-based editor is a good fit for a researcher constructing a pedigree from structured data that already exists. A gesture-drawing canvas is a good fit for a clinician whose pedigree comes out of a conversation with a patient.

Nomenclature and vocabulary integration

genoDraw's emphasis on standardised human pedigree nomenclature and biomedical vocabulary integration is a genuine strength. Research papers benefit from pedigree figures whose symbols and annotations sit cleanly inside a recognised ontology stack, because reviewers and readers can map the figure to a shared vocabulary without additional interpretation. For a paper submitting to a journal that expects HPO or other vocabulary-aware annotation, genoDraw's methodology is a good foundation.

Evagene uses NSGC/ISCN symbol conventions and codes diseases to ICD-10 and OMIM across its curated 200+ catalogue. That coverage is sufficient for clinical workflow and for publication figures in clinical genetics journals. Evagene does not currently lean into HPO deep phenotyping to the extent genoDraw advertises biomedical vocabulary integration; services whose publication or annotation workflow demands HPO-centric phenotype terms may prefer genoDraw for figure preparation.

Clinical workflow and risk analytics

genoDraw does not advertise integrated clinical risk modelling, clinical report generation, or case management. Its purpose is faithful pedigree representation; risk modelling and workflow are out of its declared scope. A research team or clinic that uses genoDraw will typically complement it with separate tools for risk calculation and reporting.

Evagene integrates the full clinical loop. BRCAPRO, MMRpro, and PancPRO run on the pedigree without re-entry. Mendelian inheritance calculators cover AD, AR, and XR patterns. Batch risk screening sweeps across the entire 200+ disease catalogue for a given proband, surfacing conditions whose family history crosses a risk or testing-eligibility threshold — useful when a clinician cannot recall every monogenic possibility in scope for a particular family. Karyogram viewing, consanguinity detection via Wright's coefficient, and 4 clinical report types round out the clinical surface.

If your work stops at the pedigree, genoDraw is enough. If your work continues into risk interpretation and reporting, Evagene does the continuation without a toolchain handoff.

AI, API, and platform capabilities

genoDraw is not an AI-augmented tool, and it does not advertise an API for third-party integration. It is a focused web editor.

Evagene includes AI clinical interpretation using bring-your-own-key Anthropic Claude and OpenAI GPT (encrypted at rest with Fernet), Analysis Templates for custom prompt-based reports, an MCP server exposing 11 pedigree tools to Claude Desktop / Claude Code / other MCP agents, a scoped REST API with rate-limited, SHA-256-hashed keys, HMAC-SHA256-signed webhooks, and an embeddable pedigree viewer (iframe / SVG / JS). These capabilities are what distinguish Evagene as a platform; they are also precisely the capabilities that a focused research tool like genoDraw is not trying to provide.

Governance, security, and clinical fit

genoDraw is a research tool. Clinical services that need documented security controls, audit logging, role-based access, and vendor-backed data governance should not assume those are present in an academic product unless the documentation says so.

Evagene applies baseline clinical controls: API keys scoped and rate-limited, hashed with SHA-256 at rest; webhook payloads signed with HMAC-SHA256; LLM keys encrypted at rest with Fernet. Formal certification status (HIPAA, ISO 27001, Cyber Essentials Plus, NHS DSP Toolkit) should be confirmed directly with the vendor during procurement. The platform is in Alpha, which is the honest status; clinics considering Evagene at institutional scale should factor in Alpha-stage expectations.

When to choose genoDraw

• You need pedigree diagrams for a research paper or supplementary material, and standardised nomenclature with biomedical vocabulary integration is a priority.
• Your workflow treats the pedigree as a figure, not as the substrate for clinical risk analysis.
• You prefer graph-based editing and explicit data-model exposure over a gesture-drawing canvas.
• You want a free academic tool with a visible publication record and no commercial obligation.
• You are comfortable complementing genoDraw with separate tools for risk calculation, reporting, and clinical workflow.

When to choose Evagene

• You are running a clinical service where the pedigree becomes part of the medical record.
• You want integrated cancer risk modelling (BRCAPRO, MMRpro, PancPRO) and Mendelian inheritance analysis without exporting to another tool.
• You want AI-assisted clinical interpretation using your own LLM keys (Anthropic, OpenAI), not a vendor-chosen model.
• You are building AI agents, internal tooling, or patient portals that need programmatic pedigree access via REST API, webhooks, MCP, or embeds.
• You want broad import coverage (GEDCOM 5.5.1, JSON, 23andMe, XEG, pedigree image OCR) and 4 structured clinical report types.
• You value gesture drawing optimised for live clinical construction during consultations.

Migrating from genoDraw to Evagene

The route depends on what genoDraw exports. If GEDCOM 5.5.1 is supported, that is the cleanest path into Evagene. SVG export can be used to bring the pedigree in as an image via Evagene's OCR import, though this is lossier than a structured export. Disease annotations expressed in biomedical vocabularies that overlap with OMIM and ICD-10 will map cleanly; HPO-centric annotations will need to be re-mapped against Evagene's 200+ catalogue.

For research teams using genoDraw for publication figures and Evagene for clinical workflow, the pragmatic pattern is to run them side by side: clinical management in Evagene, publication figures in genoDraw when its vocabulary integration is needed. Evagene's SVG export is publication-suitable in most cases, but if your paper specifically wants genoDraw's nomenclature rigour, using both is fine.

Frequently asked questions

Related comparisons and reading

• Phenotips vs Evagene
• PERSEUS vs Evagene
• ConceptViz vs Evagene
• Pedigree drawing software: a practical guide
• All Evagene comparisons
• Clinical genetics pedigree tools: a field guide