Avatar CWS 2022 Quarterly Release 2022.02 Acceptance Tests

Last updated
Save as PDF

Update 3 Summary \| Details Columbia Suicide Risk Assessment added to other forms Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following: Columbia Suicide Risk Assessment Product Final to Draft Override Dynamic Form Mental Status Assessment Move Selected Data (CWS) HomeView - My To Do's widget Scenario 1: Validate Product Final to Draft Override Steps Open a form such as the "Columbia Suicide Risk Assessment" form. Fill out all required fields and file the form in a "Final" "Status". Open the 'Product Final to Draft Override' form Set the 'Option' field to the desired form. Set the 'Entity Lookup' field to "Client A" Select any valid episode from the 'Episode Number' field Click [Select Row] Select any row Click [OK] Set the 'Override Reason' field to "Test" Click [Submit] Click [Yes] Verify the form files successfully. Open the assessment form opened previously in this scenario. Validate the assessment is back in a "Draft" status. Scenario 2: Move Selected Data [CWS] - Moving Data from one episode to another Steps Open a form such as the "Columbia Suicide Risk Assessment" form. Fill out all required fields and file the assessment either in a draft or finalized status. Open the "Move Selected Data" form. Move data from a client episode to another episode for the same client. Open the assessment form opened in step 1. Validate on the pre-display that the assessment was moved from one episode to another. Scenario 3: Move Selected Data [CWS] - Move Core Form from one entity to another Steps Open a form such as the "Columbia Suicide Risk Assessment" form. Fill out all required fields and file the assessment either in a draft or finalized status. Open the "Move Selected Data" form. Move data from a client to another. Open the assessment form opened in step 1. Validate on the pre-display that the assessment was moved from one client to another. Scenario 4: Columbia Suicide Risk Assessment - document routing Steps Open the "Document Routing Setup" form. Choose a form. Enable document routing for that form. Submit to file. Open the form that document routing is enabled for. Fill out all required fields and finalize the form. Sign the form. Open "Clinical Document Viewer". Locate the form that was finalized. Validate you can display and print the form. Columbia Suicide Risk Assessment Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following: Columbia Suicide Risk Assessment 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 Access the 'Columbia Suicide Risk Assessment' form. Select "Client A" and the desired episode. Set 'Assessment Date' to the current date. Select "Yes" in the 'Wish to be Dead: In Your Lifetime (When You Felt Most Suicidal)' field. Verify the 'In the Past Month?' field is required and select any value. Verify the 'If Yes, Describe field' is required and enter any value. Select "No" in the 'Non-Specific Active Suicidal Thoughts: In Your Lifetime (When You Felt Most Suicidal)' field. Verify the 'In the Past Month?' field is disabled. Verify the 'If Yes, Describe' field is disabled. Select any value in the 'Active Suicidal Ideation with Any Methods (Not Plan) Without Intent to Act: In Your Lifetime (When You Felt Most Suicidal)' field and validate the event logic works as expected. Populate any required and desired fields and validate the event logic works as expected. Select "Final" in the 'Status' field. Click [OK] on the 'Once set to 'Final', the data cannot be edited in the future' prompt. Select "Yes" in the 'Enroll in Clinical Pathway' field. Select desired pathway from the 'Pathway Name' field. Click [Submit]. Scenario 2: SQL table SYSTEM.Columbia_Assessment Specific Setup: A client must have the 'Columbia Suicide Risk Assessment' assessment filed (Client A). Steps Access Crystal Reports or other SQL Reporting tool. Select the CWS namespace. Create a report using the 'SYSTEM.Columbia_Assessment' table. Validate a row is displayed for the assessment on file for "Client A". Validate all filed information is displayed. Close the report.	Topics • Product Final to Draft Override • NX • myAvatar/myAvatar NX • Mental Status Assessment • Clinical Pathway
Update 4 Summary \| Details Treatment Plan - Document Routing Scenario 1: 'Client Treatment Plan' - validate the SYSTEM.cw_tx_client_plan table when document routing is enabled Specific Setup: An application with the 'Client Treatment Plan' form is used. Note: If using the new 'Treatment Plan' form, disregard these steps. Document routing is enabled for the 'Client Treatment Plan' form. A client is enrolled in an existing episode (Client A). Steps Select "Client A" and access the 'Client Treatment Plan' form. Populate all required and desired fields. Select "Final" in the 'Treatment Plan Status' field. Validate a "Confirm Document" window is displayed. Click [Accept] to accept the document. Access Crystal Reports or other SQL Reporting tool. Select the CWS namespace. Create a report using the 'SYSTEM.cw_tx_client_plan' table. Validate a row is displayed for the treatment plan submitted in the previous steps. Validate the 'PATID' field contains the ID for "Client A". Validate the 'document_routing_status' field contains "Final". Close the report. Scenario 2: Treatment Plan - 'Pending Approval' workflow Specific Setup: A client must be enrolled in an existing episode (Client A). The Wiley Libraries must be installed. A staff member must be associated to the logged in user. (Staff Member A) "Staff Member A" must be set up in the 'Notification Users' form. 'Treatment Plan' and "Staff Member A" must be set up in 'Required User List Management' form. The 'My To Do's' widget must be set up on a user's view. Steps Select "Client A" and access the 'Treatment Plan' form. Select the desired episode if present. Enter the desired date in the 'Plan Date' field. Select the desired value for the 'Plan Type' field. Populate any required and desired fields. Select "Draft" in the 'Treatment Plan Status' field. Click [Launch Plan]. Select the desired problem and drag it into the Treatment Plan. Populate all desired fields. Select a desired goal and drag it into the Treatment Plan. Populate all desired fields. Select a desired objective and drag it into the Treatment Plan. Populate all desired fields. Click [Return to Plan]. Validate a 'Plan Save' dialog stating: "Plan saved successfully." Click [OK]. Select "Pending Approval" in the 'Treatment Plan Status' field. Select "Staff Member A" in the 'Team Member To Notify' field. Click [Submit]. Navigate to the 'My To Do's' widget. Click [Approve To Do Item] for "Client A". Select "Yes" in the 'Approve To Do Item' field. Enter the desired value in the 'Comments' field. Click [Submit]. Click [Review To Do Item] for "Client A". Select "Reviewed" in the 'Set To Do Item to Reviewed' field. Click [Submit]. Validate the item is no longer present for "Client A". Scenario 3: Treatment Plan Copy- 'Pending Approval' workflow Specific Setup: A client must be enrolled in an existing episode (Client A). The Wiley Libraries must be installed. A staff member must be associated to the logged in user. (Staff Member A) "Staff Member A" must be set up in the 'Notification Users' form. A copy must exist of the 'Treatment Plan' form (Treatment Plan Copy). 'Treatment Plan Copy' and "Staff Member A" must be set up in 'Required User List Management' form. The 'My To Do's' widget must be set up on a user's view. Steps Select "Client A" and access the 'Treatment Plan Copy' form. Select the desired episode if present. Enter the desired date in the 'Plan Date' field. Select the desired value for the 'Plan Type' field. Populate any required and desired fields. Select "Draft" in the 'Treatment Plan Status' field. Click [Launch Plan]. Select the desired problem and drag it into the Treatment Plan. Populate all desired fields. Select a desired goal and drag it into the Treatment Plan. Populate all desired fields. Select a desired objective and drag it into the Treatment Plan. Populate all desired fields. Click [Return to Plan]. Validate a 'Plan Save' dialog stating: "Plan saved successfully." Click [OK]. Select "Pending Approval" in the 'Treatment Plan Status' field. Select "Staff Member A" in the 'Team Member To Notify' field. Click [Submit]. Navigate to the 'My To Do's' widget. Click [Approve To Do Item] for "Client A". Select "Yes" in the 'Approve To Do Item' field. Enter the desired value in the 'Comments' field. Click [Submit]. Click [Review To Do Item] for "Client A". Select "Reviewed" in the 'Set To Do Item to Reviewed' field. Click [Submit]. Validate the item is no longer present for "Client A". Scenario 4: Treatment Plan - Document Routing - "Allow Transcriber" functionality Specific Setup: A user has an associated staff member and has "Yes" selected in the 'Transcriber' field in 'User Definition (User A). A user has an associated staff member and is not a transcriber in 'User Definition' (User B). "User A" and "User B" have the 'My To Do's' widget on their HomeView. Document routing is enabled for 'Treatment Plan' and 'Allow Transcriber' is set to "Yes". Must be logged in as "User A". Please note: This is for myAvatar systems only. Steps Access the 'Treatment Plan' form. Select "Client A" in the 'Select Client' field. Enter the desired date in the 'Plan Date' field. Select any value in the 'Plan Type' field. Select "Draft" in the 'Treatment Plan Status' field. Click [Launch Plan]. Click [Add New Problem]. Populate any required and desired fields. Click [Return to Plan] and [OK]. Select "Final" in the 'Treatment Plan Status' field. Click [Submit]. Validate a "Select Author" dialog is displayed. Select the staff member associated to "User B" in the 'Select Author' field. Click [Submit] and verify successful filing. Log out. Log in as "User B". Navigate to the 'My To Do's' widget. Validate there is a To Do for "Client A". Click [Approve Document]. Validate the document is displayed in the new TIFF format. Validate the treatment plan has electronic signatures for the Transcriber (User A) & Author (User B). Click [Respond]. Enter the desired value in the 'Response for Transcriber' field and click [OK]. Validate the To Do is no longer displayed. Log in as "User A". Navigate to the 'My To Do's' widget. Validate there is a To Do for "Client A". Click [Review To Do Item]. Validate the 'To Do Information' field contains the response from "User B". Select "Reviewed" in the 'Set To Do Item to Reviewed' field. Click [Submit]. Validate the To Do is no longer displayed. Scenario 5: Treatment Plan - Validate the 'Enable Automatic Backup' registry setting - accept Specific Setup: The 'Avatar CWS->Treatment Plan->->->->Enable Automatic Backup' registry setting must be set to "Y". Document routing must be enable for the 'Treatment Plan' form through 'Document Routing Setup'. A client must be enrolled in an existing episode (Client A). Steps Select “Client A” and access the ‘Treatment Plan’ form. Set the ‘Plan Date’ field to the current date. Set the ‘Plan Name’ to any value. Select any value in the ‘Plan Type’ field. Select “Draft” in the ‘Treatment Plan Status’ field and click [Launch Plan]. Click [Add New Problem]. Set the ‘Problem Code’ field to any value. Select “Active” in the ‘Status (Problem List)’ field. Set the ‘Problem’ field to any value. Select any value in the ‘Status’ field. Click [Add New Goal]. Set the ‘Goal’ field to any value. Select any value in the ‘Status’ field. Click [Add New Objective]. Set the ‘Objective’ field to any value. Select any value in the ‘Status’ field. Click [Add New Intervention]. Set the ‘Intervention’ field to any value. Select any value in the ‘Status’ field. Click [Back to Plan Page]. Select "Final" in the 'Treatment Plan Status field and click [Submit]. Validate the treatment plan displays as expected. Click [Accept]. Enter the password associated with the logged in user and click [Verify]. Scenario 6: Treatment Plan Copy - Form Validations Specific Setup: Client must be enrolled in current episode (Client A). A copy of the Treatment Plan form exists (Treatment Plan Copy). "Treatment Plan Copy" must have document routing enabled. Steps Select "Client A" and access the 'Treatment Plan Copy' form. Select the desired value in the 'Plan Type' field. Select "Draft" in the 'Treatment Plan Status' field. Validate the 'Problems' label displays above the 'Problems' grid. Validate the 'Plan Participants' label displays above the 'Plan Participants' grid. Populate any desired fields. Click [Submit]. Select "Client A" and access the 'Treatment Plan Copy' form. Verify the plan filed in the previous steps. Click [Launch Plan] and [Add New Problem]. Populate required and desired fields. Click [Return to Plan] and [OK]. Click [Final - Treatment Plan Status] and [Submit]. Validate the 'Document Routing' screen is displayed and contains all populated treatment plan data in the new TIFF format. Click [Accept]. Enter the password associated with the logged in user. Click [Verify]. Scenario 7: Treatment Plan - File a Treatment Plan with Document Routing Specific Setup: Client must be admitted into an active episode with problems recorded in 'Problem List' form (Client A). The 'Treatment Plan' form must have document routing enabled. Must have the 'My To Do's' widget configured on a view. Steps Select "Client A" and access the 'Treatment Plan' form. Click [Add]. Enter "T" in the 'Plan Date' field. Validate the current date is displayed in the 'Plan Date' field. Click [Plan Date T]. Validate the current date is displayed in the 'Plan Date' field. Select any value in the 'Plan Type' field. Select any value from 'Problem List'. Click [New Row]. Select any value from the 'Role' field in the 'Participation' section. Select 'Staff ID' and enter "Staff Member A". Validate that the selected staff member's name displays in the 'Participant Name' field. Select any value from the 'Plan Author' field. Select any value from the 'Notification' field, Add multiple staff members as needed. Enter any value in the 'Strengths' field. Enter any value in the 'Weakness' field. Enter any value in the 'Discharge Planning' field. Select "Draft" in the 'Draft/Final' field. Click [Launch Plan]. Select the problem from the 'Tree View'. Select any value from the Status field. Click [Add New Goal]. Enter any value in the 'Goal' field. Select any value from the Status field. Click [Add New Objective]. Enter any value in the 'Objective' field. Select any value from the Status field. Click [Add New Intervention]. Enter any value in the 'Intervention' field. Select any value in the 'Status' field. Click [Return to Plan]. Select "Final" in the 'Draft/Final' field. Click [Submit]. Validate the 'Document Routing' screen is displayed and contains all populated treatment plan data in the new TIFF format. Click [Sign and Route]. Enter the password and press the 'Enter' key. Select the staff member associated with the logged in user in the 'Route Document To' field and click [Add]. Click [Submit] Access the 'My To Do's' widget. Click [My To Do's]. Validate the record for "Client A" and click [Review]. Validate the 'Document Preview' contains the treatment plan data in the new TIFF format. Click [Accept] and [Sign]. Enter the password and click [Verify]. Validate the record is no longer present. Close the 'To Do's'.	Topics • Treatment Plan • Document Routing
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) Set System Defaults (CWS) Dynamic Form - Admission - Client Admission (Outpatient) Financial Eligibility Managed Care Authorizations Client Charge Input Delete/Re-Assign To Do Items Dynamic Form - Edit Service Information - Select Service(s) to Edit 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 Open the 'Edit Service Information' form. Select the service created in 'Setup' that uses the allowable un. Enter a diagnosis code or a referring practitioner. Click [Submit]. 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: Note requirement To-do. 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 Open the 'Edit Service Information' form. Select the service with the units same as 'Maximum Units' defined in the 'Managed Care Authorization' form. Enter a diagnosis code or a referring practitioner. Click [Submit]. 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. 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 Select any client "Client A" and access the 'Medications Dispensed' form. Populate the required fields selecting any medication from the 'Medication Order Code' field. File the form. Validate the correct medication and order code are displayed. Access "Client A's" chart view. Click the 'Medications Dispensed' link. 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 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 Access SoapUI for the 'TreatmentPlan' - 'AddTreatmentPlan' web service. Enter the system code that will be used to log into Avatar in the 'SystemCode' field. Enter the user name that will be used to log into Avatar in the 'UserName' field. Enter the password that will be used to log into Avatar in the 'Password' field. Enter the desired date in the 'PlanDate' field. Enter the desired value in the 'PlanName' field. Enter the desired value in the 'PlanType' field. Enter the desired value in the 'TreatmentPlanStatus' field. Enter a valid problem code in the 'SNOMEDCode' field. Enter the corresponding problem description in the 'SNOMEDDesc' field. Enter the desired value in the 'ProblemCodeStatus' field. Enter the desired date in the 'DateOfOnset' field. Enter the desired staff ID in the 'StaffResponsible' field. Enter the desired date in the 'DateOpened' field. Enter the desired value in the 'Problem' field. Enter the desired value in the 'Status' field. Populate any other desired fields. Enter "STAFF" in the 'Role' field. Enter the desired staff ID in the 'StaffMember' field. Enter "57020" in the 'TreatmentPlanParticipants' - 'SSSignature' - 'FieldNumber' field. Enter a base64 encoded signature value in the 'TreatmentPlanParticipants' - 'SSSignature' - 'FieldValue' field. Enter "52143" in the 'SSSignature' - 'FieldNumber' field. Enter a base64 encoded signature value in the 'SSSignature' - 'FieldValue' field. Enter "Client A" in the 'ClientID' field. Enter "1" in the 'EpisodeNumber' field. Enter "CWS60000" in the 'OptionID' field. Click [Run]. Validate the 'Confirmation' field contains the unique ID for the treatment plan filed. Validate the 'Message' field contains: "Treatment Plan web service has been filed successfully". Select "Client A" and access "View A". Validate the 'Treatment Plan' widget contains the record added in the previous steps. Click [View]. Validate the 'Console Widget Viewer' displays all treatment plan data filed in the previous steps. Validate the 'SS Treatment Plan Client Sign 1' field contains the signature added in the previous steps. Validate the 'SS Treatment Plan Part Sign 1' field contains the signature added in the previous steps. 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 Access SoapUI for the 'TreatmentPlan' - 'EditTreatmentPlan' web service. Enter the system code that will be used to log into Avatar in the 'SystemCode' field. Enter the user name that will be used to log into Avatar in the 'UserName' field. Enter the password that will be used to log into Avatar in the 'Password' field. Enter the original date on file in the 'PlanDate' field. Enter the desired value in the 'PlanName' field. Enter the desired value in the 'PlanType' field. Enter the desired value in the 'TreatmentPlanStatus' field. Enter a valid problem code in the 'SNOMEDCode' field. Enter the corresponding problem description in the 'SNOMEDDesc' field. Enter the desired value in the 'ProblemCodeStatus' field. Enter the desired date in the 'DateOfOnset' field. Enter the desired staff ID in the 'StaffResponsible' field. Enter the desired date in the 'DateOpened' field. Enter the desired value in the 'Problem' field. Enter the desired value in the 'Status' field. Populate any other desired fields. Enter "STAFF" in the 'Role' field. Enter the desired staff ID in the 'StaffMember' field. Enter "57020" in the 'TreatmentPlanParticipants' - 'SSSignature' - 'FieldNumber' field. Enter a base64 encoded signature value in the 'TreatmentPlanParticipants' - 'SSSignature' - 'FieldValue' field. Enter "52143" in the 'SSSignature' - 'FieldNumber' field. Enter a base64 encoded signature value in the 'SSSignature' - 'FieldValue' field. Enter "Client A" in the 'ClientID' field. Enter "1" in the 'EpisodeNumber' field. Enter the unique ID for the existing 'Treatment Plan' record in the 'TPUniqueID' field. Click [Run]. Validate the 'Confirmation' field contains the unique ID for the treatment plan filed. Validate the 'Message' field contains: "Treatment Plan web service has been filed successfully". Select "Client A" and access "View A". Validate the 'Treatment Plan' widget contains the record updated in the previous steps. Click [View]. Validate the 'Console Widget Viewer' displays all treatment plan data updated in the previous steps. Validate the 'SS Treatment Plan Client Sign 1' field contains the signature updated in the previous steps. Validate the 'SS Treatment Plan Part Sign 1' field contains the signature updated in the previous steps. 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 Access SoapUI for the 'TreatmentPlan' - 'GetTreatmentPlan' web service. Enter the system code that will be used to log into Avatar in the 'SystemCode' field. Enter the user name that will be used to log into Avatar in the 'UserName' field. Enter the password that will be used to log into Avatar in the 'Password' field. Enter "Client A" in the 'ClientID' field. Enter the unique ID for the existing 'Treatment Plan' record in the 'TPUniqueID' field. Click [Run]. Validate the 'GetTreatmentPlanResponse' field contains the 'Treatment Plan' data on file. 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: A date field "TestingTheAllow" set to allow future dates ("No"). A date field "TestingTheError" set to an error dialog when future dates are selected ("Error"). A date field "TestingTheWarning" set to a warning ("Warning"). A client must be enrolled in an existing episode (Client A). Steps Select "Client A" and access the 'Progress Notes (Group and Individual)' form. Select desired episodes from the 'Request Episode(s)' field. Select 'New Service'. Select "Psychologist" from the 'Note Type' field. Set 'Notes Field' field to "test". Search for and select a valid practitioner in the 'Practitioner' field. Set the 'Date Of Service' field to a future date. Validate the 'Warning' Dialog is displayed and click [Cancel]. Set the 'Date Of Service' field to a date in the past. Validate the 'Date Of Service' field is set to a date in the past. Search for and select any desired code in the 'Service Charge Code'. Select "Draft" from the 'Draft/Final' field. Set the 'Date' field to the current date. Set the 'TestingTheWarning' field to a future date. Validate the 'Warning' Dialog is displayed and click [Cancel]. Set the 'TestingTheWarning' field to a future date. Validate the 'Warning' Dialog is displayed and click [OK]. Validate the 'TestingTheWarning' field contains a future date. Set the 'TestingTheWarning' field to the current date. Validate the 'TestingTheWarning' field is set to the current date. Set the 'TestingTheError' field to a date future date. Validate the 'Error' Dialog is displayed and click [OK]. Set the 'TestingTheError' field to the current date. Validate the 'TestingTheError' field is set to the current date. Set the 'TestingTheAllow' field to a future date. Validate the 'TestingTheAllow' field is set to a future date. Click [File Note]. 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 Select "Client A" and access the 'Vitals Entry' form. Select "Add" in the 'Update Vital Sign' field. Enter the current date in the 'Date' field. Enter "9:00 AM" in the 'Time' field. Populate all desired fields. Click [Submit] and [No] to exit the form. Select "Client A" and access the 'Significant Findings' form. Set the 'Significant Finding Date' field to a future date. Validate the 'Significant Finding Date' field is a future date. Set the "Allow Future Significant Finding Date" registry setting to "2". Log out of the application and log back in. Select "Client A" and access the 'Significant Findings' form. Set the 'Significant Finding Date' field to a future date. Validate the 'Warning' Dialog is displayed and click [Cancel]. Set the 'Significant Finding Date' field to the current date. Validate the 'Significant Finding Date' field is set to the current date. Enter the current time in the 'Significant Finding Time' field. Validate the 'Findings' field contains the vitals filed in the previous steps. Validate the 'Findings' field is sorted in descending chronological order. Close the form. Select "Client A" and access the 'Vitals Entry' form. Select "Add" in the 'Update Vital Sign' field. Enter the current date in the 'Date' field. Enter "9:00 AM" in the 'Time' field. Populate all desired fields. Click [Submit] and [No] to exit the form. Set the "Allow Future Significant Finding Date" registry setting to "3". Log out of the application and log back in. Select "Client A" and access the 'Significant Findings' form. Set the 'Significant Finding Date' field to a future date. Validate the 'Error' Dialog is displayed and click [OK]. Set the 'Significant Finding Date' field to the current date. Validate the 'Significant Finding Date' field is set to the current date. Set the 'Significant Finding Time' field to a future time. Validate the 'Error' Dialog is displayed and click [OK]. Enter the current time in the 'Significant Finding Time' field. Validate the 'Findings' field contains the vitals filed in the previous steps. Validate the 'Findings' field is sorted in descending chronological order. Close the form.	Topics • Progress Notes • Vitals
Update 24 Summary \| Details Zynx Library Import and Ordering of Results in the 'Treatment Plan' form. Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following: Treatment Plan Definition Scenario 1: Treatment Plan Definition - Export Library / Import Library Specific Setup: A treatment plan library must already exist in the system via the 'Treatment Plan Definition' form. Steps Access the ‘Treatment Plan Definition’ form. Select the ‘Export Library’ section. Click [Select Library]. Select any existing library and click [Return]. Click [Export File]. Navigate to the desired location and click save. Navigate to the location of the exported library. Validate that the exported library is displayed. Select the ‘Import Library’ section. Click [Select File]. Navigate to the location of the exported library and click [OK]. Click [Validate Import]. Validate a message displays stating “Library with this name exists. Importing the file will overwrite current library. Do you want to continue?” and click [Yes]. Validate the ‘Import Results’ field contains no errors. Click [Import File]. Validate a message displays stating “Library with this name already exists. Are you sure you want to delete the old library and import the file?” and click [Yes]. Validate a message displays stating “Library Import Complete” and click [OK]. Select the ‘Library Definition’ section. Click [Select Library]. Select the import library and click [Return]. Click [Print Library]. Validate the ‘Treatment Plan Library Report’ report contains all imported information for the library selected. Close the report and the form. Scenario 2: Treatment Plan Definition - Import existing Zynx Library Specific Setup: Two Treatment Plan libraries must already exist in the 'Treatment Plan Definition' form. (Library A & Library B) Must have an XML file that contains the two previously defined Treatment Plan libraries. Steps Access the ‘Treatment Plan Definition’ form. Select the 'Import Library' section. Select "FHIR Care Plan" from the 'File Format' field and click [Select File]. Select an XML file containing the existing libraries and click [Validate Import]. Validate the 'Import Library' dialog states: "One or more libraries from this file already exists in the system and will be overwritten. Do you want to overwrite all of them? Select Yes if so, select No to evaluate them on a case by case basis." Click [Yes]. Select the 'Library Definition' section and click [Select Library]. Validate the two existing libraries are displayed and click [Return]. Select the 'Import Library' section. Select "FHIR Care Plan" from the 'File Format' field and click [Select File]. Select an XML file containing the existing libraries and click [Validate Import]. Validate the 'Import Library' dialog states: "One or more libraries from this file already exists in the system and will be overwritten. Do you want to overwrite all of them? Select Yes if so, select No to evaluate them on a case by case basis." Click [No]. Validate the 'Import Library' dialog states: "The library "Library A" with the same external ID already exists. Are you sure you want to overwrite the old library and import the file?" and click [Yes]. Validate the 'Import Library' dialog states: "The library "Library B" with the same external ID already exists. Are you sure you want to overwrite the old library and import the file?" and click [No]. Select the 'Library Definition' section and click [Select Library]. Validate the two existing libraries are displayed and click [Return]. Treatment Plan - Search Results Scenario 1: Treatment Plan - Add a Problem, Goal, Objective, and Intervention 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). Scrolling Free Text fields must be enabled via the 'Site Specific Section Modeling' form for a 'Treatment Plan' form. (Strengths, Weaknesses, Discharge Planning) (Treatment Plan) Steps Select “Client A” and access the ‘Treatment Plan’ form. Set the ‘Plan Date’ field to the current date. Set the ‘Plan Name’ to any value. Select any value in the ‘Plan Type’ field. Set the 'Strengths' field to any value. Set the 'Weaknesses' field to any value. Set the 'Discharge Planning' field to any value. Select “Draft” in the ‘Treatment Plan Status’ field and click [Launch Plan]. Click [Add New Problem]. Set the ‘Problem Code’ field to any value. Select “Active” in the ‘Status (Problem List)’ field. Set the ‘Problem’ field to any value. Select any value in the ‘Status’ field. Click [Add New Goal]. Set the ‘Goal’ field to any value. Select any value in the ‘Status’ field. Click [Add New Objective]. Set the ‘Objective’ field to any value. Select any value in the ‘Status’ field. Click [Add New Intervention]. Set the ‘Intervention’ field to any value. Select any value in the ‘Status’ field. Click [Back to Plan Page]. Close the form. Select “Client A” and access the ‘Treatment Plan’ form. 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]. Validate the 'Strengths' field contains the value previously filed. Validate the 'Weaknesses' field contains the value previously filed. Validate the 'Discharge Planning' field contains the value previously filed. Click [Launch Plan]. Validate the ‘Tree view’ contains values for the problem, goal, objective, and intervention previously added. Click [Exit to Home View].	Topics • Treatment Plan • myAvatar/myAvatar NX • Treatment Plan Definition
Update 29 Summary \| Details Allergies and Hypersensitivities - No Known Food/Medications Allergies Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following: Allergies and Hypersensitivities Scenario 1: Allergies and Hypersensitivities - Client Header Specific Setup: The 'Set 'Allergies/Reactions Reviewed' Upon Updating Allergies' registry setting must be set to "N". Please log out of the application and log back in after completing the above configuration. A client must be admitted into an active episode who does not have any information filed in the 'Allergies and Hypersensitivities' form. (Client A) Steps Access the 'Allergies and Hypersensitivities' form for "Client A". Validate the 'Client Header' displays 'Allergies' contains "No Known Medication or Food Allergies". Validate that no value is selected in the 'Allergies/Hypersensitivities Reviewed' field. Click [Update] and [New Row]. Create a food allergy for "SHELLFISH (MDX-2891)" and click [Save]. Validate the 'Known Food Allergies' field is set to "Yes". Select "No" in the 'Known Medication Allergies' field. Validate that no value is selected in the 'Allergies/Hypersensitivities Reviewed' field. Select 'Yes' in the' Allergies/Hypersensitivities Reviewed' field and click [Submit]. Access the 'Allergies and Hypersensitivities' form for "Client A". Validate the 'Client Header' displays "Allergies (1) " with a red icon. Click [Update] and [New Row]. Set the 2nd 'Allergen/Reactant' field to "amoxicillin" and press Tab. Create a drug allergy "AMOXICILLIN (MDX-376) (RxNorm=723)" and click [Save]. Select 'Yes' in the 'Allergies/Hypersensitivities Reviewed' field and click [Submit]. Access the 'Allergies and Hypersensitivities' form for "Client A". Validate the 'Client Header' displays "Allergies (2)" with a red icon.	Topics • Allergies and Hypersensitivities
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 Select "Client A" and access the 'Clinical Pathway Enrollment' form. Verify the 'Date of Enrollment' field defaults to the current date. Select "Pathway A" in the 'Pathway Name' field. Select "Yes" for 'Primary Pathway'. Click [Submit] and [No]. Validate the 'My Clients' list contains "Client A" in the pathway color. Select "Client A" and access the 'Clinical Pathway Enrollment' form. Click [Add] to add an additional pathway. Select "Pathway A" in the 'Pathway Name' field. Validate a message is displayed stating: Client is already enrolled in the selected Clinical Pathway. Click [OK]. Select any new value in the 'Pathway Name' field. Select "Yes" for 'Primary Pathway'. Validate a message is displayed stating: Primary Pathway already exists. "Pathway A" is the current Primary Pathway. Click [OK]. Select "No" in the 'Primary Pathway' field. Click [Submit] and [No]. 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 Open "Clinical Pathway Enrollment" form for a test client. Select a record from the pre-display. Click [Edit]. Verify the "Date of Enrollment" field is displayed and disabled. Verify the "Pathway Name" field is displayed and disabled. The only field that can be edited is the "Primary Pathway" field. Select "Yes" in the "Primary Pathway" field. Click [Submit]. 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 Select "Client A" and access the 'Clinical Pathway Enrollment' form. Verify the 'Date of Enrollment' field defaults to the current date. Select "Pathway A" in the 'Pathway Name' field. Select "Yes" for 'Primary Pathway'. Click [Submit] and [No]. Validate the 'My Clients' list contains "Client A" in the pathway color. Select "Client A" and access the 'Clinical Pathway Enrollment' form. Select the existing enrollment in the pre-display. Click [Delete]. Validate a message is displayed stating: Are you sure you want to delete this item? Click [Yes]. Validate a message is displayed stating: Enrollment was successfully deleted. Click [OK] and exit the form. 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 Access SoapUI for the 'ClinicalPathwayEnroll' - 'AddEnrollment' web service. Enter the system code that will be used to log into Avatar in the 'SystemCode' field. Enter the user name that will be used to log into Avatar in the 'UserName' field. Enter the password that will be used to log into Avatar in the 'Password' field. Enter the current date in the 'EnrollmentDate' field. Enter "PathwayA" in the 'PathwayName' field. Enter "Y" in the 'PrimaryPathway' field. Enter "ClientA" in the 'ClientID' field. Click [Run]. Validate the 'Confirmation' field contains: "Unique ID : CPE#####.###". Validate the 'Message' field contains: "Clinical Pathway Enrollment web service has been filed successfully". Select "Client A" from the 'My Clients' list. Validate an alert is displayed stating: "Selected Client is Enrolled in the following Clinical Pathways: PathwayA". Click [Yes] to proceed. Access the 'Clinical Pathway Enrollment' form. Validate the record added in the previous steps is displayed and select it. Validate the 'Client Header' contains "Client A" in the pathway color and contains the icon associated with "PathwayA". Validate the 'Date of Enrollment' field contains the current date. Validate the 'Pathway Name' field contains "PathwayA". Validate "Yes" is selected in the 'Primary Pathway' field. 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 Access SoapUI for the 'ClinicalPathwayEnroll' - 'UpdateEnrollment' web service. Enter the system code that will be used to log into Avatar in the 'SystemCode' field. Enter the user name that will be used to log into Avatar in the 'UserName' field. Enter the password that will be used to log into Avatar in the 'Password' field. Enter "N" in the 'PrimaryPathway' field. Enter "ClientA" in the 'ClientID' field. Enter the unique ID for the enrollment in the 'enrollHG' field. Click [Run]. Validate the 'Confirmation' field contains: "Unique ID : CPE#####.###". Validate the 'Message' field contains: "Clinical Pathway Enrollment web service has been filed successfully". Select "Client A" from the 'My Clients' list. Validate an alert is displayed stating: "Selected Client is Enrolled in the following Clinical Pathways: PathwayA". Click [Yes] to proceed. Access the 'Clinical Pathway Enrollment' form. Validate the record updated in the previous steps is displayed and select it. Validate the 'Primary Pathway' field is set to "No". 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 Access SoapUI for the 'ClinicalPathwayEnroll' - 'DeleteEnrollment' web service. Enter the system code that will be used to log into Avatar in the 'SystemCode' field. Enter the user name that will be used to log into Avatar in the 'UserName' field. Enter the password that will be used to log into Avatar in the 'Password' field. Enter "ClientA" in the 'ClientID' field. Enter the unique ID for the enrollment in the 'enrollHG' field. Click [Run]. Validate the 'Message' field contains: "Clinical Pathway Enrollment web service has been filed successfully". Select "Client A" and access the 'Clinical Pathway Enrollment' form. Validate the enrollment deleted is no longer displayed. 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 Access SoapUI for the 'ClinicalPathwayEnroll' - 'GetDictionaryItems' web service. Enter the system code that will be used to log into Avatar in the 'SystemCode' field. Enter the user name that will be used to log into Avatar in the 'UserName' field. Enter the password that will be used to log into Avatar in the 'Password' field. Click [Run]. 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 Select "Client A" and access the 'Clinical Pathway Enrollment' form. Verify the 'Date of Enrollment' field defaults to the current date. Select "Pathway A" in the 'Pathway Name' field. Select "Yes" for 'Primary Pathway'. Click [Submit] and [No]. Validate the 'My Clients' list contains "Client A" in the pathway color. Select "Client A" and access the 'Clinical Pathway Disenrollment' form. Validate the 'Date of Disenrollment' field defaults the current date. Select "Pathway A" in the 'Pathway Name' field. Select desired value in the 'Reason for Disenrollment' field. Click [Submit] and [No]. Select "Client A" and access the 'Clinical Pathway Enrollment' form. Validate the Pre-Display contains the prior enrollment record in "Pathway A" and the 'Disenrollment Date' field contains the date of disenrollment. Click [Edit]. Validate a "Clinical Pathway Enrollment" message is displayed stating: Disenrollment exists. Enrollment can only be viewed. Click [OK]. Validate the 'Date of Enrollment' field is disabled and cannot be edited. Validate the 'Pathway Name' field is disabled and cannot be edited. Validate the 'Primary Pathway' field is disabled and cannot be edited. Close the form. 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 Access SoapUI for the 'ClinicalPathwayDisenroll' - 'AddDisenrollment' web service. Enter the system code that will be used to log into Avatar in the 'SystemCode' field. Enter the user name that will be used to log into Avatar in the 'UserName' field. Enter the password that will be used to log into Avatar in the 'Password' field. Enter the current date in the 'DisenrollmentDate' field. Enter "PathwayA" in the 'PathwayName' field. Enter the desired reason in the 'DisenrollmentReason' field. Enter "ClientA" in the 'ClientID' field. Click [Run]. Validate the 'Confirmation' field contains: "Unique ID : CPE#####.###". Validate the 'Message' field contains: "Clinical Pathway Disenrollment web service has been filed successfully". Select "Client A" and access the 'Clinical Pathway Disenrollment' form. Select the disenrollment record filed in the previous steps and click [Edit]. Validate the 'Date of Disenrollment' field is disabled and contains the current date. Validate the 'Pathway Name' field is disabled and contains "Pathway A". Validate the 'Reason For Disenrollment' field contains the reason entered in the previous steps. 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 Access SoapUI for the 'ClinicalPathwayDisenroll' - 'UpdateDisenrollment' web service. Enter the system code that will be used to log into Avatar in the 'SystemCode' field. Enter the user name that will be used to log into Avatar in the 'UserName' field. Enter the password that will be used to log into Avatar in the 'Password' field. Enter the desired reason in the 'DisenrollmentReason' field. Enter "ClientA" in the 'ClientID' field. Enter the unique ID for the disenrollment in the 'disenrollHG' field. Click [Run]. Validate the 'Confirmation' field contains: "Unique ID : CPD#####.###". Validate the 'Message' field contains: "Clinical Pathway Disenrollment web service has been filed successfully". Select "Client A" and access the 'Clinical Pathway Disenrollment' form. Validate the record updated in the previous steps is displayed and select it. Validate the 'Reason For Disenrollment' field contains the reason entered in the previous steps. 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 Access SoapUI for the 'ClinicalPathwayDisenroll' - 'DeleteDisenrollment' web service. Enter the system code that will be used to log into Avatar in the 'SystemCode' field. Enter the user name that will be used to log into Avatar in the 'UserName' field. Enter the password that will be used to log into Avatar in the 'Password' field. Enter "ClientA" in the 'ClientID' field. Enter the unique ID for the disenrollment in the 'disenrollHG' field. Click [Run]. Validate the 'Message' field contains: "Clinical Pathway Disenrollment web service has been filed successfully". Select "Client A" and access the 'Clinical Pathway Disenrollment' form. Validate the deleted disenrollment is no longer displayed. 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 Access SoapUI for the 'ClinicalPathwayDisenroll' - 'GetDictionaryItems' web service. Enter the system code that will be used to log into Avatar in the 'SystemCode' field. Enter the user name that will be used to log into Avatar in the 'UserName' field. Enter the password that will be used to log into Avatar in the 'Password' field. Click [Run]. 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 39 Summary \| Details Review Results - View Image Scenario 1: Results Import - Results View Specific Setup: A Results file must be imported for "Client A" with an associated lab order which has an image. The logged in user's 'HomeView' must contain the following widgets: Results by Caseload My To Do's Lab Results Radiology Results A client must have an active episode. (Client A) “Client A” must have a ‘Date of Birth’, ‘Sex’ and address on file in the ‘Update Client Data’ form, as well as information filed in the ‘Allergies and Hypersensitivities’ form, ‘Diagnosis’ form, and in the ‘Height’ and ‘Weight’ fields in the ‘Vitals Entry’ form. Steps Select "Client A" and access the Order Entry Console. Create a 'LAB' order and take note of the order number. Access the 'Results Import' form and Import the 'Results' file. Select "Client A". Select the 'LAB' result from the 'Radiology Results' widget Click [Review Results]. Validate the 'Results' field contains "observation ID: (PDFReport1) LAB (PDF Report1)". Click [View Images]. Validate a PDF is displayed with client's lab results. Click [Close All Documents and Exit]. Select "Client A". Select the 'LAB' result from the 'Results by Caseload' widget. Click [View Result]. Validate the 'Results' field contains "observation ID: (PDFReport1) LAB (PDF Report1)". Click [View Images]. Validate a PDF is displayed with client's lab results. Click [Close All Documents and Exit]. Select "Client A". Validate the 'Lab Results' widget contains the 'LAB' results. Access the Order Entry Console. Select 'Last Activity' for the client's 'LAB' order. Select 'Results Received' for the lab results. Validate the 'Results' field contains "observation ID: (PDFReport1) LAB (PDF Report1)". Click [View Images]. Validate a PDF is displayed with client's lab results. Click [Close All Documents and Exit]. Select "Client A". Access the 'My To Do's' widget. Select 'Review Results' for "Client A". Validate the 'Results' field contains "observation ID: (PDFReport1) LAB (PDF Report1)". Click [View Images]. Validate a PDF is displayed with client's lab results. Click [Close All Documents and Exit].	Topics • Order Entry Console
Update 40 Summary \| Details Allergies and Hypersensitivities - Date Recognized Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following: Allergies and Hypersensitivities Scenario 1: Allergies and Hypersensitivities - Require 'Date Recognized' column. Specific Setup: A client must have an active episode. (Client A) Steps Access the 'Registry Settings' form. Search for "Require 'Date Recognized" in the 'Limit Registry Settings to the Following Search Criteria' field. Click [View Registry Settings]. Validate the 'Registry Setting' field contains "Avatar CWS->CWS Utilities->Set System Defaults->CWS Allergies->->Require 'Date Recognized' column". Validate the 'Registry Setting Details' field contains the following information "When this setting has a value of "Y" the 'Date Recognized' column will be required when adding or modifying records within the 'Allergies and Hypersensitivities' form grid." Validate the 'Registry Setting Value' field contains a "Y". Close the form. Select "Client A" and access the 'Allergies and Hypersensitivities' form. Click [Update]. Validate the 'Allergen/Reactant' dialog is displayed. Double click the 'Allergen/Reactant' cell and search for and select "PENICILLIN MDX-39913". Validate the 'Date Recognized' field is required. Double click the 'Status' cell. Select "Confirmed" and click [Select]. Double click the 'Reactions' cell and select any values and click [OK]. Double click the 'Reaction Severity' cell and select any values and click [Select]. Validate that the [Save] is disabled. Double click the 'Date Recognized' cell, select the current date and press Enter. Validate that [Save] is enabled and click it. Validate the 'Known Medication Allergies' field is disabled and has "Yes" selected. Select "No" in the 'Known Food Allergies' field and click [Submit]. Access the 'Registry Settings' form. Search for "Require 'Date Recognized" in the 'Limit Registry Settings to the Following Search Criteria' field. Click [View Registry Settings]. Validate the 'Registry Setting' field contains "Avatar CWS->CWS Utilities->Set System Defaults->CWS Allergies->->Require 'Date Recognized' column". Validate the 'Registry Setting Details' field contains the following information "When this setting has a value of "Y" the 'Date Recognized' column will be required when adding or modifying records within the 'Allergies and Hypersensitivities' form grid." Validate the 'Registry Setting Value' field contains a "N". Close the form. Log out of the application and log back in. Select "Client A" and access the 'Allergies and Hypersensitivities' form. Click [Update]. Validate the 'Allergen/Reactant' dialog is displayed. Double click the 'Allergen/Reactant' cell and search for and select "Shellfish". Validate the 'Date Recognized' field is not required. Double click the 'Status' cell. Select "Confirmed" and click [Select]. Double click the 'Reactions' cell and select any values and click [OK]. Double click the 'Reaction Severity' cell and select any values and click [Select]. Validate that the [Save] is disabled. Double click the 'Date Recognized' cell, select the current date and press Enter. Validate that [Save] is enabled and click it. Validate the 'Known Medication Allergies' field is disabled and has "Yes" selected. Validate the 'Known Food Allergies' field is disabled and has "Yes" selected and click [Submit].	Topics • Allergies and Hypersensitivities
Update 41 Summary \| Details eMAR - Blood Pressure Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following: Vitals Entry eMAR widget Scenario 1: eMAR - 'Time Window for selection of previously entered Blood Pressure readings in eMAR' set to "Y". Specific Setup: Registry setting "Avatar eMAR->General->Settings->->->Time Window for selection of previously entered Blood Glucose readings in eMAR" must be set to "120" Registry setting "Avatar eMAR->General->Settings->->->Time Window for selection of previously entered Blood Pressure readings in eMAR" must be set to "120" A client must have an active episode. (Client A) Steps Access the 'Order Code Setup' form. Select 'Edit Existing Code' from the 'Add/Edit Order Code' field. Search for and select "JEVITY 1.5 CAL LIQUID ORAL " in the 'Existing Order Code. Add the following vitals to the 'Additional Data Elements To Include In Avatar eMAR (Administration)' and 'Additional Data Elements To Include In Avatar eMAR (Results)' 'Additional Data Elements To Require In Avatar eMAR (Administration)' and 'Additional Data Elements To Require In Avatar eMAR (Results)' fields: Blood Glucose Blood Pressure Heart Rate Oxygen Click [Submit]. Validate a message is displayed "Do you wish to return to form?" and click [No]. Access the 'Vitals Entry' form for "Client A". Set the 'Date' to the current date. Set the 'Time' field to "03:30 PM". Set the 'Systolic' field to "120". Set the 'Diastolic' field to "80". Select "Sitting" from the 'Position' field. Set the 'Blood Glucose' field to "82". Set the '(ft in)' field to "5 8". Set the '(lbs)' field to "175" and click [Submit]. Validate a message is displayed "Do you wish to return to form?" and click [Yes]. Set the 'Date' to the current date. Set the 'Time' field to "03:45 PM". Set the 'Systolic' field to "110". Set the 'Diastolic' field to "77". Select "Lying" from the 'Position' field. Set the 'Blood Glucose' field to "77". Click [Submit]. Validate a message is displayed "Do you wish to return to form?" and click [Yes]. Set the 'Date' to the current date. Set the 'Time' field to "03:55 PM". Set the 'Systolic' field to "100". Set the 'Diastolic' field to "77". Select "Standing" from the 'Position' field. Set the 'Blood Glucose' field to "77". Click [Submit]. Validate a message is displayed "Do you wish to return to form?" and click [No]. Access the Order Entry Console. Search for and select "JEVITY 1.5 CAL LIQUID ORAL" from the 'New Order' field. Set the 'Dose' field to "400". Select "mL" from the 'Dose Unit' field. Select "3 TIMES A DAY" from the 'Frequency' field. Set the 'Duration' field to "30" and click [Days]. Click [Add to Scratchpad] and [Sign]. Validate the 'Order grid' contains an order for "JEVITY 1.5 CAL ORAL LIQUID400 mL, 3 TIMES A DAY". Click the eMAR tab. Validate the 'Order Description' field is equal to "JEVITY 1.5 CAL ORAL LIQUID ↳Give: 400 mL 3 TIMES A DAY". Click the 'Click here to provide override reason' item. Select "Wristband is wet" from the 'Please provide a reason for not scanning the client wristband' field and click [OK]. Double click a cell under the current date. Set the 'Med ID' cell to the med id for the order (70074-0573-33). Validate the 'Qty' cell is equal to "400". Validate the 'Unit' cell is equal to "mL". Select "Nurse Administered" from the 'Administration Event' field. Populate any warnings if they exist. Click the 'Additional Data (Administration)' tab. Validate all entries from the 'Vitals Entry' form display in the dropdown fields for 'Blood Glucose' and 'Blood Pressure'. Select the "82" entry from the 'Blood Glucose (mg/dL)' field. Select the "120/80" entry in the 'Blood Pressure (Systolic/Diastolic -mm/Hg)' field. Set the Heart Rate (bpm) field to "70". Set the Oxygen Saturation (%) field to "98". Click the 'Accept administration information entered' checkbox and click [OK]. Validate the cell selected displays "400 mL" and the current time. Double click on the cell previously administered. Set the 'Result' field to "Testing". Click the 'Additional Data (Administration)' tab. Validate the 'Blood Glucose' field is equal to "82". Validate the 'Blood Pressure' field is equal to "120/80". Validate the 'Heart Rate (bpm)' field is equal to "70". Validate the 'Oxygen Saturation (%)' field is equal to "98". Click the 'Add'l Data (Results)' tab. Select the "110/77" entry from the 'Blood Glucose (mg/dL)' field. Select the "77" entry from the 'Blood Pressure (Systolic/Diastolic -mm/Hg)' field. Set the 'Heart Rate (bpm)' field to "70". Set the 'Oxygen Saturation (%)' field to "95". Click the 'Accept administration information entered' checkbox and click [OK].	Topics • Avatar eMAR
Update 45 Summary \| Details Default value for 'Status' field in Allergies and Hypersensitivities form. Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following: Allergies and Hypersensitivities Scenario 1: Allergies and Hypersensitivities - Default value for 'Status' Specific Setup: A client must have an active episode. (Client A) Steps Select "Client A" and access the 'Allergies and Hypersensitivities' form. Click [Update] and [New Row]. Search for and select "ADVIL (MDX-4974) (RxNorm=153010)" from the 'Allergen/Reactant' field. Set the 'Date Recognized' field the current date. Validate the 'Status' field does not contain a value. Search for and select "Confirmed (C)" from the 'Status' field and click [Save]. Validate "Yes" is selected from the 'Known Medication Allergies' field. Select "No" from the 'Known Food Allergies' field and click [Submit]. Access the Order Entry Console. Search for and select "ADVIL 200 MG TABLET ORAL" from the 'New Order' field. Validate the 'At least one warning has been found with this order code.' warning is displayed. Click the warning and validate a message is displayed that states: "A history of hypersensitivity to the following substance has been noted for this patient: ADVIL." Click [Close] and exit the Order Entry Console. Access the 'Registry Settings' form. Search for and select the registry setting: "Avatar CWS->CWS Utilities->Set System Defaults->CWS Allergies->->Default value for 'Status' in 'Allergies and Hypersensitivities' form". Set the 'Registry Setting Value' field to "C" and click [Submit]. Validate a message is displayed that states: "Filing Results" and click [OK]. Validate a message is displayed that states: "Registry Settings has completed. Do you wish to return to form?" and click [No]. Log out and log back into the application. Access the 'Allergies and Hypersensitivities' form. Click [Update] and [New Row]. Search for and select "PENICILLIN (MDX-39913)" from the second 'Allergen/Reactant' field. Set the second 'Date Recognized' field the current date. Validate the second 'Status' field contains "Confirmed (C)". Click [Save] and [Submit]. Access the Order Entry Console. Search for and select "PENICILLIN G POTASSIUM 20 MILLION UNITS POWDER FOR SOLUTION INJECTION" from the 'New Order' field. Validate the 'At least one warning has been found with this order code.' warning is displayed. Click the warning and validate a message is displayed that states: "Drug: PENICILLIN G POTASSIUM 20 MILLION UNITS INJECTION POWDER FOR SOLUTION and Allergen: PENICILLIN Description: BETA-LACTAMS (CARBAPENEMS, CEPHALOSPORINS, CLAVULANIC ACID, MONOBACTAMS, PENICILLINS, SULBACTAM, TAZOBACTAM, AND VABORBACTAM) Screening Message: CROSS-REACTIVITY BETWEEN BETA-LACTAMS (CARBAPENEMS, CEPHALOSPORINS, CLAVULANIC ACID, MONOBACTAMS, PENICILLINS, SULBACTAM, TAZOBACTAM, AND VABORBACTAM) MAY OCCUR. AZTREONAM MAY BE AN APPROPRIATE PENICILLIN ALTERNATIVE IN SOME PENICILLIN-ALLERGIC PATIENTS BUT SHOULD BE USED WITH CAUTION AS CROSS-REACTIVITY WITH PENICILLINS, ESPECIALLY CEFTAZIDIME HAS BEEN REPORTED. There was an experienced reaction of (Reactions Not Specified)." Click [Close] and exit the Order Entry Console. Scenario 2: Allergies and Hypersensitivities - Add/Edit Allergies Specific Setup: A client must have an active episode. (Client A) The user has the 'Allergies and Hypersensitivities' form available on the Chart View. Steps Select "Client A" and access the 'Allergies and Hypersensitivities' form. Select "No" in the 'Known Medication Allergies' field. Select "No" in the 'Known Food Allergies' field. Click [Update]. Validate the 'Allergies and Hypersensitivities' grid is displayed. Click [New Row]. Select any value in the 'Allergen/Reactant' field. Enter the desired date in the 'Date Recognized' field. Select "Active" in the 'Status' field. Select any value in the 'Reaction Severity' field. Click [Save] and [Submit]. Access the Chart View for "Client A". Select the 'Allergies and Hypersensitivities' form from the left-hand side. Validate the allergy added in the previous steps is displayed with a status of "Active". Close the chart. Select "Client A" and access the 'Allergies and Hypersensitivities' form. Click [Update]. Select the allergy added in the previous steps and click [Delete Row]. Validate a "Confirm" message is displayed stating: Are you sure you want to delete these rows? Click [Yes]. Validate an "Error" message is displayed stating: Allergies that have been saved previously cannot be deleted. Please update the 'Status' as appropriate. Click [OK]. Validate the 'Allergies and Hypersensitivities' grid still contains the allergy filed in the previous steps. Select "Inactive" in the 'Status' field. Click [Save] and [Submit]. Access the Chart View for "Client A". Select the 'Allergies and Hypersensitivities' form from the left-hand side. Validate the allergy added in the previous steps is displayed with a status of "Inactive". Close the chart. Select "Client A" and access the 'Allergies and Hypersensitivities' form. Click [Update]. Validate the 'Allergies and Hypersensitivities' grid is displayed. Click [New Row]. Select any value in the 'Allergen/Reactant' field. Enter the desired date in the 'Date Recognized' field. Select "Active" in the 'Status' field. Select any value in the 'Reaction Severity' field. Select the new allergy record and click [Delete Row]. Validate a "Confirm" message is displayed stating: Are you sure you want to delete these rows? Click [Yes]. Validate the 'Allergies and Hypersensitivities' grid does not contain the second allergy record. Click [Close/Cancel] and close the form.	Topics • Order Entry Console • Allergies and Hypersensitivities • NX • myAvatar/myAvatar NX
Update 50 Summary \| Details 'Treatment Plan' field 'Status (Problem List)' is updated to default a specific value. Scenario 1: Treatment Plan - Problems - Status (Problem List) default Specific Setup: Registry Setting 'Default value for 'Status (Problem List)' is set to 'Yes'. Steps Open the 'Treatment Plan' form for any client. Set the 'Plan Date' field to the current date. Set the Plan Type field to any value. Select "Draft" from the 'Treatment Plan Status' field. Click [Launch Plan]. Click [Add New Problem]. Set the 'Problem Code' field to any problem code. Set the 'Problem' field to any text. Validate the 'Status (Problem List)' field is defaulted to the value as set in the Registry Setting 'Default value for 'Status (Problem List)'. Set the 'Status' field to any value. Complete any required fields as needed. Click [Back to Plan Page]. Click [Launch Plan]. Validate the Status (Problem List)' field is populated with the default value. Click [Back to Plan Page]. Click [Submit]. Validate the form submits successfully.	Topics • Registry Settings • Treatment Plan - Status (Problem List)
Update 52 Summary \| Details Avatar CWS - Allergen Search Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following: Allergies and Hypersensitivities Scenario 1: Validate the 'ClientAllergies' - 'SearchAllergenCodes' web service Specific Setup: CareFabric is configured and enabled. A client must have an active episode. (Client A) The 'Enable Allergen Search Web Service' registry setting is enabled. Steps Access SoapUI for the 'Client Allergies' - 'SearchAllergenCodes' web service. Enter the system code that will be used to log into Avatar in the 'SystemCode' field. Enter the user name that will be used to log into Avatar in the 'UserName' field. Enter the password that will be used to log into Avatar in the 'Password' field. Enter the desired search value in the 'SearchTerm' field. Click [Run]. Validate the 'SearchAllergenCodesResponse' field contains allergens based on the 'SearchTerm' entered. Scenario 2: Validate the 'Enable Allergen Search Web Service' registry setting Specific Setup: CareFabric is configured and enabled. The 'Enable Allergen Search Web Service' registry setting is enabled. A client must have an active episode. (Client A) Steps Access the 'Registry Settings' form. Enter "Enable Allergen Search Web Service" in the 'Limit Registry Settings to the Following Search Criteria' field. Click [View Registry Settings]. Select "Enable Allergen Search Web Service" and click [OK]. Validate the 'Registry Setting' field contains "Avatar CWS->CWS Utilities->Set System Defaults->CWS Allergies->->Enable Allergen Search Web Service". Validate the 'Registry Setting Detail' field contains: Use this registry setting to enable the Allergen Code search to derive its content via a web service that accesses Netsmart's cloud-based Service Oriented Architecture (SOA). Netsmart's cloud-based content provides Micromedex-derived Allergen Codes, and is supplemented with additional SNOMED-derived Allergen Codes as needed. Please note: This registry setting only allows for the value 'Y'. Please note: This is a onetime setup process. Once this registry setting is set to 'Y' it will enable the Allergy WebService Search and the Registry Setting value cannot be changed anymore. Please note: If the 'Avatar CareFabric' module is loaded and enabled (requires Avatar CareFabric 2022 Update #35) then the SDK based services will be used and it will no longer require the 'CareFabric Configuration' form to be submitted. Validate the 'Registry Setting Value' is set to "Y". Enter "Allergen Search Web Service URL" in the 'Limit Registry Settings to the Following Search Criteria' field. Click [View Registry Settings]. Select "Allergen Search Web Service URL" and click [OK]. Validate the 'Registry Setting' field contains "Avatar CWS->CWS Utilities->Set System Defaults->CWS Allergies->->Allergen Search Web Service URL". Validate the 'Registry Setting Detail' field contains: Enter the URL where the allergen search web service resides. If entered, the allergen search process will use this and it will no longer require the 'CareFabric Configuration' form to be submitted. Please note: This registry setting only takes effect when the 'Enable Allergen Search Web Service' is enabled. Please note: If the 'Avatar CareFabric' module is loaded and enabled (requires Avatar CareFabric 2022 Update #35) then the SDK based services will be used and this registry setting will be disregarded. Please contact your Netsmart representative for more information on this and other available web services. Please note: the 'Allergen Search Web Service URL' registry setting will now only be required when the 'Enable Allergen Search Web Service' registry setting is enabled and CareFabric is NOT enabled. Close the form. Select "Client A" and access the 'Allergies and Hypersensitivities' form. Select "No" in the 'Known Medication Allergies' field. Select "No" in the 'Known Food Allergies' field. Click [Update]. Validate the 'Allergies and Hypersensitivities' grid is displayed. Click [New Row]. Search for any value in the 'Allergen/Reactant' field. Validate the allergen search returns successfully and select the desired value. Populate all other required and desired fields. Click [Save] and [Submit]. Scenario 3: 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 Select "Client A" and access the 'Launch OrderConnect' form. Click [Launch OrderConnect]. Verify the 'OrderConnect Chart' is displayed. Click [Allergies] and [Add Allergy]. Verify the 'Allergy Search/Assign' dialog is displayed. Select any value in the 'Type' field. Enter any value in the 'Search Term' field. Click [Search]. Select the desired value and click [Add]. Verify the 'Add Allergy - Attributes' dialog is displayed. Select any value in the 'Reaction' field. Select any value in the 'Severity' field. Click [Add]. Validate a "Message from webpage" message is displayed stating: Are you sure you want to add this Allergy to the patient record. Click [OK] and [Close Chart]. Close the form. Select "Client A" and access the 'Allergies and Hypersensitivities' form. Validate the client header contains the reviewed status "Allergies Reviewed = Yes". Click [Update]. Verify the 'Allergies and Hypersensitivities' table is displayed. Validate the 'Allergies and Hypersensitivities' table contains the Allergy filed through OrderConnect in the previous steps. Click [Close/Cancel] and [Submit]. Access Crystal Reports or other SQL reporting tool. Create a report using the 'SYSTEM.cw_client_allergies_review' table. Validate a row is displayed for the review information for "Client A". Validate the 'PATID' field contains the Client ID for "Client A". Validate the 'reviewed_code' field contains "Y" for the saved allergy in the previous steps. Validate the 'reviewed_value' field contains "Yes" for the saved allergy in the previous steps. Close the report. Scenario 4: Allergies and Hypersensitivities - Add/Edit Allergies Specific Setup: CareFabric is configured and enabled. The 'Enable Allergen Search Web Service' registry setting is enabled. A client must have an active episode. (Client A) Steps Select "Client A" and access the 'Allergies and Hypersensitivities' form. Select "No" in the 'Known Medication Allergies' field. Select "No" in the 'Known Food Allergies' field. Click [Update]. Validate the 'Allergies and Hypersensitivities' grid is displayed. Click [New Row]. Search for and select any value in the 'Allergen/Reactant' field. Enter the desired date in the 'Date Recognized' field. Select "Active" in the 'Status' field. Select any value in the 'Reaction Severity' field. Click [Save] and [Submit]. Select "Client A" and access the 'Allergies and Hypersensitivities' form. Click [Update]. Validate the 'Allergies and Hypersensitivities' grid contains the allergy filed in the previous steps. Select "Inactive" in the 'Status' field. Click [Save] and [Submit]. Select "Client A" and access the 'Allergies and Hypersensitivities' form. Click [Update]. Validate the 'Allergies and Hypersensitivities' grid contains the allergy with the "Inactive" status. Click [Close/Cancel] and close the form. Scenario 5: Validate the 'ClientAllergies' - 'Save' web service Specific Setup: CareFabric is configured and enabled. A client must have an active episode. (Client A) The 'Enable Allergen Search Web Service' registry setting is enabled. Steps Access SoapUI for the 'Client Allergies' - 'Save' web service. Enter the system code that will be used to log into Avatar in the 'SystemCode' field. Enter the user name that will be used to log into Avatar in the 'UserName' field. Enter the password that will be used to log into Avatar in the 'Password' field. Enter "Client A" in the 'ClientID' field. Enter the allergen reactant code in the 'allergenReactant' field. Enter the status code in the 'Status' field. Enter the date in the 'dateRecognized' field. Click [Run]. Validate the request has sent successfully. Validate the 'Message' field contains the 'ClientAllergies web service has been filed successfully.' Select "Client A" and access the 'Allergies and Hypersensitivities' form. Click [Update]. Verify the 'Allergies and Hypersensitivities' grid is displayed. Validate the 'Allergies and Hypersensitivities' grid contains the allergy filed in the previous steps. Click [Close/Cancel] and [Submit].	Topics • Web Services • Allergy • Registry Settings • Allergies and Hypersensitivities • Allergies
Update 55 Summary \| Details Additional fields are added to the 'Allowable Services' grid in the "Treatment Plan" Intervention tab. Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following: Treatment Plan Interventions - Assigned Services Treatment Plan - Interventions Scenario 1: Validate Treatment Plan - Assigned Services grid. Specific Setup: Middleware update is required for full functionality. Registry Setting 'Enable Service Entry Restriction by Client Treatment Plan' is set to 'S'. Registry Setting 'Activate Program/Service Code Filter' is set to 'Y'. 'Assign Services' section in the 'Program Maintenance' form has field 'Enable Service Entry Restriction for Program' set to 'Yes' for one or more programs. Test client (Client A) is admitted into a program with the above set up. Steps Open 'Treatment Plan' for the test client 'Client A'. Click 'Add' on the pre-display to add a new plan. Set the 'Plan Date' to any date. Set the 'Plan Name' to any text (note: this field may not be displayed for your facility). Select any value from the 'Plan Type' dropdown list. Click [Draft]. Click [Launch Plan]. Click [Add New Problem]. Select any value in the 'Problem Code' field. Select 'Active' from the 'Status (Problem List)' dropdown list. Enter any text in the 'Problem' text box. Select any value from the 'Status' dropdown list. Click [Add New Goal]. Enter any text in the 'Goal' text box. Select any value from the 'Status' dropdown list. Click [Add New Objective]. Enter any text in the 'Objective' text box Select any value from the 'Status' dropdown list. Click [Add New Intervention]. Enter any text in the 'Intervention' text box. Select any value from the 'Status' drop down list. Click 'Add Service' in the 'Assigned Services' grid. Select a program from the 'Service Program' dropdown list. Select a service code from the 'Service Code' dropdown list. Select any value in the 'Frequency' dropdown list. Select any value in the 'Duration' dropdown list. Select any value in the 'Service Mode' dropdown list. Select any value in the 'Place of Service' dropdown list. Enter any alphanumeric characters in the 'Amount' field. Enter any alphanumeric characters in the 'Agency / Staff Responsible' field. Click [Back to Plan Page]. Click [Launch Plan] to display the existing plan. Click on the 'Intervention' entered in the above steps. Verify the 'Service Program' field is populated. Verify the 'Frequency' field is populated. Verify the 'Duration' field is populated. Verify the 'Service Mode' field is populated. Verify the 'Place of Service' field is populated. Verify the 'Agency / Staff Responsible' field is populated. Click [Back to Plan Page]. Click [Final] to finalize the plan and route the document. Click [Submit]. If document routing is enabled, review the treatment plan display and verify all data is displayed for the 'Assigned Services' fields. Continue to accept the document per your agency requirements. Return to the Home View. Right mouse on the client and click [Display Chart] Click on Treatment Plan (if available). Verify the data displays for the 'Assigned Services' under the 'Interventions' section.	Topics • Treatment Plan • NX
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: Allergies and Hypersensitivities 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 Select "Client A" and access the 'Launch OrderConnect' form. Click [Launch OrderConnect]. Verify the 'OrderConnect Chart' is displayed. Click [Allergies] and [Add Allergy]. Verify the 'Allergy Search/Assign' dialog is displayed. Select any value in the 'Type' field. Enter any value in the 'Search Term' field. Click [Search]. Select the desired value and click [Add]. Verify the 'Add Allergy - Attributes' dialog is displayed. Select any value in the 'Reaction' field. Select any value in the 'Severity' field. Click [Add]. Validate a "Message from webpage" message is displayed stating: Are you sure you want to add this Allergy to the patient record. Click [OK] and [Close Chart]. Close the form. Select "Client A" and access the 'Allergies and Hypersensitivities' form. Validate the client header contains the reviewed status "Allergies Reviewed = Yes". Click [Update]. Verify the 'Allergies and Hypersensitivities' table is displayed. Validate the 'Allergies and Hypersensitivities' table contains the Allergy filed through OrderConnect in the previous steps. Click [Close/Cancel] and [Submit]. Access Crystal Reports or other SQL reporting tool. Create a report using the 'SYSTEM.cw_client_allergies_review' table. Validate a row is displayed for the review information for "Client A". Validate the 'PATID' field contains the Client ID for "Client A". Validate the 'reviewed_code' field contains "Y" for the saved allergy in the previous steps. Validate the 'reviewed_value' field contains "Yes" for the saved allergy in the previous steps. 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 Access SoapUI for the 'Client Allergies' - 'SaveAllergenCodes' web service. Enter the system code that will be used to log into Avatar in the 'SystemCode' field. Enter the user name that will be used to log into Avatar in the 'UserName' field. Enter the password that will be used to log into Avatar in the 'Password' field. Enter "Client A" in the 'ClientID' field. Enter the allergen reactant code in the 'allergenReactant' field. Enter the status code in the 'Status' field. Enter the date in the 'dateRecognized' field. Click [Run]. Validate the request has sent successfully. Validate the 'Message' field contains the 'ClientAllergies web service has been filed successfully.' data on file. Select "Client A" and access the 'Allergies and Hypersensitivities' form. Validate the client header contains the reviewed status "Allergies Reviewed = Yes". Click [Update]. Verify the 'Allergies and Hypersensitivities' table is displayed. Validate the 'Allergies and Hypersensitivities' table contains the Allergy filed through Web Service in the previous steps. Click [Close/Cancel] and [Submit]. Access Crystal Reports or other SQL Reporting Tool. Create a report using the 'SYSTEM.cw_client_allergies_review' table. Validate a row is displayed for the review information for "Client A". Validate the 'PATID' field contains the Client ID for "Client A". Validate the 'reviewed_code' field contains "Y" for the saved allergy in the previous steps. Validate the 'reviewed_value' field contains "Yes" for the saved allergy in the previous steps. Close the report.	Topics • OrderConnect • Allergies and Hypersensitivities • Allergy • Web Services
Update 57 Summary \| Details Task List - Remove "Incomplete" as an option for 'Void Task Action' Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following: Task Definitions Task Associations Task Reporting Task List - Dismiss Task dialog Task Event List Scenario 1: Task List - Void Task Action from Task Reporting Specific Setup: A client must have an active episode. (Client A) “Client A” must have a ‘Date of Birth’, ‘Sex’ and address on file in the ‘Update Client Data’ form, as well as information filed in the ‘Allergies and Hypersensitivities’ form, ‘Diagnosis’ form, and in the ‘Height’ and ‘Weight’ fields in the ‘Vitals Entry’ form. Steps Access the 'Task Definitions' form. Select "Add" from the 'Add/Edit Task Definition' field. Set the 'New Task Code' field to "Dismiss" and press Tab. Set the 'Task Title' field to "Task to Dismiss" and click [Submit]. Validate a message is displayed that states: "Task Definitions has completed. Do you wish to return to form?" and click [No]. Access the 'Task Associations' form. Select "Task Definition" from the 'Task Type' field. Search for and select "Task to Dismiss (Dismiss)" from the 'Task Group/Definition' field. Select "Add" from the 'Add/Edit/Delete Association' field. Select "Order Entry" from the 'Order Event' field. Search for and select "4 WAY SALINE (MULTI INGREDIENT SPRAY) (10) SPRAY NASAL" from the 'Order Code' field. Click [Update Associations] and [Submit]. Validate a message is displayed that states: "Task Associations has completed. Do you wish to return to form?" and click [No]. Select "Client A" and access the Order Entry Console. Search for and select "4 WAY SALINE (MULTI INGREDIENT SPRAY) (10) SPRAY NASAL" from the 'New Order' field. Set the 'Dose' field to "1". Select "app" from the 'Dose Unit' field. Select "Every Hour" from the 'Freq' field. Set the 'Duration' field to "2" and click [Hours]. Set the 'Start Time' field to "0000". Click [Add to Scratchpad] and [Sign]. Validate the 'Interactions' dialog is displayed. Override all interactions and click [Save Override and Exit]. Access the 'Task List' widget. Search for and select "Client A" from the 'Search Patients' field. Validate that two tasks labeled: "Task to Dismiss" were created and placed under the Overdue column. Access the 'Task Reporting' form. Select the 'Dismiss Task' tab. Set the 'From Date' and 'To Date' fields to the current date. Search for and select "Client A" from the 'Patient' field. Select "Incomplete" from the 'Task Status' field. Select "Task to Dismiss (Dismiss)" from the 'Task Code' field and click [Select Tasks]. Validate a dialog is launched that contains the two overdue tasks. Select the two tasks and click [OK]. Select "Other" from the 'Reason' field. Set the 'Reason Text' field to "Patient not in bed" and click [Dismiss]. Access the 'Task List' widget. Validate that the two tasks labeled: "Task to Dismiss" are removed from the Overdue column. Access the 'Task Reporting' form. Select the 'Void task Action' tab. Set the 'From Date' and 'To Date' fields to the current date. Search for and select "Client A" from the 'Patient' field. Search for and select the logged in user from the 'Staff' field. Select "Task to Dismiss (Dismiss)" from the 'Task Code' field. Select "Dismissed" from the 'Task Action Event' field and click [Select Task Event]. Validate a dialog is launched that contains the two dismissed tasks. Select the two tasks and click [OK]. Select "Other" from the 'Void Reason' field. Set the 'Reason Text' field to "Correction" and click [Void]. Validate a message is displayed that states: "Task voided" and click [OK]. Click [Discard]. Validate a message is displayed that states: "Are you sure you want to Close without saving?" and click [Yes]. Access the 'Task List' widget. Validate that the two tasks labeled: "Task to Dismiss" are re-added to the Overdue column. Task List - 'Addl Instructions' in the Task description Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following: Task Definitions Task Associations Scenario 1: Task List - Complete, Attempt, and Dismiss generic Scheduled Tasks Specific Setup: A client must have an active episode. (Client A) “Client A” must have a ‘Date of Birth’, ‘Sex’ and address on file in the ‘Update Client Data’ form, as well as information filed in the ‘Allergies and Hypersensitivities’ form, ‘Diagnosis’ form, and in the ‘Height’ and ‘Weight’ fields in the ‘Vitals Entry’ form. Steps Access the 'Task Definitions' form. Select "Add" from the 'Add/Edit Task Definition' field. Set the 'New Task Code' field to "Example" and press Tab. Set the 'Task Title' field to "Task Example" and click [Submit]. Validate a message is displayed that states: "Task Definitions has completed. Do you wish to return to form?" and click [No]. Access the 'Task Associations' form. Select "Task Definition" from the 'Task Type' field. Search for and select "Task Example (Example)" from the 'Task Group/Definition' field. Select "Add" from the 'Add/Edit/Delete Association' field. Select "Order Entry" from the 'Order Event' field. Search for and select "CORGARD 20 MG TABLET ORAL" from the 'Order Code' field. Click [Update Associations] and [Submit]. Validate a message is displayed that states: "Task Associations has completed. Do you wish to return to form?" and click [No]. Select "Client A" and access the Order Entry Console. Search for and select "CORGARD 20 MG TABLET ORAL" from the 'New Order' field. Set the 'Dose' field to "1". Select "Tablet" from the 'Dose Unit' field. Select "Every Hour" from the 'Freq' field. Set the 'Duration' field to "6" and click [Hours]. Click [Add to Scratchpad] and [Sign]. Validate the 'Interactions' dialog is displayed. Override all interactions and click [Save Override and Exit]. Access the 'Task List' widget. Search for and select "Client A" from the 'Search Patients' field. Validate that six "Task Example" tasks are created under first six hours. Select the first "Task Example" task. Validate the "Due" field contains the scheduled date and time of the task. Click [Complete]. Validate the 'Complete Date' field contains the current date. Validate the 'Complete Time' field contains the current time and click [Save]. Validate that the first 'Task Example' task is removed. Select the second "Task Example" task and click 'Mark as Attempted'. Select "Other" from the 'Rationale for not completing task' field. Set the 'Reason' field to any value and click [Save]. Validate that the second 'Task Example' task has an orange circle, indicating that the task was Attempted. Select the second "Task Example" task and click [Complete] and Save. Validate that the second 'Task Example' task is removed. Select the third "Task Example" task and click 'Dismiss'. Select "Patient Refused" from the 'Rationale for not completing task' field and click [Save]. Validate the third 'Task Example' task is removed. Scenario 2: Task List - Include 'Addl Instructions' on a Task created from an Order Specific Setup: A client must have an active episode. (Client A) “Client A” must have a ‘Date of Birth’, ‘Sex’ and address on file in the ‘Update Client Data’ form, as well as information filed in the ‘Allergies and Hypersensitivities’ form, ‘Diagnosis’ form, and in the ‘Height’ and ‘Weight’ fields in the ‘Vitals Entry’ form. Steps Access the 'Task Definitions' form. Select "Add" from the 'Add/Edit Task Definition' field. Set the 'New Task Code' field to "HasDesc" and press Tab. Set the 'Task Title' field to "Has a Description". Set the 'Task Description' field to "This task has a Task Description configured in the Task Definitions form." and click [Submit]. Validate a message is displayed that states: "Task Definitions has completed. Do you wish to return to form?" and click [Yes]. Select "Add" from the 'Add/Edit Task Definition' field. Set the 'New Task Code' field to "NoDesc" and press Tab. Set the 'Task Title' field to "No Default Description" and click [Submit]. Validate a message is displayed that states: "Task Definitions has completed. Do you wish to return to form?" and click [No]. Access the 'Task Associations' form. Select "Task Definition" from the 'Task Type' field. Search for and select "Has a Description (HasDesc)" from the 'Task Group/Definition' field. Select "Add" from the 'Add/Edit/Delete Association' field. Select "Order Entry" from the 'Order Event' field. Search for and select "WELLBUTRIN 100 MG TABLET ORAL" from the 'Order Code' field. Click [Update Associations] and [Submit]. Validate a message is displayed that states: "Task Associations has completed. Do you wish to return to form?" and click [Yes]. Select "Task Definition" from the 'Task Type' field. Search for and select "No Default Description (NoDesc)" from the 'Task Group/Definition' field. Select "Add" from the 'Add/Edit/Delete Association' field. Select "Order Entry" from the 'Order Event' field. Search for and select "WELLBUTRIN 100 MG TABLET ORAL" from the 'Order Code' field. Click [Update Associations] and [Submit]. Validate a message is displayed that states: "Task Associations has completed. Do you wish to return to form?" and click [No]. Select "Client A" and access the Order Entry Console. Search for and select "WELLBUTRIN 100 MG TABLET ORAL" from the 'New Order' field. Set the 'Dose' field to "100". Select "MG" from the 'Dose Unit' field. Select "Every 6 Hours" from the 'Freq' field. Set the 'Duration' field to "28" and click [Days]. Set the 'Addl Instructions' field to "These instructions are entered in the Order Entry Console". Click [Add to Scratchpad] and [Sign]. Validate the 'Order grid' contains an order for "WELLBUTRIN 100 MG ORAL TABLET, Every 6 Hours". Validate the 'Addl Instructions' field for the order contains "These instructions are entered in the Order Entry Console.". Access the 'Task List' widget. Search for and select "Client A" from the 'Search Patients' field. Validate that a task labelled: "No Default Description" and "Has a Description" are created and placed under a future hour. Hover over the "No Default Description" task. Validate the "No Default Description" task contains the text, "Addl Instructions: These instructions are entered in the Order Entry Console." Hover over the "Has a Description" task. Validate the "Has a Description" task contains the text, "This task has a Task Description configured in the Task Definitions form. Addl Instructions: These instructions are entered in the Order Entry Console." Task List - Various fixes and improvements Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following: CarePOV Management Update Client Data Task Definitions Task Associations Frequency Code Setup Order Entry User Definition Task Shift Task Frequency Scenario 1: Task List - Bedboard Alert setup for Task List widget through CarePOV Management Specific Setup: A client must have an active episode. (Client A) “Client A” must have a ‘Date of Birth’, ‘Sex’ and address on file in the ‘Update Client Data’ form, as well as information filed in the ‘Allergies and Hypersensitivities’ form, ‘Diagnosis’ form, and in the ‘Height’ and ‘Weight’ fields in the ‘Vitals Entry’ form. Steps Access the 'CarePOV Management' form. Select the 'Client Alerts' tab. Select "Edit" from the 'Add or Edit Alert' field. Select "New Orders (1)" from the 'Client Alert' field. Validate "Yes" is selected from the 'Active' field. Validate "New Order" is selected from the 'Alert Type' field. Select "Yes" from the 'Include in Client Header' field and click [Save]. Validate a message is displayed that states: "Saved." and click [OK]. Select "Edit" from the 'Add or Edit Alert' field. Select "Stat Orders (2)" from the 'Client Alert' field. Validate "Yes" is selected from the 'Active' field. Validate "Stat Order" is selected from the 'Alert Type' field. Select "Yes" from the 'Include in Client Header' field and click [Save]. Validate a message is displayed that states: "Saved." and click [OK]. Select "Edit" from the 'Add or Edit Alert' field. Select "Pregnant (11)" from the 'Client Alert' field. Validate "Yes" is selected from the 'Active' field. Validate "Pregnancy" is selected from the 'Alert Type' field. Select "Yes" from the 'Include in Client Header' field and click [Save]. Validate a message is displayed that states: "Saved." and click [OK]. Close the form. Select "Client A" and access the 'Update Client Data' form. Validate "Female" is selected from the 'Sex' field. Select "Pregnant" from the 'Pregnancy Status' field and click [Submit]. Access the Order Entry Console. Search for and select "ADVIL MIGRAINE 200 MG CAPSULE, LIQUID FILLED ORAL" from the 'New Order' field. Set the 'Dose' field to "1". Select "Tablet" from the 'Dose Unit' field. Select "TWICE A DAY" from the 'Freq' field. Set the 'Duration' field to "1" and click [Days]. Click [Add to Scratchpad] Search for and select "Lisinopril 5 MG Tablet ORAL" from the 'New Order' field. Set the 'Dose' field to "1". Select "TABLET" from the 'Dose Unit' field. Select "STAT" from the 'Freq' field. Validate the 'Duration' field contains "1" and [Days] is selected. Click [Add to Scratchpad] and [Sign]. Validate the 'Order grid' contains an order for "ADVIL MIGRAINE 200 MG CAPSULE, LIQUID FILLED Tablet, TWICE A DAY". Validate the 'Order grid' contains an order for "Lisinopril 5 MG ORAL Tablet, STAT". Access the 'Task List' widget. Search for and select "Client A" from the 'Search Patients' field. Validate a 'Pregnancy' alert is displayed for the selected patient. Validate a 'New Orders' alert is displayed for the "Advil Migraine" order. Validate a 'Stat Orders' alert is displayed for the "Lisinopril" order. Scenario 2: Task List - Creating a Scheduled Task using Interval Frequency Specific Setup: A client must have an active episode. (Client A) “Client A” must have a ‘Date of Birth’, ‘Sex’ and address on file in the ‘Update Client Data’ form, as well as information filed in the ‘Allergies and Hypersensitivities’ form, ‘Diagnosis’ form, and in the ‘Height’ and ‘Weight’ fields in the ‘Vitals Entry’ form. Steps Access the 'Task Definitions' form. Select "Add" from the 'Add/Edit Task Definition' field. Set the 'New Task Code' field to "E2H" and press [Tab]. Set the 'Task Title' field to "Every Two Hours, Interval" and click [Submit]. Validate a message is displayed that states "Task Definitions has completed. Do you wish to return to form?" and click [No]. Access the 'Task Associations' form. Select "Task Definition" from the 'Task Type' field. Search for and select "Every Two Hours, Interval (E2H)" from the 'Task Group/Definition' field. Select "Add" from the 'Add/Edit/Delete Association' field. Select "Order Entry" from the 'Order Event' field. Search for and select "RITALIN 10 MG TABLET ORAL" from the 'Order Code' field. Click [Update Associations] and [Submit]. Validate a message is displayed that states "Task Associations has completed. Do you wish to return to form?" and click [No]. Select "Client A" and access the Order Entry Console. Search for and select "RITALIN 10 MG TABLET ORAL" from the 'New Order' field. Set the 'Dose' field to "1". Select "MG" from the 'Dose Unit' field. Select "Every 2 Hours" from the 'Freq' field. Set the 'Duration' field to "6" and click [Days]. Complete any other required fields and click [Add to Scratchpad] and [Sign]. Validate the 'Interactions' dialog is displayed. Override any interactions and click [Save Override and Exit] button. Access the 'Task List' widget. Search and select "Client A" from the 'Search Patients' field. Validate that three "Every Two Hours, Interval" tasks were created; the first task under the current hour, the second task two hours in the future, and the third task four hours in the future. Scenario 3: Task List - Bedboard Alert - Continuous Orders (Medical Food) Specific Setup: The following extended attributes must be set in the Order Entry Tabled Files ‘(500) Order Types’ dictionary for “Medical Food”: ‘(501) Order Type Category’ = “Pharmacy” ‘(506) Default Orders To Open-Ended When No Default Duration’ = “Yes” ‘(560) Is This a Medical Food Order Type’ = “Yes” ‘(10181) Route of Administration’ = “GASTROSTOMY TUBE”, "J-TUBE", "NASOGASTRIC", "TUBE FEED", "INTRAVENOUS" Please log out of the application and log back in after completing the above configuration. An 'Order Code' must exist with an 'Order Type' of "Medical Food" and a 'Route of Administration' of "Tube Feed". (Medical Food) A client must have an active episode. (Client A) “Client A” must have a ‘Date of Birth’, ‘Sex’ and address on file in the ‘Update Client Data’ form, as well as information filed in the ‘Allergies and Hypersensitivities’ form, ‘Diagnosis’ form, and in the ‘Height’ and ‘Weight’ fields in the ‘Vitals Entry’ form. Steps Access the 'CarePOV Management' form. Select the 'Client Alerts' tab. Select "Edit" from the 'Add or Edit Alert' field. Select "Continuous Order (15)" from the 'Client Alert' field. Validate "Yes" is selected from the 'Active' field. Validate "Continuous Order" is selected from the 'Alert Type' field. Select "Yes" from the 'Include in Client Header' field and click [Save]. Validate a message is displaying that states: "Saved." and click [OK]. Close the form. Select "Client A" and access the Order Entry Console. Search for and select "Medical Food" from the 'New Order' field. Select "EVERY DAY" from the 'Freq' field. Validate the 'Route' field contains "TUBE FEED". Select "Pump" from the 'Admin Method' field. Validate the 'Rate Unit' field contains "mL/hr". Set the 'Rate Amount' field to "1". Set the 'Duration' field to "3" and click [Days]. Click [Add to Scratchpad] and [Sign]. Validate the 'Interactions' dialog is displayed. Override all interactions and click [Save Override and Exit]. Validate the 'Order grid' contains an order for "Medical Food Tube Feed Pump Rate: 1 mL/hr EVERY DAY". Access the 'HomeView' and deselect "Client A". Select "Client A" and access the Order Entry Console. Validate the 'Client Header' contains a 'Client Alert' with an infinity symbol. Validate when hovering over the 'Client Alert' that a message is displayed that states: "Continuous Order (Medical Food)". Access the 'Task List' widget. Search for and select "Client A" from the 'Search Patients' field. Validate that the 'Client Card' contains a "Continuous Order" 'Bedboard Alert'. Scenario 4: OE NX - New Order - Administration Method "IV Primary (Continuous)" Specific Setup: The following extended attributes must be set in the Order Entry Client Information '(20969) Administration Method' dictionary for “IVPR”: ‘(20990) Preferred Description’ = “IV Continuous” ‘(20991) Show Diluent’ = “No” ‘(20992) Require Diluent’ = “No” '(20993) Allow Selection' = "Yes" '(20995) Show Additive Prompts' = "Yes" '(20996) Applicable Routes' = "INTRAVENOUS" Please log out of the application and log back in after completing the above configuration. In the 'Order Code Setup' form the 'Additive Component' checkbox must be checked in the 'Is an IV Additive Component' field for the "DOPAMINE HCL 160 MG/1 ML SOLUTION INTRAVENOUS" order code. A client must have an active episode. (Client A) “Client A” must have a ‘Date of Birth’, ‘Sex’ and address on file in the ‘Update Client Data’ form, as well as information filed in the ‘Allergies and Hypersensitivities’ form, ‘Diagnosis’ form, and in the ‘Height’ and ‘Weight’ fields in the ‘Vitals Entry’ form. Steps Access the 'CarePOV Management' form. Select the 'Client Alerts' tab. Select "Edit" from the 'Add or Edit Alert' field. Select "Continuous Order (15)" from the 'Client Alert' field. Validate "Yes" is selected from the 'Active' field. Validate "Continuous Order" is selected from the 'Alert Type' field. Select "Yes" from the 'Include in Client Header' field and click [Save]. Validate a message is displaying that states: "Saved." and click [OK]. Close the form. Select "Client A" and access the Order Entry Console. Search for and select "Dextrose et DEXTROSE 5% Solution INTRAVENOUS" from the 'New Order' field. Set the 'Dose' field to "500". Select "mL" from the 'Dose Unit' field. Select "Continuous" from the 'Freq' field. Select "IV Continuous" from the 'Admin Method' field. Select "DOPAMINE HCL" from the 'Additive' field. Set the 'Additive Dose' field to "800". Select "MG" from the 'Additive Dose Unit' field. Select "As Directed" from the 'Rate Unit' field. Validate the 'Rate Amount' field contains "As Directed". Set the 'Volume Amount in ML' field to "800". Set the 'Duration' field to "28" and click [Days]. Click [Add to Scratchpad] and [Sign]. Validate the 'Order grid' contains an order for "Dextrose et DEXTROSE 5% INTRAVENOUS Solution Additive: DOPAMINE HCL 800 MG 500 mL, Continuous". Access the 'Task List' widget. Search for and select "Client A" from the 'Search Patients' field. Validate that the 'Client Card' contains a "Continuous Order" 'Bedboard Alert'. Scenario 5: Task List - Creating an Unscheduled Task based on Task Shift frequencies Specific Setup: A client must have an active episode. (Client A) “Client A” must have a ‘Date of Birth’, ‘Sex’ and address on file in the ‘Update Client Data’ form, as well as information filed in the ‘Allergies and Hypersensitivities’ form, ‘Diagnosis’ form, and in the ‘Height’ and ‘Weight’ fields in the ‘Vitals Entry’ form. Steps Access the 'Task Shift' form. Select "Add" from the 'Add/Edit Shift Definition' field. Set the 'New Shift Code' field to "Nurse" and press [TAB]. Set the 'Shift Description' field to "Nursing Shifts". Set the 'Shift 1 Start Time' field to "0800" and press [TAB]. Set the 'Shift 2 Start Time' field to "1600" and press [TAB]. Set the 'Shift 3 Start Time' field to "0000" and press [TAB]. Validate the 'Shift 1 End Time' field contains "1559". Validate the 'Shift 2 End Time' field contains "2359". Validate the 'Shift 3 End Time' field contains "0759". Click [Submit]. Validate a message is displayed that states: "Task Shift has completed. Do you wish to return to form?" and click [No]. Access the 'Task Frequency' form. Select "Add" from the 'Add/Edit Frequency' field. Set the 'New Task Frequency Code' field to "Nurse" and press [TAB]. Set the 'Task Frequency Description' field to "Nursing Shifts". Select "Shift" from the 'Type of Frequency' field. Select "Nursing Shifts (Nurse)" from the 'Shift' field and click [Submit]. Validate a message is displayed that states: "Task Frequency has completed. Do you wish to return to form?" and click [No]. Access the 'Task Definitions' form. Select "Add" from the 'Add/Edit Task Definition' field. Set the 'New Task Code' field to "Shift" and press [Tab]. Set the 'Task Title' field to "Nurse Shift Example". Select "Yes" from the 'Override Originating Task Details' field Select "Nursing Shifts (Nurse)" from the 'Default Frequency' field. Set the 'Default Duration' field to "1". Select "Days" from the 'Default Duration (Units)' field and click [Submit]. Validate a message is displayed that states "Task Definitions has completed. Do you wish to return to form?" and click [No]. Access the 'Task Associations' form. Select "Task Definition" from the 'Task Type' field. Search for and select "Nurse Shift Example (Shift)" from the 'Task Group/Definition' field. Select "Add" from the 'Add/Edit/Delete Association' field. Select "Order Entry" from the 'Order Event' field. Search for and select "PRILOSEC 10 MG/1 PACKET ORAL" from the 'Order Code' field. Click [Update Associations] and [Submit]. Validate a message is displayed that states "Task Associations has completed. Do you wish to return to form?" and click [No]. Select "Client A" and access the Order Entry Console. Search for and select "PRILOSEC 10 MG/1 PACKET ORAL" from the 'New Order' field. Set the 'Dose' field to "1". Select "Tablet" from the 'Dose Unit' field. Select "EVERY DAY" from the 'Freq' field. Set the 'Duration' field to "1" and click [Days]. Complete any other required fields and click [Add to Scratchpad] and [Sign]. Access the 'Task List' widget. Search and select "Client A" from the 'Search Patients' field. Validate that one task labeled: 'Nurse Shift Example' is displayed and placed under the Unscheduled column based on the current time.	Topics • myAvatar/myAvatar NX • Task List • Order Entry Console • NX
Update 58 Summary \| Details Vitals Entry - Height format Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following: Vitals Entry Dynamic Form - Admission - Client Scenario 1: Vitals Entry - Field Validations Specific Setup: Select an existing client or admit a new client for the test. Steps Open the "Vitals Entry" form. Select the client identified as the test client. Set the "Height (cm)" field to "182.8". Validate the "Height (ft in)" field contains "6 0.0". Set "Weight (lbs)" to "132.8". Validate the "Weight (kgs)" contains "60.2". Set "Weight (kgs)" to "60.2". Validate the "Weight (lbs)" is "132.7". Populate all the other fields on the form. Submit the form to file data. Remain in the form. Elect to "Edit" an existing vital sign record. Click "Select Vital Sign" button. Select a row to edit. Validate data displays as it was data entered. Remain in the form. Elect to "Delete" an existing vital sign record. Click "Select Vital Sign" button. Select a row to delete. Validate row is removed. Scenario 2: Vitals Entry - BMI Entry Configuration Specific Setup: Admit or select a client over the age of 18 with an existing episode. Admit or select a client that is under the age of 18 with an existing episode. Steps Open the "Registry Settings" form. Set the "BMI Entry Configuration" registry setting to "D". Submit to file. Open the "Vitals Entry" form for the client that is over 18. Enter a height in the "Height (ft in)" field. Submit to File. Open the "Vitals Entry" form. Validate the height fields are defaulted to the previously entered height. Close the form. Open the "Vitals Entry" form for the client that is under 18. Enter a height in the "Height (ft in)" field. Submit to File. Open the "Vitals Entry" form. Validate the height fields are not defaulted to the previously entered height. Close the form. Open the "Registry Settings" form. Set the "BMI Entry Configuration" registry setting to "R". Submit to file. Open the "Vitals Entry" form. Enter in height information. Validate the weight fields are required. Remove all height and weight fields. Enter in weight information. Validate the height fields are required. Close the form. Open the "Registry Settings" form. Set the "BMI Entry Configuration" registry setting to "N". Submit to file. Open the "Vitals Entry" form for a client over the age of 18. Validate the height fields aren't defaulted in. Enter in height information. Validate that it's not requiring the weight fields be filled in. Close Form. Vitals Entry - Conversion from pounds to kilograms Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following: Vitals Entry Scenario 1: Vitals Entry - Field Validations Specific Setup: Select an existing client or admit a new client for the test. Steps Open the "Vitals Entry" form. Select the client identified as the test client. Set the "Height (cm)" field to "182.8". Validate the "Height (ft in)" field contains "6 0.0". Set "Weight (lbs)" to "132.8". Validate the "Weight (kgs)" contains "60.2". Set "Weight (kgs)" to "60.2". Validate the "Weight (lbs)" is "132.7". Populate all the other fields on the form. Submit the form to file data. Remain in the form. Elect to "Edit" an existing vital sign record. Click "Select Vital Sign" button. Select a row to edit. Validate data displays as it was data entered. Remain in the form. Elect to "Delete" an existing vital sign record. Click "Select Vital Sign" button. Select a row to delete. Validate row is removed. Scenario 2: Vitals Entry Web Services Steps Using the preferred web service tool, file the ClientVitals web service to add Weight data to the vitals data. To do this set the readingCode to "Wtlb" and the readingValue to "132.8". File the web service. Open the "Vitals Entry" form. Validate the "Weight (lbs)" field is set to "132.8" Validate the "Weight (kgs)" field is set to "60.2". Using the preferred web service tool, file the ClientVitals web service to add Weight data to the vitals data. To do this set the readingCode to "WtKg" and the readingValue to "60.2". File the web service. Open the "Vitals Entry" form. Validate the "Weight (lbs)" field is set to "132.7" Validate the "Weight (kgs)" field is set to "60.2".	Topics • Vitals Entry • NX • 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: 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 Open the Treatment Plan form. Select [ClientA]. Populate any required fields on the main form. In the "Problems" grid select or add a problem [Problem1] with a status of "Active". Add or select a second problem [Problem2] with a different status, for example "Monitoring". Click [Launch Plan]. Validate the treatment plan tree loads without a warning. Validate both problems are listed in the grid, as expected. Select [Problem1] and validate the "Status(Problem List) field equals "Active". Populate any other required fields in the "Problem" section. Select [Problem2] and validate the "Status(Problem List) field equals "Monitoring". Populate any other required fields in the "Problem" section. Click [Back to Plan Page]. Submit the treatment plan. Return to the form and select the treatment plan just submitted. Click [Launch Plan]. Validate all three problems are displayed. Click each problem and validate fields in the problem section are populated as expected. Click [Back to Plan Page]. In the "Problems" grid, click "New Row". Enter the same problem entered for [Problem1]. Validate a message displays blocking entry that states "Problem already exists", as expected. Select the new row just attempted and click [Delete] to remove it. Validate the row is deleted from the "Problems" grid. In the "Problems" grid, click "New Row" again. Enter a problem code other than the ones in [Problem1] or [Problem2]. Validate the entry is accepted. Select a status of "Active" for the problem. Click [Launch Plan]. Validate the treatment plan tree loads without a warning. Validate all three problems are listed in grid. Select the problem just added. Populate any other required fields in the "Problem" section. Click [Back to Plan Page]. Submit the treatment plan. Return to the form and select the treatment plan just submitted. Click [Launch Plan]. Validate all three problems are displayed and populated, as expected. Close the form.	Topics • Treatment Plan • NX • Chart View
Update 61 Summary \| Details Allergies and Hypersensitivities - Single Select Dictionary fields Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following: Allergies and Hypersensitivities Scenario 1: 'Allergies and Hypersensitivities' form - field validations Specific Setup: A client is enrolled in an existing episode and has two allergies on file (Client A). Steps Select "Client A" and access the 'Allergies and Hypersensitivities' form. Click [Update]. Validate the two allergies on file for "Client A" are displayed. Click on any column header to sort the data. Validate the data is sorted accordingly. Select the desired value in the 'Onset' field for both allergies. Click [Save]. Validate the 'Allergies and Hypersensitivities' grid is dismissed. Click [Update]. Validate the 'Onset' field contains the value selected in the previous steps. Click [Close/Cancel]. Validate the 'Allergies and Hypersensitivities' grid is dismissed. Click [Submit]. Scenario 2: Allergies and Hypersensitivities - Add/Edit Allergies Specific Setup: A client must have an active episode. (Client A) Steps Select "Client A" and access the 'Allergies and Hypersensitivities' form. Select "No" in the 'Known Medication Allergies' field. Select "No" in the 'Known Food Allergies' field. Click [Update]. Validate the 'Allergies and Hypersensitivities' grid is displayed. Click [New Row]. Select any value in the 'Allergen/Reactant' field. Enter the desired date in the 'Date Recognized' field. Select "Active" in the 'Status' field. Select any value in the 'Reaction Severity' field. Click [Save] and [Submit]. Select "Client A" and access the 'Allergies and Hypersensitivities' form. Click [Update]. Select the allergy added in the previous steps and click [Delete Row]. Validate a "Confirm" message is displayed stating: Are you sure you want to delete these rows? Click [Yes]. Validate an "Error" message is displayed stating: Allergies that have been saved previously cannot be deleted. Please update the 'Status' as appropriate. Click [OK]. Validate the 'Allergies and Hypersensitivities' grid still contains the allergy filed in the previous steps. Select "Inactive" in the 'Status' field. Click [Save] and [Submit]. Select "Client A" and access the 'Allergies and Hypersensitivities' form. Click [Update]. Validate the 'Allergies and Hypersensitivities' grid is displayed. Click [New Row]. Select any value in the 'Allergen/Reactant' field. Enter the desired date in the 'Date Recognized' field. Select "Active" in the 'Status' field. Select any value in the 'Reaction Severity' field. Select the new allergy record and click [Delete Row]. Validate a "Confirm" message is displayed stating: Are you sure you want to delete these rows? Click [Yes]. Validate the 'Allergies and Hypersensitivities' grid does not contain the second allergy record. Click [Close/Cancel] and close the form.	Topics • Allergies and Hypersensitivities • myAvatar/myAvatar NX
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: Client Health Maintenance Results Entry 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 Select "Client A" and access the 'Family Health History' form. Validate "Add New" is selected in the 'Select Family Member' field. Select any value in the 'Relationship' field. Populate any desired fields. Select "Yes" in the 'Health Problems To Record' field. Click [Enter Health History]. Click [New Row]. Enter any value in the 'Problem' field. Populate any desired field. Click [Save], [Submit], and [No]. Navigate to the 'All Documents' view. Select 'All Forms'. Select "Family Health History" in the 'Form Description' field. Validate the entry from the previous steps is present. Validate the 'Time' field displays. Select the entry and validate it displays in the 'Console Widget Viewer'. Validate the 'Launch Report' button exists. Click [Launch Report]. Validate a report displays with the information filed in the previous steps. 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 Access the 'Client Health Maintenance' form. Select "Client A". Click Immunization [Update] and [New Row] Double click the 'Refused' field. Select "Yes" in the 'Refused' field. Validate the 'Reason' field is required. Double click the 'Refused' field. Select "No" in the 'Refused' field. Validate the 'Reason' field is not required. Select "Historical Information - From Parent's Recall (04)" in the 'Source of Immunization' field. Complete all required fields. Click [Save] and [Submit]. Access the 'All Documents' widget. Select "Client A". Select the 'All Forms' tab. Validate the 'Time' field displays. Select the 'Client Health Maintenance' entry. Validate the 'Console Widget Viewer' displays the immunization data filed in the previous steps. Validate the 'Source of Immunization' displays as expected. Validate the 'Launch Report' button exists. Click [Launch Report]. Validate a report displays with the information filed in the previous steps. 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 Select "Client A" and access the 'Results Entry' form. Select "Add" in the 'Add/Edit/Delete Result' field. Populate all required and desired fields. Click [File Header Info]. Validate a message is displayed stating: "Header information filed." Click [OK]. Select 'Result Details'. Select "Add" in the 'Add/Edit/Delete Result Detail' field. Validate the 'Header' field contains the data from the previous steps. Populate all required and desired fields. Click [File Detail Info]. Validate a message is displayed stating: "Detail information filed." Click [OK] and [Exit Option]. Access the 'Review Results' form. Select "Client A" in the 'Client ID' field. Select the entry from the previous steps in the 'Select Results' field. Validate the 'Results' field contains the data from the previous steps. Select any value in the 'Review Status' field. Click [Submit]. Select "Client A" and access the 'All Documents' view. Select "All Episodes" in the 'Header Episode' field. Select 'All Forms'. Select "Review Results" in the 'Form Description' field. Validate the entry from the previous steps is present. Validate the 'Time' field displays. Select the entry and validate it displays in the 'Console Widget Viewer'. Validate the 'Launch Report' button exists. Click [Launch Report]. Validate a report displays with the information filed in the previous steps. Close the report.	Topics • Widgets • Console Widget • NX • Client Health Maintenance • Family Health History • Review Results
Update 69 Summary \| Details The 'Problem List', 'Treatment Plans', 'Assessment Mapping' and 'Clinical Reconciliation' forms are updated with DSM/ICD information. Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following: Clinical Reconciliation Problem List Scenario 1: Clinical Reconciliation - Verify Problem List Details Specific Setup: One or more problems have been entered in the 'Problem List' form after the updates were installed. Avatar 2022 CWS Update 69 is required for full functionality. Avatar 2022 CareFabric Update 54 is required for full functionality. Avatar 2022 PM Update 81or Avatar Cal-PM Update 39 is required for full functionality. Steps Open the 'Clinical Reconciliation' form for any test client that has problems on file. Select any value in the 'Reconciliation Type' field. Select the client episode in the 'Episode' field. Click [Problem List] on the left menu. Scroll to the 'Details' column. Click [View] on any of the problems entered after the updates were installed. Verify 'Last Date Updated' displays. Verify the 'Problem Name:' is displayed. Verify the 'Status' is displayed. Verify the 'DSM/ICD10 Code:' is displayed. Verify the 'System Notes' are displayed. Click [Close]. Click [Close Form]. Scenario 2: Treatment Plan - Verify 'Problem List' Specific Setup: One or more problems have been entered in the 'Problem List' form for any test client (Client A). Avatar 2022 CWS Update 69 is required for full functionality. Avatar 2022 CareFabric Update 54 is required for full functionality. Avatar 2022 PM Update 81or Avatar Cal-PM Update 39 is required for full functionality. Steps Open any 'Treatment Plan' form for Client A. Click [Edit] for any existing plan from the pre display what is in 'Draft' status. Click on any problem in the 'Problem List' grid. Navigate to the 'DSM/ICD Code' column. Click [View]. Validate the ICD10 Code item is equal to "Populated with the associated ICD10 code". Validate the ICD10 Description item is equal to "ICD10 description". Click [System Notes] - View button. Validate the 'Action' column is equal to "Action related to the problem". Validate the 'Date' column is equal to "Action date". Validate the 'Status' column is equal to "Status of problem". Validate the 'User' column is equal to "User logged in at time of action". Validate the'From' column is equal to "From or option from which the action was created". Click [Close Form]. Scenario 3: Problem List - field verification Specific Setup: One or more problems have been entered in the 'Problem List' form. Avatar 2022 CWS Update 69 is required for full functionality. Avatar 2022 CareFabric Update 54 is required for full functionality. Avatar 2022 PM Update 81or Avatar Cal-PM Update 39 is required for full functionality. Steps Open 'Problem List' form for any client (Client A) who has existing problems filed. Click [View/Enter Problems]. Verify the 'Problem' column contains the description of the problem. Verify the 'Problem Classification' column is populated. Verify the 'Date of Onset' is populated. Verify the 'Status' is populated. Click [View] on the 'DSM/ICD' column. Verify the 'ICD10Code' row contains the associated ICD Code. Verify the 'ICD10 Description' contains the associated description. Click [Close]. Click [View] on the 'System Note' column. Verify the 'Action' column contains the action taken on the problem. Verify the 'Date' column contains the date the action occurred. Verify the 'Status' column contains the problem status. Verify the 'User' column contains the name of the user logged in at the time the action occurred. Verify the 'From' column contains the name of the form where the action occurred. Click [Close]. Click [Close/Cancel]. Click [Yes] on the message 'Confirm Loss of Changes'. Click [Close Form]. 'Problem List', 'Treatment Plans', 'Assessment Mapping' and 'Clinical Reconciliation' forms Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following: Problem List Patient Health Profile Change MR# Scenario 1: Assessment Mapping to the "Problem List" form verification Specific Setup: Using "Assessment Mapping", create an assessment mapping for the 'Problem List' type. Ex: Patient Conditions was used in this scenario. A record for any test client has been filed in the mapped assessment. Avatar CareFabic 2022 Update 54 must be installed for full functionality. Avatar PM 2022 Update 81 or Avatar Cal-PM 2022 Update 39 must be installed for full functionality. Steps Open the form used in the 'Assessment Mapping' such as 'Patient Conditions'. File the data for any test client, being certain to include the mapped fields. Open the client "Problem List". Click 'System Notes' on the row added from the mapped assessment. Verify 'Action' column is populated. Verify 'Date' column is populated. Verify 'Status' column is populated. Verify 'User' column is populated. Verify 'From' column contains the name of the mapped assessment. Click [Close]. Click [Close/Cancel] to exit the grid. Click [Submit]. Scenario 2: Validate Patient Health Profile web service Specific Setup: Access to SoapUI or other webservice tool. Dictionary Update: Avatar CWS: File: CWS, Data Element: (2526) Problem Type: Add or note at least one value in the dictionary. Avatar CareFabric 2022 Update 54 is required for full functionality. Avatar PM 2022 Update 81 or Avatar Cal-PM Update 39 is required for full functionality Steps Create a new project for the 'Patient Health Profile' web service. Populate the 'SystemCode', 'UserName', and 'Password' fields with the information used to log into Avatar. Within the 'PHPProblemDataObject': Input the 'Problem Type' dictionary code from Setup in the 'Type' field. Input any valid date into the 'ProblemDate' field. Input any text into the 'Status' field. Input any text into the 'Description' field. Within the 'PHPOpenCareGapsObject': Input any valid date into the 'EventDate' field. Input any text into the 'Measure' field. Input any text into the 'MeasureDescription' field. Within the 'PHPInpatientStaysObject': Input any text into the 'Type' field. Input any valid date into the 'DateOfStay' field. Input any text into the 'Facility' field. Input any text into the 'LengthOfStay' field. Input any text into the 'AdmitCOndition' field. Within the 'PHPPhysicianConsultObject': Input any valid date into the 'ConsultDate' field. Input any text into the 'Location' field. Input any text into the 'ProviderName' field. Within the 'PHPMedicationsObject'. Input any valid date into the 'EntryDate' field. Input any text into the 'Provider' field. Input any valid NDC number into the 'NDC' field (This value can come from the 'Order Code Setup' form). Within the 'PHPLabDataObject': Input any valid date into the 'LabDate' field. Input any text into the 'LabDescription' field. Input any text into the ':LabResults' field. Input any client into the 'ClientID' field. Click [Send]. Verify the 'Message' field displays "PHPData web service has been filed successfully". Log into Avatar. Open the 'Patient Health Profile' form with the client for which the web service was filed. Select any value in the 'Medications - Verification' cell. Select any value in the 'Problems - Verification' cell. Click [Submit]. Verify the form files without errors. Open the 'Problem List' form. Click 'View/Enter Problems' Click 'System Notes' 'View' button on any row added in the web service. Verify the 'From' column is populated. Open 'Crystal Reports' or another SQL reporting tool. Create queries for SYSTEM.php_data, SYSTEM.php_problems, SYSTEM.php_open_care_gaps, SYSTEM.php_inpatient_stays, SYSTEM.php_physician_consults, and SYSTEM.php_lab_data. Verify all information displays correctly. Scenario 3: Problem List - field verification Specific Setup: One or more problems have been entered in the 'Problem List' form. Avatar 2022 CWS Update 69 is required for full functionality. Avatar 2022 CareFabric Update 54 is required for full functionality. Avatar 2022 PM Update 81or Avatar Cal-PM Update 39 is required for full functionality. Steps Open 'Problem List' form for any client (Client A) who has existing problems filed. Click [View/Enter Problems]. Verify the 'Problem' column contains the description of the problem. Verify the 'Problem Classification' column is populated. Verify the 'Date of Onset' is populated. Verify the 'Status' is populated. Click [View] on the 'DSM/ICD' column. Verify the 'ICD10Code' row contains the associated ICD Code. Verify the 'ICD10 Description' contains the associated description. Click [Close]. Click [View] on the 'System Note' column. Verify the 'Action' column contains the action taken on the problem. Verify the 'Date' column contains the date the action occurred. Verify the 'Status' column contains the problem status. Verify the 'User' column contains the name of the user logged in at the time the action occurred. Verify the 'From' column contains the name of the form where the action occurred. Click [Close]. Click [Close/Cancel]. Click [Yes] on the message 'Confirm Loss of Changes'. Click [Close Form]. Scenario 4: Problem List System Notes - verify modeled form name displays in System Notes 'From' column Specific Setup: A modeled form exists which has Alias definition for Diagnosis. Avatar 2022 CWS Update 69 is required for full functionality. Avatar 2022 CareFabric Update 54 is required for full functionality. Avatar 2022 PM Update 81or Avatar Cal-PM Update 39 is required for full functionality. Steps Open the modeled form where there is alias definition for diagnosis. Complete the form and file. Open the 'Problem List form for the same client. Click [View/Enter Problems]. Select the row which contains the information from the modeled form. Click [View] under the 'System Notes' column. Verify the 'From' column displays the name of the modeled form. Click [Close]. Click [Close/Cancel]. Click [Close Form]. Scenario 5: AddClientProblem web service validation Specific Setup: A client (Client A) must be in an active episode and have no problems filed in their 'Problem List'. Avatar CareFabric 2022 Update 54 must be installed for full functionality. Avatar PM 2022 Update 81 or Avatar Cal-PM 2022 Update 54 must be installed for full functionality. Steps Access 'SoapUI' or another web service tool. File an 'AddClientProblems' web service. Validate a success message is received. In myAvatar, open the 'Problem List' form for Client A. Click [View/Enter Problems]. Validate the problem added via the AddClientProblems web service has been added to the clients Problem List. Click [Save]. Click [Yes]. Click [Submit]. Validate the form files successfully. Scenario 6: CDR Table - validate CWSSYSTEM.cw_problem_list_history Specific Setup: Avatar PM 2022 Update 81 or Avatar Cal-PM 2022 Update 39 is required for full functionality. Avatar CareFabric 2022 Update 54 is required for full functionality. Problems have been entered for a test client (Client A) in the 'Problem List' form. Access to an SQL reporting tool such as Crystal Reports. Steps Verify access to table SYSTEM.cw_problem_list_history and CWSSYSTEM.cw_problem_list_history has been set in 'User Definition' form. Using any SQL reporting tool, create a report for CWSSYSTEM.cw_problem_list_history including the following fields: PATID data_entry_date staff_name action_value Run the report (Note: if there is a large volume of Problems on file, it is recommended that you select a few clients rather than running the report for all clients. This will assure the report completes in a timely manner). Verify the columns are populated for the existing records. Repeat the steps above for the SYSTEM.cw_problem_list_history table. Open the 'Problem List' form. Add new rows for any test client. Update existing rows for any test client. File the form. Run the reports again. Verify the data is added / updated appropriately. Open the 'Treatment Plan' form. Enter a new treatment plan for any test client. Run the above reports again. Verify the problem added in Treatment Plan is displays in the reports. Open 'Change MR#' form for Client A. Click [Assign MR#]. Click [Submit]. Run the SQL report again for the new MR#. Verify all data for Client A is now listed against the new MR#. 'Problem List' grid will not refile data unless changes are input. Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following: Problem List Scenario 1: TDE Comparison - verify only modified rows are re-filed in the Problem List grid. Specific Setup: One or more problems have been entered in the 'Problem List' form. Avatar 2022 CWS Update 69 is required for full functionality. Avatar 2022 CareFabric Update 54 is required for full functionality. Avatar 2022 PM Update 81or Avatar Cal-PM Update 39 is required for full functionality. Steps Create an SQL report against SYSTEM.cw_problem_list. Include the data_entry columns in the report. Open the 'Problem List' and file a new problem for any test client. Run the report. Review the data_entry columns. Go back to the 'Problem List' for the same client. Refile the 'Problem List' without making changes. Wait a few moments. Run the report again. Verify that no changes have been logged in the table. Only updated data rows will be reflected in the table. Create a mapping for the problem list in the 'Assessment Mapping' form. Access the mapped assessment and file a change for one record for any test client. Run the report. Note that only the updated data row will be updated. All other rows should not be changed.	Topics • NX • Treatment Plan • Problem List • Web Services • Patient Health Profile • Modeling • Query/Reporting
Update 70 Summary \| Details Bells Notes Integration - Progress Notes (Group and Individual) Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following: HomeView - My To Do's widget Scenario 1: Progress Notes (Group and Individual) - File a new service note with document routing enabled Specific Setup: Document Routing must be enabled on the 'Progress Notes (Group and Individual)' form. A client must be enrolled in an active episode (Client A). Google Chrome Browser settings are set to enable Autofill for passwords and the logged in user's password has been saved. Steps Select "Client A" from the 'My Clients' list and access the 'Progress Notes (Group and Individual)' form. Select any value from the 'Select Episode' field. Select "New Service" from the 'Progress Notes For' field. Select any value from the 'Note Type' field. Set the 'Notes Field' to any value. Set the 'Date Of Service' field to the current date. Set the 'Service Charge Code' field to any value. Select "Final" from the 'Draft/Final' field/ Click [Submit Note]. Validate that the 'Document Routing' dialog is displayed with the progress note data. Click [Accept]. Validate the 'Password' field autofill's with the user's password that is saved in Google Chrome. Click [OK]. Validate a 'Progress Notes message' is displayed stating: "Note Filed". Click [OK]. Click [Discard]. Access the 'Client Ledger' form. Set the 'Client ID' field to "Client A". Select "All Episodes" from the 'Claim/Episode/All Episodes' field. Select "Simple" from the 'Ledger Type' field. Select "Yes" from the 'Include Zero Charges' field. Click [Process]. Validate the Client Ledger Report page contains the service created in the previous steps. Click [Dismiss]. Scenario 2: Bells Notes Integration - Validate document routing for progress notes when a supervisor is not required Specific Setup: myAvatar must be configured to integrate with Bells Notes. Please note: this must be done by a Netsmart Associate. A user is defined [UserA] with the following: Access to Bells Notes with an existing client admitted (Client A) Associated practitioner enrolled in Medical Note (Practitioner A) Access to the 'My To Do's' widget on the HomeView Must be logged in as this user Document Routing is enabled for the 'Additional Progress Note Information (CWS21015)' form in 'Document Routing Setup'. A supervisor is NOT required. A Progress Notes form is configured and selected in the "Bells Notes" section of the 'CarePOV Management' form. Please note: this must be done by a Netsmart Associate. Steps Access the 'Scheduling Calendar' form. Right click in the 'Appointment Grid' and click [Add Appointment]. Enter the desired service code in the 'Service Code' field. Enter "Client A" in the 'Client' field. Select the desired value in the 'Episode Number' field. Validate the 'Practitioner' field is populated with "Practitioner A" Fill out all required fields. Click [Submit]. Validate successful submission. Validate the scheduled appointment is added to the 'Scheduling Calendar' form. Log into Bells Notes with existing login credentials. Click the "Agenda" section and verify the existence of the scheduled appointment from the 'Scheduling Calendar' form in myAvatar. Select the scheduled appointment and validate the summary of the scheduled appointment is displayed on the right side of the Bells Notes. Validate [Start Note] is displayed for the scheduled appointment on the right side of the Bells Notes. Click [Start Note] and verify the existence of the "Session Information" window. Fill out all required fields and select the desired note type. Validate user is able to start a note successfully. Verify the existence of "Client A" in the client header when note is started. Fill out all required fields and click [Sign Note]. Validate the "Sign Note" window pops up. Enter the desired value in the 'Pin' field and click [Sign]. Validate the warning messages "Note Signed Successfully" is displayed when note is signed off successfully. Validate the user is navigated to the "Agenda" page. Select the scheduled appointment and validate the appointment status is displayed as "Signed". Log into myAvatar as [UserA]. Navigate to the "My To Do's" widget. Locate the To Do just routed and click [Approve Document]. Validate the document is displayed with the progress note data, including an electronic signature at the bottom for "Practitioner A" as Author. Click [Accept]. Enter the password for "User A" in the 'Verify Password' dialog and click [OK]. Validate the To-Do is no longer displayed. Scenario 3: Bells Notes Integration - Accept a note via the "Sign" section of the 'My To Do's' widget 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 is configured and selected in the "Bells Notes" section of the 'CarePOV Management' form. Please note: this must be done by a Netsmart Associate. 'Progress Notes (Group and Individual)' must have document routing enabled. 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' widget on the HomeView. A client is enrolled in an existing episode (Client A). Steps Log into Bells Notes with existing login credentials for "User A". Search for "Client A". Click [Start Note] and verify the existence of the 'Session Information' window. Fill out all required fields and select the desired note type. Verify the existence of "Client A" in the client header when note is started. Fill out all required fields. Click [Sign Note]. Validate the Sign Note' dialog is displayed. Enter the pin for "User A" in the 'Pin' field and click [Sign]. Validate a message is displayed stating: Note Signed Successfully. Log into myAvatar as "User A". Navigate to the "My To Do's" widget. Select the "Sign" section. Validate the 'Search Documents' field contains the progress note document sent via Bells Notes for "Client A". Validate the 'Document' field contains the progress note data. Click [Accept]. Validate the 'Search Documents' field no longer contains the progress note document for "Client A". Validate the 'Accepted Documents' field contains the accepted progress note document for "Client A". Click [Sign All]. Enter the password for "User A" in the 'Verify Password' dialog and click [OK]. Validate the 'Accepted Documents' field no longer contains the progress note document for "Client A". Scenario 4: Bells Notes Integration - Accept a note via the "All" section of the 'My To Do's' widget 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 is configured and selected in the "Bells Notes" section of the 'CarePOV Management' form. Please note: this must be done by a Netsmart Associate. The 'Progress Notes (Group and Individual)' form must have document routing enabled. 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' widget on the HomeView. A client is enrolled in an existing episode (Client A). Steps Log into Bells Notes with existing login credentials for "User A". Search for "Client A". Click [Start Note] and verify the existence of the 'Session Information' window. Fill out all required fields and select the desired note type. Verify the existence of "Client A" in the client header when note is started. Fill out all required fields. Click [Sign Note]. Validate the Sign Note' dialog is displayed. Enter the pin for "User A" in the 'Pin' field and click [Sign]. Validate a message is displayed stating: Note Signed Successfully. Log into myAvatar as "User A". Navigate to the "My To Do's" widget. Select the "All" section. Validate a To-Do is displayed for the progress note sent via Bells Notes for "Client A". Click [Approve Document]. Validate the progress note data is displayed. Click [Accept]. Enter the password for "User A" in the 'Verify Password' field and click [OK]. Validate the To-Do is no longer displayed. Scenario 5: Bells Notes Integration - Validate document routing for progress notes when a supervisor is required Specific Setup: myAvatar must be configured to integrate with Bells Notes. Please note: this must be done by a Netsmart Associate. A user is defined [UserA] with the following: Access to Bells Notes with an existing client admitted (Client A) Associated practitioner enrolled in Medical Note (Practitioner A) Access to the 'My To Do's' widget on the HomeView Must be logged in as this user A user is defined [UserB] with the following: Associated practitioner enrolled in Medical Note (Practitioner B) Access to the 'My To Do's' widget on the HomeView Document Routing is enabled for the 'Additional Progress Note Information (CWS21015)' form in 'Document Routing Setup'. A supervisor is required. A Progress Notes form is configured and selected in the "Bells Notes" section of the 'CarePOV Management' form. Please note: this must be done by a Netsmart Associate. Steps Access the 'Scheduling Calendar' form. Right click in the 'Appointment Grid' and click [Add Appointment]. Enter the desired service code in the 'Service Code' field. Enter "Client A" in the 'Client' field. Select the desired value in the 'Episode Number' field. Validate the 'Practitioner' field is populated with "Practitioner A" Fill out all required fields. Click [Submit]. Validate successful submission. Validate the scheduled appointment is added to the 'Scheduling Calendar' form. Log into Bells Notes with existing login credentials. Click the "Agenda" section and verify the existence of the scheduled appointment from the 'Scheduling Calendar' form in myAvatar. Select the scheduled appointment and validate the summary of the scheduled appointment is displayed on the right side of the Bells Notes. Validate [Start Note] is displayed for the scheduled appointment on the right side of the Bells Notes. Click [Start Note] and verify the existence of the "Session Information" window. Fill out all required fields and select the desired note type. Validate user is able to start a note successfully. Verify the existence of "Client A" in the client header when note is started. Fill out all required fields and click [Sign Note]. Validate the "Sign Note" window pops up. Enter the desired value in the 'Pin' field and click [Sign]. Validate the warning messages "Note Signed Successfully" is displayed when note is signed off successfully. Validate the user is navigated to the "Agenda" page. Select the scheduled appointment and validate the appointment status is displayed as "Signed". Log into myAvatar as [UserB]. Navigate to the "My To Do's" widget. Locate the To Do just routed and click [Approve Document]. Validate the document is displayed with the progress note data, including an electronic signature at the bottom for "Practitioner A" as Author and "Practitioner B" as Supervisor. Click [Accept]. Enter the password for [UserB] in the 'Verify Password' dialog and click [OK]. Validate the To-Do is no longer displayed. Scenario 6: Bell Notes Integration - Validate progress notes when Document Routing is disabled Specific Setup: myAvatar must be configured to integrate with Bells Notes. Please note: this must be done by a Netsmart Associate. A user is defined [UserA] with the following: Access to Bells Notes with an existing client admitted (Client A) Associated practitioner Must be logged in as this user "Progress Notes" widget configured into myAvatar A Progress Notes form is configured and selected in the "Bells Notes" section of the 'CarePOV Management' form. Please note: this must be done by a Netsmart Associate. Document routing is disabled for the selected progress note form. Steps Access the 'Scheduling Calendar' form. Right click in the 'Appointment Grid' and click [Add Appointment]. Enter the desired service code in the 'Service Code' field. Enter "Client A" in the 'Client' field. Select the desired value in the 'Episode Number' field. Fill out all required fields. Click [Submit]. Validate successful submission. Validate the scheduled appointment is added to the 'Scheduling Calendar' form. Log into Bells Notes with existing login credentials. Click the "Agenda" section and verify the existence of the scheduled appointment from the 'Scheduling Calendar' form in myAvatar. Select the scheduled appointment and validate the summary of the scheduled appointment is displayed on the right side of the Bells Notes. Validate [Start Note] is displayed for the scheduled appointment on the right side of the Bells Notes. Click [Start Note] and verify the existence of the "Session Information" window. Fill out all required fields and select the desired note type. Validate user is able to start a note successfully. Verify the existence of "Client A" in the client header when note is started. Fill out all required fields and click [Sign Note]. Validate the "Sign Note" window pops up. Enter the desired value in the 'Pin' field and click [Sign]. Validate the warning messages "Note Signed Successfully" is displayed when note is signed off successfully. Validate the user is navigated to the "Agenda" page. Select the scheduled appointment and validate the appointment status is displayed as "Signed". Log into myAvatar as [UserA]. Select "Client A" and select "Progress Notes" widget. Verify the Progress Note status is final on the signed off appointment with document routing disabled.	Topics • Document Routing • Progress Notes • CareFabric
Update 71 Summary \| Details 'Recent Vitals' widget template Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following: Vitals Entry Scenario 1: Vitals Entry - validate vitals in the 'Vital Signs' widget Specific Setup: A client is enrolled in an existing episode (Client A). The 'Vital Signs' widget is on the HomeView. Steps Select "Client A" and access the 'Vitals Entry' form. Select "Add" from the 'Add/Edit/Delete Vital Sign' field. Enter the desired date in the 'Date' field. Enter the desired time in the 'Time' field. Select "No" from the 'Refused Vitals' field. Populate all remaining vital sign fields. Click [Submit] and [No]. Select "Client A" and navigate to the 'Vital Signs' widget. Validate the vitals entered in the previous steps are displayed. Scenario 2: Validate the 'Preferred Weight For Displays/Reports' Registry Setting Specific Setup: The 'Recent Vitals' widget and 'Vital Signs' widget must be added to the HomeView of the logged in user. A client is enrolled in an existing episode (Client A). Steps Access the 'Registry Settings' form Set the 'Limit Registry Settings to the Following Search Criteria' field to "preferred weight for displays/reports". Click [View Registry Settings]. Set the 'Registry Setting Value' field to "1". Click [Submit], [OK] and [No]. Select "Client A" and access the 'Vitals Entry' form. Select "Add" from the 'Add/Edit/Delete Vital Sign' field. Enter the desired date in the 'Date' field. Enter the desired time in the 'Time' field. Select "No" from the 'Refused Vitals' field. Enter the desired value in the 'Weight' field. Populate all remaining vital sign fields. Click [Submit] and [No]. Select "Client A" and navigate to the 'Vital Signs' widget. Validate the vitals entered in the previous steps are displayed. Validate the 'Weight' field is displayed in lbs. Navigate to the 'Recent Vitals' widget. Validate the vitals entered in the previous steps are displayed. Validate the 'Weight' field is displayed in lbs. Access the 'Vitals Entry' form. Select the 'Vitals Reports' section. Click [Start Date T] and [End Date T]. Select "All" in the 'Vital Sign(s) for Report' field. Set the 'Start Time' to the desired time. Click [End Time Current Time] and [View Report]. Validate the vitals entered in the previous steps are displayed. Validate the 'Weight' field is displayed in lbs. Close the report and the form. Access the 'Registry Settings' form Set the 'Limit Registry Settings to the Following Search Criteria' field to "preferred weight for displays/reports". Click [View Registry Settings]. Set the 'Registry Setting Value' field to "2". Click [Submit], [OK] and [No]. Select "Client A" and navigate to the 'Vital Signs' widget. Validate the vitals entered in the previous steps are displayed. Validate the 'Weight' field is displayed in kgs. Navigate to the 'Recent Vitals' widget. Validate the vitals entered in the previous steps are displayed. Validate the 'Weight' field is displayed in kgs. Access the 'Vitals Entry' form. Select the 'Vitals Reports' section. Click [Start Date T] and [End Date T]. Select "All" in the 'Vital Sign(s) for Report' field. Set the 'Start Time' to the desired time. Click [End Time Current Time] and [View Report]. Validate the vitals entered in the previous steps are displayed. Validate the 'Weight' field is displayed in kgs. Close the report and the form. Scenario 3: Progress Notes - Validate the 'Recent Vitals' on demand widget template Specific Setup: The 'Enable Templates On Demand for SQL Widgets' registry setting must be set to "Y". The 'Recent Vitals' and 'Progress Notes' widgets must be on the HomeView for the user in 'View Definition'. A client must be enrolled in an existing episode (Client A). Steps Select "Client A" and access the 'Vitals Entry' form. Select "Add" from the 'Add/Edit/Delete Vital Sign' field. Enter the desired date in the 'Date' field. Enter the desired time in the 'Time' field. Select "No" from the 'Refused Vitals' field. Populate all remaining vital sign fields. Click [Submit] and [No]. Access the 'Progress Notes (Group and Individual)' form. Select any value from the 'Select Episode' field. Select any value from the 'Progress Note For' field. Select any value from the 'Note Type' field. Click [Template Icon]. Click [Widget Templates]. Click [Client] and [Recent Vitals]. Validate the 'Notes Field' contains the vitals entered in the previous steps. Complete the required fields. Select "Draft" from the 'Draft/Final' field. Click [Submit Note]. Close the form. Select "Client A" and navigate to the 'Progress Notes' widget. Validate the note displays with the vitals entered in the previous steps. Scenario 4: Treatment Plan - Validate the 'Recent Vitals' on demand widget template Specific Setup: The 'Enable Templates On Demand for SQL Widgets' registry setting must be set to "Y". User must have the 'Recent Vitals' widget assigned to the HomeView in 'View Definition'. A user must have a console widget configured for the 'Treatment Plan' in the 'Console Widget Configuration' form. A user must have a view configured containing the 'Treatment Plan' console widget and 'Console Widget Viewer' (View A). A client must be enrolled in an existing episode and have a problem on file (Client A). Steps Select "Client A" and access the 'Vitals Entry' form. Select "Add" from the 'Add/Edit/Delete Vital Sign' field. Enter the desired date in the 'Date' field. Enter the desired time in the 'Time' field. Select "No" from the 'Refused Vitals' field. Populate all remaining vital sign fields. Click [Submit] and [No]. Access the 'Treatment Plan' form. Enter the desired date in the 'Plan Date' field. Select the desired value in the 'Plan Type' field. Select "Draft" in the 'Treatment Plan Status' field. Select the problem to include in the 'Problems' field. Click [Template Icon] next to the 'Strengths' field. Click [Widget Templates]. Click [Client] and [Recent Vitals]. Validate the 'Strengths' field contains the vitals entered in the previous steps. Click [Launch Plan]. Populate any required and desired fields. Click [Return To Plan] and [OK]. Submit the form. Select "Client A" and navigate to "View A". Validate the 'Treatment Plan' console widget contains the draft treatment plan filed in the previous steps and select it. Click [View]. Validate the 'Console Widget Viewer' displays the draft treatment plan details filed in the previous steps. Scenario 5: Vitals Entry - validate vitals in the 'Recent Vitals' widget Specific Setup: The 'Recent Vitals' widget must be added to the HomeView of the logged in user. A client is enrolled in an existing episode (Client A). Steps Select "Client A" and access the 'Vitals Entry' form. Select "Add" from the 'Add/Edit/Delete Vital Sign' field. Enter the desired date in the 'Date' field. Enter the desired time in the 'Time' field. Select "No" from the 'Refused Vitals' field. Populate all remaining vital sign fields. Click [Submit] and [No]. Select "Client A" and navigate to the 'Recent Vitals' widget. Validate the vitals entered in the previous steps are displayed.	Topics • Vitals Entry • Registry Settings • Progress Notes • Treatment Plan
Update 74 Summary \| Details Vitals Entry Web Service Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following: Vitals Entry Scenario 1: Vitals Entry - Field Validations Specific Setup: Select an existing client or admit a new client for the test. Steps Open the "Vitals Entry" form. Select the client identified as the test client. Set the "Height (cm)" field to "182.8". Validate the "Height (ft in)" field contains "6 0.0". Set "Weight (lbs)" to "132.8". Validate the "Weight (kgs)" contains "60.2". Set "Weight (kgs)" to "60.2". Validate the "Weight (lbs)" is "132.7". Populate all the other fields on the form. Submit the form to file data. Remain in the form. Elect to "Edit" an existing vital sign record. Click "Select Vital Sign" button. Select a row to edit. Validate data displays as it was data entered. Remain in the form. Elect to "Delete" an existing vital sign record. Click "Select Vital Sign" button. Select a row to delete. Validate row is removed. Scenario 2: Vitals Entry Web Services Steps Using the preferred web service tool, file the ClientVitals web service to add Weight data to the vitals data. To do this set the readingCode to "Wtlb" and the readingValue to "132.8". File the web service. Open the "Vitals Entry" form. Validate the "Weight (lbs)" field is set to "132.8" Validate the "Weight (kgs)" field is set to "60.2". Using the preferred web service tool, file the ClientVitals web service to add Weight data to the vitals data. To do this set the readingCode to "WtKg" and the readingValue to "60.2". File the web service. Open the "Vitals Entry" form. Validate the "Weight (lbs)" field is set to "132.7" Validate the "Weight (kgs)" field is set to "60.2". Using the preferred web service tool, file the ClientVitals web service to add temperature data to the vitals data. To do this set the readingCode to "TF" and the readingValue to "98.5". File the web service. Open the "Vitals Entry" form. Validate the "Temp (F)" field is set to "98.5" Validate the "Temp (C)" field is set to "36.9". Using the preferred web service tool, file the ClientVitals web service to add blood pressure data to the vitals data. To do this set up 3 CWSVitalSign group, where the first group has vitalSignCodeKey set to "1", readingCode to "BPS" and the readingValue to "80". The 2nd CWSVitalSign group, has vitalSignCodeKey set to "2", readingCode to "BPD" and the readingValue to "100". The 23rd CWSVitalSign group, has vitalSignCodeKey set to "3", readingCode to "POSIT" and the readingValue to "1". File the web service. Open the "Vitals Entry" form. Validate the "Blood Pressure Systolic" field is set to "80" Validate the "Blood Pressure Diastolic" field is set to "100". Validate the "Sitting - Position" radio button is checked.	Topics • Vitals Entry • Web Services
2021 Update 78 Summary \| Details Progress Notes - Add-On Service Code Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following: Progress Note Corrections Scenario 1: Progress Note Corrections - Revert a Final Progress note to a Draft status - Delete Service 'No'. Specific Setup: A client must be enrolled in an active episode with a final progress note filed (Client A). Progress note must be associated with a service (New Service note) with an Add-On Service. User must have the Progress Note widget associated with a view in the 'View Definition' form. Steps Access the 'Progress Note Corrections' form. Enter "Client A" in the 'Client ID' field. Select "Episode # 1" in the 'Episode Number' field. Click [End Date T]. Select the note from the setup in the 'Select Note to Correct' field. Click [OK]. Select "Revert Final Note to Draft" in the 'Correction Action' field. Select any value in the 'Reason for Correction' field. Enter any value in the 'Comments' field. Select "No" in the 'Delete Service' field. Click [Submit] and [No]. Select "Client A" and navigate to the 'Progress Note' widget. Validate the widget contains the draft note. Select "Client A" and access the 'Progress Notes (Group and Individual)' form. Select "Episode # 1" in the 'Select Episode' field. Select the note from before in the 'Select Draft Note to Edit' field. Validate the 'Add-On Service' and 'Select Add-On Services' fields are enabled. Enter a new value in the 'Service Charge Code' field. Validate the previous value is not present in the 'Add-On Service' field. Select any value in the 'Add On-Service' field. Populate any required and desired fields. Click [Save Add-On Service]. Select "Final" in the 'Draft/Final' field. Click [File Note]. Close the form. Access the 'Client Ledger' form. Select "Client A" in the 'Client ID' field. Select "Episode" in the 'Claim/Episode/All Episodes' field. Select "Episode # 1" in the 'Episode Number' field. Select "Crystal" in the 'Ledger Type' field. Click [Process]. Validate the report contains the new values in the 'Service Description' field. Close the report and the form. Scenario 2: Progress Note Corrections - Revert a Final Progress note to a Draft status - Delete Service 'Yes'. Specific Setup: A client must be enrolled in an active episode with a final progress note filed (Client A). Progress note must be associated with a service (New Service note) with an Add-On Service. User must have the Progress Note widget associated with a view in the 'View Definition' form. Steps Access the 'Progress Note Corrections' form. Enter "Client A" in the 'Client ID' field. Select "Episode # 1" in the 'Episode Number' field. Click [End Date T]. Select the note from the setup in the 'Select Note to Correct' field. Click [OK]. Select "Revert Final Note to Draft" in the 'Correction Action' field. Select any value in the 'Reason for Correction' field. Enter any value in the 'Comments' field. Select "Yes" in the 'Delete Service' field. Click [Submit] and [No]. Select "Client A" and navigate to the 'Progress Note' widget. Validate the widget contains the draft Independent note. Validate the Add-On Service is still present. Access the 'Client Ledger' form. Select "Client A" in the 'Client ID' field. Select "Episode" in the 'Claim/Episode/All Episodes' field. Select "Episode # 1" in the 'Episode Number' field. Select "Crystal" in the 'Ledger Type' field. Click [Process]. Validate the service code is not present. Close the report and the form. Select "Client A" and access the 'Progress Notes (Group and Individual)' form. Select "Episode # 1" in the 'Select Episode' field. Select the note from before in the 'Select Draft Note to Edit' field. Select the service in the 'Select Add-On Service Entry to Edit/Remove' field. Click [Remove Add-On Service]. Select "Final" in the 'Draft/Final' field. Click [File Note]. Close the form. Select "Client A" and navigate to the 'Progress Note' widget. Validate the Add-On Service is no longer present.	Topics • Progress Notes • Progress Note Corrections
2021 Update 99 Summary \| Details Progress Note Corrections - Voided Progress Notes Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following: Progress Note Corrections Client Charge Input Ambulatory Progress Notes Individual Cash Posting (PM) Scenario 1: 'Progress Notes (Group and Individual)' - File a new service note and delete the service in the 'Progress Note Corrections' form Specific Setup: A Charge Reversal Code must be defined in 'Set System Defaults'. A Client must be enrolled in an existing episode (Client A). Steps Access the 'Progress Notes (Group and Individual)' form. Enter "Client A" in the 'Select Client' field. Select any value from the 'Select Episode' field. Select "New Service" from the 'Progress Notes For' field. Select any value that does not require a co-sign from the 'Note Type' field. Enter any value in the 'Notes Field' field. Enter the current date in the 'Date Of Service' field. Enter any service charge code in the 'Service Charge Code' field. Select "Final" from the 'Draft/Final' field. Click [File Note]. Validate a "Progress Notes" dialog is displayed stating: Note Filed. Click [OK]. Close the form. Validate a "Confirm" dialog is displayed stating: Are you sure you want to close the form? Click [Yes]. Access the 'Client Ledger' form. Enter "Client A" in the 'Client ID' field. Select "All Episodes" from the 'Claim/Episode/All Episodes' field. Select "Simple" from the 'Ledger Type' field. Select "Yes" from the 'Include Zero Charges' field. Click [Process]. Verify the 'Client Ledger Report' is displayed. Validate the 'Client Ledger Report' displays the service created in the previous steps. Click [Dismiss]. Validate a "Form Return" dialog is displayed stating: Processing report has completed. Do you wish to return to form? Click [No]. Access the 'Progress Note Corrections' form. Enter "Client A" in the 'Client ID' field. Select the episode that the New Service note was created for from the 'Episode Number' field. Click [Select Note to Correct]. Verify the "Select Note To Correct" dialog is displayed. Select the New Service note created in the previous steps. Click [OK]. Select "Void Progress Note" from the 'Correction Action' field. Select any value from the 'Reason for Correction' field. Enter any value in the 'Comments' field. Select "Yes" from the 'Delete Service' field. Click [Submit]. Validate a "Form Return" dialog is displayed stating: Submitting has completed. Do you wish to return to form? Click [No]. Access the 'Client Ledger' form. Enter "Client A" in the 'Client ID' field. Select "All Episodes" from the 'Claim/Episode/All Episodes' field. Select "Simple" from the 'Ledger Type' field. Select "Yes" from the 'Include Zero Charges' field. Click [Process]. Verify the 'Client Ledger Report' is displayed. Validate the 'Client Ledger Report' no longer displays the service created in the previous steps. Click [Dismiss]. Validate a "Form Return" dialog is displayed stating: Processing report has completed. Do you wish to return to form? Click [No]. Create a report using the 'SYSTEM.progress_note_corrections' table. Validate the note is present. Close the report. Create a report using the 'SYSTEM.cw_notes_voided' table. Validate the note is present. Close the report. Scenario 2: 'Progress Notes (Group and Individual)' - File an existing appointment note and delete the service in the 'Progress Note Corrections' form Specific Setup: A Charge Reversal Code must be defined in 'Set System Defaults'. A Client must be enrolled in an existing episode and must have an existing appointment scheduled (Client A). Steps Access the 'Progress Notes (Group and Individual)' form. Enter "Client A" in the 'Select Client' field. Select any value from the 'Select Episode' field. Select "Existing Appointment" from the 'Progress Notes For' field. Select the existing appointment in the 'Note Addresses Which Existing Service/Appointment' field. Select any value that does not require a co-sign from the 'Note Type' field. Enter any value in the 'Notes Field' field. Select "Final" from the 'Draft/Final' field. Click [File Note]. Validate a "Progress Notes" dialog is displayed stating: Note Filed. Click [OK]. Close the form. Validate a "Confirm" dialog is displayed stating: Are you sure you want to close the form? Click [Yes]. Access the 'Client Ledger' form. Enter "Client A" in the 'Client ID' field. Select "All Episodes" from the 'Claim/Episode/All Episodes' field. Select "Simple" from the 'Ledger Type' field. Select "Yes" from the 'Include Zero Charges' field. Click [Process]. Verify the 'Client Ledger Report' is displayed. Validate the 'Client Ledger Report' displays the service created in the previous steps. Click [Dismiss]. Validate a "Form Return" dialog is displayed stating: Processing report has completed. Do you wish to return to form? Click [No]. Access the 'Progress Note Corrections' form. Enter "Client A" in the 'Client ID' field. Select the episode that the Existing Appointment note was created for from the 'Episode Number' field. Click [Select Note to Correct]. Verify the "Select Note To Correct" dialog is displayed. Select "Note A". Click [OK]. Select "Void Progress Note" from the 'Correction Action' field. Select any value from the 'Reason for Correction' field. Enter any value in the 'Comments' field. Select "Yes" from the 'Delete Service' field. Click [Submit]. Validate a "Form Return" dialog is displayed stating: Submitting has completed. Do you wish to return to form? Click [No]. Access the 'Client Ledger' form. Enter "Client A" in the 'Client ID' field. Select "All Episodes" from the 'Claim/Episode/All Episodes' field. Select "Simple" from the 'Ledger Type' field. Select "Yes" from the 'Include Zero Charges' field. Click [Process]. Verify the 'Client Ledger Report' is displayed. Validate the 'Client Ledger Report' no longer displays the service created in the previous steps. Click [Dismiss]. Validate a "Form Return" dialog is displayed stating: Processing report has completed. Do you wish to return to form? Click [No]. Create a report using the 'SYSTEM.progress_note_corrections' table. Validate the note is present. Close the report. Create a report using the 'SYSTEM.cw_notes_voided' table. Validate the note is present. Close the report. Scenario 3: 'Progress Notes (Group and Individual)' - File an existing service note and delete the service in the 'Progress Note Corrections' form Specific Setup: A Charge Reversal Code must be defined in 'Set System Defaults'. A Client must be enrolled in an existing episode and must have an existing service (Client A). Steps Access the 'Progress Notes (Group and Individual)' form. Enter "Client A" in the 'Select Client' field. Select any value from the 'Select Episode' field. Select "Existing Service" from the 'Progress Notes For' field. Select the existing service in the 'Note Addresses Which Existing Service/Appointment' field. Select any value that does not require a co-sign from the 'Note Type' field. Enter any value in the 'Notes Field' field. Select "Final" from the 'Draft/Final' field. Click [File Note]. Validate a 'Progress Notes' dialog is displayed stating: "Note Filed." Click [OK]. Close the form. Validate a 'Confirm' dialog is displayed stating: "Are you sure you want to close the form?" Click [Yes]. Access the 'Client Ledger' form. Enter "Client A" in the 'Client ID' field. Select "All Episodes" from the 'Claim/Episode/All Episodes' field. Select "Simple" from the 'Ledger Type' field. Select "Yes" from the 'Include Zero Charges' field. Click [Process]. Verify the 'Client Ledger Report' is displayed. Validate the 'Client Ledger Report' displays the service created in the previous steps. Click [Dismiss]. Validate a 'Form Return' dialog is displayed stating: "Processing report has completed. Do you wish to return to form?" Click [No]. Access the 'Progress Note Corrections' form. Enter "Client A" in the 'Client ID' field. Select the episode that the Existing Service note was created for from the 'Episode Number' field. Click [Select Note to Correct]. Verify the "Select Note To Correct" dialog is displayed. Select "Note A" from the 'Select Note To Correct' dialog. Click [OK]. Select "Void Progress Note" from the 'Correction Action' field. Select any value from the 'Reason for Correction' field. Enter any value in the 'Comments' field. Select "Yes" from the 'Delete Service' field. Click [Submit]. Validate a 'Form Return' dialog is displayed stating: "Submitting has completed. Do you wish to return to form?" Click [No]. Access the 'Client Ledger' form. Enter "Client A" in the 'Client ID' field. Select "All Episodes" from the 'Claim/Episode/All Episodes' field. Select "Simple" from the 'Ledger Type' field. Select "Yes" from the 'Include Zero Charges' field. Click [Process]. Verify the 'Client Ledger Report' is displayed. Validate the 'Client Ledger Report' no longer displays the service created in the previous steps. Click [Dismiss]. Validate a 'Form Return' dialog is displayed stating: "Processing report has completed. Do you wish to return to form?" Click [No]. Create a report using the 'SYSTEM.progress_note_corrections' table. Validate the note is present. Close the report. Create a report using the 'SYSTEM.cw_notes_voided' table. Validate the note is present. Close the report. Scenario 4: 'Progress Notes (Group and Individual)' - Finalize an independent note and revert it to 'Draft' in 'Progress Note Corrections' form Specific Setup: The Registry Setting 'Avatar CWS->Progress Notes->Progress Notes (Group and Individual)->->->Limit Note Types By Practitioner Category' must be set to "Y". The Registry Setting 'Avatar CWS->Progress Notes->Progress Notes (Group and Individual)->->->Default Staff Associated With Current Login User' must be set to "Y". The dictionary 'Note Type' must be defined for the practitioner category of the logged in user. Client A must be enrolled in an existing episode. Steps Access the 'Progress Notes (Group and Individual)' form. Enter "Client A" in the 'Select Client' field. Select "Episode 1" in the 'Select Episode' field. Select "Independent Note" in the 'Progress Note For' field. Select the note type associated to the practitioner category of the logged in user in the 'Note Type' field. Enter any value in the 'Notes Field' field. Validate the 'Practitioner' field contains the practitioner associated to the logged in user. Select "Final" in the 'Draft/Final' field. Click [File Note]. Validate a "Progress Notes" message is displayed stating: Note Filed. Click [OK] and close the form. Access the 'Progress Note Corrections' form. Enter "Client A" in the 'Client ID' field. Select "Episode 1" in the 'Episode Number' field. Click [Select Note to Correct]. Verify the 'Select Note To Correct' dialog is displayed. Select the independent note created in the previous steps in the 'Select Note To Correct' dialog. Click [OK]. Select "Revert Final Note to Draft" in the 'Correction Action' field. Select any value in the 'Reason for Correction' field. Enter any value in the 'Comments' field. Click [Submit]. Validate a "Form Return" message is displayed stating: Submitting has completed. Do you wish to return to form? Click [No]. Access the 'Progress Notes (Group and Individual)' form. Enter "Client A" in the 'Select Client' field. Select "Episode 1" in the 'Select Episode' field. Select the draft independent note corrected in the previous steps in the 'Select Draft Note To Edit' field. Validate the 'Progress Notes For' field contains "Independent Note". Validate the 'Note Type' field contains the note type associated to the practitioner category of the logged in user. Validate the 'Notes Field' field contains the value entered in the previous steps. Validate the 'Practitioner' field contains the practitioner associated to the logged in user. Select "Final" in the 'Draft/Final' field. Click [File Note]. Validate a "Progress Notes" message is displayed stating: Note Filed. Click [OK] and close the form. Scenario 5: 'Progress Note Corrections' - Validate an error when trying to void a note and delete a service when cash posting has been completed Specific Setup: A client must be enrolled in an existing episode (Client A). Steps Access the 'Client Charge Input' form. Enter "Client A" in the 'Client ID' field. Enter the desired date in the 'Date of Service' field. Enter any value in the 'Service Code' field. Enter any value in the 'Practitioner' field. Click [Submit]. Validate a 'Form Return' dialog stating: "Client Charge Input had completed. Do you wish to return to form?" Click [No]. Access the 'Close Charges' form. Select "Close Charges" in the 'Liability Update Or Close Charges' field. Enter today's date in the 'Thru Date' field. Select "Individual" in the 'Individual, All Or Interim Batch Cycle' field. Enter "Client A" in the 'Client ID' field. Select the episode from the previous steps in the 'Episode Number' field. Click [Submit]. Access the 'Individual Cash Posting' form. Enter "Client A" in the 'Client' field. Select "Episode" in the 'Post By' field. Select the episode from the previous steps in the 'Episode' field. Click [Select Item(s) to Post Against]. Select the entry from the previous steps and click [OK]. Validate an 'Information' dialog stating: "Current Balance for this Guarantor is 95.00" and click [OK]. Enter "95.00" in the 'Dollar Amount To Be Posted' field. Enter any value in the 'Posting Date' field. Enter any value in the 'Date of Receipt' field. Select any value in the 'Posting Code' field. Click [Update Temporary File], [OK], and [Submit]. Validate an 'Individual Cash Posting' dialog stating: "Filing will permanently update the client's billing information. Are you sure that you want to continue filing?" Click [Yes]. Close the form. Access the 'Progress Notes (Group and Individual)' form. Enter "Client A" in the 'Select Client' field. Select any value from the 'Select Episode' field. Select "Existing Service" from the 'Progress Notes For' field. Select the note associated to the existing service (Note A) from the 'Note Addresses Which Existing Service/Appointment' field. Select any value that does not require a co-sign from the 'Note Type' field. Enter any value in the 'Notes Field' field. Select "Final" from the 'Draft/Final' field. Click [File Note]. Validate a 'Progress Notes' dialog is displayed stating: "Note Filed." Click [OK]. Close the form. Validate a 'Confirm' dialog is displayed stating: "Are you sure you want to close the form?" Click [Yes]. Access the 'Progress Note Corrections' form. Enter "Client A" in the 'Client ID' field. Select the episode that the Existing Service note was created for from the 'Episode Number' field. Click [Select Note to Correct]. Verify the "Select Note To Correct" dialog is displayed. Select "Note A" from the 'Select Note To Correct' dialog. Click [OK]. Select "Void Progress Note" from the 'Correction Action' field. Select any value from the 'Reason for Correction' field. Enter any value in the 'Comments' field. Select "Yes" from the 'Delete Service' field. Click [Submit]. Validate a 'Filing Error' dialog stating: "Payment activity is present for this service. Use the 'Delete Service' form to delete it." Click [OK]. Close the form. Create a report using the 'SYSTEM.progress_note_corrections' table. Validate the note is not present. Close the report. Create a report using the 'SYSTEM.cw_notes_voided' table. Validate the note is not present. Close the report.	Topics • Progress Notes • Progress Note Corrections