Designing a Correction Process - Signature Deficiencies for Epic - English - Foundation 22.1 - OnBase - external

Signature Deficiencies for Epic

Platform
OnBase
Product
Signature Deficiencies for Epic
Release
Foundation 22.1
License

The following are a few examples of document correction processes. You can model your process off one or more of these examples, or you can design your own approach.

  • When users submit a document for correction, display a form requesting additional information about the necessary changes. OnBase Workflow can use the values to route both the form and the submitted document to the appropriate queue.

  • When users submit a document for correction, prompt them with a note requesting an explanation for the submission. The note also can serve to notify other users that the document has been submitted for correction.

  • Create multiple correction actions, each one dedicated to a specific type of correction (for example, correcting the MRN, or reordering pages). Map each action to a Workflow life cycle dedicated to that type of correction.

In the following example, the Analysis window presents the user with a form requesting the correction reason. Workflow adds a note to indicate the document has been submitted.

Continue to the following topics for more information: