In the Main Menu, click Setup, Family/Insurance, Clearinghouses. Double-click on ClaimConnect.

Visit www.dentalxchange.com or contact DentalXChange at 800.576.6412 Ext 455 to learn more about their services and pricing.

Set up in Open Dental

Login ID and Password:
Enter your DentalXchange account credentials.

Use Claim Export Path:

• Checked: Save 837 files sent with e-claims to the Claim Export Path.
• Unchecked: Block saving 837 files sent with e-claims to the Claim Export Path.

ERA Options:

• Report Path: Enter path where downloaded ERAs will be stored.
• Do Not Download ERAs: Do not automatically download ERAs.
• Download ERAs: Automatically download ERAs to the Report Path.

According to ClaimConnect, the advantages are:

• HIPAA compliant X12 format.
• Submits directly from Open Dental software via secure, HTTPS Internet protocol. No third party program to download and install.
• ClaimConnect offers direct connections to most major insurance companies meaning less "hops" in between you and the Payor and faster payments.
• ClaimConnect is the only service that offers real-time claim processing for MetLife claims. You get an Estimate of Benefits back within moments of the claim submission.
• Online claim management screens that allow you to view, track, edit and even resubmit claims with a few mouse clicks and keystrokes.
• Other HIPAA compliant real-time services available include:
  • Eligibility and Plan Benefit information for selected Payors.
  • Claim Status Inquiry for selected Payors.
• 30 Day Satisfaction Guarantee

Register with ClaimConnect

1. Go to www.dentalxchange.com.
2. Create a new account or edit your existing account.
3. Select Open Dental as your Practice Management Software.
4. Choose the services you are interested in.

• To use ClaimConnect for electronic eligibility and benefits, see Electronic Eligibility and Benefits.
• To use DentalXChange for patient credit checks, see DentalXChange Patient Credit Score Service.
• To use DentalXChange for attachments, see below.

Attachments

DentalXChange Attachment Service is an additional paid service for sending Electronic Attachments.

1. Sign up with DentalXChange. Contact DentalXChange for pricing and account setup.
2. Check Allow sending attachments in this setup window. If using clinics, this option can be enabled or disabled on a per clinic basis using the dropdown at the top-right.
3. To allow saving attachments, check Save DXC Attachments to Images Module. If checked, create an Image Category in Definitions: Image Categories. When checked, attachments will be saved to the Images Module when attachments are created.
4. To view an XML file of outgoing attachment request, check Save DXC Transmissions. This is typically only checked when troubleshooting. The XML file will be saved to the Claim Export Path.

Other Services

The password above applies to other services from DentalXChange:

• When billing, see Billing Defaults.
• For credit card services, see PayConnect Window.
• If using electronic benefit remittance, see ERAs and set up a Report Path.

Troubleshooting & Technical Details

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.

1. Go to the DentalXChange website and verify that the user can login.
2. Verify that the same password is entered for the clearinghouse in Open Dental.

Soap Exception

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: http://www.dentalxchange.com/x/payerlist.jsp 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. Enrollment forms may be found here: http://www.dentalxchange.com/x/enrollmentpayers.jsp.

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.

Uploads Fail

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 ClaimConnect 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 ClaimConnect 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 ClaimConnect: 150. Service Not Contracted.

This means you are not signed up for the ERA download service with ClaimConnect. You have two options:

1. To enable the service, contact ClaimConnect.
2. To stop the error message (and not enable the service), update to version 16.1.14 or greater.

Can we use a terminal server / hosted app for ClaimConnect?

Yes. The claim export path uses temporary subfolders when on a terminal server / hosted app. This allows multiple users to send claims simultaneously.