← System records

Django · Genetic data · Research

myDNAHealth

A substantive private Django experiment in parsing consumer genetic data, retained only as a synthetic historical case study.

State
Restricted historical case study
Form
Case study
Updated
2024-10-09
  1. Synthetic input
  2. Parse
  3. Research view
  4. Educational explanation
01

Problem

Raw genetics exports are difficult to interpret, but health-risk language creates serious correctness and privacy obligations.

02

Actual state

The private Django app contains ingestion, variant matching, prevalence views, reports, and retrieval-assisted explanations. Its health-risk logic and data lifecycle are not suitable for public or clinical use.

03

System architecture

Uploaded genotype data feeds parsing and heuristic matching, reports, cached results, and external retrieval services.

04

Christian's role

Built the Django application, ingestion and reporting flows, visual explanations, and retrieval-assisted learning surfaces.

05

Verified evidence

risk-reviewPrivacy, caching, heuristic, and testing gaps documented
06

Safety, privacy, and authority boundary

  • Synthetic data only in public material
  • No medical claim or clinical validity
  • No DNA files, screenshots, or source link are public
07

Current limitation

  • Clinical correctness, privacy, deletion, security, and health-pipeline tests require reconstruction.
08

Next milestone

None scheduled; preserve safely as earlier work.