FamGenix vs Evagene: a detailed clinical pedigree software comparison

Short version. FamGenix is the strongest product on the market today if your single most important requirement is running every major published breast cancer risk model simultaneously. Its Provider Portal advertises BOADICEA v6, Tyrer-Cuzick v8, BayesMendel variants, Gail, Claus, and QRISK3 all running together on the same pedigree, plus automated identification of NCCN and ACMG referral criteria, built-in HPO/OMIM/CHV/NCI ontologies, genetic testing result tracking, regional data residency (US/CA/UK-EU/AU), and a Progeny pedigree import path. That is a deeper published risk-model set than Evagene ships today, and we are not going to pretend otherwise. Evagene matches FamGenix on BRCAPRO, MMRpro, and PancPRO specifically, and beats it on AI-native clinical interpretation, bring-your-own-key LLM integration, MCP for AI agents, Analysis Templates, a scoped REST API, signed webhooks, an embeddable pedigree viewer, GEDCOM 5.5.1 import/export, 23andMe import, and pedigree image OCR. For services whose bottleneck is risk-model breadth, FamGenix is the stronger choice today. For services modernising workflows around AI agents, programmatic access, and interoperable data, Evagene wins.

This article is an honest, fact-by-fact comparison. Where FamGenix is stronger, we say so; where Evagene is stronger, we say that too. All product claims about FamGenix are drawn from FamGenix's public website and documentation as of April 2026; if anything has since changed, FamGenix's product pages supersede this article.

How the two products position themselves

FamGenix Provider Portal positions itself as a "Pedigree Chart Maker for Clinical Genetics." The public pages foreground cancer genetics: fast pedigree drawing with full support for consanguinity, same-sex parents, donors, and surrogates, auto-pedigree from patient questionnaires, a built-in medical ontology (HPO, OMIM, CHV, NCI), genetic testing result tracking, automated NCCN and ACMG referral criteria identification, Progeny pedigree import, EHR integration, custom reporting, per-patient document storage, a patient portal, and regional data storage (US, Canada, UK/EU, Australia). The risk-model coverage is the centrepiece: BOADICEA v6, Tyrer-Cuzick v8, BayesMendel variants, Gail, Claus, and QRISK3 all running simultaneously. The product is clearly aimed at cancer genetics services that want every major published risk model available in the same session.

Evagene positions itself as clinical-grade pedigree management for precision medicine. Its emphasis is on the pedigree as the central clinical artefact, with a gesture drawing canvas for live consultation work, BayesMendel risk models (BRCAPRO, MMRpro, PancPRO), Mendelian inheritance analysis, AI-powered clinical interpretation via bring-your-own-key LLMs, an MCP server for agentic AI, a scoped REST API with signed webhooks, an embeddable pedigree viewer, and comprehensive data import including GEDCOM 5.5.1, 23andMe, JSON, XEG, and pedigree image OCR. See our platform page for the full surface.

The two products share a lot of surface area — both aim at cancer genetics services, both are cloud, both have a clinical ontology at their core. They diverge in emphasis. FamGenix optimises for risk-model depth and codified NCCN/ACMG screening. Evagene optimises for AI-assisted interpretation and programmatic access. Neither emphasis is universally correct; the right one is the one your service actually uses.

Feature-by-feature comparison

The matrix below summarises the product features each vendor publishes on their public site and documentation. A tick means the feature is publicly advertised or documented; a dash means it is not publicly listed (which does not necessarily mean it is absent — enterprise products often keep capabilities behind sales). Where nuance matters, we add a note.

Matrix compiled from publicly available product pages, documentation, and marketing material as of April 2026. "—" indicates the capability is not publicly advertised and does not necessarily mean it is absent. Enterprise products commonly keep capabilities behind sales; confirm with each vendor for a procurement-grade comparison.

Pedigree drawing

Both products draw pedigrees using standardised clinical notation and both support the modern structural requirements clinical genetics actually produces in practice — consanguinity, same-sex parents, donor and surrogate arrangements, twins, and multi-spouse configurations. FamGenix advertises "fast drawing" plus auto-pedigree generation from patient questionnaire responses; Evagene emphasises gesture drawing during live consultations, keyboard shortcuts, and automatic symbol standardisation based on recorded sex and affected status.

For services whose data capture model is a pre-visit patient questionnaire feeding a pedigree, FamGenix's questionnaire pipeline is a well-specified fit. For services whose pedigree is constructed live during the consultation or reconstructed from imported data (a referral's written pedigree, a GEDCOM from another tool, a 23andMe upload from the patient), Evagene's live canvas plus multi-format import is the intended match.

A small but useful differentiator on Evagene's side: consanguinity detection using Wright's coefficient runs automatically on the pedigree, and a karyogram viewer is included — neither is advertised on FamGenix's public pages. These matter in reproductive genetics, rare disease, and research contexts more than they do in pure cancer genetics.

Risk models: where FamGenix is stronger today

We have to be direct about this section. If your single most important requirement is the ability to run every major published breast cancer risk model on the same pedigree in the same session, FamGenix is the stronger product today and we are not going to pretend otherwise.

FamGenix advertises BOADICEA v6 (the latest release of the Cambridge BOADICEA model, with polygenic risk score and mammographic density inputs), Tyrer-Cuzick v8 (the most recent version of the IBIS model), BayesMendel variants (BRCAPRO, MMRpro, PancPRO), Gail, Claus, and QRISK3 (cardiovascular, not cancer, but widely used in UK practice). That is six model families running simultaneously, and a cancer genetics service that wants to show a patient every published risk estimate side by side can do so without leaving the product.

Evagene's coverage is narrower but named precisely: BRCAPRO, MMRpro, and PancPRO from BayesMendel, plus Mendelian inheritance analysis for autosomal dominant, autosomal recessive, and X-linked recessive conditions. On top of these, Evagene ships batch risk screening: for a given proband, the software screens across all catalogued diseases simultaneously with configurable thresholds, surfacing conditions where family history crosses a risk or testing-eligibility threshold. That is a different kind of capability — broader in disease scope but shallower in per-disease model depth.

The honest summary: FamGenix is the right product if your workflow is breast cancer risk assessment that must present BOADICEA v6 and Tyrer-Cuzick v8 as first-class outputs. Evagene is the right product if BRCAPRO-family BayesMendel plus Mendelian plus batch screening covers your workflow, and if the other capabilities (AI interpretation, BYOK LLM, API, MCP, embeds) matter more than having six named models running in parallel.

NCCN and ACMG referral criteria

FamGenix advertises automated identification of NCCN and ACMG referral criteria as a direct product feature. This is valuable in clinical settings where a service's screening workflow is explicitly codified around the NCCN cancer genetics guidelines (for example, NCCN breast and ovarian hereditary cancer criteria) — the product flags a patient who meets criteria without the clinician having to walk through the checklist manually.

Evagene does not implement an explicit NCCN/ACMG criteria library as a named feature today. Its closest equivalent is the batch risk screening engine, which runs all catalogued diseases against a proband's pedigree with configurable thresholds (risk, testing eligibility, affected-relative counts) and surfaces any condition where family history crosses a configured threshold. In practice this covers a meaningful portion of the same screening work — identifying patients who should be offered further evaluation — but it is built on risk-model outputs and configurable thresholds rather than a codified NCCN criteria set.

For services whose workflow is explicitly "does this patient meet NCCN breast/ovarian criteria," FamGenix's native implementation is the more direct fit. For services whose workflow is "find any condition where this family history crosses a risk threshold," Evagene's batch screening covers similar ground.

AI and clinical interpretation: where Evagene is stronger

This is the largest single gap in the comparison, and it runs in Evagene's favour. FamGenix's public product pages do not advertise an AI clinical interpretation engine, a bring-your-own-key LLM integration, an MCP server for AI agents, or custom AI prompt templates as of April 2026.

Evagene treats AI interpretation as a first-class capability. The AI interpretation engine generates structured clinical reports covering key findings, family implications, data gaps, and screening recommendations — designed as a drafting aid for clinicians, not a replacement for clinical judgement. Bring-your-own-key (BYOK) LLM support for Anthropic Claude and OpenAI GPT means your service uses its own LLM account and keys (encrypted at rest with Fernet), so interpretation traffic goes directly to the model provider you have already risk-assessed and contracted with. No Evagene-hosted model sits in the middle handling your clinical text.

Analysis Templates let you codify your house style of report writing. Each template is a custom AI prompt with variable injection ({{pedigree_description}}, {{proband_name}}, and others), reusable across cases, which means a service can standardise the structure of its AI-drafted reports across clinicians without losing the flexibility to tailor individual runs. The MCP (Model Context Protocol) server exposes eleven pedigree tools to Claude Desktop, Claude Code, and any MCP-compatible AI agent — so a clinician can ask their AI assistant to read, modify, or analyse a pedigree from inside their normal AI workspace without ever opening the Evagene UI.

If AI-assisted interpretation is peripheral to your workflow, this gap may not matter. If AI is becoming central to how your service drafts reports, reviews cases, and interoperates with automated agents, Evagene's AI surface is the most significant reason to prefer it over FamGenix today.

Interoperability, API, and integration

FamGenix advertises EHR integration, Progeny pedigree import, and per-patient document storage. Its regional data residency offering (US, Canada, UK/EU, Australia) is a genuinely strong feature for services operating across multiple jurisdictions, and we acknowledge that openly — Evagene does not currently publish an equivalent regional residency matrix, and services with strict data-residency requirements should weigh FamGenix accordingly.

Evagene approaches integration through a platform layer. A scoped, rate-limited REST API (keys in the format evg_<43 chars>, SHA-256 hashed at rest, with read, write, and analyse scopes) lets another system query or modify pedigrees programmatically. Webhooks deliver HMAC-SHA256-signed payloads for eight event types (pedigree and individual CRUD, analysis completed, import completed) so downstream systems can react to changes. The embeddable pedigree viewer ships as an iframe, raw SVG, or JavaScript snippet — suitable for patient portals, research dashboards, and EHR integration layers that need to show a pedigree without a full SSO handshake. The MCP server exposes eleven pedigree tools to AI agents. Documentation is public at evagene.net/help.

On data formats, Evagene supports GEDCOM 5.5.1 import and export (the de facto standard for clinical pedigree exchange), JSON, 23andMe genotype/traits/health-history, XEG (legacy), and pedigree image OCR. FamGenix publicly advertises Progeny pedigree import; other format support is not enumerated in the public product pages we checked.

For a service whose priority is jurisdictional data residency and document storage per patient, FamGenix is the more traditional fit. For a team building AI agents, patient portals, internal tooling, or EHR-side integration layers that need programmatic access, Evagene's API plus webhook plus embed plus MCP surface is broader.

Deployment, pricing, and governance

FamGenix is a cloud-hosted SaaS product with regional data residency. Its navigation lists a Free / Individual tier alongside provider-portal and enterprise options; full list pricing is not publicly displayed. Evagene is a cloud-hosted browser application currently in Alpha, free to access via the waiting list at evagene.com. Pricing for general availability has not been published.

On security baseline, Evagene encrypts LLM keys at rest with Fernet, signs webhook payloads with HMAC-SHA256, and uses scoped API keys hashed with SHA-256. Any formal certification status (HIPAA, ISO 27001, Cyber Essentials Plus, NHS DSP Toolkit, etc.) should be confirmed directly with either vendor at the point of procurement. FamGenix's regional data residency offering is a meaningful procurement differentiator where cross-jurisdiction workflows are involved; request its compliance documentation alongside Evagene's as part of a normal evaluation.

When to choose FamGenix

• Your single most important requirement is running every major published breast cancer risk model (BOADICEA v6, Tyrer-Cuzick v8, Gail, Claus, BayesMendel, QRISK3) simultaneously on the same pedigree.
• Your clinical workflow is explicitly codified around NCCN and ACMG referral criteria and you want automated identification of patients who meet them.
• You need regional data residency (US, Canada, UK/EU, Australia) as a named procurement requirement.
• You need HPO, OMIM, CHV, and NCI ontologies all built in at once.
• You want genetic testing result tracking and per-patient document storage inside the same product.
• You have an existing Progeny estate and want a vendor-supplied Progeny pedigree import path.

When to choose Evagene

• You match on BRCAPRO, MMRpro, and PancPRO and do not need BOADICEA v6 or Tyrer-Cuzick v8 as first-class outputs.
• AI-assisted clinical interpretation matters, and you want to use your own LLM keys (Anthropic, OpenAI) rather than a vendor-mediated model.
• You are building AI agents, internal tooling, patient portals, or research dashboards that need programmatic pedigree access via REST API, webhooks, MCP, or an embeddable viewer.
• You need codified, reusable AI prompt templates (Analysis Templates) for house-style report drafting.
• You need GEDCOM, 23andMe, and pedigree-image OCR for import, archival, and referral workflows.
• Mendelian inheritance analysis for non-cancer monogenic conditions matters to your workflow.
• You want to start free today via the Alpha waiting list rather than going through an enterprise procurement cycle first.

Migrating from FamGenix to Evagene

If you decide to move from FamGenix to Evagene, the practical path runs through shared data formats. Where FamGenix can export a pedigree as GEDCOM or as a structured JSON/XML representation, Evagene imports it directly. Where only a rendered pedigree image is available (a PDF report, an exported PNG), Evagene's pedigree image OCR reconstructs the structure automatically for the clinician to verify and clean up. Evagene also imports 23andMe genotype/traits/health-history files directly, which is useful for services whose patients have submitted raw DTC genetic data alongside family history.

Standard demographics and OMIM-coded diseases transfer cleanly. FamGenix-specific data — NCCN/ACMG criteria outputs, custom document store contents, genetic testing result records — will need to be re-expressed in Evagene's model: the AI interpretation engine and Analysis Templates absorb much of the narrative reporting workload, and the REST API absorbs the bespoke workflow layer. Risk-model outputs that relied on BOADICEA v6 or Tyrer-Cuzick v8 will not port directly; services that need those specific models as ongoing outputs should either keep FamGenix for that workflow or plan to re-run the cohort through an external CanRisk pipeline alongside Evagene's BayesMendel outputs.

For services running both products in parallel during transition, Evagene's webhook surface and embeddable viewer allow pedigrees to appear inside another application — including a FamGenix portal or a hospital EHR — without a full data migration up front. A sensible migration pattern is: run Evagene alongside FamGenix for new cases, export-and-reimport a representative historical cohort via whatever export FamGenix supports, verify BRCAPRO/MMRpro/PancPRO outputs against FamGenix's equivalents, then plan a cutover if the risk-model coverage is sufficient for your workflow.

Frequently asked questions

Related comparisons and reading

• Phenotips vs Evagene
• Progeny vs Evagene
• TrakGene vs Evagene
• Hereditary cancer risk assessment
• Mendelian inheritance calculator
• Clinical genetics pedigree tools
• Pedigree drawing software: a field guide