Skip to main content

RADplus 2023 Update 2

  1. Last updated
  2. Save as PDF

Product Requirements / Recommendations

RADplus required

Recommended Update Level

RADplus 2022 Update 72

Product Update Form Description

The following issues are resolved: 1) Form types not displaying on the list after clicking the 'View Form Types' button in the 'Document Archiving' form if the form types have any document restrictions filed. 2) Documents for episodes associated to programs not assigned to the current system code are listed in the 'Append Documents' form. 3) To dos showing on the 'Sign' tab of the 'My To Do's' widget for programs not assigned to the logged in system code. 4) Co-signing a document routing to do for another practitioner sometimes displays the incorrect signature line.

Included Updates

None

Required Updates

None

Details
NEW0 CHANGED0 FIXED4
Fixed (4)
Append Document
The "Append Documents" form is updated to ensure that only documents associated to programs that are assigned to the logged in system code, are displayed for edit
Topics
• Document Routing • NX
 
My To Do's Widget - Sign Tab
An issue is resolved when logged into a sub system code only assigned permissions to specific "Program(s)", where the user could access a "To Do" in the "My To Do's" widget that was not generated in a "Program" assigned to the sub system code
Topics
• My To Do's
 
My To Do's Widget - Sign Tab
An issue is resolved when co-signing a document for another staff member on the "Sign" tab of the "My To Do's" widget, to ensure the correct staff member's signature displays on the document.
Topics
• My To Do's
 
Document Archiving
An issue is resolved in form "Document Archiving" to ensure the "View Form Types Included" field successfully displays a form type, if the form type was filed with restrictions selected in the "Document Restrictions" field of the "Document Management Definition" form.
Topics
• Document Management • NX
 
Acceptance Tests
AV-84047 Summary | Details
Append Document
Scenario 1: Append Documents - Validate user permissions to append documents
Specific Setup:
  • Have a system with a [Root] system code and sub system code defined [TestSub]
  • Sub system code [TestSub] has been assigned a specific program [ProgramA]
  • [TestClient] is admitted in two episodes:
  • [Episode1] to [ProgramA]
  • [Episode2] to [ProgramB]
  • [UserA] has access to both the [Root] system code and sub system code [TestSub]
  • [UserB] has access only to the sub system code [TestSub]
  • [FormA] has been submitted for [TestClient] in [Episode1] and a document has been generated [DocA]
  • [FormB] has been submitted for [TestClient] in [Episode2] and a document has been generated [DocB]
  • Log in as [UserB] into the [TestSub] sub system code
Steps
  1. Open form "Append Documents"
  2. Select the applicable form type in the "Form Type" field
  3. Select [TestClient] in the "Entity" field
  4. Enter the applicable date range in the "From Date" and "To Date" fields
  5. Click the "List of Documents" field
  6. Validate the drop down list displays [Doc1] filed for [FormA] in [Episode1, ProgramA]
  7. Validate the drop down list does not display [Doc2] filed for [FormB] in [Episode2, ProgramB], as expected
  8. Select the row for [Doc1]
  9. Add any desired comments in the "New Comments to be Appended to Original Document" field
  10. Submit the form
  11. Validate the 'Confirm Document' dialog displays the appended comments
  12. Validate the document contains the appended signature of the logged in user [UserB] at the end of the document.
  13. Click [Accept].
  14. Validate the form files successfully.
  15. Log out as [UserB]
  16. Log in as [UserA] into the sub system code [SubCode]
  17. Repeat step1
  18. Validate the results are the same, as the sub code is restricted to only [ProgramA]
  19. Log out as [UserA]
  20. Log in as [UserA] into the [Root] system code
  21. Repeat step 1
  22. Validate the drop down list displays [Doc1] filed for [FormA] in [Episode1, ProgramA]
  23. Validate the drop down list also displays [Doc2] filed for [FormB] in [Episode2, ProgramB], as [UserA] has access to both the root and sub system code.
Topics
• Document Routing • NX
AV-84554 Summary | Details
My To Do's Widget - Sign Tab
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • HomeView.My To Do's Widget (Sign Tab)
Scenario 1: 'My To Do's Widget - Validate user permissions to access documents
Specific Setup:
  • Have a system with a root and a sub system code
  • The sub system is code is assigned to only [ProgramA]
  • [UserA] is a staff member that can cosign for other staff members and has access to log into both the root and the sub code
  • [UserB] is a staff member and cannot cosign for other staff members and has access to log both the root and the sub code
  • [TestClient] has been admitted in two episodes:
  • "Episode1" in [ProgramA]
  • "Episode2" in [ProgramB]
  • Two documents have been routed for [TestForm] for [TestClient]
  • [DocA] - was routed to [UserA] for an [Epsiode1]
  • [DocB] - was routed to [UserB] for [Episode2]
  • [UserA] and [UserB] have the "My To Do's" widget on their home view
Steps
  1. Log in to the sub code as [UserA]
  2. Navigate to the "My To Do's" widget
  3. Click the [Sign] tab
  4. Search for [UserA] in the "Staff" search field
  5. Validate [DocA] is found
  6. Search for [UserB] in the Staff field
  7. Validate [DocB] is not found, as [DocB] was filed in [Episode2], [ProgramB], which is not a program assigned to the logged in sub code
  8. Log out as [UserA] from sub code
  9. Log in as [UserA] to the root system code
  10. Navigate to the "My To Do's" widget
  11. Click the [Sign] tab
  12. Search for [UserA] in the "Staff" search field
  13. Validate [DocA] is found
  14. Search for [UserB] in the "Staff" search field
  15. Validate [DocB] is found, as [UserA] can co-sign for other staff members is logged into the root system code, which has access to all programs
  16. Log out as [UserA]
  17. Log in as [UserB] into the sub code
  18. Navigate to the "My To Do's" widget
  19. Click the [Sign] tab
  20. Validate the "Staff" search field is disabled, as [UserB] cannot cosign for any other staff members.
  21. Validate [DocA] is not listed in the "Search Documents" list, as that document was routed to another staff member.
  22. Validate [DocB] is not listed in the "Search Documents" list, as that document was filed in [Episode2], [ProgramB], which is not a program assigned to the logged in sub code
  23. Log out as [UserB] from sub code
  24. Log in as [UserB] to the root system code
  25. Navigate to the "My To Do's" widget
  26. Click the [Sign] tab
  27. Validate the "Staff" search field is disabled, as [UserB] cannot cosign for any other staff members.
  28. Validate [DocA] is not listed in the "Search Documents" list, as that document was routed to another staff member.
  29. Validate [DocB] is listed in the "Search Documents" list, as the document was routed to [UserB] and is logged into the root system code, which has access to all programs
Topics
• My To Do's
AV-84987 Summary | Details
My To Do's Widget - Sign Tab
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Clinical Document Viewer
Scenario 1: 'My To Do's Widget (Sign Tab) - Validate approving documents as as Co-Signer
Specific Setup:
  • [UserA] is a staff member
  • [UserB] is a staff member
  • [UserC] is a staff member that can co-sign To Do's for other staff members
  • Two documents have been routed in form [TestForm], for [TestClient]
  • [DocA] - was routed to [UserA] in [Episode1]
  • [DocB] - was routed to [UserB] in [Episode2]
  • [UserC] has the "My To Do's" widget on their home view
  • Log in as [UserC]
Steps
  1. Navigate to the "My To Do's" widget
  2. Click the [Sign] tab
  3. In the "Staff" search filed, search for [UserA]
  4. Validate the row for [DocA] is the "Search Documents" list, and select the row
  5. Validate the "Document" preview pane displays data as expected for the document
  6. Navigate to the end of the document
  7. Validate the last signature indicates [UserC], as the "Co-Signer" signature. For example, "Electronically Signed By: [UserC] (Date and Time) - Co-Signer"
  8. Click [Accept], to move the document to the "Accepted Documents" section
  9. Select the document
  10. Click [Sign All]
  11. Validate the document is removed from the "Sign Tab"
  12. In the "Staff" search filed, search for [UserB]
  13. Validate the row for [DocB] is the "Search Documents" list, and select the row
  14. Validate the "Document" preview pane displays data as expected for the document
  15. Navigate to the end of the document
  16. Validate the last signature indicates [UserC], as the "Co-Signer" signature. For example, "Electronically Signed By: [UserC] (Date and Time) - Co-Signer"
  17. Click [Accept], to move the document to the "Accepted Documents" section
  18. Select the document
  19. Click [Sign All]
  20. Validate the document is removed from the "Sign Tab"
  21. Open form "Clinical Document Viewer"
  22. Select [TestClient] in the "Select Client" field
  23. Click [Process]
  24. Click the [Results] tab
  25. Locate the row for the [DocA] signed in step 1b and select the "View" check box
  26. Click the [View] button
  27. Validate the "Document" preview pane displays data as expected for the document
  28. Navigate to the end of the document
  29. Validate the last signature indicates [UserC], as the "Co-Signer" signature. For example, "Electronically Signed By: [UserC] (Date and Time) - Co-Signer"
  30. Click [Close All Documents]
  31. Locate the row for the [DocB] signed in step 1b and select the "View" check box
  32. Click the [View] button
  33. Validate the "Document" preview pane displays data as expected for the document
  34. Navigate to the end of the document
  35. Validate the last signature indicates [UserC], as the "Co-Signer" signature. For example, "Electronically Signed By: [UserC] (Date and Time) - Co-Signer"
  36. Click [Close All Documents]
  37. Click the [Search] tab
  38. Click [Close]
Topics
• My To Do's
AV-85162 Summary | Details
Document Archiving
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Document Archiving
Scenario 1: Document Archiving - Form field validations
Specific Setup:
  • A "Form" type [FormtypeA], is defined in form "Document Management Definition" and includes restrictions selected in field "Document Restrictions'
  • [FormA] is set up in form "Document Routing Setup" with [FormtypeA]
  • A document [DocumentA] generated with [FormA] exists for [TestClient], that was created over "180" days ago
  • A "Form" type [FormtypeB], is defined in form "Document Management Definition" and does "not" include any restrictions selected in field "Document Restrictions'
  • [FormB] is set up in form "Document Routing Setup" with [FormtypeB]
  • A document [DocumentB] that was generated with [FormB] exists for [TestClient], that was created over "180" days ago
Steps
  1. Open form "Clinical Document Viewer"
  2. Select [TestClient]
  3. Click [Process]
  4. Validate [DocumentA] generated by [FormA], is displayed as expected date
  5. Validate [DocumentB] generated by [FormB], is displayed as expected date
  6. Close the form
  7. Open form "Document Archiving"
  8. Select "Client" the entity type in the "Entity Type" field
  9. Select "Individual" in the "Include" field
  10. Select [TestClient] in the "Entity" field
  11. Select the applicable episode in the "Episode" field
  12. In the "Archive Documents Older Than" enter the desired date greater than "180" days
  13. Click the "View Form Types Included"
  14. Validate row is displayed for [FormTypeA] for [FormA]
  15. Validate row is displayed for [FormTypeB] for [FormB]
  16. Click [Archive]
  17. At the "Are you sure you want to Archive these Documents" dialog, click [Yes]
  18. Close the form
  19. Open form "Clinical Document Viewer"
  20. Select [TestClient]
  21. Click [Process]
  22. Validate [DocumentA] generated by [FormA] is no longer displayed, as expected
  23. Validate [DocumentB] generated by [FormB] is no longer displayed, as expected
Topics
• Document Management • NX