<?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:itunes="http://www.itunes.com/dtds/podcast-1.0.dtd"
	xmlns:media="http://search.yahoo.com/mrss/"
	>
<channel>
	<title>Comments on: U of M Physician&#8217;s Ties to Medical Device Company Scrutinized</title>
	<atom:link href="http://www.doctorpundit.com/index.php/2009/07/29/u-of-m-physicians-ties-to-medical-device-company-scrutinized/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.doctorpundit.com/index.php/2009/07/29/u-of-m-physicians-ties-to-medical-device-company-scrutinized/</link>
	<description>Healthcare &#38; Science Policy Blog</description>
	<lastBuildDate>Tue, 24 Jan 2012 14:51:45 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
<xhtml:meta xmlns:xhtml="http://www.w3.org/1999/xhtml" name="robots" content="noindex" />
	<item>
		<title>By: Academic Physician Resigns from Board Amid Problematic Ties to Device Company &#124; DOCTOR PUNDIT</title>
		<link>http://www.doctorpundit.com/index.php/2009/07/29/u-of-m-physicians-ties-to-medical-device-company-scrutinized/comment-page-1/#comment-2115</link>
		<dc:creator>Academic Physician Resigns from Board Amid Problematic Ties to Device Company &#124; DOCTOR PUNDIT</dc:creator>
		<pubDate>Tue, 25 Aug 2009 11:05:19 +0000</pubDate>
		<guid isPermaLink="false">http://www.doctorpundit.com/?p=2891#comment-2115</guid>
		<description>[...] the brouhaha over a congressional probe into over $1 million in payments from a Twin Cities-based medical device company, a prominent and [...]</description>
		<content:encoded><![CDATA[<p>[...] the brouhaha over a congressional probe into over $1 million in payments from a Twin Cities-based medical device company, a prominent and [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>

