Skip to main content

Avatar CWS 2024 Monthly Release 2024.01.00 Acceptance Tests

  1. Last updated
  2. Save as PDF
Update 3 Summary | Details
Treatment Plan Web Service - Problem of "Other"
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Treatment Plan
  • Create New Treatment Plan
Scenario 1: Treatment Plan Web Service - Add Treatment Plan
Specific Setup:
  • A client is enrolled in an existing episode (Client A).
  • The 'SS Treatment Plan Client Scrolling Free Text 1' field is added to the 'Treatment Plan' form via 'Site Specific Section Modeling'. (Field #52021)
  • Create a non episodic Treatment Plan using the "Create New Treatment Plan" form.
Steps
  1. Access SoapUI for the 'TreatmentPlan' - 'AddTreatmentPlan' web service.
  2. Enter the system code that will be used to log into Avatar in the 'SystemCode' field.
  3. Enter the user name that will be used to log into Avatar in the 'UserName' field.
  4. Enter the password that will be used to log into Avatar in the 'Password' field.
  5. Enter the desired date in the 'PlanDate' field.
  6. Enter the desired value in the 'PlanName' field.
  7. Enter the desired value in the 'PlanType' field.
  8. Enter the desired value in the 'TreatmentPlanStatus' field.
  9. Enter a valid problem code in the 'SNOMEDCode' field.
  10. Enter the corresponding problem description in the 'SNOMEDDesc' field.
  11. Enter the desired value in the 'ProblemCodeStatus' field.
  12. Enter the desired date in the 'DateOfOnset' field.
  13. Enter the desired staff ID in the 'StaffResponsible' field.
  14. Enter the desired date in the 'DateOpened' field.
  15. Enter the desired value in the 'Problem' field.
  16. Enter the desired value in the 'Status' field.
  17. Enter the desired value in the 'CurrentStatus' field.
  18. Enter "52021" in the 'SSFreeTextScrolling' - 'FieldNumber' field.
  19. Enter a value containing more than 50 characters in the 'SSFreeTextScrolling' - 'FieldValue' field.
  20. Populate any other desired fields.
  21. Enter "Client A" in the 'ClientID' field.
  22. Enter "1" in the 'EpisodeNumber' field.
  23. Enter "CWS60000" in the 'OptionID' field.
  24. Click [Run].
  25. Validate that the 'Confirmation' field contains the unique ID for the treatment plan filed.
  26. Validate the 'Message' field contains: "Treatment Plan web service has been filed successfully".
  27. Select "Client A" and access the 'Treatment Plan' form.
  28. Select the record filed in the previous steps and click [Edit].
  29. Validate all data filed in the previous steps is displayed.
  30. Validate the 'SS Treatment Plan Client Scrolling Free Text 1' field contains the value filed in the previous steps.
  31. Close the form.
  32. Access SoapUI for the 'TreatmentPlan' - 'AddTreatmentPlan' web service.
  33. Enter the system code that will be used to log into Avatar in the 'SystemCode' field.
  34. Enter the user name that will be used to log into Avatar in the 'UserName' field.
  35. Enter the password that will be used to log into Avatar in the 'Password' field.
  36. Enter the desired date in the 'PlanDate' field.
  37. Enter the desired value in the 'PlanName' field.
  38. Enter the desired value in the 'PlanType' field.
  39. Enter the desired value in the 'TreatmentPlanStatus' field.
  40. Enter a valid problem code in the 'SNOMEDCode' field.
  41. Enter the corresponding problem description in the 'SNOMEDDesc' field.
  42. Enter the desired value in the 'ProblemCodeStatus' field.
  43. Enter the desired date in the 'DateOfOnset' field.
  44. Enter the desired staff ID in the 'StaffResponsible' field.
  45. Enter the desired date in the 'DateOpened' field.
  46. Enter the desired value in the 'Problem' field.
  47. Enter the desired value in the 'Status' field.
  48. Enter the desired value in the 'CurrentStatus' field.
  49. Enter "52021" in the 'SSFreeTextScrolling' - 'FieldNumber' field.
  50. Enter a value containing more than 50 characters in the 'SSFreeTextScrolling' - 'FieldValue' field.
  51. Populate any other desired fields.
  52. Enter "Client A" in the 'ClientID' field.
  53. Enter "0" in the 'EpisodeNumber' field.
  54. Enter "CWS60008" in the 'OptionID' field.
  55. Click [Run].
  56. Validate that the 'Confirmation' field contains the unique ID for the treatment plan filed.
  57. Validate the 'Message' field contains: "Treatment Plan web service has been filed successfully".
  58. Select "Client A" and access the 'Treatment Plan Number 8' form.
  59. Select the record filed in the previous steps and click [Edit].
  60. Validate all data filed in the previous steps is displayed.
  61. Validate the 'SS Treatment Plan Client Scrolling Free Text 1' field contains the value filed in the previous steps.
  62. Close the form.
Scenario 2: Treatment Plan Web Service - Edit Treatment Plan
Specific Setup:
  • A client is enrolled in an existing episode and has a 'Treatment Plan' on file (Client A).
  • The 'SS Treatment Plan Client Scrolling Free Text 1' field is added to the 'Treatment Plan' form via 'Site Specific Section Modeling'. (Field #52021)
  • Episodic and Non Episodic Treatment Plans must be on file for (Client A)
Steps
  1. Access SoapUI for the 'TreatmentPlan' - 'EditTreatmentPlan' web service.
  2. Enter the system code that will be used to log into Avatar in the 'SystemCode' field.
  3. Enter the user name that will be used to log into Avatar in the 'UserName' field.
  4. Enter the password that will be used to log into Avatar in the 'Password' field.
  5. Enter the original date on file in the 'PlanDate' field.
  6. Enter the desired value in the 'PlanName' field.
  7. Enter the desired value in the 'PlanType' field.
  8. Enter the desired value in the 'TreatmentPlanStatus' field.
  9. Enter a valid problem code in the 'SNOMEDCode' field.
  10. Enter the corresponding problem description in the 'SNOMEDDesc' field.
  11. Enter the desired value in the 'ProblemCodeStatus' field.
  12. Enter the desired date in the 'DateOfOnset' field.
  13. Enter the desired staff ID in the 'StaffResponsible' field.
  14. Enter the desired date in the 'DateOpened' field.
  15. Enter the desired value in the 'Problem' field.
  16. Enter the desired value in the 'Status' field.
  17. Enter the desired value in the 'CurrentStatus' field.
  18. Enter "52021" in the 'SSFreeTextScrolling' - 'FieldNumber' field.
  19. Enter a value containing more than 50 characters in the 'SSFreeTextScrolling' - 'FieldValue' field.
  20. Populate any other desired fields.
  21. Enter "Client A" in the 'ClientID' field.
  22. Enter "1" in the 'EpisodeNumber' field.
  23. Enter the unique ID for the existing 'Treatment Plan' record in the 'TPUniqueID' field.
  24. Click [Run].
  25. Validate that the 'Confirmation' field contains the unique ID for the treatment plan filed.
  26. Validate the 'Message' field contains: "Treatment Plan web service has been filed successfully".
  27. Select "Client A" and access the 'Treatment Plan' form.
  28. Select the record filed in the previous steps and click [Edit].
  29. Validate all data filed in the previous steps is displayed.
  30. Validate the 'SS Treatment Plan Client Scrolling Free Text 1' field contains the value filed in the previous steps.
  31. Close the form.
Treatment Plan Web Service - Multiple Problems
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Treatment Plan
  • Create New Treatment Plan
  • SOAPUI - Delete Treatment Plan
  • SoapUI - Get Treatment Plan
Scenario 1: Treatment Plan Web Service - Add Treatment Plan
Specific Setup:
  • A client is enrolled in an existing episode (Client A).
  • The 'SS Treatment Plan Client Scrolling Free Text 1' field is added to the 'Treatment Plan' form via 'Site Specific Section Modeling'. (Field #52021)
  • Create a non episodic Treatment Plan using the "Create New Treatment Plan" form.
Steps
  1. Access SoapUI for the 'TreatmentPlan' - 'AddTreatmentPlan' web service.
  2. Enter the system code that will be used to log into Avatar in the 'SystemCode' field.
  3. Enter the user name that will be used to log into Avatar in the 'UserName' field.
  4. Enter the password that will be used to log into Avatar in the 'Password' field.
  5. Enter the desired date in the 'PlanDate' field.
  6. Enter the desired value in the 'PlanName' field.
  7. Enter the desired value in the 'PlanType' field.
  8. Enter the desired value in the 'TreatmentPlanStatus' field.
  9. Enter a valid problem code in the 'SNOMEDCode' field.
  10. Enter the corresponding problem description in the 'SNOMEDDesc' field.
  11. Enter the desired value in the 'ProblemCodeStatus' field.
  12. Enter the desired date in the 'DateOfOnset' field.
  13. Enter the desired staff ID in the 'StaffResponsible' field.
  14. Enter the desired date in the 'DateOpened' field.
  15. Enter the desired value in the 'Problem' field.
  16. Enter the desired value in the 'Status' field.
  17. Enter the desired value in the 'CurrentStatus' field.
  18. Enter "52021" in the 'SSFreeTextScrolling' - 'FieldNumber' field.
  19. Enter a value containing more than 50 characters in the 'SSFreeTextScrolling' - 'FieldValue' field.
  20. Populate any other desired fields.
  21. Enter "Client A" in the 'ClientID' field.
  22. Enter "1" in the 'EpisodeNumber' field.
  23. Enter "CWS60000" in the 'OptionID' field.
  24. Click [Run].
  25. Validate that the 'Confirmation' field contains the unique ID for the treatment plan filed.
  26. Validate the 'Message' field contains: "Treatment Plan web service has been filed successfully".
  27. Select "Client A" and access the 'Treatment Plan' form.
  28. Select the record filed in the previous steps and click [Edit].
  29. Validate all data filed in the previous steps is displayed.
  30. Validate the 'SS Treatment Plan Client Scrolling Free Text 1' field contains the value filed in the previous steps.
  31. Close the form.
  32. Access SoapUI for the 'TreatmentPlan' - 'AddTreatmentPlan' web service.
  33. Enter the system code that will be used to log into Avatar in the 'SystemCode' field.
  34. Enter the user name that will be used to log into Avatar in the 'UserName' field.
  35. Enter the password that will be used to log into Avatar in the 'Password' field.
  36. Enter the desired date in the 'PlanDate' field.
  37. Enter the desired value in the 'PlanName' field.
  38. Enter the desired value in the 'PlanType' field.
  39. Enter the desired value in the 'TreatmentPlanStatus' field.
  40. Enter a valid problem code in the 'SNOMEDCode' field.
  41. Enter the corresponding problem description in the 'SNOMEDDesc' field.
  42. Enter the desired value in the 'ProblemCodeStatus' field.
  43. Enter the desired date in the 'DateOfOnset' field.
  44. Enter the desired staff ID in the 'StaffResponsible' field.
  45. Enter the desired date in the 'DateOpened' field.
  46. Enter the desired value in the 'Problem' field.
  47. Enter the desired value in the 'Status' field.
  48. Enter the desired value in the 'CurrentStatus' field.
  49. Enter "52021" in the 'SSFreeTextScrolling' - 'FieldNumber' field.
  50. Enter a value containing more than 50 characters in the 'SSFreeTextScrolling' - 'FieldValue' field.
  51. Populate any other desired fields.
  52. Enter "Client A" in the 'ClientID' field.
  53. Enter "0" in the 'EpisodeNumber' field.
  54. Enter "CWS60008" in the 'OptionID' field.
  55. Click [Run].
  56. Validate that the 'Confirmation' field contains the unique ID for the treatment plan filed.
  57. Validate the 'Message' field contains: "Treatment Plan web service has been filed successfully".
  58. Select "Client A" and access the 'Treatment Plan Number 8' form.
  59. Select the record filed in the previous steps and click [Edit].
  60. Validate all data filed in the previous steps is displayed.
  61. Validate the 'SS Treatment Plan Client Scrolling Free Text 1' field contains the value filed in the previous steps.
  62. Close the form.
Scenario 2: Treatment Plan Web Service - Edit Treatment Plan
Specific Setup:
  • A client is enrolled in an existing episode and has a 'Treatment Plan' on file (Client A).
  • The 'SS Treatment Plan Client Scrolling Free Text 1' field is added to the 'Treatment Plan' form via 'Site Specific Section Modeling'. (Field #52021)
  • Episodic and Non Episodic Treatment Plans must be on file for (Client A)
Steps
  1. Access SoapUI for the 'TreatmentPlan' - 'EditTreatmentPlan' web service.
  2. Enter the system code that will be used to log into Avatar in the 'SystemCode' field.
  3. Enter the user name that will be used to log into Avatar in the 'UserName' field.
  4. Enter the password that will be used to log into Avatar in the 'Password' field.
  5. Enter the original date on file in the 'PlanDate' field.
  6. Enter the desired value in the 'PlanName' field.
  7. Enter the desired value in the 'PlanType' field.
  8. Enter the desired value in the 'TreatmentPlanStatus' field.
  9. Enter a valid problem code in the 'SNOMEDCode' field.
  10. Enter the corresponding problem description in the 'SNOMEDDesc' field.
  11. Enter the desired value in the 'ProblemCodeStatus' field.
  12. Enter the desired date in the 'DateOfOnset' field.
  13. Enter the desired staff ID in the 'StaffResponsible' field.
  14. Enter the desired date in the 'DateOpened' field.
  15. Enter the desired value in the 'Problem' field.
  16. Enter the desired value in the 'Status' field.
  17. Enter the desired value in the 'CurrentStatus' field.
  18. Enter "52021" in the 'SSFreeTextScrolling' - 'FieldNumber' field.
  19. Enter a value containing more than 50 characters in the 'SSFreeTextScrolling' - 'FieldValue' field.
  20. Populate any other desired fields.
  21. Enter "Client A" in the 'ClientID' field.
  22. Enter "1" in the 'EpisodeNumber' field.
  23. Enter the unique ID for the existing 'Treatment Plan' record in the 'TPUniqueID' field.
  24. Click [Run].
  25. Validate that the 'Confirmation' field contains the unique ID for the treatment plan filed.
  26. Validate the 'Message' field contains: "Treatment Plan web service has been filed successfully".
  27. Select "Client A" and access the 'Treatment Plan' form.
  28. Select the record filed in the previous steps and click [Edit].
  29. Validate all data filed in the previous steps is displayed.
  30. Validate the 'SS Treatment Plan Client Scrolling Free Text 1' field contains the value filed in the previous steps.
  31. Close the form.
Scenario 3: Treatment Plan Web Service - Delete
Specific Setup:
  • A treatment plan is filed for any test client.
  • The Treatment Plan Unique ID is recorded (will be used in the web service to delete the record).
  • Using "Create New Treatment Plan" to generate a non episodic treatment plan form.
  • A non episodic treatment plan is filed for any test client.
Steps
  1. Using SOAPUI or other Web Services tool, delete an episodic Treatment Plan record for the test client.
  2. Open 'Treatment Plan' for the test client.
  3. Verify the record which was deleted is no longer displayed for selection on the 'Treatment Plan Pre-Display'.
  4. Using SOAPUI or other Web Services tool, delete a non episodic Treatment Plan record for the test client.
  5. Open a non episodic Treatment Plan for the test client.
  6. Verify the record which was deleted is no longer displayed for selection on the 'Treatment Plan Pre-Display'.
Scenario 4: Treatment Plan Web Service- Get Treatment Plan
Specific Setup:
  • A client is enrolled in an existing episode and has a 'Treatment Plan' on file (Client A).
  • The following signature fields must be added to the 'Treatment Plan' form via 'Site Specific Section Modeling':
  • SS Treatment Plan Client Sign 1 (Field #52143 - This can be found in the 'Form and Table Documentation' form).
  • SS Treatment Plan Part Sign 1 (Field #57020 - This can be found in the 'Form and Table Documentation' form).
Steps
  1. Access SoapUI for the 'TreatmentPlan' - 'GetTreatmentPlan' web service.
  2. Enter the system code that will be used to log into Avatar in the 'SystemCode' field.
  3. Enter the user name that will be used to log into Avatar in the 'UserName' field.
  4. Enter the password that will be used to log into Avatar in the 'Password' field.
  5. Enter "Client A" in the 'ClientID' field.
  6. Enter the unique ID for the existing 'Treatment Plan' record in the 'TPUniqueID' field.
  7. Click [Run].
  8. Validate the 'GetTreatmentPlanResponse' field contains the 'Treatment Plan' data on file.
  9. Validate the signatures on file are returned in a base64 encoded format. Please note: you can use any online decoder to confirm the base64 value matches the signature on file.
Treatment Plan Web Service - Non Episodic Treatment Plan
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Treatment Plan
  • Create New Treatment Plan
  • SOAPUI - Delete Treatment Plan
  • SoapUI - Get Treatment Plan
Scenario 1: Treatment Plan Web Service - Add Treatment Plan
Specific Setup:
  • A client is enrolled in an existing episode (Client A).
  • The 'SS Treatment Plan Client Scrolling Free Text 1' field is added to the 'Treatment Plan' form via 'Site Specific Section Modeling'. (Field #52021)
  • Create a non episodic Treatment Plan using the "Create New Treatment Plan" form.
Steps
  1. Access SoapUI for the 'TreatmentPlan' - 'AddTreatmentPlan' web service.
  2. Enter the system code that will be used to log into Avatar in the 'SystemCode' field.
  3. Enter the user name that will be used to log into Avatar in the 'UserName' field.
  4. Enter the password that will be used to log into Avatar in the 'Password' field.
  5. Enter the desired date in the 'PlanDate' field.
  6. Enter the desired value in the 'PlanName' field.
  7. Enter the desired value in the 'PlanType' field.
  8. Enter the desired value in the 'TreatmentPlanStatus' field.
  9. Enter a valid problem code in the 'SNOMEDCode' field.
  10. Enter the corresponding problem description in the 'SNOMEDDesc' field.
  11. Enter the desired value in the 'ProblemCodeStatus' field.
  12. Enter the desired date in the 'DateOfOnset' field.
  13. Enter the desired staff ID in the 'StaffResponsible' field.
  14. Enter the desired date in the 'DateOpened' field.
  15. Enter the desired value in the 'Problem' field.
  16. Enter the desired value in the 'Status' field.
  17. Enter the desired value in the 'CurrentStatus' field.
  18. Enter "52021" in the 'SSFreeTextScrolling' - 'FieldNumber' field.
  19. Enter a value containing more than 50 characters in the 'SSFreeTextScrolling' - 'FieldValue' field.
  20. Populate any other desired fields.
  21. Enter "Client A" in the 'ClientID' field.
  22. Enter "1" in the 'EpisodeNumber' field.
  23. Enter "CWS60000" in the 'OptionID' field.
  24. Click [Run].
  25. Validate that the 'Confirmation' field contains the unique ID for the treatment plan filed.
  26. Validate the 'Message' field contains: "Treatment Plan web service has been filed successfully".
  27. Select "Client A" and access the 'Treatment Plan' form.
  28. Select the record filed in the previous steps and click [Edit].
  29. Validate all data filed in the previous steps is displayed.
  30. Validate the 'SS Treatment Plan Client Scrolling Free Text 1' field contains the value filed in the previous steps.
  31. Close the form.
  32. Access SoapUI for the 'TreatmentPlan' - 'AddTreatmentPlan' web service.
  33. Enter the system code that will be used to log into Avatar in the 'SystemCode' field.
  34. Enter the user name that will be used to log into Avatar in the 'UserName' field.
  35. Enter the password that will be used to log into Avatar in the 'Password' field.
  36. Enter the desired date in the 'PlanDate' field.
  37. Enter the desired value in the 'PlanName' field.
  38. Enter the desired value in the 'PlanType' field.
  39. Enter the desired value in the 'TreatmentPlanStatus' field.
  40. Enter a valid problem code in the 'SNOMEDCode' field.
  41. Enter the corresponding problem description in the 'SNOMEDDesc' field.
  42. Enter the desired value in the 'ProblemCodeStatus' field.
  43. Enter the desired date in the 'DateOfOnset' field.
  44. Enter the desired staff ID in the 'StaffResponsible' field.
  45. Enter the desired date in the 'DateOpened' field.
  46. Enter the desired value in the 'Problem' field.
  47. Enter the desired value in the 'Status' field.
  48. Enter the desired value in the 'CurrentStatus' field.
  49. Enter "52021" in the 'SSFreeTextScrolling' - 'FieldNumber' field.
  50. Enter a value containing more than 50 characters in the 'SSFreeTextScrolling' - 'FieldValue' field.
  51. Populate any other desired fields.
  52. Enter "Client A" in the 'ClientID' field.
  53. Enter "0" in the 'EpisodeNumber' field.
  54. Enter "CWS60008" in the 'OptionID' field.
  55. Click [Run].
  56. Validate that the 'Confirmation' field contains the unique ID for the treatment plan filed.
  57. Validate the 'Message' field contains: "Treatment Plan web service has been filed successfully".
  58. Select "Client A" and access the 'Treatment Plan Number 8' form.
  59. Select the record filed in the previous steps and click [Edit].
  60. Validate all data filed in the previous steps is displayed.
  61. Validate the 'SS Treatment Plan Client Scrolling Free Text 1' field contains the value filed in the previous steps.
  62. Close the form.
Scenario 2: Treatment Plan Web Service - Edit Treatment Plan
Specific Setup:
  • A client is enrolled in an existing episode and has a 'Treatment Plan' on file (Client A).
  • The 'SS Treatment Plan Client Scrolling Free Text 1' field is added to the 'Treatment Plan' form via 'Site Specific Section Modeling'. (Field #52021)
  • Episodic and Non Episodic Treatment Plans must be on file for (Client A)
Steps
  1. Access SoapUI for the 'TreatmentPlan' - 'EditTreatmentPlan' web service.
  2. Enter the system code that will be used to log into Avatar in the 'SystemCode' field.
  3. Enter the user name that will be used to log into Avatar in the 'UserName' field.
  4. Enter the password that will be used to log into Avatar in the 'Password' field.
  5. Enter the original date on file in the 'PlanDate' field.
  6. Enter the desired value in the 'PlanName' field.
  7. Enter the desired value in the 'PlanType' field.
  8. Enter the desired value in the 'TreatmentPlanStatus' field.
  9. Enter a valid problem code in the 'SNOMEDCode' field.
  10. Enter the corresponding problem description in the 'SNOMEDDesc' field.
  11. Enter the desired value in the 'ProblemCodeStatus' field.
  12. Enter the desired date in the 'DateOfOnset' field.
  13. Enter the desired staff ID in the 'StaffResponsible' field.
  14. Enter the desired date in the 'DateOpened' field.
  15. Enter the desired value in the 'Problem' field.
  16. Enter the desired value in the 'Status' field.
  17. Enter the desired value in the 'CurrentStatus' field.
  18. Enter "52021" in the 'SSFreeTextScrolling' - 'FieldNumber' field.
  19. Enter a value containing more than 50 characters in the 'SSFreeTextScrolling' - 'FieldValue' field.
  20. Populate any other desired fields.
  21. Enter "Client A" in the 'ClientID' field.
  22. Enter "1" in the 'EpisodeNumber' field.
  23. Enter the unique ID for the existing 'Treatment Plan' record in the 'TPUniqueID' field.
  24. Click [Run].
  25. Validate that the 'Confirmation' field contains the unique ID for the treatment plan filed.
  26. Validate the 'Message' field contains: "Treatment Plan web service has been filed successfully".
  27. Select "Client A" and access the 'Treatment Plan' form.
  28. Select the record filed in the previous steps and click [Edit].
  29. Validate all data filed in the previous steps is displayed.
  30. Validate the 'SS Treatment Plan Client Scrolling Free Text 1' field contains the value filed in the previous steps.
  31. Close the form.
Scenario 3: Treatment Plan Web Service - Delete
Specific Setup:
  • A treatment plan is filed for any test client.
  • The Treatment Plan Unique ID is recorded (will be used in the web service to delete the record).
  • Using "Create New Treatment Plan" to generate a non episodic treatment plan form.
  • A non episodic treatment plan is filed for any test client.
Steps
  1. Using SOAPUI or other Web Services tool, delete an episodic Treatment Plan record for the test client.
  2. Open 'Treatment Plan' for the test client.
  3. Verify the record which was deleted is no longer displayed for selection on the 'Treatment Plan Pre-Display'.
  4. Using SOAPUI or other Web Services tool, delete a non episodic Treatment Plan record for the test client.
  5. Open a non episodic Treatment Plan for the test client.
  6. Verify the record which was deleted is no longer displayed for selection on the 'Treatment Plan Pre-Display'.
Scenario 4: Treatment Plan Web Service- Get Treatment Plan
Specific Setup:
  • A client is enrolled in an existing episode and has a 'Treatment Plan' on file (Client A).
  • The following signature fields must be added to the 'Treatment Plan' form via 'Site Specific Section Modeling':
  • SS Treatment Plan Client Sign 1 (Field #52143 - This can be found in the 'Form and Table Documentation' form).
  • SS Treatment Plan Part Sign 1 (Field #57020 - This can be found in the 'Form and Table Documentation' form).
Steps
  1. Access SoapUI for the 'TreatmentPlan' - 'GetTreatmentPlan' web service.
  2. Enter the system code that will be used to log into Avatar in the 'SystemCode' field.
  3. Enter the user name that will be used to log into Avatar in the 'UserName' field.
  4. Enter the password that will be used to log into Avatar in the 'Password' field.
  5. Enter "Client A" in the 'ClientID' field.
  6. Enter the unique ID for the existing 'Treatment Plan' record in the 'TPUniqueID' field.
  7. Click [Run].
  8. Validate the 'GetTreatmentPlanResponse' field contains the 'Treatment Plan' data on file.
  9. Validate the signatures on file are returned in a base64 encoded format. Please note: you can use any online decoder to confirm the base64 value matches the signature on file.
Topics
• Treatment Plan • Web Services
Update 9 Summary | Details
Progress Notes - The 'Limit Edits/Deletions To Original Author' registry setting
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Registry Settings (CWS)
  • Ambulatory Progress Notes
  • Progress Notes (Group and Individual)
Scenario 1: Progress Notes (Group and Individual) - Validate the 'Limit Edits/Deletions To Original Author' registry setting
Specific Setup:
  • Two users are defined with "Level 2" selected for 'User Security Level' (User A & User B).
  • "User A" must have had their user ID changed in the 'Change User ID' form.
  • The 'Limit Edits/Deletion to Original Author' registry setting must be set to "Y" for the 'Progress Notes (Group and Individual)' form.
  • The 'Edit/Delete Security Level Override' registry setting must be set to "3" for the 'Progress Notes (Group and Individual)' form.
  • A client must be enrolled in an existing episode (Client A).
Steps
  1. Login as "User A".
  2. Access the 'Progress Notes (Group and Individual)' form.
  3. Select "Client A" in the 'Select Client' field.
  4. Select the desired value in the 'Select Episode' field.
  5. Populate all required and desired fields.
  6. Select "Draft" in the 'Draft/Final' field.
  7. File the note.
  8. Log out.
  9. Log in as "User B".
  10. Access the 'Progress Notes (Group and Individual)' form.
  11. Select "Client A" in the 'Select Client' field.
  12. Validate the 'Select Draft Note To Edit' field does not contain the draft note filed by "User A".
  13. Close the form.
Scenario 2: Ambulatory Progress Notes - Validate the 'Limit Edits/Deletions To Original Author' registry setting
Specific Setup:
  • Two users are defined with "Level 2" selected for 'User Security Level' (User A & User B).
  • "User A" must have had their user ID changed in the 'Change User ID' form.
  • The 'Limit Edits/Deletion to Original Author' registry setting must be set to "Y" for the 'Ambulatory Progress Notes' form.
  • The 'Edit/Delete Security Level Override' registry setting must be set to "3" for the 'Ambulatory Progress Notes' form.
  • A client must be enrolled in an existing outpatient episode (Client A).
Steps
  1. Login as "User A".
  2. Select "Client A" and access the 'Ambulatory Progress Notes' form.
  3. Populate all required and desired fields.
  4. Select "Draft" in the 'Draft/Final' field.
  5. Submit the note.
  6. Log out.
  7. Log in as "User B".
  8. Select "Client A" and access the 'Ambulatory Progress Notes' form.
  9. Validate the Pre-Display does not contain the draft note filed by "User A".
  10. Close the form.
Scenario 3: Inpatient Progress Notes - Validate the 'Limit Edits/Deletions To Original Author' registry setting
Specific Setup:
  • Two users are defined with "Level 2" selected for 'User Security Level' (User A & User B).
  • "User A" must have had their user ID changed in the 'Change User ID' form.
  • The 'Limit Edits/Deletion to Original Author' registry setting must be set to "Y" for the 'Ambulatory Progress Notes' form.
  • The 'Edit/Delete Security Level Override' registry setting must be set to "3" for the 'Ambulatory Progress Notes' form.
  • A client must be enrolled in an existing inpatient episode (Client A).
Steps
  1. Login as "User A".
  2. Select "Client A" and access the 'Inpatient Progress Notes' form.
  3. Populate all required and desired fields.
  4. Select "Draft" in the 'Draft/Final' field.
  5. Submit the note.
  6. Log out.
  7. Log in as "User B".
  8. Select "Client A" and access the 'Inpatient Progress Notes' form.
  9. Validate the Pre-Display does not contain the draft note filed by "User A".
  10. Close the form.
'Columbia Suicide Risk Assessment' and 'Columbia SRA Since Last Visit' forms
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Columbia Suicide Risk Assessment
  • Columbia SRA Since Last Visit
  • Clinical Pathway Enrollment
Scenario 1: Columbia Suicide Risk Assessment - Field Validations
Specific Setup:
  • A client must be admitted to an active episode (Client A).
  • One or more clinical pathways defined in the 'Clinical Pathway Definition' form.
Steps
  1. Select "Client A" and access the 'Columbia Suicide Risk Assessment' form.
  2. Enter the current date in the 'Assessment Date' field.
  3. Populate all required and desired fields.
  4. Select "Draft" in the 'Status' field.
  5. Submit the form.
  6. Select "Client A" and access the 'Columbia Suicide Risk Assessment' form.
  7. Select the record filed in the previous steps and click [Edit].
  8. Validate the 'Assessment Date' field is disabled and contains the current date.
  9. Validate all previously filed data is displayed.
  10. Select "Final" in the 'Status' field.
  11. Click [OK] on the 'Once set to 'Final', the data cannot be edited in the future' prompt.
  12. Validate the 'Assessment Date' field remains disabled.
  13. Select "Yes" in the 'Enroll in Clinical Pathway' field.
  14. Select desired pathway from the 'Pathway Name' field.
  15. Submit the form.
Scenario 2: Columbia SRA Since Last Visit
Specific Setup:
  • A client must be enrolled in an existing episode (Client A).
  • One or more clinical pathways defined in the 'Clinical Pathway Definition' form.
Steps
  1. Select "Client A" and access the 'Columbia SRA Since Last Visit' form.
  2. Enter the current date in the 'Assessment Date' field.
  3. Populate all required and desired fields.
  4. Select "Draft" in the 'Status' field.
  5. Submit the form.
  6. Select "Client A" and access the 'Columbia SRA Since Last Visit' form.
  7. Select the record filed in the previous steps and click [Edit].
  8. Validate the 'Assessment Date' field is disabled and contains the current date.
  9. Validate all previously filed data is displayed.
  10. Select "Final" in the 'Status' field.
  11. Click [OK] on the 'Once set to 'Final', the data cannot be edited in the future' prompt.
  12. Validate the 'Assessment Date' field remains disabled.
  13. Select "Yes" in the 'Enroll in Clinical Pathway' field.
  14. Select desired pathway from the 'Pathway Name' field.
  15. Submit the form.
Topics
• User Definition • Registry Settings • Progress Notes • Clinical Pathway
Update 12 Summary | Details
Progress Notes - Progress Notes Web Service - Existing Appointments
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Progress Notes (Group and Individual)
Scenario 1: Creating Progress Note for an Existing Appointment in 'Progress Notes (Group and Individual)'
Specific Setup:
  • Service:
  • Service should be picked from existing or newly created and the Fee definitions should be defined for the service(s).
  • Client:
  • A client is enrolled in an existing episode and has multiple existing Appointments on file (Client A).
  • Registry Settings:
  • Set the "Enable Alternative Service Location Fields" Registry setting to "Y" for Progress Notes (Group and Individual)
  • Set the "Limit Existing Services to Current Login User" Registry Setting value as "0" for Progress Notes (Group and Individual).
  • Set the "Limit Existing Appointments to Current Login User" Registry Setting value as "0" for Progress Notes (Group and Individual).
Steps
  1. Access the 'Progress Notes (Group and Individual)' form.
  2. Select "Client A" in the 'Select Client' field.
  3. Select the desired episode in the 'Select Episode' field.
  4. Select "Existing Appointment" in the 'Progress Note For' field.
  5. Select any existing appointments of "Client A" in the 'Note Addresses Which Existing Service/Appointment' field.
  6. Populate all required and desired fields.
  7. Verify that the Facility Location fields are populated with the data entered in 'Edit Service Information'.
  8. Update at least one facility location field value.
  9. Select "Draft" in the 'Draft/Final' field.
  10. Click [File Note].
  11. Validate a message is displayed stating: Note Filed.
  12. Click [OK].
  13. Click [Yes] in the form return.
  14. Select the "Client A" in the 'Select Client' field.
  15. Select the note filed in the previous steps in the 'Draft Note To Edit' field.
  16. Validate all previously filed data is displayed.
  17. Select "Final" in the 'Draft/Final' field.
  18. Click [File Note].
  19. Click [Accept].
  20. Enter the Password and select [Verify].
  21. Select "Admitting Practitioner" in Add Approver.
  22. Select [Submit].
  23. Validate the acknowledgment 'Note Filed'.
  24. Click [No] and close the form.
Scenario 2: Validating 'AddProgressNotes' web service request for an existing Appointment
Specific Setup:
  • Access to SoapUI or any other web service.
  • Client with multiple existing Appointments (10 appointments) created in the 'Scheduling Calendar' form. 'Client A'.
Steps
  1. Access the SoapUI or any other tool to test the web service.
  2. Consume the WSDL for WEB.SVC.ProgressNotes.Client.Request.
  3. Enter data on the web service request for the "Existing Appointment".
  4. Set the "NotesField" item to any desired text value.
  5. Set the "NoteType" item to "Any desired Note type value". (one with or without a co-practitioner).
  6. On selecting the Note Type that has the co-practitioner, Set the desired value for 'User To Send Co-Sign To Do Item To'.
  7. Set the "DraftFinal" item to "D".
  8. Set the "ProgressNoteFor" item to "EI".
  9. Set the "ServiceProgram" item to "Any desired program value".
  10. Set the "ServiceDuration" item to "Any desired duration value".
  11. Set the "DateOfService" item to "Any desired date value".
  12. Leave all the "Facility Location" field values empty.
  13. Set the "ClientID" item to 'Client A'.
  14. Set the "EpisodeNumber" to the client episode for the service.
  15. Set the "NoteAddressesWhichExistingServiceAppointment" to any existing appointment's appointment ID. This can be obtained from the below table,
  16. "appt_data"
  17. Set the "Option" to "Any desired option value".
  18. Click [Send].
  19. Verify the Message response contains "Progress Notes web service has been filed successfully" with the "Unique ID" value.
  20. Access the 'Progress Notes (Group and Individual)' form.
  21. Select "Client A" in the 'Select Client' field.
  22. Validate that the note filed in the previous steps is shown in the 'Draft Note To Edit' field for selection.
  23. Select the note filed in the previous steps in the 'Draft Note To Edit' field.
  24. Verify that all the data filed as part of the note is populated in the respective fields.
  25. Click [Discard].
  26. Click [Yes].
Topics
• Progress Notes • Web Services
Update 14 Summary | Details
Progress Notes - Signatures and Treatment Plan Grid data
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Treatment Plan
  • Progress Notes (Group and Individual)
  • Site Specific Section Modeling (CWS)
  • Registry Settings (CWS)
Scenario 1: Progress Notes (Group and Individual) - Validate 'Treatment Plan' Grid and 'Signature' fields
Specific Setup:
  • Signature support must be enabled in the 'System Security Defaults' form.
  • The 'Progress Notes' widget is accessible on the HomeView.
  • The 'Enable Treatment Plan Grid' registry setting is set to "Y" for the 'Progress Notes (Group and Individual)' form.
  • The 'Progress Notes (Group and Individual)' form must have a signature field added via 'Site Specific Section Modeling' (Signature A).
  • A client must have a Treatment Plan filed with a problem, goal, objective, and intervention associated (Client A).
  • Must have a crystal report configured for document routing configured for "Signature A" and the 'Treatment Plan' grid for progress notes (Crystal Report A).
  • Crystal Report Document Routing must be configured for the 'Progress Notes (Group and Individual)' form using "Crystal Report 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'.
  6. Click [New Row] in the 'Treatment Plan Grid'.
  7. Select "Treatment Plan" in the 'Select T.P. Version' field.
  8. Click [View].
  9. Select the desired treatment plan item and click [Return].
  10. Enter the desired value in the 'T.P. Item Notes/Documentations' field.
  11. Click [Sign] for "Signature A" and enter the desired signature.
  12. Select "Final" in the 'Draft/Final' field.
  13. Click [File Note].
  14. Validate the 'Confirm Document' dialog is displayed with "Crystal Report A". Validate the signature and treatment plan grid data display as expected.
  15. Leave the form open.
  16. Access Crystal Reports or other SQL Reporting Tool.
  17. Create a report using the 'CWSTEMP.cw_patient_notes_tpnotes' SQL table.
  18. Validate a row is displayed for the treatment plan data entered for "Client A" in the previous steps.
  19. Please note: this is a temporary storage table. A process will run once daily that will clean up this data, which will become available in the SYSTEM.cw_patient_notes_tpnotes' SQL table after filing the note.
  20. Close the report.
  21. Create a report using the 'CWSTEMP.cw_tx_pn_sign_data' SQL table.
  22. Validate a row is displayed for the signature data entered for "Client A" in the previous steps.
  23. Please note: this is a temporary storage table. A process will run once daily that will clean up this data, which will become available in the SYSTEM.cw_tx_pn_sign_data' SQL table after filing the note.
  24. Close the report.
  25. Navigate back to the 'Progress Notes (Group and Individual)' form.
  26. Click [Accept].
  27. Enter the password associated to the logged in user.
  28. Close the form.
  29. Select "Client A" and access the 'Progress Notes' widget.
  30. Validate the progress note filed in the previous steps is displayed with the treatment plan and signature data.
  31. Access Crystal Reports or other SQL Reporting Tool.
  32. Create a report using the 'SYSTEM.cw_patient_notes_tpnotes' SQL table.
  33. Validate a row is displayed for the treatment plan data entered for "Client A" in the previous steps.
  34. Close the report.
  35. Create a report using the 'SYSTEM.cw_tx_pn_sign_data' SQL table.
  36. Validate a row is displayed for the signature data entered for "Client A" in the previous steps.
  37. Close the report.
Scenario 2: Ambulatory Progress Notes - Validate 'Treatment Plan' Grid and Signature fields
Specific Setup:
  • Signature support must be enabled in the 'System Security Defaults' form.
  • The 'Progress Notes' widget is accessible on the HomeView.
  • The 'Enable Treatment Plan Grid' registry setting is set to "Y" for the 'Ambulatory Progress Notes' form.
  • The 'Ambulatory Progress Notes' form must have a signature field added via 'Site Specific Section Modeling' (Signature A).
  • A client must be enrolled in an outpatient episode and have a Treatment Plan filed with a problem, goal, objective, and intervention associated (Client A).
  • Must have a crystal report configured for document routing configured for "Signature A" and the 'Treatment Plan' grid for 'Ambulatory Progress Notes' (Crystal Report A).
  • Crystal Report Document Routing must be configured for the 'Ambulatory Progress Notes' form using "Crystal Report A".
Steps
  1. Select "Client A" and access the 'Ambulatory Progress Notes' form.
  2. Select "Independent Note" in the 'Progress Note For' field.
  3. Select the desired value in the 'Note Type' field.
  4. Enter the desired value in the 'Notes Field'.
  5. Click [New Row] in the 'Treatment Plan Grid'.
  6. Select "Treatment Plan" in the 'Select T.P. Version' field.
  7. Click [View].
  8. Select the desired treatment plan item and click [Return].
  9. Enter the desired value in the 'T.P. Item Notes/Documentations' field.
  10. Click [Sign] for "Signature A" and enter the desired signature.
  11. Select "Final" in the 'Draft/Final' field.
  12. Click [Submit].
  13. Validate the 'Confirm Document' dialog is displayed with "Crystal Report A". Validate the signature and treatment plan grid data display as expected.
  14. Leave the form open.
  15. Access Crystal Reports or other SQL Reporting Tool.
  16. Create a report using the 'CWSTEMP.cw_patient_notes_tpnotes' SQL table.
  17. Validate a row is displayed for the treatment plan data entered for "Client A" in the previous steps.
  18. Please note: this is a temporary storage table. A process will run once daily that will clean up this data, which will become available in the SYSTEM.cw_patient_notes_tpnotes' SQL table after filing the note.
  19. Close the report.
  20. Create a report using the 'CWSTEMP.cw_tx_pn_sign_data' SQL table.
  21. Validate a row is displayed for the signature data entered for "Client A" in the previous steps.
  22. Please note: this is a temporary storage table. A process will run once daily that will clean up this data, which will become available in the SYSTEM.cw_tx_pn_sign_data' SQL table after filing the note.
  23. Close the report.
  24. Navigate back to the 'Ambulatory Progress Notes' form.
  25. Click [Accept].
  26. Enter the password associated to the logged in user.
  27. Close the form.
  28. Select "Client A" and access the 'Progress Notes' widget.
  29. Validate the progress note filed in the previous steps is displayed with the treatment plan and signature data.
  30. Access Crystal Reports or other SQL Reporting Tool.
  31. Create a report using the 'SYSTEM.cw_patient_notes_tpnotes' SQL table.
  32. Validate a row is displayed for the treatment plan data entered for "Client A" in the previous steps.
  33. Close the report.
  34. Create a report using the 'SYSTEM.cw_tx_pn_sign_data' SQL table.
  35. Validate a row is displayed for the signature data entered for "Client A" in the previous steps.
  36. Close the report.
Scenario 3: Inpatient Progress Notes - Validate 'Treatment Plan' Grid and 'Signature' fields
Specific Setup:
  • Signature support must be enabled in the 'System Security Defaults' form.
  • The 'Progress Notes' widget is accessible on the HomeView.
  • The 'Enable Treatment Plan Grid' registry setting is set to "Y" for the 'Inpatient Progress Notes' form.
  • The 'Inpatient Progress Notes' form must have a signature field added via 'Site Specific Section Modeling' (Signature A).
  • A client must be enrolled in an inpatient episode and have a Treatment Plan filed with a problem, goal, objective, and intervention associated (Client A).
  • Must have a crystal report configured for document routing configured for "Signature A" and the 'Treatment Plan' grid for Inpatient progress notes (Crystal Report A).
  • Crystal Report Document Routing must be configured for the 'Inpatient Progress Notes' form using "Crystal Report A".
Steps
  1. Select "Client A" and access the 'Inpatient Progress Notes' form.
  2. Select "Independent Note" in the 'Progress Note For' field.
  3. Select the desired value in the 'Note Type' field.
  4. Enter the desired value in the 'Notes Field'.
  5. Click [New Row] in the 'Treatment Plan Grid'.
  6. Select "Treatment Plan" in the 'Select T.P. Version' field.
  7. Click [View].
  8. Select the desired treatment plan item and click [Return].
  9. Enter the desired value in the 'T.P. Item Notes/Documentations' field.
  10. Click [Sign] for "Signature A" and enter the desired signature.
  11. Select "Final" in the 'Draft/Final' field.
  12. Click [File Note].
  13. Validate the 'Confirm Document' dialog is displayed with "Crystal Report A". Validate the signature and treatment plan grid data display as expected.
  14. Leave the form open.
  15. Access Crystal Reports or other SQL Reporting Tool.
  16. Create a report using the 'CWSTEMP.cw_patient_notes_tpnotes' SQL table.
  17. Validate a row is displayed for the treatment plan data entered for "Client A" in the previous steps.
  18. Please note: this is a temporary storage table. A process will run once daily that will clean up this data, which will become available in the SYSTEM.cw_patient_notes_tpnotes' SQL table after filing the note.
  19. Close the report.
  20. Create a report using the 'CWSTEMP.cw_tx_pn_sign_data' SQL table.
  21. Validate a row is displayed for the signature data entered for "Client A" in the previous steps.
  22. Please note: this is a temporary storage table. A process will run once daily that will clean up this data, which will become available in the SYSTEM.cw_tx_pn_sign_data' SQL table after filing the note.
  23. Close the report.
  24. Navigate back to the ' InpatientProgress Notes ' form.
  25. Click [Accept].
  26. Close the form.
  27. Select "Client A" and access the 'Progress Notes' widget.
  28. Validate the progress note filed in the previous steps is displayed with the treatment plan and signature data.
  29. Access Crystal Reports or other SQL Reporting Tool.
  30. Create a report using the 'SYSTEM.cw_patient_notes_tpnotes' SQL table.
  31. Validate a row is displayed for the treatment plan data entered for "Client A" in the previous steps.
  32. Close the report.
  33. Create a report using the 'SYSTEM.cw_tx_pn_sign_data' SQL table.
  34. Validate a row is displayed for the signature data entered for "Client A" in the previous steps.
  35. Close the report.
Topics
• Document Routing • Progress Notes • Query/Reporting
Update 18 Summary | Details
Attach Individual Notes to Existing Appointments/Services - Auto Append Document Image
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Registry Settings (CWS)
  • Attach Individual Notes To Existing Services/Appointments
Scenario 1: Registry Settings - Auto Append Document Image
Steps
  1. Open the "Registry Settings" form.
  2. Search for the setting "Avatar CWS->Progress Notes->Attach Individual Notes To Existing Services/Appointments->->->Auto Append Document Image".
  3. Set the Value to "Y".
  4. Submit to file the form.
  5. Open the "Attach Individual Notes to Existing Services/Appointments" form.
  6. Click "Select Note To Attach".
  7. Validate a column called "Document" exists on this form.
  8. Cancel processing and exit the form.
  9. Open the "Registry Settings" form.
  10. Search for the setting "Auto Append Document Image".
  11. Set the Value to "N".
  12. Submit to file the form.
  13. Open the "Attach Individual Notes to Existing Services/Appointments" form.
  14. Click "Select Note To Attach".
  15. Validate a column called "Document" no longer exists on this form.
  16. Cancel processing and exit the form.
Scenario 2: Attach Individual Notes to Existing Services/Appointments - Auto Append Document Image
Specific Setup:
  • Enable Registry Setting "Avatar CWS->Progress Notes->Attach Individual Notes To Existing Services/Appointments->->->Auto Append Document Image" by setting it to "Y".
  • Create using "Create New Progress Note" form or use an existing copy of the "Progress Notes (Group and Individual)" form.
  • Give Avatar users access to the newly created progress notes form.
  • Refresh menus.
  • Using "Document Routing Setup", enable document routing for the newly created progress notes form.
  • Select a test client with services on file or create services using "Client Charge Input" and appointments on file or create appointments using "Scheduling Calendar".
Steps
  1. Open the copy of "Progress Notes (Group and Individual)" form:
  2. Create an independent note and finalize it.
  3. Sign the document.
  4. Open the copy of "Progress Notes (Group and Individual)" form:
  5. Create an independent note and finalize it.
  6. Sign and route the document.
  7. Open the "Attach Individual Notes To Existing Services/Appointments" form:
  8. Select a note that has "Pending" in the "Document" column.
  9. Validate a message displays stating, "The selected note is associated with a document that is not "Final". The note cannot be attached to an existing service or appointment until the document is finalized.".
  10. Select a note that has "Final" in the "Document" column.
  11. Validate a message says "The selected note is associated with a finalized document. Continuing will append the document. Would you like to continue?".
  12. Select "Appointments" in the "Link Note To".
  13. Select the specific appointment in the "Appointments/Services" field.
  14. Click "Submit".
  15. Validate there is a page appended to the note that indicates what appointment/service the note is now attached to.
  16. Click "Sign".
  17. Provide the password for the document.
  18. Open the "Attach Individual Notes To Existing Services/Appointments" form:
  19. Select a note that has "Pending" in the "Document" column.
  20. Validate a message displays stating, "The selected note is associated with a document that is not "Final". The note cannot be attached to an existing service or appointment until the document is finalized.".
  21. Select a note that has "Final" in the "Document" column.
  22. Validate a message says "The selected note is associated with a finalized document. Continuing will append the document. Would you like to continue?".
  23. Select "Services" in the "Link Note To".
  24. Select the specific service in the "Appointments/Services" field.
  25. Click "Submit".
  26. Validate there is a page appended to the note that indicates what appointment/service the note is now attached to.
  27. Click "Sign".
  28. Provide the password for the document.
  29. Open the "Clinical Document Viewer".
  30. Open the documents filed as final and attached to an existing appointment/service.
  31. Validate the appended page is included as the last page of the document.
Topics
• Registry Settings • Progress Notes • Append Progress Notes
2023 Update 19 Summary | Details
Task Export/Import - Reason Code and Order Code
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Task Definitions
  • Task List Export/Import
  • Task Associations
  • Orders This Episode
Scenario 1: Task List Export/Import - Task Association - Reason and Order Code
Steps
  1. Access the 'Task Definition' form.
  2. Select "Add" from the 'Add/Edit Task Definition' field.
  3. Populate the 'New Task Code' field (Task A) and any other desired fields and click [Submit].
  4. Access the 'Task Associations' form.
  5. Set the 'Task Type' field to "Task Definition"
  6. Set the 'Task Group / Definition' field to "Task A".
  7. File 'Task Associations' for a 'Reason Code' as well as an 'Order Code'.
  8. File the form.
  9. Access the 'Task List Export/Import' form.
  10. Select 'Specific Task Type' from the 'Export All/Selected Task Types' field.
  11. Select "Task Associations" from the 'Task Types to Export' field.
  12. Select "Select Associations" from the 'Export All Task Associations' field.
  13. Select "Task A" from the 'Task Associations to Export' field.
  14. Click [Export Selected Task Items] and confirm a "TaskListExport (#).XML" file is downloaded.
  15. Click [Import Tasks] and then click [Select File To Import].
  16. Select the recently downloaded "TaskListExport (#).XML" file and then click [Validate Import File].
  17. Confirm that the 'Validation Results' field contains "Validation completed with no Errors or Warnings.".
  18. Click [Post Import File], confirm a "File Posted Successfully" message is displayed and click [OK].
  19. Close the form.
  20. Access the 'Task Associations' form.
  21. Set the 'Task Type' field to "Task Definition"
  22. Set the 'Task Group / Definition' field to "Task A".
  23. Validate the information filed displays correctly.
Pre-Administration Tasks
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Task Definitions
  • Task Associations
  • Orders This Episode
  • eMAR
Scenario 1: eMAR NX - Pre-Administration task warning - Administration Event
Steps

Internal Testing Only
Topics
• NX • Task List • eMAR NX
Update 20 Summary | Details
OE NX - Result Notifications Configuration
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Review Results
  • View Results
  • Void Results
  • Results Importing
  • Result Notification Configuration
  • Notifications Setup
Scenario 1: NX - Result Notification Configuration - Abnormal Results
Specific Setup:
  • A Client must have an active episode. (Client A)
  • "Client A" must have an active lab order. (Order A)
  • The staff member associated with the logged in user must be the 'Ordering Practitioner' for "Order A".
  • A HL-7 result file must exist for an abnormal result referencing "Client A" and the 'Order Number' associated to "Order A". (Result File A)
Steps
  1. Access the 'Result Notification Configuration' form.
  2. Select "Edit" from the 'Add/Edit' field.
  3. Select "Ordering Practitioner (Abnormal)" from the 'Select Existing Notification Type' field.
  4. Select "Abnormal" from the 'Notify On Result Type' field.
  5. Select any value in the 'Result To Do Type' field.
  6. Select "Ordering Practitioner" in the 'Notify User On Result' field and file the form.
  7. Access the 'Notifications Setup' form.
  8. Select "Results Entry: Ordering Practitioner (Abnormal)" from the 'Notification Type' field.
  9. Select "Popup Notification" as well as any other desired values from the 'Notification Method' field.
  10. Set the 'Notification Text' field to any value and file the form.
  11. Access the 'Results Importing' form.
  12. Set the 'File Path for Import' field to the location of "Result File A " and click [Import].
  13. Validate the result imports successfully.
  14. Validate a popup notification is received containing the value entered in the 'Notification Text' field.
  15. Validate any other 'Notification Method' selected also displays correctly.
Scenario 2: NX - Result Notification Configuration - Normal Results
Specific Setup:
  • A client must have an active episode. (Client A)
  • "Client A" must have an active lab order (Order A).
  • The staff member associated with the logged in user must be the 'Ordering Practitioner' for "Order A".
  • A HL-7 result file must exist for a normal result referencing "Client A" and the 'Order Number' associated to "Order A". (Result File A)
Steps
  1. Access the 'Result Notification Configuration' form.
  2. Select "Edit" from the 'Add/Edit' field.
  3. Select "Ordering Practitioner (Results Entry)" from the 'Select Existing Notification Type' field.
  4. Select "Normal" from the 'Notify On Result Type' field.
  5. Select any value in the 'Result To Do Type' field.
  6. Select "Ordering Practitioner" in the 'Notify User On Result' field and file the form.
  7. Access the 'Notifications Setup' form.
  8. Select "Results Entry: Ordering Practitioner" from the 'Notification Type' field.
  9. Select "Popup Notification" as well as any other desired values from the 'Notification Method' field.
  10. Set the 'Notification Text' field to any value and file the form.
  11. Access the 'Results Importing' form.
  12. Set the 'File Path for Import' field to the location of "Result File A " and click [Import].
  13. Validate the result imports successfully.
  14. Validate a popup notification is received containing the value entered in the 'Notification Text' field.
  15. Validate any other 'Notification Method' selected also displays correctly.
Topics
• Results
Update 21 Summary | Details
'Progress Notes' web service
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Progress Notes (Group and Individual)
  • Registry Settings (CWS)
  • SoapUI - ProgressNotes.Client.Request - AddProgressNotes
  • SoapUI - ProgressNotes.Client.Request - EditProgressNotes
Scenario 1: File a new progress note using the 'WEBSVC.ProgressNotes.Client.Request' web service
Specific Setup:
  • Document routing is not enabled on the 'Progress Notes (Group and Individual)' form.
  • The 'Multiple Start and End Times to Document Sessions' registry setting is set to "Y" for the 'Progress Notes (Group and Individual)' form.
  • A client must be enrolled in an existing episode (Client A).
  • Must have the 'Progress Notes' widget accessible from the HomeView.
Steps
  1. Access SOAPUI for the 'ProgressNotes.Client.Request' - 'AddProgressNotes' web service.
  2. Enter the system code that will be used to log on in the 'SystemCode' field.
  3. Enter the username that will be used to log on in the 'UserName' field.
  4. Enter the password for the user logging on in the 'Password' field.
  5. Enter the desired practitioner ID in the 'Practitioner' field.
  6. Enter the desired value in the 'NotesField' field.
  7. Enter the desired value in the 'NoteType' field.
  8. Enter the desired value in the 'Location' field.
  9. Enter "F" in the 'DraftFinal' field.
  10. Enter "N" in the 'ProgressNoteFor' field.
  11. Enter the desired value in the 'ServiceChargeCode' field.
  12. Enter the desired value in the 'ServiceProgram' field.
  13. Enter the desired date in the 'DateOfService' field.
  14. Enter "9:00 AM" in the first 'SessionTimes' - 'StartTime' field.
  15. Enter "9:30 AM" in the first 'SessionTimes' - 'EndTime' field.
  16. Enter "10:00 AM" in the second 'SessionTimes' - 'StartTime' filed.
  17. Enter "10:45 AM" in the second 'SessionTimes' - 'EndTime' field.
  18. Enter "Client A's" PATID in the 'ClientID' field.
  19. Enter the desired episode in the 'EpisodeNumber' field.
  20. Enter "CWSPN22000" in the 'Option' field.
  21. Click [Run].
  22. Validate the 'Confirmation' field contains a Unique ID (ex. Unique ID: NOT65244.001).
  23. Validate the 'Message' field contains: Progress Notes web service has been filed successfully.
  24. Select "Client A" and navigate to the 'Progress Notes' widget.
  25. Validate the 'Progress Notes' widget contains the progress note filed via web service in the previous steps.
  26. Validate the 'Start/End Time(s)' field contains the multiple session start/end times filed in the previous steps.
  27. Validate the 'Service Duration' field is populated accordingly.
Scenario 2: Edit an existing progress note using the 'WEBSVC.ProgressNotes.Client.Request' web service
Specific Setup:
  • Document routing is not enabled on the 'Progress Notes (Group and Individual)' form.
  • The 'Multiple Start and End Times to Document Sessions' registry setting is set to "Y" for the 'Progress Notes (Group and Individual)' form.
  • A client must be enrolled in an existing episode and have a draft note on file (Client A).
  • Must have the 'Progress Notes' widget accessible from the HomeView.
Steps
  1. Access SOAPUI for the 'ProgressNotes.Client.Request' - 'EditProgressNotes' web service.
  2. Enter the system code that will be used to log on in the 'SystemCode' field.
  3. Enter the username that will be used to log on in the 'UserName' field.
  4. Enter the password for the user logging on in the 'Password' field.
  5. Enter the desired practitioner ID in the 'Practitioner' field.
  6. Enter the desired value in the 'NotesField' field.
  7. Enter the desired value in the 'NoteType' field.
  8. Enter the desired value in the 'Location' field.
  9. Enter "F" in the 'DraftFinal' field.
  10. Enter "N" in the 'ProgressNoteFor' field.
  11. Enter the desired value in the 'ServiceChargeCode' field.
  12. Enter the desired value in the 'ServiceProgram' field.
  13. Enter the desired date in the 'DateOfService' field.
  14. Enter "10:00 AM" in the first 'SessionTimes' - 'StartTime' field.
  15. Enter "10:30 AM" in the first 'SessionTimes' - 'EndTime' field.
  16. Enter "10:30 AM" in the second 'SessionTimes' - 'StartTime' filed.
  17. Enter "10:45 AM" in the second 'SessionTimes' - 'EndTime' field.
  18. Enter "Client A's" PATID in the 'ClientID' field.
  19. Enter the desired episode in the 'EpisodeNumber' field.
  20. Enter the unique ID for the draft note in the 'NoteUniqueID' field.
  21. Enter "CWSPN22000" in the 'Option' field.
  22. Click [Run].
  23. Validate the 'Confirmation' field contains a Unique ID (ex. Unique ID: NOT65244.001).
  24. Validate the 'Message' field contains: Progress Notes web service has been filed successfully.
  25. Select "Client A" and navigate to the 'Progress Notes' widget.
  26. Validate the 'Progress Notes' widget contains the progress note updated via web service in the previous steps.
  27. Validate the 'Start/End Time(s)' field contains the multiple session start/end times filed in the previous steps.
  28. Validate the 'Service Duration' field is populated accordingly.
Topics
• Progress Notes • Web Services
 

Avatar_CWS_2024_Monthly_Release_2024.01.00_Details.csv