Skip to main content

RADplus 2022 Monthly Release 2022.04.00 Acceptance Tests

  1. Last updated
  2. Save as PDF
Update 112 Summary | Details
Envelope and Report Definition Forms
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Envelope Export (PM)
  • ModeledForm
  • Report Definition (PM)
  • Report Definition Export
  • Report Definition Import (PM)
Scenario 1: Envelope Export - validations
Specific Setup:
  • Have an existing Modeled form [FormA] that exists in [EnvelopeA]
Steps
  1. Open form "Envelope Definition"
  2. Select [EnvelopeA]
  3. Note the value in the "Envelope Version Number" field, for example "1.01"
  4. Close the form
  5. Open form "Envelope Export"
  6. Select [EnvelopeA]
  7. Click [Begin Export]
  8. In the "File Explorer" dialog, select a folder location in the "Save In" field to save the export file.
  9. In the "File_Name" field, validate that the file name populated includes the name of [ReportA], appended by a "V" followed by the "Report Version Number" value noted in step 1 and the file extension. For example "NetsmartExportModeledFormV1_01.TXT"
  10. Click [Save]
  11. Close the form
  12. Open file "Envelope Import"
  13. Click [Select Envelope Import File]
  14. In the "File Explorer" dialog, navigate to the location of the export file
  15. Select the file and click [Open]
  16. Select the "Overwrite Existing" radio button
  17. Click [Begin Import Scan]
  18. Click [Begin Import]
  19. At the "Import Complete" dialog, click [OK]
  20. Close the form
  21. At the Home View, search for [FormA] and open the form
  22. Populate the desired fields on the form
  23. Submit the form
  24. Validate the form files successfully
Scenario 2: Report Definition Export - validations
Specific Setup:
  • In form "Report Definition", have an existing report definition report [ReportA] created. For example, report "Admits By Program, Zip Code, Ethnicity" can be used
Steps
  1. Open form "Report Definition"
  2. Select [ReportA]
  3. Note the value in the "Report Version Number" field, for example "1"
  4. Close the form
  5. Open form "Report Definition Export"
  6. Click [Begin Export]
  7. Select [ReportA] and in the "File Explorer" dialog:
  8. In the "Save In" field, Select a folder location to save the export file.
  9. In the "File_Name" field, validate the file name populated includes:
  10. The name of [ReportA], appended by a "V" followed by the "Report Version Number" value noted in step 1 and then the file extension. For example "CSMReportExportAdmitsByProgramZipCodeEthnicityV1.TXT"
  11. Click [Save]
  12. Close the form
  13. Open file "Report Definition Import"
  14. Click [Select Report Import File]
  15. Navigate to the location of the export file saved in step 2, and select the file.
  16. Select the "Overwrite Existing" radio button
  17. Click [Begin Import Scan]
  18. Click [Begin Import]
  19. Click [OK], in the "Import Complete" dialog
  20. Close the form
  21. At the home view, search for [ReportA] and click to open the form
  22. Populate the desired fields on the form
  23. Submit the form and vlidate the report is displayed as expected
  24. Close the report and the form
Topics
• Envelope Definition • Envelope Import • NX • Envelope Export
Update 119.1 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 Import/Export (CWS)
  • Form Designer (CWS)
Scenario 1: (GA ASO) enabled "Progress Notes (Group and Individual)" forms - Validate "Site Specific Section Modeling" & "Import/Export" functionality
Steps
  1. Internal Testing Only
Scenario 2: "Create New Progress Note" form - Validate functionality in (GA-ASO) enabled environments
Steps
  1. Internal Testing Only
Scenario 3: Form Designer - Adding/Moving/Deleting Subsections(Bookmarks)
Specific Setup:
  • Have access to form "Form Designer" in any application
  • Have a form [FormA] that can be used to make form designer changes that already contains one or more sections. For this example the "Progress Notes (Group & Individual)" form is used
Steps
  1. Open "Form Designer"
  2. Select [FormA] in the "Forms" field
  3. Select a [SectionA] from the "Tabs" field
  4. Click [Show Tab]
  5. Locate a blank section of the form to create the bookmark for the new subsection
  6. Right click along the left edge of layout in the black shaded area
  7. Validate red stop sign shaped object displays and a grey section divider is created that is labeled "Sub-Section New"
  8. If desired click on the label and change the name of the subsection
  9. Drag field to the new subsection or move any existing fields already present in the subsection
  10. Validate the change is successful
  11. Holding the "Ctrl" key, click on the red stop sign symbol and move the section either up or down
  12. Validate the change is successful
  13. Click [Save]
  14. Click [Submit]
  15. Open [FormA]
  16. On the upper left side of the form click [SectionA]
  17. Validate under the name of [SectionA], the subsection created is displayed and name is as expected.
  18. Click on the subsection name
  19. Validate the user is taken directly to the new subsection
  20. Validate fields in that subsection are displayed as expected
  21. Close the form
  22. Open "Form Designer"
  23. Select [FormA] in the "Forms" field
  24. Select a [SectionA] from the "Tabs" field
  25. Click [Show Tab]
  26. Locate the new subsection added in step 1
  27. Right-Click on the red stop sign icon and click "Delete"
  28. Validate the subsections is removed
  29. Click [Save]
  30. Click [Submit]
  31. Open [FormA]
  32. On the upper left side of the form click [SectionA]
  33. Validate under the name of [SectionA] the subsection added in step 1 is no longer present,
Scenario 4: Site Specific Section Modeling Form - prompt and value validations
Steps
  1. Open form "Site Specific Section Modeling".
  2. Select any form from the "Site Specific Section" drop down list. For example the "Progress Notes Group and Individual " form.
  3. Click [OK] to edit the form.
  4. Validate the "Site Specific Section Description" field is populated, as expected
  5. Validate the "Form Description" field is populate as expected
  6. Validate prompt 'Generate Bookmark for First Page of Section' is not present
  7. Validate prompt "Include Page Number Within Bookmark" is not present
  8. Validate the "Menu Location" field is populated with "Progress Notes"
  9. Select the "Prompt Definition" section
  10. In the "Prompt Definition" grid, select a prompt that contains a "Product" field. For example the "Select Client" prompt.
  11. Click [Delete Selected Item].
  12. Validate message "Prompt cannot be deleted. To exclude this prompt, set "Exclude from Data Collection Instrument" to "Yes".
  13. Click [OK].
  14. Validate the prompt is not removed from the "Prompt Definition" grid.
  15. Select a prompt that does not contain a "Product" field. For example, a "SS Note Integer" type field.
  16. Click [Delete Selected Item].
  17. Validate message "Are Your Sure?" is displayed.
  18. Click [OK].
  19. Validate the prompt is removed from the "Prompt Definition" grid.
  20. Click [Add New Item].
  21. From the "Site Specific Field" drop down list, select a "Dictionary" type field that is not already in grid.
  22. Validate the prompt is added to the "Prompt Definition" grid.
  23. Validate the field property setting "Default to Specific Value on Addition of a New Table Row" for the dictionary field is set to "No".
  24. Select the prompt just added.
  25. Click [Edit].
  26. Validate the field property setting "Default to Specific Value on Addition of a New Table Row" for the dictionary field is still set to "No".
  27. Select any other prompt in the "Prompt Definition" grid.
  28. Click [Edit].
  29. Make a change to any of the field's property values. For example, the name of the prompt in the "Label" field.
  30. Validate the "Label" column for that prompt row in the "Prompt Definition" grid, reflects the new value.
  31. Click [Submit].
  32. Validate the form files successfully.
Topics
• Site Specific Section Modeling • NX • Form Designer
Update 122 Summary | Details
My To Do's - Results to Review
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Review Results
  • Results To Review - Review Results
Scenario 1: Avatar NX - "Results to Review" To Do validations
Specific Setup:
  • A user is logged in and has the 'My To Do's' widget on their home view (User A).
  • A client has a result (Result A) submitted in the 'Results Entry' form (Client A).
  • In the 'Review Results' form, "Result A" has been submitted with field 'Send Results Notification To' set to "User A", to generate a "To Do".
Steps
  1. Click to open the 'My To Do's' widget.
  2. In the 'Results to Review' field, locate the 'To Do' generated for "Client A".
  3. Click [Review Results].
  4. Click the 'Client Reviewed' checkbox.
  5. Click [Save].
  6. Click [Review Results] again.
  7. Validate 'Client Reviewed' checkbox is checked.
  8. Click the 'Client Reviewed' checkbox to uncheck it.
  9. Click [Save].
  10. Click [Review Results] again.
  11. Validate 'Client Reviewed' checkbox is unchecked.
  12. Click the 'Client Reviewed' checkbox.
  13. Click [Marked Reviewed].
  14. Populate the 'Notes' field if desired.
  15. Click [Save].
  16. Validate the 'To Do' is removed from the 'Results to Review' field.
'All Documents' Widget
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Progress Notes (Group and Individual)
  • Treatment Plan
  • Console Widget Viewer
Scenario 1: Validate the 'Allow Users Access To All Forms on NX 'All Documents' Widget' registry setting
Specific Setup:
  • A client must be enrolled in an existing episode and has 'Progress Notes (Group and Individual)' and 'Treatment Plan' records on file (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).
  • A user who doesn't have access to the 'Progress Notes (Group and Individual)' and 'Treatment Plan' forms (User A).
  • Please note: this scenario is for Avatar NX systems.
Steps
  1. Log in as "User A".
  2. Access the 'Registry Settings' form.
  3. Enter "allow users access to all" in the 'Limit Registry Settings to the Following Search Criteria' field.
  4. Click [View Registry Settings].
  5. Validate the "Allow Users Access To All Forms on NX 'All Documents' Widget" registry setting is present.
  6. Select the registry setting and click [OK].
  7. Validate the 'Registry Setting Details' field contains "When set to 'Y', the user may view all forms on the Documentation View and 'All Documents' widget per the configuration of the 'All Documents' widget displayed, regardless of individual form access permissions configured in 'User Definition' or 'User Role Definition'. When set to 'N', the user's form access permissions will apply to the list of forms on the Documentation View, suppressing the forms to which the user does not have either read or read/write permission."
  8. Validate the 'Registry Setting Value' field contains "N".
  9. Click [Submit], [OK], and [No].
  10. Select "Client A" and navigate to the 'All Documents' view.
  11. Select 'All Forms'.
  12. Validate "Progress Notes (Group and Individual)" and "Treatment Plan" and not present in the 'Form Description' field.
  13. Access the 'Registry Settings' form.
  14. Enter "allow users access to all" in the 'Limit Registry Settings to the Following Search Criteria' field.
  15. Click [View Registry Settings].
  16. Select the "Allow Users Access To All Forms on NX 'All Documents' Widget" registry setting and click [OK].
  17. Enter "Y" in the 'Registry Setting Value' field.
  18. Click [Submit].
  19. Validate a 'Registry Editor Filing' dialog.
  20. Click [OK] and [No].
  21. Navigate to the 'All Documents' view.
  22. Refresh the 'All Documents' widget.
  23. Select 'All Forms'.
  24. Select "Progress Notes (Group and Individual)" in the 'Form Description' field.
  25. Select a progress note and validate the note displays in the 'Console Widget Viewer'.
  26. Validate the 'Open' and 'Open Record' buttons are disabled.
  27. Click [Clear Filters].
  28. Select "Treatment Plan" in the 'Form Description' field.
  29. Select a treatment plan and validate the plan displays in the 'Console Widget Viewer'.
  30. Validate the 'Open' and 'Open Record' buttons are disabled.
My To Do's - Reassign
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Approver Override
  • HomeView - My To Do's widget
  • Reassign To Do Item
  • Review To Do Item
  • TO DO'S
  • Progress Notes (Group and Individual)
Scenario 1: Validate the 'Allow Users to Reassign To Do List Items' registry setting
Specific Setup:
  • The 'Allow Users to Reassign To Do List Items' registry setting must be disabled.
  • There must be two users:
  • A user must have the 'My To Do's' widget configured on a view with various To Do's awaiting approval (User A).
  • "User A" must be logged in.
  • A user must have the 'My To Do's' widget configured on a view (User B).
  • Various To Do's must include:
  • Approve Document (To Do A)
  • Review Results (To Do B)
  • Review To Do Item (To Do C)
Steps
  1. Navigate to the 'My To Do's' widget.
  2. Validate "To Do A", "To Do B", and "To Do C" display.
  3. Validate the 'Ellipsis' displays.
  4. Click this and validate 'Reassign To Do' is disabled.
  5. Select "Create Note to Self" from the menu.
  6. Validate a 'Note to Self' dialog and type any value in the 'Create a new note' field.
  7. Click [OK].
  8. Verify the icon is a check box.
  9. Mouse over the icon and validate the note displays.
  10. Access the 'Registry Settings' form.
  11. Enter "allow users to reassign to do" in the 'Limit Registry Settings to the Following Search Criteria' field.
  12. Click [View Registry Settings].
  13. Enter "Y" in the 'Registry Setting Value' field.
  14. Click [Submit].
  15. Validate a 'Registry Editor Filing' dialog and click [OK], and [No].
  16. Navigate to the 'My To Do's' widget.
  17. For "To Do A", click the 'Ellipsis' and select "Reassign To Do" from the menu.
  18. Validate a 'Continue?' dialog stating: "This to-do cannot be re-assigned with the "Reassign To-Do Item" form, continuing will open "Approver Override" and click [OK].
  19. Validate the 'Approver Override' form displays.
  20. Click [Update Approvers].
  21. In the 'Route Document To' dialog, deselect "User A" as an approver in the approver list.
  22. In the 'Add Approver' field search for "User B" and then click [Add] to add the user to approver list.
  23. Click [Submit].
  24. Close the form.
  25. Validate "To Do A" no longer displays.
  26. For "To Do B", click the 'Ellipsis' and select "Reassign To Do" from the menu.
  27. Validate the 'Reassign To Do Item' form launches.
  28. Enter "User B" in the 'Select User to Reassign To Do Item to' field.
  29. Click [Submit].
  30. Validate "To Do B" no longer displays.
  31. For "To Do C", click the 'Ellipsis' and select "Reassign To Do" from the menu.
  32. Validate the 'Reassign To Do Item' form launches.
  33. Enter "User B" in the 'Select User to Reassign To Do Item to' field.
  34. Click [Submit].
  35. Validate "To Do B" no longer displays.
  36. Log out and log in as "User B".
  37. Navigate to the 'My To Do's' widget.
  38. Validate "To Do A", "To Do B", and "To Do C" display.
  39. Click [Review] for "To Do A".
  40. Validate the to do displays as expected in the 'Document Preview'.
  41. Click [Accept] and [Sign].
  42. Enter the password and click [Verify].
  43. Validate "To Do A" no longer displays.
  44. Click [Review Results] for "To Do B".
  45. Validate the results display as expected in the 'Results to Review'.
  46. Click the 'Client Reviewed' checkbox.
  47. Click [Mark Reviewed].
  48. Enter any value in the 'Notes' field.
  49. Click [Save].
  50. Validate "To Do B" no longer displays.
  51. Click [Review To Do Item] for "To Do C".
  52. Validate the 'Review To Do Item' form opens and displays as expected.
  53. Click [Reviewed] and [Submit].
  54. Validate "To Do C" no longer displays.
  55. Close the To Do's.
Topics
• NX • My To Do's • Registry Settings • All Documents Widget • ToDo's
Update 125 Summary | Details
Form Designer - ScriptLink
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Form Designer (PM)
  • Envelope Export (PM)
Scenario 1: Envelope Import/Export - Validate "ScriptLink" script settings and functionality are retained
Specific Setup:
  • Have a "ScriptLink" script [ScriptA] created.
  • [EnvelopeA] contains [FormA]
  • [FormA] contains a "ScriptLink" script [ScriptA], imported into the form via "Form Designer" and is configured on [FieldA]. For example, the script that will trigger a test error message when the field is populated.
Steps
  1. Open "Form Designer"
  2. Select [FormA]
  3. In the "Tab" field, select the section containing [FieldA]
  4. Navigate to [FieldA] and click in the field to highlight it
  5. On the left side panel under "General", validate the name in the "ScriptLink" field, contains [ScriptA]
  6. Click [Edit]
  7. Validate [ScriptA] is populated in the "Available Scripts" field and the "Script Parameter" field is populated (if applicable), as expected
  8. Click [Cancel] and exit the form
  9. Open form "Envelope Export"
  10. Select [EnvelopeA]
  11. In the "Include Form Design Changes" prompt, select "Yes"
  12. Click "Begin Export"
  13. Select a folder location to save the text file
  14. Populate a name for the file [ExportA]
  15. Click [Save]
  16. Close the form
  17. Open file "Envelope Import"
  18. Click "Select Envelope Import File"
  19. Navigate to the saved location of [ExportA]
  20. Select [ExportA]
  21. Click "Overwrite Existing" radio button
  22. Click the "Yes" radio button in the "Include Form Design Changes" field
  23. Click [Begin Import Scan]
  24. Click "Begin Import"
  25. Validate the "Import Complete" dialog is displayed
  26. Click [OK]
  27. Repeat step 1
  28. Validate the script and script settings are still present, as expected
  29. Open [FormA]
  30. Navigate to [FieldA] and populate the field
  31. Validate the script is triggered and results are as expected
  32. Repeat step 3, this time selecting "No" in field "Include Form Design Changes"
  33. Repeat step 1
  34. Validate the "ScriptLink" settings are still present and set in [FieldA], as expected
  35. Repeat step 5
  36. Validate the script is still triggered and results are as expected
Topics
• Form Designer • NX
Update 127 Summary | Details
Envelope Import
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Modeled_Service_Doc_Form
  • ModeledFormAlias
  • ModeledFormAliasTwo
Scenario 1: Envelope Import - Import scan results validation
Specific Setup:
  • Have an envelope [EnvelopeA] that contains one or more modeled forms which, in total, comprise a large amount of fields, sections, tables, and columns.
Steps
  1. Open form "Envelope Import"
  2. Click [Select Envelope Import File]
  3. In Windows Explorer, navigate to the location of [EnvelopeA]
  4. Select the file
  5. Click [Save]
  6. Click [Create New]
  7. Click [Begin Import Scan]
  8. Validate the import scan is successful
  9. Click [Begin Import]
  10. Validate the envelope imports successfully
  11. Open a form contained in [EnvelopeA]
  12. Validate the form opens successfully
  13. Populate fields on the form
  14. Submit the form
  15. Validate the form files successfully
  16. Repeat step 2 for any other forms contained in [EnvelopeA]
  17. Validate results are as expected
Topics
• Envelope Import
Update 130 Summary | Details
Export Crystal Report File - Avatar PM form
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Export Crystal Report File (CWS)
  • Export Crystal Report File (PM)
Scenario 1: Validate the 'Export Crystal Report File' PM form
Specific Setup:
  • SAP Crystal Report Viewer must be installed.
Steps
  1. Access the 'Export Crystal Report File' PM form.
  2. In the 'Report Type' field, select the "Command Button Report".
  3. Select any desired report in the 'Select Report' field [ReportA] (Note: A system may not have any reports for export).
  4. Click [Export Report].
  5. In the "Save" dialog, click the "Save In" field and navigate to a desired folder location [FolderA],
  6. Click [Save].
  7. Open "File Explorer" and navigate to [FolderA].
  8. In the 'File Name' column, double click on [ReportA] to open the report.
  9. Validate the report opens successfully.
  10. Close the report.
  11. In the 'Report Type' field, select the "Disclosure Management Report".
  12. Repeat steps 2 and 3.
  13. Validate results are as expected.
  14. In the 'Report Type' field, select "Menu Report".
  15. Repeat steps 2 and 3.
  16. Validate results are as expected.
  17. In the 'Report Type' field, select "Document Routing Report".
  18. Repeat steps 2 and 3.
  19. Validate results are as expected.
  20. In the 'Report Type' field, select "Report Definition Report".
  21. Repeat steps 2 and 3.
  22. Validate results are as expected.
  23. In the 'Report Type' field, select "RADplus Report".
  24. Repeat steps 2 and 3.
  25. Validate results are as expected.
  26. Close the form.
Topics
• RADplus Utilities • Report Viewer
Update 134 Summary | Details
Client Header 'Gender Identity' Display
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Client Lookup/Header Configuration Manager
Scenario 1: Client Header - Verification of 'Gender Identity' Display (Avatar Cal-PM)
Specific Setup:
  • Avatar Cal-PM 2022 Update 80 must be installed for support of conditional Client Header 'Gender Identity' display
  • 'Gender Identity' must be included in Client Header display fields (via 'Client Lookup/Header Configuration' Manager form)
  • Client Demographic record(s) where 'Gender Identity' field contains value 'Additional gender category or other, please specify', and 'Gender Identity (Please Describe)' field value is defined
Steps
  1. Open myAvatar/myAvatar NX Client Header display (via active client selection/chart view or Avatar client-based form).
  2. In Client Header display, ensure that 'Gender Identity' field is included (as specified in 'Client Lookup/Header Configuration' Manager form).
  3. Ensure that Client Header 'Gender Identity' field displays value from Client Demographic information for selected/active client.
  4. In case where 'Gender Identity' value in Client Demographic record for selected/active client is filed as 'Additional gender category or other, please specify', ensure that Client header 'Gender Identity' field displays value from 'Gender Identity (Please Describe)' field in Client Demographic information.
  5. Note - this conditional display of 'Gender Identity' value in Client Header is only supported in Avatar Cal-PM instances where Avatar Cal-PM 2022 Update 80 is also installed; Avatar PM instances will display 'Gender Identity' value regardless of value if included in Client Header.
  6. Ensure that updates to 'Gender Identity' and/or 'Gender Identity (Please Describe)' fields in Client Demographic information are accurately reflected in Client Header 'Gender Identity' field display.
Topics
• Client Management • NX • Header Customization
 

RADplus_2022_Monthly_Release_2022.04.00_Details.csv