Get started with the BizTalk Accelerator for HL7


Using the Microsoft BizTalk Accelerator for HL7 (BTAHL7), you can develop business processes between your health care computer systems. By using BTAHL7, developers, IT professionals, and interface analysts can work in a common environment to develop end-to-end integrated BTAHL7-based solutions across health care applications.

More specifically, with BTAHL7 you can:

  • Simplify health care application integration. Build, manage, and track distributed business processes using the BizTalk Server development environment.

  • Standardize clinical data interchange between medical applications. Transform existing data transmission between applications to the BTAHL7 standard.

  • Increase efficiency. Automate all communication processes between medical applications with minimal manual intervention.

This section provides role-specific information about how you can use BTAHL7 and BizTalk Server to facilitate Enterprise Application Integration (EAI) within hospitals and the healthcare arena to automate business-to-business healthcare solutions.

BTAHL7 provides four separate scenarios in tutorial format for each type of solution. Before you begin these tutorials, you should understand the fundamental concepts in BizTalk Server, and the tools and processes that are required to start building solutions with BTAHL7.

System_CAPS_ICON_tip.jpg Tip

Before you begin these lessons, learn about the HL7 accelerator and the BizTalk tools available.

The following descriptions provide a general understanding of each BTAHL7 tutorial.

The BTAHL7 End-to-End tutorial provides you with detailed steps to facilitate business processes in a subscriber and publisher scenario. This scenario is a situation in which a publisher, for example, an Admissions Discharge and Transfer system sends a message to specific subscribers.

The message routes to the BTAHL7 Interface Engine, which in turn receives, processes, validates, reformats, and then routes the message to the subscribers. The subscribers in this scenario are a Hospital Information System and a Pharmacy System.

This scenario uses both File and Minimal Lower Layer Protocol (MLLP) adapter types. The publisher does not need to be aware of the subscribers, and the BTAHL7 Interface Engine sends an appropriate acknowledgement to the publisher after processing the message.

The BTAHL7 Interrogative tutorial provides you with detailed steps for implementing a query-response system between sub-systems within an organization. In this scenario, a line-of-business (LOB) application in the Admissions, Discharge, and Transfer system sends a query to the Hospital Information System to obtain patient lab results. After the Hospital Information System receives the query, it sends the requested data back to the system that issued the query.

This scenario uses MLLP as the transport protocol for all messages, including acknowledgments.

The BTAHL7 Enrichment tutorial provides you with detailed steps to solve a particular business problem: the message-enrichment scenario. The message-enrichment scenario is a situation in which you have to add to, or enrich, a message that is not HL7-compliant and/or is incomplete. This situation can occur with an application, such as a patient-registration application, or when you are populating a message with XML data from SQL Server.

In the message enrichment scenario, 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 adapter.

The BTAHL7 Batching tutorial provides you with detailed steps to receive and send batched messages. Batching involves receiving and/or sending a group of individual messages (or acknowledgments) as a single composite message.

BTAHL7 supports the following three message batching scenarios:

  • Fragmented inbound batch. In this scenario, BTAHL7 receives an HL7 message batch, and then routes the individual messages to the destination system.

  • Batch in/batch out. BTAHL7 receives an HL7 message batch, verifies the individual messages within the batch, and then routes the message batch to the destination system.

  • Create batch (or outbound batching). BTAHL7 receives individual messages and batches them before routing them to the destination system.

Accessibility for People with Disabilities