For a longer discussion of Attachments in electronic data interchange and their use in our APIs, see this page.
The Attachments Submission supports the X12 EDI 275 Patient Information transaction. It translates this standard to JSON
, so it is more accessible to developers for integration into users’ applications.
Attachments submission take two forms: Solicited and Unsolicited. As an example of an unsolicited attachments, consider workman's compensation claims. Attachments illustrating the conditions giving rise to the claim are required in all worker's compensation claims, hence they called unsolicited claims. Solicited claims usually are sent by payers to providers requesting documentation for a claim.
An attachment, in the context of healthcare electronic data interchange (EDI), is an electronic rendition of medical documentation, such as an X-ray, lab report, or questionnaire, to support a healthcare administrative transaction.
JPG, TIF, TIFF, PDF, JPEG, and PNG are the supported formats for 275 attachments.
Our Attachments solution includes workers’ compensation attachments and medical attachments. Any receiver who does not support electronic attachments will receive the documentation through fax or mail.
Try our APIs
- To try or test our APIs in your own a development platform/tool, download and import our OpenAPI spec provided above by clicking the Download OpenAPI Spec using our sandbox predefined values to familiarize yourself with our APIs.
- If you do not own a development platform to try or test our APIs, use our interactive Try It interface to familiarize yourself with our APIs, for example, generate a bearer token. For information, see using the Try It interface.
Release Notes | FAQs |
---|---|
View the API Release Notes for information about the history of programmatic updates for the Attachments Submission API. | Check out our Attachments Submission API FAQ for help with specific questions about this API! |
NOTE
Please see the API FAQs section for tips and solutions to some of the questions most commonly asked by customers and staff, and in the developer community about the use of our APIs.