HL7加速器错误:未找到架构(升级到BizTalk 2013后)

时间:2013-11-08 22:51:10

标签: biztalk btahl7 hl7-v2 biztalk-2013

在开发计算机上,我们将BizTalk 2010服务器升级到BizTalk 2013.我们正在从另一台计算机发送HL72垃圾邮件到此处并找到未找到架构的错误:

备用错误号码:301  备用错误说明:未找到架构http://microsoft.com/HealthCare/HL7/2X#ORU_R01_23_GLO_DEF  替代编码系统:HL7-BTA

该消息指定“LAB”作为发送应用程序,我们有一个名为“LAB”的方指定“http://mycompany/myapplication/HL7/2X/2.3/ORU/v1”作为模式名称空间,因此我们无法弄清楚它为什么要查找ORU 默认的microsoft 命名空间中的R01 2.3模式。

enter image description here

我们的信息如下:

MSH|^~\&|LAB|ABC|LAB||201311071138||ORU^R01|D2863329|D|2.3|
PID|1|A00003766|XX00014202|9191610101|Ihhendrickson^Plis||19691202|M|||8423 Panko Pvt^^Here^BC^XXX XXX||111-1111|||||xx0055355x3|9x9x6x0x0x|
PV1|1|R|TRAKBHLB||||93190^Plisihd^xxxxxx^^^Dr^^xxxxxx|||||||||||RCR||BC|||||||||||||||||||xxxxx||REG|||201207261453|
ORC|RE|PT80755100.0010|||CM|N|||201311071138|^xxxxxx^Linda^^^^^xxxx||93190^xxxx^Aaron^^^Dr^^xxxx|xxx|
OBR|1|PT0711:T00001R100.0010|PT0711:T00001R|100.0010^Group \T\ Screen^00050252^34532-2^Blood Type \T\ Indirect Antibody Screen^pCLOCD|R|201311071004|201311071004|||G|||PLIS Testing|201311071004|T|93190^Plisihd^xxx^^^Dr^^Pxxxxx||00050252|||xxx|201311071004||BBK|F|||93190^xxx^Aaron^^^Dr^^xxxx|
NTE|1||Date required: 20131107|
NTE|2||Any previous transfusions? Unknown|
NTE|3||Specify any underlying blood disorders: U|
NTE|4||Has consent for blood products been obtained? Yes|
OBX|1|ST|150.0100^Patient Blood Group^00050252^882-1^Blood Type \T\ Indirect Antibody Screen^pCLOCD||OPOS^O Rh Pos|||||A~S|F|||201311071137|xx^xx^L|IH001^^Blood Group^Patient Blood Group^150.0100|
OBX|2|ST|200.0100^Ab Screen Gel^00050252^XBC1931-6^Blood Type \T\ Indirect Antibody Screen^pCLOCD||NEGATIVE^NEGATIVE|||||A~S|F|||201311071138|xx^xx^L|IH001^^Ab Scr Gel^Antibody Screen Gel^200.0100|
ZDR||xxx^xxxx^Aaron^^^Dr^^^^^^^^^ATP|
ZPR||

任何人都有我们应该尝试的想法吗?

2 个答案:

答案 0 :(得分:1)

对于发送端口,HL7 2.X汇编程序组件应为use the MSH 5 field value to determine the party to use。发送端口上的管道配置应该有一个选项来启用部分名称解析(EnablePartialNameResolutionForReceivingApplication),这在启用时可能有所帮助。

在接收位置,HL7 2X反汇编程序组件should use MSH 3 for party resolution。接收位置的BTAHL72XReceivePipeline配置包含名为EnablePartialNameResolutionForSendingApplicationEnablePartialNameResolutionForReceivingApplication的设置,供您开启。

旧版本的BizTalk需要a hotfix才能使这些设置正常工作,但这不再是必需的。在该页面中,设置说明如下:

对于发送管道,BTAHL7 2.X汇编程序包含以下属性:

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. 

对于接收管道,BTAHL7 2.X反汇编程序包含以下属性:

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.

如果这没有帮助,那么还有一件事只能尝试发送端口:在聚会配置中,尝试将聚会分配给您的发送端口,如步骤3 here中所述。这是试图强迫它使用正确派对的一种方法。但是,这对接收地点没有帮助。

答案 1 :(得分:1)