<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xml:base="http://www.fiercehealthcare.com" xmlns:dc="http://purl.org/dc/elements/1.1/">
<channel>
 <title>Credit Information</title>
 <link>http://www.fiercehealthcare.com/tags/credit-information</link>
 <description></description>
 <language>en</language>
<item>
 <title>Trend: Identity thieves get better at stealing medical records</title>
 <link>http://www.fiercehealthcare.com/story/trend-identity-thieves-get-better-at-stealing-medical-records/2008-05-07?utm_medium=rss&amp;utm_source=rss&amp;cmp-id=OTC-RSS-FH0</link>
 <description>
&lt;P&gt;Recently, identity thieves have become increasingly focused on stealing medical records--and have begun using better methods to get patient data, too. Medical records offer a rich trove of information for an identity thief, often including not only health insurance account numbers and billing addresses, but also dates of birth, Social Security numbers and even credit information. Given the richness of patient records, thieves may make more money stealing them than they would by going after credit card numbers or bank accounts directly. Worse, the thieves are getting more skilled at such thefts. While providers often encrypt their data, thieves often work with insiders who can help them break through these security measures. Concerned about this trend, &lt;A href=&quot;http://www.fiercehealthit.com/story/california-expands-health-data-breach-rules/2008-01-07&quot;&gt;California&lt;/a&gt; and Arkansas now require that consumers be notified when their medical data is accessed, and federal legislators are considering a measure instituting similar requirements.&lt;BR /&gt;&lt;BR /&gt;To learn more about medical record theft:&lt;BR /&gt;- read this &lt;EM&gt;USA Today&lt;/em&gt; &lt;A href=&quot;http://www.usatoday.com/news/health/2008-05-06-privacy_N.htm&quot;&gt;article&lt;/a&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;STRONG&gt;Related Articles:&lt;/strong&gt;&lt;BR /&gt;&lt;A href=&quot;http://www.fiercehealthcare.com/story/the-growing-problem-of-medical-identity-theft/2006-09-25&quot;&gt;The growing problem of medical identity theft&lt;/a&gt;&lt;BR /&gt;&lt;A href=&quot;http://www.fiercehealthcare.com/story/ny-hospital-worker-charged-with-massive-file-theft/2008-04-14&quot;&gt;NY hospital worker charged with massive file theft&lt;/a&gt;&lt;BR /&gt;&lt;A href=&quot;http://www.fiercehealthit.com/story/california-expands-health-data-breach-rules/2008-01-07&quot;&gt;California expands health data breach rules&lt;/a&gt;&lt;/p&gt;

</description>
 <comments>http://www.fiercehealthcare.com/story/trend-identity-thieves-get-better-at-stealing-medical-records/2008-05-07#comments</comments>
 <category domain="http://www.fiercehealthcare.com/tags/credit-information">Credit Information</category>
 <category domain="http://www.fiercehealthcare.com/tags/electronic-medical-records">Electronic Medical Records (EMRs)</category>
 <category domain="http://www.fiercehealthcare.com/tags/insurers">Insurance</category>
 <category domain="http://www.fiercehealthcare.com/tags/medical-records-0">medical records</category>
 <category domain="http://www.fiercehealthcare.com/tags/patient-data">patient data</category>
 <category domain="http://www.fiercehealthcare.com/tags/patient-records">patient records</category>
 <category domain="http://www.fiercehealthcare.com/tags/social-security-numbers-0">Social Security Numbers</category>
 <pubDate>Wed, 07 May 2008 06:59:57 -0400</pubDate>
 <dc:creator />
 <guid isPermaLink="false">26807 at http://www.fiercehealthcare.com</guid>
</item>
<item>
 <title>Dental HMO leaks personal information to website</title>
 <link>http://www.fiercehealthcare.com/story/dental-hmo-leaks-personal-information-to-website/2008-03-27?utm_medium=rss&amp;utm_source=rss&amp;cmp-id=OTC-RSS-FH0</link>
 <description>&lt;p&gt;
Here we go again! As reported by the &lt;em&gt;Baltimore Sun&lt;/em&gt;, a CareFirst BlueCross BlueShield dental HMO accidentally leaked personal information--including Social Security numbers--of around 75,000 patients on a public website in February, failing to inform them of the gaffe for three weeks. While the company claims none of the information has been misused, it also has offered members 12 months of free credit monitoring, and information to contact credit bureaus for fraud alert purposes. Still, this is the &lt;a href=&quot;http://www.fiercehealthcare.com/story/also-noted-tn-medicaid-to-test-e-prescribing-program-nih-alerts-patients-of/2008-03-25&quot;&gt;second time in two months&lt;/a&gt; that this sort of thing has happened. What has to happen for these sorts of mistakes to cease?
&lt;/p&gt;
&lt;p&gt;
For more information:&lt;br /&gt;
- read the &lt;em&gt;Baltimore Sun&lt;/em&gt;&#039;s &lt;a href=&quot;http://www.baltimoresun.com/news/health/bal-te.md.dental26mar26,0,4823354.story&quot;&gt;article&lt;/a&gt;
&lt;/p&gt;
</description>
 <comments>http://www.fiercehealthcare.com/story/dental-hmo-leaks-personal-information-to-website/2008-03-27#comments</comments>
 <category domain="http://www.fiercehealthcare.com/tags/bcbs">BlueCross BlueShield (BCBS)</category>
 <category domain="http://www.fiercehealthcare.com/tags/carefirst-bluecross-0">Carefirst Bluecross</category>
 <category domain="http://www.fiercehealthcare.com/tags/contact">contact</category>
 <category domain="http://www.fiercehealthcare.com/tags/credit-information">Credit Information</category>
 <category domain="http://www.fiercehealthcare.com/tags/fraud">fraud</category>
 <category domain="http://www.fiercehealthcare.com/tags/information-security-0">Information Security</category>
 <category domain="http://www.fiercehealthcare.com/tags/personal-information">personal information</category>
 <category domain="http://www.fiercehealthcare.com/tags/personal-security">Personal Security</category>
 <category domain="http://www.fiercehealthcare.com/tags/social-security-numbers-0">Social Security Numbers</category>
 <pubDate>Thu, 27 Mar 2008 07:59:55 -0400</pubDate>
 <dc:creator />
 <guid isPermaLink="false">22316 at http://www.fiercehealthcare.com</guid>
</item>
</channel>
</rss>
