[IDEA] The XML standard is that attribute order doesn't matter.

[frankparth]

When create OBX segments if the order of the XML children is out of order fields are being added that shouldn't exist and order is being rearranged in HL7 v2 representation.

In this specific case if in the XML version of the HL7 message has OBX.2.1 come before OBX.3.1 additional fields are created in the HL7 v2 version of the message. In our case the value in OBX.14.1 in the XML was being moved to OBX.16.1 in the v2 message.

<OBX.1>
<OBX.1.1>1</OBX.1.1>
</OBX.1>
<OBX.3>
<OBX.3.1>code</OBX.3.1>
<OBX.3.2>display</OBX.3.2>
<OBX.3.3>system</OBX.3.3>
</OBX.3>
<OBX.2>
<OBX.2.1>CWE</OBX.2.1>
</OBX.2>
...

XML order should not matter.

[pacmano1]

Build segments in order.

Or https://github.com/nextgenhealthcare/connect-examples/tree/master/Code%20Templates/Fix%20HL7%20Node%20Order

[frankparth]

Thanks pacmano1! Hope you're doing well! I already created a code template to do the same thing but why isn't fixHL7NodeOrder embedded in the solution?