Process documentationValue Mapping: Use of System-Specific Code Lists

 

You use this process to implement value mapping using system-specific code lists. You must use a system-specific code list if you are using Application Link Enabling (ALE) communications or if target systems do not support value mapping.

Process

The following steps describe value mapping for a selected value when you use a system-specific code list. The selected value is the Company form of address.

  1. Outbound Processing on the MDG Hub

    When the MDG hub sends a message that contains the Company form of address, the system converts the internal code defined for the MDG hub (0004) to the code defined for the message (0003). See graphic below.

    The value mapping configuration information shown in the graphic is summarized in the table below.

    Values in the Message

    Internal Values (MDG Hub)

    • Values come from one of the global code lists for the Global Data Type (GDT) FormOfAddressCode. This code list has a list agency ID of MDG_GLOBAL and a list version ID of 1.

    • Codes are 0002 = Ms., 0001 = Mr., and 0003 = Company.

    • Values are mapped to the values described in the Internal Values (MDG Hub) column.

    • Values come from the AD_TITLE data element. This data element is associated with the AD_TITLE domain.

    • Codes are 0001 = Ms., 0002 = Mr., and 0004 = Company.

    • Values are mapped to the values described in the Values in the Message column.

  2. Inbound Processing on the Target System

    When the target system receives a message that contains the Company form of address, the system accepts the values as they are without doing any conversion.