Attachments Status V1 Getting Started

Attachments Status V1 API

For detailed description about the API, see Attachments Status.

The Attachments Status API enables customers to query for the status of medical documents that they have sent as attachments transactions to their payer. The Attachments Status API reads transaction details and returns status information in an understandable format. In this section, you will learn about the various advantages of using the Attachments Status API, including its requirements, using metadata search, remediating incorrect transactions and other features.

For example, consider a provider sending a medical document to the Veteran's Administration (VA).

• How do they know it was received?
• Did Optum receive it?
• Was it processed and delivered to the VA?
• Did the VA accept it?
• When customers want to know the status of any attachments transaction, they can use our Status API to find out the status of the medical data they have sent to their payer.

You can search for all attachments transactions for a given patient or provider over a period of time. The Attachments Status API also ensures privacy by tying all requests to the specific Submitter ID associated with the API consumer.

Through our Attachments submission API, /attachments/submission/v1/uploads endpoint, the clearinghouse processes provider-submitted attachments transactions before forwarding the documents to the payer. Attachments Status API queries can receive responses directly from Optum, and responses that originate from the payer, so you will always know where the status is reported from.

Attachments Status endpoints

Please see Attachments Status URL.

📘

NOTE

The Optum Marketplace /attachments/submission/v1/uploads endpoint is a prerequisite for using the Attachments Status API.

See the API FAQs for more detailed information.

📘

NOTE

• If you only plan to use a few daily transactions, you can use our ConnectCenter for your Medical Network transaction needs.
  It provides most of the features supported by an API console but only allows manual entry for all data needed for a transaction. It contains PayerLists, the PayerList Enrollments wizard, and other API customer resources.
• For providers sending hundreds of daily requests, we recommend using our APIs to be able to automate the submission processes and have a better fit for your business needs.

Related Topics

• API Reference
• Security and Authorization V2
• Error Messages
• Troubleshoot APIs with Metadata
• ConnectCenter