<?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: HIStalk Interviews Ross Koppel</title>
	<atom:link href="http://histalk2.com/2009/08/12/histalk-interviews-ross-koppel/feed/" rel="self" type="application/rss+xml" />
	<link>http://histalk2.com/2009/08/12/histalk-interviews-ross-koppel/</link>
	<description>Healthcare IT News and Opinion</description>
	<lastBuildDate>Thu, 18 Mar 2010 00:28:59 -0500</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Dr. Zhivago</title>
		<link>http://histalk2.com/2009/08/12/histalk-interviews-ross-koppel/comment-page-1/#comment-5124</link>
		<dc:creator>Dr. Zhivago</dc:creator>
		<pubDate>Fri, 14 Aug 2009 04:21:32 +0000</pubDate>
		<guid isPermaLink="false">http://histalk2.com/2009/08/12/histalk-interviews-ross-koppel/#comment-5124</guid>
		<description>Both the Joint Commission and the FDA has failed to protect defenseless patients from the dangers of these products. 

Based on the comments of Dr. Koppel and others (including the excellent comments on this blog), there is dire need for these defacto medical devices (CPOE and others) to undergo methodological evaluation for safety and efficacy by the FDA.

The output of the meeting of 13 years ago, mentioned by Dr, Koppel,  established a self serving self-regulatory algorithm for HIT vendors&#039; products.  The proposed program and its algorithm gets an &quot;F&quot; in each of the 13 years since it was published.

Each site currently utilizing CPOE devices should be declared an in situ experimental site by the FDA.  Data collection on intrinsic device flaws, ergonomic flaws, adverse events, work arounds, vendor conduct, delays in care, and others should begin immediately.  

There ought to be a link to the FDA on each CPOE terminal to facilitate the reporting of the errors and defects.

If CPOE devices fail, the risks to the patient are formidable, putting these devices in FDA Class 3. Thus, the rigors of pre-market approval protocols are indicated.

Ultimately, this will be good for the patients, the health care professionals using the devices, and the industry itself. 

Perhaps Commissioner Hamburg and the new director of FDA&#039;s CDRH will  come to this understanding.  ZZ</description>
		<content:encoded><![CDATA[<p>Both the Joint Commission and the FDA has failed to protect defenseless patients from the dangers of these products. </p>
<p>Based on the comments of Dr. Koppel and others (including the excellent comments on this blog), there is dire need for these defacto medical devices (CPOE and others) to undergo methodological evaluation for safety and efficacy by the FDA.</p>
<p>The output of the meeting of 13 years ago, mentioned by Dr, Koppel,  established a self serving self-regulatory algorithm for HIT vendors&#8217; products.  The proposed program and its algorithm gets an &#8220;F&#8221; in each of the 13 years since it was published.</p>
<p>Each site currently utilizing CPOE devices should be declared an in situ experimental site by the FDA.  Data collection on intrinsic device flaws, ergonomic flaws, adverse events, work arounds, vendor conduct, delays in care, and others should begin immediately.  </p>
<p>There ought to be a link to the FDA on each CPOE terminal to facilitate the reporting of the errors and defects.</p>
<p>If CPOE devices fail, the risks to the patient are formidable, putting these devices in FDA Class 3. Thus, the rigors of pre-market approval protocols are indicated.</p>
<p>Ultimately, this will be good for the patients, the health care professionals using the devices, and the industry itself. </p>
<p>Perhaps Commissioner Hamburg and the new director of FDA&#8217;s CDRH will  come to this understanding.  ZZ</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: anon</title>
		<link>http://histalk2.com/2009/08/12/histalk-interviews-ross-koppel/comment-page-1/#comment-5121</link>
		<dc:creator>anon</dc:creator>
		<pubDate>Fri, 14 Aug 2009 01:31:20 +0000</pubDate>
		<guid isPermaLink="false">http://histalk2.com/2009/08/12/histalk-interviews-ross-koppel/#comment-5121</guid>
		<description>&quot;Russ’s article required reading for my clients. Recently read Steve’s great work.&quot;

Think you mean Ross and Scott?</description>
		<content:encoded><![CDATA[<p>&#8220;Russ’s article required reading for my clients. Recently read Steve’s great work.&#8221;</p>
<p>Think you mean Ross and Scott?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Justen</title>
		<link>http://histalk2.com/2009/08/12/histalk-interviews-ross-koppel/comment-page-1/#comment-5120</link>
		<dc:creator>Justen</dc:creator>
		<pubDate>Fri, 14 Aug 2009 01:27:39 +0000</pubDate>
		<guid isPermaLink="false">http://histalk2.com/2009/08/12/histalk-interviews-ross-koppel/#comment-5120</guid>
		<description>This needs to be reprinted, verbatim, as Chapter 1 of An Introduction to the Healthcare Information Systems and Technology Industry, 2009 Edition...</description>
		<content:encoded><![CDATA[<p>This needs to be reprinted, verbatim, as Chapter 1 of An Introduction to the Healthcare Information Systems and Technology Industry, 2009 Edition&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ann Farrell</title>
		<link>http://histalk2.com/2009/08/12/histalk-interviews-ross-koppel/comment-page-1/#comment-5119</link>
		<dc:creator>Ann Farrell</dc:creator>
		<pubDate>Fri, 14 Aug 2009 00:32:03 +0000</pubDate>
		<guid isPermaLink="false">http://histalk2.com/2009/08/12/histalk-interviews-ross-koppel/#comment-5119</guid>
		<description>Kudos to Drs Koppel and Silverstein. Russ&#039;s article required reading for my clients.  Recently read Steve&#039;s great work.  

I&#039;ve been vocal re potential harm in EMRs.  I and others have reported to senior execs &quot;glitches&quot; in systems that pose clear danger of harm.  I saw TDS execs (system studied) respond ethically when errors found, regardless of finanicial impact. This hasn&#039;t been the case since with vendors response most often &quot;shooting the messenger&quot;.
 
While beauracracy could paralyze us, it&#039;s fightening no regulatory agency sits between some profit driven (apparently soul-less) vendors and hospitals.  Some hospitals simply resource strapped and non-software savvy - staff assume no vendor would knowingly ship dangerous code.  

With EMR/CDSS and non-FDA regulated medical device middeware, IT drives life-critical data and processes, with push in some cases to eliminate or marginalize the clinician.  A  Risk is enormous and worsens as we outsource, patch old systems and skimp on analysis, design and QA (cost saving).  Glitches are invisible to buyers.  

Many vendor and hospital staff expected to meet unrealistic deadlines driven in public companies by quarterly performance demands.  ARRA (incentives and timelines) and economy (need for those with jobs to retain them and companies to continue to produce &quot;numbers&quot;) add to perfect storm for errors and misuse of IT.  The HCIT industry works on &quot;honor system&quot;. Clinicians who raise issues have short careers.  

I&#039;ve documented and presented concerns, had reached out to implore HIMSS and Gartner execs to take leadership role in raising awareness with vendor client members&#039; CEOs/execs - not knowing who else might wield influence at this level.  No response.  

Who can/will advocate for clinicians and patients with corporate interests driving healthcare and HCIT? 

Russ, you are my hero! Tim, keep em coming!  Will be hard to top this interview.  Timely to have these discussions!</description>
		<content:encoded><![CDATA[<p>Kudos to Drs Koppel and Silverstein. Russ&#8217;s article required reading for my clients.  Recently read Steve&#8217;s great work.  </p>
<p>I&#8217;ve been vocal re potential harm in EMRs.  I and others have reported to senior execs &#8220;glitches&#8221; in systems that pose clear danger of harm.  I saw TDS execs (system studied) respond ethically when errors found, regardless of finanicial impact. This hasn&#8217;t been the case since with vendors response most often &#8220;shooting the messenger&#8221;.</p>
<p>While beauracracy could paralyze us, it&#8217;s fightening no regulatory agency sits between some profit driven (apparently soul-less) vendors and hospitals.  Some hospitals simply resource strapped and non-software savvy &#8211; staff assume no vendor would knowingly ship dangerous code.  </p>
<p>With EMR/CDSS and non-FDA regulated medical device middeware, IT drives life-critical data and processes, with push in some cases to eliminate or marginalize the clinician.  A  Risk is enormous and worsens as we outsource, patch old systems and skimp on analysis, design and QA (cost saving).  Glitches are invisible to buyers.  </p>
<p>Many vendor and hospital staff expected to meet unrealistic deadlines driven in public companies by quarterly performance demands.  ARRA (incentives and timelines) and economy (need for those with jobs to retain them and companies to continue to produce &#8220;numbers&#8221;) add to perfect storm for errors and misuse of IT.  The HCIT industry works on &#8220;honor system&#8221;. Clinicians who raise issues have short careers.  </p>
<p>I&#8217;ve documented and presented concerns, had reached out to implore HIMSS and Gartner execs to take leadership role in raising awareness with vendor client members&#8217; CEOs/execs &#8211; not knowing who else might wield influence at this level.  No response.  </p>
<p>Who can/will advocate for clinicians and patients with corporate interests driving healthcare and HCIT? </p>
<p>Russ, you are my hero! Tim, keep em coming!  Will be hard to top this interview.  Timely to have these discussions!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Fourth Hansen Brother</title>
		<link>http://histalk2.com/2009/08/12/histalk-interviews-ross-koppel/comment-page-1/#comment-5118</link>
		<dc:creator>Fourth Hansen Brother</dc:creator>
		<pubDate>Fri, 14 Aug 2009 00:31:46 +0000</pubDate>
		<guid isPermaLink="false">http://histalk2.com/2009/08/12/histalk-interviews-ross-koppel/#comment-5118</guid>
		<description>There&#039;s wildly different responses fro vendors on patient safety issues- and sometimes, wildly different responses within the same vendor.

The non-disclosure clauses need to go. The non-compete clauses need to go. They&#039;re holding back the development in the industry from the normal percolation of ideas and people.</description>
		<content:encoded><![CDATA[<p>There&#8217;s wildly different responses fro vendors on patient safety issues- and sometimes, wildly different responses within the same vendor.</p>
<p>The non-disclosure clauses need to go. The non-compete clauses need to go. They&#8217;re holding back the development in the industry from the normal percolation of ideas and people.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
