Skip to main content

RADplus 2022 Monthly Release 2022.03.02 Acceptance Tests

  1. Last updated
  2. Save as PDF
Update 87 Summary | Details
API Gateway Dashboard
Scenario 1: MyAvatar (API Gateway) Dashboard - functionality
Steps
  • Internal Testing Only
Topics
• Cache • NX
Update 111 Summary | Details
Dictionary Values
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Dictionary Import (PM)
Scenario 1: Validate updating dictionary fields via the right-click "Update Dictionary" grid functionality
Specific Setup:
  • Have a form [FormA] that includes an "Unlocked" dictionary field [FieldA], that includes existing dictionary values.
Steps
  1. Open [FormA]
  2. Right-click on [FieldA]
  3. Click [Yes] to update the dictionary
  4. In the grid, click on any dictionary value in the "Dictionary Value" column
  5. Change the existing value to a value that includes a less than sign (<)
  6. Validate an error is displayed "Can Not Contain '<'
  7. Click [OK]
  8. Change the existing value to a value that does not include a less than sign (<)
  9. Validate the value is accepted
  10. Change the existing value in the "Active" column to a new value
  11. Click on any other row in the grid
  12. Click [Delete Row]
  13. Click [Yes] at the "Confirm Delete" dialog
  14. Validate an error is displayed stating existing dictionary codes cannot be deleted
  15. Click [OK]
  16. Click [New Row]
  17. Validate a new row is inserted at the bottom of the grid
  18. Populate the "Dictionary Code" field
  19. Populate the "Dictionary Value" field
  20. Enter a value that includes a less than sign (<)
  21. Validate an error is displayed "Can Not Contain '<'
  22. Click [OK]
  23. Enter a value that does not include a less than sign (<)
  24. Validate the value is accepted
  25. Select a value in the "Active" column to a new value
  26. Click [Save]
  27. Click [OK] to exit the grid
  28. Click [OK]
  29. Right-click on [FieldA]
  30. Validate all changes made in step 1 are displayed, as expected
  31. Close the grid
  32. On [FormA], click [FieldA]
  33. Validate the selection list contains the expected values
Scenario 2: Dictionary Update (Form) - Field Validations
Steps
  1. Open form "Dictionary Update" in any application. For this test "PM" is used
  2. Click the "File" file filed and select a file, for example "Payor"
  3. In the "Data Element" field, search for a dictionary field to update. For this example "Financial Class" is used
  4. In the "Dictionary Code" field, select any existing code
  5. In the "Dictionary Value" field, insert a less than sign "<" anywhere in the value
  6. Validate an error is displayed "Can Not Contain '<'"
  7. Click [OK]
  8. In the "Dictionary Code" field, enter a new code, for example "999"
  9. In the "Dictionary Value" field, enter a value that contains a less than sign "<"
  10. Validate an error is displayed "Can Not Contain '<' "
  11. Click [OK]
  12. In the "Dictionary Value" field, enter a value that does not contain a less than sign "<"
  13. Validate the value is accepted
  14. If applicable, select an extended dictionary from the "Extended Dictionary Data Element" field
  15. Select a dictionary value from the "Extended Dictionary Value (Single Dictionary)" field
  16. Click [Apply Changes]
  17. At the "Filed" dialog, click [OK]
Scenario 3: Dictionary Import - Data import validations
Specific Setup:
  • Have a form [FormA] that contains a "Dictionary" type field [FieldA]
  • Have access to form "Dictionary Update"
  • Have a "Dictionary Import" file created [FileA] created for [FieldA], that contains dictionary codes configured with the following type characters in their dictionary values:
  • [Code1] includes a dictionary value containing a less than sign (<)
  • [Code2] includes a dictionary value containing a caret symbol (^)
  • [Code3] includes a dictionary value containing an equal sign (=)
  • [Code4] includes a dictionary value containing a tilde symbol (~)
  • Have a "Dictionary Import" file created [FileB] created for [FieldA], that does not contain, a less than sign, caret symbol, equal sign or tilde symbol in any of the dictionary values to be imported
Steps
  1. Open form "Dictionary Import"
  2. Click [Select File]
  3. Navigate the location of [FileA] and select it
  4. Click "Scan Import File"
  5. Validate the scan results indicate
  6. Error in row 1: Caret(s) found in dictionary value.
  7. Error in row 2: Equal sign(s) found in dictionary value.
  8. Error in row 3: Tilde(s) found in dictionary value.
  9. Error in row 4: Less than sign(s) found in dictionary value. Import file cannot be processed due to critical errors.
  10. Navigate the location of [FileB] and select it
  11. Click "Scan Import File"
  12. Validate the scan results indicate "No errors or warnings found in file."
  13. Click "Begin Import"
  14. At the "Dictionary Import Complete" dialog, click [OK]
  15. Open [FormA]
  16. Navigate to [FieldA] and click on the field
  17. Validate the fields imported in [FileB] in step 1, are present in the selection list as expected
  18. Close the form
Topics
• Dictionary • NX
Update 117 Summary | Details
User File Import
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • User File Import
  • User Definition
Scenario 1: Verify 'User File Import'
Specific Setup:
  • Have a system with Netsmart's "(NIAM) Netsmart’s Identity and Access Management" functionality” configured.
  • An "(ODIC) Identity Provider" solution is configured with Netsmart's (NIAM) functionality to provide external login authentication.
  • [UserA] has been assigned an external login ID [NaimID] and password that can be used to login using the '(ODIC) Identity Provider' solution
  • The system also has the "Identity Manager" module installed
  • In form "User Definition", [UserA] has prompt "Associate User to Network ID Through Avatar Identity Manager" set to "Yes".
  • Have registry setting "Enable Avatar Identity Manager" set to "No"
  • Have a "User File Import" file created [FileA], that includes a row for [UserA], set with:
  • Field "Associate User to Network ID Through Avatar Identity Manager" set to "No"
  • Field "User Description" set to a desired description
  • Field "Use External Login" set to "Yes"
  • Field "External Login ID" set to the user external ID [NaimID]
  • Have a second "User File Import" file created [FileB], that includes a row for [UserA], set with:
  • Field "Associate User to Network ID Through Avatar Identity Manager" set to "Yes"
  • Field "User Description" set to blank
  • Field "Use External Login" set to "No"
  • Field "External Login ID" set to blank
Steps
  1. Open the 'User File Import' form.
  2. Click [Select User Import File]
  3. Navigate to the location of [FileA] and select the file
  4. Click [Open].
  5. Validate the scan results display messages, "Warning: Row 1 contains an existing User ID which will be edited on import (UserA)" and "Warnings but no errors detected in import file. Import may proceed"
  6. Click [Process User Import File]
  7. Validate there are no errors
  8. Click [OK].
  9. Validate the import completes successfully
  10. Close the form
  11. Open form "User Definition"
  12. Select [UserA] in the "Select User" field
  13. Validate field "Associate User to Network ID Through Avatar Identity Manager" set to "No"
  14. Validate field "User Description" is populated
  15. Validate field "Use External Login" set to "Yes"
  16. Validate field "External Login ID" set to the user external ID [NaimID]
  17. Open the 'User File Import' form.
  18. Click [Select User Import File]
  19. Navigate to the location of [FileB] and select the file
  20. Click [Open].
  21. Validate the scan results display messages, "Warning: Row 1 contains an existing User ID which will be edited on import (UserA)" and "Warnings but no errors detected in import file. Import may proceed"
  22. Click [Process User Import File]
  23. Validate there are no errors
  24. Click [OK].
  25. Validate the import completes successfully
  26. Close the form
  27. Open form "User Definition"
  28. Select [UserA] in the "Select User" field
  29. Validate field "Associate User to Network ID Through Avatar Identity Manager" set to "Yes"
  30. Validate field "User Description" is blank
  31. Validate field "Use External Login" set to "No"
  32. Validate field "External Login ID" set to blank
Topics
• File Import • NX
Update 120 Summary | Details
RADplus is enhanced to support future functionality.
Internal Test Only
Topics
• Registry Settings
Update 123 Summary | Details
Update - background processing
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Move Selected Data (CWS)
Scenario 1: Move Selected Data - Table data validations
Specific Setup:
  • Have a progress note form [FormA], which is enabled for document routing. For example, the "Inpatient Progress Note" form
  • [ClientA] is admitted in two episodes [Episode1] and [Episode2]
  • [ClientA] has a row filed [RowA] in [FormA] in [Episode1], as "Final", with the document routing document routed and approved.
  • [ClientA] has a row filed [RowB] in [FormA] in [Episode2] as "Draft"
  • [ClentB] is admitted in [Episode1]
  • Have a report or query created to display data in the "DocR.document" table [ReportA]
  • Have a report or query created to display data in the "DocR.document_history" table [ReportB]
  • Have [FormA] added to the logged in users "Chart View"
Steps
  1. Run [ReportA], to display data in the "DocR.document" table
  2. Validate [RowA] is present for [ClientA] in [Episode1]
  3. Make a note of the "DocID". For example "789"
  4. Make a note of the value in "JOIN_TO_UNIQUE_ID" field. For example: "NOTxxxxx.001"
  5. Open form "Move Selected Data"
  6. Select [ClientA] in the "Entity Database" field
  7. Select [FormA] in the "Form" field
  8. Select [ClientA] in the "Old Entity" field
  9. Select [Episode1] in the "Old Episode" field
  10. Click [Select Row to be Moved]
  11. Select [RowA]
  12. Select [ClientA] in the "New Entity" field
  13. Select [Episode2] in the "New Episode" field
  14. Populate the "Reason for Moving Data" field
  15. Click [Submit]
  16. At the "Confirm Document" screen, click [Sign]
  17. Populate the "Verify Password" dialog and click [Verify]
  18. Validate the form files successfully
  19. Run [ReportA], to display data in the "DocR.document" table
  20. Validate [RowA] is present for [ClientA] in [Episode1], with the "DocID" noted in step 1
  21. Make a note of the value in "JOIN_TO_UNIQUE_ID" field. For example: "NOTxxxxx.001"
  22. Validate the same value exists in the "JOIN_TO_UNIQUE_ID" field but has incremented by 1 after the decimal point. For example "NOTxxxxx.002".
  23. Run [ReportB], to display data in the "DocR.document_history" table
  24. Validate [RowA] is present for [ClientA] in [Episode1]
  25. Locate the "doc_id" field (Note: the value in "doc_id" contains several values separated by pipe (|) symbols)
  26. Validate the field value contains the same value "JOIN_TO_UNIQUE_ID" value noted in step 3. For this example "NOTxxxxx.002".
  27. Select [ClientA]
  28. Right-click on the clients name to open the clients "Chart"
  29. On the left side panel, choose [FormA]
  30. Click the "Episode 1" tab in the main window
  31. Validate [RowA] is not present
  32. Click the "Episode 2" tab in the main window
  33. Validate [RowA] is displayed, as expected
  34. Open form "Move Selected Data"
  35. Select [ClientA] in the "Entity Database" field
  36. Select [FormA] in the "Form" field
  37. Select [ClientA] in the "Old Entity" field
  38. Select [Episode2] in the "Old Episode" field
  39. Click [Select Row to be Moved]
  40. Select [RowB]
  41. Select [ClientB] in the "New Entity" field
  42. Select [Episode1] in the "New Episode" field
  43. Populate the "Reason for Moving Data" field
  44. Validate the form files successfully
  45. Select [ClientA]
  46. Right-click on the clients name to open the clients "Chart"
  47. On the left side panel, choose [FormA]
  48. Click the "Episode 2" tab in the main window
  49. Validate [RowB] is not present
  50. Select [ClientB]
  51. Right-click on the clients name to open the clients "Chart"
  52. On the left side panel, choose [FormA]
  53. Click the "Episode 1" tab in the main window
  54. Validate [RowB] is present, as expected
Topics
• Move Selected Data • NX
Update 126 Summary | Details
Client Middle Name is expanded to 25 characters including spaces.
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Update Client Data
  • Chart View (Client Header)
Scenario 1: Update Client Data - Validate client name allows spaces and client middle name displays up to 25 characters.
Specific Setup:
  • Avatar RADplus 2022 Update 126 is required for full functionality.
  • Registry Setting 'Avatar PM->Client Information->Client Demographics->->->Allow Spaces in Client Name' is set to 'Y' to allow spaces. Note: Once enabled, the user will only be able to edit an existing client 'Client Name' field within 'Update Client Data' form.
  • Registry Setting 'Client Demographics - Additional Fields' must be set to include '3: 'Detailed Client Name' to enable this functionality. This setting will add the 'Detail Client Name' fields to the 'Demographics' section of Admission forms.
Steps
  1. Open 'Update Client Data' form for an existing client.
  2. Set the 'Client Last Name' field to a last name which includes spaces in the name i.e.: 'FRANKLIN MILLER MOTT'
  3. Set the 'Client First Name' field to a first name which includes spaces in the name i.e: 'BENJAMIN WALLY'
  4. Set the 'Client Middle Name' field to a middle name which includes spaces and is maximum of 25 characters i.e: 'BILL ED MIDDLE NAME LONG'
  5. Click [Submit].
  6. Right click on the client name in the 'Recent Clients' list.
  7. Select 'Display Chart'.
  8. Verify the name displays in the client banner, including all spaces and a maximum of 25 characters for the middle name.
  9. Close the client chart.
Client name fields are enhanced to allow spaces in the names.
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Scheduling Calendar - Appointment Grid
  • Group Registration
  • Update Client Data
  • Chart View (Client Header)
Scenario 1: Appointment Scheduling: Scheduling Calendar - support expanded client name field up to 100 characters and the name contains spaces.
Specific Setup:
  • A client (Client A) is admitted with a name where the first name, middle name, and last name combined is up to 100 characters.
  • Access to Crystal Reports or other SQL reporting tool.
  • Avatar PM 2022 Update 118 is required for full functionality.
  • RADplus 2022 Update 126 is required for full functionality.
Steps
  1. Open the 'Scheduling Calendar'.
  2. Click on any time slot.
  3. Right mouse and select 'Add Appointment'.
  4. Populate all required fields.
  5. Select 'Client A' in the 'Client' field.
  6. Validate that the client name displays all characters, up to 100.
  7. Submit the appointment.
  8. Validate that the client name displays the entire name in the time slot. Note: if the client name is not displayed, check the 'Show Name' box on the bottom left of the screen.
  9. Click 'Show MR#' box on the bottom left of the screen.
  10. Validate that the Client name as well as the MR# are displayed in the time slot.
  11. Right click on the appointment and select 'Check In'.
  12. Verify the entire client name displays in the 'Client' field. The user may need to scroll to the right to see the entire name.
  13. Click [View Client Data].
  14. Verify the 'Client Name' displays the entire client name.
  15. Click [Submit].
  16. Select one or more items from the 'Services to Check In' combo box.
  17. Click [Submit].
  18. Right click on the appointment and select 'Check Out'.
  19. Validate that the client name displays the entire name in the time slot. Note: if the client name is not displayed, check the 'Show Name' box on the bottom left of the screen.
  20. Complete additional fields as needed.
  21. Click [Submit].
  22. Open Crystal reports or other SQL Reporting tool.
  23. Create a report against SYSTEM.check_in_clients.
  24. Include, at a minimum, the following fields
  25. PATID
  26. patient_name
  27. data_entry_date
  28. Run the report for Client A.
  29. Verify the 'patient_name' field contains the entire client name, up to 100 characters. This field may need to be set to 'Can Grow' if using Crystal reports.
  30. Close the report.
  31. Open Crystal reports or other SQL Reporting tool.
  32. Create a report against SYSTEM.check_out_client_history.
  33. Include, at a minimum, the following fields
  34. PATID
  35. patient_name
  36. data_entry_date
  37. Run the report for Client A.
  38. Verify the 'patient_name' field contains the entire client name, up to 100 characters. This field may need to be set to 'Can Grow' if using Crystal reports.
  39. Close the report.
Scenario 2: 'Group Registration' - support client names with up to 100 characters.
Specific Setup:
  • Avatar PM 2022 Update 118 and RADplus 2022 Update 126 are required for full functionality.
  • Registry Setting 'Allow Spaces in Client Name' is set to 'Y'.
  • Registry Setting 'Client Demographics - Additional Fields' include a value of '3' to add the client name detail fields.
  • A client (Client A) has been admitted where the client name is greater than 40 characters, up to 100 characters.
Steps
  1. Open 'Group Registration' form.
  2. Select any group in the 'Select Group' field.
  3. Click the group to be selected.
  4. Click [Select].
  5. Click [Group Member Assignment].
  6. Click [Add New Item].
  7. Set the 'Client' field to Client A.
  8. Verify the 'Client' field is populated with the entire client name. The user may need to scroll to the right to view the entire name.
  9. Select any episode in the 'Episode Number' field.
  10. Set the 'Group Assignment Start Date' to any date.
  11. Click [Submit].
  12. Using Crystal Reports or any reporting tool, create a report against SYSTEM.appt_group_member_data table.
  13. Include, at a minimum, the following fields:
  14. PATID
  15. patient_name
  16. group_name.
  17. Run the report for Client A.
  18. Verify the 'patient_name' field is populated with the full client name, up to 100 characters. The user may need to set the field to 'Can Grow' if using Crystal Reports.
  19. Close the report.
  20. Open 'Scheduling Calendar'.
  21. Add a group appointment for a group where Client A is a member.
  22. Click 'Group Members' section.
  23. Verify that Client A displays the full client name. This name may wrap to a second line in order to display all characters.
  24. Click [Submit].
Scenario 3: Admission - validate Registry setting 'Allow spaces in Client Name'.
Specific Setup:
  • Registry Setting 'Avatar PM->Client Information->Client Demographics->->->Allow Spaces in Client Name' is set to 'Y' to allow spaces. Note: Once enabled, the user will only be able to edit an existing client 'Client Name' field within 'Update Client Data' form.
  • Registry Setting 'Client Demographics - Additional Fields' must be set to include '3: 'Detailed Client Name' to enable this functionality. This setting will add the 'Detail Client Name' fields to the 'Demographics' section of Admission forms.
Steps
  1. Open 'Admission (Outpatient)' form.
  2. Set the 'Last Name' on the 'Select Client' popup window to any name value.
  3. Set the 'First Name' on the 'Select Client' popup window to any name value.
  4. Select the gender in the 'Sex' drop down list.
  5. Click [Search].
  6. Click [OK] on the 'Search Results' popup window: 'No matches found'.
  7. Click [New Client].
  8. Click [Yes] on the 'Auto Assign Next ID Number' popup window.
  9. Click on the 'Demographics' section.
  10. Set the 'Client Last Name' to any name including one or more spaces. i.e.: 'Last Name'.
  11. Set the 'Client First Name' to any name including one or more spaces. i.e.: 'First Name'
  12. Set the 'Client Middle Name' to any name including one or more spaces. i.e.: 'Middle Name'.
  13. Complete any required fields.
  14. Click the 'Admission' section.
  15. Verify the 'Client Name' field contains the full name, including spaces.
  16. Click [Submit].
  17. Right click on the client name in the 'Recent Clients' section.
  18. Click 'Display Chart'.
  19. Verify the client name displays all characters entered in the 'Admission' form. Note that the user may need to place the cursor over the client name and review the 'hover help' as it will display the client name.
Scenario 4: Update Client Data - Validate client name allows spaces and client middle name displays up to 25 characters.
Specific Setup:
  • Avatar RADplus 2022 Update 126 is required for full functionality.
  • Registry Setting 'Avatar PM->Client Information->Client Demographics->->->Allow Spaces in Client Name' is set to 'Y' to allow spaces. Note: Once enabled, the user will only be able to edit an existing client 'Client Name' field within 'Update Client Data' form.
  • Registry Setting 'Client Demographics - Additional Fields' must be set to include '3: 'Detailed Client Name' to enable this functionality. This setting will add the 'Detail Client Name' fields to the 'Demographics' section of Admission forms.
Steps
  1. Open 'Update Client Data' form for an existing client.
  2. Set the 'Client Last Name' field to a last name which includes spaces in the name i.e.: 'FRANKLIN MILLER MOTT'
  3. Set the 'Client First Name' field to a first name which includes spaces in the name i.e: 'BENJAMIN WALLY'
  4. Set the 'Client Middle Name' field to a middle name which includes spaces and is maximum of 25 characters i.e: 'BILL ED MIDDLE NAME LONG'
  5. Click [Submit].
  6. Right click on the client name in the 'Recent Clients' list.
  7. Select 'Display Chart'.
  8. Verify the name displays in the client banner, including all spaces and a maximum of 25 characters for the middle name.
  9. Close the client chart.
Topics
• NX • Registry Settings • Update Client Data • Admission (Outpatient) • Group Appointment • Group Member Assignment • Scheduling Calendar
Update 136 Summary | Details
Modeling - Single-Select Dictionary fields
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Table Definition (PM)
  • Modeled Client
Scenario 1: Modeling - Add additional fields to an existing modeled form
Specific Setup:
  • A client must be enrolled in an existing episode (Client A).
  • A modeled form (Form A) must be defined using a table (Table A)
Steps
  1. Access the 'Table Definition' form.
  2. Select "Table A".
  3. Select the "Column Definition" section.
  4. Click [Add New Item].
  5. Enter the desired value in the 'Column Name' field.
  6. Enter the desired value in the 'Column Description' field.
  7. Select "Dictionary - Single Response" in the 'Type of Column' field.
  8. Select "Yes" in the 'Lock Dictionary Values' field.
  9. Click [Submit] and close the form.
  10. Access the 'Dictionary Update' form.
  11. Select "User Defined Client" in the 'File' field.
  12. Select the Data Element created in the previous steps.
  13. Enter the desired value in the 'Dictionary Code' field.
  14. Enter the desired value in the 'Dictionary Value' field.
  15. Click [Apply Changes] and close the form.
  16. Access the 'Form Definition' form.
  17. Select "Form A".
  18. Select the "Section Def." section.
  19. Select any desired section.
  20. Select the "Object Def." section.
  21. Click [Add New Item].
  22. Select the table column added in the previous steps in the 'Table Column' field.
  23. Select "No" in the 'Default to Specific Value on Addition of a New Table Row' field.
  24. Click [Submit].
  25. Select "Client A" and access "Form A".
  26. Validate the new single-select dictionary field is displayed with the dictionary value defined.
  27. Validate the dictionary value is NOT selected.
  28. Close the form.
Topics
• Modeling