<?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: Covisint Jumps onto PaaS Bandwagon</title>
	<atom:link href="http://chilmarkresearch.com/2009/11/15/covisint-jumps-onto-paas-bandwagon/feed/" rel="self" type="application/rss+xml" />
	<link>http://chilmarkresearch.com/2009/11/15/covisint-jumps-onto-paas-bandwagon/</link>
	<description>Providing perspective on key IT trends in the healthcare sector</description>
	<lastBuildDate>Fri, 30 Jul 2010 06:41:04 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.com/</generator>
	<item>
		<title>By: Is HITECH Working? #4: While most attention has been focused on demand side incentives (will doctors and hospitals buy EHRs?), the supply (vendor) side of HIT is already transforming. &#124; e-CareManagement</title>
		<link>http://chilmarkresearch.com/2009/11/15/covisint-jumps-onto-paas-bandwagon/#comment-5037</link>
		<dc:creator>Is HITECH Working? #4: While most attention has been focused on demand side incentives (will doctors and hospitals buy EHRs?), the supply (vendor) side of HIT is already transforming. &#124; e-CareManagement</dc:creator>
		<pubDate>Mon, 19 Apr 2010 18:06:54 +0000</pubDate>
		<guid isPermaLink="false">http://chilmarkresearch.com/?p=2138#comment-5037</guid>
		<description>[...] Covisint Jumps onto PaaS Bandwagon [...]</description>
		<content:encoded><![CDATA[<p>[...] Covisint Jumps onto PaaS Bandwagon [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Cloud Computing, Security &#38; Privacy Considerations &#171; Chilmark Research</title>
		<link>http://chilmarkresearch.com/2009/11/15/covisint-jumps-onto-paas-bandwagon/#comment-4133</link>
		<dc:creator>Cloud Computing, Security &#38; Privacy Considerations &#171; Chilmark Research</dc:creator>
		<pubDate>Wed, 09 Dec 2009 19:37:31 +0000</pubDate>
		<guid isPermaLink="false">http://chilmarkresearch.com/?p=2138#comment-4133</guid>
		<description>[...] the &#8220;cloud computing&#8221; paradigm in the healthcare sector, be it personal health clouds, HIE vendors transitioning to PaaS vendors (note: Medicity made their own PaaS announcement yesterday &#8211; more to follow in near future), [...]</description>
		<content:encoded><![CDATA[<p>[...] the &#8220;cloud computing&#8221; paradigm in the healthcare sector, be it personal health clouds, HIE vendors transitioning to PaaS vendors (note: Medicity made their own PaaS announcement yesterday &#8211; more to follow in near future), [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Art_Vandelay</title>
		<link>http://chilmarkresearch.com/2009/11/15/covisint-jumps-onto-paas-bandwagon/#comment-4052</link>
		<dc:creator>Art_Vandelay</dc:creator>
		<pubDate>Sat, 28 Nov 2009 13:48:39 +0000</pubDate>
		<guid isPermaLink="false">http://chilmarkresearch.com/?p=2138#comment-4052</guid>
		<description>All Covisnt is offering via APIs is single sign-in. I am unaware of them even having patient context synchronized between the applications. As for an underlying data structure, they have no central data structure. I have not seen a comprehensive federated structure for their product. Even when you federate data, it still is placed in a virtual or physical model. I just see their product as single sign-in and a bunch of loose channel relationships. It also doesn&#039;t address the functional duplications and the challenges that causes when you federate functions across applications and avoid shutting down duplicative functions in others. PaaS is yet another marketing channel to try and get this company on the radar screen. At least they haven&#039;t tried to make Applications as a Simple Service of themselves yet.

As for physicians having to go to one application or multiple applications, look-and-feel and the ergonomics of the applications matter. If patient search isn&#039;t consistent, training and user adoption will be a challenge. Microsoft, working with the UK, developed a consistent patient banner as well as other components in a consistent UI to help manage training, increase usability, and increase patient safety. Physicians want usability, they don&#039;t want to waste time on training, they want their data to be available and exchanged between applications and they want to run reports from time-to-time. I fail to see how a loose bunch of applications can satisfy this demand. They are not marketing composite applications or even a worthwhile mash-up. Without a consistent user interface, some level of a physical or federated data model, data interfaces or integration, a single call for support model, a single licensing model and some recognition of different workflow needs for different practice sizes, specialties and configurations, it is just a single sign-on web page to me. I dare not even call it one of the former buzz words dujour, a portal. 

So what if the AMA wants Allscripts, find other channel partners. Better yet, acquire someone that fits your architecture, truly integrate them and create the better mousetrap instead of this set of stand-alone applications.</description>
		<content:encoded><![CDATA[<p>All Covisnt is offering via APIs is single sign-in. I am unaware of them even having patient context synchronized between the applications. As for an underlying data structure, they have no central data structure. I have not seen a comprehensive federated structure for their product. Even when you federate data, it still is placed in a virtual or physical model. I just see their product as single sign-in and a bunch of loose channel relationships. It also doesn&#8217;t address the functional duplications and the challenges that causes when you federate functions across applications and avoid shutting down duplicative functions in others. PaaS is yet another marketing channel to try and get this company on the radar screen. At least they haven&#8217;t tried to make Applications as a Simple Service of themselves yet.</p>
<p>As for physicians having to go to one application or multiple applications, look-and-feel and the ergonomics of the applications matter. If patient search isn&#8217;t consistent, training and user adoption will be a challenge. Microsoft, working with the UK, developed a consistent patient banner as well as other components in a consistent UI to help manage training, increase usability, and increase patient safety. Physicians want usability, they don&#8217;t want to waste time on training, they want their data to be available and exchanged between applications and they want to run reports from time-to-time. I fail to see how a loose bunch of applications can satisfy this demand. They are not marketing composite applications or even a worthwhile mash-up. Without a consistent user interface, some level of a physical or federated data model, data interfaces or integration, a single call for support model, a single licensing model and some recognition of different workflow needs for different practice sizes, specialties and configurations, it is just a single sign-on web page to me. I dare not even call it one of the former buzz words dujour, a portal. </p>
<p>So what if the AMA wants Allscripts, find other channel partners. Better yet, acquire someone that fits your architecture, truly integrate them and create the better mousetrap instead of this set of stand-alone applications.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: John</title>
		<link>http://chilmarkresearch.com/2009/11/15/covisint-jumps-onto-paas-bandwagon/#comment-4015</link>
		<dc:creator>John</dc:creator>
		<pubDate>Wed, 18 Nov 2009 01:10:12 +0000</pubDate>
		<guid isPermaLink="false">http://chilmarkresearch.com/?p=2138#comment-4015</guid>
		<description>You make some good points here Art.  Do believe that the transition of the traditional HIE offering to one that is more of a PaaS is inevitable and Covisint is but one example, but one that is not necessarily fully mature by any stretch of the imagination.  For example, choosing AllScripts as the first EMR offering seems like overkill and Covisint would likely be better off with smaller, more agile EMR apps.  The only reason AllScripts is there is that this is who the AMA wanted on their platform which is based on Covisint.  Same could probably be said for just about all the apps on Covisint today as Covisint and AMA began working on this concept earlier in 2009.

As for your other comments regarding the multitude of apps, well it really all depends on the job the physician is trying to accomplish. In some encounters he/she may need access to multiple apps, in other situations, only one.  The underlying data structure, in a PaaS model is supported within Covisint and served up through the API into the various apps that a physician may invoke in the course of his daily practice.  Apps that are easy and intuitive will succeed, those that are not will not be popular, not be adopted and fade.  

Again, good points raised Art and HIE vendors would be wise to think these issues through as they launch their own PaaS.  Sill early, still very immature, but this is the future of healthcare IT in the small ambulatory setting.</description>
		<content:encoded><![CDATA[<p>You make some good points here Art.  Do believe that the transition of the traditional HIE offering to one that is more of a PaaS is inevitable and Covisint is but one example, but one that is not necessarily fully mature by any stretch of the imagination.  For example, choosing AllScripts as the first EMR offering seems like overkill and Covisint would likely be better off with smaller, more agile EMR apps.  The only reason AllScripts is there is that this is who the AMA wanted on their platform which is based on Covisint.  Same could probably be said for just about all the apps on Covisint today as Covisint and AMA began working on this concept earlier in 2009.</p>
<p>As for your other comments regarding the multitude of apps, well it really all depends on the job the physician is trying to accomplish. In some encounters he/she may need access to multiple apps, in other situations, only one.  The underlying data structure, in a PaaS model is supported within Covisint and served up through the API into the various apps that a physician may invoke in the course of his daily practice.  Apps that are easy and intuitive will succeed, those that are not will not be popular, not be adopted and fade.  </p>
<p>Again, good points raised Art and HIE vendors would be wise to think these issues through as they launch their own PaaS.  Sill early, still very immature, but this is the future of healthcare IT in the small ambulatory setting.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Lincoln Nguyen</title>
		<link>http://chilmarkresearch.com/2009/11/15/covisint-jumps-onto-paas-bandwagon/#comment-4012</link>
		<dc:creator>Lincoln Nguyen</dc:creator>
		<pubDate>Tue, 17 Nov 2009 16:18:18 +0000</pubDate>
		<guid isPermaLink="false">http://chilmarkresearch.com/?p=2138#comment-4012</guid>
		<description>There needs to be more EMR lite applications in the market and more APIs for patient monitoring.</description>
		<content:encoded><![CDATA[<p>There needs to be more EMR lite applications in the market and more APIs for patient monitoring.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Art_Vandelay</title>
		<link>http://chilmarkresearch.com/2009/11/15/covisint-jumps-onto-paas-bandwagon/#comment-4011</link>
		<dc:creator>Art_Vandelay</dc:creator>
		<pubDate>Tue, 17 Nov 2009 11:36:17 +0000</pubDate>
		<guid isPermaLink="false">http://chilmarkresearch.com/?p=2138#comment-4011</guid>
		<description>While single sign-on is a great offering, this is far from innovative. It is a list of links on a web page with some lightweight messaging. The physicians still need to remember to go into each application to conduct services. Functionality is replicated in multiple products. Who is conducting the workflow analysis to attempt to reconcile 11 application categories with a practice management system and electronic record system such as Allscripts? Who is going to take that information and change it into interfaces and notifications to guide the physician to go into the other systems? After that, who is going to support this as one or more of the 11 vendors + the practice management/electronic record vendor changes their underlying data structures, logic or navigation methods? Who is bringing together these vendor partners (term is used as loosely as possible) in a consistent and understandable structure that allows the physician to select services, rationalize duplicates, contract, receive and coordinate support, understand charges from the vendors, and resolve disputes?

This looks like the definition of information overload to me - just like first generation stand-alone blog readers without keyword searches, alerts and the ability to follow a feed. Better yet, it is a poorly produced song - &quot;Physician Office PaaS,&quot; by Covisnt, featuring MedAI, Wellcentive, Reach My Doctor, LabCorp, HealthVault and with special guest Allscripts. Where&#039;s Kanye when you need a good comment?</description>
		<content:encoded><![CDATA[<p>While single sign-on is a great offering, this is far from innovative. It is a list of links on a web page with some lightweight messaging. The physicians still need to remember to go into each application to conduct services. Functionality is replicated in multiple products. Who is conducting the workflow analysis to attempt to reconcile 11 application categories with a practice management system and electronic record system such as Allscripts? Who is going to take that information and change it into interfaces and notifications to guide the physician to go into the other systems? After that, who is going to support this as one or more of the 11 vendors + the practice management/electronic record vendor changes their underlying data structures, logic or navigation methods? Who is bringing together these vendor partners (term is used as loosely as possible) in a consistent and understandable structure that allows the physician to select services, rationalize duplicates, contract, receive and coordinate support, understand charges from the vendors, and resolve disputes?</p>
<p>This looks like the definition of information overload to me &#8211; just like first generation stand-alone blog readers without keyword searches, alerts and the ability to follow a feed. Better yet, it is a poorly produced song &#8211; &#8220;Physician Office PaaS,&#8221; by Covisnt, featuring MedAI, Wellcentive, Reach My Doctor, LabCorp, HealthVault and with special guest Allscripts. Where&#8217;s Kanye when you need a good comment?</p>
]]></content:encoded>
	</item>
</channel>
</rss>
