Rule Based Routing - Multiple iteration tables
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
- Admission (Outpatient)
- Dynamic Form - Admission - Client
- Dynamic Form - document routing - sign
- Dynamic Form - document routing - verify password
- Dynamic Form - Progress Notes
- Financial Eligibility
- Routing Assignment Definition
- Routing Configuration Definition
- Routing Queue Definition
- Routing Role Assignment
- Routing Role Definition
- Routing Views Definition
- Rule Based Routing
- Routing Status Definition
- Routing Worklist Item
Scenario 1: Rule Based Routing - Validating data in the multiple iteration tables of the 'Clinical Document QA' form upon form submission.
Specific Setup:
- The system is set up for Rule based routing with a queue functionality.
- The 'Rule Based Routing' widget is placed on HomeView.
- Any progress note form is set up for the document routing (i.e., Progress Notes (Group and Individual)). Note the form name and product name where it is created for further testing. Please Note: The 'Clinical Document QA' form used in this test as it contains multiple iteration table in the form.
- Document Routing Setup:
- Document routing functionality is enabled for the 'Medical Coding Note' form.
- Routing Role Definition:
- Must have an active routing role created in the form (i.e., Admin, Document QA). Note the roles.
- Routing Queue Definition:
- Must have an active queue set up for the form with the multiple iteration table (i.e., Coding QA). Note the name of the queue for further testing.
- Routing Assignment Definition:
- Two routing assignments are created such that one assignment that completes a workflow and one that doesn't. Note the name of the assignments.
- Routing Configuration Definition:
- The 'Product' field is set to the product where the progress note form exists (i.e., CWS). Note the value for further testing.
- The progress note form configured above is selected in the 'Form' field. Note the name of the form for further testing.
- The queue created is selected in the 'Initial Assignment' field (i.e., Coding QA). Note the name of the queue for further testing.
- Select 'Yes' in the 'Active' field.
- Desired value is selected in the 'Initial Service Status' field. Note the value for further validation.
- Desired value in the 'Coding Complete Service Status' fields. Note the value for further testing.
- Apply Status without Coding Form Submission = 'No'. Note the value for further testing.
- Routing Views Definition:
- Desired columns are defined to display in the 'Rule Based Routing' widget.
- User Definition:
- A staff member is associated with the current user. Note the password for the user.
- Guarantor:
- An existing guarantor is identified. Note the guarantor’s code/name.
- Admission:
- An existing outpatient client is identified with the guarantor assigned to the client. Note the Client ID/name, Admission program, Admission date.
- Service Code:
- An existing professional service code is identified. Note the service code.
- Service Fee/Cross Reference Maintenance Form:
- The service fee and HCPCS code are defined for the service code identified above.
- Progress Note Group and Individual:
- A final note is filed for the client using 'New Service' option. Note the date of the service.
Steps
- Locate the 'Rule Based Routing' widget.
- Select desired queue from the 'Queue' dropdown list.
- Select 'All Statuses' from the 'Status' dropdown.
- Click [Refresh].
- Verify the document finalized from the 'Progress Notes (Group and Individual)' in the setup is available in this widget.
- Select the document recently created through the 'Progress Note Group And Individual' form.
- Select the desired document.
- Click [Launch Worklist Item].
- Verify the 'Clinical Document QA' form launched successfully from the widget.
- Enter data for the missing and Incorrect code type in the multi iteration table.
- Click [Save For Later].
- Verify the system successfully navigates to the home view.
- Locate to the 'Rule Based Routing' widget.
- Select desired queue from the 'Queue' dropdown list.
- Select 'All Statuses' from the 'Status' dropdown.
- Click [Refresh].
- Select the document recently saved.
- Click [Launch Worklist Item].
- Verify the 'Clinical Document QA' form launched successfully from the widget.
- Verify the multiple iteration table retains data correctly as entered.
- Click [Save For Later].
- Verify the system successfully navigates to the home view.
Scenario 2: Rule Based Routing - Validating data in the multiple iteration tables of the 'Coding QA' form upon form submission.
Specific Setup:
- The system is set up for Rule based routing with a queue functionality.
- The 'Rule Based Routing' widget is placed on HomeView.
- Document Routing Setup:
- Any progress note form is set up for the document routing (i.e., Progress Notes (Group and Individual)). Note the form name and product name where it is created for further testing.
- Please Note: The 'Coding QA' form used in this test as it contains multiple iteration table in the form.
- Routing Role Definition:
- Must have an active routing role created in the form (i.e., Admin, Document QA). Note the roles.
- Routing Queue Definition:
- Must have an active queue set up for the form with the multiple iteration table (i.e., Clinical Document QA, Coding QA). Note the name of the queue for further testing.
- Routing Assignment Definition:
- Two routing assignments are created such that one assignment that completes a workflow and one that doesn't. Note the name of the assignments.
- Routing Configuration Definition:
- The 'Product' field is set to the product where the progress note form exists (i.e., CWS). Note the value for further testing.
- The progress note form configured above is selected in the 'Form' field. Note the name of the form for further testing.
- The queue created is selected in the 'Initial Assignment' field (i.e., Clinical Document QA). Note the name of the queue for further testing.
- Select 'Yes' in the 'Active' field.
- Desired value is selected in the 'Initial Service Status' field. Note the value for further validation.
- Desired value in the 'Coding Complete Service Status' fields. Note the value for further testing.
- Apply Status without Coding Form Submission = 'No'. Note the value for further testing.
- Routing Views Definition:
- Desired columns are defined to display in the 'Rule Based Routing' widget.
- User Definition:
- A staff member is associated with the current user. Note the password for the user.
- Guarantor:
- An existing guarantor is identified. Note the guarantor's code/name.
- Admission:
- An existing outpatient client is identified with the guarantor assigned to the client. Note the Client ID/name, Admission program, Admission date.
- Service Code:
- An existing professional service code is identified. Note the service code.
- Service Fee/Cross Reference Maintenance Form:
- The service fee and HCPCS code are defined for the service code identified above.
- Progress Note Group and Individual:
- A final note is filed for the client using 'New Service' option. Note the date of the service.
Steps
- Locate the 'Rule Based Routing' widget.
- Select desired queue from the 'Queue' dropdown list.
- Select 'All Statuses' from the 'Status' dropdown.
- Click [Refresh].
- Verify the document finalized from the 'Progress Notes (Group and Individual)' in the setup is available in this widget.
- Select the document recently created through the 'Progress Note Group And Individual' form.
- Select the desired document.
- Click [Launch Worklist Item].
- Verify the 'Coding QA' form launched successfully from the widget.
- Enter data for the missing and Incorrect code type in the multi iteration table.
- Click [Save For Later].
- Verify the system successfully navigates to the home view.
- Locate to the 'Rule Based Routing' widget.
- Select desired queue from the 'Queue' dropdown list.
- Select 'All Statuses' from the 'Status' dropdown.
- Click [Refresh].
- Select the document recently saved.
- Click [Launch Worklist Item].
- Verify the 'Coding QA' form launched successfully from the widget.
- Verify the multiple iteration table retains the correct information as entered.
- Click [Save For Later].
- Verify the system successfully navigates to the home view.
|
Topics
• NX
• Rule Based Routing
|
