End-to-End Tutorial for BizTalk Accelerator for HL7

This tutorial contains detailed steps that describe how you use Microsoft BizTalk Accelerator for HL7 (BTAHL7) to facilitate business processes in a subscriber and publisher scenario.

Important

To use this tutorial, you must install the test tools when installing BTAHL7. If you performed a typical installation to install BTAHL7, then you must run a Custom installation and install the test tools in order for this tutorial to work correctly. At the Custom Setup screen of the BTAHL7 custom installation, select MLLP Test Tool from the Adapter folder, and select Test Instances from the Artifacts folder. For more information, see Install BizTalk Accelerator for HL7.

Declarative Scenario

This tutorial uses the publish/subscribe or declarative scenario. In the declarative scenario, the flow of business is similar to that shown in the following figure. The numbered list following the figure describes the workflow.

1. The workflow begins when the publisher, for example, an Admissions Discharge and Transfer system, sends a message to specific subscribers. The publisher in the workflow is "Tutorial_ADTSystem", and the message is called "ADT^A03."

2. The message is routed to the BTAHL7 Interface Engine, which in turn receives, processes, validates, reformats, and then routes the message to subscribers.

3. The subscribers in this scenario are a Hospital Information System (Tutorial_HISystem) and a Pharmacy System (Tutorial_RXSystem). This scenario uses both File and MLLP adapter types. The publisher does not need to be aware of the subscribers and BTAHL7 appropriately sends an acknowledgment to the publisher after processing the message.

4. The publisher sends the ADT^A03 message through a one-way MLLP adapter (Tutorial_1WayReceivePort).

5. The destination of this message is the BTAHL7 Interface Engine, so the incoming message contains a source message (MSH3 = Tutorial_ADTSystem) and a destination message (MSH5 = BTAHL7InterfaceEngine).

6. BTAHL7 generates an acknowledgment (ACK) after appropriately validating the message, and then sends the acknowledgment to the Tutorial_ADTSystem through the File adapter.

7. The Tutorial_HISystem system and the Tutorial_RXSystem system subscribe to the ADT message received by the BTAHL7 Interface Engine.

8. The transformation occurs when you specify values for the respective fields by using the MSH Map tab in BTAHL7 Configuration Explorer.

   For example, the party Tutorial_RXSystem has MSH3=BTHL7 specified in the MSH Map tab. Therefore, the message received by the subscriber will have "BTAHL7" as the value for the MSH3 field.

In this section

• Testing Your Installation

• Preparing to Use the Tutorial

• Step 1: Create and Deploy Header and Acknowledgment Schemas

• Step 2: Create Common Schemas for v2.3.1

• Step 3: Create and Deploy a Trigger Event (Message) Project

• Step 4: Create the Receive Port for Accepting ADT^A03 Messages from ADT Systems Using the MLLP Adapter

• Step 5: Create a Send Port to Deliver Acknowledgments to the ADT System Using the File Adapter

• Step 6: Create a Send Port to Deliver the ADT^A03 Message to the RX System Using the File Adapter

• Step 7: Create a Send Port to Deliver the ADT^A03 Message to HIS Using the MLLP Adapter

• Step 8: Configure Party Information

• Step 9: Restart BizTalk Server

• Step 10: Verify the End-to-End Scenario

See also

Get started with the BizTalk Accelerator for HL7