[Jim]

Thank you Rob I am following up with support they are researching the issue.

 

Jim

[Jim]

Thank you Charlie’s code worked like a charm.

Jim

[Jim]

Rob,

 

What happened to patch 19.1.3.0

 

We have the release notes but the software is not available on the download site did they pull it back.

Jim

[Jim]

Rob Abbott is there an Infor official recommendation?

Jim

[Jim]

Thank you Charlie.

Jim

[Jim]

Rob,

How can I minimize the number of messages that are sent to the translation thread when I have multiple different criteria for different routes? If I have a Trx ID UPOC on the Inbound side that will create a subset of messages for the route as outlined in my above post which is based only on MSH then the only way to route any other messages is from the static_route by doing a generate and creating a route which is now hidden from view?

Jim

[Jim]

That’s what I suspected.

Jim

[Jim]

Rob,

Will the 20.x version of Cloverleaf be supported on Redhat Enterprise Linux 8.x

Jim

[Jim]

Thank Jim

We found that when we converted from SMAT file’s to SMAT dB’s our disk space use was substantially increased.

Jim

[Jim]

Michael,

The problem is that the sending application’s conversion process has bugs in it and they haven’t found them all yet. The code that we wrote works so I am not to concerned. The data is entered into a from and then converted to plain text.

Jim

[Jim]

Michael,

Great idea the only problem is it is a known problem in the sending system and there is nobody on the application side to fix the issue. When you look at it on the application side it doesn’t look like there is a problem it only occurs when the system creates the HL7 message. Of course they told us 2 releases ago that it would be fixed in a future release.

Jim

Jim

[Jim]

Has anyone been able to get the colorized version to work with 6.1.2.1?

Jim

[Jim]

Mike,

Thank you. The sending system randomly puts the r in the message and can be anywhere. Therefore we have to process the message in whole then put the r back in the correct locations.

We resolved the issue with the following in our script;

set newmsg [string map {“PID” “rPID”} $newmsg]

set newmsg [string map {“OBR” “rOBR”} $newmsg]

set newmsg [string map {“OBX” “rOBX”} $newmsg]

since these are the only segments in the message we should be ok.

Jim

Jim

[Jim]

Loved the colors when I was 6.1.2 but since we installed the patch to version 6.1.2.1 it no longer works.

Jim

[Jim]

Fellow Clovertechers

As it turns out this is a bug in 6.0.2 which manifests itself when you have a connection that is either up or opening and several hundred messages queued for that thread. The process panics and produces a core dump. This is what support had to say;

“R&D told me this was a bug that was reported and the fix will be in 6.0.3 which should be coming out soon. They suggest to go back to 6.0 until the patch is available. “

Jim

Jim

[Author]

Replies