Configuring Fields - IHE - Foundation 23.1 - Foundation 23.1 - Ready - OnBase - Premier - external - Standard - Essential - Premier - Standard - Essential

IHE Solutions

Platform
OnBase
Product
IHE
Release
Foundation 23.1
License
Premier
Standard
Essential

HL7 messages transmit data within fields, field components, and subcomponents. Within templates, individual fields must be configured in order to specify how the information found in those fields is processed. Field configuration is performed in the IHE Field Settings dialog box, which is accessed from a template's Field dialog box either by clicking the Create button to make a new field, or by selecting an existing field and clicking the Settings button.

The following field settings are available:

Field Setting

Description

Field ID

The location of the data within the field group.

If the field ID contains two numbers separated by a decimal point, it represents a component. For example, if the field ID is 3.1, the data is expected in the first component of the third field.

If the field ID contains three numbers separated by decimal points, it represents a subcomponent. For example, if the field ID is 3.1.2, the data is expected in the second subcomponent of the first component of the third field.

See the HL7 Module documentation on Examples of Mapped Fields, Components, and Subcomponents for more information.

Field Group ID

The number of the group to which the field belongs.

Field Name

A short description of the data expected in this field.

Keyword Type

Allows you to map a Keyword Type mapped to this field, component, or subcomponent. Keyword Type mapping can be used for indexing documents and populating outbound messages.

Translation Table

Allows field values to be translated using the selected translation table. See the HL7 Module documentation on Translation Tables for more information.

Static Value

Allows you to manually enter a default value for the field.

Cardinality

Allows you to set the optionality and variability for values contained in the field. See Cardinality Relationships for more information.

Source Processing

Specify how the field is used for outbound communication, when the template is applied to a rule in the Source processing type. The following options are available:

  • Keyword Type: Populates the field with the value of the Keyword Type selected in the Keyword Type drop-down list above.

  • Primary Key: Prevents the entire template from being used for outbound communication unless there is a value for the Keyword Type selected in the Keyword Type drop-down list above. This setting is only applicable if the Keyword Type option is selected for Source Processing.

  • Static Value: Populates the field with the value entered in the Static Value field above.

  • Disabled: Does not populate the field during Source processing.

Repository Processing

Specify how the field is used for inbound communication, when the template is applied to a rule in the Repository processing type. The following options are available:

  • Keyword Type: Stores the value found in the field as the value of the Keyword Type selected in the Keyword Type drop-down list above.

  • Static Search Key: Checks the value found in the field to see if it matches the value entered in the Static Value field above. If the found value does not match the specified static value, no processing is performed on the group to which this field belongs.

  • Disabled: Does not use the value found in the field for Repository processing.