<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Journal of AHIMA &#187; Health information exchange</title>
	<atom:link href="http://journal.ahima.org/category/health-information-exchange/feed/" rel="self" type="application/rss+xml" />
	<link>http://journal.ahima.org</link>
	<description>The Journal of AHIMA is published monthly by the American Health Information Management Association</description>
	<lastBuildDate>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>
			<item>
		<title>$27.8 Million for IT in Community Health Centers</title>
		<link>http://journal.ahima.org/2009/09/30/27-8-million-for-it-in-community-health-centers/</link>
		<comments>http://journal.ahima.org/2009/09/30/27-8-million-for-it-in-community-health-centers/#comments</comments>
		<pubDate>Wed, 30 Sep 2009 13:54:27 +0000</pubDate>
		<dc:creator>Kevin Heubusch</dc:creator>
				<category><![CDATA[ARRA]]></category>
		<category><![CDATA[Electronic records]]></category>
		<category><![CDATA[Health information exchange]]></category>

		<guid isPermaLink="false">http://journal.ahima.org/?p=996</guid>
		<description><![CDATA[The Department of Health and Human Services announced awards totaling $27.8 million to health center networks and large multi-site health centers to implement health IT.
The funds are part of the $2 billion allotted to HHS’s Health Resources and Services Administration (HRSA) under the American Recovery and Reinvestment Act to expand healthcare services to low-income and uninsured [...]]]></description>
			<content:encoded><![CDATA[<p>The Department of Health and Human Services <a href="http://www.hhs.gov/news/press/2009pres/09/20090929a.html" target="_blank">announced</a> awards totaling $27.8 million to health center networks and large multi-site health centers to implement health IT.</p>
<p>The funds are part of the $2 billion allotted to HHS’s Health Resources and Services Administration (HRSA) under the American Recovery and Reinvestment Act to expand healthcare services to low-income and uninsured individuals.</p>
<p>The $27.8 million will be used to expand and upgrade health IT systems, including electronic health records, and are related to other ARRA efforts to promote the adoption and use of health IT throughout healthcare.</p>
<p>Eighteen grants totaling more than $22.6 million will support EHR implementations. Grants totaling more than $2.6 million will help four grantees implement other health IT-related projects, including creation of health information exchange networks. Another five grants totaling more than $2.5 million will help health centers use existing EHRs to improve patient health outcomes.</p>
<p>HRSA-supported health centers treated 17 million patients in 2008, 40 percent of whom have no health insurance, according to HHS.</p>
<p>A list of grant recipients is available through the above link. More on ARRA provisions for community health centers is available through the <a href="http://www.hhs.gov/recovery/hrsa/healthcentergrants.html" target="_blank">HHS.gov/Recovery site</a>.</p>
]]></content:encoded>
			<wfw:commentRss>http://journal.ahima.org/2009/09/30/27-8-million-for-it-in-community-health-centers/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Funding Deadlines for Health IT Extension Centers</title>
		<link>http://journal.ahima.org/2009/08/24/funding-deadlines-for-health-it-extension-centers/</link>
		<comments>http://journal.ahima.org/2009/08/24/funding-deadlines-for-health-it-extension-centers/#comments</comments>
		<pubDate>Mon, 24 Aug 2009 17:40:15 +0000</pubDate>
		<dc:creator>Kevin Heubusch</dc:creator>
				<category><![CDATA[ARRA]]></category>
		<category><![CDATA[Electronic records]]></category>
		<category><![CDATA[Health information exchange]]></category>
		<category><![CDATA[Workforce]]></category>

		<guid isPermaLink="false">http://journal.ahima.org/?p=928</guid>
		<description><![CDATA[Update, September 2: HHS has posted new and revised program materials online: a transcript of its August 27 technical assistance conference, an FAQ, and a revised preliminary application template.
The first applications from aspiring health IT resource centers are due in two weeks—September 8. The Office of the National Coordinator for Health Information Technology will award grants in [...]]]></description>
			<content:encoded><![CDATA[<p><strong>Update, September 2:</strong> HHS has posted <a href="http://healthit.hhs.gov/extensionprogram" target="_blank">new and revised program materials online</a>: a transcript of its August 27 technical assistance conference, an FAQ, and a revised preliminary application template.</p>
<p>The first applications from aspiring health IT resource centers are due in two weeks—September 8. The Office of the National Coordinator for Health Information Technology will award grants in two additional cycles with initial deadlines in December and June. ONC announced the deadlines in a press event last week.</p>
<p>Program details and the full application schedule appears in the <a href="http://healthit.hhs.gov/portal/server.pt?open=512&amp;objID=1335&amp;parentname=CommunityPage&amp;parentid=47&amp;mode=2&amp;in_hi_userid=11113&amp;cached=true#3" target="_blank">funding opportunity announcement</a> on the Health and Human Services health IT Web site. Applications will be screened in two phases. Successful preliminary applicants will be requested to submit a full application for merit review.</p>
<table border="1" cellspacing="0" cellpadding="0">
<thead>
<tr>
<td valign="top"><strong>Initial Cycle</strong></td>
<td valign="top"><strong>Approx Funding</strong></td>
<td valign="top"><strong>Preliminary Application</strong></td>
<td valign="top"><strong>Preliminary Approval</strong></td>
<td valign="top"><strong>Full Applications</strong></td>
<td valign="top"><strong>Awardee Selection</strong></td>
</tr>
<tr>
<td valign="top">1</td>
<td valign="top">$189,000,000</td>
<td valign="top">September 8, 2009</td>
<td valign="top">September 29, 2009</td>
<td valign="top">November 3, 2009</td>
<td valign="top">December 11, 2009</td>
</tr>
<tr>
<td valign="top">2</td>
<td valign="top">$225,000,000</td>
<td valign="top">December 22, 2009</td>
<td valign="top">January 19, 2010</td>
<td valign="top">March 2, 2010</td>
<td valign="top">April 27, 2010</td>
</tr>
<tr>
<td valign="top">3</td>
<td valign="top">$184,000,000</td>
<td valign="top">June 1, 2010</td>
<td valign="top">June 22, 2010</td>
<td valign="top">August 3, 2010</td>
<td valign="top">September 28, 2010</td>
</tr>
</thead>
<tbody></tbody>
</table>
<p> <span id="more-928"></span></p>
<p>The centers are part of the HITECH Act in the American Recovery and Reinvestment Act (ARRA). ONC released a <a href="http://journal.ahima.org/2009/05/28/onc-drafts-health-it-extension-program/" target="_blank">draft plan</a> for public comment in late May.</p>
<p>The regional centers will furnish education, outreach, and technical assistance to help providers select, successfully implement, and meaningfully use certified EHR technology.  They will also help providers achieve, through appropriate available infrastructures, exchange of health information in compliance with applicable statutory and regulatory requirements, and patient preferences.</p>
<p>ONC expects to establish 70 or more centers supporting 100,000 primary care providers. Each center will serve a defined geographic area.</p>
]]></content:encoded>
			<wfw:commentRss>http://journal.ahima.org/2009/08/24/funding-deadlines-for-health-it-extension-centers/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</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>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>ONC Drafts Health IT Extension Program</title>
		<link>http://journal.ahima.org/2009/05/28/onc-drafts-health-it-extension-program/</link>
		<comments>http://journal.ahima.org/2009/05/28/onc-drafts-health-it-extension-program/#comments</comments>
		<pubDate>Thu, 28 May 2009 13:38:02 +0000</pubDate>
		<dc:creator>Kevin Heubusch</dc:creator>
				<category><![CDATA[ARRA]]></category>
		<category><![CDATA[Electronic records]]></category>
		<category><![CDATA[Health information exchange]]></category>
		<category><![CDATA[Workforce]]></category>

		<guid isPermaLink="false">http://journal.ahima.org/?p=604</guid>
		<description><![CDATA[ONC published a draft description of the health IT extension program in today’s Federal Register, requesting comments within two weeks—by June 11.
The extension program is called for under the HITECH Act in ARRA, the American Recovery and Reinvestment Act. It authorizes creation of a National Health Information Technology Research Center and affiliated regional extension centers [...]]]></description>
			<content:encoded><![CDATA[<p>ONC published a draft description of the health IT extension program in today’s <a href="http://edocket.access.gpo.gov/2009/pdf/E9-12419.pdf" target="_blank"><em>Federal Register</em></a>, requesting comments within two weeks—by June 11.</p>
<p>The extension program is called for under the HITECH Act in ARRA, the American Recovery and Reinvestment Act. It authorizes creation of a National Health Information Technology Research Center and affiliated regional extension centers to assist providers in selecting and implementing certified electronic health records.</p>
<p>The program also will assist providers in becoming “meaningful users” of the systems, a prerequisite to receiving bonus Medicare and Medicaid payments under a separate ARRA provision.</p>
<p>The extension program is to give preference to providers serving uninsured, underinsured, underserved, and special-needs populations.<span id="more-604"></span></p>
<p>The HITECH Act also calls for the regional centers to participate “to the extent practicable” in health information exchanges and to integrate health IT into the initial and ongoing training of health professionals and others in the industry. They will be encouraged to seek broad industry, academic, and state government participation and use federal expertise where appropriate.</p>
<p>ONC proposes that the regional extension centers will form a consortium coordinated and facilitated by the research center. The research center’s primary function will be to produce best practices, and the regional centers will be responsible for disseminating them.</p>
<p>The draft proposes that the regional centers’ key service will be on-site assistance, with an established minimum level of service that would include unbiased information on appropriate exchange of health information and information on integrating health IT into practice workflow.</p>
<p>HITECH specifies that the regional centers will be organizations “affiliated with any United States-based nonprofit organization, or group thereof.” ONC’s proposal includes draft required criteria as well as its own preferred criteria, which include “multi-stakeholder collaborations that leverage local resources,” as well as applicants that identify viable matching funds.</p>
<p>ONC is proposing two-year awards based on the size of the population served. It expects awards to range $1-2 million per year, with a maximum of $10 million.</p>
<p>ONC anticipates that applicants will require 2 months or more to prepare their proposals. It expects to make awards as early as the first quarter of 2010 and continue through that year. The timing is intended to enable the centers to help providers be eligible for the bonus payments in 2011 (hospitals) and 2012 (physicians), when the incentives are greatest.</p>
]]></content:encoded>
			<wfw:commentRss>http://journal.ahima.org/2009/05/28/onc-drafts-health-it-extension-program/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>HITECH Act Privacy Provisions’ Impact for Health Information Exchanges</title>
		<link>http://journal.ahima.org/2009/04/16/hitech-act-privacy-provisions%e2%80%99-impact-for-health-information-exchanges/</link>
		<comments>http://journal.ahima.org/2009/04/16/hitech-act-privacy-provisions%e2%80%99-impact-for-health-information-exchanges/#comments</comments>
		<pubDate>Thu, 16 Apr 2009 11:00:57 +0000</pubDate>
		<dc:creator>Anne Zender</dc:creator>
				<category><![CDATA[ARRA]]></category>
		<category><![CDATA[Health information exchange]]></category>
		<category><![CDATA[Privacy and security]]></category>
		<category><![CDATA[privacy & security]]></category>

		<guid isPermaLink="false">http://journal.ahima.org/?p=402</guid>
		<description><![CDATA[Continuing this week’s focus on privacy, today’s guest author Stacie Durkin, RN-C, RHIA, MBA, owner, Durkin &#38; Associates, explains what ARRA’s privacy provisions might mean for health information exchange. Durkin co-chairs an AHIMA/HIMSS collaborative workgroup focused on privacy and security in the HIE/RHIO environment. 
HIPAA has sharper teeth and a wider net due to the American [...]]]></description>
			<content:encoded><![CDATA[<p><em>Continuing this week’s focus on privacy, today’s guest author </em><a href="mailto:sdurkn@durkinassoc.com"><em>Stacie Durkin</em></a><em>, RN-C, RHIA, MBA, owner, Durkin &amp; Associates, explains what ARRA’s privacy provisions might mean for health information exchange. Durkin co-chairs an AHIMA/HIMSS collaborative workgroup focused on privacy and security in the HIE/RHIO environment. </em></p>
<p>HIPAA has sharper teeth and a wider net due to the <a href="http://frwebgate.access.gpo.gov/cgi-bin/getdoc.cgi?dbname=111_cong_bills&amp;docid=f:h1enr.txt.pdf" target="_blank">American Recovery and Reinvestment Act </a>of 2009 (ARRA).  A section of ARRA called The Health Information Technology for Economic and Clinical Health Act (HITECH Act) is the healthcare portion of the stimulus package that provides $19 billion for health information technology and the Federal financial commitment which supports and promotes the adoption of electronic health records (EHRs) by 2014.  Some of the perceived weaknesses in HIPAA&#8217;s privacy and security regulations will be rectified by ARRA, dubbed “HIPAA II.”</p>
<p>There has been much discussion around the privacy and security issues of shared data.   Before the stimulus package, health information exchanges (HIE) were not directly regulated under the Health Insurance Portability and Accountability Act of 1996 (HIPAA). The new legislation is loaded with requirements, new enforcement provisions and penalties for covered entities, business associates, vendors and others.<span id="more-402"></span></p>
<p>The legislation expands HIPAA’s net to include employees of covered entities and to individual or corporate persons that perform any function or activity involving the use or disclosure of protected health information  (PHI)  on behalf of a covered entity such as “business associates.” HIPAA defines covered entities as “health care providers that conduct certain electronic transactions, health care clearinghouses, and health plans.”</p>
<p>Business associates will be required to implement the same security safeguards and restrictions on uses and disclosures, to protect individually identifiable health information. It also subjects business associates to the same potential civil and criminal liability for breaches as covered entities. All business associate agreements will have to be amended to reflect these changes.  To ensure compliance the Secretary of HHS is required to conduct periodic compliance audits of business associates as well as covered entities.</p>
<p>The HITECH Act is meant to increase the momentum of the development and implementation of the EHR by 2014.  HHS is allocated $2 billion for the Office of the National Coordinator for Health Information Technology.  ARRA has also expanded the duties and authority of this office.  The national coordinator is responsible for:</p>
<ul>
<li>the coordinating development and implementation of HIT standards,</li>
<li>strategic planning, including the electronic exchange of health information,</li>
<li>certification of HIT as meeting standards,</li>
<li>assessment of disparities in the use of HIT,<br />
evaluate benefits and costs of the use of EHR, and</li>
<li>development and updating of EHR technology.</li>
</ul>
<p>Timelines for the privacy provisions, regulations, and guidance under HITECH Act are listed in the <a href="http://journal.ahima.org/wp-content/uploads/provisions.pdf" target="_blank">linked table</a>.</p>
<p>The act represents commitment by the federal government to bolster the healthcare industry, particularly in the adoption of EHRs.  At the same time, the lawmakers have put teeth into the enforcement of laws and regulations governing the privacy and security of personal health information.  </p>
<p>The act does not change state law preemption, and covered entities and business associates will continue to have to comply with federal privacy and security standards as well as more restrictive state law requirements.</p>
<h5>References</h5>
<p>&#8220;American Recovery and Reinvestment Act of 2009 &#8212; An Analysis.&#8221; LexisNexis Emerging Issues Analysis, 2009.</p>
<p>H.R. 1, <a href="http://frwebgate.access.gpo.gov/cgi-bin/getdoc.cgi?dbname=111_cong_bills&amp;docid=f:h1enr.pdf" target="_blank">American Recovery and Reinvestment Act of 2009.</a></p>
<p>Mills, Tom, and Marion Kristal Goldberg. “<a href="http://www.linexlegal.com/transit.php?content_id=84029&amp;id8" target="_blank">The Stimulus Bill’s Effect on the Health Care Industry</a>.” Winston &amp; Strawn, LLP Healthcare Practice Briefing, 2009.</p>
<p>Steinbrook, Robert. &#8220;<a href="http://content.nejm.org/cgi/content/full/360/11/1057" target="_blank">Health Care and the American Recovery and Reinvestment Act</a>.&#8221; <em>New England Journal of Medicine</em>, March 12, 2009.</p>
]]></content:encoded>
			<wfw:commentRss>http://journal.ahima.org/2009/04/16/hitech-act-privacy-provisions%e2%80%99-impact-for-health-information-exchanges/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>HISPC Privacy Project Receives Extension</title>
		<link>http://journal.ahima.org/2009/04/01/hispc-privacy-receives-extension/</link>
		<comments>http://journal.ahima.org/2009/04/01/hispc-privacy-receives-extension/#comments</comments>
		<pubDate>Wed, 01 Apr 2009 20:07:42 +0000</pubDate>
		<dc:creator>Chris Dimick</dc:creator>
				<category><![CDATA[Health information exchange]]></category>
		<category><![CDATA[Privacy and security]]></category>

		<guid isPermaLink="false">http://journal.ahima.org/?p=331</guid>
		<description><![CDATA[The Health Information Security and Privacy Collaboration (HISPC) will continue its work to foster nationwide health information exchange through a recently announced extension. The Office of the National Coordinator for Health IT (ONC) set the extension to begin April 1 after determining funds remained from the most recent phase of the project, which was scheduled [...]]]></description>
			<content:encoded><![CDATA[<p>The <a href="http://privacysecurity.rti.org/" target="_blank">Health Information Security and Privacy Collaboration</a> (HISPC) will continue its work to foster nationwide health information exchange through a recently announced extension. The <a href="http://www.hhs.gov/healthit/onc/mission/" target="_blank">Office of the National Coordinator for Health IT</a> (ONC) set the extension to begin April 1 after determining funds remained from the most recent phase of the project, which was scheduled to end last month.</p>
<p>Under HISPC, 42 US states and territories have worked to identify and solve privacy and security barriers to health information exchange (HIE). Formed in 2006, HISPC organized into seven multistate collaboratives in its most recent phase, each focused on a specific issue such as interstate disclosure and patient consent requirements or consumer education.<span id="more-331"></span></p>
<p>Currently in its third and final phase, HISPC was originally scheduled to wrap up its work at a March national conference in which the seven collaboratives demonstrated their deliverables. But the no-cost extension that begins today will allow the groups more time to complete, test, and implement their work, according to Linda Dimitropoulos, PhD, the director of the health services program at RTI International and project manager for HISPC. RTI, based in Chicago, was contracted by ONC to run HISPC.</p>
<p>The extension was welcomed by HISPC participants as a way to keep their momentum going. The work of discovery and consensus-building takes time, Dimitropoulos said, and the groups “have been pressed; the schedules have been so aggressive that this gave them a little breathing room to actually finalize their work in a way that they can be really happy and proud of.”</p>
<p>The HISPC phase 3 Challenge and Innovation Stage will last until July 31. During the extension, all seven collaboratives will use the tools developed by the Consumer Education and Engagement and Provider Education Collaboratives to conduct outreach and education on HIE health information exchange issues with consumers and providers in HISPC states.</p>
<h5>A Window to Keep the Work Going</h5>
<p>In phase 3, the Inter-Organizational Agreements Collaborative developed a standardized legal agreement that promotes the interstate exchange of public health data such as immunization records. The group will use the extension to lobby additional states to adopt the form and begin exchanging limited data.</p>
<p>Public health data exchange is already taking place between several state health departments through the collaborative’s work. The group will also continue to increase the number of private organizations exchanging health data with other private entities, another of its initiatives.</p>
<p>The Provider Education Collaborative initially focused its HIE education outreach to primary care physicians. During the extension, the collaborative will adapt its materials for specialty physicians and reach out to those groups, Dimitropoulos said.</p>
<p>As of now, HISPC will end following the completion of the phase 3 extension. An additional year of work was built into the original contract, but ONC has opted not to renew the project, Dimitropoulos said. Given the leadership change occurring at both Health and Human Services and ONC, including the recent appointment of new ONC head David Blumenthal, healthcare experts have said ONC officials are waiting to finalize any initiatives until the new administration’s priorities and goals are established.</p>
<p>RTI plans to release its HISPC wrap-up report this summer in the form of an “action and implementation” manual, which will detail the findings, tools, and deliverables. RTI will add an addendum describing the work done during the extension.</p>
<p>A feature in the upcoming May issue of the Journal offers a look at the ambitious three-year HISPC project and details select work from its most recent phase.</p>
]]></content:encoded>
			<wfw:commentRss>http://journal.ahima.org/2009/04/01/hispc-privacy-receives-extension/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>First Health Record Bank Pilot Launches</title>
		<link>http://journal.ahima.org/2009/03/30/first-health-record-bank-pilot-launches/</link>
		<comments>http://journal.ahima.org/2009/03/30/first-health-record-bank-pilot-launches/#comments</comments>
		<pubDate>Mon, 30 Mar 2009 16:55:41 +0000</pubDate>
		<dc:creator>Chris Dimick</dc:creator>
				<category><![CDATA[Health information exchange]]></category>
		<category><![CDATA[Personal health records]]></category>
		<category><![CDATA[health record bank]]></category>
		<category><![CDATA[health record banking]]></category>

		<guid isPermaLink="false">http://journal.ahima.org/?p=272</guid>
		<description><![CDATA[Washington State’s experiment in consumer-controlled health records has moved into a pilot phase, transforming the health record banking model from theory to testing. Earlier this month the Washington State Health Care Authority (HCA) announced the launch of three pilot sites that will try out the feasibility of a permanent statewide health record bank network.
Health record [...]]]></description>
			<content:encoded><![CDATA[<p>Washington State’s experiment in consumer-controlled health records has moved into a pilot phase, transforming the health record banking model from theory to testing. Earlier this month the <a href="http://www.hca.wa.gov/hit" target="_blank">Washington State Health Care Authority</a> (HCA) announced the launch of three pilot sites that will try out the feasibility of a permanent statewide health record bank network.</p>
<p>Health record banks centrally store copies of consumer’s health records, which providers “deposit” into the accounts. Consumers control which providers can contribute information and which providers and individuals can view their records.</p>
<p>This model of health information exchange, where many providers send patient information to one central location, is seen as an alternative to the many-to-many exchange model, where several organizations directly exchange copies of patient’s records. If the pilot project is successful, Washington State hopes to show by example that health record banks are the ideal model for nationwide information exchange, says Juan Alaniz, health record bank pilot project manager for HCA.<span id="more-272"></span></p>
<p>Advocates for the health record banks agree that the pilot is an important demonstration of the model. William Yasnoff, MD, PhD, is managing partner of National Health Information Infrastructure Advisors and CEO of the Health Record Banking Alliance. “As the first operational health record bank, the Washington State pilots represent an important step in demonstrating how this approach addresses the key challenges of making comprehensive electronic medical records available at any point of care,” he says.</p>
<p>A main goal of the pilot is to show that health information can get into the hands of patients and providers, Alaniz says, which will reduce redundant medical procedures and costs and improve the quality and safety of care provided. “By having this information available, I think that we are arming consumers with valuable information they can use in a timely basis,” he says.</p>
<h5>Three Pilot Sites</h5>
<p>The Washington State pilot is the first large-scale testing of the health record bank model. The test contains three projects across the state, which will target 18,000 participants who have specialized healthcare needs such as chronic-illness patients, families with children, and caregivers.</p>
<p>The banks are managed by local community healthcare facilities, which identified and recruited patients to take part in the pilot, Alaniz says. The state contributed $1.7 million to the pilot, with participant healthcare communities also pitching in funds.</p>
<p>The three pilot sites are in the following locales:</p>
<ul>
<li>Bellingham, with St. Joseph Hospital Foundation and the Critical Junctures Institute</li>
<li>Cashmere, with Community Choice Healthcare Network</li>
<li>Spokane, with Inland Northwest Health Services.</li>
</ul>
<h5>“High Value” Data</h5>
<p>Participating providers will begin by loading five types of “high value” data into consumers’ health record banks: medication history, immunization records, allergy information, family history, and a health status synopsis. </p>
<p>The pilot will end in July, when a preliminary results analysis will be conducted, Alaniz says. The project will test the financial sustainability of the banks, their ability to provide public health data, and how the banks should be organized and governed.</p>
<p>But most importantly, the pilot is meant to see if consumers and providers find health record banks valuable and would sign up for a fully-integrated, statewide health record banking system. “If it is of no value to consumers or providers, then we certainly don’t want to do this,” Alaniz says.</p>
<p>At the end of the pilot, the health record banks will continue to operate if funding can be secured. The goal is to have the banks financially self-sustainable by 2011. </p>
<h5>Private Infrastructure</h5>
<p>The pilot banks run PHR programs from Microsoft Health Vault and Google Health. Each site chose between the two programs, which Alaniz describes as PHRs “on steroids.” When data are uploaded into the bank, the information is automatically organized in specialized ways useful to patients and providers.</p>
<p>Having private companies provide the infrastructure saved HCA the cost of developing its own software. In addition, the banks benefit from the companies’ work to make the interfaces consumer friendly, says Alaniz. If the health record bank project was to advance, Alaniz says banks would have their choice between using existing products and developing platforms from scratch.</p>
<p>Prior to the pilot, it was unclear who would build or provide the technical infrastructure for health record banks. The choice of Google and Microsoft isn’t surprising, says Yasnoff—the majority of health information infrastructures are built and operated from systems developed by private firms. Each of the health record bank pilots is governed by the local community, which he says will provide a watchful eye on how the records are managed.</p>
<h5>Public Results</h5>
<p>Washington State officials plan to share the information they obtain from the pilots with interested parties. HCA has already talked with Oregon and New York state officials about sharing pilot data. Other communities including Louisville, KY, Ocala, FL, and Kansas City, MO, are also interested in pursuing health record banks, Yasnoff says.</p>
<p>The pilots are only the “test and learn” phase of building a state-wide health record bank system, which officials hope to launch in 2012, Alaniz says. If the results of the pilot support moving forward, the project will begin implementing lessons learned and develop the basic bank infrastructure.</p>
]]></content:encoded>
			<wfw:commentRss>http://journal.ahima.org/2009/03/30/first-health-record-bank-pilot-launches/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Google Health Announces Profile Sharing</title>
		<link>http://journal.ahima.org/2009/03/05/google-health-announces-profile-sharing/</link>
		<comments>http://journal.ahima.org/2009/03/05/google-health-announces-profile-sharing/#comments</comments>
		<pubDate>Thu, 05 Mar 2009 22:40:44 +0000</pubDate>
		<dc:creator>Kevin Heubusch</dc:creator>
				<category><![CDATA[Electronic records]]></category>
		<category><![CDATA[Health information exchange]]></category>
		<category><![CDATA[Personal health records]]></category>

		<guid isPermaLink="false">http://journal.ahima.org/?p=235</guid>
		<description><![CDATA[Google Health, the Internet giant’s free online personal health record service, is nearing a year old. This week the company rolled out some changes to the service, some of which the company anticipated last spring.
Users may now share their health profiles with others, such as doctors and family. Account owners grant access to others via e-mail [...]]]></description>
			<content:encoded><![CDATA[<p><a href="http://www.google.com/health" target="_blank">Google Health</a>, the Internet giant’s free online personal health record service, is nearing a year old. This week the company rolled out some changes to the service, some of which the company <a href="http://journal.ahima.org/2008/06/02/google-health-launch-just-%e2%80%9cthe-beginning%e2%80%9d/" target="_blank">anticipated last spring</a>.</p>
<p>Users may now share their health profiles with others, such as doctors and family. Account owners grant access to others <a href="http://www.google.com/support/health/bin/answer.py?answer=138423" target="_blank">via e-mail addresses</a>. Viewers cannot edit or share a profile. Account owners control how much of the profile others see, another change.</p>
<p>Google’s list of partners continues to grow. Partners are primarily national pharmacy chains that can feed medication information into Google Health accounts. However, patients of the Cleveland Clinic and Beth Israel Deaconess Medical Center can import their records through those facilities’ patient portals.</p>
]]></content:encoded>
			<wfw:commentRss>http://journal.ahima.org/2009/03/05/google-health-announces-profile-sharing/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Redisclosure Resources</title>
		<link>http://journal.ahima.org/2009/02/02/redisclosure-resources/</link>
		<comments>http://journal.ahima.org/2009/02/02/redisclosure-resources/#comments</comments>
		<pubDate>Mon, 02 Feb 2009 17:30:06 +0000</pubDate>
		<dc:creator>Kevin Heubusch</dc:creator>
				<category><![CDATA[Compliance]]></category>
		<category><![CDATA[HIM operations]]></category>
		<category><![CDATA[Health information exchange]]></category>
		<category><![CDATA[Privacy and security]]></category>

		<guid isPermaLink="false">http://journal.ahima.org/?p=141</guid>
		<description><![CDATA[&#8220;Redisclosure of Patient Health Information (Updated),&#8221; the practice brief in this month&#8217;s print issue, offers guidance on one of HIM&#8217;s trickier issues. Redisclosure is the sharing or release of patient health information that the organization received from another source (such as a facility or provider) and subsequently made part of the patient’s health record or [...]]]></description>
			<content:encoded><![CDATA[<p><a href="http://library.ahima.org/xpedio/groups/public/documents/ahima/bok1_042636.hcsp?dDocName=bok1_042636" target="_blank">&#8220;Redisclosure of Patient Health Information (Updated),&#8221;</a> the practice brief in this month&#8217;s print issue, offers guidance on one of HIM&#8217;s trickier issues. Redisclosure is the sharing or release of patient health information that the organization received from another source (such as a facility or provider) and subsequently made part of the patient’s health record or the organization’s designated record set. A glance at the sample situations in the brief shows just how complicated this issue can become.</p>
<p>AHIMA&#8217;s library contains additional related guidance on redisclosure. Look for these practice briefs:</p>
<ul>
<li><a href="http://library.ahima.org/xpedio/groups/public/documents/ahima/bok1_037468.hcsp?dDocName=bok1_037468" target="_blank">“Defining and Disclosing the Designated Record Set and the Legal Health Record”</a></li>
<li><a href="http://library.ahima.org/xpedio/groups/public/documents/ahima/bok1_016467.hcsp?dDocName=bok1_016467" target="_blank">“Notice of Privacy Practices”</a></li>
<li><a href="http://library.ahima.org/xpedio/groups/public/documents/ahima/bok1_000027.hcsp?dDocName=bok1_000027" target="_blank">“Patient Access and Amendment to Health Records (Updated)”</a></li>
<li><a href="http://library.ahima.org/xpedio/groups/public/documents/ahima/bok1_018177.hcsp?dDocName=bok1_018177" target="_blank">“Understanding the Minimum Necessary Standard (Updated)”</a></li>
</ul>
]]></content:encoded>
			<wfw:commentRss>http://journal.ahima.org/2009/02/02/redisclosure-resources/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>A Cost-Benefit Model for PHRs</title>
		<link>http://journal.ahima.org/2008/11/17/a-cost-benefit-model-for-phrs/</link>
		<comments>http://journal.ahima.org/2008/11/17/a-cost-benefit-model-for-phrs/#comments</comments>
		<pubDate>Mon, 17 Nov 2008 20:09:05 +0000</pubDate>
		<dc:creator>Chris Dimick</dc:creator>
				<category><![CDATA[Electronic records]]></category>
		<category><![CDATA[Health information exchange]]></category>
		<category><![CDATA[Personal health records]]></category>

		<guid isPermaLink="false">http://journal.ahima.org/?p=117</guid>
		<description><![CDATA[Healthcare is badly in need of some cost-savings. A new study suggests that a change in the way we keep health records could save billions. Last week the industry got a look at a cost-benefit model for personal health records. According to the report, widespread use of PHRs could save the US healthcare industry between $13 [...]]]></description>
			<content:encoded><![CDATA[<p>Healthcare is badly in need of some cost-savings. A new study suggests that a change in the way we keep health records could save billions. Last week the industry got a look at a cost-benefit model for personal health records. According to the report, widespread use of PHRs could save the US healthcare industry between $13 and $21 billion a year.</p>
<p>The <a href="http://www.citl.org" target="_blank">Center for Information Technology Leadership</a> (CITL), a nonprofit IT research center based at Partners HealthCare System in Boston, offers the projections in the study <a href="http://www.citl.org/research/PHR.asp" target="_blank">“The Value of Personal Health Records.”</a> The study describes an evidence-based model that estimates the industry costs and benefits of four different PHR architectures. The study is the first of its kind to examine the different PHR architectures and show their direct cost savings to healthcare providers and payers, CITL officials say.<span id="more-117"></span></p>
<p>PHRs provide patients with greater access to their health information and, depending on the individual product, give them an opportunity to add their own information. Many PHRs put patients in control of who can access their records, allowing them to share their information with providers, payers, and caregivers.</p>
<p>A PHR is different from a provider or payer’s record, which the organization controls for business and legal purposes. PHRs have the potential to improve care by sharing patient information among authorized providers. They can also increase a consumer’s awareness of his or her health and help in making informed health decisions.</p>
<h4>Savings Vary by Type</h4>
<p>Blackford Middleton, MD, MPH, MSs, is chairman of CITL and director of clinical informatics research and development for Partners Healthcare. He says that CITL believes electronic health record systems—implemented and maintained by providers—are a part of improving care and lowering cost; however, “we believe that the PHR is perhaps an equally important or maybe even more important part of the solution as well.”</p>
<p>Published November 12 and presented at the <a href="http://www.amia.org" target="_blank">American Medical Informatics Association</a> annual symposium, the CITL cost-benefit model assumes 80 percent of the US population actively uses one of four emerging PHR architectures: payer-tethered PHRs, provider-tethered PHRs, third-party PHRs, and interoperable PHRs. A panel of healthcare experts organized by CITL synthesized hundreds of articles on healthcare and PHRs to build the model.</p>
<p>Provider-tethered PHRs are tied to a healthcare organization’s internal record system. Payer-tethered systems are tied to a given payer’s system. Consumers use third-party PHRs to aggregate data from different, unconnected sources.</p>
<p>Interoperable PHRs represent a &#8220;future type&#8221; of record “populated with data from all regional data sources via standards-based automated data exchange. The connections with these sources would create a record that is more complete than any individual repository (e.g., [electronic health records], other PHRs, payer claims databases),” according to the report.</p>
<p>While the implementation and steady use of each of the four PHR architectures would result in vast cost savings, some architectures produce greater savings than others, according to the study.</p>
<p>The model projects that mass use of the interoperable PHR architecture could lead to the highest savings by streamlining healthcare operations and decreasing administrative and clinical costs, such as preventing duplicate medical tests and reducing adverse drug interactions.</p>
<p>The projected annual savings by model are:</p>
<ul>
<li>Interoperable PHRs: $21 billion</li>
<li>Third-party PHR: $16 billion</li>
<li>Provider-tethered PHR: up to $14 billion </li>
<li>Payer-tethered PHR: $13 billion</li>
</ul>
<h4>Highlighting the Value of Data Sharing</h4>
<p>The  model assumes that PHRs in each category have certain functionality, including the ability to share test results and medication information. Other, more specialized functions include electronic appointment scheduling and e-visits. Middleton hopes the study will help policy makers and the general healthcare industry understand which PHR models can best improve healthcare and reduce costs.</p>
<p>“The PHR architecture and what data is accessible—and to what degree data is interoperable—that really defines the value of a PHR,” Middleton says. “Our intent is to model a what-if scenario; [for example,] what if everyone had a provider-tethered PHR or an interoperable PHR. And the goal is then to highlight the differences so that we can inform policy makers and the industry about what is valuable.”</p>
<p>Though interoperable PHRs presents the highest potential savings in cost, they are still a work in progress. But CITL’s cost-benefit model indicates that PHR development should lean toward an interoperable architecture, Middleton says. Interoperable PHRs act as a hub for patient information, connecting multiple payers and providers to each other through a patient-controlled record.</p>
<p>While PHR use does offer savings, establishing the products and the networks takes money. The cost-benefit model also adjusts to reflect the savings after deducting the cost of implementing each PHR architecture. Providing interoperable PHRs for 80 percent of the US population could cost an estimated $3.7 billion to acquire and $1.9 billion annually to maintain, the study estimates. After cost, and based on a 10-year roll-out of infrastructure, the interoperable PHR could still save $19 billion annually in healthcare costs.</p>
<p>CITL hopes several things come as the result of this model, Middleton says. Third-party PHR companies like Google Health and Microsoft HealthVault can use the study to recognize the value of standards that will make their products more interoperable. Providers and payers can recognize the value of PHRs and pledge their support for PHR adoption. Finally, policymakers can recognize the value of PHRs and address issues that will allow nationwide health IT adoption, Middleton says.</p>
]]></content:encoded>
			<wfw:commentRss>http://journal.ahima.org/2008/11/17/a-cost-benefit-model-for-phrs/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
	</channel>
</rss>
