CAQH CORE HTTP/S (250: Claim Status Infrastructure Rule) Connectivity
CAQH CORE HTTP/S is secure and reliable enough to protect the delivery of healthcare information over the Internet. In Phase I development discussions, CAQH CORE solicited input on this topic from its Technical Work Group members and experts within healthcare and other industries, such as financial services. Based on this input, including the information that other healthcare industry projects are using HTTP/S over the Internet, CAQH CORE determined that HTTP/S is an appropriate choice as the baseline standard for delivery of healthcare information.
Payers may support other versions, but they must support HTTPS 1.1 in order to achieve CORE Certification. The intent of CAQH CORE 270: Connectivity Rule Version 2.2.0, which applies to the conduct of this Phase II CAQH CORE Claim Status Rule, is to provide a safe harbor that application vendors can develop towards without needing to get detailed information from every potential payer with whom they would like to connect.
Is there a required format in Phase I CAQH CORE Connectivity for the authorization, date/time, and payload ID to be sent in the HTTP message? CAQH CORE decided not to require a format for these data elements for Phase I. However, in Phase II CAQH CORE and future phases, CAQH CORE does require a specific format for sending these data elements. Please speak with your CAQH CORE-authorized testing vendor on how they will work with you on CORE Certification testing given your organization’s current HTTP format requirements and those used by the CAQH CORE-authorized testing vendor.
SOAP 1.2 implementation approach
The conformance guidelines for different stakeholder types for implementing the two envelope standards (SOAP 1.2 and HTTP+MIME Multipart) defined in CAQH CORE 270: Connectivity Rule Version 2.2.0 are provided in the rule. SOAP 1.2 is one of the two supported envelope standards, and needs to be implemented over HTTP/S 1.1. The use of attachments is applicable to Batch processing, and is not applicable to Real time processing. Further, the intent of CAQH CORE 270: Connectivity Rule Version 2.2.0 is to provide a safe harbor that application vendors can develop towards without needing to get detailed information from every potential payer with whom they would like to connect.