Individual #00188821

ID_report -
Reference -
Remarks -
Gender ?
Consanguinity -
Country -
Population -
Age at death -
VIP -
Data_av -
Treatment -
Panel size 1
Diseases ?
Owner name Michael Woods
Database submission license No license selected
Created by Michael Woods
Date created 2008-12-17 12:00:00 +01:00 (CET)
Date last edited N/A


Stop! No phenotypes found for this individual!



Screenings


AscendingScreening ID     

Template     

Technique     

Tissue     

Remarks     

Genes screened     

Variants found     

Owner     
0000189790 DNA ? - - MLH1, MSH6 2 Michael Woods



Variants

2 entries on 1 page. Showing entries 1 - 2.
Legend   How to query  

Chr     

Allele     

Effect     

Classification method     

Clinical classification     

AscendingDNA change (genomic) (hg19)     

DNA change (hg38)     

Published as     

ISCN     

DB-ID     

Variant remarks     

Reference     

ClinVar ID     

dbSNP ID     

Origin     

Segregation     

Frequency     

Re-site     

VIP     

Methylation     

Owner     

Gene     

IDbase Accession Number     

VariO/DNA     

VariO/Protein     

VariO/RNA     

Exon     

DNA change (cDNA)     

Haplotype     

RNA change     

Protein     

P-domain     

Exon_old     

Predicted     

Type/DNA     

Enzyme activity     

mRNA level     

Predict-BioInf     

Legacy protein change     

Protein level     
2 Unknown +/. - pathogenic g.48027733_48027736dup g.47800594_47800597dup 2614_2615insATTA - MSH6_000455 - PubMed: Steinke 2008 - - Germline - - - - - Michael Woods MSH6 - - - - 4 NM_000179.2:c.2611_2614dup - r.(?) p.(Ile872Asnfs*10) - - - - - - - - -
3 Parent #1 ?/. - VUS g.37090070G>T g.37048579G>T - - MLH1_000712 This individual also has an alteration in MSH6 c.2611_2614dupATTA p.Ile872AsnfsX10 (see Supplementary Table 1). PubMed: Steinke 2008 - - Germline - - - - - Michael Woods MLH1 - - - - 17 NM_000249.3:c.1959G>T - r.1959g>u p.= - - - - - - - - -
Legend   How to query  


Screenscraping/webscraping (downloading large amounts of data using scripts) is strictly prohibited.
Use our APIs to retrieve data.