Skip to main content

RADplus 2022 Update 101

  1. Last updated
  2. Save as PDF

Product Requirements / Recommendations

RADplus required

Product Update Form Description

The following issues are resolved: 1) Cosigning on the 'Sign' tab of the 'My To Do's' widget does not update the DocR.document_history table correctly. 2) To dos showing on the 'Sign' tab of the 'My To Do's' widget for programs not assigned to the logged in system code. 3) The error '[SUBSCRIPT]LicenseAndConnection+16^GUIMetricCalls2' when clicking the 'Test Metrics Collections' button on the 'Guardiant' form.

Included Updates

2, 23, 35, 46, 48, 62, 72, 81, 91, 93

Required Updates

None

Details
NEW0 CHANGED0 FIXED3
Fixed (3)
DocR.document_history table
An issue is resolved to ensure the value in the "User_id" field of the "DocR.document_history" table is updated, if the user approving the 'To Do' is a co-signer
Topics
• My To Do's
 
My To Do's Widget - Sign Tab
An issue is resolved to ensure a user can search and display To Do's in the "Sign" tab of the "My To Do's" widget, for only To Do's associated with "Programs" assigned to the logged in system code KB0068645 v0.01
Topics
• My To Do's • NX
 
Guardiant - Form
An issue is resolved to ensure successful execution of 'Test Metrics Collections' within the 'Guardiant' form.
Topics
• Guardiant • NX
 
Acceptance Tests
AV-73995 Summary | Details
DocR.document_history table
Scenario 1: Validate data in 'DocR.document' table
Specific Setup:
  • [UserA] is a staff member and also has permissions to co-sign to do's for other staff members
  • [UserB] is a staff member and has the 'My To Do's' widget on the Home View.
  • A client [ClientA] is enrolled in an open episode
  • Document routing is enabled for a form [FormA]. For example, a progress note or modeled form
  • Have a report [ReportA] to display data in the "DocR.document_history" table
  • Log in as [UserB]
Steps
  1. Access [FormA]
  2. Select [ClientA] in the 'Select Client' field.
  3. Select [Episode1] where the client is enrolled in [ProgramA]
  4. Populate all required fields any desired fields in the form
  5. Select "Final" in the 'Draft/Final' field.
  6. Click [File Note].
  7. Validate that the 'Confirm Document' dialog is displayed with expected data
  8. Click [Accept and Route].
  9. Validate the 'Route Document To' dialog is displayed.
  10. Select the [UserA] as the 'Approver'.
  11. Click [Submit].
  12. Validate submission is successful
  13. Navigate to the 'My To Do's' widget.
  14. Select the "Sign" tab.
  15. Validate the 'Search Documents' field contains a row for the To do document routed in step 1
  16. Log out as [UserB]
  17. Log in as [UserA]
  18. Navigate to the 'My To Do's' widget.
  19. Select the "Sign" tab.
  20. Search for [UserA] in the "Staff" field
  21. Validate the To do document routed to [UserA] in step 1 is listed in the "Search Document" list box
  22. Select the To Do row
  23. Click [Accept].
  24. Validate the row is moved from the "Search Documents" section to the "Accepted Documents" section
  25. Select the row in the "Accepted Documents" section
  26. Validate the document preview, contains the expected data
  27. Click [Sign All]
  28. Enter the password for [UserA] in the 'Verify Password' dialog and click [OK].
  29. Validate the 'Accepted Documents' field no longer contains the To do. (Note the approval submission date and time).
  30. Launch [ReportA]
  31. In the "Action Date" and "Action Time" columns, locate the row based on the approval submission date and time noted in step 5
  32. Validate the "User_Task" column indicates "Approver" and the "UserID" column indicates the user ID or [UserA], the co-signer
Topics
• My To Do's
AV-75858 Summary | Details
My To Do's Widget - Sign Tab
Scenario 1: 'My To Do's' widget - Validate approving documents from the "Sign" Tab
Specific Setup:
  • Have a system with a root system code [RootA] and sub system code defined [SubA]
  • [SubA] is set up to be restricted to only [ProgramA]
  • [UserA] is a staff member and also has permissions to co-sign to do's for other staff members
  • A client [ClientA] is enrolled in [ProgramA] in [Episode1] and [ProgramB] in [Episode2]
  • Document routing is enabled for a form[FormA]. For example a progress note or modeled form
  • [UserA] has access to log into [SubA] but does not have access to [RootA]
  • [UserB] has access to [SubA] and [RootA]
  • Both users have the 'My To Do's' widget on the Home View.
  • Log in as [UserB]
Steps
  1. Access [FormA]
  2. Select [ClientA] in the 'Select Client' field.
  3. Select [Episode1] where the client is enrolled in [ProgramA]
  4. Populate all required fields any desired fields in the form
  5. Select "Final" in the 'Draft/Final' field.
  6. Click [File Note].
  7. Validate that the 'Confirm Document' dialog is displayed with expected data
  8. Click [Accept and Route].
  9. Validate the 'Route Document To' dialog is displayed.
  10. Select the [UserB] as the 'Approver'.
  11. Click [Submit].
  12. Validate submission is successful
  13. Return to [FormA]
  14. Select [ClientA] in the 'Select Client' field.
  15. Select [Episode2] where the client is enrolled in [ProgramB]
  16. Repeat steps1c thru e
  17. Validate routing and submission is successful
  18. Navigate to the 'My To Do's' widget.
  19. Select the "Sign" tab.
  20. Validate the 'Search Documents' list box contains the row for the To Do routed for [Episode1] / [ProgramA] and a row for the To Do document routed for [Episode2] / [ProgramB]
  21. Log out as [UserB]
  22. Log in as [UserA] to sub code [SubA]
  23. Navigate to the 'My To Do's' widget.
  24. Select the "Sign" tab.
  25. Search for [UserA] in the "Search Documents" field
  26. Validate the To Do document routed for [Episode1] / [ProgramA] in step 1
  27. Validate the To Do document routed for [Episode2] / [ProgramB] in step 2 is not present, as sub code [SubA] is restricted to only episodes admitted in [ProgramA]
  28. Select the To Do row
  29. Click [Accept].
  30. Validate the row is moved from the "Search Documents" section to the "Accepted Documents" section
  31. Select the row in the "Accepted Documents" section
  32. Validate the document preview, contains the expected data
  33. Click [Sign All]
  34. Enter the password for [UserA] in the 'Verify Password' dialog and click [OK].
  35. Validate the 'Accepted Documents' field no longer contains the To Do row for [Episode1] / [ProgramA]
  36. Log out as [UserB] and login as [UserA]
  37. Access the 'Clinical Document Viewer' form.
  38. Select "Client" in the 'Select All or Individual Client' field.
  39. Select [ClientA] in the 'Select Client' field.
  40. Click [Process].
  41. Validate the document row for the To Do approved in step 4 is present
  42. Double click on the row
  43. Validate the document preview, contains the expected data
  44. Close the form.
Topics
• My To Do's • NX
AV-81280 Summary | Details
Guardiant - Form
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Guardiant
Scenario 1: Guardiant form - Field validations
Specific Setup:
  • Have a system configured for "Guardiant" reporting
  • Have a user with access to the "Guardiant" form
Steps
  1. Open form "Guardiant"
  2. Click the "Guardiant Configuration" section
  3. Click [Test Connectivity]
  4. Validate message "Connectivity Test Successful" is displayed
  5. Click [OK]
  6. Click [Test Daily Collection]
  7. Click [Yes] to the warning message
  8. Validate message "Test Succeeded" is displayed
  9. Click [Test Metrics Collection]
  10. Click [Yes] to the warning message
  11. Validate message "Test Succeeded" is displayed
  12. Click "Export Configuration"
  13. In "File Explorer", select a directory to save file
  14. Click [Save]
  15. Go to the directory where the file was saved
  16. Open the "GuardiantConfiguration.txt" file
  17. Validate data is present in the file
Topics
• Guardiant • NX

 

  1. Back to top
  • Was this article helpful?

Recommended articles

  1. Page type
    Reference
  2. Tags
    1. content:release
    2. Guardiant
    3. llm-no-index
    4. My To Do's
    5. NX
    6. nx:nx
    7. role:sysadmin
    8. search:ready