<?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: Together again: KP and IBM.</title>
	<atom:link href="http://blog.fixkp.org/2007/10/29/together-again-kp-and-ibm/503/feed" rel="self" type="application/rss+xml" />
	<link>http://blog.fixkp.org/2007/10/29/together-again-kp-and-ibm/503</link>
	<description>FixKP: the unofficial Kaiser Permanente blog at blog.fixkp.org</description>
	<lastBuildDate>Sun, 23 Dec 2007 04:28:33 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: justen :: Epic: In for a penny, in for a pound?</title>
		<link>http://blog.fixkp.org/2007/10/29/together-again-kp-and-ibm/503/comment-page-1#comment-5619</link>
		<dc:creator>justen :: Epic: In for a penny, in for a pound?</dc:creator>
		<pubDate>Fri, 16 Nov 2007 15:03:04 +0000</pubDate>
		<guid isPermaLink="false">http://blog.fixkp.org/2007/10/29/together-again-kp-and-ibm/503#comment-5619</guid>
		<description>[...] forth, which led, in part, to the poor reliability of HealthConnect. The issue, as I alluded to in the post on IBM and KP getting back together, is that Epic either didn&#8217;t try or was ineffective when it came to helping Kaiser Permanente [...]</description>
		<content:encoded><![CDATA[<p>[...] forth, which led, in part, to the poor reliability of HealthConnect. The issue, as I alluded to in the post on IBM and KP getting back together, is that Epic either didn&#8217;t try or was ineffective when it came to helping Kaiser Permanente [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
