Introduction

This article describes a hotfix that lets Microsoft BizTalk Server 2010 Accelerator for HL7 (BTAHL7) support HL7 Version 2.5.1 (v2.5.1) message processing.

This hotfix contains schemas, and it updates engine files that are used by BTAHL7 to validate, parse, and serialize events for HL7 v2.5.1 message processing.

Additionally, this hotfix resolves several issues for HL7 message processing that are described in the "More Information" section.

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:

http://support.microsoft.com/contactus/?ws=supportNote 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

To apply this hotfix, you must have BTAHL7 installed, and you must apply the hotfix that is described in the following Microsoft Knowledge Base article:

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

Restart requirement

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

Hotfix replacement information

This hotfix does not replace any other hotfixes.

File information

The global 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 Server 2010 Accelerator for HL7

File name

File version

File size

Date

Time

Platform

Microsoft.solutions.btahl7.ddvhelper.dll

3.9.546.2

18,792

01-Mar-2012

10:52

x86

Microsoft.solutions.btahl7.hl72fdasm.dll

3.9.546.2

102,760

01-Mar-2012

10:52

x86

Microsoft.solutions.btahl7.hl7wizard.dll

3.9.546.2

61,800

01-Mar-2012

10:52

x86

Microsoft.solutions.btahl7.mllp.dll

3.9.546.2

123,232

01-Mar-2012

10:52

x86

Microsoft.solutions.btahl7.pipelinecommon.dll

3.9.546.2

90,488

01-Mar-2012

10:52

x86

Microsoft.solutions.btahl7.pipelinemessagecore.dll

3.9.546.2

86,400

01-Mar-2012

10:52

x86

Microsoft.solutions.btahl7.shared.dll

3.9.546.2

94,568

01-Mar-2012

10:52

x86

More Information

Issue 1


When you try to use BTAHL7 to receive and to process an HL7 v2.5.1 message, the parsing stage fails, and you receive an error message that resembles the following:

Event Type: Error
Event Source: BizTalk Accelerator for HL7
Event Category: None
Event ID: 4100
Date: <Date>
Time: <Time>
User: N/A
Computer: <Computer>
Description:
Validation error in header during parsing
Error # 1
Segment Id: MSH
Sequence Number: 1
Field Number: 7
Error Number: 102
Error Description: Data type error
Encoding System: HL7nnnn


Note This issue is caused by the MSH 7 Date/Time of Message field. This field contains a DateTime data type value. However, this value is generated incorrectly as a String data type value.

Issue 2
Slow performance occurs when you process HL7 messages on a receive location that uses the Minimal Lower Layer Protocol (MLLP) adapter.

After you apply this hotfix, a new "Use Direct Synchronous HL7 ACK" setting is available in the MLLP Transport Properties configuration page. The setting improves performance in a Two Way receive port & location if the following conditions are true:

  1. The receive port is a two-way receive port, and the "Use Direct Synchronous HL7 ACK" option is set to "True" in the MLLP Receive port configuration.

    Note If the receive port is a one-way port and this option is enabled, there is no performance improvement.

  2. BizTalk HL7 DASM is used to generate the ACK.

    Note You can achieve this by using the default BTAHL72XReceivePipeline or the BTAHHL7.HL72fDasm that is included with BizTalk HL7 Accelerator.

    The “Route ACK to Send pipeline on request-response receive port” setting of the Source party must be in the HL7 Configuration explorer, and the Acknowledgement Type must be set to a value that is not "None."

    Be aware that in the other scenarios where the ACK is not generated by the BizTalk HL7 DASM (for example, the ACK is given by the downstream system and is given to the send adapter which in turn is submitted to EPM, and which in turn is routed to the receive port and also to the upstream system or another disassembler is used) there is no performance improvement. The HL7 ACK will still be routed back to the upstream system successfully.

    This change enables BizTalk to receive more messages. This expedes processing on the send side for send ports that are subscribed to the receive port. Also, when the "Use Direct Synchronous HL7 ACK" option is changed, you must restart the host instance to see the behavior change by using the "BizTalk:Messaging:Documents received/Sec" Performance Monitor Counter.

Issue 3
Additional support for the following acknowledgement codes is enabled on two-way MLLP send ports.

  • AE

  • AR

  • CR

  • CE



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

973909 FIX: Event IDs 5812, 5743, and 5754 are logged when you use BizTalk 2009 Accelerator for HL7 (BTAHL7)

Issue 4
When you change the XPN_0_0Surname field in the ORU^R01 schema, and then you use the schema to submit a message that does not contain a value in the PID_6 field, you receive a validation error message.

When you change the value of the minOccurs attribute from 0 to 1 for the PID_6 and XPN_0_0_Surname fields in the ORU^R01 schema, you expect the following behavior to occur:

  • If an ORU_R01 incoming message does not have a value in the PID_6 field, the message is valid.

  • If an ORU_R01 incoming message has a value in any of the PID_6 subfields, and the XPN_0_0_Surname field is present, the message is valid.

  • If an ORU_R01 incoming message has a value in any of the PID_6 subfields, and the ORU_R01 incoming message has no value in the XPN_0_0_Surname field, the message is not valid.

Note This expected behavior meets federal guidelines.

Issue 5
ACK processing fails because of a mismatch between the MessageType schema, the DocSpecType schema, and the SchemaStrongName schema. When this issue occurs, an error that resembles the following is logged in the xlang/s engine event log:

Uncaught exception (see the 'inner exception' below) has suspended an instance of service'<Service Instance Name>' .
The service instance will remain suspended until administratively resumed or terminated.
If resumed the instance will continue from its last persisted state and may re-throw the same unexpected exception.
InstanceId: <Instance ID>
Shape name:
ShapeId:
Exception thrown from: segment -1, progress -1
Inner exception: Received unexpected message type '<Message Type>, BTAHL7V2XCommon, Version=1.0.0.0, Culture=neutral, PublicKeyToken=6f98b98dc03f2db5' does not match expected type '<Message Type>, BTAHL7V2XCommon, Version=1.0.0.0, Culture=neutral, PublicKeyToken=6f98b98dc03f2db5'.

Exception type: UnexpectedMessageTypeException
Source: Microsoft.XLANGs.Engine
Target Site: Void _verifyPublisherSchema()

Issue 6
The value of the minOccurs attribute is changed from 0 to 1 in the following schemas to meet federal guidelines:

<xs:complexType name="EI">
<xs:element minOccurs="0" name="EI_2_UniversalId" type="ST_L199" />
<xs:element minOccurs="0" name="EI_3_UniversalIdType" type="ID_301" />



<xs:complexType name="CX">
<xs:element minOccurs="0" name="CX_3_AssigningAuthority">
<xs:element minOccurs="0" name="CX_4_IdentifierTypeCode" type="ID_203" />

Issue 7
This hotfix enables the Minimal Lower Layer Protocol (MLLP) adapters to handle multiple connections to same MLLP port.

Post-installation instructions

After you install this hotfix, follow these steps:

  1. On the Resources tab of the application in the BizTalk Server Administration Console, delete BTAHL7 V2X Common Project.

    Note If the project was deployed, you have to undeploy the project before you do this.

  2. Start Microsoft Visual Studio, click new BizTalk project, click BTAHL7 V2X Common project, and then open BTAHL7 V2X Common project.

  3. On the Resources tab of the application in the BizTalk Server Administration Console, delete BTAHL7 V251 Common Project.

    Note If the project was deployed, you have to undeploy the project before you do this.

  4. Start Microsoft Visual Studio, click New BizTalk project, and then click BTAHL7 V251 Common project.

  5. Open the Datatypes_251.xsd file, and then change the value of the minOccurs attribute in the following code from 0 to 1:

    <xs: element minOccurs="0" name="XPN_0_0_Surname" type="ST_0" />
  6. Redeploy the BTAHL7 V251 Common project.

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 HL7 v2 messaging standards, go to the following Health Level Seven website:

General information about HL7 v2 messaging standardsFor more information about the HL7 v2.x versions that are supported by BTAHL7, go to the following Microsoft website:

General information about supported HL7 2.x versionsFor information about service packs and cumulative updates for BizTalk Server, click the following article number to view the article in the Microsoft Knowledge Base:

2555976 Service pack and cumulative update list for BizTalk Server
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

ヘルプを表示

スキルを磨く
トレーニングの探索
新機能を最初に入手
Microsoft Insider に参加する

この情報は役に立ちましたか?

どのような要因がお客様の操作性に影響しましたか?

フィードバックをお送りいただきありがとうございます!

×