[Gordon Koch]

Thank you Paul for your responses – very helpful.

I definately agree that we are hitting some resource constraint or limit on Interconnect, but was looking into some short term solution on the Cloverleaf side. Also, we will take a deeper look into Interconnect with Epic, and which is remotely hosted for us.

Lastly, can I contact you directly about your setup? My email is: kochg@hss.edu

Please email if you are available – I will be out of the office next week, but would follow up afterwards at your convenience.

Thanks again.

Gordon Koch

Hospital for Special Surgery – NY, NY

• This reply was modified 2 years, 7 months ago by Gordon Koch.

[Gordon Koch]

Hello All,

I am hoping to re-engage on this subject as we have been live for some time, and it is mostly going well. However, there are two scenarios where we have experienced problems.

 

Firstly, when an individual message is particularly large (even for encoded PDFs), Interconnect has a problem reading the whole single OBX segment in one try (and generates an error). Has anyone tried to convert a single OBX segment (of these very long encoded sequences) into more than one? I assume Interconnect can read multiple OBXs for a single PDF per a previous post.

 

Secondly, when multiple PDF messages are sent to Interconnect at roughly the same time, the same apparent resource constraint issue on Interconnect arises. Is there an ideal way to throttle the messages being sent from Cloverleaf?

 

Thank you.

[Gordon Koch]

That is a good point.

[Gordon Koch]

Hello Charlie,

You are of course correct in that the root cause needs to be investigated. However this sometimes occurs on our main ADT process, and it often needs to be brought back up right away.

[Gordon Koch]

Thank you for the response – very helpful; I was not sure that it was this straightforward (and noted that the exec action is selected).

• This reply was modified 2 years, 11 months ago by Gordon Koch.

[Gordon Koch]

Got it – thanks again!

Have a good weekend.

Gordon

[Gordon Koch]

Thank you Paul for the quick response – very helpful!

We are mostly set on the Bridges side, their documentation is good and we have a great TS. However, we are hosted and Interconnect is a black box to me – no access or control of it.

I am glad to hear that this interface is working well for you, and that is an interesting point about not needing to merge OBX segments.

Just one more basic Cloverleaf question: in the pdl-tcpip setup, are you going out to a URL or IP address? I assume the Port was provided to you, correct?

I ask because I am waiting to hear back from Epic on the basic connectivity setup.

Thank you.

Gordon

• This reply was modified 3 years, 2 months ago by Gordon Koch.

[Gordon Koch]

Hello Mike and Paul,

I am now starting a project to send encoded PDFs in MDM (HL7) messages to Epic’s Interconnect from our engine. I am very interested in any issues you encountered, and the basic setup for this in Cloverleaf. I see that this thread started regarding missing ACKs, and am wondering if this is still an issue. Another important point stated is to make sure Interconnect can accommodate the very large base64 encoded messages.

And first off, what is the Thread Protocol used to interface with Interconnect?

Any input is appreciated.

Thank you.

Gordon Koch

HSS

 

 

• This reply was modified 3 years, 2 months ago by Gordon Koch.
• This reply was modified 3 years, 2 months ago by Gordon Koch.

[Gordon Koch]

Thanks again Charlie. I was wondering this setting in the Properties tab interacts (or overrides) the others discussed in the Outbound tab.

[Gordon Koch]

Thank you Charlie for the information – this is exactly the insight I am looking for.

I agree that 5 seconds is normally too short of time, and we have the Timeout field (Inbound Replies pane, Outbound tab) set to a minimum of 30 seconds for all our interfaces (except this one for the special circumstances).

Finally, in the Thread pane of the Properties tab, what does this “Retries” field indicate or control?

Thanks again!

[Gordon Koch]

Thank you Robert for the detailed response – it is rather helpful. The reasoning behind this setup is that the messages sent to the receiving system from the engine are very time sensitive, and become “stale” quickly due to the overall workflow. I was told that it is better for the receiving system to not receive the message if delayed, as subsequent workflow generates a new “fresh” or updated message with the same order information.

[Gordon Koch]

We have all our devices going to a middleware product and then through the engine before Epic. At Jim stated, it should be isolated in its own site, and be careful about the SMATs.

For our setup, Epic actually wanted us to go through the engine before Bridges (Epic). I am curious as to why they recommended differently.

[Gordon Koch]

Hello Kaley,

     I have a similar issue if wanting to compare two fields in separate iterations of the same segment type (but I need to suppress one of them), and I was wondering how you structured your Xlate. Can you please share this?

Thank you.

[Gordon Koch]

Thank you for the response. My original use case was resolved in a different manor (the messages were interrogated inside the Xlate), but I will make a note of this for the future.

[Gordon Koch]

Yes, best of luck in your future endevors!!

Jim, thanks again for the help you have provided to me and to everyone else on Clovertech.

[Author]

Replies