本文介绍了如何确保BTAHL7 ACK消息的消息控件ID与原始消息相同的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我们有一个要求,即HL7 ACK消息的消息控制ID(MSH.10)应该等于原始消息的消息控制ID(MSH.10).我们将BTAHL7与BizTalk 2013 R2,CU5一起使用.在目前的情况下,ACK的消息控件ID实际上是原始消息的消息控件ID的排列.任何帮助,将不胜感激.

We have a requirement that the Message Control Id (MSH.10) of the HL7 ACK message should be equal to the message control id (MSH.10) of the original message. We are using BTAHL7 with BizTalk 2013 R2, CU5. In our case at present, the message control id of ACK is actually a permutation of the original message's message control id. Any help would be appreciated.

推荐答案

正确答案:甚至不要尝试.这不是标准的HL7.

The correct answer: don't even try. This is not standard HL7.

参考值符合HL7的MSA02.

The ref value is in MSA02 per HL7.

这不是HL7或BizTalk Server的问题.这是您的贸易伙伴创建的问题.

This is not a problem with HL7 or BizTalk Server. This is a problem created by your Trading Partner.

如果这是由贸易合作伙伴推动的,则第一个响应就是否" ,因为这不是标准的HL7.

If this is being pushed by a Trading Partner, the first response is simply NO, because this is not standard HL7.

如果他们继续努力,那么下一步就是通知您的管理层,因为贸易伙伴要求使用非标准的HL7,因此您将需要很多额外的时间和金钱来.您将需要一个完全自定义的编号方案.

If they keep pushing this, your next step is to inform your management that because the Trading Partner is requiring non standard HL7, it will take you a lot of extra time and money to support this. You will need a completely custom numbering scheme.

这篇关于如何确保BTAHL7 ACK消息的消息控件ID与原始消息相同的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持!

09-06 04:07