<?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/"
	xmlns:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments for </title>
	<atom:link href="http://blog.hieworks.com/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.hieworks.com</link>
	<description></description>
	<lastBuildDate>Thu, 01 Sep 2011 17:58:51 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.com/</generator>
	<item>
		<title>Comment on Thoughts on PCAST HealthIT Report by VC Independent</title>
		<link>http://blog.hieworks.com/2011/02/08/thoughts-on-pcast-healthit-report/#comment-205</link>
		<dc:creator><![CDATA[VC Independent]]></dc:creator>
		<pubDate>Thu, 01 Sep 2011 17:58:51 +0000</pubDate>
		<guid isPermaLink="false">http://blog.hieworks.com/?p=305#comment-205</guid>
		<description><![CDATA[very informative, keep posts like this coming.]]></description>
		<content:encoded><![CDATA[<p>very informative, keep posts like this coming.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on HIE Frameworks, Generating Real Value and &#8220;Clobber-ation&#8221; by HIE&#8217;s Real Missing Ingredient: Value &#171;</title>
		<link>http://blog.hieworks.com/2011/03/29/hie-frameworks-generating-real-value-and-clobber-ation/#comment-194</link>
		<dc:creator><![CDATA[HIE&#8217;s Real Missing Ingredient: Value &#171;]]></dc:creator>
		<pubDate>Tue, 31 May 2011 12:12:11 +0000</pubDate>
		<guid isPermaLink="false">http://blog.hieworks.com/?p=325#comment-194</guid>
		<description><![CDATA[[...] Much of the value I list is to the benefit of a single given provider. That&#8217;s fine&#8230; as you, our loyal HIEWorks blog reader knows by now, our approach is to fill the healthcare landscape with enterprise HIEs that are valuable and sustainable, reliable and secure. Then we weave the &#8220;private&#8221; enterprise HIEs together into a public exchange fabric with technologies like NwHIN and the Direct Project: fed by the rocket fuel of competition before the fruits of cooperation. I&#8217;ll avoid digressing by referring you to our other posts, including this one that contrasts public and private HIE viability. [...]]]></description>
		<content:encoded><![CDATA[<p>[...] Much of the value I list is to the benefit of a single given provider. That&#8217;s fine&#8230; as you, our loyal HIEWorks blog reader knows by now, our approach is to fill the healthcare landscape with enterprise HIEs that are valuable and sustainable, reliable and secure. Then we weave the &#8220;private&#8221; enterprise HIEs together into a public exchange fabric with technologies like NwHIN and the Direct Project: fed by the rocket fuel of competition before the fruits of cooperation. I&#8217;ll avoid digressing by referring you to our other posts, including this one that contrasts public and private HIE viability. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Regional Extension Centers vs. the Competition by vswamy</title>
		<link>http://blog.hieworks.com/2010/07/06/regional-extension-centers-vs-the-competition/#comment-101</link>
		<dc:creator><![CDATA[vswamy]]></dc:creator>
		<pubDate>Tue, 27 Jul 2010 01:38:38 +0000</pubDate>
		<guid isPermaLink="false">http://blog.hieworks.com/?p=281#comment-101</guid>
		<description><![CDATA[I think the introduction of REC’s through the &lt;a href=&quot;http://www.waitingroomsolutions.com/wrs/regional-extension-centers-arra-rec&quot; rel=&quot;nofollow&quot;&gt;HITECH act.&lt;/a&gt; is a great way to avail of quality EHR solutions at competitive prices. The stiff competition among not only these REC’s but also among EHR vendors ( to become a preferred vendor of a given REC) will result in lot of positives to medical practioners.
Looking the funding provided to the REC’s, the &lt;a href=&quot;http://www.waitingroomsolutions.com/wrs/regional-extension-center-health-it&quot; rel=&quot;nofollow&quot;&gt;staggered grant allocation system&lt;/a&gt; also promises to be an unbiased way of allocating funds. It will also help in the concept of REC’s helping out each with their own unique business models. It can be one of the possible answers to the &#039;safe EHR vendor&#039; challenge as discussed by many critics.


As far as implementation challenges goes, the &lt;a href=&quot;http://www.waitingroomsolutions.com/wrs/certification-criteria-electronic-health-records-ARRA-Certification-Requirements-Health-Record-Certification&quot; rel=&quot;nofollow&quot;&gt;federal guidelines for certification&lt;/a&gt; and usability are pretty much clear. Useful improvisation on these lines can make ones EHR&#039;s friendly to most practices of varying specialties.]]></description>
		<content:encoded><![CDATA[<p>I think the introduction of REC’s through the <a href="http://www.waitingroomsolutions.com/wrs/regional-extension-centers-arra-rec" rel="nofollow">HITECH act.</a> is a great way to avail of quality EHR solutions at competitive prices. The stiff competition among not only these REC’s but also among EHR vendors ( to become a preferred vendor of a given REC) will result in lot of positives to medical practioners.<br />
Looking the funding provided to the REC’s, the <a href="http://www.waitingroomsolutions.com/wrs/regional-extension-center-health-it" rel="nofollow">staggered grant allocation system</a> also promises to be an unbiased way of allocating funds. It will also help in the concept of REC’s helping out each with their own unique business models. It can be one of the possible answers to the &#8216;safe EHR vendor&#8217; challenge as discussed by many critics.</p>
<p>As far as implementation challenges goes, the <a href="http://www.waitingroomsolutions.com/wrs/certification-criteria-electronic-health-records-ARRA-Certification-Requirements-Health-Record-Certification" rel="nofollow">federal guidelines for certification</a> and usability are pretty much clear. Useful improvisation on these lines can make ones EHR&#8217;s friendly to most practices of varying specialties.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Are State-based HIEs Good for Healthcare? by Todd Fisher</title>
		<link>http://blog.hieworks.com/2010/06/09/are-state-based-hies-good-for-healthcare/#comment-68</link>
		<dc:creator><![CDATA[Todd Fisher]]></dc:creator>
		<pubDate>Mon, 21 Jun 2010 21:46:02 +0000</pubDate>
		<guid isPermaLink="false">http://blog.hieworks.com/?p=268#comment-68</guid>
		<description><![CDATA[John, thank you for the thoughtful comment.  I don&#039;t believe we divurge as much as it may at first appear.  I agree; cross-institution/state/region agreements and standards must be in place.  Moreover, I completely support the various NHIN initiatives, as that is the backbone of how all this will play out, in my mind. State and other government entities implementing regulatory requirements regarding data sharing, security, consent and use, to me, however, is a far cry from actually specifying, purchasing and selling/offering technology used to support healthcare.  I guess an analogy might be financial services or the oil industry.  I agree that strict regulations instituted and audited by the government must be in place to protect the consumer and tangential industries.  I don&#039;t, however, believe specific technologies should be purchased by the government and offered to private organizations for use to ensure regulatory compliance.   Doing so mutes competitive advantage and mitigates the desire to cut costs and improve care.  Unfortunately, in a government operated environment, doing so is left to altruism and not competition.  The government will have established the lowest common denominator, for lack of a better term.  Based on the philosophy of minimalism, folks will do the minimum necessary to accomplish what they need to accomplish, whether that be cost savings, patient consent, or health information security.]]></description>
		<content:encoded><![CDATA[<p>John, thank you for the thoughtful comment.  I don&#8217;t believe we divurge as much as it may at first appear.  I agree; cross-institution/state/region agreements and standards must be in place.  Moreover, I completely support the various NHIN initiatives, as that is the backbone of how all this will play out, in my mind. State and other government entities implementing regulatory requirements regarding data sharing, security, consent and use, to me, however, is a far cry from actually specifying, purchasing and selling/offering technology used to support healthcare.  I guess an analogy might be financial services or the oil industry.  I agree that strict regulations instituted and audited by the government must be in place to protect the consumer and tangential industries.  I don&#8217;t, however, believe specific technologies should be purchased by the government and offered to private organizations for use to ensure regulatory compliance.   Doing so mutes competitive advantage and mitigates the desire to cut costs and improve care.  Unfortunately, in a government operated environment, doing so is left to altruism and not competition.  The government will have established the lowest common denominator, for lack of a better term.  Based on the philosophy of minimalism, folks will do the minimum necessary to accomplish what they need to accomplish, whether that be cost savings, patient consent, or health information security.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Are State-based HIEs Good for Healthcare? by John</title>
		<link>http://blog.hieworks.com/2010/06/09/are-state-based-hies-good-for-healthcare/#comment-67</link>
		<dc:creator><![CDATA[John]]></dc:creator>
		<pubDate>Mon, 21 Jun 2010 20:59:52 +0000</pubDate>
		<guid isPermaLink="false">http://blog.hieworks.com/?p=268#comment-67</guid>
		<description><![CDATA[Good post Todd and for most part I agree with your overall premise, especially that heavy-handed, top-down govt strategies for HIEs are likely to falter.  

Where we diverge is on the issue of the &quot;DURSA&quot; and how does one institute a statewide, if not a multi-state DURSA that all can live by and support.  It takes more than just the technical requirements of asking a given healthcare system to have the open technology links to share data, there also needs to be a policy framework in place to share that data securely, preserve provenance, manage consent and minimize liability concerns.]]></description>
		<content:encoded><![CDATA[<p>Good post Todd and for most part I agree with your overall premise, especially that heavy-handed, top-down govt strategies for HIEs are likely to falter.  </p>
<p>Where we diverge is on the issue of the &#8220;DURSA&#8221; and how does one institute a statewide, if not a multi-state DURSA that all can live by and support.  It takes more than just the technical requirements of asking a given healthcare system to have the open technology links to share data, there also needs to be a policy framework in place to share that data securely, preserve provenance, manage consent and minimize liability concerns.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on What’s Your HIE’s IQ by Chuck Buck</title>
		<link>http://blog.hieworks.com/2010/05/06/what%e2%80%99s-your-hie%e2%80%99s-iq/#comment-40</link>
		<dc:creator><![CDATA[Chuck Buck]]></dc:creator>
		<pubDate>Thu, 06 May 2010 12:29:20 +0000</pubDate>
		<guid isPermaLink="false">http://blog.hieworks.com/?p=258#comment-40</guid>
		<description><![CDATA[Best post to-date.]]></description>
		<content:encoded><![CDATA[<p>Best post to-date.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on HIE in 4D by All Roads Lead to HIE &#171;</title>
		<link>http://blog.hieworks.com/2010/04/15/hie-in-4d/#comment-36</link>
		<dc:creator><![CDATA[All Roads Lead to HIE &#171;]]></dc:creator>
		<pubDate>Tue, 27 Apr 2010 12:06:19 +0000</pubDate>
		<guid isPermaLink="false">http://blog.hieworks.com/?p=231#comment-36</guid>
		<description><![CDATA[[...] can weave together these Enterprise networks (say, using the NHIN specifications). Done properly, which requires all four dimensions of HIE, you can get to the community-wide, holistic solution faster than ”waiting for Godot” – [...]]]></description>
		<content:encoded><![CDATA[<p>[...] can weave together these Enterprise networks (say, using the NHIN specifications). Done properly, which requires all four dimensions of HIE, you can get to the community-wide, holistic solution faster than ”waiting for Godot” – [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on HIE in 4D by Chuck Buck</title>
		<link>http://blog.hieworks.com/2010/04/15/hie-in-4d/#comment-29</link>
		<dc:creator><![CDATA[Chuck Buck]]></dc:creator>
		<pubDate>Thu, 15 Apr 2010 13:22:31 +0000</pubDate>
		<guid isPermaLink="false">http://blog.hieworks.com/?p=231#comment-29</guid>
		<description><![CDATA[Refreshing perspective. Thanks.]]></description>
		<content:encoded><![CDATA[<p>Refreshing perspective. Thanks.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on HIE &#8220;Tipping Point&#8221; by HIE in 4D &#171;</title>
		<link>http://blog.hieworks.com/2010/03/22/hie-tipping-point-3/#comment-28</link>
		<dc:creator><![CDATA[HIE in 4D &#171;]]></dc:creator>
		<pubDate>Thu, 15 Apr 2010 10:54:16 +0000</pubDate>
		<guid isPermaLink="false">http://blog.hieworks.com/?p=200#comment-28</guid>
		<description><![CDATA[[...] themselves.  Competition, therefore, must precede cooperation.  As the market matures, however, cooperation inevitably evolves. Consumers lean heavily against healthcare’s regional nature, forcing providers to cooperate to [...]]]></description>
		<content:encoded><![CDATA[<p>[...] themselves.  Competition, therefore, must precede cooperation.  As the market matures, however, cooperation inevitably evolves. Consumers lean heavily against healthcare’s regional nature, forcing providers to cooperate to [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Inter-system/Community Exchanges Lack Sustainability by HIE in 4D &#171;</title>
		<link>http://blog.hieworks.com/2010/02/04/inter-systemcommunity-exchanges-lack-sustainability/#comment-27</link>
		<dc:creator><![CDATA[HIE in 4D &#171;]]></dc:creator>
		<pubDate>Thu, 15 Apr 2010 10:54:12 +0000</pubDate>
		<guid isPermaLink="false">http://blog.hieworks.com/?p=129#comment-27</guid>
		<description><![CDATA[[...] Economic dimension is best viewed as time.  I’ve previously written that an economic model based on self-interest’s “invisible hand” is important to ensure sustainability.  While some cooperative models have succeeded, they are, unfortunately, the exception:  those [...]]]></description>
		<content:encoded><![CDATA[<p>[...] Economic dimension is best viewed as time.  I’ve previously written that an economic model based on self-interest’s “invisible hand” is important to ensure sustainability.  While some cooperative models have succeeded, they are, unfortunately, the exception:  those [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>

