Skip to main content

Avatar CWS 2024 Quarterly Release 2024.02 Acceptance Tests

  1. Last updated
  2. Save as PDF
Update 1 Summary | Details
2024 Update installation
Scenario 1: Validate Upgrading Avatar CWS 2023 to 2024 is successful when 2023.04.00 is loaded
Steps
  1. Open the "Product Updates" form.
  2. Select the appropriate [Namespace] from the Application dropdown list
  3. Click [Select Update/Customization Pack].
  4. Browse to the location for the updates and select the Update 1.
  5. Click [OK] on the "File Upload Complete" window.
  6. Click [Review Update/Customization Pack Contents].
  7. Verify Update 1 is included.
  8. Click [Install Update/Customization Pack].
  9. Click [OK] when the install completes.
  10. Click [Close Form].
Topics
• Upgrade
Update 2 Summary | Details
"Client Problem List" product custom logic
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Problem List
  • System Code Definition
Scenario 1: Progress Notes (Group and Individual) - Validate 'Client Problem List' product custom logic
Specific Setup:
  • Must have a 'SS Note Multiple Response Dictionary' field added to the 'Progress Notes (Group and Individual)' form with "Client Problem List" selected in the 'Product Custom Logic' field in 'Site Specific Section Modeling'. This field will be referred to as the 'Client Problem List' field.
  • Document routing is enabled on the 'Progress Notes (Group and Individual)' form.
  • A client is enrolled in an existing episode (Client A).
  • The 'Progress Notes' widget is accessible on the HomeView.
Steps
  1. Select "Client A" and access the 'Problem List' form.
  2. Click [View/Enter Problems].
  3. Validate the 'Problem List' grid is displayed.
  4. Click [New Row].
  5. Add a new problem. This will be referred to as "Problem A".
  6. Select the desired value in the 'Problem Classification' field.
  7. Select the desired value in the 'Type' field.
  8. Select "Active" in the 'Status' field.
  9. Populate any other required and desired fields.
  10. Click [New Row].
  11. Add another new problem. This will be referred to as "Problem B".
  12. Select "Specify Other" in the 'Problem' field.
  13. Enter the desired value in the 'Other' field.
  14. Select the desired value in the 'Problem Classification' field.
  15. Select the desired value in the 'Type' field.
  16. Select "Active" in the 'Status' field.
  17. Populate any other required and desired fields.
  18. Click [Save], [Yes] and [Submit].
  19. Access the 'Progress Notes (Group and Individual)' form.
  20. Select "Client A" in the 'Select Client' field.
  21. Select the desired episode in the 'Select Episode' field.
  22. Select "Independent Note" in the 'Progress Note For' field.
  23. Select the desired value in the 'Note Type' field.
  24. Enter the desired value in the 'Notes Field'.
  25. Populate any other desired fields.
  26. Validate the 'Client Problem List' field is displayed and contains:
  27. "Problem A" with a problem description that matches the 'Problem List'
  28. "Problem B" as "Specify Other".
  29. Select "Problem A" and "Problem B" in the 'Client Problem List' field.
  30. Select "Final" in the 'Draft/Final' field.
  31. Click [File Note].
  32. Validate a document routing image is displayed with the note details.
  33. Validate "Problem A" is displayed and the problem description matches the 'Problem List'.
  34. Validate "Problem B" is displayed as "Other".
  35. Click [Accept].
  36. Enter the password for the logged in user and click [OK].
  37. Validate a message is displayed stating: Note Filed. Do you want to return to Progress Notes form?
  38. Click [No].
  39. Select "Client A" and access the 'Progress Notes' widget.
  40. Validate the note filed in the previous steps is displayed.
  41. Validate "Problem A" is displayed and the problem description matches the 'Problem List'.
  42. Validate "Problem B" is displayed as "Specify Other".
  43. Select "Client A" and access the 'Client Chart'.
  44. Select the 'Progress Notes (Group and Individual)' form from the left-hand side.
  45. Validate the note filed in the previous steps is displayed.
  46. Validate "Problem A" is displayed and the problem description matches the 'Problem List'.
  47. Validate "Problem B" is displayed as "Specify Other".
  48. Close the chart.
  49. Access the 'Clinical Document Viewer' form.
  50. Select "Client" in the 'Select Type' field.
  51. Select "Individual" in the 'Select All or Individual Client' field.
  52. Select "Client A" in the 'Select Client' field.
  53. Select "All" in the 'Episode' field.
  54. Click [Process].
  55. Validate the document filed in the previous steps is displayed and select it for viewing.
  56. Validate the progress note details are displayed as expected.
  57. Validate "Problem A" is displayed and the problem description matches the 'Problem List'.
  58. Validate "Problem B" is displayed as "Other".
  59. Click [Close All Documents], [Search], and [Close].
Scenario 2: Progress Notes - validate Problem Classification sub-system code restrictions for "Client Problem List" PCL
Specific Setup:
  • A client (Client A) is admitted into a program (Program A).
  • Two sub-system codes are defined in the 'System Code Definition' form:
  • "System Code A" and "System Code B" have "Program A" selected in 'Associated Programs'.
  • Two problem classifications are defined for the '(16250) Problem Classification' CWS dictionary:
  • "Classification A" has both the root system code being used & "System Code A" selected in the 'Restricted Sub-system Codes' extended dictionary.
  • "Classification B" has both the root system code being used & "System Code B" selected in the 'Restricted Sub-system Codes' extended dictionary.
  • Must have a 'SS Note Multiple Response Dictionary' field added to the 'Progress Notes (Group and Individual)' form with "Client Problem List" selected in the 'Product Custom Logic' field in 'Site Specific Section Modeling'. This field will be referred to as the 'Client Problem List' field.
Steps
  1. Select "Client A" and access the 'Problem List' form.
  2. Click [View/Enter Problems].
  3. Validate the 'Problem List' grid is displayed.
  4. Click [New Row].
  5. Add a new problem. This will be referred to as "Problem A".
  6. Select "Classification A" in the 'Problem Classification' field.
  7. Select "Primary" in the 'Type' field.
  8. Select "Active" in the 'Status' field.
  9. Click [New Row].
  10. Add a new problem. This will be referred to as "Problem B".
  11. Select "Classification B" in the 'Problem Classification' field.
  12. Select "Primary" in the 'Type' field.
  13. Select "Active" in the 'Status' field.
  14. Click [Save], [Yes] and [Submit].
  15. Access the 'Progress Notes (Group and Individual)' form.
  16. Select "Client A" in the 'Select Client' field.
  17. Select the desired episode in the 'Select Episode' field.
  18. Validate the 'Client Problem List' field is displayed and contains "Problem A" and "Problem B".
  19. Validate the problem descriptions match the 'Problem List'.
  20. Close the form.
  21. Log out.
  22. Login using "System Code A".
  23. Access the 'Progress Notes (Group and Individual)' form.
  24. Select "Client A" in the 'Select Client' field.
  25. Select the desired episode in the 'Select Episode' field.
  26. Validate the 'Client Problem List' field is displayed and only contains "Problem A".
  27. Validate the problem descriptions match the 'Problem List'.
  28. Close the form.
  29. Log out.
  30. Login using "System Code B".
  31. Access the 'Progress Notes (Group and Individual)' form.
  32. Select "Client A" in the 'Select Client' field.
  33. Select the desired episode in the 'Select Episode' field.
  34. Validate the 'Client Problem List' field is displayed and only contains "Problem B".
  35. Validate the problem descriptions match the 'Problem List'.
  36. Close the form.
Topics
• Progress Notes • Problem List
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
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
  • 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
  • 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 4 Summary | Details
Vitals Quick Action - Flags and warnings
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Quick Actions Page
  • CWS Vital Signs Setup
Scenario 1: Validate the 'Quick Vitals' quick action
Specific Setup:
  • A client must be enrolled in an existing episode (Client A)
  • 'Quick Vitals' Quick Action must be assigned to the user in the 'NX View Definition' form.
  • This is for Avatar NX systems only.
  • A client must be over the age of 18 and must be enrolled in an existing episode (Client B).
  • A client must be between the ages of 12-18 and must be enrolled in an existing episode (Client C).
  • Using the form "CWS Vital Signs Setup"
  • Enter in rules or warnings to enforce, such as Blood Pressure Systolic must be in the range of 112-120 for clients who are over the age of 18.
  • Enter a rule that clients of all ages must have a temperature in Fahrenheit degrees of 98.0 - 99.0.
Steps
  1. Select "Client A" and access the 'Client Dashboard'.
  2. Navigate to the 'Quick Vitals' quick action.
  3. Click [Quick Vitals - Add].
  4. Validate "Diastolic" is spelled correctly.
  5. Enter the desired value in the 'Systolic' field.
  6. Validate the 'Diastolic' and 'Position' fields are required.
  7. Populate the desired fields and click [Save].
  8. Validate the 'Quick Vitals' quick action contains "Vitals last entered: [current date and time]".
  9. Click [Quick Vitals - Add].
  10. Populate the desired fields and click [Save].
  11. Validate the 'Quick Vitals' quick action contains "Vitals last entered: [current date and time]".
  12. Click [Quick Vitals - Add].
  13. Populate the desired fields and click [Save].
  14. Validate the 'Quick Vitals' quick action contains "Vitals last entered: [current date and time]".
  15. Click [Close].
  16. Select "Client B" and access the 'Client Dashboard'.
  17. Navigate to the "Quick Vitals" quick action.
  18. In the quick action, enter values that will cause warnings because fields are over/under limits set in "CWS Vital Signs Setup" form.
  19. Validate the fields whose values are outside of the limits set display the data value in red text and that warning messages indicating that fields are outside of the limits when you attempt to "Save" the data.
  20. Access the 'Vitals Entry' form.
  21. Select the 'Vitals Report' field.
  22. Click [Start Date Y].
  23. Click [Start Date T].
  24. Enter any value in the 'Start Time' field.
  25. Enter any value in the 'End Time' field.
  26. Select "All" in the 'Vital Sign(s) for Report' field.
  27. Click [View Report].
  28. Validate the report contains the entries filed in the previous steps.
  29. Click [Close Report].
  30. Close the form.
Assessment Mapping - Treatment Plans mapped to Progress Notes (Group and Individual)
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Assessment Mapping
  • Clinical Assessment
  • Treatment Plan
  • Flag Assessment Forms
  • Assessment Code Mapping
Scenario 1: Treatment Plan - validate 'Assessment Mapping'
Specific Setup:
  • Must have a user defined assessment for testing with a 'Strengths' field (Assessment A).
  • A client must be enrolled in an existing episode (Client A).
  • Using the "Flag Assessment" form
  • Flag the "Progress Notes (Group and Individual)" form as a form that can be mapped.
  • Using the "Assessment Mapping" form
  • Map the "Treatment Plan" form fields "Strengths", "Weaknesses", "Discharge Plan" to fields on the "Progress Notes (Group and Individual)" form.
Steps
  1. Access the 'Assessment Mapping' form.
  2. Select "Treatment Plan" in the 'Map Code for Use In' field.
  3. Select "Assessment A" in the 'Form to Map' field.
  4. Select "Strength" in the 'Map To' field.
  5. Select "Strengths" in the 'Assessment Field' field.
  6. Click [Save Mapping] and [OK].
  7. Close the form.
  8. Select "Client A" and access "Assessment A".
  9. Populate all required and desired fields.
  10. Enter "Test Strengths" in the 'Strengths' field.
  11. Click [Submit].
  12. Select "Client A" and access the 'Treatment Plan' form.
  13. Populate all required and desired fields.
  14. Validate the 'Strength' field contains "Test Strengths".
  15. Click [Submit].
  16. Select "Client A" and access "Assessment A".
  17. Click [Add] to add a new record.
  18. Populate all required and desired fields.
  19. Enter "New Test Strengths" in the 'Strengths' field.
  20. Click [Submit].
  21. Select "Client A" and access the 'Treatment Plan' form.
  22. Click [Add] to add a new record.
  23. Populate all required and desired fields.
  24. Validate the 'Strength' field contains "New Test Strengths".
  25. Click [Submit].
  26. Select "Client A" and open the "Progress Notes (Group and Individual)" form.
  27. Create a new progress note making sure to populate the fields that are mapped to the "Treatment Plan" form through "Assessment Mapping".
  28. Complete the progress note.
  29. Select "Client A" and open the "Treatment Plan" form.
  30. Validate the "Strengths", "Weaknesses" and "Discharge Plan" fields are populated with the values from the fields mapped to "Progress Notes (Group and Individual)" form.
Topics
• NX • Quick Actions • Treatment Plan • Progress Notes • Assessment Mapping
Update 5 Summary | Details
The 'Limit Scratch Notes to Current Login User' registry setting
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • SoapUI - ProgressNotes.Group.Request - GetGroupNoteItem
  • SoapUI - ProgressNotes.Group.Request - GetGroupNoteItemResponse - GetGroupNoteItemResult
Scenario 1: Validate the 'Limit Scratch Notes to Current Login User' registry setting, when set to "Y"
Specific Setup:
  • Four users are defined with associated practitioners:
  • User A - Practitioner A
  • User B - Practitioner B
  • User C - Practitioner C
  • User D - Practitioner D
  • The 'Co-Practitioner' and 'Co-Practitioner 2' fields must be available on the 'Progress Notes (Group and Individual)' form. This can be done via 'Site Specific Section Modeling'.
  • A group (Group A) must be defined with two clients (Client A & Client B).
Steps
  1. Log in as "User A".
  2. Access the 'Registry Settings' form.
  3. Enter "Limit Scratch Notes to Current Login User" in the 'Limit Registry Settings to the Following Search Criteria' field.
  4. Click [View Registry Settings].
  5. Select the registry setting for the 'Progress Notes (Group and Individual)' form and click [OK].
  6. Validate the 'Registry Setting Details' field contains: If 'Y' is selected the 'Select Note to Edit' list will be limited to Notes where the current logged in user is listed as a practitioner or co-practitioner. An exception is made when launching the 'Progress Notes (Group and Individual)' form from the To-Do list. If 'N' is selected, all of the Scratch Notes that match the 'Group Name or Number' and 'Note Date' will be listed.
  7. Enter "Y" in the 'Registry Setting Value' field.
  8. Click [Submit] and close the form.
  9. Access the 'Progress Notes (Group and Individual)' form.
  10. Select the "Group Default Notes" section.
  11. Enter the current date in the 'Date of Group' field.
  12. Select "Practitioner A" in the 'Practitioner' field.
  13. Select "New Service" in the 'Progress Notes For' field.
  14. Select "Group A" in the 'Group Name or Number' field.
  15. Select the desired value in the 'Note Type' field.
  16. Enter the desired value in the 'Note' field.
  17. Select any group service code in the 'Service Charge Code' field.
  18. Select the desired value in the 'Service Program' field.
  19. Select the desired value in the 'Location' field.
  20. Select "Practitioner B" in the 'Co-Practitioner' field.
  21. Select "Practitioner C" in the 'Co-Practitioner 2' field.
  22. Populate any other desired fields.
  23. Click [File Note].
  24. Validate a message is displayed stating: Progress Notes are filed.
  25. Select the "Individual Progress Notes" section.
  26. Select "Group A" in the 'Group Name or Number' field.
  27. Enter the current date in the 'Note Date' field.
  28. Validate the 'Select Note To Edit' field contains the scratch notes for "Client A" and "Client B".
  29. Close the form.
  30. Log out.
  31. Log in as "User B".
  32. Access the 'Progress Notes (Group and Individual)' form.
  33. Select "Group A" in the 'Group Name or Number' field.
  34. Enter the current date in the 'Note Date' field.
  35. Validate the 'Select Note To Edit' field contains the scratch notes for "Client A" and "Client B".
  36. Close the form.
  37. Log out.
  38. Log in as "User C".
  39. Access the 'Progress Notes (Group and Individual)' form.
  40. Select "Group A" in the 'Group Name or Number' field.
  41. Enter the current date in the 'Note Date' field.
  42. Validate the 'Select Note To Edit' field contains the scratch notes for "Client A" and "Client B".
  43. Close the form.
  44. Log out.
  45. Log in as "User D".
  46. Access the 'Progress Notes (Group and Individual)' form.
  47. Select "Group A" in the 'Group Name or Number' field.
  48. Enter the current date in the 'Note Date' field.
  49. Validate a message is displayed stating: Group notes do not exist for the selected group and date and logged in user.
  50. Click [OK] and close the form.
  51. Close the form.
  52. Log out.
  53. Log in as "User A".
  54. Access the 'Progress Notes (Group and Individual)' form.
  55. Select "Group A" in the 'Group Name or Number' field.
  56. Enter the current date in the 'Note Date' field.
  57. Validate the 'Select Note To Edit' field contains the scratch notes for "Client A" and "Client B".
  58. Select the note for "Client A".
  59. Validate all fields populate based off the values entered in the group note.
  60. Individualize the note as desired and file the note.
  61. Repeat for "Client B".
  62. Close the form.
Scenario 2: Validate the 'Limit Scratch Notes to Current Login User' registry setting, when set to "N"
Specific Setup:
  • Four users are defined with associated practitioners:
  • User A - Practitioner A
  • User B - Practitioner B
  • User C - Practitioner C
  • User D - Practitioner D
  • The 'Co-Practitioner' and 'Co-Practitioner 2' fields must be available on the 'Progress Notes (Group and Individual)' form. This can be done via 'Site Specific Section Modeling'.
  • A group (Group A) must be defined with two clients (Client A & Client B).
Steps
  1. Log in as "User A".
  2. Access the 'Registry Settings' form.
  3. Enter "Limit Scratch Notes to Current Login User" in the 'Limit Registry Settings to the Following Search Criteria' field.
  4. Click [View Registry Settings].
  5. Select the registry setting for the 'Progress Notes (Group and Individual)' form and click [OK].
  6. Validate the 'Registry Setting Details' field contains: If 'Y' is selected the 'Select Note to Edit' list will be limited to Notes where the current logged in user is listed as a practitioner or co-practitioner. An exception is made when launching the 'Progress Notes (Group and Individual)' form from the To-Do list. If 'N' is selected, all of the Scratch Notes that match the 'Group Name or Number' and 'Note Date' will be listed.
  7. Enter "N" in the 'Registry Setting Value' field.
  8. Click [Submit] and close the form.
  9. Access the 'Progress Notes (Group and Individual)' form.
  10. Select the "Group Default Notes" section.
  11. Enter the current date in the 'Date of Group' field.
  12. Select "Practitioner A" in the 'Practitioner' field.
  13. Select "New Service" in the 'Progress Notes For' field.
  14. Select "Group A" in the 'Group Name or Number' field.
  15. Select the desired value in the 'Note Type' field.
  16. Enter the desired value in the 'Note' field.
  17. Select any group service code in the 'Service Charge Code' field.
  18. Select the desired value in the 'Service Program' field.
  19. Select the desired value in the 'Location' field.
  20. Select "Practitioner B" in the 'Co-Practitioner' field.
  21. Select "Practitioner C" in the 'Co-Practitioner 2' field.
  22. Populate any other desired fields.
  23. Click [File Note].
  24. Validate a message is displayed stating: Progress Notes are filed.
  25. Select the "Individual Progress Notes" section.
  26. Select "Group A" in the 'Group Name or Number' field.
  27. Enter the current date in the 'Note Date' field.
  28. Validate the 'Select Note To Edit' field contains the scratch notes for "Client A" and "Client B".
  29. Close the form.
  30. Log out.
  31. Log in as "User B".
  32. Access the 'Progress Notes (Group and Individual)' form.
  33. Select "Group A" in the 'Group Name or Number' field.
  34. Enter the current date in the 'Note Date' field.
  35. Validate the 'Select Note To Edit' field contains the scratch notes for "Client A" and "Client B".
  36. Close the form.
  37. Log out.
  38. Log in as "User C".
  39. Access the 'Progress Notes (Group and Individual)' form.
  40. Select "Group A" in the 'Group Name or Number' field.
  41. Enter the current date in the 'Note Date' field.
  42. Validate the 'Select Note To Edit' field contains the scratch notes for "Client A" and "Client B".
  43. Close the form.
  44. Log out.
  45. Log in as "User D".
  46. Access the 'Progress Notes (Group and Individual)' form.
  47. Select "Group A" in the 'Group Name or Number' field.
  48. Enter the current date in the 'Note Date' field.
  49. Validate the 'Select Note To Edit' field contains the scratch notes for "Client A" and "Client B" since the registry setting is disabled.
  50. Click [OK] and close the form.
  51. Close the form.
  52. Log out.
  53. Log in as "User A".
  54. Access the 'Progress Notes (Group and Individual)' form.
  55. Select "Group A" in the 'Group Name or Number' field.
  56. Enter the current date in the 'Note Date' field.
  57. Validate the 'Select Note To Edit' field contains the scratch notes for "Client A" and "Client B".
  58. Select the note for "Client A".
  59. Validate all fields populate based off the values entered in the group note.
  60. Individualize the note as desired and file the note.
  61. Repeat for "Client B".
  62. Close the form.
Scenario 3: 'WEBSVC.ProgressNotes.Group.Request' - 'GetGroupNoteItems' web service - Validate the 'Limit Scratch Notes to Current Login User' registry setting when set to "Y"
Specific Setup:
  • The 'Limit Scratch Notes to Current Login User' registry setting is set to "Y" for the 'Progress Notes (Group and Individual)' form.
  • The 'Co-Practitioner' and 'Co-Practitioner 2' fields must be available on the 'Progress Notes (Group and Individual)' form. This can be done via 'Site Specific Section Modeling'.
  • A group (Group A) must be defined with two clients (Client A & Client B).
  • A user (User A) is defined with an associated practitioner (Practitioner A).
  • "Group A" must have multiple group default notes on file for the current date. Some with "Practitioner A" as either 'Practitioner' or 'Co-Practitioner' and some without "Practitioner A".
Steps
  1. Access SOAPUI for the 'ProgressNotes.Group.Request' - 'GetGroupNoteItems' web service.
  2. Enter the system code that will be used to log on in the 'SystemCode' field.
  3. Enter "User A" in the 'UserName' field.
  4. Enter the password for the user logging on in the 'Password' field.
  5. Enter "Group A" in the 'GroupID' field.
  6. Enter the current date in the 'NoteDate' field.
  7. Click [Run].
  8. Validate the 'Response' field contains notes where "Practitioner A" is either the 'Practitioner' or 'Co-Practitioner'.
Scenario 4: 'WEBSVC.ProgressNotes.Group.Request' - 'GetGroupNoteItems' web service - Validate the 'Limit Scratch Notes to Current Login User' registry setting when set to "N"
Specific Setup:
  • The 'Limit Scratch Notes to Current Login User' registry setting is set to "N" for the 'Progress Notes (Group and Individual)' form.
  • The 'Co-Practitioner' and 'Co-Practitioner 2' fields must be available on the 'Progress Notes (Group and Individual)' form. This can be done via 'Site Specific Section Modeling'.
  • A group (Group A) must be defined with two clients (Client A & Client B).
  • A user (User A) is defined with an associated practitioner (Practitioner A).
  • "Group A" must have multiple group default notes on file for the current date. Some with "Practitioner A" as either 'Practitioner' or 'Co-Practitioner' and some without "Practitioner A".
Steps
  1. Access SOAPUI for the 'ProgressNotes.Group.Request' - 'GetGroupNoteItems' web service.
  2. Enter the system code that will be used to log on in the 'SystemCode' field.
  3. Enter "User A" in the 'UserName' field.
  4. Enter the password for the user logging on in the 'Password' field.
  5. Enter "Group A" in the 'GroupID' field.
  6. Enter the current date in the 'NoteDate' field.
  7. Click [Run].
  8. Validate the 'Response' field contains all group notes for "Group A" on the current date, regardless of practitioner.
Topics
• Registry Settings • Group Progress Notes • Progress Notes • Web Services
Update 6 Summary | Details
Observer NX - future functionality
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Manage Nursing Caseload
  • Nursing Caseload Assignment
  • ProgressNote Approval
  • Client Observation
  • Discharge
  • Orders This Episode
Scenario 1: Observer NX - Filing a late observation
Steps

Internal Testing Only.

Scenario 2: Validate the 'Enable Observation Copy Forward Action' registry setting
Steps

Internal Testing Only.

Scenario 3: Observer NX - Validate voiding an Observation
Steps

Internal Testing Only.

Scenario 4: Observer NX - Validate the order number in payload when filing an observation
Steps

Internal Testing Only.

Scenario 5: Observer NX - Validate transfers in the "Observer.caseload_audit" table
Steps

Internal Testing Only.
Topics
• Observer NX • NX Only • Order Entry Console
Update 7 Summary | Details
Allergies and Hypersensitivities - No Known Drug Allergy
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • HL7 Connection Monitor
  • Orders This Episode
Scenario 1: 'Known Medication Allergies' and 'Known Food Allergies' in ADT Outbound messages
Specific Setup:
  • An ADT-Outbound connection must be configured for HL7.
  • Three clients must exist that each have an active episode. (Client A) (Client B) (Client C)
  • “Client A”, "Client B", and "Client C" must have a ‘Date of Birth’, ‘Sex’ and address on file in the ‘Update Client Data’ form, as well as information filed in the ‘Diagnosis’ form, and in the ‘Height’ and ‘Weight’ fields in the ‘Vitals Entry’ form.
Steps
  1. Select "Client A" and access the 'Allergies and Hypersensitivities' form.
  2. Click [Update], validate there are no rows in the grid, and click [Close/cancel].
  3. Select "No" in the 'Known Medication Allergies' field.
  4. Select "No" in the 'Known Food Allergies' field.
  5. Click [Submit].
  6. Access the 'HL7 Connection Monitor' form and select the "ADT Outbound" connection.
  7. Validate that the 'Last Message Processed' contains an 'AL1-3.2' segment = "NKDA - NO KNOWN DRUG ALLERGIES".
  8. Create a report using the ‘cw_client_clinical_info’ table and validate that the row for "Client A" has an "N" for the 'known_med_allergies_code', and for the 'known_allergies_code'.
  9. Access the 'Allergies and Hypersensitivities' form and click [Update].
  10. Add a new row for any medicine (for example, Penciclovir) with a "Confirmed" status and click [Save].
  11. Validate 'Known Medication Allergies' field is disabled and has "Yes" selected.
  12. Exit the form without submitting.
  13. Access the 'HL7 Connection Monitor' form, click [Refresh Monitor], and select and select the "ADT Outbound" connection.
  14. Validate that the 'Last Message Processed' contains an 'AL1-3.2' segment = "PENCICLOVIR".
  15. Refresh the report and validate that the row for "Client A" has a "Y" for the 'known_med_allergies_code' and for the 'known_allergies_code'.
  16. Close the 'HL7 Connection Monitor' form and clear "Client A".
  17. Select "Client B" and access the 'Allergies and Hypersensitivities' form.
  18. Click [Update].
  19. Add a new row for any food allergy (for example, SHELLFISH) with a "Confirmed" status and click [Save].
  20. Validate 'Known Food Allergies' is set to "Yes" and is disabled.
  21. Exit the form without submitting.
  22. Access the 'HL7 Connection Monitor' form and select the "ADT Outbound" connection.
  23. Validate that the 'Last Message Processed' contains 2 'AL1' segments.
  24. The 1st 'AL1-3.2' segment = "SHELLFISH".
  25. The 2nd 'AL1-3.2' segment = "NO KNOWN DRUG ALLERGIES - NKDA".
  26. Refresh the report and validate that the row for "Client B" has a "Y" for the 'known_food_allergies_code' and for the 'known_allergies_code'.
  27. Close the 'HL7 Connection Monitor' form and clear "Client B".
  28. Select "Client C" and access the 'Allergies and Hypersensitivities' form.
  29. Click [Update], validate that there is no row in the grid.
  30. Add a new row for any food allergy (for example, SHELLFISH) with a "Confirmed" status.
  31. Add a new row for any medicine allergy (for example, Penciclovir) with "Confirmed" status and click [Save].
  32. Validate the 'Known Medication Allergies' field is disabled and has "Yes" selected.
  33. Validate the 'Known Food Allergies' field is disabled and has "Yes" selected.
  34. Click [Submit].
  35. Click 'myDay'.
  36. Access the 'HL7 Connection Monitor' form and select the "ADT Outbound" connection.
  37. Validate that the 'Last Message Processed' contains 2 'AL1' segments.
  38. The 1st 'AL1-3.2' segment = "SHELLFISH".
  39. The 2nd 'AL1-3.2' segment = "PENCICLOVIR".
  40. Refresh the report and validate that the row for 'Client C' has a "Y" for the 'known_food_allergies_code', 'known_med_allergies_code', and for the 'known_allergies_code'.
  41. Access the 'Allergies and Hypersensitivities' form click [Update].
  42. Edit the row for the medication allergy and set the 'Status to "Invalid" and click [Save].
  43. Select "No" in the 'Known Medication Allergies' field and click [Submit].
  44. Access the 'HL7 Connection Monitor' form.
  45. Click [Refresh Monitor].
  46. Select the "ADT Outbound" connection.
  47. Validate that the 'Last Message Processed' contains 3 'AL1' segments.
  48. The 1st 'AL1-3.2' segment = "SHELLFISH".
  49. The 2nd 'AL1-3.2' segment = "PENCICLOVIR".
  50. The 3rd 'AL1-3.2' segment = "NO KNOWN DRUG ALLERGIES - NKDA".
  51. Refresh the report and validate that the row for "Client C" has a "Y" for the 'known_food_allergies_code' and 'known_allergies_code', and has an "N" for 'known_med_allergies_code'.
  52. Access the 'Allergies and Hypersensitivities' form click [Update].
  53. Edit the row for the food allergy, set the 'Status' to "Invalid", and click [Save].
  54. Select "No" in the 'Known Food Allergies' field and click [Submit].
  55. Access the 'HL7 Connection Monitor' form.
  56. Click [Refresh Monitors].
  57. Select the "ADT Outbound" connection.
  58. Validate that the 'Last Message Processed' contains 3 'AL1' segments.
  59. The 1st 'AL1-3.2' segment = "SHELLFISH".
  60. The 2nd 'AL1-3.2' segment = "PENCICLOVIR".
  61. The 3rd 'AL1-3.2' segment = "NO KNOWN DRUG ALLERGIES - NKDA".
  62. Refresh the report and validate that the row for "Client C" has an "N" for the 'known_food_allergies_code', the 'known_allergies_code', and the 'known_med_allergies_code'.
Topics
• HL7 • Allergies and Hypersensitivities
Update 8 Summary | Details
Medication Inventory Management
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Finalize
  • Medical Note
  • Medication Inventory Management
  • Service Code Upload Process
  • Lot Number Manager
  • Adjust Inventory
  • Client Health Maintenance
Scenario 1: Medical Note - Inventory Management Disabled - Full Note Workflow
Specific Setup:
  • The 'Avatar CWS->Medication Inventory Management->->->->Enable Medication Inventory Management' registry setting must be set to "N".
  • Please log out of the application and log back in after completing the above configuration.
  • Two 'Vaccination/Immunization' procedure-type service codes must be configured in the 'Service Codes' form. (Immunization A) (Immunization B)
  • A 'Medication Administration' procedure-type service code must be configured in the 'Service Codes' form. (Medication A)
  • A procedure-type service code that is not a "Vaccination/Immunization" nor "Medication Administration" must be configured in the 'Service Codes' form. (Procedure A)
  • An outpatient program configured as a 'Primary Care' program in the 'Program Maintenance' form must exist. (Program A)
  • A client must have an active episode in "Program A". (Client A)
Steps
  1. Search for and select "Client A" and access 'Medical Note'.
  2. Click [Add Note] and create a new "Primary Care" Note.
  3. In the Facesheet:
  4. Select the ‘Vitals’ section and enter Blood Pressure, Height, Weight, and Temperature information, click [Save], and pull to note.
  5. Select the ‘Immunization’ section and enter a “Historical Immunization” record for yesterday.
  6. Select the ‘Allergies’ section and enter an allergy to “Shellfish” and pull to note.
  7. Select the ‘Document’ tab.
  8. Complete the 'Chief Complaint', 'HPI', 'Physical Exam' and 'Diagnosis' sections as necessary.
  9. Select the ‘Immunizations’ section.
  10. Expand the ‘Immunization History’ section and validate the Historical Immunization Record for the precious day is correctly shown.
  11. Click [Add] and then [Order Immunizations], select "Immunization A" from the 'Immunization Search' field and click [Continue].
  12. Fill in any required fields and click [Order].
  13. Click [Add] and then [Order Immunizations], select "Immunization B" from the 'Immunization Search' field and click [Continue].
  14. Fill in any required fields and click [Administer].
  15. Validate "Immunization A" is listed under the 'Pending Administrations' section and " Immunization B" is listed under the 'Immunization History' section.
  16. Populate all required fields and click [Save].
  17. Select the ‘Procedures’ section and click [Add].
  18. Select "Procedure A" from the 'Procedure' field.
  19. Select "Complete" from the 'Status' field.
  20. Set the 'Completion Date' field to "Today's Date.
  21. Populate any remaining required fields and click [Save].
  22. Validate "Procedure A" is listed under the 'Current Procedures' Section.
  23. Select the ‘In Office Administrations’ section.
  24. Click [Add], select "Medication A" from the 'In-Office Administrations Search' field and click [Continue].
  25. Populate all required fields and click [Administer].
  26. Populate all required fields and click [Save].
  27. Click [Add], select "Medication A" from the 'In-Office Administrations Search' field and click [Continue].
  28. Populate all required fields and click [Order].
  29. Validate "Medication A" is listed under the 'Pending Administrations' section and " Medication A" is listed under the 'Administration History' section.
  30. Select the ‘Finalize’ tab.
  31. Populate all required fields and click [Generate Note].
  32. Validate the ‘Note Summary’ is displayed and contains the appropriate information:
  33. The populated sections of the 'Facesheet' tab that were pulled into the note. (Allergies and Vitals)
  34. The required and populated sections of the 'Document' tab. (Chief Complaint, HPI, Physical Exam, Diagnosis)
  35. The 'Immunizations' section shows "Immunization A" in the 'Ordered (Pending)' section and "Immunization B" in the 'Administered In-Office' section.
  36. The 'Procedures' section shows "Procedure A" as complete.
  37. The 'In-Office Administrations' section shows "Medication A" in the 'Ordered (Pending)' section and "Medication B" in the 'Administered In-Office' section.
  38. Click [Sign Off] validate the Document is displayed and click [Accept], set the ‘Password’ field to the appropriate value and click [Verify].
Scenario 2: Medical Note - Inventory Management Enabled - In-Office Administration - Full Note Workflow
Specific Setup:
  • The 'Avatar CWS->Medication Inventory Management->->->->Enable Medication Inventory Management' registry setting must be set to "Y".
  • There must be at least one value in the Other CWS Tabled Files ‘(74101) Inventory Location’ dictionary. (Location A)
  • Please log out of the application and log back in after completing the above configuration.
  • A generic 'Evaluation Management' service code must be configured in the 'Service Codes' form. (Service Code A)
  • A 'Medication Administration' procedure-type service code must be configured in the 'Service Codes' form. (Medication A)
  • "Medication A" must have a template defined in the 'Medication Inventory Management' form. (Template A)
  • In the 'Medication Inventory Management' form inventory for "Template A" must be received to "Location A". (Inventory A)
  • An outpatient program must exist. (Program A)
  • In the 'Assign Services To Program' section of the 'Program Maintenance' form "Service Code A" must be associated to "Program A".
  • A client must have an active episode associated with "Program A". (Client A)
Steps
  1. Search for and select "Client A" and navigate to the 'Medical Note'.
  2. Click [Add Note].
  3. Create a 'Psychiatry' note.
  4. Select the ‘Document’ tab.
  5. Populate all required sections in the 'Document' tab.
  6. Click the 'In-Office Administration' section.
  7. Click [Add] and select "Medication A" from the 'In-Office Administration Search' field.
  8. Validate the 'Dose', 'Unit', and 'Route' fields automatically populate based on the entries made in "Template A"
  9. Fill in any remaining required fields and click [Order].
  10. Validate the 'Pending Administrations' field contains a row for "Medication A".
  11. Click the ellipses under the 'Action' column for "Medication A" and click [Administer].
  12. Validate, in the first section, the 'Dose', 'Unit', and 'Route' fields are correctly populated with the updated values and that all fields are disabled.
  13. Click the 'Lot Number Search' button and validate the 'Lot Number Manager' dialog is launched.
  14. Select the row for "Inventory A" and click [Select].
  15. Validate the 'Lot Number', 'Manufacturer', 'Expiration Date', and 'NDC" are all correctly populated and disabled.
  16. Fill in any remaining required fields and click [Save].
  17. Expand the 'Administration History' field and validate it contains a row for "Medication A" and that all columns are accurate.
  18. Click the ellipses under the 'Action' column for "Medication A" and click [Document Reaction].
  19. Select any value for the 'Reaction' field and click [Save].
  20. Click the ellipses under the 'Action' column for "Medication A" and click [View Details].
  21. Validation the 'Reaction' field contains the correct value and click [Close]
  22. Select the ‘Finalize’ tab.
  23. Populate all required fields and click [Generate Note].
  24. Validate the ‘Note Summary’ is displayed and contains the appropriate information and click [Sign Off].
  25. Validate the Document is displayed and click [Accept], set the ‘Password’ field to the appropriate value and click [Verify].
Scenario 3: Medical Note - Administering a medication order under the 'In-Office Administration' section when 'Inventory Management' is disabled - Pediatric
Specific Setup:
  • The 'Avatar CWS->Medication Inventory Management->->->->Enable Medication Inventory Management' registry setting must be set to "N".
  • Please log out of the application and log back in after completing the above configuration.
  • A 'Medication Administration' procedure-type service code must be configured in the 'Service Codes' form. (Medication A)
  • An outpatient program that is configured in the 'Program Maintenance' form to be a 'Primary Care' program must exist. (Program A)
  • A client must have an active episode in "Program A". (Client A)
Steps
  1. Search for and select "Client A" and navigate to the 'Medical Note'.
  2. Click [Add Note] and create a new 'Primary Care' note.
  3. Select the 'Document' tab.
  4. Navigate to the 'Diagnosis' section.
  5. Add a new diagnosis for "Client A".
  6. Navigate to the 'In-Office Administrations' section.
  7. Click [Add] and select "Medication A" from the 'In-Office Administrations Search' field.
  8. Validate the new diagnosis is listed under the 'Diagnosis' dropdown and select it.
  9. Fill in any remaining required fields and click [Order].
  10. Validate the 'Pending Administrations' field contains a row for "Medication A"
  11. Click the ellipses under the 'Action' column for "Medication A" and click [Administer].
  12. Validate, in the first section, the 'Dose', 'Unit', and 'Route' fields are correctly populated and that all fields are disabled.
  13. Fill in all required fields and click [Save].
  14. Validate the 'Pending Administrations' field no longer contains a row for "Medication A".
  15. Expand the 'Administration History' field and validate it contains a row for "Medication A" and that all columns are accurate.
Scenario 4: Medical Note - Administering a medication under the 'Pending Administration' sub-section of 'In Office Administration' and voiding the medications under the 'Administration History' section
Specific Setup:
  • The 'Avatar CWS->Medication Inventory Management->->->->Enable Medication Inventory Management' registry setting must be set to "N".
  • Please log out of the application and log back in after completing the above configuration.
  • Two 'Medication Administration' procedure-type service codes must be configured in the 'Service Codes' form. (Medication A)(Medication B)
  • An Outpatient program must exist. (Program A)
  • A client must have an active episode in "Program A". (Client A)
Steps
  1. Search for and select "Client A" and navigate to the 'Medical Note'.
  2. Click [Add Note] and create a new note.
  3. Select the 'Document' tab and then navigate to the 'In-Office Administration' section.
  4. Click [Add], select "Medication A" from the 'In-Office Administration Search' field and click [Continue].
  5. Populate all required fields and click [Order].
  6. Validate the 'Pending Administrations' field contains a row for "Medication A".
  7. Click [Add], select "Medication B" from the 'In-Office Administration Search' field and click [Continue].
  8. Populate all required fields and click [Order].
  9. Validate the 'Pending Administrations' field contains a row for "Medication A" and one for "Medication B".
  10. Click the ellipses under the 'Action' column for "Medication A" and click [Administer].
  11. Populate all required fields and click [Save].
  12. Expand the 'Administration History' field and validate it contains a row for "Medication A" and that all columns are accurate.
  13. Click the ellipses under the 'Action' column for "Medication B" and click [Refuse].
  14. Set the 'Refusal Reason' field to any value and click [Save].
  15. Validate the 'Administration History' field contains a row for "Medication A" and the status shows as "Administered".
  16. Validate the 'Administration History' field contains a row for "Medication B" and the status shows as "Refused".
  17. Click the ellipses under the 'Action' column for "Medication B" and click [Void].
  18. Set the 'Comments' field to any value and click [Save].
  19. Validate the 'Administration History' field contains a row for "Medication B" and the status shows as "Voided".
Scenario 5: Medical Note - Edit a medication that is listed under the 'Pending Medications' sub-section in the 'In-Office Administrations' section
Specific Setup:
  • The 'Avatar CWS->Medication Inventory Management->->->->Enable Medication Inventory Management' registry setting must be set to "Y".
  • There must be at least one value in the Other CWS Tabled Files ‘(74101) Inventory Location’ dictionary. (Location A)
  • Please log out of the application and log back in after completing the above configuration.
  • A 'Medication Administration' procedure-type service code must be configured in the 'Service Codes' form. (Medication A)
  • "Medication A" must have a template defined in the 'Medication Inventory Management' form. (Template A)
  • In the 'Medication Inventory Management' form, inventory for "Template A" must be received to "Location A". (Inventory A)
  • An outpatient program must exist. (Program A)
  • A client must have an active episode in "Program A". (Client A)
Steps
  1. Search for and select "Client A" and navigate to the 'Medical Note'.
  2. Click [Add Note] and create a new note.
  3. Select the 'Document' tab and then navigate to the 'In-Office Administrations' section.
  4. Click [Add] and select "Medication A" from the 'In-Office Administrations Search' field.
  5. Validate the 'Dose', 'Unit', and 'Route' fields automatically populate based on the entries made in "Template A".
  6. Fill in any remaining required fields and click [Order].
  7. Validate the 'Pending Administrations' field contains a row for "Medication A".
  8. Click the ellipses under the 'Action' column for "Medication A" and click [Edit].
  9. Set the 'Dose' and 'Unit' fields to any other values and click [Update].
  10. Validate the row for "Medication A" in the 'Pending Administrations field reflects the updated values.
  11. Click the ellipses under the 'Action' column for "Medication A" and click [Administer].
  12. Validate, in the first section, the 'Dose', 'Unit', and 'Route' fields are correctly populated with the updated values and that all fields are disabled.
  13. Click the 'Lot Number Search' button and validate the 'Lot Number Manager' dialog is launched.
  14. Select the row for "Inventory A" and click [Select].
  15. Validate the 'Lot Number', 'Manufacturer', 'Expiration Date', and 'NDC" are all correctly populated and disabled.
  16. Fill in any remaining required fields and click [Save].
  17. Validate the 'Pending Administrations' field no longer contains a row for "Medication A".
  18. Expand the 'Administration History' field and validate it contains a row for "Medication A" and that all columns are accurate.
Scenario 6: Medical Note - Order an In-Office Administration as "Provider" - Edit/Administer as "Nurse"
Specific Setup:
  • The 'Avatar CWS->Medication Inventory Management->->->->Enable Medication Inventory Management' registry setting must be set to "Y".
  • There must be at least one value in the Other CWS Tabled Files ‘(74101) Inventory Location’ dictionary. (Location A)
  • Please log out of the application and log back in after completing the above configuration.
  • A 'Medication Administration' procedure-type service code must be configured in the 'Service Codes' form. (Medication A)
  • "Medication A" must have a template defined in the 'Medication Inventory Management' form. (Template A)
  • In the 'Medication Inventory Management' form, inventory for "Template A" must be received to "Location A". (Inventory A)
  • An outpatient program must exist. (Program A)
  • A client must have an active episode in "Program A". (Client A)
  • Two users must exist. (User A) (User B).
  • "User A" who is configured as a "Provider".
  • "User B" who is configured as a "Nurse".
Steps
  1. Log into the application as "User A".
  2. Search for and select "Client A" and navigate to 'Medical Note'.
  3. Click [Add Note] and create a new note.
  4. Select the 'Document' tab and then navigate to the 'In-Office Administrations' section.
  5. Click [Add], search for and select "Medication A" from the 'In-Office Administrations Search' field, and click [Continue].
  6. Validate the 'Dose', 'Unit', and 'Route' fields automatically populate based on the entries made in "Template A".
  7. Populate any remaining required fields and click [Order].
  8. Validate the 'Pending Administrations' field contains a row for "Medication A" and click [Save Draft].
  9. Log out of the application and then log in as "User B".
  10. Search for and select "Client A" and navigate to the 'Medical Note'.
  11. Click [Select Note] and select the newly created note.
  12. Select the 'Document' tab and then navigate to the 'In-Office Administrations' section.
  13. Validate the 'Pending Administrations' field contains a row for "Medication A".
  14. Click the ellipses under the 'Action' column for "Medication A" and click [Administer].
  15. Validate, in the first section, the 'Dose', 'Unit', and 'Route' fields are correctly populated and that all fields are disabled.
  16. Validate the 'Entered By' and 'Ordered By' fields contain "User A" and the 'Administered By' field contains "User B".
  17. Click the 'Lot Number Search' button and validate the 'Lot Number Manager' dialog is launched.
  18. Select the row for "Inventory A" and click [Select].
  19. Validate the 'Lot Number', 'Manufacturer', 'Expiration Date', and 'NDC" are all correctly populated and disabled.
  20. Populate all remaining required fields and click [Save].
  21. Validate the 'Pending Administrations' field no longer contains a row for "Medication A".
  22. Expand the 'Administration History' field and validate it contains a row for "Medication A" and that all columns are accurate.
  23. Log out of the application and then log in as "User A".
  24. Search for and select "Client A" and navigate to the 'Medical Note'.
  25. Click [Select Note] and select the newly created note.
  26. Select the 'Document' tab and then navigate to the 'In-Office Administrations' section.
  27. Validate the 'Pending Administrations' field no longer contains a row for "Medication A".
  28. Expand the 'Administration History' field and validate it contains a row for "Medication A" and that all columns are accurate.
Scenario 7: Medical Note - Immunizations - Edit; Cancel; Grouping
Specific Setup:
  • The 'Avatar CWS->Medication Inventory Management->->->->Enable Medication Inventory Management' registry setting must be set to "Y".
  • There must be at least one value in the Other CWS Tabled Files ‘(74101) Inventory Location’ dictionary. (Location A)
  • Please log out of the application and log back in after completing the above configuration.
  • Two 'Vaccination/Immunization' procedure type service codes must be configured in the 'Service Codes' form. (Immunization A)(Immunization B).
  • "Immunization A" must have a template defined in the 'Medication Inventory Management' form. (Template A)
  • In the 'Medication Inventory Management' form, inventory for "Template A" must be received to "Location A" and the 'Manufacturer of Vaccine (MVX)' and 'Vaccine Code (CVX)' fields must be populated. (Inventory A)
  • An outpatient program configured as a 'Primary Care' program in the 'Program Maintenance' form must exist. (Program A)
  • A client must have an active episode in "Program A". (Client A)
Steps
  1. Search for and select "Client A" and navigate to the 'Medical Note'.
  2. Click [Add Note] and create a new 'Primary Care' note.
  3. Select the 'Document' tab and then navigate to the 'Immunizations' section.
  4. Click [Add] and then [Order Immunizations], select "Immunization A" from the 'Immunization Search' field and click [Continue].
  5. Fill in any required fields and click [Order].
  6. Click [Add] and then [Order Immunizations], select "Immunization B" from the 'Immunization Search' field and click [Continue].
  7. Fill in any required fields and click [Order].
  8. Click the ellipses under the 'Action' column for "Immunization A" and click [Edit].
  9. Change the values for the 'Dose' and 'Route' fields and click [Update].
  10. Click the ellipses under the 'Action' column for "Immunization B" and click [Cancel].
  11. Validate the 'Cancel Pending Administration' dialog appears and contains: "Are you sure you want to cancel this pending administration? Canceling this will permanently remove this pending administration."
  12. Click [Continue], populate the 'Comments' field and click [Save].
  13. Validate the 'Pending Immunizations' section only contains a row for "Immunization A".
  14. Click the ellipses under the 'Action' column for "Immunization A" and click [Administer].
  15. Validate, in the first section, the 'Dose', 'Unit', and 'Route' fields are correctly populated according to the edited values, and that all fields are disabled.
  16. Select "Facility" from the 'Provided By' field.
  17. Click the 'Lot Number Search' button and validate the 'Lot Number Manager' dialog is launched.
  18. Select the row for "Inventory A" and click [Select].
  19. Validate all fields in the "Administration Details' section are populated correctly.
  20. Populate any remaining required fields and click [Save].
  21. Expand the 'Immunization History' field and validate it contains a row for "Immunization A" and all columns are correctly populated.
  22. Click [Add] and then [Order Immunizations], select "Immunization A" from the 'Immunization Search' field and click [Continue].
  23. Populate any required fields and click [Administer].
  24. Set the 'Provided By' field to "Facility".
  25. Click the 'Lot Number Search' button and validate the 'Lot Number Manager' dialog is launched.
  26. Select the row for "Inventory A" and click [Select].
  27. Validate all fields in the "Administration Details' section are populated correctly.
  28. Populate any remaining required fields and click [Save].
  29. Click [Group By Vaccine] in the 'Immunization History' section.
  30. Validate that the 2 immunization administrations for "Immunization A" are grouped together.
Scenario 8: Medical Note - Order/Administer an Immunization in Single Workflow - Void Administration - Reconcile Inventory
Specific Setup:
  • The 'Avatar CWS->Medication Inventory Management->->->->Enable Medication Inventory Management' registry setting must be set to "Y".
  • There must be at least one value in the Other CWS Tabled Files ‘(74101) Inventory Location’ dictionary. (Location A)
  • Please log out of the application and log back in after completing the above configuration.
  • A 'Vaccination/Immunization' procedure-type service code must be configured in the 'Service Codes' form. (Immunization A)
  • "Immunization A" must have a template defined in the 'Medication Inventory Management' form. (Template A)
  • In the 'Medication Inventory Management' form, inventory for "Template A" must be received to "Location A" and the 'Manufacturer of Vaccine (MVX)' and 'Vaccine Code (CVX) fields but be populated. (Inventory A)
  • An outpatient program that is configured to be a 'Primary Care' program in the 'Program Maintenance' form must exist. (Program A)
  • A client must have an active episode in "Program A". (Client A)
Steps
  1. Search for and select "Client A" and navigate to the 'Medical Note'.
  2. Click [Add Note] and create a new 'Primary Care' note.
  3. Select the 'Document' tab and then navigate to the 'Immunizations' section.
  4. Click [Add], select "Immunization A" from the 'Immunization Search' field and click [Continue].
  5. Validate the 'Dose', 'Unit', and 'Route' fields automatically populate based on the entries made in "Template A".
  6. Fill in any remaining required fields and click [Administer].
  7. Select "Facility" from the 'Provided By' field.
  8. Click the 'Lot Number Search' button and validate the 'Lot Number Manager' dialog is launched.
  9. Select the row for "Inventory A" and click [Select].
  10. Validate the fields in the 'Administration Details' section are all accurately populated.
  11. Fill in any remaining required fields and click [Save].
  12. Validate the 'Pending Administrations' field does not contain a row for "Immunization A".
  13. Expand the 'Immunization History' field and validate it contains a row for "Immunization A" and that all columns are accurate.
  14. Click the ellipses under the 'Action' column for "Immunization A" and click [Void].
  15. Populate the 'Comments' field and click [Save].
  16. Validate the 'Immunization History' field still contains a row for "Immunization A" and that the 'Status' column shows "Voided".
  17. Access the 'Medication Inventory Management' form.
  18. Click [Adjust Inventory] and select the row for "Inventory A" from the 'Select Row' field.
  19. Validate that the 'Event Log' field contains a row for the previously given administration.
  20. Validate the 'Current Balance' is correctly calculated.
  21. Select 'Add to inventory' from the 'Event Type' field.
  22. Set the 'Quantity' field, such that when added to the current balance, the total is equal to the amount originally added to inventory.
  23. Click [Submit].
Scenario 9: Medical Note - Complete a Pending Immunization After a Note Is Finalized - Pediatric Full Workflow
Specific Setup:
  • The 'Avatar CWS->Medication Inventory Management->->->->Enable Medication Inventory Management' registry setting must be set to "Y".
  • The Other CWS Tabled Files '(74101) Inventory Location’ dictionary must contain at least one value. (Location A)
  • Please log out of the application and log back in after completing the above configuration.
  • Two "Vaccination/Immunization" procedure-type service codes must be configured in the 'Service Codes' form. (Medication A and Medication B)
  • "Medication A" and "Medication B" must have a template defined in the 'Medication Inventory Management' form. (Template A and Template B)
  • In the 'Medication Inventory Management' form inventory for "Template A" and "Template B" must be received to "Location A". (Inventory A and Inventory B)
  • An outpatient program must exist that is configured as a "Primary Care Program". (Program A)
  • A client must have an active episode that is associated with "Program A" and is a pediatric patient. (Client A)
Steps
  1. Search for and select "Client A" and navigate to the 'Medical Note'.
  2. Click [Add Note].
  3. Create a 'Primary Care' note.
  4. Select the ‘Document’ tab.
  5. Select ‘Immunizations’.
  6. Click [Add] and select "Medication A" from the 'Immunization Search' field.
  7. Validate the 'Dose', 'Unit', and 'Route' fields automatically populate based on the entries made in "Template A".
  8. Fill in any remaining required fields and click [Order].
  9. Validate the 'Pending Administrations' field contains a row for "Medication A"
  10. Click [Add] and select "Medication B" from the 'Immunization Search' field.
  11. Validate the 'Dose', 'Unit', and 'Route' fields automatically populate based on the entries made in "Template B".
  12. Fill in any remaining required fields and click [Administer].
  13. Validate, in the first section, the 'Dose', 'Unit', and 'Route' fields are correctly populated with the updated values and that all fields are disabled.
  14. Select "Yes" for the 'Consent Obtained' radio button.
  15. Select "Not VFC eligible" from the 'VFC Eligibility Code' field.
  16. Select "Facility" from the 'Provided By' field.
  17. Click the 'Lot Number Search' button and validate the 'Lot Number Manager' dialog is launched.
  18. Select the row for "Inventory B" and click [Select].
  19. Validate the 'Lot Number', 'Manufacturer', 'Expiration Date', and 'NDC' are all correctly populated and disabled.
  20. Fill in any remaining required fields and click [Save].
  21. Expand the 'Immunization History' field and validate it contains a row for "Medication B" and that all columns are accurate.
  22. Populate any remaining required sections in the 'Document' tab.
  23. Select the ‘Finalize’ tab.
  24. Populate all required fields and click [Generate Note].
  25. Validate the ‘Note Summary’ is displayed and contains the appropriate information and click [Sign Off].
  26. Validate the 'Progress Note' is displayed and click [Accept], set the ‘Password’ field to the appropriate value, and click [Verify].
  27. Refresh Medical Note.
  28. Click [Add Note].
  29. Create a 'Primary Care' note.
  30. Select the 'Document' tab and navigate to the 'Immunization' section.
  31. Validate the 'Pending Administrations' field contains a row for "Medication A"
  32. Click the ellipses under the 'Action' column for "Medication A" and click [Administer].
  33. Validate, in the first section, the 'Dose', 'Unit', and 'Route' fields are correctly populated with the updated values and that all fields are disabled.
  34. Select "Yes" for the 'Consent Obtained' field.
  35. Select "Not VFC eligible" from the 'VFC Eligibility Code' field.
  36. Select "Facility" from the 'Provided By' field.
  37. Click the 'Lot Number Search' button and validate the 'Lot Number Manager' dialog is launched.
  38. Select the row for "Inventory A" and click [Select].
  39. Validate the 'Lot Number', 'Manufacturer', 'Expiration Date', and 'NDC' are all correctly populated and disabled.
  40. Populate all remaining required fields and click [Save].
  41. Expand the 'Immunization History' field and validate it contains a row for "Medication A" and that all columns are accurate.
Scenario 10: Medical Note - Administering an immunization when 'Inventory Management' is disabled
Specific Setup:
  • The 'Avatar CWS->Medication Inventory Management->->->->Enable Medication Inventory Management' registry setting must be set to "N".
  • Please log out of the application and log back in after completing the above configuration.
  • A 'Vaccination/Immunization' procedure-type service code must be configured in the 'Service Codes' form. (Immunization A)
  • An outpatient program configured as a 'Primary Care' program in the 'Program Maintenance' form must exist. (Program A)
  • A client must have an active episode in "Program A". (Client A)
Steps
  1. Search for and select "Client A" and navigate to the 'Medical Note'.
  2. Click [Add Note] and create a new 'Primary Care' note.
  3. Select the 'Document' tab and then navigate to the 'Immunizations' section.
  4. Click [Add] and then [Order Immunizations], select "Immunization A" from the 'Immunization Search' field and click [Continue].
  5. Fill in any required fields and click [Administer].
  6. Select "Facility" from the 'Provided By' field.
  7. Fill in any remaining required fields and click [Save].
  8. Expand the 'Immunization History' field and validate it contains a row for "Immunization A" and all columns are correctly populated.
  9. Complete any remaining required sections in the 'Document' tab.
  10. Select the 'Finalize' tab and click [End Face-to-Face Time].
  11. Choose one of the options in the 'CPT Code Selected' field and click [Generate Note].
  12. Validate the 'Note Summary' field shows the correct information.
  13. Set the 'Completion Status' field to "Completed" and sign off on the note.
Scenario 11: Medical Note - Service Code Upload - Medication Administration and Vaccine/Immunization Procedure Types
Specific Setup:
  • A service code upload file must exist that contains two new service codes, one with "Vaccination/Immunization" and one with "Medication Administration" selected in the 'Procedure Type' field, and must be placed on the server where the application resides. (File A)
Steps
  1. Access the 'Service Code Upload Process' form.
  2. Click [Select File].
  3. Select and open "File A".
  4. Select "Compile" in the 'Compile or Post' field.
  5. Select "Yes" in the 'Override Existing Service Codes' field.
  6. Click [Submit].
  7. Validate a "Compiled completed" message is displayed and click [OK].
  8. Select "Post" in the 'Compile or Post' field and click [Submit].
  9. Validate a "Post completed" message is displayed and click [OK].
  10. Access the 'Service Codes' form.
  11. Select "Edit" in the 'Add New or Edit Existing' field.
  12. Search for and select the first service code created and ensure that "Yes" is selected in the 'Is This Service A Procedure' field and that "Vaccination/Immunization" is selected in the 'Procedure Type' field.
  13. Search for and select the second service code created and ensure that "Medication Administration" is selected in the 'Procedure Type' field.
Scenario 12: Medical Note - Receiving new inventory - Administering an In-Office Administration - Entering a 'Reaction'
Specific Setup:
  • The 'Avatar CWS->Medication Inventory Management->->->->Enable Medication Inventory Management' registry setting must be set to "Y".
  • There must be at least one value in the Other CWS Tabled Files ‘(74101) Inventory Location’ dictionary. (Location A)
  • Please log out of the application and log back in after completing the above configuration.
  • A 'Medication Administration' procedure-type service code must be configured in the 'Service Codes' form. (Medication A)
  • An outpatient program must exist. (Program A)
  • A client must have an active episode in "Program A". (Client A)
Steps
  1. Access the 'Medication Inventory Management' form.
  2. Click [Template Definition] and select "Add New" from the 'Select Template Definition' field.
  3. Set the 'Service Code' field to "Medication A".
  4. Populate any remaining required fields and click [Submit].
  5. Click [Medication Definition] and select the previously made template from the 'Select Template' field.
  6. Select "Location A" from the 'Inventory Location' field.
  7. Set the 'Lot #' field to "72293".
  8. Set the 'Expiration Date' field to a future date.
  9. Set the 'Container Size' field to 50.
  10. Populate any remaining required fields and click [Submit].
  11. Click [Adjust Inventory] and set the 'Lot #' field to "72293"
  12. Validate the new medication definition is shown in the 'Inventory Items' field.
  13. Select the new medication definition from the 'Select Row' field.
  14. Select "Add to inventory" from the 'Event Type' field.
  15. Validate "Add (A)" is selected from the 'Impact' field and that the field is disabled.
  16. Set the 'Quantity' field to "50" and click [Submit] and close the form.
  17. Search for and select "Client A" and navigate to the 'Medical Note'.
  18. Click [Add Note] and create a new note.
  19. Select the 'Document' tab and then navigate to the 'In-Office Administrations' section.
  20. Click [Add], search for and select "Medication A" from the 'In-Office Administrations Search' field and click [Continue].
  21. Validate the 'Dose', 'Unit', and 'Route' fields automatically populate based on selections made in the "Template Definition" section of the 'Medication Inventory Management' form.
  22. Fill in any remaining required fields and click [Administer].
  23. Click the 'Lot Number Search' button and validate the 'Lot Number Manager' dialog is launched.
  24. Select the row for new medication definition and click [Select].
  25. Validate the 'Administration Details' section is correctly populated based on selections made in the "Medication Definition" section of the 'Medication Inventory Management' form.
  26. Populate any remaining required fields and click [Save].
  27. Expand the 'Administration History' field and validate it contains a row for "Medication A" and that all columns are accurate.
  28. Click the ellipses under the 'Action' column for "Medication A" and click [Document Reaction].
  29. Set the 'Reaction' field to any value and click [Save].
  30. Click the ellipses under the 'Action' column for "Medication A" and click [View Details].
  31. Validate the details are read-only, that all fields are correctly populated and then click [Cancel].
  32. Access the 'Medication Inventory Management' form.
  33. Click [Adjust Inventory] and select the new medication definition from the 'Select Row' field.
  34. Validate that the 'Event Log' field contains a row for the previously given administration.
  35. Validate the 'Current Balance' is correctly calculated.
Scenario 13: Medical Note - Refuse medications that are listed in under the 'Pending Medications' sub-section of the 'In-Office Administrations' section. Confirm details in Progress Note.
Specific Setup:
  • A 'Medication Administration' procedure-type service code must be configured in the 'Service Codes' form. (Medication A)
  • An outpatient program must exist. (Program A)
  • A client must have an active episode associated with "Program A". (Client A)
Steps
  1. Search for and select "Client A" and navigate to the 'Medical Note'.
  2. Click [Add Note] and create a new note.
  3. Select the 'Document' tab and then navigate to the 'In-Office Administrations' section.
  4. Click [Add], select "Medication A" from the 'In-Office Administrations Search' field and click [Continue].
  5. Populate any required fields and click [Order].
  6. Validate the 'Pending Administrations' field contains a row for "Medication A".
  7. Click the ellipses under the 'Action' column for "Medication A" and click [Refuse].
  8. Select any value from the 'Refused Reason' field and click [Save].
  9. Validate the 'Pending Administrations' field no longer contains a row for "Medication A".
  10. Expand the 'Administration History' field and validate it contains a row for "Medication A" and that "Refused" is shown in the 'Status' column.
  11. Click the ellipses under the 'Action' column for "Medication A" and click [View Details].
  12. Validate the 'Refused Reason' field matches to what was previously selected and click [Cancel].
  13. Select the 'Finalize' tab and click [Generate Note].
  14. Validate that the 'Note Summary' field contains a section for In-Office Administrations and "Medication A" is listed and shows as "Refused".
Scenario 14: Medical Note - Cancel a medication that is listed in under the 'Pending Medications' sub-section of the 'In-Office Administrations' section.
Specific Setup:
  • A 'Medication Administration' procedure-type service code must be configured in the 'Service Codes' form. (Medication A)
  • An outpatient program must exist. (Program A)
  • A client must have an active episode associated with "Program A". (Client A)
Steps
  1. Search for and select "Client A" and navigate to the 'Medical Note'.
  2. Click [Add Note] and create a new note.
  3. Select the 'Document' tab and then navigate to the 'In-Office Administration' section.
  4. Click [Add], search for and select "Medication A" from the 'In-Office Administration Search' field and click [Continue].
  5. Populate any required fields and click [Order].
  6. Validate that a row for "Medication A" is listed in the 'Pending Immunizations' section.
  7. Click the ellipses under the 'Action' column for "Medication A" and click [Cancel].
  8. Validate the 'Cancel Pending Administration' dialog contains "Are you sure you want to cancel this pending administration? Canceling this will permanently remove this pending administration." and click [Continue].
  9. Populate the 'Comments' field and click [Save].
  10. Validate the 'Pending Administrations' field no longer contains a row for "Medication A".
  11. Expand the 'Administration History' field and validate it does not contain a row for "Medication A".
  12. Click [Select Note] and then click [Delete] for the newly created note.
  13. Validate the 'Delete Note' dialog contains "Are you sure you want to delete this draft note? Please make sure to void any administrations or procedures completed during the visit, as necessary."
  14. Click [Delete Note] and validate a 'Start' button now shows for the newly created note.
Scenario 15: Medical Note - Complete In-Office Administration - Delete Note - Void Administration - Reconcile Inventory
Specific Setup:
  • The 'Avatar CWS->Medication Inventory Management->->->->Enable Medication Inventory Management' registry setting must be set to "Y".
  • There must be at least one value in the Other CWS Tabled Files ‘(74101) Inventory Location’ dictionary. (Location A)
  • Please log out of the application and log back in after completing the above configuration.
  • A 'Medication Administration' procedure-type service code must be configured in the 'Service Codes' form. (Medication A)
  • "Medication A" must have a template defined in the 'Medication Inventory Management' form. (Template A)
  • In the 'Medication Inventory Management' form, inventory for "Template A" must be received to "Location A". (Inventory A)
  • An outpatient program must exist. (Program A)
  • A client must have an active episode in "Program A". (Client A)
Steps
  1. Search for and select "Client A" and navigate to the 'Medical Note'.
  2. Click [Add Note] and create a new note.
  3. Select the 'Document' tab and then navigate to the 'In-Office Administrations' section.
  4. Click [Add], search for and select "Medication A" from the 'In-Office Administrations Search' field and click [Continue].
  5. Validate the 'Dose', 'Unit', and 'Route' fields automatically populate based on the entries made in "Template A".
  6. Fill in any remaining required fields and click [Administer].
  7. Click the 'Lot Number Search' button and validate the 'Lot Number Manager' dialog is launched.
  8. Select the row for "Inventory A" and click [Select].
  9. Populate any remaining required fields and click [Save].
  10. Expand the 'Administration History' field and validate it contains a row for "Medication A" and that all columns are accurate.
  11. Click [Select Note] and then click [Delete] for the newly created note.
  12. Validate the 'Delete Note' dialog contains "Are you sure you want to delete this draft note? Please make sure to void any administrations or procedures completed during the visit, as necessary.".
  13. Click [Delete Note] and validate an error message is displayed at the top of the medical note stating "Completed procedures/administrations that updated medication inventory must be voided first before the visit can be deleted.".
  14. Select the 'Document' tab and then navigate to the 'In-Office Administrations' section.
  15. Expand the 'Administration History' field, click the ellipses under the 'Action' column for "Medication A" and click [Void].
  16. Populate the 'Comments' field and click [Save].
  17. Validate a passive alert is displayed at the top of the document tab stating "Void Administration: Voiding an administration does not update inventory. Please reconcile your inventory as needed."
  18. Validate the 'Status' column shows "Voided" for "Medication A".
  19. Click [Select Note] and then click [Delete] for the newly created note.
  20. Validate the 'Delete Note' dialog contains "Are you sure you want to delete this draft note? Please make sure to void any administrations or procedures completed during the visit, as necessary." and click [Delete Note].
  21. Access the 'Medication Inventory Management' form.
  22. Click [Adjust Inventory] and select the row for "Inventory A" from the 'Select Row' field.
  23. Validate that the 'Event Log' field contains a row for the previously given administration.
  24. Validate the 'Current Balance' is correctly calculated.
  25. Select 'Add to inventory' from the 'Event Type' field.
  26. Set the 'Quantity' field, such that when added to the current balance, the new balance will be equal to the amount prior to the administration and click [Submit].
Scenario 16: Medical Note - Administering a Pediatric Immunization when 'Inventory Management' is enabled
Specific Setup:
  • The 'Avatar CWS->Medication Inventory Management->->->->Enable Medication Inventory Management' registry setting must be set to "Y".
  • There must be at least one value in the Other CWS Tabled Files ‘(74101) Inventory Location’ dictionary. (Location A)
  • Please log out of the application and log back in after completing the above configuration.
  • Two 'Vaccination/Immunization' procedure-type service codes must be configured in the 'Service Codes' form. (Immunization A) (Immunization B)
  • "Immunization A" must have a template defined in the 'Medication Inventory Management' form. (Template A)
  • In the 'Medication Inventory Management' form, inventory for "Template A" must be received to "Location A" and the 'Manufacturer of Vaccine (MVX)' and 'Vaccine Code (CVX)' fields must be populated. (Inventory A)
  • An outpatient program configured as a 'Primary Care' program in the 'Program Maintenance' form must exist. (Program A)
  • A client must have an active episode in "Program A". (Client A)
  • "Client A" must be under the age of 19.
Steps
  1. Search for and select "Client A" and navigate to the 'Medical Note'.
  2. Navigate to the 'Immunizations' section of the Facesheet.
  3. Click [Add] and then [Historical Immunization Record].
  4. Select any immunization listed in the 'Historical Immunization Record Search' field.
  5. Fill out any required fields and click [Save].
  6. Validate the 'Immunization History' section contains a row for the new historical immunization record.
  7. Click [Add Note] and create a 'Primary Care' note.
  8. Select the 'Document' tab and then navigate to the 'Immunization' section.
  9. Click [Add] and then [Order Immunizations], select "Immunization A" from the 'Immunizations Search' field and click [Continue].
  10. Validate the 'Dose', 'Unit', and 'Route' fields automatically populate based on the entries made in "Template A".
  11. Fill in any remaining required fields and click [Order].
  12. Validate the 'Pending Immunizations' field contains a row for "Immunization A"
  13. Click the ellipses under the 'Action' column for "Immunization A" and click [Edit].
  14. Clear the 'Diagnosis' field, enter in a new value and click [Update].
  15. Click the ellipses under the 'Action' column for "Immunization A" and click [Administer].
  16. Validate the 'Diagnosis' field contains the updated value.
  17. Validate the following fields, restricted to pediatric clients only, show and are required:
  18. 'Consent Obtained'.
  19. 'VFC Eligibility Code'.
  20. 'Funding Source'.
  21. Click the 'Lot Number Search' button and validate the 'Lot Number Manager' dialog is launched.
  22. Select the row for "Inventory A" and click [Select].
  23. Fill in any remaining required fields and click [Save].
  24. Validate the 'Pending Immunizations' field no longer contains a row for "Immunization A".
  25. Expand the 'Immunization History' field and validate it contains a row for "Immunization A" and that all columns are accurate.
  26. Click the ellipses under the 'Action' column for "Immunization A" and click [Document Reaction].
  27. Populate the 'Reaction' field and click [Save].
  28. Click the ellipses under the 'Action' column for "Immunization A" and click [View Details].
  29. Validate all fields are correctly populated and disabled and click [Cancel].
  30. Click [Add] and then [Order Immunizations], select "Immunization B" from the 'Immunizations Search' field and click [Continue].
  31. Populate all required fields and click [Order].
  32. Select the 'Finalize' tab and click [Generate Note].
  33. Validate the 'Note Summary' field contains a section for pending immunizations and has "Immunization B" listed.
  34. Validate the 'Note Summary' field contains a section for administered in-office immunizations and has "Immunization A" listed.
  35. Validate the 'Note Summary' field does not contain the new Historical Immunization Record.
  36. Select the 'Document' tab and then navigate to the 'Immunization' section.
  37. Click the ellipses under the 'Action' column for "Immunization B" and click [Cancel].
  38. Validate the 'Cancel Pending Administration' dialog appears and contains: "Are you sure you want to cancel this pending administration? Canceling this will permanently remove this pending administration."
  39. Click [Continue], populate the 'Comments' field and click [Save].
  40. Select the 'Finalize' tab and click [Generate Note].
  41. Validate the 'Note Summary' field does not contain a section for pending immunizations.
Scenario 17: Medical Note - Administering a Pediatric Immunization when 'Inventory Management' is disabled
Specific Setup:
  • The 'Avatar CWS->Medication Inventory Management->->->->Enable Medication Inventory Management' registry setting must be set to "N".
  • Please log out of the application and log back in after completing the above configuration.
  • A 'Vaccination/Immunization' procedure-type service code must be configured in the 'Service Codes' form. (Medication A)
  • An Outpatient program must exist that is configured as a 'Primary Care' program. (Program A)
  • A client must have an active episode associated with "Program A". (Client A)
  • "Client A" must be 18 years of age or younger.
Steps
  1. Search for and select "Client A" and navigate to the 'Medical Note'.
  2. Click [Add Note].
  3. Create a 'Primary Care' note.
  4. Select the 'Document' tab and then navigate to the 'Immunization' section.
  5. Populate all required fields and click [Order].
  6. Validate the 'Pending Administrations' field contains a row for "Medication A".
  7. Click the ellipses under the 'Action' column for "Medication A" and click [Administer].
  8. Select "Yes" for the 'Consent Obtained' radio button.
  9. Select "Not VFC eligible" from the 'VFC Eligibility Code' field.
  10. Select "Other" from the 'Provided By' field.
  11. Populate all required fields and click [Save].
  12. Expand the 'Immunization History' field and validate it contains a row for "Medication A" and that all columns are accurate.
  13. Click the ellipses under the 'Action' column for "Medication B" and click [Document Reaction].
  14. Select any value for the 'Reaction' field and click [Save].
  15. Click the ellipses under the 'Action' column for "Medication B" and click [View Details].
  16. Validate the 'Reaction' field contains the correct value and click [Close]
Scenario 18: Medical Note - Add Historical Immunization Record - Validate through 'Client Health Maintenance' form
Specific Setup:
  • A client must have an active episode. (Client A)
Steps
  1. Search for and select "Client A" and navigate to the 'Medical Note'.
  2. Navigate to the 'Immunizations' section of the Facesheet.
  3. Click [Add] and then [Historical Immunization Record].
  4. Select any immunization listed in the 'Historical Immunization Record Search' field.
  5. Fill out any required fields and click [Save].
  6. Validate the 'Immunization History' section contains a row for the new historical immunization record.
  7. Access the 'Client Health Maintenance' form.
  8. Search for and select "Client A" from the 'Client ID' field.
  9. Click [List Immunizations] and validate the 'Immunizations History and Alerts' report is launched.
  10. Validate the 'Immunization History' section contains data for the new historical immunization record and click [Close Report].
  11. Click [Update] and then [New Row].
  12. Populate the 'Vaccine', 'Dose', 'Provided By' and 'Date' cells and click [Save].
  13. Navigate to the 'Medical Note'.
  14. Navigate to the 'Immunizations' section of the Facesheet.
  15. Validate the 'Immunization History' section contains a row for both new immunization records.
Scenario 19: Medical Note - Add Historical Records - In Office Administration
Specific Setup:
  • A procedure-type service code must be configured in the 'Service Codes' form. (Medication A)
  • An Outpatient program must exist. (Program A)
  • A client must have an active episode associated with "Program A". (Client A)
Steps
  1. Search for and select "Client A" and navigate to the 'Medical Note'.
  2. Click [Add Note].
  3. Create a 'Psychiatry' note.
  4. Select the 'Document' tab and then navigate to the 'Procedure' section.
  5. Click [Add] and select "Medication A" from the 'Procedure Search' field.
  6. Select ‘Diagnosis’ and enter a diagnosis.
  7. Click 'Complete' field.
  8. Click 'Routine' field.
  9. Populate all remaining required fields and click [Save].
  10. Validate the 'Current Procedures' field contains a row for "Medication A".
  11. Access the 'Service Codes' form.
  12. Select "Edit" in the 'Add New or Edit Existing' field.
  13. Search for and select "Medication A" and select "Medication Administration" in the 'Procedure Type' field.
  14. Click [Submit].
  15. Validate a message is displayed stating "Service Codes has completed. Do you wish to return to form?" and click [Yes].
  16. Refresh 'Medical Note'.
  17. Click [Select Note] and click [Edit].
  18. Select the 'Document' tab and then navigate to the 'In-Office Administration' section.
  19. Expand the 'Administration History' field.
  20. Validate the 'Historical Records' section is displayed and contains "Medication A".
Scenario 20: Medical Note - In-Office Administration - ToDo's - Administer and refusal
Specific Setup:
  • The 'Avatar CWS->Medication Inventory Management->->->->Enable Medication Inventory Management' registry setting must be set to "N".
  • Please log out of the application and log back in after completing the above configuration.
  • Two 'Medication Administration' procedure-type service codes must be configured in the 'Service Codes' form. (Medication A and Medication B)
  • An outpatient program must exist. (Program A)
  • A client must have an active episode in "Program A". (Client A)
  • Two users must exist in the application. (User A and User B)
  • "User A" is configured as a "Nurse" and "User B" is configured as a "Provider".
  • "User A" must be logged into the application.
Steps
  1. Search for and select "Client A" and navigate to the 'Medical Note'.
  2. Click [Add Note] and create a new note.
  3. Select the 'Document' tab and then navigate to the 'In-Office Administration' section.
  4. Click [Add] and select "Medication A" from the 'In-Office Administration Search' field.
  5. Populate any required fields and click [Order].
  6. Validate the 'Pending Administrations' field contains a row for "Medication A".
  7. Click [Add] and select "Medication B" from the 'In-Office Administration Search' field.
  8. Populate any required fields and click [Order].
  9. Validate the 'Pending Administrations' field contains a row for "Medication B".
  10. Click [Send To Do].
  11. Set "User B" in the 'To-Do Recipient'.
  12. Set the 'Notes' field to any value and click [Send].
  13. Log out of the application and log back in as "User B".
  14. Access the 'My To Do's' widget.
  15. Select "Client A" from the 'Additional ToDos' list and click [Review To Do Item].
  16. Click 'In-Office Administrations'.
  17. Validate the 'Pending Administrations' field contains a row for "Medication A".
  18. Click the ellipses under the 'Action' column for "Medication A" and click [Administer].
  19. Validate, in the first section, the 'Dose', 'Unit', and 'Route' fields are correctly populated and disabled.
  20. Populate any required fields and click [Save].
  21. Expand the 'Administration History' field and validate it contains a row for "Medication A" and that all columns are accurate.
  22. Click the ellipses under the 'Action' column for "Medication B" and click [Refuse].
  23. Select any value in the 'Refused Reason' field and click [Save].
  24. Expand the 'Administration History' field and validate it contains a row for "Medication B" with a status of 'Refused'.
Scenario 21: Medical Note - Inventory Management Enabled - Full Immunization Work Flow
Specific Setup:
  • The 'Avatar CWS->Medication Inventory Management->->->->Enable Medication Inventory Management' registry setting must be set to "Y".
  • There must be at least one value in the Other CWS Tabled Files ‘(74101) Inventory Location’ dictionary. (Location A)
  • Please log out of the application and log back in after completing the above configuration.
  • Two 'Vaccination/Immunization' procedure-type service codes must be configured in the 'Service Codes' form. (Medication A and Medication B)
  • "Medication A" and "Medication B" must have a template defined in the 'Medication Inventory Management' form. (Template A and Template B)
  • In the 'Medication Inventory Management' form inventory for "Template A" and "Template B" must be received to "Location A". (Inventory A and Inventory B)
  • An Outpatient program must exist that is configured as a primary care program. (Program A)
  • A client must have an active episode associated with "Program A". (Client A)
Steps
  1. Search for and select "Client A" and navigate to the 'Medical Note'.
  2. Click [Add Note] and create a 'Primary Care' note.
  3. Select the ‘Document’ tab.
  4. Enter a value in the ‘Chief Complaint’ field.
  5. Select ‘HPI’ and add a value along with symptoms.
  6. Select ‘Physical Exam’ and select the ‘Constitutional’ tab.
  7. Check off the appropriate values.
  8. Select ‘Diagnosis’ and enter a diagnosis.
  9. Select ‘Immunizations’.
  10. Click [Add] and select "Medication A" from the 'Immunization Search' field.
  11. Validate the 'Dose', 'Unit', and 'Route' fields automatically populate based on the entries made in "Template A".
  12. Fill in any remaining required fields and click [Order].
  13. Validate the 'Pending Administrations' field contains a row for "Medication A"
  14. Click [Add] and select "Medication B" from the 'Immunization Search' field.
  15. Validate the 'Dose', 'Unit', and 'Route' fields automatically populate based on the entries made in "Template B".
  16. Fill in any remaining required fields and click [Administer].
  17. Validate, in the first section, the 'Dose', 'Unit', and 'Route' fields are correctly populated with the updated values and that all fields are disabled.
  18. Click the 'Lot Number Search' button and validate the 'Lot Number Manager' dialog is launched.
  19. Select the row for "Inventory B" and click [Select].
  20. Validate the 'Lot Number', 'Manufacturer', 'Expiration Date', and 'NDC' are all correctly populated and disabled.
  21. Fill in any remaining required fields and click [Save].
  22. Expand the 'Immunization History' field and validate it contains a row for "Medication B" and that all columns are accurate.
  23. Click the ellipses under the 'Action' column for "Medication B" and click [Document Reaction].
  24. Select any value for the 'Reaction' field and click [Save].
  25. Click the ellipses under the 'Action' column for "Medication B" and click [View Details].
  26. Validate the 'Reaction' field contains the correct value and click [Close].
  27. Select the ‘Finalize’ tab.
  28. Populate all required fields and click [Generate Note].
  29. Validate the ‘Note Summary’ is displayed and contains the appropriate information and click [Sign Off].
  30. Validate the Document is displayed and click [Accept], set the ‘Password’ field to the appropriate value and click [Verify].
  31. Refresh Medical Note.
  32. Click [Add Note].
  33. Select "Primary Care" from the 'Appointment/Note Workflow' field.
  34. Select "Main Street Center" from the 'Site' field.
  35. Select "Program A" from the 'Service Program' field.
  36. Search for and select "Service Code A" from the 'Service Code' field.
  37. Fill out any remaining required fields and click [Save].
  38. Select the 'Document' tab and then navigate to the 'Immunization' section.
  39. Validate the 'Pending Administrations' field contains a row for "Medication A"
  40. Click the ellipses under the 'Action' column for "Medication A" and click [Administer].
  41. Validate, in the first section, the 'Dose', 'Unit', and 'Route' fields are correctly populated with the updated values and that all fields are disabled.
  42. Click the 'Lot Number Search' button and validate the 'Lot Number Manager' dialog is launched.
  43. Select the row for "Inventory A" and click [Select].
  44. Validate the 'Lot Number', 'Manufacturer', 'Expiration Date', and 'NDC' are all correctly populated and disabled.
  45. Fill in any remaining required fields and click [Save].
  46. Expand the 'Immunization History' field and validate it contains a row for "Medication A" and that all columns are accurate.
  47. Select the 'Facesheet' tab and then navigate to the 'Immunization' section.
  48. Validate "Medication A" and "Medication B" are displayed.
  49. Select the 'Document' tab and then navigate to the 'Immunization' section.
  50. Void the administrations of "Medication A" and "Medication B".
  51. Refresh Medical Note.
  52. Click [Select Note] and click [Delete].
  53. Validate the 'Delete Note' dialog is displayed and contains "Are you sure you want to delete this draft note. Please make sure to void any administrations or procedures completed during the visit, as necessary."
  54. Click [Delete Note].
Scenario 22: Medical Note - Order an Immunization as "Provider" - Edit/Administer as "Nurse"
Specific Setup:
  • The 'Avatar CWS->Medication Inventory Management->->->->Enable Medication Inventory Management' registry setting must be set to "Y".
  • There must be at least one value in the Other CWS Tabled Files ‘(74101) Inventory Location’ dictionary. (Location A)
  • Please log out of the application and log back in after completing the above configuration.
  • A 'Vaccination/Immunization' procedure-type service code must be configured in the 'Service Codes' form. (Immunization A)
  • "Immunization A" must have a template defined in the 'Medication Inventory Management' form. (Template A)
  • In the 'Medication Inventory Management' form, inventory for "Template A" must be received to "Location A" and the 'Manufacturer of Vaccine (MVX)' and 'Vaccine Code (CVX)' fields must be populated. (Inventory A)
  • An outpatient program configured as a 'Primary Care' program in the 'Program Maintenance' form must exist. (Program A)
  • A client must have an active episode in "Program A". (Client A)
  • Two users must exist. (User A) (User B).
  • "User A" who is configured as a "Provider".
  • "User B" who is configured as a "Nurse".
Steps
  1. Log into the application as "User A".
  2. Search for and select "Client A" and navigate to the 'Medical Note'.
  3. Click [Add Note] and create a 'Primary Care' note.
  4. Select the 'Document' tab and then navigate to the 'Immunization' section.
  5. Click [Add] and then [Order Immunizations], select "Immunization A" from the 'Immunizations Search' field and click [Continue].
  6. Validate the 'Dose', 'Unit', and 'Route' fields automatically populate based on the entries made in "Template A".
  7. Fill in any remaining required fields and click [Order].
  8. Validate the 'Pending Immunizations' field contains a row for "Immunization A" and click [Save Draft].
  9. Log out of the application and then log in as "User B".
  10. Search for and select "Client A" and navigate to the 'Medical Note'.
  11. Click [Select Note] and select the newly created 'Primary Care' note.
  12. Select the 'Document' tab and then navigate to the 'Immunizations' section.
  13. Validate the 'Pending Immunizations' field contains a row for "Immunization A".
  14. Click the ellipses under the 'Action' column for "Immunization A" and click [Administer].
  15. Validate, in the first section, the 'Dose', 'Unit', and 'Route' fields are correctly populated and that all fields are disabled.
  16. Validate the 'Entered By' and 'Ordered By' fields contains "User A" and the 'Administered By' field contains "User B".
  17. Select "Facility" from the 'Provided By' field.
  18. Click the 'Lot Number Search' button and validate the 'Lot Number Manager' dialog is launched.
  19. Select the row for "Inventory A" and click [Select].
  20. Validate all fields in the 'Administration Details' section are populated correctly.
  21. Fill in any remaining required fields and click [Save].
  22. Validate the 'Pending Immunizations' field no longer contains a row for "Immunization A".
  23. Expand the 'Immunization History' field and validate it contains a row for "Immunization A" and that all columns are accurate.
  24. Log out of the application and then log in as "User A".
  25. Search for and select "Client A" and navigate to the 'Medical Note'.
  26. Click [Select Note] and select the 'Primary Care' note.
  27. Select the 'Document' tab and then navigate to the 'Immunizations' section.
  28. Validate the 'Pending Immunizations' field no longer contains a row for "Immunization A".
  29. Expand the 'Immunization History' field and validate it contains a row for "Immunization A" and that all columns are accurate.
Scenario 23: Medical Note - Pediatric Immunization - ToDo's - Administer and refusal
Specific Setup:
  • The 'Avatar CWS->Medication Inventory Management->->->->Enable Medication Inventory Management' registry setting must be set to "N".
  • The Other CWS Tabled Files '(74101) Inventory Location’ dictionary must contain at least one value. (Location A)
  • Please log out of the application and log back in after completing the above configuration.
  • A generic 'Evaluation Management' service code must be configured in the 'Service Codes' form. (Service Code A)
  • A 'Medication Administration' procedure-type service code must be configured in the 'Service Codes' form. (Medication A)
  • A 'Vaccination/Immunization' procedure-type service code must be configured in the 'Service Codes' form. (Medication B)
  • An outpatient program must exist that is configured as a 'Primary Care' program. (Program A)
  • A client must have an active episode associated with "Program A" and is pediatric patient. (Client A)
  • Two users must exist in the application: One who is configured as a "Nurse" (User A) and one who is configured as a "Provider". (User A and User B).
  • "User A" must be logged into the application.
Steps
  1. Search for and select "Client A" and navigate to the 'Medical Note'.
  2. Click [Add Note].
  3. Create a 'Primary Care' note.
  4. Select the 'Document' tab and then navigate to the 'Immunization' section.
  5. Click [Add] and select "Medication A" from the 'Immunization Search' field.
  6. Populate all required fields and click [Order].
  7. Validate the 'Pending Administrations' field contains a row for "Medication A".
  8. Click [Add] and select "Medication B" from the 'Immunization Search' field.
  9. Populate all required fields and click [Order].
  10. Validate the 'Pending Administrations' field contains a row for "Medication B".
  11. Click [Send To Do].
  12. Set "User A" in the 'To-Do Recipient'.
  13. Set the 'Notes' field to any value and click [Send].
  14. Log out of the application and log back in as "User B".
  15. Access the 'My To Do's' widget.
  16. Select "Client A" from the 'Additional ToDos' list and click [Review To Do Item].
  17. Select the 'Immunization' section.
  18. Validate the 'Pending Administrations' field contains a row for "Medication A".
  19. Click the ellipses under the 'Action' column for "Medication A" and click [Administer].
  20. Validate, in the first section, the 'Dose', 'Unit', and 'Route' fields are correctly populated with the updated values and that all fields are disabled.
  21. Select "Yes" for the 'Consent Obtained' radio button.
  22. Select "Not VFC eligible" from the 'VFC Eligibility Code' field.
  23. Select "Facility" from the 'Provided BY' field.
  24. Populate all required fields and click [Save].
  25. Expand the 'Immunization History' field and validate it contains a row for "Medication A" and that all columns are accurate.
  26. Click the ellipses under the 'Action' column for "Medication B" and click [Refuse].
  27. Select any value for the 'Refused Reason' field and click [Save].
  28. Expand the 'Immunization History' field and validate it contains a row for "Medication B" with a status of "Refused".
Topics
• Medical Note • NX • Service Code • To Dos
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:
  • Ambulatory Progress Notes
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 10 Summary | Details
Treatment Plan - Search Filter
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Treatment Plan
  • Treatment Plan Definition
  • Dynamic Form Library Definition
  • Dynamic Form Treatment Plan Setup
Scenario 1: Treatment Plan - Validate the 'Apply Search Results By' filter
Specific Setup:
  • Please note: this is for Avatar NX only.
  • A client is enrolled in an existing episode (Client A).
  • Must have Treatment Plan libraries configured with problems, goals, objectives, and interventions.
  • Document routing is enabled on the 'Treatment Plan' form.
Steps
  1. Select "Client A" and access the 'Treatment Plan' form.
  2. Enter the desired date in the 'Plan Date' field.
  3. Select the desired value in the 'Plan Type' field.
  4. Select "Draft" in the 'Treatment Plan Status' field.
  5. Click [Launch Plan].
  6. Validate the Treatment Plan libraries are listed on the left-hand side.
  7. Validate the 'Apply Search Results By' field is displayed and contains the following values:
  8. Search All - this will be the existing search functionality that performs a search on all library items
  9. Problem - this will return applicable problems and their child elements
  10. Goal - this will return applicable goals and their child elements
  11. Objective - this will return applicable objectives and their child elements
  12. Intervention - this will return applicable interventions
  13. Select "Search All" in the 'Apply Search Results By' field.
  14. Enter the desired value in the 'Search' field.
  15. Validate all applicable treatment plan library items are returned as expected.
  16. Remove the value from the 'Search' field.
  17. Select "Problem" in the 'Apply Search Results By' field.
  18. Enter the desired value in the 'Search' field.
  19. Validate all applicable problems are returned as expected.
  20. Validate applicable child items for the problems display in a collapsed state, but can be expanded.
  21. Drag the desired problem to the 'Treatment Plan' field.
  22. Enter the desired value in the 'Problem Code' field.
  23. Select the desired value in the 'Status (Problem List)' field.
  24. Select the desired value in the 'Status' field.
  25. Remove the value from the 'Search' field.
  26. Select "Goal" in the 'Apply Search Results By' field.
  27. Enter the desired value in the 'Search' field.
  28. Validate all applicable goals are returned as expected.
  29. Validate applicable child items for the goals display in a collapsed state, but can be expanded.
  30. Drag the desired goal to the 'Treatment Plan' field.
  31. Select the desired value in the 'Status' field.
  32. Remove the value from the 'Search' field.
  33. Select "Objective" in the 'Apply Search Results By' field.
  34. Enter the desired value in the 'Search' field.
  35. Validate all applicable objectives are returned as expected.
  36. Validate applicable child items for the objectives display in a collapsed state, but can be expanded.
  37. Drag the desired objective to the 'Treatment Plan' field.
  38. Select the desired value in the 'Status' field.
  39. Remove the value from the 'Search' field.
  40. Select "Intervention" in the 'Apply Search Results By' field.
  41. Enter the desired value in the 'Search' field.
  42. Validate all applicable interventions are returned as expected.
  43. Drag the desired intervention to the 'Treatment Plan' field.
  44. Select the desired value in the 'Status' field.
  45. Click [Return to Plan] and [OK].
  46. Select "Final" in the 'Treatment Plan Status' field.
  47. Click [Submit].
  48. Validate a 'Confirm Document' dialog is displayed with the treatment plan data.
  49. Validate the problem, goal, objective, and intervention added in the previous steps are displayed.
  50. Click [Accept].
  51. Enter the password for the logged in user and click [Verify].
  52. Verify successful submission.
Scenario 2: Treatment Plan Copy - Validate the 'Apply Search Results By' filter
Specific Setup:
  • Please note: this is for Avatar NX only.
  • A client is enrolled in an existing episode (Client A).
  • A copy of the 'Treatment Plan' form must be defined (Treatment Plan Copy).
  • Must have Treatment Plan libraries configured with problems, goals, objectives, and interventions.
  • Document routing is enabled on the 'Treatment Plan Copy' form.
Steps
  1. Select "Client A" and access the 'Treatment Plan Copy' form.
  2. Enter the desired date in the 'Plan Date' field.
  3. Select the desired value in the 'Plan Type' field.
  4. Select "Draft" in the 'Treatment Plan Status' field.
  5. Click [Launch Plan].
  6. Validate the Treatment Plan libraries are listed on the left-hand side.
  7. Validate the 'Apply Search Results By' field is displayed and contains the following values:
  8. Search All - this will be the existing search functionality that performs a search on all library items
  9. Problem - this will return applicable problems and their child elements
  10. Goal - this will return applicable goals and their child elements
  11. Objective - this will return applicable objectives and their child elements
  12. Intervention - this will return applicable interventions
  13. Select "Search All" in the 'Apply Search Results By' field.
  14. Enter the desired value in the 'Search' field.
  15. Validate all applicable treatment plan library items are returned as expected.
  16. Remove the value from the 'Search' field.
  17. Select "Problem" in the 'Apply Search Results By' field.
  18. Enter the desired value in the 'Search' field.
  19. Validate all applicable problems are returned as expected.
  20. Validate applicable child items for the problems display in a collapsed state, but can be expanded.
  21. Drag the desired problem to the 'Treatment Plan' field.
  22. Enter the desired value in the 'Problem Code' field.
  23. Select the desired value in the 'Status (Problem List)' field.
  24. Select the desired value in the 'Status' field.
  25. Remove the value from the 'Search' field.
  26. Select "Goal" in the 'Apply Search Results By' field.
  27. Enter the desired value in the 'Search' field.
  28. Validate all applicable goals are returned as expected.
  29. Validate applicable child items for the goals display in a collapsed state, but can be expanded.
  30. Drag the desired goal to the 'Treatment Plan' field.
  31. Select the desired value in the 'Status' field.
  32. Remove the value from the 'Search' field.
  33. Select "Objective" in the 'Apply Search Results By' field.
  34. Enter the desired value in the 'Search' field.
  35. Validate all applicable objectives are returned as expected.
  36. Validate applicable child items for the objectives display in a collapsed state, but can be expanded.
  37. Drag the desired objective to the 'Treatment Plan' field.
  38. Select the desired value in the 'Status' field.
  39. Remove the value from the 'Search' field.
  40. Select "Intervention" in the 'Apply Search Results By' field.
  41. Enter the desired value in the 'Search' field.
  42. Validate all applicable interventions are returned as expected.
  43. Drag the desired intervention to the 'Treatment Plan' field.
  44. Select the desired value in the 'Status' field.
  45. Click [Return to Plan] and [OK].
  46. Select "Final" in the 'Treatment Plan Status' field.
  47. Click [Submit].
  48. Validate a 'Confirm Document' dialog is displayed with the treatment plan data.
  49. Validate the problem, goal, objective, and intervention added in the previous steps are displayed.
  50. Click [Accept].
  51. Enter the password for the logged in user and click [Verify].
  52. Verify successful submission.
Topics
• Treatment Plan • NX
Update 11 Summary | Details
Progress Notes (Group and Individual) - Autosave
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Ambulatory Progress Notes
Scenario 1: Progress Notes (Group and Individual) - Validate autosave functionality
Specific Setup:
  • Autosave must be enabled on the 'Progress Notes (Group and Individual)' form.
  • A client is enrolled in an existing episode and has a treatment plan on file (Client A).
Steps
  1. Access the 'Progress Notes (Group and Individual)' form.
  2. Enter "Client A" in the 'Select Client' field.
  3. Select the desired episode in the 'Select Episode' field.
  4. Select the desired group in the 'Group Name or Number' field.
  5. Select "Independent Note" in the 'Progress Note For' field.
  6. Select the desired value in the 'Note Type' field.
  7. Enter the desired value in the 'Notes Field' field.
  8. Select "Final" in the 'Draft/Final' field.
  9. Click [Backup Form] and close the form.
  10. Access the 'Progress Notes (Group and Individual)' form.
  11. Validate a 'Restore/Delete Backup Data' dialog is displayed.
  12. Select the progress note backed up in the previous steps and click [OK].
  13. Validate the 'Select Client' field contains "Client A".
  14. Validate the 'Select Episode' field contains the episode selected in the previous steps.
  15. Validate the 'Group Name or Number' field contains the group selected in the previous steps.
  16. Validate the 'Progress Note For' field contains "Independent Note".
  17. Validate the 'Note Type' field contains the value selected in the previous steps.
  18. Validate the 'Notes Field' field contains the value entered in the previous steps.
  19. Click [File Note].
  20. Validate a "Progress Notes" message is displayed stating: Note Filed.
  21. Click [OK] and close the form.
Scenario 2: Progress Notes (Group and Individual) Copy - Validate autosave functionality
Specific Setup:
  • A copy of the 'Progress Notes (Group and Individual)' form must be defined.
  • Autosave must be enabled on this form in 'Set System Defaults'.
  • A client is enrolled in an existing episode (Client A).
  • A group is defined in 'Group Registration'.
Steps
  1. Access the 'Progress Notes (Group and Individual) Copy' form.
  2. Enter "Client A" in the 'Select Client' field.
  3. Select the desired episode in the 'Select Episode' field.
  4. Select the desired group in the 'Group Name or Number' field.
  5. Select "Independent Note" in the 'Progress Note For' field.
  6. Select the desired value in the 'Note Type' field.
  7. Enter the desired value in the 'Notes Field' field.
  8. Select "Final" in the 'Draft/Final' field.
  9. Click [Backup Form] and close the form.
  10. Access the 'Progress Notes (Group and Individual) Copy' form.
  11. Validate a 'Restore/Delete Backup Data' dialog is displayed.
  12. Select the progress note backed up in the previous steps and click [OK].
  13. Validate the 'Select Client' field contains "Client A".
  14. Validate the 'Select Episode' field contains the episode selected in the previous steps.
  15. Validate the 'Group Name or Number' field contains the group selected in the previous steps.
  16. Validate the 'Progress Note For' field contains "Independent Note".
  17. Validate the 'Note Type' field contains the value selected in the previous steps.
  18. Validate the 'Notes Field' field contains the value entered in the previous steps.
  19. Click [File Note].
  20. Validate a "Progress Notes" message is displayed stating: Note Filed.
  21. Click [OK] and close the form.
Topics
• Progress Notes • Auto Save
Update 12 Summary | Details
Progress Notes - Progress Notes Web Service - Existing Appointments
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
2023 Update 13 Summary | Details
POC Results Entry - Observation Value Unit
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • POC Results Entry Configuration
Scenario 1: POC Results Entry Configuration form - Observation Value Unit field is not required as vital sign is selected in the 'Observation Definition' tab
Specific Setup:
  • A Prompt Definition (Prompt Definition 1) must be set up via the Avatar CWS 'Site Specific Section Modeling' form for "Vitals Entry - (CWS14000)" such that:
  • 'Site Specific Field' = "SS Vital Signs Integer" or "SS Vital Signs Free Text".
  • 'Exclude from Data Collection Instrument' = "No".
  • 'Initially enabled' = "Yes".
  • The logged in user must have access to the 'POC Results Entry Configuration' form.
Steps
  1. Open the 'POC Results Entry Configuration' form.
  2. Select "Observation Definition" from the 'Section' menu.
  3. Select "Add" from the 'Add/Edit/Delete Observation' field.
  4. Populate the 'Observation ID Code' field.
  5. Select "Prompt Definition 1" from the 'Save as Vital Sign' field.
  6. Validate the 'Observation Value Unit' field contains "Prompt Definition 1 - Units".
  7. Delete the existing value from 'Observation Value Unit' field.
  8. Populate the 'Observation Value Unit' field with any value other than "Prompt Definition 1 - Units" and Press the Tab key.
  9. Validate an "Error Message" is displayed stating "If 'Save as Vital Sign' is defined the Observation Value Unit must either be blank or equal to Value Unit tied to the Vital Sign which is 'SS Vital Signs Free Text 1 - Units'."
  10. Click [OK].
  11. Click [Discard], validate the 'Confirm Close' dialog displays stating "Are you sure you want to Close without saving?" and click [Yes].
Topics
• POC Results Entry • POC Results Entry Configuration form
Update 13 Summary | Details
Disclosure Management - View attached document
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Disclosure Management Configuration
  • Disclosure Management
Scenario 1: Disclosure Management - Validating notes from the authorized episodes in the 'Disclosure Management' report - Document Images Authorized For Disclosure
Specific Setup:
  • Disclosure Management Configuration:
  • The 'Valid Attachment Type' field is set to '(Avatar CWS) Progress Notes (Group and Individual) /EPISODE BASED' or any other document to be used. Note the document selected.
  • Document Routing Setup:
  • The document routing is set up for the document identified above.
  • Admission:
  • A new client is admitted to the desired program. Note the client id, admission date, admission program.
  • Progress Notes (Group and Individual):
  • A progress note is filed for the client / episode. Note the date when progress note filed.
  • Append Document:
  • Append a document to the progress note filed in the previous step.
Steps
  1. Open the 'Disclosure Management' form.
  2. Enter a date in the ‘Request Date’ field.
  3. Enter a date in the ‘Request Information Start Date’ field.
  4. Enter a date in the ‘Request Information End Date’ field.
  5. Select the topmost Document Image in the ‘Requested Document Images’ field.
  6. Enter an organization name in the ‘Organization’ field.
  7. Go to the ‘Authorization’ section.
  8. Enter a date in the ‘Authorization Start Date’.
  9. Enter a date in the ‘Authorization End Date’.
  10. Click the ‘Update Document Images Authorized For Disclosure’ button.
  11. Select the ‘Document Image’ row and set the ‘Authorized’ field to ‘Yes’.
  12. Click the ‘Save’ button.
  13. Click the ‘Refresh Document Images’ button.
  14. Verify the previously selected document displays as ‘Authorized’ in the ‘Document Images Authorized For Disclosure’.
  15. Go to the ‘Disclosure’ section.
  16. Enter a date in the ‘Disclosure Date’ field.
  17. Enter a time in the ‘Disclosure Time’ field.
  18. Select the document image in the ‘Disclosure Images’ field.
  19. Click the ‘Process’ button.
  20. Click the ‘Disclose’ button.
  21. Verify the disclosure information displays for the previously selected document image.
  22. Click the ‘Cancel’ button to return to the ‘Disclosure’ section.
  23. Click the ‘Submit’ button to file the record.
  24. Click ‘Yes’ to return to the pre-display.
  25. Click the ‘Add’ button to create another record.
  26. Enter a date in the ‘Request Date’ field.
  27. Enter a date in the ‘Request Information Start Date’ field.
  28. Enter a date in the ‘Request Information End Date’ field.
  29. Select both Document Images in the ‘Requested Document Images’ field.
  30. Enter an organization name in the ‘Organization’ field.
  31. Go to the ‘Authorization’ section.
  32. Enter a date in the ‘Authorization Start Date’.
  33. Enter a date in the ‘Authorization End Date’.
  34. Click the ‘Update Document Images Authorized For Disclosure’ button.
  35. Select each ‘Document Image’ row and set the ‘Authorized’ field to ‘Yes’.
  36. Click the ‘Save’ button.
  37. Click the ‘Refresh Document Images’ button.
  38. Verify the previously selected documents display as ‘Authorized’ in the ‘Document Images Authorized For Disclosure’.
  39. Go to the ‘Disclosure’ section.
  40. Enter a date in the ‘Disclosure Date’ field.
  41. Enter a time in the ‘Disclosure Time’ field.
  42. Select the document image in the ‘Disclosure Images’ field.
  43. Click the ‘Process’ button.
  44. Click the ‘Disclose’ button.
  45. Verify the disclosure information displays for the previously selected document images.
  46. Click the ‘Cancel’ button to return to the ‘Disclosure’ section.
  47. Click the ‘Submit’ button to file the record.
  48. Click ‘No’ to exit the form.
Scenario 2: Disclosure Management - Validating notes from the authorized episodes in the 'Disclosure Management' report - Chart items authorized for disclosure
Specific Setup:
  • Disclosure Management Configuration:
  • The 'Valid Attachment Type' field is set to '(Avatar CWS) Progress Notes (Group and Individual) /EPISODE BASED' or any other document to be used. Note the document selected.
  • Document Routing Setup:
  • The document routing is set up for the document identified above.
  • Admission:
  • A new client is admitted to the desired program. Note the client id, admission date, admission program.
  • Progress Notes (Group and Individual):
  • A progress note is filed for the client / episode. Note the date when progress note filed.
  • Append Document:
  • Append a document to the progress note filed in the previous step.
Steps
  1. Open the 'Disclosure Management' form for the client.
  2. Enter desired date to the 'Request Date' such that it covers the progress note filing date.
  3. Select an episode in the 'Request Episode(s)' field.
  4. Select desired document type in the 'Requested Chart Items' field.
  5. Enter required organization information.
  6. Click [Save Requesting Organization].
  7. Validate the 'Requesting Organization details have been saved' message.
  8. Select the 'Authorization' section.
  9. Enter authorization dates that cover the episodes up to the date the progress notes were entered
  10. Select desired episode from the 'Authorization Episode(s)'.
  11. Set the 'Default all Chart Items to Yes' to 'YES'.
  12. Click 'Update Chart Items Authorized For Disclosure' and authorize the attachment.
  13. Select the 'Disclosure' section.
  14. Enter a 'Disclosure Date'.
  15. Select '(Avatar CWS) Progress Notes (Group and Individual)' in the field 'Chart Disclosure Information'.
  16. Click Process.
  17. Select the '(Avatar CWS) Progress Notes (Group and Individual)' entry in the 'Items for Disclosure'.
  18. Click 'View'.
  19. Verify the note displays successfully for the authorized episodes.
  20. Click [Cancel].
  21. Verify the system navigates user to the 'Disclosure Management' form.
  22. Click [Submit].
  23. Verify the disclosure submitted successfully.
Topics
• Disclosure
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
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 15 Summary | Details
Family Health History - Treatment Result
Scenario 1: Filing the 'Family Health History' form
Specific Setup:
  • Family the test client belongs to should be entered in via "Family Registration".
Steps
  1. Using the "Family Health History" form
  2. Select "Add New" from the "Select Family Member" dropdown.
  3. Set "First" to "Kennedi".
  4. Set "Last" to "Muck".
  5. Select "Granddaughter" from the "Relationship" dropdown.
  6. Set the "Date of Birth date" to "07/09/2023".
  7. Select "Female" under "Sex".
  8. Select "White/Caucasian" from the "Race" dropdown.
  9. Select "Not Of Hispanic Origin" from the "Ethnicity" dropdown.
  10. Select "Yes" under "Health Problems To Record".
  11. Click the "Enter Health History" button.
  12. Click the New Row button
  13. Set the "Problem" to "happy puppet sundrome".
  14. Set "Status" to "Currently In Treatment (2)".
  15. Click the "Save" button.
  16. Set the "Notes" to "notes field".
  17. Submit the form to file the data.
  18. Reopen the "Family Health History" form.
  19. Select "Kennedi Muck Granddaughter" from the "Select Family Member" dropdown.
  20. Validate "Relationship" contains "Granddaughter".
  21. Validate "Date of Birth date" is set to "07/09/2023".
  22. Validate "Sex" is set to "Female".
  23. Validate "Race" contains "White/Caucasian".
  24. Validate "Ethnicity" contains "Not Of Hispanic Origin".
  25. Validate "Health Problems To Record" contains "Yes".
  26. Set the "Notes" to "notes field".
  27. Click the "Enter Health History" button.
  28. Validate "Problem" contains "happy puppet syndrome".
  29. Validate "Status" contains "Currently In Treatment (2)".
  30. Click the "Close/Cancel" button.
  31. Set the "Notes" to "notes field".
Family Health History - Refused Vitals
Scenario 1: Vitals Entry Report - Report displays refused vitals information
Specific Setup:
  • Registry setting Avatar CWS->CWS Utilities->Set System Defaults->Vitals Entry->->Enable Multiple Blood Pressure Entry is set to "Y".
  • Multiple vitals are filed for a client using 'Vitals Entry'.
  • One or more records include 'Refused Vitals' set to "Yes".
Steps
  1. Access the 'Vitals Entry' form for the test client.
  2. Click [Vitals Reports] section.
  3. Select "All" in the 'Vital Sign(s) for Report' field.
  4. Set the '"Start Date" field to a date which will include the refused vitals records.
  5. Set the "Start Time" to the current time.
  6. Set the "End Date" field to the end of the date range to include records in the report.
  7. Set the "End Time" to the current time.
  8. Select "Yes" in the "Display Refused Vitals" field.
  9. Click [View Report].
  10. Verify the "Refused Vitals" data displays successfully for the dates included.
Scenario 2: Vitals Entry Report - 'Display Refused Vitals' set to "No"
Specific Setup:
  • A client has refused and not refused vitals on file in 'Vitals Entry' (Client A).
Steps
  1. Select "Client A" and access the 'Vitals Entry' form.
  2. Select the "Vitals Reports" section.
  3. Select "All" in the 'Vital Sign(s) for Report' field.
  4. Enter a date that will include refused and not refused vitals in the 'Start Date' field.
  5. Enter the current time in the 'Start Time' field.
  6. Enter a date that will include refused and not refused vitals in the 'End Date' field.
  7. Enter the current time in the 'End Time' field.
  8. Select "No" in the "Display Refused Vitals" field.
  9. Click [View Report].
  10. Validate the report does not include refused vitals or comments associated with refused vitals.
  11. Close the report and the form.
Vitals Entry - Position required
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • CWS Vital Signs Setup
Scenario 1: "Vitals Entry" form - Additional blood pressure fields
Specific Setup:
  • Avatar CWS->CWS Utilities->Set System Defaults->Vitals Entry->->Enable Multiple Blood Pressure Entry = "Y". Note that this is a one time registry setting. Once enabled, this cannot be disabled.
Steps
  1. Open "Vitals Entry" form.
  2. Select "Add" in the "Add/Edit/Delete Vital Sign" field.
  3. Enter current date in the "Date" field.
  4. Enter current time in the "Time" field.
  5. Enter any value in the Blood Pressure: "Systolic" field.
  6. Validate the Blood Pressure: "Diastolic" field becomes required.
  7. Enter any value in the Blood Pressure: "Diastolic" field.
  8. Validate the Blood Pressure "Systolic" field becomes required.
  9. Select any value in the Blood Pressure: "Position" field.
  10. Enter any value in the Blood Pressure 2: "Systolic 2" field.
  11. Validate the "Blood Pressure 2: "Diastolic 2" field becomes required.
  12. Enter any value in the Blood Pressure 2: "Diastolic 2" field.
  13. Validate the "Blood Pressure 2: "Systolic 2" field becomes required.
  14. Select any value in the Blood Pressure 2: "Position 2" field.
  15. Enter any time in the Blood Pressure 2: "Time Taken" field.
  16. Enter any value in the Blood Pressure 3: "Systolic 3" field.
  17. Validate the "Blood Pressure 3: "Diastolic 3" field becomes required.
  18. Enter any value in the Blood Pressure 3: "Diastolic 3" field.
  19. Validate the "Blood Pressure 3: "Systolic 2" field becomes required.
  20. Select any value in the Blood Pressure 3: "Position 3" field.
  21. Enter any time in the Blood Pressure 3: "Time Taken" field.
  22. Click [Submit].
  23. Click [Yes] on the "Submitting has completed. Do you wish to return to form?" prompt.
  24. Validate the following fields are not required on re-display of the form:
  25. "Position 2".
  26. "Position 3".
  27. "Time 2".
  28. "Time 3".
  29. Select "Edit" in the "Add/Edit/Delete Vital Sign" field.
  30. Click [Select Vital Sign].
  31. Click on the previously entered row to highlight.
  32. Click [OK].
  33. Verify the previously entered data displays as entered in previous steps.
  34. Click [Submit].
  35. Click [No] on the "Submitting has completed. Do you wish to return to form?" prompt to return to the menu.
  36. Open the "CWS Vital Signs Setup" form.
  37. Set low value/high value ranges for all 3 blood pressure fields.
  38. File the form.
  39. Open the :Vitals Entry" form.
  40. Validate all 3 diastolic/systolic blood pressure fields for range limits.
Scenario 2: Vitals Entry - Field Validations - Single Blood Pressure
Specific Setup:
  • Avatar CWS->CWS Utilities->Set System Defaults->Vitals Entry->->Enable Multiple Blood Pressure Entry = "N". Note that this is a one time registry setting. Once enabled, this cannot be disabled.
Steps
  1. Open "Vitals Entry" form.
  2. Select "Add" in the "Add/Edit/Delete Vital Sign" field.
  3. Enter current date in the "Date" field.
  4. Enter current time in the "Time" field.
  5. Enter any value in the Blood Pressure: "Systolic" field.
  6. Validate the Blood Pressure: "Diastolic" field becomes required.
  7. Enter any value in the Blood Pressure: "Diastolic" field.
  8. Validate the Blood Pressure "Systolic" field becomes required.
  9. Select any value in the Blood Pressure: "Position" field.
  10. Click [Submit].
  11. Click [Yes] on the "Submitting has completed. Do you wish to return to form?" prompt.
  12. Select "Edit" in the "Add/Edit/Delete Vital Sign" field.
  13. Click [Select Vital Sign].
  14. Click on the previously entered row to highlight.
  15. Click [OK].
  16. Verify the previously entered data displays as entered in previous steps.
  17. Click [Submit].
  18. Click [No] on the "Submitting has completed. Do you wish to return to form?" prompt to return to the menu.
Topics
• Family Health History • Vitals Entry
Update 16 Summary | Details
Validate Observation details in 'Client Observation' form
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Client Observation
Scenario 1: Validate Observation details 'Updated Time' does not change for previous entries in 'Client Observation' form
Steps
  1. Open 'Client Observation' form for a test client.
  2. Create multiple entries in the 'Observation Details'.
  3. Edit one of the entries and validate that the fields 'Updated Date', 'Updated time' and 'Updated By' are changed for the edited row only. The other rows do not change.
Scenario 2: Validate the values in the table 'cw_observation_archive' are populating correctly
Steps
  1. Using 'Client Observation' form, create an Observation record which is more than 30 days before from current date as Observations are archived after 30 days.
  2. To immediately archive the data contact Netsmart associate.
  3. Execute the query "select * from system.cw_observation_details_archive".
  4. Validate that the following fields are populated :
  5. -'createdDate'
  6. -'createdTime'
  7. -'createdBy'
  8. -'updatedDate'
  9. -'updatedTime'
  10. -'updatedBy'
Validate Observation Archive tables
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Client Observation
Scenario 1: Validate Observation details 'Updated Time' does not change for previous entries in 'Client Observation' form
Steps
  1. Open 'Client Observation' form for a test client.
  2. Create multiple entries in the 'Observation Details'.
  3. Edit one of the entries and validate that the fields 'Updated Date', 'Updated time' and 'Updated By' are changed for the edited row only. The other rows do not change.
Scenario 2: Validate the values in the table 'cw_observation_archive' are populating correctly
Steps
  1. Using 'Client Observation' form, create an Observation record which is more than 30 days before from current date as Observations are archived after 30 days.
  2. To immediately archive the data contact Netsmart associate.
  3. Execute the query "select * from system.cw_observation_details_archive".
  4. Validate that the following fields are populated :
  5. -'createdDate'
  6. -'createdTime'
  7. -'createdBy'
  8. -'updatedDate'
  9. -'updatedTime'
  10. -'updatedBy'
Topics
• NX • Client Observation
Update 17 Summary | Details
Progress Notes
Scenario 1: Progress Notes (Group and Individual) - Group Default Notes - file an existing appointment group note
Specific Setup:
  • Registry Settings:
  • The 'Attach Selected Appointment To Notes On Draft' registry setting is set to either "1" or "2".
  • The 'Post Appointment When the Note Is Submitted' registry setting is set to "Y".
  • Group Registration:
  • A group must exist (Group A) with two clients (Client A & Client B).
  • Add 'Group Assignment Start Date' and 'Group Assignment End Date' for Client A.
  • Add 'Group Assignment Start Date' for Client B.
  • A group appointment must be scheduled for "Group A" for the current date.
  • Document routing is enabled on the 'Progress Notes (Group and Individual)' form.
Steps
  1. Access the 'Progress Notes (Group and Individual)' form.
  2. Select the "Group Default Notes" section.
  3. Enter the current date in the 'Date Of Group' field.
  4. Enter the desired practitioner in the 'Practitioner' field.
  5. Select "Existing Appointment" in the 'Progress Note For' field.
  6. Select the existing appointment for "Group A" in the 'Note Addresses Which Existing Service/Appointment' field.
  7. Select the desired value in the 'Note Type' field.
  8. Enter the desired value in the 'Note' field.
  9. Validate the 'Client Who Attended Group' field contains "Client A" and "Client B".
  10. Click [File Note].
  11. Validate a "Group Default Notes" message is displayed stating: Progress notes are filed.
  12. Click [OK].
  13. Navigate to the "Individual Progress Notes" section.
  14. Select "Group A" in the 'Group Name or Number' field.
  15. Enter the current date in the 'Note Date' field.
  16. Select the note for "Client A" in the 'Select Note To Edit' field.
  17. Select "Final" in the 'Draft/Final' field.
  18. Click [File Note].
  19. Click [Accept] in the document routing dialog.
  20. Enter the password for the logged in user and click [Verify].
  21. Validate a message is displayed stating: Note Filed.
  22. Click [OK].
  23. Validate the 'Select Note To Edit' field contains the note for "Client B".
  24. Select "Final" in the 'Draft/Final' field.
  25. Click [File Note].
  26. Click [Accept] in the document routing dialog.
  27. Enter the password for the logged in user and click [Verify].
  28. Validate a message is displayed stating: Note Filed.
  29. Click [OK] and close the form.
  30. Access the 'Client Ledger' form.
  31. Enter "Client A" in the 'Client ID' field.
  32. Select "All Episodes" from the 'Claim/Episode/All Episodes' field.
  33. Select "Simple" from the 'Ledger Type' field.
  34. Click [Process].
  35. Verify the 'Client Ledger Report' page is displayed and contains the service for the group note filed in the previous steps.
  36. Click [Dismiss].
  37. Repeat steps 2a-2f for "Client B".
  38. Close the form.
Topics
• Progress Notes
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:
  • 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 19 Summary | Details
Medical Note - Limit Note Types By Practitioner Category
Scenario 1: Medical Note - Limit Note Types by Practitioner Category
Specific Setup:
  • A dictionary code must exist for the CWS ‘(10751) Note Type’ dictionary. (Note Type A)
  • The ‘(79) Practitioner Category’ extended attribute must be set to “Medical Doctor” in the CWS ‘(10751) Note Type’ dictionary for "Note Type A".
  • The 'Avatar CWS->Progress Notes->Inpatient (Medical Diagnosis)->->->Limit Note Types By Practitioner Category' registry setting must be set to "Y".
  • The 'Avatar CWS->Progress Notes->Ambulatory (Medical Diagnosis)->->->Limit Note Types By Practitioner Category' registry setting must be set to "Y".
  • Please log out of the application and log back in after completing the above configuration.
  • The logged in user must be associated with a practitioner who has the 'Practitioner Category' field set to "Medical Doctor" in the 'Practitioner Enrollment' form.
  • A client must have an active episode. (Client A)
Steps
  1. Search for and select "Client A" and navigate to 'Medical Note'.
  2. Click [Add Note] and select "Psychiatry" from the 'Appointment/Note Workflow' field.
  3. Click the 'Note Type' field and validate the dropdown includes "Note Type A".
  4. Populate any remaining required fields, click [Save] and validate the note is created successfully.
Topics
• Medical Note
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
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
Update 23 Summary | Details
SQL Table validation - SYSTEM.cwtxProbDefStorage
Scenario 1: SYSTEM.cwtxProbDefStorage - Validating Data Retrieval
Specific Setup:
  • System is configured with 'Avatar Wiley Library 2024' product module.
  • Tester has access to the 'Crystal Report' or any other SQL data viewer for the system.
Steps
  1. Open the 'Crystal Report' or any other SQL data viewer.
  2. Run the SQL query to retrieve data from the 'SYSTEM.cwtxProbDefStorage' table.
  3. Verify that the data successfully retrieved from the table.
  4. Close the report.
Hospitalizations and Surgeries - Data Validation
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Hospitalizations and Surgeries
Scenario 1: Hospitalizations and Surgeries - Data validation of the 'Hospital Data' table
Specific Setup:
  • Admission:
  • A new client is admitted, or an existing client is identified. Note the client's id and name of the client.
Steps
  1. Open ‘Hospitalizations and Surgeries’ form for the desired client.
  2. Add more than 10 rows of data with the desired reason code and with the classification of the "Medical", "Substance Abuse" and "Psychiatric" selected in the 'Filter by Classification' field.
  3. Click [Submit].
  4. Reopen the ‘Hospitalizations and Surgeries’ form for the same client.
  5. Verify all rows of data are correctly displayed.
  6. Verify the ‘Filter by Classification’ field is defaulted to ‘All’.
  7. Verify all records display in the grid regardless of assigned ‘Filter by Classification’ field.
  8. Click ‘Medical’ in the ‘Filter by Classification’ field.
  9. Verify only ‘Medical’ records display in the table.
  10. Click ‘Psychiatric’ in the ‘Filter by Classification’ field.
  11. Verify only ‘Psychiatric’ records display in the table.
  12. Click ‘Substance Abuse’ in the ‘Filter by Classification’ field.
  13. Verify only ‘Substance Abuse’ records display in the table.
  14. Click [Discard].
Topics
• Database Management • Hospitalizations and Surgeries
Update 26 Summary | Details
The “Hide Columns in Problem List” registry setting
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Problem List
  • Treatment Plan
Scenario 1: Problem List - Validate the 'Hide Columns in Problem List' registry setting
Specific Setup:
  • A client must be enrolled in an existing episode and has one or more problems that have been entered in the 'Problem List' form. (Client A)
Steps
  1. Access the 'Registry Settings' form.
  2. Enter "Hide Columns in Problem List" in the 'Limit Registry Settings to the Following Search Criteria' field.
  3. Click [View Registry Settings].
  4. Validate the 'Registry Setting Value' field is blank by default.
  5. Validate the 'Registry Setting Details' field contains: Entering a value for this setting hides the specified columns in the 'Problem List' grid on the 'Problem List' and 'Treatment Plan' forms. Valid entries are:
  6. AC - Hide 'Action'
  7. CM - Hide 'Comment'
  8. CR - Hide 'Chronicity'
  9. DC - Hide 'DSM/ICD Code'
  10. DI - Hide 'Date Identified'
  11. DO - Hide 'Date of Onset'
  12. DR - Hide 'Date Resolved'
  13. PI - Hide 'Problem Information'
  14. PP - Hide 'Problem Plan'
  15. SN - Hide 'System Notes'
  16. SV - Hide 'Severity'
  17. TO - Hide 'Time of Onset'
  18. TY - Hide 'Type'
  19. Multiple values may be entered, separated by an '&'. For example, entering 'DO&TO' would hide the 'Date of Onset' and 'Time of Onset' fields. Leaving this setting blank will not hide any of the columns in the Problem List grid.
  20. Enter "TY&DI&DO&TO&SV&CR&DR&AC&CM&DC&SN&PI&PP" in the 'Registry Setting Value' field.
  21. Click [Submit] and close the form.
  22. Select "Client A" and access the 'Problem List' form.
  23. Click [View/Enter Problems].
  24. Validate the existing problems on file are displayed.
  25. Validate the columns hidden via the 'Hide Columns in Problem List' registry setting are not displayed.
  26. Close the form.
  27. Access the 'Registry Settings' form.
  28. Enter "Hide Columns in Problem List" in the 'Limit Registry Settings to the Following Search Criteria' field.
  29. Click [View Registry Settings].
  30. Clear the value in the 'Registry Setting Value' field.
  31. Click [Submit] and close the form.
  32. Select "Client A" and access the 'Problem List' form.
  33. Click [View/Enter Problems].
  34. Validate the existing problems on file are displayed.
  35. Validate all columns are now displayed since the 'Hide Columns in Problem List' registry setting is no longer configured.
  36. Close the form.
Scenario 2: Treatment Plan - Validate the 'Hide Columns in Problem List' registry setting
Specific Setup:
  • A client must be enrolled in an existing episode and has one or more problems that have been entered in the 'Problem List' form. (Client A)
Steps
  1. Access the 'Registry Settings' form.
  2. Enter "Hide Columns in Problem List" in the 'Limit Registry Settings to the Following Search Criteria' field.
  3. Click [View Registry Settings].
  4. Validate the 'Registry Setting Value' field is blank by default.
  5. Validate the 'Registry Setting Details' field contains: Entering a value for this setting hides the specified columns in the 'Problem List' grid on the 'Problem List' and 'Treatment Plan' forms. Valid entries are:
  6. AC - Hide 'Action'
  7. CM - Hide 'Comment'
  8. CR - Hide 'Chronicity'
  9. DC - Hide 'DSM/ICD Code'
  10. DI - Hide 'Date Identified'
  11. DO - Hide 'Date of Onset'
  12. DR - Hide 'Date Resolved'
  13. PI - Hide 'Problem Information'
  14. PP - Hide 'Problem Plan'
  15. SN - Hide 'System Notes'
  16. SV - Hide 'Severity'
  17. TO - Hide 'Time of Onset'
  18. TY - Hide 'Type'
  19. Multiple values may be entered, separated by an '&'. For example, entering 'DO&TO' would hide the 'Date of Onset' and 'Time of Onset' fields. Leaving this setting blank will not hide any of the columns in the Problem List grid.
  20. Enter "TY&DI&DO&TO&SV&CR&DR&AC&CM&DC&SN&PI&PP" in the 'Registry Setting Value' field.
  21. Click [Submit] and close the form.
  22. Select "Client A" and access the 'Treatment Plan' form.
  23. Navigate to the 'Problems' grid.
  24. Validate the existing problems on file are displayed.
  25. Validate the columns hidden via the 'Hide Columns in Problem List' registry setting are not displayed.
  26. Close the form.
  27. Access the 'Registry Settings' form.
  28. Enter "Hide Columns in Problem List" in the 'Limit Registry Settings to the Following Search Criteria' field.
  29. Click [View Registry Settings].
  30. Clear the value in the 'Registry Setting Value' field.
  31. Click [Submit] and close the form.
  32. Select "Client A" and access the 'Treatment Plan' form.
  33. Navigate to the 'Problems' grid.
  34. Validate the existing problems on file are displayed.
  35. Validate all columns are now displayed since the 'Hide Columns in Problem List' registry setting is no longer configured.
  36. Close the form.
Topics
• Registry Settings • Problem List • Treatment Plan
Update 27 Summary | Details
CWS - Progress Notes - Prolonged Duration
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • ProgressNote Approval
  • Ambulatory Progress Notes
Scenario 1: Cal-PM - CWS - Progress Notes (Group and Individual) - Prolonged Duration
Specific Setup:
  • Registry Settings:
  • The 'Enable Multiple Add-On Code Per Primary' registry setting is set to 'Y'.
  • The 'Enable Prolonged Duration Add-On Service Generation' is set to 'Y'.
  • 'N' disables the functionality.
  • 'Y' enables the functionality and adds the 'Prolonged Duration Configuration' field to the service code form. It also allows users to manually select/submit add-on services in all the progress note forms.
  • 'YR' enables the functionality and adds the 'Prolonged Duration Configuration' field to the service code form. It prevents users from manually selecting/submitting add-on services in all the progress note forms. The add-on service(s) are created automatically based on the values in the 'Prolonged Duration Configuration' grid.
  • Dictionary Update:
  • File= 'Other Tabled File,
  • Data Element -291, Service Code Type'
  • Dictionary Code = 1
  • Dictionary Value = Evaluation Therapy
  • Extended dictionary 'Allow Multiple Add-On Code' = Yes
  • An existing add-on service code is identified with the following values, or a new add-on code is created with the following values:
  • Service Code Category = Primary Add-On Code
  • Service Code Type = Evaluation Therapy
  • Minutes per unit = 15
  • Unit Rounding Logic = Round Over 1/2 Unit
  • Designated Degree Of Rounding = Whole Unit
  • Type of Service = Individual
  • All other fields are populated as required/needed.
  • Note the code and definition.
  • An existing add-on service code is identified with the following values, or a new add-on code is created with the following values:
  • Service Code Category = Add-On Code
  • Service Code Type = Evaluation Therapy
  • Minutes per unit = 15
  • Unit Rounding Logic = Round Over 1/2 Unit
  • Designated Degree Of Rounding = Whole Unit
  • Type of Service = Individual
  • All other fields are populated as required/needed.
  • Note the code and definition.
  • An existing service code is identified with the following values, or a new add-on code is created with the following values:
  • Primary Service = desired service code
  • Service Code Category = Primary Code
  • Service Code Type = Evaluation Therapy
  • Select Add-On Service Code =Primary add-on and an add-on code defined above are selected.
  • Minutes per unit = 15
  • Unit Rounding Logic = Round Over 1/2 Unit
  • Designated Degree Of Rounding = Whole Unit
  • Type of Service = Individual
  • Enable Prolonged Duration Add-On Service Generation = Yes
  • Prolonged Duration Configuration Grid View:
  • Practitioner Category Column - desired practitioner category defined in each grid row. Note the practitioner category.
  • Location - desired location is defined in each grid row. Note the location.
  • Service Code to Use for Prolonged Duration - desired service code
  • Max Duration Primary Service Must Exceed for Prolonged Duration Add-On Service to Generate = desired duration (In minutes, any integer between 0-1440) defined in each grid row. Note the duration defined.
  • Minimum Remaining Duration to be Met for Prolonged Duration Add-On Service to Generate = desired duration (In minutes, any integer between 0-1440) defined in each grid row. Note the duration defined.
  • ·Service Fee/ Cross Reference Maintenance:
  • Primary Service Code - desired duration range is entered and desired fee definition is created.
  • Add-On Service codes = desired duration range is entered and desired fee definition is created.
  • Select an active client for progress note creation. Note client ID and episode number.
  • Select 1-2 active practitioner to be used for progress note with different practitioner category that matches with the 'Practitioner Category' defined in the 'Prolonged Duration Configuration' Grid. Note practitioner ID and category.
  • Select 1-2 active practitioner to be used for progress note with different practitioner category that does not match with the 'Practitioner Category' defined in the 'Prolonged Duration Configuration' Grid. Note practitioner ID and category.
  • Identify 1-2 dictionary codes/values for the 'Location' to be used for the progress note that matches with the 'Location' defined in the 'Prolonged Duration Configuration' Grid. Note practitioner ID and category.
  • Identify 1-2 dictionary codes/values for the 'Location' to be used for the progress note that matches with the 'Location' defined in the 'Prolonged Duration Configuration' Grid. Note practitioner ID and category.
  • Please review: The prolonged service generation logic:
  1. System identifies the practitioner category and location for the primary service because both of these parameters are needed to know which row should be evaluated in the ''Prolonged Duration Configuration' grid. The logic for evaluating if Avatar should automatically generate a prolonged duration add-on service will not occur within the progress note form until all three parameters Practitioner Category, Location and Duration have been entered.
  2. If the duration entered in the 'Service Duration' field exceeds the duration specified for the service code in the 'Max Duration Primary Service Must Exceed for Prolonged Duration Add-On Service to Generate' column in the 'Prolonged Duration Configuration' grid, Avatar will file the duration amount entered in the 'Max Duration Primary Service Must Exceed for Prolonged Duration Add-On Service to Generate' column in the 'Prolonged Duration Configuration' grid for the primary service code when the service is created.
  3. If the remaining duration amount above the duration specified for the primary service code in the new 'Max Duration Primary Service Must Exceed for Prolonged Duration Add-On Service to Generate' column in the 'Prolonged Duration Configuration' grid, s equal to or greater than the amount entered in the 'Minimum Remaining Duration to be Met for Prolonged Duration Add-On Service to Generate' column in the 'Prolonged Duration Configuration' grid, then system automatically creates and 'saves' the add-on service for prolonged duration that is specified for the primary service code in the 'Service Code to Use For Prolonged Duration' field in the 'Service Codes' form. File the remaining duration amount as the duration for the add-on service when created. This entry within the 'Select Multiple Add-On Codes' field will not be editable via the 'Select Add-On Service Entry to Edit/Remove' dropdown option prior to finalizing the progress note. The Prolonged Duration Add-On Service that Avatar generates automatically will be displayed as the first row in the 'Selected Add-On Services' field.
  4. If the value entered for the 'Practitioner', 'Location' or 'Service Duration' field are changed, Avatar will need to rerun the process/logic to evaluate if that updated duration exceeds the duration specified for the service code in the 'Max Duration Primary Service Must Exceed for Prolonged Duration Add-On Service to Generate Column' column in the Prolonged Duration Configuration grid and update the add-on row that was system generated to now list the appropriate add-on duration amount. Likewise, if the updated duration entered in the 'Service Duration' field does now not exceed the duration specified for the service code in the 'Max Duration Primary Service Must Exceed for Prolonged Duration Add-On Service to Generate' column in the 'Prolonged Duration Configuration' grid, Avatar will remove the row that was previously saved as a prolonged duration add-on is no longer needed. The same idea will extend to the Practitioner Category, Location, and Minimum Remaining Duration to be Met for Prolonged Duration Add-On Service to Generate columns that can be configured in the Prolonged Duration Configuration grid. If the Location or practitioner is changed – that will need to reevaluate the logic configured for that in the Prolonged Duration Configuration grid.
Steps
  1. Open the 'Progress Notes (Group and Individual)' form.
  2. Select desired client from the ‘Select Client’ field by name or ID.
  3. Select desired episode in the 'Select Episode' field.
  4. Select ‘New Service’ in the 'Progress Note For' field.
  5. Enter any value in the 'Note Type' field.
  6. Enter any value in the 'Notes Field' field.
  7. Enter desired date in the 'Date Of Service' field.
  8. Enter the 'Evaluation Management', 'Primary Code' defined in the setup.
  9. Validate the prolonged duration service codes display in the ‘Add On Services’ field to be manually selected and that no 'Add-On Service' was automatically created.
  10. Select the 'Practitioner' whose practitioner category matches with the practitioner category defined in one of the ‘Practitioner Category’ column of the ‘Prolonged Duration Configuration’ grid for the service code in the ‘Service Code’ form.
  11. Select the 'Location' of the service matches with the location code with the location defined in one of the ‘Location’ column of the ‘Prolonged Duration Configuration’ grid for the service code in the ‘Service Code’ form.
  12. Enter desired duration in the ‘Service Duration’ that is above the 'Max Duration Primary Service Must Exceed For Prolonged Duration Add-On Service to Generate' and has enough surplus over that so that the remaining duration is greater than or equal to 'Minimum Remaining Duration to be Met for Prolonged Duration Add-On Service to Generate' column of the ‘Prolonged Duration Configuration’ grid for the service code in the ‘Service Code’ form.
  13. Verify the prolonged duration service code will be automatically created and added to 'Selected Add-On Services' field.
  14. Select ‘Final’ from the 'Draft/Final' field.
  15. Click [File Note].
  16. Validate a Note Filed message is displayed.
  17. Click [OK].
  18. Click [Close Form].
  19. Open the 'Client Ledger' form.
  20. Select desired client, episode and 'Ledger Type' as 'Simple'.
  21. Click [Process].
  22. Verify the primary service and prolonged add-on service created with the correct units for the service and correct service code.
  23. Close the form.
  24. Open the ‘Registry Setting’ form.
  25. Set the 'Enable Prolonged Duration Add-On Service Generation' registry setting to ‘YR’.
  26. Close the form.
  27. Open the 'Progress Notes (Group and Individual)' form.
  28. Select desired client from the ‘Select Client’ field by name or ID.
  29. Select desired episode in the 'Select Episode' field.
  30. Select ‘New Service’ in the 'Progress Note For' field.
  31. Enter any value in the 'Note Type' field.
  32. Enter any value in the 'Notes Field' field.
  33. Enter desired date in the 'Date Of Service' field that falls within the ‘Effective Date’ and Expiration Date’ defined in one of the ‘Prolonged Duration Configuration’ grid for the service code in the ‘Service Code’ form. Select desired value in the 'Service Charge Code' field that match.
  34. Enter the 'Evaluation Management', 'Primary Code' defined in the setup.
  35. Verify the prolonged duration service codes does not display in the ‘Add On Services’ field to be manually selected.
  36. Select the 'Practitioner' whose practitioner category that matches with the practitioner category defined in one of the ‘Practitioner Category’ column of the ‘Prolonged Duration Configuration’ grid for the service code in the ‘Service Code’ form.
  37. Select the 'Location' of the service that matches with the location code with the location defined in one of the ‘Location’ column of the ‘Prolonged Duration Configuration’ grid for the service code in the ‘Service Code’ form.
  38. Enter desired duration in the ‘Service Duration’ that is above the 'Max Duration Primary Service Must Exceed For Prolonged Duration Add-On Service to Generate' and has enough surplus over that so that the remaining duration is greater than or equal to 'Minimum Remaining Duration to be Met for Prolonged Duration Add-On Service to Generate' column of the ‘Prolonged Duration Configuration’ grid for the service code in the ‘Service Code’ form.
  39. Verify the prolonged duration service code will be added to 'Selected Add-On Services' field.
  40. Change the ‘Service Duration’ to be above the 'Max Duration Primary Service Must Exceed For Prolonged Duration Add-On Service to Generate' but less than the 'Minimum Remaining Duration to be Met for Prolonged Duration Add-On Service to Generate'.
  41. Verify the prolonged duration service code will be removed from the 'Selected Add-On Services' field.
  42. Enter a duration in the ‘Service Duration’ field again that is above the 'Max Duration Primary Service Must Exceed For Prolonged Duration Add-On Service to Generate' and has enough surplus over that so that the remaining duration is greater than or equal to 'Minimum Remaining Duration to be Met for Prolonged Duration Add-On Service to Generate' of the ‘Prolonged Duration Configuration’ grid for the service code in the ‘Service Code’ form.
  43. Verify the prolonged duration service code will be added to 'Selected Add-On Services' field.
  44. Change the 'Service Date', 'Location' and ‘Practitioner’ (category) fields to values that do not match with the values defined for the primary service code in the ‘Prolonged Duration Configuration’ grid in the ‘Service Code’ form.
  45. Verify the prolonged duration service code will be removed from the 'Selected Add-On Services' field.
  46. Change the 'Service Date', 'Location' and ‘Practitioner’ (category) fields to the original values that match with the values defined for the primary service code in the ‘Prolonged Duration Configuration’ grid in the ‘Service Code’ form.
  47. Verify the prolonged duration service code will be added from the 'Selected Add-On Services' field.
  48. Select ‘Final’ from the 'Draft/Final' field.
  49. Click [File Note].
  50. Validate a Note Filed message is displayed.
  51. Click [OK].
  52. Click [Close Form].
  53. Open the 'Client Ledger' form.
  54. Select desired client, episode and 'Ledger Type' as 'Simple'.
  55. Click [Process].
  56. Verify the primary service and prolonged add-on service created with the correct units for the service and correct service code.
  57. Close the form.



Scenario 2: Cal-PM - CWS - Inpatient Progress Notes - Prolonged Duration
Specific Setup:
  • Registry Settings:
  • The 'Enable Multiple Add-On Code Per Primary' registry setting is set to 'Y'.
  • The 'Enable Prolonged Duration Add-On Service Generation' is set to 'Y'.
  • 'N' disables the functionality.
  • 'Y' enables the functionality and adds the 'Prolonged Duration Configuration' field to the service code form. It also allows users to manually select/submit add-on services in all the progress note forms.
  • 'YR' enables the functionality and adds the 'Prolonged Duration Configuration' field to the service code form. It prevents users from manually selecting/submitting add-on services in all the progress note forms. The add-on service(s) are created automatically based on the values in the 'Prolonged Duration Configuration' grid.
  • Dictionary Update:
  • File= 'Other Tabled File,
  • Data Element -291, Service Code Type'
  • Dictionary Code = 1
  • Dictionary Value = Evaluation Therapy
  • Extended dictionary 'Allow Multiple Add-On Code' = Yes
  • An existing add-on service code is identified with the following values or a new add-on code is created with the following values:
  • Service Code Category = Primary Add-On Code
  • Service Code Type = Evaluation Therapy
  • Minutes per unit = 15
  • Unit Rounding Logic = Round Over 1/2 Unit
  • Designated Degree Of Rounding = Whole Unit
  • Type of Service = Individual
  • All other fields are populated as required/needed.
  • Note the code and definition.
  • An existing add-on service code is identified with the following values or a new add-on code is created with the following values:
  • Service Code Category = Add-On Code
  • Service Code Type = Evaluation Therapy
  • Minutes per unit = 15
  • Unit Rounding Logic = Round Over 1/2 Unit
  • Designated Degree Of Rounding = Whole Unit
  • Type of Service = Individual
  • All other fields are populated as required/needed.
  • Note the code and definition.
  • An existing service code is identified with the following values or a new add-on code is created with the following values::
  • Primary Service = desired service code
  • Service Code Category = Primary Code
  • Service Code Type = Evaluation Therapy
  • Select Add-On Service Code =Primary add-on and an add-on code defined above are selected.
  • Minutes per unit = 15
  • Unit Rounding Logic = Round Over 1/2 Unit
  • Designated Degree Of Rounding = Whole Unit
  • Type of Service = Individual
  • Enable Prolonged Duration Add-On Service Generation = Yes
  • Prolonged Duration Configuration Grid View:
  • Practitioner Category Column - desired practitioner category defined in each grid row. Note the practitioner category.
  • Location - desired location is defined in each grid row. Note the location.
  • Service Code to Use for Prolonged Duration - desired service code
  • Max Duration Primary Service Must Exceed for Prolonged Duration Add-On Service to Generate = desired duration (In minutes, any integer between 0-1440) defined in each grid row. Note the duration defined.
  • Minimum Remaining Duration to be Met for Prolonged Duration Add-On Service to Generate = desired duration (In minutes, any integer between 0-1440) defined in each grid row. Note the duration defined.
  • ·Service Fee/ Cross Reference Maintenance:
  • Primary Service Code - desired duration range is entered and desired fee definition is created.
  • Add-On Service codes = desired duration range is entered and desired fee definition is created.
  • Select an active inpatient client for progress note creation. Note client ID and episode number.
  • Select 1-2 active practitioner to be used for progress note with different practitioner category that matches with the 'Practitioner Category' defined in the 'Prolonged Duration Configuration' Grid. Note practitioner ID and category.
  • Select 1-2 active practitioner to be used for progress note with different practitioner category that does not match with the 'Practitioner Category' defined in the 'Prolonged Duration Configuration' Grid. Note practitioner ID and category.
  • Identify 1-2 dictionary codes/values for the 'Location' to be used for the progress note that matches with the 'Location' defined in the 'Prolonged Duration Configuration' Grid. Note practitioner ID and category.
  • Identify 1-2 dictionary codes/values for the 'Location' to be used for the progress note that matches with the 'Location' defined in the 'Prolonged Duration Configuration' Grid. Note practitioner ID and category.
  • Please review: The prolonged service generation logic:
  1. System identifies the practitioner category and location for the primary service because both of these parameters are needed to know which row should be evaluated in the 'Prolonged Duration Configuration' grid. The logic for evaluating if Avatar should automatically generate a prolonged duration add-on service will not occur within the progress note form until all three parameters Practitioner Category, Location and Duration have been entered.
  2. If the duration entered in the 'Service Duration' field exceeds the duration specified for the service code in the 'Max Duration Primary Service Must Exceed for Prolonged Duration Add-On Service to Generate' column in the 'Prolonged Duration Configuration' grid., Avatar will file the duration amount entered in the 'Max Duration Primary Service Must Exceed for Prolonged Duration Add-On Service to Generate' column in the 'Prolonged Duration Configuration' grid for the primary service code when the service is created.
  3. If the remaining duration amount above the duration specified for the primary service code in the new 'Max Duration Primary Service Must Exceed for Prolonged Duration Add-On Service to Generate' column in the 'Prolonged Duration Configuration' grid, is equal to or greater than the amount entered in the 'Minimum Remaining Duration to be Met for Prolonged Duration Add-On Service to Generate' column in the 'Prolonged Duration Configuration' grid, then system automatically create and 'save' the add-on service for prolonged duration that is specified for the primary service code in the 'Service Code to Use For Prolonged Duration' field in the 'Service Codes' form. File the remaining duration amount as the duration for the add-on service when created. This entry within the 'Select Multiple Add-On Codes' field will not be editable via the 'Select Add-On Service Entry to Edit/Remove' dropdown option prior to finalizing the progress note. The Prolonged Duration Add-On Service that Avatar generates automatically will be displayed as the first row in the 'Selected Add-On Services' field.
  4. If the value entered for the 'Practitioner', 'Location' or 'Service Duration' field are changed, Avatar will need to rerun the process/logic to evaluate if that updated duration exceeds the duration specified for the service code in the 'Max Duration Primary Service Must Exceed for Prolonged Duration Add-On Service to Generate Column' column in the Prolonged Duration Configuration grid and update the add-on row that was system generated to now list the appropriate add-on duration amount. Likewise, if the updated duration entered in the 'Service Duration' field does now not exceed the duration specified for the service code in the 'Max Duration Primary Service Must Exceed for Prolonged Duration Add-On Service to Generate' column in the 'Prolonged Duration Configuration' grid, Avatar will remove the row that was previously saved as a prolonged duration add-on is no longer needed. The same idea will extend to the Practitioner Category, Location, and Minimum Remaining Duration to be Met for Prolonged Duration Add-On Service to Generate columns that can be configured in the Prolonged Duration Configuration grid. If the Location or practitioner is changed – that will need to reevaluate the logic configured for that in the Prolonged Duration Configuration grid.

Steps
  1. Open the 'Inpatient Progress Notes' form.
  2. Select desired client from the ‘Select Client’ field by name or ID.
  3. Select desired episode in the 'Select Episode' field.
  4. Select ‘New Service’ in the 'Progress Note For' field.
  5. Enter any value in the 'Note Type' field.
  6. Enter any value in the 'Notes Field' field.
  7. Enter desired date in the 'Date Of Service' field that falls within the ‘Effective Date’ and Expiration Date’ defined in one of the ‘Prolonged Duration Configuration’ grid for the service code in the ‘Service Code’ form. Select desired value in the 'Service Charge Code' field that match.
  8. Enter the 'Evaluation Management', 'Primary Code' defined in the setup.
  9. Validate the prolonged duration service codes displays in the ‘Add On Services’ field to be manually selected and that no 'Add-On Service' was automatically created.
  10. Select the 'Practitioner' whose practitioner category matches with the practitioner category defined in one of the ‘Practitioner Category’ column of the ‘Prolonged Duration Configuration’ grid for the service code in the ‘Service Code’ form. Note the row #.
  11. Select the 'Location' of the service that matches with the location code with the location defined in one of the ‘Location’ column of the ‘Prolonged Duration Configuration’ grid for the service code in the ‘Service Code’ form. Note the row #.
  12. Enter desired duration in the ‘Service Duration’ that is above the 'Max Duration Primary Service Must Exceed For Prolonged Duration Add-On Service to Generate' and has enough surplus over that so that the remaining duration is greater than or equal to 'Minimum Remaining Duration to be Met for Prolonged Duration Add-On Service to Generate' column of the ‘Prolonged Duration Configuration’ grid for the service code in the ‘Service Code’ form.
  13. Verify the prolonged duration service code will be automatically created and added to 'Selected Add-On Services' field.
  14. Select ‘Final’ from the 'Draft/Final' field.
  15. Click [File Note].
  16. Validate a Note Filed message is displayed.
  17. Click [OK].
  18. Click [Close Form].
  19. Open the 'Client Ledger' form.
  20. Select desired client, episode and 'Ledger Type' as 'Simple'.
  21. Click [Process].
  22. Verify the primary service and prolonged add-on service created with the correct units for the service and correct service code.
  23. Close the form.
  24. Open the ‘Registry Setting’ form.
  25. Set the 'Enable Prolonged Duration Add-On Service Generation' registry setting to ‘YR’.
  26. Close the form.
  27. Open the 'Inpatient Progress Notes' form.
  28. Select desired client from the ‘Select Client’ field by name or ID.
  29. Select desired episode in the 'Select Episode' field.
  30. Select ‘New Service’ in the 'Progress Note For' field.
  31. Enter any value in the 'Note Type' field.
  32. Enter any value in the 'Notes Field' field.
  33. Enter desired date in the 'Date Of Service' field that falls within the ‘Effective Date’ and Expiration Date’ defined in one of the ‘Prolonged Duration Configuration’ grid for the service code in the ‘Service Code’ form. Select desired value in the 'Service Charge Code' field that match.
  34. Enter the 'Evaluation Management', 'Primary Code' defined in the setup.
  35. Verify the prolonged duration service codes does not display up in the ‘Add On Services’ field to be manually selected.
  36. Select the 'Practitioner' whose practitioner category that matches with the practitioner category defined in one of the ‘Practitioner Category’ column of the ‘Prolonged Duration Configuration’ grid for the service code in the ‘Service Code’ form. Note the row #.
  37. Select the 'Location' of the service that matches with the location code with the location defined in one of the ‘Location’ column of the ‘Prolonged Duration Configuration’ grid for the service code in the ‘Service Code’ form. Note the row #.
  38. Enter desired duration in the ‘Service Duration’ that is above the 'Max Duration Primary Service Must Exceed For Prolonged Duration Add-On Service to Generate' and has enough surplus over that so that the remaining duration is greater than or equal to 'Minimum Remaining Duration to be Met for Prolonged Duration Add-On Service to Generate' column of the ‘Prolonged Duration Configuration’ grid for the service code in the ‘Service Code’ form.
  39. Verify the prolonged duration service code will be added to 'Selected Add-On Services' and the cost of service will be updated to reflect the cost the primary service will file with (using the max duration).
  40. Change the ‘Service Duration’ to be above the 'Max Duration Primary Service Must Exceed For Prolonged Duration Add-On Service to Generate' but less than the 'Minimum Remaining Duration to be Met for Prolonged Duration Add-On Service to Generate'.
  41. Verify the prolonged duration service code will be removed from the 'Selected Add-On Services' field.
  42. Enter a duration in the ‘Service Duration’ field again that is above the 'Max Duration Primary Service Must Exceed For Prolonged Duration Add-On Service to Generate' and has enough surplus over that so that the remaining duration is greater than or equal to 'Minimum Remaining Duration to be Met for Prolonged Duration Add-On Service to Generate' of the ‘Prolonged Duration Configuration’ grid for the service code in the ‘Service Code’ form.
  43. Verify the prolonged duration service code will be added to 'Selected Add-On Services' field.
  44. Change the 'Service Date', 'Location' and ‘Practitioner’ (category) fields to values that do not match with the values defined for the primary service code in the ‘Prolonged Duration Configuration’ grid in the ‘Service Code’ form.
  45. Verify the prolonged duration service code will be removed from the 'Selected Add-On Services' field.
  46. Change the 'Service Date', 'Location' and ‘Practitioner’ (category) fields to the original values that match with the values defined for the primary service code in the ‘Prolonged Duration Configuration’ grid in the ‘Service Code’ form.
  47. Verify the prolonged duration service code will be added from the 'Selected Add-On Services' field.
  48. Select ‘Final’ from the 'Draft/Final' field.
  49. Click [File Note].
  50. Validate a Note Filed message is displayed.
  51. Click [OK].
  52. Click [Close Form].
  53. Open the 'Client Ledger' form.
  54. Select desired client, episode and 'Ledger Type' as 'Simple'.
  55. Click [Process].
  56. Verify the primary service and prolonged add-on service created with the correct units for the service and correct service code.
  57. Close the form.


Scenario 3: Cal-PM - CWS - Ambulatory Progress Notes - Prolonged Duration
Specific Setup:
  • Registry Settings:
  • The 'Enable Multiple Add-On Code Per Primary' registry setting is set to 'Y'.
  • The 'Enable Prolonged Duration Add-On Service Generation' is set to 'Y'.
  • 'N' disables the functionality.
  • 'Y' enables the functionality and adds the 'Prolonged Duration Configuration' field to the service code form. It also allows users to manually select/submit add-on services in all the progress note forms.
  • 'YR' enables the functionality and adds the 'Prolonged Duration Configuration' field to the service code form. It prevents users from manually selecting/submitting add-on services in all the progress note forms. The add-on service(s) are created automatically based on the values in the 'Prolonged Duration Configuration' grid.
  • Dictionary Update:
  • File= 'Other Tabled File,
  • Data Element -291, Service Code Type'
  • Dictionary Code = 1
  • Dictionary Value = Evaluation Therapy
  • Extended dictionary 'Allow Multiple Add-On Code' = Yes
  • An existing add-on service code is identified with the following values or a new add-on code is created with the following values:
  • Service Code Category = Primary Add-On Code
  • Service Code Type = Evaluation Therapy
  • Minutes per unit = 15
  • Unit Rounding Logic = Round Over 1/2 Unit
  • Designated Degree Of Rounding = Whole Unit
  • Type of Service = Individual
  • All other fields are populated as required/needed.
  • Note the code and definition.
  • An existing add-on service code is identified with the following values or a new add-on code is created with the following values:
  • Service Code Category = Add-On Code
  • Service Code Type = Evaluation Therapy
  • Minutes per unit = 15
  • Unit Rounding Logic = Round Over 1/2 Unit
  • Designated Degree Of Rounding = Whole Unit
  • Type of Service = Individual
  • All other fields are populated as required/needed.
  • Note the code and definition.
  • An existing service code is identified with the following values or a new add-on code is created with the following values::
  • Primary Service = desired service code
  • Service Code Category = Primary Code
  • Service Code Type = Evaluation Therapy
  • Select Add-On Service Code =Primary add-on and an add-on code defined above are selected.
  • Minutes per unit = 15
  • Unit Rounding Logic = Round Over 1/2 Unit
  • Designated Degree Of Rounding = Whole Unit
  • Type of Service = Individual
  • Enable Prolonged Duration Add-On Service Generation = Yes
  • Prolonged Duration Configuration Grid View:
  • Practitioner Category Column - desired practitioner category defined in each grid row. Note the practitioner category.
  • Location - desired location is defined in each grid row. Note the location.
  • Service Code to Use for Prolonged Duration - desired service code
  • Max Duration Primary Service Must Exceed for Prolonged Duration Add-On Service to Generate = desired duration (In minutes, any integer between 0-1440) defined in each grid row. Note the duration defined.
  • Minimum Remaining Duration to be Met for Prolonged Duration Add-On Service to Generate = desired duration (In minutes, any integer between 0-1440) defined in each grid row. Note the duration defined.
  • ·Service Fee/ Cross Reference Maintenance:
  • Primary Service Code - desired duration range is entered and desired fee definition is created.
  • Add-On Service codes = desired duration range is entered and desired fee definition is created.
  • Select an active outpatient client for progress note creation. Note client ID and episode number.
  • Select 1-2 active practitioner to be used for progress note with different practitioner category that matches with the 'Practitioner Category' defined in the 'Prolonged Duration Configuration' Grid. Note practitioner ID and category.
  • Select 1-2 active practitioner to be used for progress note with different practitioner category that does not match with the 'Practitioner Category' defined in the 'Prolonged Duration Configuration' Grid. Note practitioner ID and category.
  • Identify 1-2 dictionary codes/values for the 'Location' to be used for the progress note that matches with the 'Location' defined in the 'Prolonged Duration Configuration' Grid. Note practitioner ID and category.
  • Identify 1-2 dictionary codes/values for the 'Location' to be used for the progress note that matches with the 'Location' defined in the 'Prolonged Duration Configuration' Grid. Note practitioner ID and category.
  • Please review: The prolonged service generation logic:
  1. System identifies the practitioner category and location for the primary service because both of these parameters are needed to know which row should be evaluated in the 'Prolonged Duration Configuration' grid. The logic for evaluating if Avatar should automatically generate a prolonged duration add-on service will not occur within the progress note form until all three parameters Practitioner Category, Location and Duration have been entered.
  2. If the duration entered in the 'Service Duration' field exceeds the duration specified for the service code in the 'Max Duration Primary Service Must Exceed for Prolonged Duration Add-On Service to Generate' column in the 'Prolonged Duration Configuration' grid., Avatar will file the duration amount entered in the 'Max Duration Primary Service Must Exceed for Prolonged Duration Add-On Service to Generate' column in the 'Prolonged Duration Configuration' grid for the primary service code when the service is created.
  3. If the remaining duration amount above the duration specified for the primary service code in the new 'Max Duration Primary Service Must Exceed for Prolonged Duration Add-On Service to Generate' column in the 'Prolonged Duration Configuration' grid, is equal to or greater than the amount entered in the 'Minimum Remaining Duration to be Met for Prolonged Duration Add-On Service to Generate' column in the 'Prolonged Duration Configuration' grid, then system automatically create and 'save' the add-on service for prolonged duration that is specified for the primary service code in the 'Service Code to Use For Prolonged Duration' field in the 'Service Codes' form. File the remaining duration amount as the duration for the add-on service when created. This entry within the 'Select Multiple Add-On Codes' field will not be editable via the 'Select Add-On Service Entry to Edit/Remove' dropdown option prior to finalizing the progress note. The Prolonged Duration Add-On Service that Avatar generates automatically will be displayed as the first row in the 'Selected Add-On Services' field.
  4. If the value entered for the 'Practitioner', 'Location' or 'Service Duration' field are changed, Avatar will need to rerun the process/logic to evaluate if that updated duration exceeds the duration specified for the service code in the 'Max Duration Primary Service Must Exceed for Prolonged Duration Add-On Service to Generate Column' column in the Prolonged Duration Configuration grid and update the add-on row that was system generated to now list the appropriate add-on duration amount. Likewise, if the updated duration entered in the 'Service Duration' field does now not exceed the duration specified for the service code in the 'Max Duration Primary Service Must Exceed for Prolonged Duration Add-On Service to Generate' column in the 'Prolonged Duration Configuration' grid, Avatar will remove the row that was previously saved as a prolonged duration add-on is no longer needed. The same idea will extend to the Practitioner Category, Location, and Minimum Remaining Duration to be Met for Prolonged Duration Add-On Service to Generate columns that can be configured in the Prolonged Duration Configuration grid. If the Location or practitioner is changed – that will need to reevaluate the logic configured for that in the Prolonged Duration Configuration grid.
Steps
  1. Open the 'Ambulatory Progress Notes' form.
  2. Select desired client from the ‘Select Client’ field by name or ID.
  3. Select desired episode in the 'Select Episode' field.
  4. Select ‘New Service’ in the 'Progress Note For' field.
  5. Enter any value in the 'Note Type' field.
  6. Enter any value in the 'Notes Field' field.
  7. Enter desired date in the 'Date Of Service' field that falls within the ‘Effective Date’ and Expiration Date’ defined in one of the ‘Prolonged Duration Configuration’ grid for the service code in the ‘Service Code’ form. Select desired value in the 'Service Charge Code' field that match.
  8. Enter the 'Evaluation Management', 'Primary Code' defined in the setup.
  9. Validate the prolonged duration service codes displays in the ‘Add On Services’ field to be manually selected and that no 'Add-On Service' was automatically created.
  10. Select the 'Practitioner' whose practitioner category that matches with the practitioner category defined in one of the ‘Practitioner Category’ column of the ‘Prolonged Duration Configuration’ grid for the service code in the ‘Service Code’ form. Note the row #.
  11. Select the 'Location' of the service that matches with the location code with the location defined in one of the ‘Location’ column of the ‘Prolonged Duration Configuration’ grid for the service code in the ‘Service Code’ form. Note the row #.
  12. Enter desired duration in the ‘Service Duration’ that is above the 'Max Duration Primary Service Must Exceed For Prolonged Duration Add-On Service to Generate' and has enough surplus over that so that the remaining duration is greater than or equal to 'Minimum Remaining Duration to be Met for Prolonged Duration Add-On Service to Generate' column of the ‘Prolonged Duration Configuration’ grid for the service code in the ‘Service Code’ form.
  13. Verify the prolonged duration service code will be automatically created and added to 'Selected Add-On Services' field.
  14. Select ‘Final’ from the 'Draft/Final' field.
  15. Click [File Note].
  16. Validate a Note Filed message is displayed.
  17. Click [OK].
  18. Click [Close Form].
  19. Open the 'Client Ledger' form.
  20. Select desired client, episode and 'Ledger Type' as 'Simple'.
  21. Click [Process].
  22. Verify the primary service and prolonged add-on service created with the correct units for the service and correct service code.
  23. Close the form.
  24. Open the ‘Registry Setting’ form.
  25. Set the 'Enable Prolonged Duration Add-On Service Generation' registry setting to ‘YR’.
  26. Close the form.
  27. Open the 'Ambulatory Progress Notes' form.
  28. Select desired client from the ‘Select Client’ field by name or ID.
  29. Select desired episode in the 'Select Episode' field.
  30. Select ‘New Service’ in the 'Progress Note For' field.
  31. Enter any value in the 'Note Type' field.
  32. Enter any value in the 'Notes Field' field.
  33. Enter desired date in the 'Date Of Service' field that falls within the ‘Effective Date’ and Expiration Date’ defined in one of the ‘Prolonged Duration Configuration’ grid for the service code in the ‘Service Code’ form. Select desired value in the 'Service Charge Code' field that match.
  34. Enter the 'Evaluation Management', 'Primary Code' defined in the setup.
  35. Verify the prolonged duration service codes does not display in the ‘Add On Services’ field to be manually selected.
  36. Select the 'Practitioner' whose practitioner category that matches with the practitioner category defined in one of the ‘Practitioner Category’ column of the ‘Prolonged Duration Configuration’ grid for the service code in the ‘Service Code’ form. Note the row #.
  37. Select the 'Location' of the service that matches with the location code with the location defined in one of the ‘Location’ column of the ‘Prolonged Duration Configuration’ grid for the service code in the ‘Service Code’ form. Note the row #.
  38. Enter desired duration in the ‘Service Duration’ that is above the 'Max Duration Primary Service Must Exceed For Prolonged Duration Add-On Service to Generate' and has enough surplus over that so that the remaining duration is greater than or equal to 'Minimum Remaining Duration to be Met for Prolonged Duration Add-On Service to Generate' column of the ‘Prolonged Duration Configuration’ grid for the service code in the ‘Service Code’ form.
  39. Verify the prolonged duration service code will be added to 'Selected Add-On Services' and the cost of service will be updated to reflect the cost the primary service will file with (using the max duration).
  40. Change the ‘Service Duration’ to be above the 'Max Duration Primary Service Must Exceed For Prolonged Duration Add-On Service to Generate' but less than the 'Minimum Remaining Duration to be Met for Prolonged Duration Add-On Service to Generate'.
  41. Verify the prolonged duration service code will be removed from the 'Selected Add-On Services' field.
  42. Enter a duration in the ‘Service Duration’ field again that is above the 'Max Duration Primary Service Must Exceed For Prolonged Duration Add-On Service to Generate' and has enough surplus over that so that the remaining duration is greater than or equal to 'Minimum Remaining Duration to be Met for Prolonged Duration Add-On Service to Generate' of the ‘Prolonged Duration Configuration’ grid for the service code in the ‘Service Code’ form.
  43. Verify the prolonged duration service code will be added to 'Selected Add-On Services' field.
  44. Change the 'Service Date', 'Location' and ‘Practitioner’ (category) fields to values that do not match with the values defined for the primary service code in the ‘Prolonged Duration Configuration’ grid in the ‘Service Code’ form.
  45. Verify the prolonged duration service code will be removed from the 'Selected Add-On Services' field.
  46. Change the 'Service Date, 'Location' and ‘Practitioner’ (category) fields to the original values that match with the values defined for the primary service code in the ‘Prolonged Duration Configuration’ grid in the ‘Service Code’ form.
  47. Verify the prolonged duration service code will be added from the 'Selected Add-On Services' field.
  48. Select ‘Final’ from the 'Draft/Final' field.
  49. Click [File Note].
  50. Validate a Note Filed message is displayed.
  51. Click [OK].
  52. Click [Close Form].
  53. Open the 'Client Ledger' form.
  54. Select desired client, episode and 'Ledger Type' as 'Simple'.
  55. Click [Process].
  56. Verify the primary service and prolonged add-on service created with the correct units for the service and correct service code.
  57. Close the form.
Topics
• Progress Notes
Update 28 Summary | Details
SQL Table validation - SYSTEM.tx_plan_recovery_plan
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Treatment Plan
Scenario 1: Verify the Treatment Plan form is checking for required fields when it is submitted
Specific Setup:
  • An application with the new 'Treatment Plan' form must be used.
  • Note: If using the old 'Client Treatment Plan' form disregard this test.
Steps
  1. Open the 'Treatment Plan' form for any client and episode.
  2. Click the [Submit] button.
  3. Verify an error is received warning about missing required fields.
  4. Click the [T] button in the 'Plan Date' field to input today's date.
  5. Enter desired text into the 'Plan Name' field.
  6. Select any value from the 'Plan Type' field.
  7. Select "Draft" from the 'Treatment Plan Status' field.
  8. Add at least 1 row in the 'Problems' grid.
  9. Select "Final" from the ''Treatment Plan Status' field.
  10. Click [Submit].
  11. Verify the form files without errors.
  12. Open the 'Crystal Report' or any other SQL data viewer.
  13. Run the SQL query to retrieve data from the 'SYSTEM.tx_plan' table.
  14. Verify that the data successfully retrieved from the table.
  15. Close the report.
Scenario 2: SYSTEM.tx_plan_recovery_plan - Validating Data Retrieval
Specific Setup:
  • Tester has access to the 'Crystal Report' or any other SQL data viewer for the system.
Steps
  1. Open the 'Crystal Report' or any other SQL data viewer.
  2. Run the SQL query to retrieve data from the 'SYSTEM.tx_plan_recovery_plan' table. Include the 'service_display' field in the query.
  3. Verify that the data was successfully retrieved from the table.
  4. Close the report.
Topics
• Treatment Plan • Database Management
Update 29 Summary | Details
Treatment Plan - Participant Plan and Author Signatures
Scenario 1: Client Merge (InPatient and Outpatient)
Specific Setup:
  • At least two clients must be admitted to active episodes. One client is admitted in the inpatient program and the other client is admitted in the outpatient program. (Client A, and Client B).
Steps
  1. Access the 'Client Merge' form.
  2. Set the 'Source Client' field to "Client A"
  3. Select "Episode # 1" from the 'Source Client Episode' field.
  4. Set the 'Target Client' field to "Client B"
  5. Validate the 'Create New Episode On Merge' field is equal to "Yes"
  6. Click [File]
  7. Validate a 'Do you wish to continue with the indicated action?' message is displayed.
  8. Click [Yes].
  9. Validate a message stating 'The following new episode has been created for the target client indicated. Episode 2' is displayed.
  10. Click [OK].
  11. Click [Close Form]
  12. Using SQL, view the SQL tables SYSTEM.cw_tx_pn_sign_data and SYSTEM.cw_tx_pn_sign_data_audit,validate the date_captured and time_captured columns are populated in the row(s) added. Note: This only affects rows created since the update was installed. Previously filed data will have the columns but they won't be populated.
Scenario 2: Progress Notes (Group and Individual) Copy - Validate 'Treatment Plan' Grid and 'Signature' fields
Specific Setup:
  • Set the registry setting "Enable Treatment Plan Grid" to "Yes".
  • A signature field must be added to a copy of the Progress Note (Group and Individual) using "Site Specific Section Modeling".
  • Using "Document Routing Setup", enable document routing for the progress note copy form.
Steps
  1. Open the copy of the "Progress Notes (Group and Individual)" from setup that has a signature field.
  2. Add an independent progress note.
  3. In the Treatment plan Grid, attach a treatment plan problem.
  4. Click [Sign].
  5. Sign the document by using the signature pad.
  6. Set the "Draft/Final" field to "Final".
  7. Click [Submit].
  8. Enter the "Password".
  9. Validate the document image contains the signature.
  10. Using the preferred method to validate SQL data, validate a row was added to the CWSTEMP.cw_tx_pn_sign_data.
  11. Validate the above temporary table contains a column called date_captured and time_captured are correct based on when the document was signed.
  12. Click [Sign] or [Accept].
  13. Using the "Clinical Document Viewer" form, validate the document displays as it was saved with the signature included
  14. Using the preferred method to validate SQL data, validate a row was added to the SYSTEM.cw_tx_pn_sign_data and SYSTEM.cw_tx_pn_sign_data_audit.
  15. Validate the above SQL table contains a column called date_captured and time_captured are correct based on when the document was signed. Note: This only affects rows created since the update was installed. Previously filed data will have the columns but they won't be populated.
Scenario 3: Treatment Plan - Obtain Signature
Specific Setup:
  • The 'Treatment Plan' form must have a signature field.
  • A client must be enrolled in an existing episode (Client A).
  • Must have a Topaz Signature pad for testing.
  • Citrix Users - Citrix Versions (pre - 7.6) - BSB / BBSB pads are supported.
Steps
  1. Select "Client A" and access the 'Treatment Plan' form.
  2. Enter the desired date in the 'Plan Date' field.
  3. Select the desired value in the 'Plan Type' field.
  4. Select "Draft" in the 'Treatment Plan Status' field.
  5. Click [Launch Plan].
  6. Add the desired treatment plan items.
  7. Click [Return To Plan].
  8. In the "Plan Participants" section of the main page, click [New Row].
  9. Add a row to the Plan Participants table.
  10. Double-click on the "Signature" column of that row.
  11. Double-click [Sign] in the 'Signature' field.
  12. Validate the 'Please Sign Below' dialog is displayed.
  13. Use the mouse to sign in the dialog box.
  14. Validate the dialog contains the signature.
  15. Click [OK].
  16. Validate the 'Please Sign Below' dialog is no longer displayed.
  17. Validate no errors display and the 'Please Sign On Signature Pad' dialog is displayed. Please note: for users using the SigPlusExtLite, the following will display: "Opening signature dialog, please wait..." and an additional dialog will open.
  18. Sign on the signature pad.
  19. Validate the dialog contains the signature.
  20. Click [Cancel].
  21. Disconnect the signature pad.
  22. Double-click [Sign] in the 'Signature' field.
  23. Validate the 'Please Sign Below' dialog is displayed.
  24. Use the mouse to sign in the dialog box.
  25. Validate the dialog contains the signature.
  26. Click [OK].
  27. Validate the 'Please Sign Below' dialog is no longer displayed.
  28. Validate the 'Signature' field contains the signature.
  29. Select "Final" in the 'Treatment Plan Status' field.
  30. Submit the form.
  31. Validate the temporary SQL table CWSTEMP.cw_pn_tx_sign_data has a row added for the 2 treatment Plan grid signatures.
  32. Validate the document image contains all 3 signatures, the 2 from the participant grid and 1 from the form signature.
  33. Click [Sign]
  34. Key in the use's password.
  35. Click [Verify]
  36. Using SQL, view the SQL tables SYSTEM.cw_tx_pn_sign_data and SYSTEM.cw_tx_pn_sign_data_audit, validate the signaturecontent column is populated in the row(s) added. Note: This only affects rows created since the update was installed. Previously filed data will have the columns but they won't be populated.
  37. Using SQL, view the SQL tables SYSTEM.cw_tx_pn_sign_data and SYSTEM.cw_tx_pn_sign_data_audit,validate the date_captured and time_captured columns are populated in the row(s) added. Note: This only affects rows created since the update was installed. Previously filed data will have the columns but they won't be populated.
  38. Open the "Clinical Document Viewer"
  39. Select "Client" from the Select Type: drop down list
  40. Click the Individual radio button
  41. Set the 'Select Client'" to "601"
  42. Click the TAMMY SMITH (000000601) cell
  43. Click [Process]
  44. Click [View] button on row 1
  45. Validate the Signature(s) appear on the finalized form
  46. Click [Print]
  47. Validate the Signature appears on the printed document
  48. Click [Close All Documents]
  49. Click the [Search] tab
  50. Click [Close]
Topics
• Client Merge • Progress Notes • Treatment Plan
Update 32 Summary | Details
'Progress Notes' web service
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 'Evidence-Based Practices' and 'Evidence-Based Practice Elements' field are added to the 'Progress Notes (Group and Individual)' form via 'Site Specific Section Modeling'.
  • 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 the desired value in the 'EvidenceBasedPracticesSingleSelect' field.
  15. Enter the desired value in the 'EvidenceBasedPracticeElements' field.
  16. Enter "Client A's" PATID in the 'ClientID' field.
  17. Enter the desired episode in the 'EpisodeNumber' field.
  18. Enter "CWSPN22000" in the 'Option' field.
  19. Click [Run].
  20. Validate the 'Confirmation' field contains a Unique ID (ex. Unique ID: NOT65244.001).
  21. Validate the 'Message' field contains: Progress Notes web service has been filed successfully.
  22. Select "Client A" and navigate to the 'Progress Notes' widget.
  23. Validate the 'Progress Notes' widget contains the progress note filed via web service in the previous steps.
  24. Validate the 'Evidence-Based Practices' field contains the value filed in the previous steps.
  25. Validate the 'Evidence-Based Practice Elements' field contains the value filed in the previous steps.
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 'Evidence-Based Practices' and 'Evidence-Based Practice Elements' field are added to the 'Progress Notes (Group and Individual)' form via 'Site Specific Section Modeling'.
  • 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 the desired value in the 'EvidenceBasedPracticesSingleSelect' field.
  15. Enter the desired value in the 'EvidenceBasedPracticeElements' field.
  16. Enter "Client A's" PATID in the 'ClientID' field.
  17. Enter the desired episode in the 'EpisodeNumber' field.
  18. Enter the unique ID for the draft note in the 'NoteUniqueID' field.
  19. Enter "CWSPN22000" in the 'Option' field.
  20. Click [Run].
  21. Validate the 'Confirmation' field contains a Unique ID (ex. Unique ID: NOT65244.001).
  22. Validate the 'Message' field contains: Progress Notes web service has been filed successfully.
  23. Select "Client A" and navigate to the 'Progress Notes' widget.
  24. Validate the 'Progress Notes' widget contains the progress note updated via web service in the previous steps.
  25. Validate the 'Evidence-Based Practices' field contains the value filed in the previous steps.
  26. Validate the 'Evidence-Based Practice Elements' field contains the value filed in the previous steps.
Scenario 3: 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 'Evidence-Based Practices' and 'Evidence-Based Practice Elements' field are added to the 'Progress Notes (Group and Individual)' form via 'Site Specific Section Modeling'.
  • 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 the desired value in the 'EvidenceBasedPracticesSingleSelect' field.
  15. Enter the desired value in the 'EvidenceBasedPracticeElements' field.
  16. Enter "Client A's" PATID in the 'ClientID' field.
  17. Enter the desired episode in the 'EpisodeNumber' field.
  18. Enter "CWSPN22000" in the 'Option' field.
  19. Click [Run].
  20. Validate the 'Confirmation' field contains a Unique ID (ex. Unique ID: NOT65244.001).
  21. Validate the 'Message' field contains: Progress Notes web service has been filed successfully.
  22. Select "Client A" and navigate to the 'Progress Notes' widget.
  23. Validate the 'Progress Notes' widget contains the progress note filed via web service in the previous steps.
  24. Validate the 'Evidence-Based Practices' field contains the value filed in the previous steps.
  25. Validate the 'Evidence-Based Practice Elements' field contains the value filed in the previous steps.
Topics
• Progress Notes • Web Services
Update 33 Summary | Details
Progress Notes - 'Service Duration' field
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Ambulatory Progress Notes
  • Clinical
  • Set System Defaults (CWS)
Scenario 1: Progress Notes (Group and Individual) - File an independent note
Specific Setup:
  • A client must be enrolled in an existing episode (Client A).
  • 'Progress Notes (Group and Individual)' must have document routing enabled.
  • A Documentation View must be set up on a user's view containing the 'All Documents' widget and the 'Console Widget Viewer' ('All Documents' view).
  • A practitioner must be associated with the logged-in user (Practitioner A).
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 "Independent Note" in the 'Progress Note For' field.
  5. Validate the 'Service Duration' field is disabled.
  6. Select the desired value in the 'Note Type' field.
  7. Enter the desired value in the 'Notes Field'.
  8. Enter any value in the 'Recommended Decision Aids' field.
  9. Validate the 'Service Duration' field is disabled.
  10. Populate any other required or desired fields.
  11. Select "Final" in the 'Draft/Final' field.
  12. Click [Submit Note].
  13. Validate a 'Confirm Document' dialog is displayed.
  14. Click [Accept].
  15. Enter the password associated with the logged-in user and click [Verify].
  16. Validate a 'Progress Notes' dialog stating: "Note Filed. Do you want to return to the Progress Notes form?" and click [No].

2. Select "Client A" and navigate to the 'All Documents' view.

  1. Select 'All Forms'.
  2. Select "Progress Notes (Group and Individual)" from the 'Form Description' field.
  3. Validate that the note from the previous steps is present and select it.
  4. Validate the progress note displays as expected in the 'Console Widget Viewer'.
Progress Notes - 'Service Status' field
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Ambulatory Progress Notes
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 'Evidence-Based Practices' and 'Evidence-Based Practice Elements' field are added to the 'Progress Notes (Group and Individual)' form via 'Site Specific Section Modeling'.
  • 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 the desired value in the 'EvidenceBasedPracticesSingleSelect' field.
  15. Enter the desired value in the 'EvidenceBasedPracticeElements' field.
  16. Enter "Client A's" PATID in the 'ClientID' field.
  17. Enter the desired episode in the 'EpisodeNumber' field.
  18. Enter "CWSPN22000" in the 'Option' field.
  19. Click [Run].
  20. Validate the 'Confirmation' field contains a Unique ID (ex. Unique ID: NOT65244.001).
  21. Validate the 'Message' field contains: Progress Notes web service has been filed successfully.
  22. Select "Client A" and navigate to the 'Progress Notes' widget.
  23. Validate the 'Progress Notes' widget contains the progress note filed via web service in the previous steps.
  24. Validate the 'Evidence-Based Practices' field contains the value filed in the previous steps.
  25. Validate the 'Evidence-Based Practice Elements' field contains the value filed in the previous steps.
Scenario 2: Validate the Chart View for Existing Service Progress Notes
Specific Setup:
  • The 'Fields to Include in Client Charge Input' registry setting must have "6" selected for 'Service Status'.
  • Service status(es) must be defined in the 'Service Status Maintenance' form.
  • A client must be enrolled in an existing episode and have an existing service (Client A).
  • The existing service must have 'Service Status' populated.
  • 'Progress Notes (Group and Individual)' must be added to the Chart View.
Steps
  1. Access the 'Progress Notes (Group and Individual)' form.
  2. Enter "Client A" in the 'Select Client' field.
  3. Select the desired value in the 'Select Episode' field.
  4. Select "Existing Service" in the 'Progress Notes For' field.
  5. Select the existing service for "Client A" in the 'Note Addresses Which Existing Service/Appointment' field.
  6. Select any value in the 'Note Type' field.
  7. Enter any value in the 'Notes Field' field.
  8. Validate the 'Service Status' field contains the value filed with the service.
  9. Clear the value in the 'Service Status' field.
  10. Select "Final" in the 'Draft/Final' field.
  11. Click [File Note].
  12. Validate a "Progress Notes" message is displayed stating: Note Filed.
  13. Click [OK] and close the form.
  14. Double click on "Client A" in the 'My Clients' widget.
  15. Validate the 'Chart View' is displayed for "Client A".
  16. Select 'Progress Notes (Group and Individual)' from the left-hand side.
  17. Validate the Existing Service note filed in the previous steps is displayed.
  18. Validate the 'Progress Note For' field contains "Existing Service".
  19. Validate the 'Note Type' field contains the note type selected in the previous steps.
  20. Validate the 'Notes Field' field contains the value entered in the previous steps.
  21. Validate the 'Practitioner' field contains the practitioner associated to the service for Client A.
  22. Validate the 'Date of Service' field contains the date of the service for Client A.
  23. Validate the 'Service Program' field contains the service program selected when creating the service.
  24. Validate the 'Service Charge Code' field contains the service code used when creating the service.
  25. Validate the 'Location' field contains the location of the service.
  26. Validate the 'Service Status' field is not displayed.
  27. Validate the 'Draft/Final' field contains "Final".
  28. Close the chart.
Topics
• Progress Notes • Web Services • Group Progress Notes • Chart View
Update 34 Summary | Details
Treatment Plan - PCL Date fields
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Treatment Plan
  • Required User List Management
Scenario 1: Treatment Plan - Validate 'Pending Approval' workflow with PCL date fields
Specific Setup:
  • Please note: this is for Avatar NX only.
  • A client is enrolled in an existing episode (Client A).
  • Document routing must be enabled for the 'Treatment Plan' form.
  • The 'Treatment Plan' form must have the following configured in 'Site Specific Section Modeling':
  • 'SS Treatment Plan Client Date' field with "Use as 'Treatment Plan End Date'" selected in the 'Product Custom Logic Definition' field. This field will be referred to as 'PCL End Date'.
  • 'SS Treatment Plan Client Date' field with "Use as 'Treatment Plan Finalized Date'" selected in the 'Product Custom Logic Definition' field. This field will be referred to as 'PCL Finalized Date'.
  • Two users must be defined with associated staff members (User A & User B).
  • "User A" and "User B" must be defined as workflow users in the 'Required User List Management' form for the 'Treatment Plan'.
Steps
  1. Log into Avatar NX as "User A".
  2. Select “Client A” and access the ‘Treatment Plan’ form.
  3. Enter the desired date in the 'Plan Date' field.
  4. Enter any value in the 'Plan Name' field.
  5. Select any value in the ‘Plan Type’ field.
  6. Enter the desired date in the 'Plan End Date' field.
  7. Validate the 'PCL End Date' and 'PCL Finalized Date' fields are displayed and leave them blank.
  8. Select "Draft" in the 'Treatment Plan Status' field.
  9. Click [Launch Plan].
  10. Add a problem, goal, objective, and intervention.
  11. Populate all required and desired fields.
  12. Click [Return to Plan] and [OK].
  13. Select "Pending Approval" in the 'Treatment Plan Status' field.
  14. Click [Submit].
  15. Validate that a "Confirm Document" message is displayed.
  16. Validate the 'PCL End Date' and 'PCL Finalized Date' fields are not displayed.
  17. Click [Accept and Route].
  18. Validate a "Verify Password" message is displayed.
  19. Enter the password associated with the logged-in user in the 'Password' field.
  20. Click [Verify].
  21. Select the practitioner associated to "User A" as an approver and the practitioner associated to "User B" as an approver/supervisor.
  22. Click [Submit].
  23. Log out.
  24. Log into Avatar NX as "User B".
  25. Navigate to the 'My To Do's' widget.
  26. Click [Documents to Sign].
  27. Validate the To Do for "Client A" is displayed.
  28. Click [Review].
  29. Validate the 'Document Preview' contains the treatment plan data, without the 'PCL End Date' and 'PCL Finalized Date' fields.
  30. Click [Accept] and [Sign].
  31. Validate a "Verify Password" message is displayed.
  32. Enter the password associated with the logged-in user in the 'Password' field.
  33. Click [Verify].
  34. Validate the To Do for "Client A" is no longer displayed.
  35. Log out.
  36. Log into Avatar NX as "User A".
  37. Navigate to the 'My To Do's' widget.
  38. Click [Documents to Sign].
  39. Validate the To Do for "Client A" is displayed.
  40. Click [Review].
  41. Validate the 'Document Preview' contains the treatment plan data.
  42. Validate the 'PCL End Date' and 'PCL Finalized Date' fields are appended to the end of the document. If there are multiple approvers, these fields will only become visible when the last approver goes to approve the document.
  43. Click [Accept] and [Sign].
  44. Validate a "Verify Password" message is displayed.
  45. Enter the password associated with the logged-in user in the 'Password' field.
  46. Click [Verify].
  47. Validate the To Do for "Client A" is no longer displayed.
Scenario 2: Treatment Plan - Validate 'Final' workflow with PCL Date fields
Specific Setup:
  • A client is enrolled in an existing episode (Client A).
  • Document routing must be enabled for the 'Treatment Plan' form.
  • The 'Treatment Plan' form must have the following configured in 'Site Specific Section Modeling':
  • 'SS Treatment Plan Client Date' field with "Use as 'Treatment Plan End Date'" selected in the 'Product Custom Logic Definition' field. This field will be referred to as 'PCL End Date'.
  • 'SS Treatment Plan Client Date' field with "Use as 'Treatment Plan Finalized Date'" selected in the 'Product Custom Logic Definition' field. This field will be referred to as 'PCL Finalized Date'.
  • The logged in user must have an associated practitioner.
Steps
  1. Select “Client A” and access the ‘Treatment Plan’ form.
  2. Enter the desired date in the 'Plan Date' field.
  3. Enter any value in the 'Plan Name' field.
  4. Select any value in the ‘Plan Type’ field.
  5. Enter the desired date in the 'Plan End Date' field.
  6. Validate the 'PCL End Date' and 'PCL Finalized Date' fields are displayed and leave them blank.
  7. Select "Draft" in the 'Treatment Plan Status' field.
  8. Click [Launch Plan].
  9. Add a problem, goal, objective, and intervention.
  10. Populate all required and desired fields.
  11. Click [Return to Plan] and [OK].
  12. Select "Final" in the 'Treatment Plan Status' field.
  13. Click [Submit].
  14. Validate that a "Confirm Document" message is displayed.
  15. Validate the 'PCL End Date' and 'PCL Finalized Date' fields are displayed in the body of the document.
  16. Click [Accept and Route].
  17. Validate a "Verify Password" message is displayed.
  18. Enter the password associated with the logged-in user in the 'Password' field.
  19. Click [Verify].
  20. Select the practitioner associated to the logged in user as an approver.
  21. Click [Submit].
  22. Navigate to the 'My To Do's' widget.
  23. Click [Documents to Sign].
  24. Validate the To Do for "Client A" is displayed.
  25. Click [Review].
  26. Validate the 'Document Preview' contains the treatment plan data, with the 'PCL End Date' and 'PCL Finalized Date' fields in the body of the document.
  27. Click [Accept] and [Sign].
  28. Validate a "Verify Password" message is displayed.
  29. Enter the password associated with the logged-in user in the 'Password' field.
  30. Click [Verify].
  31. Validate the To Do for "Client A" is no longer displayed.
Scenario 3: Treatment Plan - Add a Problem, Goal, Objective, and Intervention with the 'Enable Automatic Backup' registry setting set to "Y"
Specific Setup:
  • The 'Avatar CWS->Treatment Plan->->->->Enable Automatic Backup' registry setting must be set to "Y".
  • A client must be enrolled in an existing episode (Client A).
Steps
  1. Select “Client A” and access the ‘Treatment Plan’ form.
  2. Set the ‘Plan Date’ field to the current date.
  3. Set the ‘Plan Name’ to any value.
  4. Select any value in the ‘Plan Type’ field.
  5. Set the 'Strengths' field to any value.
  6. Set the 'Weaknesses' field to any value.
  7. Set the 'Discharge Planning' field to any value.
  8. Select “Draft” in the ‘Treatment Plan Status’ field and click [Launch Plan].
  9. Click [Add New Problem], [Add New Goal], [Add New Objective] and [Add New Intervention].
  10. Without populating the required fields, click [Return to Plan].
  11. Select "Final" in the 'Treatment Plan Status' field.
  12. Validate a 'Missing Required Fields' dialog is displayed.
  13. Click [OK].
  14. Validate "Draft" remains selected in the 'Treatment Plan Status' field.
  15. Click [Launch Plan].
  16. Select the problem added in the previous steps.
  17. Set the ‘Problem Code’ field to any value.
  18. Select “Active” in the ‘Status (Problem List)’ field.
  19. Set the ‘Problem’ field to any value.
  20. Select any value in the ‘Status’ field.
  21. Select any value in the 'Staff Assigning' field.
  22. Select any value in the 'Staff Responsible' field.
  23. Select the goal added in the previous steps.
  24. Set the ‘Goal’ field to any value.
  25. Select any value in the ‘Status’ field.
  26. Select any value in the 'Staff Assigning' field.
  27. Select any value in the 'Staff Responsible' field.
  28. Select the objective added in the previous steps.
  29. Set the ‘Objective’ field to any value.
  30. Select any value in the ‘Status’ field.
  31. Select any value in the 'Staff Assigning' field.
  32. Select any value in the 'Staff Responsible' field.
  33. Select the intervention added in the previous steps.
  34. Set the ‘Intervention’ field to any value.
  35. Select any value in the ‘Status’ field.
  36. Select any value in the 'Staff Assigning' field.
  37. Select any value in the 'Staff Responsible' field.
  38. Click [Back to Plan Page] and close the form.
  39. Select “Client A” and access the ‘Treatment Plan’ form.
  40. Validate the ‘Load From Backup’ dialog displays with a message stating: "You have an unsubmitted backup of a plan from [the current date] and [the current time]. Would you like to load it instead of creating a new one?" and click [Yes].
  41. Validate the 'Strengths' field contains the value previously filed.
  42. Validate the 'Weaknesses' field contains the value previously filed.
  43. Validate the 'Discharge Planning' field contains the value previously filed.
  44. Click [Launch Plan].
  45. Validate the ‘Tree view’ contains values for the problem, goal, objective, and intervention previously added with all updated data.
  46. Click [Exit to Home View].
Scenario 4: Treatment Plan - File a Treatment Plan with Document Routing
Specific Setup:
  • The client is enrolled in an existing episode (Client A).
  • The 'Treatment Plan' form must have document routing enabled.
  • Must have the 'My To Do's' widget configured on a view.
  • The 'Set Current Status To Active When Plan Is Finalized' registry setting is set to "N" for the 'Treatment Plan' form.
  • The 'Set Current Status To Completed On Plan End Date' registry setting is set to "N" for the 'Treatment Plan' form.
  • The 'Enable Automatic Backup' registry setting is set to "N".
  • Must have a Word document with text containing smart quotes (Text A).
Steps
  1. Select "Client A" and access the 'Treatment Plan' form.
  2. Click [Add].
  3. Enter the current date displayed in the 'Plan Date' field.
  4. Select the desired date in the 'Plan Date' field.
  5. Select the desired value in the 'Plan Type' field
  6. Select "Draft" in the 'Treatment Plan Status' field.
  7. Enter any value in the 'Strength' field.
  8. Click on the [Text Editor] icon for the 'Strength Field'.
  9. Copy "Text A" from the Word document and paste it into the 'Text Editor'.
  10. Click [Save].
  11. Validate that the 'Strength Field' contains the value from "Text A".
  12. Validate "Draft" is now selected in the 'Current Status' field.
  13. Click [Launch Plan].
  14. Add a problem, goal, objective, and intervention.
  15. Click [Return to Plan] and [OK].
  16. Validate the 'Plan Date' field is disabled.
  17. Select "Final" in the 'Draft/Final' field.
  18. Select "Active" in the 'Current Status' field.
  19. Click [Submit].
  20. Validate a 'Confirm Document' dialog is displayed.
  21. Validate all treatment plan data displays as expected. Please note: the 'Current Status' field will not be included in the document image. This is because the 'Current Status' field can be updated after a 'Treatment Plan' has been finalized.
  22. Click [Accept].
  23. Enter the password and click [Verify].
  24. Select "Client A" and access the 'Treatment Plan' form.
  25. Select the record from the previous steps and click [Edit].
  26. Validate a message is displayed stating: This plan is marked as Final. Only the following field(s) may be updated: 'Current Status'. Do you want to continue?
  27. Click [Yes].
  28. Validate the plan displays as expected and fields are disabled, except for the 'Current Status' field.
  29. Select "Completed" in the 'Current Status' field.
  30. Click [Submit].
  31. Validate a message is displayed stating: The following fields are updated: 'Current Status'.
  32. Click [OK].
  33. Select "Client A" and access the 'Treatment Plan' form.
  34. Select the record from the previous steps and click [Edit].
  35. Validate a message is displayed stating: This plan is marked as Final. Only the following field(s) may be updated: 'Current Status'. Do you want to continue?
  36. Click [Yes].
  37. Validate "Completed" is selected in the 'Current Status' field.
  38. Close the form.
Topics
• Treatment Plan • Document Routing
Update 36 Summary | Details
Care Record Mapping - 'Social Drivers of Health' assessment type
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Care Record Mapping
Scenario 1: Validate the 'Social Drivers of Health' assessment type in the 'Care Record Mapping' form
Specific Setup:
  • A user modeled "Social Drivers of Health" form is defined and flagged as an assessment in the 'Flag Assessment Forms' form. This form has the following fields:
  • Assessment Date
  • Performing Provider
  • Reason For Not Screening
  • A client is enrolled in an existing episode (Client A).
Steps
  1. Access the 'Care Record Mapping' form.
  2. Validate the 'Type of Assessment' field contains "Social Drivers of Health".
  3. Select "Social Drivers of Health" in the 'Type of Assessment' field.
  4. Select the user defined "Social Drivers of Health" form in the 'Form To Map' field.
  5. Select "Social Drivers of Health" in the 'Section' field.
  6. Map the desired fields. Available fields are: 'Assessment Date', 'Performing Provider', 'Reason For Not Screening'.
  7. Click [Save Mapping] once complete.
  8. Close the form.
  9. Select "Client A" and access the user defined "Social Drivers of Health" form.
  10. Populate all required and desired fields.
  11. Click [Submit].
  12. Access the 'CareFabric Monitor' form.
  13. Enter the current date in the 'From Date' and 'Through Date' fields.
  14. Enter "Client A" in the 'Client ID' field.
  15. Enter "EhrAssessmentResultCreated" in the 'Event/Action Search' field.
  16. Click [View Activity Log].
  17. Validate the 'CareFabric Monitor Report' contains an "EhrAssessmentResultCreated" record.
  18. Click [Click To View Record].
  19. Validate the 'assessmentTypeCode' - 'code' field contains "40".
  20. Validate the 'assessmentTypeCode' - 'displayName' field contains "Social Drivers of Health".
  21. Validate the 'clientID' - 'id' field contains Client A's ID
  22. Validate the 'vocabularies' - 'code' field contains "68899-4".
  23. Validate the 'vocabularies' - 'codeSystem' field contains "2.16.840.1.113883.6.1".
  24. Validate the 'vocabularies' - 'codeSystemName' field contains "LOINC".
  25. Validate the 'vocabularies' - 'displayName' field contains "Social Drivers of Health".
  26. Close the report and the form.
Topics
• Care Record Mapping
Update 39 Summary | Details
Block Client Chart - Emergency Access
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Add New Appointment
  • Group Registration
  • Block Client Chart
  • Front Desk
  • Post Staff Activity Log
Scenario 1: Block Client Chart - Validate emergency access in the 'Progress Notes' widget
Specific Setup:
  • A client is enrolled in an existing episode and has progress notes on file (Client A).
  • The 'Progress Notes' widget is accessible from the HomeView.
Steps
  1. Access the 'Block Client Chart' form.
  2. Select the "Blocked Clients" section.
  3. Click [Add New Item].
  4. Select "Client A" in the 'Select Client' field.
  5. Select "Yes" in the 'Allow Emergency Access for User/User Role' field.
  6. Select "Yes - All" in the 'Block User Roles' field.
  7. Select "Yes - All" in the 'Block Users' field.
  8. Populate any other desired fields.
  9. Submit the form.
  10. Search for and select "Client A".
  11. Validate a 'Blocked Client' message is displayed stating: User, "Client A" chart is blocked. Your access of this client on 'Day/Date/Time' will be recorded within the database. Why are you accessing "Client A"?
  12. Enter the desired value and click [OK].
  13. Validate "Client A" is now selected.
  14. Navigate to the 'Progress Notes' widget.
  15. Validate progress notes are displayed as expected.
Topics
• Progress Notes
Update 40 Summary | Details
Allergies and Hypersensitivities - 'History' column
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Change MR#
  • Delete Last Movement
Scenario 1: Allergies and Hypersensitivities - Validate 'Change MR#' functionality
Specific Setup:
  • A client is enrolled in an existing episode (Client A).
Steps
  1. Select "Client A" and access the 'Allergies and Hypersensitivities' form.
  2. Select "No" in the 'Known Medication Allergies' field.
  3. Select "No" in the 'Known Food Allergies' field.
  4. Click [Update].
  5. Validate the 'Allergies and Hypersensitivities' grid is displayed.
  6. Click [New Row].
  7. Validate the current date displays as expected in the 'Date Recorded' field.
  8. Search for and select the desired value in the 'Allergen/Reactant' field.
  9. Enter the desired date in the 'Date Recognized' field.
  10. Select the desired value in the 'Status' field.
  11. Select the desired value in the 'Reactions' field.
  12. Select the desired value in the 'Reaction Severity' field.
  13. Enter the desired value in the 'Onset' field.
  14. Enter the desired value in the 'Treatment' field.
  15. Enter the desired value in the 'Comments' field.
  16. Validate the 'History' column is displayed.
  17. Click [Save].
  18. Validate the 'Allergies and Hypersensitivities' grid is no longer displayed.
  19. Click [Update].
  20. Validate the allergy added in the previous steps is displayed as expected.
  21. Click [View] in the 'History' field.
  22. Validate 'History' dialog displays a row with the following data:
  23. Action - Added
  24. Date
  25. Allergen/Reactant
  26. Status
  27. Reaction Severity
  28. User
  29. Close the dialog.
  30. Select any new value in the 'Status' field.
  31. Click [Save] and [Submit].
  32. Access the 'Change MR#' form.
  33. Select "Client A" in the 'Client ID' field.
  34. Click [Assign MR#] and [Yes].
  35. Validate the 'New Client ID#' field contains a new ID for "Client A".
  36. Submit the form.
  37. Validate the ID# for "Client A" has been updated.
  38. Select "Client A" and access the 'Allergies and Hypersensitivities' form.
  39. Click [Update].
  40. Validate the allergy filed in the previous steps is displayed as expected.
  41. Click [View] in the 'History' field.
  42. Validate 'History' dialog displays a row with the following data:
  43. Action - Added
  44. Date
  45. Allergen/Reactant
  46. Status
  47. Reaction Severity
  48. User
  49. Close the form.
Scenario 2: Allergies and Hypersensitivities - Add/Edit Allergies
Specific Setup:
  • A client must have an active episode. (Client A)
Steps
  1. Select "Client A" and access the 'Allergies and Hypersensitivities' form.
  2. Select "No" in the 'Known Medication Allergies' field.
  3. Select "No" in the 'Known Food Allergies' field.
  4. Click [Update].
  5. Validate the 'Allergies and Hypersensitivities' grid is displayed.
  6. Click [New Row].
  7. Validate the current date displays as expected in the 'Date Recorded' field.
  8. Search for and select the desired value in the 'Allergen/Reactant' field.
  9. Enter the desired date in the 'Date Recognized' field.
  10. Select the desired value in the 'Status' field.
  11. Select the desired value in the 'Reactions' field.
  12. Select the desired value in the 'Reaction Severity' field.
  13. Enter the desired value in the 'Onset' field.
  14. Enter the desired value in the 'Treatment' field.
  15. Enter the desired value in the 'Comments' field.
  16. Validate the 'History' column is displayed.
  17. Click [Save].
  18. Validate the 'Allergies and Hypersensitivities' grid is no longer displayed.
  19. Click [Update].
  20. Validate the allergy added in the previous steps is displayed as expected.
  21. Click [View] in the 'History' field.
  22. Validate 'History' dialog displays a row with the following data:
  23. Action - Added
  24. Date
  25. Allergen/Reactant
  26. Status
  27. Reaction Severity
  28. User
  29. Close the dialog.
  30. Select any new value in the 'Status' field.
  31. Click [Save] and [Submit].
  32. Select "Client A" and access the 'Allergies and Hypersensitivities' form.
  33. Click [Update].
  34. Validate the allergy filed in the previous steps is displayed with the updated 'Status'.
  35. Click [View] in the 'History' field.
  36. Validate the 'History' dialog displays a second row with the following data:
  37. Action - Updated
  38. Date
  39. Allergen/Reactant
  40. Status - Contains the updated 'Status'
  41. Reaction Severity
  42. User
  43. Close the dialog and the form.
Scenario 3: Allergies and Hypersensitivities - Validate 'Client Merge' functionality
Specific Setup:
  • Two clients are enrolled in existing episodes (Client A & Client B).
Steps
  1. Select "Client A" and access the 'Allergies and Hypersensitivities' form.
  2. Select "No" in the 'Known Medication Allergies' field.
  3. Select "No" in the 'Known Food Allergies' field.
  4. Click [Update].
  5. Validate the 'Allergies and Hypersensitivities' grid is displayed.
  6. Click [New Row].
  7. Validate the current date displays as expected in the 'Date Recorded' field.
  8. Search for and select the desired value in the 'Allergen/Reactant' field.
  9. Enter the desired date in the 'Date Recognized' field.
  10. Select the desired value in the 'Status' field.
  11. Select the desired value in the 'Reactions' field.
  12. Select the desired value in the 'Reaction Severity' field.
  13. Enter the desired value in the 'Onset' field.
  14. Enter the desired value in the 'Treatment' field.
  15. Enter the desired value in the 'Comments' field.
  16. Validate the 'History' column is displayed.
  17. Click [Save].
  18. Validate the 'Allergies and Hypersensitivities' grid is no longer displayed.
  19. Click [Update].
  20. Validate the allergy added in the previous steps is displayed as expected.
  21. Click [View] in the 'History' field.
  22. Validate 'History' dialog displays a row with the following data:
  23. Action - Added
  24. Date
  25. Allergen/Reactant
  26. Status
  27. Reaction Severity
  28. User
  29. Close the dialog.
  30. Select any new value in the 'Status' field.
  31. Click [Save] and [Submit].
  32. Access the 'Client Merge' form.
  33. Select "Client A" in the 'Source Client' field.
  34. Select "Yes" in the 'Merge All Client Data Through Single Filing' field.
  35. Select "Client B" in the 'Target Client' field.
  36. Select "Yes" in the 'Create New Episode On Merge' field.
  37. Click [File] and [Yes].
  38. Validate a message is displayed stating: All information has been merged into the target client and the source client has been deleted from the system.
  39. Click [OK] and close the form.
  40. Select "Client B" and access the 'Allergies and Hypersensitivities' form.
  41. Click [Update].
  42. Validate the allergy merged from "Client A" is displayed as expected.
  43. Click [View] in the 'History' field.
  44. Validate 'History' dialog displays a row with the following data:
  45. Action - Added
  46. Date
  47. Allergen/Reactant
  48. Status
  49. Reaction Severity
  50. User
  51. Close the form.
Topics
• Allergies and Hypersensitivities
Update 43 Summary | Details
Table Definition - 'Pathway Name' field aliasing
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Clinical Pathway Definition
  • Clinical Pathway Enrollment
  • Clinical Pathway Disenrollment
  • Table Definition (CWS)
Scenario 1: Clinical Pathway Enrollment - Table Aliasing
Specific Setup:
  • A client must be enrolled in an existing episode (Client A).
  • One or more pathways defined in the 'Clinical Pathway Definition' form.
  • A user defined modeled form is required that contains the following fields: 'Date of Enrollment', 'Pathway Name', and 'Primary Pathway'. This form will be referred to as "Form A". "Form A" is associated to the table described below.
  • The following must be configured in the 'Table Definition' form- this table will be referred to as "Table A":
  • In the "Column Definition" section:
  • Add a row for 'Pathway Name' with: "Yes" selected in 'Is This Column An Alias To Another Column?', "CWS" selected in 'Alias Type', "(5011) Pathway Name" selected in 'Alias Column'.
  • Add a row for 'Date of Enrollment'.
  • Add a row for 'Primary Pathway'.
  • In the "Table Alias" section, add a row and select "CWS" as the 'Alias Entity Database' and "Clinical Pathway Enrollment" as the 'Alias Table'.
  • In the "Column Mapping" section, add a row and select the column created for "Pathway Name" in the 'Table Column' field and select "Pathway Name" in the 'Alias Table Column' field. Add a second row and select the column created for 'Primary Pathway' in the 'Table Column' field and select "Primary Pathway" in the 'Alias Table Column' field.
Steps
  1. Access the 'Table Definition' form.
  2. Select "Table A" in the 'Select Table' dialog.
  3. Select the "Column Definition" section.
  4. Select the column for "Pathway Name".
  5. Validate the 'Type of Column' is "Dictionary - Single Response".
  6. Close the form.
  7. Select "Client A" and access "Form A".
  8. Validate the 'Pathway Name' field is a single-select dictionary field with all defined pathways.
  9. Select the desired pathway in the 'Pathway Name' field.
  10. Select "Yes" in the 'Primary Pathway' field.
  11. Click [Submit].
  12. Select "Client A" and access the 'Clinical Pathway Enrollment' form.
  13. Validate the enrollment filed in "Form A" is displayed.
  14. Click [Edit].
  15. Validate the previously filed values are displayed as expected.
  16. Close the form.
Clinical Pathway Definition - Edit a pathway
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Clinical Pathway Definition
  • Clinical Pathway Enrollment
  • Clinical Pathway Disenrollment
Scenario 1: 'Clinical Pathway Definition' form - Edit a pathway
Specific Setup:
  • A client must be enrolled in an existing episode (Client A).
  • The 'Include Client Information header in view' setting is enabled for the user's myDay view.
  • "Clinical Pathway" must be added to the 'Field to Include in Client Header' field in the 'Client Lookup/Header Configuration Manager' form.
Steps
  1. Access the 'Clinical Pathway Definition' form.
  2. Select "New" in the 'Create New or Edit Existing' field.
  3. Enter an alphanumeric value in the 'Pathway ID' field.
  4. Enter "Pathway A" the 'Pathway Name' field.
  5. Select "Yes" in the 'Alert When Client is Accessed?' field. This will cause an alert to display whenever the client is accessed.
  6. Select any value in the 'Appointment Status to Alert' field. This field will trigger an alert when an appointment with this status takes place.
  7. To highlight the pathway using a specific color, enter the color code. Must be in the format of '#FBD9D9'.
  8. Click [Import Icon].
  9. Navigate to the location of the icon and select the icon. When a client is assigned this clinical pathway, the icon will display on the Client Header banner.
  10. Click [Submit].
  11. Select "Client A" and access the 'Clinical Pathway Enrollment' form.
  12. Verify the 'Date of Enrollment' field defaults to the current date.
  13. Select "Pathway A" in the 'Pathway Name' field.
  14. Select "Yes" for 'Primary Pathway'.
  15. Click [Submit] and [No].
  16. Access the 'Clinical Pathway Definition' form.
  17. Select "Edit Existing" in the 'Create New or Edit Existing' field.
  18. Select "Pathway A" in the 'Pathway List' field.
  19. Enter any new value in the 'Pathway Name' field.
  20. Click [Submit] and [No].
  21. Select "Client A" and navigate to the 'Client Information' header.
  22. Navigate to the client alert and validate it displays: Select Client is Enrolled in the following Clinical Pathways: Updated name for "Pathway A".
  23. Access Crystal Reports or other SQL Reporting tool.
  24. Create a report using the 'SYSTEM.Clinical_Pathway_Enrollments' table.
  25. Navigate to the row for "Client A".
  26. Validate the 'pathway_name' field contains the updated name for "Pathway A".
  27. Close the report.
Topics
• Clinical Pathway
Update 45 Summary | Details
Observer NX - future functionality
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Manage Nursing Caseload
  • Nursing Caseload Assignment
  • Observer.Observation
Scenario 1: Observer NX - Validate filing an observation for 5 minute interval
Steps

Internal Testing Only.

Scenario 2: Observer NX - Validate transfers in the "Observer.caseload_audit" table
Steps

Internal Testing Only.

Scenario 3: Observer NX - Validate filing an observation for 10 minute interval
Steps

Internal Testing Only.

Scenario 4: Observer NX - Validate filing an observation for 15 minute interval
Steps

Internal Testing Only.

Scenario 5: Observer NX - Validate filing an observation for 30 minute interval
Steps

Internal Testing Only.

Scenario 6: Observer NX - Validate filing an observation for 60 minute interval
Steps

Internal Testing Only.
Topics
• Observer NX • NX Only
Update 47 Summary | Details
'Treatment Plan' - required fields
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Treatment Plan
Scenario 1: Treatment Plan - Add a Problem, Goal, Objective, and Intervention with the 'Enable Automatic Backup' registry setting set to "Y"
Specific Setup:
  • The 'Avatar CWS->Treatment Plan->->->->Enable Automatic Backup' registry setting must be set to "Y".
  • A client must be enrolled in an existing episode (Client A).
Steps
  1. Select “Client A” and access the ‘Treatment Plan’ form.
  2. Set the ‘Plan Date’ field to the current date.
  3. Set the ‘Plan Name’ to any value.
  4. Select any value in the ‘Plan Type’ field.
  5. Set the 'Strengths' field to any value.
  6. Set the 'Weaknesses' field to any value.
  7. Set the 'Discharge Planning' field to any value.
  8. Select “Draft” in the ‘Treatment Plan Status’ field and click [Launch Plan].
  9. Click [Add New Problem], [Add New Goal], [Add New Objective] and [Add New Intervention].
  10. Without populating the required fields, click [Return to Plan].
  11. Select "Final" in the 'Treatment Plan Status' field.
  12. Validate a 'Missing Required Fields' dialog is displayed.
  13. Click [OK].
  14. Validate "Draft" remains selected in the 'Treatment Plan Status' field.
  15. Click [Launch Plan].
  16. Select the problem added in the previous steps.
  17. Set the ‘Problem Code’ field to any value.
  18. Select “Active” in the ‘Status (Problem List)’ field.
  19. Set the ‘Problem’ field to any value.
  20. Select any value in the ‘Status’ field.
  21. Select any value in the 'Staff Assigning' field.
  22. Select any value in the 'Staff Responsible' field.
  23. Select the goal added in the previous steps.
  24. Set the ‘Goal’ field to any value.
  25. Select any value in the ‘Status’ field.
  26. Select any value in the 'Staff Assigning' field.
  27. Select any value in the 'Staff Responsible' field.
  28. Select the objective added in the previous steps.
  29. Set the ‘Objective’ field to any value.
  30. Select any value in the ‘Status’ field.
  31. Select any value in the 'Staff Assigning' field.
  32. Select any value in the 'Staff Responsible' field.
  33. Select the intervention added in the previous steps.
  34. Set the ‘Intervention’ field to any value.
  35. Select any value in the ‘Status’ field.
  36. Select any value in the 'Staff Assigning' field.
  37. Select any value in the 'Staff Responsible' field.
  38. Click [Back to Plan Page] and close the form.
  39. Select “Client A” and access the ‘Treatment Plan’ form.
  40. Validate the ‘Load From Backup’ dialog displays with a message stating: "You have an unsubmitted backup of a plan from [the current date] and [the current time]. Would you like to load it instead of creating a new one?" and click [Yes].
  41. Validate the 'Strengths' field contains the value previously filed.
  42. Validate the 'Weaknesses' field contains the value previously filed.
  43. Validate the 'Discharge Planning' field contains the value previously filed.
  44. Click [Launch Plan].
  45. Validate the ‘Tree view’ contains values for the problem, goal, objective, and intervention previously added with all updated data.
  46. Click [Exit to Home View].
Scenario 2: Treatment Plan - Add a Problem, Goal, Objective, and Intervention with the 'Enable Automatic Backup' registry setting set to "Y"
Specific Setup:
  • The 'Avatar CWS->Treatment Plan->->->->Enable Automatic Backup' registry setting must be set to "Y".
  • A client must be enrolled in an existing episode (Client A).
Steps
  1. Select “Client A” and access the ‘Treatment Plan’ form.
  2. Set the ‘Plan Date’ field to the current date.
  3. Set the ‘Plan Name’ to any value.
  4. Select any value in the ‘Plan Type’ field.
  5. Set the 'Strengths' field to any value.
  6. Set the 'Weaknesses' field to any value.
  7. Set the 'Discharge Planning' field to any value.
  8. Select “Draft” in the ‘Treatment Plan Status’ field and click [Launch Plan].
  9. Click [Add New Problem], [Add New Goal], [Add New Objective] and [Add New Intervention].
  10. Without populating the required fields, click [Return to Plan].
  11. Select "Final" in the 'Treatment Plan Status' field.
  12. Validate a 'Missing Required Fields' dialog is displayed.
  13. Click [OK].
  14. Validate "Draft" remains selected in the 'Treatment Plan Status' field.
  15. Click [Launch Plan].
  16. Select the problem added in the previous steps.
  17. Set the ‘Problem Code’ field to any value.
  18. Select “Active” in the ‘Status (Problem List)’ field.
  19. Set the ‘Problem’ field to any value.
  20. Select any value in the ‘Status’ field.
  21. Select any value in the 'Staff Assigning' field.
  22. Select any value in the 'Staff Responsible' field.
  23. Select the goal added in the previous steps.
  24. Set the ‘Goal’ field to any value.
  25. Select any value in the ‘Status’ field.
  26. Select any value in the 'Staff Assigning' field.
  27. Select any value in the 'Staff Responsible' field.
  28. Select the objective added in the previous steps.
  29. Set the ‘Objective’ field to any value.
  30. Select any value in the ‘Status’ field.
  31. Select any value in the 'Staff Assigning' field.
  32. Select any value in the 'Staff Responsible' field.
  33. Select the intervention added in the previous steps.
  34. Set the ‘Intervention’ field to any value.
  35. Select any value in the ‘Status’ field.
  36. Select any value in the 'Staff Assigning' field.
  37. Select any value in the 'Staff Responsible' field.
  38. Click [Back to Plan Page] and close the form.
  39. Select “Client A” and access the ‘Treatment Plan’ form.
  40. Validate the ‘Load From Backup’ dialog displays with a message stating: "You have an unsubmitted backup of a plan from [the current date] and [the current time]. Would you like to load it instead of creating a new one?" and click [Yes].
  41. Validate the 'Strengths' field contains the value previously filed.
  42. Validate the 'Weaknesses' field contains the value previously filed.
  43. Validate the 'Discharge Planning' field contains the value previously filed.
  44. Click [Launch Plan].
  45. Validate the ‘Tree view’ contains values for the problem, goal, objective, and intervention previously added with all updated data.
  46. Click [Exit to Home View].
Topics
• Treatment Plan
Update 50 Summary | Details
Progress Notes - 'Treatment Plan' grid
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Treatment Plan
  • Ambulatory Progress Notes
  • Problem List
Scenario 1: Progress Notes (Group and Individual) - Validate the 'Enable Treatment Plan Grid' registry setting
Specific Setup:
  • The 'Enable Treatment Plan Grid' registry setting must be set to "Y" for the 'Progress Notes (Group and Individual)' form.
  • A client must be enrolled in an existing episode and have a Treatment Plan filed with a problem, goal, objective, and intervention associated with the following special characters - <, >, ', " added to it (Client A).
  • The 'Progress Notes (Group and Individual)' form must be accessible from the Chart View.
Steps
  1. Access the 'Progress Notes (Group and Individual)' form.
  2. Enter "Client A" in the 'Select Client' field.
  3. Select the desired episode in the 'Select Episode' field.
  4. Select "Independent Note" in the 'Progress Note For' field.
  5. Select any value in the 'Note Type' field.
  6. Enter the desired value in the 'Notes Field' field.
  7. Populate any other required and desired fields.
  8. Click [New Row] in the 'Treatment Plan' grid.
  9. Select the desired Treatment Plan in the 'Select T.P. Version' field.
  10. Click [View] in the 'Select T.P. Item Note Addresses' field.
  11. Verify the 'Treatment Plan' window is displayed with "Client A's" treatment plan(s).
  12. Validate the treatment plan items are displayed with correct characters.
  13. Select the desired treatment plan item in the 'Treatment Plan' window.
  14. Click [Return].
  15. Validate the 'Note Addresses Which Treatment Plan Problem' field contains the Treatment Plan item selected in the previous step.
  16. Enter the desired value in the 'T.P. Item Notes/Documentations' field.
  17. Select "Final" in the 'Draft/Final' field.
  18. Submit the note.
  19. Access the 'Chart View' for "Client A".
  20. Select "Progress Notes (Group and Individual)" from the Forms list.
  21. Validate the progress note filed in the previous steps is displayed.
  22. Validate the treatment plan data filed displays as expected with the proper characters.
  23. Close the chart.
  24. Access Crystal Reports or other SQL Reporting tool
  25. Select the CWS namespace.
  26. Create a report using the 'SYSTEM.cw_patient_notes_tpnotes' SQL table.
  27. Validate a row is displayed for "Client A".
  28. Validate the 'note_add_which_tp_plan_prob' field contains the proper characters for the treatment plan items.
  29. Close the report.
Scenario 2: Ambulatory Progress Notes - Validate the 'Enable Treatment Plan Grid' registry setting
Specific Setup:
  • The 'Enable Treatment Plan Grid' registry setting must be set to "Y" for the 'Ambulatory Progress Notes' form.
  • A client must be enrolled in an outpatient episode and have a Treatment Plan filed with a problem, goal, objective, and intervention associated with the following special characters - <, >, ', " added to it (Client A).
  • The 'Ambulatory Progress Notes' form must be accessible from the Chart View.
Steps
  1. Select "Client A" and access the 'Ambulatory Progress Notes' form.
  2. Select the desired episode in the 'Select Episode' field.
  3. Select "Independent Note" in the 'Progress Note For' field.
  4. Select any value in the 'Note Type' field.
  5. Enter the desired value in the 'Notes Field'.
  6. Populate any other required and desired fields.
  7. Click [New Row] in the 'Treatment Plan' grid.
  8. Select the desired Treatment Plan in the 'Select T.P. Version' field.
  9. Click [View] in the 'Select T.P. Item Note Addresses' field.
  10. Verify the 'Treatment Plan' window is displayed with "Client A's" treatment plan(s).
  11. Validate the treatment plan items are displayed with correct characters.
  12. Select the desired treatment plan item in the 'Treatment Plan' window.
  13. Click [Return].
  14. Validate the 'Note Addresses Which Treatment Plan Problem' field contains the Treatment Plan item selected in the previous step.
  15. Enter the desired value in the 'T.P. Item Notes/Documentations' field.
  16. Select "Final" in the 'Draft/Final' field.
  17. Submit the form.
  18. Access the 'Chart View' for "Client A".
  19. Select "Ambulatory Progress Notes" from the Forms list.
  20. Validate the progress note filed in the previous steps is displayed.
  21. Validate the treatment plan data filed displays as expected with the proper characters.
  22. Close the chart.
  23. Access Crystal Reports or other SQL Reporting tool
  24. Select the CWS namespace.
  25. Create a report using the 'SYSTEM.cw_patient_notes_tpnotes' SQL table.
  26. Validate a row is displayed for "Client A".
  27. Validate the 'note_add_which_tp_plan_prob' field contains the proper characters for the treatment plan items.
  28. Close the report.
Scenario 3: Inpatient Progress Notes - Validate the 'Enable Treatment Plan Grid' registry setting
Specific Setup:
  • The 'Enable Treatment Plan Grid' registry setting must be set to "Y" for the 'Inpatient Progress Notes' form.
  • A client must be enrolled in an inpatient episode and have a Treatment Plan filed with a problem, goal, objective, and intervention associated with the following special characters - <, >, ', " added to it (Client A).
  • The 'Inpatient Progress Notes' form must be accessible from the Chart View.
Steps
  1. Select "Client A" and access the 'Inpatient Progress Notes' form.
  2. Select "Independent Note" in the 'Progress Note For' field.
  3. Select any value in the 'Note Type' field.
  4. Enter the desired value in the 'Notes Field'.
  5. Populate any other required and desired fields.
  6. Click [New Row] in the 'Treatment Plan' grid.
  7. Select the desired Treatment Plan in the 'Select T.P. Version' field.
  8. Click [View] in the 'Select T.P. Item Note Addresses' field.
  9. Verify the 'Treatment Plan' window is displayed with "Client A's" treatment plan(s).
  10. Validate the treatment plan items are displayed with correct characters.
  11. Select the desired treatment plan item in the 'Treatment Plan' window.
  12. Click [Return].
  13. Validate the 'Note Addresses Which Treatment Plan Problem' field contains the Treatment Plan item selected in the previous step.
  14. Enter the desired value in the 'T.P. Item Notes/Documentations' field.
  15. Select "Final" in the 'Draft/Final' field.
  16. Submit the form.
  17. Access the 'Chart View' for "Client A".
  18. Select "Inpatient Progress Notes" from the Forms list.
  19. Validate the progress note filed in the previous steps is displayed.
  20. Validate the treatment plan data filed displays as expected with the proper characters.
  21. Close the chart.
  22. Access Crystal Reports or other SQL Reporting tool
  23. Select the CWS namespace.
  24. Create a report using the 'SYSTEM.cw_patient_notes_tpnotes' SQL table.
  25. Validate a row is displayed for "Client A".
  26. Validate the 'note_add_which_tp_plan_prob' field contains the proper characters for the treatment plan items.
  27. Close the report.
Topics
• Treatment Plan • Progress Notes
Update 52 Summary | Details
'Treatment Plan' web service
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Treatment Plan
  • SOAPUI - Delete Treatment Plan
  • SoapUI - Get Treatment Plan
Scenario 1: Treatment Plan Web Service - Error validations
Specific Setup:
  • A required 'SS Treatment Plan Client Date' field is added to the 'Objectives' section of the 'Treatment Plan' form via 'Site Specific Section Modeling' (Field A).
  • A client is enrolled in an existing episode (Client A).
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. Populate all required and desired fields.
  10. Enter all required fields for a problem in the 'TreatmentPlanProblems' section.
  11. Add an associated objective for the problem entered above.
  12. Enter an objective description containing more than 50 characters.
  13. Enter "Field A" in the 'SSDate' - 'FieldNumber' field.
  14. Leave the 'SSDate' - 'FieldValue' field blank.
  15. Repeat steps 1i-1k for 6 more problems/objectives.
  16. Enter "Client A" in the 'ClientID' field.
  17. Enter "1" in the 'EpisodeNumber' field.
  18. Enter "CWS60000" in the 'OptionID' field.
  19. Click [Run].
  20. Validate the 'Message' field contains: Web service request failed with error : Missing Required Fields. Cannot finalize plan until the following required fields are complete.
  21. Enter a valid date in the 'SSDate' - 'FieldValue' fields for all objectives.
  22. Click [Run].
  23. Validate that the 'Confirmation' field contains the unique ID for the treatment plan filed.
  24. Validate the 'Message' field contains: "Treatment Plan web service has been filed successfully".
  25. Select "Client A" and access the 'Treatment Plan' form.
  26. Select the record filed in the previous steps and click [Edit].
  27. Validate all data filed in the previous steps is displayed.
  28. Close the form.
Topics
• Treatment Plan • Web Services
Update 54 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
  • SQL
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. 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. Create a report using the 'CWSTEMP.cw_tx_pn_sign_data' SQL table.
  19. Validate a row is displayed for the signature data entered for "Client A" in the previous steps.
  20. Navigate back to the 'Progress Notes (Group and Individual)' form.
  21. Click [Accept].
  22. Enter the password associated to the logged in user.
  23. Close the form.
  24. Access Crystal Reports or other SQL Reporting Tool.
  25. Refresh the report using the 'CWSTEMP.cw_patient_notes_tpnotes' SQL table.
  26. Validate a row is no longer displayed for the treatment plan data entered for "Client A" in the previous steps.
  27. Refresh the report using the 'CWSTEMP.cw_tx_pn_sign_data' SQL table.
  28. Validate a row is no longer displayed for the signature data entered for "Client A" in the previous steps.
  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.
  • A copy of the 'Ambulatory Progress Notes' form must be defined and 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. Create a report using the 'CWSTEMP.cw_tx_pn_sign_data' SQL table.
  19. Validate a row is displayed for the signature data entered for "Client A" in the previous steps.
  20. Navigate back to the 'Ambulatory Progress Notes' form.
  21. Click [Accept].
  22. Enter the password associated to the logged in user.
  23. Close the form.
  24. Access Crystal Reports or other SQL Reporting Tool.
  25. Refresh the report using the 'CWSTEMP.cw_patient_notes_tpnotes' SQL table.
  26. Validate a row is no longer displayed for the treatment plan data entered for "Client A" in the previous steps.
  27. Refresh the report using the 'CWSTEMP.cw_tx_pn_sign_data' SQL table.
  28. Validate a row is no longer displayed for the signature data entered for "Client A" in the previous steps.
  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 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.
  • A copy of the 'Inpatient Progress Notes' form must be defined and 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. Create a report using the 'CWSTEMP.cw_tx_pn_sign_data' SQL table.
  19. Validate a row is displayed for the signature data entered for "Client A" in the previous steps.
  20. Navigate back to the 'Inpatient Progress Notes' form.
  21. Click [Accept].
  22. Enter the password associated to the logged in user.
  23. Close the form.
  24. Access Crystal Reports or other SQL Reporting Tool.
  25. Refresh the report using the 'CWSTEMP.cw_patient_notes_tpnotes' SQL table.
  26. Validate a row is no longer displayed for the treatment plan data entered for "Client A" in the previous steps.
  27. Refresh the report using the 'CWSTEMP.cw_tx_pn_sign_data' SQL table.
  28. Validate a row is no longer displayed for the signature data entered for "Client A" in the previous steps.
  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.
Topics
• Document Routing • Progress Notes • Query/Reporting
2023 Update 68 Summary | Details
Avatar CWS - application mappings
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Application Namespace Connections Validation
Scenario 1: Avatar CWS - Validate the migration of global entries in the "^NTSTMAP" Global to the "^RADplusMap" Global
Steps
  1. Internal testing only
Scenario 2: Application Namespace Connection Validation
Specific Setup:
  1. Have a system with one or more child namespaces. For example: "PM" or "CWS" namespaces
  2. Have a system that the following modules installed in the system: "Avatar Data Warehouse", " Avatar CWS State Forms" or "Avatar ProviderConnect NX 2023 " and any other desired modules
Steps
  1. Open form "Applications Namespace Connection Validations"
  2. Validate "Currently Connected Namespaces" text box lists the expected child applications and namespace(s):
  3. Validate "Currently Connected Namespaces" text box indicates there are no application namespace connection or mapping errors.
  4. Click [Process]
  5. Validate the "Application Namespace Connections Validation" report list the expected connected child applications and namespace(s)
  6. Validate "Currently Connected Namespaces" text box indicates there are no application namespace connection or mappings errors.
Topics
• Forms
2023 Update 74 Summary | Details
'Client Health Maintenance' form
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Client Health Maintenance
Internal Test Only
Topics
n/a
2023 Update 77 Summary | Details
All Documents Widget - Unique form
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Treatment Plan
Scenario 1: Treatment Plan - creation of a treatment plan
Specific Setup:
  • A client must be enrolled in an existing episode (Client A).
Steps
  1. Access the 'Treatment Plan' form.
  2. Search for "Client A" in the 'Select Client' dialog.
  3. Select "Client A" from the 'Results' field.
  4. Click [Select].
  5. Enter the current date in the 'Plan Date' field.
  6. Select any value from the 'Plan Type' field.
  7. Select "Draft" from the 'Treatment Plan Status' field.
  8. Click [Launch Plan] and [Add New Problem].
  9. Enter any value in the 'Problem Code' field.
  10. Enter the current date in the 'Date of Onset' field.
  11. Select "Active" from the 'Status (Problem List)' field.
  12. Enter any value in the 'Problem' field.
  13. Click [Back to Plan Page].
  14. Validate the 'Problems' table contains the problem just added in the previous steps.
  15. Select "Final" from the 'Treatment Plan Status' field.
  16. Click [Submit].
Scenario 2: All Documents Widget - Client with multiple treatment plans and treatment plan copies on file
Specific Setup:
  • Using "Create New Treatment Plan" form:
  • Generate a new treatment plan form copy.
  • Using "Document Routing Setup" form:
  • Enable document routing for newly created treatment plan form.
  • All Documents Widget must be configured and added to a view.
Steps
  1. Open the "Treatment Plan" form.
  2. Generate and finalize two treatment plans.
  3. Open the "Treatment Plan" copy that was created.
  4. Generate and finalize two of treatment plan copies.
  5. Open the "Clinical Document Viewer".
  6. Display all treatment plans created for this test.
  7. Validate that you can open each one and that each page displays uniquely.
  8. Select the client in the "MyClients" widget.
  9. Navigate to the view that contains the "All Documents Widget".
  10. Display all treatment plans created for this test.
  11. Validate that you can open each one and that each page displays uniquely.
Topics
• Treatment Plan • Create New Treatment Plan
2023 Update 89 Summary | Details
Data Trail - AUDIT.cw_problem_list
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Data Trail Configuration
  • Problem List
  • Treatment Plan
Scenario 1: Data Trail - Problem List
Specific Setup:
  • Using the "Data Trail Configuration" form, select the SYSTEM_cw_problem_list under "Problem List"
Steps
  1. Open the "Problem List" form.
  2. Add a new problem.
  3. Click "Submit" to file data.
  4. Using the preferred method to view SQL tables, validate a row was added to the "AUDIT.cw_problem_list table and that it has an "audit_action_code" of "A" for Add.
  5. Open the "Problem List" form.
  6. Edit an existing problem.
  7. Click "Submit" to file data.
  8. Using the preferred method to view SQL tables, validate a row was added to the "AUDIT.cw_problem_list table and that it has an "audit_action_code" of "E" for Edit.
  9. Open the "Problem List" form.
  10. Mark a problem as Inactive.
  11. Click "Submit" to file data.
  12. Using the preferred method to view SQL tables, validate a row was added to the "AUDIT.cw_problem_list table and that it has an "audit_action_code" of "I" for Inactive.
Scenario 2: DataTrail -Treatment Plan Problems
Specific Setup:
  • Open the "Data Trail Configuration" form.
  • Select "SYSTEM.cw_problem_list" under Treatment Plan.
Steps
  1. Open the "Treatment Plan" form.
  2. Add a problem to the "Problem List".
  3. Complete and t finalize treatment plan.
  4. Using the preferred method to validate SQL tables, validate that a row was added to the AUDIT.cw_problem_list with a value of "A" in the audit_action_code.
  5. Open the "Treatment Plan" form.
  6. Modify an existing problem in the "Problem List".
  7. Complete and t finalize treatment plan.
  8. Using the preferred method to validate SQL tables, validate that a row was added to the AUDIT.cw_problem_list with a value of "E" in the audit_action_code.
Scenario 3: Data Trail - Treatment Plan Copies - Problems
Specific Setup:
  • Open the "Data Trail Configuration" form.
  • Select "SYSTEM.cw_problem_list" under Treatment Plan.
  • Using the "Create New Treatment Plan"
  • Create a copy of the treatment plan form.
  • Using "User Definition"
  • Add the new treatment plan form to the user's "Forms and Tables to Access".
Steps
  1. Open the Treatment Plan copy form.
  2. Add a problem to the "Problem List".
  3. Complete and finalize treatment plan.
  4. Using the preferred method to validate SQL tables, validate that a row was added to the AUDIT.cw_problem_list with a value of "A" in the audit_action_code.
  5. Open the Treatment Plan copy form.
  6. Modify an existing problem in the "Problem List".
  7. Complete and finalize treatment plan.
  8. Using the preferred method to validate SQL tables, validate that a row was added to the AUDIT.cw_problem_list with a value of "E" in the audit_action_code.
Data Trail - AUDIT.noniscrxstorage
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Home Medications
Scenario 1: Validate Data Trail tables AUDIT.rxstorage, AUDIT_rxdosagestorage
Specific Setup:
  • Add the "Order Console Widget" to the user's home view.
Steps
  1. Navigate to the "Order Console Widget".
  2. Add a medication to the Home Medications tab.
  3. Using the preferred method to validate SQL tables, validate a row is added to the AUDIT.rxdosagestorage with an "A" in the audit_action_code.
  4. Return to the "Orders Console Widget".
  5. Modify the medication entered on the Home Medications tab.
  6. Using the preferred method to validate SQL tables, validate a row is added to the AUDIT.rxdosagestorage with an "E" in the audit_action_code.
  7. Return to the "Orders Console Widget".
  8. Discontinue the medication entered on the Home Medications tab.
  9. Using the preferred method to validate SQL tables, validate a row is added to the AUDIT.rxdosagestorage with an "E" in the audit_action_code.
  10. Using the preferred method to validate SQL tables, validate a row is added to the AUDIT.rxdosagestorage with an "R" in the audit_action_code.
Scenario 2: Validate DataTrail audit tables AUDIT.noniscrxstorage
Specific Setup:
  • Add the "Order Console Widget" to the user's home view.
Steps
  1. Navigate to the "Order Console Widget".
  2. Add a reported medication to the Home Medications tab.
  3. Using the preferred method to validate SQL tables, validate a row is added to the AUDIT.rxdosagestorage with an "A" in the audit_action_code.
  4. Return to the "Orders Console Widget".
  5. Modify the reported medication entered on the Home Medications tab.
  6. Using the preferred method to validate SQL tables, validate a row is added to the AUDIT.rxdosagestorage with an "E" in the audit_action_code.
Data Trail - AUDIT.cw_hist_client_allergies
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Data Trail Configuration
Scenario 1: Data Trail - Allergies and Hypersensitivities
Specific Setup:
  • Open the "Data Trail Configuration" form.
  • Select the SYSTEM.cw_hist_client_allergies table.
Steps
  1. Open the "Allergies and Hypersensitivities" form.
  2. Add an allergy to the client.
  3. Save the data and file the form.
  4. Using the preferred method of validating SQL table, validate a row has been added to the AUDIT.cw_hist_client_allergies table and the row has an "A" in the audit_action_code.
  5. Open the "Allergies and Hypersensitivities" form.
  6. Edit an allergy for the client.
  7. Save the data and file the form.
  8. Using the preferred method of validating SQL table, validate a row has been added to the AUDIT.cw_hist_client_allergies table and the row has an "E" in the audit_action_code.
Data Trail - AUDIT_cw_implantable_device
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Data Trail Configuration
  • Implantable Device List
Scenario 1: Data Trail- Implantable Devices
Specific Setup:
  • Open the "Data Trail Configuration" form.
  • Select the System.cw_implantable_device table.
Steps
  1. Open the "Implantable Device List" form.
  2. Assign an implantable device to a client.
  3. Using the preferred method to view SQL tables, validate a row is added to the AUDIT.cw_implantable_device table with an "A" in the audit_action_code.
  4. Open the "Implantable Device List" form.
  5. Change the "Status" to "Completed".
  6. Using the preferred method to view SQL tables, validate a row is added to the AUDIT.cw_implantable_device table with an "E" in the audit_action_code.
  7. Open the "Implantable Device List" form.
  8. Change the "Status" to "Aborted".
  9. Using the preferred method to view SQL tables, validate a row is added to the AUDIT.cw_implantable_device table with an "D" in the audit_action_code.
Data Trail - AUDIT.rxdosagestorage and AUDIT.rxstorage
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Home Medications
Scenario 1: Validate Data Trail tables AUDIT.rxstorage, AUDIT_rxdosagestorage
Specific Setup:
  • Add the "Order Console Widget" to the user's home view.
Steps
  1. Navigate to the "Order Console Widget".
  2. Add a medication to the Home Medications tab.
  3. Using the preferred method to validate SQL tables, validate a row is added to the AUDIT.rxdosagestorage with an "A" in the audit_action_code.
  4. Return to the "Orders Console Widget".
  5. Modify the medication entered on the Home Medications tab.
  6. Using the preferred method to validate SQL tables, validate a row is added to the AUDIT.rxdosagestorage with an "E" in the audit_action_code.
  7. Return to the "Orders Console Widget".
  8. Discontinue the medication entered on the Home Medications tab.
  9. Using the preferred method to validate SQL tables, validate a row is added to the AUDIT.rxdosagestorage with an "E" in the audit_action_code.
  10. Using the preferred method to validate SQL tables, validate a row is added to the AUDIT.rxdosagestorage with an "R" in the audit_action_code.
Data Trail Configuration - Added tables
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Data Trail Configuration
  • Problem List
  • Treatment Plan
  • Implantable Device List
Scenario 1: Data Trail - Problem List
Specific Setup:
  • Using the "Data Trail Configuration" form, select the SYSTEM_cw_problem_list under "Problem List"
Steps
  1. Open the "Problem List" form.
  2. Add a new problem.
  3. Click "Submit" to file data.
  4. Using the preferred method to view SQL tables, validate a row was added to the "AUDIT.cw_problem_list table and that it has an "audit_action_code" of "A" for Add.
  5. Open the "Problem List" form.
  6. Edit an existing problem.
  7. Click "Submit" to file data.
  8. Using the preferred method to view SQL tables, validate a row was added to the "AUDIT.cw_problem_list table and that it has an "audit_action_code" of "E" for Edit.
  9. Open the "Problem List" form.
  10. Mark a problem as Inactive.
  11. Click "Submit" to file data.
  12. Using the preferred method to view SQL tables, validate a row was added to the "AUDIT.cw_problem_list table and that it has an "audit_action_code" of "I" for Inactive.
Scenario 2: DataTrail -Treatment Plan Problems
Specific Setup:
  • Open the "Data Trail Configuration" form.
  • Select "SYSTEM.cw_problem_list" under Treatment Plan.
Steps
  1. Open the "Treatment Plan" form.
  2. Add a problem to the "Problem List".
  3. Complete and t finalize treatment plan.
  4. Using the preferred method to validate SQL tables, validate that a row was added to the AUDIT.cw_problem_list with a value of "A" in the audit_action_code.
  5. Open the "Treatment Plan" form.
  6. Modify an existing problem in the "Problem List".
  7. Complete and t finalize treatment plan.
  8. Using the preferred method to validate SQL tables, validate that a row was added to the AUDIT.cw_problem_list with a value of "E" in the audit_action_code.
Scenario 3: Data Trail - Allergies and Hypersensitivities
Specific Setup:
  • Open the "Data Trail Configuration" form.
  • Select the SYSTEM.cw_hist_client_allergies table.
Steps
  1. Open the "Allergies and Hypersensitivities" form.
  2. Add an allergy to the client.
  3. Save the data and file the form.
  4. Using the preferred method of validating SQL table, validate a row has been added to the AUDIT.cw_hist_client_allergies table and the row has an "A" in the audit_action_code.
  5. Open the "Allergies and Hypersensitivities" form.
  6. Edit an allergy for the client.
  7. Save the data and file the form.
  8. Using the preferred method of validating SQL table, validate a row has been added to the AUDIT.cw_hist_client_allergies table and the row has an "E" in the audit_action_code.
Scenario 4: Data Trail- Implantable Devices
Specific Setup:
  • Open the "Data Trail Configuration" form.
  • Select the System.cw_implantable_device table.
Steps
  1. Open the "Implantable Device List" form.
  2. Assign an implantable device to a client.
  3. Using the preferred method to view SQL tables, validate a row is added to the AUDIT.cw_implantable_device table with an "A" in the audit_action_code.
  4. Open the "Implantable Device List" form.
  5. Change the "Status" to "Completed".
  6. Using the preferred method to view SQL tables, validate a row is added to the AUDIT.cw_implantable_device table with an "E" in the audit_action_code.
  7. Open the "Implantable Device List" form.
  8. Change the "Status" to "Aborted".
  9. Using the preferred method to view SQL tables, validate a row is added to the AUDIT.cw_implantable_device table with an "D" in the audit_action_code.
Scenario 5: Data Trail - Treatment Plan Copies - Problems
Specific Setup:
  • Open the "Data Trail Configuration" form.
  • Select "SYSTEM.cw_problem_list" under Treatment Plan.
  • Using the "Create New Treatment Plan"
  • Create a copy of the treatment plan form.
  • Using "User Definition"
  • Add the new treatment plan form to the user's "Forms and Tables to Access".
Steps
  1. Open the Treatment Plan copy form.
  2. Add a problem to the "Problem List".
  3. Complete and finalize treatment plan.
  4. Using the preferred method to validate SQL tables, validate that a row was added to the AUDIT.cw_problem_list with a value of "A" in the audit_action_code.
  5. Open the Treatment Plan copy form.
  6. Modify an existing problem in the "Problem List".
  7. Complete and finalize treatment plan.
  8. Using the preferred method to validate SQL tables, validate that a row was added to the AUDIT.cw_problem_list with a value of "E" in the audit_action_code.
Topics
• Problem List • NX • Treatment Plan • Widgets • Order Entry Console • Allergies and Hypersensitivities • Implantable Device List
2023 Update 91 Summary | Details
Task List - Follow-Up Reminders
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Orders This Episode
  • eMAR
Scenario 1: eMAR NX - Administration Event - Follow-Up Reminder
Steps

Internal Testing Only
Topics
• NX • eMAR NX
2023 Update 93 Summary | Details
Clinical Document Viewer - Service Date
Scenario 1: Clinical Document Viewer - Validating Service Date
Specific Setup:
  • Set the registry setting "Post Appointment When The Note Is Submitted" to "N".
  • Using the "Document Routing Setup" form:
  • Enable Document Routing for any progress notes form.
Steps
  1. Open the "Scheduling Calendar" form.
  2. Create an appointment.
  3. Open the progress note form setup that was enabled for document routing.
  4. Create and finalize a progress note for the appointment.
  5. Open the "Clinical Document Viewer" form.
  6. Locate the row that contains the progress note that was finalized.
  7. Validate the "Service Date" columns is populated with the date of the progress note.
Scenario 2: Progress Notes (Group and Individual) - Validate document routing
Specific Setup:
  • Document routing must be enabled for the "Progress Notes (Group and Individual)" form.
Steps
  1. Open the "Progress Notes (Group and Individual)" form.
  2. Create and finalize a document.
  3. Sign the document.
  4. Using "Clinical Document Viewer", view and print the document.
  5. Validate the document displays and prints.
  6. Open the "Progress Notes (Group and Individual)" form.
  7. Create and route a progress note to an approver.
  8. Sign on as the approver.
  9. Locate the document in the approver's "My To Do's" widget.
  10. Click on "Approve Document" and approve the document.
  11. Using the "Clinical Document Viewer", view the document that was just approved.
  12. Open the "Progress Notes (Group and Individual)" form.
  13. Create and route a note to multiple approvers.
  14. Sign on as the first approver.
  15. Locate the document in the approver's "My To Do's" widget.
  16. Click on "Approve Document".
  17. Click "Accept".
  18. Enter the approver's password.
  19. Log on as another approver.
  20. Locate the document in the approver's "My To Do's" widget.
  21. Click on "Approve Document".
  22. Click "Accept".
  23. Enter the approver's password.
  24. Open the "Clinical Document Viewer" form.
  25. Select the document that was just routed/finalized.
  26. Validate that the document displays and prints.
  27. Open the "Progress Notes (Group and Individual)" form.
  28. Create a progress note and route to several approvers.
  29. Log on as another approver.
  30. Locate the document in the approver's "My To Do's" widget.
  31. Click on "Approve Document".
  32. Click "Accept".
  33. Enter the approver's password.
  34. Repeat steps 11b-12c for each additional approver.
  35. Open "Clinical Document Viewer".
  36. Validate the document that was just filed display and prints.
Topics
• Clinical Document Viewer
2023 Update 95 Summary | Details
Manage Observer Caseload - 'Observer.caseload_audit' SQL table
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • ProgressNote Approval
Scenario 1: Manage Observer Caseload - Clear Caseload - Validate the 'Allow Clear All Caseloads' registry setting
Specific Setup:
  • A client is enrolled in an existing inpatient episode (Client A).
  • "Client A" is not part of the logged in user's caseload (User A).
Steps
  1. Access the 'Registry Settings' form.
  2. Enter "Allow Clear All Caseloads" in the 'Limit Registry Settings to the Following Search Criteria' field.
  3. Click [View Registry Settings].
  4. Validate the default 'Registry Setting Value' is "Y".
  5. Validate the 'Registry Setting Details' field contains: Enter 'Y' to allow 'Clear All Caseloads' in the 'Manage Observer Caseload' form. Enter 'N' to disallow 'Clear All Caseloads' in the 'Manage Observer Caseload' form.
  6. Click [Submit] and close the form.
  7. Access the 'Manage Observer Caseload' form.
  8. Search for and select "User A" in the 'Select User' field.
  9. Select "Add" in the 'Add or Remove Client From Caseload' field.
  10. Select the unit that "Client A" is admitted into in the 'Unit' field.
  11. Select "Client A" in the 'Select Clients' field.
  12. Click [Update Caseload].
  13. Validate the 'Current Caseload' field contains "Client A".
  14. Select the "Clear All Caseloads" section.
  15. Click [Clear All Caseloads].
  16. Validate a message is displayed stating: You are about to clear observation caseloads for all users. Do you want to continue?
  17. Click [OK].
  18. Validate a message is displayed stating: This action cannot be undone. Please be aware that by continuing, the caseloads will be cleared for all users. Do you want to continue?
  19. Click [OK].
  20. Validate a message is displayed stating: NTST Observer caseloads are cleared for all users.
  21. Click [OK].
  22. Select the "Manage Caseload" section.
  23. Search for and select "User A" in the 'Select User' field.
  24. Validate the 'Current Caseload' field no longer contains "Client A".
  25. Close the form.
  26. Access the 'Registry Settings' form.
  27. Enter "Allow Clear All Caseloads" in the 'Limit Registry Settings to the Following Search Criteria' field.
  28. Click [View Registry Settings].
  29. Enter "N" in the 'Registry Setting Value' field.
  30. Click [Submit] and close the form.
  31. Access the 'Manage Observer Caseload' form.
  32. Search for and select "User A" in the 'Select User' field.
  33. Select "Add" in the 'Add or Remove Client From Caseload' field.
  34. Select the unit that "Client A" is admitted into in the 'Unit' field.
  35. Select "Client A" in the 'Select Clients' field.
  36. Click [Update Caseload].
  37. Validate the 'Current Caseload' field contains "Client A".
  38. Select the "Clear All Caseloads" section.
  39. Click [Clear All Caseloads].
  40. Validate a message is displayed stating: 'Clear All Caseloads' is not allowed.
  41. Click [OK].
  42. Select the "Manage Caseload" section.
  43. Validate "Client A" is still displayed in the 'Current Caseload' field.
  44. Close the form.
Scenario 2: Manage Observer Caseload - Transfer Caseload - Validate Caseload Report
Specific Setup:
  • Two users are defined with associated practitioners that have credentials on file (User A & User B).
  • A client is enrolled in an existing inpatient episode (Client A).
  • "Client A" is not in the observer caseload of "User A" or "User B".
Steps
  1. Access the 'Manage Observer Caseload' form.
  2. Select "User A" in the 'Select User' field.
  3. Select "Add" in the 'Add or Remove Client From Caseload' field.
  4. Select the unit "Client A" is admitted into in the 'Unit' field.
  5. Select "Client A" in the 'Select Clients' field.
  6. Click [Update Caseload].
  7. Validate the 'Current Caseload' field contains "Client A".
  8. Select the "Transfer Caseload" section.
  9. Select "User A" in the 'Transfer Caseload From' field.
  10. Validate the 'Credentials (From Staff)' field is read-only and contains the practitioner credentials for "User A".
  11. Select "User B" in the 'Transfer Caseload To' field.
  12. Validate the 'Credentials (To Staff)' field is read-only and contains the practitioner credentials for "User B".
  13. Select "Client A" in the 'Select Clients' field.
  14. Validate the 'Caseload Assigned By' field contains the logged in user. This can be updated, if desired.
  15. Select the desired value in the 'Transfer Caseload Reason' field. Note: this is a user defined dictionary - user can right click to add dictionary values.
  16. Click [Transfer Caseload].
  17. Validate a message is displayed stating: Selected client(s) will be transferred from the caseload of "User A" to "User B". Are you sure?
  18. Click [OK] and [Run Caseload Report].
  19. Validate the report is displayed and contains the following:
  20. For "User B" there will be a record for "Client A" with the following details:
  21. Action - Added
  22. Assigned Date - Transfer date
  23. Assigned Time - Transfer time
  24. Caseload Assigned By - User selected in the 'Caseload Assigned By' field
  25. Reason - Value selected in the 'Transfer Caseload Reason' field
  26. For "User A" there will be a record for "Client A" with the following details:
  27. Action - Removed
  28. Assigned Date - Transfer date
  29. Assigned Time - Transfer time
  30. Caseload Assigned By - User selected in the 'Caseload Assigned By' field
  31. Reason - Value selected in the 'Transfer Caseload Reason' field'
  32. Close the report and the form.
  33. Access Crystal Reports or other SQL Reporting tool.
  34. Select the CWS namespace.
  35. Create a report using the 'Observer.caseload_audit' SQL table.
  36. Validate there are two rows for the caseload transfer from "User A" to "User B".
  37. Validate the 'assigned_by_user_id' and 'assigned_by_user_name' fields contain the 'Caseload Assigned By' user if populated, if not, the logged in user.
  38. Close the report.
Scenario 3: Manage Observer Caseload - Manage Caseload - Validate Caseload Report
Specific Setup:
  • A user is defined with an associated practitioner that has credentials on file (User A).
  • A client is enrolled in an existing inpatient episode (Client A).
  • "Client A" is not in "User A's" observer caseload.
Steps
  1. Access the 'Manage Observer Caseload' form.
  2. Select "User A" in the 'Select User' field.
  3. Validate the 'Credentials' field is read-only and contains the practitioner credentials for "User A".
  4. Validate the 'Caseload Assigned By' field contains the logged in user. This can be updated, if desired.
  5. Select "Add" in the 'Add or Remove Client From Caseload' field.
  6. Validate the 'Reason to Remove Caseload' field is disabled. This field will only be enabled when "Remove" is selected in the 'Add or Remove Client From Caseload' field.
  7. Select the unit "Client A" is admitted into in the 'Unit' field.
  8. Click [Update Caseload].
  9. Validate the 'Current Caseload' field contains "Client A".
  10. Click [Run Caseload Report].
  11. Validate the report is displayed and contains the following:
  12. For "User A" there will be a record for "Client A" with the following details:
  13. Action - Added
  14. Assigned Date - Added date
  15. Assigned Time - Added time
  16. Caseload Assigned By - User selected in the 'Caseload Assigned By' field
  17. Close the report.
  18. Access Crystal Reports or other SQL Reporting tool.
  19. Select the CWS namespace.
  20. Create a report using the 'Observer.caseload_audit' SQL table.
  21. Validate there is a row for "Client A" being added to "User A" caseload.
  22. Validate the 'assigned_by_user_id' and 'assigned_by_user_name' fields contain the 'Caseload Assigned By' user if populated, if not, the logged in user.
  23. Validate the 'assigned_date' contains the date "Client A" was added.
  24. Validate the 'assigned_time' field contains the time "Client A" was added.
  25. Validate the 'assigned_to_user_id' and 'assigned_to_user_name' fields contain "User A".
  26. Validate the 'PATID' field contains "Client A".
  27. Validate the 'action_code' field contains "A".
  28. Validate the 'action_value' field contains "Added".
  29. Validate the 'client_name' field contains "Client A".
  30. Validate the 'credentials_code', 'credentials_shval', and 'credentials_value' fields contains the credential codes/values for "User A".
  31. Navigate back to the 'Manage Observer Caseload' form.
  32. Validate the 'Select User' field contains "User A".
  33. Validate the 'Caseload Assigned By' field contains the logged in user.
  34. Select "Remove" in the 'Add or Remove Client From Caseload' field.
  35. Validate the 'Reason to Remove Caseload' field is now enabled.
  36. Select the desired value in the 'Reason to Remove Caseload' field. Note: this is a user defined dictionary - user can right click to add dictionary values.
  37. Select "Client A" in the 'Select Clients' field.
  38. Click [Update Caseload].
  39. Validate a message is displayed stating: You are about to remove the selected client(s) from the caseload of "User A". Are you sure you want to continue?
  40. Click [OK].
  41. Validate the 'Current Caseload' field does not contain "Client A".
  42. Click [Run Caseload Report].
  43. Validate the report is displayed and contains the following:
  44. For "User A" there will be a record for "Client A" with the following details:
  45. Action - Removed
  46. Assigned Date - Removed date
  47. Assigned Time - Removed time
  48. Caseload Assigned By - User selected in the 'Caseload Assigned By' field
  49. Reason - Value selected in the 'Reason to Remove Caseload' field
  50. Close the report and the form.
  51. Access Crystal Reports or other SQL Reporting tool.
  52. Refresh the report using the 'Observer.caseload_audit' SQL table.
  53. Validate there is a row for "Client A" being removed from "User A" caseload.
  54. Validate the 'assigned_by_user_id' and 'assigned_by_user_name' fields contain the 'Caseload Assigned By' user if populated, if not, the logged in user.
  55. Validate the 'assigned_date' contains the date "Client A" was removed.
  56. Validate the 'assigned_time' field contains the time "Client A" was removed.
  57. Validate the 'assigned_to_user_id' and 'assigned_to_user_name' fields contain "User A".
  58. Validate the 'PATID' field contains "Client A".
  59. Validate the 'action_code' field contains "R".
  60. Validate the 'action_value' field contains "Removed".
  61. Validate the 'client_name' field contains "Client A".
  62. Validate the 'credentials_code', 'credentials_shval', and 'credentials_value' fields contains the credential codes/values for "User A".
  63. Validate the 'removal_code' and 'removal_value' field contains the corresponding code/value for the value selected in the 'Reason to Remove Caseload' field.
  64. Close the report.
Topics
• Registry Settings • Manage Observer Caseload
2023 Update 96 Summary | Details
Avatar CWS - Support for other products and modules
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Query for External CCD
  • Import Clinical Information
  • Ambulatory Progress Notes
  • Treatment Plan
  • Patient Health Questionnaire-9
  • CareConnect Inbox
  • Care Connect Inbox
  • CareConnect CCD Download
  • Problem List
Scenario 1: Query for External CCD - Search, Preview, Save CCD's and validate SDK actions are triggered
Specific Setup:
  • A client must be enrolled in an existing episode (Client A).
Steps
  1. Access the 'Query for External CCD' form.
  2. Select "Client A" in the 'Client Search' field.
  3. Select an organization in the 'Organization Name or Zip' field.
  4. Click [Search CCDs].
  5. Validate message stating: "Match(es) found, # document(s) returned."
  6. Click [OK].
  7. Select a CCD in the 'Available CCDs' field.
  8. Enter the desired provider in the 'Provider Referred To' field.
  9. Click [Preview].
  10. Validate the CCD is displayed in a preview with CCD section details and close it.
  11. Click [Save].
  12. Validate an "Information" message is displayed stating: Saved.
  13. Click [OK] and close the form.
  14. Access the 'CareFabric Monitor' form.
  15. Enter the current date in the 'From Date' and 'Through Date' fields.
  16. Enter "Client A" in the 'Client ID' field.
  17. Enter "ExternalDataAckowledgementCreated" in the 'Event/Action Search' field.
  18. Click [View Activity Log].
  19. Validate that the 'CareFabric Monitor Report' contains an 'ExternalDataAcknowledgementCreated' record.
  20. Click [Click To View Record].
  21. Validate the 'referredToProviderID' - 'id' field contains the provider ID selected in the previous steps.
  22. Close the report and the form.
  23. Access Crystal Reports or other SQL Reporting Tool.
  24. Create a report using the 'SYSTEM.ccd_tempstorage' table.
  25. Validate a row is displayed for the CCD saved in the previous steps.
  26. Validate the 'PATID' field contains "Client A".
  27. Validate that the 'provider_referred_to' field contains the provider ID selected in the previous steps.
  28. Validate that the 'provider_referred_to_name' field contains the provider name selected in the previous steps.
  29. Close the report.
Scenario 2: 'External Documents' widget - Validate the 'Care Team' button
Specific Setup:
  • The 'External Document' widget and 'Console Widget Viewer' are on the HomeView.
  • A client has available CCD's (Client A).
Steps
  1. Select "Client A" and access the 'External Documents' widget.
  2. Click [Search].
  3. Validate a message is displayed stating: Match(es) found, # document(s) returned.
  4. Click [OK].
  5. Click [View] for any of the CCDs.
  6. Validate the CCD is displayed in the 'Console Widget Viewer'. Take note of the Care Team details.
  7. Click [Close All].
  8. Validate the CCD is no longer displayed.
  9. Click [Care Team] for the same CCD.
  10. Validate the Care Team details are displayed in the 'Console Widget Viewer' based on the Care Team section of the CCD.
  11. Click [Close All].
  12. Validate the Care Team details are no longer displayed.
Scenario 3: 'CareConnect CCD Download' - Search, Preview and Download CCDs
Specific Setup:
  • A client must have available CCDs (Client A).
Steps
  1. Access the 'CareConnect CCD Download' form.
  2. Enter "Client A" in the 'Client Search' field.
  3. Validate message stating: "Match(es) found, # document(s) returned."
  4. Click [OK].
  5. Select any value in the 'Available CCD(s)' field.
  6. Click [Preview].
  7. Validate a 'Document Preview' of "Client A's" CCD is displayed.
  8. Click [Close All Documents and Exit].
  9. Enter the desired provider in the 'Provider Referred To' field.
  10. Select "Yes" in the 'Save for Reconciliation' field.
  11. Click [Download].
  12. Validate an "Information" message is displayed stating: Saved.
  13. Click [OK].
  14. Access the 'CareFabric Monitor' form.
  15. Enter the current date in the 'From Date' and 'Through Date' fields.
  16. Enter "Client A" in the 'Client ID' field.
  17. Enter "ExternalDataAckowledgementCreated" in the 'Event/Action Search' field.
  18. Click [View Activity Log].
  19. Validate that the 'CareFabric Monitor Report' contains an 'ExternalDataAcknowledgementCreated' record.
  20. Click [Click To View Record].
  21. Validate the 'referredToProviderID' - 'id' field contains the provider ID selected in the previous steps.
  22. Close the report and the form.
  23. Access Crystal Reports or other SQL Reporting Tool.
  24. Create a report using the 'SYSTEM.ccd_tempstorage' table.
  25. Validate a row is displayed for the CCD saved in the previous steps.
  26. Validate the 'PATID' field contains "Client A".
  27. Validate that the 'provider_referred_to' field contains the provider ID selected in the previous steps.
  28. Validate that the 'provider_referred_to_name' field contains the provider name selected in the previous steps.
  29. Close the report.
Topics
• CCD's • Query for External CCD • External Document Widget
2023 Update 98 Summary | Details
OE NX - 'Task Shift' form
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Task Shift
Scenario 1: OE NX - 'Task Shift' form shift time calculation
Steps
  1. Access the 'Task Shift' form.
  2. Select "Add" in the 'Add/Edit Shift Definition' field.
  3. Set the 'New Shift Code' field to any value.
  4. Set the 'Shift Description' field to any value.
  5. Set the 'Shift 1 Start Time' field to any value where minutes are not equal to 00. (ex. 0730)
  6. Set the 'Shift 2 Start Time' field to any value where minutes are not equal to 00. (ex. 1530)
  7. Set the 'Shift 3 Start Time' field to any value where minutes are not equal to 00. (ex. 2330)
  8. Validate the 'Shift 1 End Time' field contains a time that is one minute prior than the value in the 'Shift 2 Start Time' field.
  9. Validate the 'Shift 2 End Time' field contains a time that is one minute prior than the value in the 'Shift 3 Start Time' field.
  10. Validate the 'Shift 3 End Time' field contains a time that is one minute prior than the value in the 'Shift 1 Start Time' field.
  11. Click [Submit].
  12. Validate a message is displayed stating: "Task Shift has completed. Do you wish to return to form?" and click [No].
Topics
• Task Shift
2023 Update 99 Summary | Details
Progress Notes - Support for Patient Calendar functionality
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Ambulatory Progress Notes (Diagnosis Entry)
  • Inpatient Progress Notes (Diagnosis Entry)
  • Ambulatory Progress Notes
Scenario 1: Progress Notes (Group and Individual) - File a note for a client only service
Specific Setup:
  • A client must be enrolled in an existing episode (Client A).
  • A "Client Only" service code must be defined in the 'Service Codes' form (Service Code A).
  • The 'Progress Notes' widget must be on the HomeView.
Steps
  1. Access the 'Progress Notes (Group and Individual)' form.
  2. Select "Client A" in the 'Select Client' field.
  3. Select any value in the 'Select Episode' field.
  4. Select "New Service" in the 'Progress Notes For' field.
  5. Select any value in the 'Note Type' field.
  6. Enter any value in the 'Notes Field'.
  7. Enter the current date in the 'Date of Service' field.
  8. Select "Service Code A" in the 'Service Charge Code' field.
  9. Populate any other required and desired fields.
  10. Select "Final" from the 'Draft/Final' field.
  11. Click [File Note].
  12. Validate a "Progress Notes" dialog is displayed stating: Note Filed. Do you want to return to the Progress Notes form?
  13. Click [No].
  14. Select "Client A" and navigate to the 'Progress Notes' widget.
  15. Validate the note filed in the previous steps is displayed.
  16. Access the 'Client Ledger' form.
  17. Search "Client A" in the 'Client ID' field.
  18. Select "All Episodes" from the 'Claim/Episode/All Episodes' field.
  19. Select "Simple" in the 'Ledger Type' field.
  20. Select "Yes" in the 'Include Zero Charges' field.
  21. Click [Process].
  22. Validate "Service Code A" is displayed in the Client Ledger.
  23. Close the form.
Scenario 2: Ambulatory Progress Notes - File a note for a client only service
Specific Setup:
  • The 'Allow Client Only Services in the Scheduling Calendar' registry setting must be set to "Y". Please note: this is only supported in Avatar NX.
  • A client must be enrolled in an existing outpatient episode (Client A).
  • A "Client Only" service code must be defined in the 'Service Codes' form (Service Code A).
  • The 'Progress Notes' widget must be on the HomeView.
  • "Client A" must have a client only appointment scheduled in the 'Scheduling Calendar' using "Service Code A". Please note: this is only supported in Avatar NX.
Steps
  1. Select "Client A" and access the 'Ambulatory Progress Notes' form.
  2. Select "Existing Appointment" in the 'Progress Note For' field.
  3. Select the existing appointment for "Service Code A" in the 'Note Addresses Which Existing Service/Appointment' field.
  4. Select the desired value in the 'Note Type' field.
  5. Enter the desired value in the 'Notes Field'.
  6. Populate any other required and desired fields.
  7. Select "Final" in the 'Draft/Final' field.
  8. Submit the note.
  9. Select "Client A" and navigate to the 'Progress Notes' widget.
  10. Validate the note filed in the previous steps is displayed.
  11. Access the 'Client Ledger' form.
  12. Search "Client A" in the 'Client ID' field.
  13. Select "All Episodes" from the 'Claim/Episode/All Episodes' field.
  14. Select "Simple" in the 'Ledger Type' field.
  15. Select "Yes" in the 'Include Zero Charges' field.
  16. Click [Process].
  17. Validate "Service Code A" is displayed in the Client Ledger.
  18. Close the form.
Scenario 3: Inpatient Progress Notes - File a note for a client only service
Specific Setup:
  • A client must be enrolled in an existing inpatient episode (Client A).
  • A "Client Only" service code must be defined in the 'Service Codes' form (Service Code A).
  • "Client A" has an existing service for "Service Code A" filed in 'Client Charge Input'.
  • The 'Progress Notes' widget must be on the HomeView.
Steps
  1. Select "Client A" and access the 'Inpatient Progress Notes' form.
  2. Select "Existing Service" in the 'Progress Note For' field.
  3. Select the existing service for "Service Code A" in the 'Note Addresses Which Existing Service/Appointment' field.
  4. Select the desired value in the 'Note Type' field.
  5. Enter the desired value in the 'Notes Field'.
  6. Populate any other required and desired fields.
  7. Select "Final" in the 'Draft/Final' field.
  8. Submit the note.
  9. Select "Client A" and navigate to the 'Progress Notes' widget.
  10. Validate the note filed in the previous steps is displayed.
  11. Access the 'Client Ledger' form.
  12. Search "Client A" in the 'Client ID' field.
  13. Select "All Episodes" from the 'Claim/Episode/All Episodes' field.
  14. Select "Simple" in the 'Ledger Type' field.
  15. Select "Yes" in the 'Include Zero Charges' field.
  16. Click [Process].
  17. Validate "Service Code A" is displayed in the Client Ledger.
  18. Close the form.
Bells Notes Integration - Evidence-Based Practices
Scenario 1: Bells Notes Integration - Progress Notes (Group and Individual) - Validate sending 'Evidence-Based Practices'
Specific Setup:
  • myAvatar must be configured to integrate with Bells Notes. Please note: this must be done by a Netsmart Associate.
  • The 'Progress Notes (Group and Individual)' form must have 'Document Routing' enabled.
  • The 'Enable Evidence Based Practice Fields' registry setting must be set to "Y".
  • Must have a note type in Bells for the 'Progress Notes (Group and Individual)' form with the 'Evidence-Based Practices' field available (Note Type A).
  • A user is defined with the following (User A):
  • Access to Bells Notes
  • Associated practitioner
  • Does not require a supervisor's approval for document routing
  • Access to the 'My To Do's' and 'Progress Notes' widgets on the HomeView.
  • A client is enrolled in an existing episode (Client A)
Steps
  1. Log into Bells Notes with existing login credentials for "User A".
  2. Search for "Client A".
  3. Click [Start Note] and verify the existence of the 'Session Information' window.
  4. Fill out all required fields and select "Note Type A".
  5. Verify the existence of "Client A" in the client header when note is started.
  6. Fill out all required fields.
  7. Select the desired value(s) in the 'Evidence-Based Practices' field.
  8. Click [Sign Note].
  9. Validate the Sign Note' dialog is displayed.
  10. Enter the pin for "User A" in the 'Pin' field and click [Sign].
  11. Validate a message is displayed stating: Note Signed Successfully.
  12. Log into myAvatar as "User A".
  13. Navigate to the "My To Do's" widget.
  14. Validate a 'To-Do' is displayed for the note sent via Bells Notes for "Client A".
  15. Click [Approve Document].
  16. Validate the progress note data is displayed, including the value(s) selected in the 'Evidence-Based Practices' field.
  17. Click [Accept].
  18. Enter the password for "User A" in the 'Verify Password' field and click [OK].
  19. Validate the 'To-Do' is no longer displayed.
  20. Select "Client A" and navigate to the 'Progress Notes' widget.
  21. Validate the progress note filed from Bells Notes is displayed.
  22. Validate the progress note data is displayed, including the value(s) selected in the 'Evidence-Based Practices' field.
Scenario 2: Bells Notes Integration - Ambulatory Progress Notes - Validate sending 'Evidence-Based Practices'
Specific Setup:
  • myAvatar must be configured to integrate with Bells Notes. Please note: this must be done by a Netsmart Associate.
  • The 'Ambulatory Progress Notes' form must have 'Document Routing' enabled.
  • The 'Enable Evidence Based Practice Fields' registry setting must be set to "Y".
  • Must have a note type in Bells for the 'Ambulatory Progress Notes' form with the 'Evidence-Based Practices' field available (Note Type A).
  • A user is defined with the following (User A):
  • Access to Bells Notes
  • Associated practitioner
  • Does not require a supervisor's approval for document routing
  • Access to the 'My To Do's' and 'Progress Notes' widgets on the HomeView.
  • A client is enrolled in an existing outpatient episode (Client A)
Steps
  1. Log into Bells Notes with existing login credentials for "User A".
  2. Search for "Client A".
  3. Click [Start Note] and verify the existence of the 'Session Information' window.
  4. Fill out all required fields and select "Note Type A".
  5. Verify the existence of "Client A" in the client header when note is started.
  6. Fill out all required fields.
  7. Select the desired value(s) in the 'Evidence-Based Practices' field.
  8. Click [Sign Note].
  9. Validate the Sign Note' dialog is displayed.
  10. Enter the pin for "User A" in the 'Pin' field and click [Sign].
  11. Validate a message is displayed stating: Note Signed Successfully.
  12. Log into myAvatar as "User A".
  13. Navigate to the "My To Do's" widget.
  14. Validate a To-Do is displayed for the note sent via Bells Notes for "Client A".
  15. Click [Approve Document].
  16. Validate the progress note data is displayed, including the value(s) selected in the 'Evidence-Based Practices' field.
  17. Click [Accept].
  18. Enter the password for "User A" in the 'Verify Password' field and click [OK].
  19. Validate the To-Do is no longer displayed.
  20. Select "Client A" and navigate to the 'Progress Notes' widget.
  21. Validate the progress note filed from Bells Notes is displayed.
  22. Validate the progress note data is displayed, including the value(s) selected in the 'Evidence-Based Practices' field.
Scenario 3: Bells Notes Integration - Inpatient Progress Notes - Validate sending 'Evidence-Based Practices'
Specific Setup:
  • myAvatar must be configured to integrate with Bells Notes. Please note: this must be done by a Netsmart Associate.
  • The 'Inpatient Progress Notes' form must have Document Routing enabled.
  • The 'Enable Evidence Based Practice Fields' registry setting must be set to "Y".
  • Must have a note type in Bells for the 'Inpatient Progress Notes' form with the 'Evidence-Based Practices' field available (Note Type A).
  • A user is defined with the following (User A):
  • Access to Bells Notes
  • Associated practitioner
  • Does not require a supervisor's approval for document routing
  • Access to the 'My To Do's' and 'Progress Notes' widgets on the HomeView.
  • A client is enrolled in an existing inpatient episode (Client A).
Steps
  1. Log into Bells Notes with existing login credentials for "User A".
  2. Search for "Client A".
  3. Click [Start Note] and verify the existence of the 'Session Information' window.
  4. Fill out all required fields and select "Note Type A".
  5. Verify the existence of "Client A" in the client header when note is started.
  6. Fill out all required fields.
  7. Select the desired value(s) in the 'Evidence-Based Practices' field.
  8. Click [Sign Note].
  9. Validate the Sign Note' dialog is displayed.
  10. Enter the pin for "User A" in the 'Pin' field and click [Sign].
  11. Validate a message is displayed stating: Note Signed Successfully.
  12. Log into myAvatar as "User A".
  13. Navigate to the "My To Do's" widget.
  14. Validate a 'To-Do' is displayed for the note sent via Bells Notes for "Client A".
  15. Click [Approve Document].
  16. Validate the progress note data is displayed, including the value(s) selected in the 'Evidence-Based Practices' field.
  17. Click [Accept].
  18. Enter the password for "User A" in the 'Verify Password' field and click [OK].
  19. Validate the To-Do is no longer displayed.
  20. Select "Client A" and navigate to the 'Progress Notes' widget.
  21. Validate the progress note filed from Bells Notes is displayed.
  22. Validate the progress note data is displayed, including the value(s) selected in the 'Evidence-Based Practices' field.
'Progress Notes (Group and Individual)' - Form Return dialog
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Progress Notes (Group and Individual) 4
  • Append Progress Notes
  • ProgressNote Approval
Scenario 1: 'Progress Notes (Group and Individual)' - New Service note
Specific Setup:
  • A client must be defined (Client A).
  • The 'Progress Notes' widget must be accessible on the HomeView.
  • Set the 'Default Staff Associated With Current Login User' option is "N" in 'Registry Setting'.
Steps
  1. Access the 'Progress Notes (Group and Individual)' form.
  2. Select "Client A" in the 'Select Client' field.
  3. Select "New Service" in the 'Progress Note For' field.
  4. Select any value in the 'Note Type' field.
  5. Enter any value in the 'Notes Field' field.
  6. Enter the current date in the 'Date Of Service' field.
  7. Enter any service code in the 'Service Charge Code' field.
  8. Enter any value in the 'Service Duration' field.
  9. Select "Final" in the 'Draft/Final' field.
  10. Click [File Note].
  11. Validate a message is displayed stating: Note Filed. Do you want to return to the Progress Notes form?
  12. Click [No] and the form closes.
  13. Select "Client A" and navigate to the 'Progress Notes' widget.
  14. Validate the note filed in the previous steps is displayed.
Scenario 2: Scheduling Calendar - Launch 'Progress Notes (Group and Individual)' for an appointment
Specific Setup:
  • A client is enrolled in an existing episode and has an appointment scheduled (Client A).
  • The 'Progress Notes' widget must be accessible on the HomeView.
  • The logged in user must have "Progress Notes (Group and Individual)" selected as a form to access from the 'Scheduling Calendar' in the 'User Definition' form.
Steps
  1. Access the 'Scheduling Calendar' form.
  2. Validate the 'Appointment Grid' table contains an appointment for "Client A".
  3. Right click on the appointment for "Client A".
  4. Click [Progress Notes (Group and Individual)].
  5. Validate the 'Progress Notes (Group and Individual)' window is displayed.
  6. Validate the 'Select Client' field contains "Client A".
  7. Validate the 'Select Episode' field contains "Episode 1".
  8. Validate the 'Progress Note For' field contains "Existing Appointment".
  9. Select any value in the 'Note Type' field.
  10. Enter any value in the 'Notes Field' field.
  11. Select "Final" in the 'Draft/Final' field.
  12. Click [File Note].
  13. Validate a "Progress Notes" message is displayed stating: Note Filed.
  14. Click [OK].
  15. Validate the 'Scheduling Calendar' is displayed.
  16. Click [Dismiss].
  17. Select "Client A" and access the 'Progress Notes' widget.
  18. Validate the note filed in the previous steps is displayed.
Scenario 3: Progress Notes (Group and Individual) - Add a progress note via the Client Chart
Specific Setup:
  • A client must be enrolled in an existing episode (Client A).
  • The 'Progress Notes (Group and Individual)' form must be accessible from the Chart View.
Steps
  1. Double click on "Client A" in the 'My Clients' widget.
  2. Verify the 'Chart View' for "Client A" is displayed.
  3. Select 'Progress Notes (Group & Individual)' on the left-hand side.
  4. Validate any previously filed notes are displayed for "Client A".
  5. Click [Add].
  6. Validate the 'Progress Notes (Group and Individual)' form is displayed.
  7. Populate all required and desired fields.
  8. Select "Draft" in the 'Draft/Final' field.
  9. Click [File Note].
  10. Validate a message is displayed stating: Note Filed.
  11. Click [OK].
  12. Validate the 'Chart View' is displayed.
  13. Refresh the chart.
  14. Validate the note filed in the previous steps is displayed.
  15. Close the chart.
Scenario 4: Progress Notes (Group and Individual) - Launch a draft progress note via To Do
Specific Setup:
  • A client is enrolled in an existing episode (Client A).
  • The 'Send Draft To-Do to Submitting User' registry setting is set to "Y" for the 'Progress Notes (Group and Individual)' form.
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 "Independent Note" in the 'Progress Note For' field.
  5. Enter the desired value in the 'Notes Field'.
  6. Select the desired value in the 'Note Type' field.
  7. Select "Draft" in the 'Draft/Final' field.
  8. Click [File Note].
  9. Validate a message is displayed stating: Note Filed. Do you want to return to the Progress Notes form?
  10. Click [No].
  11. Validate the form closes successfully.
  12. Navigate to the 'My To Do's' widget.
  13. Validate there is a 'Review To Do Item' for "Client A".
  14. Click on the link to [Progress Notes (Group and Individual)].
  15. Validate the 'Progress Notes (Group and Individual)' form is displayed with the previously filed draft note details.
  16. Select "Final" in the 'Draft/Final' field.
  17. Click [File Note].
  18. Validate a message is displayed stating: Note Filed.
  19. Click [OK].
  20. Validate the 'Progress Notes (Group and Individual)' form is closed and the user is brought back to the 'My To Do's' widget.
  21. Select "Client A" and access the 'Progress Notes' widget.
  22. Validate the finalized progress note filed in the previous steps is displayed.
Topics
• Progress Notes • CareFabric • Bells Notes • Scheduling Calendar • Chart View
2023 Update 100 Summary | Details
Treatment Plan - Item Deletion
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Treatment Plan
  • Treatment Plan Deletion
Scenario 1: Treatment Plan - validate toggling of the 'Enable Automatic Backup' registry setting
Specific Setup:
  • The 'Avatar CWS->Treatment Plan->Enable Automatic Backup' registry setting must be set to "Y".
  • A client must be enrolled in an existing episode (Client A).
Steps
  1. Select "Client A" and access the 'Treatment Plan' form.
  2. Enter the desired date in the 'Plan Date' field.
  3. Enter the desired value in the 'Plan Name' field.
  4. Select the desired value in the 'Plan Type' field.
  5. Select "Draft" in the 'Treatment Plan Status' field.
  6. Click [Launch Plan].
  7. Add a new problem and populate all required and desired fields.
  8. Click [Back To Plan Page] and close the form.
  9. Select “Client A” and access the ‘Treatment Plan’ form.
  10. Validate the ‘Load From Backup’ dialog displays with a message stating: "You have an unsubmitted backup of a plan from [the current date] and [the current time]. Would you like to load it instead of creating a new one?"
  11. Click [Yes].
  12. Validate the backed up treatment plan data displays.
  13. Leave the form open.
  14. Access the 'Registry Settings' form.
  15. Enter "Enable Automatic Backup" in the 'Limit Registry Settings To The Following Search Criteria' field.
  16. Click [View Registry Settings].
  17. Enter "N" in the 'Registry Setting Value' field.
  18. Click [Submit] and close the form.
  19. Navigate back to the 'Treatment Plan' form.
  20. Click [Submit].
  21. Select "Client A" and access the 'Treatment Plan' form.
  22. Validate the pre-display contains the draft filed in the previous steps.
  23. Click [Edit].
  24. Validate the previously filed data is displayed.
  25. Close the form.
Scenario 2: Treatmetn Plan Copy - Enable Automatic Backup Registry Setting - Item Deletion
Specific Setup:
  • The 'Avatar CWS-> Treatment Plan->->->->Enable Automatic Backup' registry setting must be set to "Y".
  • A client must have an active episode. (Client A).
  • Using the "Create New Treatment Plan" form, create a copy of the treatment plan.
  • The Treatment Plan copy form must be enabled for document routing.
Steps
  1. Select “Client A” and access the Treatment Plan Copy form.
  2. Set the ‘Plan Date’ field to the current date.
  3. Set the ‘Plan Name’ field to any value.
  4. Select any value in the ‘Plan Type’ field.
  5. Select “Draft” in the ‘Treatment Plan Status’ field and click [Launch Plan].
  6. Click [Add New Problem].
  7. Set the ‘Problem Code’ field to any value.
  8. Select “Active” in the ‘Status (Problem List)’ field.
  9. Set the ‘Problem’ field to any value
  10. Select any value in the ‘Status’ field and click [Add New Goal].
  11. Set the ‘Goal’ field to any value.
  12. Select any value in the ‘Status’ field and click [Add New Objective].
  13. Set the ‘Objective’ field to any value.
  14. Select any value in the ‘Status’ field and click [Add New Intervention].
  15. Set the ‘Intervention’ field to any value.
  16. Select any value in the ‘Status’ field and click [Back to Plan Page].
  17. Click [Submit].
  18. Select “Client A” and access the Treatment Plan Copy form.
  19. Select the treatment plan previously filed and click [Edit].
  20. Validate the ‘Plan Date’ field contains the current date.
  21. Validate the ‘Plan Name’ field contains the plan name previously filed.
  22. Validate the ‘Plan Type’ contains the value previously filed.
  23. Validate “Draft” is selected in the ‘Treatment Plan Status’ field and click [Launch Plan].
  24. Validate the Tree View contains the problem, goal, objective, and intervention added in the previous steps.
  25. Validate [Delete Items Selected] is disabled.
  26. Click [Add New Problem].
  27. Set the ‘Problem Code’ field to any value.
  28. Select “Active” in the ‘Status (Problem List)’ field.
  29. Set the ‘Problem’ field to any value
  30. Select any value in the ‘Status’ field and click [Add New Goal].
  31. Set the ‘Goal’ field to any value.
  32. Select any value in the ‘Status’ field and click [Add New Objective].
  33. Set the ‘Objective’ field to any value.
  34. Select any value in the ‘Status’ field and click [Add New Intervention].
  35. Set the ‘Intervention’ field to any value.
  36. Select any value in the ‘Status’ field and click [Back to Plan Page].
  37. Close the form.
  38. Select “Client A” and access the Treatment Plan Copy form.
  39. Select the plan previously filed and click [Edit].
  40. Validate the ‘Load From Backup’ dialog is displayed with a message stating: "You have an unsubmitted back of this plan from [the current date] at [the current time]. Would you like to load it?" and click [Yes].
  41. Click [Launch Plan].
  42. Validate the Tree View contains the problem, goal, objective, and intervention added in the previous steps and the problem, goal, objective, and intervention loaded from the backup.
  43. Select the 2nd intervention item in the Tree View.
  44. Validate the [Delete Item Selected] is enabled.
  45. Click [Back to Plan Page] and close the form.
  46. Access the ‘Registry Setting (PM)’ form.
  47. Set the ‘Limit Registry Settings to the Following Search Criteria’ field to “Enable Automatic Backup” and click [View Registry Settings].
  48. Validate the ‘Registry Setting’ field contains “Avatar CWS ->Treatment Plan->->->->Enable Automatic Backup”.
  49. Validate the ‘Registry Setting Value’ field contains “Y”.
  50. Set the ‘Registry Setting Value’ field to “YD” and click [Submit].
  51. Close the form.
  52. Select “Client A” and access the Treatment Plan Copy form.
  53. Select the plan previously field and click [Edit].
  54. Click [Yes] in the ‘Load From Backup’ dialog.
  55. Click [Launch Plan].
  56. Select the 1st intervention item in the Tree View.
  57. Validate [Delete Item Selected] is enabled.
  58. Select the 2nd intervention item in the Tree View.
  59. Validate [Delete Item Selected] is enabled.
  60. Click [Delete Item Selected].
  61. Validate the ‘Warning’ dialog is displayed with a message stating: “Item Deleted” and click [OK].
  62. Select the 1st intervention item in the Tree View and click [Delete Item Selected].
  63. Click [Back to Plan Page] and [Submit].
  64. Select “Client A” and access the ‘Treatment Plan’ form.
  65. Select the plan previously field and click [Edit].
  66. Click [Launch Plan].
  67. Validate the two intervention items are not displayed in the Tree View.
  68. Close the form.
  69. Open the "Registry Settings" form.
  70. Set the registry setting "Enable Automatic Backup" to "YD".
  71. Submit the form to file the form.
  72. Select "Client A" and access the Treatment Plan Copy form.
  73. Create a new treatment plan.
  74. Select 2 problems from the "Problem List" table.
  75. Click "Launch Plan".
  76. Add multiple goals, objectives, and interventions to the first problem listed.
  77. Click "Return to Plan Page".
  78. Set the "Status" field to "Draft".
  79. Click "Submit".
  80. Open the Treatment Plan Copy form for the same client.
  81. Select the plan that was saved in Draft status.
  82. Click "Launch Plan".
  83. Click "Return to Plan Page".
  84. Click "Discard".
  85. Open the Treatment Plan Copy form for the same client.
  86. Select the plan that was saved in Draft status.
  87. Respond "No" to the 'Default from Back Up' message.
  88. Click "Launch Plan Page".
  89. Delete the interventions, objectives, and goals for the first problem in the treatment plan.
  90. Click "Return to Plan Page".
  91. Click "Submit" and save the plan in draft.
  92. Open the Treatment Plan Copy form for the same client.
  93. Select the plan that was saved in Draft status.
  94. Click "Launch Plan".
  95. Click "Return to Plan Page".
  96. Click "Discard".
  97. Open the Treatment Plan Copy form for the same client.
  98. Select the plan that was saved in Draft status.
  99. Respond "No" to the 'Default from Back Up' message.
  100. Click "Launch Plan Page".
  101. Delete the 2nd problem on the treatment plan.
  102. Click "Return to Plan Page".
  103. Click "Submit".
  104. Open the Treatment Plan Copy form for the same client.
  105. Select the plan that was saved in Draft status.
  106. Respond "No" to the 'Default from Back Up' message.
  107. Validate the 2nd problem is no longer checked in the "Problem List" table.
  108. Click "Launch Plan Page".
  109. Validate the deleted problem isn't listed in the tree view of the plan.
  110. Set the "Status" to "Final".
  111. Click "Submit".
  112. Click "Accept".
  113. Open the "Clinical Document Viewer".
  114. Validate one can view the treatment plan that was just finalized.
Treatment Plan - Finalizing Plans
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Treatment Plan
  • Treatment Plan Deletion
Scenario 1: Treatment Plan - Field Data Validations
Specific Setup:
  • Have a treatment plan with a 'disabled ' field, set up as the last field in the Problem, Goals, Objective or Interventions sections. For example, a disabled "Scrolling Free Text" field.
  • Have another field set up right before the disabled last field in each section, that requires a selection or input type entry. For example, a "Site Specific" dictionary or integer field.
  • Registry Setting "Enable Service Entry Restrictions by Client Treatment Plan "is set to "S".
  • Registry Setting "Activate Program/Service Code Filter" = "Y".
Steps
  1. Open the "Treatment Plan" form:
  2. Search and select a client in the 'Select Client' field.
  3. Enter a plan name in the "Plan Name" field.
  4. Enter the current date in the 'Plan Date' field.
  5. Select any value from the 'Plan Type' field.
  6. Select "Draft" from the "Treatment Plan Status" field.
  7. Click [Launch Plan].
  8. Click [Add New Problem].
  9. Enter any value in the 'Problem Code' field.
  10. Enter any value in the 'Problem' field.
  11. Enter the current date in the 'Date of Onset' field.
  12. Select "Active" from the "Status (Problem List)" field.
  13. Populate any other desired fields, except for the last two fields in the section.
  14. Navigate to the next to last field, which should be the one located right before the disabled field, as outline in the setup section.
  15. Select or input a value in the next to last field in the section.
  16. Click the 'Tab' key.
  17. Click [Back to Plan Page].
  18. Validate all data enter on the main section is populated as expected.
  19. Click [Launch Plan].
  20. Select the "Problem" added in step 1g.
  21. Validate all the fields are populated in the section as expected, including the value populated in next to last field of the section.
  22. Click [Add New Goal].
  23. Populate all the required and desired fields in the section, except for the last two fields in the section.
  24. Repeat steps 1m -1q.
  25. Validate the results are as expected.
  26. Click [Add New Objective].
  27. Populate all the required and desired fields in the section, except for the last two fields in the section.
  28. Repeat steps 1m-1q.
  29. Validate the results are as expected.
  30. Click [Add New Intervention].
  31. Populate all the required and desired fields in the section, except for the last two fields in the section.
  32. Repeat steps 1m-1q.
  33. Validate the results are as expected.
  34. Click [Back to Plan Page].
  35. Click [Submit].
  36. Open the "Treatment Plan" form:
  37. Search and select the same client used in the prior step, in the 'Select Client' field.
  38. Select the treatment plan just filed.
  39. Validate all data enter on the main section is populated as expected.
  40. Click to the view data field in "Problems", "Goals", "Objectives" and "Interventions" sections.
  41. Validate all data filed is present, as expected.
  42. Open the "Treatment Plan" form:
  43. Create another treatment plan for the client.
  44. Fill out the Problem and Intervention sections.
  45. In the Intervention, add some "Assigned Services".
  46. Delete the services that were just entered.
  47. Validate all the service rows were deleted.
  48. Click "Back to Plan Page".
  49. At this point, you can either finalize the form or you can Click "Close Form".
Scenario 2: Treatment Plan - 'Enable Automatic Backup' registry setting - Item Deletion
Specific Setup:
  • The 'Avatar CWS-> Treatment Plan->->->->Enable Automatic Backup' registry setting must be set to "Y".
  • A client must have an active episode. (Client A)
  • The Treatment Plan form must be enabled for document routing.
Steps
  1. Select “Client A” and access the ‘Treatment Plan’ form.
  2. Set the ‘Plan Date’ field to the current date.
  3. Set the ‘Plan Name’ field to any value.
  4. Select any value in the ‘Plan Type’ field.
  5. Select “Draft” in the ‘Treatment Plan Status’ field and click [Launch Plan].
  6. Click [Add New Problem].
  7. Set the ‘Problem Code’ field to any value.
  8. Select “Active” in the ‘Status (Problem List)’ field.
  9. Set the ‘Problem’ field to any value
  10. Select any value in the ‘Status’ field and click [Add New Goal].
  11. Set the ‘Goal’ field to any value.
  12. Select any value in the ‘Status’ field and click [Add New Objective].
  13. Set the ‘Objective’ field to any value.
  14. Select any value in the ‘Status’ field and click [Add New Intervention].
  15. Set the ‘Intervention’ field to any value.
  16. Select any value in the ‘Status’ field and click [Back to Plan Page].
  17. Click [Submit].
  18. Select “Client A” and access the ‘Treatment Plan’ form.
  19. Select the treatment plan previously filed and click [Edit].
  20. Validate the ‘Plan Date’ field contains the current date.
  21. Validate the ‘Plan Name’ field contains the plan name previously filed.
  22. Validate the ‘Plan Type’ contains the value previously filed.
  23. Validate “Draft” is selected in the ‘Treatment Plan Status’ field and click [Launch Plan].
  24. Validate the Tree View contains the problem, goal, objective, and intervention added in the previous steps.
  25. Validate [Delete Items Selected] is disabled.
  26. Click [Add New Problem].
  27. Set the ‘Problem Code’ field to any value.
  28. Select “Active” in the ‘Status (Problem List)’ field.
  29. Set the ‘Problem’ field to any value
  30. Select any value in the ‘Status’ field and click [Add New Goal].
  31. Set the ‘Goal’ field to any value.
  32. Select any value in the ‘Status’ field and click [Add New Objective].
  33. Set the ‘Objective’ field to any value.
  34. Select any value in the ‘Status’ field and click [Add New Intervention].
  35. Set the ‘Intervention’ field to any value.
  36. Select any value in the ‘Status’ field and click [Back to Plan Page].
  37. Close the form.
  38. Select “Client A” and access the ‘Treatment Plan’ form.
  39. Select the plan previously filed and click [Edit].
  40. Validate the ‘Load From Backup’ dialog is displayed with a message stating: "You have an unsubmitted back of this plan from [the current date] at [the current time]. Would you like to load it?" and click [Yes].
  41. Click [Launch Plan].
  42. Validate the Tree View contains the problem, goal, objective, and intervention added in the previous steps and the problem, goal, objective, and intervention loaded from the backup.
  43. Select the 2nd intervention item in the Tree View.
  44. Validate the [Delete Item Selected] is enabled.
  45. Click [Back to Plan Page] and close the form.
  46. Access the ‘Registry Setting (PM)’ form.
  47. Set the ‘Limit Registry Settings to the Following Search Criteria’ field to “Enable Automatic Backup” and click [View Registry Settings].
  48. Validate the ‘Registry Setting’ field contains “Avatar CWS ->Treatment Plan->->->->Enable Automatic Backup”.
  49. Validate the ‘Registry Setting Value’ field contains “Y”.
  50. Set the ‘Registry Setting Value’ field to “YD” and click [Submit].
  51. Close the form.
  52. Select “Client A” and access the ‘Treatment Plan’ form.
  53. Select the plan previously field and click [Edit].
  54. Click [Yes] in the ‘Load From Backup’ dialog.
  55. Click [Launch Plan].
  56. Select the 1st intervention item in the Tree View.
  57. Validate [Delete Item Selected] is enabled.
  58. Select the 2nd intervention item in the Tree View.
  59. Validate [Delete Item Selected] is enabled.
  60. Click [Delete Item Selected].
  61. Validate the ‘Warning’ dialog is displayed with a message stating: “Item Deleted” and click [OK].
  62. Select the 1st intervention item in the Tree View and click [Delete Item Selected].
  63. Click [Back to Plan Page] and [Submit].
  64. Select “Client A” and access the ‘Treatment Plan’ form.
  65. Select the plan previously field and click [Edit].
  66. Click [Launch Plan].
  67. Validate the two intervention items are not displayed in the Tree View.
  68. Close the form.
  69. Open the "Registry Settings" form.
  70. Set the registry setting "Enable Automatic Backup" to "YD".
  71. Submit the form to file the form.
  72. Select "Client A" and access the "Treatment Plan" form.
  73. Create a new treatment plan.
  74. Select 2 problems from the "Problem List" table.
  75. Click "Launch Plan".
  76. Add multiple goals, objectives, and interventions to the first problem listed.
  77. Click "Return to Plan Page".
  78. Set the "Status" field to "Draft".
  79. Click "Submit".
  80. Open the "Treatment Plan" form for the same client.
  81. Select the plan that was saved in Draft status.
  82. Click "Launch Plan".
  83. Click "Return to Plan Page".
  84. Click "Discard".
  85. Open the "Treatment Plan" form for the same client.
  86. Select the plan that was saved in Draft status.
  87. Respond "No" to the 'Default from Back Up' message.
  88. Click "Launch Plan Page".
  89. Delete the interventions, objectives, and goals for the first problem in the treatment plan.
  90. Click "Return to Plan Page".
  91. Click "Submit" and save the plan in draft.
  92. Open the "Treatment Plan" form for the same client.
  93. Select the plan that was saved in Draft status.
  94. Click "Launch Plan".
  95. Click "Return to Plan Page".
  96. Click "Discard".
  97. Open the "Treatment Plan" form for the same client.
  98. Select the plan that was saved in Draft status.
  99. Respond "No" to the 'Default from Back Up' message.
  100. Click "Launch Plan Page".
  101. Delete the 2nd problem on the treatment plan.
  102. Click "Return to Plan Page".
  103. Click "Submit".
  104. Open the "Treatment Plan" form for the same client.
  105. Select the plan that was saved in Draft status.
  106. Respond "No" to the 'Default from Back Up' message.
  107. Validate the 2nd problem is no longer checked in the "Problem List" table.
  108. Click "Launch Plan Page".
  109. Validate the deleted problem isn't listed in the tree view of the plan.
  110. Set the "Status" to "Final".
  111. Click "Submit".
  112. Click "Accept".
  113. Open the "Clinical Document Viewer".
  114. Validate one can view the treatment plan that was just finalized.
Topics
• Treatment Plan • NX
 

Avatar_CWS_2024_Quarterly_Release_2024.02_Details.csv