INCLUDE
The Translation Configurator supports the INCLUDE action.
Many times, there are numerous xlates in an HL7 translation, including
ADT_A01.xlt, ADT_A02.xlt
, ADT_A03.xlt
, and so on.
In these xlates, the transformation for PID segment is the same. In this instance,
if you have a modification on a PID field you must modify each xlate, which can be
time-consuming.
With the INCLUDE action, you can use a reference in the xlate. You only create one xlate for the PID translation and refer to it in the other xlates.
There are two steps to using the INCLUDE action:
- Configure the sub-transactions. You can configure these on the segment level, for example, a PID segment in HL7.
- Click INCLUDE and add the defined sub-transactions in an actual transaction.
In the Translation Configurator, the INCLUDE action is accessed from the toolbar or the
list.The nested INCLUDE is supported.
Prefix substitution
You can define the prefixes in the Source and Destination fields. Prefixes are used to replace the group prefixes in sub-translation with specified ones in the current translation configuration.
The prefixes support multi-replacement pairs.
BOX Manager, Site Document, and CLAPI
The BOX Manager can package included xlt files that include other xlt files.
The Site Document supports xlt files and the INCLUDE action.
The clapi-xlate project supports the INCLUDE action as:
CloverXaSend extends AbstractCloverXltAction<Xainclude>
Example: Include a translation
Many times, there are numerous xlates in an HL7 translation, including ADT_A01.xlt, ADT_A02.xlt, ADT_A03.xlt, and so on. In these xlates, the transformation for PID segment is the same. In this instance, if you have a modification on a PID field you must modify each xlate, which can be time-consuming.
With the INCLUDE action, you can use a reference in the xlate. You only create one xlate for the PID translation and refer to it in the other xlates.