File Formats for HL7 Transcription Documents - HL7 Module - Foundation 23.1 - Foundation 23.1 - Ready - OnBase - Essential - Premier - Standard - external - Essential - Standard - Premier

Although the HL7 message is ASCII text, you can create several different types of Document Types using transcription data:

• By assigning Document Types with formats of RTF, Word (.rtf), HTML, or XML, you can create formatted documents, as long as the data in the OBX segment is supplied using the formatting codes appropriate for the file type.

  Note:

  If you choose to save the data to RTF, Word (.rtf), HTML, or XML Document Types, no characters will be parsed out of the OBX.5 (not even the ~, which is standard HL7 formatting).

• If the data is marked as Text data, and you save the data to a Text Report Format, OnBase will strip out all formatting characters. For text transcriptions, the HL7 message must provide one of the following values in the OBX.2 field: ST, FT, TXT, or TX.

• You can also, optionally, include HL7-defined formatting characters in the fields (see below for supported values) when saving the data as Text Report Format Document Types.

• Transcription import processes allow you to map Document Types to specific HL7 codes. If you use Document Type mapping, ensure the HL7 code is mapped to the appropriate file type for the segment. For example, if the HL7 code TXT means that the segment contains pure text, then the TXT code must be mapped to a file type of Text Report Format.

• If Document Type mapping is not used, then the configured Document Type must be based on a File Format that corresponds to the format of the segment.