US Medical Billing

Claims attachment transaction

The HIPAA transaction for supporting documentation on a claim. It runs in both directions — a provider sending attachment information in support of a claim, and a plan requesting that information from a provider — and each direction is a transaction in its own right.

Updated

A health care claims attachments transaction is defined at 45 CFR 162.2001 as the transmission of either attachment information from a health care provider to a health plan in support of a health care claims or equivalent encounter transaction, or a request from a health plan to a health care provider for attachment information.

That two-directional definition is the structural point. The plan's request is not treated as a preliminary to the provider's transmission; it is a named transaction with its own adopted standard. 45 CFR 162.2002 adopts standards for both directions, pairing an X12 transaction that carries the envelope and the claim linkage with an HL7 clinical document standard that carries the content, and adopts a separate standard where the provider uses an electronic signature.

In practice

The attachment was the last major part of the claim for which HIPAA had adopted no standard, which is why supporting documentation has been a per-payer integration — a fax number, a portal upload, a proprietary form — rather than something a practice could build once. A standard changes that in principle, but only from the date the regulation names; until then the adopted standards do not apply and nothing about how a plan may ask, or how a practice may send, is fixed by them.

The practical consequence of the two-directional definition is that the payer's ask becomes a standard message rather than a letter or a portal task, which is the half most likely to change day-to-day work in a follow-up queue.

Commonly confused with

Sources

Ready to improve your revenue cycle?

Tell us about your practice and we’ll tell you where we would start.