<?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 10/24/08</title>
	<atom:link href="http://histalk2.com/2008/10/23/news-102408/feed/" rel="self" type="application/rss+xml" />
	<link>http://histalk2.com/2008/10/23/news-102408/</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: Lazlo Hollyfeld</title>
		<link>http://histalk2.com/2008/10/23/news-102408/comment-page-1/#comment-2520</link>
		<dc:creator>Lazlo Hollyfeld</dc:creator>
		<pubDate>Sat, 25 Oct 2008 15:03:38 +0000</pubDate>
		<guid isPermaLink="false">http://histalk2.com/2008/10/23/news-102408/#comment-2520</guid>
		<description>Always enjoyed the MGMA conference more than the HIMSS conference.  Less flash and ridiculous booths because the individual clients at MGMA just don&#039;t have the same cash to spend.  Plus, MGMA just struck me as being a better run and more disciplined group.  Maybe because MGMA has a more direct representation model - MGMA represents medical practices (docs) while HIMSS is a technology group whose clients are hospitals.</description>
		<content:encoded><![CDATA[<p>Always enjoyed the MGMA conference more than the HIMSS conference.  Less flash and ridiculous booths because the individual clients at MGMA just don&#8217;t have the same cash to spend.  Plus, MGMA just struck me as being a better run and more disciplined group.  Maybe because MGMA has a more direct representation model &#8211; MGMA represents medical practices (docs) while HIMSS is a technology group whose clients are hospitals.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: The PACS Designer</title>
		<link>http://histalk2.com/2008/10/23/news-102408/comment-page-1/#comment-2519</link>
		<dc:creator>The PACS Designer</dc:creator>
		<pubDate>Fri, 24 Oct 2008 19:42:43 +0000</pubDate>
		<guid isPermaLink="false">http://histalk2.com/2008/10/23/news-102408/#comment-2519</guid>
		<description>DrM:

Thanks for the compliment!  I try to be brief and to the point with my HIStalk postings by clearly defining a concept that will improve understanding by readers.</description>
		<content:encoded><![CDATA[<p>DrM:</p>
<p>Thanks for the compliment!  I try to be brief and to the point with my HIStalk postings by clearly defining a concept that will improve understanding by readers.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: DrM</title>
		<link>http://histalk2.com/2008/10/23/news-102408/comment-page-1/#comment-2517</link>
		<dc:creator>DrM</dc:creator>
		<pubDate>Fri, 24 Oct 2008 16:48:10 +0000</pubDate>
		<guid isPermaLink="false">http://histalk2.com/2008/10/23/news-102408/#comment-2517</guid>
		<description>The WOA article is a little misleading (particularly the &quot;shorthand formula&quot;).  SOAs are pretty much always &quot;www-based&quot; (whatever that means, very non-technical description), and REST and SOAP are two different ways to approach developing it.  The similarity of the acronyms SOA and SOAP is unfortunate, they&#039;re not synonymous; SOA is an architectural principle (the  A is for Architecture), and SOAP is a protocol (the P) just like HTTP. 

TPD&#039;s description is much better.  WOA is different than SOA because it integrates at the application/resource layer with the existing web front-end, rather than at the &quot;service&quot; layer (i.e., data or business logic).  REST can be used for both, SOAP cannot.  Web portals have been doing WOA for over a decade now without it having a term, in fact most of the ads you see use the same basic concept that a user can&#039;t tell the difference about where something came from, and probably doesn&#039;t actually care.  The clinical web portal we just put in uses both SOA and WOA pretty effectively in our best-of-breed clinical environment.</description>
		<content:encoded><![CDATA[<p>The WOA article is a little misleading (particularly the &#8220;shorthand formula&#8221;).  SOAs are pretty much always &#8220;www-based&#8221; (whatever that means, very non-technical description), and REST and SOAP are two different ways to approach developing it.  The similarity of the acronyms SOA and SOAP is unfortunate, they&#8217;re not synonymous; SOA is an architectural principle (the  A is for Architecture), and SOAP is a protocol (the P) just like HTTP. </p>
<p>TPD&#8217;s description is much better.  WOA is different than SOA because it integrates at the application/resource layer with the existing web front-end, rather than at the &#8220;service&#8221; layer (i.e., data or business logic).  REST can be used for both, SOAP cannot.  Web portals have been doing WOA for over a decade now without it having a term, in fact most of the ads you see use the same basic concept that a user can&#8217;t tell the difference about where something came from, and probably doesn&#8217;t actually care.  The clinical web portal we just put in uses both SOA and WOA pretty effectively in our best-of-breed clinical environment.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Julia</title>
		<link>http://histalk2.com/2008/10/23/news-102408/comment-page-1/#comment-2515</link>
		<dc:creator>Julia</dc:creator>
		<pubDate>Fri, 24 Oct 2008 14:36:05 +0000</pubDate>
		<guid isPermaLink="false">http://histalk2.com/2008/10/23/news-102408/#comment-2515</guid>
		<description>Yes, the &quot;red flag&quot; ID theft policy and procedure for hospitals will be &quot;onerous&quot; for hospitals.  The regs will be in place on 11/01.

[From Mr. HIStalk] Actually, according to a &lt;a href=&quot;http://www.ftc.gov/opa/2008/10/redflags.shtm&quot; rel=&quot;nofollow&quot;&gt;link&lt;/a&gt; sent from a reader, FTC has delayed implementation of the rule for six months.</description>
		<content:encoded><![CDATA[<p>Yes, the &#8220;red flag&#8221; ID theft policy and procedure for hospitals will be &#8220;onerous&#8221; for hospitals.  The regs will be in place on 11/01.</p>
<p>[From Mr. HIStalk] Actually, according to a <a href="http://www.ftc.gov/opa/2008/10/redflags.shtm" rel="nofollow">link</a> sent from a reader, FTC has delayed implementation of the rule for six months.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: From Missouri</title>
		<link>http://histalk2.com/2008/10/23/news-102408/comment-page-1/#comment-2514</link>
		<dc:creator>From Missouri</dc:creator>
		<pubDate>Fri, 24 Oct 2008 13:53:26 +0000</pubDate>
		<guid isPermaLink="false">http://histalk2.com/2008/10/23/news-102408/#comment-2514</guid>
		<description>RE: BRIDGEPORT CIO POSITION

Is this facility still outsourced to ACS (formerly Superior Consultant)?</description>
		<content:encoded><![CDATA[<p>RE: BRIDGEPORT CIO POSITION</p>
<p>Is this facility still outsourced to ACS (formerly Superior Consultant)?</p>
]]></content:encoded>
	</item>
</channel>
</rss>

