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).
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."
No. CAQH CORE does not provide negotiation assistance between trading partners. CAQH CORE does provide implementation resources and education events and will clarify the rules if there are questions.
The CAQH CORE Connectivity Rule does not specify a method for capturing and logging data. The rule only specifies what data must be captured and logged. The method for how to capture and log is determined by the implementer.
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.”
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.
Please submit your request to CAQH CORE. Your request will be considered by the CORE membership for inclusion in a future version of CAQH CORE operating rules
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.
Client Certificates may be issued by a trusted third party called a Certificate Authority (CA) such as VeriSign or Entrust, or by the entity that is receiving connections.
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.