<?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: Explaining Healthcare IT application UI complexity</title>
	<atom:link href="http://www.healthcareguy.com/2009/02/09/explaining-healthcare-it-application-ui-complexity/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.healthcareguy.com/2009/02/09/explaining-healthcare-it-application-ui-complexity/</link>
	<description>Shahid&#039;s healthcare IT, EMR, EHR, PHR, medical content, and document managment advisory service. Enjoy.</description>
	<lastBuildDate>Thu, 09 Feb 2012 13:50:00 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.1.3</generator>
	<item>
		<title>By: Sean</title>
		<link>http://www.healthcareguy.com/2009/02/09/explaining-healthcare-it-application-ui-complexity/comment-page-1/#comment-841</link>
		<dc:creator>Sean</dc:creator>
		<pubDate>Thu, 03 Sep 2009 05:49:07 +0000</pubDate>
		<guid isPermaLink="false">http://www.healthcareguy.com/?p=467#comment-841</guid>
		<description>Hopefully IT in healthcare matures in the same way.
It will be good for better world</description>
		<content:encoded><![CDATA[<p>Hopefully IT in healthcare matures in the same way.<br />
It will be good for better world</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: BOB HEALTH</title>
		<link>http://www.healthcareguy.com/2009/02/09/explaining-healthcare-it-application-ui-complexity/comment-page-1/#comment-843</link>
		<dc:creator>BOB HEALTH</dc:creator>
		<pubDate>Sat, 22 Aug 2009 03:40:10 +0000</pubDate>
		<guid isPermaLink="false">http://www.healthcareguy.com/?p=467#comment-843</guid>
		<description>hi.... nice posting, keep writing thanks for sharing... thanks</description>
		<content:encoded><![CDATA[<p>hi&#8230;. nice posting, keep writing thanks for sharing&#8230; thanks</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Josh</title>
		<link>http://www.healthcareguy.com/2009/02/09/explaining-healthcare-it-application-ui-complexity/comment-page-1/#comment-844</link>
		<dc:creator>Josh</dc:creator>
		<pubDate>Tue, 18 Aug 2009 09:38:09 +0000</pubDate>
		<guid isPermaLink="false">http://www.healthcareguy.com/?p=467#comment-844</guid>
		<description>Pretty Funny illustration,
I think part of this is most of these apps are mimicking paper forms.</description>
		<content:encoded><![CDATA[<p>Pretty Funny illustration,<br />
I think part of this is most of these apps are mimicking paper forms.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Middle Blog</title>
		<link>http://www.healthcareguy.com/2009/02/09/explaining-healthcare-it-application-ui-complexity/comment-page-1/#comment-845</link>
		<dc:creator>Middle Blog</dc:creator>
		<pubDate>Fri, 14 Aug 2009 18:00:23 +0000</pubDate>
		<guid isPermaLink="false">http://www.healthcareguy.com/?p=467#comment-845</guid>
		<description>nice...   great info guys</description>
		<content:encoded><![CDATA[<p>nice&#8230;   great info guys</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Abayomi Olufemi</title>
		<link>http://www.healthcareguy.com/2009/02/09/explaining-healthcare-it-application-ui-complexity/comment-page-1/#comment-842</link>
		<dc:creator>Abayomi Olufemi</dc:creator>
		<pubDate>Wed, 05 Aug 2009 14:52:09 +0000</pubDate>
		<guid isPermaLink="false">http://www.healthcareguy.com/?p=467#comment-842</guid>
		<description>the complexity of an interface usually prevents users from adopting ICT solutions. This is particularly evident in the developing countries where ICT is still in its infancy.</description>
		<content:encoded><![CDATA[<p>the complexity of an interface usually prevents users from adopting ICT solutions. This is particularly evident in the developing countries where ICT is still in its infancy.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Joseph Kim, MD, MPH</title>
		<link>http://www.healthcareguy.com/2009/02/09/explaining-healthcare-it-application-ui-complexity/comment-page-1/#comment-840</link>
		<dc:creator>Joseph Kim, MD, MPH</dc:creator>
		<pubDate>Wed, 15 Apr 2009 02:06:16 +0000</pubDate>
		<guid isPermaLink="false">http://www.healthcareguy.com/?p=467#comment-840</guid>
		<description>This is a great illustration!</description>
		<content:encoded><![CDATA[<p>This is a great illustration!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Guest Article: What will make healthcare software usable? &#124; The Healthcare IT Guy</title>
		<link>http://www.healthcareguy.com/2009/02/09/explaining-healthcare-it-application-ui-complexity/comment-page-1/#comment-839</link>
		<dc:creator>Guest Article: What will make healthcare software usable? &#124; The Healthcare IT Guy</dc:creator>
		<pubDate>Mon, 13 Apr 2009 11:19:54 +0000</pubDate>
		<guid isPermaLink="false">http://www.healthcareguy.com/?p=467#comment-839</guid>
		<description>[...] a previous post on this blog, three prototypes compared simple experiences using Apple and Google products with the complicated [...]</description>
		<content:encoded><![CDATA[<p>[...] a previous post on this blog, three prototypes compared simple experiences using Apple and Google products with the complicated [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: buy resveratrol</title>
		<link>http://www.healthcareguy.com/2009/02/09/explaining-healthcare-it-application-ui-complexity/comment-page-1/#comment-838</link>
		<dc:creator>buy resveratrol</dc:creator>
		<pubDate>Tue, 07 Apr 2009 21:24:49 +0000</pubDate>
		<guid isPermaLink="false">http://www.healthcareguy.com/?p=467#comment-838</guid>
		<description>Very interesting post, i thought it was pretty funny yet extremely true.</description>
		<content:encoded><![CDATA[<p>Very interesting post, i thought it was pretty funny yet extremely true.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Sandy Rosenbluth</title>
		<link>http://www.healthcareguy.com/2009/02/09/explaining-healthcare-it-application-ui-complexity/comment-page-1/#comment-837</link>
		<dc:creator>Sandy Rosenbluth</dc:creator>
		<pubDate>Tue, 07 Apr 2009 13:35:23 +0000</pubDate>
		<guid isPermaLink="false">http://www.healthcareguy.com/?p=467#comment-837</guid>
		<description>Definitely lol, yet raises a tricky design point.

EMR use must be exceedingly efficient to properly support the fast-paced medical office. Less on the screen is good for training new or non-experienced users but extra clicks and screens usually slow clinical people down and may require greater practice for them to learn where all the functions are located.

More on the screen can greatly increase productivity for experienced users, though at the price of a typically steeper beginner learning curve.

Some may recall this same trade-off in word processors with the old WordPerfect 5.1 (bluescreen version) vs MS Office (windows version).  WP 5.1 was tougher to learn with all its key-combinations, but was the clear choice of professionals due to the speed with which a trained user could create and edit documents.

New users (to word processing) found the windows graphics helpful for initial learning.

All good UI designers should be aware of the tradeoffs and attempt to balance these factors.</description>
		<content:encoded><![CDATA[<p>Definitely lol, yet raises a tricky design point.</p>
<p>EMR use must be exceedingly efficient to properly support the fast-paced medical office. Less on the screen is good for training new or non-experienced users but extra clicks and screens usually slow clinical people down and may require greater practice for them to learn where all the functions are located.</p>
<p>More on the screen can greatly increase productivity for experienced users, though at the price of a typically steeper beginner learning curve.</p>
<p>Some may recall this same trade-off in word processors with the old WordPerfect 5.1 (bluescreen version) vs MS Office (windows version).  WP 5.1 was tougher to learn with all its key-combinations, but was the clear choice of professionals due to the speed with which a trained user could create and edit documents.</p>
<p>New users (to word processing) found the windows graphics helpful for initial learning.</p>
<p>All good UI designers should be aware of the tradeoffs and attempt to balance these factors.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kamal</title>
		<link>http://www.healthcareguy.com/2009/02/09/explaining-healthcare-it-application-ui-complexity/comment-page-1/#comment-836</link>
		<dc:creator>Kamal</dc:creator>
		<pubDate>Thu, 12 Feb 2009 07:08:35 +0000</pubDate>
		<guid isPermaLink="false">http://www.healthcareguy.com/?p=467#comment-836</guid>
		<description>Shahid, thanks for bringing this very important point up. Most EHR and related systems have incredibly complex and &quot;heavy&quot; interfaces.
While designing TrialX, we spend a lot of time and  effort to &lt;a href=&quot;http://blog.trialx.org/2008/12/focusing-on-usability-user-experience.html&quot; rel=&quot;nofollow&quot;&gt;keep the interface simple and minimalistic &lt;/a&gt;.
One thing that has helped in this process is looking at our usage data (e.g., logfiles) to identify problems where users seem to face issues. Also we have implemented a widget (through get satisfaction.com) to allow users to send us quick feedbacks and tips. And we rapidly iterate based on feedback and continue to do so as there are still many avenues for improvement.</description>
		<content:encoded><![CDATA[<p>Shahid, thanks for bringing this very important point up. Most EHR and related systems have incredibly complex and &#8220;heavy&#8221; interfaces.<br />
While designing TrialX, we spend a lot of time and  effort to <a href="http://blog.trialx.org/2008/12/focusing-on-usability-user-experience.html" rel="nofollow">keep the interface simple and minimalistic </a>.<br />
One thing that has helped in this process is looking at our usage data (e.g., logfiles) to identify problems where users seem to face issues. Also we have implemented a widget (through get satisfaction.com) to allow users to send us quick feedbacks and tips. And we rapidly iterate based on feedback and continue to do so as there are still many avenues for improvement.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

