<?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: Microsoft and HealthVault.com</title>
	<atom:link href="http://www.wikinomics.com/blog/index.php/2007/10/04/microsoft-and-healthvaultcom/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.wikinomics.com/blog/index.php/2007/10/04/microsoft-and-healthvaultcom/</link>
	<description>Exploring How Mass Collaboration Changes Everything</description>
	<lastBuildDate>Sun, 28 Aug 2011 14:21:24 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>By: Preston M.</title>
		<link>http://www.wikinomics.com/blog/index.php/2007/10/04/microsoft-and-healthvaultcom/comment-page-1/#comment-103461</link>
		<dc:creator>Preston M.</dc:creator>
		<pubDate>Thu, 13 Mar 2008 22:48:45 +0000</pubDate>
		<guid isPermaLink="false">http://www.wikinomics.com/blog/index.php/2007/10/04/microsoft-and-healthvaultcom/#comment-103461</guid>
		<description>&quot;I’d hate to see how personalized my web surfing would become in the future if companies like Microsoft started displaying ads for Heart medication after probing my database.&quot;

This will never happen, HIPAA is cracking the whip hard on this one. First of all, what you&#039;re worried about is illegal, and second of all it would require an entire team focused on the development of such a project, and quite frankly, Microsoft would never put themselves in this type of a risk.</description>
		<content:encoded><![CDATA[<p>&#8220;I’d hate to see how personalized my web surfing would become in the future if companies like Microsoft started displaying ads for Heart medication after probing my database.&#8221;</p>
<p>This will never happen, HIPAA is cracking the whip hard on this one. First of all, what you&#8217;re worried about is illegal, and second of all it would require an entire team focused on the development of such a project, and quite frankly, Microsoft would never put themselves in this type of a risk.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: james cannon</title>
		<link>http://www.wikinomics.com/blog/index.php/2007/10/04/microsoft-and-healthvaultcom/comment-page-1/#comment-44534</link>
		<dc:creator>james cannon</dc:creator>
		<pubDate>Sat, 03 Nov 2007 05:25:56 +0000</pubDate>
		<guid isPermaLink="false">http://www.wikinomics.com/blog/index.php/2007/10/04/microsoft-and-healthvaultcom/#comment-44534</guid>
		<description>I applaud MS on this project. This  move is cutting edge. If handled correctly, it could be a win for all stakeholders across heathcare in the US. One thing MS should keep in mind is that while it seems their project&#039;s  initial and primary focus is consumer/patient driven, the healthcare payment industry focus (i.e. business to business commerce between provider and payer to pay claims) is huge and could gain traction much quicker than relying on patients to participate as a matter of first impression. MS should remember that protected health information (PHI), by federal regulation, is allowed to be widley and freely shared for purposes of &quot;effecting payment or reimbursement&quot; to from healthcare payers to healthcare providers. Providers and payers should welcome a secure and uniform platform through which they can easily share medical record and claim information to adjudicate the patient&#039;s bill for services rendered. The information and documentation generated by commerce between payer and provider could very quickly populate the &quot;vault&quot; regardless of whether the patient chooses to access or share the medical record or claim information. Patients readily agree each day via admission and/or discharge documentation to share their PHI with any payer source for the purpose to effect payment of their claim per HIPAA regulations. MS needs to understand that every health care event generates an account receivable and attendant medical record information that payers require to review before payment to a provider or patient. MS can populate their vault and work with providers and payers to advertise to patients that the vault is already full of information that the patient can see (and share) if the so choose. Bottom line, providers and payers can easily populate the vault by placing this information therein which they are already sharing with the patients consent on a daily basis by transactions numbered in the millions each day.....</description>
		<content:encoded><![CDATA[<p>I applaud MS on this project. This  move is cutting edge. If handled correctly, it could be a win for all stakeholders across heathcare in the US. One thing MS should keep in mind is that while it seems their project&#8217;s  initial and primary focus is consumer/patient driven, the healthcare payment industry focus (i.e. business to business commerce between provider and payer to pay claims) is huge and could gain traction much quicker than relying on patients to participate as a matter of first impression. MS should remember that protected health information (PHI), by federal regulation, is allowed to be widley and freely shared for purposes of &#8220;effecting payment or reimbursement&#8221; to from healthcare payers to healthcare providers. Providers and payers should welcome a secure and uniform platform through which they can easily share medical record and claim information to adjudicate the patient&#8217;s bill for services rendered. The information and documentation generated by commerce between payer and provider could very quickly populate the &#8220;vault&#8221; regardless of whether the patient chooses to access or share the medical record or claim information. Patients readily agree each day via admission and/or discharge documentation to share their PHI with any payer source for the purpose to effect payment of their claim per HIPAA regulations. MS needs to understand that every health care event generates an account receivable and attendant medical record information that payers require to review before payment to a provider or patient. MS can populate their vault and work with providers and payers to advertise to patients that the vault is already full of information that the patient can see (and share) if the so choose. Bottom line, providers and payers can easily populate the vault by placing this information therein which they are already sharing with the patients consent on a daily basis by transactions numbered in the millions each day&#8230;..</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: product-innov8tor</title>
		<link>http://www.wikinomics.com/blog/index.php/2007/10/04/microsoft-and-healthvaultcom/comment-page-1/#comment-40008</link>
		<dc:creator>product-innov8tor</dc:creator>
		<pubDate>Thu, 11 Oct 2007 11:28:26 +0000</pubDate>
		<guid isPermaLink="false">http://www.wikinomics.com/blog/index.php/2007/10/04/microsoft-and-healthvaultcom/#comment-40008</guid>
		<description>I believe Google will come up with advertising that is totally demand driven, that is to say consumer pull rather than push.

They are already well placed to take advantage of web tv, and have policies in place to limit the amount of visible targeted advertising appropriate to the web pages being displayed.

As Google seems to be a strongly collaborative company, we must hope and encourage them to stick to their principals in this respect.</description>
		<content:encoded><![CDATA[<p>I believe Google will come up with advertising that is totally demand driven, that is to say consumer pull rather than push.</p>
<p>They are already well placed to take advantage of web tv, and have policies in place to limit the amount of visible targeted advertising appropriate to the web pages being displayed.</p>
<p>As Google seems to be a strongly collaborative company, we must hope and encourage them to stick to their principals in this respect.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

