Potential bug: xlateInVals list improperly formed from HL/7 component field

All,

Cloverleaf 2209.

I have an xltp Tcl proc that uses values in the xlateInVals matched up with XlateInList.

When I specify one of the Source elements to be a componentized field (in this case PID-5) I would expect to see either just the first component (in this case ‘Patient’) or both components as a list {Patient Sample} associated with the xlateInList element. Instead, I see Patient and Sample as additional xlateInVals elements thus throwing off the association with xlateInList. There should be 5 xlateInVals elements instead there are 6 – see below.

You will note the elements are in synch until the PID-5 definition, then there is an additional element (Sample).

Has anyone else experienced this? Does this look like a bug? I can, of course, correct this by using component notation on PID-5 but I think the correct way this should be presented is either as just Patient or {Patient Sample}

xlateInVals >Y MYKEY Patient Sample y Y<
TEST XLTECHO v1.1: *** START *********************************************************************************************
TEST XLTECHO v1.1: xlateInList >@xlt_put_userdata_debug @xlt_put_userdata_key 0(0).PID(0).#5(0) @xlt_put_userdata_key_override @xltecho_debug<

Thanks,