Genetic History

Genetic History — ancestry narratives for clinical labs

Ancestry narrative for your patients — without your data leaving your laboratory.

Request a technical demo

30-minute walkthrough. No commitment.

See sample report

Illustrative composite R-DF81 + H3c2a (~1100 words).

Genetic History push-model architecture: 5-step data flow with patient data staying at the partner lab. Push-model architecture data flow. The partner NGS lab runs sequencing locally and outputs VCF or BAM files at the partner site. The Genetic History module ingests these files locally at the partner lab and generates an ancestry narrative in prose. The partner delivers the narrative to the patient. The partner module pulls library updates from versioned HTTPS endpoints published by Genetic History, at a cadence the partner controls (weekly, monthly, or quarterly). Key differentiator: patient data never transfers to Genetic History infrastructure. Genetic History Module 1 Partner runs NGS sequencing 2 Outputs VCF/BAM at partner 3 Module ingests files locally 4 Module generates ancestry narrative 5 Partner delivers narrative to patient Library updates: lab pulls at controlled cadence from Genetic History. Patient data never transfers to Genetic History.
  1. Partner runs NGS sequencing
  2. Outputs VCF/BAM at partner
  3. Module ingests files locally
  4. Module generates ancestry narrative
  5. Partner delivers narrative to patient

Library updates: lab pulls at controlled cadence from Genetic History.

Patient data never transfers to Genetic History.

  • Push model — patient data never leaves your laboratory
  • EU hosting — Scaleway France (DC2 Vitry-sur-Seine, Val-de-Marne); library distribution only
  • YFull substrate ~12 years — Y-DNA + mtDNA tree
  • Non-clinical — exempt Ley 14/2007 + IVDR
  • VCF + BAM — industry-standard formats

Ancestry narratives for your patients — without their data leaving your lab

Genetic History distributes a push-model software module that installs in your clinical laboratory’s own infrastructure. The module processes NGS output and returns Y-DNA and mtDNA ancestry narratives in English and Spanish. Patient data never transfers to Genetic History.

What makes this integration different

  • Architectural data sovereignty. Patient genetic data resides in your infrastructure at every stage. Not a policy — an auditable technical invariant.
  • Fully offline operation. The module makes no outbound calls once the library is synchronised. No telemetry, no usage analytics.
  • Research-grade tree depth. Coverage of ≈ 42,400 Y-SNP branches and ≈ 23,900 mtDNA branches via the in-house YFull pipeline.
  • One integration, both lineages. Paternal (Y) and maternal (mtDNA) lineage coverage from a single integration.

Who this is for

European clinical laboratories with NGS capabilities that offer genetic testing to patients and want to enrich report delivery with ancestry historical context — without building that layer internally.

Next step

Read the 1-page technical brief or review the GDPR compliance posture. For an integration conversation, write to acgt@genetichistory.es.