Routing Configuration Definition
This form will define which document routing enabled forms will enter a Rule Based Routing workflow.
The forms need to meet the following criteria:
- The form must be a client entity form.
- The form must have Document routing must be enabled.
- The form must be episodic.
Key Fields
| Field | Notes |
|---|---|
| Form | A form must be selected before proceeding. |
| Initial Assignment | The assignment selected here will determine the first user, queue, and status applied to a document after it is initially finalized. |
| Skip Workflow Field | When the form selected in Routing Queue Definition is a RADplus modeled form, a field on that RADplus modeled form can be selected here to indicate whether the document should be assigned to a Rule Based Routing queue at all. This is useful for assessments that may be finalized in document routing but represent an incomplete encounter/note that should not go through the workflow. |
| Skip Workflow Field Value | (See above) |
| Initial Service Status |
If the document/form defined in the Routing Configuration Definition for includes a service (e.g., a progress note), the Initial Service Status can be defined. This is commonly used to assign a Service Status to inhibit billing while the document/service is going through the rule-based routing workflow. |
| Coding Complete Service Status |
If you specify the Medical Coding form in Routing Queue Definition and when the workflow is complete, the Service Status will update to the value specified here. |
| Apply Status without Medical Coding Form Submission | Selecting Yes allows the Service Status to update to the value defined in the Coding Complete Service Status when the Medical Coding form is not in use. Selecting No means the Medical Coding form must be used for the Coding Complete Service Status to apply. The default is No. |