Accept the data clinicians actually receive.
Support for VCF and BAM/CRAM workflows, with paired-end Illumina FASTQ support for the validated GRCh38 path.
See workflow →LYNNAGEN brings variant interpretation, phenotype context, technical quality, and evidence provenance into one clinician-led review workspace.
LYNNAGEN organizes genomic analysis into a durable review workflow instead of collapsing every signal into a single opaque answer.
Support for VCF and BAM/CRAM workflows, with paired-end Illumina FASTQ support for the validated GRCh38 path.
See workflow →Pathogenic, likely pathogenic, VUS, likely benign, and benign remain the primary classification dimension.
See review model →Variant identity, disease context, phenotype relevance, technical QC, and source evidence remain inspectable.
Explore evidence →The product is organized around four explicit stages so the reviewer can see what happened to the case and where each evidence layer belongs.
Bring the case and patient context into a controlled workspace.
Normalize and validate the data before evidence matching.
Aggregate installed evidence without erasing source distinctions.
Put the evidence dossier in front of the qualified reviewer.
A pathogenic variant is not automatically a patient diagnosis. LYNNAGEN keeps intrinsic variant assessment, patient-specific relevance, and technical validity visible as different review dimensions.
Five-tier classification remains the primary headline rather than being replaced by phenotype or QC signals.
Phenotype and disease-context evidence help prioritize relevance to the patient without silently changing intrinsic pathogenicity.
Sequence and call-quality information remains an independent review lane.
Illustrative review model — not a patient result.
LYNNAGEN can surface classification, gene–disease, phenotype, population, transcript, annotation, and functional evidence while preserving source identity and review context.
Variant-level assertions are presented with their source context rather than silently becoming a new machine assertion.
Gene–disease validity, inheritance, and disease relationships remain available alongside variant evidence.
Phenotype context helps prioritize diseases and patient relevance as a separate dimension.
Population queries and local annotation resources support evidence review while retaining assembly and transcript context.
The public website and the clinical application should remain separate systems. Patient and genomic data should not pass through the marketing site.
Large evidence, reference, runtime, and case assets can remain inside the controlled deployment environment.
Unsafe identity or reference mismatches should remain visible rather than being forced into a clinical classification.
Case continuity and audit records persist across application and WSL restarts.
Final clinical interpretation remains with the qualified clinician or laboratory reviewer.
For clinical genetics, molecular diagnostics, pathology, and diagnostic laboratory teams evaluating structured genomic interpretation workflows.