<?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: Give Ruby on Rails a shot for medical/clinical web applications</title>
	<atom:link href="http://www.healthcareguy.com/2005/11/17/give-ruby-on-rails-a-shot-for-ehealth-20-applications/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.healthcareguy.com/2005/11/17/give-ruby-on-rails-a-shot-for-ehealth-20-applications/</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: Shahid N. Shah</title>
		<link>http://www.healthcareguy.com/2005/11/17/give-ruby-on-rails-a-shot-for-ehealth-20-applications/comment-page-1/#comment-1284</link>
		<dc:creator>Shahid N. Shah</dc:creator>
		<pubDate>Wed, 16 Dec 2009 18:56:43 +0000</pubDate>
		<guid isPermaLink="false">http://www.healthcareguy.com/?p=59#comment-1284</guid>
		<description>David, thanks for the note -- you are quite correct that the advice is dated and that Ruby on Rails is not only a first-class programming stack but that it is very good for almost anyone doing healthcare IT web applications or sites. Going back and updating all blog entries in the past is probably too much so I&#039;ll probably just write a new posting about it. Thanks again.</description>
		<content:encoded><![CDATA[<p>David, thanks for the note &#8212; you are quite correct that the advice is dated and that Ruby on Rails is not only a first-class programming stack but that it is very good for almost anyone doing healthcare IT web applications or sites. Going back and updating all blog entries in the past is probably too much so I&#39;ll probably just write a new posting about it. Thanks again.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Shahid N. Shah</title>
		<link>http://www.healthcareguy.com/2005/11/17/give-ruby-on-rails-a-shot-for-ehealth-20-applications/comment-page-1/#comment-1157</link>
		<dc:creator>Shahid N. Shah</dc:creator>
		<pubDate>Wed, 16 Dec 2009 11:56:43 +0000</pubDate>
		<guid isPermaLink="false">http://www.healthcareguy.com/?p=59#comment-1157</guid>
		<description>David, thanks for the note -- you are quite correct that the advice is dated and that Ruby on Rails is not only a first-class programming stack but that it is very good for almost anyone doing healthcare IT web applications or sites. Going back and updating all blog entries in the past is probably too much so I&#039;ll probably just write a new posting about it. Thanks again.</description>
		<content:encoded><![CDATA[<p>David, thanks for the note &#8212; you are quite correct that the advice is dated and that Ruby on Rails is not only a first-class programming stack but that it is very good for almost anyone doing healthcare IT web applications or sites. Going back and updating all blog entries in the past is probably too much so I&#39;ll probably just write a new posting about it. Thanks again.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: David </title>
		<link>http://www.healthcareguy.com/2005/11/17/give-ruby-on-rails-a-shot-for-ehealth-20-applications/comment-page-1/#comment-1156</link>
		<dc:creator>David </dc:creator>
		<pubDate>Wed, 16 Dec 2009 03:31:17 +0000</pubDate>
		<guid isPermaLink="false">http://www.healthcareguy.com/?p=59#comment-1156</guid>
		<description>you really need to delete the “be careful about Rails” article.  it is way too dated and now very wrong.  Save face a hit the delete key.  In  2005 it might have been correct but please update your blog.</description>
		<content:encoded><![CDATA[<p>you really need to delete the “be careful about Rails” article.  it is way too dated and now very wrong.  Save face a hit the delete key.  In  2005 it might have been correct but please update your blog.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: contractor web design</title>
		<link>http://www.healthcareguy.com/2005/11/17/give-ruby-on-rails-a-shot-for-ehealth-20-applications/comment-page-1/#comment-1139</link>
		<dc:creator>contractor web design</dc:creator>
		<pubDate>Fri, 04 Dec 2009 01:42:32 +0000</pubDate>
		<guid isPermaLink="false">http://www.healthcareguy.com/?p=59#comment-1139</guid>
		<description>This isn&#039;t all about health actually, right? :D</description>
		<content:encoded><![CDATA[<p>This isn&#39;t all about health actually, right? <img src='http://www.healthcareguy.com/wp-includes/images/smilies/icon_biggrin.gif' alt=':D' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: The Healthcare IT Guy &#187; Best language for secure healthcare applications</title>
		<link>http://www.healthcareguy.com/2005/11/17/give-ruby-on-rails-a-shot-for-ehealth-20-applications/comment-page-1/#comment-11</link>
		<dc:creator>The Healthcare IT Guy &#187; Best language for secure healthcare applications</dc:creator>
		<pubDate>Thu, 23 Feb 2006 01:20:17 +0000</pubDate>
		<guid isPermaLink="false">http://www.healthcareguy.com/?p=59#comment-11</guid>
		<description>[...] If you want to run on different platforms and don&#8217;t have very rich UI needs, Java is a good choice. If it only needs to run best on Windows and has rich UI requirements, .NET is a good choice. That&#8217;s a simplistic view but pretty applicable in the general case. Also, give Ruby and Rails a try (see my earlier article about that). [...]</description>
		<content:encoded><![CDATA[<p>[...] If you want to run on different platforms and don&#8217;t have very rich UI needs, Java is a good choice. If it only needs to run best on Windows and has rich UI requirements, .NET is a good choice. That&#8217;s a simplistic view but pretty applicable in the general case. Also, give Ruby and Rails a try (see my earlier article about that). [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>

