If the chart should be sent to a Workflow life cycle upon creation, select the Workflow system task you configured to route the chart to the life cycle.
The HL7 Back-end Job Processor must be running in order to add the chart to Workflow. The OnBase Client must also be set up to use Core-based Workflow. For information about Core-based Workflow, see the Workflow module reference guide or help files. Charts created using this option will not transition to an inactive or closed status until the HL7 Back-end Job Processor runs.
It is considered a best practice to only use the Workflow System Task option to send charts to an MRM queue where the MRM Queue type is set to <None>. Do not configure this option to send charts to an Analysis or Coding queue on systems using OnBase Workflow for Medical Records Analysis or Coding.
Configuring the HL7 import process to send charts to Analysis or Coding could cause problems if the import process receives an update message. In this case, the system task may run on existing charts, sending them to a Workflow queue when they should not be.
To use the preferred method for sending charts to an Analysis or Coding Workflow queue, designate the appropriate system tasks under Medical | Workflow | MRMS Queue System Tasks in OnBase Configuration.
If the Workflow System Task is configured, HL7 update messages can cause existing charts to re-enter Workflow. To prevent this behavior, configure the system task to check whether the chart has already passed through the specified Workflow queue. This configuration can prevent a chart from entering a Workflow queue multiple times. If some charts should re-enter Workflow and others should not, configure two import processes for chart processing, each with different HL7 filtering options applied. In this case, one import process can allow charts that meet the filter criteria to re-enter Workflow, while the other import process can prevent charts from re-entering Workflow. For configuration assistance, contact your solution provider.