Avatar CWS 2022 Monthly Release 2022.02.00 Acceptance Tests

Last updated
Save as PDF

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 Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following: Treatment Plan Scenario 1: Treatment Plan - Add a Problem, Goal, Objective, and Intervention 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 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 50 Summary \| Details 'Treatment Plan' field 'Status (Problem List)' is updated to default a specific value. Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following: Treatment Plan 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: Registry Settings (PM) 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 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 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: Admission Vitals Entry Registry Settings (PM) 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: Admission 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 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 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 Treatment Plan 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 HomeView - my Clients Treatment Plan 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: Document Routing Setup (PM) 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 Treatment Plan 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: Admission 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