485 lines
No EOL
59 KiB
HTML
485 lines
No EOL
59 KiB
HTML
<?xml version="1.0" encoding="utf-8"?>
|
||
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
|
||
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
|
||
|
||
<head><meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
|
||
<!-- AppResources meta begin -->
|
||
<meta name="paf-app-resources" content="" />
|
||
<script type="text/javascript">var ncbi_startTime = new Date();</script>
|
||
|
||
<!-- AppResources meta end -->
|
||
|
||
<!-- TemplateResources meta begin -->
|
||
<meta name="paf_template" content="" />
|
||
|
||
<!-- TemplateResources meta end -->
|
||
|
||
<!-- Logger begin -->
|
||
<meta name="ncbi_db" content="books" /><meta name="ncbi_pdid" content="book-part" /><meta name="ncbi_acc" content="NBK573473" /><meta name="ncbi_domain" content="helpsnpfaq" /><meta name="ncbi_report" content="record" /><meta name="ncbi_type" content="fulltext" /><meta name="ncbi_objectid" content="" /><meta name="ncbi_pcid" content="/NBK573473/" /><meta name="ncbi_pagename" content="Merging RefSNP Numbers and RefSNP Clusters - SNP FAQ Archive - NCBI Bookshelf" /><meta name="ncbi_bookparttype" content="chapter" /><meta name="ncbi_app" content="bookshelf" />
|
||
<!-- Logger end -->
|
||
|
||
<title>Merging RefSNP Numbers and RefSNP Clusters - SNP FAQ Archive - NCBI Bookshelf</title>
|
||
|
||
<!-- AppResources external_resources begin -->
|
||
<link rel="stylesheet" href="/core/jig/1.15.2/css/jig.min.css" /><script type="text/javascript" src="/core/jig/1.15.2/js/jig.min.js"></script>
|
||
|
||
<!-- AppResources external_resources end -->
|
||
|
||
<!-- Page meta begin -->
|
||
<meta name="robots" content="NOINDEX,NOFOLLOW,NOARCHIVE,NOIMAGEINDEX" /><meta name="citation_inbook_title" content="SNP FAQ Archive [Internet]" /><meta name="citation_title" content="Merging RefSNP Numbers and RefSNP Clusters" /><meta name="citation_publisher" content="National Center for Biotechnology Information (US)" /><meta name="citation_date" content="2014/02/18" /><meta name="citation_fulltext_html_url" content="https://www.ncbi.nlm.nih.gov/books/NBK573473/" /><link rel="schema.DC" href="http://purl.org/DC/elements/1.0/" /><meta name="DC.Title" content="Merging RefSNP Numbers and RefSNP Clusters" /><meta name="DC.Type" content="Text" /><meta name="DC.Publisher" content="National Center for Biotechnology Information (US)" /><meta name="DC.Date" content="2014/02/18" /><meta name="DC.Identifier" content="https://www.ncbi.nlm.nih.gov/books/NBK573473/" /><meta name="og:title" content="Merging RefSNP Numbers and RefSNP Clusters" /><meta name="og:type" content="book" /><meta name="og:url" content="https://www.ncbi.nlm.nih.gov/books/NBK573473/" /><meta name="og:site_name" content="NCBI Bookshelf" /><meta name="og:image" content="https://www.ncbi.nlm.nih.gov/corehtml/pmc/pmcgifs/bookshelf/thumbs/th-helpsnpfaq-lrg.png" /><meta name="twitter:card" content="summary" /><meta name="twitter:site" content="@ncbibooks" /><meta name="warning" content="This publication is provided for historical reference only and the information may be out of date." /><meta name="bk-non-canon-loc" content="/books/n/helpsnpfaq/Bld_Mg_RefSNP_RefSNP/" /><link rel="canonical" href="https://www.ncbi.nlm.nih.gov/books/NBK573473/" /><link rel="stylesheet" href="/corehtml/pmc/css/figpopup.css" type="text/css" media="screen" /><link rel="stylesheet" href="/corehtml/pmc/css/bookshelf/2.26/css/books.min.css" type="text/css" /><link rel="stylesheet" href="/corehtml/pmc/css/bookshelf/2.26/css/books_print.min.css" type="text/css" media="print" /><style type="text/css">.main-content {background:transparent repeat-y top left;background-image:url(/corehtml/pmc/css/bookshelf/2.26/img/archive.png);background-size: auto, contain; padding:0 0 0 3em }</style><style type="text/css">p a.figpopup{display:inline !important} .bk_tt {font-family: monospace} .first-line-outdent .bk_ref {display: inline} .body-content h2, .body-content .h2 {border-bottom: 1px solid #97B0C8} .body-content h2.inline {border-bottom: none} a.page-toc-label , .jig-ncbismoothscroll a {text-decoration:none;border:0 !important} .temp-labeled-list .graphic {display:inline-block !important} .temp-labeled-list img{width:100%}</style><script type="text/javascript" src="/corehtml/pmc/js/jquery.hoverIntent.min.js"> </script><script type="text/javascript" src="/corehtml/pmc/js/common.min.js?_=3.18"> </script><script type="text/javascript" src="/corehtml/pmc/js/large-obj-scrollbars.min.js"> </script><script type="text/javascript">window.name="mainwindow";</script><script type="text/javascript" src="/corehtml/pmc/js/bookshelf/2.26/book-toc.min.js"> </script><script type="text/javascript" src="/corehtml/pmc/js/bookshelf/2.26/books.min.js"> </script><meta name="book-collection" content="helpcollect" />
|
||
|
||
<!-- Page meta end -->
|
||
<link rel="shortcut icon" href="//www.ncbi.nlm.nih.gov/favicon.ico" /><meta name="ncbi_phid" content="CE8B9B387C8BDE51000000000093007A.m_13" />
|
||
<meta name='referrer' content='origin-when-cross-origin'/><link type="text/css" rel="stylesheet" href="//static.pubmed.gov/portal/portal3rc.fcgi/4216699/css/3852956/3985586/3808861/4121862/3974050/3917732/251717/4216701/14534/45193/4113719/3849091/3984811/3751656/4033350/3840896/3577051/3852958/4008682/4207974/4206132/4062871/12930/3964959/3854974/36029/4128070/9685/3549676/3609192/3609193/3609213/3395586.css" /><link type="text/css" rel="stylesheet" href="//static.pubmed.gov/portal/portal3rc.fcgi/4216699/css/3411343/3882866.css" media="print" /></head>
|
||
<body class="book-part">
|
||
<div class="grid">
|
||
<div class="col twelve_col nomargin shadow">
|
||
<!-- System messages like service outage or JS required; this is handled by the TemplateResources portlet -->
|
||
<div class="sysmessages">
|
||
<noscript>
|
||
<p class="nojs">
|
||
<strong>Warning:</strong>
|
||
The NCBI web site requires JavaScript to function.
|
||
<a href="/guide/browsers/#enablejs" title="Learn how to enable JavaScript" target="_blank">more...</a>
|
||
</p>
|
||
</noscript>
|
||
</div>
|
||
<!--/.sysmessage-->
|
||
<div class="wrap">
|
||
<div class="page">
|
||
<div class="top">
|
||
<div id="universal_header">
|
||
<section class="usa-banner">
|
||
<div class="usa-accordion">
|
||
<header class="usa-banner-header">
|
||
<div class="usa-grid usa-banner-inner">
|
||
<img src="https://www.ncbi.nlm.nih.gov/coreutils/uswds/img/favicons/favicon-57.png" alt="U.S. flag" />
|
||
<p>An official website of the United States government</p>
|
||
<button class="non-usa-accordion-button usa-banner-button" aria-expanded="false" aria-controls="gov-banner-top" type="button">
|
||
<span class="usa-banner-button-text">Here's how you know</span>
|
||
</button>
|
||
</div>
|
||
</header>
|
||
<div class="usa-banner-content usa-grid usa-accordion-content" id="gov-banner-top" aria-hidden="true">
|
||
<div class="usa-banner-guidance-gov usa-width-one-half">
|
||
<img class="usa-banner-icon usa-media_block-img" src="https://www.ncbi.nlm.nih.gov/coreutils/uswds/img/icon-dot-gov.svg" alt="Dot gov" />
|
||
<div class="usa-media_block-body">
|
||
<p>
|
||
<strong>The .gov means it's official.</strong>
|
||
<br />
|
||
Federal government websites often end in .gov or .mil. Before
|
||
sharing sensitive information, make sure you're on a federal
|
||
government site.
|
||
</p>
|
||
</div>
|
||
</div>
|
||
<div class="usa-banner-guidance-ssl usa-width-one-half">
|
||
<img class="usa-banner-icon usa-media_block-img" src="https://www.ncbi.nlm.nih.gov/coreutils/uswds/img/icon-https.svg" alt="Https" />
|
||
<div class="usa-media_block-body">
|
||
<p>
|
||
<strong>The site is secure.</strong>
|
||
<br />
|
||
The <strong>https://</strong> ensures that you are connecting to the
|
||
official website and that any information you provide is encrypted
|
||
and transmitted securely.
|
||
</p>
|
||
</div>
|
||
</div>
|
||
</div>
|
||
</div>
|
||
</section>
|
||
<div class="usa-overlay"></div>
|
||
<header class="ncbi-header" role="banner" data-section="Header">
|
||
|
||
<div class="usa-grid">
|
||
<div class="usa-width-one-whole">
|
||
|
||
<div class="ncbi-header__logo">
|
||
<a href="/" class="logo" aria-label="NCBI Logo" data-ga-action="click_image" data-ga-label="NIH NLM Logo">
|
||
<img src="https://www.ncbi.nlm.nih.gov/coreutils/nwds/img/logos/AgencyLogo.svg" alt="NIH NLM Logo" />
|
||
</a>
|
||
</div>
|
||
|
||
<div class="ncbi-header__account">
|
||
<a id="account_login" href="https://account.ncbi.nlm.nih.gov" class="usa-button header-button" style="display:none" data-ga-action="open_menu" data-ga-label="account_menu">Log in</a>
|
||
<button id="account_info" class="header-button" style="display:none" aria-controls="account_popup" type="button">
|
||
<span class="fa fa-user" aria-hidden="true">
|
||
<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 24 24" width="20px" height="20px">
|
||
<g style="fill: #fff">
|
||
<ellipse cx="12" cy="8" rx="5" ry="6"></ellipse>
|
||
<path d="M21.8,19.1c-0.9-1.8-2.6-3.3-4.8-4.2c-0.6-0.2-1.3-0.2-1.8,0.1c-1,0.6-2,0.9-3.2,0.9s-2.2-0.3-3.2-0.9 C8.3,14.8,7.6,14.7,7,15c-2.2,0.9-3.9,2.4-4.8,4.2C1.5,20.5,2.6,22,4.1,22h15.8C21.4,22,22.5,20.5,21.8,19.1z"></path>
|
||
</g>
|
||
</svg>
|
||
</span>
|
||
<span class="username desktop-only" aria-hidden="true" id="uname_short"></span>
|
||
<span class="sr-only">Show account info</span>
|
||
</button>
|
||
</div>
|
||
|
||
<div class="ncbi-popup-anchor">
|
||
<div class="ncbi-popup account-popup" id="account_popup" aria-hidden="true">
|
||
<div class="ncbi-popup-head">
|
||
<button class="ncbi-close-button" data-ga-action="close_menu" data-ga-label="account_menu" type="button">
|
||
<span class="fa fa-times">
|
||
<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 48 48" width="24px" height="24px">
|
||
<path d="M38 12.83l-2.83-2.83-11.17 11.17-11.17-11.17-2.83 2.83 11.17 11.17-11.17 11.17 2.83 2.83 11.17-11.17 11.17 11.17 2.83-2.83-11.17-11.17z"></path>
|
||
</svg>
|
||
</span>
|
||
<span class="usa-sr-only">Close</span></button>
|
||
<h4>Account</h4>
|
||
</div>
|
||
<div class="account-user-info">
|
||
Logged in as:<br />
|
||
<b><span class="username" id="uname_long">username</span></b>
|
||
</div>
|
||
<div class="account-links">
|
||
<ul class="usa-unstyled-list">
|
||
<li><a id="account_myncbi" href="/myncbi/" class="set-base-url" data-ga-action="click_menu_item" data-ga-label="account_myncbi">Dashboard</a></li>
|
||
<li><a id="account_pubs" href="/myncbi/collections/bibliography/" class="set-base-url" data-ga-action="click_menu_item" data-ga-label="account_pubs">Publications</a></li>
|
||
<li><a id="account_settings" href="/account/settings/" class="set-base-url" data-ga-action="click_menu_item" data-ga-label="account_settings">Account settings</a></li>
|
||
<li><a id="account_logout" href="/account/signout/" class="set-base-url" data-ga-action="click_menu_item" data-ga-label="account_logout">Log out</a></li>
|
||
</ul>
|
||
</div>
|
||
</div>
|
||
</div>
|
||
|
||
</div>
|
||
</div>
|
||
</header>
|
||
<div role="navigation" aria-label="access keys">
|
||
<a id="nws_header_accesskey_0" href="https://www.ncbi.nlm.nih.gov/guide/browsers/#ncbi_accesskeys" class="usa-sr-only" accesskey="0" tabindex="-1">Access keys</a>
|
||
<a id="nws_header_accesskey_1" href="https://www.ncbi.nlm.nih.gov" class="usa-sr-only" accesskey="1" tabindex="-1">NCBI Homepage</a>
|
||
<a id="nws_header_accesskey_2" href="/myncbi/" class="set-base-url usa-sr-only" accesskey="2" tabindex="-1">MyNCBI Homepage</a>
|
||
<a id="nws_header_accesskey_3" href="#maincontent" class="usa-sr-only" accesskey="3" tabindex="-1">Main Content</a>
|
||
<a id="nws_header_accesskey_4" href="#" class="usa-sr-only" accesskey="4" tabindex="-1">Main Navigation</a>
|
||
</div>
|
||
<section data-section="Alerts">
|
||
<div class="ncbi-alerts-placeholder"></div>
|
||
</section>
|
||
</div>
|
||
<div class="header">
|
||
<div class="res_logo"><h1 class="res_name"><a href="/books/" title="Bookshelf home">Bookshelf</a></h1><h2 class="res_tagline"></h2></div>
|
||
<div class="search"><form method="get" action="/books/"><div class="search_form"><label for="database" class="offscreen_noflow">Search database</label><select id="database"><optgroup label="Recent"><option value="books" selected="selected" data-ac_dict="bookshelf-search">Books</option><option value="biosample">BioSample</option><option value="medgen">MedGen</option><option value="dbvar" class="last">dbVar</option></optgroup><optgroup label="All"><option value="gquery">All Databases</option><option value="assembly">Assembly</option><option value="biocollections">Biocollections</option><option value="bioproject">BioProject</option><option value="biosample">BioSample</option><option value="books" data-ac_dict="bookshelf-search">Books</option><option value="clinvar">ClinVar</option><option value="cdd">Conserved Domains</option><option value="gap">dbGaP</option><option value="dbvar">dbVar</option><option value="gene">Gene</option><option value="genome">Genome</option><option value="gds">GEO DataSets</option><option value="geoprofiles">GEO Profiles</option><option value="gtr">GTR</option><option value="ipg">Identical Protein Groups</option><option value="medgen">MedGen</option><option value="mesh">MeSH</option><option value="nlmcatalog">NLM Catalog</option><option value="nuccore">Nucleotide</option><option value="omim">OMIM</option><option value="pmc">PMC</option><option value="protein">Protein</option><option value="proteinclusters">Protein Clusters</option><option value="protfam">Protein Family Models</option><option value="pcassay">PubChem BioAssay</option><option value="pccompound">PubChem Compound</option><option value="pcsubstance">PubChem Substance</option><option value="pubmed">PubMed</option><option value="snp">SNP</option><option value="sra">SRA</option><option value="structure">Structure</option><option value="taxonomy">Taxonomy</option><option value="toolkit">ToolKit</option><option value="toolkitall">ToolKitAll</option><option value="toolkitbookgh">ToolKitBookgh</option></optgroup></select><div class="nowrap"><label for="term" class="offscreen_noflow" accesskey="/">Search term</label><div class="nowrap"><input type="text" name="term" id="term" title="Search Books. Use up and down arrows to choose an item from the autocomplete." value="" class="jig-ncbiclearbutton jig-ncbiautocomplete" data-jigconfig="dictionary:'bookshelf-search',disableUrl:'NcbiSearchBarAutoComplCtrl'" autocomplete="off" data-sbconfig="ds:'no',pjs:'no',afs:'no'" /></div><button id="search" type="submit" class="button_search nowrap" cmd="go">Search</button></div></div></form><ul class="searchlinks inline_list"><li>
|
||
<a href="/books/browse/">Browse Titles</a>
|
||
</li><li>
|
||
<a href="/books/advanced/">Advanced</a>
|
||
</li><li class="help">
|
||
<a href="/books/NBK3833/">Help</a>
|
||
</li><li class="disclaimer">
|
||
<a target="_blank" data-ga-category="literature_resources" data-ga-action="link_click" data-ga-label="disclaimer_link" href="https://www.ncbi.nlm.nih.gov/books/about/disclaimer/">Disclaimer</a>
|
||
</li></ul></div>
|
||
</div>
|
||
|
||
|
||
|
||
<!--<component id="Page" label="headcontent"/>-->
|
||
|
||
</div>
|
||
<div class="content">
|
||
<!-- site messages -->
|
||
<!-- Custom content 1 -->
|
||
<div class="col1">
|
||
|
||
</div>
|
||
|
||
<div class="container">
|
||
<div id="maincontent" class="content eight_col col">
|
||
<!-- Custom content in the left column above book nav -->
|
||
<div class="col2">
|
||
|
||
</div>
|
||
|
||
<!-- Book content -->
|
||
|
||
|
||
<!-- Custom content between navigation and content -->
|
||
<div class="col3">
|
||
|
||
</div>
|
||
|
||
<div class="document">
|
||
<div class="pre-content"><div><div class="bk_prnt"><p class="small">NCBI Bookshelf. A service of the National Library of Medicine, National Institutes of Health.</p><p>SNP FAQ Archive [Internet]. Bethesda (MD): National Center for Biotechnology Information (US); 2005-. </p></div><div class="messagearea bk_noprnt" style="margin-bottom:1.3846em "><ul class="messages"><li class="warn icon"><span class="icon">This publication is provided for historical reference only and the information may be out of date.</span></li></ul></div><div class="bk_prnt"><p style="color:red;"><strong>This publication is provided for historical reference only and the information may be out of date.</strong></p></div><div class="iconblock clearfix whole_rhythm no_top_margin bk_noprnt"><a class="img_link icnblk_img" title="Table of Contents Page" href="/books/n/helpsnpfaq/"><img class="source-thumb" src="/corehtml/pmc/pmcgifs/bookshelf/thumbs/th-helpsnpfaq-lrg.png" alt="Cover of SNP FAQ Archive" height="100px" width="80px" /></a><div class="icnblk_cntnt eight_col"><h2>SNP FAQ Archive [Internet].</h2><a data-jig="ncbitoggler" href="#__NBK573473_dtls__">Show details</a><div style="display:none" class="ui-widget" id="__NBK573473_dtls__"><div>Bethesda (MD): <a href="https://www.ncbi.nlm.nih.gov/" ref="pagearea=page-banner&targetsite=external&targetcat=link&targettype=publisher">National Center for Biotechnology Information (US)</a>; 2005-.</div></div><div class="half_rhythm"><ul class="inline_list"><li style="margin-right:1em"><a class="bk_cntns" href="/books/n/helpsnpfaq/">Contents</a></li></ul></div></div><div class="icnblk_cntnt two_col"><div class="pagination bk_noprnt"><a class="active page_link prev" href="/books/n/helpsnpfaq/Bld_dbSNP_Mapping/" title="Previous page in this title">< Prev</a><a class="active page_link next" href="/books/n/helpsnpfaq/Bld_Ancest_Allele/" title="Next page in this title">Next ></a></div></div></div></div></div>
|
||
<div class="main-content lit-style" itemscope="itemscope" itemtype="http://schema.org/CreativeWork"><div class="meta-content fm-sec"><h1 id="_NBK573473_"><span class="title" itemprop="name">Merging RefSNP Numbers and RefSNP Clusters</span></h1><p class="small">Created: <span itemprop="datePublished">July 7, 2005</span>; Last Update: <span itemprop="dateModified">February 18, 2014</span>.</p><p><em>Estimated reading time: 7 minutes</em></p></div><div class="body-content whole_rhythm" itemprop="text"><ul class="simple-list"><li><p><a href="#Bld_Mg_RefSNP_RefSNP.rs4823903_which_has">rs4823903, which has merged into rs4253690 (see RsMergeArch) still appears in SNPChrPosOnRef</a></p></li><li><p><a href="#Bld_Mg_RefSNP_RefSNP.the__rscurrent_fiel">The “rsCurrent" field in RsMergeArch contains 129,000 rs numbers not in the ASN.1 flat files or in a dbSNP web search. Is there a list of expired rs numbers?</a></p></li><li><p><a href="#Bld_Mg_RefSNP_RefSNP.do_you_have_tables">Do you have tables that show those rs numbers that have changed between builds and those that have not?</a></p></li><li><p><a href="#Bld_Mg_RefSNP_RefSNP.some_snps_for_a2m_s">Some SNPs for A2M seem redundant: rs3832852 and rs1799759 look like the same SNP, as do rs3832850 and rs35904656. rs5796338 and rs3080599 also look identical.</a></p></li><li><p><a href="#Bld_Mg_RefSNP_RefSNP.i_heard_that_rs_num">I heard that RS numbers are not stable. For example, rs17216163 is now rs717620, and rs17231380 is now rs5186. I assume you don't ever reuse the "retired" numbers? Why did you make some numbers obsolete?</a></p></li><li><p><a href="#Bld_Mg_RefSNP_RefSNP.when_some_refsnp_rs">When some refSNP (rs) clusters merge, the higher number rs cluster is retired. Are retired rs numbers reused when new rs clusters are added?</a></p></li><li><p><a href="#Bld_Mg_RefSNP_RefSNP.why_is_rs8111802_cl">Why is rs8111802 classified as a SNP rather than “mixed” when its exemplar submission is a DIP record?</a></p></li><li><p><a href="#Bld_Mg_RefSNP_RefSNP.dbsnp_has_more_tetr">dbSNP has more tetra-allelic SNPs than one would expect. For example, rs1045642 has 4 alleles (a/c/g/t), but in each population only two show up (C/T or A/G).</a></p></li><li><p><a href="#Bld_Mg_RefSNP_RefSNP.c_and_g_are_listed">C and G are listed as alleles in the “Summary of Genotypes” section of the detail report for ss15377600, yet the “Allele” section in the same report shows that the observed alleles are -/T.</a></p></li><li><p><a href="#Bld_Mg_RefSNP_RefSNP.can_two_id_numbers">Can two ID numbers correspond to the same SNP?</a></p></li><li><p><a href="#Bld_Mg_RefSNP_RefSNP.we_observed_two_dif">We observed two different SNPs at the same position, T/T and C/T, where the reference sequence is C/C. Would these two alleles be assigned individual refSNP numbers, or would they be assigned one refSNP number together?</a></p></li></ul><div><h4 id="Bld_Mg_RefSNP_RefSNP.rs4823903_which_has">rs4823903, which has merged into <a href="/snp/?term=4253690" class="bk_tag" ref="pagearea=body&targetsite=entrez&targetcat=term&targettype=snp">rs4253690</a> (see RsMergeArch) still appears in SNPChrPosOnRef</h4><blockquote><p>Cases like rs4823903 have a bit of a twist in their history that you can see in SNPHistory:</p><pre> [502] MSSNP_LOAD.human_9606.2> select * from SNPHistory where snp_id =4823903<br />[502] MSSNP_LOAD.human_9606.3> go -mvertsnp_id:              4823903<br /><br />create_time:         Feb 20 2003 01:26PM<br />last_updated_time:   Sep 07 2006 01:03PM<br />history_create_time: Oct 25 2006 12:19PM<br />comment: Re-activated:PHARMGKB:rs4823903|b126->rs60186231|b129:<a href="/nuccore/89059047" class="bk_tag" ref="pagearea=body&targetsite=entrez&targetcat=link&targettype=nuccore">NT_011523</a>.11_1851628</pre><p>Submitter PHARMGKB submitted many high visibility SNPs in 2003, but also withdrew a large batch in 2006. Many of their SNPs are still valid and have been cited and used successfully in experiments by dbSNP users. PHARMGKB has since re-submitted many of their withdrawn SNPs to dbSNP, and we decided to "re-activate" the same rs numbers for those SNPs that have the same flanking sequences.</p><p>The "re-activation" was noted in the SNPHistory.comment field. For those re-activated SNPs that merged, I did not go back to change the merge history since it was an event that had indeed occurred. I can see that more work need to be done to clarify the multiple sequence of events for these SNPs. For users who actually use data from RsMergeArch and SNPHistory such clarification is necessary. (<b>09/09/08</b>)</p></blockquote></div><div><h4 id="Bld_Mg_RefSNP_RefSNP.the__rscurrent_fiel">The “rsCurrent" field in RsMergeArch contains 129,000 rs numbers not in the ASN.1 flat files or in a dbSNP web search. Is there a list of expired rs numbers?</h4><blockquote><p>Let me explain how we track both merged and deleted (an entirely different process from merging) refSNP (rs) numbers, by using a hypothetical example where a “chain merge” (multiple rs numbers merge into each other) occurs:</p><p>For example, let us say rs ”A” merged into rs ”B”, and later, rs ”B” merged into rs “C”. As a result of the first merge, the entry for rs ”A” in rsCurrent</p><p>is updated to rs “B”; after the second merge, rsCurrent is then updated to rs “C”. Now, if rs “C”’s submitters withdraw all the member ss numbers within the refSNP cluster rs “C”, then rs “C” will get an entry in the SNPHistory table (the SNPHistory table ONLY contains SNPs that have "become history" — that is, SNPs that have been completely deleted). Please see ftp file for SNPHistory.bcp (located in the <a href="ftp://ftp.ncbi.nlm.nih.gov/snp/database/organism_data/human_9606/" ref="pagearea=body&targetsite=external&targetcat=link&targettype=ftp">snp/database/organism_data/species of interest</a> directory). To find the column names for the SNPHistory table, download the human_9606_table.sql, which is located in the <a href="ftp://ftp.ncbi.nlm.nih.gov/snp/organisms/human_9606/database/organism_schema/" ref="pagearea=body&targetsite=external&targetcat=link&targettype=ftp">human organism_schema directory</a>.</p><p>Getting back to RsMergeArch: since "withdrawing rs “C" is not a merge action, the table RsMergeArch is not updated. RsMergeArch is used to track "rs merge" actions only. I can see that this might be confusing, so when time allows, we will add the following explanation to the RsMergeAch table definition, to make the RsMergeArch.rsCurrent meaning clearer:</p><p>RsMergeArch is used to track each rs merge event.</p><p>If an rs number in RsMergeArch.rsCurrent is withdrawn from dbSNP by submitter request, then an the rs number of the same value as that in rsCurrent will be entered into the SNPHistory table (which contains deleted rs numbers only).</p><p>Please note: "rsCurrent" in RsMergeArch does not mean the "current rs number" in the current dbSNP build". (<b>08/12/08</b>)</p></blockquote></div><div><h4 id="Bld_Mg_RefSNP_RefSNP.do_you_have_tables">Do you have tables that show those rs numbers that have changed between builds and those that have not?</h4><blockquote><p>RefSNP (rs) numbers will change only when a refSNP cluster merges with another cluster. When two clusters merge, the higher rs number is retired, and merged cluster takes the lower rs number.</p><p>You can find the dbSNP rs merge history in the RsMergeArch table, which is located in the <a href="ftp://ftp.ncbi.nlm.nih.gov/snp/database/organism_data/human_9606" ref="pagearea=body&targetsite=external&targetcat=link&targettype=ftp">organism_data</a> directory for a particular organism in the dbSNP FTP site, or you can retrieve a list of merged rs numbers from <a href="/sites/entrez?db=snp" ref="pagearea=body&targetsite=external&targetcat=link&targettype=uri">Entrez SNP</a>. Just type “mergedrs” (without the quotation marks) in the text box at the top of the page and click the “go” button. Each entry in the returned list will include the old rs numbers that has merged, and the new rs number it has merged into (with a link to the refSNP page for the new rs number). You can limit the output to merged rs numbers within a certain species by clicking on the “Limits” tab and then selecting the organism you wish from the organism selection box. (<b>12/03/07:11/03/08</b>)</p></blockquote></div><div><h4 id="Bld_Mg_RefSNP_RefSNP.some_snps_for_a2m_s">Some SNPs for A2M seem redundant: rs3832852 and <a href="/snp/?term=1799759" class="bk_tag" ref="pagearea=body&targetsite=entrez&targetcat=term&targettype=snp">rs1799759</a> look like the same SNP, as do <a href="/snp/?term=3832850" class="bk_tag" ref="pagearea=body&targetsite=entrez&targetcat=term&targettype=snp">rs3832850</a> and rs35904656. rs5796338 and <a href="/snp/?term=3080599" class="bk_tag" ref="pagearea=body&targetsite=entrez&targetcat=term&targettype=snp">rs3080599</a> also look identical.</h4><blockquote><p>We believe that rs3832852 and <a href="/snp/?term=1799759" class="bk_tag" ref="pagearea=body&targetsite=entrez&targetcat=term&targettype=snp">rs1799759</a> in A2M are two separate refSNPs for the following reasons:</p><dl class="temp-labeled-list"><dt>1.</dt><dd><p class="no_top_margin"><a href="/snp/?term=1799759" class="bk_tag" ref="pagearea=body&targetsite=entrez&targetcat=term&targettype=snp">rs1799759</a> has variation as -/ACCAT, and rs3832852 has the variation as -/CCATA. If you put the variation in flanking context, the two different chromosome sequences are:<br /><br /><a href="/snp/?term=1799759" class="bk_tag" ref="pagearea=body&targetsite=entrez&targetcat=term&targettype=snp">rs1799759</a> (-/ACCAT)<br />C-----AG<br />CACCATAG<br /><br />rs3832852 (-/CCATA)<br />CA-----G<br />CACCATAG<br /><br />The deleted sequences above for the two refSNPs are shifted one base, so they remain separate SNPs. Currently in dbSNP, we do not have validation (freq or genotype) information for either of these two SNPs. If you have any validation information for either of these SNPs, please contact <a href="mailto:dev@null" data-email="vog.hin.mln.ibcn@bus-pns" class="oemail">vog.hin.mln.ibcn@bus-pns</a> and submit your data to dbSNP.</p></dd><dt>2.</dt><dd><p class="no_top_margin"><a href="/snp/?term=3832850" class="bk_tag" ref="pagearea=body&targetsite=entrez&targetcat=term&targettype=snp">rs3832850</a> and rs35904656 are 5 bases apart in mapping, and are therefore distinct SNPs.</p></dd><dt>3.</dt><dd><p class="no_top_margin">Similarly, rs5796338 and <a href="/snp/?term=3080599" class="bk_tag" ref="pagearea=body&targetsite=entrez&targetcat=term&targettype=snp">rs3080599</a> are 16 bases apart in mapping, and are therefore distinct SNPs. (<b>10/5/07</b>)</p></dd></dl></blockquote></div><div><h4 id="Bld_Mg_RefSNP_RefSNP.i_heard_that_rs_num">I heard that RS numbers are not stable. For example, rs17216163 is now <a href="/snp/?term=717620" class="bk_tag" ref="pagearea=body&targetsite=entrez&targetcat=term&targettype=snp">rs717620</a>, and rs17231380 is now <a href="/snp/?term=5186" class="bk_tag" ref="pagearea=body&targetsite=entrez&targetcat=term&targettype=snp">rs5186</a>. I assume you don't ever reuse the "retired" numbers? Why did you make some numbers obsolete?</h4><blockquote><p>The examples you cite are instances where multiple rs numbers were assigned at the same genomic location, and the higher rs number was merged into a lower rs number (this is the dbSNP merge rule for rs numbers). Such a merge can happen when submissions differ in the length and quality of flanking sequence. We only merge rs numbers that have an identical set of mappings to the genome and have the same type of alleles (e.g. both must be the same variation type and share one allele in common). We would not merge a SNP and an indel (insertion/deletion) into a single rs number (different variation classes) since they represent to different types of mutational "events".</p><p>The location of the rs number remains valid and we never reuse rs numbers.</p><p>We have discussed the issue of supporting query by merged rs numbers more robustly in dbSNP, Entrez and our web based services. That way a retired rs number can be found easily and used as a proxy for the current "live" number. Please note that merging is only used to reduce redundancy in the catalog of rs numbers so each position has a unique identifier.</p><p>In the first example you cite, prior to their merge, both rs17216163 and <a href="/snp/?term=717620" class="bk_tag" ref="pagearea=body&targetsite=entrez&targetcat=term&targettype=snp">rs717620</a> would have been the "address" for the same nucleotide. Now only <a href="/snp/?term=717620" class="bk_tag" ref="pagearea=body&targetsite=entrez&targetcat=term&targettype=snp">rs717620</a> is used in annotation, and rs17216163 is retained in our merge history tables. With extended annotation, users would be able to query by the full set of retired rs numbers.</p><p>Currently, there are three different entry points in dbSNP that will lead you to the partner numbers of a merge:</p><dl class="temp-labeled-list"><dt>1.</dt><dd><p class="no_top_margin">You can retrieve a list of merged rs numbers from <a href="/sites/entrez?db=snp" ref="pagearea=body&targetsite=external&targetcat=link&targettype=uri">Entrez SNP</a>. Just type “mergedrs” (without the quotation marks) in the text box at the top of the page and click the “go” button. Each entry in the returned list will include the old rs numbers that has merged, and the new rs number it has merged into (with a link to the refSNPpage for the new rs number). You can limit the output to merged rs numbers within a certain species by clicking on the “Limits” tab and then selecting the organism you wish from the organism selection box.</p></dd><dt>2.</dt><dd><p class="no_top_margin">If you enter a merged old rs number into the “Search for IDs” search on the dbSNP home page, the response page will state that the SNP has been merged, and will provide the new rs number and a link to the refSNP page for that new rs number.</p></dd><dt>3.</dt><dd><p class="no_top_margin">The <a href="ftp://ftp.ncbi.nlm.nih.gov/snp/organisms/human_9606/database/organism_data/RsMergeArch.bcp.gz" ref="pagearea=body&targetsite=external&targetcat=link&targettype=ftp">RsMergeArch table</a> houses the merged SNPs, and is available on the dbSNP ftp site. A full description of the table can be found in the <a href="/SNP/snp_db_table_description.cgi?t=RsMergeArch" ref="pagearea=body&targetsite=external&targetcat=link&targettype=uri">dbSNP Data Dictionary</a>, and the column definitions are located in the dbSNP_main_table.sql.gz, which can be found in the <a href="ftp://ftp.ncbi.nlm.nih.gov/snp/database/shared_schema" ref="pagearea=body&targetsite=external&targetcat=link&targettype=ftp">shared<wbr style="display:inline-block"></wbr>_schema</a> directory of the dbSNP FTP site.</p></dd></dl><p>(<b>11/06/07:11/03/08</b>)</p></blockquote></div><div><h4 id="Bld_Mg_RefSNP_RefSNP.when_some_refsnp_rs">When some refSNP (rs) clusters merge, the higher number rs cluster is retired. Are retired rs numbers reused when new rs clusters are added?</h4><blockquote><p>When merging causes a rs number to retire, that rs number will never be reused. (<b>12/03/07</b>)</p></blockquote></div><div><h4 id="Bld_Mg_RefSNP_RefSNP.why_is_rs8111802_cl">Why is <a href="/snp/?term=8111802" class="bk_tag" ref="pagearea=body&targetsite=entrez&targetcat=term&targettype=snp">rs8111802</a> classified as a SNP rather than “mixed” when its exemplar submission is a DIP record?</h4><blockquote><p>The SNP development group thinks that it is best if we do not cluster or merge SNPs of different variation classes even when they map to the exact same contig location. This affects about 50K of the current refSNP (rs) numbers, including <a href="/snp/?term=8111802" class="bk_tag" ref="pagearea=body&targetsite=entrez&targetcat=term&targettype=snp">rs8111802</a>. We will split these current SNP clusters by SNP class and work out all related details soon.(<b>10/6/06</b>)</p></blockquote></div><div><h4 id="Bld_Mg_RefSNP_RefSNP.dbsnp_has_more_tetr">dbSNP has more tetra-allelic SNPs than one would expect. For example, <a href="/snp/?term=1045642" class="bk_tag" ref="pagearea=body&targetsite=entrez&targetcat=term&targettype=snp">rs1045642</a> has 4 alleles (a/c/g/t), but in each population only two show up (C/T or A/G).</h4><blockquote><p>You are correct — most of the tetra-allelic SNPs in dbSNP are the result of cluster orientation error. There are a total of 2361 human SNPs that are tetra-allelic. We are working on re-blasting these SNPs and correcting this problem. <b>(9/19/05)</b></p></blockquote></div><div><h4 id="Bld_Mg_RefSNP_RefSNP.c_and_g_are_listed">C and G are listed as alleles in the “Summary of Genotypes” section of the detail report for <a href="/snp/?term=15377600" class="bk_tag" ref="pagearea=body&targetsite=entrez&targetcat=term&targettype=snp">ss15377600</a>, yet the “Allele” section in the same report shows that the observed alleles are -/T.</h4><blockquote><p>One of the idiosyncrasies of dbSNP is that genotype & frequency data need to be linked to one of the submitted-SNP(ss) records within a refSNP(rs) cluster — specifically the ss exemplar for that cluster (see FAQ regarding ss exemplars for a refSNP) — because a refSNP will sometimes merge away. Linking genotype & frequency data to the ss exemplar becomes a problem when different submitted SNPs contribute different variations to the refSNP cluster. This is the problem with the submitted SNP (<a href="/snp/?term=15377600" class="bk_tag" ref="pagearea=body&targetsite=entrez&targetcat=term&targettype=snp">ss15377600</a>) you mention in your question. In this case, <a href="/snp/?term=15377600" class="bk_tag" ref="pagearea=body&targetsite=entrez&targetcat=term&targettype=snp">ss15377600</a> happens to be the exemplar for the refSNP cluster, and is an in/del variation, while all other ss in the rs2070922 cluster are true SNPs and contribute the allele frequencies you found in the “Summary of Genotypes” section of the report.</p><p>The SNPdev team is thinking about separating refSNP clusters if the exemplar submitted SNPs within that cluster is of a different class from the other submitted SNPs in the cluster (such as indel vs. true SNP, as in this example). I will try to determine how many ss exemplars do not have the alleles reported in their refSNP genotypes. In the meantime, please look at the refSNP allele list to see if a submitted SNP genotype allele is valid or not. <b>(2/28/05)</b></p></blockquote></div><div><h4 id="Bld_Mg_RefSNP_RefSNP.can_two_id_numbers">Can two ID numbers correspond to the same SNP?</h4><blockquote><p>If you mean “can two SNPs map to the same contig and position”, then yes, it is possible. If the two SNPs map to same contig location, but have different variation classes (e.g. a true SNP like “A/G”, and an in/del SNP like “-/A”), we will not cluster them in the future. If the two SNPs have the same variation class (e.g. both are true single base substitutions), then we will merge them in a subsequent build. <b>(3/3/05)</b></p></blockquote></div><div><h4 id="Bld_Mg_RefSNP_RefSNP.we_observed_two_dif">We observed two different SNPs at the same position, T/T and C/T, where the reference sequence is C/C. Would these two alleles be assigned individual refSNP numbers, or would they be assigned one refSNP number together?</h4><blockquote><p>We cluster submitted SNPs into a refSNP based on the submitted SNPs’ genome mapping position, or based on their flanking sequence similarity. In your case, the two SNPs you found would be assigned one refSNP ID number. To report alleles in a submitted SNP, you would list all the alleles that you have observed in a mapping position. In your case, it would be “C” and “T”, so you would report the SNP as “C/T”. If you have individual sample genotypes, then you would report the genotype for each individual.</p></blockquote></div><div id="bk_toc_contnr"></div></div></div>
|
||
<div class="post-content"><div><div class="half_rhythm"><a href="/books/about/copyright/">Copyright Notice</a></div><div class="small"><span class="label">Bookshelf ID: NBK573473</span></div><div style="margin-top:2em" class="bk_noprnt"><a class="bk_cntns" href="/books/n/helpsnpfaq/">Contents</a><div class="pagination bk_noprnt"><a class="active page_link prev" href="/books/n/helpsnpfaq/Bld_dbSNP_Mapping/" title="Previous page in this title">< Prev</a><a class="active page_link next" href="/books/n/helpsnpfaq/Bld_Ancest_Allele/" title="Next page in this title">Next ></a></div></div></div></div>
|
||
|
||
</div>
|
||
|
||
<!-- Custom content below content -->
|
||
<div class="col4">
|
||
|
||
</div>
|
||
|
||
|
||
<!-- Book content -->
|
||
|
||
<!-- Custom contetnt below bottom nav -->
|
||
<div class="col5">
|
||
|
||
</div>
|
||
</div>
|
||
|
||
<div id="rightcolumn" class="four_col col last">
|
||
<!-- Custom content above discovery portlets -->
|
||
<div class="col6">
|
||
<div id="ncbi_share_book"><a href="#" class="ncbi_share" data-ncbi_share_config="popup:false,shorten:true" ref="id=NBK573473&db=books">Share</a></div>
|
||
|
||
</div>
|
||
<div xmlns:np="http://ncbi.gov/portal/XSLT/namespace" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"></div><div class="portlet"><div class="portlet_head"><div class="portlet_title"><h3><span>Views</span></h3></div><a name="Shutter" sid="1" href="#" class="portlet_shutter" title="Show/hide content" remembercollapsed="true" pgsec_name="PDF_download" id="Shutter"></a></div><div class="portlet_content"><ul xmlns:np="http://ncbi.gov/portal/XSLT/namespace" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" class="simple-list"><li><a href="/books/NBK573473/?report=reader">PubReader</a></li><li><a href="/books/NBK573473/?report=printable">Print View</a></li><li><a data-jig="ncbidialog" href="#_ncbi_dlg_citbx_NBK573473" data-jigconfig="width:400,modal:true">Cite this Page</a><div id="_ncbi_dlg_citbx_NBK573473" style="display:none" title="Cite this Page"><div class="bk_tt">SNP FAQ Archive [Internet]. Bethesda (MD): National Center for Biotechnology Information (US); 2005-. Merging RefSNP Numbers and RefSNP Clusters. 2005 Jul 7 [Updated 2014 Feb 18].<span class="bk_cite_avail"></span></div></div></li><li><a href="/books/NBK573473/pdf/Bookshelf_NBK573473.pdf">PDF version of this page</a> (78K)</li><li><a href="/books/n/helpsnpfaq/pdf/">PDF version of this title</a> (17K)</li></ul></div></div><div class="portlet"><div class="portlet_head"><div class="portlet_title"><h3><span>Other titles in this collection</span></h3></div><a name="Shutter" sid="1" href="#" class="portlet_shutter" title="Show/hide content" remembercollapsed="true" pgsec_name="source-links" id="Shutter"></a></div><div class="portlet_content"><ul xmlns:np="http://ncbi.gov/portal/XSLT/namespace" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" class="simple-list"><li><a href="/books/n/helpcollect/">NCBI Help Manual</a></li></ul></div></div><div class="portlet"><div class="portlet_head"><div class="portlet_title"><h3><span>Recent Activity</span></h3></div><a name="Shutter" sid="1" href="#" class="portlet_shutter" title="Show/hide content" remembercollapsed="true" pgsec_name="recent_activity" id="Shutter"></a></div><div class="portlet_content"><div xmlns:np="http://ncbi.gov/portal/XSLT/namespace" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" id="HTDisplay" class=""><div class="action"><a href="javascript:historyDisplayState('ClearHT')">Clear</a><a href="javascript:historyDisplayState('HTOff')" class="HTOn">Turn Off</a><a href="javascript:historyDisplayState('HTOn')" class="HTOff">Turn On</a></div><ul id="activity"><li class="ra_rcd ralinkpopper two_line"><a class="htb ralinkpopperctrl" ref="log$=activity&linkpos=1" href="/portal/utils/pageresolver.fcgi?recordid=67c8c51eab82281a80ad6095">Merging RefSNP Numbers and RefSNP Clusters - SNP FAQ Archive</a><div class="ralinkpop offscreen_noflow">Merging RefSNP Numbers and RefSNP Clusters - SNP FAQ Archive<div class="brieflinkpopdesc"></div></div><div class="tertiary"></div></li><li class="ra_rcd ralinkpopper two_line"><a class="htb ralinkpopperctrl" ref="log$=activity&linkpos=2" href="/portal/utils/pageresolver.fcgi?recordid=67c8c51da68b6b5afce88a55">The dbSNP Mapping Process - SNP FAQ Archive</a><div class="ralinkpop offscreen_noflow">The dbSNP Mapping Process - SNP FAQ Archive<div class="brieflinkpopdesc"></div></div><div class="tertiary"></div></li><li class="ra_rcd ralinkpopper two_line"><a class="htb ralinkpopperctrl" ref="log$=activity&linkpos=3" href="/portal/utils/pageresolver.fcgi?recordid=67c8c51ca68b6b5afce88404">Finding a Build Number Based on a Date and Vice Versa - SNP FAQ Archive</a><div class="ralinkpop offscreen_noflow">Finding a Build Number Based on a Date and Vice Versa - SNP FAQ Archive<div class="brieflinkpopdesc"></div></div><div class="tertiary"></div></li><li class="ra_rcd ralinkpopper two_line"><a class="htb ralinkpopperctrl" ref="log$=activity&linkpos=4" href="/portal/utils/pageresolver.fcgi?recordid=67c8c51ca68b6b5afce8829d">Finding Old Build Data - SNP FAQ Archive</a><div class="ralinkpop offscreen_noflow">Finding Old Build Data - SNP FAQ Archive<div class="brieflinkpopdesc"></div></div><div class="tertiary"></div></li><li class="ra_rcd ralinkpopper two_line"><a class="htb ralinkpopperctrl" ref="log$=activity&linkpos=5" href="/portal/utils/pageresolver.fcgi?recordid=67c8c51bf4a390645ea453b9">Using Old vs. New Build Data - SNP FAQ Archive</a><div class="ralinkpop offscreen_noflow">Using Old vs. New Build Data - SNP FAQ Archive<div class="brieflinkpopdesc"></div></div><div class="tertiary"></div></li></ul><p class="HTOn">Your browsing activity is empty.</p><p class="HTOff">Activity recording is turned off.</p><p id="turnOn" class="HTOff"><a href="javascript:historyDisplayState('HTOn')">Turn recording back on</a></p><a class="seemore" href="/sites/myncbi/recentactivity">See more...</a></div></div></div>
|
||
|
||
<!-- Custom content below discovery portlets -->
|
||
<div class="col7">
|
||
|
||
</div>
|
||
</div>
|
||
</div>
|
||
|
||
<!-- Custom content after all -->
|
||
<div class="col8">
|
||
|
||
</div>
|
||
<div class="col9">
|
||
|
||
</div>
|
||
|
||
<script type="text/javascript" src="/corehtml/pmc/js/jquery.scrollTo-1.4.2.js"></script>
|
||
<script type="text/javascript">
|
||
(function($){
|
||
$('.skiplink').each(function(i, item){
|
||
var href = $($(item).attr('href'));
|
||
href.attr('tabindex', '-1').addClass('skiptarget'); // ensure the target can receive focus
|
||
$(item).on('click', function(event){
|
||
event.preventDefault();
|
||
$.scrollTo(href, 0, {
|
||
onAfter: function(){
|
||
href.focus();
|
||
}
|
||
});
|
||
});
|
||
});
|
||
})(jQuery);
|
||
</script>
|
||
</div>
|
||
<div class="bottom">
|
||
<script type="text/javascript">
|
||
var PBooksSearchTermData = {
|
||
highlighter: "bold",
|
||
dateTime: "03/05/2025 16:32:49",
|
||
terms: [
|
||
'attack', 'heart', 'heart attack', 'infarction', 'myocardial', 'myocardial infarction', 'myocardial infarction', 'myocardial infarction'
|
||
]
|
||
};
|
||
</script>
|
||
<div id="NCBIFooter_dynamic">
|
||
<!--<component id="Breadcrumbs" label="breadcrumbs"/>
|
||
<component id="Breadcrumbs" label="helpdesk"/>-->
|
||
|
||
</div>
|
||
|
||
<div class="footer" id="footer">
|
||
<section class="icon-section">
|
||
<div id="icon-section-header" class="icon-section_header">Follow NCBI</div>
|
||
<div class="grid-container container">
|
||
<div class="icon-section_container">
|
||
<a class="footer-icon" id="footer_twitter" href="https://twitter.com/ncbi" aria-label="Twitter"><svg xmlns="http://www.w3.org/2000/svg" data-name="Layer 1" viewBox="0 0 300 300">
|
||
<defs>
|
||
<style>
|
||
.cls-11 {
|
||
fill: #737373;
|
||
}
|
||
</style>
|
||
</defs>
|
||
<title>Twitter</title>
|
||
<path class="cls-11" d="M250.11,105.48c-7,3.14-13,3.25-19.27.14,8.12-4.86,8.49-8.27,11.43-17.46a78.8,78.8,0,0,1-25,9.55,39.35,39.35,0,0,0-67,35.85,111.6,111.6,0,0,1-81-41.08A39.37,39.37,0,0,0,81.47,145a39.08,39.08,0,0,1-17.8-4.92c0,.17,0,.33,0,.5a39.32,39.32,0,0,0,31.53,38.54,39.26,39.26,0,0,1-17.75.68,39.37,39.37,0,0,0,36.72,27.3A79.07,79.07,0,0,1,56,223.34,111.31,111.31,0,0,0,116.22,241c72.3,0,111.83-59.9,111.83-111.84,0-1.71,0-3.4-.1-5.09C235.62,118.54,244.84,113.37,250.11,105.48Z">
|
||
</path>
|
||
</svg></a>
|
||
<a class="footer-icon" id="footer_facebook" href="https://www.facebook.com/ncbi.nlm" aria-label="Facebook"><svg xmlns="http://www.w3.org/2000/svg" data-name="Layer 1" viewBox="0 0 300 300">
|
||
<title>Facebook</title>
|
||
<path class="cls-11" d="M210.5,115.12H171.74V97.82c0-8.14,5.39-10,9.19-10h27.14V52l-39.32-.12c-35.66,0-42.42,26.68-42.42,43.77v19.48H99.09v36.32h27.24v109h45.41v-109h35Z">
|
||
</path>
|
||
</svg></a>
|
||
<a class="footer-icon" id="footer_linkedin" href="https://www.linkedin.com/company/ncbinlm" aria-label="LinkedIn"><svg xmlns="http://www.w3.org/2000/svg" data-name="Layer 1" viewBox="0 0 300 300">
|
||
<title>LinkedIn</title>
|
||
<path class="cls-11" d="M101.64,243.37H57.79v-114h43.85Zm-22-131.54h-.26c-13.25,0-21.82-10.36-21.82-21.76,0-11.65,8.84-21.15,22.33-21.15S101.7,78.72,102,90.38C102,101.77,93.4,111.83,79.63,111.83Zm100.93,52.61A17.54,17.54,0,0,0,163,182v61.39H119.18s.51-105.23,0-114H163v13a54.33,54.33,0,0,1,34.54-12.66c26,0,44.39,18.8,44.39,55.29v58.35H198.1V182A17.54,17.54,0,0,0,180.56,164.44Z">
|
||
</path>
|
||
</svg></a>
|
||
<a class="footer-icon" id="footer_github" href="https://github.com/ncbi" aria-label="GitHub"><svg xmlns="http://www.w3.org/2000/svg" data-name="Layer 1" viewBox="0 0 300 300">
|
||
<defs>
|
||
<style>
|
||
.cls-11,
|
||
.cls-12 {
|
||
fill: #737373;
|
||
}
|
||
|
||
.cls-11 {
|
||
fill-rule: evenodd;
|
||
}
|
||
</style>
|
||
</defs>
|
||
<title>GitHub</title>
|
||
<path class="cls-11" d="M151.36,47.28a105.76,105.76,0,0,0-33.43,206.1c5.28,1,7.22-2.3,7.22-5.09,0-2.52-.09-10.85-.14-19.69-29.42,6.4-35.63-12.48-35.63-12.48-4.81-12.22-11.74-15.47-11.74-15.47-9.59-6.56.73-6.43.73-6.43,10.61.75,16.21,10.9,16.21,10.9,9.43,16.17,24.73,11.49,30.77,8.79,1-6.83,3.69-11.5,6.71-14.14C108.57,197.1,83.88,188,83.88,147.51a40.92,40.92,0,0,1,10.9-28.39c-1.1-2.66-4.72-13.42,1-28,0,0,8.88-2.84,29.09,10.84a100.26,100.26,0,0,1,53,0C198,88.3,206.9,91.14,206.9,91.14c5.76,14.56,2.14,25.32,1,28a40.87,40.87,0,0,1,10.89,28.39c0,40.62-24.74,49.56-48.29,52.18,3.79,3.28,7.17,9.71,7.17,19.58,0,14.15-.12,25.54-.12,29,0,2.82,1.9,6.11,7.26,5.07A105.76,105.76,0,0,0,151.36,47.28Z">
|
||
</path>
|
||
<path class="cls-12" d="M85.66,199.12c-.23.52-1.06.68-1.81.32s-1.2-1.06-.95-1.59,1.06-.69,1.82-.33,1.21,1.07.94,1.6Zm-1.3-1">
|
||
</path>
|
||
<path class="cls-12" d="M90,203.89c-.51.47-1.49.25-2.16-.49a1.61,1.61,0,0,1-.31-2.19c.52-.47,1.47-.25,2.17.49s.82,1.72.3,2.19Zm-1-1.08">
|
||
</path>
|
||
<path class="cls-12" d="M94.12,210c-.65.46-1.71,0-2.37-.91s-.64-2.07,0-2.52,1.7,0,2.36.89.65,2.08,0,2.54Zm0,0"></path>
|
||
<path class="cls-12" d="M99.83,215.87c-.58.64-1.82.47-2.72-.41s-1.18-2.06-.6-2.7,1.83-.46,2.74.41,1.2,2.07.58,2.7Zm0,0">
|
||
</path>
|
||
<path class="cls-12" d="M107.71,219.29c-.26.82-1.45,1.2-2.64.85s-2-1.34-1.74-2.17,1.44-1.23,2.65-.85,2,1.32,1.73,2.17Zm0,0">
|
||
</path>
|
||
<path class="cls-12" d="M116.36,219.92c0,.87-1,1.59-2.24,1.61s-2.29-.68-2.3-1.54,1-1.59,2.26-1.61,2.28.67,2.28,1.54Zm0,0">
|
||
</path>
|
||
<path class="cls-12" d="M124.42,218.55c.15.85-.73,1.72-2,1.95s-2.37-.3-2.52-1.14.73-1.75,2-2,2.37.29,2.53,1.16Zm0,0"></path>
|
||
</svg></a>
|
||
<a class="footer-icon" id="footer_blog" href="https://ncbiinsights.ncbi.nlm.nih.gov/" aria-label="Blog">
|
||
<svg xmlns="http://www.w3.org/2000/svg" id="Layer_1" data-name="Layer 1" viewBox="0 0 40 40">
|
||
<defs><style>.cls-1{fill:#737373;}</style></defs>
|
||
<title>NCBI Insights Blog</title>
|
||
<path class="cls-1" d="M14,30a4,4,0,1,1-4-4,4,4,0,0,1,4,4Zm11,3A19,19,0,0,0,7.05,15a1,1,0,0,0-1,1v3a1,1,0,0,0,.93,1A14,14,0,0,1,20,33.07,1,1,0,0,0,21,34h3a1,1,0,0,0,1-1Zm9,0A28,28,0,0,0,7,6,1,1,0,0,0,6,7v3a1,1,0,0,0,1,1A23,23,0,0,1,29,33a1,1,0,0,0,1,1h3A1,1,0,0,0,34,33Z"></path>
|
||
</svg>
|
||
</a>
|
||
</div>
|
||
</div>
|
||
</section>
|
||
|
||
<section class="container-fluid bg-primary">
|
||
<div class="container pt-5">
|
||
<div class="row mt-3">
|
||
<div class="col-lg-3 col-12">
|
||
<p><a class="text-white" href="https://www.nlm.nih.gov/socialmedia/index.html">Connect with NLM</a></p>
|
||
<ul class="list-inline social_media">
|
||
<li class="list-inline-item"><a href="https://twitter.com/NLM_NIH" aria-label="Twitter" target="_blank" rel="noopener noreferrer"><svg xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" version="1.1" x="0px" y="0px" viewBox="0 0 249 249" style="enable-background:new 0 0 249 249;" xml:space="preserve">
|
||
<style type="text/css">
|
||
.st20 {
|
||
fill: #FFFFFF;
|
||
}
|
||
|
||
.st30 {
|
||
fill: none;
|
||
stroke: #FFFFFF;
|
||
stroke-width: 8;
|
||
stroke-miterlimit: 10;
|
||
}
|
||
</style>
|
||
<title>Twitter</title>
|
||
<g>
|
||
<g>
|
||
<g>
|
||
<path class="st20" d="M192.9,88.1c-5,2.2-9.2,2.3-13.6,0.1c5.7-3.4,6-5.8,8.1-12.3c-5.4,3.2-11.4,5.5-17.6,6.7 c-10.5-11.2-28.1-11.7-39.2-1.2c-7.2,6.8-10.2,16.9-8,26.5c-22.3-1.1-43.1-11.7-57.2-29C58,91.6,61.8,107.9,74,116 c-4.4-0.1-8.7-1.3-12.6-3.4c0,0.1,0,0.2,0,0.4c0,13.2,9.3,24.6,22.3,27.2c-4.1,1.1-8.4,1.3-12.5,0.5c3.6,11.3,14,19,25.9,19.3 c-11.6,9.1-26.4,13.2-41.1,11.5c12.7,8.1,27.4,12.5,42.5,12.5c51,0,78.9-42.2,78.9-78.9c0-1.2,0-2.4-0.1-3.6 C182.7,97.4,189.2,93.7,192.9,88.1z"></path>
|
||
</g>
|
||
</g>
|
||
<circle class="st30" cx="124.4" cy="128.8" r="108.2"></circle>
|
||
</g>
|
||
</svg></a></li>
|
||
<li class="list-inline-item"><a href="https://www.facebook.com/nationallibraryofmedicine" aria-label="Facebook" rel="noopener noreferrer" target="_blank">
|
||
<svg xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" version="1.1" x="0px" y="0px" viewBox="0 0 249 249" style="enable-background:new 0 0 249 249;" xml:space="preserve">
|
||
<style type="text/css">
|
||
.st10 {
|
||
fill: #FFFFFF;
|
||
}
|
||
|
||
.st110 {
|
||
fill: none;
|
||
stroke: #FFFFFF;
|
||
stroke-width: 8;
|
||
stroke-miterlimit: 10;
|
||
}
|
||
</style>
|
||
<title>Facebook</title>
|
||
<g>
|
||
<g>
|
||
<path class="st10" d="M159,99.1h-24V88.4c0-5,3.3-6.2,5.7-6.2h16.8V60l-24.4-0.1c-22.1,0-26.2,16.5-26.2,27.1v12.1H90v22.5h16.9 v67.5H135v-67.5h21.7L159,99.1z"></path>
|
||
</g>
|
||
</g>
|
||
<circle class="st110" cx="123.6" cy="123.2" r="108.2"></circle>
|
||
</svg>
|
||
</a></li>
|
||
<li class="list-inline-item"><a href="https://www.youtube.com/user/NLMNIH" aria-label="Youtube" target="_blank" rel="noopener noreferrer"><svg xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" version="1.1" x="0px" y="0px" viewBox="0 0 249 249" style="enable-background:new 0 0 249 249;" xml:space="preserve">
|
||
<title>Youtube</title>
|
||
<style type="text/css">
|
||
.st4 {
|
||
fill: none;
|
||
stroke: #FFFFFF;
|
||
stroke-width: 8;
|
||
stroke-miterlimit: 10;
|
||
}
|
||
|
||
.st5 {
|
||
fill: #FFFFFF;
|
||
}
|
||
</style>
|
||
<circle class="st4" cx="124.2" cy="123.4" r="108.2"></circle>
|
||
<g transform="translate(0,-952.36218)">
|
||
<path class="st5" d="M88.4,1037.4c-10.4,0-18.7,8.3-18.7,18.7v40.1c0,10.4,8.3,18.7,18.7,18.7h72.1c10.4,0,18.7-8.3,18.7-18.7 v-40.1c0-10.4-8.3-18.7-18.7-18.7H88.4z M115.2,1058.8l29.4,17.4l-29.4,17.4V1058.8z"></path>
|
||
</g>
|
||
</svg></a></li>
|
||
</ul>
|
||
</div>
|
||
<div class="col-lg-3 col-12">
|
||
<p class="address_footer text-white">National Library of Medicine<br />
|
||
<a href="https://www.google.com/maps/place/8600+Rockville+Pike,+Bethesda,+MD+20894/@38.9959508,-77.101021,17z/data=!3m1!4b1!4m5!3m4!1s0x89b7c95e25765ddb:0x19156f88b27635b8!8m2!3d38.9959508!4d-77.0988323" class="text-white" target="_blank" rel="noopener noreferrer">8600 Rockville Pike<br />
|
||
Bethesda, MD 20894</a></p>
|
||
</div>
|
||
<div class="col-lg-3 col-12 centered-lg">
|
||
<p><a href="https://www.nlm.nih.gov/web_policies.html" class="text-white">Web Policies</a><br />
|
||
<a href="https://www.nih.gov/institutes-nih/nih-office-director/office-communications-public-liaison/freedom-information-act-office" class="text-white">FOIA</a><br />
|
||
<a href="https://www.hhs.gov/vulnerability-disclosure-policy/index.html" class="text-white" id="vdp">HHS Vulnerability Disclosure</a></p>
|
||
</div>
|
||
<div class="col-lg-3 col-12 centered-lg">
|
||
<p><a class="supportLink text-white" href="https://support.nlm.nih.gov/">Help</a><br />
|
||
<a href="https://www.nlm.nih.gov/accessibility.html" class="text-white">Accessibility</a><br />
|
||
<a href="https://www.nlm.nih.gov/careers/careers.html" class="text-white">Careers</a></p>
|
||
</div>
|
||
</div>
|
||
<div class="row">
|
||
<div class="col-lg-12 centered-lg">
|
||
<nav class="bottom-links">
|
||
<ul class="mt-3">
|
||
<li>
|
||
<a class="text-white" href="//www.nlm.nih.gov/">NLM</a>
|
||
</li>
|
||
<li>
|
||
<a class="text-white" href="https://www.nih.gov/">NIH</a>
|
||
</li>
|
||
<li>
|
||
<a class="text-white" href="https://www.hhs.gov/">HHS</a>
|
||
</li>
|
||
<li>
|
||
<a class="text-white" href="https://www.usa.gov/">USA.gov</a>
|
||
</li>
|
||
</ul>
|
||
</nav>
|
||
</div>
|
||
</div>
|
||
</div>
|
||
</section>
|
||
<script type="text/javascript" src="/portal/portal3rc.fcgi/rlib/js/InstrumentOmnitureBaseJS/InstrumentNCBIConfigJS/InstrumentNCBIBaseJS/InstrumentPageStarterJS.js?v=1"> </script>
|
||
<script type="text/javascript" src="/portal/portal3rc.fcgi/static/js/hfjs2.js"> </script>
|
||
</div>
|
||
</div>
|
||
</div>
|
||
<!--/.page-->
|
||
</div>
|
||
<!--/.wrap-->
|
||
</div><!-- /.twelve_col -->
|
||
</div>
|
||
<!-- /.grid -->
|
||
|
||
<span class="PAFAppResources"></span>
|
||
|
||
<!-- BESelector tab -->
|
||
|
||
|
||
|
||
<noscript><img alt="statistics" src="/stat?jsdisabled=true&ncbi_db=books&ncbi_pdid=book-part&ncbi_acc=NBK573473&ncbi_domain=helpsnpfaq&ncbi_report=record&ncbi_type=fulltext&ncbi_objectid=&ncbi_pcid=/NBK573473/&ncbi_pagename=Merging RefSNP Numbers and RefSNP Clusters - SNP FAQ Archive - NCBI Bookshelf&ncbi_bookparttype=chapter&ncbi_app=bookshelf" /></noscript>
|
||
|
||
|
||
<!-- usually for JS scripts at page bottom -->
|
||
<!--<component id="PageFixtures" label="styles"></component>-->
|
||
|
||
|
||
<!-- CE8B5AF87C7FFCB1_0191SID /projects/books/PBooks@9.11 portal104 v4.1.r689238 Tue, Oct 22 2024 16:10:51 -->
|
||
<span id="portal-csrf-token" style="display:none" data-token="CE8B5AF87C7FFCB1_0191SID"></span>
|
||
|
||
<script type="text/javascript" src="//static.pubmed.gov/portal/portal3rc.fcgi/4216699/js/3879255/4121861/3501987/4008961/3893018/3821238/4062932/4209313/4212053/4076480/3921943/3400083/3426610.js" snapshot="books"></script></body>
|
||
</html> |