G Configuration for Functional Acknowledgment 999

This appendix provides information about the configuration of Oracle SOA Suite for healthcare integration applications to use the document type 999 Functional Acknowledgment (FA).

This appendix has the following topics:

• Introduction

• Function Acknowledgement 999: Use Cases

G.1 Introduction

Oracle Fusion Middleware B2B supports document type 999 Functional Acknowledgment (FA), which is used mostly by HIPAA professionals.

By default, the document type configuration for FA is 997. However, you can override the default by specifying document type 999 as the FA. In addition, the document protocol version is not attached to the version of the incoming message, which means that you can send 999 v5010x231 for incoming message 837 v5010x223A1.

G.2 Function Acknowledgement 999: Use Cases

If you use X12 as the document protocol, the default Functional Acknowledgment document type is 997. In case of 997, the version for 997 Acknowledgment is the same as the version of the incoming message.

During design time in Oracle B2B console, you can override the default 997 FA or the version, or both in the Document Type Parameters page by using the following parameters:

• Functional Acknowledgment Transaction and

• Functional Acknowledgment Transaction Version

The rest of the configuration, such as Document Definition, Delivery Channel, and Trading Partner Agreement is the same as 997.

The following use cases discusses the configuration for FA 999 and 997:

• Use Case 1

• Use Case 2

• Use Case 3

G.2.1 Use Case 1

If you must use 999 as the FA but want to keep the version the same as the version of the incoming message, then you must set only the Functional Acknowledgment Transaction to 999 and leave the Functional Acknowledgment Transaction Version blank.

G.2.2 Use Case 2

If you must use 999 as the FA and also want to keep the version different from the version of the incoming message, then you must set both Functional Acknowledgment Transaction and Functional Acknowledgment Transaction Version parameters. For example, you must set Functional Acknowledgment Transaction to 999 and Functional Acknowledgment Transaction Version to 5010X231.

G.2.3 Use Case 3

If you must use 997 as the FA, but want to keep the version different from the version of the incoming message, you must set Functional Acknowledgment Transaction to 997 and Functional Acknowledgment Transaction Version to 5010. (assuming that the incoming message version is 4010). However, this use case is not very common.

Figure G-1 shows the configuration for Functional Acknowledgment Transaction and Functional Acknowledgment Transaction Version.

Figure G-1 Configuration for Functional Acknowledgment Transaction

Description of "Figure G-1 Configuration for Functional Acknowledgment Transaction"