<?xml version="1.0"?>
<rss version="2.0" xmlns:prism="http://purl.org/rss/1.0/modules/prism/">
  <channel>
    <title>AMA Publishing Group: Journalology/Peer Review/Authorship Topic Collection</title>
    <link>http://pubs.jamanetwork.com/</link>
    <description>
    </description>
    <language>en-us</language>
    <pubDate>Mon, 13 May 2013 00:00:00 GMT</pubDate>
    <lastBuildDate>Tue, 14 May 2013 18:45:34 GMT</lastBuildDate>
    <generator>Silverchair</generator>
    <managingEditor>editor@pubs.jamanetwork.com</managingEditor>
    <webMaster>webmaster@pubs.jamanetwork.com</webMaster>
    <item>
      <title>Time to Publication Among Completed Clinical Trials</title>
      <link>http://pubs.jamanetwork.com/article.aspx?articleID=1657754</link>
      <pubDate>Mon, 13 May 2013 00:00:00 GMT</pubDate>
      <author>Ross JS, Mocanu M, Lampropulos JF, et al. </author>
      <description>&lt;span class="paragraphSection"&gt;Prior studies have shown that 25% to 50% of clinical trials are never published. However, among those published, we know little about the length of time required for publication in the peer-reviewed biomedical literature after study completion. Ioannidis previously demonstrated that a sample of randomized phase 2 and 3 trials conducted between 1986 and 1996 required nearly 2.5 years for publication, while our more recent study of National Institutes of Health (NIH)-funded trials found that the average time to publication was almost 2 years. We sought to determine time to publication for a recent and representative sample of trials published in 2009.&lt;/span&gt;</description>
      <prism:volume xmlns:prism="prism">173</prism:volume>
      <prism:number xmlns:prism="prism">9</prism:number>
      <prism:startingPage xmlns:prism="prism">825</prism:startingPage>
      <prism:endingPage xmlns:prism="prism">828</prism:endingPage>
      <prism:doi xmlns:prism="prism">10.1001/jamainternmed.2013.136</prism:doi>
      <guid>http://pubs.jamanetwork.com/article.aspx?articleID=1657754</guid>
    </item>
  </channel>
</rss>