<?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: The EMR-Medical Devices Mess</title>
	<atom:link href="http://rdn-consulting.com/blog/2007/09/22/the-emr-medical-devices-mess/feed/" rel="self" type="application/rss+xml" />
	<link>http://rdn-consulting.com/blog/2007/09/22/the-emr-medical-devices-mess/</link>
	<description>Software Development and Biomedical Engineering</description>
	<lastBuildDate>Fri, 19 Mar 2010 15:14:06 -0400</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Why Healthcare IT is Not a Game Changer &#124; Bob on Medical Device Software</title>
		<link>http://rdn-consulting.com/blog/2007/09/22/the-emr-medical-devices-mess/comment-page-1/#comment-2570</link>
		<dc:creator>Why Healthcare IT is Not a Game Changer &#124; Bob on Medical Device Software</dc:creator>
		<pubDate>Mon, 15 Feb 2010 20:43:19 +0000</pubDate>
		<guid isPermaLink="false">http://rdn-consulting.com/blog/2007/09/22/the-emr-medical-devices-mess/#comment-2570</guid>
		<description>[...] talked about HIT problems before, e.g. Healthcare Un-Interoperability and  The EMR-Medical Devices Mess. With all of the ARRA/HITECH talk along with the National Healthcare debate raging it made me [...]</description>
		<content:encoded><![CDATA[<p>[...] talked about HIT problems before, e.g. Healthcare Un-Interoperability and  The EMR-Medical Devices Mess. With all of the ARRA/HITECH talk along with the National Healthcare debate raging it made me [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Plug-and-Play Medicine &#124; Bob on Medical Device Software</title>
		<link>http://rdn-consulting.com/blog/2007/09/22/the-emr-medical-devices-mess/comment-page-1/#comment-2061</link>
		<dc:creator>Plug-and-Play Medicine &#124; Bob on Medical Device Software</dc:creator>
		<pubDate>Mon, 21 Sep 2009 03:56:55 +0000</pubDate>
		<guid isPermaLink="false">http://rdn-consulting.com/blog/2007/09/22/the-emr-medical-devices-mess/#comment-2061</guid>
		<description>[...] what software platform? I discussed the MD PnP program a couple of years ago. Other than the Integrated Clinical Environment (ICE, ASTM [...]</description>
		<content:encoded><![CDATA[<p>[...] what software platform? I discussed the MD PnP program a couple of years ago. Other than the Integrated Clinical Environment (ICE, ASTM [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: EMR</title>
		<link>http://rdn-consulting.com/blog/2007/09/22/the-emr-medical-devices-mess/comment-page-1/#comment-1263</link>
		<dc:creator>EMR</dc:creator>
		<pubDate>Mon, 06 Apr 2009 18:13:04 +0000</pubDate>
		<guid isPermaLink="false">http://rdn-consulting.com/blog/2007/09/22/the-emr-medical-devices-mess/#comment-1263</guid>
		<description>That does sound like a pretty big mess. Hopefully it&#039;s fixed by now.</description>
		<content:encoded><![CDATA[<p>That does sound like a pretty big mess. Hopefully it&#8217;s fixed by now.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dreaming of Flexible, Simple, Sloppy, Tolerant in Healthcare IT &#124; Bob on Medical Device Software</title>
		<link>http://rdn-consulting.com/blog/2007/09/22/the-emr-medical-devices-mess/comment-page-1/#comment-1179</link>
		<dc:creator>Dreaming of Flexible, Simple, Sloppy, Tolerant in Healthcare IT &#124; Bob on Medical Device Software</dc:creator>
		<pubDate>Sat, 03 Jan 2009 17:37:06 +0000</pubDate>
		<guid isPermaLink="false">http://rdn-consulting.com/blog/2007/09/22/the-emr-medical-devices-mess/#comment-1179</guid>
		<description>[...] to mind is HL7?  I&#8217;m not suggesting that some sort of open ad hoc system is the solution to The EMR-Medical Devices Mess.  But it&#8217;s painfully obvious that what has been built so far closely resemble &#8220;great [...]</description>
		<content:encoded><![CDATA[<p>[...] to mind is HL7?  I&#8217;m not suggesting that some sort of open ad hoc system is the solution to The EMR-Medical Devices Mess.  But it&#8217;s painfully obvious that what has been built so far closely resemble &#8220;great [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Transcription Guy</title>
		<link>http://rdn-consulting.com/blog/2007/09/22/the-emr-medical-devices-mess/comment-page-1/#comment-406</link>
		<dc:creator>Transcription Guy</dc:creator>
		<pubDate>Fri, 28 Dec 2007 22:57:47 +0000</pubDate>
		<guid isPermaLink="false">http://rdn-consulting.com/blog/2007/09/22/the-emr-medical-devices-mess/#comment-406</guid>
		<description>The purpose of HIPAA was to improve the efficiency and effectiveness of the healthcare system through the development of established health data standards and requirements for the transmission and storage of electronic health information. Currently, however, most EMR and medical transcription companies dont comply with these standards. We need to create a licencing mechanism to ensure that companies are indeed HIPAA compliant, similar to how manufacturers get ISO-9001 certified. Otherwise, the act just turns into a marketing tag line for companies.</description>
		<content:encoded><![CDATA[<p>The purpose of HIPAA was to improve the efficiency and effectiveness of the healthcare system through the development of established health data standards and requirements for the transmission and storage of electronic health information. Currently, however, most EMR and medical transcription companies dont comply with these standards. We need to create a licencing mechanism to ensure that companies are indeed HIPAA compliant, similar to how manufacturers get ISO-9001 certified. Otherwise, the act just turns into a marketing tag line for companies.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tim Gee</title>
		<link>http://rdn-consulting.com/blog/2007/09/22/the-emr-medical-devices-mess/comment-page-1/#comment-387</link>
		<dc:creator>Tim Gee</dc:creator>
		<pubDate>Wed, 19 Dec 2007 17:21:58 +0000</pubDate>
		<guid isPermaLink="false">http://rdn-consulting.com/blog/2007/09/22/the-emr-medical-devices-mess/#comment-387</guid>
		<description>Bob, thanks for the link! You&#039;re right, connectivity in ambulatory care is even worse off than in hospitals. It is expensive in hospitals, but in the physician office market many vendors (especially EMR vendors) refuse to do the work.

Certainly configuring HL7 at each installation is not practical in a highly fragmented market like physicians (where there are hundreds of thousands of practice locations). Proprietary APIs, like that offered by Midmark on the device side, and AllScript on the EMR side, are even worse. Integrating an API is a much bigger task than configuring the table of an HL7 interface. And there are dozens of medical device vendors in that market, and hundreds of EMR vendors.

There are ways to overcome this situation, but it won&#039;t happen through market &quot;evolution&quot; - it will take a real effort. Eventually the market will drive both device and EMR vendors to make this effort. Bob, I hope we&#039;re both still around to see it!</description>
		<content:encoded><![CDATA[<p>Bob, thanks for the link! You&#8217;re right, connectivity in ambulatory care is even worse off than in hospitals. It is expensive in hospitals, but in the physician office market many vendors (especially EMR vendors) refuse to do the work.</p>
<p>Certainly configuring HL7 at each installation is not practical in a highly fragmented market like physicians (where there are hundreds of thousands of practice locations). Proprietary APIs, like that offered by Midmark on the device side, and AllScript on the EMR side, are even worse. Integrating an API is a much bigger task than configuring the table of an HL7 interface. And there are dozens of medical device vendors in that market, and hundreds of EMR vendors.</p>
<p>There are ways to overcome this situation, but it won&#8217;t happen through market &#8220;evolution&#8221; &#8211; it will take a real effort. Eventually the market will drive both device and EMR vendors to make this effort. Bob, I hope we&#8217;re both still around to see it!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bridging the &#8220;Device Divide&#8221;</title>
		<link>http://rdn-consulting.com/blog/2007/09/22/the-emr-medical-devices-mess/comment-page-1/#comment-263</link>
		<dc:creator>Bridging the &#8220;Device Divide&#8221;</dc:creator>
		<pubDate>Tue, 06 Nov 2007 20:28:23 +0000</pubDate>
		<guid isPermaLink="false">http://rdn-consulting.com/blog/2007/09/22/the-emr-medical-devices-mess/#comment-263</guid>
		<description>[...] run across. It’s just that, as Robert Nadler, an employee at a device manufacturer, recently blogged: “The problem… is that we don’t have the resources to build each unique interface required to [...]</description>
		<content:encoded><![CDATA[<p>[...] run across. It’s just that, as Robert Nadler, an employee at a device manufacturer, recently blogged: “The problem… is that we don’t have the resources to build each unique interface required to [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
