[Anonymous]

I recently ran into an unexpected consequence of changing the

Topic

[Jim Kosloskey]

David,

So I am clear:

Your outbound variant has teh PV2 segment defined as optional not required AND the PV2-3 field is not defined as required.

Yet when null is COPY’d to the outbound PV2-3 and no other field is populated in the PV2 segment a PV2 segment is still created.

Is the above correct?

What release of Cloverleaf?

email: jim.kosloskey@jim-kosloskey.com 29+ years Cloverleaf, 59 years IT - old fart.

[Anonymous]

Jim Kosloskey wrote:

Your outbound variant has teh PV2 segment defined as optional not required AND the PV2-3 field is not defined as required.

Yet when null is COPY’d to the outbound PV2-3 and no other field is populated in the PV2 segment a PV2 segment is still created.

What release of Cloverleaf?

Correct, outbound PV2 segment is optional and PV2:3 field is optional.

Input message can have no PV2 segment, or an empty PV2:3 field, and a COPY still creates the empty PV2 on the outbound side.

Cloverleaf 6.0.2.0P on AIX.

Do you get a different result on your system?

[Jim Kosloskey]

I have not ried yet – hopefully will get some time later. 6.0.0 though.

In the meantime, have you looked at the 6.0.3 and later release nootes to see if this is addressed – seems like a bug to me based on what you have revealed.

email: jim.kosloskey@jim-kosloskey.com 29+ years Cloverleaf, 59 years IT - old fart.

[Jim Kosloskey]

6.0.0 does not have that capability as far as I can tell so I cannot test.

email: jim.kosloskey@jim-kosloskey.com 29+ years Cloverleaf, 59 years IT - old fart.

[Anonymous]

I have release notes for 6.0.4 and 6.1. I can’t find any reference to this issue in either.

[Robert Kersemakers]

We have 6.0.2.0 (RHEL) and I really had to search for this option (needless to say I never used it). When in the HL7 configurator, it’s in the ‘Options’ menu.

Could it be that it acts the way it is designed? Never truncate any field could mean that empty fields/segments will not be truncated/suppressed as well.

No time to test this…

Zuyderland Medisch Centrum; Heerlen/Sittard; The Netherlands

[Jared Parish]

I’ve come across similar behavior as well.  In my case, I was trying to pair down a repeating field.  For example, a field was populated with

   

Code:

|Rep_1~Rep_2~Rep_3|

I wanted to keep only the first repetition. But was left with

   

Code:

|Rep_1~~|

rather than

   

Code:

|Rep_1|

In the end, I had to write a TCL proc to clean it up.

CL 6.1 on Redhat.

- Jared Parish

[Author]

Replies