<?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: We&#8217;re Building a REALLY BIG Health Internet!</title>
	<atom:link href="http://e-CareManagement.com/were-building-a-really-big-health-internet/feed/" rel="self" type="application/rss+xml" />
	<link>http://e-CareManagement.com/were-building-a-really-big-health-internet/</link>
	<description>Chronic Disease Management • Technology • Strategy • Issues and Trends</description>
	<lastBuildDate>Wed, 10 Mar 2010 19:15:42 -0700</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Will Crawford</title>
		<link>http://e-CareManagement.com/were-building-a-really-big-health-internet/comment-page-1/#comment-12247</link>
		<dc:creator>Will Crawford</dc:creator>
		<pubDate>Wed, 07 Oct 2009 13:12:05 +0000</pubDate>
		<guid isPermaLink="false">http://e-CareManagement.com/?p=1227#comment-12247</guid>
		<description>A very good point. I saw someone point out yesterday that as far as Google Health is concerned, it&#039;s 3 down, 271 to go on the health plan side. And that doesn&#039;t even consider the transaction types. Getting a physician onto the Health Internet is a good thing. Getting them onto the Health Internet AND getting them to do eVisits through it is a good and useful thing.</description>
		<content:encoded><![CDATA[<p>A very good point. I saw someone point out yesterday that as far as Google Health is concerned, it&#8217;s 3 down, 271 to go on the health plan side. And that doesn&#8217;t even consider the transaction types. Getting a physician onto the Health Internet is a good thing. Getting them onto the Health Internet AND getting them to do eVisits through it is a good and useful thing.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Dynamic Page Served (once) in 0.353 seconds -->
