<?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: MD Leader 1/15/09</title>
	<atom:link href="http://histalk2.com/2009/01/14/md-leader-11509/feed/" rel="self" type="application/rss+xml" />
	<link>http://histalk2.com/2009/01/14/md-leader-11509/</link>
	<description>Healthcare IT News and Opinion</description>
	<lastBuildDate>Tue, 22 May 2012 14:25:13 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3</generator>
	<item>
		<title>By: bignurse</title>
		<link>http://histalk2.com/2009/01/14/md-leader-11509/comment-page-1/#comment-3069</link>
		<dc:creator>bignurse</dc:creator>
		<pubDate>Thu, 15 Jan 2009 19:42:55 +0000</pubDate>
		<guid isPermaLink="false">http://histalk2.com/2009/01/14/md-leader-11509/#comment-3069</guid>
		<description>Hello Mr H,

What do you think about the Sunquest thread in the Discussion area?  Do you think it is wise for employees to sound off about their employer in a public discussion area like HISTalk?  I guess it wasn&#039;t so wise for the poster who got dismissed. Not everyone can be a Justin Deal.  Interested in your thoughts.

BN

[From Mr. HIStalk] I hope they&#039;re not using their real names and that someone wasn&#039;t axed because they were. Posting anti-employer rants is risky if you aren&#039;t absolutely certain you don&#039;t give yourself away, even by the subtle nature of what you said or when you said it (like the police, employers always look for someone with motive, which can narrow the field down more than you might think). And, I don&#039;t always run them, especially if they insult someone by name. If someone hates their employer that much, it&#039;s time to either find a new job or quit complaining. I&#039;ve been in the same position and my only regret was that I waited too long to leave because of inertia.</description>
		<content:encoded><![CDATA[<p>Hello Mr H,</p>
<p>What do you think about the Sunquest thread in the Discussion area?  Do you think it is wise for employees to sound off about their employer in a public discussion area like HISTalk?  I guess it wasn&#8217;t so wise for the poster who got dismissed. Not everyone can be a Justin Deal.  Interested in your thoughts.</p>
<p>BN</p>
<p>[From Mr. HIStalk] I hope they&#8217;re not using their real names and that someone wasn&#8217;t axed because they were. Posting anti-employer rants is risky if you aren&#8217;t absolutely certain you don&#8217;t give yourself away, even by the subtle nature of what you said or when you said it (like the police, employers always look for someone with motive, which can narrow the field down more than you might think). And, I don&#8217;t always run them, especially if they insult someone by name. If someone hates their employer that much, it&#8217;s time to either find a new job or quit complaining. I&#8217;ve been in the same position and my only regret was that I waited too long to leave because of inertia.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: MM</title>
		<link>http://histalk2.com/2009/01/14/md-leader-11509/comment-page-1/#comment-3068</link>
		<dc:creator>MM</dc:creator>
		<pubDate>Thu, 15 Jan 2009 18:46:20 +0000</pubDate>
		<guid isPermaLink="false">http://histalk2.com/2009/01/14/md-leader-11509/#comment-3068</guid>
		<description>&quot;Good process and leadership trumps bad software.&quot;

There are some many things wrong with this statement I don&#039;t no where to start.  Suffice it to say I completely disagree with this statement.

Nothing trumps &quot;bad software.&quot;</description>
		<content:encoded><![CDATA[<p>&#8220;Good process and leadership trumps bad software.&#8221;</p>
<p>There are some many things wrong with this statement I don&#8217;t no where to start.  Suffice it to say I completely disagree with this statement.</p>
<p>Nothing trumps &#8220;bad software.&#8221;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Esther</title>
		<link>http://histalk2.com/2009/01/14/md-leader-11509/comment-page-1/#comment-3065</link>
		<dc:creator>Esther</dc:creator>
		<pubDate>Thu, 15 Jan 2009 17:15:14 +0000</pubDate>
		<guid isPermaLink="false">http://histalk2.com/2009/01/14/md-leader-11509/#comment-3065</guid>
		<description>Great post!  I love it when the clinicians take ownership of the clinical projects.  Unfortunately that is not the norm in our organization but we&#039;re getting there.  My primary soapbox as CIO is that IT should not &#039;do it&#039; to them - if they want something they need to own it.  We are there to assist them in anyway we can. We have at least gotten to the point that we are no longer calling them IT projects but Clinical Technology projects.   When a technology project is planned/budgeted it shows up in capital as the department who is driving the implementation.</description>
		<content:encoded><![CDATA[<p>Great post!  I love it when the clinicians take ownership of the clinical projects.  Unfortunately that is not the norm in our organization but we&#8217;re getting there.  My primary soapbox as CIO is that IT should not &#8216;do it&#8217; to them &#8211; if they want something they need to own it.  We are there to assist them in anyway we can. We have at least gotten to the point that we are no longer calling them IT projects but Clinical Technology projects.   When a technology project is planned/budgeted it shows up in capital as the department who is driving the implementation.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Francisco Scaramanga</title>
		<link>http://histalk2.com/2009/01/14/md-leader-11509/comment-page-1/#comment-3063</link>
		<dc:creator>Francisco Scaramanga</dc:creator>
		<pubDate>Thu, 15 Jan 2009 16:23:41 +0000</pubDate>
		<guid isPermaLink="false">http://histalk2.com/2009/01/14/md-leader-11509/#comment-3063</guid>
		<description>I can understand that you don&#039;t want people padding their budget estimates to ensure 100% success, but I also understand why someone might bristle at having their project labeled a failure for completing work too far ahead of schedule or producing something at a lower cost than expected.  Much is learned during the course of a project, and it seems like you might inadvertently be disincentiving people from taking advantage of optimization opportunities.</description>
		<content:encoded><![CDATA[<p>I can understand that you don&#8217;t want people padding their budget estimates to ensure 100% success, but I also understand why someone might bristle at having their project labeled a failure for completing work too far ahead of schedule or producing something at a lower cost than expected.  Much is learned during the course of a project, and it seems like you might inadvertently be disincentiving people from taking advantage of optimization opportunities.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Forward Solutions</title>
		<link>http://histalk2.com/2009/01/14/md-leader-11509/comment-page-1/#comment-3061</link>
		<dc:creator>Forward Solutions</dc:creator>
		<pubDate>Thu, 15 Jan 2009 15:24:06 +0000</pubDate>
		<guid isPermaLink="false">http://histalk2.com/2009/01/14/md-leader-11509/#comment-3061</guid>
		<description>An interesting post -- A partner and I are ramping up to start a consulting practice sharing best practices for HIT projects.  We are consistently amazed at what a little project management rigor can do to keep the ship on course. 

Thanks, always interested to hear success stories and lessons learned on HIT projects.</description>
		<content:encoded><![CDATA[<p>An interesting post &#8212; A partner and I are ramping up to start a consulting practice sharing best practices for HIT projects.  We are consistently amazed at what a little project management rigor can do to keep the ship on course. </p>
<p>Thanks, always interested to hear success stories and lessons learned on HIT projects.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

