I have split the POST into different processes. Now my new problem is that I have to send the 271 back thru any one of the ten routes back to one reciever thread that will send the 271 out to Cerner. I tried to just route the 10 back to 1 interface and needless to say, it created a mess.

I’m guessing that I need to set up…Read more

Cerner tells that their process is asynchronous. They can send multiple 270s in quick succession without having to wait for a 271. They can also take the 271s in whatever order they return. That was an issue in the beginning but have corrected that issue.

It looks my my configuration is similar to the one that you have posted. The…Read more

I see that my previous post isn’t very clear about my issues and what I am trying to do.

I have set up an interface using HTTP Client protocol.

First, I have an incoming tcp/ip interface sending X12 270 elibility transactions to Cloverleaf. I then wrap the 270 and post it to a 3rd party vendor using HTTP Client.

The 271 response comes…Read more

I have run into the same issue as Tom in routing the responses back to the originating system’s inbound thread. I am creating a 270 insurance eligibity interface and the responses are landing in the error db.

I was wondering if I might also get a sample of your tcl proc.

Thanks

Marian Michniak
mmichnia@nmh.org