Skip to main content

Avatar CWS 2022 Monthly Release 2022.01.02 Acceptance Tests

  1. Last updated
  2. Save as PDF
Update 12 Summary | Details
Progress Notes - ToDo Notification for the split services
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Guarantors/Payors
  • Service Codes
  • CPT Code Definition (PM)
  • Registry Settings (PM)
  • Set System Defaults (CWS)
  • User Definition
  • Dynamic Form - Admission - Client
  • Admission (Outpatient)
  • Financial Eligibility
  • Managed Care Authorizations
  • Client Charge Input
  • Delete/Re-Assign To Do Items
  • Client Ledger
  • Dynamic Form - Edit Service Information - Select Service(s) to Edit
  • Dynamic Form - document routing - sign
  • Dynamic Form - document routing - verify password
  • Review To Do Item (PM)
Scenario 1: Split service - Validating 'ToDo's’ note notification requirement - Service created in 'Client Charge Input' and updated in 'Edit Service Information'.
Specific Setup:
  • Guarantor/Payors:
  • An existing guarantor is selected to edit, or a new guarantor is identified. Note the guarantor’s code/name.
  • Authorization Information Section:
  • Select 'Check For Available Units' in the 'Verify Services and Appointments Against Available Authorizations' field.
  • Select 'Warn User If Authorization Is Missing' in the 'Verification Level For Authorizations For Client Charge Input' field.
  • Select 'Warn User If Authorization Is Missing' in the 'Verification Level For Authorizations For Appointment Scheduling' field.
  • Select 'Report As Error And Include On Bill' in the 'Verification Level For Authorizations For 837 Electronic Billing' field.
  • Set the 'Split Service If The Authorization Does Not Cover Units' to "Yes".
  • Admission (Outpatient):
  • A new client is admitted in an outpatient program. Note the client's id/name, admission program,
  • Financial Eligibility:
  • The guarantor identified above is assigned to the client.
  • Diagnosis:
  • A new diagnosis record is created for the client.
  • Service Codes:
  • A new service code is added as below. Note the service code/value.
  • Type Of Fee= User Defined
  • Minutes per Unit = desired value
  • Service Fee/Cross Reference Maintenance:
  • Service fee definition is created for the above service code.
  • Managed Care Authorizations:
  • A 'Managed Care Authorization' record is created for the client/guarantor/service code identified above.
  • The 'Maximum Units' field is set to a value that will not cover all services. Note the value.
  • Enter desired value in all required fields.
  • Client Charge Input:
  • A new service is rendered to the client. The 'Service Duration' is set to desired minutes that makes the number of units more than the 'Maximum Units' in the 'Managed Care Authorization' section. This will create a split service.
  • Client Ledger:
  • The rendered service is split into two services: one service with the units defined in the 'Maximum Units' field and the other service for the remaining units.
  • Close Charges:
  • All the charges are closed.
  • An interim billing batch is created to include the client, service, and guarantor. Note the interim billing batch#.
Steps
  1. Open the 'Edit Service Information' form.
  2. Select the service created in 'Setup' that uses the allowable un.
  3. Enter a diagnosis code or a referring practitioner.
  4. Click [Submit].
  5. Verify the system generates two To-dos notifications for the service updated through 'Edit Service Information' and the note is not attached to the service:
  6. Note requirement To-do.
  7. Service modified To-do. (i.e. 2022-05-11 Wednesday 02:43 PM [CLIENTFIRSTNAME CLIENTLASTNAME (CLIENTID)] Service [SERVICE CODE VALUE] For Service Date [DATE OF THE SERVICE]) Episode 1 Requires a note, 2022-05-11 Wednesday 02:43 PM Edit Service Information [CLIENTFIRSTNAME CLIENTLASTNAME (CLIENTID)] has a service '[SERVICE CODE VALUE] (SERVICE CODE)' on '[DATE OF THE SERVICE]' that was modified.)
Scenario 2: Split service - Validating 'ToDo's' note notification requirement - Service created through progress notes.
Specific Setup:
  • Guarantor/Payors:
  • An existing guarantor is selected to edit or a new guarantor is identified. Note the guarantor's code/name.
  • Authorization Information Section:
  • Select 'Check For Available Units' in the 'Verify Services and Appointments Against Available Authorizations' field.
  • Select 'Warn User If Authorization Is Missing' in the 'Verification Level For Authorizations For Client Charge Input' field.
  • Select 'Warn User If Authorization Is Missing' in the 'Verification Level For Authorizations For Appointment Scheduling' field.
  • Select 'Report As Error And Include On Bill' in the 'Verification Level For Authorizations For 837 Electronic Billing' field.
  • Set the 'Split Service If The Authorization Does Not Cover Units' to "Yes".
  • Admission (Outpatient):
  • A new client is admitted in an outpatient program. Note the client's id/name, admission program.
  • Financial Eligibility:
  • The guarantor identified above is assigned to the client.
  • Diagnosis:
  • A new diagnosis record is created for the client.
  • Service Codes:
  • A new service code is added as below. Note the service code/value.
  • Type Of Fee= User Defined
  • Minutes per Unit = desired value
  • Service Fee/Cross Reference Maintenance:
  • Service fee definition is created for the above service code.
  • Managed Care Authorizations:
  • Create a 'Managed Care Authorization' record for the client/guarantor/service code identified above. Note the client/guarantor/service code.
  • The 'Maximum Units' field is set to a value that will not cover all services. Note the value.
  • Enter desired value in all required fields.
  • Progress Note:
  • A new service is rendered to the client. The 'Service Duration' is set to desired minutes that makes the number of units more than the 'Maximum Units' in the 'Managed Care Authorization' section. This will create a split service.
  • Client Ledger:
  • The rendered service is split into two services: one service with the units defined in the 'Maximum Units' field and the other service for the remaining units.
  • Close Charges:
  • All the charges are closed.
  • An interim billing batch is created to include the client, service and guarantor. Note the interim billing batch#.
Steps
  1. Open the 'Edit Service Information' form.
  2. Select the service with the units same as 'Maximum Units' defined in the 'Managed Care Authorization' form.
  3. Enter a diagnosis code or a referring practitioner.
  4. Click [Submit].
  5. Verify the system does not generate a progress note requirement To-do notification for the service updated through 'Edit Service Information' as the note is already attached to the service.
  6. System only generates the To do notification for the service updated (i.e. 2022-05-11 Wednesday 02:43 PM Edit Service Information [CLIENTFIRSTNAME CLIENTLASTNAME (CLIENTID)] has a service '[SERVICE CODE VALUE] (SERVICE CODE)' on '[DATE OF THE SERVICE]' that was modified.)
Topics
• Client Charge Input • Progress Notes • NX
Update 15 Summary | Details
'Medications Dispensed' widget will display the name of the medication.
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Medications Dispensed
  • Client Chart
Scenario 1: 'Medications Dispensed' Widget validation of order name display.
Specific Setup:
  • 'Medications Dispensed' widget is added to a logged in user's home view.
  • 'Medications Dispensed' form is added to Chart view.
  • Registry Setting 'Avatar CWS->Other Chart Entry->Medications Dispensed->>>Select Medication from Avatar OE Order Codes' is set to 'Y'. This setting will use the Avatar OE Order Codes table. This will update the 'Medications Dispensed' option to include the 'Medication Order Code' lookup field and will remove the 'Medication Name' dictionary search field. Avatar OE must be installed in order to select 'Y'. Note that once this registry setting is set to 'Y' and OE Medications are selected, the setting can no longer be reset to 'N'.
Steps
  1. Select any client "Client A" and access the 'Medications Dispensed' form.
  2. Populate the required fields selecting any medication from the 'Medication Order Code' field.
  3. File the form.
  4. Validate the correct medication and order code are displayed.
  5. Access "Client A's" chart view.
  6. Click the 'Medications Dispensed' link.
  7. Validate the correct medication and order code are displayed.
Topics
• Registry Settings • NX • Medications Dispensed • Medications Dispensed widget
Update 17 Summary | Details
'Treatment Plan' web service
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • SoapUI - Add Treatment Plan
  • Treatment Plan
  • SoapUI - Edit 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 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).
  • A console widget must be configured for the 'Treatment Plan' form ('Treatment Plan' widget).
  • A view must be configured to have the 'Treatment Plans' widget and the 'Console Widget Viewer' (View 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. 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. Populate any other desired fields.
  18. Enter "STAFF" in the 'Role' field.
  19. Enter the desired staff ID in the 'StaffMember' field.
  20. Enter "57020" in the 'TreatmentPlanParticipants' - 'SSSignature' - 'FieldNumber' field.
  21. Enter a base64 encoded signature value in the 'TreatmentPlanParticipants' - 'SSSignature' - 'FieldValue' field.
  22. Enter "52143" in the 'SSSignature' - 'FieldNumber' field.
  23. Enter a base64 encoded signature value in the 'SSSignature' - 'FieldValue' field.
  24. Enter "Client A" in the 'ClientID' field.
  25. Enter "1" in the 'EpisodeNumber' field.
  26. Enter "CWS60000" in the 'OptionID' field.
  27. Click [Run].
  28. Validate the 'Confirmation' field contains the unique ID for the treatment plan filed.
  29. Validate the 'Message' field contains: "Treatment Plan web service has been filed successfully".
  30. Select "Client A" and access "View A".
  31. Validate the 'Treatment Plan' widget contains the record added in the previous steps.
  32. Click [View].
  33. Validate the 'Console Widget Viewer' displays all treatment plan data filed in the previous steps.
  34. Validate the 'SS Treatment Plan Client Sign 1' field contains the signature added in the previous steps.
  35. Validate the 'SS Treatment Plan Part Sign 1' field contains the signature added in the previous steps.
  36. Click [Close All].
Scenario 2: Treatment Plan Web Service - Edit Treatment Plan
Specific Setup:
  • A client is enrolled in an existing episode and has a draft '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).
  • A console widget must be configured for the 'Treatment Plan' form ('Treatment Plan' widget).
  • A view must be configured to have the 'Treatment Plans' widget and the 'Console Widget Viewer' (View 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. Populate any other desired fields.
  18. Enter "STAFF" in the 'Role' field.
  19. Enter the desired staff ID in the 'StaffMember' field.
  20. Enter "57020" in the 'TreatmentPlanParticipants' - 'SSSignature' - 'FieldNumber' field.
  21. Enter a base64 encoded signature value in the 'TreatmentPlanParticipants' - 'SSSignature' - 'FieldValue' field.
  22. Enter "52143" in the 'SSSignature' - 'FieldNumber' field.
  23. Enter a base64 encoded signature value in the 'SSSignature' - 'FieldValue' field.
  24. Enter "Client A" in the 'ClientID' field.
  25. Enter "1" in the 'EpisodeNumber' field.
  26. Enter the unique ID for the existing 'Treatment Plan' record in the 'TPUniqueID' field.
  27. Click [Run].
  28. Validate the 'Confirmation' field contains the unique ID for the treatment plan filed.
  29. Validate the 'Message' field contains: "Treatment Plan web service has been filed successfully".
  30. Select "Client A" and access "View A".
  31. Validate the 'Treatment Plan' widget contains the record updated in the previous steps.
  32. Click [View].
  33. Validate the 'Console Widget Viewer' displays all treatment plan data updated in the previous steps.
  34. Validate the 'SS Treatment Plan Client Sign 1' field contains the signature updated in the previous steps.
  35. Validate the 'SS Treatment Plan Part Sign 1' field contains the signature updated in the previous steps.
  36. Click [Close All].
Scenario 3: 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 • Signatures
Update 22 Summary | Details
Progress Notes - Significant Findings - Future Dates
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Significant Findings
  • Vitals Entry
Scenario 1: New Service note in 'Progress Notes (Group and Individual)'
Specific Setup:
  • Using 'Site Specific Section Modeling', 3 fields must be created:
  1. A date field "TestingTheAllow" set to allow future dates ("No").
  2. A date field "TestingTheError" set to an error dialog when future dates are selected ("Error").
  3. A date field "TestingTheWarning" set to a warning ("Warning").
  • A client must be enrolled in an existing episode (Client A).
Steps
  1. Select "Client A" and access the 'Progress Notes (Group and Individual)' form.
  2. Select desired episodes from the 'Request Episode(s)' field.
  3. Select 'New Service'.
  4. Select "Psychologist" from the 'Note Type' field.
  5. Set 'Notes Field' field to "test".
  6. Search for and select a valid practitioner in the 'Practitioner' field.
  7. Set the 'Date Of Service' field to a future date.
  8. Validate the 'Warning' Dialog is displayed and click [Cancel].
  9. Set the 'Date Of Service' field to a date in the past.
  10. Validate the 'Date Of Service' field is set to a date in the past.
  11. Search for and select any desired code in the 'Service Charge Code'.
  12. Select "Draft" from the 'Draft/Final' field.
  13. Set the 'Date' field to the current date.
  14. Set the 'TestingTheWarning' field to a future date.
  15. Validate the 'Warning' Dialog is displayed and click [Cancel].
  16. Set the 'TestingTheWarning' field to a future date.
  17. Validate the 'Warning' Dialog is displayed and click [OK].
  18. Validate the 'TestingTheWarning' field contains a future date.
  19. Set the 'TestingTheWarning' field to the current date.
  20. Validate the 'TestingTheWarning' field is set to the current date.
  21. Set the 'TestingTheError' field to a date future date.
  22. Validate the 'Error' Dialog is displayed and click [OK].
  23. Set the 'TestingTheError' field to the current date.
  24. Validate the 'TestingTheError' field is set to the current date.
  25. Set the 'TestingTheAllow' field to a future date.
  26. Validate the 'TestingTheAllow' field is set to a future date.
  27. Click [File Note].
  28. Access the clients chart and confirm a new progress form was filed.
Scenario 2: Significant Findings - Vital Sign
Specific Setup:
  • The 'Avatar CWS->Other Chart Entry->Significant Findings->->->Allow Future Significant Finding Date' registry setting must be set to "1".
  • A client must be enrolled in an existing episode (Client A).
Steps
  1. Select "Client A" and access the 'Vitals Entry' form.
  2. Select "Add" in the 'Update Vital Sign' field.
  3. Enter the current date in the 'Date' field.
  4. Enter "9:00 AM" in the 'Time' field.
  5. Populate all desired fields.
  6. Click [Submit] and [No] to exit the form.
  7. Select "Client A" and access the 'Significant Findings' form.
  8. Set the 'Significant Finding Date' field to a future date.
  9. Validate the 'Significant Finding Date' field is a future date.
  10. Set the "Allow Future Significant Finding Date" registry setting to "2".
  11. Log out of the application and log back in.
  12. Select "Client A" and access the 'Significant Findings' form.
  13. Set the 'Significant Finding Date' field to a future date.
  14. Validate the 'Warning' Dialog is displayed and click [Cancel].
  15. Set the 'Significant Finding Date' field to the current date.
  16. Validate the 'Significant Finding Date' field is set to the current date.
  17. Enter the current time in the 'Significant Finding Time' field.
  18. Validate the 'Findings' field contains the vitals filed in the previous steps.
  19. Validate the 'Findings' field is sorted in descending chronological order.
  20. Close the form.
  21. Select "Client A" and access the 'Vitals Entry' form.
  22. Select "Add" in the 'Update Vital Sign' field.
  23. Enter the current date in the 'Date' field.
  24. Enter "9:00 AM" in the 'Time' field.
  25. Populate all desired fields.
  26. Click [Submit] and [No] to exit the form.
  27. Set the "Allow Future Significant Finding Date" registry setting to "3".
  28. Log out of the application and log back in.
  29. Select "Client A" and access the 'Significant Findings' form.
  30. Set the 'Significant Finding Date' field to a future date.
  31. Validate the 'Error' Dialog is displayed and click [OK].
  32. Set the 'Significant Finding Date' field to the current date.
  33. Validate the 'Significant Finding Date' field is set to the current date.
  34. Set the 'Significant Finding Time' field to a future time.
  35. Validate the 'Error' Dialog is displayed and click [OK].
  36. Enter the current time in the 'Significant Finding Time' field.
  37. Validate the 'Findings' field contains the vitals filed in the previous steps.
  38. Validate the 'Findings' field is sorted in descending chronological order.
  39. Close the form.
Topics
• Progress Notes • Vitals
Update 31 Summary | Details
The 'ClinicalPathwayEnroll' web service
Scenario 1: Clinical Pathway Enrollment - Add an enrollment
Specific Setup:
  • A pathway is defined in the 'Clinical Pathway Definition' form. "Yes" is selected in the 'Alert When Accessed' field. This pathway is also defined with a color (Pathway A).
  • Multiple other pathways are defined with colors in the 'Clinical Pathway Definition' form.
  • A client is enrolled in an existing episode (Client A).
Steps
  1. Select "Client A" and access the 'Clinical Pathway Enrollment' form.
  2. Verify the 'Date of Enrollment' field defaults to the current date.
  3. Select "Pathway A" in the 'Pathway Name' field.
  4. Select "Yes" for 'Primary Pathway'.
  5. Click [Submit] and [No].
  6. Validate the 'My Clients' list contains "Client A" in the pathway color.
  7. Select "Client A" and access the 'Clinical Pathway Enrollment' form.
  8. Click [Add] to add an additional pathway.
  9. Select "Pathway A" in the 'Pathway Name' field.
  10. Validate a message is displayed stating: Client is already enrolled in the selected Clinical Pathway.
  11. Click [OK].
  12. Select any new value in the 'Pathway Name' field.
  13. Select "Yes" for 'Primary Pathway'.
  14. Validate a message is displayed stating: Primary Pathway already exists. "Pathway A" is the current Primary Pathway.
  15. Click [OK].
  16. Select "No" in the 'Primary Pathway' field.
  17. Click [Submit] and [No].
  18. Validate the 'My Clients' list contains "Client A" in the primary pathway color.
Scenario 2: Clinical Pathway Enrollment - Update an Enrollment
Specific Setup:
  • Clinical Pathway Enrollment on file for a test client.
Steps
  1. Open "Clinical Pathway Enrollment" form for a test client.
  2. Select a record from the pre-display.
  3. Click [Edit].
  4. Verify the "Date of Enrollment" field is displayed and disabled.
  5. Verify the "Pathway Name" field is displayed and disabled.
  6. The only field that can be edited is the "Primary Pathway" field.
  7. Select "Yes" in the "Primary Pathway" field.
  8. Click [Submit].
  9. Click "No" on the prompt "Do you want to return to Pre-Display".
Scenario 3: Clinical Pathway Enrollment - Delete an enrollment
Specific Setup:
  • A pathway is defined in the 'Clinical Pathway Definition' form. "Yes" is selected in the 'Alert When Accessed' field. This pathway is also defined with a color (Pathway A).
  • A client is enrolled in an existing episode (Client A).
Steps
  1. Select "Client A" and access the 'Clinical Pathway Enrollment' form.
  2. Verify the 'Date of Enrollment' field defaults to the current date.
  3. Select "Pathway A" in the 'Pathway Name' field.
  4. Select "Yes" for 'Primary Pathway'.
  5. Click [Submit] and [No].
  6. Validate the 'My Clients' list contains "Client A" in the pathway color.
  7. Select "Client A" and access the 'Clinical Pathway Enrollment' form.
  8. Select the existing enrollment in the pre-display.
  9. Click [Delete].
  10. Validate a message is displayed stating: Are you sure you want to delete this item?
  11. Click [Yes].
  12. Validate a message is displayed stating: Enrollment was successfully deleted.
  13. Click [OK] and exit the form.
  14. Validate the 'My Clients' list contains "Client A" without the pathway color.
Scenario 4: Validate the 'ClinicalPathwayEnroll' - 'AddEnrollment' web service
Specific Setup:
  • A pathway is defined in the 'Clinical Pathway Definition' form. "Yes" is selected in the 'Alert When Accessed' field. This pathway is also defined with pathway colors and icons (Pathway A).
  • A client is enrolled in an existing episode (Client A).
Steps
  1. Access SoapUI for the 'ClinicalPathwayEnroll' - 'AddEnrollment' 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 current date in the 'EnrollmentDate' field.
  6. Enter "PathwayA" in the 'PathwayName' field.
  7. Enter "Y" in the 'PrimaryPathway' field.
  8. Enter "ClientA" in the 'ClientID' field.
  9. Click [Run].
  10. Validate the 'Confirmation' field contains: "Unique ID : CPE#####.###".
  11. Validate the 'Message' field contains: "Clinical Pathway Enrollment web service has been filed successfully".
  12. Select "Client A" from the 'My Clients' list.
  13. Validate an alert is displayed stating: "Selected Client is Enrolled in the following Clinical Pathways: PathwayA".
  14. Click [Yes] to proceed.
  15. Access the 'Clinical Pathway Enrollment' form.
  16. Validate the record added in the previous steps is displayed and select it.
  17. Validate the 'Client Header' contains "Client A" in the pathway color and contains the icon associated with "PathwayA".
  18. Validate the 'Date of Enrollment' field contains the current date.
  19. Validate the 'Pathway Name' field contains "PathwayA".
  20. Validate "Yes" is selected in the 'Primary Pathway' field.
  21. Close the form.
Scenario 5: Validate the 'ClinicalPathwayEnroll' - 'UpdateEnrollment' web service
Specific Setup:
  • A pathway is defined in the 'Clinical Pathway Definition' form. "Yes" is selected in the 'Alert When Accessed' field. This pathway is also defined with a pathway color and icon (Pathway A).
  • A client is enrolled in "Pathway A" as the primary pathway (Client A).
Steps
  1. Access SoapUI for the 'ClinicalPathwayEnroll' - 'UpdateEnrollment' 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 "N" in the 'PrimaryPathway' field.
  6. Enter "ClientA" in the 'ClientID' field.
  7. Enter the unique ID for the enrollment in the 'enrollHG' field.
  8. Click [Run].
  9. Validate the 'Confirmation' field contains: "Unique ID : CPE#####.###".
  10. Validate the 'Message' field contains: "Clinical Pathway Enrollment web service has been filed successfully".
  11. Select "Client A" from the 'My Clients' list.
  12. Validate an alert is displayed stating: "Selected Client is Enrolled in the following Clinical Pathways: PathwayA".
  13. Click [Yes] to proceed.
  14. Access the 'Clinical Pathway Enrollment' form.
  15. Validate the record updated in the previous steps is displayed and select it.
  16. Validate the 'Primary Pathway' field is set to "No".
  17. Close the form.
Scenario 6: Validate the 'ClinicalPathwayEnroll' - 'DeleteEnrollment' web service
Specific Setup:
  • A pathway is defined in the 'Clinical Pathway Definition' form (Pathway A).
  • A client is enrolled in "Pathway A" (Client A).
Steps
  1. Access SoapUI for the 'ClinicalPathwayEnroll' - 'DeleteEnrollment' 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 "ClientA" in the 'ClientID' field.
  6. Enter the unique ID for the enrollment in the 'enrollHG' field.
  7. Click [Run].
  8. Validate the 'Message' field contains: "Clinical Pathway Enrollment web service has been filed successfully".
  9. Select "Client A" and access the 'Clinical Pathway Enrollment' form.
  10. Validate the enrollment deleted is no longer displayed.
  11. Close the form.
Scenario 7: Validate the 'ClinicalPathwayEnroll' - 'GetDictionaryItems' web service
Specific Setup:
  • One or more pathways must be defined in the 'Clinical Pathway Definition' form.
Steps
  1. Access SoapUI for the 'ClinicalPathwayEnroll' - 'GetDictionaryItems' 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. Click [Run].
  6. Validate the 'GetDictionaryItemsResponse' field is populated with the defined dictionary values associated to the 'Clinical Pathway Enrollment' form.
The 'ClinicalPathwayDisenroll' web service
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Clinical Pathway Disenrollment
Scenario 1: Clinical Pathway Disenrollment - Add a Disenrollment
Specific Setup:
  • A pathway is defined in the 'Clinical Pathway Definition' form. "Yes" is selected in the 'Alert When Accessed' field. This pathway is also defined with a color (Pathway A).
  • Dictionary values must be defined for the "CWS" file - "(5010) Reason for Disenrollment" data element. This can be done in the 'Dictionary Update' form.
Steps
  1. Select "Client A" and access the 'Clinical Pathway Enrollment' form.
  2. Verify the 'Date of Enrollment' field defaults to the current date.
  3. Select "Pathway A" in the 'Pathway Name' field.
  4. Select "Yes" for 'Primary Pathway'.
  5. Click [Submit] and [No].
  6. Validate the 'My Clients' list contains "Client A" in the pathway color.
  7. Select "Client A" and access the 'Clinical Pathway Disenrollment' form.
  8. Validate the 'Date of Disenrollment' field defaults the current date.
  9. Select "Pathway A" in the 'Pathway Name' field.
  10. Select desired value in the 'Reason for Disenrollment' field.
  11. Click [Submit] and [No].
  12. Select "Client A" and access the 'Clinical Pathway Enrollment' form.
  13. Validate the Pre-Display contains the prior enrollment record in "Pathway A" and the 'Disenrollment Date' field contains the date of disenrollment.
  14. Click [Edit].
  15. Validate a "Clinical Pathway Enrollment" message is displayed stating: Disenrollment exists. Enrollment can only be viewed.
  16. Click [OK].
  17. Validate the 'Date of Enrollment' field is disabled and cannot be edited.
  18. Validate the 'Pathway Name' field is disabled and cannot be edited.
  19. Validate the 'Primary Pathway' field is disabled and cannot be edited.
  20. Close the form.
  21. Validate the 'My Clients' list contains "Client A" without the pathway color.
Scenario 2: Validate the 'ClinicalPathwayDisenroll' - 'AddDisenrollment' web service
Specific Setup:
  • A pathway is defined in the 'Clinical Pathway Definition' form (Pathway A).
  • A client is enrolled in "Pathway A" (Client A).
  • Dictionary values must be defined for the "CWS" file - "(5010) Reason for Disenrollment" data element. This can be done in the 'Dictionary Update' form.
Steps
  1. Access SoapUI for the 'ClinicalPathwayDisenroll' - 'AddDisenrollment' 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 current date in the 'DisenrollmentDate' field.
  6. Enter "PathwayA" in the 'PathwayName' field.
  7. Enter the desired reason in the 'DisenrollmentReason' field.
  8. Enter "ClientA" in the 'ClientID' field.
  9. Click [Run].
  10. Validate the 'Confirmation' field contains: "Unique ID : CPE#####.###".
  11. Validate the 'Message' field contains: "Clinical Pathway Disenrollment web service has been filed successfully".
  12. Select "Client A" and access the 'Clinical Pathway Disenrollment' form.
  13. Select the disenrollment record filed in the previous steps and click [Edit].
  14. Validate the 'Date of Disenrollment' field is disabled and contains the current date.
  15. Validate the 'Pathway Name' field is disabled and contains "Pathway A".
  16. Validate the 'Reason For Disenrollment' field contains the reason entered in the previous steps.
  17. Close the form.
Scenario 3: Validate the 'ClinicalPathwayDisenroll' - 'UpdateDisenrollment' web service
Specific Setup:
  • A pathway is defined in the 'Clinical Pathway Definition' form (Pathway A).
  • A client has an existing disenrollment record for "Pathway A" (Client A).
  • Dictionary values must be defined for the "CWS" file - "(5010) Reason for Disenrollment" data element. This can be done in the 'Dictionary Update' form.
Steps
  1. Access SoapUI for the 'ClinicalPathwayDisenroll' - 'UpdateDisenrollment' 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 reason in the 'DisenrollmentReason' field.
  6. Enter "ClientA" in the 'ClientID' field.
  7. Enter the unique ID for the disenrollment in the 'disenrollHG' field.
  8. Click [Run].
  9. Validate the 'Confirmation' field contains: "Unique ID : CPD#####.###".
  10. Validate the 'Message' field contains: "Clinical Pathway Disenrollment web service has been filed successfully".
  11. Select "Client A" and access the 'Clinical Pathway Disenrollment' form.
  12. Validate the record updated in the previous steps is displayed and select it.
  13. Validate the 'Reason For Disenrollment' field contains the reason entered in the previous steps.
  14. Close the form.
Scenario 4: Validate the 'ClinicalPathwayDisenroll' - 'DeleteDisenrollment' web service
Specific Setup:
  • A pathway is defined in the 'Clinical Pathway Definition' form (Pathway A).
  • A client has an existing disenrollment record for "Pathway A" (Client A).
  • Dictionary values must be defined for the "CWS" file - "(5010) Reason for Disenrollment" data element. This can be done in the 'Dictionary Update' form.
Steps
  1. Access SoapUI for the 'ClinicalPathwayDisenroll' - 'DeleteDisenrollment' 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 "ClientA" in the 'ClientID' field.
  6. Enter the unique ID for the disenrollment in the 'disenrollHG' field.
  7. Click [Run].
  8. Validate the 'Message' field contains: "Clinical Pathway Disenrollment web service has been filed successfully".
  9. Select "Client A" and access the 'Clinical Pathway Disenrollment' form.
  10. Validate the deleted disenrollment is no longer displayed.
  11. Close the form.
Scenario 5: Validate the 'ClinicalPathwayDisenroll' - 'GetDictionaryItems' web service
Specific Setup:
  • One or more pathways must be defined in the 'Clinical Pathway Definition' form.
  • One or more values defined in the 'Reason For Disenrollment' field in the 'Clinical Pathway Disenrollment' form.
Steps
  1. Access SoapUI for the 'ClinicalPathwayDisenroll' - 'GetDictionaryItems' 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. Click [Run].
  6. Validate the 'GetDictionaryItemsResponse' field is populated with the defined dictionary values for the 'Reason For Disenrollment' field in the 'Clinical Pathway Disenrollment' form.
Topics
• Web Services • Clinical Pathway
Update 56 Summary | Details
Avatar CWS - 'Allergies/Hypersensitivities Reviewed'
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Launch OrderConnect
  • Allergies and Hypersensitivities
  • SQL Query/Reporting
  • SoapUI - Save Allergen Codes
Scenario 1: File an allergy in OrderConnect and validate it displays in the 'Allergies and Hypersensitivities' form
Specific Setup:
  • User with existing Provider login credentials in myAvatar
  • OrderConnect must be installed and configured to communicate with myAvatar and vice versa
  • User with a client enrolled in an existing episode
  • "Client A"
  • User has access to the 'Allergies and Hypersensitivities' form
  • User has access to the 'Registry Settings' form
  • 'Avatar CWS->CWS Utilities->Set System Defaults->CWS Allergies->->Enable Allergy Integration with OrderConnect' is set to "Y"
  • Avatar CWS->CWS Utilities->Set System Defaults->CWS Allergies->->Set 'Allergies/Hypersensitivities Reviewed' If Allergies Are Updated is set to "Y"
  • User has access to the 'SYSTEM.cw_client_allergies_review' SQL table in the 'User Definition' form
Steps
  1. Select "Client A" and access the 'Launch OrderConnect' form.
  2. Click [Launch OrderConnect].
  3. Verify the 'OrderConnect Chart' is displayed.
  4. Click [Allergies] and [Add Allergy].
  5. Verify the 'Allergy Search/Assign' dialog is displayed.
  6. Select any value in the 'Type' field.
  7. Enter any value in the 'Search Term' field.
  8. Click [Search].
  9. Select the desired value and click [Add].
  10. Verify the 'Add Allergy - Attributes' dialog is displayed.
  11. Select any value in the 'Reaction' field.
  12. Select any value in the 'Severity' field.
  13. Click [Add].
  14. Validate a "Message from webpage" message is displayed stating: Are you sure you want to add this Allergy to the patient record.
  15. Click [OK] and [Close Chart].
  16. Close the form.
  17. Select "Client A" and access the 'Allergies and Hypersensitivities' form.
  18. Validate the client header contains the reviewed status "Allergies Reviewed = Yes".
  19. Click [Update].
  20. Verify the 'Allergies and Hypersensitivities' table is displayed.
  21. Validate the 'Allergies and Hypersensitivities' table contains the Allergy filed through OrderConnect in the previous steps.
  22. Click [Close/Cancel] and [Submit].
  23. Access Crystal Reports or other SQL reporting tool.
  24. Create a report using the 'SYSTEM.cw_client_allergies_review' table.
  25. Validate a row is displayed for the review information for "Client A".
  26. Validate the 'PATID' field contains the Client ID for "Client A".
  27. Validate the 'reviewed_code' field contains "Y" for the saved allergy in the previous steps.
  28. Validate the 'reviewed_value' field contains "Yes" for the saved allergy in the previous steps.
  29. Close the report.
Scenario 2: Client Allergies Web Service - Save Allergen Codes
Specific Setup:
  • User with access to SoapUI
  • User with existing Provider login credentials in myAvatar
  • User with a client enrolled in an existing episode
  • "Client A"
  • User has access to the 'Allergies and Hypersensitivities' form
  • User has access to the 'Registry Settings' form
  • Avatar CWS->CWS Utilities->Set System Defaults->CWS Allergies->->Set 'Allergies/Hypersensitivities Reviewed' If Allergies Are Updated is set to "Y"
  • User has access to the 'SYSTEM.cw_client_allergies_review' SQL table in the 'User Definition' form
Steps
  1. Access SoapUI for the 'Client Allergies' - 'SaveAllergenCodes' 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 allergen reactant code in the 'allergenReactant' field.
  7. Enter the status code in the 'Status' field.
  8. Enter the date in the 'dateRecognized' field.
  9. Click [Run].
  10. Validate the request has sent successfully.
  11. Validate the 'Message' field contains the 'ClientAllergies web service has been filed successfully.' data on file.
  12. Select "Client A" and access the 'Allergies and Hypersensitivities' form.
  13. Validate the client header contains the reviewed status "Allergies Reviewed = Yes".
  14. Click [Update].
  15. Verify the 'Allergies and Hypersensitivities' table is displayed.
  16. Validate the 'Allergies and Hypersensitivities' table contains the Allergy filed through Web Service in the previous steps.
  17. Click [Close/Cancel] and [Submit].
  18. Access Crystal Reports or other SQL Reporting Tool.
  19. Create a report using the 'SYSTEM.cw_client_allergies_review' table.
  20. Validate a row is displayed for the review information for "Client A".
  21. Validate the 'PATID' field contains the Client ID for "Client A".
  22. Validate the 'reviewed_code' field contains "Y" for the saved allergy in the previous steps.
  23. Validate the 'reviewed_value' field contains "Yes" for the saved allergy in the previous steps.
  24. Close the report.
Topics
• OrderConnect • Allergies and Hypersensitivities • Allergy • Web Services
Update 59 Summary | Details
Chart Review - Treatment Plan
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Dynamic Form - Treatment Plan
  • Treatment Plan
  • Problem List
  • Chart Review
Scenario 1: Treatment Plan - Validate adding problems via the "Problems" list grid
Specific Setup:
  • [ClientA] is enrolled in an active episode.
Steps
  1. Open the Treatment Plan form.
  2. Select [ClientA].
  3. Populate any required fields on the main form.
  4. In the "Problems" grid select or add a problem [Problem1] with a status of "Active".
  5. Add or select a second problem [Problem2] with a different status, for example "Monitoring".
  6. Click [Launch Plan].
  7. Validate the treatment plan tree loads without a warning.
  8. Validate both problems are listed in the grid, as expected.
  9. Select [Problem1] and validate the "Status(Problem List) field equals "Active".
  10. Populate any other required fields in the "Problem" section.
  11. Select [Problem2] and validate the "Status(Problem List) field equals "Monitoring".
  12. Populate any other required fields in the "Problem" section.
  13. Click [Back to Plan Page].
  14. Submit the treatment plan.
  15. Return to the form and select the treatment plan just submitted.
  16. Click [Launch Plan].
  17. Validate all three problems are displayed.
  18. Click each problem and validate fields in the problem section are populated as expected.
  19. Click [Back to Plan Page].
  20. In the "Problems" grid, click "New Row".
  21. Enter the same problem entered for [Problem1].
  22. Validate a message displays blocking entry that states "Problem already exists", as expected.
  23. Select the new row just attempted and click [Delete] to remove it.
  24. Validate the row is deleted from the "Problems" grid.
  25. In the "Problems" grid, click "New Row" again.
  26. Enter a problem code other than the ones in [Problem1] or [Problem2].
  27. Validate the entry is accepted.
  28. Select a status of "Active" for the problem.
  29. Click [Launch Plan].
  30. Validate the treatment plan tree loads without a warning.
  31. Validate all three problems are listed in grid.
  32. Select the problem just added.
  33. Populate any other required fields in the "Problem" section.
  34. Click [Back to Plan Page].
  35. Submit the treatment plan.
  36. Return to the form and select the treatment plan just submitted.
  37. Click [Launch Plan].
  38. Validate all three problems are displayed and populated, as expected.
  39. Close the form.
Topics
• Treatment Plan • NX • Chart View
Update 67 Summary | Details
NX Console Widget Viewer - "Launch Report" button
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Console Widget Viewer
  • Client Health Maintenance
  • Results Entry
  • Review Results
Scenario 1: 'All Documents' widget - Validate 'Family Health History' records
Specific Setup:
  • A client must be enrolled in an existing episode (Client A).
  • 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).
  • This is for Avatar NX systems only.
Steps
  1. Select "Client A" and access the 'Family Health History' form.
  2. Validate "Add New" is selected in the 'Select Family Member' field.
  3. Select any value in the 'Relationship' field.
  4. Populate any desired fields.
  5. Select "Yes" in the 'Health Problems To Record' field.
  6. Click [Enter Health History].
  7. Click [New Row].
  8. Enter any value in the 'Problem' field.
  9. Populate any desired field.
  10. Click [Save], [Submit], and [No].
  11. Navigate to the 'All Documents' view.
  12. Select 'All Forms'.
  13. Select "Family Health History" in the 'Form Description' field.
  14. Validate the entry from the previous steps is present.
  15. Validate the 'Time' field displays.
  16. Select the entry and validate it displays in the 'Console Widget Viewer'.
  17. Validate the 'Launch Report' button exists.
  18. Click [Launch Report].
  19. Validate a report displays with the information filed in the previous steps.
  20. Close the report.
Scenario 2: 'All Documents' widget - Validate 'Client Health Maintenance' records
Specific Setup:
  • A client must be enrolled in an existing episode (Client A).
  • Must have a view configured with the 'All Documents' widget and 'Console Widget Viewer'.
  • This is for Avatar NX systems only.
Steps
  1. Access the 'Client Health Maintenance' form.
  2. Select "Client A".
  3. Click Immunization [Update] and [New Row]
  4. Double click the 'Refused' field.
  5. Select "Yes" in the 'Refused' field.
  6. Validate the 'Reason' field is required.
  7. Double click the 'Refused' field.
  8. Select "No" in the 'Refused' field.
  9. Validate the 'Reason' field is not required.
  10. Select "Historical Information - From Parent's Recall (04)" in the 'Source of Immunization' field.
  11. Complete all required fields.
  12. Click [Save] and [Submit].
  13. Access the 'All Documents' widget.
  14. Select "Client A".
  15. Select the 'All Forms' tab.
  16. Validate the 'Time' field displays.
  17. Select the 'Client Health Maintenance' entry.
  18. Validate the 'Console Widget Viewer' displays the immunization data filed in the previous steps.
  19. Validate the 'Source of Immunization' displays as expected.
  20. Validate the 'Launch Report' button exists.
  21. Click [Launch Report].
  22. Validate a report displays with the information filed in the previous steps.
  23. Close the report.
Scenario 3: 'All Documents' widget - Validate 'Review Results' records
Specific Setup:
  • A client must be enrolled in an existing episode (Client A).
  • 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).
  • This is for Avatar NX systems only.
Steps
  1. Select "Client A" and access the 'Results Entry' form.
  2. Select "Add" in the 'Add/Edit/Delete Result' field.
  3. Populate all required and desired fields.
  4. Click [File Header Info].
  5. Validate a message is displayed stating: "Header information filed."
  6. Click [OK].
  7. Select 'Result Details'.
  8. Select "Add" in the 'Add/Edit/Delete Result Detail' field.
  9. Validate the 'Header' field contains the data from the previous steps.
  10. Populate all required and desired fields.
  11. Click [File Detail Info].
  12. Validate a message is displayed stating: "Detail information filed."
  13. Click [OK] and [Exit Option].
  14. Access the 'Review Results' form.
  15. Select "Client A" in the 'Client ID' field.
  16. Select the entry from the previous steps in the 'Select Results' field.
  17. Validate the 'Results' field contains the data from the previous steps.
  18. Select any value in the 'Review Status' field.
  19. Click [Submit].
  20. Select "Client A" and access the 'All Documents' view.
  21. Select "All Episodes" in the 'Header Episode' field.
  22. Select 'All Forms'.
  23. Select "Review Results" in the 'Form Description' field.
  24. Validate the entry from the previous steps is present.
  25. Validate the 'Time' field displays.
  26. Select the entry and validate it displays in the 'Console Widget Viewer'.
  27. Validate the 'Launch Report' button exists.
  28. Click [Launch Report].
  29. Validate a report displays with the information filed in the previous steps.
  30. Close the report.
Topics
• Widgets • Console Widget • NX • Client Health Maintenance • Family Health History • Review Results