OBX.8, repetition and length problem

Johhny,

You need to use the proper notation to get what you want.

Each repetition can be 5 characters long but you need to tell the Xlate which repetition you are working on.

What you are doing is COPYing a string with 5 repetitions into the first repeition of the field – that will not work the way you want.

COPY each of the inbound fields to the appropriate notation like this:

COPY ORU_R01.ORU_R01 –> 1(0).1(0).3(0).0(0).OBX.#8(0)

COPY PATIENT_RESULT.OBX.OBX –> 1(0).1(0).3(0).0(0).OBX.#8(1)

COPY 8(0).#text –> 1(0).1(0).3(0).0(0).OBX.#8(2)

I think you will also need some group repetitions for the OBX address path as normally messages with OBX segments have multiple OBX group aor segment.

The ~ is sometimes difficult to understand. The ~ means that the entire field repeats.

Examples:

PID||123^A~456^B|…|…|…

PID.02(0): 123^A

PID.02(1): 456^B

PID.02(0).01: 123

PID.02(1).01: 456

PID.02(0).02: A

PID.02(1).02: B

Johnny,

I am guessing your XML schema is not set up to represent repeating elements instad it was attempted to do that by imbedding the tilde in the text of a single XML  element.

If that is the case,I do not think that will work.

I was assuming your XML schema was constructed to represent repetitions.

As far as the HL/7 notation I will attempt to repeat what you have experienced but I suspect it is simply a case of notation structure and I typed that as an example from memory assuming you could correct the differences but get the concept. If you cannot discover the correct structure on your own I will post as soon as I have an opportunity.

Johnny,

I am sorry I did not see the downloads.

The HL/7 notation I gave you works fine on 5.6 maybe that is an issue on 5.5 – however, I think I have done the # notation with repetition in 5.2.

When you select the XML field in question from the IDE Xlate Inbound tree, does it give you a place to put in a repetition value?

If it does, then that should work I think.

I am also aware that the XML handling is improved beginning with Cloverleaf(R) 5.6. I know that is no big help to you but if an upgrade is in the plans maybe going to 5.6 or 5.7 (now available) might save you some sleepless nights on this integration.

Johnny,

I am no XML guy but it sounds to me like iti is possible your schema is configured correctly bu the XML data does not match.

I am thinking the data looks like it is all one field rather than repeating fields – even though the schema says differently.