Request and Response from Payer

Suggest Edits

The API uses a POST request. You provide the input as JSON in the body of the request. Include sufficient claim information (claimInformation object) in the request to ensure the attachments submission goes to the right place. A submission for a Solicited Attachments transaction (attachments requested by the payer) contains more payer information.

Accept: application/json
Content-Type: application/json
X-CHC-Attachment-SubmitterId: 1234
X-CHC-Attachment-BillingId: 5678
X-CHC-Attachment-Provider: concordfax

Include sufficient claim information (claimInformation object) in the request to ensure the attachments submission goes to the right place.

files >> ADD FILE required field: Upload the file.

File formats supported
Our Attachments solution supports the following formats for 275 attachments: JPG, TIF, TIFF, PDF, JPEG, and PNG. Payers provide varying support for these formats. Consult your Optum representative to determine which formats your payers can work with.

Our Attachments solution includes workers’ compensation attachments and medical attachments.

request required field

curl --request POST \
     --url https://sandbox-apigw.optum.com/medicalnetwork/attachments/submission/v1/v1/attachments/uploads \
     --header 'Authorization: Bearer eyJraWQiOiIxIiwidHlwIjoiSldUIiwiYWxnIjoi...' \
     --header 'accept: */*' \
     --header 'content-type: multipart/form-data' \
     --form files='@CustomPayerConfig%20Design.jpg' \
     --form 'request={    "controlNumber": "123459999",    "tradingPartnerServiceId": "TESTEP01",    "tradingPartnerName":"unknown",    "submitter": {        "organizationName": "happy doctors grouppractice",        "etin": "1942788757"    },    "provider": {        "organizationName": "happy doctors group",        "npi": "1760854442",        "address": {            "address1": "123 address1",            "city": "city1",            "state": "wa",            "postalCode": "981010000"        },        "phoneNumber": "123456789"    },    "subscriber": {        "memberId": "0000000001",        "firstName": "johnone",        "lastName": "doeone"    },    "claimInformation": {        "patientControlNumber": "12345",        "beginClaimServiceDate": "20050513",        "endClaimServiceDate": "20050514",        "serviceLines": [            {                "payerClaimControlNumber": "123456789",                "serviceLineDateInformation": {                    "submissionDate": "20050514"                },                "attachmentDetails": {                    "name": "CustomPayerConfig Design.jpg"                }            }        ]    }}'

{
	"status": "success",
	"attachmentId": "bcf124de-1051-d783-4a50-6d3562186fb2_TESTEP01_999898"
}

After the clearinghouse sends the attachments and receives the payer acknowledgement, you will receive a response body showing the status of the attachments submission. Results may vary based on payer acceptance or non-acceptance of individual attachment files.

Each individual attachment file in the submission gets a separate object as a part of the overall response. This is how you will find out the state of a partial acceptance of attachments from the payer.

For submissions with more than one attachment, you will receive a Partial Acceptance notification as part of the response should one or more submitted files not be accepted.

In the preceding example, you see that accepted attachments will simply receive an acceptance time stamp. Rejected attachments will receive a rejectionInformation field briefly describing the reason.

For a longer set of response examples, see other kinds of responses seen in submissions.

Authorization required field: Bearer token

Updated 22 days ago