Data attribute fields

The following describes the valid fields for data attribute definition for all message types (XML, HL7v2 and v3, fixed width, and delimited).

Configuration Number – The configuration number uniquely identifies the data attribute definition within the Data section. It also determines the order in which the attribute definitions are processed.

Enabled Flag – This flag determines whether the attribute definition is enabled (on or off). This flag is used to configure your broker file to handle attributes differently for each source if necessary. For example, if you use [Global–Data] to initially create the configuration file, you can then go into each [sourceID-Data] section and set the attribute enabled flag to Y (on) or N (off) as needed. By default, all attribute definitions are enabled. Valid values are Y or N.

Segment Code – This field defines the attribute segment type (for example, MEMHEAD or MEMNAME).

Attribute Code – This field maps the message data to the attribute code defined in the MDM database. All segment codes require an attribute code except for MSGHEADER and MEMHEAD.

AsaIdxNo – This field maps the attribute to a specific asaIdxNo in the MDM database. The primary function of asaIdxNo in the Inbound Broker is to direct the placement of attribute values from source systems into “slots” in the MDM database. The Outbound Broker process uses the asaIdxNo to direct the return of attribute values from the MDM operational server to the source. If the asaIdxNo is not defined, it defaults to 0. The MDM database allows for more than one valid (active) attribute of the same type (for example, more than one valid mailing address). For outbound processing, if the consuming source does not support multiple valid attributes, you can filter out the attributes by not defining them in the configuration file.

Member Index – The member index determines the member information to be sent in the message. The primary or trigger member has a member index of 0. All subsequent members have greater than 0. List is sorted through ascending memrecno order.

Entity Index – The entity index groups the entities. 0 (zero) is the default. If you have only a single 0, the returned members are not returned by entities. Any non-zero number (for example, 01) groups the results by entity.

History Index – This field determines the history information to be sent. The most current history has a history index of 0. All older attributes have a history index greater than 0.

View Type – This field determines whether the information is a member view or an entity view. The valid values are M (Member) or E (Entity), with the M being the default M. Entity processes an EntityGet EMCA.

Config Mode - The config mode indicates whether the data object is: r = Read, w = Write, or r+w = Read and Write.