<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Journal of AHIMA &#187; Compliance</title>
	<atom:link href="http://journal.ahima.org/category/compliance/feed/" rel="self" type="application/rss+xml" />
	<link>http://journal.ahima.org</link>
	<description>The Journal of AHIMA is published monthly by the American Health Information Management Association</description>
	<lastBuildDate>Fri, 19 Mar 2010 12:50:25 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.1</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>CMS Publishes Interim Final Rule on GINA</title>
		<link>http://journal.ahima.org/2009/10/09/cms-publishes-interim-final-rule-on-gina/</link>
		<comments>http://journal.ahima.org/2009/10/09/cms-publishes-interim-final-rule-on-gina/#comments</comments>
		<pubDate>Fri, 09 Oct 2009 13:19:50 +0000</pubDate>
		<dc:creator>Meg Featheringham</dc:creator>
				<category><![CDATA[Compliance]]></category>
		<category><![CDATA[HIM operations]]></category>
		<category><![CDATA[Privacy and security]]></category>

		<guid isPermaLink="false">http://journal.ahima.org/?p=1063</guid>
		<description><![CDATA[On Wednesday the Centers for Medicare and Medicaid Services (CMS) published the interim final rule for the Genetic Information Nondiscrimination Act (GINA). In it, CMS modifies the HIPAA privacy rule to explicitly include genetic information within the definition of health information. 
The rule also proposes to:

prohibit health plans from using or disclosing protected health information that is genetic information for [...]]]></description>
			<content:encoded><![CDATA[<p>On Wednesday the Centers for Medicare and Medicaid Services (CMS) published the <a href="http://edocket.access.gpo.gov/2009/pdf/E9-22504.pdf" target="_blank">interim final rule for the Genetic Information Nondiscrimination Act (GINA)</a>. In it, CMS modifies the HIPAA privacy rule to explicitly include genetic information within the definition of health information. </p>
<p>The rule also proposes to:</p>
<ul>
<li>prohibit health plans from using or disclosing protected health information that is genetic information for underwriting purposes;</li>
<li>revise the provisions relating to the notice of privacy practices for health plans that perform underwriting;</li>
<li>make conforming modifications to definitions and other provisions of the privacy rule; and</li>
<li>make technical corrections to update the definition of “health plan.”</li>
</ul>
<p>The interim final rule applies GINA’s prohibitions on using and disclosing protected genetic health information for underwriting to all health plans subject to the privacy rule, rather than solely to the plans GINA explicitly requires be subject to the prohibition. It also proposes applying the prohibition on using or disclosing is genetic information for underwriting purposes to all health plans that are covered entities as defined by the HIPAA privacy rule.</p>
<p>CMS will accept public comments for 60 days.</p>
<p>Signed in 2008, <a href="http://frwebgate.access.gpo.gov/cgi-bin/getdoc.cgi?dbname=110_cong_public_laws&amp;docid=f:publ233.110.pdf" target="_blank">GINA</a> protects individuals against discrimination in health coverage or employment based on their genetic information.</p>
]]></content:encoded>
			<wfw:commentRss>http://journal.ahima.org/2009/10/09/cms-publishes-interim-final-rule-on-gina/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>New Delay for the Red Flags Rule</title>
		<link>http://journal.ahima.org/2009/07/29/new-delay-for-the-red-flags-rule/</link>
		<comments>http://journal.ahima.org/2009/07/29/new-delay-for-the-red-flags-rule/#comments</comments>
		<pubDate>Wed, 29 Jul 2009 16:22:27 +0000</pubDate>
		<dc:creator>Kevin Heubusch</dc:creator>
				<category><![CDATA[Compliance]]></category>

		<guid isPermaLink="false">http://journal.ahima.org/?p=866</guid>
		<description><![CDATA[The Federal Trade Commission announced today that it will further delay enforcement of the Red Flags Rule. Organizations now have until November 1, 2009, to become compliant. The rule was to go into effect Saturday, August 1.
FTC says the delay will allow organizations covered by the rule to further review its educational materials and prepare [...]]]></description>
			<content:encoded><![CDATA[<p>The Federal Trade Commission <a href="http://www.ftc.gov/opa/2009/07/redflag.shtm" target="_blank">announced today</a> that it will further delay enforcement of the Red Flags Rule. Organizations now have until November 1, 2009, to become compliant. The rule was to go into effect Saturday, August 1.</p>
<p>FTC says the delay will allow organizations covered by the rule to further review its educational materials and prepare their compliance plans.</p>
<p>The <a href="http://journal.ahima.org/2009/04/14/medical-identity-theft-and-the-red-flags-rule/" target="_blank">anti-fraud regulation</a> requires organizations that act as creditors to implement programs to identify, detect, and respond to “red flags” that could indicate identity theft. The final rule was published November 9, 2007, with an original compliance date of November 1, 2008. It has been delayed several times due to a lack of industry readiness and calls for more clarification and assistance in designing compliance plans.</p>
]]></content:encoded>
			<wfw:commentRss>http://journal.ahima.org/2009/07/29/new-delay-for-the-red-flags-rule/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Guidance on RACs</title>
		<link>http://journal.ahima.org/2009/07/24/guidance-on-racs/</link>
		<comments>http://journal.ahima.org/2009/07/24/guidance-on-racs/#comments</comments>
		<pubDate>Fri, 24 Jul 2009 17:00:17 +0000</pubDate>
		<dc:creator>Meg Featheringham</dc:creator>
				<category><![CDATA[Compliance]]></category>
		<category><![CDATA[HIM operations]]></category>
		<category><![CDATA[RACs]]></category>

		<guid isPermaLink="false">http://journal.ahima.org/?p=854</guid>
		<description><![CDATA[A new AHIMA toolkit helps HIM professionals steer their organizations through the Recovery Audit Contractor (RAC) program.
 The “Recovery Audit Contractor (RAC) Toolkit” includes background on the program and an overview of the process, including what entities are eligible to be audited, the basis for the audits, and the type of audits. It also includes appendixes [...]]]></description>
			<content:encoded><![CDATA[<p>A new AHIMA toolkit helps HIM professionals steer their organizations through the Recovery Audit Contractor (RAC) program.</p>
<p> The <a href="http://www.ahima.org/infocenter/documents/RACToolkitFINAL.pdf" target="_blank">“Recovery Audit Contractor (RAC) Toolkit”</a> includes background on the program and an overview of the process, including what entities are eligible to be audited, the basis for the audits, and the type of audits. It also includes appendixes providing:<span id="more-854"></span></p>
<ul>
<li>A preparation checklist</li>
<li>The hierarchy of authority samples</li>
<li>A sample of the RAC coordinator job description</li>
<li>A sample of a RAC policy and procedure</li>
<li>A RAC record extension request sample</li>
<li>How to develop a RAC education program</li>
<li>A presentation sample</li>
<li>RAC acronyms</li>
<li>A RAC determination response</li>
<li>The appeal process workflow</li>
<li>The Medicare appeals process</li>
<li>Sample appeal letters</li>
<li>An appeals submission checklist</li>
</ul>
<p>The kit was developed by AHIMA’s Recovery Audit Contractors (RACs) Workgroup, a subgroup of the Clinical Terminology and Classification Practice Council. It is available free of charge.</p>
<p>AHIMA offers additional toolkits online, including <a href="http://www.ahima.org/infocenter/documents/copy_functionality_toolkit.pdf" target="_blank">“Copy Functionality Toolkit,” </a>which can help HIM professionals and their organizations develop policies and procedures to allow for the review, audit, and testing surrounding this functionality. The <a href="http://www.ahima.org/hie/" target="_blank">“Health Information Exchange (HIE) Resource Toolkit”</a> outlines the HIM issues in health information exchange, as well as useful Web sites that HIM professionals can reference in preparing for HIE.</p>
<p>Look for two more toolkits on amendments to transcribed reports and amendments for EHRs, which will be released in August.</p>
]]></content:encoded>
			<wfw:commentRss>http://journal.ahima.org/2009/07/24/guidance-on-racs/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>RACs to Begin with Automated Reviews</title>
		<link>http://journal.ahima.org/2009/06/15/racs-to-begin-with-automated-reviews/</link>
		<comments>http://journal.ahima.org/2009/06/15/racs-to-begin-with-automated-reviews/#comments</comments>
		<pubDate>Mon, 15 Jun 2009 13:00:03 +0000</pubDate>
		<dc:creator>Meg Featheringham</dc:creator>
				<category><![CDATA[Coding & reimbursement]]></category>
		<category><![CDATA[Compliance]]></category>
		<category><![CDATA[RACs]]></category>

		<guid isPermaLink="false">http://journal.ahima.org/?p=667</guid>
		<description><![CDATA[The Centers for Medicare and Medicaid Services (CMS) hopes to start Recovery Audit Contractor (RAC) automated reviews in late June and July, with more complex reviews rolling out later, according to a May 29 Health Leaders report. CMS expects to begin certain complex reviews like coding and DRG validation this fall. Medical necessity complex reviews [...]]]></description>
			<content:encoded><![CDATA[<p>The Centers for Medicare and Medicaid Services (CMS) hopes to start Recovery Audit Contractor (RAC) automated reviews in late June and July, with more complex reviews rolling out later, according to a <a href="http://www.healthleadersmedia.com/content/233798/topic/WS_HLM2_FIN/CMS-Updates-RAC-Audit-Timeline-Complex-Reviews-Still-Months-Away.html" target="_blank">May 29 <em>Health Leaders</em> report</a>. CMS expects to begin certain complex reviews like coding and DRG validation this fall. Medical necessity complex reviews will not begin until early 2010.</p>
<p>&#8220;The automated reviews are less burdensome on the provider, because there&#8217;s no request for medical records,&#8221; said Marie Casey, deputy director of the Division of Recovery Audit Operations at CMS, in the news item. &#8220;They&#8217;re also easier for the RACs to manage.&#8221;</p>
<p>The delay for medical necessity auditing is due to the complexity of the reviews. &#8220;We&#8217;re delaying because it&#8217;s more difficult,&#8221; Casey said. &#8220;We are really trying to ensure that when there is a difference of opinion [on the medical necessity determination of the case], the RAC clearly documents their rationale.&#8221;</p>
<p>The delay will also help CMS roll out an issue review team, a group comprised of members from various agency divisions that will look at policy questions, such as whether the RACs have been correct in the interpretation of coding guidelines. These teams will look comprehensively at the questions before approving new issues for RAC review, according to Kathleen Wallace, a CMS representative who spoke at a May 28 Region D RAC training session held in Helena, MT.</p>
<p>When record requests do come, they will start sporadically but eventually fall into a pattern, at least in Region D, said HealthDataInsights president and CEO Andrea Denko, during the Helena training session.</p>
]]></content:encoded>
			<wfw:commentRss>http://journal.ahima.org/2009/06/15/racs-to-begin-with-automated-reviews/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Understanding National Coverage Policies</title>
		<link>http://journal.ahima.org/2009/06/02/understanding-national-coverage-policies/</link>
		<comments>http://journal.ahima.org/2009/06/02/understanding-national-coverage-policies/#comments</comments>
		<pubDate>Tue, 02 Jun 2009 13:02:03 +0000</pubDate>
		<dc:creator>Kevin Heubusch</dc:creator>
				<category><![CDATA[Coding & reimbursement]]></category>
		<category><![CDATA[Compliance]]></category>
		<category><![CDATA[Add new tag]]></category>

		<guid isPermaLink="false">http://journal.ahima.org/?p=616</guid>
		<description><![CDATA[&#8220;Present on admission indicators, hospital-acquired conditions, serious reportable events, and ‘wrong’ surgical events are each hot topics,” write the authors of a “Coding Notes” column in this month’s print issue. “However, they also can be a hot topic together, because a number of these reporting requirements are interrelated.”
Jane Cook, Cheryl D’Amato, Gail Garrett, Becky Ruhnau-Gee, [...]]]></description>
			<content:encoded><![CDATA[<p>&#8220;Present on admission indicators, hospital-acquired conditions, serious reportable events, and ‘wrong’ surgical events are each hot topics,” write the authors of a “Coding Notes” column in this month’s print issue. “However, they also can be a hot topic together, because a number of these reporting requirements are interrelated.”</p>
<p>Jane Cook, Cheryl D’Amato, Gail Garrett, Becky Ruhnau-Gee, Linda Hyde, and Natalie Novak sort out the relationship of POA, HACs, SREs, and &#8220;wrong&#8221; surgical site policies in “<a href="http://library.ahima.org/xpedio/groups/public/documents/ahima/bok1_043755.hcsp?dDocName=bok1_043755" target="_blank">Understanding National Coverage Policies</a>.”</p>
]]></content:encoded>
			<wfw:commentRss>http://journal.ahima.org/2009/06/02/understanding-national-coverage-policies/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Kaiser Fined for Celebrity Breach</title>
		<link>http://journal.ahima.org/2009/05/18/kaiser-fined-for-celebrity-breach/</link>
		<comments>http://journal.ahima.org/2009/05/18/kaiser-fined-for-celebrity-breach/#comments</comments>
		<pubDate>Mon, 18 May 2009 16:45:09 +0000</pubDate>
		<dc:creator>Meg Featheringham</dc:creator>
				<category><![CDATA[Compliance]]></category>
		<category><![CDATA[Privacy and security]]></category>

		<guid isPermaLink="false">http://journal.ahima.org/?p=583</guid>
		<description><![CDATA[On Friday the California Department of Public Health announced an administrative penalty of $250,000 against Kaiser Permanente Bellflower Hospital for failing to prevent unauthorized access to octuplet mom Nadya Suleman&#8217;s medical records. According to CDPH, 21 employees and two physicians improperly viewed Suleman&#8217;s medical records.
The penalty is the first under California&#8217;s strict new privacy laws, [...]]]></description>
			<content:encoded><![CDATA[<p>On Friday the California Department of Public Health announced <a href="http://ww2.cdph.ca.gov/HealthInfo/news/Pages/NR2009-43-AdministrativePenaltyKaiser.aspx" target="_blank">an administrative penalty </a>of $250,000 against Kaiser Permanente Bellflower Hospital for failing to prevent unauthorized access to octuplet mom Nadya Suleman&#8217;s medical records. According to CDPH, 21 employees and two physicians improperly viewed Suleman&#8217;s medical records.</p>
<p>The penalty is the first under California&#8217;s strict new privacy laws, which went into effect January 1. The $250,000 fine was the maximum allowed.</p>
<p>Kaiser first reported the breach back in April, when it <a href="http://journal.ahima.org/2009/04/02/celebrity-test-ca-privacy-laws/" target="_blank">disciplined and fired </a>employees for accessing Suleman&#8217;s records. The CDPH investigation announced Friday involved the facility only. Under a separate law, the state may seek prosecution against the individuals themselves.</p>
]]></content:encoded>
			<wfw:commentRss>http://journal.ahima.org/2009/05/18/kaiser-fined-for-celebrity-breach/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>HIPAA: 43,691 Complaints and Counting</title>
		<link>http://journal.ahima.org/2009/05/13/hipaa-43691-complaints-and-counting/</link>
		<comments>http://journal.ahima.org/2009/05/13/hipaa-43691-complaints-and-counting/#comments</comments>
		<pubDate>Wed, 13 May 2009 16:39:15 +0000</pubDate>
		<dc:creator>Kevin Heubusch</dc:creator>
				<category><![CDATA[Compliance]]></category>
		<category><![CDATA[HIPAA]]></category>
		<category><![CDATA[Privacy and security]]></category>

		<guid isPermaLink="false">http://journal.ahima.org/?p=575</guid>
		<description><![CDATA[If you ever wonder what progress the Office for Civil Rights is making as it works its way through HIPAA privacy rule complaints, the numbers are easy to find. Each month OCR reports top-line results of the HIPAA cases it has received and resolved.
OCR has logged approximately 43,700 complaints since the privacy rule went into [...]]]></description>
			<content:encoded><![CDATA[<p>If you ever wonder what progress the Office for Civil Rights is making as it works its way through HIPAA privacy rule complaints, the numbers are easy to find. Each month OCR reports <a href="http://www.hhs.gov/ocr/privacy/hipaa/enforcement/highlights/index.html" target="_blank">top-line results</a> of the HIPAA cases it has received and resolved.</p>
<p>OCR has logged approximately 43,700 complaints since the privacy rule went into effect April 14, 2003. It has resolved 86 percent of them, and as of April 30 it had nearly 6,000 cases still on its to-do list.</p>
<p>OCR enforces the HIPAA privacy rule only. Enforcement of the security rule falls to the Centers for Medicare and Medicaid Services. Violations of either rule that involve possible criminal violations are referred to the Department of Justice. Through April 30 of this year, OCR had referred 456 cases to the DOJ and 306 cases to CMS.<span id="more-575"></span></p>
<p>Individuals filed 8,526 privacy complaints with OCR in 2008. This is up 4 percent from the previous year, and up 23 percent since 2004, the first full year of the rule.</p>
<p>OCR reviews all complaints, but not all require investigation. In 2008 the office resolved 9,280 complaints, of which 36 percent warranted an investigation. Of those, 2,210 resulted in corrective action. No violation was found in the remaining 1,163 cases.</p>
<p>This breakdown largely reflects past history. Since 2005 approximately one-third of complaints have required investigation. Approximately two-thirds of investigations have resulted in corrective action.</p>
<h5>Common Complaint</h5>
<p>Improper use and disclosure of protected health information has been the leading compliance violation since 2004. The following three issues have not changed, either. They are, in order: lack of safeguards for protected health information, lack of patient access, and use or disclosure of more than the minimum necessary information. The fifth spot has alternated among issues related to amendments, notices, mitigation, and authorization.</p>
<p>Private practices lead the list of covered entity types that have been required to take corrective action. General hospitals follow.</p>
]]></content:encoded>
			<wfw:commentRss>http://journal.ahima.org/2009/05/13/hipaa-43691-complaints-and-counting/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Red Flags Rule Delayed</title>
		<link>http://journal.ahima.org/2009/05/01/red-flags-rule-delay/</link>
		<comments>http://journal.ahima.org/2009/05/01/red-flags-rule-delay/#comments</comments>
		<pubDate>Fri, 01 May 2009 17:42:11 +0000</pubDate>
		<dc:creator>Kevin Heubusch</dc:creator>
				<category><![CDATA[Compliance]]></category>
		<category><![CDATA[Privacy and security]]></category>

		<guid isPermaLink="false">http://journal.ahima.org/?p=551</guid>
		<description><![CDATA[One day before the Red Flags Rule were to take effect, the Federal Trade Commission announced a three-month delay. Organizations that would have woken up out of compliance today now have until August 1 to comply.
The rule requires &#8220;creditors&#8221; and financial institutions to develop and implement written identity theft prevention programs. (For more on the [...]]]></description>
			<content:encoded><![CDATA[<p>One day before the Red Flags Rule were to take effect, the Federal Trade Commission <a href="http://www.ftc.gov/opa/2009/04/redflagsrule.shtm" target="_blank">announced a three-month delay</a>. Organizations that would have woken up out of compliance today now have until August 1 to comply.</p>
<p>The rule requires &#8220;creditors&#8221; and financial institutions to develop and implement written identity theft prevention programs. (For more on the rule, see articles in &#8220;<a href="http://journal.ahima.org/category/privacy-and-security/" target="_blank">Privacy &amp; Security.&#8221;</a>)</p>
<p>The FTC also announced that it would release a compliance template for entities that have a low risk of identity theft, such as businesses that know their customers personally.</p>
<p>Continued confusion over the terms of the provision resulted in the delay. &#8221;Given the ongoing debate about whether Congress wrote this provision too broadly, delaying enforcement of the Red Flags Rule will allow industries and associations to share guidance with their members, provide low-risk entities an opportunity to use the template in developing their programs, and give Congress time to consider the issue further,” FTC Chairman Jon Leibowitz said in the statement.</p>
<p>This is the second delay for the Red Flags rule. The original deadline was November 2008.</p>
]]></content:encoded>
			<wfw:commentRss>http://journal.ahima.org/2009/05/01/red-flags-rule-delay/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>GINA Guidance for Researchers</title>
		<link>http://journal.ahima.org/2009/04/29/gina-guidance-for-researchers/</link>
		<comments>http://journal.ahima.org/2009/04/29/gina-guidance-for-researchers/#comments</comments>
		<pubDate>Wed, 29 Apr 2009 14:00:59 +0000</pubDate>
		<dc:creator>Meg Featheringham</dc:creator>
				<category><![CDATA[Compliance]]></category>
		<category><![CDATA[HIM operations]]></category>
		<category><![CDATA[Privacy and security]]></category>

		<guid isPermaLink="false">http://journal.ahima.org/?p=510</guid>
		<description><![CDATA[The Department of Health and Human Services has published guidance related to the Genetic Information Nondiscrimination Act (GINA) and its effect on researchers.
&#8220;Guidance on the Genetic Information Nondiscrimination Act: Implications for Investigators and Institutional Review Boards&#8221; provides background on protections provided by GINA and discusses GINA&#8217;s impact on investigators who conduct genetic research and the [...]]]></description>
			<content:encoded><![CDATA[<p>The Department of Health and Human Services has published guidance related to the <a href="http://www.govtrack.us/congress/billtext.xpd?bill=h110-493&amp;show-changes=0&amp;page-command=print" target="_blank">Genetic Information Nondiscrimination Act</a> (GINA) and its effect on researchers.</p>
<p><a href="http://www.hhs.gov/ohrp/humansubjects/guidance/gina.html" target="_blank">&#8220;Guidance on the Genetic Information Nondiscrimination Act: Implications for Investigators and Institutional Review Boards&#8221;</a> provides background on protections provided by GINA and discusses GINA&#8217;s impact on investigators who conduct genetic research and the institutional review boards that review it, particularly on criteria for IRB approval of research and the requirements for obtaining informed consent under the HHS regulations for the protection of human subjects (45 CFR part 46).</p>
<p>Final GINA regulations are expected in May.</p>
<p>To review GINA&#8217;s provisions, see the July 2008 &#8220;Word from Washington&#8221; column <a href="http://ch1as13/xpedio/groups/public/documents/ahima/bok1_039073.hcsp?dDocName=bok1_039073" target="_blank">&#8220;Getting to Know GINA.&#8221;</a></p>
]]></content:encoded>
			<wfw:commentRss>http://journal.ahima.org/2009/04/29/gina-guidance-for-researchers/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>The Red Flags Rule: Protecting Providers and Patients from Medical Identity Theft</title>
		<link>http://journal.ahima.org/2009/04/17/the-red-flags-rule-protecting-providers-and-patients-from-medical-identity-theft/</link>
		<comments>http://journal.ahima.org/2009/04/17/the-red-flags-rule-protecting-providers-and-patients-from-medical-identity-theft/#comments</comments>
		<pubDate>Fri, 17 Apr 2009 11:00:36 +0000</pubDate>
		<dc:creator>Anne Zender</dc:creator>
				<category><![CDATA[Compliance]]></category>
		<category><![CDATA[Privacy and security]]></category>
		<category><![CDATA[medical identity theft]]></category>

		<guid isPermaLink="false">http://journal.ahima.org/?p=421</guid>
		<description><![CDATA[Capping off our Health Information Privacy and Security Week series, Federal Trade Commission attorney Steven Toporoff offers tips on complying with the Red Flags Rule, which goes into effect May 1. Toporoff works in the FTC’s Division of Privacy and Identity Protection, Bureau of Consumer Protection.
Millions of Americans each year fall victim to identity theft.  [...]]]></description>
			<content:encoded><![CDATA[<p><em>Capping off our Health Information Privacy and Security Week series, Federal Trade Commission attorney </em><a href="mailto:stoporoff@ftc.gov"><em>Steven Toporoff</em></a><em> offers tips on complying with the Red Flags Rule, which goes into effect May 1. Toporoff works in the FTC’s Division of Privacy and Identity Protection, Bureau of Consumer Protection.</em></p>
<p>Millions of Americans each year fall victim to identity theft.  When identity theft involves healthcare, the consequences can be severe. It can result in losses to the healthcare provider from unpaid bills, the exhaustion of the victim’s benefits, or even potentially life-threatening corruption of a patient’s medical records. </p>
<p>The crime also can play havoc with an innocent consumer’s credit rating.  Medical identity theft may arise when a person seeks healthcare services or prescription pharmaceuticals using someone else’s name or insurance information.  A recent nationwide survey conducted for the FTC found that 4.5 percent of the 8.3 million identity theft victims have experienced some form of medical identity theft.</p>
<p>The Red Flags Rule is designed to help protect patients and providers from suffering the consequences of medical identity theft.  Briefly put, this new law requires “creditors” and “financial institutions” to determine if they have either consumer accounts that permit multiple payments or other accounts for which there is a reasonable risk of identity theft.  If they do, these covered entities must develop and implement a written identity theft prevention program. Each provider has the flexibility to implement a program that best suits its size, complexity, and actual risk of identity theft.   <span id="more-421"></span></p>
<p>Although enforcement has been deferred until May 1, 2009, many providers are already putting their programs together. Some, however, question the applicability of the rule to physicians and other providers, because they do not view them as “creditors.” For purposes of the Red Flags Rule, the definition of  “creditor” is very broad, and includes an arrangement for the deferral of payment of debts or payment for the purchase of goods or services. Healthcare providers are creditors if they regularly collect payment after services are rendered. Simply accepting credit cards as a form of payment, however, does not make a provider a creditor under the rule.  </p>
<p>The first step in implementing a program is to identity the warning signs—or “red flags”—of identity theft.  These may include identification, medical history, or information that does not seem to match the patient, or notice from consumers that they are victims of identity theft. Second, the program must include policies and procedures to detect these “red flags.” For example, many providers already check a photo ID or insurance information for new or returning patients. </p>
<p>Third, the program must include appropriate responses to prevent and mitigate identity theft. These could include not collecting on a debt against the innocent consumer or ensuring that medical records are not corrupted with errors resulting from the identity theft. Finally, providers must update their programs periodically if new risks and trends arise. To ensure that these steps become routine, the rule requires that the Red Flags Program be in writing.</p>
<p>Using this common-sense approach to developing a program can help reduce the incidence of medical identity theft without overburdening health care providers. And because the rule is risk-based, a simple plan should be sufficient for providers that have a low risk of identity theft in their practices. Still have questions? Send a message to <a href="mailto:redflags@ftc.gov">redflags@ftc.gov</a> or check <a href="http://www.ftc.gov" target="_blank">www.ftc.gov</a> for more information.</p>
]]></content:encoded>
			<wfw:commentRss>http://journal.ahima.org/2009/04/17/the-red-flags-rule-protecting-providers-and-patients-from-medical-identity-theft/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
