Full data view for gene NPHS2

Information The variants shown are described using the NM_014625.2 transcript reference sequence.

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

Effect     

Exon     

AscendingDNA change (cDNA)     

RNA change     

Protein     

Allele     

Classification method     

Clinical classification     

DNA 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     

Template     

Technique     

Tissue     

Remarks     

Disease     

ID_report     

Reference     

Remarks     

Gender     

Consanguinity     

Country     

Population     

Age at death     

VIP     

Data_av     

Treatment     

Panel size     

Owner     
+/? 4 c.479A>G r.(?) p.(D160G) Paternal (confirmed) - pathogenic g.179528869T>C g.179559734T>C - - NPHS2_000007 not in 80 control chromosomes {PMID10742096:Boute 2000}, OMIM:var0008 - - Germline - - - - - DNA SSCA, SEQ - - NPHS2 - {PMID10742096:Boute 2000} - ? yes - (Europe) - - - - 1 Johan den Dunnen
+/? 4 c.479A>G r.(?) p.(D160G) Maternal (confirmed) - pathogenic g.179528869T>C g.179559734T>C - - NPHS2_000007 not in 80 control chromosomes {PMID10742096:Boute 2000}, OMIM:var0008 - - Germline - - - - - DNA SSCA, SEQ - - NPHS2 - {PMID10742096:Boute 2000} - ? yes - (Europe) - - - - 1 Johan den Dunnen
?/? 4 c.479A>G r.(?) p.(D160G) Unknown - VUS g.179528869T>C g.179559734T>C - - NPHS2_000007 - - - rs74315346 Germline - - - - - DNA SEQ - - Healthy/Control - - - ? no - - - - - - 1 Johan den Dunnen
+/? 4 c.479A>G r.(?) p.(Asp160Gly) Both (homozygous) - pathogenic g.179528869T>C g.179559734T>C - - NPHS2_000007 - Weber et al, 2004 (Kid Int) - - Germline - - - - - DNA SEQ - - NPHS2 - Weber et al, 2004 (Kid Int) - - - - - - - - - 1 Olivier Gribouval
Legend   How to query  


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