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

I had the same thing happen to me and here is what had happened.

I had created a message type that was not part of the HL7 standard like ORU_R01 in your case but it had something to fall back on if not found like ORU in your case.

I developed the xlate with ORU_R01 tested and went live.

For some reason the site specific varinat directory tree in $HCISITEDIR/formats/hl7/2.3/my_ORU_R01_variant got deleted.

Then the engine tried its best to use the next best thing form the standard HL7 variant which was ORU.

In my case ORU and ORU_R01 were identical so this went on for years just fine without me knowing of the problem.

I noticed it when we got to QDX 5.2.1P2 and tried to open the xlate and found that the newer GUI is more strict about this sort of oversight.

With all that said, I suggest you cd to your formats directory in your relevant site at the command prompt on the cloverleaf server and check that the variant you used to develop the xlate is still there.

For example:

cd $HCISITEDIR/formats/hl7/2.3/messages

ls -l ORU_R01

Another thing would be to use the HL7 configurator from the same site the Xlate is in to see if you can open the ORU_R01 variant and view the layout of the ORU_R01.

Ovbviously if you can’t do both of these you may need to recreate the variant.