Does the requirement that entities must support a minimum of 64MB apply to the transaction or per loop?

The requirement to support a minimum of 64MB applies to the entire content of the BDS segment of the X12 v6020 275, not per loop. Please note, this requirement is only a floor, not a ceiling, meaning that organizations can choose to accept more than 64MB of data. Organizations must accept a minimum of 64MB.

Are all the data elements included in the CORE-require Minimum Data Elements specified in the non-X12 method section of the CAQH CORE Attachments Prior Authorization Data Content Rules required if the information is not available to the provider?

Do the CORE-required Minimum Data Elements specified in the non-X12 method section of the CAQH CORE Attachments Prior Authorization Data Content Rules need to correspond to X12 data elements?

No. The data does not need to conform to X12 data element naming conventions and as such, do not need to correspond to those X12 data elements as it is not an X12 transaction.

If a provider does not send all data elements listed in the CAQH CORE Attachments Prior Authorization Data Content Rule to assist with reassociation, can the health plan request that the provider send the data elements listed in the rule?

No. The list of data elements is recommended to assist with reassociation. The data elements should only be sent, if available, to the provider at the time of submissions. The lists of data elements in the rules are not prohibitive or exhaustive.

How was the list of common reference data for reassociating an X12 275 and an X12 278?

The common reference data lists represent commonly available data that, after several reviews, the Attachments Advisory Group and Attachments Subgroup participants (including providers, health plans, and vendors) ranked most useful in assisting document management systems with reassociation of an attachment to its original prior authorization request.