Skip to main content

RADplus 2023 Update 118

  1. Last updated
  2. Save as PDF

Product Requirements and Recommendations

RADplus required

Recommended Update Level

RADplus 2023 Monthly Release 2023.04.00

Product Update Description

The following issues are resolved: 1) The 'Change User ID' form is enhanced to allow a user's ID to be reverted to a previous ID. 2) An issue is resolved where merging users through the User Merge File Import form will cause the SYSTEM.RADplus_user_link table to show that all of the users in the file are linked.

Required Updates

None

Included Updates

None

Details
NEW1 CHANGED0 FIXED1
New (1)
'Change User ID' form
The 'Change User ID' form is enhanced to allow a user's ID to be reverted to a previous ID.
Value Added: Provides the ability reuse a name for user after it had been changed
Topics
• Change User ID
 
Fixed (1)
User Merge File Import
An issue is resolved to ensure the that after merging and creating multiple new users via the "User Merge File Import" form, that the 'SYSTEM.RADplus_user_link' table shows that each new merged user is assigned a unique value in the 'system_link_id' field in the table
Topics
• User Merge
 
Acceptance Tests
AV-91327 Summary | Details
'Change User ID' form
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • User Definition
Scenario 1: "Change User ID" - Validate reverting a UserID to its previous Value
Specific Setup:
  • [ChangedUserB] is a user whose UserID had been changed from [ChangedUserA], via the "Change User ID" form
  • Have a form, for example, a user based product or modeled form [TestForm] that enabled for document routing. For this test product, form "Ambulatory Progress Notes" is used
  • [ChangedUserB] has been routed a "To Do" document for client [TestClient] via form [TestForm] and has approved it, to create the document [TestDoc]
  • [ChangedUserB] has been routed another "To Do" document that is still in their "To Do" list
  • Have a report or query to display data in the "SYSTEM.Doc_documents" table and include the "data_entry_user_id" field [ReportA]
  • Have a report or query to display data in the table used in [TestForm] and include the "data_entry_user_id" field. For this test, the "SYSTEM.cw_patient_notes" table is used [ReportB]
  • A test [TestUser] and [ChangedUserB] have access to forms "Change UserID", "User Definition"
  • Log in as [TestUser]
Steps
  1. Open form "Change UserID"
  2. Select [ChangedUserB] in the "User" field
  3. Validate the "Old User ID" field is populated with [ChangedUserB]
  4. Click the "Previous" radio button in the "New or Previous ID" field
  5. Validate the "Select Previous ID" field is enabled
  6. Click the drop down list
  7. Select the users original ID [ChangedUserA] from the list
  8. Submit the form
  9. Validate the form submits successfully
  10. Open form "User Definition"
  11. In the "Select User" field, search for [ChangedUserB]
  12. Validate a message is displayed "User ID [ChangedUserB] is disabled. Only User Description can be updated"
  13. Click [OK]
  14. Validate the "Deactivate User" field is selected and disabled
  15. In the "Select User" field, search for [ChangedUserA]
  16. Validate the "Deactivate User" field is 'not' selected and the field is enabled
  17. Close the form
  18. Log out as [TestUser]
  19. At the Login screen
  20. Log in as [ChangedUserB]
  21. Validate login is unsuccessful
  22. At the Login screen
  23. Log in as [ChangedUserA] using the password that was assigned to [ChangedUserB]
  24. Validate login is successful
  25. At the Home View, navigate to the "My To Do's" list
  26. Validate the "To Do" for the document routed for [TestForm] is present in their "To Do" list, as expected
  27. Generate the report to display data in the "SYSTEM.Doc_documents" table
  28. Locate the row containing [TestDoc] for [TestClient] submitted in the setup
  29. Validate the "data_entry_user_id" field now indicates [ChangedUserA], as expected
  30. Validate other data fields are populated as expected
  31. Generate the report to display data tabled associated with [TestForm]
  32. Locate the row containing submitted for [TestClient] in the setup
  33. Validate the "data_entry_user_id" field now indicates [ChangedUserA], as expected
  34. Validate other data fields are populated as expected
  35. Open form "User Definition"
  36. In the "Select User" field, search for [ChangedUserA]
  37. Change the password to a new password
  38. Submit the form
  39. Log out as [ChangedUserA]
  40. Log in as [TestUser]
  41. Open form "Change UserID"
  42. Select [ChangedUserA] in the "User" field
  43. Validate the "Old User ID" field is populated with [ChangedUserA]
  44. Click the "Previous" radio button in the "New or Previous ID" field
  45. Validate the "Select Previous ID" field is enabled
  46. Click the drop down list
  47. Select the users original ID [ChangedUserB] from the list
  48. Submit the form
  49. Validate the form submits successfully
  50. Open form "User Definition"
  51. In the "Select User" field, search for [ChangedUserA]
  52. Validate a message is displayed "User ID [ChangedUserA] is disabled. Only User Description can be updated"
  53. Click [OK]
  54. Validate the "Deactivate User" field is selected and disabled
  55. In the "Select User" field, search for [ChangedUserB]
  56. Validate the "Deactivate User" field is 'not' selected and the field is enabled
  57. Close the form
  58. Log out as [TestUser]
  59. At the login screen
  60. Log in as [ChangedUserA]
  61. Validate login is unsuccessful
  62. At the login screen
  63. Log in as [ChangedUserB] using the new password assigned [ChangedUserA] in step 8
  64. Validate login is successful
  65. Generate the report to display data in the "SYSTEM.Doc_documents" table
  66. Locate the row containing [TestDoc] for [TestClient] submitted in the setup
  67. Validate the data_entry_user_id" field now indicates [ChangedUserB], as expected
  68. Validate other data fields are populated as expected
  69. Generate the report to display data tabled associated with [TestForm]
  70. Locate the row containing submitted for [TestClient] in the setup
  71. Validate the "data_entry_user_id" field now indicates [ChangedUserB], as expected
  72. Validate other data fields are populated as expected
Topics
• Change User ID
AV-95555 Summary | Details
User Merge File Import
Scenario 1: User Merge File Import' form (Multiple Users) - create new user
Specific Setup:
  • Have four users for testing
  • [TestUser1], [TestUser2], [TestUser3], [TestUser4],
  • Have a "User Import File" file created [TestImport]
  • Have the import file set up to merge the following users to new user:
  • [TestUser1] and [TestUser2] to a new user [Merged1]
  • [TestUser3] and [TestUser4] to a new user [Merged2]
  • Note: (For file format and requirements for a "User Merge" file, see Wiki page: https://wikihelp.ntst.com/EHR/myAvat...ge_File_Import")
  • Have a report or query to display data in the "SYSTEM.RadPlusUserLink" table
Steps
  1. Open form "User File Import"
  2. Click [Select User Import File]
  3. Navigate to the location of the [TestImport] file
  4. Select the file and click [OK]
  5. In the "User Merge File Scan Results" field, validate there are no messages blocking the import
  6. Click [Process User Merge File]
  7. Validate the merge is successful. [Please Note: by default, the new merged user's temporary password will be their user name after the merge is processed]
  8. Log in as [TestUser1]
  9. Validate login is not successful, as expected
  10. Log in as [TestUser2]
  11. Validate login is not successful, as expected
  12. Using their user name as their temporary password, log in as [Merged1]
  13. Validate the user is prompted to change their password
  14. Enter a new password
  15. Validate login is successful
  16. Repeat step 2 and 3 using [TestUser2] and [TestUser3]
  17. Validate the results are same, as expected
  18. Using their user name as their temporary password, log in as [Merged2]
  19. Validate the user is prompted to change their password
  20. Enter a new password
  21. Validate login is successful
  22. Run the report or query to display data in the "SYSTEM.RadPlusUserLink" table
  23. Locate the row for [Merged1]
  24. Validate the value in the "disable_value" field indicate "No" and note the value in their 'system_link_id" field
  25. Locate the row for [Merged2]
  26. Validate the value in the "disable_value" field indicate "No"
  27. Validate the value in their 'system_link_id" is unique, a different value than what was noted for [Merged1] in step 6a
Topics
• User Merge