<?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: If your engineers and DBAs can see medical data, it&#039;s neither private nor secure</title>
	<atom:link href="http://www.healthcareguy.com/2006/01/15/if-your-engineers-and-dbas-can-see-medical-data-its-neither-private-nor-secure/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.healthcareguy.com/2006/01/15/if-your-engineers-and-dbas-can-see-medical-data-its-neither-private-nor-secure/</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: Shahid N. Shah</title>
		<link>http://www.healthcareguy.com/2006/01/15/if-your-engineers-and-dbas-can-see-medical-data-its-neither-private-nor-secure/comment-page-1/#comment-105</link>
		<dc:creator>Shahid N. Shah</dc:creator>
		<pubDate>Thu, 19 Jan 2006 03:48:34 +0000</pubDate>
		<guid isPermaLink="false">http://www.healthcareguy.com/?p=101#comment-105</guid>
		<description>Thanks. I hope to have my part II of this article out sometime this week or early next week.</description>
		<content:encoded><![CDATA[<p>Thanks. I hope to have my part II of this article out sometime this week or early next week.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: techguy</title>
		<link>http://www.healthcareguy.com/2006/01/15/if-your-engineers-and-dbas-can-see-medical-data-its-neither-private-nor-secure/comment-page-1/#comment-104</link>
		<dc:creator>techguy</dc:creator>
		<pubDate>Thu, 19 Jan 2006 03:08:28 +0000</pubDate>
		<guid isPermaLink="false">http://www.healthcareguy.com/?p=101#comment-104</guid>
		<description>You post some really interesting questions.  I look forward to seeing the data fortress that you offer in your next article.

I&#039;ve often considered what it meant that I have complete access to the database with no logging when I do queries directly on the database.  I&#039;m not sure the best way to manage that other than creating a unique database login which tracks it.  Although I don&#039;t think that the logs for SQL Server track changes like they should for HIPAA compliance.</description>
		<content:encoded><![CDATA[<p>You post some really interesting questions.  I look forward to seeing the data fortress that you offer in your next article.</p>
<p>I&#8217;ve often considered what it meant that I have complete access to the database with no logging when I do queries directly on the database.  I&#8217;m not sure the best way to manage that other than creating a unique database login which tracks it.  Although I don&#8217;t think that the logs for SQL Server track changes like they should for HIPAA compliance.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

