<?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: Bill Stead on the National Research Council&#8217;s Report</title>
	<atom:link href="http://histalk2.com/2009/01/12/bill-stead-on-the-national-research-councils-report/feed/" rel="self" type="application/rss+xml" />
	<link>http://histalk2.com/2009/01/12/bill-stead-on-the-national-research-councils-report/</link>
	<description>Healthcare IT News and Opinion</description>
	<lastBuildDate>Fri, 12 Mar 2010 21:24:30 -0500</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Ignacio Valdes</title>
		<link>http://histalk2.com/2009/01/12/bill-stead-on-the-national-research-councils-report/comment-page-1/#comment-3661</link>
		<dc:creator>Ignacio Valdes</dc:creator>
		<pubDate>Wed, 11 Mar 2009 16:31:41 +0000</pubDate>
		<guid isPermaLink="false">http://histalk2.com/2009/01/12/bill-stead-on-the-national-research-councils-report/#comment-3661</guid>
		<description>I agree with your conclusions. There is far more at stake than what you state which I&#039;ve discussed here: http://linuxmednews.com/1236661936/index_html The thing missing is a mechanism for the flexibility you describe. The government appears poised to double down on allowing federal funds to pay for proprietary EMR black box software, greatly reducing the needed flexibility and field serviceability that you describe. It is a throwback to alchemy in which techniques were kept secret for turning lead into gold in order to corner the market. The side effect was that everyone had to discover on their own that mercury is poisonous. I have called for a law allowing federal purchasing funds to only be used for Affero General Public Licensed software. So far I am meeting much resistance but it is the only way that such flexibility and performance can be assured. -- IV</description>
		<content:encoded><![CDATA[<p>I agree with your conclusions. There is far more at stake than what you state which I&#8217;ve discussed here: <a href="http://linuxmednews.com/1236661936/index_html" rel="nofollow">http://linuxmednews.com/1236661936/index_html</a> The thing missing is a mechanism for the flexibility you describe. The government appears poised to double down on allowing federal funds to pay for proprietary EMR black box software, greatly reducing the needed flexibility and field serviceability that you describe. It is a throwback to alchemy in which techniques were kept secret for turning lead into gold in order to corner the market. The side effect was that everyone had to discover on their own that mercury is poisonous. I have called for a law allowing federal purchasing funds to only be used for Affero General Public Licensed software. So far I am meeting much resistance but it is the only way that such flexibility and performance can be assured. &#8212; IV</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Just Silly</title>
		<link>http://histalk2.com/2009/01/12/bill-stead-on-the-national-research-councils-report/comment-page-1/#comment-3042</link>
		<dc:creator>Just Silly</dc:creator>
		<pubDate>Wed, 14 Jan 2009 06:12:52 +0000</pubDate>
		<guid isPermaLink="false">http://histalk2.com/2009/01/12/bill-stead-on-the-national-research-councils-report/#comment-3042</guid>
		<description>Bill is just rationalizing his history.  10 years to implement?  Maybe at Vandy, if you try to build it on your own from scratch.  Not in most of the rest of the free world though.   Bash vendors all you want Bill, but don&#039;t project your failures on an entire industry.</description>
		<content:encoded><![CDATA[<p>Bill is just rationalizing his history.  10 years to implement?  Maybe at Vandy, if you try to build it on your own from scratch.  Not in most of the rest of the free world though.   Bash vendors all you want Bill, but don&#8217;t project your failures on an entire industry.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: John Haughton MD, MS</title>
		<link>http://histalk2.com/2009/01/12/bill-stead-on-the-national-research-councils-report/comment-page-1/#comment-3032</link>
		<dc:creator>John Haughton MD, MS</dc:creator>
		<pubDate>Tue, 13 Jan 2009 03:54:53 +0000</pubDate>
		<guid isPermaLink="false">http://histalk2.com/2009/01/12/bill-stead-on-the-national-research-councils-report/#comment-3032</guid>
		<description>Great report.

Looks as if it might explain alot - for example, have physicians been reluctant purchasers or Saavy consumers - Looks like Physicians are Saavy consumers holding on buying expensive EMR systems with little proof of efficacy.

Simple programs, designed to improve care work.  It&#039;s possible to spend less than $100 / month / physician and improve metrics of care from 40% to 80% within a three or four month period.

The secret is the right information in the point of care workflow; performance monitoring and safety-net lists of patients falling through the cracks - in other words, communication and knowledge within workflow - whether a paper or electornic office.

Congrats to the NRC team for a terrific report highlighting the emperor&#039;s clothes in the HIT world.   Hopefully application of the economic stimulus funds from the federal government will follow the path illuminated by the NRC report.

John Haughton MD, MS
DocSite</description>
		<content:encoded><![CDATA[<p>Great report.</p>
<p>Looks as if it might explain alot &#8211; for example, have physicians been reluctant purchasers or Saavy consumers &#8211; Looks like Physicians are Saavy consumers holding on buying expensive EMR systems with little proof of efficacy.</p>
<p>Simple programs, designed to improve care work.  It&#8217;s possible to spend less than $100 / month / physician and improve metrics of care from 40% to 80% within a three or four month period.</p>
<p>The secret is the right information in the point of care workflow; performance monitoring and safety-net lists of patients falling through the cracks &#8211; in other words, communication and knowledge within workflow &#8211; whether a paper or electornic office.</p>
<p>Congrats to the NRC team for a terrific report highlighting the emperor&#8217;s clothes in the HIT world.   Hopefully application of the economic stimulus funds from the federal government will follow the path illuminated by the NRC report.</p>
<p>John Haughton MD, MS<br />
DocSite</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Frank POggio</title>
		<link>http://histalk2.com/2009/01/12/bill-stead-on-the-national-research-councils-report/comment-page-1/#comment-3030</link>
		<dc:creator>Frank POggio</dc:creator>
		<pubDate>Mon, 12 Jan 2009 22:36:04 +0000</pubDate>
		<guid isPermaLink="false">http://histalk2.com/2009/01/12/bill-stead-on-the-national-research-councils-report/#comment-3030</guid>
		<description>I am not surprised to see the results of the IOM study. I could not agree with them more.
I have been in the health care IT profession for over thirty years and although progress has been made over those years, IT in healthcare is still viewed as a transaction /data system, not an intelligent system to support clinical or administrative workflow. For forty years we have invested  billions of dollars in capturing, storing, aggregating and reporting transactional data. We, as an industry are data rich, and information poor.
 
So why is it that way? Why don&#039;t we have more ‘smart’ process oriented tools /systems instead of an oceans of data on incomprehensible reports? Here’s my assessment:
 
1)      It is significantly less for a for a vendor to build data transaction systems, than process support systems. They could burn through billions of dollars building a real process oriented system and never see a ROI.
2)      Building data systems that can support and improve clinical or administrative processes is very complex and very time consuming.
3)      Process systems and clinical protocols can vary significantly from facility to facility. Whether that is good or bad is separate debate, but that is the way it is still today.
4)      Clinical protocols are dynamic, medicine is not a stagnant science, and what we don&#039;t know can fill the universe. We learn something new every day, and we adapt it by changing the protocol. So an automated process system would have to change with it ­ ...over and over.
 
Some of these same challenges exist outside of healthcare in other industries. Many sophisticated tools have been developed to address process variability. We should look at applying as many as we can. It’s time we started doing something with all that ‘data’.   

Frank Poggio
President
The Kelzon Group
Barrington, IL</description>
		<content:encoded><![CDATA[<p>I am not surprised to see the results of the IOM study. I could not agree with them more.<br />
I have been in the health care IT profession for over thirty years and although progress has been made over those years, IT in healthcare is still viewed as a transaction /data system, not an intelligent system to support clinical or administrative workflow. For forty years we have invested  billions of dollars in capturing, storing, aggregating and reporting transactional data. We, as an industry are data rich, and information poor.</p>
<p>So why is it that way? Why don&#8217;t we have more ‘smart’ process oriented tools /systems instead of an oceans of data on incomprehensible reports? Here’s my assessment:</p>
<p>1)      It is significantly less for a for a vendor to build data transaction systems, than process support systems. They could burn through billions of dollars building a real process oriented system and never see a ROI.<br />
2)      Building data systems that can support and improve clinical or administrative processes is very complex and very time consuming.<br />
3)      Process systems and clinical protocols can vary significantly from facility to facility. Whether that is good or bad is separate debate, but that is the way it is still today.<br />
4)      Clinical protocols are dynamic, medicine is not a stagnant science, and what we don&#8217;t know can fill the universe. We learn something new every day, and we adapt it by changing the protocol. So an automated process system would have to change with it ­ &#8230;over and over.</p>
<p>Some of these same challenges exist outside of healthcare in other industries. Many sophisticated tools have been developed to address process variability. We should look at applying as many as we can. It’s time we started doing something with all that ‘data’.   </p>
<p>Frank Poggio<br />
President<br />
The Kelzon Group<br />
Barrington, IL</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: robert galin</title>
		<link>http://histalk2.com/2009/01/12/bill-stead-on-the-national-research-councils-report/comment-page-1/#comment-3026</link>
		<dc:creator>robert galin</dc:creator>
		<pubDate>Mon, 12 Jan 2009 18:33:45 +0000</pubDate>
		<guid isPermaLink="false">http://histalk2.com/2009/01/12/bill-stead-on-the-national-research-councils-report/#comment-3026</guid>
		<description>I suggest the committee take a close look at the NHS in the UK, and the minimal success achieved there. There is much to learn from their experience.</description>
		<content:encoded><![CDATA[<p>I suggest the committee take a close look at the NHS in the UK, and the minimal success achieved there. There is much to learn from their experience.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
