rsid
The dbSNP identifier, such as rs429358. 23andMe internal identifiers beginning with “i” can be imported, although public catalogues may not have a match for them.
Aquest contingut encara no està disponible en català. El mostrem en anglès.
Already have a 23andMe raw data file?
Upload the original tab-separated export and turn its rsIDs and genotypes into a structured report. DNA Info Lab keeps clinical records, medication evidence and research associations separate, shows what your chip did not cover and lets you inspect free findings before choosing the complete report.
Compatibility here means a parser contract, not a marketing list of kit generations. The tested parser recognises a 23andMe banner or the familiar tab-separated rows and validates the useful fields row by row.
The dbSNP identifier, such as rs429358. 23andMe internal identifiers beginning with “i” can be imported, although public catalogues may not have a match for them.
The chromosome label supplied by the export. It is retained with the imported variant.
The numeric coordinate supplied by the file. A malformed, non-numeric position is rejected.
The reported allele pair. Rows without a genotype and 23andMe no-calls written as “--” are skipped.
Comments, blank lines, malformed rows and “--” no-calls do not become report positions. A skipped no-call is not a negative result: it means that file has no usable genotype at that row.
A 23andMe raw file contains genotypes at selected positions measured by a microarray. It is not a readout of every base in your genome and it is not whole-genome or whole-exome sequencing.
That distinction changes what “not found” means. If a variant is absent from the file, the chip may simply not have tested that position. DNA Info Lab therefore reports matched and available coverage; it does not reinterpret a missing row as a protective result.
The report also cannot discover structural variants, repeat expansions or variants outside the positions represented in the export. A consumer raw file remains a screening and education input, never a clinical diagnostic test.
The importer reads the chromosome, position and genotype written in the original export, but it does not currently infer a 23andMe chip generation, detect the genome build from marker counts, lift coordinates between reference builds or rewrite alleles onto another strand.
Catalogue joins are anchored on rsID. That avoids using the position as the variant identity, but it does not make allele orientation irrelevant: scoring and genotype-specific medication annotations still compare the alleles represented in the imported row. Use the untouched provider export rather than a hand-edited or converted file.
Because the repository has no version-labelled v3, v4 and v5 fixtures, this page does not claim a tested list of those commercial versions. The supported promise is the observable four-column format above.
A usable genotype is compared with three separately imported evidence sources. They are displayed in different report sections because their meanings and evidence standards are different.
The report finds rsIDs present both in the file and in the imported ClinVar catalogue, then shows the clinical classification, review status, associated condition and source record. A chip match still needs clinical confirmation.
Genotype-specific PharmGKB annotations can appear when the rsID and allele pair match the imported record. They describe published drug-response evidence; they do not prescribe, stop or change a medicine.
Research associations can contribute when a reported genotype contains the catalogue’s effect allele. The report preserves the measured trait, study context, effect unit and sources instead of turning associations into diagnoses.
Different arrays and product generations assay different sets of positions. Two valid 23andMe exports can therefore produce different counts, different catalogue overlap and different empty areas even when both are parsed correctly.
Catalogue coverage varies as well: a marker can be in your file but absent from the filtered datasets DNA Info Lab currently serves, or be present in a source without meeting the product’s evidence rules. Conversely, one physical variant can have several studies or condition records; the interface keeps those units distinct.
No minimum number of findings is promised. The useful result may include explicit areas with no supported matches, because an honest coverage statement is more valuable than filling the page with weak associations.
The public demo uses synthetic genotypes and the production report components. You can inspect simple and scientific modes, ClinVar, pharmacogenomics, GWAS sources and the premium boundary without creating an account or exposing a real person’s DNA.
Open the synthetic report →Use the provider download guide to obtain the raw export. Keep it compressed if supplied as ZIP and do not open and resave it in a spreadsheet, which can alter identifiers or formatting.
How to download 23andMe raw data →The server parses the original file in memory and discards that original upload. Extracted variants and derived report results are stored on the service’s EU infrastructure so the account can return to its analysis, subject to deletion and the applicable retention rules.
DNA Info Lab supports the tested, observable four-column tab-separated format described on this page. It does not currently claim a v3/v4/v5 compatibility list because there are no version-labelled fixtures proving each generation.
No. It analyses genotypes already present in your consumer microarray export. No new biological measurement or sequencing occurs.
No. The chip may not test that position, the row may be a no-call or the filtered catalogue may have no supported match. Absence from this report is not clinical evidence of absence.
No. The importer retains the coordinates in the source export and matches catalogue records by rsID. It does not infer the build, lift coordinates or change strand orientation.
No. PharmGKB annotations describe published genotype–drug evidence. Medication decisions belong with a qualified healthcare professional who knows the full clinical context.
No. File processing and the defined free findings come first. The complete report is an optional one-time purchase with no subscription.
The public example is synthetic by design. It shows the product without publishing or indexing another person’s genetic data.
Start with the free analysis, see what this particular file covers and unlock the complete report only if the supported findings are useful to you.
Analyse my 23andMe file →