Frequently Asked Questions - IV. CAQH CORE Attachments Claims Infrastructure Rule Questions

What is the exchange method required for the CAQH CORE Attachments Claims Infrastructure Rule?

Submitted by tfuchs@caqh.org on Mon, 04/18/2022 - 12:19
What is the exchange method required for the CAQH CORE Attachments Claims Infrastructure Rule?

The only exchange method that is in-scope for this rule is CORE Connectivity vC4.0.0. CORE Connectivity vC4.0.0 supports HTTP, TLS 1.2 or higher, SOAP Version 1.2 or higher, WSDL Version 1.1 or higher, JavaScript Object Notation (JSON), X.509 Digital Certificate addressing authentication, and OAuth 2.0 or higher addressing authorization.

Back to Top
How does an entity determine which version of CAQH CORE Connectivity to use when implementing the CAQH CORE Attachments Claims Infrastructure Rule?

Submitted by tfuchs@caqh.org on Mon, 04/18/2022 - 12:48
How does an entity determine which version of CAQH CORE Connectivity to use when implementing the CAQH CORE Attachments Claims Infrastructure Rule?

Since February 2022, all CAQH CORE Infrastructure Operating Rules including CAQH CORE Attachments Claims Infrastructure Rule require use of the most current CAQH CORE published and adopted version of the CAQH CORE Connectivity Rule” (please see the CAQH CORE Connectivity web page to find the most recent published and adopted version of the CAQH CORE Connectivity Rule).

Back to Top
Why is CAQH CORE Connectivity Rule vC4.0.0 specified instead of the federally mandated version?

Submitted by tfuchs@caqh.org on Mon, 04/18/2022 - 12:49
Why is CAQH CORE Connectivity Rule vC4.0.0 specified instead of the federally mandated version?

The CAQH CORE Connectivity Rule vC4.0.0 includes requirements for the exchange of messages using both SOAP and REST. The CAQH CORE Connectivity Rule vC4.0.0 also includes support for the X12 v6020X316 275 attachments transaction in the scope of the rule, meaning that the rule applies when trading partners exchange the X12 v6020X316 275.

 

The rule also applies to other payload types (e.g., HL7 C-CDA, .pdf, .doc, etc.) and as such, serves as a bridge between administrative and clinical data exchange by utilizing both X12 and non-X12 payload types. Per the CAQH CORE Rule development process, published CAQH CORE Operating Rules may be presented to the National Committee on Vital Health Statistics (NCVHS) for federal mandate.

Back to Top
Do the CAQH CORE Attachments Claims Infrastructure Rules apply if a provider is only compliant with the federally mandated CORE Connectivity vC2.2.0?

Submitted by tfuchs@caqh.org on Mon, 04/18/2022 - 12:54
Do the CAQH CORE Attachments Claims Infrastructure Rules apply if a provider is only compliant with the federally mandated CORE Connectivity vC2.2.0?

No. Adoption of these rules is currently voluntary and as such can be used between willing trading partners.

Back to Top
What is the difference between the X12 method requirements and non-X12 requirements for system connectivity?

Submitted by tfuchs@caqh.org on Mon, 04/18/2022 - 12:55
What is the difference between the X12 method requirements and non-X12 requirements for system connectivity?

Both the X12 and non-X12 methods address usage patterns for Real Time and Batch Processing Modes, including the use of SOAP and REST. Both methods address the exchange of security identifiers, and communications-level errors and acknowledgements and do not attempt to define the specific content of the message payload beyond declaring the formats that must be used between entities and that security information must be sent outside of the message envelop payload. 

Back to Top
Do Batch and/or Real Time Processing Modes apply to the Attachments Claims Infrastructure Rule?

Submitted by tfuchs@caqh.org on Mon, 04/18/2022 - 12:55
Do Batch and/or Real Time Processing Modes apply to the Attachments Claims Infrastructure Rule?

Yes. Attachments sent to support Health Care Claim submissions require Batch Processing with optional support for Real Time Processing.

Back to Top
What are the differences between the X12 v5010 999 and X12 v6020 824?

Submitted by tfuchs@caqh.org on Mon, 04/18/2022 - 12:55
What are the differences between the X12 v5010 999 and X12 v6020 824?

The usage of X12 v6020 824 is independent from other X12 responses, such as the X12 v5010 278 Response and X12 v6020 999.

 

While the X12 v5010 999 returns an acknowledgement at the application layer (payload processing) of the OSI Model, the X12 v6020 824 provides error messages one layer deeper, at the data content level. X12 v5010 999 transaction is more widely used to return common errors and acceptance acknowledgements, while the X12 v6020 824 can provide more information on errors that delay adjudication (e.g., front end edits that can be used to inform the submitter that the transaction will fail adjudication at the next level of processing; for example, invalid patient ID).

Back to Top
How will X12 v6020 824 be used to communicate errors at the application level?

Submitted by tfuchs@caqh.org on Mon, 04/18/2022 - 12:56
How will X12 v6020 824 be used to communicate errors at the application level?

The X12 v6020 824 provides error messages at the data content level, which one layer deeper, than X12 v5010 999. The X12 v5010 999 returns an acknowledgement at the application layer (payload processing). The X12 v6020 824 can also provide more information on errors that delay adjudication (e.g., front end edits that can be used to inform the submitter that the transaction will fail adjudication at the next level of processing; for example, invalid patient ID).

Back to Top
What are the processing steps and need for an X12 999 functional acknowledgment (FA) in Real Time Processing Mode where the X12 275 payload is accepted without errors and the X12 824 response is subsequently sent?

Submitted by tfuchs@caqh.org on Mon, 04/18/2022 - 12:56
What are the processing steps and need for an X12 999 functional acknowledgment (FA) in Real Time Processing Mode where the X12 275 payload is accepted without errors and the X12 824 response is subsequently sent?

When an X12 6020X316 275 is submitted, it goes through several layers of error handling, from HTTP to Payload Processing Layer, to Initial Data Content Processing Layer.

If no errors are encountered at a layer, the submission is passed to the next processing layer. Upon passing the Payload Processing Layer, an X12 999 FA is sent to acknowledge acceptance. Once the Initial Data Content Processing Layer processes the content of the payload, the receiver (server) must return an X12 v6020X257 824 to report acceptance or any errors in the payload.

Back to Top
Is there a timing requirement on when an X12 999 response to an X12 v6020 824 must be sent?
Why was the CAQH CORE Master Companion Guide Template updated, which version is required for compliance with the CAQH CORE Attachments Claims Infrastructure Rule?

Submitted by tfuchs@caqh.org on Mon, 04/18/2022 - 12:57
Why was the CAQH CORE Master Companion Guide Template updated, which version is required for compliance with the CAQH CORE Attachments Claims Infrastructure Rule?

The CAQH CORE Master Companion Guide Template was updated to align with evolving needs of industry and newest published versions of the HIPAA-Mandated X12 standards. As such, the CAQH CORE Master Companion Guide template was updated to remove references to a specific version of the ASC X12 standard from the template. implementation of the CAQH CORE Master Companion Guide Template would be considered conformance with the CAQH CORE Attachments Claims Infrastructure Rule requirement Section 4., Companion Guide for X12 275 Attachments requirements.

Back to Top