field routing using multiple fields question

[Jim Kosloskey]

Cloverleaf 6.0.0

AIX

I have defined a trxID using Field routing and I have selected multiple fields (3) but the TrxID I get appears to be 3 different TrxIDs.

I am using MSH-9.1 and MSH-9.2 (one field), OBR-24, and OBX-5.5.

The values retrieved are:

MSH-9.1 (ORU)

MSH-9.2 (R01)

OBR-24 (MICRO)

OBX-5.4 (PDF)

What I expect to see is ORU_R01_MICRO_PDF as a single TrxID but what I am seeing is 3 TrxIDs:

ORU_R01

MICRO

PDF

I don’t think that is what should be returned – or do I have to do something else to get these strung together and presented as one TrxID?

Anybody else using multiple fields?

email: jim.kosloskey@jim-kosloskey.com 30+ years Cloverleaf, 60 years IT – old fart.

Topic

[Keith McLeod]

If the separators get replaced with the _, how will it determine with 4 components selected that it is to replace the ^ symbol with an underscore?

Can you add a separation character into the definition separating the components?

Just thoughts…

[Jim Kosloskey]

Keith,

Thanks for the reply.

I did try adding the underscore between fields in the GUI but that threw an error upon execution as  it tried to parse on the entire string of all address paths as if it were one field.

The fields specified get placed as a list in the NetConfig.

It appears rather than concatenating the values associated with that list into a single TrxID each value is being presented as a separate TrxID.

I looked all around and did not see anything that indicated what I am trying is invalid – but there is no good example in the doc as to what to expect.

My next step (unless I hear something) is to take a look at what is actually in the NetConfig – maybe it is not a single list of multiple elements but rather multiple lists with one element per list. That could be confusing.

email: jim.kosloskey@jim-kosloskey.com 30+ years Cloverleaf, 60 years IT – old fart.

[Yves Guerin]

Hello,

We use a tcl proc to determine the trxId (upoc) so we can return everything we want, more easy and flexible.

Yves

[Jim Kosloskey]

Yves,

Thanks but I want to make sure I know how to use this technique in addition to Tcl .

Anybody know how this is supposed to work?

If I have to I will contact support but I hoped the community could assist.

email: jim.kosloskey@jim-kosloskey.com 30+ years Cloverleaf, 60 years IT – old fart.

[Robert Kersemakers]

Hi Jim,

(Testing CL6.0.2 on RHEL)

I hadn’t seen this option until I saw this post. I looked at the docs as well, but alas.

As the field routing is a list of fields, can’t you define the trx ID for the route as a list as well? With your example that could be {ORU_R01 MICRO PDF} or, with wildcards turned on {ORU_R01 {MICRO|MACRO} {PDF|RTF}}.

I am not able to test this myself currently, but will have a look at it as this could replace some custom scripts that we have in place for determining specific trx IDs, where several fields are being concatenated.

Zuyderland Medisch Centrum; Heerlen/Sittard; The Netherlands

[Jim Kosloskey]

Robert,

What is actually received is 3 distinct TrxIDs

ORU_R01

MICRO

PDF

not one TrxID like this: ‘ORU_R01 MICRO PDF’.

I have confirmed this is an issue in 6.0.2 and it is a known problem.

My understanding is it has been brought to the attention of R&D and escalated.

So hopefully it will be corrected in 6.1.1.

email: jim.kosloskey@jim-kosloskey.com 30+ years Cloverleaf, 60 years IT – old fart.

[Robert Kersemakers]

Hi Jim,

Ah, that’s good to know. I will forget about this then, as we won’t be migrating to 6.1 soon (I think).

Thanks for the information.

Zuyderland Medisch Centrum; Heerlen/Sittard; The Netherlands

[Author]

Replies