<?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: Guest Article: IT Security and Record Management in Healthcare</title>
	<atom:link href="http://www.healthcareguy.com/2008/03/13/guest-article-it-security-and-record-management-in-healthcare/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.healthcareguy.com/2008/03/13/guest-article-it-security-and-record-management-in-healthcare/</link>
	<description>Shahid&#039;s healthcare IT, EMR, EHR, PHR, medical content, and document managment advisory service. Enjoy.</description>
	<lastBuildDate>Thu, 09 Feb 2012 13:50:00 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.1.3</generator>
	<item>
		<title>By: alex farguson</title>
		<link>http://www.healthcareguy.com/2008/03/13/guest-article-it-security-and-record-management-in-healthcare/comment-page-1/#comment-689</link>
		<dc:creator>alex farguson</dc:creator>
		<pubDate>Mon, 13 Apr 2009 04:22:07 +0000</pubDate>
		<guid isPermaLink="false">http://www.healthcareguy.com/index.php/archives/417#comment-689</guid>
		<description>Just grabbed the feed... thanks for posting this.</description>
		<content:encoded><![CDATA[<p>Just grabbed the feed&#8230; thanks for posting this.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Sclero Nurse</title>
		<link>http://www.healthcareguy.com/2008/03/13/guest-article-it-security-and-record-management-in-healthcare/comment-page-1/#comment-688</link>
		<dc:creator>Sclero Nurse</dc:creator>
		<pubDate>Mon, 24 Mar 2008 05:43:45 +0000</pubDate>
		<guid isPermaLink="false">http://www.healthcareguy.com/index.php/archives/417#comment-688</guid>
		<description>I was talking with some co-workers about this very issue the other day at lunch.  We all came to the conclusion that none of use had seen a system out there that could adequately deal with these issues.  Its surprising that nobody has created a workable system considering the immense amount of potential revenue that is out there in the medical industry.  One of my co-workers brought up a CRM program called Interaction that is very popular amongst lawyers and integrates Lexis Nexis.  It would be nice if something like this program could be put in place for patient information management.</description>
		<content:encoded><![CDATA[<p>I was talking with some co-workers about this very issue the other day at lunch.  We all came to the conclusion that none of use had seen a system out there that could adequately deal with these issues.  Its surprising that nobody has created a workable system considering the immense amount of potential revenue that is out there in the medical industry.  One of my co-workers brought up a CRM program called Interaction that is very popular amongst lawyers and integrates Lexis Nexis.  It would be nice if something like this program could be put in place for patient information management.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: François Jean</title>
		<link>http://www.healthcareguy.com/2008/03/13/guest-article-it-security-and-record-management-in-healthcare/comment-page-1/#comment-687</link>
		<dc:creator>François Jean</dc:creator>
		<pubDate>Tue, 18 Mar 2008 15:58:31 +0000</pubDate>
		<guid isPermaLink="false">http://www.healthcareguy.com/index.php/archives/417#comment-687</guid>
		<description>An article that shows how the current information flow does not protect the privacy of the patient:

http://www.healthcareitnews.com/story.cms?id=8904

In that case you know who got access to unauthorized information but they were not able to prevent it in first place.

Maybe the problem reside in the balance between patient safety (the need to see the medical information for proper treatment) and patient privacy (hide medical information to unauthorized access).</description>
		<content:encoded><![CDATA[<p>An article that shows how the current information flow does not protect the privacy of the patient:</p>
<p><a href="http://www.healthcareitnews.com/story.cms?id=8904" rel="nofollow">http://www.healthcareitnews.com/story.cms?id=8904</a></p>
<p>In that case you know who got access to unauthorized information but they were not able to prevent it in first place.</p>
<p>Maybe the problem reside in the balance between patient safety (the need to see the medical information for proper treatment) and patient privacy (hide medical information to unauthorized access).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rich Olson</title>
		<link>http://www.healthcareguy.com/2008/03/13/guest-article-it-security-and-record-management-in-healthcare/comment-page-1/#comment-686</link>
		<dc:creator>Rich Olson</dc:creator>
		<pubDate>Fri, 14 Mar 2008 03:39:57 +0000</pubDate>
		<guid isPermaLink="false">http://www.healthcareguy.com/index.php/archives/417#comment-686</guid>
		<description>Before HIPAA, every alleged breach in privacy was open to local adjudication.  Unfortunately, it seems  HIPAA, while making an attempt to codify and standardize privacy requirements, leaves plenty of opening for further litigation.  I notice the proposed HIT federal budget included 13 positions for prosecuting HIPAA violations.

One vexing practical issue, the good old patient identifier prohibition.  If the goal is a National Health Information Network, how in the world can a person&#039;s records be linked without a key field?  Can your firm design an encrypted form of the SSN, or whatever, that keeps prying novice eyes from mass identity theft, yet allows massive livesaving and time/resource-saving interoperability?</description>
		<content:encoded><![CDATA[<p>Before HIPAA, every alleged breach in privacy was open to local adjudication.  Unfortunately, it seems  HIPAA, while making an attempt to codify and standardize privacy requirements, leaves plenty of opening for further litigation.  I notice the proposed HIT federal budget included 13 positions for prosecuting HIPAA violations.</p>
<p>One vexing practical issue, the good old patient identifier prohibition.  If the goal is a National Health Information Network, how in the world can a person&#8217;s records be linked without a key field?  Can your firm design an encrypted form of the SSN, or whatever, that keeps prying novice eyes from mass identity theft, yet allows massive livesaving and time/resource-saving interoperability?</p>
]]></content:encoded>
	</item>
</channel>
</rss>

