1. How should the X12 270/271 transactions be tracked throughout a system/application to demonstrate conformance with the response time requirements specified in the CAQH CORE 155 Rule?

The CAQH CORE Response Time Rules (CAQH CORE 155 & 156 Rules) require HIPAA covered entities to capture, log, audit, match, and report the date, time, and control numbers from their own internal systems, and corresponding data received from their trading partners. The auditing requirement is included so that each entity will have the log of data to be used to resolve any issues or concerns.

2. Do the time frames still apply if it is an especially large batch? Do the CAQH CORE Rules define the batch size?

The CAQH CORE 155 Rule does not define batch size. Section 6 of the CAQH CORE 270: Connectivity Rule Version 2.2.0 defines a large batch file (payload) as "A single submission of a message payload that contains more than one X12 Interchange, each of which may contain one or more Functional Groups, each of which may contain one or more X12 transaction sets."

3. If an X12 270 is received in a batch, does the X12 271 have to be returned in a batch?

The CAQH CORE Rule does not address this issue. The batch response time rule only requires that a health plan have the batch of responses available by 7:00 AM the next business day following a submission of inquiries by 9:00 PM ET the previous business day. Therefore, the CAQH CORE 155 Rule does not specify whether or not the batch of X12 271 responses must match exactly the batch of X12 270 inquiries.

4. The maximum response time for the availability of the ASC X12 Implementation Acknowledgement (999) is one hour as specified in CAQH CORE 155: Batch Response Time Rule. What is the maximum response time for HTTP message after a file is dropped off?