Sign in with Microsoft
Sign in or create an account.
Select a different account.
You have multiple accounts
Choose the account you want to sign in with.


This article describes a hotfix that allows for parsing of HL7 messages that have versions later than 2.5.1 in Microsoft BizTalk Server 2010 Accelerator for HL7 (BTAHL7). This parsing occurs after you deploy the correct schema for the messages.

More Information

Hotfix information

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

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, submit a request to 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 website: 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.

Post-installation instructions

After you apply this hotfix, you should validate the HL7 messages. To do this, add the HL7 version number to Table 104 in the MSH_25_GLO_DEF.xsd file. For example, add the following element to Table 104:

<xs:enumeration value="2.7" />


  • Table 104 is the version ID that maps to a specific field in an HL7 message.

  • If the BTAHL7V2XCommon project that contains the MSH_25_GLO_DEF.xsd file is already deployed, you have to undeploy the project before you take the step that is described in this section. Then, redeploy the project after the step is completed.


You must have BTAHL7 installed. Additionally, you must apply the hotfixes that are described in the following Microsoft Knowledge Base (KB) articles:

2564013 FIX: A hotfix is available that provides additional Delivery Mode properties for the Minimal Lower Layer Protocol send and receive adapters in BizTalk Accelerator for HL7 in a BizTalk Server 2010 environment

2607536 FIX: Hotfix adds support to HL7 v2.5.1 message processing and fixes several issues in BizTalk Server 2010 Accelerator for HL7

Restart requirement

After you apply this hotfix, you do not have to restart the computer. However, you must restart the BizTalk services.

Hotfix replacement information

This hotfix does not replace a previously released hotfix.

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.

File name

File version

File size

























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

More Information

For more information about BizTalk Server hotfixes, click the following article number to view the article in the Microsoft Knowledge Base:

2003907 Information about BizTalk hotfixes and service pack support

Need more help?

Want more options?

Explore subscription benefits, browse training courses, learn how to secure your device, and more.

Communities help you ask and answer questions, give feedback, and hear from experts with rich knowledge.

Was this information helpful?

What affected your experience?
By pressing submit, your feedback will be used to improve Microsoft products and services. Your IT admin will be able to collect this data. Privacy Statement.

Thank you for your feedback!