I'm using v 1.2 and am running across a problem where it looks like a destination configured as LLP Sender is only sending the raw data, not the transformed. When I set up the channel source, I establish a javascript transform that is something as simple as:
// the gender is M, as a test, change it to 1
msg['PID']['PID.16']['CE.1'] = '1';
logger.info("MSG gender is" + msg['PID']['PID.16']['CE.1']);
localMap.put('hl7_xml', msg);
hl7_xml = msg;
Note: I've tried a bunch of variations on this script -- this is the most sane.
If I set up a file writer destination, then I can choose to write the transformed message. However, it appears that no matter what I tried (or have tried so far) only the original, raw, non-transformed message goes out via LLP. I have a process running a HAPI-based server that reads the message via LLP and writes out the gender, which is always the original 'M'. Any clues on what I am doing wrong or what I can try?
I appreciate it.
Andy
// the gender is M, as a test, change it to 1
msg['PID']['PID.16']['CE.1'] = '1';
logger.info("MSG gender is" + msg['PID']['PID.16']['CE.1']);
localMap.put('hl7_xml', msg);
hl7_xml = msg;
Note: I've tried a bunch of variations on this script -- this is the most sane.
If I set up a file writer destination, then I can choose to write the transformed message. However, it appears that no matter what I tried (or have tried so far) only the original, raw, non-transformed message goes out via LLP. I have a process running a HAPI-based server that reads the message via LLP and writes out the gender, which is always the original 'M'. Any clues on what I am doing wrong or what I can try?
I appreciate it.
Andy
Comment