<?xml version="1.0"?>
<rss version="2.0" xmlns:prism="http://purl.org/rss/1.0/modules/prism/">
  <channel>
    <title>JAMA: Advance Directives Topic Collection</title>
    <link>http://jama.jamanetwork.com/</link>
    <description>
    </description>
    <language>en-us</language>
    <pubDate>Mon, 10 Sep 2012 00:00:00 GMT</pubDate>
    <lastBuildDate>Tue, 01 Jan 2013 00:43:50 GMT</lastBuildDate>
    <generator>Silverchair</generator>
    <managingEditor>editor@jama.jamanetwork.com</managingEditor>
    <webMaster>webmaster@jama.jamanetwork.com</webMaster>
    <item>
      <title>The Evolution of Advance Directives</title>
      <link>http://jama.jamanetwork.com/article.aspx?articleID=1104456</link>
      <pubDate>Wed, 05 Oct 2011 00:00:00 GMT</pubDate>
      <author>White DB, Arnold RM. </author>
      <description>&lt;span class="paragraphSection"&gt;There are 2 widely known problems with end-of-life care in the United States. First, care often does not reflect patients' values and preferences. Second, end-of-life care constitutes a disproportionate amount of health care expenditures. There is a need to improve the value of health care spending because of changing economic and political climates and because Medicare and Medicaid costs account for nearly a quarter of the federal budget. Despite recognition that advance directives have conceptual limitations, their appeal persists because of the theoretical possibility that advance directives can simultaneously improve the patient centeredness of care and decrease health care expenditures near the end of life.&lt;/span&gt;</description>
      <prism:volume xmlns:prism="prism">306</prism:volume>
      <prism:number xmlns:prism="prism">13</prism:number>
      <prism:startingPage xmlns:prism="prism">1485</prism:startingPage>
      <prism:endingPage xmlns:prism="prism">1486</prism:endingPage>
      <prism:doi xmlns:prism="prism">10.1001/jama.2011.1430</prism:doi>
      <guid>http://jama.jamanetwork.com/article.aspx?articleID=1104456</guid>
    </item>
  </channel>
</rss>