Overview

The Clinical Data Exchange (CDEx) Attachment Submission API allows providers, provider organizations, and trading partners to submit supporting clinical documentation for prior authorization or claim-review requests.

Parameters

ParameterDescription
parameter >> nameThis identifies the business parameter being sent. Select a value, supported values include, TrackingId, AttachTo, RequestId, PayerId, OrganizationId, ProviderId, MemberId, ServiceDate, Attachment (required).
part >> nameThis is one component of the Attachment; describes something about the attachment. Supported values for the attachment part name, LineItem, Code, Content (optional).
resourceThe actual clinical document payload.
valueCodeableConceptDescribe the type of attachment/document being submitted/attachment.
valueStringThe attachment part name, for example, if it is LineItem, '1'.
valueCodeValue used when name is AttachTo. Allowed values are claim and prior-auth.
valueDateA single ServiceDate, format: YYYY-MM-DD.
valueIdentifierUsed to represent business identifiers such as Tracking ID, Payer ID, Organization ID, Provider ID (NPI), and Member ID. It contains both the identifier value and the system that issued or defines the identifier.
valuePeriodServiceDate range.
valueStringValue used when name is RequestId. Example payer request identifier: PA-REQUEST-12345.
resourceTypeFixed value, Parameters.
Headers
x-mock-scenarioUsed in sandbox environments to return predefined mock responses instead of real backend processing.
x-optum-trace-idUnique identifier used to trace and correlate requests across Optum systems for troubleshooting and support.
ParameterRequiredNotes
TrackingIdYesCorrelation ID for submission
AttachToYesclaim or prior-auth
RequestIdYesRequest identifier
PayerIdYesPayer identifier
OrganizationIdYesSubmitting organization
ProviderIdYesProvider NPI
MemberIdYesMember identifier
ServiceDateYesDate of service
AttachmentYesClinical document
Release NoteFAQs
View the API Release Notes for more information about the API.—