<?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/"
	>

<channel>
	<title>Journal of AHIMA</title>
	<atom:link href="http://journal.ahima.org/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>
	<pubDate>Thu, 02 Jul 2009 03:18:52 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.7</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>Journal of AHIMA - July 2009</title>
		<link>http://journal.ahima.org/2009/07/01/journal-of-ahima-july-2009/</link>
		<comments>http://journal.ahima.org/2009/07/01/journal-of-ahima-july-2009/#comments</comments>
		<pubDate>Wed, 01 Jul 2009 13:05:15 +0000</pubDate>
		<dc:creator>Meg Featheringham</dc:creator>
		
		<category><![CDATA[In the magazine]]></category>

		<guid isPermaLink="false">http://journal.ahima.org/?p=734</guid>
		<description><![CDATA[The July feature article takes a look at how HIM professionals have integrated POA reporting into their workflow processes and reporting requirements over the past two years. Other features report on the use of ICD-10 for mortality coding, how to make the most of external coding audits, and the benefits of standards development organizations that collaborate together.
Members may read [...]]]></description>
			<content:encoded><![CDATA[<p>The July feature article takes a look at how HIM professionals have integrated POA reporting into their workflow processes and reporting requirements over the past two years. Other features report on the use of ICD-10 for mortality coding, how to make the most of external coding audits, and the benefits of standards development organizations that collaborate together.<span id="more-734"></span></p>
<p><em>Members may read all stories online in the </em><a href="http://www.ahima.org/" target="_blank"><span style="color: #073766;"><em>AHIMA FORE Library: HIM Body of Knowledge</em></span></a><em>. </em><a href="http://library.ahima.org/xpedio/groups/public/documents/web_assets/bok1_016845.hcst" target="_blank"><span style="color: #073766;"><em>Select features </em></span></a><em>and </em><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" target="_blank"><span style="color: #073766;"><em>practice briefs</em></span></a><em> also are available publicly.</em></p>
<p><a href="http://journal.ahima.org/wp-content/uploads/july09_cover.gif"><img class="alignleft size-full wp-image-735" title="july09_cover" src="http://journal.ahima.org/wp-content/uploads/july09_cover.gif" alt="july09_cover" width="150" height="195" /></a></p>
<h3>July 2009</h3>
<h5>Features</h5>
<ul>
<li><a href="http://library.ahima.org/xpedio/groups/public/documents/ahima/bok1_043994.hcsp?dDocName=bok1_043994" target="_blank">Present on Admission: Where We Are Now</a>, by Gail Garrett, RHIT</li>
<li>Mortality Coding Marks 10 Years of ICD-10, by Chris Dimick</li>
<li>Making the Most of External Coding Audits, by Cathy Brownfield, RHIA, CCS, and Donna M. Didier, MEd, RHIA, CCS</li>
<li><a href="http://library.ahima.org/xpedio/groups/public/documents/ahima/bok1_043995.hcsp?dDocName=bok1_043995" target="_blank">Healthcare Standards Development: The Value of Nurturing Collaboration</a>, by William Edward Hammond, PhD, Charles Jaffe, MD, PhD, and Rebecca Daniels Kush, PhD</li>
</ul>
<h5>In Addition</h5>
<ul>
<li>Classifications without Borders, by Sue Bowman, RHIA, CCS, and Rita Scichilone, MHSA, RHIA, CCS, CCS-P, F-CHC</li>
</ul>
<h5>Practice Brief</h5>
<ul>
<li><a href="http://library.ahima.org/xpedio/groups/public/documents/ahima/bok1_044000.hcsp?dDocName=bok1_044000" target="_blank">Managing the Integrity of Patient Identity in Health Information Exchange</a></li>
</ul>
<h5>Working Smart</h5>
<ul>
<li>Documenting Data Loss, by Sandra Nunn, MA, RHIA, CHP</li>
<li>Amendments to FERPA Regulations, by Laurie A. Rinehart-Thompson, JD, RHIA, CHP</li>
<li>Preparing for ICD-10-CM, by Eric Rose, MD, FAAFP</li>
<li>Parental Proxy Access via Web Portals, by Sheila Green-Shook, MHA, RHIA, CHP</li>
</ul>
<h5>Coding Notes</h5>
<ul>
<li>New Guidance for Home Health Coding, by Ida Blevins, RHIA</li>
<li><a href="http://library.ahima.org/xpedio/groups/public/documents/ahima/bok1_043991.hcsp?dDocName=bok1_043991" target="_blank">The Casting Conundrum</a>, by Tanai S. Nelson, CCS, CCS-P, and Christina Benjamin, MA, RHIA, CCS, CCS-P</li>
</ul>
]]></content:encoded>
			<wfw:commentRss>http://journal.ahima.org/2009/07/01/journal-of-ahima-july-2009/feed/</wfw:commentRss>
		</item>
		<item>
		<title>Classifications without Borders</title>
		<link>http://journal.ahima.org/2009/07/01/classifications-without-borders/</link>
		<comments>http://journal.ahima.org/2009/07/01/classifications-without-borders/#comments</comments>
		<pubDate>Wed, 01 Jul 2009 13:02:10 +0000</pubDate>
		<dc:creator>Kevin Heubusch</dc:creator>
		
		<category><![CDATA[Clinical terminologies]]></category>

		<category><![CDATA[Coding & reimbursement]]></category>

		<guid isPermaLink="false">http://journal.ahima.org/?p=753</guid>
		<description><![CDATA[AHIMA representatives to the World Health Organization participate in the development and maintenance of classifications that create consistent data worldwide. In the July print edition, Sue Bowman and Rita Scichilone describe three work groups on which they serve. This online version of the story includes additional information on each group’s specific charges.
* * *
The World [...]]]></description>
			<content:encoded><![CDATA[<p><em>AHIMA representatives to the World Health Organization participate in the development and maintenance of classifications that create consistent data worldwide. In the July print edition, <a href="mailto: sue.bowman@ahima.org">Sue Bowman </a>and <a href="mailto: rita.scichilone@ahima.org">Rita Scichilone</a> describe three work groups on which they serve. This online version of the story includes additional information on each group’s specific charges.</em></p>
<p>* * *</p>
<p>The World Health Organization maintains the Family of International Classifications, a suite of classification products that may be used in an integrated fashion to compare health information internationally and nationally. The International Classification of Diseases is published and maintained by WHO-FIC. ICD-10 is the current edition, and ICD-11 is in development.</p>
<p>Internationally endorsed classifications such as those in WHO-FIC facilitate the storage, retrieval, analysis, and interpretation of data; they enable the comparison of data within populations over time and between populations at the same point in time. Their use results in the compilation of internationally consistent data.<span id="more-753"></span></p>
<p>Accordingly, WHO-FIC seeks to</p>
<ul>
<li>improve health through provision of sound health information to support decision making at all levels;</li>
<li>provide a conceptual framework of information domains for which classifications are, or are likely to be, required for purposes related to health and health management;</li>
<li>provide a suite of endorsed classifications for particular purposes defined within the framework;</li>
<li>promote the appropriate selection of classifications in a wide range of settings in the health field across the world;</li>
<li>establish a common language to improve communication;</li>
<li>permit comparisons of data within and between member states, health care disciplines, services and time; and</li>
<li>stimulate research on health and the health system.</li>
</ul>
<p>WHO has designated a number of collaborating centers to work with it in the development, dissemination, maintenance, and use of WHO-FIC. The WHO Collaborating Center for the Classification of Diseases for North America was established in 1976 to represent the US and Canada in international activities related to study and revision of ICD.</p>
<p>Now known as the WHO Collaborating Center for the Family of International Classifications for North America (abbreviated as NACC), it is located at the National Center for Health Statistics, a part of the US Centers for Disease Control and Prevention.</p>
<p>NACC works in close collaboration with two Canadian agencies: the Canadian Institute for Health Information and Statistics Canada. It maintains liaison with WHO on use, implementation, and maintenance of the FIC by the US and Canadian governments.</p>
<p>Nine WHO committees and reference groups contribute to maintaining the FIC:</p>
<ul>
<li>Update and Revision Committee</li>
<li>Education Committee</li>
<li>Implementation Committee</li>
<li>Family Development Committee</li>
<li>Electronic Tools Committee</li>
<li>Mortality Reference Group</li>
<li>Morbidity Reference Group</li>
<li>Functioning and Disability Reference Group</li>
<li>Terminology Reference Group</li>
</ul>
<p>In addition to representatives from the collaborating centers who are members of the WHO-FIC network, other classification, health information, and clinical experts can be appointed by respective collaborating centers to represent their respective countries.</p>
<p>Representatives from AHIMA currently serve on three committees and reference groups: the Morbidity Reference Group, the Terminology Reference Group, and the Education Committee.</p>
<h5>Morbidity Reference Group</h5>
<p>The Morbidity Reference Group seeks to improve international comparability of morbidity data and the application of ICD in morbidity by analyzing and integrating needs deriving from statistics (e.g., hospital data), case mix (e.g., DRG systems), and clinical documentation (e.g., clinical terminology and electronic health records).</p>
<p>AHIMA’s participation helps provide the US health information management perspective to the process of developing and maintaining current and future versions of ICD and developing associated international usage rules.</p>
<p>While differences in national regulatory requirements and reimbursement systems inevitably lead to differences in clinical modifications of ICD and reporting rules, the goal is to minimize these differences and achieve international data consistency and comparability, to the extent possible, through international collaboration.</p>
<p>Sue Bowman, RHIA, CCS, AHIMA director of coding policy and compliance, currently serves on the Morbidity Reference Group and shares a US vote with Donna Pickett, MPH, RHIA, medical systems administrator at the National Center for Health Statistics.</p>
<p>The group:</p>
<ul>
<li>Identifies, discusses, and solves problems related to the interpretation and application of ICD to coding and classification of morbidity, including the establishment of standardised interpretation of the categories and the development of agreed definitions, coding rules and guidelines</li>
<li>Develops recommendations for ICD-10 updates for forwarding to the Update and Revision Committee annually, through a democratic process that attempts to achieve consensus</li>
<li>Supports the revision process for ICD by providing advice on morbidity-related issues and possible terminology linkage for morbidity coding</li>
<li>Reviews possible morbidity applications of WHO-derived and related classifications, to inform recommendations for change to ICD</li>
<li>Considers and supports statistical, epidemiological, reimbursement (including casemix), and clinical applications of ICD for morbidity purposes</li>
<li>Constructs a database summarizing national applications of ICD for morbidity purposes</li>
<li>Provides documentation of discussions and decisions in a database that can be used online and offline</li>
</ul>
<p>The Morbidity Reference Group participates in the development of ICD-11, as do all of the committees and reference groups.</p>
<h5>Terminology Reference Group</h5>
<p>The Terminology Reference Group follows terminology and terminology systems developments and promotes awareness of the need to ensure and verify congruence between concepts underlying clinical terminologies and the WHO classifications.</p>
<p>The group first convened at the 2006 WHO-FIC meeting in Tunisia. Its establishment reflects the importance placed on the relationship between the classifications of WHO-FIC and the emerging clinical terminology initiatives around the world. Subsequent meetings were held in 2007 and 2008.</p>
<p>AHIMA director of practice leadership Rita Scichilone, MSHA, RHIA, CCS, CCS-P, F-CHC, serves as a US representative to the group. The group:</p>
<ul>
<li>Promotes awareness of the need to ensure and verify congruence between concepts in clinical terminologies and the categories available within the WHO-FIC products such as ICD and ICF</li>
<li>Collaborates with the research community, healthcare providers, software developers, and health authorities</li>
<li>Monitors and provides guidance for mapping between classification and clinical terminologies</li>
<li>Guides the evolution of WHO-FIC products (e.g., ICD-11) so new work takes account of the content and formalisms used to construct and maintain clinical terminologies</li>
</ul>
<p>Discussions between the International Healthcare Terminology Standards Development Organisation (IHTSDO) and WHO-FIC began in 2007 for harmonization of classification systems with the Systematized Nomenclature of Medicine Clinical Terms (SNOMED CT).</p>
<h5>Education Committee</h5>
<p>The Education Committee assists and advises WHO and the WHO-FIC Network in improving the level and quality of use of WHO-FIC in member states by developing an education, training, and certification strategy; identifying best training practices; and providing a network for sharing training expertise and experience. Its current work plans prioritize ICD and the International Classification of Disability, Functioning, and Health.</p>
<p>The Education Committee entered into a joint collaboration with the International Federation of Health Records Organizations (IFHRO) in 2001. IFHRO is a nongovernmental organization in official relations with WHO; AHIMA is its US representative. Together the Education Committee and IFHRO have developed an international training and certification program for ICD-10 coders and trainers. In cooperation with the WHO, they have been developing Web-based training tools for ICD-10 and the International Classification of Disability, Functioning, and Health.</p>
<p>AHIMA director of practice leadership Rita Scichilone serves as a US representative to the Education Committee. Its functions include:</p>
<ul>
<li>Assessment of the needs of users of the classifications, including those who provide source information, apply codes, conduct research or use the resulting data</li>
<li>Identification of the learning objectives for educational approaches</li>
<li>Inventory of existing educational materials and capacity</li>
<li>Recommendations for learning content including development of core curricula</li>
<li>Recommendations for best practices for promotion and delivery of educational material</li>
<li>Harmonization, review, development, and maintenance of self learning tools.</li>
</ul>
<h5>References</h5>
<p>Berg, Lars, and James R. Campbell. <a href="http://www.tc215wg3.nhs.uk/pages/docs/isotc215wg3_n362.pdf" target="_blank">“Mapping SNOMED CT to ICD-10—A Joint Task of IHTSDO and WHO-FIC.”</a> 2008.</p>
<p>National Center for Health Statistics. <a href="http://www.cdc.gov/nchs/about/otheract/icd9/nacc.htm" target="_blank">“WHO Collaborating Center for the Family of International Classifications for North America.”</a></p>
<p>World Health Organization. <a href="http://www.who.int/classifications/committees/committeetor.pdf" target="_blank">“Terms of Reference of the WHO-FIC Committees.”</a></p>
<p>World Health Organization. <a href="http://www.who.int/classifications/en" target="_blank">“The WHO Family of International Classifications.”</a></p>
]]></content:encoded>
			<wfw:commentRss>http://journal.ahima.org/2009/07/01/classifications-without-borders/feed/</wfw:commentRss>
		</item>
		<item>
		<title>2009 Coding Guide</title>
		<link>http://journal.ahima.org/2009/07/01/2009-coding-guide/</link>
		<comments>http://journal.ahima.org/2009/07/01/2009-coding-guide/#comments</comments>
		<pubDate>Wed, 01 Jul 2009 13:00:38 +0000</pubDate>
		<dc:creator>Meg Featheringham</dc:creator>
		
		<category><![CDATA[Buyers guides]]></category>

		<guid isPermaLink="false">http://journal.ahima.org/?p=739</guid>
		<description><![CDATA[Published in the July Journal, the 2009 Coding Guide is a special advertising section that promotes coding software, products, and services. 
The Journal of AHIMA publishes four Buyers Guides a year: Consulting/Outsourcing (February), Transcription (April), Coding (July), and Software and Health IT (September).
Click on the image to view the guide
]]></description>
			<content:encoded><![CDATA[<p><a title="2009 Coding Guide" href="http://journal.ahima.org/wp-content/uploads/09july_buyersguide2.pdf" target="_blank"><img style="float: left;" title="09july_buyersguide_cover" src="http://journal.ahima.org/wp-content/uploads/09july_buyersguide_cover.gif" alt="09july_buyersguide_cover" width="140" height="182" /></a>Published in the July <em>Journal,</em> the 2009 Coding Guide is a special advertising section that promotes coding software, products, and services. </p>
<p>The <em>Journal of AHIMA</em> publishes four Buyers Guides a year: Consulting/Outsourcing (February), Transcription (April), Coding (July), and Software and Health IT (September).</p>
<p>Click on the image to view the guide</p>
]]></content:encoded>
			<wfw:commentRss>http://journal.ahima.org/2009/07/01/2009-coding-guide/feed/</wfw:commentRss>
		</item>
		<item>
		<title>ONC Releases &#8220;Meaningful Use&#8221; Draft Definition</title>
		<link>http://journal.ahima.org/2009/06/16/onc-releases-meaningful-use-draft-definition/</link>
		<comments>http://journal.ahima.org/2009/06/16/onc-releases-meaningful-use-draft-definition/#comments</comments>
		<pubDate>Tue, 16 Jun 2009 16:25:38 +0000</pubDate>
		<dc:creator>Kevin Heubusch</dc:creator>
		
		<category><![CDATA[ARRA]]></category>

		<guid isPermaLink="false">http://journal.ahima.org/?p=715</guid>
		<description><![CDATA[ONC released a draft definition for the “meaningful use” of EHRs today, prepared by a workgroup of the Health IT Policy Committee.
The definition will in part determine which providers are eligible to receive incentive payments for the use of health IT under the American Recovery and Reinvestment Act. Providers who are “meaningful users” of health [...]]]></description>
			<content:encoded><![CDATA[<p>ONC released a <a onclick="pageTracker._trackPageview('/outbound/article/http://healthit.hhs.gov/portal/server.pt?open=512&amp;objID=1269&amp;parentname=CommunityPage&amp;parentid=4&amp;mode=2&amp;in_hi_userid=10741&amp;cached=true#MeaningfulUse');" href="http://healthit.hhs.gov/portal/server.pt?open=512&amp;objID=1269&amp;parentname=CommunityPage&amp;parentid=4&amp;mode=2&amp;in_hi_userid=10741&amp;cached=true#MeaningfulUse" target="_blank">draft definition</a> for the “meaningful use” of EHRs today, prepared by a workgroup of the Health IT Policy Committee.</p>
<p>The definition will in part determine which providers are eligible to receive incentive payments for the use of health IT under the American Recovery and Reinvestment Act. Providers who are “meaningful users” of health IT can receive up to $44,000 in increased Medicare and Medicaid payments over five years.</p>
<p>Public comments are due June 26.</p>
<p>The proposed definition features a series of evolving objectives and measures for 2011, 2013, and 2015. The objectives are keyed to five healthcare outcomes policy priorities identified in a 2008 report from the National Priorities Partnership, convened by the National Quality Forum.</p>
<p>The workgroup recommends meaningful use support the following five goals:<br />
<span id="more-715"></span></p>
<ul>
<li>Improve quality, safety, efficiency, and reduce health disparities</li>
<li>Engage patients and families</li>
<li>Improve care coordination</li>
<li>Improve population and public health</li>
<li>Ensure adequate privacy and security protections for personal health information</li>
</ul>
<p align="left">The policy committee workgroup highlights several aspects of the proposal for feedback in particular. In a preamble to the draft, it writes:</p>
<p>&#8220;We seek specific stakeholder feedback on whether the recommended timeline of requirements is overly aggressive based on the current state of technology and the demands on new provider workflows, or not challenging enough to result in significant transformation, in light of the declining level of Medicare incentives in future years.&#8221;</p>
<p>The draft recommends that the definition of meaningful use vary by setting. Thus &#8220;some features and capabilities will be recommended as required in an ambulatory setting before similar functions are expected to be widely used in the hospital.&#8221;</p>
<p>The group also singles out measures reporting for feedback, noting that there are currently &#8220;considerable gaps in EHR-generated measures available to monitor key desired policy outcomes.&#8221;</p>
<p>The workgroup&#8217;s proposal will not be the final word on meaningful use. In fact, it won&#8217;t be its own final word—the group has already been asked to present revisions at the full committee&#8217;s next meeting on July 16. Ultimately ONC and the Centers for Medicare and Medicaid Services will weigh a range of input and develop a proposed rule later this year. That proposal will be open for public comment for 60 days.</p>
<p><em>updated June 17</em></p>
]]></content:encoded>
			<wfw:commentRss>http://journal.ahima.org/2009/06/16/onc-releases-meaningful-use-draft-definition/feed/</wfw:commentRss>
		</item>
		<item>
		<title>Core Services to Support the EHR Lifecycle</title>
		<link>http://journal.ahima.org/2009/06/16/core-services-to-support-the-ehr-lifecycle/</link>
		<comments>http://journal.ahima.org/2009/06/16/core-services-to-support-the-ehr-lifecycle/#comments</comments>
		<pubDate>Tue, 16 Jun 2009 13:35:49 +0000</pubDate>
		<dc:creator>Kevin Heubusch</dc:creator>
		
		<category><![CDATA[ARRA]]></category>

		<category><![CDATA[Electronic records]]></category>

		<guid isPermaLink="false">http://journal.ahima.org/?p=685</guid>
		<description><![CDATA[The American Recovery and Reinvestment Act calls for the creation of regional health IT extension centers that help providers adopt and use health IT such as electronic health records. The Office of the National Coordinator for Health IT published a draft description of the program May 28, requesting comments by June 11.
While ONC&#8217;s draft description [...]]]></description>
			<content:encoded><![CDATA[<p>The American Recovery and Reinvestment Act calls for the creation of regional health IT extension centers that help providers adopt and use health IT such as electronic health records. The Office of the National Coordinator for Health IT published a <a href="http://journal.ahima.org/2009/05/28/onc-drafts-health-it-extension-program/" target="_blank">draft description</a> of the program May 28, requesting comments by June 11.</p>
<p>While ONC&#8217;s draft description rightly stressed the delivery of IT assistance, the centers and their clients will require a wider range of expertise for the full preparation, deployment, and management of health information communications and technology. Different phases of EHR implementation and use require differing skills.</p>
<p>In its <a href="http://journal.ahima.org/2009/06/15/more-clarity-consideration-needed-for-hit-extension-centers/" target="_blank">comments on the draft description</a>, AHIMA recommended that the final program define core services that include a range of services to assist in EHR use throughout a system’s lifecycle.</p>
<p>This range of services includes workflow analysis, transition planning, data analysis, and training. The sample phases of an EHR lifecycle shown below illustrate the differing core services that users may require over the entire lifecycle.<span id="more-685"></span></p>
<p>In its proposal, ONC indicated it could begin requesting applications from potential regional centers as early as this summer, with grants awarded this fall.</p>
<p><strong> Sample EHR Lifecycle and Possible Core Services</strong></p>
<table style="BORDER-RIGHT: medium none; BORDER-TOP: medium none; BORDER-LEFT: medium none; BORDER-BOTTOM: medium none; BORDER-COLLAPSE: collapse; mso-table-layout-alt: fixed; mso-padding-alt: 0in 5.4pt 0in 5.4pt" border="1" cellspacing="0" cellpadding="0">
<tbody>
<tr>
<td style="padding-right: 5.4pt; padding-left: 5.4pt; padding-bottom: 0in; width: 156.15pt; padding-top: 0in; height: 5.35pt; background-color: transparent; border: #ece9d8;" valign="top"><strong>Phases </strong></td>
<td style="padding-right: 5.4pt; padding-left: 5.4pt; padding-bottom: 0in; width: 156.15pt; padding-top: 0in; height: 5.35pt; background-color: transparent; border: #ece9d8;" valign="top"><strong>Description </strong></td>
<td style="padding-right: 5.4pt; padding-left: 5.4pt; padding-bottom: 0in; width: 156.15pt; padding-top: 0in; height: 5.35pt; background-color: transparent; border: #ece9d8;" valign="top"><strong>Core Services </strong></td>
</tr>
<tr>
<td style="padding-right: 5.4pt; padding-left: 5.4pt; padding-bottom: 0in; width: 156.15pt; padding-top: 0in; height: 19.25pt; background-color: transparent; border: #ece9d8;" valign="top">Initiation and planning</td>
<td style="padding-right: 5.4pt; padding-left: 5.4pt; padding-bottom: 0in; width: 156.15pt; padding-top: 0in; height: 19.25pt; background-color: transparent; border: #ece9d8;" valign="top">Assessments of current functions, vendor review and selection, resource planning</td>
<td style="padding-right: 5.4pt; padding-left: 5.4pt; padding-bottom: 0in; width: 156.15pt; padding-top: 0in; height: 19.25pt; background-color: transparent; border: #ece9d8;" valign="top">Vendor analysis, system review analysis, identifies business needs, risk assessment, impact analysis</td>
</tr>
<tr>
<td style="padding-right: 5.4pt; padding-left: 5.4pt; padding-bottom: 0in; width: 156.15pt; padding-top: 0in; height: 12.35pt; background-color: transparent; border: #ece9d8;" valign="top">Requirements analysis</td>
<td style="padding-right: 5.4pt; padding-left: 5.4pt; padding-bottom: 0in; width: 156.15pt; padding-top: 0in; height: 12.35pt; background-color: transparent; border: #ece9d8;" valign="top">Assessment and understanding of the business needs of the organization</td>
<td style="padding-right: 5.4pt; padding-left: 5.4pt; padding-bottom: 0in; width: 156.15pt; padding-top: 0in; height: 12.35pt; background-color: transparent; border: #ece9d8;" valign="top">Data flow analysis, workflow analysis</td>
</tr>
<tr>
<td style="padding-right: 5.4pt; padding-left: 5.4pt; padding-bottom: 0in; width: 156.15pt; padding-top: 0in; height: 19.25pt; background-color: transparent; border: #ece9d8;" valign="top">Design and development</td>
<td style="padding-right: 5.4pt; padding-left: 5.4pt; padding-bottom: 0in; width: 156.15pt; padding-top: 0in; height: 19.25pt; background-color: transparent; border: #ece9d8;" valign="top">Develop functional specifications of the vendor products to meet the needs of an organization</td>
<td style="padding-right: 5.4pt; padding-left: 5.4pt; padding-bottom: 0in; width: 156.15pt; padding-top: 0in; height: 19.25pt; background-color: transparent; border: #ece9d8;" valign="top">Database support and development, business case analysis, reports analysis, IT design</td>
</tr>
<tr>
<td style="padding-right: 5.4pt; padding-left: 5.4pt; padding-bottom: 0in; width: 156.15pt; padding-top: 0in; height: 19.25pt; background-color: transparent; border: #ece9d8;" valign="top">Development and testing</td>
<td style="padding-right: 5.4pt; padding-left: 5.4pt; padding-bottom: 0in; width: 156.15pt; padding-top: 0in; height: 19.25pt; background-color: transparent; border: #ece9d8;" valign="top">Modify systems according to the requirements and design; test software and functions</td>
<td style="padding-right: 5.4pt; padding-left: 5.4pt; padding-bottom: 0in; width: 156.15pt; padding-top: 0in; height: 19.25pt; background-color: transparent; border: #ece9d8;" valign="top">Software testing, functional user testing, data flow analysis</td>
</tr>
<tr>
<td style="padding-right: 5.4pt; padding-left: 5.4pt; padding-bottom: 0in; width: 156.15pt; padding-top: 0in; height: 19.25pt; background-color: transparent; border: #ece9d8;" valign="top">Implement</td>
<td style="padding-right: 5.4pt; padding-left: 5.4pt; padding-bottom: 0in; width: 156.15pt; padding-top: 0in; height: 19.25pt; background-color: transparent; border: #ece9d8;" valign="top">Move from testing to production of the system; users begin using products for daily clinical and business activities</td>
<td style="padding-right: 5.4pt; padding-left: 5.4pt; padding-bottom: 0in; width: 156.15pt; padding-top: 0in; height: 19.25pt; background-color: transparent; border: #ece9d8;" valign="top">Training and awareness, system process support, IT support</td>
</tr>
<tr style="height: 12.35pt; mso-yfti-irow: 6; mso-yfti-lastrow: yes;">
<td style="padding-right: 5.4pt; padding-left: 5.4pt; padding-bottom: 0in; width: 156.15pt; padding-top: 0in; height: 12.35pt; background-color: transparent; border: #ece9d8;" valign="top">Operations and maintenance</td>
<td style="padding-right: 5.4pt; padding-left: 5.4pt; padding-bottom: 0in; width: 156.15pt; padding-top: 0in; height: 12.35pt; background-color: transparent; border: #ece9d8;" valign="top">Full scale release of the system and continued use in the live environment</td>
<td style="padding-right: 5.4pt; padding-left: 5.4pt; padding-bottom: 0in; width: 156.15pt; padding-top: 0in; height: 12.35pt; background-color: transparent; border: #ece9d8;" valign="top">Follow up support, participation in learning community</td>
</tr>
</tbody>
</table>
]]></content:encoded>
			<wfw:commentRss>http://journal.ahima.org/2009/06/16/core-services-to-support-the-ehr-lifecycle/feed/</wfw:commentRss>
		</item>
		<item>
		<title>More Clarity, Consideration Needed for HIT Extension Centers</title>
		<link>http://journal.ahima.org/2009/06/15/more-clarity-consideration-needed-for-hit-extension-centers/</link>
		<comments>http://journal.ahima.org/2009/06/15/more-clarity-consideration-needed-for-hit-extension-centers/#comments</comments>
		<pubDate>Mon, 15 Jun 2009 21:04:02 +0000</pubDate>
		<dc:creator>Kevin Heubusch</dc:creator>
		
		<category><![CDATA[ARRA]]></category>

		<category><![CDATA[Electronic records]]></category>

		<category><![CDATA[Physician practices]]></category>

		<guid isPermaLink="false">http://journal.ahima.org/?p=677</guid>
		<description><![CDATA[AHIMA expressed support for a federal program establishing regional health IT extension centers that assist providers, but it registered concern that a program implemented ineffectively would cause confusion and contention and ultimately distract from the goal of EHR adoption and implementation.
AHIMA’s comments were in response to a draft description of the program published May 28 [...]]]></description>
			<content:encoded><![CDATA[<p>AHIMA expressed support for a federal program establishing regional health IT extension centers that assist providers, but it registered concern that a program implemented ineffectively would cause confusion and contention and ultimately distract from the goal of EHR adoption and implementation.</p>
<p><a href="http://www.ahima.org/dc/documents/AHIMA_ONCRFI_RegionalCenters_FINAL_090611.pdf" target="_blank">AHIMA’s comments</a> were in response to a <a href="http://journal.ahima.org/2009/05/28/onc-drafts-health-it-extension-program/" target="_blank">draft description</a> of the program published May 28 by the Office of the National Coordinator for Health IT. Specified under the American Recovery and Reinvestment Act, the program calls for a central Health IT Research Center with affiliated regional extension centers that provide direct assistance to providers. The centers will help providers meet requirements for receiving bonus Medicare and Medicaid payments under a separate ARRA provision.</p>
<p>AHIMA offered recommendations around four main comments:<span id="more-677"></span></p>
<p><strong>Establish a clear and consistent set of goals:</strong></p>
<ul>
<li>Define what constitutes a “region” for the regional centers</li>
<li>Clarify the relationship among the regional centers and between the regional centers and the central Health IT Research Center</li>
<li>Reconsider the proposed plan to issue multiple, closely spaced requests for proposals from organizations seeking to become regional centers </li>
<li>Consider mechanisms that ensure all providers are covered by qualified regional centers and that they are not penalized by any delay in accessing the services</li>
</ul>
<p><strong>Define a consistent set of core services delivered by an interdisciplinary team:</strong></p>
<ul>
<li>Further define the minimum level of services the regional centers must supply</li>
<li>Provide a consistent and uniform approach toward core services that addresses different functional components during each phase of an EHR implementation</li>
<li>Consider critical areas of health IT implementation that are not just technical in nature and require specialized skills, such as workflow analysis, transition planning, data analysis, training, and customization (see related story for <a href="http://journal.ahima.org/2009/06/16/core-services-to-support-the-ehr-lifecycle/" target="_blank">sample core services</a>)</li>
</ul>
<p><strong>Clarify the governance and management structure:</strong></p>
<ul>
<li>Define a clear and uniform structure for governance and management of the overall program, the regional centers, and the corresponding research center</li>
<li>Discuss a coordinated, consistent, and standard approach toward program planning and service delivery of the regional centers and their relationship to the resource center</li>
<li>Separate the research center’s research function from any management of the regional centers (the proposal seems to suggest that the research center will serve both roles)</li>
</ul>
<p><strong>Develop a sound program evaluation process that creates a learning community for sharing best practices with the resource center and among the regional centers:</strong></p>
<ul>
<li>Create a uniform and consistent approach toward evaluating the program</li>
<li>Develop a uniform measurement process that enables ONC to assess, evaluate, and make decision regarding future award programs, determining successful and unsuccessful regions, and defining areas that may need additional resources</li>
<li>Provide detail on the evaluation process</li>
</ul>
<p>In the draft program proposal, the Office of the National Coordinator indicated it could begin requesting applications from potential regional centers this summer, with grants awarded as early as the fall.</p>
]]></content:encoded>
			<wfw:commentRss>http://journal.ahima.org/2009/06/15/more-clarity-consideration-needed-for-hit-extension-centers/feed/</wfw:commentRss>
		</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>
		</item>
		<item>
		<title>HISPC Concludes with &#8220;Action Manual,&#8221; Webinars</title>
		<link>http://journal.ahima.org/2009/06/08/hispc-concludes-with-action-manual-webinars/</link>
		<comments>http://journal.ahima.org/2009/06/08/hispc-concludes-with-action-manual-webinars/#comments</comments>
		<pubDate>Mon, 08 Jun 2009 20:45:28 +0000</pubDate>
		<dc:creator>Kevin Heubusch</dc:creator>
		
		<category><![CDATA[Health information exchange]]></category>

		<category><![CDATA[Privacy and security]]></category>

		<guid isPermaLink="false">http://journal.ahima.org/?p=656</guid>
		<description><![CDATA[The HISPC summary report on the work of its final phase is out. Styled an “action and implementation manual,” it presents the work of the privacy and security group’s year-long third phase.
In addition to the summary report, the seven subgroups that comprise the collaboration are presenting their work through free webinars on Tuesdays and Thursdays [...]]]></description>
			<content:encoded><![CDATA[<p>The <a href="http://healthit.hhs.gov/html/hispc/AIMReport.pdf" target="_blank">HISPC summary report</a> on the work of its final phase is out. Styled an “action and implementation manual,” it presents the work of the privacy and security group’s year-long third phase.</p>
<p>In addition to the summary report, the seven subgroups that comprise the collaboration are presenting their work through free <a href="http://privacysecurity.rti.org/Default.aspx?tabid=101" target="_blank">webinars</a> on Tuesdays and Thursdays this month. The sessions focus on the tools and processes developed by each group, as well as how individual, local, regional, and state-level stakeholders can use them.<span id="more-656"></span></p>
<p>Formed in 2006, the Health Information Security and Privacy Collaboration was charged with studying privacy and security issues associated with interstate electronic health information exchange. It is managed by RTI International under a contract with the Department of Health and Human Services. The third phase, scheduled to end in April, received a <a href="http://journal.ahima.org/2009/04/01/hispc-privacy-receives-extension/" target="_blank">last-minute extension</a> through July. RTI will add an addendum to the recent report to describe the work of the extension.</p>
<p>Material from all three phases of the HISPC project—including documents, tools, reports, and products—are available through <a href="http://healthit.hhs.gov/portal/server.pt?open=512&amp;objID=1240&amp;parentname=CommunityPage&amp;parentid=8&amp;mode=2&amp;in_hi_userid=10882&amp;cached=true " target="_blank">Health and Human Services</a>.</p>
<p>Exactly how HISPC’s body of work will live on, and how directly it is promoted, is unclear given the changes in HHS personnel and programming brought about by the new presidential administration and the American Recovery and Reinvestment Act. However, ARRA’s goal to promote the secure, widespread exchange of electronic health records certainly relies on overcoming the barriers to health data exchange between states that HISPC identified and worked toward resolving.</p>
]]></content:encoded>
			<wfw:commentRss>http://journal.ahima.org/2009/06/08/hispc-concludes-with-action-manual-webinars/feed/</wfw:commentRss>
		</item>
		<item>
		<title>Reducing Healthcare Disparities through PHRs</title>
		<link>http://journal.ahima.org/2009/06/05/reducing-healthcare-disparities-phrs/</link>
		<comments>http://journal.ahima.org/2009/06/05/reducing-healthcare-disparities-phrs/#comments</comments>
		<pubDate>Fri, 05 Jun 2009 17:15:53 +0000</pubDate>
		<dc:creator>Kevin Heubusch</dc:creator>
		
		<category><![CDATA[Personal health records]]></category>

		<guid isPermaLink="false">http://journal.ahima.org/?p=650</guid>
		<description><![CDATA[Can health IT help reduce disparities in quality of care caused by racial and ethnic differences, geographic isolation, poverty, and low health literacy and consumer involvement? Authors of a new Journal web-exclusive story discuss the potential of personal health records to mitigate healthcare disparities.
HIM professionals can play four important roles, the authors write:

Advocating, designing, and [...]]]></description>
			<content:encoded><![CDATA[<p>Can health IT help reduce disparities in quality of care caused by racial and ethnic differences, geographic isolation, poverty, and low health literacy and consumer involvement? Authors of a new Journal web-exclusive story discuss the potential of personal health records to mitigate healthcare disparities.</p>
<p>HIM professionals can play four important roles, the authors write:</p>
<ul>
<li>Advocating, designing, and testing PHR products that are sensitive to underserved populations</li>
<li>Promoting PHR use within their communities</li>
<li>Training both consumers and providers in PHR use</li>
<li>Helping secure personal health information to both safeguard individuals and build the trust that will encourage consumer acceptance of health IT</li>
</ul>
<p>See <a href="http://library.ahima.org/xpedio/groups/public/documents/ahima/bok1_043826.hcsp?dDocName=bok1_043826" target="_blank">“Healthcare Disparities and the Role of Personal Health Records”</a> by Jennifer Garvin, Barbara Odom-Wesley, William J. Rudman, and Rachelle S. Stewart.</p>
<p>For a look at the need to improve data collection in support of efforts to reduce disparities, see the April 2009 Journal feature <a href="http://library.ahima.org/xpedio/groups/public/documents/ahima/bok1_043245.hcsp?dDocName=bok1_043245" target="_blank">“Data Collection and Reporting for Healthcare Disparities.”</a></p>
]]></content:encoded>
			<wfw:commentRss>http://journal.ahima.org/2009/06/05/reducing-healthcare-disparities-phrs/feed/</wfw:commentRss>
		</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>
		</item>
	</channel>
</rss>
