Individual #00470941

ID_report KO
Reference PubMed: Kosaka 2025
Remarks -
Gender -
Consanguinity -
Country Japan
Population -
Age at death -
VIP -
Data_av -
Treatment -
Panel size 1
Diseases GT1
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 2025-12-14 10:57:11 +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     
0000472607 DNA SEQ - - ITGA2B 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     

Predicted     

Type/DNA     

Enzyme activity     

mRNA level     

Predict-BioInf     

Legacy protein change     

Protein level     
17 Unknown +/. - NA g.42462703_42462704insTTGTCC g.44385335_44385336insTTGTCC - - ITGA2B_000051 in vitro expression analysis shows complete loss of PAC-1 binding, reduced binding to soluble fibrinogen after activation and spreading on fibrinogen-coated plates, affects integrin activation PubMed: Kosaka 2025 - - In vitro (cloned) - - - - - Johan den Dunnen ITGA2B - - - - - NM_000419.3:c.575-1_575insGGACAA - - p.Phe191_Ser192insArgThr - - - - - - - - -
Legend   How to query  


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