<?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: News 7/13/07</title>
	<atom:link href="http://histalk2.com/2007/07/12/news-71307/feed/" rel="self" type="application/rss+xml" />
	<link>http://histalk2.com/2007/07/12/news-71307/</link>
	<description>Healthcare IT News and Opinion</description>
	<lastBuildDate>Wed, 08 Feb 2012 23:08:39 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3</generator>
	<item>
		<title>By: Kate Moxie</title>
		<link>http://histalk2.com/2007/07/12/news-71307/comment-page-1/#comment-80</link>
		<dc:creator>Kate Moxie</dc:creator>
		<pubDate>Thu, 19 Jul 2007 20:48:08 +0000</pubDate>
		<guid isPermaLink="false">http://histalk2.com/2007/07/12/news-71307/#comment-80</guid>
		<description>RE:  Bob Saccamano: “Re: CHOP.
I heard from a friend at CHOP that the downtime was due to a power &quot;oops&quot; in the data center and it affected lots of apps, not just Epic.</description>
		<content:encoded><![CDATA[<p>RE:  Bob Saccamano: “Re: CHOP.<br />
I heard from a friend at CHOP that the downtime was due to a power &#8220;oops&#8221; in the data center and it affected lots of apps, not just Epic.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: observer</title>
		<link>http://histalk2.com/2007/07/12/news-71307/comment-page-1/#comment-64</link>
		<dc:creator>observer</dc:creator>
		<pubDate>Sat, 14 Jul 2007 14:08:52 +0000</pubDate>
		<guid isPermaLink="false">http://histalk2.com/2007/07/12/news-71307/#comment-64</guid>
		<description>I heard that there is a lawyer in madison that specifically works with ex-Epic employees and HR issues.</description>
		<content:encoded><![CDATA[<p>I heard that there is a lawyer in madison that specifically works with ex-Epic employees and HR issues.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: p_anon</title>
		<link>http://histalk2.com/2007/07/12/news-71307/comment-page-1/#comment-62</link>
		<dc:creator>p_anon</dc:creator>
		<pubDate>Fri, 13 Jul 2007 13:50:43 +0000</pubDate>
		<guid isPermaLink="false">http://histalk2.com/2007/07/12/news-71307/#comment-62</guid>
		<description>Re: Apple. Your reader gave an excellent characterization of Windows, circa 1995. Actually, the &quot;stole all ideas from Apple&quot; bullet point was from even earlier--the 80&#039;s. The one thing your reader got 100% right is that Microsoft produces classless/crass products, with the Zune being the prime example. It&#039;s like an iPod, but worse in almost every way.

But I&#039;m not really here to talk about that. I am actually interested in discussing the iPhone, or the &quot;mobile platform&quot; in whatever form it takes, whether it&#039;s the admittedly awesome iPhone or BlackBerry phones or Windows Mobile phones. This has potential to open up several new opportunities in healthcare. I&#039;m thinking of physician e-signing specifically--imagine the physician can now do everything they need on the little phone.

I suppose the better way to envision the (ever-improving) mobile platform is to think of it as POTENTIALLY as useful as e-mail on a BlackBerry, but in a more general sense. Just like we make jokes about executives reading their email during meetings, we can IN THE FUTURE possibly make jokes about how &gt; is always &gt; on their phone. The point is, the potential is there, for something...not sure exactly what at this point.</description>
		<content:encoded><![CDATA[<p>Re: Apple. Your reader gave an excellent characterization of Windows, circa 1995. Actually, the &#8220;stole all ideas from Apple&#8221; bullet point was from even earlier&#8211;the 80&#8242;s. The one thing your reader got 100% right is that Microsoft produces classless/crass products, with the Zune being the prime example. It&#8217;s like an iPod, but worse in almost every way.</p>
<p>But I&#8217;m not really here to talk about that. I am actually interested in discussing the iPhone, or the &#8220;mobile platform&#8221; in whatever form it takes, whether it&#8217;s the admittedly awesome iPhone or BlackBerry phones or Windows Mobile phones. This has potential to open up several new opportunities in healthcare. I&#8217;m thinking of physician e-signing specifically&#8211;imagine the physician can now do everything they need on the little phone.</p>
<p>I suppose the better way to envision the (ever-improving) mobile platform is to think of it as POTENTIALLY as useful as e-mail on a BlackBerry, but in a more general sense. Just like we make jokes about executives reading their email during meetings, we can IN THE FUTURE possibly make jokes about how &gt; is always &gt; on their phone. The point is, the potential is there, for something&#8230;not sure exactly what at this point.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Epic_Escapee</title>
		<link>http://histalk2.com/2007/07/12/news-71307/comment-page-1/#comment-61</link>
		<dc:creator>Epic_Escapee</dc:creator>
		<pubDate>Fri, 13 Jul 2007 13:38:13 +0000</pubDate>
		<guid isPermaLink="false">http://histalk2.com/2007/07/12/news-71307/#comment-61</guid>
		<description>The Epic non competes are different depending on position and when the person joined the company.  When I started, the non compete I signed was that I couldn&#039;t work for customers of Epic for six months after I left Epic or until I had been at Epic for three years, which ever came first.

I&#039;ve seen a similar situation to the original Epic comment.  An Epic customer hired an ex Epic employee as a consultant.  When Epic found out, they told the customer that they would sue them if they didn&#039;t stop working with the consultant.  In fact, they specifically stated that they could not allow the consultant to access any documentation, screen shots or access to the system.  The consultant was out of their non compete and had every right to do the work (IMO).  Basically it sounded like Epic railroaded this poor guy out of a job.  The kicker is that Epic promised to allocate extra resources (Epic internal) to the customer to work on the issues that the consultant was but then never did.  That actually wasn&#039;t that all that uncommon of an occurrence while I was there unless of course your company initials were KP.  After getting out and working in the non Epic world, it&#039;s amazing that Epic doesn&#039;t have more deinstalls.</description>
		<content:encoded><![CDATA[<p>The Epic non competes are different depending on position and when the person joined the company.  When I started, the non compete I signed was that I couldn&#8217;t work for customers of Epic for six months after I left Epic or until I had been at Epic for three years, which ever came first.</p>
<p>I&#8217;ve seen a similar situation to the original Epic comment.  An Epic customer hired an ex Epic employee as a consultant.  When Epic found out, they told the customer that they would sue them if they didn&#8217;t stop working with the consultant.  In fact, they specifically stated that they could not allow the consultant to access any documentation, screen shots or access to the system.  The consultant was out of their non compete and had every right to do the work (IMO).  Basically it sounded like Epic railroaded this poor guy out of a job.  The kicker is that Epic promised to allocate extra resources (Epic internal) to the customer to work on the issues that the consultant was but then never did.  That actually wasn&#8217;t that all that uncommon of an occurrence while I was there unless of course your company initials were KP.  After getting out and working in the non Epic world, it&#8217;s amazing that Epic doesn&#8217;t have more deinstalls.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Forgot the cutesy ex-epic name I used last time</title>
		<link>http://histalk2.com/2007/07/12/news-71307/comment-page-1/#comment-59</link>
		<dc:creator>Forgot the cutesy ex-epic name I used last time</dc:creator>
		<pubDate>Fri, 13 Jul 2007 03:34:54 +0000</pubDate>
		<guid isPermaLink="false">http://histalk2.com/2007/07/12/news-71307/#comment-59</guid>
		<description>&lt;p&gt;Unfortunately Epic has a triple lock on employees leaving: a one year non-compete against working or consulting for any of the major vendors or anyone who&#039;s ever contacted sales, customers agree not to employee ex-epic (not sure of the details) and only consultants working at approved (read as supporting the non-compete) firms can maintain their certifications.&lt;/p&gt;
&lt;p&gt;Which means most ex-employees work at Walmart for a year and then consult or find a company not on the non-compete and never look back (I chose the latter).&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>Unfortunately Epic has a triple lock on employees leaving: a one year non-compete against working or consulting for any of the major vendors or anyone who&#8217;s ever contacted sales, customers agree not to employee ex-epic (not sure of the details) and only consultants working at approved (read as supporting the non-compete) firms can maintain their certifications.</p>
<p>Which means most ex-employees work at Walmart for a year and then consult or find a company not on the non-compete and never look back (I chose the latter).</p>
]]></content:encoded>
	</item>
</channel>
</rss>

