<?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>DocAsap &#187; HITECH act</title>
	<atom:link href="http://blog.docasap.com/tag/hitech-act/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.docasap.com</link>
	<description>Company news and online health care insights</description>
	<lastBuildDate>Wed, 18 Jan 2012 18:42:27 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>HITECH Act and EMR implementation hurdles</title>
		<link>http://blog.docasap.com/2009/03/addressing-emr-implementation-hurdles-for-small-practices/</link>
		<comments>http://blog.docasap.com/2009/03/addressing-emr-implementation-hurdles-for-small-practices/#comments</comments>
		<pubDate>Sun, 01 Mar 2009 20:02:48 +0000</pubDate>
		<dc:creator>vince</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[Allscripts]]></category>
		<category><![CDATA[EMR]]></category>
		<category><![CDATA[HITECH act]]></category>

		<guid isPermaLink="false">http://blog.docasap.com/?p=80</guid>
		<description><![CDATA[Today&#8217;s NYT article on the hurdles that small practices might face with EMR implementation in lieu of the HITECH Act corroborates our earlier post about the steep learning curve in implementing the systems.  One provision of the HITECH Act that gives us optimism that the government will help small practices install EMRs is the funding [...]]]></description>
		<wfw:commentRss>http://blog.docasap.com/2009/03/addressing-emr-implementation-hurdles-for-small-practices/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

