Skip to main content

RADplus 2023 Monthly Release 2023.04.00 Acceptance Tests

  1. Last updated
  2. Save as PDF
Update 87 Summary | Details
Modeled Forms - 'Data Entry Local Time' pre-display field
Scenario 1: Modeled forms - Validate 'Data Entry Local Time' pre-display field
Specific Setup:
  • Have a system enabled to use UTC date and time. Please note: this must be done by a Netsmart Representative.
  • Have a modeled form configured to have the 'Data Entry Local Time' field in the pre-display (Form A).
  • This form also has a 'Draft/Final' field.
  • A client is enrolled in an existing episode (Client A).
Steps
  1. Select "Client A" and access "Form A".
  2. Populate all required and desired fields.
  3. Select "Draft" in the 'Draft/Final' field.
  4. Submit the form.
  5. Select "Client A" and access "Form A".
  6. Validate a pre-display is displayed.
  7. Validate the 'Data Entry Local Time' field contains the time the record was filed.
  8. Select the record and click [Edit].
  9. Validate all previously filed values are displayed.
  10. Close the form.
Topics
• Modeling
Update 98 Summary | Details
Document Archiving - 'Entity' field
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Document Archiving
Scenario 1: Document Archiving - archive documents for "Individual"
Specific Setup:
  • A client must have documents for archiving (Client A).
Steps
  1. Access the 'Document Archiving' form.
  2. Select "Client" in the 'Entity Type' field.
  3. Select "Individual" in the 'Include' field.
  4. Select "Client A" in the 'Entity' field.
  5. Clear the value from the 'Entity' field.
  6. Validate no error is displayed.
  7. Select "Client A" in the 'Entity' field.
  8. Set "All Episodes" in the 'Episode' field.
  9. Enter the desired date in the 'Archive Documents Older Than' field.
  10. Click [View Form Types Included].
  11. Validate forms for archive are displayed.
  12. Click [Archive].
  13. Validate a message is displayed stating: Are you sure you want to archive these documents?
  14. Click [Yes].
  15. Validate a message is displayed stating: Documents archived.
  16. Click [OK] and close the form.
User Definition - 'External Login ID' field
Scenario 1: User Definition (Field Validation) - Enable/Disable a "Netsmart Identity and Access Management(NIAM)" User
Specific Setup:
  • The 'Enable OpenID Connect Support' registry setting enabled by a Netsmart Representative.
  • The 'System Security Defaults' form must be configured with the appropriate settings in the "OpenID Connect Configuration" section.
  • The logged in user has permissions to add and edit users in the 'User Definition' form.
Steps
  1. Access the 'User Definition' form.
  2. Enter the desired value in the 'User ID' field.
  3. Enter the desired value in the 'User Description' field.
  4. Select "Yes" in the 'Use External Login' field.
  5. Enter a value containing an apostrophe in the 'External Login ID'.
  6. Validate the 'System Generated Password' field is disabled and does not contain a value.
  7. Validate the 'Password Term Duration (Days)' field is disabled and does not contain a value.
  8. Validate the 'Reminder Notice Number of Days' field is disabled and does not contain a value.
  9. Validate the 'Allow User Renewal' field is disabled.
  10. Populate any other required and desired fields.
  11. Click [Submit]. Note: this will now be referred to as "User A".
  12. Access the 'User Definition' form.
  13. Select "User A" in the 'Select User' field.
  14. Validate the 'Use External Login' field is set to "Yes".
  15. Validate the 'External Login ID' field contains the value filed in the previous steps.
  16. Validate the 'System Generated Password' field is disabled and does not contain a value.
  17. Validate the 'Password Term Duration (Days)' field is disabled and does not contain a value.
  18. Validate the 'Reminder Notice Number of Days' field is disabled and does not contain a value.
  19. Validate the 'Allow User Renewal' field is disabled.
  20. Select "No" in the 'Use External Login' field.
  21. Validate the 'System Generated Password' field is now enabled.
  22. Enter the desired value in the 'System Generated Password' field, or click [Generate New Password] to auto generate a new password.
  23. Validate the 'Password Term Duration (Days)' field is now enabled.
  24. Enter the desired value in the 'Password Term Duration (days)' field.
  25. Validate the 'Reminder Notice Number of Days' field is now enabled.
  26. Enter the desired value in the 'Reminder Notice Number of Days' field.
  27. Validate the 'Allow User Renewal' field is now enabled.
  28. Select the desired value in the 'Allow User Renewal' field.
  29. Click [Submit].
  30. Access the 'User Definition' form.
  31. Select "User A" in the 'Select User' field.
  32. Validate the 'Use External Login' field is set to "No".
  33. Validate the values filed in the previous steps are displayed.
  34. Select "Yes" in the 'Use External Login' field.
  35. Validate the 'System Generated Password' field is disabled and does not contain a value.
  36. Validate the 'Password Term Duration (Days)' field is disabled and does not contain a value.
  37. Validate the 'Reminder Notice Number of Days' field is disabled and does not contain a value.
  38. Validate the 'Allow User Renewal' field is disabled.
  39. Click [Submit].
  40. Access the 'User Definition' form.
  41. Select "User A" in the 'Select User' field.
  42. Validate the 'Use External Login' field is set to "Yes".
  43. Validate the values filed in the previous steps are displayed.
  44. Close the form.
Document Management Definition - Special Characters in Form Type
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Document Management Definition
  • Envelope Export (PM)
Scenario 1: Document Management Definition - Validate form names with special characters
Specific Setup:
  • A modeled form must be defined (Form A).
  • A client is enrolled in an existing episode (Client A).
Steps
  1. Access the 'Document Management Definition' form.
  2. Click [Select Form].
  3. Select "Add New" and click [OK].
  4. Enter "<Test>" in the 'Form Name' field.
  5. Select the desired value in the 'Form Type' field.
  6. Select "Client" in the 'Entity Database' form.
  7. Click [File] and close the form.
  8. Access the 'Document Routing Setup' form.
  9. Select the desired value in the 'Application' field.
  10. Click [Select Form].
  11. Select "Form A" in the 'Select a form to enable Document Routing' field.
  12. Click [Select Type].
  13. Select "<Test>" as the form type.
  14. Select "Yes" in the 'Enable Document Routing' field.
  15. Select the desired value in the 'Void Reason Code' field.
  16. Click [File].
  17. Access the 'Envelope Export' form.
  18. Select the envelope for "Form A" and click [Select].
  19. Click [Begin Export].
  20. Navigate to the desired export location and click [Save].
  21. Access the 'Envelope Import' form.
  22. Click [Select Envelope Import File] and [OK].
  23. Navigate to the exported file and select it for import.
  24. Click "Overwrite Existing".
  25. Click [Begin Import Scan].
  26. Validate the 'Import Scan Results' field contains: There are no errors/warnings found within the import file.
  27. Select the desired value in the 'Include Form Designer Changes?' field.
  28. Click [Begin Import].
  29. Validate a message is displayed stating: Import Completed!
  30. Click [OK] and close the form.
  31. Select "Client A" and access "Form A".
  32. Populate all required and desired fields.
  33. Select "Final" in the 'Draft/Final' field.
  34. Click [Submit].
  35. Validate a "Confirm Document" document routing dialog is displayed with the data filed.
  36. Click [Accept].
  37. Enter the password for the logged in user and click [OK].
View Definition - Disabling view customization in Avatar NX
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • View Definition
Scenario 1: View Definition - Validate disabling view customization removes existing customizations
Specific Setup:
  • Please note: this test is for Avatar NX systems.
  • Two users must be configured for testing (User A & User B).
Steps
  1. Log in as "User A".
  2. Access the 'View Definition' form.
  3. Click [Select View].
  4. Select "Add New View" and click [OK].
  5. Enter the desired value in the 'View ID' field.
  6. Enter the desired value in the 'View Description' field.
  7. Select "Home View" in the 'View Type' field.
  8. Select "Yes" in the 'Allow User To Customize View' field.
  9. Select 'Home view' in the field 'View Type' radio button
  10. Click [Launch View Designer].
  11. Drag and drop the desired widgets to the view.
  12. Click [Submit]. Please note: this will now be referred to as "View A".
  13. Access the 'User Definition' form.
  14. Select "User B" in the 'Select User' field.
  15. Select the "Forms and Tables" sections.
  16. Select "View A" in the 'Home View' field.
  17. Click [Submit].
  18. Log out.
  19. Log in as "User B".
  20. Validate "View A" is displayed.
  21. Customize the view as desired.
  22. Log out.
  23. Log in as "User A".
  24. Access the 'View Definition' form.
  25. Click [Select View].
  26. Select "View A" and click [OK].
  27. Select "No" in the 'Allow User To Customize View' field.
  28. Click [Submit] and close the form.
  29. Log in as "User B".
  30. Validate "View A" is displayed with the default layout and customizations have been removed.
  31. Validate the user is not able to customize the view.
Envelope Import
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Document Management Definition
  • Envelope Export (PM)
Scenario 1: Envelope Export/Import - Validations
Specific Setup:
  • Must have an envelope available for export (Envelope A).
Steps
  1. Access the 'Envelope Export' form.
  2. Select "Envelope A".
  3. Select the desired value in the 'Include Form Designer Changes' field.
  4. Click [Begin Export].
  5. Validate the file is exported to the desired location.
  6. Close the form.
  7. Access the 'Envelope Import form.
  8. Click [Select Envelope Import File].
  9. Select the export file for "Envelope A".
  10. Select "Overwrite Existing".
  11. Select the desired value in the 'Load Un-Locked Dictionary Entries' field.
  12. Select the desired value in the 'Load Locked Dictionary Entries' field.
  13. Select the desired value in the 'Include Form Designer Changes' field.
  14. Click [Begin Import Scan].
  15. Validate the 'Import Scan Results' field does not contain errors.
  16. Click [Begin Import].
  17. Validate a message is displayed stating: Import Complete.
  18. Click [OK] and close the form.
  19. Access the 'Envelope Definition' form.
  20. Select "Envelope A".
  21. Validate the envelope details are displayed as expected.
  22. Close the form.
Search Fields
Scenario 1: Client Search - Search using large amount of characters
Specific Setup:
  • A client is enrolled in an existing episode (Client A).
  • A client form must have document routing enabled (Form A).
  • The logged in user must have an associated practitioner (Practitioner A).
Steps
  1. Navigate to the 'My Clients' widget.
  2. Enter a large value in the 'Search Clients' field that should not return results.
  3. Validate the 'Search Results' field contains "No matches found, please refine search".
  4. Validate no errors are displayed.
  5. Enter "Client A" in the 'Search Clients' field.
  6. Validate the 'Search Results' field contains "Client A".
  7. Access "Form A".
  8. In the 'Select Client' dialog, enter a large value that should not return results.
  9. Validate the 'Search Results' field contains "No matches found, please refine search".
  10. Validate no errors are displayed.
  11. In the 'Select Client' dialog, search and select "Client A".
  12. Populate all required and desired fields.
  13. Select "Final" in the 'Draft/Final' field.
  14. Click [Submit].
  15. Validate a "Confirm Document" document routing dialog is displayed with the document data.
  16. Click [Accept and Route].
  17. Enter the password for the logged in user and click [OK].
  18. Enter a large value in the 'Supervisor' search field that should not return results.
  19. Validate the 'Search Results' field contains "No matches found, please refine search".
  20. Validate no errors are displayed.
  21. Enter "Practitioner A" in the 'Supervisor' field.
  22. Click [Add] and [Submit].
  23. Navigate to the 'My To Do's' widget.
  24. Validate a To Do is displayed for the document routed in the previous steps.
  25. Click [Approve Document].
  26. Validate the document data is displayed as expected.
  27. Click [Accept].
  28. Enter the password for the logged in user and click [OK].
  29. Validate a To Do is no longer displayed.
Quick User Definition - Identity Manager users
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Quick User Definition
Scenario 1: Quick User Definition - Field Validations
Specific Setup:
  • Have a system with the following configured:
  • The 'Enable OpenID Connect Support' registry setting enabled by a Netsmart Representative.
  • The 'System Security Defaults' form must be configured with the appropriate settings in the "OpenID Connect Configuration" section.
  • The 'Identity Manager' module is installed and configured.
  • The 'System Security Defaults' form must be configured with the appropriate settings in the "Identity Manager Settings" section.
Steps
  1. Access the 'User Definition' form
  2. Enter the desired value in the 'User ID' field.
  3. Enter the desired value in the 'User Description' field.
  4. Select "Yes" in the 'Associate User with a User Role' field.
  5. Select the desired user role in the 'User Role(s)' field.
  6. Select "Yes" in the 'Associate User To Network ID Through Avatar Identity Manager' field.
  7. Populate any other required and desired fields.
  8. Click [Submit]
  9. Access the 'Quick User Definition' form
  10. Select the user created in the previous steps in the 'Select User' field.
  11. Select "Yes" in the 'Use External Login' field.
  12. Validate a message is displayed stating: A user may not be associated to network logins through both Identity Manager and an external ID.
  13. Click [OK] and close the form.
Topics
• NX • Document Archiving • User Definition • Document Routing • Envelope Import • View Definition • Envelope Export • Client Search • Quick User Definition • Identity Manager
Update 114 Summary | Details
New dictionary value named "Integrated Apps Admin" added in the field "Netsmart Mobile App Access".
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • User Role Definition
Scenario 1: Validate the field 'Integrated Apps Admin' in 'User Definition' and 'User Role Definition' forms.
Specific Setup:
  1. User (User A) should have the access to the 'User Definition' form.
Steps
  1. Login to the Avatar NX with "User A".
  2. Access the 'User Definition' form.
  3. Ser the 'Select User' field to "User A".
  4. Click [Forms and Tables].
  5. Select 'Integrated Apps Admin - Netsmart Mobile App Access' field and close the form.
  6. Access the 'User Role Definition' form.
  7. Click [Select User Role button].
  8. Select "User A" role in the 'Select User Role' field.
  9. Click [Ok].
  10. Select 'Integrated Apps Admin - Netsmart Mobile App Access' field and close the form.
Topics
• User Definition • User Role Definition • Mobile Application Build
Update 120 Summary | Details
Widget Wizard - widgets
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • WidgetWizardEnhancedWidget
Scenario 1: "Widget Wizard" - Validate "Enhanced Widget View" column sorting/filtering/resizing and form launch functionality
Specific Setup:
  • In form "Widget Wizard" have a widget defined [TestWidget] with the 'Enhanced Widget View' field set to "Yes"
  • Have a field selected in prompt "Associate Which Field to Link" (for example, the "Episode" field) to be used as a hyperlink to launch a form [TestForm]
  • Have [TestWidget] placed on the logged in users home view
Steps
  1. Click to "Refresh" [TestWidget]
  2. Validate all column data is displayed, as expected
  3. Validate a "Search:' filter box is displayed at the top of the widget [This is for Avatar NX only]
  4. In the 'Search" filter box, enter a search to filter on any data displayed in any of the columns
  5. For example, a "Data Entry Date" column exists with two client rows with same date displayed
  6. In the "Search" box, enter that date
  7. Validate the two expected client rows, are displayed in the widget results
  8. Clear the "Search" filter box
  9. Validate all data is displayed again in the widget, as expected
  10. Click to "Refresh" [TestWidget]
  11. Validate all data is displayed in the widget, as expected
  12. Validate there is a "Search" box in each column under their respective column name header
  13. Select any column [TestColumnA] in the widget
  14. In the search box below the column name, enter a search criteria to filter the data
  15. Validate the list is filtered and displays as expected based on the search criteria
  16. In any of rows returned via the search, click the hyperlink to launch [TestForm], which was configured in the setup
  17. Validate [TestForm] is launched successfully, as expected
  18. Close or submit the form
  19. Validate the search criteria is still entered in "Search" field for [TestColumnA] and the widget still displays only rows based on the search criteria entered
  20. Clear the search criteria in the "Search" box
  21. Validate all columns display all their data again, as expected
  22. Navigate to any desired column [TestColumnA], in the widget
  23. Click column header name once
  24. Validate the "Up" arrow icon is highlighted and data in the column is sorted in ascending order
  25. Click column header a second time
  26. Validate the "Down" arrow icon is highlighted and data in the column is sorted in descending order
  27. Click column header a third time
  28. Validate the "Up" and "Down" arrows are no longer highlighted and data is no longer sorted in the column
  29. Press and hold down the "Shift" key while doing the following:
  30. Click the column name for [TestColumnA] name once and then the column name for [TestColumnB] twice
  31. Validate widget data results are sorted by [TestColumnA] in ascending order and then by [TestColumnB] in descending order, as expected
  32. Click the line between [TestColumnA]and [TestColumnB] and drag the line to the right, in order to increase the size of [TestColumnA]
  33. Validate the width of [TestColumnA] is increased as expected
  34. Click the line between [TestColumnA] and [TestColumnB] and drag the line to the left, in order to reduce the size of [TestColumnA]
  35. Validate the width of [TestColumnA] is reduced, as expected
Topics
• Widgets
Update 126 Summary | Details
'Form and Table Documentation' form
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Form and Table Documentation (PM)
Scenario 1: "Form and Table Documentation" form (Modeled Forms) - Validate "Generate Form Map' report results
Specific Setup:
  • Have a "Modeled" form that contains event logic defined on the form [FormA].
  • Make a note or all the fields on the form.
  • Make a note of the event logic defined on the form.
  • Have a "Modeled" form that does 'not' contain event logic defined on the form [FormB]
  • Make a note or all the fields on the form
  • Have access to form "Form and Table Documentation"
Steps
  1. Open 'Form and Table Documentation'.
  2. Set 'Type of Documentation' to 'Form'.
  3. Select "Individual" in the "Individual or All Forms" field
  4. Select [FormA] from the 'Form to be Documented' field. (Modeled form with event logic defined)
  5. Navigate to the "Generate Form Map" button and click to launch the w
  6. Validate the user is presented with a file explorer dialog [Note: In Avatar NX the file will automatically be created and saved in the windows "Downloads" directory on the server]
  7. Validate the (.htm) type file name field is populated in the file name field
  8. Validate the file name includes the associated internal "FormID' for [FormA], followed by its form "Name". For example: "NetsmartFormMap_USER9_Modeled Form with Event logic"
  9. Select a folder location to save the file and click [Save]
  10. Navigate to the location of the (.htm) file
  11. Click to open the file
  12. Validate the title of the report reflects the name of [FormA] and its associated internal "FormID"
  13. Validate each "Section" name is displayed on the form as expected with each field contained in that section listed beneath it
  14. Validate the field names contain both the name and its associated field number in brackets, for example "Date of Entry (777.77)"
  15. Locate a field on the form that contains event logic defined
  16. Validate the event logic noted in the setup is displayed as expected. For example:
  17. Date of Entry(777.77)
  18. Type of Event: Result of Input With Value Checking
  19. Compare with For Event: Specific Value
  20. Specific Value: 12/06/2022
  21. Relationship To Comparison Value to Trigger Event: Less Than
  22. Set Specific Objects to Required on Event: Yes
  23. Required: Integer (FormA_Integerfield)
  24. Close the page
  25. Select [FormB] from the 'Form to be Documented' field. (Modeled form with 'no' event logic defined)
  26. Repeat steps 1a thru 1e
  27. Validate results are as expected
  28. Close the form
Scenario 2: "Form and Table Documentation" form (Product Forms) - Validate "Generate Form Map' report results
Specific Setup:
  • Have a "Product" form that is available to be configured for site specific section modeling in form "Site Specific Section" modeling and contains event logic defined on the form [FormA]. For example form "Update Client Data"
  • Make a note or all the fields on the form.
  • Make a note of the event logic defined on the form
  • Have a "Product" form that is available to be configured for site specific section modeling in form "Site Specific Section" modeling and does 'not' have event logic defined on the form [FormB]. For example form "Client Charge Input"
  • Make a note or all the fields on the form
  • Have a "Product" form that is 'not' available to be configured for site specific section modeling in form "Site Specific Section" modeling [FormC]. For example, the "Billed Charges" form'
  • Have access to form "Form and Table Documentation"
Steps
  1. Open 'Form and Table Documentation'.
  2. Set 'Type of Documentation' to 'Form'.
  3. Select "Individual" in the "Individual or All Forms" field
  4. Select [FormA] from the 'Form to be Documented' field. (A 'Product' form that can be configured with site-specific section modeling and contains event logic defined)
  5. Navigate to the "Generate Form Map" button and click to launch the report
  6. Validate the user is presented with a file explorer dialog. [Note: In Avatar NX, the file will automatically be created and saved in the windows "Downloads" directory on the server]
  7. Validate the (.htm) type file name field is populated in the file name field
  8. Validate the file name includes the associated internal "FormID" for [FormA], followed by its form "Name". For example: "NetsmartFormMap_PATIENT14_Update Client Data.htm"
  9. Select a folder location to save the file and click [Save]
  10. Navigate to the location of the (.htm) file
  11. Click to open the file
  12. Validate the title on the page reflects the name of [FormA] and its associated internal "FormID". For example, "Update Client Data (PATIENT14)"
  13. Validate each "Section" name is displayed on the form as expected, with each field contained in that section listed beneath it.
  14. Validate the field names contain both the name and its associated field number in brackets, for example "Date of Citizenship (631.1)"
  15. Locate a field on the form that contains event logic defined
  16. Validate the event logic noted in the setup is displayed as expected. For example:
  17. Date of Citizenship (631.1)
  18. Type of Event: Valid Entry
  19. Prompts To Be Disabled: Gender Identity (730)
  20. Close the page
  21. Select [FormB] from the 'Form to be Documented' field. (A 'Product' form that can be configured with site-specific section modeling and does 'not' contain event logic)
  22. Repeat steps 1a thru 1c
  23. Validate results are as expected
  24. Close the form
  25. Open 'Form and Table Documentation'.
  26. Set 'Type of Documentation' to 'Form'.
  27. Select "Individual" in the "Individual or All Forms" field
  28. Select [FormC] from the 'Form to be Documented' field. (The 'Product' form that can 'not' be configured with site-specific section modeling)
  29. Validate "Generate Form Map" button is not present on the form as expected
Topics
• Modeling • Forms
Update 131 Summary | Details
Issue resolved where users were unable to log into Med Note due to blank Organization email address in User Definition
Scenario 1: SOAP UI - Med Note errors for users who had the User Management web service submitted with a blank email address
Specific Setup:
  1. User must have access to the SOAP UI application.
  2. A Client (Client A) must be exist with active episodes.
Steps
  1. Access the SOAP UI application.
  2. Enter the request message by leaving the "<tem:OrganizationEmailAddress></tem:OrganizationEmailAddress>" field as "Blank".
  3. Click "Run" icon.
  4. Validate the successful message "User LABSTAFF successfully updated." in the response tab.
  5. Login to the Avatar application.
  6. Select "Client A" and access the 'Medical Note' tab.
  7. Validate the 'Medical Note' opens without and error messages.
  8. Validate the 'Medical Note' tab doesn't contains the error message {"error":"An error occurred during authentication. Please contact your system administrator."}".
  9. Update the field "<tem:OrganizationEmailAddress></tem:OrganizationEmailAddress>" with "Spaces" , "Alpha Numeric" , "Comma" , "Invalid Email Address" and validate the 'Medical Note' tab opens by repeating the above steps.
Topics
• User Definition
Update 138 Summary | Details
Progress Notes - Widget
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • HomeView - Console Widget Viewer
Scenario 1: Progress Notes (Product) Widget - Validate data display and formatting
Specific Setup:
  • Have a client [TestClient] with a row of data in submitted in each of the product progress note forms: "Ambulatory Progress Notes", "Ambulatory Progress Notes(Diagnosis Entry)", "Inpatient Progress Notes", "Inpatient Progress Notes(Diagnosis Entry)", "Progress Notes (Group and Individual)" and a copy of the "Progress Notes (Group and Individual)"
  • [TestUser] also has product "Progress Notes Widget" on their home view an in their "Chart" view
Steps
  1. At Home View, select [TestClient]
  2. Navigate to the "Progress Notes" widget
  3. Scroll down to row submitted for the "Progress Notes (Group and Individual)" form
  4. Validate all field data is populated, as expected
  5. Validate the following data formatting:
  6. Validate the "Form" name heading is left justified with no indentation
  7. Validate all the "Field" names listed under the heading, are displayed with the same indentation
  8. Scroll down to row submitted for the copy of the "Progress Notes (Group and Individual)" form
  9. Validate all field data is populated, as expected
  10. Validate the following data formatting:
  11. Validate the "Form" name heading is left justified with no indentation
  12. Validate all the "Field" names listed under the heading, are displayed with the same
  13. Scroll down to row submitted for the "Ambulatory Progress Notes" form
  14. Validate all field data is populated, as expected
  15. Validate the following data formatting:
  16. Validate the "Form" name heading is left justified with no indentation
  17. Validate all the "Field" names listed under the heading, contain the same indentation
  18. Scroll down to row submitted for the "Ambulatory Progress Notes (Diagnosis Entry)" form
  19. Validate all field data is populated, as expected
  20. Validate the following data formatting:
  21. Validate the "Form" name heading is left justified with no indentation
  22. Validate all the "Field" names listed under the heading, contain the same indentation
  23. Scroll down to row submitted for the "Inpatient Progress Notes" form
  24. Validate all field data is populated, as expected
  25. Validate the following data formatting:
  26. Validate the "Form" name heading is left justified with no indentation
  27. Validate all the "Field" names listed under the heading, contain the same indentation
  28. Scroll down to row submitted for the "Inpatient Progress Notes (Diagnosis Entry)" form
  29. Validate all field data is populated, as expected
  30. Validate the following data formatting:
  31. Validate the "Form" name heading is left justified with no indentation
  32. Validate all the "Field" names listed under the heading, are displayed with the same indentation
  33. At Home View, select [TestClient] and click to open their "Chart" view
  34. Navigate to the "Progress Notes" widget in the view
  35. Repeat step 1a for each of the forms in that step
  36. Validate results are as expected
Topics
• Progress Notes
Update 139 Summary | Details
Document Routing - Document Image
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • ModeledForm (w/Doc routing Crystal Report Template)
Scenario 1: "Document Routing" - Document display validations
Specific Setup:
  • Have two users for testing [TestUserA] and [TestUserB].
  • Both users have the "My To Do's" widget on their home view.
  • Have two forms enabled for document routing:
  • [TestFormA] is enabled in form "Document Routing Setup" with "User Crystal Report Template" set to "Y" and report selected in the "Crystal Report" field.
  • [TestFormB] is not enabled to use a crystal report template.
  • Log in as [TestUserA].
Steps
  1. Access [TestFormA]:
  2. Populate all desired fields on the form.
  3. Select "Final" in the 'Draft/Final' field.
  4. Click "OK".
  5. Click [Submit].
  6. In the "Confirm Document" screen:
  7. Verify document is displayed in the expected the "Crystal Report" template format.
  8. Validate all data is populated as expected.
  9. Click [Accept and Route].
  10. Enter the user's password in the 'Password' field.
  11. Click [OK].
  12. In the "Route Document To" screen, select [TestUserB] as an approver.
  13. Click [Submit].
  14. Validate the form submits successfully.
  15. Log out as [TestUserA].
  16. Log in as [TestUserB].
  17. Navigate to the 'My To Do's' widget:
  18. Locate the document in the "My To Do's" widget for [TestFormA]:
  19. Click [Approve Document].
  20. In the "Confirm Document" screen:
  21. Verify document is displayed in the expected "Crystal Report" template format.
  22. Validate all data is populated as expected.
  23. Click [Accept].
  24. Validate the "To Do" accepted successfully and is removed from the 'My To Do's' widget.
  25. Access [TestFormB]:
  26. Populate all desired fields on the form.
  27. Select "Final" in the 'Draft/Final' field.
  28. Click "OK".
  29. Click [Submit].
  30. In the "Confirm Document" screen:
  31. Verify document is displayed in the expected as a standard "TIF" image, not in a "Crystal Report" 'PDF' template format.
  32. Validate all data is populated as expected.
  33. Click [Accept and Route].
  34. Enter the user's password in the 'Password' field.
  35. Click [OK].
  36. In the "Route Document To" screen, select [TestUserA] as an approver.
  37. Click [Submit].
  38. Validate the form submits successfully.
  39. Log out as [TestUserB].
  40. Log in as [TestUserA].
  41. Navigate to the 'My To Do's' widget.
  42. Locate the document in the "My To Do's" widget for [TestFormB]:
  43. Click [Approve Document].
  44. In the "Confirm Document" screen:
  45. Verify document is displayed in the expected as a standard "TIF" image, not in a "Crystal Report" 'PDF' template format.
  46. Validate all data is populated as expected.
  47. Click [Accept].
  48. Validate the "To Do" accepted successfully and is removed from the 'My To Do's' widget.
Approver Override - document image
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Approver Override
Scenario 1: "Approver Override" form - Validate Document display and functionality
Specific Setup:
  • Have two users who are staff members [StaffA] and [StaffB].
  • Have two forms enabled for document routing [FormA] and [FormB] and both use form type, [TypeA].
  • [ClientA] has two document rows [DocRow1] and [DocRow2] submitted in [FormA] that has been routed to [StaffB] for approval.
  • [ClientB] has two document rows [DocRow1] and [DocRow2] submitted in [FormB] that has been routed to [StaffB] for approval.
  • [StaffA] has the "My To Do's" widget on their home view.
  • Log in as [StaffA].
Steps
  1. Open form "Approver Override":
  2. In the "Form Type" field choose In the "Entity" field, select [TypeA].
  3. In the "Entity" field select [ClientA]:
  4. Populate the "From" and "To", date fields.
  5. Click the "List of Documents" field:
  6. Validate both [DocRow1] and [DocRow2] are displayed as expected.
  7. Select [DocRow1]:
  8. Click [Display Document] to view the document:
  9. Validate the "Confirm Document" screen displays document data for [ClientA], [DocRow1], as expected.
  10. Click [Close].
  11. Click the "List of Documents" field:
  12. Select [DocRow2].
  13. Click [Display Document] to view the document:
  14. Validate the "Confirm Document" screen displays document data for [ClientA], [DocRow2], as expected.
  15. Click [Close].
  16. In the "Entity" field select [ClientB]:
  17. Populate the "From" and "To", date fields.
  18. Click the "List of Documents" field.
  19. Validate both [DocRow1] and [DocRow2] are displayed as expected.
  20. Select [DocRow1]:
  21. Click [Display Document] to view the document:
  22. Validate the "Confirm Document" screen displays document data for [ClientB], [DocRow1], as expected.
  23. Click [Close]
  24. Click the "List of Documents" field
  25. Select [DocRow2]
  26. Click [Display Document] to view the document
  27. Validate the "Confirm Document" screen displays document data for [ClientB], [DocRow2], as expected
  28. Click [Update Approvers]
  29. In the "Route Document To" screen, uncheck the current selected approver
  30. In the "Add Approver" field, select [StaffA]
  31. Click [Submit]
  32. Navigate to the "My To Do's" widget, and locate the row with the To Do sent in step 1d
  33. Click [Approve Document]
  34. Validate the "Confirm Document" screen displays document data for [ClientB], [DocRow2], as expected
  35. Click [Accept]
  36. Populate the "Verify Password" prompt
  37. Click [OK]
  38. Validate the "To Do" is removed from the "My To Do's"
My To Do's widget - Approval comments
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Add Non-User Signature (PM)
  • Progress Notes (Group and Individual) 6
  • Clinical Document Viewer
  • ModeledForm
Scenario 1: 'My To Dos' Widget - Validate display of "Approval Comments" and "DocR.Comments" table data
Specific Setup:
  • Have a testing system that is accessible via "myAvatar" and/or "Avatar NX".
  • Enable document routing for any form [TestForm] in form "Document Routing Setup":
  • Set prompt 'Allow Comments During Approval' to 'Yes' for the form.
  • Have three users, [StaffA], [StaffB] and [StaffC].
  • Each user has the "My To Do's" widget on their home view.
  • Have report that will display data in the "SYSTEM.DocR.comments" table.
Steps
  1. Log in as [StaffA] via "AvatarNX" (if applicable).
  2. Launch [TestForm] for any client:
  3. Populate all desired fields on the form.
  4. Submit the form as "Final".
  5. At the "Route To" dialog.
  6. Add [StaffA] as an approver.
  7. Submit the document [DocA] to be routed.
  8. Validate submission is successful.
  9. Repeat step 2, for [StaffB] and routing [DocB].
  10. Repeat step 2, for [StaffC] and routing [DocC].
  11. Navigate to the "My To Do's" widget:
  12. In the "Documents to Sign" column, validate the To Do for [DocA] is present in the widget as expected
  13. Click to review the To Do.
  14. Validate the document contents are as expected.
  15. Click to "Accept" the documents.
  16. In the "Approval Comments" field, enter desired comments [DocAComments] for [DocA]
  17. Click [Sign]:
  18. Validate the To Do is approved successfully.
  19. Log out a [StaffA].
  20. Log in as [StaffB] via "myAvatar".
  21. Navigate to the "My To Do's" widget:
  22. Click the "All" or "New" tab in the widget:
  23. Validate a row is present for the [DocB] as expected.
  24. Click "Approve Document" link in the "Action" column of the row
  25. In the document preview screen, validate the document contents are as expected.
  26. Click to "Accept".
  27. In the "Approval Comments" dialog, enter desired comments [DocBComments] for [DocA].
  28. Click [OK].
  29. Validate the To Do is approved successfully.
  30. Log out as [StaffB].
  31. Log in as [StaffC] via "myAvatar".
  32. Navigate to the "My To Do's" widget:
  33. Click the "Sign" tab in the widget.
  34. In the "Search Documents" section, validate a row is present for [DocC] as expected:
  35. Click to select that row.
  36. In the "Document Preview", validate the document contents are as expected.
  37. Click "Accept".
  38. In the "Approval Comments" dialog, enter desired comments [DocCComments] for [DocC].
  39. Click [OK].
  40. In the "Accepted Documents" section.
  41. Click [Sign All].
  42. Validate the To Do is approved successfully.
  43. Generate the report for the "SYSTEM.DocR.comments" table.
  44. Locate the row for [StaffA]:
  45. Validate the "Approved Comment" column is populated with the comments [DocAComments], entered in step 7.
  46. Locate the row for [StaffB]:
  47. Validate the "Approved Comment" column is populated with the comments [DocBComments], entered in step 8.
  48. Locate the row for [StaffC]:
  49. Validate the "Approved Comment" column is populated with the comments [DocCComments], entered in step 9.
Topics
• Document Routing • NX • Document Management • My To Do's
Update 141 Summary | Details
Product Updates
Scenario 1: Validate accessabilty to the "Product Updates" form based on system configuration
Steps
  1. Internal Testing Only
Topics
• Update Install
Update 142 Summary | Details
User Role Definition - 'My Forms'
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Change User Role ID
  • User Role Definition
Scenario 1: User Role Definition - 'My Forms' section validations
Specific Setup:
  • Two users must exist for testing (User A & User B).
Steps
  1. Login as "User A".
  2. Access the 'User Role Definition' form.
  3. Create a new user role.
  4. Populate all required and desired fields.
  5. Select the "My Forms" section.
  6. Add the desired forms.
  7. Click [Submit] and close the form.
  8. Access the 'Change User Role ID' form.
  9. Select the user role created in the previous steps from the 'User Role' field.
  10. Validate the 'Current User Role ID' field contains the user role ID defined in the previous steps.
  11. Enter any new value in the 'New User Role ID' field.
  12. Click [Submit] and close the form.
  13. Access the 'User Role Definition' form.
  14. Click [Select User Role].
  15. Select the user role ID updated in the previous steps.
  16. Select the "My Forms" section.
  17. Validate all previously selected forms are displayed.
  18. Close the form.
  19. Access the 'User Definition' form.
  20. Select "User B" in the 'Select User' field.
  21. Select "Yes" in the 'Associate User with User Role' field.
  22. Select "No" in the 'Allow User Role Customization' field.
  23. Select the user role created in the previous steps in the 'User Role(s)' field.
  24. Click [Submit] and close the form.
  25. Logout.
  26. Login as "User B".
  27. For myAvatar users - Validate the 'My Forms' list in the 'Forms & Data' widget contains the forms selected in the "My Forms" section of 'User Role Definition'.
  28. For myAvatar NX users - Validate the 'My Favorites' list contains the forms selected in the "My Forms" Section of 'User Role Definition'.
Topics
• Change User Role Id • User Role Definition • User Definition
 

RADplus_2023_Monthly_Release_2023.04.00_Details.csv