<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Legacy Data Conversion: Fuzzy Patient Matching to the EHR</title>
	<atom:link href="http://blog.galenhealthcare.com/2009/12/08/legacy-data-conversion-fuzzy-patient-matching-to-the-ehr/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.galenhealthcare.com/2009/12/08/legacy-data-conversion-fuzzy-patient-matching-to-the-ehr/</link>
	<description>Empowering our partners to provide extraordinary patient care</description>
	<lastBuildDate>Thu, 02 Feb 2012 19:57:45 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Justin Campbell</title>
		<link>http://blog.galenhealthcare.com/2009/12/08/legacy-data-conversion-fuzzy-patient-matching-to-the-ehr/comment-page-1/#comment-2046</link>
		<dc:creator>Justin Campbell</dc:creator>
		<pubDate>Tue, 08 Dec 2009 19:31:07 +0000</pubDate>
		<guid isPermaLink="false">http://blog.galenhealthcare.com/?p=419#comment-2046</guid>
		<description>John - thanks for the comment. As a side note, we also assisted the same client in another issue with this legacy conversion. The flat-file export from the legacy system included a process in which a manual operator would go through a series of menus, selecting options for format of the file output. Inconsistencies in the process used by these operators led to unformatted textual result, thus causing the text to render as a blog after import into the EHR. We were able to write a script to update these records inserting carriage return and line-feeds, keying off of labels (Patient Name, Accession Number, etc) to properly format the results. Just a seemingly small programmatical update improved the perception of the client&#039;s IT staff with end-users and clinicians.</description>
		<content:encoded><![CDATA[<p>John &#8211; thanks for the comment. As a side note, we also assisted the same client in another issue with this legacy conversion. The flat-file export from the legacy system included a process in which a manual operator would go through a series of menus, selecting options for format of the file output. Inconsistencies in the process used by these operators led to unformatted textual result, thus causing the text to render as a blog after import into the EHR. We were able to write a script to update these records inserting carriage return and line-feeds, keying off of labels (Patient Name, Accession Number, etc) to properly format the results. Just a seemingly small programmatical update improved the perception of the client&#8217;s IT staff with end-users and clinicians.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: John Lynn</title>
		<link>http://blog.galenhealthcare.com/2009/12/08/legacy-data-conversion-fuzzy-patient-matching-to-the-ehr/comment-page-1/#comment-2044</link>
		<dc:creator>John Lynn</dc:creator>
		<pubDate>Tue, 08 Dec 2009 17:28:15 +0000</pubDate>
		<guid isPermaLink="false">http://blog.galenhealthcare.com/?p=419#comment-2044</guid>
		<description>Very cool stuff.  I love the concept of Fuzzy Lookup.  A lot of stuff can be improved using this type of process.

Data conversion is such a pain in the butt though.  Sadly most EMR systems make it even harder than it should be.</description>
		<content:encoded><![CDATA[<p>Very cool stuff.  I love the concept of Fuzzy Lookup.  A lot of stuff can be improved using this type of process.</p>
<p>Data conversion is such a pain in the butt though.  Sadly most EMR systems make it even harder than it should be.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

