Each different domain, covered by HL7 v2 standard, has a set of message definitions which support message exchanges for a particular domain. Most of the message definitions for a domain share certain segments. Many of the segments are optional and perhaps not used in a particular messaging environment.
In any but the simplest of HL7 messaging environments there will be multiple sources and multiple destinations of HL7 messages. It is very unlikely that all, or even a majority of these, will use exactly the same HL7 message structures in terms of versions, optional/mandatory segments, extension Z segments, and so on.
It is common for integrating specialists, if the tooling which they use permits, to develop one or few generalised message structures which can be used to represent more than one distinct message from a domain they work with. These are typically called canonical models. The overriding purpose is to standardise the message payload being passed around between integration components, enabling reuse and reducing complexity. The Canonical Message model (CMM) works hand-in-glove with the enterprise architecture in which transformation to/from the CMM is performed at the edges of the integration domain, standardizing as much as possible, payload structure within the integration domain.
The article, whose full text is available at https://blogs.czapski.id.au/wp-content/uploads/2012/09/SOASuiteHCI_ch5_CanonicalMessage_v0.1.0.pdf, works through the mechanics of deriving a Canonical Message Model for the series of articles on SOA Suite for healthcare integration using the “Oracle SOA Suite for healthcare integration” tooling. It contains an abridged version of the article “Healthcare Enterprise – IT Architecture Building Blocks – Canonical Message Model for a HL7 Enterprise”, available at https://blogs.czapski.id.au/2010/10/healthcare-enterprise-%e2%80%93-it-architecture-building-blocks-canonical-message-model-for-a-hl7-enterprise, but adds new material related to testing the canonical structure against sample data and modifying the structure to accommodate data idiosyncrasies.
blogs.czapski.id.au
Articles on gtkdialog and demo image building. Formerly on JavaCAPS and SOA Suite for healthcare integration.
Sep 02
This blog used to have technical material on different topics relating to Sun Java CAPS, OpenESB and SOA Suite for healthcare integration.
New posts are not going to be related to either of these. Of late the technical topics relate to building Linux-based infrastructure demo images.
What the future holds - who knows ...
Hello Michael,
Thanks a lot for this very outstanding article!
I installed the latest version of the Oracle Document Editor (11.1.1.5) from link address http://download.oracle.com/otn/nt/middleware/11g/111150/ofm_doc_editor_win_11.1.1.5_disk1_1of3.zip….
When I run install.exe at the top level, it installs XML automotive. So I went into the Oracle Document Editor folder and ran setup.exe to install it.
After I installed the latest version, it installed Oracle Document Editor 7.0.5.4016 and I run specbuilder.exe (powered by Edifecs) but the screens for usage of the Oracle Document in your PDF don’t match as this looks like a completely different version. What version are you using?
Thanks a lot for all of your great help!
Fred
Hello, Fred.
Long time no hear.
I alwasy get all components of the SOA SUite distribution, and associated bits, at the same time. From recollection the B2B Document Editor would have been release 6.6.x.x.x. Release 7.x is somewhat different. For example it has support for debugging mapsets, which 6.6 does not have.
Here is the BoM for the image I built:
V29856-01 Oracle WebLogic Server 11gR1 (10.3.6) Generic and Coherence V29856-01 1.0G
V29672-01 Part 1 of 2 Oracle SOA Suite 11g Patch Set 5 (11.1.1.6.0) (Part 1 of 2) V29672-01 Part 1 of 2 1.6G
V29672-01 Part 2 of 2 Oracle SOA Suite 11g Patch Set 5 (11.1.1.6.0) (Part 2 of 2) V29672-01 Part 2 of 2 1.2G
V29790-01 Oracle JDeveloper 11g and Oracle Application Development Framework 11g (11.1.1.6.0) V29790-01 1.9G
V29774-01 Oracle JDeveloper 11g Extensions (11.1.1.6.0) V29774-01 698M
V29674-01 Oracle Fusion Middleware Repository Creation Utility 11g (11.1.1.6.0) for Linux x86 V29674-01 390M
V29675-01 Oracle Fusion Middleware Repository Creation Utility 11g (11.1.1.6.0) for Microsoft Windows V29675-01 319M
V18738-01 Oracle Fusion Middleware 11g Release 1 Patch Set 1 Patch Scripts V18738-01 6.4M
V30762-01 Oracle Fusion Middleware Documentation Library 11g Release 1 (11.1.1.6.0) V30762-01 2.5G
V24561-01 Part 1 of 3 B2B Document Editor v11.1.1.4.0 (Part 1 of 3) V24561-01 Part 1 of 3 157M
V24561-01 Part 2 of 3 B2B Document Editor v11.1.1.4.0 (Part 2 of 3) V24561-01 Part 2 of 3 1.8G
V24561-01 Part 3 of 3 B2B Document Editor v11.1.1.4.0 (Part 3 of 3) V24561-01 Part 3 of 3 2.2G
V30996-01 Oracle JDK 6 Update 31 for Microsoft Windows x64 (64-bit) V30996-01 69M
V31000-01 Oracle JDK 6 Update 31 documentation (covers JDK and JRE) V31000-01 59M
I did not bother creating an installation document because tehre are plenty of them around. I used one to guide me through the installaiton process, though once you have done that half a dozen times it sort of goes automatically – dangerous …
Regards
Michael
[…] Creating a Canonical Message Model – https://blogs.czapski.id.au/2012/09/soa-suite-for-healthcare-integration-series-creating-a-canonical-… […]