<?xml version="1.0"?>
<rss version="2.0" xmlns:prism="http://purl.org/rss/1.0/modules/prism/">
  <channel>
    <title>AMA Publishing Group: Genetic Counseling Topic Collection</title>
    <link>http://pubs.jamanetwork.com/</link>
    <description>
    </description>
    <language>en-us</language>
    <pubDate>Wed, 10 Apr 2013 00:00:00 GMT</pubDate>
    <lastBuildDate>Wed, 10 Apr 2013 22:44:53 GMT</lastBuildDate>
    <generator>Silverchair</generator>
    <managingEditor>editor@pubs.jamanetwork.com</managingEditor>
    <webMaster>webmaster@pubs.jamanetwork.com</webMaster>
    <item>
      <title>The Indispensable Role of Professional Judgment in Genomic Medicine Professional Judgment in Genomic Medicine </title>
      <link>http://pubs.jamanetwork.com/article.aspx?articleID=1677382</link>
      <pubDate>Wed, 10 Apr 2013 00:00:00 GMT</pubDate>
      <author> McGuire AL,  McCullough LB, Evans JP. </author>
      <description>&lt;span class="paragraphSection"&gt;Whole-genome sequencing and whole-exome sequencing (WGS/WES) have become increasingly affordable and accessible to individuals. There are currently 3 main pathways through which a person can receive WGS/WES: as a research participant in a genomic study; through a direct-to-consumer personal genome company; or as part of clinical care. In the research context, the extent to which findings from WGS/WES are communicated to study participants and used to inform their clinical care is a topic of much debate, but guidelines suggest that investigators may have an obligation to offer at least some results to study participants.&lt;/span&gt;</description>
      <prism:volume xmlns:prism="prism">309</prism:volume>
      <prism:number xmlns:prism="prism">14</prism:number>
      <prism:startingPage xmlns:prism="prism">1465</prism:startingPage>
      <prism:endingPage xmlns:prism="prism">1466</prism:endingPage>
      <prism:doi xmlns:prism="prism">10.1001/jama.2013.1438</prism:doi>
      <guid>http://pubs.jamanetwork.com/article.aspx?articleID=1677382</guid>
    </item>
  </channel>
</rss>