Translation tables allow you to translate raw HL7 values before using them to index documents or medical records charts. For inbound messages, HL7 translation tables can convert HL7 codes into values that can be used for Keywords, E-Forms, and chart metadata. For outbound messages, translation tables can translate OnBase values into HL7 codes.
Translations occur for all repetitions of a field.
For example, a message's Patient Class(PV1.2) value is represented by a single letter, such as I for Inpatient. Using translation tables, OnBase can receive an HL7 message with the value I and interpret the value as the full word Inpatient. When sending a message for a document that has a Keyword Value of Inpatient, OnBase can translate the Keyword Value to I in the outbound message.
It is considered a best practice to create a translation table for translating the Patient Sex value (PID.8) in outbound messages. In OnBase, the Patient Sex on charts is designated a value of 0 (Unknown), 1 (Male), or 2 (Female). A translation table can change outbound messages to use the values expected by other applications.
Once a translation table is created, it can be assigned to fields in HL7 message templates. For example, if you create a translation table for patient classes, you can assign the translation table to the Patient Class field (PV1.2). When assigning a translation table to a field, you can specify whether the table should be used to translate inbound values, outbound values, or both.