<?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>Galen Healthcare Solutions: Allscripts Consultants Enterprise EHR &#187; Results Interface</title>
	<atom:link href="http://blog.galenhealthcare.com/tag/results-interface/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.galenhealthcare.com</link>
	<description>Empowering our partners to provide extraordinary patient care</description>
	<lastBuildDate>Tue, 07 Feb 2012 20:59:28 +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>The Costs of HL7 Interfaces</title>
		<link>http://blog.galenhealthcare.com/2012/01/13/the-costs-of-hl7-interfaces/</link>
		<comments>http://blog.galenhealthcare.com/2012/01/13/the-costs-of-hl7-interfaces/#comments</comments>
		<pubDate>Fri, 13 Jan 2012 17:20:11 +0000</pubDate>
		<dc:creator>Justin Campbell</dc:creator>
				<category><![CDATA[Data Conversion]]></category>
		<category><![CDATA[Interfaces]]></category>
		<category><![CDATA[Interoperability]]></category>
		<category><![CDATA[Clinical Conversion]]></category>
		<category><![CDATA[ConnectR]]></category>
		<category><![CDATA[HL7]]></category>
		<category><![CDATA[HL7 Interface Cost]]></category>
		<category><![CDATA[Integration]]></category>
		<category><![CDATA[Results Interface]]></category>

		<guid isPermaLink="false">http://blog.galenhealthcare.com/?p=2114</guid>
		<description><![CDATA[In the past on this blog, we&#8217;ve addressed the top data integration challenges as well as the ROI of a results interface. Recently, Health Management Technology featured a related article on the economics of interfaces. The key points from the article were as follows:   Opportunity Cost True Investment Integration is not simple Pitfalls of proprietary Features [...]]]></description>
		<wfw:commentRss>http://blog.galenhealthcare.com/2012/01/13/the-costs-of-hl7-interfaces/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Announcing Free Allscripts Result Interface Training</title>
		<link>http://blog.galenhealthcare.com/2011/10/21/announcing-free-allscripts-result-interface-training/</link>
		<comments>http://blog.galenhealthcare.com/2011/10/21/announcing-free-allscripts-result-interface-training/#comments</comments>
		<pubDate>Fri, 21 Oct 2011 17:48:47 +0000</pubDate>
		<dc:creator>Zak Fjeldheim</dc:creator>
				<category><![CDATA[Free Webcasts]]></category>
		<category><![CDATA[Galen Webcast Series]]></category>
		<category><![CDATA[Healthcare IT]]></category>
		<category><![CDATA[Industry Events]]></category>
		<category><![CDATA[Interfaces]]></category>
		<category><![CDATA[Training]]></category>
		<category><![CDATA[Allscripts]]></category>
		<category><![CDATA[Allscripts Enterprise EHR]]></category>
		<category><![CDATA[Allscripts Interface]]></category>
		<category><![CDATA[ConnectR]]></category>
		<category><![CDATA[ConnectR Training]]></category>
		<category><![CDATA[Integration]]></category>
		<category><![CDATA[Interface Training]]></category>
		<category><![CDATA[Interoperability]]></category>
		<category><![CDATA[Results Interface]]></category>

		<guid isPermaLink="false">http://blog.galenhealthcare.com/?p=1790</guid>
		<description><![CDATA[Have you ever found yourself asking how the heck does Imagelink work?  How is it possible to click a button in the Allscripts application and view an X-ray?  Have you ever wanted to know how a result closes an order is closed without a Touchworks Order number?  Have you ever heard someone say, did you [...]]]></description>
		<wfw:commentRss>http://blog.galenhealthcare.com/2011/10/21/announcing-free-allscripts-result-interface-training/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Top 3 EHR Data Integration Challenges</title>
		<link>http://blog.galenhealthcare.com/2011/09/19/top-3-ehr-data-integration-challenges/</link>
		<comments>http://blog.galenhealthcare.com/2011/09/19/top-3-ehr-data-integration-challenges/#comments</comments>
		<pubDate>Mon, 19 Sep 2011 19:50:31 +0000</pubDate>
		<dc:creator>Justin Campbell</dc:creator>
				<category><![CDATA[Device Integration]]></category>
		<category><![CDATA[Interfaces]]></category>
		<category><![CDATA[Interoperability]]></category>
		<category><![CDATA[Allscripts]]></category>
		<category><![CDATA[Extensibility]]></category>
		<category><![CDATA[HIE]]></category>
		<category><![CDATA[HL7]]></category>
		<category><![CDATA[Integration]]></category>
		<category><![CDATA[Results Interface]]></category>
		<category><![CDATA[Standards]]></category>

		<guid isPermaLink="false">http://blog.galenhealthcare.com/?p=1652</guid>
		<description><![CDATA[  In response to a guest post on EMRandHIPAA, we take a look at the top EHR data integration challenges faced today: Technology Proliferation of point-to-point interfaces instead of using a hub-and-spoke type of model (like that which Surescripts utilizes with electronic prescribing). Unfortunately, most organizations which exchange data in and out of the AE-EHR utilize highly-customized [...]]]></description>
		<wfw:commentRss>http://blog.galenhealthcare.com/2011/09/19/top-3-ehr-data-integration-challenges/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Allscripts Enterprise EHR Imagelink Demonstration</title>
		<link>http://blog.galenhealthcare.com/2010/11/17/allscripts-enterprise-ehr-imagelink-demonstration/</link>
		<comments>http://blog.galenhealthcare.com/2010/11/17/allscripts-enterprise-ehr-imagelink-demonstration/#comments</comments>
		<pubDate>Wed, 17 Nov 2010 14:57:52 +0000</pubDate>
		<dc:creator>Justin Campbell</dc:creator>
				<category><![CDATA[Client Success Stories]]></category>
		<category><![CDATA[Demonstration]]></category>
		<category><![CDATA[Interfaces]]></category>
		<category><![CDATA[Meaningful Use]]></category>
		<category><![CDATA[Technical]]></category>
		<category><![CDATA[Allscripts Enterprise EHR]]></category>
		<category><![CDATA[Enterprise EHR]]></category>
		<category><![CDATA[Extensibility]]></category>
		<category><![CDATA[Imagelink]]></category>
		<category><![CDATA[Integration]]></category>
		<category><![CDATA[Interoperability]]></category>
		<category><![CDATA[Results Interface]]></category>

		<guid isPermaLink="false">http://blog.galenhealthcare.com/?p=1071</guid>
		<description><![CDATA[A recent article in Health Management Technology &#8211; Poised to touch all things -  highlighted the importance of Picture Archiving and Communication System (PACs) and offered the opinions of where PACs is headed from various leaders within the industry. Additionally, as presented in a recent article in Health Data Management -  Is a Picture Worth [...]]]></description>
		<wfw:commentRss>http://blog.galenhealthcare.com/2010/11/17/allscripts-enterprise-ehr-imagelink-demonstration/feed/</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
		<item>
		<title>Order Reconciliation Woes</title>
		<link>http://blog.galenhealthcare.com/2010/10/11/order-reconciliation-woes/</link>
		<comments>http://blog.galenhealthcare.com/2010/10/11/order-reconciliation-woes/#comments</comments>
		<pubDate>Mon, 11 Oct 2010 13:13:32 +0000</pubDate>
		<dc:creator>Justin Campbell</dc:creator>
				<category><![CDATA[Healthcare IT]]></category>
		<category><![CDATA[Interfaces]]></category>
		<category><![CDATA[Meaningful Use]]></category>
		<category><![CDATA[Technical]]></category>
		<category><![CDATA[Allscripts Enterprise EHR]]></category>
		<category><![CDATA[CPOE]]></category>
		<category><![CDATA[Crystal Reports]]></category>
		<category><![CDATA[Custom Reports]]></category>
		<category><![CDATA[Integration]]></category>
		<category><![CDATA[Interoperability]]></category>
		<category><![CDATA[Order Interface]]></category>
		<category><![CDATA[Reconciliation]]></category>
		<category><![CDATA[Reporting]]></category>
		<category><![CDATA[Requisition]]></category>
		<category><![CDATA[Results Interface]]></category>

		<guid isPermaLink="false">http://blog.galenhealthcare.com/?p=571</guid>
		<description><![CDATA[Organizations exploring Computerized Physician Order Entry (CPOE) might first pursue low-hanging fruit and implement an electronic workflow for results and keep a paper workflow for orders. Often times, electronic order entry can be cumbersome for end users and cause longer workflows.  As alluded to in a previous blog article, the benefits of implementing a solicited [...]]]></description>
		<wfw:commentRss>http://blog.galenhealthcare.com/2010/10/11/order-reconciliation-woes/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Proposing an Allscripts Clinical Application Programming Interface Re-design</title>
		<link>http://blog.galenhealthcare.com/2010/09/15/proposing-an-allscripts-clinical-application-programming-interface-re-design/</link>
		<comments>http://blog.galenhealthcare.com/2010/09/15/proposing-an-allscripts-clinical-application-programming-interface-re-design/#comments</comments>
		<pubDate>Wed, 15 Sep 2010 14:38:43 +0000</pubDate>
		<dc:creator>Justin Campbell</dc:creator>
				<category><![CDATA[Healthcare IT]]></category>
		<category><![CDATA[Interfaces]]></category>
		<category><![CDATA[Meaningful Use]]></category>
		<category><![CDATA[Technical]]></category>
		<category><![CDATA[Allscripts Enterprise EHR]]></category>
		<category><![CDATA[ConnectR]]></category>
		<category><![CDATA[Database]]></category>
		<category><![CDATA[Enterprise EHR]]></category>
		<category><![CDATA[Enterprise Order]]></category>
		<category><![CDATA[HIE]]></category>
		<category><![CDATA[HL7]]></category>
		<category><![CDATA[Integration]]></category>
		<category><![CDATA[Interoperability]]></category>
		<category><![CDATA[Results Interface]]></category>

		<guid isPermaLink="false">http://blog.galenhealthcare.com/?p=777</guid>
		<description><![CDATA[Currently, exchange of clinical data in and out of the Allscripts Enterprise EHR is facilitated via stored procedures. This  application programming interface (API) approach certainly comes with its downsides. In this article, we propose a re-design of the API to segment out the data and the configuration components of clinical data exchange. At the outset [...]]]></description>
		<wfw:commentRss>http://blog.galenhealthcare.com/2010/09/15/proposing-an-allscripts-clinical-application-programming-interface-re-design/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Result Data Exchange with the EHR</title>
		<link>http://blog.galenhealthcare.com/2009/11/03/result-data-exchange-with-the-ehr/</link>
		<comments>http://blog.galenhealthcare.com/2009/11/03/result-data-exchange-with-the-ehr/#comments</comments>
		<pubDate>Tue, 03 Nov 2009 11:55:21 +0000</pubDate>
		<dc:creator>Justin Campbell</dc:creator>
				<category><![CDATA[Interfaces]]></category>
		<category><![CDATA[Technical]]></category>
		<category><![CDATA[TouchWorks EHR]]></category>
		<category><![CDATA[Custom Reports]]></category>
		<category><![CDATA[EHR]]></category>
		<category><![CDATA[Integration]]></category>
		<category><![CDATA[Results Interface]]></category>

		<guid isPermaLink="false">http://blog.galenhealthcare.com/?p=273</guid>
		<description><![CDATA[The benefits of a results data exchange between a vendor system and the Electronic Healthcare Record (EHR) are profound, as the need for redundant and often erroneous data is greatly reduced. More importantly, by implementing a results data exchange to the EHR, providers are delivered more timely and accurate clinical data, yielding an increased level [...]]]></description>
		<wfw:commentRss>http://blog.galenhealthcare.com/2009/11/03/result-data-exchange-with-the-ehr/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>Result Synching</title>
		<link>http://blog.galenhealthcare.com/2009/05/11/220/</link>
		<comments>http://blog.galenhealthcare.com/2009/05/11/220/#comments</comments>
		<pubDate>Mon, 11 May 2009 20:00:52 +0000</pubDate>
		<dc:creator>Erin Sain</dc:creator>
				<category><![CDATA[Healthcare IT]]></category>
		<category><![CDATA[Implementations]]></category>
		<category><![CDATA[TouchWorks EHR]]></category>
		<category><![CDATA[Allscripts Consultants]]></category>
		<category><![CDATA[Allscripts Enterprise EHR]]></category>
		<category><![CDATA[Results Interface]]></category>
		<category><![CDATA[Successful EHR Implementation]]></category>

		<guid isPermaLink="false">http://blog.galenhealthcare.com/?p=220</guid>
		<description><![CDATA[Synching of results in Allscripts Enterprise EHR v11 has been both very appealing and difficult for many to understand. The premise is this – if a patient has a test done over time, you would like to compare the results – in HMPs, flow sheets and result history.  If the lab changes the code used [...]]]></description>
		<wfw:commentRss>http://blog.galenhealthcare.com/2009/05/11/220/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

