<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Quick note: Usability of Electronic Health Records</title>
	<atom:link href="http://humanfactorsblog.org/2009/02/25/quick-note-usability-of-electronic-health-records/feed/" rel="self" type="application/rss+xml" />
	<link>http://humanfactorsblog.org/2009/02/25/quick-note-usability-of-electronic-health-records/</link>
	<description>Not blaming the user since 2007!</description>
	<lastBuildDate>Fri, 11 May 2012 12:27:42 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.2</generator>
	<item>
		<title>By: Richard Pak</title>
		<link>http://humanfactorsblog.org/2009/02/25/quick-note-usability-of-electronic-health-records/comment-page-1/#comment-739</link>
		<dc:creator>Richard Pak</dc:creator>
		<pubDate>Fri, 27 Mar 2009 14:13:05 +0000</pubDate>
		<guid isPermaLink="false">http://humanfactorsblog.org/?p=694#comment-739</guid>
		<description>That is quite surprising!  I just read the report and perceived or actual usability was not listed as a barrier to adoption.  But I suspect usability issues are embedded in the numbers for &quot;maintenance costs&quot; and &quot;inadequate IT staff&quot;.</description>
		<content:encoded><![CDATA[<p>That is quite surprising!  I just read the report and perceived or actual usability was not listed as a barrier to adoption.  But I suspect usability issues are embedded in the numbers for &#8220;maintenance costs&#8221; and &#8220;inadequate IT staff&#8221;.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Eric Shaver</title>
		<link>http://humanfactorsblog.org/2009/02/25/quick-note-usability-of-electronic-health-records/comment-page-1/#comment-737</link>
		<dc:creator>Eric Shaver</dc:creator>
		<pubDate>Wed, 25 Mar 2009 21:54:36 +0000</pubDate>
		<guid isPermaLink="false">http://humanfactorsblog.org/?p=694#comment-737</guid>
		<description>In line with this topic, the New England Journal of Medicine just released a special article entitled &quot;Use of Electronic Health Records in U.S. Hospitals.&quot;  

They found that only 1.5% of AMA hospital members respondents are using a comprehensive electronic records system.  

You can find it here: http://content.nejm.org/cgi/reprint/NEJMsa0900592v1.pdf</description>
		<content:encoded><![CDATA[<p>In line with this topic, the New England Journal of Medicine just released a special article entitled &#8220;Use of Electronic Health Records in U.S. Hospitals.&#8221;  </p>
<p>They found that only 1.5% of AMA hospital members respondents are using a comprehensive electronic records system.  </p>
<p>You can find it here: <a href="http://content.nejm.org/cgi/reprint/NEJMsa0900592v1.pdf" >http://content.nejm.org/cgi/reprint/NEJMsa0900592v1.pdf</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: TheHumanFactorsBlog</title>
		<link>http://humanfactorsblog.org/2009/02/25/quick-note-usability-of-electronic-health-records/comment-page-1/#comment-1630</link>
		<dc:creator>TheHumanFactorsBlog</dc:creator>
		<pubDate>Wed, 25 Feb 2009 12:48:25 +0000</pubDate>
		<guid isPermaLink="false">http://humanfactorsblog.org/?p=694#comment-1630</guid>
		<description>&lt;span class=&quot;topsy_trackback_comment&quot;&gt;&lt;span class=&quot;topsy_twitter_username&quot;&gt;&lt;span class=&quot;topsy_trackback_content&quot;&gt;New entry: Quick note: Usability of Electronic Health Records http://humanfactorsblog.org/?p=694&lt;/span&gt;&lt;/span&gt;</description>
		<content:encoded><![CDATA[<p><span class="topsy_trackback_comment"><span class="topsy_twitter_username"><span class="topsy_trackback_content">New entry: Quick note: Usability of Electronic Health Records <a href="http://humanfactorsblog.org/?p=694" >http://humanfactorsblog.org/?p=694</a></span></span></span></p>
]]></content:encoded>
	</item>
</channel>
</rss>

