Copyright © TIBCO Software Inc. All Rights Reserved
Copyright © TIBCO Software Inc. All Rights Reserved


Chapter 4 Configuring Protocol Features : CAQH Connectivity Rules

CAQH Connectivity Rules
TIBCO BusinessConnect EDI protocol powered by Instream supports CAQH connectivity rules, including Phase II (version 2.2.0) and Phase IV (version 4.0.0) of the CAQH connectivity rules.
There are 2 type of envelope specifications - HTTP MIME Multipart and SOAP + WSDL. Phase II (version 2.2.0) connectivity rules support both envelopes, but Phase IV (version 4.0.0) only support SOAP + WSDL envelope.
SOAP + WSDL Envelope
The SOAP +WSDL envelope feature combines both TIBCO BusinessConnect EDI protocol powered by Instream and TIBCO BusinessConnect SOAP protocol to handle CAQH requests and supports SOAP + WSDL format for CAQH.
CAQH Real-time Interaction
SOAP synchronize request-response and EDI synchronize request-response operations combine to support CAQH real-time interaction. The following is a sample shown in Figure 9.
Figure 9 CAQH Real-time Interaction
 
 
The following is the process flow:
For version 2.2.0, the CAQH message is packaged as SOAP body and for version 4.0.0, the CAQH message is package as a SOAP MTOM attachment.
SOAP operations that are used to exchange CAQH real-time transactions are pre-defined. You can find them in the CAQH samples of the SOAP protocol:
CAQH Batch Interaction
SOAP synchronize request-response and EDI notify operations combine to support CAQH batch interactions.
(A) Batch Submission Request
The process flow of a sample CAQH batch submission request is shown in Figure 10.
Figure 10 CAQH Batch Submission Request
The following is the process flow for a batch submission request:
(B) Batch Retrieval Request
The process flow of a sample CAQH batch retrieval request is shown in Figure 11.
Figure 11 CAQH Batch Retrieval Request
The following is the process flow for a batch retrieval request:
SOAP operations that are used to exchange CAQH batch transactions are pre-defined. You can find them in the CAQH samples of the SOAP protocol:
HTTP MIME Multipart Envelope
This envelope feature uses only TIBCO BusinessConnect EDI protocol powered by Instream to transmit CAQH requests over HTTP/HTTPS transport. HTTP MIME Multipart envelope is defined based on HTTP transport, so you need to configure HTTP or HTTPS transport for trading partner and then specify HTTP/HTTPS transport as the primary transport in Business Agreement before you use HTTP MIME Multipart envelope to exchange CAQH message with your trading partner.
TIBCO BusinessConnect EDI protocol powered by Instream will decide whether the outbound CAQH message is packaged with HTTP MIME Multipart envelope or SOAP + WSDL envelope by identifying the query string provided in the outbound HTTP/HTTPS transport URL.
The query string takes the form:
package = x12-caqh-mime
For example:
server1.company.example.com:6700/X12?package=x12- caqh-mime
CAQH Real-time Interaction
The process flow of a sample real-time interaction request is shown in Figure 12.
Figure 12 CAQH Real-time Interaction
CAQH Batch Interaction
(A) Batch Submission Request
The process flow of a sample CAQH batch submission request is shown in Figure 13.
Figure 13 Batch Submission Request
(B) Batch Retrieval Request
The process flow of a sample CAQH batch retrieval request is shown in Figure 14.
Figure 14 Batch Retrieval Request
 

Copyright © TIBCO Software Inc. All Rights Reserved
Copyright © TIBCO Software Inc. All Rights Reserved