<?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: News 6/13/07</title>
	<atom:link href="http://histalk2.com/2007/06/12/news-61307/feed/" rel="self" type="application/rss+xml" />
	<link>http://histalk2.com/2007/06/12/news-61307/</link>
	<description>Healthcare IT News and Opinion</description>
	<lastBuildDate>Wed, 08 Feb 2012 23:08:39 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3</generator>
	<item>
		<title>By: Mr. HIStalk</title>
		<link>http://histalk2.com/2007/06/12/news-61307/comment-page-1/#comment-17</link>
		<dc:creator>Mr. HIStalk</dc:creator>
		<pubDate>Wed, 13 Jun 2007 18:39:12 +0000</pubDate>
		<guid isPermaLink="false">http://histalk2.com/2007/06/12/news-61307/#comment-17</guid>
		<description>Fan, you are reading ahead! That&#039;s the plan, assuming the reader poll trend continues (showing a vast preference for HIStalk2&#039;s format.) I just need to set up an e-mail alerting system. Actually, I could easily keep populating HIStalk with no work at all since it can read RSS feeds, i.e. it can be an automatically populating mirror of the new HIStalk2 if there&#039;s a reason to do that (downtime, maybe, in case HIStalk2 gets trashed somehow?) The commenting capability in both HIStalk2 and the Discussion Forum are much better than under HIStalk, so it will definitely improve.</description>
		<content:encoded><![CDATA[<p>Fan, you are reading ahead! That&#8217;s the plan, assuming the reader poll trend continues (showing a vast preference for HIStalk2&#8242;s format.) I just need to set up an e-mail alerting system. Actually, I could easily keep populating HIStalk with no work at all since it can read RSS feeds, i.e. it can be an automatically populating mirror of the new HIStalk2 if there&#8217;s a reason to do that (downtime, maybe, in case HIStalk2 gets trashed somehow?) The commenting capability in both HIStalk2 and the Discussion Forum are much better than under HIStalk, so it will definitely improve.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Fan</title>
		<link>http://histalk2.com/2007/06/12/news-61307/comment-page-1/#comment-16</link>
		<dc:creator>Fan</dc:creator>
		<pubDate>Wed, 13 Jun 2007 18:25:30 +0000</pubDate>
		<guid isPermaLink="false">http://histalk2.com/2007/06/12/news-61307/#comment-16</guid>
		<description>With respect to original HISTalk and HISTalk2, the idea that there are two places for comments is less than ideal.  Why not shut down original HISTalk (keep for archives only) and move the mailing list and link to HISTalk2?  Everytime you add a new post to HISTalk 2, you could add a new post to HisTalk1 with just the link to HISTalk2.  Any comments I add to a posting will be less-read because most will not read on both websites -- I like to know my comments are read :-).</description>
		<content:encoded><![CDATA[<p>With respect to original HISTalk and HISTalk2, the idea that there are two places for comments is less than ideal.  Why not shut down original HISTalk (keep for archives only) and move the mailing list and link to HISTalk2?  Everytime you add a new post to HISTalk 2, you could add a new post to HisTalk1 with just the link to HISTalk2.  Any comments I add to a posting will be less-read because most will not read on both websites &#8212; I like to know my comments are read <img src='http://histalk2.com/wp-includes/images/smilies/icon_smile.gif' alt=':-)' class='wp-smiley' /> .</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: adam</title>
		<link>http://histalk2.com/2007/06/12/news-61307/comment-page-1/#comment-15</link>
		<dc:creator>adam</dc:creator>
		<pubDate>Wed, 13 Jun 2007 05:17:02 +0000</pubDate>
		<guid isPermaLink="false">http://histalk2.com/2007/06/12/news-61307/#comment-15</guid>
		<description>Must take into account the recent IRS ruling on hospital-provided EMR&#039;s.    As I understand it, the ruling

1) forces outside practices which accept the systems to take the same system that the hospital already uses (or, at least, a system provided by the same vendor). So, if a hospital used Epic, the system provided to the outside practices would most likely also be Epic. That&#039;s why this is advantageous to the hospital systems vendors and it&#039;s one reason why we might see rapid consolidation of ambulatory EMR vendors.

The flip side is that the doctors would have to accept a system that they might not like. Most of hospital HCIT vendors have less than optimal ambulatory offerings.

2) So, what you say, it&#039;s almost FREE to the outside practice. Well, there&#039;s a catch, which is that the outside practice would HAVE TO SHARE ITS DATA with the hospital. Since these hospitals make good money selling the data, there are privacy concerns. Also, and probably more important, is the fact that hospitals could now comb through outside physician data. This could be used AGAINST the physician at some point (think lawsuits, reimbursement or P4P schemes, etc...). 

So, the question for the outside practice is: is it worth it to get an almost free but poor ambulatory EMR system, but to create privacy concerns for your patients, and jeopardize the future of your practice as your patient data becomes semi-public information?  Somehow, I doubt it.

OTOH: what would you do if you were a big hospital vendor and you saw this tremendous opportunity slipping away. I might partner with or acquire the best ambulatory HCIT system(s) I could find and integrate the same with my hospital offerings.

So, unless the IRS ruling is changed or further clarified, look for bunches of new partnerships and/or acquisitions.</description>
		<content:encoded><![CDATA[<p>Must take into account the recent IRS ruling on hospital-provided EMR&#8217;s.    As I understand it, the ruling</p>
<p>1) forces outside practices which accept the systems to take the same system that the hospital already uses (or, at least, a system provided by the same vendor). So, if a hospital used Epic, the system provided to the outside practices would most likely also be Epic. That&#8217;s why this is advantageous to the hospital systems vendors and it&#8217;s one reason why we might see rapid consolidation of ambulatory EMR vendors.</p>
<p>The flip side is that the doctors would have to accept a system that they might not like. Most of hospital HCIT vendors have less than optimal ambulatory offerings.</p>
<p>2) So, what you say, it&#8217;s almost FREE to the outside practice. Well, there&#8217;s a catch, which is that the outside practice would HAVE TO SHARE ITS DATA with the hospital. Since these hospitals make good money selling the data, there are privacy concerns. Also, and probably more important, is the fact that hospitals could now comb through outside physician data. This could be used AGAINST the physician at some point (think lawsuits, reimbursement or P4P schemes, etc&#8230;). </p>
<p>So, the question for the outside practice is: is it worth it to get an almost free but poor ambulatory EMR system, but to create privacy concerns for your patients, and jeopardize the future of your practice as your patient data becomes semi-public information?  Somehow, I doubt it.</p>
<p>OTOH: what would you do if you were a big hospital vendor and you saw this tremendous opportunity slipping away. I might partner with or acquire the best ambulatory HCIT system(s) I could find and integrate the same with my hospital offerings.</p>
<p>So, unless the IRS ruling is changed or further clarified, look for bunches of new partnerships and/or acquisitions.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

