Use configured / invoked Other HL7 Application Name & Facility values of sending HL7 application in MSH.3 / MSH.4 fields of outgoing HL7 messages

[vrindanayak]

Current code behavior populates HL7 application name and facility values of (sending) HL7 application of archive in MSH.3 / MSH.4 of outgoing HL7 messages, f.e. HL7SND|DCM4CHEE

even if an alias Other HL7 Application Name & Facility is configured on above (sending) HL7 application and is used in

• configured Dcm2HL7Exporter URI eg. hl7:HL7SND-ALIAS/DCM4CHEE:HL7RCV/DCM4CHEE
• invoked HL7 RS services to manage patient records in external archive

Rationale : Use instead the configured / invoked alias Other HL7 Application Name & Facility in outgoing messages' MSH fields as an alias may be configured on HL7 applications of several archive nodes in one cluster, and this alias is recognized by other external HL7 receivers in healthcare setups