﻿<?xml version="1.0" encoding="utf-8"?>
<feed xmlns="http://www.w3.org/2005/Atom">
	<title>Zach Mortensen -- The Economics of Healthcare Information Technology: Recent Comments</title>
	<updated>2010-03-13T06:32:37Z</updated>
	<id>http://zachmortensen.net/comments/atom.aspx</id>
	<link href="http://zachmortensen.net/comments/atom.aspx" rel="self" type="application/rss+xml" />
	<link href="http://zachmortensen.net" rel="alternate" type="application/rss+xml" />
	<generator uri="http://app.onlinequickblog.com/" version="2.0">Quick Blogcast</generator>
	<entry>
		<title>Comment on The Long Tail of Healthcare IT</title>
		<link href="http://zachmortensen.net/2006/10/21/the-long-tail-of-healthcare-it.aspx#comment-164362" rel="alternate" type="application/rss+xml" />
		<id>tag:zachmortensen.net,2006-11-04:164362</id>
		<author>
			<name>zm</name>
		</author>
		<updated>2006-11-05T06:55:20Z</updated>
		<published>2006-11-05T06:55:20Z</published>
		<content type="html">Joseph,&lt;br /&gt;&lt;br /&gt;Thanks for visiting the blog and taking the time to comment on this topic.&lt;br /&gt;&lt;br /&gt;Being familiar with the EMR vendor side of the acute-care segment, here's how I think vendors will deal with the situation you describe:&lt;br /&gt;&lt;br /&gt;The commitment to CCHIT certification is ongoing with new requirements becoming available each year. I think vendors who are committed to the idea of CCHIT certification will orient their major releases to the timing of the CCHIT requirements cycle, and they may try to name their releases such that any occurring in the meantime are not new "versions" but rather updated releases of the certified version.&lt;br /&gt;&lt;br /&gt;For example, if "Version 8" of a product is certified, then the vendor may reason that the next (non-explicitly certified) release should be called 8.1 instead of 9.0, since 8.1 could reasonably be construed as just a "service pack" for Version 8.&lt;br /&gt;&lt;br /&gt;I'm curious to know whether that tactic has been employed in the ambulatory segment, and if so, how the vendor(s) in question have fared as a result. Best regards,&lt;br /&gt;&lt;br /&gt;ZM&lt;br /&gt;</content>
	</entry>
	<entry>
		<title>Comment on Metcalfe's Law: Manifest Destiny of Cerner and Epic?</title>
		<link href="http://zachmortensen.net/2006/10/21/metcalfes-law.aspx#comment-164356" rel="alternate" type="application/rss+xml" />
		<id>tag:zachmortensen.net,2006-11-04:164356</id>
		<author>
			<name>zm</name>
		</author>
		<updated>2006-11-05T06:44:21Z</updated>
		<published>2006-11-05T06:44:21Z</published>
		<content type="html">Thanks for reading and taking the time to comment.&lt;br /&gt;&lt;br /&gt;You're right, this particular post addressed only the value side of the equation. My intent was to show that while there is an intrinsic value (network effects) to be realized through an integrated architecture, smart people in other industries have overestimated that value, sometimes with tragic results.&lt;br /&gt;&lt;br /&gt;I addressed the cost side of the equation in a subsequent &lt;a class="" href="http://zachmortensen.net/2006/10/26/the-schwarzschild-radius-of-software-systems.aspx" target=""&gt;post&lt;/a&gt;, although I wouldn't consider it light reading. In a nutshell, the cost of creating the next feature on an integrated architecture is &lt;em&gt;exponential &lt;/em&gt;with respect to the number of features already supported by the architecture. Since the cost of creating an integrated architecture is exponential with respect to size and the value of an integrated architecture is at best polynomial (quadratic) in that same respect, the cost is bound to overwhelm the value beyond some point.&lt;br /&gt;&lt;br /&gt;So an integrated architecture is only economically feasible up to a certain point. The question is, have the market leaders crossed that point, and if not, how close are they to doing so? I'll have to address that one in another post, so stay tuned!&lt;br /&gt;&lt;br /&gt;ZM</content>
	</entry>
	<entry>
		<title>Comment on The Long Tail of Healthcare IT</title>
		<link href="http://zachmortensen.net/2006/10/21/the-long-tail-of-healthcare-it.aspx#comment-163782" rel="alternate" type="application/rss+xml" />
		<id>tag:zachmortensen.net,2006-11-04:163782</id>
		<author>
			<name>Joseph</name>
		</author>
		<updated>2006-11-04T12:37:20Z</updated>
		<published>2006-11-04T12:37:20Z</published>
		<content type="html">CCHIT will kill innovation as the certification is version specific and vendors will withhold refinements and improvements in their software because they have to tell CCHIT each time they upgrade and pay the fees. &lt;br&gt;The certification itself has nothing to do functionality as evidenced by a lot of doctors already using non certified systems.&lt;br&gt;Government wants interoperability. But there is no set standards yet. CCHIT just is a popup agency collecting fees telling doctors that if there is a seal of certification the software you are buying will be suitable for your office 100%. That is not the case as seen by postings by a lot of users at http://www.emrupdate.com/forums/default.aspx&lt;br&gt;&lt;br&gt;Regards</content>
	</entry>
	<entry>
		<title>Comment on Metcalfe's Law: Manifest Destiny of Cerner and Epic?</title>
		<link href="http://zachmortensen.net/2006/10/21/metcalfes-law.aspx#comment-154520" rel="alternate" type="application/rss+xml" />
		<id>tag:zachmortensen.net,2006-10-25:154520</id>
		<author>
			<name>Kyle</name>
		</author>
		<updated>2006-10-26T05:36:49Z</updated>
		<published>2006-10-26T05:36:49Z</published>
		<content type="html">Interesting thoughts here, although I don't see any logic to refute an "integrated architecture" strategy by health IT players.  Even if the relationship is n log n instead of exponential the integrated system is still worth more connected than would be individual departmental systems in isolation.</content>
	</entry>
	<entry>
		<title>Comment on The Long Tail of Healthcare IT</title>
		<link href="http://zachmortensen.net/2006/10/21/the-long-tail-of-healthcare-it.aspx#comment-154514" rel="alternate" type="application/rss+xml" />
		<id>tag:zachmortensen.net,2006-10-25:154514</id>
		<author>
			<name>Kyle</name>
		</author>
		<updated>2006-10-26T05:17:51Z</updated>
		<published>2006-10-26T05:17:51Z</published>
		<content type="html">I haven't read the long tail yet -but does it really apply to a market like HIT where there are a relatively small number of potential customers?  YOur point #3 re: scale only applies if the scale is big enough that there are at least enough customers to make products at the end of the tail profitable.&lt;br&gt;Another consideration is that in software there are VERY strong network effects.  In industries with strong network effects you don't see the long-tail ... you see a limited number of dominant players emerge.  Just my 2 cents.</content>
	</entry>
</feed>