Static Acknowledgments
BizTalk Accelerator for HL7 (BTAHL7) supports original, enhanced, deferred, and static acknowledgment (ACK) modes. If you select static ACK mode for a party in BTAHL7 Configuration Explorer, BTAHL7 will generate static ACKs that contain only an indication of success or failure. The static ACK indicates whether the receiving system received and processed the message, in success and failure values configured in BTAHL7 Configuration Explorer.
In original, enhanced, and deferred modes, BTAHL7 generates dynamic ACKs. They are HL7-encoded, and contain fields such as the MSA.1 Acknowledgment Code field and the ERR segment. The MSA.1 field of a dynamic ACK will indicate whether a failure condition is a Reject or an Error, which result in different processing (see Message Acknowledgment Segment). The ERR segment provides detailed information about the error. Static ACKs provide no such information.
BTAHL7 processes a static ACK differently from a dynamic ACK. If a two-way send port (which will only send the next message after receiving the ACK) receives the static ACK, and the ACK indicates failure (or is not a valid ACK), BTAHL7 will move to the secondary transport or suspend the message. It will not retry the message, as it would if it received a dynamic ACK, depending upon the failure condition.
When the BTAHL7 parser processes a static ACK, it writes the IsStaticAck Boolean property to the message context. The serializer uses this value to determine whether it should process the message as a static ACK.
See Also
Creating and Processing Acknowledgments
Message Acknowledgment Segment