> ## Documentation Index
> Fetch the complete documentation index at: https://docs.getbased.health/llms.txt
> Use this file to discover all available pages before exploring further.
# Import and interpret DNA data with getbased
> Import raw DNA, a SNP report, or selected catalog calls and review 60 curated associations without uploading your genome.
getbased can add genetic context to your labs, recommendations, Light & Sun model, and AI conversations. The public catalog contains **60 SNPs across 18 categories**. It includes health and lab context, context-dependent associations, and educational traits.
Raw DNA and SNP reports are parsed in your browser. getbased keeps only catalog matches and optional mtDNA data, not your complete genome.
Genome findings are wellness and educational context. They are not diagnoses, pathogenic-variant classifications, or polygenic risk scores. Association direction, evidence strength, and personal relevance are separate.
## Ways to add Genome data
You can use any of these paths from the **Genome** lens or **Genetic Modifiers** dashboard widget:
* **Raw DNA file** — scan a provider export against the complete 60-SNP catalog.
* **Report PDF/text** — extract catalog SNP calls from a small clinical or wellness report without using AI.
* **Add SNP manually** — paste one or more catalog rsID and genotype pairs, such as `rs1801133 CT` or `rs8175347 6/7`.
* **mtDNA file or manual haplogroup** — resolve a maternal lineage from supported markers or enter a known haplogroup in the profile editor.
Manual and report entry accept only SNPs already in the getbased catalog. To propose a new catalog entry, use **Suggest a catalog SNP** in the Genome view.
## Supported raw-DNA providers
You need the underlying raw data export, not a PDF health summary.
| Provider | File format | How to download |
| - | - | - |
| **AncestryDNA** | Tab-separated text | Settings → DNA → Download Raw DNA Data |
| **23andMe** | Tab-separated text | Settings → 23andMe Data → Download Raw Data |
| **MyHeritage** | CSV or tab-separated text | DNA → Manage DNA kits → Download Raw Data |
| **FTDNA** (Family Tree DNA) | CSV | myFTDNA → Download Raw Data |
| **Living DNA** | Separate autosomal and motherline text exports | Dashboard → Download Raw DNA |
| **Illumina GenomeStudio / DNAEra** | CSV with `[Header]` and `[Data]` blocks | Provided by your clinical lab |
getbased identifies files by content, not only by filename. Living DNA motherline files are detected as mtDNA instead of being sent through the autosomal parser.
## Import a raw DNA file
Common entry points open the same local file picker:
* Open **Genome** and choose **Add your DNA data**.
* Add or open the **Genetic Modifiers** dashboard widget and use its empty state.
* Use the import button in the header.
* Drag the raw DNA file onto the app.
Select the provider's text or CSV export. The app detects the format from its headers and scans the file locally.
Findings are grouped into risk associations, protective associations, informational traits, and reference or neutral calls. Each interpreted finding shows separate evidence and relevance labels. If you already added report or manual calls, the preview also tells you how many curated overrides will be preserved.
Save the matched calls for the current profile. All non-catalog rows from the raw file are discarded.
No AI provider is needed. Raw DNA is parsed locally in a Web Worker, and report/manual calls use deterministic local parsing and catalog lookup.
## Import a report or add calls manually
Choose **Report PDF/text** when a report contains rsIDs and genotype results but is not a full provider export. getbased can read PDF, text, and CSV reports, normalize allele order and supported repeat genotypes, and preview only calls that match the public catalog.
Choose **Add SNP** to paste a short list directly:
```text theme={null}
rs1801133 CT
rs8175347 6/7
rs429358 TT APOE report
```
You can add an optional source label. Invalid rows and rsIDs outside the catalog are skipped. Accepted calls merge into existing Genome data instead of removing the other calls.
## What the catalog covers
The catalog contains 60 SNPs across 18 categories. A catalog entry can provide biomarker context, a context-dependent association, or an educational trait; inclusion does not imply that every entry is highly actionable or strongly evidenced.
| Category | SNPs | Example genes | Related context |
| - | -: | - | - |
| Methylation | 6 | MTHFR, MTR, MTRR, CBS, BHMT | Homocysteine, folate, vitamin B12 |
| Iron | 5 | HFE, TMPRSS6, TF | Ferritin, transferrin, iron, hemoglobin |
| Lipids | 8 | APOE, CETP, LIPC, PCSK9, LPA | LDL, HDL, cholesterol, triglycerides, Lp(a) |
| Vitamin D | 6 | VDR, GC, CYP2R1, CYP27B1, CYP24A1, DHCR7 region | 25-OH vitamin D and modeled UV response context |
| Vitamin B12 | 4 | FUT2, TCN1, TCN2, CUBN | Vitamin B12 and homocysteine |
| Bilirubin | 2 | UGT1A1 | Total bilirubin |
| Thyroid | 3 | TSHR, DIO1, DIO2 | TSH, fT3, fT4 |
| Fatty acids | 4 | FADS1, FADS2, ELOVL2 | Omega-3 index and fatty-acid metabolism |
| Blood sugar | 5 | TCF7L2, PPARG, ADIPOQ, MTNR1B | Glucose, HbA1c, insulin, HOMA-IR |
| Sex hormones | 5 | SHBG, CYP17A1, CYP19A1, CYP1B1 | Testosterone, estradiol, SHBG, DHEA-S |
| Alcohol | 2 | ALDH2, ADH1B | Alcohol metabolism and liver-marker context |
| Caffeine | 1 | CYP1A2 | Caffeine exposure context |
| Body composition | 1 | FTO | Body composition and glycemic context |
| Neurotransmitter metabolism | 1 | COMT | Educational biochemical trait context |
| Exercise traits | 1 | ACTN3 | Muscle-performance trait context |
| Digestion | 1 | MCM6 / LCT | Lactase-persistence context |
| Vitamin A | 2 | BCO1 | Beta-carotene conversion context |
| Skin & Sun | 3 | MC1R, HERC2 / OCA2 | Pigmentation and sun-sensitivity context |
### APOE haplotype
The two APOE SNPs, `rs429358` and `rs7412`, are interpreted together as the standard ε2, ε3, or ε4 haplotype. The combined haplotype is shown instead of treating the two component calls as independent findings.
## How to read a finding
The Genome view deliberately avoids collapsing everything into one severity score.
### Association direction
| Label | Meaning |
| - | - |
| **Risk association** | The imported genotype is associated with the catalog's narrowly stated risk or biomarker direction. It is not an absolute-risk estimate. |
| **Protective association** | The studied association points in a protective direction. It is not universally beneficial. |
| **Informational trait** | Educational phenotype or biochemical context, not a health warning. |
| **Reference / neutral** | Reference, no-effect, or neutral catalog call. These are kept under **Other imported SNPs**. |
### Evidence strength
| Label | Meaning |
| - | - |
| **Strong / replicated** | Replicated human evidence, a large meta-analysis or GWAS, or a well-established functional variant supports the scoped claim. |
| **Supported** | Credible human or functional evidence supports the claim, with meaningful limitations. |
| **Mixed evidence** | Relevant studies disagree, or functional evidence has not produced a consistent human phenotype. |
| **Preliminary** | The claim relies on a small, single, ancestry-specific, or otherwise limited study. |
| **Mechanistic only** | Laboratory or molecular evidence supports a mechanism, but not a reliable personal health outcome. |
### Personal relevance
| Label | Meaning |
| - | - |
| **Health / lab context** | Interpret with measured biomarkers, symptoms, family history, medications, or professional guidance. |
| **Context-dependent** | Diet, exposure, behavior, ancestry, or environment materially changes what the association means. |
| **Trait only** | Educational trait or biochemical context; no health action follows from genotype alone. |
Open **Evidence & interpretation** on a finding to see the narrowly supported claim, interpretation limits, publication links, **Ask AI**, and **Suggest correction**. A strong evidence label supports that specific claim; it does not mean severe, diagnostic, highly penetrant, or clinically actionable.
## Where Genome data appears
**Genome lens** — shows catalog coverage, APOE, mtDNA, association groups, evidence and relevance, publication links, and contribution links.
**Dashboard** — the **Genetic Modifiers** widget summarizes risk, protective, and trait findings. Expand a row for evidence, interpretation boundaries, source links, **Ask AI**, and correction controls.
**Biomarker details and Recommendations** — relevant findings appear next to affected markers and recommendation context. Genetic hints now retain the evidence and relevance labels instead of presenting genotype as a prescription.
**Light & Sun** — four vitamin-D-pathway loci can apply conservative context weights to the modeled serum-response estimate: `GC rs2282679`, `CYP2R1 rs10741657`, `NADSYN1/DHCR7 rs12785878`, and the `CYP24A1`-region `rs6013897`. This is not a clinical dose calculation or a direct measurement of skin synthesis. VDR and CYP27B1 catalog entries remain informational and do not change the numeric estimate.
**AI chat** — control the **APOE & mtDNA summary**, **Priority SNP findings**, and **Other SNP lookup inventory** separately in **Insight → Manage → Context → Data sources → Genome**. Routine context stays compact and omits long claim and interpretation prose. Choosing **Ask AI** on one finding opens a focused, editable prompt with that finding's evidence, relevance, scope, context, and sources; the selected model can add broader knowledge if it distinguishes established evidence from inference.
You can [read the app-written Genome question](/developers/system-prompts-chat#prompt-chat-prefills) before using it; in the app it opens in the composer so you can edit or remove it before sending.
## mtDNA maternal-line import
getbased can resolve a maternal haplogroup from a supported mitochondrial marker file.
### Supported file formats
Living DNA motherline files can contain one positive mutation per line:
```text theme={null}
263G
462T
1438G
10398G
13708A
```
The parser also accepts 23andMe tab-separated `MT` rows. It compares the observed mutations with diagnostic markers from PhyloTree Build 17 and MITOMAP, shows the matched-marker count, and asks you to confirm before saving.
The catalog covers 39 maternal lineages, including subclades such as A2, H1, H3, J1, J2, K1, T1, T2, U5a, U5b, and U6. When a parent and subclade both match, the resolver prefers the more specific supported match.
### Manual haplogroup entry
If you already know your maternal haplogroup, use **Profile editor → mtDNA Haplogroup (maternal lineage)**. Manual entry stores the lineage and available framework context without pretending that diagnostic mutations were imported.
### Mitochondrial climate-adaptation lens
The Genome view places the maternal lineage on a seven-level continuum from coupled through intermediate to uncoupled and can compare the framework's climate bands with the latitude stored in your profile. It also exposes the framework's supporting, mixed, and null studies with model and limitation notes.
This is an evolutionary bioenergetics lens, not a measured personal coupling test. Population patterns and cell or observational studies cannot determine your preferred climate, prove that a climate causes symptoms, or predict a treatment response. Lineage, tissue, nuclear background, environment, and individual variation all matter.
## Re-importing safely
A new raw file refreshes raw-file calls but preserves:
* mtDNA data;
* SNPs added manually; and
* SNPs imported from a report.
If a new raw file contains the same rsID as a manual or report call, the explicit curated call remains authoritative. The preview and final summary use the preserved result, so a consumer-file call does not silently overwrite a result you intentionally added. Use **Delete** in Genome when you want to remove the complete genetics record rather than refresh it.
## Privacy and storage
* Raw DNA and report files are processed locally and are not uploaded.
* The complete raw file is not stored.
* Raw-file imports store only matched catalog calls and interpretation metadata.
* Manual/report calls also store their source label and can retain the filename and a bounded excerpt around the matched row; they do not store the entire report.
* mtDNA import stores the matched mutation list, resolved lineage, match count, and framework context.
* Genome data is included in profile JSON exports, backups, optional encrypted Sync, and encrypted profile sharing when those features are used.
* Local encryption covers Genome data when encryption is enabled.
* Public suggestion and correction links do not add your genotype, raw DNA, labs, location, or profile notes to the issue URL. Do not paste private health data into a public issue.
## FAQ
The catalog favors narrow, reviewable claims over a long list of weak or ambiguous associations. Evidence can still be strong, supported, mixed, preliminary, or mechanistic; every retained entry must disclose that grade, its personal-relevance level, its claim scope, and publication links. See the [Genome evidence methodology](/developers/genome-evidence-methodology).
Make sure you downloaded the raw text or CSV export rather than a formatted report. For Illumina GenomeStudio output, confirm that the file contains `[Header]` and `[Data]` blocks. Use **Report PDF/text** for a small clinical SNP report instead of dropping it into the raw-file path.
Yes. Choose **Add SNP** and paste one or more rsID and genotype pairs. The rsID must already exist in the getbased catalog, and the genotype must match an allele or supported repeat form for that entry. These calls merge with existing Genome data and survive later raw-file imports.
Yes. Use **Suggest a catalog SNP** or **Suggest correction** in the Genome view. Define a narrow claim and provide primary publication links, study population, effect direction, limitations, and why the entry belongs in a wellness catalog. Never include your genotype or other private profile data in the public issue.
APOE status requires both `rs429358` and `rs7412`. getbased combines the calls into standard ε2/ε3/ε4 notation and avoids listing the component SNPs as independent priority findings when the haplotype is available.
No. Genome data provides context for interpreting labs, traits, and exposures. It does not diagnose a condition or establish a treatment. Discuss consequential findings with a qualified clinician or genetic counselor.
This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.