Commentary

George Hulme
 

Healthcare Providers Want "Red Flag" Exception

Dentists, physicians, and veterinarians are asking the Federal Trade Commission to exclude healthcare professionals from regulations designed to mitigate the risks of identity theft. I say: Step up and protect your customers from identity theft.

Dentists, physicians, and veterinarians are asking the Federal Trade Commission to exclude healthcare professionals from regulations designed to mitigate the risks of identity theft. I say: Step up and protect your customers from identity theft.In a letter sent to FTC Chairman Jon Leibowitz from the American Dental Association (ADA), American Medical Association (AMA), American Osteopathic Association (AOA), and American Veterinary Medical Association (AVMA), the groups are asking that the "red flags" rule not apply to them.

They say the FTC's interpretation of the regulation imposes an "unjustified, unfunded mandate on health professionals for detecting and responding to identity theft."


More Healthcare Insights

White Papers

More >>

Reports

More >>

Webcasts

More >>

From the press release that went out Friday:

The organizations asked the FTC to make it clear that the rule will not apply to their members given the result of recent litigation brought by the American Bar Association against the FTC. In that case, the U.S. District Court for the District of Columbia ruled that lawyers should be excluded from the requirements imposed by the red flags rule.
This healthcare consortium may be legally right, and they may win this argument.

But they're going to lose the battle over their public image. The fact is that most healthcare providers do painfully little to protect their patients' from identity and medical identity theft. This comes despite years of news reports covering the growth of medical identity theft and hospital workers snooping at what should be private health data. So if they don't care about protecting patient data, why should we expect them to care about keeping an eye out for potential identity thieves?

When it comes to protecting data, most small retailers do more (thanks to payment industry regulations) to protect credit card data than most small healthcare providers do to protect their customers.

A quick search of the Dataloss database (www.datalossdb.net) shows medical data breaches that spilled nearly 7.5 million sensitive records with a mean of 33,386 records per incident. Check it out here for yourself.

An important part of the group's argument stems from a court decision earlier this year that the FTC Red Flag rules do not apply to lawyers. And if they don't apply to lawyers, they shouldn't apply to healthcare providers.

It's not that straightforward of a comparison. The government hasn't set a goal to get electronic legal records established for every American within the next five years.

But that's exactly the goal the Obama administration has set for electronic medical records. EMRs are to be on file for every American by 2014. And the government has put forth $20 billion in incentives for the adoption of EMRs in the American Recovery and Reinvestment Act of 2009.

With all of our health records being digitized, and the growth of medical identity theft, it's not asking that much for the stewards of this data to step up and take the step to implement a written identity theft prevention program to identify the warning signs "Red Flags" of identity theft. That's essentially what the Red Flag rules do.

As more of our health data is digitized, the more healthcare providers - large and small - will be targeted for that information. And, one way or another, all healthcare providers are going to have to detect and respond to it. The idea is to do that before patients find themselves without access to health insurance or are bankrupt.


Related Reading




Currently we allow the following HTML tags in comments:

Single tags

These tags can be used alone and don't need an ending tag.

<br> Defines a single line break

<hr> Defines a horizontal line

Matching tags

These require an ending tag - e.g. <i>italic text</i>

<a> Defines an anchor

<b> Defines bold text

<big> Defines big text

<blockquote> Defines a long quotation

<caption> Defines a table caption

<cite> Defines a citation

<code> Defines computer code text

<em> Defines emphasized text

<fieldset> Defines a border around elements in a form

<h1> This is heading 1

<h2> This is heading 2

<h3> This is heading 3

<h4> This is heading 4

<h5> This is heading 5

<h6> This is heading 6

<i> Defines italic text

<p> Defines a paragraph

<pre> Defines preformatted text

<q> Defines a short quotation

<samp> Defines sample computer code text

<small> Defines small text

<span> Defines a section in a document

<s> Defines strikethrough text

<strike> Defines strikethrough text

<strong> Defines strong text

<sub> Defines subscripted text

<sup> Defines superscripted text

<u> Defines underlined text

InformationWeek encourages readers to engage in spirited, healthy debate, including taking us to task. However, InformationWeek moderates all comments posted to our site, and reserves the right to modify or remove any content that it determines to be derogatory, offensive, inflammatory, vulgar, irrelevant/off-topic, racist or obvious marketing/SPAM. InformationWeek further reserves the right to disable the profile of any commenter participating in said activities.

Disqus Tips To upload an avatar photo, first complete your Disqus profile. | View the list of supported HTML tags you can use to style comments. | Please read our commenting policy.
T-Shirt Giveaway T-Shirt Giveaway: Each week we're selecting one great comment from our readers. The author of the comment will receive an InformaitonWeek Community t-shirt. So get posting!
Subscribe to RSS

Resource Links