<?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 on: How can EHR be made to work?</title>
	<atom:link href="http://healthcareitstrategy.com/2009/09/27/how-can-ehr-be-made-to-work/feed/" rel="self" type="application/rss+xml" />
	<link>http://healthcareitstrategy.com/2009/09/27/how-can-ehr-be-made-to-work/</link>
	<description></description>
	<lastBuildDate>Wed, 29 Feb 2012 17:31:20 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.com/</generator>
	<item>
		<title>By: Why I differ with Mr. Halamka&#8217;s EHR strategy &#171; EHR: How difficult is it without the correct strategy?</title>
		<link>http://healthcareitstrategy.com/2009/09/27/how-can-ehr-be-made-to-work/#comment-147</link>
		<dc:creator><![CDATA[Why I differ with Mr. Halamka&#8217;s EHR strategy &#171; EHR: How difficult is it without the correct strategy?]]></dc:creator>
		<pubDate>Thu, 01 Oct 2009 17:20:04 +0000</pubDate>
		<guid isPermaLink="false">http://healthcareitstrategy.com/?p=891#comment-147</guid>
		<description><![CDATA[[...] comments HealthBlawg on How can EHR be made to&#160;wo&#8230;Paul Roemer on What should be the role of the&#8230;Paul Roemer on When you&#8217;re in a hole, [...]]]></description>
		<content:encoded><![CDATA[<p>[...] comments HealthBlawg on How can EHR be made to&nbsp;wo&hellip;Paul Roemer on What should be the role of the&hellip;Paul Roemer on When you&#8217;re in a hole, [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: HealthBlawg</title>
		<link>http://healthcareitstrategy.com/2009/09/27/how-can-ehr-be-made-to-work/#comment-146</link>
		<dc:creator><![CDATA[HealthBlawg]]></dc:creator>
		<pubDate>Wed, 30 Sep 2009 15:01:56 +0000</pubDate>
		<guid isPermaLink="false">http://healthcareitstrategy.com/?p=891#comment-146</guid>
		<description><![CDATA[&lt;strong&gt;Whither meaningful use of the certified, interoperable EHR?...&lt;/strong&gt;

Paul Roemer asks: Have you ever been a part of a successful launch of a national IT system that: required a hundred thousand or so implementations of a parochial system? has been designed by 400 vendors? had 400 applications based......]]></description>
		<content:encoded><![CDATA[<p><strong>Whither meaningful use of the certified, interoperable EHR?&#8230;</strong></p>
<p>Paul Roemer asks: Have you ever been a part of a successful launch of a national IT system that: required a hundred thousand or so implementations of a parochial system? has been designed by 400 vendors? had 400 applications based&#8230;&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Scott Nicol</title>
		<link>http://healthcareitstrategy.com/2009/09/27/how-can-ehr-be-made-to-work/#comment-138</link>
		<dc:creator><![CDATA[Scott Nicol]]></dc:creator>
		<pubDate>Sun, 27 Sep 2009 22:53:52 +0000</pubDate>
		<guid isPermaLink="false">http://healthcareitstrategy.com/?p=891#comment-138</guid>
		<description><![CDATA[Have you ever been a part of a successful launch of a national IT system that:   
    * required a hundred thousand or so implementations of a parochial system
    * has been designed by 400 vendors
    * has 400 applications based on their own standards
    * has to transport different versions of health records in and out of hundreds of different regional health information networks
    * has to be interoperable
    * may result in someone’s death if it fails


Yikes, I’m almost tempted to inquire about that ad in the back of Popular Science on Locksmithing, but I do like a challenge.

Kinda brings it all home. I&#039;m wondering what the folks at NextGen and Greenway are telling their clients when it comes to the upload part of all this. Am I buying the capability as they envision it today or as it *will be* at some future set of temporal coordinates. Perhaps that&#039;s part of the wonderful 20% service contract.

Probably the best example of what works today in healthcare is the various registries. These proprietary systems all have one thing in common; they accept a single data set in a very rigid format. If you want to play, it has to be by their rules. If your data is hosed up, it gets bounced. There are tools that help you scrub it before the upload, so rejection is rare. Of course this is all batch-based, and an EMR to EHR transfer should be more of a real-time single record arrangement – but other than that it’s quite similar.

As far as examples of a good transport system, I think you must turn to a Google or some other entity that can handle mass transactions with low risk of failure. The Automated Clearing House (ACH) is an electronic network for financial transactions in the United States. This system moves more than 10 billion transactions per year – albeit in batch. But if you look at the proprietary sub systems like the ATM networks, thy work very well and appears to be real-time, otherwise you could take a trip around town to 10 different ATM’s and clean out your account a few times over. I’ve never had a bogus transaction via ATM in more than 25 years. Credit cards are another story of course.

Yes it can be done well and at a reasonable cost, but rigid standards and simplicity in the design of the transport and storage architecture must be at the top of the priority list.]]></description>
		<content:encoded><![CDATA[<p>Have you ever been a part of a successful launch of a national IT system that:<br />
    * required a hundred thousand or so implementations of a parochial system<br />
    * has been designed by 400 vendors<br />
    * has 400 applications based on their own standards<br />
    * has to transport different versions of health records in and out of hundreds of different regional health information networks<br />
    * has to be interoperable<br />
    * may result in someone’s death if it fails</p>
<p>Yikes, I’m almost tempted to inquire about that ad in the back of Popular Science on Locksmithing, but I do like a challenge.</p>
<p>Kinda brings it all home. I&#8217;m wondering what the folks at NextGen and Greenway are telling their clients when it comes to the upload part of all this. Am I buying the capability as they envision it today or as it *will be* at some future set of temporal coordinates. Perhaps that&#8217;s part of the wonderful 20% service contract.</p>
<p>Probably the best example of what works today in healthcare is the various registries. These proprietary systems all have one thing in common; they accept a single data set in a very rigid format. If you want to play, it has to be by their rules. If your data is hosed up, it gets bounced. There are tools that help you scrub it before the upload, so rejection is rare. Of course this is all batch-based, and an EMR to EHR transfer should be more of a real-time single record arrangement – but other than that it’s quite similar.</p>
<p>As far as examples of a good transport system, I think you must turn to a Google or some other entity that can handle mass transactions with low risk of failure. The Automated Clearing House (ACH) is an electronic network for financial transactions in the United States. This system moves more than 10 billion transactions per year – albeit in batch. But if you look at the proprietary sub systems like the ATM networks, thy work very well and appears to be real-time, otherwise you could take a trip around town to 10 different ATM’s and clean out your account a few times over. I’ve never had a bogus transaction via ATM in more than 25 years. Credit cards are another story of course.</p>
<p>Yes it can be done well and at a reasonable cost, but rigid standards and simplicity in the design of the transport and storage architecture must be at the top of the priority list.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: squarie</title>
		<link>http://healthcareitstrategy.com/2009/09/27/how-can-ehr-be-made-to-work/#comment-137</link>
		<dc:creator><![CDATA[squarie]]></dc:creator>
		<pubDate>Sun, 27 Sep 2009 20:49:42 +0000</pubDate>
		<guid isPermaLink="false">http://healthcareitstrategy.com/?p=891#comment-137</guid>
		<description><![CDATA[my 2 cents
Phased approach
Start with the data points which are available in existing data streams (ie HL7)** yes here someone will have to decide on the format. we know each facility is a &quot;snowflake&quot; but the data will have to be standardized in/out of the PTP nw
Feed a peer-to-peer network which is searchable based on several layers of matching criteria (exact and fuzzy)
Authentication and logging is handled within each facility with proper audit measures in place. 
What&#039;s next? Ideally something like medication or radiology reports, not sure which would be easier!
labs data
cardiology waveforms
other stuff i know nothing about!
free-text narratives.

I&#039;m not sure a nationwide repository is necessary,it would be a duplication of data. Perhaps it would open a business model for EHR backup services.
yup, still lots of unanswered questions.]]></description>
		<content:encoded><![CDATA[<p>my 2 cents<br />
Phased approach<br />
Start with the data points which are available in existing data streams (ie HL7)** yes here someone will have to decide on the format. we know each facility is a &#8220;snowflake&#8221; but the data will have to be standardized in/out of the PTP nw<br />
Feed a peer-to-peer network which is searchable based on several layers of matching criteria (exact and fuzzy)<br />
Authentication and logging is handled within each facility with proper audit measures in place.<br />
What&#8217;s next? Ideally something like medication or radiology reports, not sure which would be easier!<br />
labs data<br />
cardiology waveforms<br />
other stuff i know nothing about!<br />
free-text narratives.</p>
<p>I&#8217;m not sure a nationwide repository is necessary,it would be a duplication of data. Perhaps it would open a business model for EHR backup services.<br />
yup, still lots of unanswered questions.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

