<?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>APP Design Blog &#187; Business</title>
	<atom:link href="http://www.appdesign.com/blog/category/business/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.appdesign.com/blog</link>
	<description>Thoughts, rants, and code snippets from the folks at APP Design, Inc.</description>
	<lastBuildDate>Wed, 24 Apr 2013 20:20:29 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
		<item>
		<title>Patient Consent in HIEs: Consumers are Key</title>
		<link>http://www.appdesign.com/blog/2011/10/10/patient-consent-in-hies-consumers-are-key/</link>
		<comments>http://www.appdesign.com/blog/2011/10/10/patient-consent-in-hies-consumers-are-key/#comments</comments>
		<pubDate>Mon, 10 Oct 2011 14:16:16 +0000</pubDate>
		<dc:creator>Sarah K</dc:creator>
				<category><![CDATA[Business]]></category>
		<category><![CDATA[Misc]]></category>

		<guid isPermaLink="false">http://www.appdesign.com/blog/2011/10/10/patient-consent-in-hies-consumers-are-key/</guid>
		<description><![CDATA[In past blogs, we&#8217;ve discussed how health information exchanges (HIE) play a crucial role in transforming the healthcare industry by enabling the systematic sharing of health-related information between disparate clinical systems and various organizations, or stakeholders. HIEs have demonstrated their ability to improve the clinical and financial performance of healthcare organizations and, if properly designed, [...]]]></description>
			<content:encoded><![CDATA[<p><!--[if gte mso 9]><xml>  <w:WordDocument>   <w:View>Normal</w:View>   <w:Zoom>0</w:Zoom>   <w:TrackMoves/>   <w:TrackFormatting/>   <w:PunctuationKerning/>   <w:ValidateAgainstSchemas/>   <w:SaveIfXMLInvalid>false</w:SaveIfXMLInvalid>   <w:IgnoreMixedContent>false</w:IgnoreMixedContent>   <w:AlwaysShowPlaceholderText>false</w:AlwaysShowPlaceholderText>   <w:DoNotPromoteQF/>   <w:LidThemeOther>EN-US</w:LidThemeOther>   <w:LidThemeAsian>X-NONE</w:LidThemeAsian>   <w:LidThemeComplexScript>X-NONE</w:LidThemeComplexScript>   <w:Compatibility>    <w:BreakWrappedTables/>    <w:SnapToGridInCell/>    <w:WrapTextWithPunct/>    <w:UseAsianBreakRules/>    <w:DontGrowAutofit/>    <w:SplitPgBreakAndParaMark/>    <w:DontVertAlignCellWithSp/>    <w:DontBreakConstrainedForcedTables/>    <w:DontVertAlignInTxbx/>    <w:Word11KerningPairs/>    <w:CachedColBalance/>   </w:Compatibility>   <w:BrowserLevel>MicrosoftInternetExplorer4</w:BrowserLevel>   <m:mathPr>    <m:mathFont m:val="Cambria Math"/>    <m:brkBin m:val="before"/>    <m:brkBinSub m:val="--"/>    <m:smallFrac m:val="off"/>    <m:dispDef/>    <m:lMargin m:val="0"/>    <m:rMargin m:val="0"/>    <m:defJc m:val="centerGroup"/>    <m:wrapIndent m:val="1440"/>    <m:intLim m:val="subSup"/>    <m:naryLim m:val="undOvr"/>   </m:mathPr></w:WordDocument> </xml><![endif]--><!--[if gte mso 9]><xml>  <w:LatentStyles DefLockedState="false" DefUnhideWhenUsed="true"   DefSemiHidden="true" DefQFormat="false" DefPriority="99"   LatentStyleCount="267">   <w:LsdException Locked="false" Priority="0" SemiHidden="false"    UnhideWhenUsed="false" QFormat="true" Name="Normal"/>   <w:LsdException Locked="false" SemiHidden="false" UnhideWhenUsed="false"    QFormat="true" Name="heading 1"/>   <w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 2"/>   <w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 3"/>   <w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 4"/>   <w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 5"/>   <w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 6"/>   <w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 7"/>   <w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 8"/>   <w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 9"/>   <w:LsdException Locked="false" Priority="39" Name="toc 1"/>   <w:LsdException Locked="false" Priority="39" Name="toc 2"/>   <w:LsdException Locked="false" Priority="39" Name="toc 3"/>   <w:LsdException Locked="false" Priority="39" Name="toc 4"/>   <w:LsdException Locked="false" Priority="39" Name="toc 5"/>   <w:LsdException Locked="false" Priority="39" Name="toc 6"/>   <w:LsdException Locked="false" Priority="39" Name="toc 7"/>   <w:LsdException Locked="false" Priority="39" Name="toc 8"/>   <w:LsdException Locked="false" Priority="39" Name="toc 9"/>   <w:LsdException Locked="false" Priority="35" QFormat="true" Name="caption"/>   <w:LsdException Locked="false" Priority="10" SemiHidden="false"    UnhideWhenUsed="false" QFormat="true" Name="Title"/>   <w:LsdException Locked="false" Priority="1" Name="Default Paragraph Font"/>   <w:LsdException Locked="false" Priority="11" SemiHidden="false"    UnhideWhenUsed="false" QFormat="true" Name="Subtitle"/>   <w:LsdException Locked="false" Priority="22" SemiHidden="false"    UnhideWhenUsed="false" QFormat="true" Name="Strong"/>   <w:LsdException Locked="false" Priority="20" SemiHidden="false"    UnhideWhenUsed="false" QFormat="true" Name="Emphasis"/>   <w:LsdException Locked="false" Priority="0" Name="Normal (Web)"/>   <w:LsdException Locked="false" Priority="59" SemiHidden="false"    UnhideWhenUsed="false" Name="Table Grid"/>   <w:LsdException Locked="false" UnhideWhenUsed="false" Name="Placeholder Text"/>   <w:LsdException Locked="false" Priority="1" SemiHidden="false"    UnhideWhenUsed="false" QFormat="true" Name="No Spacing"/>   <w:LsdException Locked="false" Priority="60" SemiHidden="false"    UnhideWhenUsed="false" Name="Light Shading"/>   <w:LsdException Locked="false" Priority="61" SemiHidden="false"    UnhideWhenUsed="false" Name="Light List"/>   <w:LsdException Locked="false" Priority="62" SemiHidden="false"    UnhideWhenUsed="false" Name="Light Grid"/>   <w:LsdException Locked="false" Priority="63" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Shading 1"/>   <w:LsdException Locked="false" Priority="64" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Shading 2"/>   <w:LsdException Locked="false" Priority="65" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium List 1"/>   <w:LsdException Locked="false" Priority="66" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium List 2"/>   <w:LsdException Locked="false" Priority="67" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 1"/>   <w:LsdException Locked="false" Priority="68" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 2"/>   <w:LsdException Locked="false" Priority="69" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 3"/>   <w:LsdException Locked="false" Priority="70" SemiHidden="false"    UnhideWhenUsed="false" Name="Dark List"/>   <w:LsdException Locked="false" Priority="71" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful Shading"/>   <w:LsdException Locked="false" Priority="72" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful List"/>   <w:LsdException Locked="false" Priority="73" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful Grid"/>   <w:LsdException Locked="false" Priority="60" SemiHidden="false"    UnhideWhenUsed="false" Name="Light Shading Accent 1"/>   <w:LsdException Locked="false" Priority="61" SemiHidden="false"    UnhideWhenUsed="false" Name="Light List Accent 1"/>   <w:LsdException Locked="false" Priority="62" SemiHidden="false"    UnhideWhenUsed="false" Name="Light Grid Accent 1"/>   <w:LsdException Locked="false" Priority="63" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Shading 1 Accent 1"/>   <w:LsdException Locked="false" Priority="64" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Shading 2 Accent 1"/>   <w:LsdException Locked="false" Priority="65" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium List 1 Accent 1"/>   <w:LsdException Locked="false" UnhideWhenUsed="false" Name="Revision"/>   <w:LsdException Locked="false" Priority="34" SemiHidden="false"    UnhideWhenUsed="false" QFormat="true" Name="List Paragraph"/>   <w:LsdException Locked="false" Priority="29" SemiHidden="false"    UnhideWhenUsed="false" QFormat="true" Name="Quote"/>   <w:LsdException Locked="false" Priority="30" SemiHidden="false"    UnhideWhenUsed="false" QFormat="true" Name="Intense Quote"/>   <w:LsdException Locked="false" Priority="66" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium List 2 Accent 1"/>   <w:LsdException Locked="false" Priority="67" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 1 Accent 1"/>   <w:LsdException Locked="false" Priority="68" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 2 Accent 1"/>   <w:LsdException Locked="false" Priority="69" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 3 Accent 1"/>   <w:LsdException Locked="false" Priority="70" SemiHidden="false"    UnhideWhenUsed="false" Name="Dark List Accent 1"/>   <w:LsdException Locked="false" Priority="71" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful Shading Accent 1"/>   <w:LsdException Locked="false" Priority="72" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful List Accent 1"/>   <w:LsdException Locked="false" Priority="73" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful Grid Accent 1"/>   <w:LsdException Locked="false" Priority="60" SemiHidden="false"    UnhideWhenUsed="false" Name="Light Shading Accent 2"/>   <w:LsdException Locked="false" Priority="61" SemiHidden="false"    UnhideWhenUsed="false" Name="Light List Accent 2"/>   <w:LsdException Locked="false" Priority="62" SemiHidden="false"    UnhideWhenUsed="false" Name="Light Grid Accent 2"/>   <w:LsdException Locked="false" Priority="63" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Shading 1 Accent 2"/>   <w:LsdException Locked="false" Priority="64" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Shading 2 Accent 2"/>   <w:LsdException Locked="false" Priority="65" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium List 1 Accent 2"/>   <w:LsdException Locked="false" Priority="66" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium List 2 Accent 2"/>   <w:LsdException Locked="false" Priority="67" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 1 Accent 2"/>   <w:LsdException Locked="false" Priority="68" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 2 Accent 2"/>   <w:LsdException Locked="false" Priority="69" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 3 Accent 2"/>   <w:LsdException Locked="false" Priority="70" SemiHidden="false"    UnhideWhenUsed="false" Name="Dark List Accent 2"/>   <w:LsdException Locked="false" Priority="71" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful Shading Accent 2"/>   <w:LsdException Locked="false" Priority="72" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful List Accent 2"/>   <w:LsdException Locked="false" Priority="73" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful Grid Accent 2"/>   <w:LsdException Locked="false" Priority="60" SemiHidden="false"    UnhideWhenUsed="false" Name="Light Shading Accent 3"/>   <w:LsdException Locked="false" Priority="61" SemiHidden="false"    UnhideWhenUsed="false" Name="Light List Accent 3"/>   <w:LsdException Locked="false" Priority="62" SemiHidden="false"    UnhideWhenUsed="false" Name="Light Grid Accent 3"/>   <w:LsdException Locked="false" Priority="63" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Shading 1 Accent 3"/>   <w:LsdException Locked="false" Priority="64" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Shading 2 Accent 3"/>   <w:LsdException Locked="false" Priority="65" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium List 1 Accent 3"/>   <w:LsdException Locked="false" Priority="66" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium List 2 Accent 3"/>   <w:LsdException Locked="false" Priority="67" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 1 Accent 3"/>   <w:LsdException Locked="false" Priority="68" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 2 Accent 3"/>   <w:LsdException Locked="false" Priority="69" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 3 Accent 3"/>   <w:LsdException Locked="false" Priority="70" SemiHidden="false"    UnhideWhenUsed="false" Name="Dark List Accent 3"/>   <w:LsdException Locked="false" Priority="71" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful Shading Accent 3"/>   <w:LsdException Locked="false" Priority="72" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful List Accent 3"/>   <w:LsdException Locked="false" Priority="73" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful Grid Accent 3"/>   <w:LsdException Locked="false" Priority="60" SemiHidden="false"    UnhideWhenUsed="false" Name="Light Shading Accent 4"/>   <w:LsdException Locked="false" Priority="61" SemiHidden="false"    UnhideWhenUsed="false" Name="Light List Accent 4"/>   <w:LsdException Locked="false" Priority="62" SemiHidden="false"    UnhideWhenUsed="false" Name="Light Grid Accent 4"/>   <w:LsdException Locked="false" Priority="63" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Shading 1 Accent 4"/>   <w:LsdException Locked="false" Priority="64" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Shading 2 Accent 4"/>   <w:LsdException Locked="false" Priority="65" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium List 1 Accent 4"/>   <w:LsdException Locked="false" Priority="66" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium List 2 Accent 4"/>   <w:LsdException Locked="false" Priority="67" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 1 Accent 4"/>   <w:LsdException Locked="false" Priority="68" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 2 Accent 4"/>   <w:LsdException Locked="false" Priority="69" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 3 Accent 4"/>   <w:LsdException Locked="false" Priority="70" SemiHidden="false"    UnhideWhenUsed="false" Name="Dark List Accent 4"/>   <w:LsdException Locked="false" Priority="71" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful Shading Accent 4"/>   <w:LsdException Locked="false" Priority="72" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful List Accent 4"/>   <w:LsdException Locked="false" Priority="73" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful Grid Accent 4"/>   <w:LsdException Locked="false" Priority="60" SemiHidden="false"    UnhideWhenUsed="false" Name="Light Shading Accent 5"/>   <w:LsdException Locked="false" Priority="61" SemiHidden="false"    UnhideWhenUsed="false" Name="Light List Accent 5"/>   <w:LsdException Locked="false" Priority="62" SemiHidden="false"    UnhideWhenUsed="false" Name="Light Grid Accent 5"/>   <w:LsdException Locked="false" Priority="63" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Shading 1 Accent 5"/>   <w:LsdException Locked="false" Priority="64" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Shading 2 Accent 5"/>   <w:LsdException Locked="false" Priority="65" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium List 1 Accent 5"/>   <w:LsdException Locked="false" Priority="66" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium List 2 Accent 5"/>   <w:LsdException Locked="false" Priority="67" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 1 Accent 5"/>   <w:LsdException Locked="false" Priority="68" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 2 Accent 5"/>   <w:LsdException Locked="false" Priority="69" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 3 Accent 5"/>   <w:LsdException Locked="false" Priority="70" SemiHidden="false"    UnhideWhenUsed="false" Name="Dark List Accent 5"/>   <w:LsdException Locked="false" Priority="71" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful Shading Accent 5"/>   <w:LsdException Locked="false" Priority="72" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful List Accent 5"/>   <w:LsdException Locked="false" Priority="73" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful Grid Accent 5"/>   <w:LsdException Locked="false" Priority="60" SemiHidden="false"    UnhideWhenUsed="false" Name="Light Shading Accent 6"/>   <w:LsdException Locked="false" Priority="61" SemiHidden="false"    UnhideWhenUsed="false" Name="Light List Accent 6"/>   <w:LsdException Locked="false" Priority="62" SemiHidden="false"    UnhideWhenUsed="false" Name="Light Grid Accent 6"/>   <w:LsdException Locked="false" Priority="63" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Shading 1 Accent 6"/>   <w:LsdException Locked="false" Priority="64" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Shading 2 Accent 6"/>   <w:LsdException Locked="false" Priority="65" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium List 1 Accent 6"/>   <w:LsdException Locked="false" Priority="66" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium List 2 Accent 6"/>   <w:LsdException Locked="false" Priority="67" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 1 Accent 6"/>   <w:LsdException Locked="false" Priority="68" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 2 Accent 6"/>   <w:LsdException Locked="false" Priority="69" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 3 Accent 6"/>   <w:LsdException Locked="false" Priority="70" SemiHidden="false"    UnhideWhenUsed="false" Name="Dark List Accent 6"/>   <w:LsdException Locked="false" Priority="71" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful Shading Accent 6"/>   <w:LsdException Locked="false" Priority="72" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful List Accent 6"/>   <w:LsdException Locked="false" Priority="73" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful Grid Accent 6"/>   <w:LsdException Locked="false" Priority="19" SemiHidden="false"    UnhideWhenUsed="false" QFormat="true" Name="Subtle Emphasis"/>   <w:LsdException Locked="false" Priority="21" SemiHidden="false"    UnhideWhenUsed="false" QFormat="true" Name="Intense Emphasis"/>   <w:LsdException Locked="false" Priority="31" SemiHidden="false"    UnhideWhenUsed="false" QFormat="true" Name="Subtle Reference"/>   <w:LsdException Locked="false" Priority="32" SemiHidden="false"    UnhideWhenUsed="false" QFormat="true" Name="Intense Reference"/>   <w:LsdException Locked="false" Priority="33" SemiHidden="false"    UnhideWhenUsed="false" QFormat="true" Name="Book Title"/>   <w:LsdException Locked="false" Priority="37" Name="Bibliography"/>   <w:LsdException Locked="false" Priority="39" QFormat="true" Name="TOC Heading"/>  </w:LatentStyles> </xml><![endif]--><!--[if !mso]></p>
<p><object  classid="clsid:38481807-CA0E-42D2-BF39-B33AF135CC4D" id=ieooui></object><br />
<style> st1\:*{behavior:url(#ieooui) } </style>
<p> <![endif]--><!--[if gte mso 10]></p>
<style>  /* Style Definitions */  table.MsoNormalTable 	{mso-style-name:"Table Normal"; 	mso-tstyle-rowband-size:0; 	mso-tstyle-colband-size:0; 	mso-style-noshow:yes; 	mso-style-priority:99; 	mso-style-qformat:yes; 	mso-style-parent:""; 	mso-padding-alt:0in 5.4pt 0in 5.4pt; 	mso-para-margin:0in; 	mso-para-margin-bottom:.0001pt; 	mso-pagination:widow-orphan; 	font-size:10.0pt; 	font-family:"Calibri","sans-serif"; 	mso-bidi-font-family:"Times New Roman";} </style>
<p> <![endif]--></p>
<p>In past blogs, we&#8217;ve discussed how health information exchanges (HIE) play a crucial role in transforming the healthcare industry by enabling the systematic sharing of health-related information between disparate clinical systems and various organizations, or stakeholders. HIEs have demonstrated their ability to improve the clinical and financial performance of healthcare organizations and, if properly designed, can have a clear and commanding return on investment. Promoting sustainable HIEs plays an important role in the improvement of quality, safety and cost-effectiveness of healthcare delivered throughout the country. They ensure that patients, providers, payers and others involved have access to the right information at the right time.</p>
<p>To ensure success, however, HIEs must be able to share a patients’ medical information. For that to happen, an HIE must have a way to obtain meaningful consent and the support of patients. One of the main issues affecting the development of health information exchanges is the role of consumer participation. Consumer education is necessary for establishing trust in an HIE. Many polls and surveys have shown that consumers support the implementation and exchange of EHRs because they can improve patient care and reduce the number of unnecessary tests and procedures.</p>
<p>In our blog on the privacy and security of HIEs, we pointed out that even as an HIE enables an environment with new capabilities and opportunities, it also brings about new challenges. Without consent from patients to share their data, the viability and therefore sustainability of an HIE is limited significantly. Thus, HIEs face a multi-faceted decision on how and when to obtain patient consent. The choice of a consent model affects a multitude of stakeholders, from patients to payers and providers, and can have an impact on the way the HIE is structured.<span id="more-25"></span></p>
<p>The two main options HIEs usually use for patient consent are the opt-in and opt-out approaches. With the opt-in consent model, patients have to give formal consent before any of their data is shared through the HIE. Conversely, with the opt-out model, patient information is automatically included unless patients choose to remove some or all of their data. According to Jennifer Covich Bordenick, CEO of eHealth Initiative (eHI), the opt-out approach is currently used most among HIEs because it is the easiest to do initially, although more HIEs may switch to the opt-in model as other HIEs have success with that model.</p>
<p>With either model, the decision must take into account consumer concerns and needs, state laws, structural limitations, policy decisions and more. Decisions should only be made following research of all related issues and should focus on the needs of all involved stakeholders. Education on consent needs to highlight the safeguards to ensure high levels of privacy and security. Therefore it is necessary to educate patients on the consent process including who has access to their information and privacy issues concerning confidential medical records such as substance abuse records, mental health records and STI/HIV related records.</p>
<p>A prime example of a current HIE utilizing patient consent is HEALTHeLINK, one of the country&#8217;s most successful RHIOs. Companion to HEALTHeLINK, is Western New York’s administrative information exchange, HealtheNet, powered by APP Design’s RHIOnet. RHIOnet provides real-time, online services including health plan eligibility and benefit verification, claim status and inquiry, referral submission, single sign-on and more. APP Design was selected to design and develop a real-time patient consent interface to HEALTHeLINK to increase patient consent by delivering consent status through the eligibility transaction.</p>
<p>The interface, using NHIN XDS.b standards, enables HEALTHeLINK to gather more consent for an opt-in state and further integrates administrative and clinical workflows to reduce costs and improve outcomes for WNY patients. Through the interface, authorized users of WNYHealtheNet are able to retrieve HEALTHeLINK patient consent status during eligibility verification, saving time and multiple logins. This project again uses APP Design’s RHIOnet, a Web-based healthcare information exchange system designed to deliver accurate and timely healthcare data to caregivers distributed across wide geographical areas.</p>
<p>APP Design also was recently awarded a contract by the Office of the National Coordinator (ONC) for Health Information Technology to support its e-consent trial. The e-consent pilot program is scheduled to take place at four provider sites within HEALTHeLINK. Once a consent form is signed by a patient, physicians and other health-care providers who are involved in the patient’s care can securely access their lab results, tests, radiology reports, transcribed reports, medication information and a range of other health information to better treat the patient.</p>
<p>Though the model implemented by WNYHealtheLINK has proven successful, an HIE is only as good as consumers&#8217; willingness to allow their data to be shared in ways that clinicians find valuable. In addition, that willingness will drive the usefulness of the HIE and its sustainability. HIE administrators and healthcare providers are themselves healthcare consumers, and their decisions about patient involvement in the HIE should reflect that.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.appdesign.com/blog/2011/10/10/patient-consent-in-hies-consumers-are-key/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Live and Learn: The Benefits of Using Online Training and E-Learning as a Value-added Service</title>
		<link>http://www.appdesign.com/blog/2011/09/23/live-and-learn-the-benefits-of-using-online-training-and-e-learning-as-a-value-added-service/</link>
		<comments>http://www.appdesign.com/blog/2011/09/23/live-and-learn-the-benefits-of-using-online-training-and-e-learning-as-a-value-added-service/#comments</comments>
		<pubDate>Fri, 23 Sep 2011 17:09:05 +0000</pubDate>
		<dc:creator>Sarah K</dc:creator>
				<category><![CDATA[Business]]></category>

		<guid isPermaLink="false">http://www.appdesign.com/blog/2011/09/23/live-and-learn-the-benefits-of-using-online-training-and-e-learning-as-a-value-added-service/</guid>
		<description><![CDATA[Value-added services in an HIE assist providers in simplifying the administrative side of healthcare while generating a significant amount of revenue with which to sustain the HIE. These services offer solutions to meet the needs of various stakeholders, thereby improving quality of care and providing more favorable patient outcomes. As each HIE and region is [...]]]></description>
			<content:encoded><![CDATA[<p>Value-added services in an HIE assist providers in simplifying the administrative side of healthcare while generating a significant amount of revenue with which to sustain the HIE. These services offer solutions to meet the needs of various stakeholders, thereby improving quality of care and providing more favorable patient outcomes. As each HIE and region is unique, the menu service offerings should reflect the specifics of the community they service.</p>
<p>HIEs which promote an environment where people can achieve their full potential, increase their productivity and expand their professional horizons are most likely to achieve long-term profitability. Learning is essential given the ongoing and rapid changes in the work world, especially in relation to technology. Therefore, investing in the development of the skills of those who are part of an HIE is essential, and a primary method for this development and education is online training, also called e-learning.</p>
<p>Online training provides flexibility and convenience not always available in onsite training by allowing users to train on their own time and at their own pace. Materials can be accessed 24/7 anywhere there is Internet access. An HIE can set up online training specific to its region, allowing other involved entities to access the same program or materials and taking the burden off hospitals in that region.</p>
<p><span id="more-24"></span>One of the biggest benefits online training offers an HIE is reduced cost. According to Training Magazine, corporations save between 50 to 70 percent when replacing instructor-led training with electronic content delivery due to reduced or eliminated travel costs and more targeted training. HIEs can pay for the training used without having to pay for a training professional, and they don&#8217;t have to print and ship expensive manuals.</p>
<p>Research also shows that online training can be nearly 93 percent cheaper than instructor led training while offering customized content to meet specific learning objectives and needs. It allows for the simple yet effective management of targeted, up-to-date content for any size group, especially important for an HIE. Along these same lines, online training enables an administrator to highlight areas of special interest to a group or region.</p>
<p>Online training and e-learning allow HIEs to thoroughly educate and/or train in an engaging and interactive manner through an easy-to-use, intuitive design. They ensure that all users have the in-depth knowledge of the programs they are using, maximizing productivity and improving the quality of their work. They may also assist users in adapting a new technology or provide immediate information on new products or procedures.</p>
<p>On the administrative side, using e-learning in an HIE offers measurable tracking of users&#8217; progress with advanced reporting. Those needing to check a user&#8217;s progress can do so 24/7 without having to sift through a broad spectrum of data. Administrators can compare and contrast results by user, subject, region and more.</p>
<p>As discussed in a previous blog, HIEs must have safeguards and guidelines in place to ensure high levels of privacy and security across the board. The issue of privacy is also relevant in online training and e-learning as sensitive data may be exchanged in such processes. Again, the privacy and security rules of HIPAA require that protected health data is accessible to patients, released according to both state and Federal laws and maintains the privacy, security and integrity of patient data.</p>
<p>While conventional training and instruction may still be the best option in some cases, online training and e-learning provide a quick, effective and cost-saving method for HIEs and their users. As a value-added service, these processes provide a measurable return on investment for an HIE while offering an integral service to those users.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.appdesign.com/blog/2011/09/23/live-and-learn-the-benefits-of-using-online-training-and-e-learning-as-a-value-added-service/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>HIE Privacy and Security: Rules and Regulations for Consumer Confidence</title>
		<link>http://www.appdesign.com/blog/2011/05/19/hie-privacy-and-security-rules-and-regulations-for-consumer-confidence/</link>
		<comments>http://www.appdesign.com/blog/2011/05/19/hie-privacy-and-security-rules-and-regulations-for-consumer-confidence/#comments</comments>
		<pubDate>Thu, 19 May 2011 20:10:46 +0000</pubDate>
		<dc:creator>Rob Q</dc:creator>
				<category><![CDATA[Business]]></category>

		<guid isPermaLink="false">http://www.appdesign.com/blog/2011/05/19/hie-privacy-and-security-rules-and-regulations-for-consumer-confidence/</guid>
		<description><![CDATA[In addition to playing a crucial role in transforming the healthcare industry by enabling the sharing of information between disparate clinical systems and stakeholders, Health information exchanges (HIEs) offer patients a unique and convenient method in deciding how their health data is exchanged. They offer significant benefits and can result in improved patient care and [...]]]></description>
			<content:encoded><![CDATA[<p>In addition to playing a crucial role in transforming the healthcare industry by enabling the sharing of information between disparate clinical systems and  stakeholders, Health information exchanges (HIEs) offer patients a unique and convenient method in deciding how their health data is exchanged. They offer significant benefits and can result in improved patient care and reduced healthcare costs across a large geographic area. Most importantly, they are able to provide complete and accurate patient data, resulting in a more coordinated care process.<br />
While the number and breadth of HIEs is growing across the United States, the issue of privacy and security offered by them has become a hot topic. Just as an HIE enables an environment with new capabilities and opportunities, it also brings about new challenges. To address these challenges, HIEs must have safeguards and guidelines in place to ensure high levels of privacy and security across the board. Although such guidelines are not foolproof, they serve to heighten the level of patient trust, which in turn adds to the success of HIEs.<span id="more-23"></span></p>
<p>A survey run recently by the <a href="http://www.nationalehealth.org">National eHealth Collaborative (NeHC)</a> polled healthcare providers, government units, HIE operators and other officials and found that the issue they believed was most likely to potential derail HIEs was privacy and security. The United States government is taking steps and performing research to combat this issue. For example, Office of the National Coordinator for Health IT (ONC) is working with President Obama&#8217;s cybersecurity initiative to obtain input from security experts across the country, input which will then be used by the ONC to offer standards for HIEs to follow.</p>
<p>There are Federal regulations in place for the exchange of patient health data, and some states have their own laws targeted toward the privacy of such information. As for HIPAA, the law follows the Federal government in that it provides specific rules for the protection of patient data, although it does not override state-level laws which offer higher levels of privacy protection for patients. The privacy and security rules of HIPAA require that protected health data is accessible to patients, released according to both state and Federal laws and maintains the privacy, security and integrity of patient data.</p>
<p>Even with these laws and regulations in place, HIEs should follow a set of guidelines to ensure the privacy and security of their data is handled appropriately and with the right amount of protection. By tackling this issue in the planning stages of the HIE, the correct policies will be in place to offer the most secure solution to protect patient data. Although these guidelines aren&#8217;t state or national-level law, they should work with the specific rules and regulations of the area(s) in which they serve.</p>
<p>First, an HIE should draft an agreement outlining the specific rules and requirements for the parties involved. This agreement should include the terms of inclusion in the HIE along with the rights and responsibilities of all involved. All stakeholders have a right to have a say on the structure of the HIE, especially patients. Without the involvement of patients and their trust, the success of an HIE is severely threatened.</p>
<p>Along the same lines, patients need to be educated on the advantages of HIEs and what safeguards are in place to secure their data so that it doesn&#8217;t fall into the wrong hands. They need to know what data is included in the HIE, what purpose it serves and who has access to it.  Those who are authorized to view patient data must have in place specific accounting for disclosures, risk management and control, limited use statements and an appropriate opt-out procedure. Patient data should be protected by safeguards for unlikely but possible risks including unauthorized access, unnecessary disclosure, loss, significant changes and more.</p>
<p>Patient data for an HIE should be obtained with the consent of the patient and used only for the purposes for which it was received. To provide another layer of security, the HIE should draft a list of who can access the data. Also, the HIE needs to make sure that the people on that list are equipped with appropriate authorization. Unnecessary and/or unlawful use of such patient data can only hurt public opinion on HIEs, placing an unfortunate obstacle to an otherwise comprehensive and innovative system and solution.</p>
<p>Again, while not all security and privacy measures in an HIE are foolproof, having the appropriate guidelines in place to address this issue is integral to the success of an HIE. With the growth of HIEs, the potential benefits they offer can only help improve the delivery of healthcare in this country.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.appdesign.com/blog/2011/05/19/hie-privacy-and-security-rules-and-regulations-for-consumer-confidence/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>HIE Staying Power: Eligibility Verification and Checking</title>
		<link>http://www.appdesign.com/blog/2011/02/15/hie-staying-power-eligibility-verification-and-checking/</link>
		<comments>http://www.appdesign.com/blog/2011/02/15/hie-staying-power-eligibility-verification-and-checking/#comments</comments>
		<pubDate>Tue, 15 Feb 2011 21:51:35 +0000</pubDate>
		<dc:creator>Rob Q</dc:creator>
				<category><![CDATA[Business]]></category>

		<guid isPermaLink="false">http://www.appdesign.com/blog/2011/02/15/hie-staying-power-eligibility-verification-and-checking/</guid>
		<description><![CDATA[Mount Rushmore. Rock music. Baseball and apple pie. No, it&#8217;s not a recipe for a summer road trip, it&#8217;s a list of things that have staying power. Though the facade of Mount Rushmore may change over the years because of environmental conditions, it has been around for many years and will be for years to [...]]]></description>
			<content:encoded><![CDATA[<p>Mount Rushmore. Rock music. Baseball and apple pie.</p>
<p>No, it&#8217;s not a recipe for a summer road trip, it&#8217;s a list of things that have staying power. Though the facade of Mount Rushmore may change over the years because of environmental conditions, it has been around for many years and will be for years to come. Rock music may get harder and less original, but it&#8217;s still a basic of the music scene. As for baseball and apple pie, while other sports may occasional eclipse it in popularity from time to time, stories of fathers and sons &#8211; and daughters! &#8211; bonding over nine innings of strategy and scorekeeping are numerous and legendary.</p>
<p>As discussed in one of our previous posts, an integral part of a successful HIE is working to ensure that it is sustainable long-term. Part of this success involves providing services that reduce existing costs along with services that offer administrative transaction cost savings, thereby balancing the cost of other  services such as clinical data exchange. A service we consider to be high in value is that of eligibility verification or checking.<span id="more-22"></span></p>
<p>A properly designed eligibility verification solution allows an HIE to quickly and effectively connect healthcare providers and health plans in real-time for the exchange of eligibility and benefits data. This eliminates the need to verify patient eligibility through multiple steps, from faxes and phone calls to less efficient paper-based processes. For payers, such a solution renders the ability to communicate patient-specific pre-authorization or eligibility to respond to various patient and provider queries. Also, eligibility verification can provide access to transactions like claim status checks and others. The ability of providers to access this information from one central place, the HIE, instead of multiple payer sites, saves the providers time and money.</p>
<p>A significant benefit of an eligibility verification or checking solution is its ability to lower administration costs for an HIE. By streamlining assorted transactions, the solution reduces rework, provides immediate and current patient data and results in a higher level of accuracy. In the area of patient medication safety, eligibility verification coupled with the reconciliation of prescribed medication and generation of electronic prescriptions can improve patient medication compliance and, most importantly, reduce prescription errors.</p>
<p>Security is a concern in any technology solution, a high quality eligibility verification solution allows for the appropriate exchange of various types of data while insuring the privacy for all those involved in an HIE. Today&#8217;s technologies are able to successfully accomplish this level of security at a much lower initial cost than was previously possible. In addition to the privacy, a well-built eligibility verification solution is by far more reliable that using any paper-based solution.</p>
<p>Advances in eligibility verification and checking put eligibility and benefit information instantly at the fingertips of those who require it in an HIE. Therefore, by implementing such a select service in the early stages of an HIE, a major step toward its sustainability is achieved. Incorporating such an integral solution at this stage also gives those involved a single point of connectivity to access necessary data. Just like with Mount Rushmore, rock music and baseball and apple pie, a successful eligibility verification solution should indeed do a large part to result in the necessary staying power for an HIE.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.appdesign.com/blog/2011/02/15/hie-staying-power-eligibility-verification-and-checking/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>One and Done: The Benefits of Single Sign-on for an HIE</title>
		<link>http://www.appdesign.com/blog/2010/12/07/one-and-done-the-benefits-of-single-sign-on-for-an-hie/</link>
		<comments>http://www.appdesign.com/blog/2010/12/07/one-and-done-the-benefits-of-single-sign-on-for-an-hie/#comments</comments>
		<pubDate>Tue, 07 Dec 2010 17:37:30 +0000</pubDate>
		<dc:creator>Rob Q</dc:creator>
				<category><![CDATA[Business]]></category>

		<guid isPermaLink="false">http://www.appdesign.com/blog/2010/12/07/one-and-done-the-benefits-of-single-sign-on-for-an-hie/</guid>
		<description><![CDATA[Although the advice “practice makes perfect” can be beneficial in some aspects of life like music and sports, in others, doing the same thing over and over is not only tiring but also inefficient. Sometimes, when working to accomplish certain tasks, the phrase &#8220;one and done&#8221; can be the best method. Such is the case [...]]]></description>
			<content:encoded><![CDATA[<p>Although the advice “practice makes perfect” can be beneficial in some aspects of life like music and sports, in others, doing the same thing over and over is not only tiring but also inefficient. Sometimes, when working to accomplish certain tasks, the phrase &#8220;one and done&#8221; can be the best method. Such is the case for using single sign-on functionality for a health information exchange (HIE).</p>
<p>As defined in the <a href="http://www.appdesign.com/blog/2010/11/16/taking-the-time-to-do-it-right-value-added-services-in-an-hie/">previous post</a>, value-added services assist providers in simplifying the administrative side of healthcare while generating a significant amount of revenue with which to sustain the HIE. An especially integral service, single sign-on functionality and/or authentication provides the ability for an authorized user to enter the same identification and password to log on to multiple applications within an HIE, eliminating the need for the memorization and/or storage of assorted passwords.<span id="more-20"></span></p>
<p>Provided at the Web portal to an HIE, a single sign-on server stores multiple passwords in a secure database, making it available to the user transparently during the login process. This value-added service eliminates the often frustrating need for management of multiple passwords and saves time by not having to repeatedly log in and out of applications.</p>
<p>Through use of single sign-on (SSO), an HIE is able to centralize authorization credentials from multiple back-end applications through a portal that uses application definitions. Because the ability to easily and securely access data from any location plays an integral role in maintaining unimpeded workflow and directly impacts the quality of patient care, single sign-on benefits providers as well as the HIE.</p>
<p>In addition to eliminating the need for multiple passwords and saving time for users, single-sign on provides a whole host of benefits for an HIE. Users have a convenient and more efficient way to access the data they need, resulting in increased productivity. Also, by allowing the user to navigate through multiple applications without repeated logins, the possibility of human error is dramatically decreased.</p>
<p>For those who manage an HIE, single sign-on allows them to better monitor, control, protect and update authorization data for increased compliance and security. Through easier management of authorization data, it enables centralized security reporting and auditing for compliance adherence. Single sign-on also provides them with a common authentication framework, improving developer productivity. Access to applications or functions within applications can be restricted when the user is not at work or not on the assigned work location. Plus, through simplified administration, an HIE doesn&#8217;t have to spend more time and money retrieving forgotten passwords for users, thereby reducing operational costs.</p>
<p>It is important to note that single sign-on is not the only answer to improved security within an HIE but rather an integral part of the bigger picture. In order for single sign-on to be effective for a sustainable HIE, it must involve comprehensive planning and the correct combination of infrastructure tools. It also needs to be designed correctly to achieve the many benefits it is able to provide. With each of these things in place, single sign-on can provide an invaluable contribution to the success of the HIE.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.appdesign.com/blog/2010/12/07/one-and-done-the-benefits-of-single-sign-on-for-an-hie/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Taking the Time to Do it Right: Value-Added Services in an HIE</title>
		<link>http://www.appdesign.com/blog/2010/11/16/taking-the-time-to-do-it-right-value-added-services-in-an-hie/</link>
		<comments>http://www.appdesign.com/blog/2010/11/16/taking-the-time-to-do-it-right-value-added-services-in-an-hie/#comments</comments>
		<pubDate>Tue, 16 Nov 2010 14:49:51 +0000</pubDate>
		<dc:creator>Rob Q</dc:creator>
				<category><![CDATA[Business]]></category>

		<guid isPermaLink="false">http://www.appdesign.com/blog/2010/11/16/taking-the-time-to-do-it-right-value-added-services-in-an-hie/</guid>
		<description><![CDATA[Nothing lasts forever. They don&#8217;t make &#8216;em like that anymore. You get what you pay for. Many of us have least heard, if not spoken, these phrases once or twice in our lifetime. Often we think businesses are in too much of a hurry these days to give us the level of service we deserve [...]]]></description>
			<content:encoded><![CDATA[<p>Nothing lasts forever. They don&#8217;t make &#8216;em like that anymore. You get what you pay for.</p>
<p>Many of us have least heard, if not spoken, these phrases once or twice in our lifetime. Often we think businesses are in too much of a hurry these days to give us the level of service we deserve and that products are not made as well as they were decades ago. It&#8217;s as if taking enough time to make sure something is done right isn&#8217;t part of our culture anymore.</p>
<p>When it comes to building and maintaining a sustainable HIE, though, taking the time to do it right is essential. As we discussed in our previous post, there is there is no magic bullet for long-term HIE sustainability, but HIEs that make sustainability an integral part of their long term plan can reduce or eliminate their dependence on grant funding. Also as previously mentioned, grants can be use in the initial, start-up phase of an HIE but should not be relied upon past that stage. This post will highlight one of the steps in the plan &#8211; offering value-added services alongside the clinical exchange to fund the HIE.</p>
<p><span id="more-19"></span></p>
<p>For our purposes, value-added services are defined as those which assist providers in simplifying the administrative side of healthcare while generating a significant amount of revenue with which to sustain the HIE. They should be services that the community wants at a fee applicable to their specific market, and they should contribute to the sustainability of the HIE while matching its clinical priorities. HIEs may even layer such services to add to their contribution to the community and stakeholders whom they serve. Again, a small margin on these services can result in considerable amounts of funding for the HIE while still providing savings to members over current costs.</p>
<p>Those HIEs that have enjoyed long-term success have typically implemented value-added services incrementally, starting with those that encourage participation and result in measurable revenue right off the bat. Though not all value-added services revenues are directly measurable, they should all provide some level of value to the HIE. These services have to offer solutions to meet the needs of various stakeholders in order to improve quality of care and provide more favorable patient outcomes. As each HIE and region is unique, the menu service offerings depend upon which services deliver the most “bang for the buck” for its members.</p>
<p>Pricing of value-added services for an HIE has to be figured so that what the HIE charges to cover the cost of a service covers its expenses and surpasses the value of that service in the community or marketplace. The HIE should be careful in offering “loss leaders”  that encourage usage without significant revenues.  Though Tthese can be helpful in early stages, by driving towards increased usage that will ultimately result in significant revenues, the HIE must have reasonable expectation the revenues will soon materialize. And of course, the quality of the services an HIE offers needs to be even with or above those of similar service providers within the community.</p>
<p>Development and deployment of value-added services within an HIE must consider the specifics of the community it services. The market for value-added services in each area should be examined along with the geographic reach and demographics of that community. Even though evaluating a prospective service can involve measuring its technical, operational and economic viability, that process is all for naught if that service does not fit the needs of the HIEs community.</p>
<p>Some value-added services an HIE can provide include payer eligibility and claim submission/inquiry, transcription and coding services, community-wide credentialing, authentication,  authorization and enrollment/screening services. Others may involve , quality reporting, patient access, community-wide analysis  and more.. In our next post, we&#8217;ll highlight some of these servicesone specific service, single sign-on, and explain why they&#8217;re its especially important to a sustainable HIE.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.appdesign.com/blog/2010/11/16/taking-the-time-to-do-it-right-value-added-services-in-an-hie/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>HIE Sustainability: Expecting a magic bullet?</title>
		<link>http://www.appdesign.com/blog/2010/11/09/hie-sustainability-expecting-a-magic-bullet/</link>
		<comments>http://www.appdesign.com/blog/2010/11/09/hie-sustainability-expecting-a-magic-bullet/#comments</comments>
		<pubDate>Tue, 09 Nov 2010 22:56:07 +0000</pubDate>
		<dc:creator>Rob Q</dc:creator>
				<category><![CDATA[Business]]></category>

		<guid isPermaLink="false">http://www.appdesign.com/blog/2010/11/09/hie-sustainability-expecting-a-magic-bullet/</guid>
		<description><![CDATA[Gratification, as defined by Wikipedia, is &#8220;the positive emotional response (happiness) to a fulfillment of desire.&#8221; We have become a society in which we not only want instant gratification, we seem to expect it. With technology embedded into most facets of our life, we get used to instant access, quick responses and often immediate solutions. [...]]]></description>
			<content:encoded><![CDATA[<p>Gratification, as defined by Wikipedia, is &#8220;the positive emotional response (happiness) to a fulfillment of desire.&#8221; We have become a society in which we not only want instant gratification, we seem to expect it. With technology embedded into most facets of our life, we get used to instant access, quick responses and often immediate solutions. The increased speed and efficiency of appliances, computers and other forms of technology have enabled us to accomplish more than was possible in previous decades. Even though information flows more swiftly and freely than it ever has, many of us become deeply impatient when we don&#8217;t get a response or answer right away.</p>
<p>Although health information exchanges (HIE) play a crucial role in transforming the healthcare industry by enabling the systematic sharing of health-related information between disparate clinical systems and various organizations, or stakeholders, there is no magic bullet for long-term HIE sustainability. <span id="more-18"></span>For HIEs, also often referred to as regional health information organizations (RHIOs), to achieve future sustainability, there are certian steps that have to be taken, steps that do not result in instant gratification.</p>
<p>First, it&#8217;s important to note that HIEs which rely heavily or solely on major grant funding face considerable sustabinability issues. While grants can play an important part in the start-up or initial stages of an HIE, this funding is usually given all at once or only available during a specific period of time. Grants allow organizations to pursue implementation without establishing a self-sustaining revenue model up front. As a result, such HIEs must be prepared with a solution for when the grant money runs dry.</p>
<p>Second, if an HIE is to be sustainable, a framework that is centered on what its stakeholders value is necessary. This requires community participation and effort by the stakeholders as they address issues that could affect the HIE. For most organizations, a successful HIE allows relevant healthcare data to be available when and where it is needed. It must not only contribute to improved patient care and safety but also assist in reducing the time and costs of delivering healthcare for it stakeholders. An HIE that benefits patients by placing increased burdens on providers is ultimately unsustainable. The HIE must also deliver significant benefits to providers, both large and small, to encourage participation.</p>
<p>Third, being able to measure the return on investment, or ROI, by stakeholders and the community in general is a necessary step in creating a sustainable HIE. By demonstrating sufficient value, both existing and potential, in the early stages of an HIE, those funding it are able to see its inherent value and benefits. Adding a consistent review process to measure its success both financially and clinically allows those invested in an HIE to realize the need for continued involvement, providing another step in sustainability.</p>
<p>Next, an HIE that is to remain sustainable for years to come must become a hub for healthcare related information. Ask the users of one of our customers, WNY HealtheNet. They will say they cannot remember how they got along without it. It has simply become a part of their daily life, and they cannot imagine going back to the “bad old days.” In addition, an HIE should offer value-added services, reduce administrative costs and facilitate reduced operational costs. It should become the central point for healthcare information for patients, providers and payers. In our next few posts, we’ll explain how offering value-added services alongside the clinical exchange can be used to fund the HIE, eliminating a dependence on grants.</p>
<p>According to a report just released by eHealth Initiative (eHI) titled &#8220;The State of Health Information Exchange in 2010: Connecting the Nation to Achieve Meaningful Use,&#8221; there is continued growth in the number of HIE initiatives and those which are operational. eHealth Initiative counts 234 active HIEs in the country as of July 27, 2010, and those operational initiatives are currently transmitting data that is being used by stakeholders.</p>
<p>Even as HIEs have been shown to improve healthcare and lower costs, implementing a business model which highlights the need for funding from stakeholders who obtain value and benefits using technology to share health information among key healthcare providers is critical. HIE developers must know what participants expect to receive from the exchange. Especially for those organizations not reliant upon grant funding, sustainability is an attainable goal for HIEs as more and more organizations are providing services to patients and providing access to patient data through them.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.appdesign.com/blog/2010/11/09/hie-sustainability-expecting-a-magic-bullet/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>&#8220;Hidden in Plain Sight&#8221; book</title>
		<link>http://www.appdesign.com/blog/2007/09/02/hidden-in-plain-sight-book/</link>
		<comments>http://www.appdesign.com/blog/2007/09/02/hidden-in-plain-sight-book/#comments</comments>
		<pubDate>Sun, 02 Sep 2007 21:34:09 +0000</pubDate>
		<dc:creator>Ivan K</dc:creator>
				<category><![CDATA[Business]]></category>

		<guid isPermaLink="false">http://www.appdesign.com/blog/2008/01/11/hidden-in-plain-sight-book/</guid>
		<description><![CDATA[Finished a third of the Hidden in Plain Sight book. I thought I read good reviews about it, but I could not find them any more. Anyway, the premise is this: find out what customers want and deliver it. This breakthrough insight is based on a number of corporate anecdotes. I feel cheated out of [...]]]></description>
			<content:encoded><![CDATA[<p>Finished a third of the <a href="http://http://www.amazon.com/Hidden-Plain-Sight-Companys-Strategy/dp/1422101657/ref=pd_bbs_sr_1?ie=UTF8&amp;s=books&amp;qid=1200086678&amp;sr=8-1" target="_blank">Hidden in Plain Sight</a> book. I thought I read good reviews about it, but I could not find them any more. Anyway, the premise is this: find out what customers want and deliver it. This breakthrough insight is based on a number of corporate anecdotes. I feel cheated out of my $20, I hope I bought it used.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.appdesign.com/blog/2007/09/02/hidden-in-plain-sight-book/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>The &#8220;Halo Effect&#8221; book</title>
		<link>http://www.appdesign.com/blog/2007/06/19/the-halo-effect-book/</link>
		<comments>http://www.appdesign.com/blog/2007/06/19/the-halo-effect-book/#comments</comments>
		<pubDate>Tue, 19 Jun 2007 18:06:56 +0000</pubDate>
		<dc:creator>Ivan K</dc:creator>
				<category><![CDATA[Business]]></category>

		<guid isPermaLink="false">http://www.appdesign.com/blog/2008/01/09/the-halo-effect-book/</guid>
		<description><![CDATA[Just finished reading The Halo Effect: &#8230; book by Phil Rosenzweig. It is almost exclusively devoted to debunking these three books: Built to Last: Successful Habits of Visionary Companies by Jim Collins and Jerry I. Porras Good to Great: Why Some Companies Make the Leap&#8230; and Others Don&#8217;t by Jim Collins In Search of Excellence [...]]]></description>
			<content:encoded><![CDATA[<p> Just finished reading <a href="http://www.amazon.com/Halo-Effect-Business-Delusions-Managers/dp/0743291255/ref=sr_1_5?ie=UTF8&amp;s=books&amp;qid=1199899187&amp;sr=1-5"><span class="sans">The Halo Effect: &#8230;</span></a>  book by Phil Rosenzweig. It is almost exclusively devoted to debunking these three books:<span id="more-4"></span></p>
<ol>
<li><a href="http://www.amazon.com/Built-Last-Successful-Visionary-Companies/dp/0060566108/ref=pd_bbs_sr_1?ie=UTF8&amp;s=books&amp;qid=1199899638&amp;sr=1-1"><span class="srTitle">Built to Last: Successful Habits of Visionary Companies</span></a>      by Jim Collins and Jerry I. Porras</li>
<li><a href="http://www.amazon.com/Good-Great-Companies-Leap-Others/dp/0066620996/ref=pd_bbs_2?ie=UTF8&amp;s=books&amp;qid=1199899638&amp;sr=1-2"><span class="srTitle">Good to Great: Why Some Companies Make the Leap&#8230; and Others Don&#8217;t</span></a>      by Jim Collins</li>
<li><a href="http://www.amazon.com/Search-Excellence-Americas-Best-Run-Companies/dp/B0007M2K8Q/ref=pd_bbs_sr_1?ie=UTF8&amp;s=books&amp;qid=1199899830&amp;sr=1-1"><span class="srTitle">In Search of Excellence                                                          : Lessons from America&#8217;s Best-Run Companies</span></a>      by Thomas J. Peters and Robert H. Waterman</li>
</ol>
<p>I&#8217;m very glad that Mr. Rosenzweig bothered to do it. I read &#8220;Build to Last&#8221; several years ago and it immediately struck me a pile of bovine manure and, yes, it&#8217;s easy for me to say in hindsight. You see, I&#8217;m a former scientist and the main argument of these books is logically similar to this:</p>
<ol>
<li>Start tossing coins.</li>
<li>Discard all the tails.</li>
<li>Claim that coin toss produces heads.</li>
</ol>
<p>And that was just a start. If I dared to present something like this at any scientific forum or journal, I would be laughed off the podium and never allowed to speak again. Yet,  Messrs. Collins, Porras, Peters, and Waterman have managed to build a nice cottage industry out of their respective delusions.<br />
<a href="http://www.amazon.com/exec/obidos/search-handle-url/002-8247529-2644019?%5Fencoding=UTF8&amp;search-type=ss&amp;index=books&amp;field-author=Phil%20Rosenzweig"></a></p>
<p>Phil Rosenzweig has many more insights into the fallacies of these books, but the most crucial idea is simple: they tell compelling stories we&#8217;d like to hear &#8211; similar to motivational speeches &#8211; and we suspend our critical thinking in awe. The actual facts produced by the scientific methods are far less glamorous, but much more honest: we simple do not know the recipe for success and our chances of finding out are slim given the complexities of the business world. There are some subtle  hints, though.</p>
<p>So, I&#8217;m now a big fan of Mr. Rosenzweig now and I highly recommend this book.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.appdesign.com/blog/2007/06/19/the-halo-effect-book/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
