Individual #00322875

ID_report -
Reference PubMed: Marini et al., 2007 (Körkkö and Prockop, personal communication)
Remarks -
Gender -
Consanguinity -
Country -
Population -
Age at death -
VIP -
Data_av -
Treatment -
Panel size 1
Diseases OI, OI1
Owner name Raymond Dalgleish
Database submission license Creative Commons Attribution-NonCommercial-ShareAlike 4.0 InternationalCreative Commons License
Created by Raymond Dalgleish
Date created 2008-03-14 13:11:22 +01:00 (CET)
Date last edited 2014-01-21 14:51:15 +01:00 (CET)


Stop! No phenotypes found for this individual!



Screenings


AscendingScreening ID     

Template     

Technique     

Tissue     

Remarks     

Genes screened     

Variants found     

Owner     
0000324064 ? ? - - COL1A2 1 Raymond Dalgleish



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     
7 Unknown +/+ - pathogenic g.94034033G>A - - - COL1A2_000001 - PubMed: Marini et al., 2007 (Körkkö and Prockop, personal communication) - rs72656358 Unknown - - - - - Raymond Dalgleish COL1A2 - - - - 8 NM_000089.3:c.353G>A - r.(?) p.(Gly118Asp) - - - - - - missense - - - - - Gly28Asp -
Legend   How to query  


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