Document Types Are Mapped Incorrectly - HL7 Module - English - Foundation 22.1 - OnBase - Essential - Premier - Standard - external - Essential - Standard - Premier

HL7 Module
Platform
OnBase
Product
HL7 Module
Release
Foundation 22.1
License
Essential
Standard
Premier

For the Document Update Processor to re-index a document to another Document Type, the HL7 message must provide a value that resolves to a single Document Type in OnBase. The Document Update Processor will fail to re-index a document if the $$DOCTYPE value in the HL7 message cannot be resolved to a Document Type.

  1. Determine where the $$DOCTYPE value is mapped in the message template.
    1. In OnBase Configuration, select Medical | HL7 | Import Process.
    2. Select the import process that generated the error.
    3. Click Settings.
    4. Under Message Type Information, click View Mappings.
    5. In the User Defined column, look for $$DOCTYPE. Take note of the field mapped to this value.
    6. Click OK.
  2. Determine whether the failed HL7 message provided a valid Document Type identifier in the $$DOCTYPE field.
    1. Open hl7failedmessages.txt.
    2. Find the error description.
    3. Identify the failed Document Type value, which is specified in brackets. In following example, the failed Document Type value is TX.
      HL7 Inbound processor [Update Document Processor]:The document type [TX] in the $$DOCTYPE mapped field could not be identified.
  3. Check how the message action is configured to identify Document Types.

    • If the message action is configured using the Change Document Type based on exact match with $$DOCTYPE option, then the $$DOCTYPE value must exactly match the name of a Document Type in OnBase.

    • If the message action is configured using the Use Document Type mapping option, then the $$DOCTYPE value must be mapped to a Document Type in OnBase.

  4. Take corrective action.

    If the HL7 message placed the Document Type identifier in the wrong field, do one of the following:

    • If the sending application is configured incorrectly, update it to place Document Type identifiers in the $$DOCTYPE field.

    • If OnBase needs to respect the sending application's configuration, configure the message template to look for the $$DOCTYPE in the appropriate field.

    If the HL7 message provided an invalid Document Type identifier, do one of the following:

    • If the sending application is sending $$DOCTYPE values in the wrong format, update it to provide the expected values.

    • If OnBase needs to respect the sending application's values, update the Document Type mapping or the system's Document Type names to correctly resolve the $$DOCTYPE values to Document Types.

    Note:

    If you reconfigure OnBase, consider whether the message template is used for other sending applications. You may need to first copy the message template and the TXA segment to accommodate the sending application's unique configuration. Once the copied message template is configured, create a new import process using the copied message template, and configure a filter in the import process's Sending Application field.