A walkthrough of the Genome page

When you upload your DNA, Haeckel runs seventeen separate analyses against the resulting variant set. The Genome page lays them out under a single tab bar so you can move from ancestry to clinical variants to pharmacogenomics without losing context. Here is what sits where.

Overview

The first tab is a one-screen summary: ancestry composition, top three population matches, your Y and mtDNA haplogroups, your archaic ancestry percentages, and a small dossier card for each clinical or pharmacological variant of interest. Most users start here and only dive into specific tabs when something catches their attention.

Health

A panel of 89 clinically significant genes screened against ClinVar. Findings are grouped by clinical significance: pathogenic, likely pathogenic, variant of uncertain significance, carrier (heterozygous for a recessive condition), and benign. Each finding includes the source publication count, the penetrance estimates by age, and an actionability tag.

Pharmacogenomics

Star-allele calling for twelve pharmacogenes plus an FDA Black Box flag for ten high-risk drug-gene pairs. Bring this page to any prescriber before they write a new prescription, especially for opioids, anticoagulants, antidepressants, or chemotherapy.

Polygenic scores

The PRS tab carries our six independent polygenic scoring methods (Basic, Clumping and Thresholding, PRS-CS, LDpred2, Lassosum, and SBayesR) across thirteen traits. The headline number is the ensemble z-score, but you can drill into the per-method results to see how much agreement there is.

Phenotype, nutrigenomics, archaic, and more

The remaining tabs cover HIrisPlex-S phenotype prediction, the 46-SNP nutrigenomics panel (lactose, caffeine, alcohol, folate, vitamins, gluten, omega-3 conversion), Neanderthal and Denisovan introgression, runs of homozygosity for consanguinity detection, kinship inference, HLA typing for transplant compatibility, structural variants, and a 22.5 million-SNP raw browser for anyone who wants to look up a specific rsID.

How the page handles loading and partial failures

Each tab fetches its data independently with its own client-side cache, keyed by the analyser name plus your kit ID. The page renders skeleton placeholders while data is in flight, then fills in section by section as each fetch resolves. If one analyser failed during the pipeline run, that tab shows an inline notice ("Phenotype prediction unavailable for this kit; coverage was below the 67% threshold") rather than blocking the rest of the page.

When a new pipeline version becomes available that would meaningfully refresh your results, an "update available" badge appears on the Genome page header. Tapping it triggers a re-process from the encrypted file in storage, which finishes in 2 to 10 minutes for chip data and 8 to 25 minutes for whole genomes. The current results remain visible during the re-process and are atomically replaced when the new run completes.

Mobile vs desktop

The Genome page is desktop-first today. The 15-tab structure collapses on narrow screens to a horizontal-scroll tab bar, but several visualisations (the karyotype ideogram, the chromosome inheritance bars, the longitudinal risk chart) are designed for at least 768px of horizontal space and may feel cramped on a phone. A dedicated mobile sweep of the Genome surface is on the roadmap.

Empty states

• No genome uploaded yet: each tab shows a single "Upload your DNA to populate this section" CTA that deep-links to the upload flow.
• Genome uploaded but pipeline still running: each tab shows a small skeleton plus a progress indicator pointing to the Data page where you can watch the live pipeline status.
• Genome uploaded but the QC analyser flagged it: a banner across the top of every tab explains which QC metric flagged and what (if anything) you can do about it.
• Specific analyser failed: that single tab carries an inline notice with the analyser name, the failure reason if known, and a link to re-trigger the analyser specifically.