Message Enrichment Tutorial
This tutorial provides step-by-step procedures for using Microsoft BizTalk Accelerator for HL7 (BTAHL7) to solve a particular business problem: the message enrichment problem. The message enrichment tutorial describes a situation in which you have to add to, or enrich, a message that is not HL7-compliant and/or is incomplete. This can occur with an application, such as a patient registration application, or it can occur when you are populating a message with XML data from Microsoft SQL Server.
In this tutorial, you capture the messages with BTAHL7, and provide any missing data, for example, from a patient records database. You then convert the message and send it to a laboratory, insurance, or any legacy line-of-business (LOB) application using the MLLP (Minimal Lower Layer Protocol) adapter.
In this tutorial, you use a Web service client (WSClient.exe) application to send an XML-formatted message, in this case a "doorbell" Register Patient trigger event, through the SOAP adapter to BizTalk Server with BTAHL7. BizTalk Server receives the message in a SOAP receive port, and routes the message to an orchestration published as a Web service. The XML message contains a patient name and social security number. You augment the message, and use schemas, a map, and a transform to convert the message into HL7 format. You will then send it through an MLLP adapter to the laboratory, insurance, or LOB application.
The following figure shows the process flow of the tutorial.
Note
This tutorial requires Windows Server Standard, Enterprise, Datacenter, or Web Edition, and a custom BTAHL7 installation that includes the MLLP test tools. Additionally, you should be familiar with BizTalk Server development in Visual C# and the information found in learn about the HL7 accelerator and the BizTalk tools available.
Note
You can avoid errors by undeploying assemblies, stopping send ports, and disabling receive locations that you used in previous tutorials.