<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet type="text/xsl" media="screen" href="/~d/styles/rss2full.xsl"?><?xml-stylesheet type="text/css" media="screen" href="http://feeds.feedburner.com/~d/styles/itemcontent.css"?><rss 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/" xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0" version="2.0">

<channel>
	<title>Journal of AHIMA</title>
	
	<link>http://journal.ahima.org</link>
	<description>The Journal of AHIMA is published monthly by the American Health Information Management Association</description>
	<lastBuildDate>Wed, 18 Nov 2009 19:55:09 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="self" href="http://feeds.feedburner.com/JournalOfAhima" type="application/rss+xml" /><atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="hub" href="http://pubsubhubbub.appspot.com" /><item>
		<title>Best Practices for Terminal Digit Filing</title>
		<link>http://feedproxy.google.com/~r/JournalOfAhima/~3/WK49sOjyByw/</link>
		<comments>http://journal.ahima.org/2009/11/18/best-practices-for-terminal-digit-filing/#comments</comments>
		<pubDate>Wed, 18 Nov 2009 19:55:09 +0000</pubDate>
		<dc:creator>Kevin Heubusch</dc:creator>
				<category><![CDATA[HIM operations]]></category>

		<guid isPermaLink="false">http://journal.ahima.org/?p=1234</guid>
		<description><![CDATA[Paper doesn’t get the publicity these days, but maintaining current and legacy paper-based health records continues to be important to day-to-day HIM operations. Understanding how to file, retrieve, and maintain paper records—especially across multiple locations, such as offsite storage—remains a core function in many departments.
Most HIM departments file by terminal digits, which is the only [...]]]></description>
			<content:encoded><![CDATA[<p>Paper doesn’t get the publicity these days, but maintaining current and legacy paper-based health records continues to be important to day-to-day HIM operations. Understanding how to file, retrieve, and maintain paper records—especially across multiple locations, such as offsite storage—remains a core function in many departments.</p>
<p>Most HIM departments file by terminal digits, which is the only way to keep files expanding at an even rate. In a terminal digit filing system the last two, three, or four digits of the file number are treated as a single number. Since all numbers in the file are sorted by their ending digits, each section contains approximately the same number of folders, so the file shelves are divided for easy expansion.</p>
<p>A new, free <a href="http://www.ahima.org/infocenter/practice_tools.asp#Kits" target="_blank">toolkit</a> from AHIMA offers best practices in terminal digit filing. Managers can use the kit to train new or existing staff by having employees review the kit and complete the exercises.</p>
<img src="http://feeds.feedburner.com/~r/JournalOfAhima/~4/WK49sOjyByw" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://journal.ahima.org/2009/11/18/best-practices-for-terminal-digit-filing/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		<feedburner:origLink>http://journal.ahima.org/2009/11/18/best-practices-for-terminal-digit-filing/</feedburner:origLink></item>
		<item>
		<title>Putting ICD Updates on Ice</title>
		<link>http://feedproxy.google.com/~r/JournalOfAhima/~3/tEjVOVonPSg/</link>
		<comments>http://journal.ahima.org/2009/11/17/putting-icd-on-ice/#comments</comments>
		<pubDate>Tue, 17 Nov 2009 14:52:49 +0000</pubDate>
		<dc:creator>Kevin Heubusch</dc:creator>
				<category><![CDATA[Coding & reimbursement]]></category>
		<category><![CDATA[ICD-10]]></category>

		<guid isPermaLink="false">http://journal.ahima.org/?p=1226</guid>
		<description><![CDATA[One step to help the industry make the transition to ICD-10-CM/PCS will be temporarily suspending updates to the code set as the October 2013 deadline gets closer.
Freezing both the current ICD-9-CM and the new ICD-10-CM/PCS code sets will save organizations further cost and complexity by enabling them to focus on the system change without simultaneously [...]]]></description>
			<content:encoded><![CDATA[<p>One step to help the industry make the transition to ICD-10-CM/PCS will be temporarily suspending updates to the code set as the October 2013 deadline gets closer.</p>
<p>Freezing both the current ICD-9-CM and the new ICD-10-CM/PCS code sets will save organizations further cost and complexity by enabling them to focus on the system change without simultaneously managing code updates. The Centers for Medicare and Medicaid Services has been receiving recommendations on whether to freeze the code sets and, if so, for how long.</p>
<p>In a <a href="http://www.ahima.org/icd10/documents/Freezing_code_sets.pdf" target="_blank">recently released statement</a>, AHIMA recommends that:</p>
<ul>
<li>The final ICD-9-CM update should be FY 2012 (beginning October 2011, in conjunction with the federal government’s fiscal year).</li>
<li>No updates should be made to ICD-10-CM/PCS for FY 2013 or FY 2014 (i.e., beginning October 2012).</li>
<li>Updates to ICD-10-CM/PCS should resume in FY 2015 (October 2014).<span id="more-1226"></span></li>
</ul>
<p>Freezing code sets presents its own challenges, given that the practice of medicine will keep evolving. AHIMA recommends that exceptions should be allowed for urgently needed codes. Organizations requesting updates would be required to make a “clear and convincing” case to the Coordination and Maintenance Committee as to why the codes can’t wait for the next regularly scheduled update (such as the emergence of a new disease).</p>
<p>AHIMA recommends that the Coordination and Maintenance Committee, which maintains the code sets in the US, should continue to meet during the freeze in order to consider code proposals and avoid a backlog in 2014. “Working draft addenda” could keep the industry appraised of code changes slated to go into effect for FY 2015.</p>
<p>In addition, AHIMA recommends that flexibility be retained during the freeze to correct errors identified in the ICD-10-CM/PCS code sets, such as incorrect index entries or incorrect code references in instructional notes.</p>
<p>AHIMA offers ICD-10 information and resources at <a href="http://www.ahima.org/icd10" target="_blank">www.ahima.org/icd10</a>.</p>
<img src="http://feeds.feedburner.com/~r/JournalOfAhima/~4/tEjVOVonPSg" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://journal.ahima.org/2009/11/17/putting-icd-on-ice/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		<feedburner:origLink>http://journal.ahima.org/2009/11/17/putting-icd-on-ice/</feedburner:origLink></item>
		<item>
		<title>More E-Signature Resources</title>
		<link>http://feedproxy.google.com/~r/JournalOfAhima/~3/8Wgvb5Xb1lw/</link>
		<comments>http://journal.ahima.org/2009/11/11/more-e-signature-resources/#comments</comments>
		<pubDate>Wed, 11 Nov 2009 15:33:10 +0000</pubDate>
		<dc:creator>Meg Featheringham</dc:creator>
				<category><![CDATA[Electronic records]]></category>
		<category><![CDATA[HIM operations]]></category>

		<guid isPermaLink="false">http://journal.ahima.org/?p=1222</guid>
		<description><![CDATA[Organizations can find further guidance on developing electronic signature policies in the online version of the November–December practice brief “Electronic Signature, Attestation, and Authorship (Updated).”
The online version includes five separate appendixes, linked at the end of the brief:

Appendix A excerpts portions of the HL7 EHR-System Records Management and Evidentiary Support Functional Profile Standard, which can [...]]]></description>
			<content:encoded><![CDATA[<p>Organizations can find further guidance on developing electronic signature policies in the online version of the November–December practice brief <a href="http://library.ahima.org/xpedio/groups/public/documents/ahima/bok1_045551.hcsp?dDocName=bok1_045551">“Electronic Signature, Attestation, and Authorship (Updated).”</a></p>
<p>The online version includes five separate appendixes, linked at the end of the brief:</p>
<ul>
<li><strong>Appendix A</strong> excerpts portions of the HL7 EHR-System Records Management and Evidentiary Support Functional Profile Standard, which can be used to develop proposals for selecting an EHR system or as a checklist to evaluate current applications for basic record management functionality.</li>
<li><strong>Appendix B</strong> lists the various e-signature laws, regulations, and acts that organizations can refer to in developing and implementing e-signature functionality and policy.</li>
<li><strong>Appendix C</strong> outlines a sample e-signature model policy template, including important legal and compliance recommendations.</li>
<li><strong>Appendix D</strong> provides a glossary of terms that organizations can use in their e-signature policies.</li>
<li><strong>Appendix E </strong>provides practice guidance on making amendments, corrections, and deletions in transcribed reports.<strong> </strong></li>
</ul>
<p><strong> </strong></p>
<p>Managing e-signatures is complex, but doing it correctly is critical  in supporting an organization’s legal health record. Successfully implementing and using e-signatures requires proper attention to individual system functionality, regulatory requirements, and organizational policy.</p>
<img src="http://feeds.feedburner.com/~r/JournalOfAhima/~4/8Wgvb5Xb1lw" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://journal.ahima.org/2009/11/11/more-e-signature-resources/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		<feedburner:origLink>http://journal.ahima.org/2009/11/11/more-e-signature-resources/</feedburner:origLink></item>
		<item>
		<title>More Delays for the Red Flags Rule</title>
		<link>http://feedproxy.google.com/~r/JournalOfAhima/~3/MJFLOkWQOkw/</link>
		<comments>http://journal.ahima.org/2009/11/02/more-delays-for-the-red-flags-rule/#comments</comments>
		<pubDate>Mon, 02 Nov 2009 18:06:20 +0000</pubDate>
		<dc:creator>Kevin Heubusch</dc:creator>
				<category><![CDATA[Privacy and security]]></category>

		<guid isPermaLink="false">http://journal.ahima.org/?p=1217</guid>
		<description><![CDATA[The Federal Trade Commission has announced a new delay for the Red Flags Rule. Enforcement will now begin June 1, 2010.
The delay, announced October 30, comes at the request of Congressional members, the FTC said. The rule was scheduled to go into effect November 1.
The announcement comes a week after the House of Representatives passed an [...]]]></description>
			<content:encoded><![CDATA[<p>The Federal Trade Commission has <a href="http://www.ftc.gov/opa/2009/10/redflags.shtm" target="_blank">announced a new delay</a> for the Red Flags Rule. Enforcement will now begin June 1, 2010.</p>
<p>The delay, announced October 30, comes at the request of Congressional members, the FTC said. The rule was scheduled to go into effect November 1.</p>
<p>The announcement comes a week after the House of Representatives passed <a href="http://journal.ahima.org/2009/10/22/exception-coming-on-red-flags-rule/" target="_blank">an amendment to the rule</a> that would exclude certain businesses, including small healthcare, accounting, and legal practices. The House bill is currently in the Senate.</p>
<p>On the day FTC announced the delay, the US District Court for the District of Columbia ruled that the FTC may not apply the Red Flags Rule to attorneys.</p>
<p>This is the fourth delay for the rule, which was originally scheduled to take effect November 1, 2008. Industry groups, including healthcare providers and lawyers, have pushed for an exclusion, while others have complained that the rule lacked sufficient detail and guidance. The FTC has since been adding <a href="http://www.ftc.gov/redflagsrule" target="_blank">information and guidance online</a>.</p>
<img src="http://feeds.feedburner.com/~r/JournalOfAhima/~4/MJFLOkWQOkw" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://journal.ahima.org/2009/11/02/more-delays-for-the-red-flags-rule/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		<feedburner:origLink>http://journal.ahima.org/2009/11/02/more-delays-for-the-red-flags-rule/</feedburner:origLink></item>
		<item>
		<title>Exposing Double Identity at Patient Registration</title>
		<link>http://feedproxy.google.com/~r/JournalOfAhima/~3/LbYEDxp8aZQ/</link>
		<comments>http://journal.ahima.org/2009/11/01/exposing-double-identity/#comments</comments>
		<pubDate>Sun, 01 Nov 2009 13:03:31 +0000</pubDate>
		<dc:creator>Chris Dimick</dc:creator>
				<category><![CDATA[Data quality]]></category>
		<category><![CDATA[HIM operations]]></category>

		<guid isPermaLink="false">http://journal.ahima.org/?p=1208</guid>
		<description><![CDATA[Keeping the organization’s master patient index clean leads some HIM departments all the way back to patient registration, where they collaborate to prevent errors before care starts. Accurate registration helps keep patient data complete and clean as it moves throughout the organization.
Long-term trouble can start during a brief check-in. A rushed or incomplete search of [...]]]></description>
			<content:encoded><![CDATA[<p>Keeping the organization’s master patient index clean leads some HIM departments all the way back to patient registration, where they collaborate to prevent errors before care starts. Accurate registration helps keep patient data complete and clean as it moves throughout the organization.</p>
<p>Long-term trouble can start during a brief check-in. A rushed or incomplete search of the organization’s MPI can cause clinical registrars to create duplicate patient records or even select the wrong record.</p>
<p>Faulty information entered at check-in streams straight through the system, risking treatment errors and leading to eventual billing problems. Entities that participate in health information exchange will export bad information into their networks.</p>
<p>Error-ridden MPIs also hamper an organization’s ability to understand its patient population and its own performance, both for internal and external reporting. Patient information spread across multiple records can distort measures of patient severity and overall risk of mortality. And correcting errors consumes time.</p>
<p>HIM departments often are the hub of identifying and mitigating registration errors. HIM staff sift through the MPI, merging duplicate records and  separating out information that has been overlaid into the wrong patient account.<span id="more-1208"></span></p>
<p>But what HIM learns about the types of MPI errors occurring in patient registration may never be shared with that department. Because HIM and registration are typically managed through different departments, there can be an information exchange disconnect between the two areas. If registration staff do not know what they are doing wrong, how can they correct it?</p>
<p>Some facilities have instituted registration improvement programs, which can feature cross-department committees whose purpose is to reduce registration errors and clean up the MPI.</p>
<h5>Providing Feedback to Registration</h5>
<p>Not only do these registration improvement processes eventually reduce work for HIM, they also give vital feedback to registration staff about how their actions directly impact the medical record and patient care, according to Gwyndle Kravec, MBA, RHIA, CCS, director of HIM and privacy officer at Peninsula Regional Medical Center, based in Salisbury, MD. Peninsula instituted a registration improvement program that has greatly reduced MPI errors.</p>
<p>“I think this program heightens the awareness that this is an issue of data quality and that these [duplicate MPIs] do impact patient safety,” Kravec says. “When you heighten awareness of what the downstream effects are of having a duplicate medical record, then I think [registrars] are more conscientious of what they are doing. They want to get it right.”</p>
<p>Registration improvement programs can be simple or elaborate, depending on what investment a facility feels is appropriate to clean up its MPI and registration processes.</p>
<p>The HIM department at Christiana Care Health System, based in Newark, DE, has worked with the facility’s registration areas for several years to improve registration processes and reduce MPI duplicates and overlays. The initiative is an important part of ensuring health records are complete and accurate, says Kathy Westhafer, RHIA, CHPS, program manager for clinical information.</p>
<p>“We are looking for that MPI to really be the focus of how we identify the patient, that we have one record for the patient within the health system,” Westhafer says.</p>
<p>Each day a team of Christiana Care HIM professionals uses a clinical system tool that identifies possible MPI duplicates and overlays. A notification tool is also available for all staff to report possible duplicate MPI accounts. HIM staff investigates these suggested cases, merging duplicate MPIs or separating out information in overlay cases.</p>
<p>“That team is doing the research and determining if it is a situation where two people were merged inappropriately, in an overlay situation, or if it is really one person that has multiple records,” Westhafer says.</p>
<p>Because each ancillary area at Christiana Care conducts patient registration, duplicate and overlay MPI cases are compiled by HIM and separated by the specific ancillary area where the error occurred. Reports describing the circumstances of the error are circulated monthly to the various registration area managers. The information is used to create better registration processes as well as develop specific education for registration staff, Westhafer says.</p>
<p>Providing feedback to the registration departments is key to the facility’s MPI cleanup efforts. Instead of HIM doing cleanup work solely on the back end, registration now can use the information to improve accuracy on the front end, Westhafer says.</p>
<p>Since Christiana Care started its improvement processes, registration errors have been significantly reduced. A recent audit showed the organization’s MPI duplication rate accounts for fewer than 2 percent of all MPI records, a typical industry benchmark for MPI best practices, Westhafer says.</p>
<p>“We felt really good that the processes that we have put in place over the years seem to have worked,” she says.</p>
<h5>Direct Training for Dramatic Results</h5>
<p>In other organizations, HIM may have a more hands-on role in registration improvement efforts. At Peninsula, MPI duplication rates were so high that in 2007 the HIM department staff formed a committee and began direct education with registrars.</p>
<p>At that time, Peninsula’s registration staff was not taking enough time to accurately select or create MPI numbers. HIM staff struggled to fix the resulting duplicate accounts being entered into the system each day.</p>
<p>“We were processing 60 duplicates a week,” Kravec recalls. “Some of those were expected as part of our [trauma] registration process, but a majority of them were errors. So we had to get together because [the registration department] were not taking accountability. They were creating the error, and HIM was cleaning it up.”</p>
<p>The resulting committee, made up of representatives from HIM, patient registration, finance, IT, and labs, meets monthly to review duplication creation rates, discuss trends in registration data errors, and create new processes to correct the mistakes. A registrar is also invited to each meeting to discuss how a registration error occurred and how it could be prevented in the future.</p>
<p>Through the program, HIM collects all MPI account duplicates and sends them to the registration department manager. The registration manager uses the information for educational training in the department and monitoring which registrars are habitually creating errors. Under a disciplinary action program, a registrar who creates three duplicate MPI accounts within a rolling one-year time period is terminated from the organization. The policy holds registrars accountable for their mistakes and has helped reduce the number of errors committed, Kravec says.<br />
 <br />
Also, once a month the HIM operational manager will visit the registration department and conduct quality training with the registrars. The manager provides registrars the recent duplicate MPI rates and shares specific examples of recent registration errors that HIM has found. The HIM manager also observes the registrars at work, watching for any shortcuts that could lead to registration errors, Kravec says.</p>
<p>“There were so many errors and missing information in different records that we knew we needed to get something done,” Kravec says. “So we built in this ad-hoc way to do it where the HIM manager goes up [to registration] and does training on a monthly basis and brings true live examples where they registered a patient incorrectly.”</p>
<p>The registration improvement program has drastically reduced the number of MPI account duplicates at Peninsula.</p>
<p>In the first year of the program, MPI duplication rates dropped 23 percent from the previous year. By the end of the second year, rates had dropped 57 percent compared to rates before the improvement program was implemented.</p>
<p>“It is less resources I’m using, and my identity coordinator can certainly use their time doing better things than merging duplicate records,” Kravec says. “It is not just with one system—we have 17 downstream systems that it impacts. We have to coordinate and synchronize these merges so that patient safety is not impacted in a negative way.”</p>
<p>The registration improvement program at Peninsula is vital in keeping the duplication rates under control. It holds people accountable for their actions, Kravec says. “You do betterwhen you think somebody is watching,” she says. “Now if we stopped the program or stopped the [training] on these, I can see these numbers reversing.”</p>
<h5>How Registration Errors Occur</h5>
<p>The cause of registration errors varies from simple accidents to negligence.</p>
<p>The turnover rate for registration department employees is especially high in many facilities. With new employees regularly starting work, education on proper MPI creation is constantly needed, Westhafer says.</p>
<p>The rush to register patients can also affect error rates. At Peninsula, the emergency department has a policy that patients should be registered within two minutes so treatment is not delayed. Nearly 65 percent of Peninsula’s patients are admitted through the ED.</p>
<p>Registering a patient within two minutes is a lot of pressure, Kravec says, and with both patients and registrars in such a hurry, mistakes can easily be made. </p>
<p>The most common registration error at Peninsula is misspelling a patient’s name when searching the MPI. Because of this, the MPI duplication committee has asked registrars to confirm at least three unique identifiers in a patient’s record—such as name, Social Security number, and date of birth—before assuming they have found the correct file.</p>
<p>Many registration mistakes can be avoided by requiring registrars to ask patients if they have ever been to the hospital before. “That is very simple, but there were some registrars that never asked that,” Kravec says.</p>
<p>Technological problems are partly to blame for some registration errors at Christiana Care. The facility’s registration system is nearly 20 years old and in dire need of upgrade, Westhafer says. “There are inherent problems with a 20-year-old system in that you are very limited in how you can search [for MPI records],” she says.</p>
<p>The organization has decided to replace the registration system, and Westhafer says staff is looking for a system that makes it easier for registrars to look up MPI records.</p>
<p>One guideline at Christiana Care contributes to duplicate records, intentionally. Registrars are instructed to create a new record if they cannot confirm they have correctly matched a patient to an existing record. “We have told registers, ‘when in doubt—unless you are positive—it is better for you to create a duplicate than it would be to choose somebody incorrectly,’” Westhafer says. HIM staff would rather merge a duplicate record than sort out patient information from an incorrect account, Westhafer explains.</p>
<h5>Getting Started</h5>
<p>Improvement programs do not need to be elaborate. Merely sharing duplicate creation rates with registration staff can help reduce errors. Registration management can use the rates to help develop new registration procedures, train registrars, and track improvement progress.</p>
<p>Facilities looking to create programs should first track their duplication rates. Identifying specific MPI issues will help organize a response to the problem. Next, they can create a project assessment and determine which facility departments would be affected by a registration improvement program. Contact those parties and invite them to help develop the project, Kravec recommends.</p>
<p>Regardless of how the errors occur, an important part of a registration improvement program is educating registrars about the impact their work has on the rest of the facility. Registration’s impact on patient care is a focal point of the education sessions HIM conducts at Peninsula, Kravec says.</p>
<p>Just educating registrars on the importance of finding the correct patient MPI during registration can have a positive impact on their work.</p>
<p>“Registrars didn’t have the full picture before this program,” Kravec says. “Now they have the full picture.”</p>
<img src="http://feeds.feedburner.com/~r/JournalOfAhima/~4/LbYEDxp8aZQ" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://journal.ahima.org/2009/11/01/exposing-double-identity/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		<feedburner:origLink>http://journal.ahima.org/2009/11/01/exposing-double-identity/</feedburner:origLink></item>
		<item>
		<title>Journal of AHIMA – Nov-Dec 2009</title>
		<link>http://feedproxy.google.com/~r/JournalOfAhima/~3/3gem21_C2BI/</link>
		<comments>http://journal.ahima.org/2009/11/01/journal-of-ahima-nov-dec-2009/#comments</comments>
		<pubDate>Sun, 01 Nov 2009 13:00:01 +0000</pubDate>
		<dc:creator>Meg Featheringham</dc:creator>
				<category><![CDATA[In the magazine]]></category>

		<guid isPermaLink="false">http://journal.ahima.org/?p=1197</guid>
		<description><![CDATA[The cover story in the November-December Journal examines how healthcare organizations can plan to resolve the anticipated influx of disputed information in EHRs and PHRs. Other features outline downtime planning for health IT systems and the project to transition MS-DRGs to ICD-10-CM/PCS.

Members may read all stories online in the AHIMA Body of Knowledge. Select features and practice briefs are [...]]]></description>
			<content:encoded><![CDATA[<p>The cover story in the November-December <em>Journal</em> examines how healthcare organizations can plan to resolve the anticipated influx of disputed information in EHRs and PHRs. Other features outline downtime planning for health IT systems and the project to transition MS-DRGs to ICD-10-CM/PCS.</p>
<p><span id="more-1197"></span></p>
<p><em>Members may read all stories online in the <a href="http://www.ahima.org/">AHIMA Body of Knowledge</a>. <a href="http://library.ahima.org/xpedio/groups/public/documents/web_assets/bok1_016845.hcst">Select features </a>and <a href="http://library.ahima.org/xpedio/idcplg?IdcService=GET_SEARCH_RESULTS&amp;SearchProviders=master_on_ch1as13%2C&amp;ftx=1&amp;AdvSearch=True&amp;adhocquery=1&amp;urlTemplate=/xpedio/groups%2Fpublic%2Fdocuments%2Fweb_assets%2Fqueryresults.hcsp&amp;ResultCount=25&amp;SortField=xPubDate&amp;SortOrder=Desc&amp;QueryText=xPublishSite+%3Csubstring%3E+%60BoK%60+%3cAND%3e+%28xSource+%3csubstring%3e+%60AHIMA+Practice+Brief%60+%3cNOT%3e+xSource+%3csubstring%3e+%60AHIMA+Practice+Brief+attachment%60%29">practice briefs </a>are also available publicly.</em></p>
<h3><a href="http://journal.ahima.org/wp-content/uploads/09Nov_cover.gif"><img class="alignleft size-full wp-image-1199" title="09Nov_cover" src="http://journal.ahima.org/wp-content/uploads/09Nov_cover.gif" alt="09Nov_cover" width="154" height="200" /></a></h3>
<h3>November-December 2009</h3>
<h5>Features</h5>
<ul>
<li><a href="http://library.ahima.org/xpedio/groups/public/documents/ahima/bok1_045493.hcsp?dDocName=bok1_045493" target="_blank">Dispute Resolution: Planning for Disputed Information in EHRs and PHRs</a>, by Lydia Washington, MS, RHIA, CPHIMS; Ethan Katsh, JD; and Norman Sondheimer, PhD</li>
<li>Plan B: A Practical Approach to Downtime Planning in Medical Practices, by Cheryl Gregg Fahrenholz, RHIA, CCS-P; Lance J. Smith, RHIT, CCS-P; Kyle Tucker, RHIA, CCS; and Diana Warner, MS, RHIA, CHPS</li>
<li>Converting MS-DRGs to ICD-10-CM/PCS: Methods Used, Lessons Learned, by Rhonda Butler, CCS, CCS-P, and Janice Bonazelli, RN</li>
</ul>
<h5>In Addition</h5>
<ul>
<li>75 Years of HIM Education, by Shirley Eichenwald Maki, MBA, RHIA, FAHIMA</li>
</ul>
<h5>Practice Brief</h5>
<ul>
<li><a href="http://library.ahima.org/xpedio/groups/public/documents/ahima/bok1_045551.hcsp?dDocName=bok1_045551" target="_blank">Electronic Signature, Attestation, and Authorship (Updated)</a></li>
</ul>
<h5>Working Smart</h5>
<ul>
<li><a href="http://library.ahima.org/xpedio/groups/public/documents/ahima/bok1_045489.hcsp?dDocName=bok1_045489" target="_blank">Fear Factor: Ambiguities in State Law Leave Some Providers Hesitant to Adopt EHRs</a>, by Chris Dimick</li>
<li><a href="http://library.ahima.org/xpedio/groups/public/documents/ahima/bok1_045487.hcsp?dDocName=bok1_045487" target="_blank">Genomics and HIM: Three Areas of Increasing Intersection</a>, by W. Gregory Feero, MD, PhD; Selma Holden, MD; and Barbara Fuller, JD, RHIA, FAHIMA</li>
<li>Medical Device Deliberations: Data Issues to Consider When Purchasing and Implementing New Devices, by Beth Acker, RHIA</li>
<li>Communicating Security Efforts: Informing Consumers of Data Protection Programs Helps Build Trust, by John Parmigiani</li>
</ul>
<h5>Coding Notes</h5>
<ul>
<li><a href="http://library.ahima.org/xpedio/groups/public/documents/ahima/bok1_045483.hcsp?dDocName=bok1_045483" target="_blank">FY 2010 Changes to the Hospital IPPS</a>, by Kathy DeVault, RHIA, CCS</li>
<li>Coding in Critical Access Hospitals, by Karen M. Kostick, RHIT, CCS, CCS-P</li>
</ul>
<img src="http://feeds.feedburner.com/~r/JournalOfAhima/~4/3gem21_C2BI" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://journal.ahima.org/2009/11/01/journal-of-ahima-nov-dec-2009/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		<feedburner:origLink>http://journal.ahima.org/2009/11/01/journal-of-ahima-nov-dec-2009/</feedburner:origLink></item>
		<item>
		<title>Exception Coming on Red Flags Rule?</title>
		<link>http://feedproxy.google.com/~r/JournalOfAhima/~3/REadS5bFzss/</link>
		<comments>http://journal.ahima.org/2009/10/22/exception-coming-on-red-flags-rule/#comments</comments>
		<pubDate>Thu, 22 Oct 2009 13:51:26 +0000</pubDate>
		<dc:creator>Kevin Heubusch</dc:creator>
				<category><![CDATA[Physician practices]]></category>
		<category><![CDATA[Privacy and security]]></category>

		<guid isPermaLink="false">http://journal.ahima.org/?p=1179</guid>
		<description><![CDATA[The oft-delayed Red Flags Rule, scheduled to take effect November 1, may be in for a major change. A bill that passed the US House October 20 and arrived in the Senate the next day would exempt, among others, healthcare practices with 20 or fewer employees from meeting the law’s requirements.
The amendment is intended to [...]]]></description>
			<content:encoded><![CDATA[<p>The oft-delayed <a href="http://www.ftc.gov/bcp/edu/microsites/redflagsrule/index.shtml" target="_blank">Red Flags Rule</a>, scheduled to take effect November 1, may be in for a major change. A <a href="http://thomas.loc.gov/cgi-bin/bdquery/z?d111:h.r.03763:" target="_blank">bill</a> that passed the US House October 20 and arrived in the Senate the next day would exempt, among others, healthcare practices with 20 or fewer employees from meeting the law’s requirements.</p>
<p>The amendment is intended to relieve the administrative burden on small businesses.</p>
<p>The Red Flags Rule, part of the Fair and Accurate Credit Transaction Act of 2003, requires “creditors” and financial institutions to develop and implement written identity theft prevention programs. As described in the rule, creditors are organizations that maintain consumer accounts that receive multiple payments or payments made in installments.</p>
<p>In full, HR 3763 amends the Fair Credit Reporting Act to exclude “any health care practice, accounting practice, or legal practice with 20 or fewer employees.” It also excludes any other business that the Federal Trade Commission, which oversees the rule, determines:</p>
<ul>
<li>knows all its customers or clients individually;</li>
<li>only performs services in or around the residences of its customers; or </li>
<li>has not experienced incidents of identity theft, and identity theft is rare for businesses of that type.<span id="more-1179"></span></li>
</ul>
<p>The proposed amendment moved easily through the House. It was introduced October 8 and was voted on without debate on October 20. There were 400 votes to approve and no votes in opposition.</p>
<p>The House bill was received and read in the Senate and referred to the Committee on Banking, Housing, and Urban Affairs.</p>
<p>The Red Flags Rule was first scheduled to take effect November 2008. The Federal Trade Commission offered several delays to provide more guidance and give businesses more time to prepare.</p>
<h5>Provider Burden or Consumer Protection?</h5>
<p>Rep. John Adler (D-NJ) sponsored the bill. “The Federal Trade Commission went too far and went beyond the intent of Congress by considering non-financial, service-related industries to be ‘creditors’…,” he said in a floor speech before the vote.</p>
<p>“Its ruling would force thousands of small businesses to comply with burdensome, expensive regulations by forcing them to develop and implement an identity theft program.”</p>
<p>The American Medical Association also is opposed to inclusion of medical practices and has lobbied against it.</p>
<p>However, in a <a href="http://journal.ahima.org/wp-content/uploads/HR3763letter.pdf" target="_blank">letter</a> to the Senate committee chair, AHIMA argues that medical practices are already a target of identity thieves and that exempting them from the rule would motivate thieves to focus on them more.</p>
<p>AHIMA also noted that the bill has a much farther reach than might appear. Nearly half of physicians work in practices of six physicians or fewer, according to a 2008 report from the Centers for Medicare and Medicaid Services. At a time when medical identity theft and healthcare fraud are on the rise, the bill would exempt a large share of providers from having identity theft prevention programs.</p>
<p>In addition, the exemption would undermine efforts to raise awareness of identity theft and subsequent fraud within the healthcare industry, AHIMA wrote.</p>
<p>The Senate Committee on Banking, Housing, and Urban Affairs has yet to schedule discussion of the bill. With a full plate and the winter recess approaching, it is unclear if the committee will consider the House bill this year.</p>
<p><em>Updated Oct. 28</em></p>
<p><a href="http://www.ftc.gov/bcp/edu/microsites/redflagsrule/index.shtml"></a></p>
<img src="http://feeds.feedburner.com/~r/JournalOfAhima/~4/REadS5bFzss" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://journal.ahima.org/2009/10/22/exception-coming-on-red-flags-rule/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		<feedburner:origLink>http://journal.ahima.org/2009/10/22/exception-coming-on-red-flags-rule/</feedburner:origLink></item>
		<item>
		<title>No Script Needed for California Breach Notification</title>
		<link>http://feedproxy.google.com/~r/JournalOfAhima/~3/Ox359kMAHzA/</link>
		<comments>http://journal.ahima.org/2009/10/22/no-script-needed-ca-breach-notification/#comments</comments>
		<pubDate>Thu, 22 Oct 2009 13:19:48 +0000</pubDate>
		<dc:creator>Chris Dimick</dc:creator>
				<category><![CDATA[ARRA]]></category>
		<category><![CDATA[Privacy and security]]></category>

		<guid isPermaLink="false">http://journal.ahima.org/?p=1184</guid>
		<description><![CDATA[California Governor Arnold Schwarzenegger vetoed a state legislature bill on October 11 that would have specified content requirements for privacy breach notifications.
California law requires businesses and state agencies that have unencrypted personal information lost, stolen, or improperly accessed from their databases to notify affected consumers. However, the law does not specify what information the notification [...]]]></description>
			<content:encoded><![CDATA[<p>California Governor Arnold Schwarzenegger vetoed a state legislature bill on October 11 that would have specified content requirements for privacy breach notifications.</p>
<p>California law requires businesses and state agencies that have unencrypted personal information lost, stolen, or improperly accessed from their databases to notify affected consumers. However, the law does not specify what information the notification letters must contain.</p>
<p><a href="http://www.leginfo.ca.gov/cgi-bin/postquery?bill_number=sb_20&amp;sess=CUR&amp;house=B&amp;search_type=email" target="_blank">Senate bill 20</a> would have ensured businesses include key information in their notices, such as the type of personal information breached, a description of the incident, the date it took place, and who to contact for more information.</p>
<p>The bill was vetoed, Schwarzenegger wrote in his explanation, because there is no evidence of a problem with the information businesses are currently providing consumers.<span id="more-1184"></span></p>
<p>The veto does not dramatically affect state healthcare organizations, which beginning September 23 must meet similar requirements under federal breach notification laws. The federal laws require companies that handle personal health information to include specific information in breach notification letters, including date of the incident and the personal information breached.</p>
<p>However, the federal provisions—part of the American Recovery and Reinvestment Act’s HITECH section—only cover healthcare businesses, leaving California organizations such as banks and educational institutions open to include as much or as little information in their breach notifications as they deem appropriate.</p>
<h5>Veto “Surprising”</h5>
<p>Senate bill 20 was proposed by state senator Joe Simitian, who said it was necessary to ensure that victims receive the information they need to understand the problem and protect themselves from harm.</p>
<p>“This is one of the most surprising vetoes I’ve gotten while I’ve been here, over nine years,” Simitian said.</p>
<p>The bill had moved through the state legislature with strong support.</p>
<p>Simitian acknowledged that the majority of the notices that go out to consumers do contain adequate, helpful information. However, he said there have been instances of vague and meaningless breach notifications.</p>
<p>A survey of data breach victims included in a 2007 University of California-Berkeley School of Law paper found that 28 percent of those receiving a breach notification did not understand the “potential consequences of the breach after reading the letter.” Simitian cited this study as well as personal conversations with confused breach notification recipients to explain why legislation is needed.</p>
<p>The proposed additions to California’s privacy law would not break new ground. Several states have added similar breach notice requirements to their privacy laws, Simitian said. Setting notification requirements could also benefit businesses by spelling out their responsibilities. Having clear-cut requirements saves businesses from guessing at what they should do to be compliant.</p>
<p>While he feels the breach notification content requirements were not necessarily a bad idea, California-based healthcare attorney Reece Hirsch said he can understand why the bill was vetoed. Hirsch, a partner with Morgan Lewis’s FDA/Healthcare regulation practice, has helped clients draft many breach notifications. The breach notification requirements proposed in the bill are considered best practices in the field and already followed, he noted.</p>
<p>“Most companies responding to a security breach under the existing law would typically include the elements that are stated in senate bill 20,” Hirsch said. “Certainly there are consumer groups who have felt that these notices are maybe confusing, not as forthcoming as they should be.</p>
<p>“But by and large I am not sure that the elements that were specified in senate bill 20 would really affect a real change in the sorts of notices that consumers are seeing under the current California law.”</p>
<h5>No Copy for the Attorney General</h5>
<p>Senate bill 20 also called on businesses to send a copy of their breach notifications to the California attorney general if the breach affected more than 500 people. The provision was included to give law enforcement and the legislature a way to track privacy breaches across industries and identify trends, Simitian said.</p>
<p>In his veto message, Schwarzenegger wrote there was “no additional consumer benefit” to the provision because the bill does not require the attorney general to do anything with the notices.</p>
<p>“I thought there was a little irony in the veto message suggesting that we didn’t have evidence of the nature of the problem, and then going on to say ‘and by the way, why on earth would you want to have a place where there is a repository of this information,’” Simitian said.</p>
<p>Under state law that took effect January 1 of this year, healthcare organizations are already required to report breaches of any size to the California Department of Public Health, Center for Health Care Quality, which has power to investigate and fine organizations.</p>
<p>However, sending a breach notice directly to the attorney general could have increased an organization’s chance of being prosecuted, Hirsch noted. The federal breach notification provisions give attorneys general the power to enforce privacy protections and take enforcement action against healthcare organizations that have experienced a breach of protected health information.</p>
<p>Though the bill was vetoed, Simitian said he will have conversations with the California governor’s office on how to get the bill passed. He plans to reintroduce the legislation next year.</p>
<h5>The Federal Content Requirements</h5>
<p>Two federal laws govern breach notification. <a href="http://journal.ahima.org/2009/08/24/hhs-releases-breach-notification-rule/" target="_blank">A rule</a> promulgated by the Department of Health and Human Services governs HIPAA covered entities; <a href="http://journal.ahima.org/2009/08/25/ftc-releases-breach-notification-rule/" target="_blank">a rule</a> published by the Federal Trade Commission applies to noncovered entities such as personal health record vendors.</p>
<p>The rule governing covered entities spells out that breach notifications must:</p>
<ul>
<li>Be written in plain language</li>
<li>Describe what happened, including the date of breach and discovery (if known)</li>
<li>Describe the types of unsecured personal information involved in the breach</li>
<li>Provide steps individuals should take to protect themselves</li>
<li>Give a brief description of what the healthcare organization is doing to investigate, mitigate harm, and protect against further breaches</li>
<li>Describe contact procedures for patient questions, including a toll-free telephone number</li>
</ul>
<p>The rule currently exists as an interim final rule, meaning that it could be modified based on public comments. The comment period ends this Friday, October 23. The FTC law governing noncovered entities has similar content requirements, though it provides less detail.</p>
<p>The California bill would have required businesses to include two items in addition to what the federal laws specify:</p>
<ul>
<li>Contact information for credit reporting agencies</li>
<li>A statement describing whether there was a delay in notification because of law enforcement investigations</li>
</ul>
<img src="http://feeds.feedburner.com/~r/JournalOfAhima/~4/Ox359kMAHzA" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://journal.ahima.org/2009/10/22/no-script-needed-ca-breach-notification/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		<feedburner:origLink>http://journal.ahima.org/2009/10/22/no-script-needed-ca-breach-notification/</feedburner:origLink></item>
		<item>
		<title>ICD-10-CM/PCS Project Management Resources</title>
		<link>http://feedproxy.google.com/~r/JournalOfAhima/~3/HN_pBPtZoNg/</link>
		<comments>http://journal.ahima.org/2009/10/20/icd-10-cmpcs-project-management-resources/#comments</comments>
		<pubDate>Tue, 20 Oct 2009 16:55:22 +0000</pubDate>
		<dc:creator>Meg Featheringham</dc:creator>
				<category><![CDATA[Coding & reimbursement]]></category>
		<category><![CDATA[ICD-10]]></category>

		<guid isPermaLink="false">http://journal.ahima.org/?p=1175</guid>
		<description><![CDATA[Organizations looking to begin the transition to ICD-10-CM/PCS can find project management resources in the October practice brief “Transitioning ICD-10-CM/PCS Data Management Processes.” Web-only resources include:

Sample project communication plan
Sample project plan
Sample project progress report
Sample issues log

The online version also includes a list of communication aids that organizations may use in the transition to ICD-10-CM/PCS and [...]]]></description>
			<content:encoded><![CDATA[<p>Organizations looking to begin the transition to ICD-10-CM/PCS can find project management resources in the October practice brief <a href="http://library.ahima.org/xpedio/groups/public/documents/ahima/bok1_044963.hcsp?dDocName=bok1_044963">“Transitioning ICD-10-CM/PCS Data Management Processes.”</a> Web-only resources include:</p>
<ul>
<li>Sample project communication plan</li>
<li>Sample project plan</li>
<li>Sample project progress report</li>
<li>Sample issues log</li>
</ul>
<p>The online version also includes a list of communication aids that organizations may use in the transition to ICD-10-CM/PCS and a contact form for the major stakeholders leading the ICD-10-CM/PCS implementation.</p>
<p>As the practice brief notes, planning for the transition to ICD-10-CM/PCS is a multifaceted effort. Defining the organization’s data management plan will facilitate a smooth transition to ICD-10-CM/PCS and optimize its greater specificity.</p>
<img src="http://feeds.feedburner.com/~r/JournalOfAhima/~4/HN_pBPtZoNg" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://journal.ahima.org/2009/10/20/icd-10-cmpcs-project-management-resources/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		<feedburner:origLink>http://journal.ahima.org/2009/10/20/icd-10-cmpcs-project-management-resources/</feedburner:origLink></item>
		<item>
		<title>Converting MS-DRGs to ICD-10</title>
		<link>http://feedproxy.google.com/~r/JournalOfAhima/~3/Kv9Ofp-layw/</link>
		<comments>http://journal.ahima.org/2009/10/14/converting-ms-drgs-to-icd-10/#comments</comments>
		<pubDate>Wed, 14 Oct 2009 21:34:07 +0000</pubDate>
		<dc:creator>Kevin Heubusch</dc:creator>
				<category><![CDATA[Coding & reimbursement]]></category>
		<category><![CDATA[ICD-10]]></category>

		<guid isPermaLink="false">http://journal.ahima.org/?p=1165</guid>
		<description><![CDATA[Like the rest of us, MS-DRGs have to transition to ICD-10-CM/PCS. Their conversion is off to a good start, with a preliminary version already available.
The conversion project offered an early test of the General Equivalence Mappings and provides organizations with a process for converting their own applications to ICD-10-CM/PCS.
Rhonda Butler and Janice Bonazelli, senior clinical [...]]]></description>
			<content:encoded><![CDATA[<p>Like the rest of us, MS-DRGs have to transition to ICD-10-CM/PCS. Their conversion is off to a good start, with a preliminary version already available.</p>
<p>The conversion project offered an early test of the General Equivalence Mappings and provides organizations with a process for converting their own applications to ICD-10-CM/PCS.</p>
<p>Rhonda Butler and Janice Bonazelli, senior clinical analysts at 3M Health Information Systems, offer an <a href="http://journal.ahima.org/wp-content/uploads/JAHIMA_Nov09.pdf" target="_blank">overview of the conversion</a> in this early look into the upcoming November/December issue of the Journal.</p>
<img src="http://feeds.feedburner.com/~r/JournalOfAhima/~4/Kv9Ofp-layw" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://journal.ahima.org/2009/10/14/converting-ms-drgs-to-icd-10/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		<feedburner:origLink>http://journal.ahima.org/2009/10/14/converting-ms-drgs-to-icd-10/</feedburner:origLink></item>
	</channel>
</rss>
