<?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 for blogs.czapski.id.au</title>
	<atom:link href="http://blogs.czapski.id.au/comments/feed" rel="self" type="application/rss+xml" />
	<link>http://blogs.czapski.id.au</link>
	<description>Formerly Java CAPS, OpenESB and related - of late HL7 tooling and solutions using WebLogic and SOA Suite and HL7.</description>
	<lastBuildDate>Sun, 10 Feb 2013 03:38:09 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.5.1</generator>
	<item>
		<title>Comment on Migrating Java CAPS 5/6 Assets to Oracle SOA Suite 11g &#8211; HL7 JCD to Spring Component Migration by Migrating Java CAPS 5/6 Assets to Oracle SOA Suite &#8211; HL7 JCD to Document Callout Migration</title>
		<link>http://blogs.czapski.id.au/2010/10/migrating-java-caps-56-assets-to-oracle-soa-suite-11g-hl7-jcd-to-spring-component-migration/comment-page-1#comment-3163</link>
		<dc:creator>Migrating Java CAPS 5/6 Assets to Oracle SOA Suite &#8211; HL7 JCD to Document Callout Migration</dc:creator>
		<pubDate>Sun, 10 Feb 2013 03:38:09 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.czapski.id.au/?p=632#comment-3163</guid>
		<description><![CDATA[[...] Java CAPS 5/6 Assets to Oracle SOA Suite 11g – HL7 JCD to Spring Component Migration”, at http://blogs.czapski.id.au/2010/10/migrating-java-caps-56-assets-to-oracle-soa-suite-11g-hl7-jcd-to-...,  and presents a different method of recusing “HL7 Transformer JCD” code in a SOA or OSB [...]]]></description>
		<content:encoded><![CDATA[<p>[...] Java CAPS 5/6 Assets to Oracle SOA Suite 11g – HL7 JCD to Spring Component Migration”, at <a href="http://blogs.czapski.id.au/2010/10/migrating-java-caps-56-assets-to-oracle-soa-suite-11g-hl7-jcd-to-" rel="nofollow">http://blogs.czapski.id.au/2010/10/migrating-java-caps-56-assets-to-oracle-soa-suite-11g-hl7-jcd-to-</a>&#8230;,  and presents a different method of recusing “HL7 Transformer JCD” code in a SOA or OSB [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on SOA Suite for healthcare integration Series &#8211; Implement an A19 Query Processor by SOA Suite for healthcare integration Series &#8211; Series Overview</title>
		<link>http://blogs.czapski.id.au/2013/01/soa-suite-for-healthcare-integration-series-implement-an-a19-query-processor/comment-page-1#comment-3149</link>
		<dc:creator>SOA Suite for healthcare integration Series &#8211; Series Overview</dc:creator>
		<pubDate>Sun, 03 Feb 2013 20:45:56 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.czapski.id.au/?p=748#comment-3149</guid>
		<description><![CDATA[[...] Implementing an A19 Query Processor &#8211; http://blogs.czapski.id.au/2013/01/soa-suite-for-healthcare-integration-series-implement-an-a19-quer... [...]]]></description>
		<content:encoded><![CDATA[<p>[...] Implementing an A19 Query Processor &#8211; <a href="http://blogs.czapski.id.au/2013/01/soa-suite-for-healthcare-integration-series-implement-an-a19-quer" rel="nofollow">http://blogs.czapski.id.au/2013/01/soa-suite-for-healthcare-integration-series-implement-an-a19-quer</a>&#8230; [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on SOA Suite for healthcare integration Series &#8211; Routing and Transformation using XSL Solution by SOA Suite for healthcare integration Series &#8211; Series Overview</title>
		<link>http://blogs.czapski.id.au/2012/12/soa-suite-for-healthcare-integration-series-routing-and-transformation-using-xsl-solution/comment-page-1#comment-3148</link>
		<dc:creator>SOA Suite for healthcare integration Series &#8211; Series Overview</dc:creator>
		<pubDate>Sun, 03 Feb 2013 20:45:36 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.czapski.id.au/?p=720#comment-3148</guid>
		<description><![CDATA[[...] Transformation and Routing using XSL and Mediator &#8211; http://blogs.czapski.id.au/2012/12/soa-suite-for-healthcare-integration-series-routing-and-transform... [...]]]></description>
		<content:encoded><![CDATA[<p>[...] Transformation and Routing using XSL and Mediator &#8211; <a href="http://blogs.czapski.id.au/2012/12/soa-suite-for-healthcare-integration-series-routing-and-transform" rel="nofollow">http://blogs.czapski.id.au/2012/12/soa-suite-for-healthcare-integration-series-routing-and-transform</a>&#8230; [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on SOA Suite for healthcare integration Series &#8211; Domain Value Map (DVM) – On-the-fly Code Mapping by SOA Suite for healthcare integration Series &#8211; Series Overview</title>
		<link>http://blogs.czapski.id.au/2013/01/soa-suite-for-healthcare-integration-series-domain-value-map-dvm-on-the-fly-code-mapping/comment-page-1#comment-2921</link>
		<dc:creator>SOA Suite for healthcare integration Series &#8211; Series Overview</dc:creator>
		<pubDate>Sat, 05 Jan 2013 01:28:57 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.czapski.id.au/?p=718#comment-2921</guid>
		<description><![CDATA[[...] Adding Data Map for pass-through code translation &#8211; http://blogs.czapski.id.au/2013/01/soa-suite-for-healthcare-integration-series-domain-value-map-dvm-... [...]]]></description>
		<content:encoded><![CDATA[<p>[...] Adding Data Map for pass-through code translation &#8211; <a href="http://blogs.czapski.id.au/2013/01/soa-suite-for-healthcare-integration-series-domain-value-map-dvm-" rel="nofollow">http://blogs.czapski.id.au/2013/01/soa-suite-for-healthcare-integration-series-domain-value-map-dvm-</a>&#8230; [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on SOA Suite for healthcare integration Series &#8211; HL7 v2 Inbound to File Solution by SOA Suite for healthcare integration Series &#8211; Series Overview</title>
		<link>http://blogs.czapski.id.au/2012/11/soa-suite-for-healthcare-integration-series-hl7-v2-inbound-to-file-solution/comment-page-1#comment-2920</link>
		<dc:creator>SOA Suite for healthcare integration Series &#8211; Series Overview</dc:creator>
		<pubDate>Sat, 05 Jan 2013 01:28:41 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.czapski.id.au/?p=708#comment-2920</guid>
		<description><![CDATA[[...] HL7 v2 Inbound to File &#8211; http://blogs.czapski.id.au/2012/11/soa-suite-for-healthcare-integration-series-hl7-v2-inbound-to-fil... [...]]]></description>
		<content:encoded><![CDATA[<p>[...] HL7 v2 Inbound to File &#8211; <a href="http://blogs.czapski.id.au/2012/11/soa-suite-for-healthcare-integration-series-hl7-v2-inbound-to-fil" rel="nofollow">http://blogs.czapski.id.au/2012/11/soa-suite-for-healthcare-integration-series-hl7-v2-inbound-to-fil</a>&#8230; [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on SOA Suite for healthcare integration Series &#8211; Exception Handling &#8211; Processing Endpoint Errors by SOA Suite for healthcare integration Series &#8211; Series Overview</title>
		<link>http://blogs.czapski.id.au/2013/01/soa-suite-for-healthcare-integration-series-exception-handling-processing-endpoint-errors/comment-page-1#comment-2919</link>
		<dc:creator>SOA Suite for healthcare integration Series &#8211; Series Overview</dc:creator>
		<pubDate>Sat, 05 Jan 2013 01:28:14 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.czapski.id.au/?p=739#comment-2919</guid>
		<description><![CDATA[[...] Automating Exception Message Handling &#8211; http://blogs.czapski.id.au/2013/01/soa-suite-for-healthcare-integration-series-exception-handling-pr... [...]]]></description>
		<content:encoded><![CDATA[<p>[...] Automating Exception Message Handling &#8211; <a href="http://blogs.czapski.id.au/2013/01/soa-suite-for-healthcare-integration-series-exception-handling-pr" rel="nofollow">http://blogs.czapski.id.au/2013/01/soa-suite-for-healthcare-integration-series-exception-handling-pr</a>&#8230; [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on SOA Suite for healthcare integration Series &#8211; HL7 v2 Inbound CMM to Outbound Pass-through Solution by SOA Suite for healthcare integration Series &#8211; Series Overview</title>
		<link>http://blogs.czapski.id.au/2012/12/soa-suite-for-healthcare-integration-series-hl7-v2-inbound-cmm-to-outbound-pass-through-solution/comment-page-1#comment-2918</link>
		<dc:creator>SOA Suite for healthcare integration Series &#8211; Series Overview</dc:creator>
		<pubDate>Sat, 05 Jan 2013 01:27:59 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.czapski.id.au/?p=714#comment-2918</guid>
		<description><![CDATA[[...] HL7 v2 Inbound to HL7 v2 Outbound Pass-through &#8211; http://blogs.czapski.id.au/2012/12/soa-suite-for-healthcare-integration-series-hl7-v2-inbound-cmm-to... [...]]]></description>
		<content:encoded><![CDATA[<p>[...] HL7 v2 Inbound to HL7 v2 Outbound Pass-through &#8211; <a href="http://blogs.czapski.id.au/2012/12/soa-suite-for-healthcare-integration-series-hl7-v2-inbound-cmm-to" rel="nofollow">http://blogs.czapski.id.au/2012/12/soa-suite-for-healthcare-integration-series-hl7-v2-inbound-cmm-to</a>&#8230; [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on SOA Suite for healthcare integration Series &#8211; Creating a Canonical HL7 v2 Message Model by SOA Suite for healthcare integration Series &#8211; Series Overview</title>
		<link>http://blogs.czapski.id.au/2012/09/soa-suite-for-healthcare-integration-series-creating-a-canonical-hl7-v2-message-model/comment-page-1#comment-2917</link>
		<dc:creator>SOA Suite for healthcare integration Series &#8211; Series Overview</dc:creator>
		<pubDate>Sat, 05 Jan 2013 01:27:42 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.czapski.id.au/?p=702#comment-2917</guid>
		<description><![CDATA[[...] Creating a Canonical Message Model &#8211; http://blogs.czapski.id.au/2012/09/soa-suite-for-healthcare-integration-series-creating-a-canonical-... [...]]]></description>
		<content:encoded><![CDATA[<p>[...] Creating a Canonical Message Model &#8211; <a href="http://blogs.czapski.id.au/2012/09/soa-suite-for-healthcare-integration-series-creating-a-canonical-" rel="nofollow">http://blogs.czapski.id.au/2012/09/soa-suite-for-healthcare-integration-series-creating-a-canonical-</a>&#8230; [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on SOA Suite for healthcare integration Series &#8211; Overview of the Development Environment by SOA Suite for healthcare integration Series &#8211; Implement an A19 Query Processor</title>
		<link>http://blogs.czapski.id.au/2012/08/soa-suite-for-healthcare-integration-series-overview-of-the-development-environment/comment-page-1#comment-2916</link>
		<dc:creator>SOA Suite for healthcare integration Series &#8211; Implement an A19 Query Processor</dc:creator>
		<pubDate>Sat, 05 Jan 2013 01:07:20 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.czapski.id.au/?p=699#comment-2916</guid>
		<description><![CDATA[[...] While most HL7 v2 messaging is of the store-and-forward kind, where a sender sends a message to a partner, receives a positive acknowledgement and forgets the transaction, there are circumstances where a sender wants to query the receiver and get and process a response. For ADT-related queries A19 transaction serves this function. A client application can send an A19 QRY message, with a patient identifier and assigning authority and request patient demographic information to be returned using the A19 ADR response message. In this article we will develop and exercise an A19 Query Processor solution. This article assumes that the reader has the SOA Suite for healthcare integration environment with all necessary components installed and ready to use. The Bill of Materials for such an environment and a discussion on where the components can be obtained is provided in the earlier article, “SOA Suite for healthcare integration Series &#8211; Overview of the Development Environment”, to be found at http://blogs.czapski.id.au/2012/08/soa-suite-for-healthcare-integration-series-overview-of-the-devel.... [...]]]></description>
		<content:encoded><![CDATA[<p>[...] While most HL7 v2 messaging is of the store-and-forward kind, where a sender sends a message to a partner, receives a positive acknowledgement and forgets the transaction, there are circumstances where a sender wants to query the receiver and get and process a response. For ADT-related queries A19 transaction serves this function. A client application can send an A19 QRY message, with a patient identifier and assigning authority and request patient demographic information to be returned using the A19 ADR response message. In this article we will develop and exercise an A19 Query Processor solution. This article assumes that the reader has the SOA Suite for healthcare integration environment with all necessary components installed and ready to use. The Bill of Materials for such an environment and a discussion on where the components can be obtained is provided in the earlier article, “SOA Suite for healthcare integration Series &#8211; Overview of the Development Environment”, to be found at <a href="http://blogs.czapski.id.au/2012/08/soa-suite-for-healthcare-integration-series-overview-of-the-devel" rel="nofollow">http://blogs.czapski.id.au/2012/08/soa-suite-for-healthcare-integration-series-overview-of-the-devel</a>&#8230;. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on SOA Suite for healthcare integration Series &#8211; Overview of the Development Environment by SOA Suite for healthcare integration Series &#8211; Externalise, Repair and Resubmit “Broken” Messages</title>
		<link>http://blogs.czapski.id.au/2012/08/soa-suite-for-healthcare-integration-series-overview-of-the-development-environment/comment-page-1#comment-2897</link>
		<dc:creator>SOA Suite for healthcare integration Series &#8211; Externalise, Repair and Resubmit “Broken” Messages</dc:creator>
		<pubDate>Fri, 04 Jan 2013 01:22:57 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.czapski.id.au/?p=699#comment-2897</guid>
		<description><![CDATA[[...] This article assumes that the reader has the SOA Suite for healthcare integration environment with all necessary components installed and ready to use. The Bill of Materials for such an environment and a discussion on where the components can be obtained is provided in the earlier article, “SOA Suite for healthcare integration Series &#8211; Overview of the Development Environment”, to be found at http://blogs.czapski.id.au/2012/08/soa-suite-for-healthcare-integration-series-overview-of-the-devel.... [...]]]></description>
		<content:encoded><![CDATA[<p>[...] This article assumes that the reader has the SOA Suite for healthcare integration environment with all necessary components installed and ready to use. The Bill of Materials for such an environment and a discussion on where the components can be obtained is provided in the earlier article, “SOA Suite for healthcare integration Series &#8211; Overview of the Development Environment”, to be found at <a href="http://blogs.czapski.id.au/2012/08/soa-suite-for-healthcare-integration-series-overview-of-the-devel" rel="nofollow">http://blogs.czapski.id.au/2012/08/soa-suite-for-healthcare-integration-series-overview-of-the-devel</a>&#8230;. [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
