<?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: Another Year, Another HIMSS</title>
	<atom:link href="http://chilmarkresearch.com/2010/03/05/another-year-another-himss/feed/" rel="self" type="application/rss+xml" />
	<link>http://chilmarkresearch.com/2010/03/05/another-year-another-himss/</link>
	<description>Providing perspective on key IT trends in the healthcare sector</description>
	<lastBuildDate>Thu, 09 Feb 2012 23:01:44 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.com/</generator>
	<item>
		<title>By: vswamy</title>
		<link>http://chilmarkresearch.com/2010/03/05/another-year-another-himss/#comment-5502</link>
		<dc:creator><![CDATA[vswamy]]></dc:creator>
		<pubDate>Tue, 27 Jul 2010 01:45:35 +0000</pubDate>
		<guid isPermaLink="false">http://chilmarkresearch.com/?p=2381#comment-5502</guid>
		<description><![CDATA[Really, could not agree more on this topic. Great post, flushed out many of the certification , cost and implementation issues in this incentive era.

I feel today medical practitioners are looking to avail of this federal incentive by trying to comply with the definition of &lt;a href=&quot;http://www.waitingroomsolutions.com/wrs/meaningful-use-EHR-meaningful-use-definition-EHR-Matrix-Regulations&quot; rel=&quot;nofollow&quot;&gt;meaningful use&lt;/a&gt; but at the same time EHR providers are looking at their own set of profits.
This misunderstanding is mostly I believe as a result of wrong interpretation of the &lt;a href=&quot;http://www.waitingroomsolutions.com/wrs/certification-criteria-electronic-health-records-ARRA-Certification-Requirements-Health-Record-Certification&quot; rel=&quot;nofollow&quot;&gt;federal guidelines.&lt;/a&gt;.  The EHR providers need to look at these guidelines from the prospective of the practitioners who deal with different specialties.
Each &lt;a href=&quot;http://www.waitingroomsolutions.com/wrs/specialty-main.html&quot; rel=&quot;nofollow&quot;&gt;specialty EHR&lt;/a&gt; has its own set of challenges or requirements which I believe is overlooked by in most EHR vendors in a effort to merely follows federal guidelines. This is resulting in low usability to the practitioners, thus less ROI, finally redundancy of the EHR solution in place.
I think ROI is very important factor that should be duly considered when look achieve a &#039;meaning use&#039; out of a EHR solution. Though one may get vendors providing &#039;meaning use&#039; at a lower cost, their ROI / savings through the use of their EHR might be pretty low when compared to costlier initial investment. Found a pretty useful ROI tool that is pretty customizable and easy to use. It also accounts for the different specialty EHR&#039;s too.
Also the introduction of REC’s through the &lt;a href=&quot;http://www.waitingroomsolutions.com/wrs/regional-extension-centers-arra-rec&quot; rel=&quot;nofollow&quot;&gt;HITECH act.&lt;/a&gt; is a great way to avail of quality EHR solutions at competitive prices. The stiff competition among not only these REC’s but also among EHR vendors ( to become a preferred vendor of a given REC) will result in lot of positives to medical practioners.
Looking the funding provided to the REC’s, the &lt;a href=&quot;http://www.waitingroomsolutions.com/wrs/regional-extension-center-health-it&quot; rel=&quot;nofollow&quot;&gt;staggered grant allocation system&lt;/a&gt; also promises to be an unbiased way of allocating funds. It will also help in the concept of REC’s helping out each with their own unique business models. It can be one of the possible answers to the &#039;safe EHR vendor&#039; challenge as discussed by many critics.

Sorry to have diverted a bit from the topic but I feel this HITECT act and the REC&#039;s are going to play an important role, as discussed above in the successful EHR implementation in the medical practices in our country. 

As far as implementation challenges goes, the &lt;a href=&quot;http://www.waitingroomsolutions.com/wrs/certification-criteria-electronic-health-records-ARRA-Certification-Requirements-Health-Record-Certification&quot; rel=&quot;nofollow&quot;&gt;federal guidelines for certification&lt;/a&gt; and usability are pretty much clear. Useful improvisation on these lines can make ones EHR&#039;s friendly to most practices of varying specialties.]]></description>
		<content:encoded><![CDATA[<p>Really, could not agree more on this topic. Great post, flushed out many of the certification , cost and implementation issues in this incentive era.</p>
<p>I feel today medical practitioners are looking to avail of this federal incentive by trying to comply with the definition of <a href="http://www.waitingroomsolutions.com/wrs/meaningful-use-EHR-meaningful-use-definition-EHR-Matrix-Regulations" rel="nofollow">meaningful use</a> but at the same time EHR providers are looking at their own set of profits.<br />
This misunderstanding is mostly I believe as a result of wrong interpretation of the <a href="http://www.waitingroomsolutions.com/wrs/certification-criteria-electronic-health-records-ARRA-Certification-Requirements-Health-Record-Certification" rel="nofollow">federal guidelines.</a>.  The EHR providers need to look at these guidelines from the prospective of the practitioners who deal with different specialties.<br />
Each <a href="http://www.waitingroomsolutions.com/wrs/specialty-main.html" rel="nofollow">specialty EHR</a> has its own set of challenges or requirements which I believe is overlooked by in most EHR vendors in a effort to merely follows federal guidelines. This is resulting in low usability to the practitioners, thus less ROI, finally redundancy of the EHR solution in place.<br />
I think ROI is very important factor that should be duly considered when look achieve a &#8216;meaning use&#8217; out of a EHR solution. Though one may get vendors providing &#8216;meaning use&#8217; at a lower cost, their ROI / savings through the use of their EHR might be pretty low when compared to costlier initial investment. Found a pretty useful ROI tool that is pretty customizable and easy to use. It also accounts for the different specialty EHR&#8217;s too.<br />
Also the introduction of REC’s through the <a href="http://www.waitingroomsolutions.com/wrs/regional-extension-centers-arra-rec" rel="nofollow">HITECH act.</a> is a great way to avail of quality EHR solutions at competitive prices. The stiff competition among not only these REC’s but also among EHR vendors ( to become a preferred vendor of a given REC) will result in lot of positives to medical practioners.<br />
Looking the funding provided to the REC’s, the <a href="http://www.waitingroomsolutions.com/wrs/regional-extension-center-health-it" rel="nofollow">staggered grant allocation system</a> also promises to be an unbiased way of allocating funds. It will also help in the concept of REC’s helping out each with their own unique business models. It can be one of the possible answers to the &#8216;safe EHR vendor&#8217; challenge as discussed by many critics.</p>
<p>Sorry to have diverted a bit from the topic but I feel this HITECT act and the REC&#8217;s are going to play an important role, as discussed above in the successful EHR implementation in the medical practices in our country. </p>
<p>As far as implementation challenges goes, the <a href="http://www.waitingroomsolutions.com/wrs/certification-criteria-electronic-health-records-ARRA-Certification-Requirements-Health-Record-Certification" rel="nofollow">federal guidelines for certification</a> and usability are pretty much clear. Useful improvisation on these lines can make ones EHR&#8217;s friendly to most practices of varying specialties.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Has innovation taken backbench is Healthcare IT? &#124; Shadzlog</title>
		<link>http://chilmarkresearch.com/2010/03/05/another-year-another-himss/#comment-5202</link>
		<dc:creator><![CDATA[Has innovation taken backbench is Healthcare IT? &#124; Shadzlog]]></dc:creator>
		<pubDate>Sun, 23 May 2010 05:49:43 +0000</pubDate>
		<guid isPermaLink="false">http://chilmarkresearch.com/?p=2381#comment-5202</guid>
		<description><![CDATA[[...] Chilmark&#8217;s Post [...]]]></description>
		<content:encoded><![CDATA[<p>[...] Chilmark&#8217;s Post [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: 50 EMR Markets Instead of 1 EMR Market &#124; EMR and HIPAA</title>
		<link>http://chilmarkresearch.com/2010/03/05/another-year-another-himss/#comment-4844</link>
		<dc:creator><![CDATA[50 EMR Markets Instead of 1 EMR Market &#124; EMR and HIPAA]]></dc:creator>
		<pubDate>Mon, 22 Mar 2010 15:06:00 +0000</pubDate>
		<guid isPermaLink="false">http://chilmarkresearch.com/?p=2381#comment-4844</guid>
		<description><![CDATA[[...] Moore at Chilmark Research said, &#8220;So Many EHRs, So Little Time: Simply amazing that this market can support so many EMR/EHR [...]]]></description>
		<content:encoded><![CDATA[<p>[...] Moore at Chilmark Research said, &#8220;So Many EHRs, So Little Time: Simply amazing that this market can support so many EMR/EHR [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jim Bloedau @ Information Advantage Group</title>
		<link>http://chilmarkresearch.com/2010/03/05/another-year-another-himss/#comment-4707</link>
		<dc:creator><![CDATA[Jim Bloedau @ Information Advantage Group]]></dc:creator>
		<pubDate>Sat, 06 Mar 2010 15:37:49 +0000</pubDate>
		<guid isPermaLink="false">http://chilmarkresearch.com/?p=2381#comment-4707</guid>
		<description><![CDATA[John, thanks for the nice review.  Since the ‘80s we&#039;ve seen the exchange of clinical data being proposed under any number of acronyms at HIMSS - CHIN’s in the 90s and more recently RHIOs and HIEs.  All suffered from solving one major hurtle only to find that their efforts offered a better view of the next under-anticipated problem. Through all of these formulations, the struggle to prove adequate economic benefit to cover the cost of pulling together a highly fractionated system has not been won enough times to seed a movement, let a lone a sustainable business model for all. Yet, much of the discussion centers on trying to sell an HIE like they were selling a super highway -- difficult to do when the average provider community only sees, wants or can afford a cow path.  Add the temptation/mandate of money for EHR and the jam starts getting pretty thin on the bread.

Be patient - thing move in big slow waves in healthcare.  

Cooperation as a community seems to be the trick…read more @ 
http://iagllc.blogspot.com/2010/02/should-cowpaths-of-cooperation-be-first.html#more]]></description>
		<content:encoded><![CDATA[<p>John, thanks for the nice review.  Since the ‘80s we&#8217;ve seen the exchange of clinical data being proposed under any number of acronyms at HIMSS &#8211; CHIN’s in the 90s and more recently RHIOs and HIEs.  All suffered from solving one major hurtle only to find that their efforts offered a better view of the next under-anticipated problem. Through all of these formulations, the struggle to prove adequate economic benefit to cover the cost of pulling together a highly fractionated system has not been won enough times to seed a movement, let a lone a sustainable business model for all. Yet, much of the discussion centers on trying to sell an HIE like they were selling a super highway &#8212; difficult to do when the average provider community only sees, wants or can afford a cow path.  Add the temptation/mandate of money for EHR and the jam starts getting pretty thin on the bread.</p>
<p>Be patient &#8211; thing move in big slow waves in healthcare.  </p>
<p>Cooperation as a community seems to be the trick…read more @<br />
<a href="http://iagllc.blogspot.com/2010/02/should-cowpaths-of-cooperation-be-first.html#more" rel="nofollow">http://iagllc.blogspot.com/2010/02/should-cowpaths-of-cooperation-be-first.html#more</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: ICMCC News Page &#187; Another Year, Another HIMSS</title>
		<link>http://chilmarkresearch.com/2010/03/05/another-year-another-himss/#comment-4705</link>
		<dc:creator><![CDATA[ICMCC News Page &#187; Another Year, Another HIMSS]]></dc:creator>
		<pubDate>Sat, 06 Mar 2010 14:31:13 +0000</pubDate>
		<guid isPermaLink="false">http://chilmarkresearch.com/?p=2381#comment-4705</guid>
		<description><![CDATA[[...] Article John Moore, Chilmark Research, 5 March 2010 SHARETHIS.addEntry({ title: &quot;Another Year, Another HIMSS&quot;, url: &quot;http://articles.icmcc.org/2010/03/06/another-year-another-himss/&quot; }); [...]]]></description>
		<content:encoded><![CDATA[<p>[...] Article John Moore, Chilmark Research, 5 March 2010 SHARETHIS.addEntry({ title: &quot;Another Year, Another HIMSS&quot;, url: &quot;<a href="http://articles.icmcc.org/2010/03/06/another-year-another-himss/&#038;quot" rel="nofollow">http://articles.icmcc.org/2010/03/06/another-year-another-himss/&#038;quot</a>; }); [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: medicalfutureshock</title>
		<link>http://chilmarkresearch.com/2010/03/05/another-year-another-himss/#comment-4701</link>
		<dc:creator><![CDATA[medicalfutureshock]]></dc:creator>
		<pubDate>Sat, 06 Mar 2010 01:16:32 +0000</pubDate>
		<guid isPermaLink="false">http://chilmarkresearch.com/?p=2381#comment-4701</guid>
		<description><![CDATA[John,  good take.  I thought it was just me.  

A few things that I noticed were:

As you mention Microsoft has stepped it up with HVCC which is good for me because we just become HealthVault partners.

Platforms:  Makes total sense, add software engineering to healthcare and you get platforms.  BEA, ATG, WebSphere just to name a few that modernized Internet sites.  If they build platforms like these, it will revolutionize the building and customizing of health care systems.

Google Health:  Looks like Google is moving from &quot;science project&quot; to a real PHR.  They have also removed their beta label from the site.  I spoke with one of their engineers and they told me that they are adding things like full compliant CCR and CCD compliance.  They are also planning more support for developers with has been an issue in the past.
Regardless of what you think about Google in the PHR space it will help bring overall exposure to the concept.
 
Even though I saw a lot and learned a little less than I expected, I really enjoyed the show and look forward to the next one.

Next year I predict will be the year of wireless innovation across the spectrum, from home healthcare to in-patient devices, which are currently in majority RS-232 (unbelievable) 

Jeff Brandt
www.hieconnect.net]]></description>
		<content:encoded><![CDATA[<p>John,  good take.  I thought it was just me.  </p>
<p>A few things that I noticed were:</p>
<p>As you mention Microsoft has stepped it up with HVCC which is good for me because we just become HealthVault partners.</p>
<p>Platforms:  Makes total sense, add software engineering to healthcare and you get platforms.  BEA, ATG, WebSphere just to name a few that modernized Internet sites.  If they build platforms like these, it will revolutionize the building and customizing of health care systems.</p>
<p>Google Health:  Looks like Google is moving from &#8220;science project&#8221; to a real PHR.  They have also removed their beta label from the site.  I spoke with one of their engineers and they told me that they are adding things like full compliant CCR and CCD compliance.  They are also planning more support for developers with has been an issue in the past.<br />
Regardless of what you think about Google in the PHR space it will help bring overall exposure to the concept.</p>
<p>Even though I saw a lot and learned a little less than I expected, I really enjoyed the show and look forward to the next one.</p>
<p>Next year I predict will be the year of wireless innovation across the spectrum, from home healthcare to in-patient devices, which are currently in majority RS-232 (unbelievable) </p>
<p>Jeff Brandt<br />
<a href="http://www.hieconnect.net" rel="nofollow">http://www.hieconnect.net</a></p>
]]></content:encoded>
	</item>
</channel>
</rss>

