NOTE: Providers are not required to include the reference data listed in the rule but are encouraged to include all data elements that are readily available. Additionally, the lists of data elements in the rules are not prohibitive or exhaustive.
Frequently Asked Questions - V. CAQH CORE Attachments Claims Data Content Rule Questions
- How was the list of common reference data for reassociating an X12 275 and an X12 837 developed?
- If a provider does not send all data elements listed in the CAQH CORE Attachments Claims Data Content Rules to assist with reassociation, can the health plan request that the provider send the data elements listed in the rule?
- Will an ‘Auth # ID’ be required at the time the X12 275 attachment or additional documentation is sent?
- Do the CORE-required Minimum Data Elements specified in the non-X12 method section of the CAQH CORE Attachments Claims Data Content Rules need to correspond to X12 data elements?
- 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 Claims Data Content Rules required if the information is not available to the provider?
- If an entity has an internal management system that is not used for attachments, is it still subject to the 64 MB size minimum?
- Can multiple attachments be sent within a single instance of the X12 v6020 275 transaction?
- Does the requirement that entities must support a minimum of 64MB apply to the transaction or per loop?
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.
No. The CORE-required Minimum Data Elements regarding labels and descriptions indicate that the data could be originating within the provider’s system or the payer’s system. As such, if an Auth ID is not available when the attachment is sent, it is not required.
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.
No. If the information is not available, it is not required.
No. If an entity’s internal document management system is not used for holding and processing attachments, it is not subject to the 64 MB minimum size requirement.
Yes. Multiple attachments can be sent within a single X12 v6020 275.
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.