Individual #00050102

ID_report -
Reference PubMed: Lu 2007, Journal: Lu 2007
Remarks 276 controls and 124 CAKUT/VUR probands
Gender -
Consanguinity -
Country -
Population -
Age at death -
VIP -
Data_av -
Treatment -
Panel size 3
Diseases -
Owner name Johan den Dunnen
Database submission license Creative Commons Attribution-NonCommercial-ShareAlike 4.0 InternationalCreative Commons License
Created by Johan den Dunnen
Date created 2015-09-21 20:51:47 +02:00 (CEST)
Date last edited 2015-09-21 21:01:48 +02:00 (CEST)


Stop! No phenotypes found for this individual!



Screenings


AscendingScreening ID     

Template     

Technique     

Tissue     

Remarks     

Genes screened     

Variants found     

Owner     
0000050044 DNA SEQ - - ROBO2 1 Johan den Dunnen



Variants

1 entry on 1 page. Showing entry 1.
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     

Function/GVS     

Predict/AGVGD     

Predict/MutationTaster     

Predict/SIFT     

Predicted     

Type/DNA     

CpG     

Enzyme activity     

mRNA level     

Predict-BioInf     

Legacy protein change     

Protein level     
3 Unknown -?/. - likely benign g.77614215T>C g.77565064T>C 2436T>C (I598T) - ROBO2_000005 - PubMed: Lu 2007, Journal: Lu 2007 - - Unknown ? 3/552 control chromosomes - - - Johan den Dunnen ROBO2 - - - - 13 NM_001128929.2:c.1841T>C - r.(?) p.(Ile614Thr) - - - - - - - - - - - - - -
Legend   How to query  


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