This page is part of the Da Vinci Clinical Documentation Exchange (v1.1.0: STU1.1) based on FHIR R4. This is the current published version in its permanent home (it will always be available at this URL). For a full list of available versions, see the Directory of published versions
The following page is DRAFT. It has not yet undergone HL7 balloting.
Currently claims typically come through X12 transactions or portal submissions. Payers may need additional information from a Provider to determine if the service being billed (claim) or requested (prior authorization) is supported by medical benefits or by policy benefits. In this guide, the use of the term “attachments” is limited to a subset of additional information which are defined by the LOINC Document Ontology and data elements presented in document form. Attachments for claims or prior authorization can be divided into solicited and unsolicited workflows. The sections below document the differences and similarities between these workflows and the CDex transactions that can be used for each.
For an unsolicited attachment the Provider will submit additional documentation to support a claim or prior authorization based on Payer predefined rules without any type of request. The attachments may be submitted before, at the same time as, or after the claim or pre-authorization has been supplied to the Payer. Following submission, the attachment is then associated with the claim or prior authorization.
In all of these cases, the Payer will require a trading partner agreement for sending attachments based on predefined rules.
The flow diagram for this transaction is shown in the figure below:
See the Sending Attachments page for how CDex transactions can be used to support unsolicited attachment transactions.
For a solicited attachment the Provider will submit additional documentation, to support a claim or prior authorization, in response to a Payer’s request for additional documentation. The submitted attachments are then associated with the claim or prior authorization. The flow diagram for this transaction is shown in the figures below:
Attachments may be requested via a non-CDex-FHIR-based request such as an X12 transaction, fax, portal, or other platform or they may be requested using CDex. See the Requesting Attachments page and Sending Attachments page for how CDex transactions can be used to support solicited attachment transactions.