Rule Based Routing - Encounter Date
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
- Admission (Outpatient)
- Dynamic Form - Admission - Client
- Financial Eligibility
- Medical Coding Note
- Ok - Cancel Dialog
- Routing Assignment Definition
- Routing Configuration Definition
- Routing Queue Definition
- Routing Role Assignment
- Routing Role Definition
- Routing Views Definition
- Routing Worklist Item
- Rule Based Routing Widget (Home View)
- Scheduling Calendar
- DDTT Note w/ Encounter Info
- Client Charge Input
- Registry Settings (PM)
Scenario 1: Rule Based Routing widget - Validating 'Encounter Date' after submitting progress note - New Service
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 'Medical Coding Note' form used in this test is the copy of the progress note and renamed to 'Medical Coding Note'.
- 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.
- Routing Queue Definition:
- Must have an active queue set up where the 'Medical Coding Note' is selected in the 'Form' field. 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. 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.
- Guarantor:
- An existing guarantor is identified.
- 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.
- Medical Coding Note:
- A final note is filed for the client using 'New Service' option.
Steps
- Locate the 'Rule Based Routing' widget.
- Select the queue identified in the setup section.
- Select desired queue from the 'Queue' dropdown list.
- Select 'All Statuses' from the 'Status' dropdown.
- Click [Refresh].
- Verify the document finalized from the 'Medical Coding Note' in the setup is available in this widget.
- Verify the 'Encounter Date' column displays the 'Date of Service' from the medical coding note.
Scenario 2: Rule Based Routing widget - Validating 'Encounter Date' after submitting progress note - Existing Appointment
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 'Medical Coding Note' form used in this test is the copy of the progress note and renamed it to 'Medical Coding Note'.
- 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.
- Routing Queue Definition:
- Must have an active queue set up where the medical coding form is selected in the 'Form' field. 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. 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.
- Guarantor:
- An existing guarantor is identified.
- 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.
- Scheduling Calendar:
- A new appointment is created for the client. Note the date of the appointment.
- Medical Coding Note:
- A final note is filed for the client using 'Existing Appointment' option. The 'Date of Service' field of the medical coding note defaults to the appointment date.
Steps
- Locate the 'Rule Based Routing' widget.
- Select the queue identified in the setup section.
- Select desired queue from the 'Queue' dropdown list.
- Select 'All Statuses' from the 'Status' dropdown.
- Click [Refresh].
- Verify the document finalized from the 'Medical Coding Note' using 'Existing Appointment' option is available in this widget.
- Verify the 'Encounter Date' column displays the 'Date of Service' from the medical coding note that is appointment date of the client.
Scenario 3: Rule Based Routing widget - Validating 'Encounter Date' after submitting modeled form with date/time
Specific Setup:
- The system is set up for Rule based routing with a queue functionality.
- The 'Rule Based Routing' widget is placed on HomeView.
- A modeled form is set up for the document routing. Note the form name and the product name where it is created for further testing. Please Note: The 'DDTT Note w/Encounter Info' form used in this test is the modeled form with date/time.
- Document Routing Setup:
- Document routing functionality is enabled for the 'DDTT Note w/Encounter Info' form.
- Routing Role Definition:
- Must have an active routing role created in the form.
- Routing Queue Definition:
- Must have an active queue set up where the medical coding form is selected in the 'Form' field. 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. 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.
- Guarantor:
- An existing guarantor is identified.
- 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.
- DDTT Note w/Encounter Info:
- A final document is filed for the client.
Steps
- Locate the 'Rule Based Routing' widget.
- Select the queue identified in the setup section.
- Select desired queue from the 'Queue' dropdown list.
- Select 'All Statuses' from the 'Status' dropdown.
- Click [Refresh].
- Verify the document finalized from the 'DDTT Note w/ Encounter Info' in the setup is available in this widget.
- Verify the 'Encounter Date' column displays the 'Date of Service' from the note.
Scenario 4: Rule Based Routing widget - Validating 'Encounter Date' after submitting progress note - Independent Note
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 'Medical Coding Note' form used in this test is the copy of the progress note and renamed it to 'Medical Coding Note'.
- 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.
- Routing Queue Definition:
- Must have an active queue set up where the medical coding form is selected in the 'Form' field. 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. 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.
- Guarantor:
- An existing guarantor is identified.
- 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.
- Medical Coding Note:
- A final note is filed for the client using 'Independent Note' option.
Steps
- Locate the 'Rule Based Routing' widget.
- Select the queue identified in the setup section.
- Select desired queue from the 'Queue' dropdown list.
- Select 'All Statuses' from the 'Status' dropdown.
- Click [Refresh].
- Verify the document finalized from the 'Medical Coding Note' in the setup is available in this widget.
- Verify the 'Encounter Date' column displays the date when the medical coding note is filed.
Scenario 5: Rule Based Routing widget - Validating 'Encounter Date' after submitting progress note - Existing Service
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 'Medical Coding Note' form used in this test is the copy of the progress note and renamed it to 'Medical Coding Note'.
- 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.
- Routing Queue Definition:
- Must have an active queue set up where the medical coding form is selected in the 'Form' field. 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. 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.
- Guarantor:
- An existing guarantor is identified.
- 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.
- Client Charge Input:
- A service is rendered to the client using the service code identified above. Note the service date for further testing.
- Registry setting:
- Set the 'Days After Service Date to Allow a Progress Note' registry setting is set to desired value such that the service rendered to the client in 'Client Charge Input' can be associated in the progress note.
- Medical Coding Note:
- A final note is filed for the client using 'Existing Service' option for the service rendered using 'Client Charge Input' form.
Steps
- Locate the 'Rule Based Routing' widget.
- Select the queue identified in the setup section.
- Select desired queue from the 'Queue' dropdown list.
- Select 'All Statuses' from the 'Status' dropdown.
- Click [Refresh].
- Verify the document finalized from the 'Medical Coding Note' in the setup is available in this widget.
- Verify the 'Encounter Date' column displays the 'Date of Service' from the medical coding note.
|
Topics
• Rule Based Routing
|
