<?xml version="1.0" encoding="UTF-8"?>

<rdf:RDF
 xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
 xmlns="http://purl.org/rss/1.0/"
 xmlns:content="http://purl.org/rss/1.0/modules/content/"
 xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/"
 xmlns:dc="http://purl.org/dc/elements/1.1/"
 xmlns:syn="http://purl.org/rss/1.0/modules/syndication/"
 xmlns:prism="http://purl.org/rss/1.0/modules/prism/"
 xmlns:admin="http://webns.net/mvcb/"
>

<channel rdf:about="http://jamia.bmj.com">
<title>Journal of the American Medical Informatics Association Viewpoint paper</title>
<link>http://jamia.bmj.com</link>
<description>Journal of the American Medical Informatics Association RSS feed -- recent Viewpoint paper articles</description>
<prism:eIssn>1527-974X</prism:eIssn>
<prism:publicationName>Journal of the American Medical Informatics Association</prism:publicationName>
<prism:issn>1067-5027</prism:issn>
<items>
 <rdf:Seq>
  <rdf:li rdf:resource="http://jamia.bmj.com/cgi/content/short/17/6/615?rss=1" />
  <rdf:li rdf:resource="http://jamia.bmj.com/cgi/content/short/17/6/617?rss=1" />
  <rdf:li rdf:resource="http://jamia.bmj.com/cgi/content/short/17/6/624?rss=1" />
  <rdf:li rdf:resource="http://jamia.bmj.com/cgi/content/short/17/6/671?rss=1" />
 </rdf:Seq>
</items>
<image rdf:resource="http://jamia.bmj.com/site/homepage/JAMIA_95x60.gif" />
</channel>
<image rdf:about="http://jamia.bmj.com/site/homepage/JAMIA_95x60.gif">
<title>Journal of the American Medical Informatics Association</title>
<url>http://jamia.bmj.com/site/homepage/JAMIA_95x60.gif</url>
<link>http://jamia.bmj.com</link>
</image>
<item rdf:about="http://jamia.bmj.com/cgi/content/short/17/6/615?rss=1">
<title><![CDATA[Foundational biomedical informatics research in the clinical and translational science era: a call to action]]></title>
<link>http://jamia.bmj.com/cgi/content/short/17/6/615?rss=1</link>
<description><![CDATA[
<p>Advances in clinical and translational science, along with related national-scale policy and funding mechanisms, have provided significant opportunities for the advancement of applied clinical research informatics (CRI) and translational bioinformatics (TBI). Such efforts are primarily oriented to application and infrastructure development and are critical to the conduct of clinical and translational research. However, they often come at the expense of the foundational CRI and TBI research needed to grow these important biomedical informatics subdisciplines and ensure future innovations. In light of this challenge, it is critical that a number of steps be taken, including the conduct of targeted advocacy campaigns, the development of community-accepted research agendas, and the continued creation of forums for collaboration and knowledge exchange. Such efforts are needed to ensure that the biomedical informatics community is able to advance CRI and TBI science in the context of the modern clinical and translational science era.</p>
]]></description>
<dc:creator><![CDATA[Payne, P. R. O., Embi, P. J., Niland, J.]]></dc:creator>
<dc:date>2010-10-20T08:49:30-07:00</dc:date>
<dc:identifier>info:doi/10.1136/jamia.2010.005165</dc:identifier>
<dc:identifier>hwp:resource-id:amiajnl;17/6/615</dc:identifier>
<dc:publisher>American Medical Informatics Association</dc:publisher>
<dc:subject><![CDATA[Editor''s choice]]></dc:subject>
<dc:title><![CDATA[Foundational biomedical informatics research in the clinical and translational science era: a call to action]]></dc:title>
<prism:publicationDate>2010-11-01</prism:publicationDate>
<prism:section>Viewpoint paper</prism:section>
<prism:volume>17</prism:volume>
<prism:number>6</prism:number>
<prism:startingPage>615</prism:startingPage>
<prism:endingPage>616</prism:endingPage>
</item>
<item rdf:about="http://jamia.bmj.com/cgi/content/short/17/6/617?rss=1">
<title><![CDATA[Health information technology: fallacies and sober realities]]></title>
<link>http://jamia.bmj.com/cgi/content/short/17/6/617?rss=1</link>
<description><![CDATA[
<p>Current research suggests that the rate of adoption of health information technology (HIT) is low, and that HIT may not have the touted beneficial effects on quality of care or costs. The twin issues of the failure of HIT adoption and of HIT efficacy stem primarily from a series of fallacies about HIT. We discuss 12 HIT fallacies and their implications for design and implementation. These fallacies must be understood and addressed for HIT to yield better results. Foundational cognitive and human factors engineering research and development are essential to better inform HIT development, deployment, and use.</p>
]]></description>
<dc:creator><![CDATA[Karsh, B.-T., Weinger, M. B., Abbott, P. A., Wears, R. L.]]></dc:creator>
<dc:date>2010-10-20T08:49:30-07:00</dc:date>
<dc:identifier>info:doi/10.1136/jamia.2010.005637</dc:identifier>
<dc:identifier>hwp:resource-id:amiajnl;17/6/617</dc:identifier>
<dc:publisher>American Medical Informatics Association</dc:publisher>
<dc:title><![CDATA[Health information technology: fallacies and sober realities]]></dc:title>
<prism:publicationDate>2010-11-01</prism:publicationDate>
<prism:section>Viewpoint paper</prism:section>
<prism:volume>17</prism:volume>
<prism:number>6</prism:number>
<prism:startingPage>617</prism:startingPage>
<prism:endingPage>623</prism:endingPage>
</item>
<item rdf:about="http://jamia.bmj.com/cgi/content/short/17/6/624?rss=1">
<title><![CDATA[All's well that ends well for JAMIA editors]]></title>
<link>http://jamia.bmj.com/cgi/content/short/17/6/624?rss=1</link>
<description><![CDATA[
<p>Dr Randolph A Miller begins a self-imposed <I>JAMIA</I> retirement on January 1, 2011 after serving as Editor-in-Chief for eight and a half years. He lauds the selection of Lucia Ohno-Machado as an energetic, innovative, and highly qualified successor.</p>
]]></description>
<dc:creator><![CDATA[Miller, R. A.]]></dc:creator>
<dc:date>2010-10-20T08:49:30-07:00</dc:date>
<dc:identifier>info:doi/10.1136/jamia.2010.008656</dc:identifier>
<dc:identifier>hwp:resource-id:amiajnl;17/6/624</dc:identifier>
<dc:publisher>American Medical Informatics Association</dc:publisher>
<dc:title><![CDATA[All's well that ends well for JAMIA editors]]></dc:title>
<prism:publicationDate>2010-11-01</prism:publicationDate>
<prism:section>Viewpoint paper</prism:section>
<prism:volume>17</prism:volume>
<prism:number>6</prism:number>
<prism:startingPage>624</prism:startingPage>
<prism:endingPage>625</prism:endingPage>
</item>
<item rdf:about="http://jamia.bmj.com/cgi/content/short/17/6/671?rss=1">
<title><![CDATA[Drug safety surveillance using de-identified EMR and claims data: issues and challenges]]></title>
<link>http://jamia.bmj.com/cgi/content/short/17/6/671?rss=1</link>
<description><![CDATA[
<p>The author discusses the challenges of pharmacovigilance using electronic medical record and claims data. Use of ICD-9 encoded data has low sensitivity for detection of adverse drug events (ADEs), because it requires that an ADE escalate to major-complaint level before it can be identified, and because clinical symptomatology is relatively under-represented in ICD-9. A more appropriate vocabulary for ADE identification, SNOMED CT, awaits wider deployment. The narrative-text record of progress notes can potentially be used for more sensitive ADE detection. More effective surveillance will require the ability to grade ADEs by severity. Finally, access to online drug information that includes both a reliable hierarchy of drug families as well as structured information on existing ADEs can improve the focus and predictive ability of surveillance efforts.</p>
]]></description>
<dc:creator><![CDATA[Nadkarni, P. M.]]></dc:creator>
<dc:date>2010-10-20T08:49:30-07:00</dc:date>
<dc:identifier>info:doi/10.1136/jamia.2010.008607</dc:identifier>
<dc:identifier>hwp:resource-id:amiajnl;17/6/671</dc:identifier>
<dc:publisher>American Medical Informatics Association</dc:publisher>
<dc:title><![CDATA[Drug safety surveillance using de-identified EMR and claims data: issues and challenges]]></dc:title>
<prism:publicationDate>2010-11-01</prism:publicationDate>
<prism:section>Viewpoint paper</prism:section>
<prism:volume>17</prism:volume>
<prism:number>6</prism:number>
<prism:startingPage>671</prism:startingPage>
<prism:endingPage>674</prism:endingPage>
</item>
</rdf:RDF>
