N TA1 Acknowledgment
This appendix discusses the TA1 acknowledgment feature of Oracle B2B.
HIPAA messages are used for information exchange. HIPAA messages are required to send the Interchange Acknowledgment (TA1).
The appendix contains the following sections:
N.1 Introduction
There are many kind of acknowledgments for a HIPAA document that are exchanged between initiator and responder.
When an initiator sends a message, following are the different types of the acknowledgments in the order of precedence:
-
TA1 – Interchange level acknowledgment
-
997/999– Functional acknowledgment (999 for 5010 versions and above)
The message flow is completed when TA1 or 997/ 999 is sent for inbound business message as shown in Figure N-1.
Note:
TA1 documents are available as a preseeded ZIP file in Oracle B2B.
Figure N-2 displays a sample TA1 document definition.
Figure N-2 A Sample TA1 Document Definition

Description of "Figure N-2 A Sample TA1 Document Definition"
Figure N-3 displays a sample TA1 agreement.
N.2 Configuring TA1
You can configure Oracle B2B to use TA1 both for the inbound and the outbound message directions.
N.2.1 TA1 for Inbound Direction
For inbound messages, EDI position ISA14 Payload value of 0
or 1
determines whether Oracle B2B should send a TA1 acknowledgment. If the value is 1
, then the Interchange is checked and TA1 is sent to the trading partner.