<?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 for The BAE Company</title>
	<atom:link href="http://www.thebaecompany.com/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.thebaecompany.com</link>
	<description>The BAE Company</description>
	<lastBuildDate>Fri, 17 Feb 2012 14:15:31 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>Comment on Megachange Requires a Mega-Goal: A Response to The Brookings Institution Report on &#8220;HIE and Megachange&#8221; by Edna Boone</title>
		<link>http://www.thebaecompany.com/2012/02/megachange-requires-a-mega-goal-edwards/#comment-21</link>
		<dc:creator>Edna Boone</dc:creator>
		<pubDate>Fri, 17 Feb 2012 14:15:31 +0000</pubDate>
		<guid isPermaLink="false">http://www.thebaecompany.com/?p=287#comment-21</guid>
		<description>With the consumerism of wellness via mobile devices, one should expect to see an increase in demand to share patient health information with providers, most likely skipping the tradional PHR models &amp;/or secure email.  This becomes a great opportunity for HIEs to embrace and engage their community members directly.</description>
		<content:encoded><![CDATA[<p>With the consumerism of wellness via mobile devices, one should expect to see an increase in demand to share patient health information with providers, most likely skipping the tradional PHR models &amp;/or secure email.  This becomes a great opportunity for HIEs to embrace and engage their community members directly.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Megachange Requires a Mega-Goal: A Response to The Brookings Institution Report on &#8220;HIE and Megachange&#8221; by pam matthews</title>
		<link>http://www.thebaecompany.com/2012/02/megachange-requires-a-mega-goal-edwards/#comment-20</link>
		<dc:creator>pam matthews</dc:creator>
		<pubDate>Fri, 17 Feb 2012 13:47:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.thebaecompany.com/?p=287#comment-20</guid>
		<description>Good report from Brookings - And Thank yous go out to the authors from reaching out to HIMSS for participating in the report effort</description>
		<content:encoded><![CDATA[<p>Good report from Brookings &#8211; And Thank yous go out to the authors from reaching out to HIMSS for participating in the report effort</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Blog by Megachange Requires a Mega-Goal: A Response to The Brookings Institution Report on &#8220;HIE and Megachange&#8221; &#124; The BAE Company</title>
		<link>http://www.thebaecompany.com/blog/#comment-16</link>
		<dc:creator>Megachange Requires a Mega-Goal: A Response to The Brookings Institution Report on &#8220;HIE and Megachange&#8221; &#124; The BAE Company</dc:creator>
		<pubDate>Mon, 13 Feb 2012 21:09:50 +0000</pubDate>
		<guid isPermaLink="false">http://bae.bbdg.net/?page_id=127#comment-16</guid>
		<description>[...] Blog [...]</description>
		<content:encoded><![CDATA[<p>[...] Blog [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Carladenise A. Edwards by Megachange Requires a Mega-Goal: A Response to The Brookings Institution Report on &#8220;HIE and Megachange&#8221; &#124; The BAE Company</title>
		<link>http://www.thebaecompany.com/about-us/carladenise-a-edwards/#comment-15</link>
		<dc:creator>Megachange Requires a Mega-Goal: A Response to The Brookings Institution Report on &#8220;HIE and Megachange&#8221; &#124; The BAE Company</dc:creator>
		<pubDate>Mon, 13 Feb 2012 20:51:36 +0000</pubDate>
		<guid isPermaLink="false">http://bae.bbdg.net/?page_id=76#comment-15</guid>
		<description>[...] Carladenise A. Edwards [...]</description>
		<content:encoded><![CDATA[<p>[...] Carladenise A. Edwards [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>

