Multiple OBR segments broke out to single messages

[Sandi Meyers]

I am sending to a facility that can not (or will not) accept a message that has multiple OBR segments.  Since this is very common with microbiology results I am trying to figure out a way to ‘fix’ this.  One suggestion I received was to break these out to send an entire new message with each OBR/OBX group.  I have no tcl experience yet.  Training is set for the new year.  Does anyone have anyhting out there that I could play with to try and make work.  I am adding an attachment that is an example of a result that i would need to manipulate.  I am guessing I would need to include the entire top part of the message MSH, PID, PV1, ORC as well as the OBR and subsequent OBX’s at each break of OBR’s.  Any help or direction would be appreciated and hopefully after training I can reciprocate.

Topic

[Gary Atkinson]

You can do this in the translate by using CONTINUE.

[Jim Kosloskey]

Inside your OBR Iteration as the last Action before leaving the OBR Iteration (not the OBX or any NTE Iterations) use the CONTINUE Action.

Then make sure that outside of the OBR Iteration (normally I do this at or near the beginning of the Xlate) use a SUPPRESS Action.

Hopefully you are not using BULKCOPY.

email: jim.kosloskey@jim-kosloskey.com 29+ years Cloverleaf, 59 years IT - old fart.

[Sandi Meyers]

I have some iterations for OBX and NTE within my OBR iterations, do I wnat to put the CONTINUE as the last action after all these?

And why do I want a Suppress?

[Gary Atkinson]

If you don’t suppress, then the translate will send out an extra message.  I believe if just nest your iterates together and then add the CONTINUE at the end, you should be good to go.

[Jim Kosloskey]

Xlate will always produce a message.

In your case, you are producing ADDITIONAL messages (via the CONTINUE). When you are finished producing your additional messages (exhausted the OBR repetitions in your case) the Xlate still has a message to cut. This most likely will be an additional copy of your last message you generated.

In almost all cases, you do not want that additional message so the SUPPRESS Action tells the Xlate not to produce its message. This is what is used when folks do message filtering inside the Xlate.

I normally place the SUPPRESS at the beginning of my Xlate so that it is a reminder I have a SEND or CONTINUE later on.

Although this is not your case, if the CONTINUE or SEND were conditional, then you would not want the SUPRESS to be unilateral but rather be a complement to the conditional SEND or CONTINUE. Thus the SUPPRESS (in the case of conditional SEND or CONTINUE) would NOT be at the beginning unconditionally.

email: jim.kosloskey@jim-kosloskey.com 29+ years Cloverleaf, 59 years IT - old fart.

[Author]

Replies