jswaff wrote:
Thanks for your help. I think I'm almost there.
I've set up the outbound template in the destination transformer. Here it is:
I've deleted all the mapper steps and added a few message builder steps.
The message segment is something like: tmp['PID']['PID.3']['PID.3.1']
and the mapping value something like: msg['pc.patientid'].toString()
When using a file writer, the values I'm mapping are just blank now. The value from the template isn't used, nor the value from the database/inbound message.
Thank you again,
--
James
I've set up the outbound template in the destination transformer. Here it is:
Code:
MSH|^~&|MEDPLUS|PG|TouchScript|Interface|${date.get('yyyyMMddHHmmss')}||ADT^A31|1234|D|2.2|||||| EVN|A31|${date.get('yyyyMMddHHmmss')}|||| PID|||709-1|VEN709|Swafford^James^F||19750301|m|||addy1^addy2^Greenville^NC^27858||(555)555-5555|||M|||123-45-6789|||||||||
The message segment is something like: tmp['PID']['PID.3']['PID.3.1']
and the mapping value something like: msg['pc.patientid'].toString()
When using a file writer, the values I'm mapping are just blank now. The value from the template isn't used, nor the value from the database/inbound message.
Thank you again,
--
James
When I changed the mapping value from
msg['pc.patientid'].toString() to msg['patientid'].toString(), they all showed up.
I still have to set up the LLP sender and verify the 0x0d character is there (my original problem), but I'm confident it will be... I only had a minute and wanted to post that the above was solved.
THANK YOU! I hope I can give back to this project in the future. Honestly, I think the documentation is kind of lacking, but the support has been fantastic.
Thanks again,
--
James
Leave a comment: