1. Per Section 3.3, the CAQH CORE Payment & Remittance (835) Uniform Use of CARCs and RARCs Rule applies when entities process the X12 v5010 835 in either real time or batch. Does this requirement mean that the CAQH CORE Payment & Remittance (835) Unifo

No. Per Section 3.3, When the Rule Applies, of the CAQH CORE Payment & Remittance (835) Uniform Use of CARCs and RARCs Rule, the rule applies when an entity uses, conducts, or processes the X12 v5010 835, either in real time or batch processing mode.

2. The CAQH CORE Payment & Remittance (835) Infrastructure Rule requires health plans to support the CAQH CORE Connectivity Rule vC.2.2.0 to transmit the X12 v5010 835. Our organization is a health plan that currently limits the size of the batch X12 v5

No. Section 4.1, Health Care Claim Payment/Advice Connectivity Requirements, of the CAQH CORE Payment & Remittance (835) Infrastructure Rule requires all health plans to support use of the CAQH CORE Connectivity Safe Harbor described in the CAQH CORE Connectivity Rule vC2.2.0 to transmit the X12 v5010 835.

3. CAQH CORE Payment & Remittance (835) Infrastructure Rule requires health plans to support the CAQH CORE Connectivity Rule vC2.2.0 to transmit the X12 v5010 835. Our organization is a health plan that currently transmits several X12 v5010 835 transact

No. Section 4.1, Health Care Claim Payment/Advice Connectivity Requirements, of the CAQH CORE Payment & Remittance (835) Infrastructure Rule requires all health plans to support use of the CAQH CORE Connectivity Safe Harbor described in the CAQH CORE Connectivity Rule vC2.2.0 to transmit the X12 v5010 835.

5. The CAQH CORE Payment & Remittance (835) Infrastructure Rule requires entities to support the requirements for batch processing of the X12 v5010 835 specified in the CAQH CORE Connectivity Rule vC2.2.0. In Section 4.2.2.1 of the CAQH CORE Connectivit

Yes. Section 4.2.2.1, CORE Connectivity XML Schema Specification (normative), of CAQH CORE Connectivity Rule vC2.2.0 specifies a value of minOccurs=”0” for the Payload element because the Batch Results Retrieval Request does not always require a payload (e.g., if there is no batch available for retrieval).

7. Section 4.1 of the CAQH CORE Payment & Remittance (835) Infrastructure Rule requires entities to support the CAQH CORE Connectivity Rule vC2.2.0 to send/receive the X12 v5010 835. CAQH CORE Connectivity requires health plans and clearinghouses to pub

Connectivity Companion Guides are entity-specific guides that outline the requirements to establish and maintain a connection with the entity.

9. If a submitter’s transaction real time response is not received from a receiver, can the submitter’s transaction be excluded from the submitter’s response time reporting as a failed transaction caused by external problems?

No, all transactions should be recorded for response time tracking. Failed transactions due to external timeouts should be reported and investigated with external trading partners.

Subscribe to III. CAQH CORE Connectivity Rule vC3.1.0