Reply To: segment ## is out of order for message type XXXXXX

[David Teh]

Hi Mary,

You probably should be on 5.3 by now.

Was your problem solved in 5.3?

I am encountering similar problems for the same translation in 3 different boxes – 2 on 5.3 and 1 on 3.8.1. The XLT uses A31 for both inbound and outbound formats.

But the error is complaining about A08:

“The # 3 segment encountered ‘OBX’ is out of order for message type ‘ADT_A08’.  Segment ignored.”

PV1 is mandatory for A08, but optional for A31.

The error disappeared when we made PV1 optional for A08.

Strange…..

Mary Kobis wrote:

We are on 3.5.2P… I think it is a bug in the software… In my variant I created a ORU_R01 message, but when the engine runs it always defaults to ORU. The message I created (ORU_R01) is total different than the ORU. To stop the messages, I think I’m going to have to revert back to the ORU structure, but mark any required segments to optional and then add what I need…

BTW, I’m hoping our hosptial will be on 5.3 by fall!…

Thanks for all your responses.