We support a dedicated X12-formatted Eligibility API to send your submission in X12 EDI format. It supports the standard syntax for a complete X12 EDI 270 transaction set.
Our Eligibility API solution provides complete patient profiles and benefits information to support healthcare delivery and more efficient and accurate reimbursement.
Payers will find claims spend less time in pending status and will see fewer rejected and reworked claims.
A: Some payers require National Provider Identifier (NPI) enrollment before they will process eligibility requests and send responses. For the list of payers who require enrollment, please refer to the payer list on ConnectCenter. You will need to log in to access this information.
Depending on the payer, you may need to send the NPI in all Eligibility requests. An office can enroll one NPI and use that NPI for all requests in their office, or they can enroll additional NPIs.
For more information, your Optum implementation analyst will be able to help.
A: Each NPI that will use Eligibility requests requires a separate enrollment. So, there's one NPI per enrollment. The TIN (Taxpayer Identification Number) does not apply, except for its being on the enrollment form. If an office enrolls one NPI, they use that NPI for all requests in that office or they can enroll additional NPIs.
A: Yes, you can use our sandbox environment before signing a contract. The login requires a separate set of credentials that you can get from your Optum representative. After receiving your client_id and client_secret for our sandbox environment, you can test the API in our interactive documentation, use an application like Postman, or test APIs using your own development console.