<?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: Now That Is Open Source</title>
	<atom:link href="http://madisonian.net/2008/10/20/now-that-is-open-source/feed/" rel="self" type="application/rss+xml" />
	<link>http://madisonian.net/2008/10/20/now-that-is-open-source/</link>
	<description>a blog about law, tech, culture, and related things</description>
	<lastBuildDate>Thu, 10 May 2012 20:32:56 -0500</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Frank</title>
		<link>http://madisonian.net/2008/10/20/now-that-is-open-source/comment-page-1/#comment-263460</link>
		<dc:creator>Frank</dc:creator>
		<pubDate>Tue, 21 Oct 2008 19:48:44 +0000</pubDate>
		<guid isPermaLink="false">http://madisonian.net/?p=1549#comment-263460</guid>
		<description>Well, here&#039;s a squib from Greg Vetter&#039;s case study up on ssrn: 

&quot;The case study involves software to manage health information for hospitals or physician groups in the form of the electronic medical record, or EMR. Proprietary software venders supply most of the products for this software market. Recently, the U.S. government undertook experimental steps to promote a FOSS package for EMR, raising the question as to whether the EMR software market is amenable to FOSS. This Article describes various factors that might signal a FOSS disfavoring market, including low technical aptitude among users, differences among users in their work flow and software interface needs, users with dispassionate computing agendas, and entrenched proprietary competitors in an area supporting minimal complementary goods or services. FOSS, however, might be able to overcome these impedances in a particular software market if its unique motivational mix is strong enough.&quot;

Mark Hall is also working on this issue.

Some patients now keep exhaustive files, and scan information in (0r request CD&#039;s or DVD&#039;s from hospital records staff).  

I&#039;m glad Deven blogged the article--I found it pretty frightening.  To me, let&#039;s get some guaranteed backstop of care first.  I&#039;ll bet most of these pioneers (like Pinker, Dyson, etc.) will never have to worry about not having insurance, since they&#039;re wealthy enough to pay for it all on their own.</description>
		<content:encoded><![CDATA[<p>Well, here&#8217;s a squib from Greg Vetter&#8217;s case study up on ssrn: </p>
<p>&#8220;The case study involves software to manage health information for hospitals or physician groups in the form of the electronic medical record, or EMR. Proprietary software venders supply most of the products for this software market. Recently, the U.S. government undertook experimental steps to promote a FOSS package for EMR, raising the question as to whether the EMR software market is amenable to FOSS. This Article describes various factors that might signal a FOSS disfavoring market, including low technical aptitude among users, differences among users in their work flow and software interface needs, users with dispassionate computing agendas, and entrenched proprietary competitors in an area supporting minimal complementary goods or services. FOSS, however, might be able to overcome these impedances in a particular software market if its unique motivational mix is strong enough.&#8221;</p>
<p>Mark Hall is also working on this issue.</p>
<p>Some patients now keep exhaustive files, and scan information in (0r request CD&#8217;s or DVD&#8217;s from hospital records staff).  </p>
<p>I&#8217;m glad Deven blogged the article&#8211;I found it pretty frightening.  To me, let&#8217;s get some guaranteed backstop of care first.  I&#8217;ll bet most of these pioneers (like Pinker, Dyson, etc.) will never have to worry about not having insurance, since they&#8217;re wealthy enough to pay for it all on their own.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mike Madison</title>
		<link>http://madisonian.net/2008/10/20/now-that-is-open-source/comment-page-1/#comment-263434</link>
		<dc:creator>Mike Madison</dc:creator>
		<pubDate>Tue, 21 Oct 2008 12:39:26 +0000</pubDate>
		<guid isPermaLink="false">http://madisonian.net/?p=1549#comment-263434</guid>
		<description>This post partially preempts a question that I&#039;ve been meaning to ask here, so I&#039;ll ask it in the comments and see if it provokes some discussion.  (Deven, you&#039;re welcome to appropriate it if you like and add it to the Co-Op version, where it might get more visibility).

Who owns your health data?  Your historical blood pressure statistics, your chloresterol readings and weight, and so on.

Partly, this is a grand philosophical and normative question.  I&#039;m not asking about that.

More importantly, it is a powerful and important practical question.  Data portability projects are underway all over the country, and institutions at several levels are salivating over the prospects of owning this stuff.  They are the usual suspects -- hospitals and physicians, insurance carriers.  

In case of ambiguity, form contracts coupled to HIPAA notices will cover their butts vis-a-vis individuals.

Is that the right outcome?  This stuff is just the basis for so-called bargains?  We might not like the rhetorical presumption of &quot;ownership,&quot; but we&#039;re stuck with some frame that presumes control.  If control isn&#039;t allocated to individuals, then it will be appropriated by other institutions, and that may be a bad thing.  If we want to vest individual patients with control, how do we get from where we are now (state of acute uncertainty, capable of being exploited by large institutions), to that position?  Again, I&#039;m not interested in distributive justice arguments.  I&#039;m interested in pragmatics.  How is this going to work?</description>
		<content:encoded><![CDATA[<p>This post partially preempts a question that I&#8217;ve been meaning to ask here, so I&#8217;ll ask it in the comments and see if it provokes some discussion.  (Deven, you&#8217;re welcome to appropriate it if you like and add it to the Co-Op version, where it might get more visibility).</p>
<p>Who owns your health data?  Your historical blood pressure statistics, your chloresterol readings and weight, and so on.</p>
<p>Partly, this is a grand philosophical and normative question.  I&#8217;m not asking about that.</p>
<p>More importantly, it is a powerful and important practical question.  Data portability projects are underway all over the country, and institutions at several levels are salivating over the prospects of owning this stuff.  They are the usual suspects &#8212; hospitals and physicians, insurance carriers.  </p>
<p>In case of ambiguity, form contracts coupled to HIPAA notices will cover their butts vis-a-vis individuals.</p>
<p>Is that the right outcome?  This stuff is just the basis for so-called bargains?  We might not like the rhetorical presumption of &#8220;ownership,&#8221; but we&#8217;re stuck with some frame that presumes control.  If control isn&#8217;t allocated to individuals, then it will be appropriated by other institutions, and that may be a bad thing.  If we want to vest individual patients with control, how do we get from where we are now (state of acute uncertainty, capable of being exploited by large institutions), to that position?  Again, I&#8217;m not interested in distributive justice arguments.  I&#8217;m interested in pragmatics.  How is this going to work?</p>
]]></content:encoded>
	</item>
</channel>
</rss>

