Skip to main content

RADplus 2023 Monthly Release 2023.03.00 Acceptance Tests

  1. Last updated
  2. Save as PDF
Update 41 Summary | Details
Forms - Switching from "Final" to "Draft"
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Modeled Form With Service Documentation
  • Draft/Final Dialog - The following required prompt(s) do not contain information
  • Admission (Outpatient)
  • Patient Health Questionnaire-9
Scenario 1: Modeled 'Service Documentation' Forms - Field Validations
Specific Setup:
  • A modeled table must be defined in 'Table Definition' with the following (Table A):
  • Fields that are mapped in the 'Service Documentation' section that are required for Service Documentation functionality. These include: 'Progress Note For', 'Date of Service', 'Service Start Time', 'Service End Time', 'Service Duration', 'Location', 'Service Program', 'Service Charge Code', 'Service Practitioner' and 'Draft/Final' fields.
  • Fields added that are not mapped for Service Documentation functionality.
  • A modeled form (Form A) must be defined in 'Form Definition' that uses "Table A" and contains all Service Documentation and non-Service Documentation fields.
  • A client is enrolled in an existing episode (Client A).
Steps
  1. Select "Client A" and access "Form A".
  2. Select "New Service" in the 'Progress Note For' field.
  3. Enter the desired date in the 'Date of Service' field.
  4. Enter the desired time in the 'Service Start Time' and 'Service End Time' fields.
  5. Select the desired value in the 'Service Charge Code' field.
  6. Enter the desired value in the 'Service Duration' field.
  7. Select the desired value in the 'Service Practitioner' field.
  8. Populate all other required and desired fields.
  9. Select "Final" in the 'Draft/Final' field.
  10. Validate a message is displayed stating: Selecting "Final" prevents future edits.
  11. Click [OK].
  12. Validate all fields are disabled.
  13. Select "Draft" in the 'Draft/Final' field.
  14. Validate all fields are enabled.
  15. Click [Submit].
  16. Select "Client A" and access "Form A".
  17. Select the draft filed in the previous steps and click [Edit].
  18. Validate all previously filed data is displayed.
  19. Close the form.
Topics
• Forms • Service Documentation
Update 67 Summary | Details
All Documents Widget
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Console Widget Viewer
Scenario 1: All Documents Widget - column data validations
Specific Setup:
  • [TestFormA] is a form that contains an apostrophe within the forms name
  • [TestFormB] is a form that does not contain an apostrophe within the forms name
  • Have a 'Program" [ProgramA] defined that has an apostrophe in the program description name
  • Have a 'Program" [ProgramB] defined that does not have an apostrophe in the program description name
  • [TestClient] is admitted in [ProgramA] in [Ep1]
  • A row of data for has been submitted in [Ep1] for form [TestFormA]
  • A row of data for has been submitted in [Ep2] for form [TestFormB]
  • [TestClient] is admitted in [ProgramB] in [Ep2]
  • A row of data for has been submitted in [Ep1] for form [TestFormA]
  • A row of data for has been submitted in [Ep2] for form [TestFormB]
  • Have the "All Documents Widget" configured with a "Tab" [TestTab] defined in the widget, that contains [TestFormA] and [TestformB]
  • The logged in user has the "All Document Widget" widget on their home view and has permissions to both test forms
Steps
  1. At the home view, select [TestClientA]
  2. Navigate to the "All Document Widget"
  3. Navigate to the "All Document Widget" and select tab [TestTab] in the widget
  4. From the "Form Description' column drop down list, select [TestFormA], the form that includes an apostrophe in its form name
  5. From the "Episode" column drop down list, select the "All" check box
  6. For [TestFormA], validate the row filed in [Ep1] [ProgramA] is displayed
  7. Validate the data results displayed in the "Form Description", "Episode(Program Name)", "Date", "Time", "Data Entry By" and "Workflow Status" columns, are populated as expected
  8. For [TestFormA], validate the row filed in [Ep2] [ProgramB] is displayed
  9. Validate the data results displayed in the "Form Description", "Episode(Program Name)", "Date", "Time", "Data Entry By" and "Workflow Status" columns, are populated as expected
  10. From the "Episode" column drop down list, select just [Ep1]
  11. For [TestFormA], validate only the row filed in [Ep1] [ProgramA] is displayed
  12. Validate the data results displayed in the "Form Description", "Episode(Program Name)", "Date", "Time", "Data Entry By" and "Workflow Status" columns, are populated as expected
  13. From the "Episode" column drop down list, select just [Ep2]
  14. For [TestFormA], validate only the row filed in [Ep2] [ProgramB] is displayed
  15. Validate the data results displayed in the "Form Description", "Episode(Program Name)", "Date", "Time", "Data Entry By" and "Workflow Status" columns, are populated as expected
  16. From the "Form Description' column drop down list, select [TestFormB], the form that does 'not' include an apostrophe in its form name
  17. For [TestFormB], validate the row filed in [Ep1] [ProgramA] is displayed
  18. Validate the data results displayed in the "Form Description", "Episode(Program Name)", "Date", "Time", Data Entry By" and "Workflow Status" columns, are populated as expected
  19. For [TestFormB], validate the row filed in [Ep2] [ProgramB] is displayed
  20. Validate the data results displayed in the "Form Description", "Episode(Program Name)", "Date", "Time", "Data Entry By" and "Workflow Status" columns, are populated as expected
  21. From the "Episode" column drop down list, select just [Ep1]
  22. For [TestFormB], validate only the row filed in [Ep1] [ProgramA] is displayed
  23. Validate the data results displayed in the "Form Description", "Episode(Program Name)", "Date", "Time", "Data Entry By" and "Workflow Status" columns, are populated as expected
  24. From the "Episode" column drop down list, select just [Ep2]
  25. For [TestFormB], validate only the row filed in [Ep2] [ProgramB] is displayed
  26. Validate the data results displayed in the "Form Description", "Episode(Program Name)", "Date", "Time", "Data Entry By" and "Workflow Status" columns, are populated as expected
Topics
• Widgets • NX
Update 75 Summary | Details
Document Routing - RADplus
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Treatment Plan
  • Modeled Form With Service Documentation
  • Add Non-User Signature (PM)
  • Ambulatory Progress Notes
Scenario 1: Inpatient Progress Notes - Validate document routing
Specific Setup:
  • Document routing must be enabled for the "Inpatient Progress Notes" form.
  • Tester must select a client for testing who has an inpatient episode.
Steps
  1. Open the "Inpatient Progress Notes" form.
  2. Create and finalize a document.
  3. Sign the document.
  4. Using "Clinical Document Viewer", view and print the document.
  5. Validate the document displays and prints.
  6. Open the "Inpatient Progress Notes" form.
  7. Create and route a progress note to an approver.
  8. Sign on as the approver.
  9. Locate the document in the approver's "My To Do's" widget.
  10. Click on "Approve Document" and approve the document.
  11. Using the "Clinical Document Viewer", view the document that was just approved.
  12. Open the "Inpatient Progress Notes" form.
  13. Create and route a note to multiple approvers.
  14. Sign on as the first approver.
  15. Locate the document in the approver's "My To Do's" widget.
  16. Click on "Approve Document".
  17. Click "Accept".
  18. Enter the approver's password.
  19. Log on as another approver.
  20. Locate the document in the approver's "My To Do's" widget.
  21. Click on "Approve Document".
  22. Click "Accept".
  23. Enter the approver's password.
  24. Open the "Clinical Document Viewer" form.
  25. Select the document that was just routed/finalized.
  26. Validate that the document displays and prints.
  27. Open the "Inpatient Progress Notes" form.
  28. Create a progress note and route to several approvers.
  29. Log on as another approver.
  30. Locate the document in the approver's "My To Do's" widget.
  31. Click on "Approve Document".
  32. Click "Accept".
  33. Enter the approver's password.
  34. Repeat steps 12b-13c for each additional approver.
  35. Open "Clinical Document Viewer".
  36. Validate the document that was just filed display and prints.
Scenario 2: Document Routing - (Accept/Route) Modeled Form
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 in step 1
  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.
Scenario 3: Document Routing - (Accept/Route) Modeled Form with "Service Documentation"
Specific Setup:
  • Have a modeled form that is enabled for "Service Documentation"
Steps
  1. Open the modeled form
  2. Select a client [TestClient]
  3. In the "Data Row For" field, select "New Service"
  4. Set the "Service Date" field
  5. Populate all other required fields on the form
  6. Set the "Draft/Final" field to "Final"
  7. Click "Accept and Route" at the document routing "Confirm Document" screen
  8. On the "Route Document To" screen, select and add an approver in the "Add" prompt box
  9. Click "Submit" to route the document [TestDoc]
  10. Navigate to the 'My To Do's' widget.
  11. Locate the To Do for document just routed in step 1
  12. Click [Approve Document]
  13. Verify the document preview displays the data as expected
  14. Click [Accept].
  15. Enter the password for the user in the 'Password' field.
  16. Click [OK].
  17. Validate the "To Do" has been removed from the "My To Do's" widget
  18. Access the 'Clinical Document Viewer' form.
  19. Enter [TestClient] in the 'Select Client' field.
  20. Locate [TestDoc] in the document results list
  21. Click [View] to display the document
  22. Verify the document preview displays the data as expected
  23. Close the form.

Scenario 4: Treatment Plan - File a Treatment Plan with Document Routing
Specific Setup:
  • Client is enrolled in an existing episode (Client A).
  • The 'Treatment Plan' form must have document routing enabled.
  • Must have the 'My To Do's' widget configured on a view.
  • The 'Set Current Status To Active When Plan Is Finalized' registry setting is set to "N" for the 'Treatment Plan' form.
  • The 'Set Current Status To Completed On Plan End Date' registry setting is set to "N" for the 'Treatment Plan' form.
Steps
  1. Select "Client A" and access the 'Treatment Plan' form.
  2. Click [Add].
  3. Enter the current date is displayed in the 'Plan Date' field.
  4. Select the desired date in the 'Plan Date' field.
  5. Select the desired value in the 'Plan Type' field
  6. Select "Draft" in the 'Treatment Plan Status' field.
  7. Validate "Draft" is now selected in the 'Current Status' field.
  8. Click [Launch Plan].
  9. Add a problem, goal, objective, and intervention.
  10. Click [Return to Plan] and [OK].
  11. Hover over the problem in the 'Problems' field.
  12. Validate a "not allowed" icon displays indicating the field cannot be edited.
  13. Validate the 'Problem' is displayed in dark grey text.
  14. Select "Final" in the 'Draft/Final' field.
  15. Select "Active" in the 'Current Status' field.
  16. Click [Submit].
  17. Validate a 'Confirm Document' dialog is displayed.
  18. Validate the user is unable to print.
  19. Validate all treatment plan data displays as expected. Please note: the 'Current Status' field will not be included in the document image. This is because the 'Current Status' field can be updated after a 'Treatment Plan' has been finalized.
  20. Click [Accept].
  21. Enter the password and click [Verify].
  22. Select "Client A" and access the 'Treatment Plan' form.
  23. Select the record from the previous steps and click [Edit].
  24. Validate a message is displayed stating: This plan is marked as Final. Only the following field(s) may be updated: 'Current Status'. Do you want to continue?
  25. Click [Yes].
  26. Validate the plan displays as expected and fields are disabled, except for the 'Current Status' field.
  27. Select "Completed" in the 'Current Status' field.
  28. Click [Submit].
  29. Validate a message is displayed stating: The following fields are updated: 'Current Status'.
  30. Click [OK].
  31. Select "Client A" and access the 'Treatment Plan' form.
  32. Select the record from the previous steps and click [Edit].
  33. Validate a message is displayed stating: This plan is marked as Final. Only the following field(s) may be updated: 'Current Status'. Do you want to continue?
  34. Click [Yes].
  35. Validate "Completed" is selected in the 'Current Status' field.
  36. Close the form.
Scenario 5: Document Routing (Modeled Form) - (Accept / Route) Documents with 'Approval Comments'
Specific Setup:
  • Have a form [TestForm], for example a "Modeled" form or "Treatment Plan" form that has been enabled for document routing in form "Document Routing Setup" and has prompt "Allow Comments During Approval" to "Yes"
  • [TestForm] includes a "Signature" field
  • Have three users:
  • [StaffA] and [StaffB] are staff members and have the "My To Do's" widget on their home view
  • [StaffC] is a staff member and has the "Co Signer for Other Practitioners" prompt in the document routing section set to 'Yes'.in form 'User Definition'
  • All three users have the "My To Do's" widget on their home views
  • Have a report to display data in the "SYSTEM.DocR.comments" table
  • Log in as [StaffA]
Steps
  1. Open form [TestForm] and select any client
  2. Populate the "Signature" field. Make a note of the signature entered.
  3. Set the "Draft/Final" field to "Final".
  4. Submit the form.
  5. At the "Confirm Document" screen
  6. Validate the "Signature" field is populated as expected
  7. Click [Accept]
  8. Provide the password and click [Verify]
  9. At the "Approval Comments" dialog, populate the text field with a desired comment [TestComments]. Make note of the comment entered
  10. Click [OK]
  11. Open the "Clinical Document Viewer" form.
  12. Select the client and click [Process]
  13. Select and view the document submitted in step 1.
  14. Validate the "Signature" field on the document is populated with signature noted in step 1.
  15. Validate the "Comments" entered and noted in step 1, are displayed as expected
  16. At the bottom of the document, validate that the document includes the "Electronically Signed By:" field, populated with name of [StaffA]
  17. Close the form
  18. Run the report or query on the "SYSTEM.DocR.comments" table
  19. Validate a row is present for the "Approval Comments" entered in step 1 and is displayed as expected
  20. Open [TestForm] and a select any client
  21. Populate the "Signature" field. Make a note of the signature entered.
  22. Set the "Draft/Final" field to "Final".
  23. Submit the form.
  24. At the "Confirm Document" screen
  25. Validate the "Signature" field is populated as expected
  26. Click [Accept and Route]
  27. At the "Route To Document" screen, add [StaffA], [StaffB] and [StaffC] as approvers
  28. Click [Submit]
  29. Log out as [StaffA]
  30. Log in as [StaffB]
  31. Navigate the "My To Do's widget
  32. Click on the "New" tab and validate the To Do sent in step 4, is present
  33. Click [Approve Document]
  34. At the document preview
  35. Validate the "Signature" field on the document is populated with signature noted in step 4
  36. At the bottom of the document, validate that the document includes two "Electronically Signed By:" field signatures:
  37. [StaffA] signed as the "Author" and below it, [StaffB] signed as "Staff"
  38. Click [Accept]
  39. At the "Approval Comments" dialog, populate the text field with a desired comment [TestComments]. Make note of the comment
  40. Click [OK]
  41. Log out as [StaffB]
  42. Log in as [StaffC]
  43. Navigate the "My To Do's widget
  44. Click on the "Sign" tab
  45. In the "Staff" search field, search for [StaffA]. [Note: for Avatar NX, clicking the 'Change' link located in the top left corner of the widget, allows the user to search for another staff member]
  46. Validate the To Do sent to [StaffA] is found, select the To Do to review it
  47. Validate the "Signature" field on the document is populated with signature noted in step 4
  48. At the bottom of the document, validate that the document includes three "Electronically Signed By:" field signatures:
  49. [StaffA] signed as the "Author"
  50. [StaffB] signed as "Staff"
  51. [StaffC] signed as "Staff"
  52. Click [Accept]
  53. At the "Approval Comments" dialog, populate the text field with a desired comment [TestComments]. Make note of the comment entered
  54. Click [OK]
  55. Click [Sign All]
  56. Validate the To Do is removed from the To Do list
  57. Navigate back to the "My To Do's" widget
  58. Click on the "Sign" tab
  59. In the "Staff" search field, search for [StaffC].
  60. Validate the To Do sent to [StaffC] in step 4 is present, select the To Do
  61. Click [Approve Document]
  62. At the document preview
  63. Validate the "Signature" field on the document is populated with signature noted in step 4
  64. At the bottom of the document, validate that the document includes three "Electronically Signed By:" field signatures,
  65. [StaffA] signed as the "Author",
  66. [StaffB] signed as "Staff"
  67. [StaffC] signed as "Staff"
  68. Click [Accept]
  69. At the "Approval Comments" dialog, populate the text field with a desired comment [TestComments]. Make note of the comment entered
  70. Click [OK]
  71. Open the "Clinical Document Viewer" form.
  72. Select the client and click [Process]
  73. Select and view the document that was just created in the previous step
  74. Validate the "Signature" field on the document is populated with signature noted in step 10
  75. Validate the "Comments" entered noted in step 10, are displayed as expected
  76. At the bottom of the document, validate that the document includes three "Electronically Signed By:" field signatures,
  77. [StaffA] signed as the "Author"
  78. [StaffB] signed as "Staff"
  79. Validate the comments entered by [StaffB] are entered in step 7 are displayed as expected
  80. [StaffC] signed as "Staff" (Signing for [StaffA])
  81. Validate the comments entered by [StaffC] in step 9, are displayed as expected
  82. [StaffC] signed as "Staff" (Signing for [StaffC])
  83. Validate the comments entered by [StaffC] in step 10, are displayed as expected
  84. Close the form
  85. Run the report or query on the "SYSTEM.DocR.comments" table
  86. Validate the following rows are present on the report, displayed as expected:
  87. A row displaying the "Approval Comments" entered in step 1 by [StaffA]
  88. A row displaying the "Approval Comments" entered in step 7 by [StaffB]
  89. A row displaying the "Approval Comments" entered in step 9 by [StaffC] when signing for [StaffA]
  90. A row displaying the "Approval Comments" entered in step 10 by [StaffC], signing as [StaffC]
Scenario 6: Document Routing (Treatment Plan) - (Accept / Route) Documents with 'Approval Comments'
Specific Setup:
  • Have a "Treatment Plan" form [TestForm] has been enabled for document routing in form "Document Routing Setup" and has prompt "Allow Comments During Approval" to "Yes"
  • [TestForm] includes a "Signature" field
  • Have three users:
  • [StaffA] and [StaffB] are staff members and have the "My To Do's" widget on their home view
  • [StaffC] is a staff member and has the 'Co Signer for Other Practitioners' prompt in the document routing section set to 'Yes'.in form 'User Definition'
  • All three users the "My To Do's" widget on their home views
  • Have a report to display data in the "SYSTEM.DocR.comments" table
  • Log in as [StaffA]
Steps
  1. Open form [TestForm] and select any client
  2. Populate the "Signature" field. Make a note of the signature entered.
  3. Set the "Draft/Final" field to "Final".
  4. Submit the form.
  5. At the "Confirm Document" screen
  6. Validate the "Signature" field is populated as expected
  7. Click [Accept]
  8. Provide the password and click [Verify]
  9. At the "Approval Comments" dialog, populate the text field with a desired comment [TestComments]. Make note of the comment entered
  10. Click [OK]
  11. Open the "Clinical Document Viewer" form.
  12. Select the client and click [Process]
  13. Select and view the document submitted in step 1.
  14. Validate the "Signature" field on the document is populated with signature noted in step 1.
  15. Validate the "Comments" entered and noted in step 1, are displayed as expected
  16. At the bottom of the document, validate that the document includes the "Electronically Signed By:" field, populated with name of [StaffA]
  17. Close the form
  18. Run the report or query on the "SYSTEM.DocR.comments" table
  19. Validate a row is present for the "Approval Comments" entered in step 1 and is displayed as expected
  20. Open [TestForm] and a select any client
  21. Populate the "Signature" field. Make a note of the signature entered.
  22. Set the "Draft/Final" field to "Final".
  23. Submit the form.
  24. At the "Confirm Document" screen
  25. Validate the "Signature" field is populated as expected
  26. Click [Accept and Route]
  27. At the "Route To Document" screen, add [StaffA], [StaffB] and [StaffC] as approvers
  28. Click [Submit]
  29. Log out as [StaffA]
  30. Log in as [StaffB]
  31. Navigate the "My To Do's widget
  32. Click on the "New" tab and validate the To Do sent in step 4, is present
  33. Click [Approve Document]
  34. At the document preview
  35. Validate the "Signature" field on the document is populated with signature noted in step 4
  36. At the bottom of the document, validate that the document includes two "Electronically Signed By:" field signatures:
  37. [StaffA] signed as the "Author" and below it, [StaffB] signed as "Staff"
  38. Click [Accept]
  39. At the "Approval Comments" dialog, populate the text field with a desired comment [TestComments]. Make note of the comment
  40. Click [OK]
  41. Log out as [StaffB]
  42. Log in as [StaffC]
  43. Navigate the "My To Do's widget
  44. Click on the "Sign" tab
  45. In the "Staff" search field, search for [StaffA]. [Note: for Avatar NX, clicking the 'Change' link located in the top left corner of the widget, allows the user to search for another staff member]
  46. Validate the To Do sent to [StaffA] is found, select the To Do to review it
  47. Validate the "Signature" field on the document is populated with signature noted in step 4
  48. At the bottom of the document, validate that the document includes three "Electronically Signed By:" field signatures:
  49. [StaffA] signed as the "Author"
  50. [StaffB] signed as "Staff"
  51. [StaffC] signed as "Staff"
  52. Click [Accept]
  53. At the "Approval Comments" dialog, populate the text field with a desired comment [TestComments]. Make note of the comment entered
  54. Click [OK]
  55. Click [Sign All]
  56. Validate the To Do is removed from the To Do list
  57. Navigate back to the "My To Do's" widget
  58. Click on the "Sign" tab
  59. In the "Staff" search field, search for [StaffC].
  60. Validate the To Do sent to [StaffC] in step 4 is present, select the To Do
  61. Click [Approve Document]
  62. At the document preview
  63. Validate the "Signature" field on the document is populated with signature noted in step 4
  64. At the bottom of the document, validate that the document includes three "Electronically Signed By:" field signatures,
  65. [StaffA] signed as the "Author",
  66. [StaffB] signed as "Staff"
  67. [StaffC] signed as "Staff"
  68. Click [Accept]
  69. At the "Approval Comments" dialog, populate the text field with a desired comment [TestComments]. Make note of the comment entered
  70. Click [OK]
  71. Open the "Clinical Document Viewer" form.
  72. Select the client and click [Process]
  73. Select and view the document that was just created in the previous step
  74. Validate the "Signature" field on the document is populated with signature noted in step 10
  75. Validate the "Comments" entered noted in step 10, are displayed as expected
  76. At the bottom of the document, validate that the document includes three "Electronically Signed By:" field signatures,
  77. [StaffA] signed as the "Author"
  78. [StaffB] signed as "Staff"
  79. Validate the comments entered by [StaffB] are entered in step 7 are displayed as expected
  80. [StaffC] signed as "Staff" (Signing for [StaffA])
  81. Validate the comments entered by [StaffC] in step 9, are displayed as expected
  82. [StaffC] signed as "Staff" (Signing for [StaffC])
  83. Validate the comments entered by [StaffC] in step 10, are displayed as expected
  84. Close the form
  85. Run the report or query on the "SYSTEM.DocR.comments" table
  86. Validate the following rows are present on the report, displayed as expected:
  87. A row displaying the "Approval Comments" entered in step 1 by [StaffA]
  88. A row displaying the "Approval Comments" entered in step 7 by [StaffB]
  89. A row displaying the "Approval Comments" entered in step 9 by [StaffC] when signing for [StaffA]
  90. A row displaying the "Approval Comments" entered in step 10 by [StaffC], signing as [StaffC]
Scenario 7: Ambulatory Progress Notes - Validate document routing
Specific Setup:
  • Document routing must be enabled for the "Ambulatory Progress Notes" form.
Steps
  1. Open the "Ambulatory Progress Notes" form.
  2. Create and finalize a document.
  3. Sign the document.
  4. Using "Clinical Document Viewer", view and print the document.
  5. Validate the document displays and prints.
  6. Open the "Ambulatory Progress Notes" form.
  7. Create and route a progress note to an approver.
  8. Sign on as the approver.
  9. Locate the document in the approver's "My To Do's" widget.
  10. Click on "Approve Document" and approve the document.
  11. Using the "Clinical Document Viewer", view the document that was just approved.
  12. Open the "Ambulatory Progress Notes" form.
  13. Create and route a note to multiple approvers.
  14. Sign on as the first approver.
  15. Locate the document in the approver's "My To Do's" widget.
  16. Click on "Approve Document".
  17. Click "Accept".
  18. Enter the approver's password.
  19. Log on as another approver.
  20. Locate the document in the approver's "My To Do's" widget.
  21. Click on "Approve Document".
  22. Click "Accept".
  23. Enter the approver's password.
  24. Open the "Clinical Document Viewer" form.
  25. Select the document that was just routed/finalized.
  26. Validate that the document displays and prints.
  27. Open the "Ambulatory Progress Notes" form.
  28. Create a progress note and route to several approvers.
  29. Log on as another approver.
  30. Locate the document in the approver's "My To Do's" widget.
  31. Click on "Approve Document".
  32. Click "Accept".
  33. Enter the approver's password.
  34. Repeat steps 7b-8c for each additional approver.
  35. Open "Clinical Document Viewer".
  36. Validate the document that was just filed display and prints.
Topics
• Document Routing • NX • Service Documentation • Treatment Plan
Update 89 Summary | Details
Deactivating Users
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Deactivate Users By Role
Scenario 1: 'Deactivate Users by Role' Form- (Deactivate All Selected User's)
Specific Setup:
  • In form "User Definition", the following users have these "User Role" assignments:
  • [User1] is assigned to "User Role" [TestRole1]
  • [User2] is assigned to roles [TestRole1] and [TestRole2]
  • [User3] is assigned to [TestRole2]
  • [User4] is not assigned to any role
  • [User5] is assigned to [TestRole1] and has prompt "Allow User Role Customization" set to "Yes"
  • [User6] has been "Disabled" in the system. [Note: For example, a user can become disabled via the 'Change User ID' or 'User Merge' forms. 'Disabled' users are automatically "Deactivated" and that status can no longer be updated.]
Steps
  1. Open form "Deactivate Users By Role"
  2. Select prompt "Deactivate All Selected Users"
  3. In the "Select Role" field, select [TestRole1]
  4. Please Note: Upon submitting the form with this prompt selected, the following will outcomes are to be expected:
  5. Users assigned to the selected Role will be "Deactivated"
  6. Users not assigned to any Role will also be "Deactivated"
  7. Users not assigned to the selected Role but are assigned to any other role will be “Activated”
  8. Submit the form
  9. Validate form submits successfully and a message is displayed indicating the number of user "Deactivated" and the number of users "Activated"
  10. Click [OK]
  11. Open form "User Definition",
  12. For each user listed below from the setup, verify that their "Deactivated" or "Activated" status is as follows, following the form submission in step 2:
  13. [User1] who is assigned to the role that was selected in step 1 [TestRole1], is "Deactivated"
  14. [User2] who is assigned to multiple roles [TestRole1] and [TestRole2], is also "Deactivated". [Note: As long as one of roles assigned to a user is the selected role, the user is deactivated]
  15. [User3] who is assigned to [TestRole2] is "Active", as they are not assigned to the selected role in step1
  16. [User4] who is not assigned to any role is "Deactivated"
  17. [User5] who is assigned to [TestRole1] but has prompt "Allow User Role Customization" set to "Yes", is "Deactivated". (Note: This form treats customized users, as a user who is not assigned to any role(s))
  18. [User6] who is a "Disabled" user in the system
  19. Validate, a message indicating the user is disabled and cannot be updated, is displayed when selecting the user.
  20. Validate the user is "Deactivated" and the "Deactivate" checkbox is disabled, as expected
Scenario 2: 'Deactivate Users by Role' Form- (Deactivate All User's Except Selected)
Specific Setup:
  • In form "User Definition", the following users have these "User Role" assignments:
  • [User1] is assigned to "User Role" [TestRole1]
  • [User2] is assigned to roles [TestRole1] and [TestRole2]
  • [User3] is assigned to [TestRole2]
  • [User4] is not assigned to any role
  • [User5] is assigned to [TestRole1] and has prompt "Allow User Role Customization" set to "Yes"
  • [User6] has been "Disabled" in the system. [Note: For example, a user can become disabled via the 'Change User ID' or 'User Merge' forms. 'Disabled' users are automatically "Deactivated" and that status can no longer be updated.]
Steps
  1. Re- open form "Deactivate User's By Role"
  2. Select prompt "Deactivate All Users Except Selected"
  3. In the "Select Role" field, select [TestRole1] again
  4. Please Note: Upon submitting the form with this prompt selected, the following will occur:
  5. Users assigned to the ‘selected’ Role will be “Activated”
  6. Users not assigned to the ‘selected’ Role will be “Deactivated”
  7. Users not a member of “any” Role will also be "Deactivated"
  8. Submit the form
  9. Validate form submits successfully and a message is displayed indicating the number of user "Deactivated" and the number of users "Activated"
  10. Click [OK]
  11. Open form "User Definition",
  12. For each user listed below from the setup, verify that their "Deactivated" or "Activated" status is as follows, following form submission in step 3:
  13. [User1] who is assigned to the role selected in step 1[TestRole1], is "Activated"
  14. [User2] who is assigned to multiple roles [TestRole1] and [TestRole2], is also "Activated". [Note: As long as one of roles assigned to a user is the selected role, the user is activated]
  15. [User3] assigned to [TestRole2] is "Deactivated", as they are not assigned to the selected role in step4
  16. [User4] not assigned to any role, still remains "Deactivated"
  17. [User5] assigned to [TestRole1] but has prompt "Allow User Role Customization" set to "Yes", is "Deactivated". (Note: This form treats customized users as a user who are not assigned to any role(s))
  18. [User6] who is a "Disabled" user in the system.
  19. Validate a message indicating the user is disabled and cannot be updated, is displayed when selecting the user.
  20. Validate the user is "Deactivated" and the "Deactivate" checkbox is disabled, as expected
Topics
• User Definition • User Role Definition • NX • "My To Do's" widget
Update 90 Summary | Details
Site Specific Section Modeling - form
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Site Specific Section Modeling (CWS)
Scenario 1: Site Specific Section Modeling Form - prompt and value validations
Specific Setup:
  • Have access to form "Site Specific Section Modeling"
Steps
  1. Open form "Site Specific Section Modeling"
  2. Select any form [TestFormA] from the "Site Specific Section" drop down list that has not already been configured, for example the "(Inpatient Progress Notes) Supplemental Information" form
  3. Click [OK] to edit the form.
  4. Validate the "Site Specific Section Description" field is enabled and pre-populated with the default description of "Supplemental Information", as expected
  5. Change the name of the field to a new desired value [ValueA]
  6. Validate the "Form Description" field is enabled and blank, as expected
  7. Populate the field to a desired value [ValueB]
  8. Validate the "Menu Location" field is enabled
  9. Click the drop down list and select a menu location
  10. Select the "Prompt Definition" section
  11. Click "Add New Item" and add any desired field [NewField1]
  12. Submit the form
  13. Validate the form files successfully
  14. Return to "Site Specific Section Modeling" and select [TestFormA]
  15. Select the "Prompt Definition" section
  16. In the "Prompt Definition" grid, validate [NewField1] is present, as expected
  17. Select the prompt and click [Delete Selected Item].
  18. Validate message "Are Your Sure?" is displayed.
  19. Click [OK].
  20. Validate the prompt is removed from the "Prompt Definition" grid.
  21. Click "Add New Item" and add any desired field [NewField2]
  22. Navigate to the "Initially Required" prompt and set it to "Yes"
  23. Navigate to prompt "Exclude from Data Collection Instrument" and set it to "Yes"
  24. Validate a message is displayed "Cannot exclude a required prompt", is displayed
  25. Click "OK"
  26. \Navigate to the "Initially Required" prompt and set it to "No"
  27. Navigate to prompt "Exclude from Data Collection Instrument" and set it to "Yes"
  28. Validate the selection is accepted
  29. Submit the form
  30. Validate the form files successfully
  31. Return to "Site Specific Section Modeling" and select [TestFormA]
  32. Validate the "Site Specific Section Description" field is still enabled and populated as expected
  33. Validate the "Form Description" field is populated as expected and is now disabled as the form, since the form has already been submitted.
  34. Validate the "Menu Location" field is populated as expected and also now disabled after form submission, as expected
  35. Navigate the "Prompt Definition" section
  36. Validate [NewField2] is present in the grid and the prompts populated in step 2 are populated as expected
  37. Validate [NewField1] that was deleted, is not present in the grid as expected
ScriptLink - form launch
Scenario 1: "ScriptLink' - Launch additional form validations
Specific Setup:
  • Have two "ScriptLink" scripts configured to prompt the user with a message to launch an additional form [TestFormC]
  • [ScriptA] is 'not' configured with user defined message and will contain the default message to the user when the prompt is launched. For example "ScriptLink is attempting to launch the Avatar form "Update Client Data. Press OK to do this now"
  • [ScriptB] is configured with user defined message when the prompt is launched. For example "Launch Form "Update Client Data" ?
  • Have two forms for testing.
  • [TestFormA] is configured with [ScriptA]. For this example, it is configured to trigger when the [TestFormA] is launched
  • [TestFormB] is configured with [ScriptB]. For this example, it is configured to trigger when a value in [TesField] on the form
Steps
  1. Open [TestFormA]
  2. Select a desired client
  3. Click to add a new row
  4. Validate the user is prompted with the Avatar default message "ScriptLink is attempting to launch the Avatar form '[TestFormC]'. Press 'OK' to do this now"
  5. Click "No"
  6. Validate the user is returned to [TestFormA]
  7. Close the form
  8. Re-open [TestFormA]
  9. Select a desired client
  10. Click to add a new row
  11. Validate the user is prompted with the Avatar default message "ScriptLink is attempting to launch the Avatar form '[TestFormC]'. Press 'OK' to do this now"
  12. Click "OK"
  13. Validate [TestFormC] is launched, as expected
  14. Submit or close the form
  15. Open [TestFormB]
  16. Select a desired client
  17. Navigate to [TestField]
  18. Select a value in the field other than the value set to trigger the script
  19. Validate [TestFormC] is not launched, as expected
  20. Select the value in the field set to trigger the script
  21. Validate the form launch message is displayed
  22. Validate the message includes the user defined message configured in the script, as expected. For example "Launch form [TestFormC] ?
  23. Click "No"
  24. Validate the user is returned to [TestFormB]
  25. Select the value in the field set to trigger the script again
  26. Validate the form launch message is displayed
  27. Validate the message includes the user defined message configured in the script. For example "Launch form [TestFormC] ?"
  28. Click "Yes"
  29. Validate [TestFormC] is launched as expected
  30. Submit or close the form
Topics
• Site Specific Section Modeling • NX • Scriptlink
Update 93 Summary | Details
Modeled form with Service Documentation
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Registry Settings (PM)
  • Modeled Form With Service Documentation
Scenario 1: Service Documentation - Validate Registry Setting - "Allow Appointment Modifications"
Specific Setup:
  • Have a modeled form [TestForm] configured and enabled for service documentation that contains all the required service documentation type fields
  • Have two appointments set for a client [TestClient] for today, one set earlier than the other. For this example:
  • [ApptA] exists for staff [StaffA] from 7am to 8am today
  • [ApptB] exists for staff [StaffB] from 8am to 9am today
  • Have access to the "Registry Settings", "Scheduling Calendar" and form [TestForm]
Steps
  1. Open form "Registry Settings"
  2. Search for and select setting "Allow Appointment Modifications" for edit. Note: Selecting 'Y' will enable the Service Code, Location, Duration, Start Time and End Time fields on Service Documentation-enabled modeled forms when editing an existing appointment. Changes to these values will be applied to the appointment when the data is filed as Final. Selecting 'N' will disable the service documentation fields."
  3. Set the registry setting value to "N" and submit the form
  4. Open form [TestForm]
  5. Select client [TestClient]
  6. In the "Documentation For" selection field
  7. Select "Existing Appointment"
  8. Select [ApptA] from the drop down list
  9. Validate fields "Service Charge Code", "Location", "Duration, "Start Time" and "End Time" are "Disabled" as expected, based on the registry setting.
  10. Close the form
  11. Open form "Registry Settings"
  12. Search for and select setting "Allow Appointment Modifications" for edit.
  13. Set the registry setting value to "Y"
  14. Submit the form
  15. Open form [TestForm]
  16. Select client [TestClient]
  17. In the "Documentation For" selection field, select "Existing Appointment"
  18. Select [ApptA] from the drop down list
  19. Validate fields "Service Charge Code", "Location", "Duration", "Start Time" and "End Time" are "Enabled" and this time and populated as expected.
  20. Change the appointment start and end times for [ApptA] to the same times as those of [ApptB]
  21. Set the "Draft/Final" field to "Final
  22. Validate there's a message displayed blocking the change, indicating the [TestClient] already has an appointment for the new start and end times inputted.
  23. Change the appointment start and end times for [ApptA] to a start and end time that does not conflict with another appointment
  24. Set the "Duration" field to the correct value based on the appointment start and end times entered
  25. Change the "Service Charge Code" field to a new value
  26. Validate the value is accepted
  27. Change the "Service Location" to a new value
  28. Validate the value is accepted
  29. Populate the other required fields and any other fields on the form
  30. Set the "Draft/Final" field to "Draft"
  31. Click [Submit]
  32. Validate submission is successful
  33. Open form [TestForm]
  34. Select client [TestClient]
  35. Validate all the fields on the form are populated as expected, including the fields updated in step 4
  36. Set the "Draft/Final" field to "Final
  37. Click [OK] at the "Selecting 'Final' prevents further edits dialog
  38. Click [Submit]
  39. Validate submission is successful
  40. Open form "Scheduling Calendar"
  41. Navigate to [ApptA] in the appointment grid
  42. Validate the start and end times of the appointment on the grid is match new values entered in step 4b
  43. Click to edit the appointment
  44. Validate the value "Service Start Time" field, is the new value entered in step 4b
  45. Validate the value "Service End Time" field, is the new value entered in step 4b
  46. Validate the value "Duration" field, is the new value entered in step 4b
  47. Validate the "Service Code" field, is the new value entered in step 4b
  48. Validate the "Location" field, is the new value entered in step 4b
  49. Validate all other fields are populated, as expected
  50. Close the form
Topics
• Service Documentation • NX
Update 94 Summary | Details
Product Scrolling Free Text Templates - System Templates
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Product Scrolling Free Text Templates (CWS)
  • Individual Progress Note
  • Treatment Plan
  • Append / Replace
  • Progress Notes (Group and Individual)
  • Registry Settings (PM)
  • Ambulatory Progress Notes
Scenario 1: Product Scrolling Free Text Templates- Validate 'Append', 'Replace', 'Cancel' functionality
Specific Setup:
  • In form "Product Scrolling Free Text Templates", have a template set up for a text field in any product form. For example, the 'Notes Field' in any progress notes form.
Steps
  1. Open the product form.
  2. Right click in the text field.
  3. Select the template.
  4. Validate the text in the template is populated as expected.
  5. Hit "Enter" to go to the next line.
  6. Right click in the text field again.
  7. Select the template.
  8. Click [Append].
  9. Validate the text in the template is populated as expected after the first template.
  10. Validate any lines after the first line and before the appended system template line should not have a leading space.
  11. Hit "Enter" to go to the next line.
  12. Right click in the text field again.
  13. Select the template.
  14. Click [Cancel].
  15. Right click in the text field again.
  16. Select the template.
  17. Click [Append].
  18. Validate the text in the template is populated as expected after the first two templates.
  19. Validate any lines after the second line and before the appended system template line should not have a leading space.
  20. Hit "Enter" to go to the next line.
  21. Right click in the text field again.
  22. Select the template.
  23. Click [Replace].
  24. Validate all the templates are removed and just the new template is populated.
  25. Repeat step 1 but without hitting the "Enter" key after each template is chosen.
  26. Validate results are as expected.
Topics
• Product Scrolling Free Text Templates
Update 97.1 Summary | Details
Client Chart - Non-episodic Documents
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Document Capture
  • Entity-Based Document Capture
Scenario 1: Validate Document Capture - Import Non-Episodic
Specific Setup:
  • Perceptive must be configured and enabled.
  • Please note: this is for Avatar NX systems only.
  • A client must be enrolled in an existing episode (Client A).
  • A Documentation View must be set up on a user's view containing the 'All Documents' widget and the 'Console Widget Viewer' ('All Documents' view).
Steps
  1. Select "Client A" and launch the 'Client Dashboard'.
  2. Click 'Document Capture' icon.
  3. Validate a 'Capture Mode' dialog stating: "How would you like to capture documents?"
  4. Click [Import].
  5. Select "Non-episodic" in the "Episode" field.
  6. Validate the 'Document Capture' opens in a new window.
  7. Select any value in the 'Document Type' field.
  8. Enter any value in the 'Document Description' field.
  9. Click [Capture] and [Browse].
  10. Locate the file to be imported and click [Open] and [Done].
  11. Validate the image displays.
  12. Click [Save].
  13. Validate a message stating: "Save Was Successful." and "Document Added to Avatar!"
  14. Click [Close Document Capture].
  15. Close the 'Client Dashboard'.
  16. Navigate to the 'All Documents' view.
  17. Validate the newly imported non-episodic document is present and select it.
  18. Validate the 'Console Widget Viewer' displays the document as expected.
  19. Click [Close All].
  20. Validate the 'Console Widget Viewer' no longer displays the document.
Scenario 2: Client Chart - Document Capture - Import Non-Episodic
Specific Setup:
  • Perceptive must be configured and enabled.
  • Please note: this is for myAvatar systems only.
  • A client is enrolled in an existing episode (Client A).
Steps
  1. Select "Client A" and access the 'Client Chart'.
  2. Click "Document Capture".
  3. Import a non-episodic document.
  4. Select the desired value in the 'Document Type' field.
  5. Enter the desired value in the 'Document Description' field.
  6. Save the document.
  7. Validate messages display that indicate the document was successfully saved.
  8. Refresh the 'Client Chart'.
  9. Select the document type from the list that the document was just saved under.
  10. Select the non-episodic document that was just saved from the document list.
  11. Validate the document displays as expected.
  12. Click [Close All Documents] and close the 'Client Chart'.
Topics
• Document Capture • Perceptive
Update 99 Summary | Details
'User File Import' form
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • User File Import
Scenario 1: User File Import - File Validations
Specific Setup:
  • Have a "User File Import" file created that includes a user that has a 'User Description' greater than 40 characters (File A).
  • Have a "User File Import" file created that includes a user that has a 'User Description' less than 40 characters (File B).
Steps
  1. Access the 'User File Import' form.
  2. Click [Select User Import File].
  3. Select "File A" and click [Open].
  4. Validate the 'Import File Scan Results' field contains: Row 1 new user description is greater than 40 characters. Import file cannot be processed due to one or more errors.
  5. Validate the [Process User Import File] button is disabled.
  6. Click [Select User Import File].
  7. Select "File B" and click [Open].
  8. Validate the 'Import File Scan Results' field contains: No errors or warnings detected in import file.
  9. Click [Process User Import File].
  10. Validate a message is displayed stating: Import Completed!
  11. Click [OK] and close the form.
  12. Access the 'User Definition' form.
  13. Select the user imported via "File B" in the 'Select User' field.
  14. Validate all imported data is displayed as expected.
  15. Close the form.
Topics
• User Definition
Update 103 Summary | Details
Avatar NX - Dialog boxes
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • User Role Definition
  • Service Codes
  • Service Fee/Cross Reference Maintenance
  • CPT Code Definition (PM)
Scenario 1: Service Fee/Cross Reference Maintenance - Add/Edit Service Fee Definition
Specific Setup:
  • Service Codes:
  • Add a new service code for testing purposes (Service Code A).
  • CPT Code Definition:
  • A CPT Code must be defined (CPT Code A).
Steps
  1. Access the ‘Service Fee/Cross Reference Maintenance’ form.
  2. Select "Enter New" in the ‘Enter New Or Edit Existing Fee/Cross Reference’ field.
  3. Enter "Service Code A" in the 'Service Code' field.
  4. Enter the desired date in the ‘From Date’ field.
  5. Enter the desired value in the 'Fee' field.
  6. Enter "CPT Code A" in the 'CPT-4 / HCPCS Code' field.
  7. Enter desired value with quotation marks into the 'CPT-4 / HCPCS Modifier' field.
  8. Click [Submit].
  9. Click [Yes].
  10. Select "Edit Existing" in the ‘Enter New Or Edit Existing Fee/Cross Reference’ field.
  11. Enter "Service Code A" in the 'Service Code' field.
  12. Enter the same date in the ‘From Date’ field.
  13. Click [Select Fee/Cross Ref To Edit/Default From Existing Row].
  14. Select the desired row that filed in above steps.
  15. Click [OK].
  16. Validate that the entered 'Fee' exists.
  17. Validate that the entered 'CPT-4 / HCPCS Code' exists.
  18. Validate that the selected ‘CPT-4 / HCPCS Modifier’ exists.
  19. Close the form.
  20. Access the ‘Service Fee/Cross Reference Maintenance’ form.
  21. Select "Enter New" in the ‘Enter New Or Edit Existing Fee/Cross Reference’ field.
  22. Enter "Service Code A" in the 'Service Code' field.
  23. Enter the same date entered in the previous steps in the 'From Date' field.
  24. Click [Submit].
  25. Validate a dialog is displayed stating: Fee Definition already exists, please edit the existing definition.
  26. Click [OK] and validate the dialog closes.
  27. Validate a 'Filing Error' dialog stating "Filing aborted." and click [OK].
  28. Validate the form is still open with the data entered in the previous steps.
  29. Close the form.
Topics
• NX • Service Fee/Cross Reference Maintenance
 

RADplus_2023_Monthly_Release_2023.03.00_Details.csv