<?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/"
	xmlns:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments on: About the Reporting Framework Integration Project</title>
	<atom:link href="http://ruddzw.wordpress.com/2007/05/30/about-the-reporting-framework-integration-project/feed/" rel="self" type="application/rss+xml" />
	<link>http://ruddzw.wordpress.com/2007/05/30/about-the-reporting-framework-integration-project/</link>
	<description>BIRT Integration, Web Services, and Saving Lives</description>
	<lastBuildDate>Thu, 19 Jun 2008 01:52:48 +0000</lastBuildDate>
	<generator>http://wordpress.com/</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Justin Miranda</title>
		<link>http://ruddzw.wordpress.com/2007/05/30/about-the-reporting-framework-integration-project/#comment-6</link>
		<dc:creator>Justin Miranda</dc:creator>
		<pubDate>Wed, 13 Jun 2007 07:00:59 +0000</pubDate>
		<guid isPermaLink="false">http://ruddzw.wordpress.com/2007/05/30/about-the-reporting-framework-integration-project/#comment-6</guid>
		<description>Rudd, 

The major reason for providing a plugin that interfaces with the OpenMRS API (via web services) is to hide the implementation details of the OpenMRS data model.  This means the user doesn&#039;t have to worry about performing complex joins when defining their report data set (all that is done in the background).  As you say, the main point of this plug-in is to be as transparent as possible.   

Good post.</description>
		<content:encoded><![CDATA[<p>Rudd, </p>
<p>The major reason for providing a plugin that interfaces with the OpenMRS API (via web services) is to hide the implementation details of the OpenMRS data model.  This means the user doesn&#8217;t have to worry about performing complex joins when defining their report data set (all that is done in the background).  As you say, the main point of this plug-in is to be as transparent as possible.   </p>
<p>Good post.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
