Phenotips vs Evagene: a detailed clinical pedigree software comparison

Short version. Phenotips is an enterprise-grade genomic health record platform with deep Human Phenotype Ontology (HPO) integration and is particularly strong in undiagnosed rare disease and phenotype-driven candidate-gene workflows. Evagene is a browser-first pedigree management system with integrated BayesMendel cancer risk models, AI-powered clinical interpretation via bring-your-own-key (BYOK) large language models, an MCP server for agentic AI integration, and an embeddable pedigree viewer. Both tools are serious clinical products; which one fits depends on whether your service is phenotype-first or pedigree-first, whether you need enterprise EHR integration today, and whether AI-assisted interpretation and programmatic access matter to your workflow.

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

How the two products position themselves

Phenotips positions itself as "the complete Genomic Health Record" — an EHR-integrated solution for collaborative genomic medicine. Its marketing emphasises diagnostic yield for rare disease ("up to 30× faster"), a large installed base (100,000+ patient records across 60+ countries per its homepage), and HPO-driven phenotype capture paired with automated gene and disease suggestions. The product is oriented towards genetics institutions, rare disease clinics, cancer genetics services, and research groups that want a single platform managing the entire genomic clinical record.

Evagene positions itself as clinical-grade pedigree management for precision medicine. Its emphasis is on the pedigree as the central clinical artefact: a gesture-drawing canvas for fast construction during live consultations, integrated BayesMendel risk models (BRCAPRO, MMRpro, PancPRO) that run directly on the pedigree data, Mendelian inheritance analysis, AI-powered clinical interpretation using your own LLM keys, and a platform layer (REST API, webhooks, MCP server, embeddable viewer, analysis templates) that lets the pedigree flow into whatever downstream system or agent you use.

The headline difference is one of shape. Phenotips is a broad genomic health record platform in which the pedigree is one component. Evagene is a deep pedigree platform with the modern surfaces (AI, API, MCP, embeds) that make pedigree data useful outside the application itself.

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.

Pedigree drawing

Both products draw pedigrees using standardised clinical notation. Both support gender-inclusive symbols — a capability Phenotips calls out explicitly, and one Evagene also supports. The practical difference is in the drawing interaction itself. Phenotips uses a conventional click-and-drag canvas, supplemented by automated pedigree generation from patient-completed questionnaires. Evagene adds a gesture drawing mode designed to let clinicians construct a pedigree while talking to a patient, without breaking the flow of the conversation — keyboard shortcuts, continuous gestures, and automatic standardisation of symbols based on recorded sex and affected status.

For teams whose pedigree construction happens mostly pre-consultation (via questionnaire) or post-consultation (data entry from notes), Phenotips's questionnaire-driven approach may reduce clinician time. For teams whose pedigree is built live during consultation, Evagene's gesture drawing is the intended fit. Neither approach is universally better; the question is which matches your clinical workflow.

Risk models

Phenotips advertises simultaneous execution of multiple cancer risk models but does not publicly name the full set on its homepage. Evagene lists its BayesMendel coverage explicitly: BRCAPRO for breast and ovarian cancer, MMRpro for Lynch syndrome, and PancPRO for pancreatic cancer. Evagene additionally offers Mendelian inheritance calculators for autosomal dominant, autosomal recessive, and X-linked recessive conditions — useful in reproductive genetics and non-cancer monogenic settings where BayesMendel does not apply. See our Mendelian inheritance calculator guide for the underlying approach.

A distinctive Evagene feature here is 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. 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." Phenotips does something conceptually similar in its phenotype-to-gene suggestion pipeline, but it operates from phenotype features rather than running Bayesian risk models across a disease catalogue.

AI and clinical interpretation

This is the area where the two products differ most. Phenotips's public documentation does not advertise an AI clinical interpretation engine that generates narrative reports from the pedigree. Its intelligence sits in its gene-and-disease suggestion layer driven by HPO phenotypes.

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.

Beyond interpretation, Evagene ships Analysis Templates — custom AI prompt templates with variable injection ({{pedigree_description}}, {{proband_name}}, etc.) that lets a service codify its house style of report writing and reuse it across cases. And the MCP (Model Context Protocol) server exposes 11 pedigree tools to Claude Desktop, Claude Code, and any other 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. None of this is advertised by Phenotips today.

If AI-assisted interpretation is peripheral to your workflow, this difference may not matter. If AI is becoming central to how your service drafts reports and reviews cases, the gap between the two products is large.

Interoperability and integration

Phenotips's headline integration story is the EHR. Its homepage describes the product as "EHR-integrated," and its enterprise sales motion is partly about fitting into large institutional IT estates alongside Epic, Cerner, and similar systems. Specific EHR compatibility is not exhaustively listed on the public site.

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/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, a raw SVG, or a JavaScript snippet — suitable for patient portals, research dashboards, and EHR integration layers that need to show a pedigree without a full SSO handshake.

For a large hospital that wants a pre-integrated pedigree component inside Epic with a vendor-managed integration, Phenotips is the more traditional fit. For a team building its own integration, or one whose EHR work happens through a FHIR gateway, or one building an AI agent that needs pedigree tools, Evagene's API surface is more approachable.

On data portability, Evagene supports GEDCOM 5.5.1 import and export, plus JSON, 23andMe genotype / traits / health-history imports, XEG (legacy format), and pedigree image OCR. See our guide to GEDCOM pedigree software for why this matters for clinical archival and multi-institution collaboration.

Deployment, pricing, and governance

Phenotips is a cloud-hosted SaaS product (cloud.phenotips.com). On-premise deployment is not emphasised on its public pages. Pricing is not published; access is gated by a demo and institutional contract. The product's established base (100,000+ patient records, 500+ specialists, 60+ countries per its homepage) and acquisition by Think Research make it a relatively safe procurement choice for large institutions, but the opaque pricing can be a friction point for smaller services.

Evagene is a browser-based application currently in Alpha, accessible via a free waiting list. 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, though 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 Phenotips; its enterprise customers generally request specific compliance documentation as part of procurement.

When to choose Phenotips

• Your service is phenotype-driven rare disease diagnostics and HPO capture is central to your workflow.
• You need a single platform managing the complete genomic health record, not just the pedigree.
• Your institution requires a deeply integrated EHR experience with a vendor-managed integration layer.
• You need pre-built patient questionnaires that feed automatically into a pedigree.
• You are procuring at institutional scale and opacity in published pricing is not a blocker.

When to choose Evagene

• The pedigree is the central clinical artefact in your workflow and you need fast, live construction during consultations.
• You use BRCAPRO, MMRpro, or PancPRO and want those models 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, or patient portals that need programmatic pedigree access via REST API, webhooks, MCP, or an embeddable viewer.
• You want GEDCOM and 23andMe interoperability to move data in and out freely.
• You want to start free today via the Alpha waiting list rather than going through an enterprise procurement cycle first.

Migrating from Phenotips to Evagene

If you decide to move from Phenotips to Evagene, the practical path is through shared data formats. Phenotips exports pedigrees as standard formats; Evagene imports GEDCOM 5.5.1 (the de facto standard for pedigree data exchange), JSON, and pedigree images via OCR when no structured export is available. Disease annotations that map to OMIM transfer cleanly; HPO-first phenotype records will need to be restructured around Evagene's ICD-10 / OMIM disease model, which may be a workflow change if your documentation is HPO-native.

For services running both products in parallel during transition, Evagene's REST API and webhook surface allow a one-way or two-way sync to be built against Phenotips's own integration surface, depending on what Phenotips exposes to your contract.

Frequently asked questions

Related comparisons and reading

• Progeny vs Evagene
• TrakGene vs Evagene
• FamGenix vs Evagene
• Alternatives to Phenotips
• Clinical genetics pedigree tools: a field guide
• Hereditary cancer risk assessment