In Clearinghouses, double-click ClaimConnect.
Visit www.dentalxchange.com or contact DentalXChange at 800.576.6412 Ext 455 to learn more about their services and pricing.
Login ID: Enter the DentalXChange account Login ID.
Password: Enter the DentalXChange account password.
Use Claim Export Path:
According to DentalXChange, the advantages are:
To use DentalXChange for:
DentalXChange also offers Integrated credit card services using PayConnect. For setup, see PayConnect Setup.
DentalXChange Attachment Service is an additional paid service for sending electronic attachments.
DentalXChange sometimes uses payor ID 06126 as the default for insurance carriers that do not do e-claims.
The best troubleshooting approach to nearly any problem is to monitor the DentalXChange website. It will show you which claims were successfully submitted, which ones have errors, and so on. Use it regularly to stay on top of your claims.
When sending claims, receive 'authentication failed.authBadPwd' error.
This error is due to a bad password.
You may receive a "Soap Exception" from Claim Connect when attempting to send e-claims. This is almost always because the Electronic ID entered for the carrier is wrong. Go to the payer list on the DentalXChange website and look up the carrier to verify the Electronic ID shown in the Edit Insurance Plan window. Fix the ID, and resend. If the ID was correct, then you might need to enroll with the carrier for electronic submission. .
Claims Not Sending. You send claims. There are no errors, but nothing gets sent. The claim files are still sitting in the out folder such as, or whatever your setting is in the window above.
The most likely explanation is that your Comm Bridge in the window above is set to None instead of ClaimConnect.
After a failed upload, the next time that a user tries to send a claim, there is a warning, "A previous batch submission was found in an incomplete state." Resubmit the batch in question as well as the subsequent failed batch. Also, check the DentalXChange website to make sure all claims went through. This can be a particularly annoying problem because the user who gets the error message might click through it without reading it. There will then be no further warning, and the office may not realize that the batch failed until they start following up on aging claims a few weeks later. So, if you get a warning of some sort, start checking the DentalXChange website to verify that recent batches went through.
Invalid authentication request.authNoGroupUserFound.
This may be due to an interface change at DentalXChange that requires an action on your part. You are required to either check package requirements or view must read messages and general announcements prior to logging in and sending claims. Please contact DentalXChange.
Error retrieving. Era request unsuccessful. Error message received directly from DentalXChange: 150. Service Not Contracted.
This means you are not signed up for the ERA download service with DentalXChange. You have two options:
Can we use a terminal server / hosted app for DentalXChanget?
Yes. The claim export path uses temporary subfolders when on a terminal server / hosted app. This allows multiple users to send claims simultaneously.