<?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:itunes="http://www.itunes.com/dtds/podcast-1.0.dtd"
	xmlns:media="http://search.yahoo.com/mrss/"
	>
<channel>
	<title>Comments on: One-on-One w/KLAS Clinical GM Jason Hess (II)</title>
	<atom:link href="http://healthsystemcio.com/2010/02/12/one-on-one-wklas-clinical-research-gm-jason-hess-ii/feed/" rel="self" type="application/rss+xml" />
	<link>http://healthsystemcio.com/2010/02/12/one-on-one-wklas-clinical-research-gm-jason-hess-ii/</link>
	<description>healthsystemCIO.com is the sole online-only publication dedicated to exclusively and comprehensively serving the information needs of healthcare CIOs.</description>
	<lastBuildDate>Tue, 24 Apr 2012 00:55:00 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=112</generator>
<xhtml:meta xmlns:xhtml="http://www.w3.org/1999/xhtml" name="robots" content="noindex" />
	<item>
		<title>By: Winchester</title>
		<link>http://healthsystemcio.com/2010/02/12/one-on-one-wklas-clinical-research-gm-jason-hess-ii/#comment-164</link>
		<dc:creator>Winchester</dc:creator>
		<pubDate>Mon, 15 Feb 2010 20:55:00 +0000</pubDate>
		<guid isPermaLink="false">http://healthsystemcio.com/?p=1080#comment-164</guid>
		<description>Jason, thanks for your insights - looking forward to seeing your report.  In the meantime, can you or other readers comment on something that has confused me?  I&#039;ve long battled w. vendor interoperabilty issues (mostly around cost and vendor slowness), but actually not sure about how they differentiate on &quot;HIE friendliness&quot;... how do we measure this exactly?  Would seem that if they provide/ allow all neccessary HL7 transactions, HIE platforms can deal with the vendors and make the HIE work.  Do some simply not allow HL7 to be built for which HIEs call for?  Is it that they don&#039;t do CCRs, CDA&#039;s, etc?  Do some not play along with locator services?  I&#039;ve heard the critique that EPIC isn&#039;t fond of being interoperable with non-EPIC sites, and have seen interviews with EPIC saying that non-EPIC interfaces don&#039;t provide semantic interoperability (which I&#039;m guessing an HIE could make it work with additional programming) - but, isn&#039;t that the case with all disparate vendor interoperability scenarios?  - Looking forward to you guidance - thanks in advance...</description>
		<content:encoded><![CDATA[<p>Jason, thanks for your insights &#8211; looking forward to seeing your report.  In the meantime, can you or other readers comment on something that has confused me?  I&#8217;ve long battled w. vendor interoperabilty issues (mostly around cost and vendor slowness), but actually not sure about how they differentiate on &#8220;HIE friendliness&#8221;&#8230; how do we measure this exactly?  Would seem that if they provide/ allow all neccessary HL7 transactions, HIE platforms can deal with the vendors and make the HIE work.  Do some simply not allow HL7 to be built for which HIEs call for?  Is it that they don&#8217;t do CCRs, CDA&#8217;s, etc?  Do some not play along with locator services?  I&#8217;ve heard the critique that EPIC isn&#8217;t fond of being interoperable with non-EPIC sites, and have seen interviews with EPIC saying that non-EPIC interfaces don&#8217;t provide semantic interoperability (which I&#8217;m guessing an HIE could make it work with additional programming) &#8211; but, isn&#8217;t that the case with all disparate vendor interoperability scenarios?  &#8211; Looking forward to you guidance &#8211; thanks in advance&#8230;</p>
]]></content:encoded>
	</item>
</channel>
</rss>

