FIX: A hotfix is available that enables partial name resolution on the BizTalk Accelerator for HL7 2.X assembler/disassembler in BizTalk Server 2006 R2 and in BizTalk Server 2009

Article translations Article translations
Article ID: 977120 - View products that this article applies to.
Expand all | Collapse all

On This Page

INTRODUCTION

This article describes a hotfix that enables partial name resolution on the Microsoft BizTalk Accelerator for HL7 (BTAHL7) 2.X disassembler and on the BTAHL7 2.X assembler in Microsoft BizTalk Server 2006 R2. This hotfix also enables partial name resolution in Microsoft BizTalk Server 2009.

To receive or send HL7 messages, you typically use Microsoft BTAHL7 2.0 in BizTalk Server 2006 R2, or you use Microsoft BizTalk Accelerator 2009 for HL7 in BizTalk Server 2009. You create BizTalk parties for trading partners and then specify configurations in BTAHL7 Configuration Explorer.

A valid HL7 message contains the following information:
  • Source party information in the MSH3 fields of the message header section.
  • Destination party information in the MSH5 fields of the message header section.
The MSH3 source party fields and the MSH5 destination party fields are defined as complex type schema. MSH3 and MSH5 each consists of three fields. The following table describes the value that each field represents:
Collapse this tableExpand this table
MSH3 fields-Source PartyMSH3.1MSH3.2MSH3.3
MSH5 fields-Destination PartyMSH5.1MSH5.2MSH5.3
DescriptionNamespaceIDUniversalIdUniversalIdType
When BTAHL7 processes HL7 messages, the BTAHL7 2.X disassembler and the BTAHL7 2.X assembler try to match the HL7 message to the corresponding BizTalk parties. This behavior is known as party resolution. The disassembler and the assembler use the values in certain HL7 message fields to find a match to the BizTalk parties according to the party names. When the party names are matched to the values in the HL7 message fields, BTAHL7 uses the settings that are configured for the party in BTAHL7 Configuration Explorer to process the HL7 message. Currently, the disassembler and assembler use only the values in the MSH3.1 and MSH5.1 fields to perform party resolution.

More information

After you apply this hotfix, the following new settings are provided for the BTAHL7 2.X disassembler and for the BTAHL7 2.X assembler:
  • For the receive pipeline, the BTAHL7 2.X disassembler contains the following properties:
    • Property name: Enable Partial Name Resolution For Receiving Application
      Default value: False
      Description for the property:
      First check party with name MSH5.1 + MSH5.2 + MSH5.3. If not found, check party with name MSH5.1 + MSH5.2. If not found, check with name MSH5.1.
    • Property name: Enable Partial Name Resolution For Sending Application
      Default value: False
      Description for the property:
      First check party with name MSH3.1 + MSH3.2 + MSH3.3. If not found, check party with name MSH3.1 + MSH3.2. If not found, check with name MSH3.1. 
  • For the send pipeline, the BTAHL7 2.X assembler contains the following property:
    Property name: Enable Partial Name Resolution For Receiving Application
    Default value: False
    Description for the property:
    First check party with name MSH5.1 + MSH5.2 + MSH5.3. If not found, check party with name MSH5.1 + MSH5.2. If not found, check with name MSH5.1. 
You can configure these properties when you create a custom pipeline in Microsoft Visual Studio. Or, you can configure these properties on the Receive Location properties page or on the Send Port properties page in the BizTalk Server Administration console.

When the new properties are enabled, partial name resolution is enabled on the BTAHL7 2.X disassembler and on the BTAHL7 2.X assembler. Partial name resolution provides flexibility for the disassembler and the assembler to adapt to different business requirements.

Hotfix information

For BizTalk Server 2006 R2 and for BizTalk Server 2009

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article.

If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site:
http://support.microsoft.com/contactus/?ws=support
Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.  

Prerequisites

You must have BTAHL7 2.0 or BizTalk Accelerator 2009 for HL7 installed to apply this hotfix. Additionally, you must install the hotfix that is described in the following Microsoft Knowledge Base (KB) article before you apply this hotfix if you are using BTAHL7 2.0. Click the following article number to view the KB article:
961023 FIX: Batched and unbatched messages log event 4119 as an informational event in BTAHL7, or the whole batch is suspended if any message contains a parsing error

Restart requirement

You do not have to restart the computer after you apply this hotfix. However, you must restart the BizTalk Server host instance after you apply this hotfix. For more information about this procedure, refer to the Readme.txt file that is included in the hotfix package.

Hotfix replacement information

This hotfix does not replace other hotfixes.

File information

The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.
BizTalk Accelerator for HL7 2.0
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatform
Btahl72xpipelines.dll2.0.315.042,85614-Jan-201001:31x86
Microsoft.solutions.btahl7.hl72fasm.dll2.0.315.059,27214-Jan-201001:31x86
Microsoft.solutions.btahl7.hl72fdasm.dll2.0.315.0100,23214-Jan-201001:31x86
Microsoft.solutions.btahl7.hl7wizard.dll2.0.302.062,87214-Jan-201001:31x86
Microsoft.solutions.btahl7.shared.dll2.0.315.087,94414-Jan-201001:31x86
BizTalk Accelerator 2009 for HL7
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatform
Btahl72xpipelines.dll3.7.508.242,85619-Feb-201010:20x86
Microsoft.solutions.btahl7.hl72fasm.dll3.7.508.259,27219-Feb-201010:20x86
Microsoft.solutions.btahl7.hl72fdasm.dll3.7.508.2100,23219-Feb-201010:20x86
Microsoft.solutions.btahl7.shared.dll3.7.508.287,94419-Feb-201010:20x86

For BizTalk Server 2006 R2 SP1

The hotfix that resolves this problem is included in cumulative update package 3 for BizTalk Server 2006 R2 SP1. 

For more information about how to obtain the cumulative update package, click the following article number to view the article in the Microsoft Knowledge Base: 
2286501 Cumulative update package 3 for BizTalk Server 2006 R2 Service Pack 1

For more information about BizTalk Server 2006 R2 SP1 hotfixes, click the following article number to view the article in the Microsoft Knowledge Base:
974563 List of Microsoft BizTalk Server hot fixes that are included in BizTalk Server 2006 R2 Service Pack 1
 

Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

References

For more information about how messages flow through BTAHL7, visit the following Microsoft Developer Network (MSDN) Web site:
How messages flow through BTAHL7
For more information about BizTalk Server hotfixes, click the following article number to view the article in the Microsoft Knowledge Base:
2003907 Information on BizTalk Server hot fixes

Properties

Article ID: 977120 - Last Review: June 21, 2014 - Revision: 3.0
Applies to
  • Microsoft BizTalk Server 2006 R2 Branch Edition
  • Microsoft BizTalk Server 2006 R2 Developer Edition
  • Microsoft BizTalk Server 2006 R2 Enterprise Edition
  • Microsoft BizTalk Server 2006 R2 Standard Edition
  • Microsoft BizTalk Accelerator for HL7 1.0 Enterprise Edition, when used with:
    • Microsoft BizTalk Server 2009 Developer
    • Microsoft BizTalk Server 2009 Enterprise
    • Microsoft BizTalk Server 2009 Standard
Keywords: 
kbbiztalk2009presp1fix kbbtsaccelerators kbbiztalk2006r2presp2fix kbexpertiseadvanced kbautohotfix kbsurveynew kbqfe KB977120

Give Feedback

 

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com