Skip to main content

RADplus 2022 Monthly Release 2022.02.01 Acceptance Tests

  1. Last updated
  2. Save as PDF
Update 12 Summary | Details
Cache Temporary Storage file for images
Scenario 1: Validate client picture and signature images submitted in forms - "AutoSave" enabled
Specific Setup:
  • Have a modeled form, [FormA] that includes:
  • "Client Picture" table column is added to the form with setting and "Allow User to Update Client Picture Image" to "Yes"
  • "Signature" field object added to the form
  • Setting "Form supports automatic backup" set to "Yes" in "Form Definition"
  • Have a "Progress Note" form [FormB] for example the "Inpatient Progress Notes" form, that includes:
  • Site-specific "Signature" field object added to the form
  • "Autosave" enabled on the form
  • Have three image files (for example "jpg" pictures) "Image1", "Image2" and "Image3" available for import from the server
  • [UserA] has access to both [FormA] and [FormB] and the forms have been added to their "Chart" view
Steps
  1. Open [FormA]
  2. Select a client [ClientA]
  3. Navigate to the "Signature" field
  4. Click [Get Signature]
  5. Populate the "Please Sign" signature box with signature [Sig1]
  6. Click [OK]
  7. Click [Get Signature] again
  8. Populate the "Please Sign" signature box with a different signature [Sig2]
  9. Click [OK]
  10. Click [Get Signature] again
  11. Populate the "Please Sign" signature box with a different signature [Sig3]
  12. Click [OK]
  13. Navigate to the "Client Picture" field.
  14. Click to "Acquire Image"
  15. Navigate to the folder on server containing the images stated in the set up
  16. Select [Image1]
  17. Validate "Image1" is displayed in the "Client Picture" field
  18. Repeat step c, this time selecting [Image2]
  19. Validate results are as expected
  20. Repeat step c, this time selecting [Image3]
  21. Validate results are as expected.
  22. Populate any other desired fields, making note of the values entered
  23. Click the [Backup] form button
  24. Click to exit the form
  25. Open [FormA]
  26. Select a client [ClientA]
  27. Validate a message displays: "You have an unsubmitted backup of this data record. Do you wish to restore from the backup?"
  28. Click [Yes]
  29. Navigate to the "Signature" field
  30. Validate the field is populated with the last signature signed[Sig3], as expected
  31. Navigate to the "Client Picture" field
  32. Validate the field is populated with the imported [Image3], as expected
  33. Validate all other fields are populated as expected
  34. Submit the form
  35. Return to [FormA]
  36. Select a client [ClientA]
  37. Select the row just submitted
  38. Navigate to the "Signature" field
  39. Validate the field is populated with the last signature signed[Sig3], as expected
  40. Navigate to the "Client Picture" field
  41. Validate the field is populated with the imported [Image3], as expected
  42. Validate all other fields are populated as expected
  43. At the home view, right-click on [ClientA] to go to their "Chart"
  44. Select [FormA] in the forms list
  45. Validate the row submitted in step 3 is present
  46. Locate to the "Signature" field
  47. Validate the field is populated with the last signature signed[Sig3], as expected
  48. Locate to the "Client Picture" field
  49. Validate the field is populated with the imported [Image3], as expected
  50. Validate all other fields are populated as expected
  51. Repeat steps 1 thru 4 for the [FormB] that contains the signature field
  52. Validate results are as expected
Scenario 2: Validate client picture and signature images submitted in forms - "Autosave" not enabled
Specific Setup:
  • Have a modeled form, [FormA] that includes:
  • "Client Picture" table column is added to the form with setting and "Allow User to Update Client Picture Image" to "Yes"
  • "Signature" field object added to the form
  • Setting "Form supports automatic backup" set to "No" in "Form Definition"
  • Have a "Progress Note" form [FormB] for example the "Inpatient Progress Notes" form, that includes:
  • Site-specific "Signature" field object added to the form
  • "Autosave" is not enabled on the form
  • Have three image files (for example "jpg" pictures) "Image1", "Image2" and "Image3" available for import from the server
  • [UserA] has access to both [FormA] and [FormB] and the forms have been added to their "Chart" view
Steps
  1. Open [FormA]
  2. Select a client [ClientA]
  3. Navigate to the "Signature" field
  4. Click [Get Signature]
  5. Populate the "Please Sign" signature box with signature [Sig1]
  6. Click [OK]
  7. Click [Get Signature] again
  8. Populate the "Please Sign" signature box with a different signature [Sig2]
  9. Click [OK]
  10. Click [Get Signature] again
  11. Populate the "Please Sign" signature box with a different signature [Sig3]
  12. Click [OK]
  13. Navigate to the "Client Picture" field.
  14. Click to "Acquire Image"
  15. Navigate to the folder on server containing the images stated in the set up
  16. Select [Image1]
  17. Validate "Image1" is displayed in the "Client Picture" field
  18. Repeat step c, selecting [Image2]
  19. Validate results are as expected
  20. Repeat step c, selecting [Image3]
  21. Validate results are as expected.
  22. Populate any other desired fields, making note of the values entered
  23. Submit the form
  24. Open [FormA]
  25. Select a client [ClientA]
  26. Navigate to the "Signature" field
  27. Validate the field is populated with the last signature signed[Sig3], as expected
  28. Navigate to the "Client Picture" field
  29. Validate the field is populated with the imported [Image3], as expected
  30. Validate all other fields are populated as expected
  31. Exit the form
  32. At the home view, right-click on [ClientA] to go to their "Chart"
  33. Select [FormA] in the forms list
  34. Validate the row submitted in step 2 is present
  35. Locate to the "Signature" field
  36. Validate the field is populated with the last signature signed[Sig3], as expected
  37. Locate to the "Client Picture" field
  38. Validate the field is populated with the imported [Image3], as expected
  39. Validate all other fields are populated as expected
  40. Repeat steps 1 thru 3 for the [FormB] that contains the signature field
  41. Validate results are as expected
Topics
• Modeling • Auto Save • Client Image • NX • Forms • Signatures
Update 30 Summary | Details
State Form Button Mapping
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • State Form Button Mapping
Scenario 1: Validate the use of "State Form Button" mapping functionality in a Modeled Form
Specific Setup:
  • Have a client [ClientA], that's currently admitted in two episodes. [Episode1] and [Episode2]
  • Have a state form definition file [StateFormDefA] created that extracts the "Episode" number from the "SYSTEM.admission_data" table
  • Have modeled form [FormA] that includes a "ScriptLink" type button [PopulateA] defined, as well as an "Episode" number field on the form
  • In form "State Form Button Mapping", have the following prompts populated with the form submitted
  • [PopButtonA] selected in the "Button Field"
  • [StateFormDefA] selected in the "State Form Definition" field
  • "Episode Number" selected in the "Parameter Field 1" field
  • "Netsmart" has configured the [PopulateA] button on [FormA] using "Programmer Override" logic so that when the button is clicked, it will run state form definition file [StateformDefA] to populate "Episode" number field on [FormA], with the current selected episode
Steps
  1. Open [FormA]
  2. Select the desired client [ClientA]
  3. Select [Episode1]
  4. Click the [PopulateA] button, set up on the form
  5. Validate the [Episode] field contains the expected selected episode, [Episode1]
  6. Click [Submit]
  7. Validate the form files successfully
  8. Return to [FormA]
  9. Select [Episode1]
  10. Select [ClientA]
  11. Validate the [Episode] field contains the expected selected episode, [Episode1]
  12. Close the form
  13. pen [FormA]
  14. Select the desired client [ClientA]
  15. Select [Episode2]
  16. Click the [PopulateA] button, set up on the form
  17. Validate the [Episode] field contains the expected selected episode, [Episode2]
  18. Click [Submit]
  19. Validate the form files successfully
  20. Return to [FormA]
  21. Select [Episode2]
  22. Select [ClientA]
  23. Validate the [Episode] field contains the expected selected episode, [Episode2]
  24. Close the form
State Form Tools - Populate functionality
Scenario 1: Validate the use of "State Form Button" mapping functionality in a Modeled Form w/Event Logic
Specific Setup:
  • Have a modeled form [FormA], that includes the following field types: "Name" field [NameA] ;"Date" field [DOB] ; "Dictionary" field [FieldA], Dictionary field [FieldB] and "ScriptLink" button [PopulateA]
  • [FormA] has event logic set on a field [FieldA] that will set [FieldB] to be required when specific value [Value1], is selected in [FieldA]
  • Have a "State Form Definition" file [StateFormDefA] created that extracts the "Patient Name" and "Date of birth" from the "SYSTEM.patient_current_demographics" table
  • Have the "State Form Button Mapping" form submitted with following values populated:
  • [PopulateA] selected in the "Button Field"
  • [StateFormDefA] is selected in the "State Form Definition" field
  • [FieldA] is selected in the "Parameter Field1" field
  • [FieldB] is selected in the "Parameter Field2" field
  • "Netsmart" has configured the [PopulateA] button on [FormA] using "Programmer Override" logic to run state form definition file [StateformDefA] to then populate field values on [FormA] and also trigger any expected event logic
Steps
  1. Open [FormA]
  2. Select [ClientA]
  3. Click the [PopulateA] button, set up on the form
  4. Validate the [Name] field contains the expected name for [ClientA]
  5. Validate the [Date] field contains the date of birth for [ClientA]
  6. Validate [FieldA] is populated with [ValueA], the trigger value for the event logic
  7. Validate [FieldB] is set to be 'Required', as expected
  8. Deselect any values selected in the field
  9. Submit the form
  10. Validate a message indicating [FieldB] is not populated is displayed
  11. Select a value in [FieldB]
  12. Submit the form
  13. Validate the form files successfully
  14. Return to [FormA]
  15. Select [ClientA]
  16. Validate fields all are populated as expected
Topics
• NX • State Form Tools
Update 54 Summary | Details
Manage Observer Caseload
Scenario 1: Manage Observer Caseload - Adding client to Caseload
Specific Setup:
  • Have or create a user [UserA] in form "User Definition", that includes a period "." in their "UserID"
  • Have or create another user [UserB] in form "User Definition", that does not include a period "." in their "UserID"
Steps
  1. Open the "Manage Observer Caseload" form
  2. Select [UserA] in the "Select User" field
  3. Click the "Caseload" radio button
  4. Click "Add" in the "Add or Remove Client From Caseload" field
  5. Select a client [ClientB], from the "Unit" field or by using the "Client" search field
  6. Click the [Upload Caseload] button.
  7. Validate the "Current Caseload" field contains [ClientA]
  8. Select [UserB] in the "Select User" field
  9. Click the "Caseload" radio button
  10. Click "Add" in the "Add or Remove Client From Caseload" field
  11. Select a client [ClientB], from the "Unit" field or by using the "Client" search field
  12. Validate the "Current Caseload" field contains [ClientB]
  13. Exit the form
  14. Open form "Change UserID"
  15. Select [UserA] in the "User" field
  16. Populate the "New User ID" field with a new user ID [UserC]
  17. Submit the form
  18. Validate the form files successfully
  19. Return to the form
  20. Select [UserB] in the "User" field
  21. Populate the "New User ID" field [UserD]
  22. Submit the form
  23. Validate the form files successfully
  24. Open the "Manage Observer Caseload" form
  25. Search for [UserA]
  26. Validate [UserA] is not found
  27. Search for [UserC]
  28. Validate [UserC] the users new ID, is found
  29. Validate [ClientA] added in step 1 displays in the "Current Caseload" field, as expected
  30. Search for [UserB]
  31. Validate [UserB] is not found
  32. Search for [UserD]
  33. Validate [UserD] the users new ID, is found
  34. Validate [ClientB] added in step 1 displays in the "Current Caseload" field, as expected
Topics
• User Definition • NX
Update 58 Summary | Details
'Team Assignment' is enhanced to no longer allow inactive teams in the drop down search.
Scenario 1: 'Team Assignment' - validate Inactive and Deleted Teams are no longer included in the 'Admission' form 'Team Assignment' selection drop down field.
Specific Setup:
  • RADplus 2022 Update 58 is required for full functionality.
  • One or more teams are defined in the 'Team Definition' form.
  • Client A is assigned to a team which will be flagged as 'Inactive'.
  • Using 'Team Definition', flag the team Client A is assigned to as 'Inactive'.
  • Client B is assigned to a team which will be deleted.
  • Using 'Team Definition', flag the team Client B assigned to as 'Deleted'
Steps
  1. Create a report against SQL Table 'admission_data_other'.
  2. Include in the report, at a minimum, the following fields:
  3. PATID
  4. team_assignment_value
  5. team_assignment_code
  6. data_entry_date
  7. Run the report. Note the values entered for Client A and Client B. The team_assignment_value and team_assignment_code fields will be blank for both clients.
  8. Open the 'Admission (Outpatient)' form. Note that this functionality is the same in the 'Admission' form as well.
  9. Select Client A.
  10. Verify that there is no selection in the 'Team Assignment' field.
  11. Navigate to the 'Team Assignment' field.
  12. Click on the drop down list.
  13. Verify that no Teams defined as 'Inactive' are displayed for selection.
  14. Select any active Team from the list.
  15. Click [Submit].
  16. Open the 'Admission (Outpatient)' form. Note that this functionality is the same in the 'Admission' form as well.
  17. Select Client B.
  18. Verify that there is no selection in the 'Team Assignment' field. This team has been deleted from the 'Team Definition' form.
  19. Navigate to the 'Team Assignment' field.
  20. Click on the drop down list.
  21. Verify that no Teams which were deleted are included in the drop down list.
  22. Select any active Team from the list.
  23. Click [Submit].
  24. Run the report again.
  25. Verify the team_assignment_value and team_assignment_code fields are populated for both Client A and Client B.
Topics
• NX • Team Assignment
Update 59 Summary | Details
Form Designer
Scenario 1: Form Designer - Form field validations
Specific Setup:
  • Have a system with multiple root system codes defined.
  • [UserA] has access to the "Form Designer" form
  • [UserA] access to the following forms:
  • 'Table Definition', 'Form Definition', 'Envelope Definition', 'Report Definition', 'Site Specific Section Modeling' and any other desired forms
  • [UserA] is logged any desired root system code
Steps
  1. Open form "Form Designer"
  2. From the "Forms" list, select any desired form
  3. Select any section from the "Sections" tab
  4. Validate field "Other System Codes to File Form Designer Changes to" contains all other valid root systems codes, displayed as expected
  5. Click back to the "Forms" list and validate the following forms are present for selection in the drop down list:
  6. 'Table Definition'
  7. 'Form Definition'
  8. 'Envelope Definition'
  9. 'Report Definition'
  10. 'Site Specific Section Modeling'
  11. Select each form in step c
  12. Click [Show Section]
  13. Select each section listed for the form for edit:
  14. Validate the form layout is displayed as expected
  15. Click [Save]
  16. Validate the section saved successfully
  17. Click [Submit]
  18. Validate the "Form Definition" form is saved successfully
Form Designer and Form Definition (Form's) - Product design and field changes
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Form Definition (CWS)
Scenario 1: Form Designer - Revert changes to a previous layout
Specific Setup:
  • Have a system where the cache server resides in a different time zone than the client's workstation. For example, cache server rides in "Central" time zone, users workstation is in "Eastern" time zone.
  • In the 'Registry Settings' form, set registry 'Utilize Local Workstation Time Zone' setting to "Y".
  • Open any form [FormA] in "Form Designer" and make any change to the field layout on the form. [FDChange1].
  • Note the current layout of the form and the current date and time.
  • Submit the form.
Steps
  1. Open the 'Form Designer' form.
  2. Select [FormA] from the 'Forms' field.
  3. Select the desired section.
  4. Click [Show Section].
  5. Validate the changes made [FDChange1] in the setup, are present.
  6. Make another change to form field layout. [FDChange2].
  7. Note the current layout of the form and the current date and time.
  8. Submit the form.
  9. Repeat steps 1 thru 4.
  10. Validate the changes made [FDChange2] in the setup, are present on the form layout.
  11. Click [Cancel] then [Yes] to go back to the main section.
  12. In the "Revert To Other Form Designer Copy" select "Yes".
  13. Click the "Select Copy to Revert to" drop down list.
  14. Locate the row of the last change made [FDChange2].
  15. Validate the timestamp for that row is consistent with the data and time noted in step 6.
  16. Locate the row of form designer change made in the setup [FDChange1].
  17. Validate the timestamp for that row is consistent with the data and time noted in setup.
  18. Select that row.
  19. Submit the form.
  20. On the home view, search for [FormA].
  21. Open the form.
  22. Validate the form layout of the form is consistent with the layout [FDChange1], reverted to in step 11.
Scenario 2: Form Definition (Form) - Validate "Netsmart Produced " product design field and format changes
Specific Setup:
  • Have access to the "Form Definition" form in the "PM" namespace and any child namespace
  • Have access to the "Form Designer" form in the "PM" namespace and any child namespace
  • Have access to any modeled form in each namespace [FormA]
  • In each namespace, open "Form Definition" and select [FormA], make a note the following:
  • In "Event Definition" section, note the size of all the "Multi-Select" dictionary fields, for example, the "Enable", "Disable", "Required", "Not Required", "Hide" and "Unhide" fields
Steps
  1. Open form "Form Designer"
  2. From the "Forms" drop down list, select "Form Definition"
  3. Select the "Event Def." section from the "Sections" field
  4. Navigate to the "Select Copy to Revert to" field.
  5. Select "Netsmart Produced Changes". (Please Note: This selection will revert the section to the latest Netsmart product design layout for the section. Note: In the event the user wants to revert to the previous layout after submission, the user can return and select the previous layout from the "Select Copy to Revert to" field drop down list and restore it back)
  6. Click [Submit]
  7. Validate the form files successfully
  8. Navigate back to the "Form Definition"
  9. Select [FormA]
  10. Navigate to the "Object Definition" and select a field to edit
  11. Click the "Event Def" section on the left side
  12. Scroll down and observe the size of all the "Multi-Select" dictionary fields, for example, the "Enable", "Disable", "Required", "Not Required", "Lock", "Unlock" and "Fields for Summation" fields
  13. Validate the size of the box containing the dictionary values of the fields noted in the set up has increased and more dictionary values are now visible, if applicable. (Note: the increase is approximately twice the original size)
  14. Close the form
  15. Repeat steps 1 and 2 in any child namespaces
  16. Validate results are as expected
Topics
• Form Designer • NX • Auto Save • Azure Authentication • Assign MR# • Audit Log
Update 63 Summary | Details
User Management web service
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • User Definition
Scenario 1: Updating a user using the 'User Management' web service
Specific Setup:
  • Have a system with “Netsmarts "(NIAM) Netsmart’s Identity and Access Management" functionality” configured.
  • In form "User Definition",:
  • User [ExternalA] has is set with prompt 'Use External Login' to 'Yes' and an external user ID populated in field in 'External Login ID'
  • User [ExternalA] is assigned to a user role with "SQL" Table access in form "User Definition"
  • User [NoExternalA] is assigned is set with prompt 'Use External Login' to 'No' and is assigned to any user role
  • Have access to form "Change User ID"
  • Have access to program "SoapUI" to execute web services
  • Have the web service "WEBSVC.UserManagement" imported and the "UpdateUser" request populated with the required fields to update an existing user
Steps
  1. Open "SoapUI"
  2. Navigate to the "WEBSVC.UserManagement" web service
  3. Locate the <UserID> field in the "UpdateUser" request configured in the set up
  4. Populate the field with the UserID for [UserA]
  5. Change the existing value in any field currently populated. For example, change the current value in the <User Description> field to a different value [NewValueA]
  6. Click the "Submit Request" arrow to execute the web service
  7. Validate the 'Message' field in the response section states: "User [UserA] was successfully updated"
  8. Open form "User Definition"
  9. Select [UserA]
  10. Locate the field that was updated in step 1
  11. Validate the field updated via the web service in step1, contains the new value [NewValueA]
  12. Navigate back to the "WEBSVC.UserManagement" web service
  13. Locate the <UserID> field in the "UpdateUser" request configured in the set up
  14. Populate the field with the UserID for [UserB]
  15. Change the existing value in any field currently populated. For example, change the current value in the <User Description> field to a different value [NewValueA]
  16. Click the "Submit Request" arrow to execute the web service
  17. Validate the 'Message' field in the response section states: "User [UserB] was successfully updated"
  18. Open form "User Definition"
  19. Select [UserB]
  20. Locate the field that was updated in step 3
  21. Validate the field updated via the web service in step 3, contains the new value [NewValueA]
  22. Navigate back to the "WEBSVC.UserManagement" web service
  23. Locate the <UserID> filed in the "UpdateUser" request configured in the set up
  24. Populate the field with the UserID for [UserC]
  25. Change the existing value in any field currently populated. For example, change the current value in the <User Description> field to a different value [NewValueA]
  26. Click the "Submit Request" arrow to execute the web service
  27. Validate the 'Message' field in the response section states: "User [UserC] was successfully updated"
  28. Open form "User Definition"
  29. Select [UserC]
  30. Locate the field that was updated in step 5
  31. Validate the field updated via the web service in step4, contains the new value [NewValueA]
Topics
• Web Services
Update 80 Summary | Details
"UpdateUser" web service
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • User Definition
Scenario 1: Updating a user using the 'User Management' web service
Specific Setup:
  • Have a system with “Netsmarts "(NIAM) Netsmart’s Identity and Access Management" functionality” configured.
  • In form "User Definition",:
  • User [ExternalA] has is set with prompt 'Use External Login' to 'Yes' and an external user ID populated in field in 'External Login ID'
  • User [ExternalA] is assigned to a user role with "SQL" Table access in form "User Definition"
  • User [NoExternalA] is assigned is set with prompt 'Use External Login' to 'No' and is assigned to any user role
  • Have access to form "Change User ID"
  • Have access to program "SoapUI" to execute web services
  • Have the web service "WEBSVC.UserManagement" imported and the "UpdateUser" request populated with the required fields to update an existing user
Steps
  1. Open "SoapUI"
  2. Navigate to the "WEBSVC.UserManagement" web service
  3. Locate the <UserID> field in the "UpdateUser" request configured in the set up
  4. Populate the field with the UserID for [UserA]
  5. Change the existing value in any field currently populated. For example, change the current value in the <User Description> field to a different value [NewValueA]
  6. Click the "Submit Request" arrow to execute the web service
  7. Validate the 'Message' field in the response section states: "User [UserA] was successfully updated"
  8. Open form "User Definition"
  9. Select [UserA]
  10. Locate the field that was updated in step 1
  11. Validate the field updated via the web service in step1, contains the new value [NewValueA]
  12. Navigate back to the "WEBSVC.UserManagement" web service
  13. Locate the <UserID> field in the "UpdateUser" request configured in the set up
  14. Populate the field with the UserID for [UserB]
  15. Change the existing value in any field currently populated. For example, change the current value in the <User Description> field to a different value [NewValueA]
  16. Click the "Submit Request" arrow to execute the web service
  17. Validate the 'Message' field in the response section states: "User [UserB] was successfully updated"
  18. Open form "User Definition"
  19. Select [UserB]
  20. Locate the field that was updated in step 3
  21. Validate the field updated via the web service in step 3, contains the new value [NewValueA]
  22. Navigate back to the "WEBSVC.UserManagement" web service
  23. Locate the <UserID> filed in the "UpdateUser" request configured in the set up
  24. Populate the field with the UserID for [UserC]
  25. Change the existing value in any field currently populated. For example, change the current value in the <User Description> field to a different value [NewValueA]
  26. Click the "Submit Request" arrow to execute the web service
  27. Validate the 'Message' field in the response section states: "User [UserC] was successfully updated"
  28. Open form "User Definition"
  29. Select [UserC]
  30. Locate the field that was updated in step 5
  31. Validate the field updated via the web service in step4, contains the new value [NewValueA]
Scenario 2: Updating a user using the 'User Management' web service
Specific Setup:
  • Have a system configured to use Netsmart's "(NIAM) Netsmart’s Identity and Access Management" functionality
  • In form "User Definition":
  • User [UserA] is set with prompt 'Use External Login' to 'Yes' and an external user ID populated in field in 'External Login ID'
  • User [UserA] is assigned to a user role with "SQL" table access
  • User [UserB] is set with prompt 'Use External Login' to 'No' and is assigned to any desired user role
  • Have access to form "Change User ID"
  • Have access to program "SoapUI" to execute web services
  • Have the web service "WEBSVC.UserManagement" imported and the "UpdateUser" request populated with the required fields to update an existing user
Steps
  1. Open "SoapUI"
  2. Navigate to the "WEBSVC.UserManagement" web service
  3. Locate the "<UserID>" field in the "UpdateUser" request configured in the set up
  4. Populate the field with [UserA]
  5. Change the current value in the "<User Description>" field to a different value [NewValueA]
  6. Change the value of a second field, for example "Warn Non Caseload Access" to a new value [NewValueB]
  7. Click the "Submit Request" arrow to execute the web service
  8. Validate the message 'User USERA successfully updated', is displayed as expected
  9. Open form "User Definition"
  10. Select [UserA]
  11. Validate the "User Description" field contains the new value [NewValueA], updated via web service
  12. Validate the field "Warn if User Attempts Non Caseload Access" is set to [NewValueB], updated via the web service
  13. Open form "Change User ID"
  14. Select [UserB] in the "User" Field
  15. Populate the "New User ID" field with a new ID [UserC]
  16. Submit the form
  17. Validate the form files successfully
  18. Open form "User Definition"
  19. Select [UserB]
  20. Validate the field "Deactivate User" is checked
  21. Validate only the "User Description" field is enabled on the form
  22. Navigate back to the "WEBSVC.UserManagement" web service
  23. Locate the "<UserID>" field in the "UpdateUser" request configured in the set up
  24. Populate the field with [UserB]
  25. Change the current value in the "<User Description>" field to a different value [NewValueA]
  26. Change the value of a second field, for example "Warn Non Caseload Access" to a new value [NewValueB]
  27. Click the "Submit Request" arrow to execute the web service
  28. Validate message 'User USERB successfully updated', is displayed
  29. Open form "User Definition"
  30. Select [UserB]
  31. Validate the "User Description" field contains the new value [NewValueA], updated via web service
  32. Validate the field "Warn if User Attempts Non Caseload Access" is not set to its original valued, as only the "User Description" field can be updated for deactivated users
  33. Navigate back to the "WEBSVC.UserManagement" web service
  34. Locate the "<UserID>" filed in the "UpdateUser" request configured in the set up
  35. Populate the field with the [UserC]
  36. Change the current value in the "<User Description>" field to a different value [NewValueA]
  37. Change a value of a second field, for example "Warn Non Caseload Access" to a new value [NewValueB]
  38. Click the "Submit Request" arrow to execute the web service
  39. Validate message "User USERC successfully updated", is displayed
  40. Open form "User Definition"
  41. Select [UserC]
  42. Validate the "User Description" field contains the new value [NewValueA], updated via web service
  43. Validate the field "Warn if User Attempts Non Caseload Access" is set to [NewValueB], updated via the web service
Topics
• Web Services
Update 82 Summary | Details
About - Copyright Information
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • NX - Application About
  • myAvatar 2021 - About
  • myAvatar 2021 - Copyright
Scenario 1: Avatar NX - Validate the 'About' dialog
Steps
  1. Navigate to the 'User Menu'.
  2. Click [About].
  3. Validate the 'About' dialog is displayed.
  4. Validate the 'CPT Copyright' field is displayed and contains the following: "CPT copyright 2021 American Medical Association. All rights reserved. Fee scheduled, relative value units, conversion factors and/or related components are not assigned by the AMA, are not part of the CPT, and the AMA is not recommending their use. The AMA does not directly or indirectly practice medicine or dispense medical services. The AMA assumes no liability for data contained or not contained herein. CPT is a registered trademark of the American Medical Association. U.S. Government End Users. CPT is commercial technical data, which was developed exclusively at private expense by the American Medical Association (AMA), 330 North Wabash Avenue, Chicago, Illinois 60611. Use of CPT in connection with this product shall not be construed to grant the Federal Government a direct license to use CPT based on FAR52.227-14 (Data Rights - General) and DFARS 252.227-7015 (Technical Data - Commercial Items). The responsibility for the content of any "National Correct Coding Policy" included in this product is with the Centers for Medicare and Medicaid Services and no endorsement by the AMA or should be implied. The AMA disclaims responsibility for any consequences or liability attributable to or related to any use, nonuse or interpretation of information contained in this product."
  5. Click [OK].
  6. Validate the 'About' dialog is no longer displayed.
Scenario 2: myAvatar - Validate the 'About' dialog
Steps
  1. Click [Help].
  2. Select "About..." from the 'Help' menu.
  3. Validate the 'About' dialog is displayed.
  4. Click [Copyright Information].
  5. Validate the 'Copyright' dialog is displayed.
  6. Scroll down and validate there is a 'CPT' field.
  7. Validate the CPT field contains: "CPT copyright 2021 American Medical Association. All rights reserved. Fee scheduled, relative value units, conversion factors and/or related components are not assigned by the AMA, are not part of the CPT, and the AMA is not recommending their use. The AMA does not directly or indirectly practice medicine or dispense medical services. The AMA assumes no liability for data contained or not contained herein. CPT is a registered trademark of the American Medical Association. U.S. Government End Users. CPT is commercial technical data, which was developed exclusively at private expense by the American Medical Association (AMA), 330 North Wabash Avenue, Chicago, Illinois 60611. Use of CPT in connection with this product shall not be construed to grant the Federal Government a direct license to use CPT based on FAR52.227-14 (Data Rights - General) and DFARS 252.227-7015 (Technical Data - Commercial Items). The responsibility for the content of any "National Correct Coding Policy" included in this product is with the Centers for Medicare and Medicaid Services and no endorsement by the AMA or should be implied. The AMA disclaims responsibility for any consequences or liability attributable to or related to any use, nonuse or interpretation of information contained in this product."
  8. Click [Close] and [OK].
  9. Validate the 'Copyright' and 'About' dialogs are no longer displayed.
Topics
• NX • About...
Update 93 Summary | Details
Avatar NX - 'My To Do's' 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
Scenario 1: Progress Notes (Group and Individual) - Document Routing - "Allow Transcriber" functionality - Reject/Respond
Specific Setup:
  • A user has an associated staff member and has "Yes" selected in the 'Transcriber' field in 'User Definition (User A).
  • A user has an associated staff member and is not a transcriber in 'User Definition' (User B).
  • "User A" and "User B" have the 'My To Do's' widget on their HomeView.
  • Document routing is enabled for 'Progress Notes (Group and Individual)' and 'Allow Transcriber' is set to "Yes".
  • A client must be enrolled in an existing episode (Client A).
  • Must be logged in as "User A".
  • Please note: this scenario is for Avatar NX systems.
Steps
  1. Access the 'Progress Notes (Group and Individual)' form.
  2. Select "Client A" in the 'Select Client' 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' field.
  6. Select "Final" in the 'Draft/Final' field.
  7. Click [File Note].
  8. Validate a "Select Author" dialog is displayed.
  9. Select the staff member associated to "User B" in the 'Select Author' field.
  10. Click [Submit] and verify successful filing.
  11. Log out.
  12. Log in as "User B".
  13. Navigate to the 'My To Do's' widget.
  14. Validate there is a To Do for "Client A".
  15. Click [Transcription Review].
  16. Validate the document is displayed with the progress note data and has electronic signatures for the Transcriber (User A) & Author (User B).
  17. Click [Reject].
  18. Enter the desired value in the 'Comments for Rejected' field and click [Sign].
  19. Validate the To Do is no longer displayed.
  20. Log in as "User A".
  21. Navigate to the 'My To Do's' widget.
  22. Validate there is a To Do for "Client A".
  23. Click [Review To Do Item].
  24. Validate the 'To Do Information' field contains the response from "User B".
  25. Select "Reviewed" in the 'Set To Do Item to Reviewed' field.
  26. Click [Submit].
  27. Validate the To Do is no longer displayed.
Scenario 2: Treatment Plan - Document Routing - "Allow Transcriber" functionality - Reject/Respond
Specific Setup:
  • A user has an associated staff member and has "Yes" selected in the 'Transcriber' field in 'User Definition (User A).
  • A user has an associated staff member and is not a transcriber in 'User Definition' (User B).
  • "User A" and "User B" have the 'My To Do's' widget on their HomeView.
  • Document routing is enabled for 'Treatment Plan' and 'Allow Transcriber' is set to "Yes".
  • A client must be enrolled in an existing episode (Client A).
  • Must be logged in as "User A".
  • Please note: this scenario is for Avatar NX systems.
Steps
  1. Access the 'Treatment Plan' form.
  2. Select "Client A" in the 'Select Client' field.
  3. Enter the desired date in the 'Plan Date' field.
  4. Select any value in the 'Plan Type' field.
  5. Select "Draft" in the 'Treatment Plan Status' field.
  6. Click [Launch Plan].
  7. Click [Add New Problem].
  8. Populate any required and desired fields.
  9. Click [Return to Plan] and [OK].
  10. Select "Final" in the 'Treatment Plan Status' field.
  11. Click [Submit].
  12. Validate a "Select Author" dialog is displayed.
  13. Select the staff member associated to "User B" in the 'Select Author' field.
  14. Click [Submit] and verify successful filing.
  15. Log out.
  16. Log in as "User B".
  17. Navigate to the 'My To Do's' widget.
  18. Validate there is a To Do for "Client A".
  19. Click [Transcription Review].
  20. Validate the treatment plan has electronic signatures for the Transcriber (User A) & Author (User B).
  21. Click [Reject].
  22. Enter the desired value in the 'Comments for Rejected' field and click [Sign].
  23. Validate the To Do is no longer displayed.
  24. Log out.
  25. Log in as "User A".
  26. Navigate to the 'My To Do's' widget.
  27. Validate there is a To Do for "Client A".
  28. Click [Review To Do Item].
  29. Validate the 'To Do Information' field contains the response from "User B".
  30. Select "Reviewed" in the 'Set To Do Item to Reviewed' field.
  31. Click [Submit].
  32. Validate the To Do is no longer displayed.
Scenario 3: Incident Data Form - Review To Do Item
Specific Setup:
  • Logged in user must have a to do sent to them through the 'Incident Data Form'.
  • User must have the 'My To Do's' widget configured on a view.
Steps
  1. Navigate to the 'User Menu'.
  2. Select "Preferences" in the 'User Menu'.
  3. Select "Slideout" in the 'To Do's' field
  4. Click [Save].
  5. Navigate to the 'My To Do's' widget.
  6. Validate there is a To-Do for the 'Incident Data Form'.
  7. Click [Review To Do Item].
  8. Validate the slideout To-Do loads.
  9. Click [Discard].
  10. Click [Incident Data Form].
  11. Validate the 'Incident Data Form' loads with the data populated.
  12. Click [Discard].
  13. Close the ToDo's.
  14. Navigate to the 'User Menu'.
  15. Select "Preferences" in the 'User Menu'.
  16. Select "Normal" in the 'To Do's' field
  17. Click [Save].
  18. Navigate to the 'My To Do's' widget.
  19. Click [Incident Data Form].
  20. Validate the 'Incident Data Form' loads with the data populated.
  21. Navigate to the 'Supervisor Report' field.
  22. Populate all required and desired fields.
  23. Click [Submit].
  24. Navigate back to the 'My To Do's' widget.
  25. Click [Review To Do Item].
  26. Validate the To-Do loads.
  27. Select "Reviewed" in the 'Set To Do Item to Reviewed' field.
  28. Click [Submit].
  29. Validate the To-Do is no longer present.
Scenario 4: Treatment Plan - Document Routing - "Allow Transcriber" functionality - Approve
Specific Setup:
  • A user has an associated staff member and has "Yes" selected in the 'Transcriber' field in 'User Definition (User A).
  • A user has an associated staff member and is not a transcriber in 'User Definition' (User B).
  • "User A" and "User B" have the 'My To Do's' widget on their HomeView.
  • "User B" must have at least three documents routed to their To-Do's.
  • Document routing is enabled for 'Treatment Plan' and 'Allow Transcriber' is set to "Yes".
  • A client must be enrolled in an existing episode (Client A).
  • Must be logged in as "User A".
  • Please note: this scenario is for Avatar NX systems.
Steps
  1. Access the 'Treatment Plan' form.
  2. Select "Client A" in the 'Select Client' field.
  3. Enter the desired date in the 'Plan Date' field.
  4. Select any value in the 'Plan Type' field.
  5. Select "Draft" in the 'Treatment Plan Status' field.
  6. Click [Launch Plan].
  7. Click [Add New Problem].
  8. Populate any required and desired fields.
  9. Click [Return to Plan] and [OK].
  10. Select "Final" in the 'Treatment Plan Status' field.
  11. Click [Submit].
  12. Validate a "Select Author" dialog is displayed.
  13. Select the staff member associated to "User B" in the 'Select Author' field.
  14. Click [Submit] and verify successful filing.
  15. Log out.
  16. Log in as "User B".
  17. Navigate to the 'My To Do's' widget.
  18. Validate there is a To Do for "Client A".
  19. Click [Review All].
  20. Validate the treatment plan has electronic signatures for the Transcriber (User A) & Author (User B).
  21. Validate all of the documents to sign display in the 'Queue' field.
  22. Select "Client Name A-Z" in the 'Sort By' field.
  23. Validate the to do's are sorted alphabetically.
  24. Select "To Do Type A-Z" in the 'Sort By' field.
  25. Validate the to do's are sorted by type alphabetically.
  26. Click [Treatment Plan].
  27. Validate an 'Unsaved Changes' dialog stating: "You have unsaved changes would you like to continue?"
  28. Click [OK].
  29. Validate the treatment plan for "Client A" opens as a Draft.
  30. Select "Final" in the 'Treatment Plan Status' field.
  31. Click [Submit].
  32. Validate a 'Confirm Document' dialog displaying the treatment plan for "Client A" and click [Accept].
  33. Enter the password associated with the logged in user and click [Verify].
  34. Validate the to do for "Client A" is no longer present in the 'My To Do's' widget.
  35. Close the To Do's.
Scenario 5: Progress Notes (Group and Individual) - Document Routing - "Allow Transcriber" functionality - Approve
Specific Setup:
  • A user has an associated staff member and has "Yes" selected in the 'Transcriber' field in 'User Definition (User A).
  • A user has an associated staff member and is not a transcriber in 'User Definition' (User B).
  • "User A" and "User B" have the 'My To Do's' widget on their HomeView.
  • Document routing is enabled for 'Progress Notes (Group and Individual)' and 'Allow Transcriber' is set to "Yes".
  • A client must be enrolled in an existing episode (Client A).
  • Must be logged in as "User A".
  • Please note: this scenario is for Avatar NX systems.
Steps
  1. Access the 'Progress Notes (Group and Individual)' form.
  2. Select "Client A" in the 'Select Client' 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' field.
  6. Select "Final" in the 'Draft/Final' field.
  7. Click [File Note].
  8. Validate a "Select Author" dialog is displayed.
  9. Select the staff member associated to "User B" in the 'Select Author' field.
  10. Click [Submit] and verify successful filing.
  11. Log out.
  12. Log in as "User B".
  13. Navigate to the 'My To Do's' widget.
  14. Validate there is a To Do for "Client A".
  15. Click [Transcription Review].
  16. Validate the progress note has electronic signatures for the Transcriber (User A) & Author (User B).
  17. Click [Progress Notes (Group and Individual)].
  18. Validate an 'Unsaved Changes' dialog stating: "You have unsaved changes would you like to continue?"
  19. Click [OK].
  20. Validate the progress note for "Client A" opens as a Draft.
  21. Select "Final" in the 'Draft/Final' field.
  22. Click [File Note].
  23. Validate a 'Confirm Document' dialog displaying the progress note for "Client A" and click [Accept].
  24. Enter the password associated with the logged in user and click [Verify].
  25. Validate a 'Progress Notes' dialog stating: "Note Filed." and click [OK].
  26. Validate the to do for "Client A" is no longer present in the 'My To Do's' widget.
  27. Close the To Do's.
Scenario 6: 'My To Do's' widget - Approving Documents
Specific Setup:
  • A user is a staff member and has the 'My To Do's' widget on their myDay view (User A).
  • Document routing is enabled for the 'Progress Notes (Group and Individual)' form.
  • A client must be enrolled in an existing episode (Client A).
  • Log in as "User A".
Steps
  1. Access the 'Progress Notes (Group and Individual)' form.
  2. Select "Client A" in the 'Select Client' 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' field.
  6. Select "Final" in the 'Draft/Final' field.
  7. Click [Submit Note].
  8. Validate that the 'Confirm Document' dialog is displayed with the progress note data, including an electronic signature at the bottom for the current user/staff member as the Author.
  9. Click [Accept and Route].
  10. Validate the 'Route Document To' dialog is displayed.
  11. Select the "User A" as the 'Approver'.
  12. Click [Submit].
  13. Validate a 'Progress Notes' dialog is displayed stating: "Note Filed."
  14. Click [OK].
  15. Navigate to the 'My To Do's' widget.
  16. Validate there is a To-Do's for the 'Progress Notes (Group and Individual)' form for "Client A".
  17. Click [Review All].
  18. Validate the 'Documents to Review' opens with all the documents in the left-hand side.
  19. Select the row for "Client A" and click the [Review].
  20. Validate the document is displayed with the expected data and click [Accept].
  21. Click [Cancel].
  22. Validate an 'Unsaved Changes' dialog stating: "You have unsaved changes would you like to continue?" and click [OK].
  23. Click [Review] and validate the document is displayed with the expected data.
  24. Click [Accept] and [Sign].
  25. Enter the password for "User A" in the 'Verify Password' dialog and click [Verify].
  26. Validate the To-Do is no longer displayed.
  27. Access the 'Clinical Document Viewer' form.
  28. Select "Client" in the 'Select All or Individual Client' field.
  29. Select "Client A" in the 'Select Client' field.
  30. Click [Process].
  31. Validate the document for "Client A" displays in the document list.
  32. Click to view the document.
  33. Validate that the document displays the expected data.
  34. Close the form.
Topics
• Progress Notes (Group And Individual) • Document Routing • NX • My To Do's • Treatment Plan • To-Do's