Edit

Share via

ACK message modes

  • Article

For acknowledgment (ACK) messages, Microsoft BizTalk Accelerator for HL7 (BTAHL7) determines the acknowledgment mode and values to use for populating MSH15 and MSH16 fields of the ACK you want to generate. These values are present in the Trading Partner Management (TPM) configuration. The following values are possible for ACK mode:

Note

In the following list, the HL7 specification mandates items 1 through 3 and that they contain MSH15 and MSH16 values. BTAHL7 defines item 4 to signify that an acknowledgment should not be generated.

  1. Original - One ACK sent after validating the header and body. This mode involves schema validation.

  2. Enhanced - Two ACK messages sent:

    • Accept ACK – The receiving system sends this type of ACK after validation of the header. This ACK signals to the initiating application that the message is committed to the database.

    • Application ACK- The receiving system sends this type of ACK after complete message validation, including the header and the body.

  3. Deferred - Two ACK messages sent.

    • Original Mode: The receiving system sends this type of ACK after validation of the header and body. This mode involves schema validation.

    • Deferred Mode: The line-of-business application acknowledges the message after processing it. The application delivers the deferred message to BizTalk Server, which process it as a stand-alone message and delivers it to the destination.

  4. Static - An on success or on failure ACK sent.

See Also

Creating and Processing Acknowledgments Programming Guide ACK Process Model Static Acknowledgments