2024 Update installation
Scenario 1: Validate Upgrading Avatar CWS 2023 to 2024 is successful when 2023.04.00 is loaded
Steps
- Open the "Product Updates" form.
- Select the appropriate [Namespace] from the Application dropdown list
- Click [Select Update/Customization Pack].
- Browse to the location for the updates and select the Update 1.
- Click [OK] on the "File Upload Complete" window.
- Click [Review Update/Customization Pack Contents].
- Verify Update 1 is included.
- Click [Install Update/Customization Pack].
- Click [OK] when the install completes.
- Click [Close Form].
|
Topics
• Upgrade
|
Treatment Plan Web Service - Problem of "Other"
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
- Treatment Plan
- Create New Treatment Plan
Scenario 1: Treatment Plan Web Service - Add Treatment Plan
Specific Setup:
- A client is enrolled in an existing episode (Client A).
- The 'SS Treatment Plan Client Scrolling Free Text 1' field is added to the 'Treatment Plan' form via 'Site Specific Section Modeling'. (Field #52021)
- Create a non episodic Treatment Plan using the "Create New Treatment Plan" form.
Steps
- 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.
- Enter the desired value in the 'CurrentStatus' field.
- Enter "52021" in the 'SSFreeTextScrolling' - 'FieldNumber' field.
- Enter a value containing more than 50 characters in the 'SSFreeTextScrolling' - 'FieldValue' field.
- Populate any other desired fields.
- Enter "Client A" in the 'ClientID' field.
- Enter "1" in the 'EpisodeNumber' field.
- Enter "CWS60000" in the 'OptionID' field.
- Click [Run].
- Validate that 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 the 'Treatment Plan' form.
- Select the record filed in the previous steps and click [Edit].
- Validate all data filed in the previous steps is displayed.
- Validate the 'SS Treatment Plan Client Scrolling Free Text 1' field contains the value filed in the previous steps.
- Close the form.
- 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.
- Enter the desired value in the 'CurrentStatus' field.
- Enter "52021" in the 'SSFreeTextScrolling' - 'FieldNumber' field.
- Enter a value containing more than 50 characters in the 'SSFreeTextScrolling' - 'FieldValue' field.
- Populate any other desired fields.
- Enter "Client A" in the 'ClientID' field.
- Enter "0" in the 'EpisodeNumber' field.
- Enter "CWS60008" in the 'OptionID' field.
- Click [Run].
- Validate that 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 the 'Treatment Plan Number 8' form.
- Select the record filed in the previous steps and click [Edit].
- Validate all data filed in the previous steps is displayed.
- Validate the 'SS Treatment Plan Client Scrolling Free Text 1' field contains the value filed in the previous steps.
- Close the form.
Scenario 2: Treatment Plan Web Service - Edit Treatment Plan
Specific Setup:
- A client is enrolled in an existing episode and has a 'Treatment Plan' on file (Client A).
- The 'SS Treatment Plan Client Scrolling Free Text 1' field is added to the 'Treatment Plan' form via 'Site Specific Section Modeling'. (Field #52021)
- Episodic and Non Episodic Treatment Plans must be on file for (Client A)
Steps
- 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.
- Enter the desired value in the 'CurrentStatus' field.
- Enter "52021" in the 'SSFreeTextScrolling' - 'FieldNumber' field.
- Enter a value containing more than 50 characters in the 'SSFreeTextScrolling' - 'FieldValue' field.
- Populate any other desired fields.
- 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 that 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 the 'Treatment Plan' form.
- Select the record filed in the previous steps and click [Edit].
- Validate all data filed in the previous steps is displayed.
- Validate the 'SS Treatment Plan Client Scrolling Free Text 1' field contains the value filed in the previous steps.
- Close the form.
|
Topics
• Treatment Plan
• Web Services
|
Vitals Quick Action - Flags and warnings
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
- Quick Actions Page
- CWS Vital Signs Setup
Scenario 1: Validate the 'Quick Vitals' quick action
Specific Setup:
- A client must be enrolled in an existing episode (Client A)
- 'Quick Vitals' Quick Action must be assigned to the user in the 'NX View Definition' form.
- This is for Avatar NX systems only.
- A client must be over the age of 18 and must be enrolled in an existing episode (Client B).
- A client must be between the ages of 12-18 and must be enrolled in an existing episode (Client C).
- Using the form "CWS Vital Signs Setup"
- Enter in rules or warnings to enforce, such as Blood Pressure Systolic must be in the range of 112-120 for clients who are over the age of 18.
- Enter a rule that clients of all ages must have a temperature in Fahrenheit degrees of 98.0 - 99.0.
Steps
- Select "Client A" and access the 'Client Dashboard'.
- Navigate to the 'Quick Vitals' quick action.
- Click [Quick Vitals - Add].
- Validate "Diastolic" is spelled correctly.
- Enter the desired value in the 'Systolic' field.
- Validate the 'Diastolic' and 'Position' fields are required.
- Populate the desired fields and click [Save].
- Validate the 'Quick Vitals' quick action contains "Vitals last entered: [current date and time]".
- Click [Quick Vitals - Add].
- Populate the desired fields and click [Save].
- Validate the 'Quick Vitals' quick action contains "Vitals last entered: [current date and time]".
- Click [Quick Vitals - Add].
- Populate the desired fields and click [Save].
- Validate the 'Quick Vitals' quick action contains "Vitals last entered: [current date and time]".
- Click [Close].
- Select "Client B" and access the 'Client Dashboard'.
- Navigate to the "Quick Vitals" quick action.
- In the quick action, enter values that will cause warnings because fields are over/under limits set in "CWS Vital Signs Setup" form.
- Validate the fields whose values are outside of the limits set display the data value in red text and that warning messages indicating that fields are outside of the limits when you attempt to "Save" the data.
- Access the 'Vitals Entry' form.
- Select the 'Vitals Report' field.
- Click [Start Date Y].
- Click [Start Date T].
- Enter any value in the 'Start Time' field.
- Enter any value in the 'End Time' field.
- Select "All" in the 'Vital Sign(s) for Report' field.
- Click [View Report].
- Validate the report contains the entries filed in the previous steps.
- Click [Close Report].
- Close the form.
Assessment Mapping - Treatment Plans mapped to Progress Notes (Group and Individual)
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
- Assessment Mapping
- Admission (Outpatient)
- Clinical Assessment
- Treatment Plan
- Flag Assessment Forms
- Assessment Code Mapping
- Progress Notes (Group and Individual)
Scenario 1: Treatment Plan - validate 'Assessment Mapping'
Specific Setup:
- Must have a user defined assessment for testing with a 'Strengths' field (Assessment A).
- A client must be enrolled in an existing episode (Client A).
- Using the "Flag Assessment" form
- Flag the "Progress Notes (Group and Individual)" form as a form that can be mapped.
- Using the "Assessment Mapping" form
- Map the "Treatment Plan" form fields "Strengths", "Weaknesses", "Discharge Plan" to fields on the "Progress Notes (Group and Individual)" form.
Steps
- Access the 'Assessment Mapping' form.
- Select "Treatment Plan" in the 'Map Code for Use In' field.
- Select "Assessment A" in the 'Form to Map' field.
- Select "Strength" in the 'Map To' field.
- Select "Strengths" in the 'Assessment Field' field.
- Click [Save Mapping] and [OK].
- Close the form.
- Select "Client A" and access "Assessment A".
- Populate all required and desired fields.
- Enter "Test Strengths" in the 'Strengths' field.
- Click [Submit].
- Select "Client A" and access the 'Treatment Plan' form.
- Populate all required and desired fields.
- Validate the 'Strength' field contains "Test Strengths".
- Click [Submit].
- Select "Client A" and access "Assessment A".
- Click [Add] to add a new record.
- Populate all required and desired fields.
- Enter "New Test Strengths" in the 'Strengths' field.
- Click [Submit].
- Select "Client A" and access the 'Treatment Plan' form.
- Click [Add] to add a new record.
- Populate all required and desired fields.
- Validate the 'Strength' field contains "New Test Strengths".
- Click [Submit].
- Select "Client A" and open the "Progress Notes (Group and Individual)" form.
- Create a new progress note making sure to populate the fields that are mapped to the "Treatment Plan" form through "Assessment Mapping".
- Complete the progress note.
- Select "Client A" and open the "Treatment Plan" form.
- Validate the "Strengths", "Weaknesses" and "Discharge Plan" fields are populated with the values from the fields mapped to "Progress Notes (Group and Individual)" form.
|
Topics
• NX
• Quick Actions
• Treatment Plan
• Progress Notes
• Assessment Mapping
|
Medication Inventory Management
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
- Finalize
- Medical Note
- Medication Inventory Management
- Service Code Upload Process
- Lot Number Manager
- Adjust Inventory
- Client Health Maintenance
Scenario 1: Medical Note - Inventory Management Disabled - Full Note Workflow
Specific Setup:
- The 'Avatar CWS->Medication Inventory Management->->->->Enable Medication Inventory Management' registry setting must be set to "N".
- Please log out of the application and log back in after completing the above configuration.
- Two 'Vaccination/Immunization' procedure-type service codes must be configured in the 'Service Codes' form. (Immunization A) (Immunization B)
- A 'Medication Administration' procedure-type service code must be configured in the 'Service Codes' form. (Medication A)
- A procedure-type service code that is not a "Vaccination/Immunization" nor "Medication Administration" must be configured in the 'Service Codes' form. (Procedure A)
- An outpatient program configured as a 'Primary Care' program in the 'Program Maintenance' form must exist. (Program A)
- A client must have an active episode in "Program A". (Client A)
Steps
- Search for and select "Client A" and access 'Medical Note'.
- Click [Add Note] and create a new "Primary Care" Note.
- In the Facesheet:
- Select the ‘Vitals’ section and enter Blood Pressure, Height, Weight, and Temperature information, click [Save], and pull to note.
- Select the ‘Immunization’ section and enter a “Historical Immunization” record for yesterday.
- Select the ‘Allergies’ section and enter an allergy to “Shellfish” and pull to note.
- Select the ‘Document’ tab.
- Complete the 'Chief Complaint', 'HPI', 'Physical Exam' and 'Diagnosis' sections as necessary.
- Select the ‘Immunizations’ section.
- Expand the ‘Immunization History’ section and validate the Historical Immunization Record for the precious day is correctly shown.
- Click [Add] and then [Order Immunizations], select "Immunization A" from the 'Immunization Search' field and click [Continue].
- Fill in any required fields and click [Order].
- Click [Add] and then [Order Immunizations], select "Immunization B" from the 'Immunization Search' field and click [Continue].
- Fill in any required fields and click [Administer].
- Validate "Immunization A" is listed under the 'Pending Administrations' section and " Immunization B" is listed under the 'Immunization History' section.
- Populate all required fields and click [Save].
- Select the ‘Procedures’ section and click [Add].
- Select "Procedure A" from the 'Procedure' field.
- Select "Complete" from the 'Status' field.
- Set the 'Completion Date' field to "Today's Date.
- Populate any remaining required fields and click [Save].
- Validate "Procedure A" is listed under the 'Current Procedures' Section.
- Select the ‘In Office Administrations’ section.
- Click [Add], select "Medication A" from the 'In-Office Administrations Search' field and click [Continue].
- Populate all required fields and click [Administer].
- Populate all required fields and click [Save].
- Click [Add], select "Medication A" from the 'In-Office Administrations Search' field and click [Continue].
- Populate all required fields and click [Order].
- Validate "Medication A" is listed under the 'Pending Administrations' section and " Medication A" is listed under the 'Administration History' section.
- Select the ‘Finalize’ tab.
- Populate all required fields and click [Generate Note].
- Validate the ‘Note Summary’ is displayed and contains the appropriate information:
- The populated sections of the 'Facesheet' tab that were pulled into the note. (Allergies and Vitals)
- The required and populated sections of the 'Document' tab. (Chief Complaint, HPI, Physical Exam, Diagnosis)
- The 'Immunizations' section shows "Immunization A" in the 'Ordered (Pending)' section and "Immunization B" in the 'Administered In-Office' section.
- The 'Procedures' section shows "Procedure A" as complete.
- The 'In-Office Administrations' section shows "Medication A" in the 'Ordered (Pending)' section and "Medication B" in the 'Administered In-Office' section.
- Click [Sign Off] validate the Document is displayed and click [Accept], set the ‘Password’ field to the appropriate value and click [Verify].
Scenario 2: Medical Note - Inventory Management Enabled - In-Office Administration - Full Note Workflow
Specific Setup:
- The 'Avatar CWS->Medication Inventory Management->->->->Enable Medication Inventory Management' registry setting must be set to "Y".
- There must be at least one value in the Other CWS Tabled Files ‘(74101) Inventory Location’ dictionary. (Location A)
- Please log out of the application and log back in after completing the above configuration.
- A generic 'Evaluation Management' service code must be configured in the 'Service Codes' form. (Service Code A)
- A 'Medication Administration' procedure-type service code must be configured in the 'Service Codes' form. (Medication A)
- "Medication A" must have a template defined in the 'Medication Inventory Management' form. (Template A)
- In the 'Medication Inventory Management' form inventory for "Template A" must be received to "Location A". (Inventory A)
- An outpatient program must exist. (Program A)
- In the 'Assign Services To Program' section of the 'Program Maintenance' form "Service Code A" must be associated to "Program A".
- A client must have an active episode associated with "Program A". (Client A)
Steps
- Search for and select "Client A" and navigate to the 'Medical Note'.
- Click [Add Note].
- Create a 'Psychiatry' note.
- Select the ‘Document’ tab.
- Populate all required sections in the 'Document' tab.
- Click the 'In-Office Administration' section.
- Click [Add] and select "Medication A" from the 'In-Office Administration Search' field.
- Validate the 'Dose', 'Unit', and 'Route' fields automatically populate based on the entries made in "Template A"
- Fill in any remaining required fields and click [Order].
- Validate the 'Pending Administrations' field contains a row for "Medication A".
- Click the ellipses under the 'Action' column for "Medication A" and click [Administer].
- Validate, in the first section, the 'Dose', 'Unit', and 'Route' fields are correctly populated with the updated values and that all fields are disabled.
- Click the 'Lot Number Search' button and validate the 'Lot Number Manager' dialog is launched.
- Select the row for "Inventory A" and click [Select].
- Validate the 'Lot Number', 'Manufacturer', 'Expiration Date', and 'NDC" are all correctly populated and disabled.
- Fill in any remaining required fields and click [Save].
- Expand the 'Administration History' field and validate it contains a row for "Medication A" and that all columns are accurate.
- Click the ellipses under the 'Action' column for "Medication A" and click [Document Reaction].
- Select any value for the 'Reaction' field and click [Save].
- Click the ellipses under the 'Action' column for "Medication A" and click [View Details].
- Validation the 'Reaction' field contains the correct value and click [Close]
- Select the ‘Finalize’ tab.
- Populate all required fields and click [Generate Note].
- Validate the ‘Note Summary’ is displayed and contains the appropriate information and click [Sign Off].
- Validate the Document is displayed and click [Accept], set the ‘Password’ field to the appropriate value and click [Verify].
Scenario 3: Medical Note - Administering a medication order under the 'In-Office Administration' section when 'Inventory Management' is disabled - Pediatric
Specific Setup:
- The 'Avatar CWS->Medication Inventory Management->->->->Enable Medication Inventory Management' registry setting must be set to "N".
- Please log out of the application and log back in after completing the above configuration.
- A 'Medication Administration' procedure-type service code must be configured in the 'Service Codes' form. (Medication A)
- An outpatient program that is configured in the 'Program Maintenance' form to be a 'Primary Care' program must exist. (Program A)
- A client must have an active episode in "Program A". (Client A)
Steps
- Search for and select "Client A" and navigate to the 'Medical Note'.
- Click [Add Note] and create a new 'Primary Care' note.
- Select the 'Document' tab.
- Navigate to the 'Diagnosis' section.
- Add a new diagnosis for "Client A".
- Navigate to the 'In-Office Administrations' section.
- Click [Add] and select "Medication A" from the 'In-Office Administrations Search' field.
- Validate the new diagnosis is listed under the 'Diagnosis' dropdown and select it.
- Fill in any remaining required fields and click [Order].
- Validate the 'Pending Administrations' field contains a row for "Medication A"
- Click the ellipses under the 'Action' column for "Medication A" and click [Administer].
- Validate, in the first section, the 'Dose', 'Unit', and 'Route' fields are correctly populated and that all fields are disabled.
- Fill in all required fields and click [Save].
- Validate the 'Pending Administrations' field no longer contains a row for "Medication A".
- Expand the 'Administration History' field and validate it contains a row for "Medication A" and that all columns are accurate.
Scenario 4: Medical Note - Administering a medication under the 'Pending Administration' sub-section of 'In Office Administration' and voiding the medications under the 'Administration History' section
Specific Setup:
- The 'Avatar CWS->Medication Inventory Management->->->->Enable Medication Inventory Management' registry setting must be set to "N".
- Please log out of the application and log back in after completing the above configuration.
- Two 'Medication Administration' procedure-type service codes must be configured in the 'Service Codes' form. (Medication A)(Medication B)
- An Outpatient program must exist. (Program A)
- A client must have an active episode in "Program A". (Client A)
Steps
- Search for and select "Client A" and navigate to the 'Medical Note'.
- Click [Add Note] and create a new note.
- Select the 'Document' tab and then navigate to the 'In-Office Administration' section.
- Click [Add], select "Medication A" from the 'In-Office Administration Search' field and click [Continue].
- Populate all required fields and click [Order].
- Validate the 'Pending Administrations' field contains a row for "Medication A".
- Click [Add], select "Medication B" from the 'In-Office Administration Search' field and click [Continue].
- Populate all required fields and click [Order].
- Validate the 'Pending Administrations' field contains a row for "Medication A" and one for "Medication B".
- Click the ellipses under the 'Action' column for "Medication A" and click [Administer].
- Populate all required fields and click [Save].
- Expand the 'Administration History' field and validate it contains a row for "Medication A" and that all columns are accurate.
- Click the ellipses under the 'Action' column for "Medication B" and click [Refuse].
- Set the 'Refusal Reason' field to any value and click [Save].
- Validate the 'Administration History' field contains a row for "Medication A" and the status shows as "Administered".
- Validate the 'Administration History' field contains a row for "Medication B" and the status shows as "Refused".
- Click the ellipses under the 'Action' column for "Medication B" and click [Void].
- Set the 'Comments' field to any value and click [Save].
- Validate the 'Administration History' field contains a row for "Medication B" and the status shows as "Voided".
Scenario 5: Medical Note - Edit a medication that is listed under the 'Pending Medications' sub-section in the 'In-Office Administrations' section
Specific Setup:
- The 'Avatar CWS->Medication Inventory Management->->->->Enable Medication Inventory Management' registry setting must be set to "Y".
- There must be at least one value in the Other CWS Tabled Files ‘(74101) Inventory Location’ dictionary. (Location A)
- Please log out of the application and log back in after completing the above configuration.
- A 'Medication Administration' procedure-type service code must be configured in the 'Service Codes' form. (Medication A)
- "Medication A" must have a template defined in the 'Medication Inventory Management' form. (Template A)
- In the 'Medication Inventory Management' form, inventory for "Template A" must be received to "Location A". (Inventory A)
- An outpatient program must exist. (Program A)
- A client must have an active episode in "Program A". (Client A)
Steps
- Search for and select "Client A" and navigate to the 'Medical Note'.
- Click [Add Note] and create a new note.
- Select the 'Document' tab and then navigate to the 'In-Office Administrations' section.
- Click [Add] and select "Medication A" from the 'In-Office Administrations Search' field.
- Validate the 'Dose', 'Unit', and 'Route' fields automatically populate based on the entries made in "Template A".
- Fill in any remaining required fields and click [Order].
- Validate the 'Pending Administrations' field contains a row for "Medication A".
- Click the ellipses under the 'Action' column for "Medication A" and click [Edit].
- Set the 'Dose' and 'Unit' fields to any other values and click [Update].
- Validate the row for "Medication A" in the 'Pending Administrations field reflects the updated values.
- Click the ellipses under the 'Action' column for "Medication A" and click [Administer].
- Validate, in the first section, the 'Dose', 'Unit', and 'Route' fields are correctly populated with the updated values and that all fields are disabled.
- Click the 'Lot Number Search' button and validate the 'Lot Number Manager' dialog is launched.
- Select the row for "Inventory A" and click [Select].
- Validate the 'Lot Number', 'Manufacturer', 'Expiration Date', and 'NDC" are all correctly populated and disabled.
- Fill in any remaining required fields and click [Save].
- Validate the 'Pending Administrations' field no longer contains a row for "Medication A".
- Expand the 'Administration History' field and validate it contains a row for "Medication A" and that all columns are accurate.
Scenario 6: Medical Note - Order an In-Office Administration as "Provider" - Edit/Administer as "Nurse"
Specific Setup:
- The 'Avatar CWS->Medication Inventory Management->->->->Enable Medication Inventory Management' registry setting must be set to "Y".
- There must be at least one value in the Other CWS Tabled Files ‘(74101) Inventory Location’ dictionary. (Location A)
- Please log out of the application and log back in after completing the above configuration.
- A 'Medication Administration' procedure-type service code must be configured in the 'Service Codes' form. (Medication A)
- "Medication A" must have a template defined in the 'Medication Inventory Management' form. (Template A)
- In the 'Medication Inventory Management' form, inventory for "Template A" must be received to "Location A". (Inventory A)
- An outpatient program must exist. (Program A)
- A client must have an active episode in "Program A". (Client A)
- Two users must exist. (User A) (User B).
- "User A" who is configured as a "Provider".
- "User B" who is configured as a "Nurse".
Steps
- Log into the application as "User A".
- Search for and select "Client A" and navigate to 'Medical Note'.
- Click [Add Note] and create a new note.
- Select the 'Document' tab and then navigate to the 'In-Office Administrations' section.
- Click [Add], search for and select "Medication A" from the 'In-Office Administrations Search' field, and click [Continue].
- Validate the 'Dose', 'Unit', and 'Route' fields automatically populate based on the entries made in "Template A".
- Populate any remaining required fields and click [Order].
- Validate the 'Pending Administrations' field contains a row for "Medication A" and click [Save Draft].
- Log out of the application and then log in as "User B".
- Search for and select "Client A" and navigate to the 'Medical Note'.
- Click [Select Note] and select the newly created note.
- Select the 'Document' tab and then navigate to the 'In-Office Administrations' section.
- Validate the 'Pending Administrations' field contains a row for "Medication A".
- Click the ellipses under the 'Action' column for "Medication A" and click [Administer].
- Validate, in the first section, the 'Dose', 'Unit', and 'Route' fields are correctly populated and that all fields are disabled.
- Validate the 'Entered By' and 'Ordered By' fields contain "User A" and the 'Administered By' field contains "User B".
- Click the 'Lot Number Search' button and validate the 'Lot Number Manager' dialog is launched.
- Select the row for "Inventory A" and click [Select].
- Validate the 'Lot Number', 'Manufacturer', 'Expiration Date', and 'NDC" are all correctly populated and disabled.
- Populate all remaining required fields and click [Save].
- Validate the 'Pending Administrations' field no longer contains a row for "Medication A".
- Expand the 'Administration History' field and validate it contains a row for "Medication A" and that all columns are accurate.
- Log out of the application and then log in as "User A".
- Search for and select "Client A" and navigate to the 'Medical Note'.
- Click [Select Note] and select the newly created note.
- Select the 'Document' tab and then navigate to the 'In-Office Administrations' section.
- Validate the 'Pending Administrations' field no longer contains a row for "Medication A".
- Expand the 'Administration History' field and validate it contains a row for "Medication A" and that all columns are accurate.
Scenario 7: Medical Note - Immunizations - Edit; Cancel; Grouping
Specific Setup:
- The 'Avatar CWS->Medication Inventory Management->->->->Enable Medication Inventory Management' registry setting must be set to "Y".
- There must be at least one value in the Other CWS Tabled Files ‘(74101) Inventory Location’ dictionary. (Location A)
- Please log out of the application and log back in after completing the above configuration.
- Two 'Vaccination/Immunization' procedure type service codes must be configured in the 'Service Codes' form. (Immunization A)(Immunization B).
- "Immunization A" must have a template defined in the 'Medication Inventory Management' form. (Template A)
- In the 'Medication Inventory Management' form, inventory for "Template A" must be received to "Location A" and the 'Manufacturer of Vaccine (MVX)' and 'Vaccine Code (CVX)' fields must be populated. (Inventory A)
- An outpatient program configured as a 'Primary Care' program in the 'Program Maintenance' form must exist. (Program A)
- A client must have an active episode in "Program A". (Client A)
Steps
- Search for and select "Client A" and navigate to the 'Medical Note'.
- Click [Add Note] and create a new 'Primary Care' note.
- Select the 'Document' tab and then navigate to the 'Immunizations' section.
- Click [Add] and then [Order Immunizations], select "Immunization A" from the 'Immunization Search' field and click [Continue].
- Fill in any required fields and click [Order].
- Click [Add] and then [Order Immunizations], select "Immunization B" from the 'Immunization Search' field and click [Continue].
- Fill in any required fields and click [Order].
- Click the ellipses under the 'Action' column for "Immunization A" and click [Edit].
- Change the values for the 'Dose' and 'Route' fields and click [Update].
- Click the ellipses under the 'Action' column for "Immunization B" and click [Cancel].
- Validate the 'Cancel Pending Administration' dialog appears and contains: "Are you sure you want to cancel this pending administration? Canceling this will permanently remove this pending administration."
- Click [Continue], populate the 'Comments' field and click [Save].
- Validate the 'Pending Immunizations' section only contains a row for "Immunization A".
- Click the ellipses under the 'Action' column for "Immunization A" and click [Administer].
- Validate, in the first section, the 'Dose', 'Unit', and 'Route' fields are correctly populated according to the edited values, and that all fields are disabled.
- Select "Facility" from the 'Provided By' field.
- Click the 'Lot Number Search' button and validate the 'Lot Number Manager' dialog is launched.
- Select the row for "Inventory A" and click [Select].
- Validate all fields in the "Administration Details' section are populated correctly.
- Populate any remaining required fields and click [Save].
- Expand the 'Immunization History' field and validate it contains a row for "Immunization A" and all columns are correctly populated.
- Click [Add] and then [Order Immunizations], select "Immunization A" from the 'Immunization Search' field and click [Continue].
- Populate any required fields and click [Administer].
- Set the 'Provided By' field to "Facility".
- Click the 'Lot Number Search' button and validate the 'Lot Number Manager' dialog is launched.
- Select the row for "Inventory A" and click [Select].
- Validate all fields in the "Administration Details' section are populated correctly.
- Populate any remaining required fields and click [Save].
- Click [Group By Vaccine] in the 'Immunization History' section.
- Validate that the 2 immunization administrations for "Immunization A" are grouped together.
Scenario 8: Medical Note - Order/Administer an Immunization in Single Workflow - Void Administration - Reconcile Inventory
Specific Setup:
- The 'Avatar CWS->Medication Inventory Management->->->->Enable Medication Inventory Management' registry setting must be set to "Y".
- There must be at least one value in the Other CWS Tabled Files ‘(74101) Inventory Location’ dictionary. (Location A)
- Please log out of the application and log back in after completing the above configuration.
- A 'Vaccination/Immunization' procedure-type service code must be configured in the 'Service Codes' form. (Immunization A)
- "Immunization A" must have a template defined in the 'Medication Inventory Management' form. (Template A)
- In the 'Medication Inventory Management' form, inventory for "Template A" must be received to "Location A" and the 'Manufacturer of Vaccine (MVX)' and 'Vaccine Code (CVX) fields but be populated. (Inventory A)
- An outpatient program that is configured to be a 'Primary Care' program in the 'Program Maintenance' form must exist. (Program A)
- A client must have an active episode in "Program A". (Client A)
Steps
- Search for and select "Client A" and navigate to the 'Medical Note'.
- Click [Add Note] and create a new 'Primary Care' note.
- Select the 'Document' tab and then navigate to the 'Immunizations' section.
- Click [Add], select "Immunization A" from the 'Immunization Search' field and click [Continue].
- Validate the 'Dose', 'Unit', and 'Route' fields automatically populate based on the entries made in "Template A".
- Fill in any remaining required fields and click [Administer].
- Select "Facility" from the 'Provided By' field.
- Click the 'Lot Number Search' button and validate the 'Lot Number Manager' dialog is launched.
- Select the row for "Inventory A" and click [Select].
- Validate the fields in the 'Administration Details' section are all accurately populated.
- Fill in any remaining required fields and click [Save].
- Validate the 'Pending Administrations' field does not contain a row for "Immunization A".
- Expand the 'Immunization History' field and validate it contains a row for "Immunization A" and that all columns are accurate.
- Click the ellipses under the 'Action' column for "Immunization A" and click [Void].
- Populate the 'Comments' field and click [Save].
- Validate the 'Immunization History' field still contains a row for "Immunization A" and that the 'Status' column shows "Voided".
- Access the 'Medication Inventory Management' form.
- Click [Adjust Inventory] and select the row for "Inventory A" from the 'Select Row' field.
- Validate that the 'Event Log' field contains a row for the previously given administration.
- Validate the 'Current Balance' is correctly calculated.
- Select 'Add to inventory' from the 'Event Type' field.
- Set the 'Quantity' field, such that when added to the current balance, the total is equal to the amount originally added to inventory.
- Click [Submit].
Scenario 9: Medical Note - Complete a Pending Immunization After a Note Is Finalized - Pediatric Full Workflow
Specific Setup:
- The 'Avatar CWS->Medication Inventory Management->->->->Enable Medication Inventory Management' registry setting must be set to "Y".
- The Other CWS Tabled Files '(74101) Inventory Location’ dictionary must contain at least one value. (Location A)
- Please log out of the application and log back in after completing the above configuration.
- Two "Vaccination/Immunization" procedure-type service codes must be configured in the 'Service Codes' form. (Medication A and Medication B)
- "Medication A" and "Medication B" must have a template defined in the 'Medication Inventory Management' form. (Template A and Template B)
- In the 'Medication Inventory Management' form inventory for "Template A" and "Template B" must be received to "Location A". (Inventory A and Inventory B)
- An outpatient program must exist that is configured as a "Primary Care Program". (Program A)
- A client must have an active episode that is associated with "Program A" and is a pediatric patient. (Client A)
Steps
- Search for and select "Client A" and navigate to the 'Medical Note'.
- Click [Add Note].
- Create a 'Primary Care' note.
- Select the ‘Document’ tab.
- Select ‘Immunizations’.
- Click [Add] and select "Medication A" from the 'Immunization Search' field.
- Validate the 'Dose', 'Unit', and 'Route' fields automatically populate based on the entries made in "Template A".
- Fill in any remaining required fields and click [Order].
- Validate the 'Pending Administrations' field contains a row for "Medication A"
- Click [Add] and select "Medication B" from the 'Immunization Search' field.
- Validate the 'Dose', 'Unit', and 'Route' fields automatically populate based on the entries made in "Template B".
- Fill in any remaining required fields and click [Administer].
- Validate, in the first section, the 'Dose', 'Unit', and 'Route' fields are correctly populated with the updated values and that all fields are disabled.
- Select "Yes" for the 'Consent Obtained' radio button.
- Select "Not VFC eligible" from the 'VFC Eligibility Code' field.
- Select "Facility" from the 'Provided By' field.
- Click the 'Lot Number Search' button and validate the 'Lot Number Manager' dialog is launched.
- Select the row for "Inventory B" and click [Select].
- Validate the 'Lot Number', 'Manufacturer', 'Expiration Date', and 'NDC' are all correctly populated and disabled.
- Fill in any remaining required fields and click [Save].
- Expand the 'Immunization History' field and validate it contains a row for "Medication B" and that all columns are accurate.
- Populate any remaining required sections in the 'Document' tab.
- Select the ‘Finalize’ tab.
- Populate all required fields and click [Generate Note].
- Validate the ‘Note Summary’ is displayed and contains the appropriate information and click [Sign Off].
- Validate the 'Progress Note' is displayed and click [Accept], set the ‘Password’ field to the appropriate value, and click [Verify].
- Refresh Medical Note.
- Click [Add Note].
- Create a 'Primary Care' note.
- Select the 'Document' tab and navigate to the 'Immunization' section.
- Validate the 'Pending Administrations' field contains a row for "Medication A"
- Click the ellipses under the 'Action' column for "Medication A" and click [Administer].
- Validate, in the first section, the 'Dose', 'Unit', and 'Route' fields are correctly populated with the updated values and that all fields are disabled.
- Select "Yes" for the 'Consent Obtained' field.
- Select "Not VFC eligible" from the 'VFC Eligibility Code' field.
- Select "Facility" from the 'Provided By' field.
- Click the 'Lot Number Search' button and validate the 'Lot Number Manager' dialog is launched.
- Select the row for "Inventory A" and click [Select].
- Validate the 'Lot Number', 'Manufacturer', 'Expiration Date', and 'NDC' are all correctly populated and disabled.
- Populate all remaining required fields and click [Save].
- Expand the 'Immunization History' field and validate it contains a row for "Medication A" and that all columns are accurate.
Scenario 10: Medical Note - Administering an immunization when 'Inventory Management' is disabled
Specific Setup:
- The 'Avatar CWS->Medication Inventory Management->->->->Enable Medication Inventory Management' registry setting must be set to "N".
- Please log out of the application and log back in after completing the above configuration.
- A 'Vaccination/Immunization' procedure-type service code must be configured in the 'Service Codes' form. (Immunization A)
- An outpatient program configured as a 'Primary Care' program in the 'Program Maintenance' form must exist. (Program A)
- A client must have an active episode in "Program A". (Client A)
Steps
- Search for and select "Client A" and navigate to the 'Medical Note'.
- Click [Add Note] and create a new 'Primary Care' note.
- Select the 'Document' tab and then navigate to the 'Immunizations' section.
- Click [Add] and then [Order Immunizations], select "Immunization A" from the 'Immunization Search' field and click [Continue].
- Fill in any required fields and click [Administer].
- Select "Facility" from the 'Provided By' field.
- Fill in any remaining required fields and click [Save].
- Expand the 'Immunization History' field and validate it contains a row for "Immunization A" and all columns are correctly populated.
- Complete any remaining required sections in the 'Document' tab.
- Select the 'Finalize' tab and click [End Face-to-Face Time].
- Choose one of the options in the 'CPT Code Selected' field and click [Generate Note].
- Validate the 'Note Summary' field shows the correct information.
- Set the 'Completion Status' field to "Completed" and sign off on the note.
Scenario 11: Medical Note - Service Code Upload - Medication Administration and Vaccine/Immunization Procedure Types
Specific Setup:
- A service code upload file must exist that contains two new service codes, one with "Vaccination/Immunization" and one with "Medication Administration" selected in the 'Procedure Type' field, and must be placed on the server where the application resides. (File A)
Steps
- Access the 'Service Code Upload Process' form.
- Click [Select File].
- Select and open "File A".
- Select "Compile" in the 'Compile or Post' field.
- Select "Yes" in the 'Override Existing Service Codes' field.
- Click [Submit].
- Validate a "Compiled completed" message is displayed and click [OK].
- Select "Post" in the 'Compile or Post' field and click [Submit].
- Validate a "Post completed" message is displayed and click [OK].
- Access the 'Service Codes' form.
- Select "Edit" in the 'Add New or Edit Existing' field.
- Search for and select the first service code created and ensure that "Yes" is selected in the 'Is This Service A Procedure' field and that "Vaccination/Immunization" is selected in the 'Procedure Type' field.
- Search for and select the second service code created and ensure that "Medication Administration" is selected in the 'Procedure Type' field.
Scenario 12: Medical Note - Receiving new inventory - Administering an In-Office Administration - Entering a 'Reaction'
Specific Setup:
- The 'Avatar CWS->Medication Inventory Management->->->->Enable Medication Inventory Management' registry setting must be set to "Y".
- There must be at least one value in the Other CWS Tabled Files ‘(74101) Inventory Location’ dictionary. (Location A)
- Please log out of the application and log back in after completing the above configuration.
- A 'Medication Administration' procedure-type service code must be configured in the 'Service Codes' form. (Medication A)
- An outpatient program must exist. (Program A)
- A client must have an active episode in "Program A". (Client A)
Steps
- Access the 'Medication Inventory Management' form.
- Click [Template Definition] and select "Add New" from the 'Select Template Definition' field.
- Set the 'Service Code' field to "Medication A".
- Populate any remaining required fields and click [Submit].
- Click [Medication Definition] and select the previously made template from the 'Select Template' field.
- Select "Location A" from the 'Inventory Location' field.
- Set the 'Lot #' field to "72293".
- Set the 'Expiration Date' field to a future date.
- Set the 'Container Size' field to 50.
- Populate any remaining required fields and click [Submit].
- Click [Adjust Inventory] and set the 'Lot #' field to "72293"
- Validate the new medication definition is shown in the 'Inventory Items' field.
- Select the new medication definition from the 'Select Row' field.
- Select "Add to inventory" from the 'Event Type' field.
- Validate "Add (A)" is selected from the 'Impact' field and that the field is disabled.
- Set the 'Quantity' field to "50" and click [Submit] and close the form.
- Search for and select "Client A" and navigate to the 'Medical Note'.
- Click [Add Note] and create a new note.
- Select the 'Document' tab and then navigate to the 'In-Office Administrations' section.
- Click [Add], search for and select "Medication A" from the 'In-Office Administrations Search' field and click [Continue].
- Validate the 'Dose', 'Unit', and 'Route' fields automatically populate based on selections made in the "Template Definition" section of the 'Medication Inventory Management' form.
- Fill in any remaining required fields and click [Administer].
- Click the 'Lot Number Search' button and validate the 'Lot Number Manager' dialog is launched.
- Select the row for new medication definition and click [Select].
- Validate the 'Administration Details' section is correctly populated based on selections made in the "Medication Definition" section of the 'Medication Inventory Management' form.
- Populate any remaining required fields and click [Save].
- Expand the 'Administration History' field and validate it contains a row for "Medication A" and that all columns are accurate.
- Click the ellipses under the 'Action' column for "Medication A" and click [Document Reaction].
- Set the 'Reaction' field to any value and click [Save].
- Click the ellipses under the 'Action' column for "Medication A" and click [View Details].
- Validate the details are read-only, that all fields are correctly populated and then click [Cancel].
- Access the 'Medication Inventory Management' form.
- Click [Adjust Inventory] and select the new medication definition from the 'Select Row' field.
- Validate that the 'Event Log' field contains a row for the previously given administration.
- Validate the 'Current Balance' is correctly calculated.
Scenario 13: Medical Note - Refuse medications that are listed in under the 'Pending Medications' sub-section of the 'In-Office Administrations' section. Confirm details in Progress Note.
Specific Setup:
- A 'Medication Administration' procedure-type service code must be configured in the 'Service Codes' form. (Medication A)
- An outpatient program must exist. (Program A)
- A client must have an active episode associated with "Program A". (Client A)
Steps
- Search for and select "Client A" and navigate to the 'Medical Note'.
- Click [Add Note] and create a new note.
- Select the 'Document' tab and then navigate to the 'In-Office Administrations' section.
- Click [Add], select "Medication A" from the 'In-Office Administrations Search' field and click [Continue].
- Populate any required fields and click [Order].
- Validate the 'Pending Administrations' field contains a row for "Medication A".
- Click the ellipses under the 'Action' column for "Medication A" and click [Refuse].
- Select any value from the 'Refused Reason' field and click [Save].
- Validate the 'Pending Administrations' field no longer contains a row for "Medication A".
- Expand the 'Administration History' field and validate it contains a row for "Medication A" and that "Refused" is shown in the 'Status' column.
- Click the ellipses under the 'Action' column for "Medication A" and click [View Details].
- Validate the 'Refused Reason' field matches to what was previously selected and click [Cancel].
- Select the 'Finalize' tab and click [Generate Note].
- Validate that the 'Note Summary' field contains a section for In-Office Administrations and "Medication A" is listed and shows as "Refused".
Scenario 14: Medical Note - Cancel a medication that is listed in under the 'Pending Medications' sub-section of the 'In-Office Administrations' section.
Specific Setup:
- A 'Medication Administration' procedure-type service code must be configured in the 'Service Codes' form. (Medication A)
- An outpatient program must exist. (Program A)
- A client must have an active episode associated with "Program A". (Client A)
Steps
- Search for and select "Client A" and navigate to the 'Medical Note'.
- Click [Add Note] and create a new note.
- Select the 'Document' tab and then navigate to the 'In-Office Administration' section.
- Click [Add], search for and select "Medication A" from the 'In-Office Administration Search' field and click [Continue].
- Populate any required fields and click [Order].
- Validate that a row for "Medication A" is listed in the 'Pending Immunizations' section.
- Click the ellipses under the 'Action' column for "Medication A" and click [Cancel].
- Validate the 'Cancel Pending Administration' dialog contains "Are you sure you want to cancel this pending administration? Canceling this will permanently remove this pending administration." and click [Continue].
- Populate the 'Comments' field and click [Save].
- Validate the 'Pending Administrations' field no longer contains a row for "Medication A".
- Expand the 'Administration History' field and validate it does not contain a row for "Medication A".
- Click [Select Note] and then click [Delete] for the newly created note.
- Validate the 'Delete Note' dialog contains "Are you sure you want to delete this draft note? Please make sure to void any administrations or procedures completed during the visit, as necessary."
- Click [Delete Note] and validate a 'Start' button now shows for the newly created note.
Scenario 15: Medical Note - Complete In-Office Administration - Delete Note - Void Administration - Reconcile Inventory
Specific Setup:
- The 'Avatar CWS->Medication Inventory Management->->->->Enable Medication Inventory Management' registry setting must be set to "Y".
- There must be at least one value in the Other CWS Tabled Files ‘(74101) Inventory Location’ dictionary. (Location A)
- Please log out of the application and log back in after completing the above configuration.
- A 'Medication Administration' procedure-type service code must be configured in the 'Service Codes' form. (Medication A)
- "Medication A" must have a template defined in the 'Medication Inventory Management' form. (Template A)
- In the 'Medication Inventory Management' form, inventory for "Template A" must be received to "Location A". (Inventory A)
- An outpatient program must exist. (Program A)
- A client must have an active episode in "Program A". (Client A)
Steps
- Search for and select "Client A" and navigate to the 'Medical Note'.
- Click [Add Note] and create a new note.
- Select the 'Document' tab and then navigate to the 'In-Office Administrations' section.
- Click [Add], search for and select "Medication A" from the 'In-Office Administrations Search' field and click [Continue].
- Validate the 'Dose', 'Unit', and 'Route' fields automatically populate based on the entries made in "Template A".
- Fill in any remaining required fields and click [Administer].
- Click the 'Lot Number Search' button and validate the 'Lot Number Manager' dialog is launched.
- Select the row for "Inventory A" and click [Select].
- Populate any remaining required fields and click [Save].
- Expand the 'Administration History' field and validate it contains a row for "Medication A" and that all columns are accurate.
- Click [Select Note] and then click [Delete] for the newly created note.
- Validate the 'Delete Note' dialog contains "Are you sure you want to delete this draft note? Please make sure to void any administrations or procedures completed during the visit, as necessary.".
- Click [Delete Note] and validate an error message is displayed at the top of the medical note stating "Completed procedures/administrations that updated medication inventory must be voided first before the visit can be deleted.".
- Select the 'Document' tab and then navigate to the 'In-Office Administrations' section.
- Expand the 'Administration History' field, click the ellipses under the 'Action' column for "Medication A" and click [Void].
- Populate the 'Comments' field and click [Save].
- Validate a passive alert is displayed at the top of the document tab stating "Void Administration: Voiding an administration does not update inventory. Please reconcile your inventory as needed."
- Validate the 'Status' column shows "Voided" for "Medication A".
- Click [Select Note] and then click [Delete] for the newly created note.
- Validate the 'Delete Note' dialog contains "Are you sure you want to delete this draft note? Please make sure to void any administrations or procedures completed during the visit, as necessary." and click [Delete Note].
- Access the 'Medication Inventory Management' form.
- Click [Adjust Inventory] and select the row for "Inventory A" from the 'Select Row' field.
- Validate that the 'Event Log' field contains a row for the previously given administration.
- Validate the 'Current Balance' is correctly calculated.
- Select 'Add to inventory' from the 'Event Type' field.
- Set the 'Quantity' field, such that when added to the current balance, the new balance will be equal to the amount prior to the administration and click [Submit].
Scenario 16: Medical Note - Administering a Pediatric Immunization when 'Inventory Management' is enabled
Specific Setup:
- The 'Avatar CWS->Medication Inventory Management->->->->Enable Medication Inventory Management' registry setting must be set to "Y".
- There must be at least one value in the Other CWS Tabled Files ‘(74101) Inventory Location’ dictionary. (Location A)
- Please log out of the application and log back in after completing the above configuration.
- Two 'Vaccination/Immunization' procedure-type service codes must be configured in the 'Service Codes' form. (Immunization A) (Immunization B)
- "Immunization A" must have a template defined in the 'Medication Inventory Management' form. (Template A)
- In the 'Medication Inventory Management' form, inventory for "Template A" must be received to "Location A" and the 'Manufacturer of Vaccine (MVX)' and 'Vaccine Code (CVX)' fields must be populated. (Inventory A)
- An outpatient program configured as a 'Primary Care' program in the 'Program Maintenance' form must exist. (Program A)
- A client must have an active episode in "Program A". (Client A)
- "Client A" must be under the age of 19.
Steps
- Search for and select "Client A" and navigate to the 'Medical Note'.
- Navigate to the 'Immunizations' section of the Facesheet.
- Click [Add] and then [Historical Immunization Record].
- Select any immunization listed in the 'Historical Immunization Record Search' field.
- Fill out any required fields and click [Save].
- Validate the 'Immunization History' section contains a row for the new historical immunization record.
- Click [Add Note] and create a 'Primary Care' note.
- Select the 'Document' tab and then navigate to the 'Immunization' section.
- Click [Add] and then [Order Immunizations], select "Immunization A" from the 'Immunizations Search' field and click [Continue].
- Validate the 'Dose', 'Unit', and 'Route' fields automatically populate based on the entries made in "Template A".
- Fill in any remaining required fields and click [Order].
- Validate the 'Pending Immunizations' field contains a row for "Immunization A"
- Click the ellipses under the 'Action' column for "Immunization A" and click [Edit].
- Clear the 'Diagnosis' field, enter in a new value and click [Update].
- Click the ellipses under the 'Action' column for "Immunization A" and click [Administer].
- Validate the 'Diagnosis' field contains the updated value.
- Validate the following fields, restricted to pediatric clients only, show and are required:
- 'Consent Obtained'.
- 'VFC Eligibility Code'.
- 'Funding Source'.
- Click the 'Lot Number Search' button and validate the 'Lot Number Manager' dialog is launched.
- Select the row for "Inventory A" and click [Select].
- Fill in any remaining required fields and click [Save].
- Validate the 'Pending Immunizations' field no longer contains a row for "Immunization A".
- Expand the 'Immunization History' field and validate it contains a row for "Immunization A" and that all columns are accurate.
- Click the ellipses under the 'Action' column for "Immunization A" and click [Document Reaction].
- Populate the 'Reaction' field and click [Save].
- Click the ellipses under the 'Action' column for "Immunization A" and click [View Details].
- Validate all fields are correctly populated and disabled and click [Cancel].
- Click [Add] and then [Order Immunizations], select "Immunization B" from the 'Immunizations Search' field and click [Continue].
- Populate all required fields and click [Order].
- Select the 'Finalize' tab and click [Generate Note].
- Validate the 'Note Summary' field contains a section for pending immunizations and has "Immunization B" listed.
- Validate the 'Note Summary' field contains a section for administered in-office immunizations and has "Immunization A" listed.
- Validate the 'Note Summary' field does not contain the new Historical Immunization Record.
- Select the 'Document' tab and then navigate to the 'Immunization' section.
- Click the ellipses under the 'Action' column for "Immunization B" and click [Cancel].
- Validate the 'Cancel Pending Administration' dialog appears and contains: "Are you sure you want to cancel this pending administration? Canceling this will permanently remove this pending administration."
- Click [Continue], populate the 'Comments' field and click [Save].
- Select the 'Finalize' tab and click [Generate Note].
- Validate the 'Note Summary' field does not contain a section for pending immunizations.
Scenario 17: Medical Note - Administering a Pediatric Immunization when 'Inventory Management' is disabled
Specific Setup:
- The 'Avatar CWS->Medication Inventory Management->->->->Enable Medication Inventory Management' registry setting must be set to "N".
- Please log out of the application and log back in after completing the above configuration.
- A 'Vaccination/Immunization' procedure-type service code must be configured in the 'Service Codes' form. (Medication A)
- An Outpatient program must exist that is configured as a 'Primary Care' program. (Program A)
- A client must have an active episode associated with "Program A". (Client A)
- "Client A" must be 18 years of age or younger.
Steps
- Search for and select "Client A" and navigate to the 'Medical Note'.
- Click [Add Note].
- Create a 'Primary Care' note.
- Select the 'Document' tab and then navigate to the 'Immunization' section.
- Populate all required fields and click [Order].
- Validate the 'Pending Administrations' field contains a row for "Medication A".
- Click the ellipses under the 'Action' column for "Medication A" and click [Administer].
- Select "Yes" for the 'Consent Obtained' radio button.
- Select "Not VFC eligible" from the 'VFC Eligibility Code' field.
- Select "Other" from the 'Provided By' field.
- Populate all required fields and click [Save].
- Expand the 'Immunization History' field and validate it contains a row for "Medication A" and that all columns are accurate.
- Click the ellipses under the 'Action' column for "Medication B" and click [Document Reaction].
- Select any value for the 'Reaction' field and click [Save].
- Click the ellipses under the 'Action' column for "Medication B" and click [View Details].
- Validate the 'Reaction' field contains the correct value and click [Close]
Scenario 18: Medical Note - Add Historical Immunization Record - Validate through 'Client Health Maintenance' form
Specific Setup:
- A client must have an active episode. (Client A)
Steps
- Search for and select "Client A" and navigate to the 'Medical Note'.
- Navigate to the 'Immunizations' section of the Facesheet.
- Click [Add] and then [Historical Immunization Record].
- Select any immunization listed in the 'Historical Immunization Record Search' field.
- Fill out any required fields and click [Save].
- Validate the 'Immunization History' section contains a row for the new historical immunization record.
- Access the 'Client Health Maintenance' form.
- Search for and select "Client A" from the 'Client ID' field.
- Click [List Immunizations] and validate the 'Immunizations History and Alerts' report is launched.
- Validate the 'Immunization History' section contains data for the new historical immunization record and click [Close Report].
- Click [Update] and then [New Row].
- Populate the 'Vaccine', 'Dose', 'Provided By' and 'Date' cells and click [Save].
- Navigate to the 'Medical Note'.
- Navigate to the 'Immunizations' section of the Facesheet.
- Validate the 'Immunization History' section contains a row for both new immunization records.
Scenario 19: Medical Note - Add Historical Records - In Office Administration
Specific Setup:
- A procedure-type service code must be configured in the 'Service Codes' form. (Medication A)
- An Outpatient program must exist. (Program A)
- A client must have an active episode associated with "Program A". (Client A)
Steps
- Search for and select "Client A" and navigate to the 'Medical Note'.
- Click [Add Note].
- Create a 'Psychiatry' note.
- Select the 'Document' tab and then navigate to the 'Procedure' section.
- Click [Add] and select "Medication A" from the 'Procedure Search' field.
- Select ‘Diagnosis’ and enter a diagnosis.
- Click 'Complete' field.
- Click 'Routine' field.
- Populate all remaining required fields and click [Save].
- Validate the 'Current Procedures' field contains a row for "Medication A".
- Access the 'Service Codes' form.
- Select "Edit" in the 'Add New or Edit Existing' field.
- Search for and select "Medication A" and select "Medication Administration" in the 'Procedure Type' field.
- Click [Submit].
- Validate a message is displayed stating "Service Codes has completed. Do you wish to return to form?" and click [Yes].
- Refresh 'Medical Note'.
- Click [Select Note] and click [Edit].
- Select the 'Document' tab and then navigate to the 'In-Office Administration' section.
- Expand the 'Administration History' field.
- Validate the 'Historical Records' section is displayed and contains "Medication A".
Scenario 20: Medical Note - In-Office Administration - ToDo's - Administer and refusal
Specific Setup:
- The 'Avatar CWS->Medication Inventory Management->->->->Enable Medication Inventory Management' registry setting must be set to "N".
- Please log out of the application and log back in after completing the above configuration.
- Two 'Medication Administration' procedure-type service codes must be configured in the 'Service Codes' form. (Medication A and Medication B)
- An outpatient program must exist. (Program A)
- A client must have an active episode in "Program A". (Client A)
- Two users must exist in the application. (User A and User B)
- "User A" is configured as a "Nurse" and "User B" is configured as a "Provider".
- "User A" must be logged into the application.
Steps
- Search for and select "Client A" and navigate to the 'Medical Note'.
- Click [Add Note] and create a new note.
- Select the 'Document' tab and then navigate to the 'In-Office Administration' section.
- Click [Add] and select "Medication A" from the 'In-Office Administration Search' field.
- Populate any required fields and click [Order].
- Validate the 'Pending Administrations' field contains a row for "Medication A".
- Click [Add] and select "Medication B" from the 'In-Office Administration Search' field.
- Populate any required fields and click [Order].
- Validate the 'Pending Administrations' field contains a row for "Medication B".
- Click [Send To Do].
- Set "User B" in the 'To-Do Recipient'.
- Set the 'Notes' field to any value and click [Send].
- Log out of the application and log back in as "User B".
- Access the 'My To Do's' widget.
- Select "Client A" from the 'Additional ToDos' list and click [Review To Do Item].
- Click 'In-Office Administrations'.
- Validate the 'Pending Administrations' field contains a row for "Medication A".
- Click the ellipses under the 'Action' column for "Medication A" and click [Administer].
- Validate, in the first section, the 'Dose', 'Unit', and 'Route' fields are correctly populated and disabled.
- Populate any required fields and click [Save].
- Expand the 'Administration History' field and validate it contains a row for "Medication A" and that all columns are accurate.
- Click the ellipses under the 'Action' column for "Medication B" and click [Refuse].
- Select any value in the 'Refused Reason' field and click [Save].
- Expand the 'Administration History' field and validate it contains a row for "Medication B" with a status of 'Refused'.
Scenario 21: Medical Note - Inventory Management Enabled - Full Immunization Work Flow
Specific Setup:
- The 'Avatar CWS->Medication Inventory Management->->->->Enable Medication Inventory Management' registry setting must be set to "Y".
- There must be at least one value in the Other CWS Tabled Files ‘(74101) Inventory Location’ dictionary. (Location A)
- Please log out of the application and log back in after completing the above configuration.
- Two 'Vaccination/Immunization' procedure-type service codes must be configured in the 'Service Codes' form. (Medication A and Medication B)
- "Medication A" and "Medication B" must have a template defined in the 'Medication Inventory Management' form. (Template A and Template B)
- In the 'Medication Inventory Management' form inventory for "Template A" and "Template B" must be received to "Location A". (Inventory A and Inventory B)
- An Outpatient program must exist that is configured as a primary care program. (Program A)
- A client must have an active episode associated with "Program A". (Client A)
Steps
- Search for and select "Client A" and navigate to the 'Medical Note'.
- Click [Add Note] and create a 'Primary Care' note.
- Select the ‘Document’ tab.
- Enter a value in the ‘Chief Complaint’ field.
- Select ‘HPI’ and add a value along with symptoms.
- Select ‘Physical Exam’ and select the ‘Constitutional’ tab.
- Check off the appropriate values.
- Select ‘Diagnosis’ and enter a diagnosis.
- Select ‘Immunizations’.
- Click [Add] and select "Medication A" from the 'Immunization Search' field.
- Validate the 'Dose', 'Unit', and 'Route' fields automatically populate based on the entries made in "Template A".
- Fill in any remaining required fields and click [Order].
- Validate the 'Pending Administrations' field contains a row for "Medication A"
- Click [Add] and select "Medication B" from the 'Immunization Search' field.
- Validate the 'Dose', 'Unit', and 'Route' fields automatically populate based on the entries made in "Template B".
- Fill in any remaining required fields and click [Administer].
- Validate, in the first section, the 'Dose', 'Unit', and 'Route' fields are correctly populated with the updated values and that all fields are disabled.
- Click the 'Lot Number Search' button and validate the 'Lot Number Manager' dialog is launched.
- Select the row for "Inventory B" and click [Select].
- Validate the 'Lot Number', 'Manufacturer', 'Expiration Date', and 'NDC' are all correctly populated and disabled.
- Fill in any remaining required fields and click [Save].
- Expand the 'Immunization History' field and validate it contains a row for "Medication B" and that all columns are accurate.
- Click the ellipses under the 'Action' column for "Medication B" and click [Document Reaction].
- Select any value for the 'Reaction' field and click [Save].
- Click the ellipses under the 'Action' column for "Medication B" and click [View Details].
- Validate the 'Reaction' field contains the correct value and click [Close].
- Select the ‘Finalize’ tab.
- Populate all required fields and click [Generate Note].
- Validate the ‘Note Summary’ is displayed and contains the appropriate information and click [Sign Off].
- Validate the Document is displayed and click [Accept], set the ‘Password’ field to the appropriate value and click [Verify].
- Refresh Medical Note.
- Click [Add Note].
- Select "Primary Care" from the 'Appointment/Note Workflow' field.
- Select "Main Street Center" from the 'Site' field.
- Select "Program A" from the 'Service Program' field.
- Search for and select "Service Code A" from the 'Service Code' field.
- Fill out any remaining required fields and click [Save].
- Select the 'Document' tab and then navigate to the 'Immunization' section.
- Validate the 'Pending Administrations' field contains a row for "Medication A"
- Click the ellipses under the 'Action' column for "Medication A" and click [Administer].
- Validate, in the first section, the 'Dose', 'Unit', and 'Route' fields are correctly populated with the updated values and that all fields are disabled.
- Click the 'Lot Number Search' button and validate the 'Lot Number Manager' dialog is launched.
- Select the row for "Inventory A" and click [Select].
- Validate the 'Lot Number', 'Manufacturer', 'Expiration Date', and 'NDC' are all correctly populated and disabled.
- Fill in any remaining required fields and click [Save].
- Expand the 'Immunization History' field and validate it contains a row for "Medication A" and that all columns are accurate.
- Select the 'Facesheet' tab and then navigate to the 'Immunization' section.
- Validate "Medication A" and "Medication B" are displayed.
- Select the 'Document' tab and then navigate to the 'Immunization' section.
- Void the administrations of "Medication A" and "Medication B".
- Refresh Medical Note.
- Click [Select Note] and click [Delete].
- Validate the 'Delete Note' dialog is displayed and contains "Are you sure you want to delete this draft note. Please make sure to void any administrations or procedures completed during the visit, as necessary."
- Click [Delete Note].
Scenario 22: Medical Note - Order an Immunization as "Provider" - Edit/Administer as "Nurse"
Specific Setup:
- The 'Avatar CWS->Medication Inventory Management->->->->Enable Medication Inventory Management' registry setting must be set to "Y".
- There must be at least one value in the Other CWS Tabled Files ‘(74101) Inventory Location’ dictionary. (Location A)
- Please log out of the application and log back in after completing the above configuration.
- A 'Vaccination/Immunization' procedure-type service code must be configured in the 'Service Codes' form. (Immunization A)
- "Immunization A" must have a template defined in the 'Medication Inventory Management' form. (Template A)
- In the 'Medication Inventory Management' form, inventory for "Template A" must be received to "Location A" and the 'Manufacturer of Vaccine (MVX)' and 'Vaccine Code (CVX)' fields must be populated. (Inventory A)
- An outpatient program configured as a 'Primary Care' program in the 'Program Maintenance' form must exist. (Program A)
- A client must have an active episode in "Program A". (Client A)
- Two users must exist. (User A) (User B).
- "User A" who is configured as a "Provider".
- "User B" who is configured as a "Nurse".
Steps
- Log into the application as "User A".
- Search for and select "Client A" and navigate to the 'Medical Note'.
- Click [Add Note] and create a 'Primary Care' note.
- Select the 'Document' tab and then navigate to the 'Immunization' section.
- Click [Add] and then [Order Immunizations], select "Immunization A" from the 'Immunizations Search' field and click [Continue].
- Validate the 'Dose', 'Unit', and 'Route' fields automatically populate based on the entries made in "Template A".
- Fill in any remaining required fields and click [Order].
- Validate the 'Pending Immunizations' field contains a row for "Immunization A" and click [Save Draft].
- Log out of the application and then log in as "User B".
- Search for and select "Client A" and navigate to the 'Medical Note'.
- Click [Select Note] and select the newly created 'Primary Care' note.
- Select the 'Document' tab and then navigate to the 'Immunizations' section.
- Validate the 'Pending Immunizations' field contains a row for "Immunization A".
- Click the ellipses under the 'Action' column for "Immunization A" and click [Administer].
- Validate, in the first section, the 'Dose', 'Unit', and 'Route' fields are correctly populated and that all fields are disabled.
- Validate the 'Entered By' and 'Ordered By' fields contains "User A" and the 'Administered By' field contains "User B".
- Select "Facility" from the 'Provided By' field.
- Click the 'Lot Number Search' button and validate the 'Lot Number Manager' dialog is launched.
- Select the row for "Inventory A" and click [Select].
- Validate all fields in the 'Administration Details' section are populated correctly.
- Fill in any remaining required fields and click [Save].
- Validate the 'Pending Immunizations' field no longer contains a row for "Immunization A".
- Expand the 'Immunization History' field and validate it contains a row for "Immunization A" and that all columns are accurate.
- Log out of the application and then log in as "User A".
- Search for and select "Client A" and navigate to the 'Medical Note'.
- Click [Select Note] and select the 'Primary Care' note.
- Select the 'Document' tab and then navigate to the 'Immunizations' section.
- Validate the 'Pending Immunizations' field no longer contains a row for "Immunization A".
- Expand the 'Immunization History' field and validate it contains a row for "Immunization A" and that all columns are accurate.
Scenario 23: Medical Note - Pediatric Immunization - ToDo's - Administer and refusal
Specific Setup:
- The 'Avatar CWS->Medication Inventory Management->->->->Enable Medication Inventory Management' registry setting must be set to "N".
- The Other CWS Tabled Files '(74101) Inventory Location’ dictionary must contain at least one value. (Location A)
- Please log out of the application and log back in after completing the above configuration.
- A generic 'Evaluation Management' service code must be configured in the 'Service Codes' form. (Service Code A)
- A 'Medication Administration' procedure-type service code must be configured in the 'Service Codes' form. (Medication A)
- A 'Vaccination/Immunization' procedure-type service code must be configured in the 'Service Codes' form. (Medication B)
- An outpatient program must exist that is configured as a 'Primary Care' program. (Program A)
- A client must have an active episode associated with "Program A" and is pediatric patient. (Client A)
- Two users must exist in the application: One who is configured as a "Nurse" (User A) and one who is configured as a "Provider". (User A and User B).
- "User A" must be logged into the application.
Steps
- Search for and select "Client A" and navigate to the 'Medical Note'.
- Click [Add Note].
- Create a 'Primary Care' note.
- Select the 'Document' tab and then navigate to the 'Immunization' section.
- Click [Add] and select "Medication A" from the 'Immunization Search' field.
- Populate all required fields and click [Order].
- Validate the 'Pending Administrations' field contains a row for "Medication A".
- Click [Add] and select "Medication B" from the 'Immunization Search' field.
- Populate all required fields and click [Order].
- Validate the 'Pending Administrations' field contains a row for "Medication B".
- Click [Send To Do].
- Set "User A" in the 'To-Do Recipient'.
- Set the 'Notes' field to any value and click [Send].
- Log out of the application and log back in as "User B".
- Access the 'My To Do's' widget.
- Select "Client A" from the 'Additional ToDos' list and click [Review To Do Item].
- Select the 'Immunization' section.
- Validate the 'Pending Administrations' field contains a row for "Medication A".
- Click the ellipses under the 'Action' column for "Medication A" and click [Administer].
- Validate, in the first section, the 'Dose', 'Unit', and 'Route' fields are correctly populated with the updated values and that all fields are disabled.
- Select "Yes" for the 'Consent Obtained' radio button.
- Select "Not VFC eligible" from the 'VFC Eligibility Code' field.
- Select "Facility" from the 'Provided BY' field.
- Populate all required fields and click [Save].
- Expand the 'Immunization History' field and validate it contains a row for "Medication A" and that all columns are accurate.
- Click the ellipses under the 'Action' column for "Medication B" and click [Refuse].
- Select any value for the 'Refused Reason' field and click [Save].
- Expand the 'Immunization History' field and validate it contains a row for "Medication B" with a status of "Refused".
|
Topics
• Medical Note
• NX
• Service Code
• To Dos
|
Progress Notes - The 'Limit Edits/Deletions To Original Author' registry setting
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
- Ambulatory Progress Notes
- Progress Notes (Group and Individual)
Scenario 1: Progress Notes (Group and Individual) - Validate the 'Limit Edits/Deletions To Original Author' registry setting
Specific Setup:
- Two users are defined with "Level 2" selected for 'User Security Level' (User A & User B).
- "User A" must have had their user ID changed in the 'Change User ID' form.
- The 'Limit Edits/Deletion to Original Author' registry setting must be set to "Y" for the 'Progress Notes (Group and Individual)' form.
- The 'Edit/Delete Security Level Override' registry setting must be set to "3" for the 'Progress Notes (Group and Individual)' form.
- A client must be enrolled in an existing episode (Client A).
Steps
- Login as "User A".
- Access the 'Progress Notes (Group and Individual)' form.
- Select "Client A" in the 'Select Client' field.
- Select the desired value in the 'Select Episode' field.
- Populate all required and desired fields.
- Select "Draft" in the 'Draft/Final' field.
- File the note.
- Log out.
- Log in as "User B".
- Access the 'Progress Notes (Group and Individual)' form.
- Select "Client A" in the 'Select Client' field.
- Validate the 'Select Draft Note To Edit' field does not contain the draft note filed by "User A".
- Close the form.
Scenario 2: Ambulatory Progress Notes - Validate the 'Limit Edits/Deletions To Original Author' registry setting
Specific Setup:
- Two users are defined with "Level 2" selected for 'User Security Level' (User A & User B).
- "User A" must have had their user ID changed in the 'Change User ID' form.
- The 'Limit Edits/Deletion to Original Author' registry setting must be set to "Y" for the 'Ambulatory Progress Notes' form.
- The 'Edit/Delete Security Level Override' registry setting must be set to "3" for the 'Ambulatory Progress Notes' form.
- A client must be enrolled in an existing outpatient episode (Client A).
Steps
- Login as "User A".
- Select "Client A" and access the 'Ambulatory Progress Notes' form.
- Populate all required and desired fields.
- Select "Draft" in the 'Draft/Final' field.
- Submit the note.
- Log out.
- Log in as "User B".
- Select "Client A" and access the 'Ambulatory Progress Notes' form.
- Validate the Pre-Display does not contain the draft note filed by "User A".
- Close the form.
Scenario 3: Inpatient Progress Notes - Validate the 'Limit Edits/Deletions To Original Author' registry setting
Specific Setup:
- Two users are defined with "Level 2" selected for 'User Security Level' (User A & User B).
- "User A" must have had their user ID changed in the 'Change User ID' form.
- The 'Limit Edits/Deletion to Original Author' registry setting must be set to "Y" for the 'Ambulatory Progress Notes' form.
- The 'Edit/Delete Security Level Override' registry setting must be set to "3" for the 'Ambulatory Progress Notes' form.
- A client must be enrolled in an existing inpatient episode (Client A).
Steps
- Login as "User A".
- Select "Client A" and access the 'Inpatient Progress Notes' form.
- Populate all required and desired fields.
- Select "Draft" in the 'Draft/Final' field.
- Submit the note.
- Log out.
- Log in as "User B".
- Select "Client A" and access the 'Inpatient Progress Notes' form.
- Validate the Pre-Display does not contain the draft note filed by "User A".
- Close the form.
'Columbia Suicide Risk Assessment' and 'Columbia SRA Since Last Visit' forms
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
- Columbia Suicide Risk Assessment
- Columbia SRA Since Last Visit
- Clinical Pathway Enrollment
Scenario 1: Columbia Suicide Risk Assessment - Field Validations
Specific Setup:
- A client must be admitted to an active episode (Client A).
- One or more clinical pathways defined in the 'Clinical Pathway Definition' form.
Steps
- Select "Client A" and access the 'Columbia Suicide Risk Assessment' form.
- Enter the current date in the 'Assessment Date' field.
- Populate all required and desired fields.
- Select "Draft" in the 'Status' field.
- Submit the form.
- Select "Client A" and access the 'Columbia Suicide Risk Assessment' form.
- Select the record filed in the previous steps and click [Edit].
- Validate the 'Assessment Date' field is disabled and contains the current date.
- Validate all previously filed data is displayed.
- Select "Final" in the 'Status' field.
- Click [OK] on the 'Once set to 'Final', the data cannot be edited in the future' prompt.
- Validate the 'Assessment Date' field remains disabled.
- Select "Yes" in the 'Enroll in Clinical Pathway' field.
- Select desired pathway from the 'Pathway Name' field.
- Submit the form.
Scenario 2: Columbia SRA Since Last Visit
Specific Setup:
- A client must be enrolled in an existing episode (Client A).
- One or more clinical pathways defined in the 'Clinical Pathway Definition' form.
Steps
- Select "Client A" and access the 'Columbia SRA Since Last Visit' form.
- Enter the current date in the 'Assessment Date' field.
- Populate all required and desired fields.
- Select "Draft" in the 'Status' field.
- Submit the form.
- Select "Client A" and access the 'Columbia SRA Since Last Visit' form.
- Select the record filed in the previous steps and click [Edit].
- Validate the 'Assessment Date' field is disabled and contains the current date.
- Validate all previously filed data is displayed.
- Select "Final" in the 'Status' field.
- Click [OK] on the 'Once set to 'Final', the data cannot be edited in the future' prompt.
- Validate the 'Assessment Date' field remains disabled.
- Select "Yes" in the 'Enroll in Clinical Pathway' field.
- Select desired pathway from the 'Pathway Name' field.
- Submit the form.
|
Topics
• User Definition
• Registry Settings
• Progress Notes
• Clinical Pathway
|
Progress Notes (Group and Individual) - Autosave
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
- Progress Notes (Group and Individual)
- Ambulatory Progress Notes
Scenario 1: Progress Notes (Group and Individual) - Validate autosave functionality
Specific Setup:
- Autosave must be enabled on the 'Progress Notes (Group and Individual)' form.
- A client is enrolled in an existing episode and has a treatment plan on file (Client A).
Steps
- Access the 'Progress Notes (Group and Individual)' form.
- Enter "Client A" in the 'Select Client' field.
- Select the desired episode in the 'Select Episode' field.
- Select the desired group in the 'Group Name or Number' field.
- Select "Independent Note" in the 'Progress Note For' field.
- Select the desired value in the 'Note Type' field.
- Enter the desired value in the 'Notes Field' field.
- Select "Final" in the 'Draft/Final' field.
- Click [Backup Form] and close the form.
- Access the 'Progress Notes (Group and Individual)' form.
- Validate a 'Restore/Delete Backup Data' dialog is displayed.
- Select the progress note backed up in the previous steps and click [OK].
- Validate the 'Select Client' field contains "Client A".
- Validate the 'Select Episode' field contains the episode selected in the previous steps.
- Validate the 'Group Name or Number' field contains the group selected in the previous steps.
- Validate the 'Progress Note For' field contains "Independent Note".
- Validate the 'Note Type' field contains the value selected in the previous steps.
- Validate the 'Notes Field' field contains the value entered in the previous steps.
- Click [File Note].
- Validate a "Progress Notes" message is displayed stating: Note Filed.
- Click [OK] and close the form.
Scenario 2: Progress Notes (Group and Individual) Copy - Validate autosave functionality
Specific Setup:
- A copy of the 'Progress Notes (Group and Individual)' form must be defined.
- Autosave must be enabled on this form in 'Set System Defaults'.
- A client is enrolled in an existing episode (Client A).
- A group is defined in 'Group Registration'.
Steps
- Access the 'Progress Notes (Group and Individual) Copy' form.
- Enter "Client A" in the 'Select Client' field.
- Select the desired episode in the 'Select Episode' field.
- Select the desired group in the 'Group Name or Number' field.
- Select "Independent Note" in the 'Progress Note For' field.
- Select the desired value in the 'Note Type' field.
- Enter the desired value in the 'Notes Field' field.
- Select "Final" in the 'Draft/Final' field.
- Click [Backup Form] and close the form.
- Access the 'Progress Notes (Group and Individual) Copy' form.
- Validate a 'Restore/Delete Backup Data' dialog is displayed.
- Select the progress note backed up in the previous steps and click [OK].
- Validate the 'Select Client' field contains "Client A".
- Validate the 'Select Episode' field contains the episode selected in the previous steps.
- Validate the 'Group Name or Number' field contains the group selected in the previous steps.
- Validate the 'Progress Note For' field contains "Independent Note".
- Validate the 'Note Type' field contains the value selected in the previous steps.
- Validate the 'Notes Field' field contains the value entered in the previous steps.
- Click [File Note].
- Validate a "Progress Notes" message is displayed stating: Note Filed.
- Click [OK] and close the form.
|
Topics
• Progress Notes
• Auto Save
|
Progress Notes - Progress Notes Web Service - Existing Appointments
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
- Progress Notes (Group and Individual)
Scenario 1: Creating Progress Note for an Existing Appointment in 'Progress Notes (Group and Individual)'
Specific Setup:
- Service:
- Service should be picked from existing or newly created and the Fee definitions should be defined for the service(s).
- Client:
- A client is enrolled in an existing episode and has multiple existing Appointments on file (Client A).
- Registry Settings:
- Set the "Enable Alternative Service Location Fields" Registry setting to "Y" for Progress Notes (Group and Individual)
- Set the "Limit Existing Services to Current Login User" Registry Setting value as "0" for Progress Notes (Group and Individual).
- Set the "Limit Existing Appointments to Current Login User" Registry Setting value as "0" for Progress Notes (Group and Individual).
Steps
- Access the 'Progress Notes (Group and Individual)' form.
- Select "Client A" in the 'Select Client' field.
- Select the desired episode in the 'Select Episode' field.
- Select "Existing Appointment" in the 'Progress Note For' field.
- Select any existing appointments of "Client A" in the 'Note Addresses Which Existing Service/Appointment' field.
- Populate all required and desired fields.
- Verify that the Facility Location fields are populated with the data entered in 'Edit Service Information'.
- Update at least one facility location field value.
- Select "Draft" in the 'Draft/Final' field.
- Click [File Note].
- Validate a message is displayed stating: Note Filed.
- Click [OK].
- Click [Yes] in the form return.
- Select the "Client A" in the 'Select Client' field.
- Select the note filed in the previous steps in the 'Draft Note To Edit' field.
- Validate all previously filed data is displayed.
- Select "Final" in the 'Draft/Final' field.
- Click [File Note].
- Click [Accept].
- Enter the Password and select [Verify].
- Select "Admitting Practitioner" in Add Approver.
- Select [Submit].
- Validate the acknowledgment 'Note Filed'.
- Click [No] and close the form.
Scenario 2: Validating 'AddProgressNotes' web service request for an existing Appointment
Specific Setup:
- Access to SoapUI or any other web service.
- Client with multiple existing Appointments (10 appointments) created in the 'Scheduling Calendar' form. 'Client A'.
Steps
- Access the SoapUI or any other tool to test the web service.
- Consume the WSDL for WEB.SVC.ProgressNotes.Client.Request.
- Enter data on the web service request for the "Existing Appointment".
- Set the "NotesField" item to any desired text value.
- Set the "NoteType" item to "Any desired Note type value". (one with or without a co-practitioner).
- On selecting the Note Type that has the co-practitioner, Set the desired value for 'User To Send Co-Sign To Do Item To'.
- Set the "DraftFinal" item to "D".
- Set the "ProgressNoteFor" item to "EI".
- Set the "ServiceProgram" item to "Any desired program value".
- Set the "ServiceDuration" item to "Any desired duration value".
- Set the "DateOfService" item to "Any desired date value".
- Leave all the "Facility Location" field values empty.
- Set the "ClientID" item to 'Client A'.
- Set the "EpisodeNumber" to the client episode for the service.
- Set the "NoteAddressesWhichExistingServiceAppointment" to any existing appointment's appointment ID. This can be obtained from the below table,
- "appt_data"
- Set the "Option" to "Any desired option value".
- Click [Send].
- Verify the Message response contains "Progress Notes web service has been filed successfully" with the "Unique ID" value.
- Access the 'Progress Notes (Group and Individual)' form.
- Select "Client A" in the 'Select Client' field.
- Validate that the note filed in the previous steps is shown in the 'Draft Note To Edit' field for selection.
- Select the note filed in the previous steps in the 'Draft Note To Edit' field.
- Verify that all the data filed as part of the note is populated in the respective fields.
- Click [Discard].
- Click [Yes].
|
Topics
• Progress Notes
• Web Services
|
Disclosure Management - View attached document
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
- Admission (Outpatient)
- Disclosure Management Configuration
- Progress Notes (Group and Individual)
- Disclosure Management
Scenario 1: Disclosure Management - Validating notes from the authorized episodes in the 'Disclosure Management' report - Document Images Authorized For Disclosure
Specific Setup:
- Disclosure Management Configuration:
- The 'Valid Attachment Type' field is set to '(Avatar CWS) Progress Notes (Group and Individual) /EPISODE BASED' or any other document to be used. Note the document selected.
- Document Routing Setup:
- The document routing is set up for the document identified above.
- Admission:
- A new client is admitted to the desired program. Note the client id, admission date, admission program.
- Progress Notes (Group and Individual):
- A progress note is filed for the client / episode. Note the date when progress note filed.
- Append Document:
- Append a document to the progress note filed in the previous step.
Steps
- Open the 'Disclosure Management' form.
- Enter a date in the ‘Request Date’ field.
- Enter a date in the ‘Request Information Start Date’ field.
- Enter a date in the ‘Request Information End Date’ field.
- Select the topmost Document Image in the ‘Requested Document Images’ field.
- Enter an organization name in the ‘Organization’ field.
- Go to the ‘Authorization’ section.
- Enter a date in the ‘Authorization Start Date’.
- Enter a date in the ‘Authorization End Date’.
- Click the ‘Update Document Images Authorized For Disclosure’ button.
- Select the ‘Document Image’ row and set the ‘Authorized’ field to ‘Yes’.
- Click the ‘Save’ button.
- Click the ‘Refresh Document Images’ button.
- Verify the previously selected document displays as ‘Authorized’ in the ‘Document Images Authorized For Disclosure’.
- Go to the ‘Disclosure’ section.
- Enter a date in the ‘Disclosure Date’ field.
- Enter a time in the ‘Disclosure Time’ field.
- Select the document image in the ‘Disclosure Images’ field.
- Click the ‘Process’ button.
- Click the ‘Disclose’ button.
- Verify the disclosure information displays for the previously selected document image.
- Click the ‘Cancel’ button to return to the ‘Disclosure’ section.
- Click the ‘Submit’ button to file the record.
- Click ‘Yes’ to return to the pre-display.
- Click the ‘Add’ button to create another record.
- Enter a date in the ‘Request Date’ field.
- Enter a date in the ‘Request Information Start Date’ field.
- Enter a date in the ‘Request Information End Date’ field.
- Select both Document Images in the ‘Requested Document Images’ field.
- Enter an organization name in the ‘Organization’ field.
- Go to the ‘Authorization’ section.
- Enter a date in the ‘Authorization Start Date’.
- Enter a date in the ‘Authorization End Date’.
- Click the ‘Update Document Images Authorized For Disclosure’ button.
- Select each ‘Document Image’ row and set the ‘Authorized’ field to ‘Yes’.
- Click the ‘Save’ button.
- Click the ‘Refresh Document Images’ button.
- Verify the previously selected documents display as ‘Authorized’ in the ‘Document Images Authorized For Disclosure’.
- Go to the ‘Disclosure’ section.
- Enter a date in the ‘Disclosure Date’ field.
- Enter a time in the ‘Disclosure Time’ field.
- Select the document image in the ‘Disclosure Images’ field.
- Click the ‘Process’ button.
- Click the ‘Disclose’ button.
- Verify the disclosure information displays for the previously selected document images.
- Click the ‘Cancel’ button to return to the ‘Disclosure’ section.
- Click the ‘Submit’ button to file the record.
- Click ‘No’ to exit the form.
Scenario 2: Disclosure Management - Validating notes from the authorized episodes in the 'Disclosure Management' report - Chart items authorized for disclosure
Specific Setup:
- Disclosure Management Configuration:
- The 'Valid Attachment Type' field is set to '(Avatar CWS) Progress Notes (Group and Individual) /EPISODE BASED' or any other document to be used. Note the document selected.
- Document Routing Setup:
- The document routing is set up for the document identified above.
- Admission:
- A new client is admitted to the desired program. Note the client id, admission date, admission program.
- Progress Notes (Group and Individual):
- A progress note is filed for the client / episode. Note the date when progress note filed.
- Append Document:
- Append a document to the progress note filed in the previous step.
Steps
- Open the 'Disclosure Management' form for the client.
- Enter desired date to the 'Request Date' such that it covers the progress note filing date.
- Select an episode in the 'Request Episode(s)' field.
- Select desired document type in the 'Requested Chart Items' field.
- Enter required organization information.
- Click [Save Requesting Organization].
- Validate the 'Requesting Organization details have been saved' message.
- Select the 'Authorization' section.
- Enter authorization dates that cover the episodes up to the date the progress notes were entered
- Select desired episode from the 'Authorization Episode(s)'.
- Set the 'Default all Chart Items to Yes' to 'YES'.
- Click 'Update Chart Items Authorized For Disclosure' and authorize the attachment.
- Select the 'Disclosure' section.
- Enter a 'Disclosure Date'.
- Select '(Avatar CWS) Progress Notes (Group and Individual)' in the field 'Chart Disclosure Information'.
- Click Process.
- Select the '(Avatar CWS) Progress Notes (Group and Individual)' entry in the 'Items for Disclosure'.
- Click 'View'.
- Verify the note displays successfully for the authorized episodes.
- Click [Cancel].
- Verify the system navigates user to the 'Disclosure Management' form.
- Click [Submit].
- Verify the disclosure submitted successfully.
|
Topics
• Disclosure
|
Progress Notes - Signatures and Treatment Plan Grid data
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
- Treatment Plan
- Progress Notes (Group and Individual)
- Site Specific Section Modeling (CWS)
Scenario 1: Progress Notes (Group and Individual) - Validate 'Treatment Plan' Grid and 'Signature' fields
Specific Setup:
- Signature support must be enabled in the 'System Security Defaults' form.
- The 'Progress Notes' widget is accessible on the HomeView.
- The 'Enable Treatment Plan Grid' registry setting is set to "Y" for the 'Progress Notes (Group and Individual)' form.
- The 'Progress Notes (Group and Individual)' form must have a signature field added via 'Site Specific Section Modeling' (Signature A).
- A client must have a Treatment Plan filed with a problem, goal, objective, and intervention associated (Client A).
- Must have a crystal report configured for document routing configured for "Signature A" and the 'Treatment Plan' grid for progress notes (Crystal Report A).
- Crystal Report Document Routing must be configured for the 'Progress Notes (Group and Individual)' form using "Crystal Report A".
Steps
- Access the 'Progress Notes (Group and Individual)' form.
- Select "Client A" in the 'Select Client' field.
- Select "Independent Note" in the 'Progress Note For' field.
- Select the desired value in the 'Note Type' field.
- Enter the desired value in the 'Notes Field'.
- Click [New Row] in the 'Treatment Plan Grid'.
- Select "Treatment Plan" in the 'Select T.P. Version' field.
- Click [View].
- Select the desired treatment plan item and click [Return].
- Enter the desired value in the 'T.P. Item Notes/Documentations' field.
- Click [Sign] for "Signature A" and enter the desired signature.
- Select "Final" in the 'Draft/Final' field.
- Click [File Note].
- Validate the 'Confirm Document' dialog is displayed with "Crystal Report A". Validate the signature and treatment plan grid data display as expected.
- Leave the form open.
- Access Crystal Reports or other SQL Reporting Tool.
- Create a report using the 'CWSTEMP.cw_patient_notes_tpnotes' SQL table.
- Validate a row is displayed for the treatment plan data entered for "Client A" in the previous steps.
- Please note: this is a temporary storage table. A process will run once daily that will clean up this data, which will become available in the SYSTEM.cw_patient_notes_tpnotes' SQL table after filing the note.
- Close the report.
- Create a report using the 'CWSTEMP.cw_tx_pn_sign_data' SQL table.
- Validate a row is displayed for the signature data entered for "Client A" in the previous steps.
- Please note: this is a temporary storage table. A process will run once daily that will clean up this data, which will become available in the SYSTEM.cw_tx_pn_sign_data' SQL table after filing the note.
- Close the report.
- Navigate back to the 'Progress Notes (Group and Individual)' form.
- Click [Accept].
- Enter the password associated to the logged in user.
- Close the form.
- Select "Client A" and access the 'Progress Notes' widget.
- Validate the progress note filed in the previous steps is displayed with the treatment plan and signature data.
- Access Crystal Reports or other SQL Reporting Tool.
- Create a report using the 'SYSTEM.cw_patient_notes_tpnotes' SQL table.
- Validate a row is displayed for the treatment plan data entered for "Client A" in the previous steps.
- Close the report.
- Create a report using the 'SYSTEM.cw_tx_pn_sign_data' SQL table.
- Validate a row is displayed for the signature data entered for "Client A" in the previous steps.
- Close the report.
Scenario 2: Ambulatory Progress Notes - Validate 'Treatment Plan' Grid and Signature fields
Specific Setup:
- Signature support must be enabled in the 'System Security Defaults' form.
- The 'Progress Notes' widget is accessible on the HomeView.
- The 'Enable Treatment Plan Grid' registry setting is set to "Y" for the 'Ambulatory Progress Notes' form.
- The 'Ambulatory Progress Notes' form must have a signature field added via 'Site Specific Section Modeling' (Signature A).
- A client must be enrolled in an outpatient episode and have a Treatment Plan filed with a problem, goal, objective, and intervention associated (Client A).
- Must have a crystal report configured for document routing configured for "Signature A" and the 'Treatment Plan' grid for 'Ambulatory Progress Notes' (Crystal Report A).
- Crystal Report Document Routing must be configured for the 'Ambulatory Progress Notes' form using "Crystal Report A".
Steps
- Select "Client A" and access the 'Ambulatory Progress Notes' form.
- Select "Independent Note" in the 'Progress Note For' field.
- Select the desired value in the 'Note Type' field.
- Enter the desired value in the 'Notes Field'.
- Click [New Row] in the 'Treatment Plan Grid'.
- Select "Treatment Plan" in the 'Select T.P. Version' field.
- Click [View].
- Select the desired treatment plan item and click [Return].
- Enter the desired value in the 'T.P. Item Notes/Documentations' field.
- Click [Sign] for "Signature A" and enter the desired signature.
- Select "Final" in the 'Draft/Final' field.
- Click [Submit].
- Validate the 'Confirm Document' dialog is displayed with "Crystal Report A". Validate the signature and treatment plan grid data display as expected.
- Leave the form open.
- Access Crystal Reports or other SQL Reporting Tool.
- Create a report using the 'CWSTEMP.cw_patient_notes_tpnotes' SQL table.
- Validate a row is displayed for the treatment plan data entered for "Client A" in the previous steps.
- Please note: this is a temporary storage table. A process will run once daily that will clean up this data, which will become available in the SYSTEM.cw_patient_notes_tpnotes' SQL table after filing the note.
- Close the report.
- Create a report using the 'CWSTEMP.cw_tx_pn_sign_data' SQL table.
- Validate a row is displayed for the signature data entered for "Client A" in the previous steps.
- Please note: this is a temporary storage table. A process will run once daily that will clean up this data, which will become available in the SYSTEM.cw_tx_pn_sign_data' SQL table after filing the note.
- Close the report.
- Navigate back to the 'Ambulatory Progress Notes' form.
- Click [Accept].
- Enter the password associated to the logged in user.
- Close the form.
- Select "Client A" and access the 'Progress Notes' widget.
- Validate the progress note filed in the previous steps is displayed with the treatment plan and signature data.
- Access Crystal Reports or other SQL Reporting Tool.
- Create a report using the 'SYSTEM.cw_patient_notes_tpnotes' SQL table.
- Validate a row is displayed for the treatment plan data entered for "Client A" in the previous steps.
- Close the report.
- Create a report using the 'SYSTEM.cw_tx_pn_sign_data' SQL table.
- Validate a row is displayed for the signature data entered for "Client A" in the previous steps.
- Close the report.
Scenario 3: Inpatient Progress Notes - Validate 'Treatment Plan' Grid and 'Signature' fields
Specific Setup:
- Signature support must be enabled in the 'System Security Defaults' form.
- The 'Progress Notes' widget is accessible on the HomeView.
- The 'Enable Treatment Plan Grid' registry setting is set to "Y" for the 'Inpatient Progress Notes' form.
- The 'Inpatient Progress Notes' form must have a signature field added via 'Site Specific Section Modeling' (Signature A).
- A client must be enrolled in an inpatient episode and have a Treatment Plan filed with a problem, goal, objective, and intervention associated (Client A).
- Must have a crystal report configured for document routing configured for "Signature A" and the 'Treatment Plan' grid for Inpatient progress notes (Crystal Report A).
- Crystal Report Document Routing must be configured for the 'Inpatient Progress Notes' form using "Crystal Report A".
Steps
- Select "Client A" and access the 'Inpatient Progress Notes' form.
- Select "Independent Note" in the 'Progress Note For' field.
- Select the desired value in the 'Note Type' field.
- Enter the desired value in the 'Notes Field'.
- Click [New Row] in the 'Treatment Plan Grid'.
- Select "Treatment Plan" in the 'Select T.P. Version' field.
- Click [View].
- Select the desired treatment plan item and click [Return].
- Enter the desired value in the 'T.P. Item Notes/Documentations' field.
- Click [Sign] for "Signature A" and enter the desired signature.
- Select "Final" in the 'Draft/Final' field.
- Click [File Note].
- Validate the 'Confirm Document' dialog is displayed with "Crystal Report A". Validate the signature and treatment plan grid data display as expected.
- Leave the form open.
- Access Crystal Reports or other SQL Reporting Tool.
- Create a report using the 'CWSTEMP.cw_patient_notes_tpnotes' SQL table.
- Validate a row is displayed for the treatment plan data entered for "Client A" in the previous steps.
- Please note: this is a temporary storage table. A process will run once daily that will clean up this data, which will become available in the SYSTEM.cw_patient_notes_tpnotes' SQL table after filing the note.
- Close the report.
- Create a report using the 'CWSTEMP.cw_tx_pn_sign_data' SQL table.
- Validate a row is displayed for the signature data entered for "Client A" in the previous steps.
- Please note: this is a temporary storage table. A process will run once daily that will clean up this data, which will become available in the SYSTEM.cw_tx_pn_sign_data' SQL table after filing the note.
- Close the report.
- Navigate back to the ' InpatientProgress Notes ' form.
- Click [Accept].
- Close the form.
- Select "Client A" and access the 'Progress Notes' widget.
- Validate the progress note filed in the previous steps is displayed with the treatment plan and signature data.
- Access Crystal Reports or other SQL Reporting Tool.
- Create a report using the 'SYSTEM.cw_patient_notes_tpnotes' SQL table.
- Validate a row is displayed for the treatment plan data entered for "Client A" in the previous steps.
- Close the report.
- Create a report using the 'SYSTEM.cw_tx_pn_sign_data' SQL table.
- Validate a row is displayed for the signature data entered for "Client A" in the previous steps.
- Close the report.
|
Topics
• Document Routing
• Progress Notes
• Query/Reporting
|
Family Health History - Treatment Result
Scenario 1: Filing the 'Family Health History' form
Specific Setup:
- Family the test client belongs to should be entered in via "Family Registration".
Steps
- Using the "Family Health History" form
- Select "Add New" from the "Select Family Member" dropdown.
- Set "First" to "Kennedi".
- Set "Last" to "Muck".
- Select "Granddaughter" from the "Relationship" dropdown.
- Set the "Date of Birth date" to "07/09/2023".
- Select "Female" under "Sex".
- Select "White/Caucasian" from the "Race" dropdown.
- Select "Not Of Hispanic Origin" from the "Ethnicity" dropdown.
- Select "Yes" under "Health Problems To Record".
- Click the "Enter Health History" button.
- Click the New Row button
- Set the "Problem" to "happy puppet sundrome".
- Set "Status" to "Currently In Treatment (2)".
- Click the "Save" button.
- Set the "Notes" to "notes field".
- Submit the form to file the data.
- Reopen the "Family Health History" form.
- Select "Kennedi Muck Granddaughter" from the "Select Family Member" dropdown.
- Validate "Relationship" contains "Granddaughter".
- Validate "Date of Birth date" is set to "07/09/2023".
- Validate "Sex" is set to "Female".
- Validate "Race" contains "White/Caucasian".
- Validate "Ethnicity" contains "Not Of Hispanic Origin".
- Validate "Health Problems To Record" contains "Yes".
- Set the "Notes" to "notes field".
- Click the "Enter Health History" button.
- Validate "Problem" contains "happy puppet syndrome".
- Validate "Status" contains "Currently In Treatment (2)".
- Click the "Close/Cancel" button.
- Set the "Notes" to "notes field".
Family Health History - Refused Vitals
Scenario 1: Vitals Entry Report - Report displays refused vitals information
Specific Setup:
- Registry setting Avatar CWS->CWS Utilities->Set System Defaults->Vitals Entry->->Enable Multiple Blood Pressure Entry is set to "Y".
- Multiple vitals are filed for a client using 'Vitals Entry'.
- One or more records include 'Refused Vitals' set to "Yes".
Steps
- Access the 'Vitals Entry' form for the test client.
- Click [Vitals Reports] section.
- Select "All" in the 'Vital Sign(s) for Report' field.
- Set the '"Start Date" field to a date which will include the refused vitals records.
- Set the "Start Time" to the current time.
- Set the "End Date" field to the end of the date range to include records in the report.
- Set the "End Time" to the current time.
- Select "Yes" in the "Display Refused Vitals" field.
- Click [View Report].
- Verify the "Refused Vitals" data displays successfully for the dates included.
Scenario 2: Vitals Entry Report - 'Display Refused Vitals' set to "No"
Specific Setup:
- A client has refused and not refused vitals on file in 'Vitals Entry' (Client A).
Steps
- Select "Client A" and access the 'Vitals Entry' form.
- Select the "Vitals Reports" section.
- Select "All" in the 'Vital Sign(s) for Report' field.
- Enter a date that will include refused and not refused vitals in the 'Start Date' field.
- Enter the current time in the 'Start Time' field.
- Enter a date that will include refused and not refused vitals in the 'End Date' field.
- Enter the current time in the 'End Time' field.
- Select "No" in the "Display Refused Vitals" field.
- Click [View Report].
- Validate the report does not include refused vitals or comments associated with refused vitals.
- Close the report and the form.
Vitals Entry - Position required
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
Scenario 1: "Vitals Entry" form - Additional blood pressure fields
Specific Setup:
- Avatar CWS->CWS Utilities->Set System Defaults->Vitals Entry->->Enable Multiple Blood Pressure Entry = "Y". Note that this is a one time registry setting. Once enabled, this cannot be disabled.
Steps
- Open "Vitals Entry" form.
- Select "Add" in the "Add/Edit/Delete Vital Sign" field.
- Enter current date in the "Date" field.
- Enter current time in the "Time" field.
- Enter any value in the Blood Pressure: "Systolic" field.
- Validate the Blood Pressure: "Diastolic" field becomes required.
- Enter any value in the Blood Pressure: "Diastolic" field.
- Validate the Blood Pressure "Systolic" field becomes required.
- Select any value in the Blood Pressure: "Position" field.
- Enter any value in the Blood Pressure 2: "Systolic 2" field.
- Validate the "Blood Pressure 2: "Diastolic 2" field becomes required.
- Enter any value in the Blood Pressure 2: "Diastolic 2" field.
- Validate the "Blood Pressure 2: "Systolic 2" field becomes required.
- Select any value in the Blood Pressure 2: "Position 2" field.
- Enter any time in the Blood Pressure 2: "Time Taken" field.
- Enter any value in the Blood Pressure 3: "Systolic 3" field.
- Validate the "Blood Pressure 3: "Diastolic 3" field becomes required.
- Enter any value in the Blood Pressure 3: "Diastolic 3" field.
- Validate the "Blood Pressure 3: "Systolic 2" field becomes required.
- Select any value in the Blood Pressure 3: "Position 3" field.
- Enter any time in the Blood Pressure 3: "Time Taken" field.
- Click [Submit].
- Click [Yes] on the "Submitting has completed. Do you wish to return to form?" prompt.
- Validate the following fields are not required on re-display of the form:
- "Position 2".
- "Position 3".
- "Time 2".
- "Time 3".
- Select "Edit" in the "Add/Edit/Delete Vital Sign" field.
- Click [Select Vital Sign].
- Click on the previously entered row to highlight.
- Click [OK].
- Verify the previously entered data displays as entered in previous steps.
- Click [Submit].
- Click [No] on the "Submitting has completed. Do you wish to return to form?" prompt to return to the menu.
- Open the "CWS Vital Signs Setup" form.
- Set low value/high value ranges for all 3 blood pressure fields.
- File the form.
- Open the :Vitals Entry" form.
- Validate all 3 diastolic/systolic blood pressure fields for range limits.
Scenario 2: Vitals Entry - Field Validations - Single Blood Pressure
Specific Setup:
- Avatar CWS->CWS Utilities->Set System Defaults->Vitals Entry->->Enable Multiple Blood Pressure Entry = "N". Note that this is a one time registry setting. Once enabled, this cannot be disabled.
Steps
- Open "Vitals Entry" form.
- Select "Add" in the "Add/Edit/Delete Vital Sign" field.
- Enter current date in the "Date" field.
- Enter current time in the "Time" field.
- Enter any value in the Blood Pressure: "Systolic" field.
- Validate the Blood Pressure: "Diastolic" field becomes required.
- Enter any value in the Blood Pressure: "Diastolic" field.
- Validate the Blood Pressure "Systolic" field becomes required.
- Select any value in the Blood Pressure: "Position" field.
- Click [Submit].
- Click [Yes] on the "Submitting has completed. Do you wish to return to form?" prompt.
- Select "Edit" in the "Add/Edit/Delete Vital Sign" field.
- Click [Select Vital Sign].
- Click on the previously entered row to highlight.
- Click [OK].
- Verify the previously entered data displays as entered in previous steps.
- Click [Submit].
- Click [No] on the "Submitting has completed. Do you wish to return to form?" prompt to return to the menu.
|
Topics
• Family Health History
• Vitals Entry
|
Validate Observation details in 'Client Observation' form
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
Scenario 1: Validate Observation details 'Updated Time' does not change for previous entries in 'Client Observation' form
Steps
- Open 'Client Observation' form for a test client.
- Create multiple entries in the 'Observation Details'.
- Edit one of the entries and validate that the fields 'Updated Date', 'Updated time' and 'Updated By' are changed for the edited row only. The other rows do not change.
Scenario 2: Validate the values in the table 'cw_observation_archive' are populating correctly
Steps
- Using 'Client Observation' form, create an Observation record which is more than 30 days before from current date as Observations are archived after 30 days.
- To immediately archive the data contact Netsmart associate.
- Execute the query "select * from system.cw_observation_details_archive".
- Validate that the following fields are populated :
- -'createdDate'
- -'createdTime'
- -'createdBy'
- -'updatedDate'
- -'updatedTime'
- -'updatedBy'
Validate Observation Archive tables
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
Scenario 1: Validate Observation details 'Updated Time' does not change for previous entries in 'Client Observation' form
Steps
- Open 'Client Observation' form for a test client.
- Create multiple entries in the 'Observation Details'.
- Edit one of the entries and validate that the fields 'Updated Date', 'Updated time' and 'Updated By' are changed for the edited row only. The other rows do not change.
Scenario 2: Validate the values in the table 'cw_observation_archive' are populating correctly
Steps
- Using 'Client Observation' form, create an Observation record which is more than 30 days before from current date as Observations are archived after 30 days.
- To immediately archive the data contact Netsmart associate.
- Execute the query "select * from system.cw_observation_details_archive".
- Validate that the following fields are populated :
- -'createdDate'
- -'createdTime'
- -'createdBy'
- -'updatedDate'
- -'updatedTime'
- -'updatedBy'
|
Topics
• NX
• Client Observation
|
Attach Individual Notes to Existing Appointments/Services - Auto Append Document Image
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
- Attach Individual Notes To Existing Services/Appointments
Scenario 1: Registry Settings - Auto Append Document Image
Steps
- Open the "Registry Settings" form.
- Search for the setting "Avatar CWS->Progress Notes->Attach Individual Notes To Existing Services/Appointments->->->Auto Append Document Image".
- Set the Value to "Y".
- Submit to file the form.
- Open the "Attach Individual Notes to Existing Services/Appointments" form.
- Click "Select Note To Attach".
- Validate a column called "Document" exists on this form.
- Cancel processing and exit the form.
- Open the "Registry Settings" form.
- Search for the setting "Auto Append Document Image".
- Set the Value to "N".
- Submit to file the form.
- Open the "Attach Individual Notes to Existing Services/Appointments" form.
- Click "Select Note To Attach".
- Validate a column called "Document" no longer exists on this form.
- Cancel processing and exit the form.
Scenario 2: Attach Individual Notes to Existing Services/Appointments - Auto Append Document Image
Specific Setup:
- Enable Registry Setting "Avatar CWS->Progress Notes->Attach Individual Notes To Existing Services/Appointments->->->Auto Append Document Image" by setting it to "Y".
- Create using "Create New Progress Note" form or use an existing copy of the "Progress Notes (Group and Individual)" form.
- Give Avatar users access to the newly created progress notes form.
- Refresh menus.
- Using "Document Routing Setup", enable document routing for the newly created progress notes form.
- Select a test client with services on file or create services using "Client Charge Input" and appointments on file or create appointments using "Scheduling Calendar".
Steps
- Open the copy of "Progress Notes (Group and Individual)" form:
- Create an independent note and finalize it.
- Sign the document.
- Open the copy of "Progress Notes (Group and Individual)" form:
- Create an independent note and finalize it.
- Sign and route the document.
- Open the "Attach Individual Notes To Existing Services/Appointments" form:
- Select a note that has "Pending" in the "Document" column.
- Validate a message displays stating, "The selected note is associated with a document that is not "Final". The note cannot be attached to an existing service or appointment until the document is finalized.".
- Select a note that has "Final" in the "Document" column.
- Validate a message says "The selected note is associated with a finalized document. Continuing will append the document. Would you like to continue?".
- Select "Appointments" in the "Link Note To".
- Select the specific appointment in the "Appointments/Services" field.
- Click "Submit".
- Validate there is a page appended to the note that indicates what appointment/service the note is now attached to.
- Click "Sign".
- Provide the password for the document.
- Open the "Attach Individual Notes To Existing Services/Appointments" form:
- Select a note that has "Pending" in the "Document" column.
- Validate a message displays stating, "The selected note is associated with a document that is not "Final". The note cannot be attached to an existing service or appointment until the document is finalized.".
- Select a note that has "Final" in the "Document" column.
- Validate a message says "The selected note is associated with a finalized document. Continuing will append the document. Would you like to continue?".
- Select "Services" in the "Link Note To".
- Select the specific service in the "Appointments/Services" field.
- Click "Submit".
- Validate there is a page appended to the note that indicates what appointment/service the note is now attached to.
- Click "Sign".
- Provide the password for the document.
- Open the "Clinical Document Viewer".
- Open the documents filed as final and attached to an existing appointment/service.
- Validate the appended page is included as the last page of the document.
|
Topics
• Registry Settings
• Progress Notes
• Append Progress Notes
|
Task Export/Import - Reason Code and Order Code
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
- Task Definitions
- Task List Export/Import
- Task Associations
- Orders This Episode
Scenario 1: Task List Export/Import - Task Association - Reason and Order Code
Steps
- Access the 'Task Definition' form.
- Select "Add" from the 'Add/Edit Task Definition' field.
- Populate the 'New Task Code' field (Task A) and any other desired fields and click [Submit].
- Access the 'Task Associations' form.
- Set the 'Task Type' field to "Task Definition"
- Set the 'Task Group / Definition' field to "Task A".
- File 'Task Associations' for a 'Reason Code' as well as an 'Order Code'.
- File the form.
- Access the 'Task List Export/Import' form.
- Select 'Specific Task Type' from the 'Export All/Selected Task Types' field.
- Select "Task Associations" from the 'Task Types to Export' field.
- Select "Select Associations" from the 'Export All Task Associations' field.
- Select "Task A" from the 'Task Associations to Export' field.
- Click [Export Selected Task Items] and confirm a "TaskListExport (#).XML" file is downloaded.
- Click [Import Tasks] and then click [Select File To Import].
- Select the recently downloaded "TaskListExport (#).XML" file and then click [Validate Import File].
- Confirm that the 'Validation Results' field contains "Validation completed with no Errors or Warnings.".
- Click [Post Import File], confirm a "File Posted Successfully" message is displayed and click [OK].
- Close the form.
- Access the 'Task Associations' form.
- Set the 'Task Type' field to "Task Definition"
- Set the 'Task Group / Definition' field to "Task A".
- Validate the information filed displays correctly.
Pre-Administration Tasks
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
- Task Definitions
- Task Associations
- Orders This Episode
- eMAR
Scenario 1: eMAR NX - Pre-Administration task warning - Administration Event
|
Topics
• NX
• Task List
• eMAR NX
|
OE NX - Result Notifications Configuration
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
- Review Results
- View Results
- Void Results
- Results Importing
- Result Notification Configuration
- Notifications Setup
Scenario 1: NX - Result Notification Configuration - Abnormal Results
Specific Setup:
- A Client must have an active episode. (Client A)
- "Client A" must have an active lab order. (Order A)
- The staff member associated with the logged in user must be the 'Ordering Practitioner' for "Order A".
- A HL-7 result file must exist for an abnormal result referencing "Client A" and the 'Order Number' associated to "Order A". (Result File A)
Steps
- Access the 'Result Notification Configuration' form.
- Select "Edit" from the 'Add/Edit' field.
- Select "Ordering Practitioner (Abnormal)" from the 'Select Existing Notification Type' field.
- Select "Abnormal" from the 'Notify On Result Type' field.
- Select any value in the 'Result To Do Type' field.
- Select "Ordering Practitioner" in the 'Notify User On Result' field and file the form.
- Access the 'Notifications Setup' form.
- Select "Results Entry: Ordering Practitioner (Abnormal)" from the 'Notification Type' field.
- Select "Popup Notification" as well as any other desired values from the 'Notification Method' field.
- Set the 'Notification Text' field to any value and file the form.
- Access the 'Results Importing' form.
- Set the 'File Path for Import' field to the location of "Result File A " and click [Import].
- Validate the result imports successfully.
- Validate a popup notification is received containing the value entered in the 'Notification Text' field.
- Validate any other 'Notification Method' selected also displays correctly.
Scenario 2: NX - Result Notification Configuration - Normal Results
Specific Setup:
- A client must have an active episode. (Client A)
- "Client A" must have an active lab order (Order A).
- The staff member associated with the logged in user must be the 'Ordering Practitioner' for "Order A".
- A HL-7 result file must exist for a normal result referencing "Client A" and the 'Order Number' associated to "Order A". (Result File A)
Steps
- Access the 'Result Notification Configuration' form.
- Select "Edit" from the 'Add/Edit' field.
- Select "Ordering Practitioner (Results Entry)" from the 'Select Existing Notification Type' field.
- Select "Normal" from the 'Notify On Result Type' field.
- Select any value in the 'Result To Do Type' field.
- Select "Ordering Practitioner" in the 'Notify User On Result' field and file the form.
- Access the 'Notifications Setup' form.
- Select "Results Entry: Ordering Practitioner" from the 'Notification Type' field.
- Select "Popup Notification" as well as any other desired values from the 'Notification Method' field.
- Set the 'Notification Text' field to any value and file the form.
- Access the 'Results Importing' form.
- Set the 'File Path for Import' field to the location of "Result File A " and click [Import].
- Validate the result imports successfully.
- Validate a popup notification is received containing the value entered in the 'Notification Text' field.
- Validate any other 'Notification Method' selected also displays correctly.
|
Topics
• Results
|
'Progress Notes' web service
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
- Progress Notes (Group and Individual)
Scenario 1: File a new progress note using the 'WEBSVC.ProgressNotes.Client.Request' web service
Specific Setup:
- Document routing is not enabled on the 'Progress Notes (Group and Individual)' form.
- The 'Multiple Start and End Times to Document Sessions' registry setting is set to "Y" for the 'Progress Notes (Group and Individual)' form.
- A client must be enrolled in an existing episode (Client A).
- Must have the 'Progress Notes' widget accessible from the HomeView.
Steps
- Access SOAPUI for the 'ProgressNotes.Client.Request' - 'AddProgressNotes' web service.
- Enter the system code that will be used to log on in the 'SystemCode' field.
- Enter the username that will be used to log on in the 'UserName' field.
- Enter the password for the user logging on in the 'Password' field.
- Enter the desired practitioner ID in the 'Practitioner' field.
- Enter the desired value in the 'NotesField' field.
- Enter the desired value in the 'NoteType' field.
- Enter the desired value in the 'Location' field.
- Enter "F" in the 'DraftFinal' field.
- Enter "N" in the 'ProgressNoteFor' field.
- Enter the desired value in the 'ServiceChargeCode' field.
- Enter the desired value in the 'ServiceProgram' field.
- Enter the desired date in the 'DateOfService' field.
- Enter "9:00 AM" in the first 'SessionTimes' - 'StartTime' field.
- Enter "9:30 AM" in the first 'SessionTimes' - 'EndTime' field.
- Enter "10:00 AM" in the second 'SessionTimes' - 'StartTime' filed.
- Enter "10:45 AM" in the second 'SessionTimes' - 'EndTime' field.
- Enter "Client A's" PATID in the 'ClientID' field.
- Enter the desired episode in the 'EpisodeNumber' field.
- Enter "CWSPN22000" in the 'Option' field.
- Click [Run].
- Validate the 'Confirmation' field contains a Unique ID (ex. Unique ID: NOT65244.001).
- Validate the 'Message' field contains: Progress Notes web service has been filed successfully.
- Select "Client A" and navigate to the 'Progress Notes' widget.
- Validate the 'Progress Notes' widget contains the progress note filed via web service in the previous steps.
- Validate the 'Start/End Time(s)' field contains the multiple session start/end times filed in the previous steps.
- Validate the 'Service Duration' field is populated accordingly.
Scenario 2: Edit an existing progress note using the 'WEBSVC.ProgressNotes.Client.Request' web service
Specific Setup:
- Document routing is not enabled on the 'Progress Notes (Group and Individual)' form.
- The 'Multiple Start and End Times to Document Sessions' registry setting is set to "Y" for the 'Progress Notes (Group and Individual)' form.
- A client must be enrolled in an existing episode and have a draft note on file (Client A).
- Must have the 'Progress Notes' widget accessible from the HomeView.
Steps
- Access SOAPUI for the 'ProgressNotes.Client.Request' - 'EditProgressNotes' web service.
- Enter the system code that will be used to log on in the 'SystemCode' field.
- Enter the username that will be used to log on in the 'UserName' field.
- Enter the password for the user logging on in the 'Password' field.
- Enter the desired practitioner ID in the 'Practitioner' field.
- Enter the desired value in the 'NotesField' field.
- Enter the desired value in the 'NoteType' field.
- Enter the desired value in the 'Location' field.
- Enter "F" in the 'DraftFinal' field.
- Enter "N" in the 'ProgressNoteFor' field.
- Enter the desired value in the 'ServiceChargeCode' field.
- Enter the desired value in the 'ServiceProgram' field.
- Enter the desired date in the 'DateOfService' field.
- Enter "10:00 AM" in the first 'SessionTimes' - 'StartTime' field.
- Enter "10:30 AM" in the first 'SessionTimes' - 'EndTime' field.
- Enter "10:30 AM" in the second 'SessionTimes' - 'StartTime' filed.
- Enter "10:45 AM" in the second 'SessionTimes' - 'EndTime' field.
- Enter "Client A's" PATID in the 'ClientID' field.
- Enter the desired episode in the 'EpisodeNumber' field.
- Enter the unique ID for the draft note in the 'NoteUniqueID' field.
- Enter "CWSPN22000" in the 'Option' field.
- Click [Run].
- Validate the 'Confirmation' field contains a Unique ID (ex. Unique ID: NOT65244.001).
- Validate the 'Message' field contains: Progress Notes web service has been filed successfully.
- Select "Client A" and navigate to the 'Progress Notes' widget.
- Validate the 'Progress Notes' widget contains the progress note updated via web service in the previous steps.
- Validate the 'Start/End Time(s)' field contains the multiple session start/end times filed in the previous steps.
- Validate the 'Service Duration' field is populated accordingly.
|
Topics
• Progress Notes
• Web Services
|
Avatar CWS - application mappings
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
- Application Namespace Connections Validation
Scenario 1: Avatar CWS - Validate the migration of global entries in the "^NTSTMAP" Global to the "^RADplusMap" Global
Scenario 2: Application Namespace Connection Validation
Specific Setup:
- Have a system with one or more child namespaces. For example: "PM" or "CWS" namespaces
- Have a system that the following modules installed in the system: "Avatar Data Warehouse", " Avatar CWS State Forms" or "Avatar ProviderConnect NX 2023 " and any other desired modules
Steps
- Open form "Applications Namespace Connection Validations"
- Validate "Currently Connected Namespaces" text box lists the expected child applications and namespace(s):
- Validate "Currently Connected Namespaces" text box indicates there are no application namespace connection or mapping errors.
- Click [Process]
- Validate the "Application Namespace Connections Validation" report list the expected connected child applications and namespace(s)
- Validate "Currently Connected Namespaces" text box indicates there are no application namespace connection or mappings errors.
|
Topics
• Forms
|
'Client Health Maintenance' form
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
- Client Health Maintenance
Internal Test Only
|
Topics
n/a
|
All Documents Widget - Unique form
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
- Treatment Plan
- Create New Treatment Plan
Scenario 1: Treatment Plan - creation of a treatment plan
Specific Setup:
- A client must be enrolled in an existing episode (Client A).
Steps
- Access the 'Treatment Plan' form.
- Search for "Client A" in the 'Select Client' dialog.
- Select "Client A" from the 'Results' field.
- Click [Select].
- Enter the current date in the 'Plan Date' field.
- Select any value from the 'Plan Type' field.
- Select "Draft" from the 'Treatment Plan Status' field.
- Click [Launch Plan] and [Add New Problem].
- Enter any value in the 'Problem Code' field.
- Enter the current date in the 'Date of Onset' field.
- Select "Active" from the 'Status (Problem List)' field.
- Enter any value in the 'Problem' field.
- Click [Back to Plan Page].
- Validate the 'Problems' table contains the problem just added in the previous steps.
- Select "Final" from the 'Treatment Plan Status' field.
- Click [Submit].
Scenario 2: All Documents Widget - Client with multiple treatment plans and treatment plan copies on file
Specific Setup:
- Using "Create New Treatment Plan" form:
- Generate a new treatment plan form copy.
- Using "Document Routing Setup" form:
- Enable document routing for newly created treatment plan form.
- All Documents Widget must be configured and added to a view.
Steps
- Open the "Treatment Plan" form.
- Generate and finalize two treatment plans.
- Open the "Treatment Plan" copy that was created.
- Generate and finalize two of treatment plan copies.
- Open the "Clinical Document Viewer".
- Display all treatment plans created for this test.
- Validate that you can open each one and that each page displays uniquely.
- Select the client in the "MyClients" widget.
- Navigate to the view that contains the "All Documents Widget".
- Display all treatment plans created for this test.
- Validate that you can open each one and that each page displays uniquely.
|
Topics
• Treatment Plan
• Create New Treatment Plan
|
Data Trail - AUDIT.cw_problem_list
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
- Data Trail Configuration
- Problem List
- Treatment Plan
- Treatment Plan Number 1
Scenario 1: Data Trail - Problem List
Specific Setup:
- Using the "Data Trail Configuration" form, select the SYSTEM_cw_problem_list under "Problem List"
Steps
- Open the "Problem List" form.
- Add a new problem.
- Click "Submit" to file data.
- Using the preferred method to view SQL tables, validate a row was added to the "AUDIT.cw_problem_list table and that it has an "audit_action_code" of "A" for Add.
- Open the "Problem List" form.
- Edit an existing problem.
- Click "Submit" to file data.
- Using the preferred method to view SQL tables, validate a row was added to the "AUDIT.cw_problem_list table and that it has an "audit_action_code" of "E" for Edit.
- Open the "Problem List" form.
- Mark a problem as Inactive.
- Click "Submit" to file data.
- Using the preferred method to view SQL tables, validate a row was added to the "AUDIT.cw_problem_list table and that it has an "audit_action_code" of "I" for Inactive.
Scenario 2: DataTrail -Treatment Plan Problems
Specific Setup:
- Open the "Data Trail Configuration" form.
- Select "SYSTEM.cw_problem_list" under Treatment Plan.
Steps
- Open the "Treatment Plan" form.
- Add a problem to the "Problem List".
- Complete and t finalize treatment plan.
- Using the preferred method to validate SQL tables, validate that a row was added to the AUDIT.cw_problem_list with a value of "A" in the audit_action_code.
- Open the "Treatment Plan" form.
- Modify an existing problem in the "Problem List".
- Complete and t finalize treatment plan.
- Using the preferred method to validate SQL tables, validate that a row was added to the AUDIT.cw_problem_list with a value of "E" in the audit_action_code.
Scenario 3: Data Trail - Treatment Plan Copies - Problems
Specific Setup:
- Open the "Data Trail Configuration" form.
- Select "SYSTEM.cw_problem_list" under Treatment Plan.
- Using the "Create New Treatment Plan"
- Create a copy of the treatment plan form.
- Using "User Definition"
- Add the new treatment plan form to the user's "Forms and Tables to Access".
Steps
- Open the Treatment Plan copy form.
- Add a problem to the "Problem List".
- Complete and finalize treatment plan.
- Using the preferred method to validate SQL tables, validate that a row was added to the AUDIT.cw_problem_list with a value of "A" in the audit_action_code.
- Open the Treatment Plan copy form.
- Modify an existing problem in the "Problem List".
- Complete and finalize treatment plan.
- Using the preferred method to validate SQL tables, validate that a row was added to the AUDIT.cw_problem_list with a value of "E" in the audit_action_code.
Data Trail - AUDIT.noniscrxstorage
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
- Order Entry Console
- Home Medications
Scenario 1: Validate Data Trail tables AUDIT.rxstorage, AUDIT_rxdosagestorage
Specific Setup:
- Add the "Order Console Widget" to the user's home view.
Steps
- Navigate to the "Order Console Widget".
- Add a medication to the Home Medications tab.
- Using the preferred method to validate SQL tables, validate a row is added to the AUDIT.rxdosagestorage with an "A" in the audit_action_code.
- Return to the "Orders Console Widget".
- Modify the medication entered on the Home Medications tab.
- Using the preferred method to validate SQL tables, validate a row is added to the AUDIT.rxdosagestorage with an "E" in the audit_action_code.
- Return to the "Orders Console Widget".
- Discontinue the medication entered on the Home Medications tab.
- Using the preferred method to validate SQL tables, validate a row is added to the AUDIT.rxdosagestorage with an "E" in the audit_action_code.
- Using the preferred method to validate SQL tables, validate a row is added to the AUDIT.rxdosagestorage with an "R" in the audit_action_code.
Scenario 2: Validate DataTrail audit tables AUDIT.noniscrxstorage
Specific Setup:
- Add the "Order Console Widget" to the user's home view.
Steps
- Navigate to the "Order Console Widget".
- Add a reported medication to the Home Medications tab.
- Using the preferred method to validate SQL tables, validate a row is added to the AUDIT.rxdosagestorage with an "A" in the audit_action_code.
- Return to the "Orders Console Widget".
- Modify the reported medication entered on the Home Medications tab.
- Using the preferred method to validate SQL tables, validate a row is added to the AUDIT.rxdosagestorage with an "E" in the audit_action_code.
Data Trail - AUDIT.cw_hist_client_allergies
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
- Data Trail Configuration
- Allergies and Hypersensitivities
Scenario 1: Data Trail - Allergies and Hypersensitivities
Specific Setup:
- Open the "Data Trail Configuration" form.
- Select the SYSTEM.cw_hist_client_allergies table.
Steps
- Open the "Allergies and Hypersensitivities" form.
- Add an allergy to the client.
- Save the data and file the form.
- Using the preferred method of validating SQL table, validate a row has been added to the AUDIT.cw_hist_client_allergies table and the row has an "A" in the audit_action_code.
- Open the "Allergies and Hypersensitivities" form.
- Edit an allergy for the client.
- Save the data and file the form.
- Using the preferred method of validating SQL table, validate a row has been added to the AUDIT.cw_hist_client_allergies table and the row has an "E" in the audit_action_code.
Data Trail - AUDIT_cw_implantable_device
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
- Data Trail Configuration
- Implantable Device List
Scenario 1: Data Trail- Implantable Devices
Specific Setup:
- Open the "Data Trail Configuration" form.
- Select the System.cw_implantable_device table.
Steps
- Open the "Implantable Device List" form.
- Assign an implantable device to a client.
- Using the preferred method to view SQL tables, validate a row is added to the AUDIT.cw_implantable_device table with an "A" in the audit_action_code.
- Open the "Implantable Device List" form.
- Change the "Status" to "Completed".
- Using the preferred method to view SQL tables, validate a row is added to the AUDIT.cw_implantable_device table with an "E" in the audit_action_code.
- Open the "Implantable Device List" form.
- Change the "Status" to "Aborted".
- Using the preferred method to view SQL tables, validate a row is added to the AUDIT.cw_implantable_device table with an "D" in the audit_action_code.
Data Trail - AUDIT.rxdosagestorage and AUDIT.rxstorage
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
- Order Entry Console
- Home Medications
Scenario 1: Validate Data Trail tables AUDIT.rxstorage, AUDIT_rxdosagestorage
Specific Setup:
- Add the "Order Console Widget" to the user's home view.
Steps
- Navigate to the "Order Console Widget".
- Add a medication to the Home Medications tab.
- Using the preferred method to validate SQL tables, validate a row is added to the AUDIT.rxdosagestorage with an "A" in the audit_action_code.
- Return to the "Orders Console Widget".
- Modify the medication entered on the Home Medications tab.
- Using the preferred method to validate SQL tables, validate a row is added to the AUDIT.rxdosagestorage with an "E" in the audit_action_code.
- Return to the "Orders Console Widget".
- Discontinue the medication entered on the Home Medications tab.
- Using the preferred method to validate SQL tables, validate a row is added to the AUDIT.rxdosagestorage with an "E" in the audit_action_code.
- Using the preferred method to validate SQL tables, validate a row is added to the AUDIT.rxdosagestorage with an "R" in the audit_action_code.
Data Trail Configuration - Added tables
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
- Data Trail Configuration
- Problem List
- Treatment Plan
- Allergies and Hypersensitivities
- Implantable Device List
- Treatment Plan Number 1
Scenario 1: Data Trail - Problem List
Specific Setup:
- Using the "Data Trail Configuration" form, select the SYSTEM_cw_problem_list under "Problem List"
Steps
- Open the "Problem List" form.
- Add a new problem.
- Click "Submit" to file data.
- Using the preferred method to view SQL tables, validate a row was added to the "AUDIT.cw_problem_list table and that it has an "audit_action_code" of "A" for Add.
- Open the "Problem List" form.
- Edit an existing problem.
- Click "Submit" to file data.
- Using the preferred method to view SQL tables, validate a row was added to the "AUDIT.cw_problem_list table and that it has an "audit_action_code" of "E" for Edit.
- Open the "Problem List" form.
- Mark a problem as Inactive.
- Click "Submit" to file data.
- Using the preferred method to view SQL tables, validate a row was added to the "AUDIT.cw_problem_list table and that it has an "audit_action_code" of "I" for Inactive.
Scenario 2: DataTrail -Treatment Plan Problems
Specific Setup:
- Open the "Data Trail Configuration" form.
- Select "SYSTEM.cw_problem_list" under Treatment Plan.
Steps
- Open the "Treatment Plan" form.
- Add a problem to the "Problem List".
- Complete and t finalize treatment plan.
- Using the preferred method to validate SQL tables, validate that a row was added to the AUDIT.cw_problem_list with a value of "A" in the audit_action_code.
- Open the "Treatment Plan" form.
- Modify an existing problem in the "Problem List".
- Complete and t finalize treatment plan.
- Using the preferred method to validate SQL tables, validate that a row was added to the AUDIT.cw_problem_list with a value of "E" in the audit_action_code.
Scenario 3: Data Trail - Allergies and Hypersensitivities
Specific Setup:
- Open the "Data Trail Configuration" form.
- Select the SYSTEM.cw_hist_client_allergies table.
Steps
- Open the "Allergies and Hypersensitivities" form.
- Add an allergy to the client.
- Save the data and file the form.
- Using the preferred method of validating SQL table, validate a row has been added to the AUDIT.cw_hist_client_allergies table and the row has an "A" in the audit_action_code.
- Open the "Allergies and Hypersensitivities" form.
- Edit an allergy for the client.
- Save the data and file the form.
- Using the preferred method of validating SQL table, validate a row has been added to the AUDIT.cw_hist_client_allergies table and the row has an "E" in the audit_action_code.
Scenario 4: Data Trail- Implantable Devices
Specific Setup:
- Open the "Data Trail Configuration" form.
- Select the System.cw_implantable_device table.
Steps
- Open the "Implantable Device List" form.
- Assign an implantable device to a client.
- Using the preferred method to view SQL tables, validate a row is added to the AUDIT.cw_implantable_device table with an "A" in the audit_action_code.
- Open the "Implantable Device List" form.
- Change the "Status" to "Completed".
- Using the preferred method to view SQL tables, validate a row is added to the AUDIT.cw_implantable_device table with an "E" in the audit_action_code.
- Open the "Implantable Device List" form.
- Change the "Status" to "Aborted".
- Using the preferred method to view SQL tables, validate a row is added to the AUDIT.cw_implantable_device table with an "D" in the audit_action_code.
Scenario 5: Data Trail - Treatment Plan Copies - Problems
Specific Setup:
- Open the "Data Trail Configuration" form.
- Select "SYSTEM.cw_problem_list" under Treatment Plan.
- Using the "Create New Treatment Plan"
- Create a copy of the treatment plan form.
- Using "User Definition"
- Add the new treatment plan form to the user's "Forms and Tables to Access".
Steps
- Open the Treatment Plan copy form.
- Add a problem to the "Problem List".
- Complete and finalize treatment plan.
- Using the preferred method to validate SQL tables, validate that a row was added to the AUDIT.cw_problem_list with a value of "A" in the audit_action_code.
- Open the Treatment Plan copy form.
- Modify an existing problem in the "Problem List".
- Complete and finalize treatment plan.
- Using the preferred method to validate SQL tables, validate that a row was added to the AUDIT.cw_problem_list with a value of "E" in the audit_action_code.
|
Topics
• Problem List
• NX
• Treatment Plan
• Widgets
• Order Entry Console
• Allergies and Hypersensitivities
• Implantable Device List
|
Task List - Follow-Up Reminders
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
Scenario 1: eMAR NX - Administration Event - Follow-Up Reminder
|
Topics
• NX
• eMAR NX
|
Clinical Document Viewer - Service Date
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
- Progress Notes (Group and Individual)
Scenario 1: Clinical Document Viewer - Validating Service Date
Specific Setup:
- Set the registry setting "Post Appointment When The Note Is Submitted" to "N".
- Using the "Document Routing Setup" form:
- Enable Document Routing for any progress notes form.
Steps
- Open the "Scheduling Calendar" form.
- Create an appointment.
- Open the progress note form setup that was enabled for document routing.
- Create and finalize a progress note for the appointment.
- Open the "Clinical Document Viewer" form.
- Locate the row that contains the progress note that was finalized.
- Validate the "Service Date" columns is populated with the date of the progress note.
Scenario 2: Progress Notes (Group and Individual) - Validate document routing
Specific Setup:
- Document routing must be enabled for the "Progress Notes (Group and Individual)" form.
Steps
- Open the "Progress Notes (Group and Individual)" form.
- Create and finalize a document.
- Sign the document.
- Using "Clinical Document Viewer", view and print the document.
- Validate the document displays and prints.
- Open the "Progress Notes (Group and Individual)" form.
- Create and route a progress note to an approver.
- Sign on as the approver.
- Locate the document in the approver's "My To Do's" widget.
- Click on "Approve Document" and approve the document.
- Using the "Clinical Document Viewer", view the document that was just approved.
- Open the "Progress Notes (Group and Individual)" form.
- Create and route a note to multiple approvers.
- Sign on as the first approver.
- Locate the document in the approver's "My To Do's" widget.
- Click on "Approve Document".
- Click "Accept".
- Enter the approver's password.
- Log on as another approver.
- Locate the document in the approver's "My To Do's" widget.
- Click on "Approve Document".
- Click "Accept".
- Enter the approver's password.
- Open the "Clinical Document Viewer" form.
- Select the document that was just routed/finalized.
- Validate that the document displays and prints.
- Open the "Progress Notes (Group and Individual)" form.
- Create a progress note and route to several approvers.
- Log on as another approver.
- Locate the document in the approver's "My To Do's" widget.
- Click on "Approve Document".
- Click "Accept".
- Enter the approver's password.
- Repeat steps 11b-12c for each additional approver.
- Open "Clinical Document Viewer".
- Validate the document that was just filed display and prints.
|
Topics
• Clinical Document Viewer
|
Manage Observer Caseload - 'Observer.caseload_audit' SQL table
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
- Manage Observer Caseload
- ProgressNote Approval
Scenario 1: Manage Observer Caseload - Clear Caseload - Validate the 'Allow Clear All Caseloads' registry setting
Specific Setup:
- A client is enrolled in an existing inpatient episode (Client A).
- "Client A" is not part of the logged in user's caseload (User A).
Steps
- Access the 'Registry Settings' form.
- Enter "Allow Clear All Caseloads" in the 'Limit Registry Settings to the Following Search Criteria' field.
- Click [View Registry Settings].
- Validate the default 'Registry Setting Value' is "Y".
- Validate the 'Registry Setting Details' field contains: Enter 'Y' to allow 'Clear All Caseloads' in the 'Manage Observer Caseload' form. Enter 'N' to disallow 'Clear All Caseloads' in the 'Manage Observer Caseload' form.
- Click [Submit] and close the form.
- Access the 'Manage Observer Caseload' form.
- Search for and select "User A" in the 'Select User' field.
- Select "Add" in the 'Add or Remove Client From Caseload' field.
- Select the unit that "Client A" is admitted into in the 'Unit' field.
- Select "Client A" in the 'Select Clients' field.
- Click [Update Caseload].
- Validate the 'Current Caseload' field contains "Client A".
- Select the "Clear All Caseloads" section.
- Click [Clear All Caseloads].
- Validate a message is displayed stating: You are about to clear observation caseloads for all users. Do you want to continue?
- Click [OK].
- Validate a message is displayed stating: This action cannot be undone. Please be aware that by continuing, the caseloads will be cleared for all users. Do you want to continue?
- Click [OK].
- Validate a message is displayed stating: NTST Observer caseloads are cleared for all users.
- Click [OK].
- Select the "Manage Caseload" section.
- Search for and select "User A" in the 'Select User' field.
- Validate the 'Current Caseload' field no longer contains "Client A".
- Close the form.
- Access the 'Registry Settings' form.
- Enter "Allow Clear All Caseloads" in the 'Limit Registry Settings to the Following Search Criteria' field.
- Click [View Registry Settings].
- Enter "N" in the 'Registry Setting Value' field.
- Click [Submit] and close the form.
- Access the 'Manage Observer Caseload' form.
- Search for and select "User A" in the 'Select User' field.
- Select "Add" in the 'Add or Remove Client From Caseload' field.
- Select the unit that "Client A" is admitted into in the 'Unit' field.
- Select "Client A" in the 'Select Clients' field.
- Click [Update Caseload].
- Validate the 'Current Caseload' field contains "Client A".
- Select the "Clear All Caseloads" section.
- Click [Clear All Caseloads].
- Validate a message is displayed stating: 'Clear All Caseloads' is not allowed.
- Click [OK].
- Select the "Manage Caseload" section.
- Validate "Client A" is still displayed in the 'Current Caseload' field.
- Close the form.
Scenario 2: Manage Observer Caseload - Transfer Caseload - Validate Caseload Report
Specific Setup:
- Two users are defined with associated practitioners that have credentials on file (User A & User B).
- A client is enrolled in an existing inpatient episode (Client A).
- "Client A" is not in the observer caseload of "User A" or "User B".
Steps
- Access the 'Manage Observer Caseload' form.
- Select "User A" in the 'Select User' field.
- Select "Add" in the 'Add or Remove Client From Caseload' field.
- Select the unit "Client A" is admitted into in the 'Unit' field.
- Select "Client A" in the 'Select Clients' field.
- Click [Update Caseload].
- Validate the 'Current Caseload' field contains "Client A".
- Select the "Transfer Caseload" section.
- Select "User A" in the 'Transfer Caseload From' field.
- Validate the 'Credentials (From Staff)' field is read-only and contains the practitioner credentials for "User A".
- Select "User B" in the 'Transfer Caseload To' field.
- Validate the 'Credentials (To Staff)' field is read-only and contains the practitioner credentials for "User B".
- Select "Client A" in the 'Select Clients' field.
- Validate the 'Caseload Assigned By' field contains the logged in user. This can be updated, if desired.
- Select the desired value in the 'Transfer Caseload Reason' field. Note: this is a user defined dictionary - user can right click to add dictionary values.
- Click [Transfer Caseload].
- Validate a message is displayed stating: Selected client(s) will be transferred from the caseload of "User A" to "User B". Are you sure?
- Click [OK] and [Run Caseload Report].
- Validate the report is displayed and contains the following:
- For "User B" there will be a record for "Client A" with the following details:
- Action - Added
- Assigned Date - Transfer date
- Assigned Time - Transfer time
- Caseload Assigned By - User selected in the 'Caseload Assigned By' field
- Reason - Value selected in the 'Transfer Caseload Reason' field
- For "User A" there will be a record for "Client A" with the following details:
- Action - Removed
- Assigned Date - Transfer date
- Assigned Time - Transfer time
- Caseload Assigned By - User selected in the 'Caseload Assigned By' field
- Reason - Value selected in the 'Transfer Caseload Reason' field'
- Close the report and the form.
- Access Crystal Reports or other SQL Reporting tool.
- Select the CWS namespace.
- Create a report using the 'Observer.caseload_audit' SQL table.
- Validate there are two rows for the caseload transfer from "User A" to "User B".
- Validate the 'assigned_by_user_id' and 'assigned_by_user_name' fields contain the 'Caseload Assigned By' user if populated, if not, the logged in user.
- Close the report.
Scenario 3: Manage Observer Caseload - Manage Caseload - Validate Caseload Report
Specific Setup:
- A user is defined with an associated practitioner that has credentials on file (User A).
- A client is enrolled in an existing inpatient episode (Client A).
- "Client A" is not in "User A's" observer caseload.
Steps
- Access the 'Manage Observer Caseload' form.
- Select "User A" in the 'Select User' field.
- Validate the 'Credentials' field is read-only and contains the practitioner credentials for "User A".
- Validate the 'Caseload Assigned By' field contains the logged in user. This can be updated, if desired.
- Select "Add" in the 'Add or Remove Client From Caseload' field.
- Validate the 'Reason to Remove Caseload' field is disabled. This field will only be enabled when "Remove" is selected in the 'Add or Remove Client From Caseload' field.
- Select the unit "Client A" is admitted into in the 'Unit' field.
- Click [Update Caseload].
- Validate the 'Current Caseload' field contains "Client A".
- Click [Run Caseload Report].
- Validate the report is displayed and contains the following:
- For "User A" there will be a record for "Client A" with the following details:
- Action - Added
- Assigned Date - Added date
- Assigned Time - Added time
- Caseload Assigned By - User selected in the 'Caseload Assigned By' field
- Close the report.
- Access Crystal Reports or other SQL Reporting tool.
- Select the CWS namespace.
- Create a report using the 'Observer.caseload_audit' SQL table.
- Validate there is a row for "Client A" being added to "User A" caseload.
- Validate the 'assigned_by_user_id' and 'assigned_by_user_name' fields contain the 'Caseload Assigned By' user if populated, if not, the logged in user.
- Validate the 'assigned_date' contains the date "Client A" was added.
- Validate the 'assigned_time' field contains the time "Client A" was added.
- Validate the 'assigned_to_user_id' and 'assigned_to_user_name' fields contain "User A".
- Validate the 'PATID' field contains "Client A".
- Validate the 'action_code' field contains "A".
- Validate the 'action_value' field contains "Added".
- Validate the 'client_name' field contains "Client A".
- Validate the 'credentials_code', 'credentials_shval', and 'credentials_value' fields contains the credential codes/values for "User A".
- Navigate back to the 'Manage Observer Caseload' form.
- Validate the 'Select User' field contains "User A".
- Validate the 'Caseload Assigned By' field contains the logged in user.
- Select "Remove" in the 'Add or Remove Client From Caseload' field.
- Validate the 'Reason to Remove Caseload' field is now enabled.
- Select the desired value in the 'Reason to Remove Caseload' field. Note: this is a user defined dictionary - user can right click to add dictionary values.
- Select "Client A" in the 'Select Clients' field.
- Click [Update Caseload].
- Validate a message is displayed stating: You are about to remove the selected client(s) from the caseload of "User A". Are you sure you want to continue?
- Click [OK].
- Validate the 'Current Caseload' field does not contain "Client A".
- Click [Run Caseload Report].
- Validate the report is displayed and contains the following:
- For "User A" there will be a record for "Client A" with the following details:
- Action - Removed
- Assigned Date - Removed date
- Assigned Time - Removed time
- Caseload Assigned By - User selected in the 'Caseload Assigned By' field
- Reason - Value selected in the 'Reason to Remove Caseload' field
- Close the report and the form.
- Access Crystal Reports or other SQL Reporting tool.
- Refresh the report using the 'Observer.caseload_audit' SQL table.
- Validate there is a row for "Client A" being removed from "User A" caseload.
- Validate the 'assigned_by_user_id' and 'assigned_by_user_name' fields contain the 'Caseload Assigned By' user if populated, if not, the logged in user.
- Validate the 'assigned_date' contains the date "Client A" was removed.
- Validate the 'assigned_time' field contains the time "Client A" was removed.
- Validate the 'assigned_to_user_id' and 'assigned_to_user_name' fields contain "User A".
- Validate the 'PATID' field contains "Client A".
- Validate the 'action_code' field contains "R".
- Validate the 'action_value' field contains "Removed".
- Validate the 'client_name' field contains "Client A".
- Validate the 'credentials_code', 'credentials_shval', and 'credentials_value' fields contains the credential codes/values for "User A".
- Validate the 'removal_code' and 'removal_value' field contains the corresponding code/value for the value selected in the 'Reason to Remove Caseload' field.
- Close the report.
|
Topics
• Registry Settings
• Manage Observer Caseload
|
Progress Notes - Support for Patient Calendar functionality
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
- Ambulatory Progress Notes (Diagnosis Entry)
- Inpatient Progress Notes (Diagnosis Entry)
- Progress Notes (Group and Individual)
- Ambulatory Progress Notes
Scenario 1: Progress Notes (Group and Individual) - File a note for a client only service
Specific Setup:
- A client must be enrolled in an existing episode (Client A).
- A "Client Only" service code must be defined in the 'Service Codes' form (Service Code A).
- The 'Progress Notes' widget must be on the HomeView.
Steps
- Access the 'Progress Notes (Group and Individual)' form.
- Select "Client A" in the 'Select Client' field.
- Select any value in the 'Select Episode' field.
- Select "New Service" in the 'Progress Notes For' field.
- Select any value in the 'Note Type' field.
- Enter any value in the 'Notes Field'.
- Enter the current date in the 'Date of Service' field.
- Select "Service Code A" in the 'Service Charge Code' field.
- Populate any other required and desired fields.
- Select "Final" from the 'Draft/Final' field.
- Click [File Note].
- Validate a "Progress Notes" dialog is displayed stating: Note Filed. Do you want to return to the Progress Notes form?
- Click [No].
- Select "Client A" and navigate to the 'Progress Notes' widget.
- Validate the note filed in the previous steps is displayed.
- Access the 'Client Ledger' form.
- Search "Client A" in the 'Client ID' field.
- Select "All Episodes" from the 'Claim/Episode/All Episodes' field.
- Select "Simple" in the 'Ledger Type' field.
- Select "Yes" in the 'Include Zero Charges' field.
- Click [Process].
- Validate "Service Code A" is displayed in the Client Ledger.
- Close the form.
Scenario 2: Ambulatory Progress Notes - File a note for a client only service
Specific Setup:
- The 'Allow Client Only Services in the Scheduling Calendar' registry setting must be set to "Y". Please note: this is only supported in Avatar NX.
- A client must be enrolled in an existing outpatient episode (Client A).
- A "Client Only" service code must be defined in the 'Service Codes' form (Service Code A).
- The 'Progress Notes' widget must be on the HomeView.
- "Client A" must have a client only appointment scheduled in the 'Scheduling Calendar' using "Service Code A". Please note: this is only supported in Avatar NX.
Steps
- Select "Client A" and access the 'Ambulatory Progress Notes' form.
- Select "Existing Appointment" in the 'Progress Note For' field.
- Select the existing appointment for "Service Code A" in the 'Note Addresses Which Existing Service/Appointment' field.
- Select the desired value in the 'Note Type' field.
- Enter the desired value in the 'Notes Field'.
- Populate any other required and desired fields.
- Select "Final" in the 'Draft/Final' field.
- Submit the note.
- Select "Client A" and navigate to the 'Progress Notes' widget.
- Validate the note filed in the previous steps is displayed.
- Access the 'Client Ledger' form.
- Search "Client A" in the 'Client ID' field.
- Select "All Episodes" from the 'Claim/Episode/All Episodes' field.
- Select "Simple" in the 'Ledger Type' field.
- Select "Yes" in the 'Include Zero Charges' field.
- Click [Process].
- Validate "Service Code A" is displayed in the Client Ledger.
- Close the form.
Scenario 3: Inpatient Progress Notes - File a note for a client only service
Specific Setup:
- A client must be enrolled in an existing inpatient episode (Client A).
- A "Client Only" service code must be defined in the 'Service Codes' form (Service Code A).
- "Client A" has an existing service for "Service Code A" filed in 'Client Charge Input'.
- The 'Progress Notes' widget must be on the HomeView.
Steps
- Select "Client A" and access the 'Inpatient Progress Notes' form.
- Select "Existing Service" in the 'Progress Note For' field.
- Select the existing service for "Service Code A" in the 'Note Addresses Which Existing Service/Appointment' field.
- Select the desired value in the 'Note Type' field.
- Enter the desired value in the 'Notes Field'.
- Populate any other required and desired fields.
- Select "Final" in the 'Draft/Final' field.
- Submit the note.
- Select "Client A" and navigate to the 'Progress Notes' widget.
- Validate the note filed in the previous steps is displayed.
- Access the 'Client Ledger' form.
- Search "Client A" in the 'Client ID' field.
- Select "All Episodes" from the 'Claim/Episode/All Episodes' field.
- Select "Simple" in the 'Ledger Type' field.
- Select "Yes" in the 'Include Zero Charges' field.
- Click [Process].
- Validate "Service Code A" is displayed in the Client Ledger.
- Close the form.
Bells Notes Integration - Evidence-Based Practices
Scenario 1: Bells Notes Integration - Progress Notes (Group and Individual) - Validate sending 'Evidence-Based Practices'
Specific Setup:
- myAvatar must be configured to integrate with Bells Notes. Please note: this must be done by a Netsmart Associate.
- The 'Progress Notes (Group and Individual)' form must have 'Document Routing' enabled.
- The 'Enable Evidence Based Practice Fields' registry setting must be set to "Y".
- Must have a note type in Bells for the 'Progress Notes (Group and Individual)' form with the 'Evidence-Based Practices' field available (Note Type A).
- A user is defined with the following (User A):
- Access to Bells Notes
- Associated practitioner
- Does not require a supervisor's approval for document routing
- Access to the 'My To Do's' and 'Progress Notes' widgets on the HomeView.
- A client is enrolled in an existing episode (Client A)
Steps
- 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 "Note Type A".
- Verify the existence of "Client A" in the client header when note is started.
- Fill out all required fields.
- Select the desired value(s) in the 'Evidence-Based Practices' field.
- 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.
- Validate a 'To-Do' is displayed for the note sent via Bells Notes for "Client A".
- Click [Approve Document].
- Validate the progress note data is displayed, including the value(s) selected in the 'Evidence-Based Practices' field.
- Click [Accept].
- Enter the password for "User A" in the 'Verify Password' field and click [OK].
- Validate the 'To-Do' is no longer displayed.
- Select "Client A" and navigate to the 'Progress Notes' widget.
- Validate the progress note filed from Bells Notes is displayed.
- Validate the progress note data is displayed, including the value(s) selected in the 'Evidence-Based Practices' field.
Scenario 2: Bells Notes Integration - Ambulatory Progress Notes - Validate sending 'Evidence-Based Practices'
Specific Setup:
- myAvatar must be configured to integrate with Bells Notes. Please note: this must be done by a Netsmart Associate.
- The 'Ambulatory Progress Notes' form must have 'Document Routing' enabled.
- The 'Enable Evidence Based Practice Fields' registry setting must be set to "Y".
- Must have a note type in Bells for the 'Ambulatory Progress Notes' form with the 'Evidence-Based Practices' field available (Note Type A).
- A user is defined with the following (User A):
- Access to Bells Notes
- Associated practitioner
- Does not require a supervisor's approval for document routing
- Access to the 'My To Do's' and 'Progress Notes' widgets on the HomeView.
- A client is enrolled in an existing outpatient episode (Client A)
Steps
- 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 "Note Type A".
- Verify the existence of "Client A" in the client header when note is started.
- Fill out all required fields.
- Select the desired value(s) in the 'Evidence-Based Practices' field.
- 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.
- Validate a To-Do is displayed for the note sent via Bells Notes for "Client A".
- Click [Approve Document].
- Validate the progress note data is displayed, including the value(s) selected in the 'Evidence-Based Practices' field.
- Click [Accept].
- Enter the password for "User A" in the 'Verify Password' field and click [OK].
- Validate the To-Do is no longer displayed.
- Select "Client A" and navigate to the 'Progress Notes' widget.
- Validate the progress note filed from Bells Notes is displayed.
- Validate the progress note data is displayed, including the value(s) selected in the 'Evidence-Based Practices' field.
Scenario 3: Bells Notes Integration - Inpatient Progress Notes - Validate sending 'Evidence-Based Practices'
Specific Setup:
- myAvatar must be configured to integrate with Bells Notes. Please note: this must be done by a Netsmart Associate.
- The 'Inpatient Progress Notes' form must have Document Routing enabled.
- The 'Enable Evidence Based Practice Fields' registry setting must be set to "Y".
- Must have a note type in Bells for the 'Inpatient Progress Notes' form with the 'Evidence-Based Practices' field available (Note Type A).
- A user is defined with the following (User A):
- Access to Bells Notes
- Associated practitioner
- Does not require a supervisor's approval for document routing
- Access to the 'My To Do's' and 'Progress Notes' widgets on the HomeView.
- A client is enrolled in an existing inpatient episode (Client A).
Steps
- 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 "Note Type A".
- Verify the existence of "Client A" in the client header when note is started.
- Fill out all required fields.
- Select the desired value(s) in the 'Evidence-Based Practices' field.
- 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.
- Validate a 'To-Do' is displayed for the note sent via Bells Notes for "Client A".
- Click [Approve Document].
- Validate the progress note data is displayed, including the value(s) selected in the 'Evidence-Based Practices' field.
- Click [Accept].
- Enter the password for "User A" in the 'Verify Password' field and click [OK].
- Validate the To-Do is no longer displayed.
- Select "Client A" and navigate to the 'Progress Notes' widget.
- Validate the progress note filed from Bells Notes is displayed.
- Validate the progress note data is displayed, including the value(s) selected in the 'Evidence-Based Practices' field.
'Progress Notes (Group and Individual)' - Form Return dialog
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
- Progress Notes (Group and Individual)
- Progress Notes (Group and Individual) 4
- Append Progress Notes
- ProgressNote Approval
Scenario 1: 'Progress Notes (Group and Individual)' - New Service note
Specific Setup:
- A client must be defined (Client A).
- The 'Progress Notes' widget must be accessible on the HomeView.
- Set the 'Default Staff Associated With Current Login User' option is "N" in 'Registry Setting'.
Steps
- Access the 'Progress Notes (Group and Individual)' form.
- Select "Client A" in the 'Select Client' field.
- Select "New Service" in the 'Progress Note For' field.
- Select any value in 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 code in the 'Service Charge Code' field.
- Enter any value in the 'Service Duration' field.
- Select "Final" in the 'Draft/Final' field.
- Click [File Note].
- Validate a message is displayed stating: Note Filed. Do you want to return to the Progress Notes form?
- Click [No] and the form closes.
- Select "Client A" and navigate to the 'Progress Notes' widget.
- Validate the note filed in the previous steps is displayed.
Scenario 2: Scheduling Calendar - Launch 'Progress Notes (Group and Individual)' for an appointment
Specific Setup:
- A client is enrolled in an existing episode and has an appointment scheduled (Client A).
- The 'Progress Notes' widget must be accessible on the HomeView.
- The logged in user must have "Progress Notes (Group and Individual)" selected as a form to access from the 'Scheduling Calendar' in the 'User Definition' form.
Steps
- Access the 'Scheduling Calendar' form.
- Validate the 'Appointment Grid' table contains an appointment for "Client A".
- Right click on the appointment for "Client A".
- Click [Progress Notes (Group and Individual)].
- Validate the 'Progress Notes (Group and Individual)' window is displayed.
- Validate the 'Select Client' field contains "Client A".
- Validate the 'Select Episode' field contains "Episode 1".
- Validate the 'Progress Note For' field contains "Existing Appointment".
- Select any value in the 'Note Type' field.
- Enter any value in the 'Notes Field' field.
- Select "Final" in the 'Draft/Final' field.
- Click [File Note].
- Validate a "Progress Notes" message is displayed stating: Note Filed.
- Click [OK].
- Validate the 'Scheduling Calendar' is displayed.
- Click [Dismiss].
- Select "Client A" and access the 'Progress Notes' widget.
- Validate the note filed in the previous steps is displayed.
Scenario 3: Progress Notes (Group and Individual) - Add a progress note via the Client Chart
Specific Setup:
- A client must be enrolled in an existing episode (Client A).
- The 'Progress Notes (Group and Individual)' form must be accessible from the Chart View.
Steps
- Double click on "Client A" in the 'My Clients' widget.
- Verify the 'Chart View' for "Client A" is displayed.
- Select 'Progress Notes (Group & Individual)' on the left-hand side.
- Validate any previously filed notes are displayed for "Client A".
- Click [Add].
- Validate the 'Progress Notes (Group and Individual)' form is displayed.
- Populate all required and desired fields.
- Select "Draft" in the 'Draft/Final' field.
- Click [File Note].
- Validate a message is displayed stating: Note Filed.
- Click [OK].
- Validate the 'Chart View' is displayed.
- Refresh the chart.
- Validate the note filed in the previous steps is displayed.
- Close the chart.
Scenario 4: Progress Notes (Group and Individual) - Launch a draft progress note via To Do
Specific Setup:
- A client is enrolled in an existing episode (Client A).
- The 'Send Draft To-Do to Submitting User' registry setting is set to "Y" for the 'Progress Notes (Group and Individual)' form.
Steps
- Access the 'Progress Notes (Group and Individual)' form.
- Select "Client A" in the 'Select Client' field.
- Select the desired episode in the 'Select Episode' field.
- Select "Independent Note" in the 'Progress Note For' field.
- Enter the desired value in the 'Notes Field'.
- Select the desired value in the 'Note Type' field.
- Select "Draft" in the 'Draft/Final' field.
- Click [File Note].
- Validate a message is displayed stating: Note Filed. Do you want to return to the Progress Notes form?
- Click [No].
- Validate the form closes successfully.
- Navigate to the 'My To Do's' widget.
- Validate there is a 'Review To Do Item' for "Client A".
- Click on the link to [Progress Notes (Group and Individual)].
- Validate the 'Progress Notes (Group and Individual)' form is displayed with the previously filed draft note details.
- Select "Final" in the 'Draft/Final' field.
- Click [File Note].
- Validate a message is displayed stating: Note Filed.
- Click [OK].
- Validate the 'Progress Notes (Group and Individual)' form is closed and the user is brought back to the 'My To Do's' widget.
- Select "Client A" and access the 'Progress Notes' widget.
- Validate the finalized progress note filed in the previous steps is displayed.
|
Topics
• Progress Notes
• CareFabric
• Bells Notes
• Scheduling Calendar
• Chart View
|
Treatment Plan - Item Deletion
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
- Treatment Plan
- Treatment Plan Deletion
Scenario 1: Treatment Plan - validate toggling of the 'Enable Automatic Backup' registry setting
Specific Setup:
- The 'Avatar CWS->Treatment Plan->Enable Automatic Backup' registry setting must be set to "Y".
- A client must be enrolled in an existing episode (Client A).
Steps
- Select "Client A" and access the 'Treatment Plan' form.
- Enter the desired date in the 'Plan Date' field.
- Enter the desired value in the 'Plan Name' field.
- Select the desired value in the 'Plan Type' field.
- Select "Draft" in the 'Treatment Plan Status' field.
- Click [Launch Plan].
- Add a new problem and populate all required and desired fields.
- Click [Back To Plan Page] and 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?"
- Click [Yes].
- Validate the backed up treatment plan data displays.
- Leave the form open.
- Access the 'Registry Settings' form.
- Enter "Enable Automatic Backup" in the 'Limit Registry Settings To The Following Search Criteria' field.
- Click [View Registry Settings].
- Enter "N" in the 'Registry Setting Value' field.
- Click [Submit] and close the form.
- Navigate back to the 'Treatment Plan' form.
- Click [Submit].
- Select "Client A" and access the 'Treatment Plan' form.
- Validate the pre-display contains the draft filed in the previous steps.
- Click [Edit].
- Validate the previously filed data is displayed.
- Close the form.
Scenario 2: Treatmetn Plan Copy - Enable Automatic Backup Registry Setting - Item Deletion
Specific Setup:
- The 'Avatar CWS-> Treatment Plan->->->->Enable Automatic Backup' registry setting must be set to "Y".
- A client must have an active episode. (Client A).
- Using the "Create New Treatment Plan" form, create a copy of the treatment plan.
- The Treatment Plan copy form must be enabled for document routing.
Steps
- Select “Client A” and access the Treatment Plan Copy form.
- Set the ‘Plan Date’ field to the current date.
- Set the ‘Plan Name’ field 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 and click [Add New Goal].
- Set the ‘Goal’ field to any value.
- Select any value in the ‘Status’ field and click [Add New Objective].
- Set the ‘Objective’ field to any value.
- Select any value in the ‘Status’ field and click [Add New Intervention].
- Set the ‘Intervention’ field to any value.
- Select any value in the ‘Status’ field and click [Back to Plan Page].
- Click [Submit].
- Select “Client A” and access the Treatment Plan Copy form.
- Select the treatment plan previously filed and click [Edit].
- Validate the ‘Plan Date’ field contains the current date.
- Validate the ‘Plan Name’ field contains the plan name previously filed.
- Validate the ‘Plan Type’ contains the value previously filed.
- Validate “Draft” is selected in the ‘Treatment Plan Status’ field and click [Launch Plan].
- Validate the Tree View contains the problem, goal, objective, and intervention added in the previous steps.
- Validate [Delete Items Selected] is disabled.
- 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 and click [Add New Goal].
- Set the ‘Goal’ field to any value.
- Select any value in the ‘Status’ field and click [Add New Objective].
- Set the ‘Objective’ field to any value.
- Select any value in the ‘Status’ field and click [Add New Intervention].
- Set the ‘Intervention’ field to any value.
- Select any value in the ‘Status’ field and click [Back to Plan Page].
- Close the form.
- Select “Client A” and access the Treatment Plan Copy form.
- Select the plan previously filed and click [Edit].
- Validate the ‘Load From Backup’ dialog is displayed with a message stating: "You have an unsubmitted back of this plan from [the current date] at [the current time]. Would you like to load it?" and click [Yes].
- Click [Launch Plan].
- Validate the Tree View contains the problem, goal, objective, and intervention added in the previous steps and the problem, goal, objective, and intervention loaded from the backup.
- Select the 2nd intervention item in the Tree View.
- Validate the [Delete Item Selected] is enabled.
- Click [Back to Plan Page] and close the form.
- Access the ‘Registry Setting (PM)’ form.
- Set the ‘Limit Registry Settings to the Following Search Criteria’ field to “Enable Automatic Backup” and click [View Registry Settings].
- Validate the ‘Registry Setting’ field contains “Avatar CWS ->Treatment Plan->->->->Enable Automatic Backup”.
- Validate the ‘Registry Setting Value’ field contains “Y”.
- Set the ‘Registry Setting Value’ field to “YD” and click [Submit].
- Close the form.
- Select “Client A” and access the Treatment Plan Copy form.
- Select the plan previously field and click [Edit].
- Click [Yes] in the ‘Load From Backup’ dialog.
- Click [Launch Plan].
- Select the 1st intervention item in the Tree View.
- Validate [Delete Item Selected] is enabled.
- Select the 2nd intervention item in the Tree View.
- Validate [Delete Item Selected] is enabled.
- Click [Delete Item Selected].
- Validate the ‘Warning’ dialog is displayed with a message stating: “Item Deleted” and click [OK].
- Select the 1st intervention item in the Tree View and click [Delete Item Selected].
- Click [Back to Plan Page] and [Submit].
- Select “Client A” and access the ‘Treatment Plan’ form.
- Select the plan previously field and click [Edit].
- Click [Launch Plan].
- Validate the two intervention items are not displayed in the Tree View.
- Close the form.
- Open the "Registry Settings" form.
- Set the registry setting "Enable Automatic Backup" to "YD".
- Submit the form to file the form.
- Select "Client A" and access the Treatment Plan Copy form.
- Create a new treatment plan.
- Select 2 problems from the "Problem List" table.
- Click "Launch Plan".
- Add multiple goals, objectives, and interventions to the first problem listed.
- Click "Return to Plan Page".
- Set the "Status" field to "Draft".
- Click "Submit".
- Open the Treatment Plan Copy form for the same client.
- Select the plan that was saved in Draft status.
- Click "Launch Plan".
- Click "Return to Plan Page".
- Click "Discard".
- Open the Treatment Plan Copy form for the same client.
- Select the plan that was saved in Draft status.
- Respond "No" to the 'Default from Back Up' message.
- Click "Launch Plan Page".
- Delete the interventions, objectives, and goals for the first problem in the treatment plan.
- Click "Return to Plan Page".
- Click "Submit" and save the plan in draft.
- Open the Treatment Plan Copy form for the same client.
- Select the plan that was saved in Draft status.
- Click "Launch Plan".
- Click "Return to Plan Page".
- Click "Discard".
- Open the Treatment Plan Copy form for the same client.
- Select the plan that was saved in Draft status.
- Respond "No" to the 'Default from Back Up' message.
- Click "Launch Plan Page".
- Delete the 2nd problem on the treatment plan.
- Click "Return to Plan Page".
- Click "Submit".
- Open the Treatment Plan Copy form for the same client.
- Select the plan that was saved in Draft status.
- Respond "No" to the 'Default from Back Up' message.
- Validate the 2nd problem is no longer checked in the "Problem List" table.
- Click "Launch Plan Page".
- Validate the deleted problem isn't listed in the tree view of the plan.
- Set the "Status" to "Final".
- Click "Submit".
- Click "Accept".
- Open the "Clinical Document Viewer".
- Validate one can view the treatment plan that was just finalized.
Treatment Plan - Finalizing Plans
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
- Treatment Plan
- Treatment Plan Deletion
Scenario 1: Treatment Plan - Field Data Validations
Specific Setup:
- Have a treatment plan with a 'disabled ' field, set up as the last field in the Problem, Goals, Objective or Interventions sections. For example, a disabled "Scrolling Free Text" field.
- Have another field set up right before the disabled last field in each section, that requires a selection or input type entry. For example, a "Site Specific" dictionary or integer field.
- Registry Setting "Enable Service Entry Restrictions by Client Treatment Plan "is set to "S".
- Registry Setting "Activate Program/Service Code Filter" = "Y".
Steps
- Open the "Treatment Plan" form:
- Search and select a client in the 'Select Client' field.
- Enter a plan name in the "Plan Name" field.
- Enter the current date in the 'Plan Date' field.
- Select any value from the 'Plan Type' field.
- Select "Draft" from the "Treatment Plan Status" field.
- Click [Launch Plan].
- Click [Add New Problem].
- Enter any value in the 'Problem Code' field.
- Enter any value in the 'Problem' field.
- Enter the current date in the 'Date of Onset' field.
- Select "Active" from the "Status (Problem List)" field.
- Populate any other desired fields, except for the last two fields in the section.
- Navigate to the next to last field, which should be the one located right before the disabled field, as outline in the setup section.
- Select or input a value in the next to last field in the section.
- Click the 'Tab' key.
- Click [Back to Plan Page].
- Validate all data enter on the main section is populated as expected.
- Click [Launch Plan].
- Select the "Problem" added in step 1g.
- Validate all the fields are populated in the section as expected, including the value populated in next to last field of the section.
- Click [Add New Goal].
- Populate all the required and desired fields in the section, except for the last two fields in the section.
- Repeat steps 1m -1q.
- Validate the results are as expected.
- Click [Add New Objective].
- Populate all the required and desired fields in the section, except for the last two fields in the section.
- Repeat steps 1m-1q.
- Validate the results are as expected.
- Click [Add New Intervention].
- Populate all the required and desired fields in the section, except for the last two fields in the section.
- Repeat steps 1m-1q.
- Validate the results are as expected.
- Click [Back to Plan Page].
- Click [Submit].
- Open the "Treatment Plan" form:
- Search and select the same client used in the prior step, in the 'Select Client' field.
- Select the treatment plan just filed.
- Validate all data enter on the main section is populated as expected.
- Click to the view data field in "Problems", "Goals", "Objectives" and "Interventions" sections.
- Validate all data filed is present, as expected.
- Open the "Treatment Plan" form:
- Create another treatment plan for the client.
- Fill out the Problem and Intervention sections.
- In the Intervention, add some "Assigned Services".
- Delete the services that were just entered.
- Validate all the service rows were deleted.
- Click "Back to Plan Page".
- At this point, you can either finalize the form or you can Click "Close Form".
Scenario 2: Treatment Plan - 'Enable Automatic Backup' registry setting - Item Deletion
Specific Setup:
- The 'Avatar CWS-> Treatment Plan->->->->Enable Automatic Backup' registry setting must be set to "Y".
- A client must have an active episode. (Client A)
- The Treatment Plan form must be enabled for document routing.
Steps
- Select “Client A” and access the ‘Treatment Plan’ form.
- Set the ‘Plan Date’ field to the current date.
- Set the ‘Plan Name’ field 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 and click [Add New Goal].
- Set the ‘Goal’ field to any value.
- Select any value in the ‘Status’ field and click [Add New Objective].
- Set the ‘Objective’ field to any value.
- Select any value in the ‘Status’ field and click [Add New Intervention].
- Set the ‘Intervention’ field to any value.
- Select any value in the ‘Status’ field and click [Back to Plan Page].
- Click [Submit].
- Select “Client A” and access the ‘Treatment Plan’ form.
- Select the treatment plan previously filed and click [Edit].
- Validate the ‘Plan Date’ field contains the current date.
- Validate the ‘Plan Name’ field contains the plan name previously filed.
- Validate the ‘Plan Type’ contains the value previously filed.
- Validate “Draft” is selected in the ‘Treatment Plan Status’ field and click [Launch Plan].
- Validate the Tree View contains the problem, goal, objective, and intervention added in the previous steps.
- Validate [Delete Items Selected] is disabled.
- 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 and click [Add New Goal].
- Set the ‘Goal’ field to any value.
- Select any value in the ‘Status’ field and click [Add New Objective].
- Set the ‘Objective’ field to any value.
- Select any value in the ‘Status’ field and click [Add New Intervention].
- Set the ‘Intervention’ field to any value.
- Select any value in the ‘Status’ field and click [Back to Plan Page].
- Close the form.
- Select “Client A” and access the ‘Treatment Plan’ form.
- Select the plan previously filed and click [Edit].
- Validate the ‘Load From Backup’ dialog is displayed with a message stating: "You have an unsubmitted back of this plan from [the current date] at [the current time]. Would you like to load it?" and click [Yes].
- Click [Launch Plan].
- Validate the Tree View contains the problem, goal, objective, and intervention added in the previous steps and the problem, goal, objective, and intervention loaded from the backup.
- Select the 2nd intervention item in the Tree View.
- Validate the [Delete Item Selected] is enabled.
- Click [Back to Plan Page] and close the form.
- Access the ‘Registry Setting (PM)’ form.
- Set the ‘Limit Registry Settings to the Following Search Criteria’ field to “Enable Automatic Backup” and click [View Registry Settings].
- Validate the ‘Registry Setting’ field contains “Avatar CWS ->Treatment Plan->->->->Enable Automatic Backup”.
- Validate the ‘Registry Setting Value’ field contains “Y”.
- Set the ‘Registry Setting Value’ field to “YD” and click [Submit].
- Close the form.
- Select “Client A” and access the ‘Treatment Plan’ form.
- Select the plan previously field and click [Edit].
- Click [Yes] in the ‘Load From Backup’ dialog.
- Click [Launch Plan].
- Select the 1st intervention item in the Tree View.
- Validate [Delete Item Selected] is enabled.
- Select the 2nd intervention item in the Tree View.
- Validate [Delete Item Selected] is enabled.
- Click [Delete Item Selected].
- Validate the ‘Warning’ dialog is displayed with a message stating: “Item Deleted” and click [OK].
- Select the 1st intervention item in the Tree View and click [Delete Item Selected].
- Click [Back to Plan Page] and [Submit].
- Select “Client A” and access the ‘Treatment Plan’ form.
- Select the plan previously field and click [Edit].
- Click [Launch Plan].
- Validate the two intervention items are not displayed in the Tree View.
- Close the form.
- Open the "Registry Settings" form.
- Set the registry setting "Enable Automatic Backup" to "YD".
- Submit the form to file the form.
- Select "Client A" and access the "Treatment Plan" form.
- Create a new treatment plan.
- Select 2 problems from the "Problem List" table.
- Click "Launch Plan".
- Add multiple goals, objectives, and interventions to the first problem listed.
- Click "Return to Plan Page".
- Set the "Status" field to "Draft".
- Click "Submit".
- Open the "Treatment Plan" form for the same client.
- Select the plan that was saved in Draft status.
- Click "Launch Plan".
- Click "Return to Plan Page".
- Click "Discard".
- Open the "Treatment Plan" form for the same client.
- Select the plan that was saved in Draft status.
- Respond "No" to the 'Default from Back Up' message.
- Click "Launch Plan Page".
- Delete the interventions, objectives, and goals for the first problem in the treatment plan.
- Click "Return to Plan Page".
- Click "Submit" and save the plan in draft.
- Open the "Treatment Plan" form for the same client.
- Select the plan that was saved in Draft status.
- Click "Launch Plan".
- Click "Return to Plan Page".
- Click "Discard".
- Open the "Treatment Plan" form for the same client.
- Select the plan that was saved in Draft status.
- Respond "No" to the 'Default from Back Up' message.
- Click "Launch Plan Page".
- Delete the 2nd problem on the treatment plan.
- Click "Return to Plan Page".
- Click "Submit".
- Open the "Treatment Plan" form for the same client.
- Select the plan that was saved in Draft status.
- Respond "No" to the 'Default from Back Up' message.
- Validate the 2nd problem is no longer checked in the "Problem List" table.
- Click "Launch Plan Page".
- Validate the deleted problem isn't listed in the tree view of the plan.
- Set the "Status" to "Final".
- Click "Submit".
- Click "Accept".
- Open the "Clinical Document Viewer".
- Validate one can view the treatment plan that was just finalized.
|
Topics
• Treatment Plan
• NX
|
| |