<?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: HL7 Minimum Layer Protocol (MLP) Defined</title>
	<atom:link href="http://www.hl7standards.com/blog/2007/05/02/hl7-mlp-minimum-layer-protocol-defined/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.hl7standards.com/blog/2007/05/02/hl7-mlp-minimum-layer-protocol-defined/</link>
	<description>Healthcare &#38; Technology Resources</description>
	<lastBuildDate>Fri, 03 Feb 2012 23:54:00 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.1</generator>
	<item>
		<title>By: HL7 Version Ambiguity? Just Say No! &#124; HL7 Standards</title>
		<link>http://www.hl7standards.com/blog/2007/05/02/hl7-mlp-minimum-layer-protocol-defined/comment-page-1/#comment-39340</link>
		<dc:creator>HL7 Version Ambiguity? Just Say No! &#124; HL7 Standards</dc:creator>
		<pubDate>Thu, 14 Jan 2010 22:49:40 +0000</pubDate>
		<guid isPermaLink="false">http://hl7standards.com/blog/2007/05/02/hl7-mlp-minimum-layer-protocol-defined/#comment-39340</guid>
		<description></description>
		<content:encoded><![CDATA[<p>[...] a self-professed &ldquo;HL7 neophyte&rdquo;, while minutes later I may be on a call to review customized TCP/MLPmessage framing test results with a beleaguered multi-tasker. Thus, while some are very conversant [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Getting Started with Your HL7 Interface &#124; HL7 Standards</title>
		<link>http://www.hl7standards.com/blog/2007/05/02/hl7-mlp-minimum-layer-protocol-defined/comment-page-1/#comment-38784</link>
		<dc:creator>Getting Started with Your HL7 Interface &#124; HL7 Standards</dc:creator>
		<pubDate>Mon, 16 Nov 2009 22:15:44 +0000</pubDate>
		<guid isPermaLink="false">http://hl7standards.com/blog/2007/05/02/hl7-mlp-minimum-layer-protocol-defined/#comment-38784</guid>
		<description></description>
		<content:encoded><![CDATA[<p>[...] Details &#8211; Most HL7 interfaces transmit data over TCP/IP. That being the case, it is important to get the IP address and port information where these [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Healthcare Un-Interoperability &#124; Bob on Medical Device Software</title>
		<link>http://www.hl7standards.com/blog/2007/05/02/hl7-mlp-minimum-layer-protocol-defined/comment-page-1/#comment-36439</link>
		<dc:creator>Healthcare Un-Interoperability &#124; Bob on Medical Device Software</dc:creator>
		<pubDate>Thu, 16 Jul 2009 21:40:12 +0000</pubDate>
		<guid isPermaLink="false">http://hl7standards.com/blog/2007/05/02/hl7-mlp-minimum-layer-protocol-defined/#comment-36439</guid>
		<description>[...] MLLP (Minimal Lower Layer Protocol) [...]</description>
		<content:encoded><![CDATA[<p>[...] MLLP (Minimal Lower Layer Protocol) [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: The Essentials of a Good Interface Engine</title>
		<link>http://www.hl7standards.com/blog/2007/05/02/hl7-mlp-minimum-layer-protocol-defined/comment-page-1/#comment-9851</link>
		<dc:creator>The Essentials of a Good Interface Engine</dc:creator>
		<pubDate>Tue, 04 Sep 2007 13:56:50 +0000</pubDate>
		<guid isPermaLink="false">http://hl7standards.com/blog/2007/05/02/hl7-mlp-minimum-layer-protocol-defined/#comment-9851</guid>
		<description>[...] support special communications needs that are not handled by the standard TCP/IP connection, such as custom acknowledgements or encryption, as well as non-HL7 formats that may have been [...]</description>
		<content:encoded><![CDATA[<p>[...] support special communications needs that are not handled by the standard TCP/IP connection, such as custom acknowledgements or encryption, as well as non-HL7 formats that may have been [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Getting Started with Your HL7 Interface</title>
		<link>http://www.hl7standards.com/blog/2007/05/02/hl7-mlp-minimum-layer-protocol-defined/comment-page-1/#comment-9539</link>
		<dc:creator>Getting Started with Your HL7 Interface</dc:creator>
		<pubDate>Wed, 29 Aug 2007 16:57:58 +0000</pubDate>
		<guid isPermaLink="false">http://hl7standards.com/blog/2007/05/02/hl7-mlp-minimum-layer-protocol-defined/#comment-9539</guid>
		<description></description>
		<content:encoded><![CDATA[<p>[...] Details &#8211; Most HL7 interfaces transmit data over TCP/IP. That being the case, it is important to get the IP address and port information where these [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Point-to-Point Interface vs. Interface Engine in Healthcare</title>
		<link>http://www.hl7standards.com/blog/2007/05/02/hl7-mlp-minimum-layer-protocol-defined/comment-page-1/#comment-9211</link>
		<dc:creator>Point-to-Point Interface vs. Interface Engine in Healthcare</dc:creator>
		<pubDate>Thu, 23 Aug 2007 22:32:07 +0000</pubDate>
		<guid isPermaLink="false">http://hl7standards.com/blog/2007/05/02/hl7-mlp-minimum-layer-protocol-defined/#comment-9211</guid>
		<description>[...] A method for moving data [...]</description>
		<content:encoded><![CDATA[<p>[...] A method for moving data [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rene Spronk</title>
		<link>http://www.hl7standards.com/blog/2007/05/02/hl7-mlp-minimum-layer-protocol-defined/comment-page-1/#comment-4087</link>
		<dc:creator>Rene Spronk</dc:creator>
		<pubDate>Wed, 23 May 2007 22:01:14 +0000</pubDate>
		<guid isPermaLink="false">http://hl7standards.com/blog/2007/05/02/hl7-mlp-minimum-layer-protocol-defined/#comment-4087</guid>
		<description>Alex,

Release 2 of MLLP enhances the well-known MLLP protocol by an ack/nak message, effectively turning MLLP into a reliable messaging protocol. See http://www.hl7.org/v3ballot/html/infrastructure/transport/transport-mllp.htm (a v3 spec, but it also covers HL7 v2).

TTYL,

-Rene</description>
		<content:encoded><![CDATA[<p>Alex,</p>
<p>Release 2 of MLLP enhances the well-known MLLP protocol by an ack/nak message, effectively turning MLLP into a reliable messaging protocol. See <a href="http://www.hl7.org/v3ballot/html/infrastructure/transport/transport-mllp.htm" rel="nofollow" onclick="pageTracker._trackPageview('/outgoing/www.hl7.org/v3ballot/html/infrastructure/transport/transport-mllp.htm?referer=');">http://www.hl7.org/v3ballot/html/infrastructure/transport/transport-mllp.htm</a> (a v3 spec, but it also covers HL7 v2).</p>
<p>TTYL,</p>
<p>-Rene</p>
]]></content:encoded>
	</item>
</channel>
</rss>

