<?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>mirth &#8211; Santeware | Engineering Healthcare Data</title>
	<atom:link href="https://santeware.com/tag/mirth/feed/" rel="self" type="application/rss+xml" />
	<link>https://santeware.com</link>
	<description>&#124; Meeting Requirements &#124; Exceeding Expectations</description>
	<lastBuildDate>Fri, 05 Mar 2021 13:53:43 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=7.0</generator>

<image>
	<url>https://santeware.com/wp-content/uploads/2021/02/fav_icon.png</url>
	<title>mirth &#8211; Santeware | Engineering Healthcare Data</title>
	<link>https://santeware.com</link>
	<width>32</width>
	<height>32</height>
</image> 
	<item>
		<title>How is web API different from traditional HL7 and FHIR?</title>
		<link>https://santeware.com/how-is-web-api-different-from-traditional-hl7-and-fhir/</link>
					<comments>https://santeware.com/how-is-web-api-different-from-traditional-hl7-and-fhir/#comments</comments>
		
		<dc:creator><![CDATA[superadmin]]></dc:creator>
		<pubDate>Tue, 08 Sep 2020 09:54:00 +0000</pubDate>
				<category><![CDATA[Blog]]></category>
		<category><![CDATA[API]]></category>
		<category><![CDATA[interface]]></category>
		<category><![CDATA[mirth]]></category>
		<category><![CDATA[Restful API]]></category>
		<category><![CDATA[Santeware]]></category>
		<guid isPermaLink="false">http://localhost/sante/?p=257</guid>

					<description><![CDATA[RESTful API are the backbone of many webservices today. Having the tools to integrate an not-natively-RESTful interface engine with this common standard opens a lot of possibilities. There will be hurdles for implementing tools like these, especially since some of core RESTful requirements are lost, namely: statelessness, cacheability, and code on demand. Representational State Transfer [&#8230;]]]></description>
		
					<wfw:commentRss>https://santeware.com/how-is-web-api-different-from-traditional-hl7-and-fhir/feed/</wfw:commentRss>
			<slash:comments>5</slash:comments>
		
		
			</item>
		<item>
		<title>Why is Mirth Connect the number 1 preferred interface engine</title>
		<link>https://santeware.com/why-is-mirth-connect-the-preferred-interface-engine/</link>
					<comments>https://santeware.com/why-is-mirth-connect-the-preferred-interface-engine/#respond</comments>
		
		<dc:creator><![CDATA[superadmin]]></dc:creator>
		<pubDate>Tue, 04 Aug 2020 01:16:00 +0000</pubDate>
				<category><![CDATA[Blog]]></category>
		<category><![CDATA[EMR integration]]></category>
		<category><![CDATA[HL7]]></category>
		<category><![CDATA[mirth]]></category>
		<category><![CDATA[Santeware]]></category>
		<guid isPermaLink="false">http://localhost/sante/?p=263</guid>

					<description><![CDATA[NextGen Connect or Mirth connect is a cross-platform interface engine used in the healthcare industry that enables the management of information using bi-directional sending of many types of messages. The primary use of this interface engine is in healthcare. On September 9th, 2013 Mirth Corporation announced they were acquired by Quality Systems. Mirth Connect has [&#8230;]]]></description>
		
					<wfw:commentRss>https://santeware.com/why-is-mirth-connect-the-preferred-interface-engine/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
	</channel>
</rss>
