Skip to main content

RADplus 2023 Update 86

  1. Last updated
  2. Save as PDF

Product Requirements and Recommendations

RADplus required

Recommended Update Level

RADplus 2022 Update 91
RADplus 2023 Monthly Release 2023.03.00

Product Update Description

The following issues are resolved: 1) The form 'Document Management Form Re-Mapping' is updated to correctly check other connected root system codes. 2) A "JPGTemp Deletion Failure" error would be erroneously recorded in the error log in certain cases. 3) The "[UNDEFINED]GetLists+125^DocRoutingAPI2" error that can occur on the document routing screen when 'Notification List Defaults' is set to "Default from Last Filing" in the routing setup.

Required Updates

None

Included Updates

2, 4, 6, 7, 12, 13, 14, 22, 25, 26, 29, 33, 35, 49, 55, 56, 58, 59, 64, 71, 75, 80

Details
NEW0 CHANGED0 FIXED3
Fixed (3)
Document Management Form Re-Mapping
The 'Re-Map Synced Facilities' functionality available for "Perceptive" enabled systems in the (Netsmart Internal) form "Document Management Form Re-Mapping", is updated to ensure that connected root system codes are always checked when the process is executed.
Topics
• Document Routing
 
Document Routing
An issue is resolved where an erroneous error could be left in the error log file, after a document had been created during the document routing process
Topics
• Document Routing • NX
 
Document Routing - Default From Last Filing
An issue is resolved to ensure a form enabled for document routing with "Default From Last Filing" selected in prompt "Notifications List Defaults", can be submitted successfully
Topics
• Document Routing
 
Acceptance Tests
AV-83289 Summary | Details
Document Management Form Re-Mapping
Scenario 1: Document Management Form Re-Mapping (Re-Map Synced Facilities)
Steps
  1. Internal Testing Only
Topics
• Document Routing
AV-90747 Summary | Details
Document Routing
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Clinical Document Viewer
  • Print Error Log (PM)
Scenario 1: Document Routing - (Route) a document
Specific Setup:
  • Have any form [TestForm] enabled for document routing, for this example a Modeled form will be used
  • [TestUser] is a staff member with access to [TestFom] and has the "My To Do's" widget on their home view
  • Log in as [TestUser]
Steps
  1. Access [TestForm] for any client [TestClient]
  2. Populate the desired fields on the form
  3. Select "Final" in the 'Draft/Final' field.
  4. A message displays indicating "Selecting Final prevents future edits".
  5. Click [OK] and [Submit].
  6. Verify the document preview displays the data as expected
  7. Click [Accept].
  8. Enter the password for the user in the 'Password' field
  9. Validate the form submits successfully to create the document [TestDoc]
  10. Access the 'Clinical Document Viewer' form.
  11. Enter [TestClient] in the 'Select Client' field.
  12. Locate [TestDoc] in the document results list
  13. Click [View] to display the document
  14. Verify the document preview displays the data as expected
  15. Close the form.
  16. Open form "Print Error Log"
  17. Enter today's date in the date fields
  18. Click [Submit]
  19. Validate there are messages relating to document created in step 1
Scenario 2: Document Routing - (Accept & Route) a document
Specific Setup:
  • Have any form [TestForm] enabled for document routing, for this example a Modeled form will be used
  • [TestUser] is a staff member with access to [TestFom] and has the "My To Do's" widget on their home view
  • Log in as [TestUser]
Steps
  1. Access [TestForm] for any client [TestClient]
  2. Populate the desired fields on the form
  3. Select "Final" in the 'Draft/Final' field.
  4. A message displays indicating "Selecting Final prevents future edits".
  5. Click [OK] and [Submit].
  6. Verify the document preview displays the data as expected
  7. Click [Accept and Route].
  8. Enter the password for the user in the 'Password' field
  9. Click [OK].
  10. In the "Route Document To" screen, select [TestUser] in the "Add Approver" search field and click [Add]
  11. Click [Submit] to route the document [TestDoc]
  12. Navigate to the 'My To Do's' widget.
  13. Locate the To Do for document just routed [TestDoc]
  14. Click [Approve Document]
  15. Verify the document preview displays the data as expected
  16. Click [Accept].
  17. Enter the password for the user in the 'Password' field.
  18. Click [OK].
  19. Validate the "To Do" has been removed from the "My To Do's" widget
  20. Access the 'Clinical Document Viewer' form.
  21. Enter [TestClient] in the 'Select Client' field.
  22. Locate [TestDoc] in the document results list
  23. Click [View] to display the document
  24. Verify the document preview displays the data as expected
  25. Close the form.
  26. Open form "Print Error Log"
  27. Enter today's date in the date fields
  28. Click [Submit]
  29. Validate there are messages relating to document created in step 1
Topics
• Document Routing • NX
AV-90891 Summary | Details
Document Routing - Default From Last Filing
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Review To Do Item
Scenario 1: Doc Routing -Default Notification User from Last Filing (Send to 'Non-Staff' enabled)
Specific Setup:
  • Have a form [TestForm] set up in form "Document Routing Setup" with following prompts set:
  • 'Enable Document Routing' se to 'Yes'.
  • 'Allow Notifications When Final' set to 'Yes'.
  • 'Notification List Defaults' set to 'Default From List Filing'
  • Have "Registry setting" 'Allow sending notifications to non-staff users' set to "Y".
  • [UserA] has access to [TestForm] and form 'Registry Settings'
  • [UserB] is a Staff member and has the "My To Do's" widget on their home view
  • [UserC] is not a Staff member and has the "My To Do's" widget on their home view
  • Log in as [UserA]
Steps
  1. Access [TestForm] and select any client [TestClient]
  2. Populate all desired fields on the form.
  3. Select "Final" in the 'Draft/Final' field.
  4. Click [Accept and Route/Notify]
  5. Enter the user's password in the 'Password' field.
  6. Click [OK].
  7. On the "Route To Document" screen, navigate to the "Add Users to Notify when Final" search box
  8. Search for [UserB]
  9. Validate the user is found
  10. Click [Add] to have [UserB] receive a To do notification
  11. Search for [UserC]
  12. Validate that [UserC] is found as expected based on the setup
  13. Click [Add] to have [UserC] receive a To do notification
  14. Click [Submit]
  15. Validate the form files successfully
  16. Repeat step 1 a thru e
  17. On the "Route To Document" screen, navigate to bottom where the approvers and notifiers are listed
  18. Validate the [UserB] has been automatically defaulted as a notifier and the "Notify" check box is populated
  19. Validate the [UserC] has been automatically defaulted as a notifier and the "Notify" check box is populated
  20. Click [Submit]
  21. Validate the form files successfully
  22. Log in as [UserB]
  23. Navigate to the "My To Do's" widget
  24. Click to refresh the widget
  25. Click the "New" tab
  26. Validate there are two new notification To Do's for review, for [TestForm] submitted in step 1
  27. Click to open each To Do
  28. Validate the "To Do Information" box contains the expected data
  29. Click the "Reviewed" check box
  30. Click [Submit]
  31. Validate submission is successful and each To Do has been removed form the To Do's list
  32. Log out as [UserB]
  33. Log in as [UserC]
  34. Navigate to the "My To Do's" widget
  35. Click to refresh the widget
  36. Click the "New" tab
  37. Validate there are two new notification To Do's for review, for [TestForm] submitted in step 1
  38. Click to open each To Do
  39. Validate the "To Do Information" box contains the expected data
  40. Click the "Reviewed" check box
  41. Click [Submit]
  42. Validate submission is successful and each To Do has been removed form the To Do's list
Scenario 2: Doc Routing -Default Notification User from Last Filing (Send to 'Non-Staff' user disabled)
Specific Setup:
  • Have a form [TestForm] set up in form "Document Routing Setup" with following prompts set:
  • 'Enable Document Routing' se to 'Yes'.
  • 'Allow Notifications When Final' set to 'Yes'.
  • 'Notification List Defaults' set to 'Default From List Filing'
  • Have "Registry setting", "Allow sending notifications to non-staff users" set to "N".
  • [UserA] has access to [TestForm] and form "Registry Settings"
  • [UserB] is a Staff member and has the "My To Do's" widget on their home view
  • [UserC] is not a Staff member and has the "My To Do's" widget on their home view
  • Log in as [UserA]
Steps
  1. Access [TestForm] and select any client [TestClient]
  2. Populate all desired fields on the form.
  3. Select "Final" in the 'Draft/Final' field.
  4. Click [Accept and Route/Notify]
  5. Enter the user's password in the 'Password' field.
  6. Click [OK].
  7. On the "Route To Document" screen, navigate to the "Add Users to Notify when Final" search box
  8. Search for [UserB]
  9. Validate the user is found
  10. Click [Add] to have [UserB] receive a To do notification
  11. Search for [UserC]
  12. Validate that [UserC] is 'not' found as expected based on the setup
  13. Repeat step 1 a thru e
  14. On the "Route To Document" screen, navigate to bottom where the approvers and notifiers are listed
  15. Validate the [UserB] has been automatically defaulted as a notifier and the "Notify" check box is populated
  16. Click [Submit]
  17. Validate the form files successfully
  18. Log out as [UserA]
  19. Log in as [UserB]
  20. Navigate to the "My To Do's" widget
  21. Click to refresh the widget
  22. Click the "New" tab
  23. Validate there are two new notification To Do's for review, for [TestForm] submitted in step 1
  24. Click to open each To Do
  25. Validate the "To Do Information" box contains the expected data
  26. Click the "Reviewed" check box
  27. Click [Submit]
  28. Validate submission is successful and each To Do has been removed form the To Do's list
Topics
• Document Routing