Converting an A08 to A02

I didn’t think A08’s differed that much from A02’s, but it could just be the variant you’re using.

If there is so much difference so that you can’t just move the “A02” to the MSH-9.1 field, then you would need two translates.  The first would be an A08 to A08 translate, suppressing the messages that meet the condition of the message being converted to A02.  The second would be an A08 to A02 translate, suppress all the messages that don’t meet the condition of being converted to A02.  Then in your routing, you would have two xlate routes under the ADT_A08 trxid routing to the same destination, but using different translates.

If you don’t want the suppresses in the translate, you can also write a quick pre-proc UPOC that kills any messages that meet/don’t meet the condition.  You could do it with one proc and an argument that controls what action is done on a match.  This UPOC would then go on both routes.

That’s the thing about Cloverleaf – lots of ways to do the same thing!

One way to do this is to use Xlate Chaining. The first Xlate in the chain produces one of the OB Event Types, the second the other.

The first Xlate CONTINUES the message under the stated conditions which passes it to the chained Xlate. Means  Xlates but it makes the work very discreet and makes what is happening obvious when looking at the NetConfig.

If you have never used chaining and would like a precise I created for my team back when I was at MDACC, email me.