<?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: Monday Morning Update 11/12/07</title>
	<atom:link href="http://histalk2.com/2007/11/10/monday-morning-update-111207/feed/" rel="self" type="application/rss+xml" />
	<link>http://histalk2.com/2007/11/10/monday-morning-update-111207/</link>
	<description>Healthcare IT News and Opinion</description>
	<lastBuildDate>Thu, 18 Mar 2010 16:21:54 -0500</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Art_Vandelay</title>
		<link>http://histalk2.com/2007/11/10/monday-morning-update-111207/comment-page-1/#comment-423</link>
		<dc:creator>Art_Vandelay</dc:creator>
		<pubDate>Mon, 12 Nov 2007 11:21:41 +0000</pubDate>
		<guid isPermaLink="false">http://histalk2.com/2007/11/10/monday-morning-update-111207/#comment-423</guid>
		<description>Will - absolutely correct, I was reading into this, as-if this were a surprise after the application was bought and in-use. Even with demonstration, dry-run, or paper simulations of use-cases with the vendor or other customers, it is difficult to truly grasp the depth of trade-offs until the application is in testing or more often live use. The most challenging trade-offs are usually around those items the users take for granted (i.e., behind the scenes functions, basic system operations) such as device footprint or capabilities, authentication, reporting on data and discrete value interfacing.</description>
		<content:encoded><![CDATA[<p>Will &#8211; absolutely correct, I was reading into this, as-if this were a surprise after the application was bought and in-use. Even with demonstration, dry-run, or paper simulations of use-cases with the vendor or other customers, it is difficult to truly grasp the depth of trade-offs until the application is in testing or more often live use. The most challenging trade-offs are usually around those items the users take for granted (i.e., behind the scenes functions, basic system operations) such as device footprint or capabilities, authentication, reporting on data and discrete value interfacing.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Will Weider</title>
		<link>http://histalk2.com/2007/11/10/monday-morning-update-111207/comment-page-1/#comment-422</link>
		<dc:creator>Will Weider</dc:creator>
		<pubDate>Sun, 11 Nov 2007 21:03:26 +0000</pubDate>
		<guid isPermaLink="false">http://histalk2.com/2007/11/10/monday-morning-update-111207/#comment-422</guid>
		<description>The vendor in question is VISICU.  I suspect that concern came from one of my Ministry IT teammates.  If not, there is more than one customer asking for this.

Art, it is always a matter of traeoffs.  We have a very mature IT Assessment process, which includes looking at the required screen resolution.  But, sometimes leadership is compelled by the potential benefits (in this case patient safety) and they decide to live with some workaround, in this case additional devices to support this unique application.</description>
		<content:encoded><![CDATA[<p>The vendor in question is VISICU.  I suspect that concern came from one of my Ministry IT teammates.  If not, there is more than one customer asking for this.</p>
<p>Art, it is always a matter of traeoffs.  We have a very mature IT Assessment process, which includes looking at the required screen resolution.  But, sometimes leadership is compelled by the potential benefits (in this case patient safety) and they decide to live with some workaround, in this case additional devices to support this unique application.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Art_Vandelay</title>
		<link>http://histalk2.com/2007/11/10/monday-morning-update-111207/comment-page-1/#comment-421</link>
		<dc:creator>Art_Vandelay</dc:creator>
		<pubDate>Sun, 11 Nov 2007 13:12:25 +0000</pubDate>
		<guid isPermaLink="false">http://histalk2.com/2007/11/10/monday-morning-update-111207/#comment-421</guid>
		<description>My take on the 1280 resolution - where were your hardware technologists who do the basic reviews of the vendor product? I&#039;d hope the organization learns from this one and sets-up a checklist with the basics about what your organization can and does support (i.e., desktops, COWs, laptops, handhelds, Tablets, printers, labelers, all-in-one devices, servers, OS, database, middleware, other glue software programs like job schedulers, report writers).

Mr. HISTalk is right-on. The vendor has done their job. If this is a recurring issue, the smart vendors adapt and find a solution.</description>
		<content:encoded><![CDATA[<p>My take on the 1280 resolution &#8211; where were your hardware technologists who do the basic reviews of the vendor product? I&#8217;d hope the organization learns from this one and sets-up a checklist with the basics about what your organization can and does support (i.e., desktops, COWs, laptops, handhelds, Tablets, printers, labelers, all-in-one devices, servers, OS, database, middleware, other glue software programs like job schedulers, report writers).</p>
<p>Mr. HISTalk is right-on. The vendor has done their job. If this is a recurring issue, the smart vendors adapt and find a solution.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: MumpsMan</title>
		<link>http://histalk2.com/2007/11/10/monday-morning-update-111207/comment-page-1/#comment-420</link>
		<dc:creator>MumpsMan</dc:creator>
		<pubDate>Sun, 11 Nov 2007 03:54:52 +0000</pubDate>
		<guid isPermaLink="false">http://histalk2.com/2007/11/10/monday-morning-update-111207/#comment-420</guid>
		<description>I&#039;ve been put up in some of the seedier Madison hotels when I&#039;ve gone to WI...so hearing about Epic folks having to tolerate sub-par lodging warms my heart.  Not for any logical reason mind you, Epic had nothing to do with my crappy lodging, but whats good for the goose and all.  

A good rule of thumb - If you&#039;re going to be cheap, be cheap with the vendor first, and with your employees second.</description>
		<content:encoded><![CDATA[<p>I&#8217;ve been put up in some of the seedier Madison hotels when I&#8217;ve gone to WI&#8230;so hearing about Epic folks having to tolerate sub-par lodging warms my heart.  Not for any logical reason mind you, Epic had nothing to do with my crappy lodging, but whats good for the goose and all.  </p>
<p>A good rule of thumb &#8211; If you&#8217;re going to be cheap, be cheap with the vendor first, and with your employees second.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: HISReader</title>
		<link>http://histalk2.com/2007/11/10/monday-morning-update-111207/comment-page-1/#comment-419</link>
		<dc:creator>HISReader</dc:creator>
		<pubDate>Sun, 11 Nov 2007 02:52:40 +0000</pubDate>
		<guid isPermaLink="false">http://histalk2.com/2007/11/10/monday-morning-update-111207/#comment-419</guid>
		<description>RE: From Red: “Re: KUMED.  Their project manager (must be a Cerner lover) is putting the EPIC kids up at a 40-something buck a night motel.   

The place isn&#039;t bad.  If you&#039;re a reasonable person spending your own money, you wouldn&#039;t blink staying there  Why assume that every consultant needs a JW Marriott room at KUMEDs expense.  

Reasonable decision and a pretty decently run project all the way through.  That&#039;s the kind of decision making that keeps a customer healthy through a tough project.</description>
		<content:encoded><![CDATA[<p>RE: From Red: “Re: KUMED.  Their project manager (must be a Cerner lover) is putting the EPIC kids up at a 40-something buck a night motel.   </p>
<p>The place isn&#8217;t bad.  If you&#8217;re a reasonable person spending your own money, you wouldn&#8217;t blink staying there  Why assume that every consultant needs a JW Marriott room at KUMEDs expense.  </p>
<p>Reasonable decision and a pretty decently run project all the way through.  That&#8217;s the kind of decision making that keeps a customer healthy through a tough project.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
