The Attachments Submission API 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 submissions take two forms: Solicited and Unsolicited. As an example of an unsolicited attachment, consider workman's compensation claims. Attachments illustrating the conditions giving rise to the claim are required in all worker's compensation claims, hence they're called unsolicited claims. Solicited claims usually are sent by payers to providers requesting documentation for a claim.
This section provides a list of questions from our customers and from our sales and marketing teams; and key elements of the API explained in briefer sections to ease effective use.
Updated about 1 year ago
- How do I access the Production APIs?
- What information goes in the API request header?
- Do you have a sandbox that I can test before signing a contract?
- Sandbox predefined fields and values
- What do typical Attachments API requests look like?
- What are the differences between Solicited and Unsolicited Attachments?
- What file format types does this API support?
- What does a successful Attachments transaction response look like?
- How can I check the status of my attachment submissions?
- Trading Partners (Payer List) and Attachments Support
- Fax Numbers and the Attachments Submissions API
- Where do the Control Numbers come from?
- What are the JSON-to-EDI mappings for the Attachment Submission request?
- How do I attach multiple files in one transaction?
- How do I use the API to send a Fax to the payer?
- How do I handle payer submissions when they don't support 275 transactions and don't accept faxes?