An identifier that ties the attachment(s) back to the claim or prior authorization. This value is referred to as the "tracking control number"

In unsolicited claim attachments, the provider assigns the tracking control number on the claim and also on the submitted attachments for that claim for association. In solicited claim attachments, the payer assigns the tracking control number and sends it to the provider with the request for additional information for that specific claim. Similarly, for prior authorizations, the prior-auth tracking control number is provider assigned when the attachments are sent upon prior auth generation as unsolicited attachments, and the prior auth tracking control number is assigned and communicated by the payer when the attachments are in response to a request for additional documentation.

A value of either "claim" or "preauthorization" to communicate what the additional information is needed for. This is known by the provider when submitting unsolicited attachments and communicated to the provider through the request for solicited attachments.

The receiving payer identifier. It may be required, because the endpoint may support multiple payers. Currently, there is no standard way to obtain the payer identifiers and implementers will need to obtain them “out of band” when submitting unsolicited attachments. For solicited attachments this value is communicated to the provider through the request.

Sending organization/location identifier (e.g., Type 2 NPI). This is assumed to be known by the provider when submitting unsolicited attachments. For solicited attachments this value is communicated to the provider through the request. A ProviderId parameter or OrganizationId parameter or both SHALL be present.

Sending provider identifier (e.g.,Type 1 NPI). This is assumed to be known by the provider when submitting unsolicited attachments. For solicited attachments this value is communicated to the provider through the request. A ProviderId parameter or OrganizationId parameter or both SHALL be present.

Patient member identifier. This is assumed to be known by the provider when submitting unsolicited attachments. For solicited attachments this value is communicated to the provider through the request. This identifier can be either the Payer assigned Member ID or a provider assigned "Patient Account Number" for an unsolicited attachment for prior authorization.

Date of service or starting date of the service for the claim or prior authorization. This parameter SHALL be present and precise to the day if the attachment is for a claim. It is optional if the attachment is for prior authorization. This is assumed to be known by the provider when submitting unsolicited attachments. For solicited attachments this value is communicated to the provider through the request.

The attachments that are communicated for a claim or prior authorization. They are applied to the LineItem (line items) and/or Code (LOINC) parameters if present. If no LineItem is present, then the attachment is applied to the entire claim or prior authorization.

Claim/prior authorization line item for service in the claim or prior authorization. It may be present when submitting unsolicited attachments. For a solicited claim or claim authorization attachment, this value is the same as the line items communicated in the request.

LOINC code to identify the specific kind of information being communicated (e.g., a discharge summary or diagnostic imaging report). This value set includes LOINC terms that can be sent by a payer as part of an HL7 attachment request for additional information. It has been curated by the HL7 Payer/Provider Information Exchange (PIE) Work Group. More information about using LOINC in HIPAA attachments and the source of this value set can be found at https://loinc.org/attachments/. It SHOULD be present when submitting unsolicited attachments. For solicited attachments, this value is the same as the LOINC communicated when requesting attachments using attachments codes. When requesting attachments using Questionnaire, there is no code in the request and the code is typically not present in the response.

Attachment as a FHIR resource. Non-FHIR attachment data is conveyed using the DocumentReference or Binary resource. Servers SHALL support the DocumentReference resource type and SHOULD support other types. If Servers support requesting attachments with Questionnaire, then the SDC Questionnaire Response Profile SHALL be supported and the SDC Adaptive Questionnaire Response Profile SHOULD be supported.

Flag to indicate whether the operation is the last attachment submission (solicited or unsolicited) for the claim or prior authorization. If Final = "true", the Data Source has no more attachments to submit. This is the default meaning if this parameter is omitted. If Final = "false", the Data Source expects to submit more attachments in subsequent operations. Payers typically anticipate a single submission and may discourage multiple submissions.