All variants in the TYRP1 gene

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

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

Effect     

Exon     

AscendingDNA change (cDNA)     

RNA change     

Protein     

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     

Owner     
-/? 1i c.? r.(?) p.(?) - benign g.? - IVS1+99T/C - TYRP1_000017 - PubMed: Manga 1997 - - Unknown - - - - - William (Bill) Oetting
?/? 2 c.? r.(?) p.(?) - VUS g.? - 374C>A (Arg87Arg) - TYRP1_000001 - - - rs34509359 Unknown - - - - - William (Bill) Oetting
-/? 2 c.? r.(?) p.(?) - benign g.? - 374C>A (Arg87Arg) - TYRP1_000001 - Lynch et al., 2002 - - Unknown - - - - - William (Bill) Oetting
+/? 3 c.? r.(?) p.(?) - pathogenic g.? - (c.498C>G) S166X - TYRP1_000022 - PubMed: Manga 1997 - - Unknown - 17/19 cases - - - William (Bill) Oetting
?/? 4 c.? r.(?) p.(?) - VUS g.? - 844T>C (Ser243Ser) - TYRP1_000003 - - - rs35866166 Unknown - - - - - William (Bill) Oetting
-/? 4 c.? r.(?) p.(?) - benign g.? - 844T>C (Ser243Ser) - TYRP1_000003 - Lynch et al., 2002 - - Unknown - - - - - William (Bill) Oetting
?/? 5 c.? r.(?) p.(?) - VUS g.? - 955delT - TYRP1_000006 - - - rs35197549 Unknown - - - - - William (Bill) Oetting
+/? 6 c.? r.(?) p.(?) - pathogenic g.? - (c.117C>T) R373X - TYRP1_000025 - PubMed: Forshew 2005 - - Unknown - - - - - William (Bill) Oetting
?/? 8 c.? r.(?) p.(?) - VUS g.? - 1500A>C (Leu500Leu) - TYRP1_000010 - - - rs34060600 Unknown - - - - - William (Bill) Oetting
-/? 8 c.? r.(?) p.(?) - benign g.? - 1500A>C (Leu500Leu) - TYRP1_000010 - Manga et al., 1997 - - Unknown - - - - - William (Bill) Oetting
Legend   How to query  


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