Setup Real Time Services

[drtech]

How do you set up real time services with Claim Connect in OD? I am set up on their end, but when i request benefits in OD, I get an error to " Please fix the following errors first:" but it is blank.

[drtech]

using V 6.7.19

[jordansparks]

I know that a number of users are successful. Let me look through the code and see if I can spot a situation where it would ask you to fix errors without telling you what errors. You're not in debug mode, right?

[afeuer]

I've been trying to get real time services to work for a couple of weeks now myself. I also have the service set up with them and it works fine through their website. I've checked and rechecked my settings but when I request benefits its gives me this error:

Please fix the following errors first:
userNotAllowed

I definitely have the correct username and password. Any suggestions?

[jordansparks]

And you are on at least version 6.7.19?

I don't recognize the "userNotAllowed" error. But I'll put down as a bug that the error descriptions are inadequate. After the fix, it will hopefully give you much more information about the problem.

[drtech]

I double checked and I built it in release mode....and the other printing works fine, so that should mean I am not in debug mode.

Is there any other setup besides what I have had entered in the clearinghouse setup for e-claims for a few years?

[jordansparks]

No, there is no other setup. So we'll have to enhance the error message, recompile, and try again.

[afeuer]

Hi, I'm using version 6.7.19. It's release not debug. Also, I have the real time eligibility service with them but I do not have the electronic claims with them. That could be causing the problem. Their electronic claims service is more than twice as expensive as webmd is for us so hopefully it will work without it. Thanks for looking into this.

[jordansparks]

I believe that your default clearinghouse would have to be ClaimConnect for now. We are not quite to the point where we can do eligibility with multiple clearinghouses or directly to carriers. The biggest hurdle is building the communication layer. The messages themselves won't change.

[afeuer]

I've been playing around on a test computer. The default carrier is set to claimconnect, but i'm still getting the same error. Any suggestions?

Thanks,
Adam

[jordansparks]

You should call us and let us take a look at your clearinghouse settings. Until it moves out of beta, we don't have instructions posted, and our support staff is not yet trained on it. So we just do the best we can. As it comes out of beta, the instructions and support for it will get better.

[eiscott]

Jordan,

Please let us know if we can assist in any way.

Scott

[afeuer]

It's been a while since I've played with this. I'm now running version 6.7.21.0. When I try to request benefits it says

Clearinghouse server sent this error:
SoapException: invalidPms

any ideas?

[jordansparks]

Ah. Better error message. But I can't find a good reason for it. Possibly your clearinghouse info isn't set up right? Now that you know what the error is, you might also contact them for a suggestion.

[drtech]

Mine now says SOAP exception or error or something like that everytime...

[jordansparks]

Is it the exact same message as above? And 'afeure', can you email me with your real name? We should call you or you should call us so that we can track this down for you.

[drtech]

No, not exact:

Clearinghouse server sent this error:
SoapException:

[afeuer]

So I finally got it to work. It turns out that you have to have electronic claims set up to use this feature. I had the real time service from dentalxchange, but it wouldn't work until I added electronic claims to my package with them.

Also, for people who are getting errors it might be that you have the wrong electronic ID for the insurance company. I noticed that a few of the electronic IDs are different in OD than they are on the claim connect website. Use their website to get the electronic IDs and you shouldn't have a problem.

-Adam