Progeny vs Evagene: a detailed clinical pedigree software comparison

Short version. Progeny Clinical is the incumbent of the clinical pedigree software category. Progeny Genetics has been shipping it since 1996, and thirty years of iteration shows in its mature EHR integration, letter generation, patient questionnaire to auto-pedigree pipeline, Word and PowerPoint export, and deeply customisable clinical data management. Evagene is the modern alternative: a browser-first pedigree platform built around gesture drawing, BayesMendel risk models, bring-your-own-key AI interpretation, an MCP server for AI agents, a REST API with webhooks, and an embeddable viewer. If your team's priority is a pre-integrated enterprise EHR experience with thirty years of field tuning, Progeny wins on heritage. If your team's priority is AI-native workflows, programmatic access, and the ability to drop a pedigree into anything with an iframe or an API call, Evagene is built for where the category is going.

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

How the two products position themselves

Progeny Clinical positions itself, in Progeny Genetics's own words, as "the leading pedigree drawing software used by genetic counselors, clinicians and research institutions worldwide since 1996." The marketing foregrounds maturity, breadth of clinical data management, EHR integration, and coverage of the end-to-end genetic counselling workflow — from patient family history questionnaires, through pedigree drawing with standardised icon symbols and auto-updating legends, through cancer risk assessment, clinical data capture, genetic testing order integration, letter generation, and export to Word and PowerPoint for reporting. It is built for services that want one vendor-supplied platform to handle the full cradle-to-letter journey of a clinical genetics case.

Evagene positions itself as clinical-grade pedigree management for precision medicine in 2026. The emphasis is on the pedigree as the central clinical artefact and the modern surfaces that make it useful outside the application itself. That means a gesture drawing canvas for fast construction during live consultations, BayesMendel risk models (BRCAPRO, MMRpro, PancPRO) running directly on the pedigree, Mendelian inheritance analysis, AI-powered clinical interpretation using your own LLM keys, Analysis Templates for codified prompt libraries, an MCP server exposing eleven pedigree tools to Claude Desktop and Claude Code, a scoped REST API, signed webhooks, and an embeddable viewer. See our platform page for the full surface.

The headline difference is one of era. Progeny is a broad, mature clinical genetics platform that has iterated on a 1996 foundation. Evagene is a deep pedigree platform designed for an era where clinicians work alongside AI assistants, where EHRs talk to ecosystems through APIs and FHIR gateways, and where a pedigree needs to be readable by an AI agent as easily as it is by a human.

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 often keep capabilities behind sales conversations; confirm with each vendor for a procurement-grade comparison.

Pedigree drawing

Both Progeny and Evagene draw pedigrees using standardised clinical notation with auto-updating legends and standardised symbols. Progeny's drawing surface has had decades of iteration: manual drawing with one-click addition of family members, full support for multiple spouses, twins and higher-order multiples, customisable headers, footers, and grids, and the option to generate a pedigree automatically from the counts of affected and unaffected family members reported in a patient questionnaire. That last capability is a genuine strength for services where patients complete a structured family history form ahead of the consultation.

Evagene's drawing surface is built around a different assumption: that the pedigree is drawn live during the consultation while the clinician is talking to the patient. The gesture drawing canvas is designed to keep the clinician's attention on the patient rather than on the mouse, with continuous gestures, keyboard shortcuts, and automatic symbol standardisation based on recorded sex and affected status. Evagene also supports consanguinity detection with Wright's coefficient and a karyogram viewer that are not features we can find advertised on Progeny's public pages.

Neither drawing approach is universally better. If your service captures family history through a pre-visit questionnaire and generates the pedigree from that structured input, Progeny's auto-pedigree-from-questionnaire is a well-tuned fit. If the pedigree is constructed live during the appointment, or reconstructed from imported data, Evagene's live canvas plus imports are the intended match.

Risk models and clinical analysis

Progeny's marketing mentions cancer risk assessment as a standard capability of Progeny Clinical but does not publicly enumerate the specific model set on its homepage. Evagene is explicit about its coverage: BRCAPRO for breast and ovarian cancer, MMRpro for Lynch syndrome, and PancPRO for pancreatic cancer, all drawn from the BayesMendel suite and running directly on the pedigree without data re-entry. On top of this, Evagene layers Mendelian inheritance analysis for autosomal dominant, autosomal recessive, and X-linked recessive conditions, which is useful in reproductive genetics and non-cancer monogenic workflows where BayesMendel is not applicable. See our Mendelian inheritance calculator guide for the underlying approach.

Evagene also ships a batch risk screening feature that runs all catalogued diseases against a proband's pedigree in one pass and surfaces any where configurable thresholds (risk, testing eligibility, affected-relative counts) are crossed. This is unusual in the category: it inverts the usual workflow of "clinician suspects condition, runs model" into "software flags conditions the clinician should consider." Progeny's public pages do not advertise an equivalent.

If your service needs BOADICEA, Tyrer-Cuzick, or Gail specifically and wants all three running simultaneously today, neither Progeny (which does not publicly name its model set) nor Evagene (which lists BayesMendel explicitly) is the most direct fit — our FamGenix comparison covers that specific requirement.

AI and clinical interpretation

This is where the two products diverge most sharply. Progeny's publicly documented intelligence is rule-based and workflow-based: query-based individual highlighting, auto-updating legends, and letter generation templates. These are robust features that a thirty-year-old product has had time to polish. What Progeny does not publicly advertise, as of April 2026, is an AI clinical interpretation engine that generates narrative reports from the pedigree, nor a bring-your-own-key LLM integration, nor an MCP server for AI agents.

Evagene treats AI interpretation as a first-class capability. Its 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. Crucially, Evagene offers bring-your-own-key (BYOK) LLM support for Anthropic Claude and OpenAI GPT: 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.

On top of BYOK, Evagene ships Analysis Templates — custom AI prompt templates with variable injection ({{pedigree_description}}, {{proband_name}}, etc.) — so a service can codify its house style of report writing and reuse it across cases. 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 directly from inside their normal AI workspace. A service that is investing seriously in AI-assisted workflows today will notice this gap immediately.

If AI-assisted interpretation is peripheral to your workflow, Progeny's mature letter generation and rule-based workflow tooling may well cover what you need. If AI is becoming central to how your service drafts reports, reviews cases, and collaborates with automated agents, the gap between Progeny and Evagene is the single most important feature-level difference in this comparison.

Interoperability, API, and integration

Progeny's integration story is anchored on the EHR. Its public material emphasises that Progeny Clinical integrates with electronic health record systems, and thirty years of enterprise deployments have produced a genuinely mature integration capability. For a large hospital that wants a pre-packaged, vendor-managed EHR bridge with decades of field tuning, Progeny has a real advantage and we acknowledge it openly.

Evagene approaches integration through a platform layer rather than point-to-point EHR bindings. 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 moment they happen. The embeddable pedigree viewer ships as an iframe, a raw SVG, or a JavaScript snippet — so patient portals, research dashboards, or EHR integration layers can show a pedigree without a full SSO handshake. Developer documentation is public at evagene.net/help.

On data portability, the two products take different approaches. Progeny publicly advertises import from delimited text, Excel, XML, and Cyrillic FAM. Evagene supports GEDCOM 5.5.1 import and export, plus JSON, 23andMe genotype, traits and health-history imports, XEG (legacy), and pedigree image OCR. GEDCOM in particular is the de facto standard for clinical pedigree data exchange and long-term archival; the absence of a publicly advertised GEDCOM path in Progeny is worth a direct question to their team if that format matters to your service.

For a large institution procuring an end-to-end genetics platform with a pre-built EHR bridge, Progeny is the more traditional fit. For a team building its own integrations — whether through a FHIR gateway, a bespoke middleware, a patient portal, a research dashboard, or an AI agent — Evagene's API, webhook, embed, and MCP surface is more approachable.

Deployment, pricing, and governance

Progeny Clinical is primarily a cloud-hosted SaaS product, with on-premise data import available as a premium option. Pricing is not displayed on Progeny Genetics's website; access is gated by a demo and a sales conversation. Multiple independent third-party reports (including public reviews on sites such as Capterra) describe Progeny's prices as having risen over time, and some describe the price point as a barrier for smaller services — though we do not have a verified list price to quote, and services considering Progeny should request a current quote directly.

Evagene is a browser-based application currently in Alpha, accessible via a free waiting list at evagene.com. Pricing for general availability has not been published. The product encrypts LLM keys at rest with Fernet, signs webhook payloads with HMAC-SHA256, and uses scoped API keys hashed with SHA-256 — appropriate baseline controls for clinical software. Any formal certification status (HIPAA, ISO 27001, Cyber Essentials Plus, NHS DSP Toolkit, etc.) should be confirmed directly with the vendor at the point of procurement. The same applies to Progeny; its enterprise customers typically request specific compliance documentation as part of their procurement process.

When to choose Progeny

• Your service has been running Progeny for years, your workflow is built around it, and the switching cost outweighs the feature gaps.
• You need a mature, battle-tested EHR integration layer that has had decades of iteration in enterprise environments.
• Your data capture model centres on patient family history questionnaires that auto-generate a pedigree.
• Letter generation, genetic testing order integration, and Word/PowerPoint export are load-bearing parts of your clinical workflow.
• You are procuring at institutional scale and opacity in published pricing is not a blocker.

When to choose Evagene

• You want the pedigree to be the central clinical artefact and you draw live during consultations rather than auto-generating from a questionnaire.
• You use BRCAPRO, MMRpro, or PancPRO and want them named and run directly from the pedigree without data re-entry.
• 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.
• GEDCOM, 23andMe, and pedigree-image OCR interoperability matter for data movement and archival.
• You want to start free today via the Alpha waiting list rather than going through an enterprise procurement cycle first.

Migrating from Progeny to Evagene

If you decide to move from Progeny Clinical to Evagene, the practical path runs through shared data formats. Progeny exports pedigrees and family history to Word, PowerPoint, and delimited-text formats; Evagene imports GEDCOM 5.5.1, JSON, and pedigree images via OCR. Where Progeny can export a GEDCOM file or a structured JSON/XML representation of a family, Evagene can ingest it directly. Where only a rendered image of a pedigree is available, Evagene's OCR pipeline reconstructs the structure automatically and surfaces it for the clinician to verify and clean up.

Standard demographics and OMIM-coded diseases transfer cleanly. Progeny-specific proprietary fields (custom questionnaire responses, letter templates, testing-order records) will need to be re-expressed in Evagene's model — often through Analysis Templates for house-style report drafting, or through the REST API for bespoke workflows. For services running both products in parallel during transition, Evagene's webhook surface allows one-way or two-way sync against any Progeny integration points that your contract exposes.

A sensible migration pattern is: run Evagene alongside Progeny for a set of new cases, export-and-reimport a representative historical cohort via GEDCOM, verify the AI interpretation and BayesMendel outputs against your existing clinical notes, then plan a full cutover once the team is comfortable with the new surface.

Frequently asked questions

Related comparisons and reading

• Phenotips vs Evagene
• TrakGene vs Evagene
• FamGenix vs Evagene
• Pedigree drawing software: a field guide
• Clinical genetics pedigree tools
• Hereditary cancer risk assessment
• GEDCOM pedigree software