[Marian Michniak]

Thanks for your help.

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 a multi server. Unfortunately, we don’t have any of these running on our engine.

Have you had a chance to set one up?

Thanks

[Marian Michniak]

Jim / Bob

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 onlyu difference is that I do not have any intermediate threads to do the routing to the different queues. I use the last digit in the ISA13 to determing which queue the 270 goes into.

Do you think that changing the inbound tcp interface to raw route to an intermediate before doing the routing?

I have attached my configuration. Please look at the interfaces in the lower left.

Thanks

[Marian Michniak]

Hello

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 back and sent back to Cerner via tcp/ip.

The issue that I am having is that this is all single threading. The 270 goes out and then the 271 has to come back before the next 270 goes out. The problem with this configuration is that many users are on this at the same time causing a bottleneck especially when some responses take a long time to return.

I tried a work around where I have created 10 HTTP Client interfaces. The inbound interface has raw routes to all 10 of these clients. The clients are numbered 0 thru 9.

I have created a tclproc to distribute the 270s into a different client using the last digit (0-9) of the control number in the 270. Basically, the proc is supposed kill the message to all of the clients except for the one that matched the control number.

The 271 then comes back and gets routed to the 271 oubound tcp/ip interface. All ten of the clients are routed to this interface.  

The process to send the message to the proper client is working but everything still acts as if it’s single threaded. I’ve tested with 4 nearly simultaneous message expecting to be logged into web services 4 times at the same time but it is still logging in once, wait for the 271 and logging in with the next 270.

Is there a way to configure this interface send simulataneously or does my solution look incorrect?

Basically the setup is:

                                      client 0

                                      client 1

                                      client 2

                                      client 3

                                      client 4

FROM_270                        client 5                        TO_271

                                      client 6

                                      client 7

                                      client 8

                                      client 9

 Thanks

[Marian Michniak]

Hi Jim

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

[Marian Michniak]

I have configured for both Client and ClientAuth and specified the location of the cert and am now getting a warning that SSL is not licensed.

[Marian Michniak]

Yes an HTTPS Web Services Interface.

[Author]

Replies