Advanced Document Import can assign Document Types to documents based on values in the corresponding HL7 messages. When $$DOCTYPE or $$FILEEXT is mapped as a default value in the HL7 message template, Advanced Document Import can use values provided in that field to identify the appropriate Document Types.
When creating an advanced document import process, the following must be taken into consideration when $$DOCTYPE or $$FILEEXT is mapped:
-
The literal value found in $$FILEEXT is used to determine an appropriate file extension for the file being stored.
-
This is true even if a value of $$DOCTYPE is found.
-
$$DOCTYPE values will never be used to set the file extension.
-
-
$$DOCTYPE will be used to determine an appropriate Document Type and File Format via user-defined mappings. If $$DOCTYPE is not configured or populated, OnBase attempts to use $$FILETYPE values to find a mapping.
-
If $$FILEEXT is not configured or populated, and the OnBase File Format is not associated with a default file extension, the HL7 product will store new files with an ".hl7" file extension. To avoid this default value, configure $$FILEEXT or default file extension for the OnBase File Format.
If the $$DOCTYPE or $$FILEEXT value in an HL7 message is mapped to a Document Type, then Advanced Document Import stores the document using that Document Type. If the value is not mapped, then the default Document Type is used. For more information, see Document Type and File Type Resolution for Advanced Document Import.
If a message has values for both $$DOCTYPE and $$FILEEXT, the $$DOCTYPE mapping is used. To prevent conflict, only one of these variables should be mapped per system.
To map Document Types to HL7 codes: