Skip to main content

RADplus 2023 Update 116

  1. Last updated
  2. Save as PDF

Product Requirements and Recommendations

RADplus required

Recommended Update Level

RADplus 2022 Update 16
RADplus 2023 Monthly Release 2023.03.00

Product Update Description

An issue where Rule Based Routing documents stored by Perceptive may not display is resolved.

Required Updates

None

Included Updates

None

Details
NEW0 CHANGED0 FIXED1
Fixed (1)
Rule Based Routing - Perceptive documents
An issue where Rule Based Routing documents stored by Perceptive may not display is resolved.
Topics
• Document Routing • Rule Based Routing
 
Acceptance Tests
AV-88691 Summary | Details
Rule Based Routing - Perceptive documents
Scenario 1: Validate 'Rule Based Routing' document routing functionality
Specific Setup:
  • Multiple users must be created with access to all forms: USER A, USER B, USER C, and USER D.
  • A user modeled form must be imported that has 'Service Documentation' fields or a progress note form must be used.
  • Document routing must be enabled for this form.
  • The 'Rule Based Routing' widget must be added to the myDay view.
  • Must create four roles in the 'Routing Role Definition' form.
  • Must assign users with each of the roles created in the 'Routing Role Assignment' form.
  • Must create queues and assign a form to them in the 'Routing Queue Definition' form (Queue 1, Queue 2, and Queue 3).
  • Must create statuses associated with each queue in the 'Routing Status Definition' form.
  • Must configure each queue in the 'Routing Assignment Definition' form.
  • Must select a form in the 'Routing Configuration Definition' form (For example Ambulatory Progress Notes).
  • Must configure header fields and worklist widget details for each queue in the 'Routing Views Definition' form.
  • Must have specific actions configured to route documents to subsequent queues in the 'Routing Action Definition' form.
  • Must be signed in as User A.
Steps
  1. Select any desired client (Client A) and access the 'Ambulatory Progress Notes' form.
  2. Select any value in the 'Progress Note For' field.
  3. Select any value in the 'Note Type' field.
  4. Populate all required and desired fields.
  5. Select "Final" in the 'Draft/Final' field.
  6. Click [Submit] and [Sign and Route/Notify].
  7. Input password associated with "User A" and click [Verify].
  8. Select the practitioner associated with "User A" in the 'Approver' field.
  9. Click [Add] and [Submit].
  10. Navigate to the 'My To-Do's' widget.
  11. Validate the document filed is in the 'Documents to Sign' column.
  12. Click [Review].
  13. Validate the document opens.
  14. Click [Accept] and [Sign].
  15. Enter the password associated with "User A" and click [Verify].
  16. Logout.
  17. Login with "User B".
  18. Navigate to the 'Rule Based Routing' widget.
  19. Select "Queue 1" in the queue field.
  20. Select the entry associated with "Client A".
  21. Click [Launch Worklist Item].
  22. Fill out the desired and required fields.
  23. Click [Save for Later].
  24. Validate the entry is now "In Process" in the 'Status' field.
  25. Select the item again and click [Launch Worklist Item].
  26. Click [Submit].
  27. Refresh the 'Rule Based Routing' widget.
  28. Validate the entry is no longer present.
  29. Logout.
  30. Login with "User C".
  31. Navigate to the 'Rule Based Routing' widget.
  32. Select "Queue 2" in the queue field.
  33. Select the entry associated with "Client A".
  34. Click [Launch Worklist Item].
  35. Fill out the desired and required fields.
  36. Click [Submit].
  37. Refresh the 'Rule Based Routing' widget.
  38. Validate the entry is no longer present.
  39. Logout.
  40. Login with "User D".
  41. Navigate to the 'Rule Based Routing' widget.
  42. Select "Queue 3" in the queue field.
  43. Select the entry associated with "Client A".
  44. Click [Launch Worklist Item].
  45. Fill out the desired and required fields.
  46. Click [Submit].
  47. Refresh the 'Rule Based Routing' widget.
  48. Validate the entry is now "Completed" in the 'Status' field.
  49. Logout.
Topics
• Document Routing • Rule Based Routing