Advanced Configuration

Custom HL7 schemas

Lookup tables are used to map HL7 XML group names and EnsLib.HL7.Message group names:

• ITB installation includes a lookup table for HL7 2.5 schema called hl7_2.5
• Each HL7 schema used in XML format must include a lookup table with the name hl7_[schema]
• For instance: if a custom HL7 schema called CUSTOM is used in XML format in a production, a hl7_CUSTOM lookup table must be created containing all needed mappings.

Segment fields with dynamic data structures

A segment field that has a dynamic data structure can be defined using a custom HL7 schema.
For instance: if it's needed to have an OBX.5 field with a data structured defined by OBX.2 field:

• Create a new HL7 schema copying 2.5.HL7 in Studio.
• Mark the new HL7 schema as standard with std=1 to allow non-resolved data structure references.

<Category name="CUSTOM" std="1">

• Find OBX segment structure definition and change field 5 datatype to @2 that means that it will take the datatype defined in OBX.2.

<SegmentSubStructure piece='5' description='Observation Value' datatype='@2' symbol='&' required='C' ifrepeating='1'/>