Format of the Sender Application and Receiver Application Fields

When HL7 Module performs code table validation for a message, it determines whether to use partner specific code tables based on the value of the fields in the message header. During the execution of the convertHL7ToIData service, HL7 Module obtains the validation information from the Sender Application field (MSH.3). During the execution of the convertIDataToHL7 service, the module uses the Receiver Application field (MSH.5).

The MSH.3 and the MSH.5 fields contain the following components:

Component	HD Type	Description
namespace ID	HD.1	The application namespace value. In the MSH.3 and MSH.5 fields, the namespace ID corresponds to the Corporation Name in a Trading Networks partner profile. In the MSH.4 and MSH.6 fields, if present, the namespace ID can optionally correspond to the Unit Name for the sending and receiving Trading Networks partner respectively. For more information about how HL7 Module uses this information to identify a trading partner, see Identifying a Trading Partner. Note: Ensure that the application namespace does not contain an underscore character ('_').
universal ID	HD.2	Corresponds to the External ID of a Trading Networks partner.
universal ID Type	HD.3	Corresponds to the External ID Type of a Trading Networks partner.

The format of the data in the MSH.3 and MSH.5 fields depends on the HL7 message version:

For HL7 message versions 2.1 and 2.2, the MSH.3 and MSH.5 fields in the message header of both ER7 and XML formatted messages must be specified as a string type ST and separated by underscore "_" as follows:

namespace ID (IS)_universal ID (ST)_universal ID type (ID)

For example: wmIS_1011_DUNS

For all other HL7 2.x message versions, the format differs for ER7 and XML messages as follows:

For ER7 messages, the schema contains the namespace ID, universal ID, and universal ID type as different components that are separated by the component separator in the ER7 message.

For example: wmIS^1011^DUNS, where ^ is the message component separator.

For XML messages, the components are in separate tags in the XML message.