Skip to main content

RADplus 2024 Monthly Release 2024.00.00 Acceptance Tests

  1. Last updated
  2. Save as PDF
Update 1 Summary | Details
2024 Update installation
Scenario 1: Validate Upgrading RADplus 2023 to 2024 is successful when 2023.04.00 is loaded
Steps
  1. Open the "Product Updates" form.
  2. Select the appropriate [Namespace] from the Application dropdown list
  3. Click [Select Update/Customization Pack].
  4. Browse to the location for the updates and select the Update 1.
  5. Click [OK] on the "File Upload Complete" window.
  6. Click [Review Update/Customization Pack Contents].
  7. Verify Update 1 is included.
  8. Click [Install Update/Customization Pack].
  9. Click [OK] when the install completes.
  10. Click [Close Form].
Topics
• Upgrade
Update 4 Summary | Details
Form Definition - 'Document Routing' section
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Envelope Export (PM)
Scenario 1: Validate document routing settings in "Form Definition"
Specific Setup:
  • Have a modeled form with a "Draft/Final" or a "Draft/Final/Pending" field (Form A).
Steps
  1. Access the 'Form Definition' form.
  2. Select "Form A".
  3. Navigate to the "Document Routing" section.
  4. Validate the 'Defer Document Generation' field is not displayed.
  5. Select "Yes" in the 'Enable Document Routing' field.
  6. Click [Select Type].
  7. Select the desired value and click [OK].
  8. Select the desired value in the 'Approver Required' field.
  9. Click [Submit].
  10. Validate the form files successfully.
  11. Access the 'Form Definition' form.
  12. Select "Form A".
  13. Navigate to the "Document Routing" section.
  14. Validate all previously populated fields are displayed as expected.
  15. Close the form.
Topics
• Modeling • Document Routing
Update 8 Summary | Details
IRIS/AWS - Servers
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Guardiant
  • General / Avatar Licensing Graph
  • SMP IRIS
  • SMP IRIS - Home
  • SMP License Usage
Scenario 1: Guardiant Metric "Analytics" Data - Validations
Specific Setup:
  • Have a system configured for "Guardiant" reporting
  • Logged in user has access to the "Guardiant" form in Avatar and the "Guardiant" application
Steps
  1. Open form "Guardiant"
  2. Click [Test Daily Collection]
  3. Click [Yes] to the warning message
  4. Validate message "Test Succeeded" is displayed
  5. Click [Test Metrics Collection]
  6. Click [Yes] to the warning message
  7. Validate message "Test Succeeded" is displayed
  8. Log into "Guardiant"
  9. At the "Client Search", select the desired client account number
  10. In the right-hand corner, click "Analytics"
  11. Navigate down to "General/Avatar Licensing" graph
  12. In the right corner of the graph set the date range to the desired range, for example "60" days
  13. Click the 'Refresh' button in the graph
  14. In graph, mouse over the most recent date in the graph
  15. Validate the date and values displayed for the following statistics, are as expected
  16. Number of Named Users
  17. Number of application logins
  18. In graph, mouse over the oldest date in the graph
  19. Validate the date and values displayed for the following statistics, are as expected
  20. Number of Named Users
  21. Number of application logins
IRIS/AWS - Servers
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Crystal Reports or other SQL Reporting tool (ReportA)
  • SMP IRIS
  • SMP IRIS - Home
  • SMP License Usage
  • License Usage
  • SoapUI - ClientDemographics - Request
  • SoapUI - ClientDemographics
Scenario 1: "Avatar Sessions" Widget - Column data validations
Specific Setup:
  • Have user [UserA] logged in who has the "Avatar Sessions" widget on their desktop.
  • Have another user [UserB] who has not logged in yet.
  • Have a third user [UserC] who has an ODBC connection created to connect to the testing system, that is configured using his UserID and password
  • [UserC] has a report created [ReportA], to display data in a table in the testing system, using his ODBC connection
Steps
  1. Log in as [UserA] and note the date and time of login
  2. Navigate to the "Avatar Sessions" widget
  3. Refresh the widget and note the current date and time
  4. Validate the "UserID" column of the widget includes the expected user ID associated with [UserA].
  5. On a Netsmart hosted system
  6. Validate the "Login Date" and "Login Time" are consistent with time a date noted in step 1
  7. Validate the "Last Activity" date and time are consistent with the date and time noted in step 2a
  8. Note the current number of connections stated in the "# of Connections" column
  9. Launch any form
  10. Refresh the "Avatar Sessions" widget
  11. Validate the number of connections in the "# of Connections" column has incremented by 1
  12. Close the form just launched
  13. Validate the number of connections in the "# of Connections" column has decreased by 1
  14. Log in as [UserB] and note the current date and time.
  15. Navigate to the "Avatar Sessions" widget and refresh the widget
  16. Validate a row for both [UserA] and [UserB] are listed in the widget
  17. Validate the "UserID" column of the widget includes the expected user ID associated with [UserA]
  18. Validate the "UserID" column of the widget includes the expected user ID associated with [UserB]
  19. Repeat step 2b for [UserB]
  20. Validate results are as expected
  21. As [UserC], Open [ReportA]
  22. Click to generate the report. Note the date and time
  23. Validate the report launches successfully
  24. As [UserA], Click the 'Refresh' button on the "Avatar Sessions" widget
  25. Validate a row for both [UserA] and [UserB] are listed in the widget
  26. Validate in the "UserID" column of the widget includes the expected user ID associated with [UserA]
  27. Validate in the "UserID" column of the widget includes the expected user ID associated with [UserB]
  28. Validate a new row is present in the widget for [UserC]
  29. Validate in the "UserID" column of the widget includes the expected user ID associated with [UserC].
  30. Note the number of connections in the "# of Connections" column
  31. As [UserC], close [ReportA]
  32. As [UserA], Click the 'Refresh' button on the "Avatar Sessions" widget
  33. Validate the row for [UserC] is no longer present in the widget, as expected
  34. Validate the rows for [UserA] and [UserB] are still present
  35. As [UserB], Log out of Avatar
  36. As [UserA], Click the 'Refresh' button on the "Avatar Sessions" widget
  37. Validate the row for [UserB] is no longer present in the widget, as expected
  38. Validate the row for [UserA] is present, as expected
Topics
• Guardiant • Cache • Widgets • Forms Designer • Query/Reporting
Update 11 Summary | Details
OE - External Lab Definition - Order Code Setup - Lab Vendor Name with apostrophe
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • External Lab/Radiology Definition for CareConnect
  • Order Code Setup
  • Order Group Setup
  • Orders This Episode
Scenario 1: OE NX - Order Code Setup - External Lab Definition - Lab Vendor Name with apostrophe
Specific Setup:
  • A lab vendor must be configured in the 'External Lab/Radiology Definition for CareConnect' form where the 'Lab Vendor Name' contains an apostrophe. (Lab Vendor A).
  • A lab-type order code must exist that has the 'External Lab Definition' configured with "Lab Vendor A". (Lab Code A).
  • A client must have an active episode. (Client A)
  • “Client A” must have a ‘Date of Birth’, ‘Sex’ and address on file in the ‘Update Client Data’ form, as well as information filed in the ‘Allergies and Hypersensitivities’ form, ‘Diagnosis’ form, and in the ‘Height’ and ‘Weight’ fields in the ‘Vitals Entry’ form.
Steps
  1. Access the 'Order Code Setup' form.
  2. Search for and select a lab-type order code.
  3. Click [External Lab Definition].
  4. Validate the 'External Lab Definition' dialog is displayed.
  5. Select "Lab Vendor A" in the 'Lab Vendor Name' cell.
  6. Populate all other required fields and click [Save] and file the form.
  7. Select "Client A" and access the Order Entry Console.
  8. Search for and select "Lab Code A" in the 'New Order' field.
  9. Populate all required fields.
  10. Validate the 'External Lab Vendor Destination' field contains "Lab Vendor A".
  11. Click [Add to Scratchpad] and [Sign].
  12. Validate the 'Order grid' contains a new order.
Topics
• Order Entry Console • NX
Update 13 Summary | Details
Avatar NX - To Do notifications
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • TO DO'S
  • Progress Notes (Group and Individual)
Scenario 1: Avatar NX Login - Validate 'Workflow Management' notifications
Specific Setup:
  • Please note: this test is for Avatar NX only.
  • Two views must be defined (View A & View B):
  • "View A" does not have the 'My To Do's' widget assigned.
  • "View B" has the 'My To Do's' widget assigned.
  • The logged in user must have To Do's pending in the 'My To Do's' widget (User A).
  • "User A" must have "View B" as their 'HomeView' in the 'User Definition' form.
Steps
  1. Access the 'NX View Definition' form.
  2. Select "User" in the 'User or Role' field.
  3. Select "User A" in the 'Select User' field.
  4. Select "View A" in the 'myDay' field. This view does not have the 'My To Do's' widget associated.
  5. Click [File].
  6. Log out.
  7. Login to Avatar NX as "User A".
  8. Validate a 'Workflow Management' dialog is displayed stating: There are one or more open items within your Workflow Management To Do List.
  9. Click [OK].
  10. Validate the 'My To Do's' widget is not present on the myDay view.
  11. Access the 'NX View Definition' form.
  12. Select "User" in the 'User or Role' field.
  13. Select "User A" in the 'Select User' field.
  14. Select "View B" in the 'myDay' field. This view has the 'My To Do's' widget associated.
  15. Click [File].
  16. Log out.
  17. Login to Avatar NX as "User A".
  18. Validate no 'Workflow Management' dialog is displayed, since the 'My To Do's' widget is present on the myDay view.
'Template On Demand' widgets
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Progress Notes (Group and Individual)
  • Widget Import (PM)
  • View Definition
Scenario 1: Validate 'Template On Demand' widgets in scrolling free text fields
Specific Setup:
  • Please note: this test is for Avatar NX systems only.
  • The 'Enable Templates On Demand for SQL Widgets' registry setting must be set to "Y".
  • Must have a widget with "Yes" selected in the 'Use for Templates On Demand' field in 'Widget Definition' (Widget A).
  • Two views must be defined (View A & View B).
  • "Widget A" must be assigned to "View A" but is not assigned to "View B".
  • The logged in user (User A) must have the following:
  • "View A" assigned as their myDay view in the 'NX View Definition' form.
  • "View B" assigned as their HomeView in the 'User Definition' form.
  • A client is enrolled in an existing episode (Client A).
  • This client must also have data on file that will populate in "Widget A".
Steps
  1. Log into Avatar NX as "User A".
  2. Validate "Widget A" is present on the myDay view.
  3. Access the 'Progress Notes (Group and Individual)' form.
  4. Select "Client A" in the 'Select Client' field.
  5. Select the desired episode in the 'Select Episode' field.
  6. Select "Independent Note" in the 'Progress Note For' field.
  7. Select the desired value in the 'Note Type' field.
  8. Click on the [Template Icon] in the 'Notes Field'.
  9. Click [Widget Templates] and [Templates].
  10. Validate "Widget A" is available for selection and select it.
  11. Validate the 'Notes Field' populates with the data on file for the client accordingly.
  12. Populate any other required and desired fields.
  13. File the note.
The 'SYSTEM.RADplus_users' and 'SYSTEM.RADplus_user_roles' SQL tables
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • User Role Definition
Scenario 1: Query SQL Tables - SYSTEM.RADplus_users and SYSTEM.RADplus_user_roles
Specific Setup:
  • Have an Avatar system that has an "ECP" server configured by Netsmart Representative in order to connect to the Avatar server via the "ECP" server for reporting.
  • Various users and user roles are defined.
Steps
  1. Access Crystal Reports or other SQL Reporting Tool.
  2. Create a report using the 'SYSTEM.RADplus_users' SQL table.
  3. Validate the report displays in a timely manner and contains the users defined in the system.
  4. Close the report.
  5. Create a report using the 'SYSTEM.RADplus_roles' SQL table.
  6. Validate the report displays in a timely manner and contains the user roles defined in the system.
  7. Close the report.
Topics
• NX View Definition • My To Do's • Progress Notes • Widgets • User Role Definition • Query/Reporting
Update 15 Summary | Details
'All Documents' widget - Progress Notes
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Progress Notes (Group and Individual)
  • Append Progress Notes
  • All Documents Widget Definition
  • View Definition
  • CONSOLE WIDGET VIEWER widget
Scenario 1: 'All Documents' widget - Validate 'Progress Notes' records
Specific Setup:
  • Please note: this is for Avatar NX 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).
  • The 'All Documents' widget must contain a 'Multi-Progress Notes Tab' with all note types assigned for the 'Progress Notes (Group and Individual)' form.
  • Document routing is enabled on the 'Progress Notes (Group and Individual)' form.
Steps
  1. Select "Client A" and access the 'Progress Notes (Group and Individual)' form.
  2. Select the desired episode in the 'Select Episode' field.
  3. Select "Independent Note" in the 'Progress Note For' field.
  4. Select the desired value in the 'Note Type' field.
  5. Enter the desired value in the 'Notes Field'.
  6. Select "Final" in the 'Draft/Final' field.
  7. Click [File Note].
  8. Validate a 'Confirm Document' dialog containing the progress note details.
  9. Click [Accept].
  10. Enter the password associated with the logged in user and click [Verify].
  11. Close the form.
  12. Select "Client A" and navigate to the 'All Documents' view.
  13. In the 'All Documents' widget, select the 'Multi-Progress Notes Tab'.
  14. Validate the progress note filed in the previous steps is displayed with "Final" as the 'Workflow Status'.
  15. Select the progress note for viewing.
  16. Validate the 'Console Widget Viewer' displays the finalized progress note from the previous steps.
  17. Validate an [Append] button is displayed and click it.
  18. Validate the 'Append Progress Notes' form is displayed.
  19. Enter the desired value in the 'New Comments to Be Appended to the Original Note' field.
  20. Click [Submit].
  21. Validate a 'Confirm Document' dialog containing the progress note details & appended notes.
  22. Click [Accept].
  23. Enter the password associated with the logged in user and click [Verify].
  24. Click [Close All] in the 'Console Widget Viewer'.
  25. Refresh the 'All Documents' widget.
  26. Select the progress note appended in the previous steps for viewing.
  27. Validate the 'Console Widget Viewer' displays the finalized progress note with the appended notes at the end.
  28. Click [Close All].
Topics
• All Documents Widget
2023 Update 91 Summary | Details
'Connect/Disconnect Application Namespace'
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Application Namespace Connections Validation
  • Connect/Disconnect Application Namespace
Scenario 1: "Connect/Disconnect Application Namespace" form - Validate form submission and application connection error corrections
Specific Setup:
  • Logged in user has access to the "Connect/Disconnect Application Namespace" form
  • Logged in user has access to the "Application Namespace Connections Validation" form
Steps
  1. Open form "Applications Namespace Connection Validations":
  2. Validate "Currently Connected Namespaces" text box lists the expected child applications and namespaces:
  3. If the message "There are one or more application namespace errors", is displayed
  4. Click [Process] to review the details.
  5. Make a note of any application errors stated in the results. For example, an application "Mapping" type error and note which application for example "CWS", "MSO" that the error pertains to.
  6. Exit the form.
  7. Open the "Connect/Disconnect Application Namespace" form:
  8. From the "Application" field, select the application noted in step 1, that the error was reported in:
  9. For an application currently configured with its "(CDR) Clinical Data Repository" enabled
  10. Select "Yes" in the field "Clinical Data Repository (CDR) Link", otherwise select "No".
  11. In the "Connect or Disconnect" field, select:
  12. "Connect/Maintain Connection/Repair Connection".
  13. Submit the form (Note submission can take some time):
  14. Validate submission is successful.
  15. Open form "Applications Namespace Connection Validations":
  16. Validate "Currently Connected Namespaces" text box lists the expected child applications and namespace(s):
  17. Validate there is now a message stating "There are no Application/Namespace errors".
  18. Close the form.
Topics
• Database Management • Cache
2023 Update 113 Summary | Details
NX - Dynamic Forms
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Member Enrollment
  • User Role Definition
  • View Definition
Scenario 1: Dynamic Form - Validations
Specific Setup:
  • The logged in user [TestUserA], has access to the following forms:
  • "Basic Troubleshooting", "Treatment Plan", "Member Enrollment", "Treatment Plan", plan, User Definition", "User Role Definition" and "View Definition"
  • In form "User Definition"
  • Have another user [TestUserB], that can be used for testing
  • User [TestUserB] is not logged in
  • Log in as [TestUserA]
Steps
  1. Open form "Basic Troubleshooting"
  2. Click the [Test Dynamic Forms] button
  3. Validate message "Test Successful", is displayed
  4. Click the [OK] button
  5. Set the "Duration (minutes)" field to "1"
  6. Click the [Submit] button
  7. Verify the message window "Submitting... Please Wait", is displayed
  8. Wait "1" Minute
  9. Verify the message window "Submitting... Please Wait" displays and closes the form
  10. Validate user is returned to their home screen
  11. Open the "Treatment Plan" form and select the desired client in the "Select Client" search field
  12. Populate the "Plan Date" field
  13. Populate any other desired fields
  14. Set the "Draft/Final" to "Draft"
  15. Click the Launch Plan button
  16. Click the [Add New Problem] button
  17. Click the [Return to Plan] button
  18. Validate the "Plan Saved" message is displayed and click [OK]
  19. Set the "Draft/Final" field to "Final"
  20. Click [Submit]
  21. Validate the message "Cannot finalize plan until the following required fields are completed"
  22. Click the OK button
  23. Populate any missing required fields
  24. Click the [Submit] button
  25. Validate the form files successfully
  26. Open the Member Enrollment - Avatar MSO / Membership Management form
  27. Populate the "Last Name" field with a name that is not on file yet as a member
  28. Populate the "First Name" field
  29. Populate the Sex" field
  30. Click the Search button
  31. Validate the message "Search Results - No Matches found", is displayed
  32. Click [OK] button
  33. Click the New Client button
  34. Click the "Auto Assign ID Number" dialog, "Yes" button
  35. Validate the "Name" field is populated as expected
  36. Populate any other desired fields
  37. Submit the form
  38. Validate the form files successfully
  39. Open form "User Definition"
  40. Select [TestUserB]
  41. Click the "Generate New Password" button
  42. Make a note of the temporary password populated in the "System Generated Password" field
  43. Submit the form
  44. Log out as [TestUserA]
  45. Log in as [TestUserB]
  46. Validate the user is promoted with the dialog, "Your current password is system generated. You must enter a new password".
  47. Click [OK]
  48. At the "New password entry" dialog
  49. Populate the "Enter New Password" field
  50. Populate the "Re-enter New Password" field with same password
  51. Click [OK]
  52. Validate [TestUserB] is logged in successfully
  53. Open form "User Role Definition"
  54. Click [Select User Role]
  55. Validate the "Select User Role" dialog is displayed
  56. Click [Cancel]
  57. Validate user is returned to the form
  58. Click [Select User Role]
  59. Validate the "Select User Role" dialog is displayed
  60. From the "Select one of the following" field
  61. Select a desired user role and click [OK]
  62. Validate the information for the user role selected, is populated as expected
  63. Close the form
  64. At the "Confirm Close" dialog
  65. Click [Yes]
  66. Open form "View Definition"
  67. Click "Select View"
  68. Validate "Select Views" dialog is displayed
  69. Click [Cancel]
  70. Validate user is returned to the form
  71. Click "Select View"
  72. Validate "Select Views" dialog is displayed
  73. Select a view form the "Views" list
  74. Click [OK]
  75. Validate the information for the view selected, is populated as expected
  76. At the "Confirm Close" dialog
  77. Click [Yes]
  78. Validate the user is returned to the homeview
Topics
• Forms • Cache • NX
2023 Update 123 Summary | Details
Modeled Forms
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Modeled Form w/ Multi Iteration Section
  • Program Maintenance
Scenario 1: Validate filing Modeled forms that contain "Multiple Iteration" sections with inactive and active programs
Specific Setup:
  • The test system contains multiple system codes.
  • A modeled form has been created that is client related and contains two dictionaries mapped to the 'Program' dictionary, one on the main section and one on a multiple iteration section. Also include a dictionary not mapped to the program dictionary.
  • Test user has access to the modeled form.
  • Use the modeled form to create a record for desired client. Select an active program in the main section of the form, noting the program. In the multiple iteration section, create at least two rows with active programs, noting the programs.
  • Program Maintenance: Set the programs to 'Inactive'.
Steps
  1. Open the modeled form for the client.
  2. Validate that the program in the main section displays as inactive.
  3. Select the multiple integration section and verify that the programs display as inactive.
  4. Close the form.
  5. Open 'Program Maintenance' and make all the programs active again, filing after each program.
  6. Close the form.
  7. Open the modeled form for the client.
  8. Validate that the program in the main section displays as active.
  9. Select the multiple integration section and verify that the programs display as active.
  10. Close the form.
Topics
• Modeling • NX
2023 Update 127 Summary | Details
'Define EHI' - 'EHI Export' Form
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • EHI Export
Scenario 1: EHI Export - Field Validations
Specific Setup:
  • User must have access to the 'EHI Export' form in 'User Definition'.
Steps
  1. Access the 'EHI Export' form.
  2. Validate the "Define EHI" section is displayed.
  3. Validate the 'Forms Included in EHI Export' field is displayed. This will contain a list of forms that file to a table that has a 'PATID' field.
  4. Validate the 'Integrated Application Assessments to Include in EHI Export' field is displayed. This will contain a list of all integrated CareFabric assessments (if configured).
  5. Validate a 'Save' button is displayed. This will be used to save the above definitions.
  6. Navigate to the "Export EHI" section.
  7. Validate a message is displayed stating: Warning: This option allows an organization to export all EHI related information in this system. This can be completed for an individual client/patient or the entire database. Additionally, users can choose a date range to only export information entered into the system during a specific time period. Please note, a complete database extract may have performance implications and should not be done during peak business hours. Additionally, users should ensure that the location they choose to export is both secured and with ample space to accommodate the extracts.
  8. Validate the 'Export the Following' field is displayed and contains the following options:
  9. 'Data and Documentation' - this will export a documentation file for all forms/assessments defined in the "Define EHI" section and files for all applicable data on file for the selected client(s).
  10. 'Data Only' - this will export files for all applicable data on file for the selected client(s) based on the forms/assessments defined in the "Define EHI" section.
  11. 'Documentation Only' - this will export a documentation file for all forms/assessments defined in the "Define EHI" section.
  12. Validate the 'Select Client' field is displayed. This gives the user the ability to export EHI for a specific client.
  13. Validate the 'Entered During Start Date' and 'Entered During End Date' fields are displayed. This gives the user the ability to export EHI for a particular date range.
  14. Validate the 'Select Export Location' field is displayed.
  15. Validate the 'Reason For Export' field is displayed.
  16. Validate the 'Process' button is displayed. This will be used to initiate the export.
  17. Close the form.
Scenario 2: EHI Export - Export Data and Documentation
Specific Setup:
  • User must have access to the 'EHI Export' form in 'User Definition'.
  • A client is enrolled in an existing episode and has data filed in multiple forms & integrated application assessments (Client A).
  • Additional clients must be enrolled in existing episodes and have data on file in multiple forms & integrated application assessments.
Steps
  1. Access the 'EHI Export' form.
  2. Validate the "Define EHI" section is displayed.
  3. Select the desired form(s) in the 'Forms Included in EHI Export' field.
  4. Select the desired assessment(s) in the 'Integrated Application Assessments to Include in EHI Export' field (if configured).
  5. Click [Save].
  6. Validate a message is displayed stating: Saved!
  7. Click [OK].
  8. Navigate to the "Export EHI" section.
  9. Select "Data and Documentation" in the 'Export the Following' field.
  10. Enter the desired date in the 'Entered During Start Date' field.
  11. Enter the desired date in the 'Entered During End Date' field.
  12. Enter the desired file path in the 'Select Export Location' field.
  13. Enter the desired value in the 'Reason for Export' field.
  14. Click [Process].
  15. Validate a message is displayed stating: You do not have a Client selected. Proceeding with this export will export data for ALL clients that currently exist in the database. This can result in a large amount of data being created on the myAvatar server. Are you sure that you want to proceed with this export?
  16. Click [Yes].
  17. Validate a message is displayed stating: Export has been initiated. Once completed the contents of the export can be found in the directory: Example Directory\Folder Name
  18. Click [OK].
  19. Navigate to the directory of the export file.
  20. Validate a 'form_documentation' file is displayed.
  21. Open the file and validate it contains all documentation for the selected forms & assessments selected in the "Define EHI" section.
  22. Close the 'form_documentation' file.
  23. Validate a file is displayed for each table associated to the selected forms & assessments in the "Define EHI" section.
  24. Validate each file contains the appropriate data for the selected date range.
  25. Please note: if any data files that were output contain a "^" character, it will be replaced with "\S\" in the export file. Additionally, if any data files that were output contain a new line character, it will be replaced with "\.br\." in the export file.
  26. Navigate back to the 'EHI Export' form.
  27. Validate "Data and Documentation" is selected in the 'Export the Following' field.
  28. Validate the 'Entered During Start Date' and 'Entered During End Date' fields no longer contain a value.
  29. Select "Client A" in the 'Select Client' field.
  30. Click [Process].
  31. Validate a message is displayed stating: You do not have a date range selected. Proceeding will export all data regardless of the date it was created. This can result in a large amount of data being created on the myAvatar server. Are you sure you want to proceed with this export?
  32. Click [Yes].
  33. Validate a message is displayed stating: Export has been initiated. Once completed the contents of the export can be found in the directory: Example Directory\Folder Name
  34. Click [OK] and close the form.
  35. Navigate to the directory of the export file.
  36. Validate a 'form_documentation' file is displayed.
  37. Open the file and validate it contains all documentation for the selected forms & assessments selected in the "Define EHI" section.
  38. Close the 'form_documentation' file.
  39. Validate a file is displayed for each table associated to the selected forms & assessments in the "Define EHI" section.
  40. Validate each file contains the appropriate data for "Client A".
  41. Please note: if any data files that were output contain a "^" character, it will be replaced with "\S\" in the export file. Additionally, if any data files that were output contain a new line character, it will be replaced with "\.br\." in the export file.
Scenario 3: EHI Export - Export Documentation Only
Specific Setup:
  • User must have access to the 'EHI Export' form in 'User Definition'.
Steps
  1. Access the 'EHI Export' form.
  2. Validate the "Define EHI" section is displayed.
  3. Select the desired form(s) in the 'Forms Included in EHI Export' field.
  4. Select the desired assessment(s) in the 'Integrated Application Assessments to Include in EHI Export' field (if configured).
  5. Click [Save].
  6. Validate a message is displayed stating: Saved!
  7. Click [OK].
  8. Navigate to the "Export EHI" section.
  9. Select "Documentation Only" in the 'Export the Following' field.
  10. Validate the 'Select Client' field becomes disabled.
  11. Validate the 'Entered During Start Date' and 'Entered During End Date' fields become disabled.
  12. Enter the desired file path in the 'Select Export Location' field.
  13. Enter the desired value in the 'Reason for Export' field.
  14. Click [Process].
  15. Validate a message is displayed stating: Export has been initiated. Once completed the contents of the export can be found in the directory: Example Directory\Folder Name
  16. Click [OK] and close the form.
  17. Navigate to the directory of the export file.
  18. Validate a 'form_documentation' file is displayed.
  19. Open the file and validate it contains all documentation for the selected forms & assessments selected in the "Define EHI" section.
  20. Close the file.
Scenario 4: EHI Export - Export Data Only
Specific Setup:
  • User must have access to the 'EHI Export' form in 'User Definition'.
  • A client is enrolled in an existing episode and has data filed in multiple forms & integrated application assessments (Client A).
  • Additional clients must be enrolled in existing episodes and have data on file in multiple forms & integrated application assessments.
Steps
  1. Access the 'EHI Export' form.
  2. Validate the "Define EHI" section is displayed.
  3. Select the desired form(s) in the 'Forms Included in EHI Export' field.
  4. Select the desired assessment(s) in the 'Integrated Application Assessments to Include in EHI Export' field (if configured).
  5. Click [Save].
  6. Validate a message is displayed stating: Saved!
  7. Click [OK].
  8. Navigate to the "Export EHI" section.
  9. Select "Data Only" in the 'Export the Following' field.
  10. Enter the desired date in the 'Entered During Start Date' field.
  11. Enter the desired date in the 'Entered During End Date' field.
  12. Enter the desired file path in the 'Select Export Location' field.
  13. Enter the desired value in the 'Reason for Export' field.
  14. Click [Process].
  15. Validate a message is displayed stating: You do not have a Client selected. Proceeding with this export will export data for ALL clients that currently exist in the database. This can result in a large amount of data being created on the myAvatar server. Are you sure that you want to proceed with this export?
  16. Click [Yes].
  17. Validate a message is displayed stating: Export has been initiated. Once completed the contents of the export can be found in the directory: Example Directory\Folder Name
  18. Click [OK].
  19. Navigate to the directory of the export file.
  20. Validate a file is displayed for each table associated to the selected forms & assessments in the "Define EHI" section.
  21. Validate each file contains the appropriate data for the selected date range.
  22. Please note: if any data files that were output contain a "^" character, it will be replaced with "\S\" in the export file. Additionally, if any data files that were output contain a new line character, it will be replaced with "\.br\." in the export file.
  23. Navigate back to the 'EHI Export' form.
  24. Validate "Data Only" is selected in the 'Export the Following' field.
  25. Validate the 'Entered During Start Date' and 'Entered During End Date' fields no longer contain a value.
  26. Select "Client A" in the 'Select Client' field.
  27. Click [Process].
  28. Validate a message is displayed stating: You do not have a date range selected. Proceeding will export all data regardless of the date it was created. This can result in a large amount of data being created on the myAvatar server. Are you sure you want to proceed with this export?
  29. Click [Yes].
  30. Validate a message is displayed stating: Export has been initiated. Once completed the contents of the export can be found in the directory: Example Directory\Folder Name
  31. Click [OK] and close the form.
  32. Navigate to the directory of the export file.
  33. Validate a file is displayed for each table associated to the selected forms & assessments in the "Define EHI" section.
  34. Validate each file contains the appropriate data for "Client A".
  35. Please note: if any data files that were output contain a "^" character, it will be replaced with "\S\" in the export file. Additionally, if any data files that were output contain a new line character, it will be replaced with "\.br\." in the export file.
Scenario 5: EHI Export - Define EHI
Specific Setup:
  • User must have access to the 'EHI Export' form in 'User Definition'.
Steps
  1. Access the 'EHI Export' form.
  2. Validate the "Define EHI" section is displayed.
  3. Select the desired form(s) in the 'Forms Included in EHI Export' field.
  4. Select the desired assessment(s) in the 'Integrated Application Assessments to Include in EHI Export' field (if configured).
  5. Click [Save].
  6. Validate a message is displayed stating: Saved!
  7. Click [OK] and close the form.
  8. Access the 'EHI Export' form.
  9. Validate the "Define EHI" section is displayed.
  10. Validate the 'Forms Included in EHI Export' field contains the form(s) saved in the previous steps.
  11. Validate the 'Integrated Application Assessments to Include in EHI Export' field contains the assessment(s) saved in the previous steps.
  12. Close the form.
Topics
• EHI Export
2023 Update 128 Summary | Details
Guardiant- "Avatar Licensing" graph
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Guardiant
  • CACHE - Home
  • Globals
  • View Global Data
  • General / Avatar Licensing Graph
Scenario 1: Guardiant Metric "Analytics" Data - Validations
Specific Setup:
  • Have a system configured for "Guardiant" reporting
  • Logged in user has access to the "Guardiant" form in Avatar and the "Guardiant" application
Steps
  1. Open form "Guardiant"
  2. Click [Test Daily Collection]
  3. Click [Yes] to the warning message
  4. Validate message "Test Succeeded" is displayed
  5. Click [Test Metrics Collection]
  6. Click [Yes] to the warning message
  7. Validate message "Test Succeeded" is displayed
  8. Log into "Guardiant"
  9. At the "Client Search", select the desired client account number
  10. In the right-hand corner, click "Analytics"
  11. Navigate down to "General/Avatar Licensing" graph
  12. In the right corner of the graph set the date range to the desired range, for example "60" days
  13. Click the 'Refresh' button in the graph
  14. In graph, mouse over the most recent date in the graph
  15. Validate the date and values displayed for the following statistics, are as expected
  16. Number of Named Users
  17. Number of application logins
  18. In graph, mouse over the oldest date in the graph
  19. Validate the date and values displayed for the following statistics, are as expected
  20. Number of Named Users
  21. Number of application logins
Topics
• Guardiant
2023 Update 129 Summary | Details
User Role Definition - forms permissions
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • User Role Definition
Scenario 1: User Role Definition - "Select Forms for User Access" validations
Specific Setup:
  • In form "User Role Definition", have a role [TestRole] created that can be used for testing
  • Logged in user has access to form "User Role Definition"
Steps
  1. Open form "User Role Definition"
  2. Click [Select User Role]
  3. Select [TestRole]
  4. Click [Select Forms for User Access]
  5. In the form's selection tree dialog:
  6. For each folder, navigate to the selection box to the right of the arrow. For example folders, "Avatar PM", "Avatar CWS"
  7. Click in the selection box till the box is empty, to order to remove all permissions to forms in that folder
  8. Click the arrow next to the folder to expand it
  9. Validate the form selection box for each form in the folder is not populated, as expected
  10. Click [OK] to save the changes
  11. Submit the form
  12. Validate a message is presented with a warning message that states "No forms are selected for this role, are you sure you want to continue?"
  13. Click "Yes" to submit the form
  14. At the "Form Return" dialog, click "Yes" to return to the form
  15. Click [Select User Role]
  16. Select [TestRole]
  17. Click [Select Forms for User Access]
  18. In the form's selection tree:
  19. Validate the selection box to the right of the arrow for each folder is not populated, as expected
  20. Click the arrow next to the folder to expand it
  21. Validate the form selection box for each form in the folder is not populated, as expected
  22. Staying in the form's selection tree dialog:
  23. For each folder, navigate to the selection box to the right of the arrow
  24. Click in the box once to select "RW" read/write access
  25. Now, click the arrow next to the folder to expand it
  26. Validate the form selection box for each form in the folder is populated with "RW", as expected
  27. Click [OK] to save the changes
  28. Submit the form
  29. At the "Form Return" dialog, click "Yes" to return to the form
  30. Click [Select User Role]
  31. Select [TestRole]
  32. Click [Select Forms for User Access]
  33. For each folder, navigate to the selection box to the right of the arrow
  34. Validate the selection box is populated with "RW", as expected
  35. Now, click the arrow next to the folder to expand it
  36. Validate the form selection box for each form in the folder is populated with "RW", as expected
  37. Staying in the form's selection tree dialog:
  38. For each folder, navigate to the selection box to the right of the arrow
  39. Click in the box once to select "R" read/write access
  40. Now click the arrow next to the folder to expand it
  41. Validate the form selection box for each form in the folder is populated with "R", as expected
  42. Click [OK] to save the changes
  43. Submit the form
  44. At the "Form Return" dialog, click "Yes" to return to the form
  45. Click [Select User Role]
  46. Select [TestRole]
  47. Click [Select Forms for User Access]
  48. For each folder, navigate to the selection box to the right of the arrow
  49. Validate the selection box is populated with "R", as expected
  50. Now, click the arrow next to the folder to expand it
  51. Validate the form selection box for each form in the folder is populated with "R", as expected
  52. Close the form
  53. Re-open form "User Role Definition"
  54. Click [Select User Role]
  55. Select [TestRole]
  56. Click [Select Forms for User Access]
  57. In the form's selection tree dialog:
  58. Navigate to one of the form selection folders, for this example "Avatar PM" is used, and click the arrow next to folders selection box to expand the folder
  59. Now select a subfolder on that folder and click the arrow next to it to expand that folder
  60. Click the arrow to expand one of the subfolder under that folder
  61. For one of the forms in that subfolder [FormA], click the form selection box till the box is empty
  62. For another form in that subfolder [FormB], click the form selection box till the box is populated with "RW"
  63. For another one of the forms in the folder [FormA], click the form selection box till the box is populated with "R"
  64. Click [OK] to save the changes
  65. Submit the form
  66. At the "Form Return" dialog, click "Yes" to return to the form
  67. Click [Select User Role]
  68. Select [TestRole]
  69. Click [Select Forms for User Access]
  70. In the form's selection tree dialog
  71. Navigate to back to the subfolder selected with specific form permissions in step 2b
  72. Click the arrow next to the folder's selection box to expand the folder to display the forms
  73. Validate the form selection box for [FormA] is empty, as expected
  74. Validate the form selection box for [FormB] is contains "RW", as expected
  75. Validate the form selection box for [FormC] is contains "R", as expected
  76. Close the form
Topics
• User Role Definition • NX
2023 Update 130 Summary | Details
Form Bundles
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Simultaneous Bundle
Scenario 1: Simultaneous Form Bundle Validation
Specific Setup:
  • Have two form bundles set a with the type of bundle set to "Simultaneous"
  • [BundleA] contains:
  • The first form [FormA] being the "Admission" form. Then followed by [FormB] and [FormC], which can be any other forms
  • [BundleB] contains:
  • The first form [FormA] being any "Episodic" type form. Then followed by [FormB] a "Non-Episodic" form and then [FormC] which is another "Episodic" form
  • [TestClient] is admitted in one or more active episodes
  • The logged in user has permission to access all forms contained in the bundles
Steps
  1. At the home view, select [TestClient]
  2. Open [BundleA]
  3. Validate the user is presented with [FormA] the "Admission" form and its ready for data entry
  4. Validate no other forms in the bundle have loaded yet in a tab. [Note: this is the expected behavior]
  5. Populate and submit the "Admissions" form
  6. Validate submission is successful
  7. Validate now that [FormB] and [FormC] have each loaded in a separate tab, as expected
  8. Click the tab for [FormB] and then quickly the tab for [FormC]
  9. Validate [FormC] will not load until [FormB] has fully loaded
  10. Click back to the tab for [FormB]
  11. Validate it has loaded and displays as expected
  12. Submit the form
  13. Validate the form submits successfully
  14. Now click the tab for [FormC]
  15. Validate [FormC] has loaded and displays as expected
  16. Submit the form
  17. Validate the form submits successfully
  18. Open [BundleB]
  19. Validate [FormA] the episodic form, is loaded at the episode selection screen
  20. Click the tab for [FormC] the second episodic form, while the form is loading....
  21. Click back to the tab for [FormA]
  22. Validate the user is able to select an episode and click to open the form
  23. Validate [FormA] loads and displays as expected
  24. Populate and submit the form
  25. Validate the form submits successfully
  26. Click back to the tab for [FormC]
  27. Validate [FormC] is loaded at the episode selection screen
  28. Click the tab for [FormB], while the form is loading.......
  29. Click back to the tab for [FormC]
  30. Validate the user is able to select an episode and click to open the form
  31. Validate [FormC] loads and displays as expected
  32. Submit the form
  33. Validate the form submits successfully
Topics
• Forms
 

RADplus_2024_Monthly_Release_2024.00.00_Details.csv