<?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 for TechNation</title>
	<atom:link href="http://1technation.com/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://1technation.com</link>
	<description>Empowering the Biomedical/CE Professional</description>
	<lastBuildDate>Thu, 16 Feb 2012 18:27:30 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.1.3</generator>
	<item>
		<title>Comment on IT Update by Buzzword Busting: The Cloud &#187; eProtex Blog</title>
		<link>http://1technation.com/buzzword-busting-cloud/#comment-375</link>
		<dc:creator>Buzzword Busting: The Cloud &#187; eProtex Blog</dc:creator>
		<pubDate>Thu, 16 Feb 2012 18:27:30 +0000</pubDate>
		<guid isPermaLink="false">http://1technation.com/?p=2064#comment-375</guid>
		<description>[...] Chief Security Officer Derek Brost talks to TechNation about Cloud computing misconceptions, risks, and patient data implications. Take a read right [...]</description>
		<content:encoded><![CDATA[<p>[...] Chief Security Officer Derek Brost talks to TechNation about Cloud computing misconceptions, risks, and patient data implications. Take a read right [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on IT Update by Securely limiting medical device Internet and remote access &#187; eProtex Blog</title>
		<link>http://1technation.com/securely-limiting-medical-device-internet-remote-access/#comment-373</link>
		<dc:creator>Securely limiting medical device Internet and remote access &#187; eProtex Blog</dc:creator>
		<pubDate>Wed, 15 Feb 2012 21:00:28 +0000</pubDate>
		<guid isPermaLink="false">http://1technation.com/?p=1874#comment-373</guid>
		<description>[...] (This article by Derek Brost, eProtex Chief Security Officer, was originally featured in TechNation.) [...]</description>
		<content:encoded><![CDATA[<p>[...] (This article by Derek Brost, eProtex Chief Security Officer, was originally featured in TechNation.) [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on IT Update &#124; Derek Brost by Securely limiting medical device Internet and remote access &#187; eProtex Blog</title>
		<link>http://1technation.com/update-derek-brost-december-2011/#comment-358</link>
		<dc:creator>Securely limiting medical device Internet and remote access &#187; eProtex Blog</dc:creator>
		<pubDate>Thu, 12 Jan 2012 14:33:16 +0000</pubDate>
		<guid isPermaLink="false">http://1technation.com/?p=1740#comment-358</guid>
		<description>[...] month’s IT Update (TechNation magazine) addressed how a few key network infrastructure systems facilitate data [...]</description>
		<content:encoded><![CDATA[<p>[...] month’s IT Update (TechNation magazine) addressed how a few key network infrastructure systems facilitate data [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Contact Us by Roger Bowles</title>
		<link>http://1technation.com/contact-us/#comment-352</link>
		<dc:creator>Roger Bowles</dc:creator>
		<pubDate>Wed, 07 Dec 2011 19:01:28 +0000</pubDate>
		<guid isPermaLink="false">http://community.theornation.com/?page_id=400#comment-352</guid>
		<description>The Vault- Dynatech Defib Analyzer</description>
		<content:encoded><![CDATA[<p>The Vault- Dynatech Defib Analyzer</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Contact Us by Katherine Hay</title>
		<link>http://1technation.com/contact-us/#comment-351</link>
		<dc:creator>Katherine Hay</dc:creator>
		<pubDate>Wed, 07 Dec 2011 18:02:17 +0000</pubDate>
		<guid isPermaLink="false">http://community.theornation.com/?page_id=400#comment-351</guid>
		<description>The answer to the Vault question for December is a Dyna Tech Nevada Model PEI 3100A Defib Analyzer</description>
		<content:encoded><![CDATA[<p>The answer to the Vault question for December is a Dyna Tech Nevada Model PEI 3100A Defib Analyzer</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Expert Advice &#124; November 2011 by Felix Gorney</title>
		<link>http://1technation.com/medical-equipment-owners-selfdetermination-medical-device-maintenance-repair/#comment-342</link>
		<dc:creator>Felix Gorney</dc:creator>
		<pubDate>Thu, 17 Nov 2011 13:18:13 +0000</pubDate>
		<guid isPermaLink="false">http://1technation.com/?p=1601#comment-342</guid>
		<description>Access to owner service, tools, training, software, tech support and applications support needs to be part of the purchase agreement. That is the only time when the purchaser has the upper hand in any negotiations. If an OEM makes it difficult to service equipment, we need to quit buying their products. Some OEM&#039;s do better than others in this regard. In one recent situation we were changing IP addresses on imaging equipment. With one OEM, the user could make the necessary changes with no service key necessary. With another, only the OEM&#039;s service personnel could do this, via a long drawn out procedure. This not only limits who can do what should be a routine procedure, but also is poor software design if such chages affect how a vendors systems integrate with eachother. DICOM has been around for quite a while now.</description>
		<content:encoded><![CDATA[<p>Access to owner service, tools, training, software, tech support and applications support needs to be part of the purchase agreement. That is the only time when the purchaser has the upper hand in any negotiations. If an OEM makes it difficult to service equipment, we need to quit buying their products. Some OEM&#8217;s do better than others in this regard. In one recent situation we were changing IP addresses on imaging equipment. With one OEM, the user could make the necessary changes with no service key necessary. With another, only the OEM&#8217;s service personnel could do this, via a long drawn out procedure. This not only limits who can do what should be a routine procedure, but also is poor software design if such chages affect how a vendors systems integrate with eachother. DICOM has been around for quite a while now.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on IT Update &#124; November 2011 by Antivirus Software on Medical Devices &#187; eProtex Blog</title>
		<link>http://1technation.com/antivirus-software-medical-devices/#comment-336</link>
		<dc:creator>Antivirus Software on Medical Devices &#187; eProtex Blog</dc:creator>
		<pubDate>Mon, 14 Nov 2011 14:12:02 +0000</pubDate>
		<guid isPermaLink="false">http://1technation.com/?p=1593#comment-336</guid>
		<description>[...] article, written by our very own Derek Brost, first appeared in TechNation [...]</description>
		<content:encoded><![CDATA[<p>[...] article, written by our very own Derek Brost, first appeared in TechNation [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on The Roman Review &#124; September by Steve Davis</title>
		<link>http://1technation.com/effective-presentation-skills/#comment-327</link>
		<dc:creator>Steve Davis</dc:creator>
		<pubDate>Fri, 04 Nov 2011 22:54:51 +0000</pubDate>
		<guid isPermaLink="false">http://1technation.com/?p=1144#comment-327</guid>
		<description>Thanks Manny!  Great advice, I do make presentations to the Cs, and Navy Command Officers in my current role, and  will continue to utilize your advice and modify my presentation with consigliar advice you&#039;ve provided.</description>
		<content:encoded><![CDATA[<p>Thanks Manny!  Great advice, I do make presentations to the Cs, and Navy Command Officers in my current role, and  will continue to utilize your advice and modify my presentation with consigliar advice you&#8217;ve provided.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on The Roman Review &#124; October 2011 by Steve Davis</title>
		<link>http://1technation.com/responsibility-authority-accountability/#comment-326</link>
		<dc:creator>Steve Davis</dc:creator>
		<pubDate>Fri, 04 Nov 2011 22:24:06 +0000</pubDate>
		<guid isPermaLink="false">http://1technation.com/?p=1454#comment-326</guid>
		<description>Manny, It was great to visit with you at the 2011 AAMI Conference, and wonderful to read your words of wisdom this evening.  I plan on sharing your posts with my staff, so they may share in CREST&#039;s gem.  Thanks again for being a leader among leaders in our industry and sharing your guidance!</description>
		<content:encoded><![CDATA[<p>Manny, It was great to visit with you at the 2011 AAMI Conference, and wonderful to read your words of wisdom this evening.  I plan on sharing your posts with my staff, so they may share in CREST&#8217;s gem.  Thanks again for being a leader among leaders in our industry and sharing your guidance!</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Expert Advice &#124; November 2011 by Chris Salberg</title>
		<link>http://1technation.com/medical-equipment-owners-selfdetermination-medical-device-maintenance-repair/#comment-321</link>
		<dc:creator>Chris Salberg</dc:creator>
		<pubDate>Fri, 04 Nov 2011 07:37:56 +0000</pubDate>
		<guid isPermaLink="false">http://1technation.com/?p=1601#comment-321</guid>
		<description>Simply awesome! All we would really need to do is place &quot;medical device&quot; in place of auto and there it is....the 2011 Medical Device Service and Maintenance Freedom Act! This is obviously not the first time this subject has crossed my mind over the past 23 years of servicing diagnostic imaging equipment and I doubt it will be the last....however????? At one point and time, many years ago, I heard about a class action suit filed by ISO&#039;s against certain equipment manufacturer&#039;s for gaining access to service literature and / or service passwords. I do not know or remember the outcome to that event or if it was just wishful thinking. Could you shed some light upon that suit.....or if it even did happen? Thanks, great article!</description>
		<content:encoded><![CDATA[<p>Simply awesome! All we would really need to do is place &#8220;medical device&#8221; in place of auto and there it is&#8230;.the 2011 Medical Device Service and Maintenance Freedom Act! This is obviously not the first time this subject has crossed my mind over the past 23 years of servicing diagnostic imaging equipment and I doubt it will be the last&#8230;.however????? At one point and time, many years ago, I heard about a class action suit filed by ISO&#8217;s against certain equipment manufacturer&#8217;s for gaining access to service literature and / or service passwords. I do not know or remember the outcome to that event or if it was just wishful thinking. Could you shed some light upon that suit&#8230;..or if it even did happen? Thanks, great article!</p>
]]></content:encoded>
	</item>
</channel>
</rss>

