1. How does an entity determine which version of CAQH CORE Connectivity to use when implementing a set of CAQH CORE Operating Rules?

All CAQH CORE Infrastructure Operating Rules require use of “most recent published and CAQH CORE adopted version of the CAQH CORE Connectivity Rule” (please see the CAQH CORE Connectivity webpage for more information).  

2. Does “client” refer to a workstation or human user, i.e., can a client be an internal workstation or a web browser requesting a webpage from an Internet web server?

The CAQH CORE Connectivity Rules apply to Business to Business (B2B) transactions. The term “Client” refers to software that is initiating, submitting/sending a request to a receiving “Server." 

5. Do the CAQH CORE Connectivity Rules require the use of the MAC address?

Yes. The field constraints or value-sets for PayloadID are specified in Section 4.4.2, Table of CORE Envelope Metadata of each CORE Connectivity Rule. Specifically, the requirement specifies “PayloadID will conform to ISO UUID standards (described at ftp://ftp.rfc-editor.org/in-notes/rfc4122.txt), with hexadecimal notation, generated using a combination of local timestamp (in milliseconds) and the hardware (MAC) address, to ensure uniqueness.”

6. The Entity-Specific Connectivity Guide states that details of the message format and supported transactions, such as returning a list of files to be picked up for batch transactions, can be specified in a Connectivity Companion Guide. Does this mean t

No. By design, the CAQH CORE Connectivity Rules are highly prescriptive in the envelope metadata and message interactions because the CORE Participants need a Connectivity Rule that provides a high degree of interoperability. Entities may implement custom extensions which must be described in a Companion Guide, but such extensions are not compliant with the CAQH CORE Connectivity Rules’ normative specifications (i.e., XSD, WSDL) and are therefore considered as non-CAQH CORE connectivity interfaces.

8. Are there any guidelines/restrictions on the use of specific certificate authorities?

CAQH CORE has not specified guidelines/restrictions on the use of certificate authorities at this time. Client certificates used for node authentication over SSL can be issued by the organization that is receiving connections, or by a third-party certificate authority that is trusted by the organization to issue these certificates on its behalf.

10. What are my SenderID and ReceiverID values? Where can I obtain them?

SenderID and ReceiverID Values are unique identifiers associated with your organization. They are intended for message routing and processing, transaction auditing and as a reference to a business agreement by a message receiver. CAQH CORE recommends using OIDs from organizations like HL7 or IANA, but you may use other forms of organizational identifiers.