Avatar CareFabric 2024 Quarterly Release 2024.01 Acceptance Tests

Last updated
Save as PDF

Update 1 Summary \| Details 2024 Update installation Scenario 1: Validate Upgrading Avatar CareFabric 2023 to 2024 is successful when 2023.04.00 is loaded Specific Setup: Latest Monthly Release is installed. 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
Update 2 Summary \| Details Avatar CareFabric - Support for Medical Note Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following: Note Details Medical Note Progress Note Scenario 1: Update CPT Calculation for Low Level MDM based on 2024 Guidelines for New client type (99203) Specific Setup: Avatar CareFabric 2024 Update 2, Medical Note 2.19.1, and Medical Note 2.19.2 are required in order to utilize full functionality. A user with access to the Medical Note Admin Tool must exist. (User A) Logging in as "User A" set the following settings in the Medical Note Admin Tool 'Home' section: Set the value for the '2024 E&M Guidelines Effective Date' field to "01/01/2024". Enable the '2024 E&M MDM Required' field. Enable the 'Use 2024 E&M Guidelines for Inpatient Services' field. A client must be configured in an inpatient episode. (Client A) Steps Search for and select "Client A" and navigate to the 'Medical Note'. Click [Add Note] and create a new note such that: 'Location' = "Office". 'Client Type' = "New". Select the ‘Document’ tab and navigate to the 'Diagnosis' section. Add two new diagnoses for the client and add them both to the problem list. Navigate to the 'MDM' section. Check the 'Problem Addressed?' checkbox for one of the newly added diagnoses. Validate the 'Problem Category' field is enabled. Select "Acute, uncomplicated illness or injury requiring hospital inpatient or observation-level of care" from the 'Problem Category' field. Check the following checkboxes in the 'Amount and/or Complexity of Data to be Reviewed and Analyzed' section: "Review of prior external note(s) from each unique source". Select "Low" from the 'Risk of Complications and/or Morbidity or Mortality of Patient Management' section. Complete any remaining required sections. Select the 'Finalize' tab and navigate to the 'CPT Selection' section. Set 'Face-to-Face Time with Client' field to "30". Click [Debug] and verify the popup window 'CPT Debug' is displayed. Verify the Results section contains: 'CPT Guidelines Version:' = "2024". 'Visit Type:' = "New". 'Location Type:' = "Office or another outpatient setting". 'Visit Duration:' = "30 Minute(s)". Verify the 'MDM: Low' section contains: 'Problem Points:' = "Low". 'Data Points:' = "Minimal or none". 'Risk:' = "Low". Validate the 'CPT Codes: Office or other outpatient visit – new patient' section contains a row such that: 'Code' = "99203". 'MDM Score' = "Low". 'Min Duration' = "30". 'Doc?' = checked. 'Dur?' = checked. Close the 'CPT Debug' window. Validate that code '99203' is displayed on the 'Document-Based Recommendation' card under the section 'CPT Selection'. Validate that code '99203' is displayed on the 'Time-Based Recommendation:' card under the section 'CPT Selection'. Select the 'Document' tab and navigate to the 'MDM' section. Select "Stable, acute illness" from the 'Problem Category' field. Check the following checkboxes in the 'Amount and/or Complexity of Data to be Reviewed and Analyzed' section: "Review of prior external note(s) from each unique source". "Review of the result(s) of each unique test". "Ordering of each unique test". Select the 'Finalize' tab and navigate to the 'CPT Selection' section. Click [Debug] and verify the popup window 'CPT Debug' is displayed. Verify the 'MDM: Low' section contains: 'Problem Points:' = "Low". 'Data Points:' = "Moderate". 'Risk:' = "Low". Close the 'CPT Debug' window. Validate that code '99203' is displayed on the 'Document-Based Recommendation' card under the section 'CPT Selection'. Validate that code '99203' is displayed on the 'Time-Based Recommendation:' card under the section 'CPT Selection'. Select the 'Document' tab and navigate to the 'MDM' section. Check the 'Problem Addressed?' checkbox for the other newly added diagnoses. Validate the 'Problem Category' field is enabled. Select "Acute, uncomplicated illness or injury requiring hospital inpatient or observation-level of care" from the 'Problem Category' field. Check all remaining checkboxes in the 'Amount and/or Complexity of Data to be Reviewed and Analyzed' section Select the 'Finalize' tab and navigate to the 'CPT Selection' section. Click [Debug] and verify the popup window 'CPT Debug' is displayed. Verify the 'MDM: Low' section contains: 'Problem Points:' = "Low". 'Data Points:' = "Extensive". 'Risk:' = "Low". Close the 'CPT Debug' window. Validate that code '99203' is displayed on the 'Document-Based Recommendation' card under the section 'CPT Selection'. Validate that code '99203' is displayed on the 'Time-Based Recommendation:' card under the section 'CPT Selection'. Click 'Accept' on the 'Document-Based Recommendation' card. Validate "99203-Office or other outpatient visit - new patient" is selected in the 'CPT Code Selected' field. Click [Generate Note] and validate the note summary contains a section for 'Medical Decision Making'. Validate the 'Amount and/or Complexity of Data to be Reviewed and Analyzed:" section contains the following: "Review of prior external note(s) from each unique source". "Review of the result(s) of each unique test". "Ordering of each unique test". "Assessment requiring an independent historian(s)". "Independent interpretation of a test performed by another physician/other qualified health care professional (not separately reported)". "Discussion of management or test interpretation with external physician/other qualified health care professional/appropriate source (not separately reported)". Validate the 'Risk of Complications and/or Morbidity or Mortality of Patient Management:' = "Low". Scenario 2: Update CPT Calculation for Low Level MDM based on 2024 Guidelines for Established client type (99213) Specific Setup: Avatar CareFabric 2024 Update 2, Medical Note 2.19.1, and Medical Note 2.19.2 are required in order to utilize full functionality. A user with access to the Medical Note Admin Tool must exist. (User A) Logging in as "User A" set the following settings in the Medical Note Admin Tool 'Home' section: Set the value for the '2024 E&M Guidelines Effective Date' field to "01/01/2024". Enable the '2024 E&M MDM Required' field. Enable the 'Use 2024 E&M Guidelines for Inpatient Services' field. A client must be configured in an inpatient episode. (Client A) Steps Search for and select "Client A" and navigate to the 'Medical Note'. Click [Add Note] and create a new note such that: 'Location' = "Office". 'Client Type' = "Established". Select the ‘Document’ tab and navigate to the 'Diagnosis' section. Add a new diagnosis for the client. Navigate to the 'MDM' section. Check the 'Problem Addressed?' checkbox for the newly added diagnosis. Validate the 'Problem Category' field is enabled. Select "Acute, uncomplicated illness or injury requiring hospital inpatient or observation-level of care" from the 'Problem Category' field. Check the following checkboxes in the 'Amount and/or Complexity of Data to be Reviewed and Analyzed' section: "Ordering of each unique test". "Independent interpretation of a test performed by another physician/other qualified health care professional (not separately reported)". Select "Low" from the 'Risk of Complications and/or Morbidity or Mortality of Patient Management' section. Complete any remaining required sections. Select the 'Finalize' tab and navigate to the 'CPT Selection' section. Set 'Face-to-Face Time with Client' field to "20". Click [Debug] and verify the popup window 'CPT Debug' is displayed. Verify the Results section contains: 'CPT Guidelines Version:' = "2024". 'Visit Type:' = "Established". 'Location Type:' = "Office or another outpatient setting". 'Visit Duration:' = "20 Minute(s)". Verify the 'MDM: Low' section contains: 'Problem Points:' = "Low". 'Data Points:' = "Moderate". 'Risk:' = "Low". Validate the 'CPT Codes: Office or other outpatient visit – established patient' section contains a row such that: 'Code' = "99213". 'MDM Score' = "Low". 'Min Duration' = "20". 'Doc?' = checked. 'Dur?' = checked. Close the 'CPT Debug' window. Verify that code '99213' is displayed on the 'Document-Based Recommendation' card under the section 'CPT Selection'. Verify that code '99213' is displayed on the 'Time-Based Recommendation:' card under the section 'CPT Selection'.	Topics • Medical Note • NX
Update 3 Summary \| Details CareFabric Assessment Mapping - 'System Code(s)' field Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following: HomeView.Generic Assessment Widget Patient Health Questionnaire-A CareFabric Assessment Mapping Scenario 1: CareFabric Assessment Mapping - Validate mappings for multiple root system codes Specific Setup: myAvatar has multiple root system codes defined (System Code 1 & System Code 2). Both system codes are configured for CareFabric. Must have an assessment created using the 'Assessment Design Tool' (Assessment A). Please note: This is a Netsmart only tool. Please contact your Netsmart Representative for more information. A modeled form (Form A) is defined in both "System Code 1" & "System Code 2". Must have the 'Generic Assessment' widget available on the HomeView. A client is enrolled in an existing episode (Client A). Steps Log in with "System Code 1". Access the 'CareFabric Assessment Mapping' form. Select "Assessment A" in the 'Select Assessment' field. Select "Form A" in the 'Select Modeled Form' field. Validate the 'System Code(s)' field is displayed. This will display when there are multiple root system codes defined. Validate "System Code 2" is displayed in the 'System Code(s)' field. Click [Launch Mapping Grid]. Validate no mappings are displayed. Click [Close/Cancel] and close the form. Log out. Log in with "System Code 2". Access the 'CareFabric Assessment Mapping' form. Select "Assessment A" in the 'Select Assessment' field. Select "Form A" in the 'Select Modeled Form' field. Validate the 'System Code(s)' field is displayed. This will display when there are multiple root system codes defined. Select "System Code 1" in the 'System Code(s)' field. Click [Launch Mapping Grid]. Add the desired mappings. Click [Save] and [Yes]. Click [File Mappings] and close the form. Log out. Log in with "System Code 1". Access the 'CareFabric Assessment Mapping' form. Select "Assessment A" in the 'Select Assessment' field. Select "Form A" in the 'Select Modeled Form' field. Validate a message is displayed stating: The form is already mapped in this system code: "System Code 2". Please note: The mapping can only be edited in the root system code it was filed in. Click [OK]. Close the form. Navigate to the 'Generic Assessment' widget for "Client A". File "Assessment A" for the client, populating all required and desired fields that are mapped via 'CareFabric Assessment Mapping'. Select "Client A" and access "Form A". Validate a record is displayed for the assessment filed via the 'Generic Assessment' widget. Click [Edit]. Validate all fields display as expected based on the mappings defined via 'CareFabric Assessment Mapping'. Close the form. CarePOV Management - 'Client Alerts' section Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following: Client Alerts (PM) CarePOV Management Allergies and Hypersensitivities Client Lookup/Header Configuration Manager Scenario 1: CarePOV Management - Client Alerts - Field Validations Steps Access the 'CarePOV Management' form. Select the "Client Alerts" section. Select "Edit" in the 'Add or Edit Alert' field. Select "Alcohol Detox" in the 'Client Alert' field. Validate the 'Selected Diagnosis' field contains a list of diagnoses with codes/descriptions. Validate the 'Selected Problem' field contains a list of problems with codes/descriptions. Select "Fall Risk" in the 'Client Alert' field. Validate the 'Selected Diagnosis' field contains a list of diagnoses with codes/descriptions. Validate the 'Selected Problem' field contains a list of problems with codes/descriptions. Select "High Blood Pressure" in the 'Client Alert' field. Validate the 'Selected Diagnosis' field contains a list of diagnoses with codes/descriptions. Validate the 'Selected Problem' field contains a list of problems with codes/descriptions. Close the form.	Topics • CareFabric Assessment Mapping • Client Alerts • CarePOV Management
Update 4 Summary \| Details TeleHealth - Recurring Appointments Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following: Registry Settings (PM) CareFabric Monitor Scenario 1: Schedule recurring TeleHealth appointment with a TeleHealth service code and validate the TeleHealthAppointmentCreated/Updated/Deleted SDK events Specific Setup: A service code must be defined as a "Telehealth Service" in the 'Service Codes' form. Using the "Admission" form" Admit a new client into any episode. Navigate to the "Demographics" section. Enter a home address, city, state and zip. Enter an email address. Enter a home telephone number. Steps Open the "Scheduling Calendar" form. Schedule a recurring appointment TeleHealth service using a TeleHealth service code. Open the "CareFabric Monitor" form: Run the Activity Log for the following events "TeleHealthAppointmentCreated". Validate that a "TeleHealthAppointmentCreated" event is generated for however many appointments are in the recurrence. Validate that each "TeleHealthAppointmentCreated" event includes the following: Validate the "isReoccuringAppointment" property is "true". Validate the event includes the "RecurrenceInfo" object. Validate the "appointmentDateRange" object. Ensure the date and time are accurate. Validate the "recurrenceInfo" - "startDate" field. Ensure the date and time are accurate. Return to the "Scheduling Calendar": Edit the recurring appointment that was created in previous steps. Change the duration of the service. Open the "CareFabric Monitor" form: Run the Activity Log for the following events "TeleHealthAppointmentUpdated". Validate that a "TeleHealthAppointmentUpdated" event is generated for however many appointments are in the recurrence. Validate that each "TeleHealthAppointmentUpdated" event includes the following: Validate the "isReoccuringAppointment" property is "true". Validate the event includes the "RecurrenceInfo" object. Validate the "appointmentDateRange" object. Ensure the date and time are accurate. Validate the "recurrenceInfo" - "startDate" field. Ensure the date and time are accurate. Return to the "Scheduling Calendar": Delete the recurring appointment that was created and edited in previous steps. Open the "CareFabric Monitor" form: Run the Activity Log for the following events "TeleHealthAppointmentDeleted". Validate that a "TeleHealthAppointmentDeleted" event is generated for however many appointments are in the recurrence. Validate that each "TeleHealthAppointmentDeleted" event includes the following: Validate the "isReoccuringAppointment" property is "true". Validate the event includes the "RecurrenceInfo" object. Scenario 2: Schedule recurring TeleHealth appointment with a TeleHealth location and validate the TeleHealthAppointmentCreated/Updated/Deleted SDK events Specific Setup: Using "Dictionary Update" form: Select the "Client" File. Select data element "(10006) Location". Select one active location and designate it as "Yes" for the extended dictionary data element (586) Is this a Telehealth location?". Using the "Registry Settings" form: Enable the registry setting "Enable Telehealth integration at the location level". Using the "Admission" form: Admit a new client into any episode. Navigate to the "Demographics" section. Enter a home address, city, state and zip. Enter an email address. Enter a home telephone number. Steps Open the "Scheduling Calendar" form: Schedule a recurring appointment TeleHealth service using a TeleHealth location. Open the "CareFabric Monitor" form: Run the Activity Log for the following events "TeleHealthAppointmentCreated". Validate that a "TeleHealthAppointmentCreated" event is generated for however many appointments are in the recurrence. Validate that each "TeleHealthAppointmentCreated" event includes the following: Validate the "isReoccuringAppointment" property is "true". Validate the event includes the "RecurrenceInfo" object. Validate the "appointmentDateRange" object. Ensure the date and time are accurate. Validate the "recurrenceInfo" - "startDate" field. Ensure the date and time are accurate. Return to the "Scheduling Calendar": Edit the recurring appointment that was created in previous steps. Change the duration of the service. Open the "CareFabric Monitor" form: Run the Activity Log for the following events "TeleHealthAppointmentUpdated". Validate that a "TeleHealthAppointmentUpdated" event is generated for however many appointments are in the recurrence. Validate that each "TeleHealthAppointmentUpdated" event includes the following: Validate the "isReoccuringAppointment" property is "true". Validate the event includes the "RecurrenceInfo" object. Validate the "appointmentDateRange" object. Ensure the date and time are accurate. Validate the "recurrenceInfo" - "startDate" field. Ensure the date and time are accurate. Return to the "Scheduling Calendar": Delete the recurring appointment that was created and edited in previous steps. Open the "CareFabric Monitor" form: Run the Activity Log for the following events "TeleHealthAppointmentDeleted". Validate that a "TeleHealthAppointmentDeleted" event is generated for however many appointments are in the recurrence. Validate that each "TeleHealthAppointmentDeleted" event includes the following: Validate the "isReoccuringAppointment" property is "true". Validate the event includes the "RecurrenceInfo" object. TeleHealth - Group Appointments Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following: Group Registration CareFabric Monitor Scheduling Calendar - Add/Remove Group Members Registry Settings (PM) Scenario 1: Schedule a TeleHealth Group appointment with a TeleHealth location and validate the TeleHealthAppointmentCreated/Updated/Deleted SDK events Specific Setup: The 'Enable Telehealth integration at location level' registry setting is set to "Y". A location must be defined as a "TeleHealth Location" in the 'Dictionary Update' form. A client is enrolled in an existing episode and has a phone number and email filed (Client A). A user is defined in 'User Definition' that has the following: "TeleHealth" selected in the 'Netsmart Mobile App Access' field, "System Admin" selected in the 'Netsmart Mobile App User Role' field, an email filed in the 'Organizational Email Address' field, and an associated staff member that has hours for scheduling. Group Telehealth Service codes must be created. The services should indicate they are a Telehealth service by responding to the "Is this a Telehealth Service" with "Yes". A group needs to be selected or created for this testing. Steps Using the "Scheduling Calendar" Add a new group telehealth appointment. Leave this form open. Using the "CareFabric Monitor" form Using filters, locate the "TeleHealthAppointmentCreated" event that was triggered when the appointment was created. Validate the event includes all clients in the group. Leave this form open. Using the "Scheduling Calendar" Right click on the appointment that was just scheduled. Click on "Add/Remove Group Members" to remove a client from the group appointment. Using the "CareFabric Monitor" form Using filters, locate the "TeleHealthAppointmentUpdated" event that was triggered when a group member was removed from the group. Validate the event includes all clients who remain in the group. Leave this form open. Using the "Scheduling Calendar" Right click on the appointment that was just updated. Click on "Delete". Validate the appointment is removed from the calendar. Using the "CareFabric Monitor" form Using filters, locate the "TeleHealthAppointmentDeleted" event that was triggered when the appointment was deleted. Close all forms. Scenario 2: Schedule a TeleHealth Group Appointment with a TeleHealth service code and validate the TeleHealthAppointmentCreated/Updated/Deleted SDK events Specific Setup: A client is enrolled in an existing episode and has a phone number and email filed (Client A). A user is defined in 'User Definition' that has the following: "TeleHealth" selected in the 'Netsmart Mobile App Access' field, "System Admin" selected in the 'Netsmart Mobile App User Role' field, an email filed in the 'Organizational Email Address' field, and an associated staff member that has hours for scheduling. Group Telehealth Service codes must be created. The services should indicate they are a Telehealth service by responding to the "Is this a Telehealth Service" with "Yes". A group needs to be selected or created for this testing. Steps Using the "Scheduling Calendar" Add a new group telehealth appointment. Leave this form open. Using the "CareFabric Monitor" form Using filters, locate the "TeleHealthAppointmentCreated" event that was triggered when the appointment was created. Validate the event includes all clients in the group. Leave this form open. Using the "Scheduling Calendar" Right click on the appointment that was just scheduled. Click on "Add/Remove Group Members" to remove a client from the group appointment. Using the "CareFabric Monitor" form Using filters, locate the "TeleHealthAppointmentUpdated" event that was triggered when a group member was removed from the group. Validate the event includes all clients who remain in the group. Leave this form open. Using the "Scheduling Calendar" Right click on the appointment that was just updated. Click on "Delete". Validate the appointment is removed from the calendar. Using the "CareFabric Monitor" form Using filters, locate the "TeleHealthAppointmentDeleted" event that was triggered when the appointment was deleted. Close all forms.	Topics • Scheduling Calendar • Telehealth • CareFabric Monitor
Update 6 Summary \| Details Medical Note - Prevent Users from Editing a Note that is open in Avatar PM Form Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following: Medical Note Scenario 1: Medical Note - Prevent Users from Editing a Note that is open in PM Form Specific Setup: Avatar CareFabric 2024 Update 6 and Medical Note Release 2.19 is required in order to utilize full functionality. Two users must exist. (User A and User B) A client must have an active episode. (Client A) Steps Log into the application as "User A". Access the 'Scheduling Calendar' and create an appointment for "Client A" and close the form Select "Client A" and access 'Medical Note'. Click [Today's Appts Notes]. Find the appointment for "Client A" and click [Start]. Populate all required fields and click [Save]. Click [Today's Appts Notes] and validate that [Edit] is displayed. Open a new browser and log into the application as "User B". Access the 'Scheduling Calendar'. Right click on the appointment created for "Client A" and select 'Details/Edit'. Access the first browser where "User A" is logged in. Validate that "Client A" is selected and that you are on 'Medical Note'. Click [Today's Appts Notes]. Find the appointment for "Client A" and click [Edit]. Validate an "Appointment Locked. The appointment is currently locked by "User B". Editing is unavailable at this time." and click [Close]. Click on "Client A's" name and click [Select Note]. Find the note for appointment for "Client A" and click [Edit]. Validate an "Appointment Locked. The appointment is currently locked by "User B". Editing is unavailable at this time." and click [Close]. Click [My Draft Notes]. Find the appointment for "Client A" and click [Edit]. Validate an "Appointment Locked. The appointment is currently locked by "User B". Editing is unavailable at this time." and click [Close].	Topics • Appointment Locking
Update 7 Summary \| Details Progress Notes - 'ClinicalNoteFinalized' SDK event Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following: Ambulatory Progress Notes CareFabric Monitor Scenario 1: Clinical Notes Mapping - Progress Notes (Group and Individual) - Validate the 'ClinicalNoteFinalized' SDK event Specific Setup: A client is enrolled in an existing episode (Client A). The 'Progress Notes (Group and Individual)' form is flagged in the 'Flag Assessment Forms' form. Steps Access the 'Clinical Notes Mapping' form. Select "Progress Note" in the 'Type of CCDA Document' field. Select "[Avatar CWS] Progress Notes (Group and Individual) (CWSPN22000)" in the 'Care Record Form to Map' field. Select "Activities" in the 'Note Type to Map' field. Validate the 'CCDA Document Title' field contains "Progress Note". Select "Social History" in the 'Standard Sections To Include To CCD' field. Select "Yes" in the 'Enabled' field. Click [New Row] in the 'Field Settings' grid. Select "History of Present Illness" in the 'CCDA Field Name' field. Select "[Avatar CWS] Health and Review of Systems (CWS42000)" in the 'Care Record Form/Assessment' field. Select "Past History" in the 'Care Record Field Name' field. Click [Submit] and close the form. Select "Client A" and access the 'Health and Review of Systems' form. Enter the current date in the 'Assessing Date' field. Select the desired value in the 'Type of Client' field. Enter the desired value in the 'Past History' field. Select the desired value in the 'Include In Syndromic Reporting' field. Populate any other desired fields. Select "Final" in the 'Draft/Final' field. Click [Submit] and close the form. Access the 'Progress Notes (Group and Individual)' form. Select "Client A" in the 'Select Client' field. Select the existing episode in the 'Select Episode' field. Select "New Service" in the 'Progress Note For' field. Select "Activities" in the 'Note Type' field. Enter the desired value in the 'Notes Field' field. Select the desired practitioner in the 'Practitioner' field. Enter the current date in the 'Date Of Service' field. Select the desired service code in the 'Service Charge Code' field. Validate the 'Are you releasing to myHealthPointe or External providers?' field is visible and required. Please note: this field will only become visible when a note type that is mapped in the 'Clinical Notes Mapping' form is selected for the progress note form being used. Select "External" in the 'Are you releasing to myHealthPointe or External providers?' field. Select "Final" in the 'Draft/Final' field. Click [File Note]. Validate a message is displayed stating: Note Filed. Click [OK] and close the form. Access the 'CareFabric Monitor' form. Enter the current date in the 'From Date' and 'Through Date' fields. Select "Client A" in the 'Client ID' field. Select "ClinicalNoteFinalized" in the 'Event/Action Search' field. Click [View Activity Log]. Validate a 'ClinicalNoteFinalized' record is displayed. Click [Click To View Record]. Validate the 'documentDescription' field contains "Progress Note". Validate the 'documentID' - 'id' field contains a unique identifier. Validate the 'documentTitle' field contains "Progress Note". Validate the 'historyOfPresentIllness' field contains the 'Past History' filed in the 'Health and Review of Systems' form. Validate the 'includedSectionCodes' - 'code' field contains "Social History". Validate the 'includedSectionCodes' - 'displayName' field contains "Social History". Validate the 'isReleaseExternal' field contains "true". Validate the 'isReleaseToPatient' field contains "false". Close the report and the form. Scenario 2: Clinical Notes Mapping - Progress Notes (Group and Individual) - Validate the 'ClinicalNoteFinalized' SDK event for an existing appointment Specific Setup: A client is enrolled in an existing episode and has an appointment scheduled (Client A). The 'Progress Notes (Group and Individual)' form is flagged in the 'Flag Assessment Forms' form. Document routing is enabled on the 'Progress Notes (Group and Individual)' form. Steps Access the 'Clinical Notes Mapping' form. Select "Progress Note" in the 'Type of CCDA Document' field. Select "[Avatar CWS] Progress Notes (Group and Individual) (CWSPN22000)" in the 'Care Record Form to Map' field. Select "Activities" in the 'Note Type to Map' field. Validate the 'CCDA Document Title' field contains "Progress Note". Select "Yes" in the 'Enabled' field. Click [New Row] in the 'Field Settings' grid. Select "ProgressNote" in the 'CCDA Field Name' field. Select "[Avatar CWS] Progress Notes (Group and Individual) (CWSPN22000)" in the 'Care Record Form/Assessment' field. Select "Notes Field" in the 'Care Record Field Name' field. Click [Submit] and close the form. Access the 'Progress Notes (Group and Individual)' form. Select "Client A" in the 'Select Client' field. Select the existing episode in the 'Select Episode' field. Select "Existing Appointment" in the 'Progress Note For' field. Select the existing appointment for "Client A" in the 'Note Addresses Which Existing Service/Appointment' field. Select "Activities" in the 'Note Type' field. Enter the desired value in the 'Notes Field' field. Validate the 'Are you releasing to myHealthPointe or External providers?' field is visible and required. Please note: this field will only become visible when a note type that is mapped in the 'Clinical Notes Mapping' form is selected for the progress note form being used. Select "External" in the 'Are you releasing to myHealthPointe or External providers?' field. Select "Final" in the 'Draft/Final' field. Click [File Note]. Validate the document routing image is displayed with all note details. Click [Accept]. Enter the password associated to the logged in user and click [OK]. Validate a message is displayed stating: Note Filed. Do you want to return to the Progress Notes form? Click [No]. Access the 'CareFabric Monitor' form. Enter the current date in the 'From Date' and 'Through Date' fields. Select "Client A" in the 'Client ID' field. Select "ClinicalNoteFinalized" in the 'Event/Action Search' field. Click [View Activity Log]. Validate a 'ClinicalNoteFinalized' record is displayed. Click [Click To View Record]. Validate the 'notes' field contains the value entered in the 'Notes Field' field in the previous steps. Validate the 'documentDescription' field contains "Progress Note". Validate the 'documentID' - 'id' field contains a unique identifier. Validate the 'documentTitle' field contains "Progress Note". Validate the 'isReleaseExternal' field contains "true". Validate the 'isReleaseToPatient' field contains "false". Validate the 'serviceEndDate' and 'serviceStartDate' fields contain the appointment start/end date & time. Close the report and the form. Avatar CareFabric - 'ListGroup' SDK action Scenario 1: Validate the 'ListGroup' SDK action Steps Internal testing only.	Topics • Progress Notes • CareFabric
Update 8 Summary \| Details 'ClientCreated' and 'ClientUpdated' SDK events Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following: CareFabric Monitor Update Client Data Scenario 1: Update Client Data - Validate the 'ClientUpdated' and 'ClientDemographicsCreated' events Specific Setup: A client must be enrolled in an existing episode (Client A). Steps Select "Client A" and access the 'Update Client Data' form. Select the desired value in the 'Sex' field. Enter the desired value in the 'Address - Street' field. Enter the desired value in the 'Apartment or Unit' field. Enter the desired value in the 'Zip Code' field. Enter the desired value in the 'City' field. Select the desired value in the 'State' field. Enter the desired date in the 'Address Start Date' field. Populate any other desired fields. Click [Submit]. Access the 'CareFabric Monitor' form. Enter the current date in the 'From Date' and 'Through Date' fields. Enter "Client A" in the 'Client ID' field. Click [View Activity Log]. Validate the 'CareFabric Monitor Report' contains a "ClientUpdated" record and select it. Click [Click To View Record]. Validate the 'addresses' - 'city' field contains the value entered in the previous steps. Validate the 'addresses' - 'fromDate' field contains the 'Address Start Date' entered in the previous steps. Validate the 'addresses' - 'stateCode' field contains the value entered in the previous steps. Validate the 'addresses' - 'street1' field contains the value entered in the previous steps. Validate the 'addresses' - 'street2' field contains the value entered in the previous steps. Validate the 'addresses' - 'zipCode' field contains the value entered in the previous steps. Validate the 'addresses' - 'typeCode' - 'code' field contains "H". Validate the 'addresses' - 'typeCode' - 'codeSystem' field contains "2.16.840.1.113883.4.642.3.67". Validate the 'addresses' - 'typeCode' - 'codeSystemName' field contains "Address". Validate the 'addresses' - 'typeCode' - 'displayName' field contains "Home". Validate the 'birthDetails' - 'birthSexCode' - 'code' field contains the code associated to the value selected in the 'Sex' field. Validate the 'birthDetails' - 'birthSexCode' - 'displayName' field contains the value selected in the 'Sex' field. Validate any other filed data is displayed. Navigate back to the 'CareFabric Monitor Report' and select the "ClientDemographicsCreated" record. Click [Click To View Record]. Validate the 'addresses' - 'city' field contains the value entered in the previous steps. Validate the 'addresses' - 'fromDate' field contains the 'Address Start Date' entered in the previous steps. Validate the 'addresses' - 'stateCode' field contains the value entered in the previous steps. Validate the 'addresses' - 'street1' field contains the value entered in the previous steps. Validate the 'addresses' - 'street2' field contains the value entered in the previous steps. Validate the 'addresses' - 'zipCode' field contains the value entered in the previous steps. Close the report and the form. Scenario 2: Admission - Validate the 'ClientCreated' SDK event Steps Access the 'Admission' form. Verify the 'Select Client' dialog is displayed. Enter any new value in the 'Last Name' field. Enter any new value in the 'First Name' field. Select any value in the 'Sex' field. Click [Search]. Validate a "Search Results" message is displayed stating: No matches found. Click [New Client]. Validate a "Client" message is displayed stating: Auto Assign Next ID Number? Click [Yes]. Enter any value in the 'Date of Birth' field. Enter the current date in the 'Preadmit/Admission Date' field. Enter the current time in the 'Preadmit/Admission Time' field. Select any outpatient program in the 'Program' field. Select any value in the 'Type Of Admission' field. Select the desired practitioner in the 'Admitting Practitioner' field. Populate any other required and desired fields. Click [Submit]. Access the 'CareFabric Monitor' form. Enter the current date in the 'From Date' field. Enter the current date in the 'Through Date' field. Enter the client admitted in the previous steps in the 'Client ID' field. Click [View Activity Log]. Select "ClientCreated" in the 'Activity Type' field. Click [Click to View Record] Validate the 'clientID' - 'id' field contains the ID for the newly admitted client. Validate the 'birthSexCode' - 'code' field contains the code associated to the value selected in the 'Sex' field. Validate the 'birthSexCode' - 'displayName' field contains the value selected in the 'Sex' field. Validate the 'genderCode' - 'code' field contains the code associated to the value selected in the 'Sex' field. Validate the 'genderCode' - 'displayName' field contains the value selected in the 'Sex' field. Validate the 'name' fields contain the name of the newly admitted client. Close the report and the form. Next Of Kin - 'ClientUpdated' SDK event Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following: CareFabric Monitor Update Client Data Next Of Kin Scenario 1: Next Of Kin - Validate the 'AssociatedPerson' SDK events Specific Setup: A client is enrolled in an existing episode (Client A). Steps Select "Client A" and access the 'Next of Kin' form. Click [Add] if the pre-display is displayed. Enter the desired value in the 'Next Of Kin Name' field. Select the desired value in the 'Next Of Kin Relationship' field. Select the desired value in the 'Next Of Kin Living With Client' field. Populate all other desired fields. Click [Submit]. Access the 'CareFabric Monitor' form. Enter the current date in the 'From Date' and 'Through Date' fields. Select "Client A" in the 'Client ID' field. Click [View Activity Log]. Validate the 'CareFabric Monitor' report is displayed and contains "ClientUpdated" and "AssociatedPersonCreated" records. Click [Click To View Record] for the "AssociatedPersonCreated" record. Validate the 'associatedPersonID' - 'id' field contains a unique ID for the record. Validate the 'associatedWithClientID' - 'id' field contains the PATID for "Client A". Validate next of kin information is displayed as expected. Close the report and the form. Select "Client A" and access the 'Next of Kin' form. Click [Edit]. Enter any new value in the 'Next Of Kin Name' field. Click [Submit]. Access the 'CareFabric Monitor' form. Enter the current date in the 'From Date' and 'Through Date' fields. Select "Client A" in the 'Client ID' field. Click [View Activity Log]. Validate the 'CareFabric Monitor' report is displayed and contains "ClientUpdated" and "AssociatedPersonUpdated" records. Click [Click To View Record] for the "AssociatedPersonUpdated" record. Validate the 'associatedPersonID' - 'id' field contains a unique ID for the record. Validate the 'associatedWithClientID' - 'id' field contains the PATID for "Client A". Validate the updated next of kin information is displayed as expected. Close the report and the form. Select "Client A" and access the 'Next of Kin' form. Click [Delete] and [Yes]. Access the 'CareFabric Monitor' form. Enter the current date in the 'From Date' and 'Through Date' fields. Select "Client A" in the 'Client ID' field. Click [View Activity Log]. Validate the 'CareFabric Monitor' report is displayed and contains "ClientUpdated" and "AssociatedPersonDeleted" records. Click [Click To View Record] for the "AssociatedPersonDeleted" record. Validate the 'associatedPersonID' - 'id' field contains a unique ID for the deleted record. Close the report and the form. Scenario 2: Next Of Kin - Validate the 'ClientUpdated' SDK event Specific Setup: A client is enrolled in an existing episode (Client A). Steps Select "Client A" and access the 'Next of Kin' form. Click [Add] if the pre-display is displayed. Enter the desired value in the 'Next Of Kin Name' field. Select the desired value in the 'Next Of Kin Relationship' field. Select the desired value in the 'Next Of Kin Living With Client' field. Populate all other desired fields. Click [Submit]. Access the 'CareFabric Monitor' form. Enter the current date in the 'From Date' and 'Through Date' fields. Select "Client A" in the 'Client ID' field. Click [View Activity Log]. Validate the 'CareFabric Monitor' report is displayed and contains "ClientUpdated" and "AssociatedPersonCreated" records. Click [Click To View Record] for the "ClientUpdated" record. Validate the 'clientID' - 'id' field contains the PATID for "Client A". Validate the 'name' - 'first' field contains the first name for "Client A". Validate the 'name' - 'last' field contains the last name for "Client A". Close the report and the form. Avatar CareFabric - HL-7 Integrations Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following: CareFabric Monitor Update Client Data System Task Scheduler Discharge Scenario 1: System Task Scheduler - Avatar CareFabric - Send Facility Bed Information (HL-7) Specific Setup: Please note: this is for Avatar PM systems only. One or more units defined in the '(202) Unit' dictionary must have the following configured in 'Dictionary Update': A value entered for the '(22055) Facility Abbreviation' extended dictionary data element. A value selected for the '(22056) Level of Care' extended dictionary data element. Clients must be admitted into Inpatient episodes using the units configured above. Steps Access the 'System Task Scheduler' form. Select "Avatar CareFabric - Send Facility Bed Information (HL-7) Recurrence Pattern : Hourly -Inactive" in the 'Schedule(s)' field. Validate "Hourly" is selected in the 'Recurrence Pattern' field. Validate the 'Start Time' field contains "12:00 AM". Validate the 'End Time' field contains "11:59 PM". Validate "Yes" is selected in the 'Inactive Task' field. Enter the current date in the 'Start By' field. Select "No" in the 'Inactive Task' field. Click [Schedule Task] and close the form. Wait for the task to run. Access the 'CareFabric Monitor' form. Enter the current date in the 'From Date' and 'Through Date' fields. Select "ClientUpdated" in the 'Event/Action Search' field. Click [View Activity Log]. Validate the 'CareFabric Monitor Report' is displayed with a "ClientUpdated" record for each unit configured in the pre-conditions. Click [Click To View Record] for the first record. Validate the 'assignedFacilityInformation' - 'facilityMneumonic' field contains the value defined in the "(22055) Facility Abbreviation" extended dictionary element for the unit. Validate the 'assignedFacilityInformation' - 'levelOfCareCode' - 'code' field contains the code associated to the value selected in the "(22056) Level of Care" extended dictionary element for the unit. Validate the 'assignedFacilityInformation' - 'levelOfCareCode' - 'displayName' field contains the value selected in the "(22056) Level of Care" extended dictionary element for the unit. Validate the 'assignedFacilityInformation' - 'totalNumberOfBeds' field contains the total number of beds in the unit. Validate the 'assignedFacilityInformation' - 'totalNumberOfBedsOccupied' field contains the total number of occupied beds in the unit. Validate the 'clientID' - 'id' field contains "NO_ID". Validate the 'name' - 'first' field contains "NO_NAME". Validate the 'name' - 'last' field contains "NO_LASTNAME". Navigate back to the 'CareFabric Monitor Report' and repeat steps 3e-3m as needed for the additional units that are configured. Close the report and the form. Scenario 2: Inpatient Admission - Validate the 'ClientCreated' and 'ClientUpdated' SDK events Specific Setup: A unit must be defined with available rooms and beds (Unit A). Steps Access the 'Dictionary Update' PM form. Select "Client" in the 'File' field. Select "Data Element Number" in the 'Data Element' field. Select "(202) Unit" in the 'Data Element' field. Enter the code associated to "Unit A" in the 'Dictionary Code' field. Validate "Unit A" is displayed in the 'Dictionary Value' field. Select "(22055) Facility Abbreviation" in the 'Extended Dictionary Data Element' field. Validate the 'Extended Dictionary Value (Free Text)' field is now enabled. Enter the desired value. Select "(22056) Level of Care" in the 'Extended Dictionary Data Element' field. Validate the 'Extended Dictionary Value (Single Dictionary)' field is now enabled and contains the following values: Inpatient Observation Outpatient Select the desired value in the 'Extended Dictionary Value (Single Dictionary)' field. Click [Apply Changes]. Validate a message is displayed stating: Filed! Click [OK] and close the form. Access the 'Admission' form Verify the 'Select Client' dialog is displayed. Enter any new value in the 'Last Name' field. Enter any new value in the 'First Name' field. Select any value in the 'Sex' field. Click [Search]. Validate a "Search Results" message is displayed stating: No matches found. Click [New Client]. Validate a "Client" message is displayed stating: Auto Assign Next ID Number? Click [Yes]. Enter any value in the 'Date of Birth' field. Enter the current date in the 'Preadmit/Admission Date' field. Enter the current time in the 'Preadmit/Admission Time' field. Select any inpatient program in the 'Program' field. Select any value in the 'Type Of Admission' field. Select any value in the 'Source Of Admission' field. Enter the desired practitioner in the 'Admitting Practitioner' field. Enter the desired practitioner in the 'Attending Practitioner' field. Select the "Inpatient/Partial/Day Treatment" section. Select "Unit A" in the 'Unit' field. Select the desired room in the 'Room' field. Select the desired bed in the 'Bed' field. Select the desired value in the 'Room And Board Billing Code' field. Submit the form. Note: this will now be referred to as "Client A". Access the 'CareFabric Monitor' form. Enter the current date in the 'From Date' and 'Through Date' fields. Select "Client A" in the 'Client ID' field. Click [View Activity Log]. Validate the 'CareFabric Monitor' report is displayed and contains "ClientCreated" record. Click [Click To View Record] for the "ClientCreated" record. Validate the 'assignedFacilityInformation' - 'facilityMneumonic' field contains the value defined in the "(22055) Facility Abbreviation" extended dictionary element for "Unit A". Validate the 'assignedFacilityInformation' - 'levelOfCareCode' - 'code' field contains the code associated to the value selected in the "(22056) Level of Care" extended dictionary element for "Unit A". Validate the 'assignedFacilityInformation' - 'levelOfCareCode' - 'displayName' field contains the value selected in the "(22056) Level of Care" extended dictionary element for "Unit A". Validate the 'assignedFacilityInformation' - 'totalNumberOfBeds' field contains the total number of beds in "Unit A". Validate the 'assignedFacilityInformation' - 'totalNumberOfBedsOccupied' field contains the total number of occupied beds in "Unit A". Close the report and the form. Select "Client A" and access the 'Update Client Data' form. Enter the desired value in the 'Date Of Birth' field. Click [Submit]. Access the 'CareFabric Monitor' form. Enter the current date in the 'From Date' and 'Through Date' fields. Select "Client A" in the 'Client ID' field. Click [View Activity Log]. Validate the 'CareFabric Monitor' report is displayed and contains "ClientUpdated" record. Click [Click To View Record] for the "ClientUpdated" record. Validate the 'assignedFacilityInformation' - 'facilityMneumonic' field contains the value defined in the "(22055) Facility Abbreviation" extended dictionary element for "Unit A". Validate the 'assignedFacilityInformation' - 'levelOfCareCode' - 'code' field contains the code associated to the value selected in the "(22056) Level of Care" extended dictionary element for "Unit A". Validate the 'assignedFacilityInformation' - 'levelOfCareCode' - 'displayName' field contains the value selected in the "(22056) Level of Care" extended dictionary element for "Unit A". Validate the 'assignedFacilityInformation' - 'totalNumberOfBeds' field contains the total number of beds in "Unit A". Validate the 'assignedFacilityInformation' - 'totalNumberOfBedsOccupied' field contains the total number of occupied beds in "Unit A". Validate the 'birthDate' field contains the 'Date Of Birth' filed in the previous steps. Close the report and the form. Select "Client A" and access the 'Discharge' form. Enter the desired date in the 'Date Of Discharge' field. Enter the desired time in the 'Time Of Discharge' field. Select the desired value in the 'Type Of Discharge' field. Select the desired value in the 'Discharge Practitioner' field. Click [Submit]. Access the 'CareFabric Monitor' form. Enter the current date in the 'From Date' and 'Through Date' fields. Select "Client A" in the 'Client ID' field. Click [View Activity Log]. Validate the 'CareFabric Monitor' report is displayed and contains "ClientUpdated" record. Click [Click To View Record] for the "ClientUpdated" record. Validate the 'assignedFacilityInformation' field contains "null". Validate the 'birthDate' field contains the 'Date Of Birth' filed in the previous steps. Close the report and the form.	Topics • Update Client Data • CareFabric • Admission • Next Of Kin • Associated Person • System Task Scheduler • Discharge • CareFabric Monitor
Update 9 Summary \| Details CarePOV Management - Form Sections Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following: CarePOV Management Scenario 1: CarePOV Management - Section Validations Steps Access the 'CarePOV Management' form. Validate the 'Submit' button is disabled. Validate a [Submit 'CarePOV Management'] button is displayed. Select any desired values and click [Submit 'CarePOV Management']. Validate a message is displayed stating: Saved. Click [OK]. Validate successful form submission. Access the 'CarePOV Management' form. Validate previously saved values are displayed. Select the "Bed Board - POV" section. Validate the 'Submit' button is disabled. Validate a [Submit 'Bed Board - POV'] button is displayed. Select any desired values and click [Submit 'Bed Board - POV']. Validate a message is displayed stating: Saved. Click [OK]. Validate successful form submission. Access the 'CarePOV Management' form. Select the "Bed Board - POV" section. Validate previously saved values are displayed. Select the "Electronic Visit Verification" section. Validate the 'Submit' button is disabled. Validate a [Submit 'Electronic Visit Verification'] button is displayed. Select any desired values and click [Submit 'Electronic Visit Verification']. Validate a message is displayed stating: Saved. Click [OK]. Validate successful form submission. Access the 'CarePOV Management' form. Select the "Electronic Visit Verification" section. Validate previously saved values are displayed. Select the "Client Alerts" section. Validate the 'Submit' button is disabled. Validate the [Save] button is displayed. Note: this button is existing functionality and remains unchanged. Select the "Lab Results Flowsheet Mapping" section. Validate the 'Submit' button is disabled. Validate the [Save] button is displayed. Note: this button is existing functionality and remains unchanged. Select the "Group Check In" section. Validate the 'Submit' button is disabled. Validate the [Submit 'Group Check In'] button is displayed. Enter any desired values and click [Submit 'Group Check In']. Validate a message is displayed stating: Saved. Click [OK]. Validate successful form submission. Access the 'CarePOV Management' form. Select the "Group Check In" section. Validate previously saved values are displayed. Select the "Bells Notes" section. Validate the 'Submit' button is disabled. Validate a message is displayed stating: Contact your Netsmart Representative to set up the Progress Note that will be used for Bells Notes integration. Note: this is an existing message and remains unchanged. Select the "Telehealth" section. Validate the 'Submit' button is disabled. Validate the [Submit 'Telehealth'] button is displayed. Enter the desired value and click [Submit 'Telehealth']. Validate a message is displayed stating: Saved. Click [OK]. Validate successful form submission. Access the 'CarePOV Management' form. Select the "Telehealth" section. Validate previously saved values are displayed. Close the form. CarePOV Management - 'Electronic Visit Verification' section Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following: CarePOV Management Client Alternate Addresses Registry Settings (PM) Scenario 1: Client Alternate Addresses - Form Validations Specific Setup: The 'Enable Client Alternate Addresses' registry setting must be set to "Y". A client is admitted in an existing episode (Client A). Steps Access the 'Client Alternate Addresses' form. Select "Client A" in the 'Client' field. Select "Add" in the 'Add/Edit' field. Enter the desired value in the 'Description' field. Enter the desired date in the 'Address Start Date' field. Enter the desired date in the 'Address End Date' field. Enter the desired value in the 'Address Line 1' field. Enter the desired value in the 'Address Line 2' field. Enter the desired value in the 'Zip' field. Enter the desired value in the 'City' field. Select the desired value in the 'State' field. Enter the desired value in the 'Contact Name field. Enter the desired value in the 'Contact Phone' field. Enter the desired value in the 'Address Notes' field. Select the desired value in the 'Address Type' field. Please note: this will display values defined in the '(10006) Location' dictionary. Select "Yes" in the 'Enabled' field. Click [File]. Validate a message is displayed stating: Saved. Click [OK]. Validate the 'Client' field contains "Client A". Select "Edit" in the 'Add/Edit' field. Validate the 'Select Existing Address' field contains the alternate address filed in the previous steps with the 'Address Start Date', 'Address End Date', and 'Description'. Select the address filed in the previous steps in the 'Select Existing Address' field. Validate all previously filed data is displayed. Close the form. Access Crystal Reports or other SQL Reporting Tool. Select the PM namespace. Create a report using the 'SYSTEM.client_alternate_address' SQL table. Validate there is a row for "Client A" will all previously filed data. Validate the 'addr_type_code' and 'addr_type_value' fields contain the code/value filed in the previous steps. Close the report. Scenario 2: CarePOV Management - 'Electronic Visit Verification' section - Validate the 'Require Address Type' and 'Default Address Type for Client Demographics' fields Specific Setup: Avatar is configured to integrate with Mobile CareGiver+. This must be done by a Netsmart Representative. "Yes" must be selected for 'Enable Mobile CareGiver+' in the 'Electronic Visit Verification' section of the 'CarePOV Management' form. The 'Enable Client Alternate Addresses' registry setting must be set to "Y". A client is admitted in an existing episode (Client A). Steps Access the 'CarePOV Management' form. Select the "Electronic Visit Verification" section. Validate the 'Require Address Type' field is displayed with "Yes" and "No" values. The default value will be "No". Validate the 'Default Address Type for Client Demographics' field is displayed with values from the '(10006) Location' dictionary. Select "Yes" in the 'Require Address Type' field. Validate the 'Default Address Type for Client Demographics' field becomes required. Select the desired value in the 'Default Address Type for Client Demographics' field. Click [Submit 'Electronic Visit Verification']. Validate a message is displayed stating: Saved. Click [OK]. Validate successful submission. Access the 'Client Alternate Addresses' form. Select "Add" in the 'Add/Edit' field. Enter the desired value in the 'Description' field. Enter the desired date in the 'Address Start Date' field. Enter the desired date in the 'Address End Date' field. Enter the desired value in the 'Address Line 1' field. Enter the desired value in the 'Address Line 2' field. Enter the desired value in the 'Zip' field. Enter the desired value in the 'City' field. Select the desired value in the 'State' field. Enter the desired value in the 'Contact Name field. Enter the desired value in the 'Contact Phone' field. Enter the desired value in the 'Address Notes' field. Validate the 'Address Type' field is required. Select the desired value in the 'Address Type' field. Please note: this will display values defined in the '(10006) Location' dictionary. Select "Yes" in the 'Enabled' field. Click [File]. Validate a message is displayed stating: Saved. Click [OK] and close the form. Access the 'CarePOV Management' form. Select the "Electronic Visit Verification" section. Validate the previously selected values are displayed. Select "No" in the 'Require Address Type' field. Validate the 'Default Address Type for Client Demographics' field is no longer required. Remove the value from the 'Default Address Type for Client Demographics' field. Click [Submit 'Electronic Visit Verification']. Validate a message is displayed stating: Saved. Click [OK]. Validate successful submission. Access the 'Client Alternate Addresses' form. Select "Edit" in the 'Add/Edit' field. Validate the 'Select Existing Address' field contains the alternate address filed in the previous steps with the 'Address Start Date', 'Address End Date', and 'Description'. Select the address filed in the previous steps in the 'Select Existing Address' field. Validate all previously filed data is displayed. Validate the 'Address Type' field is no longer required. Remove the value from the 'Address Type' field. Click [File]. Validate a message is displayed stating: Saved. Click [OK] and close the form. Mobile CareGiver+ - 'EvvClientUpdated' SDK event Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following: CareFabric Monitor CarePOV Management Client Alternate Addresses Registry Settings (PM) Scenario 1: Mobile Caregiver+ - Validate the 'McgEvvAppointmentUpdated' incoming event when the 'Site' field is populated in the 'CarePOV Management' form Specific Setup: Avatar is configured to integrate with Mobile CareGiver+. Please note: This must be done by a Netsmart Representative. A product is defined in the 'CareFabric Integration Management' form for the "MobileCareGiver+" product and "McgEvvAppointmentUpdated" must be selected in the 'Event Types' field. A program is defined with a value populated in the 'EVV Provider Organization ID' field in the 'Program Maintenance' form (Program A). "Program A" has an associated location (Location A) with the following defined in 'Dictionary Update' for the "Client" file, "(10006 Location)" data element: Extended dictionary data element "(587) Place Of Service (Mobile CareGiver+)" must be set to "Home" (unless an alternate address is being used). If the above dictionary data element is not defined, then the extended dictionary data element "(579) Place Of Service (837 Electronic Billing)" will be used and must be set to "Home". If this dictionary data element is not defined, then "(578) Place Of Service (HCFA 24-B)" will be used and must be set to "Home". A service code must be defined that has "Yes" selected in the 'Does This Service Require Electronic Visit Verification' field in the 'Service Codes' form and must be assigned to "Program A" (Service Code A). This service code must also have a CPT-4/HCPCS code associated to it in the 'Service Fee/Cross Reference Maintenance' form (Procedure Code A). Must have a guarantor defined in the 'Guarantors/Payors' form (Guarantor A). The following must be set in the "Electronic Visit Verification" section of the 'CarePOV Management' form: "Yes" is selected in the 'Enable Mobile CareGiver+' field. "Yes" is selected in the 'Send Non EVV Payers' field. "No" is selected in the 'Require Authorization' field. "Guarantor A" has a row with all fields populated in the 'Payor Program ID' grid. "Yes" is selected in the following fields for the 'McgEvvAppointmentUpdated' event: 'Keep Incoming Payload in the Log', 'Keep Outgoing Payload in the Log' and 'Show in the CareFabric Monitor Report' in the 'CareFabric Management' form. This must be done by a Netsmart Representative. A site is defined with hours for scheduling (Site A). A practitioner must be defined as an EVV resource with hours for scheduling at "Site A" and has the following on file: 'Name', 'Date Of Birth', 'Cellular Telephone', 'Staff EVV ID', 'Email Address', and 'Staff EVV Type' (Practitioner A). A client is enrolled in "Program A" and has the following on file: 'Client Name', 'Address - Street', 'Zipcode', 'Cell Phone', 'Diagnosis', "Guarantor A" selected in 'Financial Eligibility' (Client A). Steps Access the 'CarePOV Management' form. Select the "Electronic Visit Verification" section. Select "Site A" in the 'Site' field. Click [Submit]. Add an unscheduled visit in the Mobile CareGiver+ application with associated tasks for "Client A" with "Practitioner A". Please note: if any of the appointment information sent from Mobile CareGiver+ can't be determined, the appointment will be available for reconciliation in the 'CareFabric Integration Reconciliation' form. Access the 'CareFabric Monitor' form. Enter the current date in the 'From Date' and 'Through Date' fields. Select "Client A" in the 'Client ID' field. Select "McgEvvAppointmentUpdated' in the 'Event/Action Search' field. Click [View Activity Log]. Validate the 'CareFabric Monitor Report' contains an "McgEvvAppointmentUpdated" record. Click [Click To View Record]. Validate the 'clientID- 'id' field contains "Client A". Validate the 'endDate' field contains the appointment end date/time. Validate the 'mcgAppointmentID' - 'id' field contains the MCG+ unique identifier for the appointment. Validate the 'resource' - 'resourceID' field contains "Practitioner A". Validate the 'services' - 'procedureCode' - 'code' field contains "Procedure Code A". Validate the 'startDate' field contains the appointment start date/time. Validate all other appointment data is displayed. Close the report and the form. Access the 'Scheduling Calendar' form. Validate the appointment for "Client A" with "Practitioner A" that was sent from Mobile CareGiver+ is displayed at "Site A". Right click on the appointment and click [Details/Edit]. Validate the appointment details are displayed as expected. Validate the 'Available Tasks' field contains the tasks sent from Mobile CareGiver+. Close the form and click [Dismiss]. Scenario 2: Mobile CareGiver+ - Client Alternate Addresses - Validate the 'EvvClientUpdated' event Specific Setup: Avatar is configured to integrate with Mobile CareGiver+. Please note: This must be done by a Netsmart Representative. A program is defined with a value populated in the 'EVV Provider Organization ID' field in the 'Program Maintenance' form (Program A). "Program A" has an associated location (Location A) with the following defined in 'Dictionary Update' for the "Client" file, "(10006 Location)" data element: Extended dictionary data element "(587) Place Of Service (Mobile CareGiver+)" If the above dictionary data element is not defined, then the extended dictionary data element "(579) Place Of Service (837 Electronic Billing)" will be used and must be set to "Home". If this dictionary data element is not defined, then "(578) Place Of Service (HCFA 24-B)" will be used and must be set to "Home". A service code must be defined that has "Yes" selected in the 'Does This Service Require Electronic Visit Verification' field in the 'Service Codes' form and must be assigned to "Program A" (Service Code A). This service code must also have a CPT-4/HCPCS code associated to it in the 'Service Fee/Cross Reference Maintenance' form (Procedure Code A). Dictionary values must be defined for the 'Other Tabled Files' - '(424) Available Electronic Visit Verification Tasks' Data Element in 'Dictionary Update (PM)'. Must have a guarantor defined in the 'Guarantors/Payors' form (Guarantor A). The following must be set in the "Electronic Visit Verification" section of the 'CarePOV Management' form: "Yes" is selected in the 'Enable Mobile CareGiver+' field. "Yes" is selected in the 'Send Non EVV Payers' field. "No" is selected in the 'Require Authorization' field. "Guarantor A" has a row with all fields populated in the 'Payor Program ID' grid. A client is enrolled in "Program A" and has the following on file: 'Client Name', 'Address - Street', 'Zipcode', 'Cell Phone', 'Diagnosis', "Guarantor A" selected in 'Financial Eligibility' (Client A). A practitioner must be defined as an EVV resource with hours for scheduling and has the following on file: 'Name', 'Date Of Birth', 'Cellular Telephone', 'Staff EVV ID', 'Email Address', and 'Staff EVV Type' (Practitioner A). The 'Enable Client Alternate Addresses' registry setting must be set to "Y". Steps Access the 'Dictionary Update' PM form. Select "Client" in the 'File' field. Select "(10006) Location" in the 'Data Element' field. Enter the desired value in the 'Dictionary Code' field. Enter "MCG+ Alternate Location" in the 'Dictionary Value' field. Select "(587) Place Of Service (Mobile CareGiver+)" in the 'Extended Dictionary Data Element' field. Select "(53) Community Mental Health Center" (or any other non "Home" value) in the 'Extended Dictionary Value (Single Dictionary)' field. Select "(579) Place Of Service (837 Electronic Billing)" in the 'Extended Dictionary Data Element' field. Select "Other Unlisted Facility" (or any other non "Home" value) in the 'Extended Dictionary Value (Single Dictionary)' field. Select "(578) Place Of Service (HCFA 24-B)" in the 'Extended Dictionary Data Element' field. Select "Other Unlisted Facility" (or any other non "Home" value) in the 'Extended Dictionary Value (Single Dictionary)' field. Click [Apply Changes]. Validate a message is displayed stating: Filed! Click [OK] and close the form. Access the 'Client Alternate Addresses' form. Select "Client A" in the 'Client' field. Select "Add" in the 'Add/Edit' field. Enter "Inactive Alternate Address" in the 'Description' field. Enter the desired date in the 'Address Start Date' field. Enter the desired date in the 'Address Line 1' field. Enter the desired value in the 'Zip' field. Enter the desired value in the 'City' field. Select the desired value in the 'State' field. Select "MCG+ Alternate Location" in the 'Address Type' field. Select "No" in the 'Enabled' field. Click [File]. Validate a message is displayed stating: Saved. Click [OK]. Select "Add" in the 'Add/Edit' field. Enter "Active Alternate Address" in the 'Description' field. Enter the desired date in the 'Address Start Date' field. Enter the desired date in the 'Address Line 1' field. Enter the desired value in the 'Zip' field. Enter the desired value in the 'City' field. Select the desired value in the 'State' field. Select "MCG+ Alternate Location" in the 'Address Type' field. Select "Yes" in the 'Enabled' field. Click [File]. Validate a message is displayed stating: Saved. Click [OK] and close the form. Access the 'CareFabric Monitor' form. Enter the current date in the 'From Date' and 'Through Date' fields. Select "Client A" in the 'Client ID' field. Select "EvvClientUpdated" in the 'Event/Action Search' field. Click [View Activity Log]. Validate the 'CareFabric Monitor Report' contains an "EvvClientUpdated" record for "Client A". Click [Click to View Record]. Validate the 'addresses' section contains only the "Active Alternate Address" and the client's home address defined in demographics. Close the report and the form. Mobile CareGiver+ - Appointment Scheduling Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following: CarePOV Management CareFabric Monitor Scheduling Calendar - Status Update Client Alternate Addresses Update Client Data Scenario 1: Mobile Caregiver+ - Validate the 'EvvAppointmentUpdated' outgoing event for a scheduled appointment Specific Setup: Avatar is configured to integrate with Mobile CareGiver+. Please note: This must be done by a Netsmart Representative. A program is defined with a value populated in the 'EVV Provider Organization ID' field in the 'Program Maintenance' form (Program A). "Program A" has an associated location (Location A) with the following defined in 'Dictionary Update' for the "Client" file, "(10006 Location)" data element: Extended dictionary data element "(587) Place Of Service (Mobile CareGiver+)" must be set to "Home" (unless an alternate address is being used). If the above dictionary data element is not defined, then the extended dictionary data element "(579) Place Of Service (837 Electronic Billing)" will be used and must be set to "Home". If this dictionary data element is not defined, then "(578) Place Of Service (HCFA 24-B)" will be used and must be set to "Home". A service code must be defined that has "Yes" selected in the 'Does This Service Require Electronic Visit Verification' field in the 'Service Codes' form and must be assigned to "Program A" (Service Code A). This service code must also have a CPT-4/HCPCS code associated to it in the 'Service Fee/Cross Reference Maintenance' form (Procedure Code A). Dictionary values must be defined for the 'Other Tabled Files' - '(424) Available Electronic Visit Verification Tasks' Data Element in 'Dictionary Update (PM)'. Must have a guarantor defined in the 'Guarantors/Payors' form (Guarantor A). The following must be set in the "Electronic Visit Verification" section of the 'CarePOV Management' form: "Yes" is selected in the 'Enable Mobile CareGiver+' field. "Yes" is selected in the 'Send Non EVV Payers' field. "No" is selected in the 'Require Authorization' field. "Guarantor A" has a row with all fields populated in the 'Payor Program ID' grid. A client is enrolled in "Program A" and has the following on file: 'Client Name', 'Address - Street', 'Zipcode', 'Cell Phone', 'Diagnosis', "Guarantor A" selected in 'Financial Eligibility' (Client A). A practitioner must be defined as an EVV resource with hours for scheduling and has the following on file: 'Name', 'Date Of Birth', 'Cellular Telephone', 'Staff EVV ID', 'Email Address', and 'Staff EVV Type' (Practitioner A). Steps Access the 'Scheduling Calendar' form. Right click in any available time slot for "Practitioner A" and click [Add Appointment]. Select "Service Code A" in the 'Service Code' field. Select "Client A" in the 'Client' field. Validate the 'Program' field contains "Program A". Validate the 'Location' field contains "Location A". Select the desired value(s) in the 'Available Tasks' field. Populate all other required and desired fields. Click [Submit]. Validate the new appointment is displayed. Click [Dismiss]. Access the 'CareFabric Monitor' form. Enter the current date in the 'From Date' and 'Through Date' fields. Select "Client A" in the 'Client ID' field. Select "EvvAppointmentUpdated" in the 'Event/Action Search' field. Click [View Activity Log]. Validate the 'CareFabric Monitor Report' contains an "EvvAppointmentUpdated" record. Click [Click To View Record]. Validate the 'appointmentAuthorization' field contains "null". Validate the 'auditInformation' - 'lastUpdatedByStaffMemberID' - 'id' field contains the logged in user ID. Validate the 'auditInformation' - 'lastUpdatedDate' field contains the date/time the appointment was scheduled. Validate the 'appointmentID' - 'id' field contains the appointment ID. Validate the 'canceledDate' field contains "null". Validate the 'canceledReasonCode' field contains "null". Validate the 'providerOrganizationID' - 'id' field contains the 'Provider Organization ID' assigned to "Program A". Validate the 'clientID' - 'id' field contains the ID for "Client A". Validate the 'diagnosisCodes' - 'code' field contains the diagnosis code on file for "Client A". Validate the 'diagnosisCodes' - 'displayName' field contains the diagnosis value on file for "Client A". Validate the 'endDate' field contains the appointment end date/time. Validate the 'insPayerID' - 'id' field contains the 'MCG+ Payer ID' on file in the 'CarePOV Management' form for "Guarantor A". Validate the 'insPlanID' - 'id' field contains the 'MCG+ Insurance Plan ID' on file in the 'CarePOV Management' form for "Guarantor A". Validate the 'isEVV' field contains "true". Validate the 'locationOfService' fields contain "Client A's" home address. Validate the 'mcgInsPayerID' - 'id' field contains the 'MCG+ Payer ID' on file in the 'CarePOV Management' form for "Guarantor A". Validate the 'mcgInsPlanID' - 'id' field contains the 'MCG+ Insurance Plan ID' on file in the 'CarePOV Management' form for "Guarantor A". Validate the 'services' - 'description' field contains the description for "Service Code A". Validate the 'services' - 'name' field contains the code for "Service Code A". Validate the 'services' - 'procedureCode' - 'code' field contains the code for "Procedure A". Validate the 'services' - 'procedureCode' - 'displayName' field contains the name for "Procedure A". Validate the 'serviceID' - 'id' field contains the code for "Service Code A". Validate the 'tasks' - 'taskCode' fields contain the value(s) selected in the 'Available Tasks' field when scheduling the appointment. Validate the 'startDate' field contains the appointment start date/time. Validate all other relevant information is displayed for "Client A" and "Practitioner A". Close the report and the form. Scenario 2: Mobile Caregiver+ - Validate the 'McgEvvAppointmentUpdated' incoming event when the 'Site' field is populated in the 'CarePOV Management' form Specific Setup: Avatar is configured to integrate with Mobile CareGiver+. Please note: This must be done by a Netsmart Representative. A product is defined in the 'CareFabric Integration Management' form for the "MobileCareGiver+" product and "McgEvvAppointmentUpdated" must be selected in the 'Event Types' field. A program is defined with a value populated in the 'EVV Provider Organization ID' field in the 'Program Maintenance' form (Program A). "Program A" has an associated location (Location A) with the following defined in 'Dictionary Update' for the "Client" file, "(10006 Location)" data element: Extended dictionary data element "(587) Place Of Service (Mobile CareGiver+)" must be set to "Home" (unless an alternate address is being used). If the above dictionary data element is not defined, then the extended dictionary data element "(579) Place Of Service (837 Electronic Billing)" will be used and must be set to "Home". If this dictionary data element is not defined, then "(578) Place Of Service (HCFA 24-B)" will be used and must be set to "Home". A service code must be defined that has "Yes" selected in the 'Does This Service Require Electronic Visit Verification' field in the 'Service Codes' form and must be assigned to "Program A" (Service Code A). This service code must also have a CPT-4/HCPCS code associated to it in the 'Service Fee/Cross Reference Maintenance' form (Procedure Code A). Must have a guarantor defined in the 'Guarantors/Payors' form (Guarantor A). The following must be set in the "Electronic Visit Verification" section of the 'CarePOV Management' form: "Yes" is selected in the 'Enable Mobile CareGiver+' field. "Yes" is selected in the 'Send Non EVV Payers' field. "No" is selected in the 'Require Authorization' field. "Guarantor A" has a row with all fields populated in the 'Payor Program ID' grid. "Yes" is selected in the following fields for the 'McgEvvAppointmentUpdated' event: 'Keep Incoming Payload in the Log', 'Keep Outgoing Payload in the Log' and 'Show in the CareFabric Monitor Report' in the 'CareFabric Management' form. This must be done by a Netsmart Representative. A site is defined with hours for scheduling (Site A). A practitioner must be defined as an EVV resource with hours for scheduling at "Site A" and has the following on file: 'Name', 'Date Of Birth', 'Cellular Telephone', 'Staff EVV ID', 'Email Address', and 'Staff EVV Type' (Practitioner A). A client is enrolled in "Program A" and has the following on file: 'Client Name', 'Address - Street', 'Zipcode', 'Cell Phone', 'Diagnosis', "Guarantor A" selected in 'Financial Eligibility' (Client A). Steps Access the 'CarePOV Management' form. Select the "Electronic Visit Verification" section. Select "Site A" in the 'Site' field. Click [Submit]. Add an unscheduled visit in the Mobile CareGiver+ application with associated tasks for "Client A" with "Practitioner A". Please note: if any of the appointment information sent from Mobile CareGiver+ can't be determined, the appointment will be available for reconciliation in the 'CareFabric Integration Reconciliation' form. Access the 'CareFabric Monitor' form. Enter the current date in the 'From Date' and 'Through Date' fields. Select "Client A" in the 'Client ID' field. Select "McgEvvAppointmentUpdated' in the 'Event/Action Search' field. Click [View Activity Log]. Validate the 'CareFabric Monitor Report' contains an "McgEvvAppointmentUpdated" record. Click [Click To View Record]. Validate the 'clientID- 'id' field contains "Client A". Validate the 'endDate' field contains the appointment end date/time. Validate the 'mcgAppointmentID' - 'id' field contains the MCG+ unique identifier for the appointment. Validate the 'resource' - 'resourceID' field contains "Practitioner A". Validate the 'services' - 'procedureCode' - 'code' field contains "Procedure Code A". Validate the 'startDate' field contains the appointment start date/time. Validate all other appointment data is displayed. Close the report and the form. Access the 'Scheduling Calendar' form. Validate the appointment for "Client A" with "Practitioner A" that was sent from Mobile CareGiver+ is displayed at "Site A". Right click on the appointment and click [Details/Edit]. Validate the appointment details are displayed as expected. Validate the 'Available Tasks' field contains the tasks sent from Mobile CareGiver+. Close the form and click [Dismiss]. Scenario 3: Mobile Caregiver+ - Cancel an EVV appointment and validate the 'EvvAppointmentUpdated' outgoing event Specific Setup: Avatar is configured to integrate with Mobile CareGiver+. Please note: This must be done by a Netsmart Representative. A program is defined with a value populated in the 'EVV Provider Organization ID' field in the 'Program Maintenance' form (Program A). "Program A" has an associated location (Location A) with the following defined in 'Dictionary Update' for the "Client" file, "(10006 Location)" data element: Extended dictionary data element "(587) Place Of Service (Mobile CareGiver+)" must be set to "Home" (unless an alternate address is being used). If the above dictionary data element is not defined, then the extended dictionary data element "(579) Place Of Service (837 Electronic Billing)" will be used and must be set to "Home". If this dictionary data element is not defined, then "(578) Place Of Service (HCFA 24-B)" will be used and must be set to "Home". A service code must be defined that has "Yes" selected in the 'Does This Service Require Electronic Visit Verification' field in the 'Service Codes' form and must be assigned to "Program A" (Service Code A). This service code must also have a CPT-4/HCPCS code associated to it in the 'Service Fee/Cross Reference Maintenance' form (Procedure Code A). Must have a guarantor defined in the 'Guarantors/Payors' form (Guarantor A). The following must be set in the "Electronic Visit Verification" section of the 'CarePOV Management' form: "Yes" is selected in the 'Enable Mobile CareGiver+' field. "Yes" is selected in the 'Send Non EVV Payers' field. "No" is selected in the 'Require Authorization' field. "No" is selected in the 'Require Cancellation Reason' field. "Guarantor A" has a row with all fields populated in the 'Payor Program ID' grid. Must have a "Cancelled" dictionary value defined in 'Dictionary Update' for the 'Client' file, "(10005) Appointment Status" data element: Extended data element "(60030) Disposition" must be set to "Cancelled". Extended data element "(60031) CarePOV Appointment Status" must be set to either "Cancelled by Patient" or "Cancelled by Staff". A client is enrolled in "Program A" and has the following on file: 'Client Name', 'Address - Street', 'Zipcode', 'Cell Phone', 'Diagnosis', "Guarantor A" selected in 'Financial Eligibility' (Client A). A practitioner must be defined as an EVV resource with hours for scheduling and has the following on file: 'Name', 'Date Of Birth', 'Cellular Telephone', 'Staff EVV ID', 'Email Address', and 'Staff EVV Type' (Practitioner A). Steps Access the 'Scheduling Calendar' form. Right click in any available future time slot for "Practitioner A" and click [Add Appointment]. Select "Service Code A" in the 'Service Code' field. Select "Client A" in the 'Client' field. Validate the 'Program' field contains "Program A". Validate the 'Location' field contains "Location A". Populate all other required and desired fields. Click [Submit]. Validate the new appointment is displayed. Click [Dismiss]. Access the 'CareFabric Monitor' form. Enter the current date in the 'From Date' and 'Through Date' fields. Select "Client A" in the 'Client ID' field. Select "EvvAppointmentUpdated' in the 'Event/Action Search' field. Click [View Activity Log]. Validate the 'CareFabric Monitor Report' contains an "EvvAppointmentUpdated" record. Click [Click To View Record]. Validate the 'appointmentAuthorization' field contains "null". Validate the 'auditInformation' - 'lastUpdatedByStaffMemberID' - 'id' field contains the logged in user ID. Validate the 'auditInformation' - 'lastUpdatedDate' field contains the date/time the appointment was scheduled. Validate the 'appointmentID' - 'id' field contains the appointment ID. Validate the 'canceledDate' field contains "null". Validate the 'canceledReasonCode' field contains "null". Validate the 'providerOrganizationID' - 'id' field contains the 'Provider Organization ID' assigned to "Program A". Validate the 'clientID' - 'id' field contains the ID for "Client A". Validate the 'diagnosisCodes' - 'code' field contains the diagnosis code on file for "Client A". Validate the 'diagnosisCodes' - 'displayName' field contains the diagnosis value on file for "Client A". Validate the 'endDate' field contains the appointment end date/time. Validate the 'insPayerID' - 'id' field contains the 'MCG+ Payer ID' on file in the 'CarePOV Management' form for "Guarantor A". Validate the 'insPlanID' - 'id' field contains the 'MCG+ Insurance Plan ID' on file in the 'CarePOV Management' form for "Guarantor A". Validate the 'isEVV' field contains "true". Validate the 'locationOfService' fields contain "Client A's" home address. Validate the 'mcgInsPayerID' - 'id' field contains the 'MCG+ Payer ID' on file in the 'CarePOV Management' form for "Guarantor A". Validate the 'mcgInsPlanID' - 'id' field contains the 'MCG+ Insurance Plan ID' on file in the 'CarePOV Management' form for "Guarantor A". Validate the 'services' - 'description' field contains the description for "Service Code A". Validate the 'services' - 'name' field contains the code for "Service Code A". Validate the 'services' - 'procedureCode' - 'code' field contains the code for "Procedure A". Validate the 'services' - 'procedureCode' - 'displayName' field contains the name for "Procedure A". Validate the 'serviceID' - 'id' field contains the code for "Service Code A". Validate the 'startDate' field contains the appointment start date/time. Validate all other relevant information is displayed for "Client A" and "Practitioner A". Close the report and the form. Access the 'Scheduling Calendar' form. Right click on the appointment for "Client A". Click [Status Update]. Select "Cancelled" in the 'Appointment Status' field. Validate the 'Cancellation Reason' field is not required. Click [Submit] and [Dismiss]. Access the 'CareFabric Monitor' form. Enter the current date in the 'From Date' and 'Through Date' fields. Select "Client A" in the 'Client ID' field. Select "EvvAppointmentUpdated' in the 'Event/Action Search' field. Click [View Activity Log]. Validate the 'CareFabric Monitor Report' contains an "EvvAppointmentUpdated" record. Click [Click To View Record]. Validate the 'auditInformation' - 'lastUpdatedByStaffMemberID' - 'id' field contains the logged in user ID. Validate the 'auditInformation' - 'lastUpdatedDate' field contains the date/time the appointment was cancelled. Validate the 'canceledDate' field contains the canceled date/time. Validate the 'canceledReasonCode' field contains "null". Close the report and the form. Scenario 4: Mobile CareGiver+ - Scheduling Calendar - Validate 'Client Alternate Addresses' functionality Specific Setup: Avatar is configured to integrate with Mobile CareGiver+. Please note: This must be done by a Netsmart Representative. A program is defined with a value populated in the 'EVV Provider Organization ID' field in the 'Program Maintenance' form (Program A). "Program A" has an associated location (Location A) with the following defined in 'Dictionary Update' for the "Client" file, "(10006 Location)" data element: Extended dictionary data element "(587) Place Of Service (Mobile CareGiver+)" If the above dictionary data element is not defined, then the extended dictionary data element "(579) Place Of Service (837 Electronic Billing)" will be used and must be set to "Home". If this dictionary data element is not defined, then "(578) Place Of Service (HCFA 24-B)" will be used and must be set to "Home". A service code must be defined that has "Yes" selected in the 'Does This Service Require Electronic Visit Verification' field in the 'Service Codes' form and must be assigned to "Program A" (Service Code A). This service code must also have a CPT-4/HCPCS code associated to it in the 'Service Fee/Cross Reference Maintenance' form (Procedure Code A). Dictionary values must be defined for the 'Other Tabled Files' - '(424) Available Electronic Visit Verification Tasks' Data Element in 'Dictionary Update (PM)'. Must have a guarantor defined in the 'Guarantors/Payors' form (Guarantor A). The following must be set in the "Electronic Visit Verification" section of the 'CarePOV Management' form: "Yes" is selected in the 'Enable Mobile CareGiver+' field. "Yes" is selected in the 'Send Non EVV Payers' field. "No" is selected in the 'Require Authorization' field. "Guarantor A" has a row with all fields populated in the 'Payor Program ID' grid. A client is enrolled in "Program A" and has the following on file: 'Client Name', 'Address - Street', 'Zipcode', 'Cell Phone', 'Diagnosis', "Guarantor A" selected in 'Financial Eligibility' (Client A). A practitioner must be defined as an EVV resource with hours for scheduling and has the following on file: 'Name', 'Date Of Birth', 'Cellular Telephone', 'Staff EVV ID', 'Email Address', and 'Staff EVV Type' (Practitioner A). The 'Enable Client Alternate Addresses' registry setting must be set to "Y". Steps Access the 'Dictionary Update' PM form. Select "Client" in the 'File' field. Select "(10006) Location" in the 'Data Element' field. Enter the desired value in the 'Dictionary Code' field. Enter "MCG+ Alternate Location" in the 'Dictionary Value' field. Select "(587) Place Of Service (Mobile CareGiver+)" in the 'Extended Dictionary Data Element' field. Select "(53) Community Mental Health Center" (or any other non "Home" value) in the 'Extended Dictionary Value (Single Dictionary)' field. Select "(579) Place Of Service (837 Electronic Billing)" in the 'Extended Dictionary Data Element' field. Select "Other Unlisted Facility" (or any other non "Home" value) in the 'Extended Dictionary Value (Single Dictionary)' field. Select "(578) Place Of Service (HCFA 24-B)" in the 'Extended Dictionary Data Element' field. Select "Other Unlisted Facility" (or any other non "Home" value) in the 'Extended Dictionary Value (Single Dictionary)' field. Click [Apply Changes]. Validate a message is displayed stating: Filed! Click [OK] and close the form. Access the 'Client Alternate Addresses' form. Select "Client A" in the 'Client' field. Select "Add" in the 'Add/Edit' field. Enter "Alternate Address Test" in the 'Description' field. Enter the desired value in the 'Address Line 1' field. Enter the desired date in the 'Address Start Date' field. Enter the desired value in the 'Zip' field. Enter the desired value in the 'Contact Name' field. Enter the desired value in the 'Contact Phone' field. Enter the desired value in the 'Address Notes' field. Select "MCG+ Alternate Location" in the 'Address Type' field. Select "Yes" in the 'Enabled' field. Click [File]. Validate a message is displayed stating: Saved. Click [OK] and close the form. Access the 'Scheduling Calendar' form. Right click in any available future time slot for "Practitioner A" and click [Add Appointment]. Select "Service Code A" in the 'Service Code' field. Select "Client A" in the 'Client' field. Validate the 'Program' field contains "Program A". Select "MCG+ Alternate Location" in the 'Location' field. Validate the 'Select Address of Service' field is displayed and does not contain any value, by default. Click [Submit]. Validate a message is displayed stating: Mobile CareGiver+: Missing Client Information: Location (LocationOfService) is missing. This is because the 'Place Of Service' extended dictionary elements do not have a value of "Home". If a value of "Home" is not selected, an address must be selected in the 'Select Address of Service' field. Click [OK]. Validate the 'Select Address of Service' field contains "Primary Address (Demographics)" and "Alternate Address Test". Select "Alternate Address Test" in the 'Select Address of Service' field. Click [Submit]. Validate the new appointment is displayed. Click [Dismiss]. Access the 'CareFabric Monitor' form. Enter the current date in the 'From Date' and 'Through Date' fields. Select "Client A" in the 'Client ID' field. Select "EvvAppointmentUpdated" in the 'Event/Action Search' field. Click [View Activity Log]. Validate the 'CareFabric Monitor Report' contains an "EvvAppointmentUpdated" record. Click [Click To View Record]. Validate the 'locationOfService' fields contain "Client A's" alternate address values (Alternate Address Test). Validate the 'locationOfService' - 'typeCode' - 'code' field contains the code selected for the '(587) Place Of Service (Mobile CareGiver+)' extended dictionary data element. Validate the 'locationOfService' - 'typeCode' - 'displayName' field contains the value selected for the '(587) Place Of Service (Mobile CareGiver+)' extended dictionary data element. Validate all other data displays as expected. Close the report and the form. Access the 'Client Alternate Addresses' form. Select "Client A" in the 'Client' field. Select "Edit" in the 'Add/Edit' field. Select "Alternate Address Test" in the 'Select Existing Address' field. Enter the desired new value in the 'Address Line 1' field. Click [File]. Validate a message is displayed stating: Saved. Click [OK] and close the form. Access the 'CareFabric Monitor' form. Enter the current date in the 'From Date' and 'Through Date' fields. Select "Client A" in the 'Client ID' field. Select "EvvAppointmentUpdated" in the 'Event/Action Search' field. Click [View Activity Log]. Validate the 'CareFabric Monitor Report' contains an "EvvAppointmentUpdated" record. Click [Click To View Record]. Validate the 'locationOfService' fields contain "Client A's" new alternate address values. Validate the 'locationOfService' - 'typeCode' - 'code' field contains the code selected for the '(587) Place Of Service (Mobile CareGiver+)' extended dictionary data element. Validate the 'locationOfService' - 'typeCode' - 'displayName' field contains the value selected for the '(587) Place Of Service (Mobile CareGiver+)' extended dictionary data element. Validate all other data displays as expected. Close the report and the form. Scenario 5: Mobile Caregiver+ - Validate the 'McgEvvAppointmentUpdated' incoming event when a client's alternate address is used Specific Setup: Avatar is configured to integrate with Mobile CareGiver+. Please note: This must be done by a Netsmart Representative. A product is defined in the 'CareFabric Integration Management' form for the "MobileCareGiver+" product and "McgEvvAppointmentUpdated" must be selected in the 'Event Types' field. A program is defined with a value populated in the 'EVV Provider Organization ID' field in the 'Program Maintenance' form (Program A). "Program A" has an associated location (Location A) with the following defined in 'Dictionary Update' for the "Client" file, "(10006 Location)" data element: Extended dictionary data element "(587) Place Of Service (Mobile CareGiver+)" must be set to "Home" (unless an alternate address is being used). If the above dictionary data element is not defined, then the extended dictionary data element "(579) Place Of Service (837 Electronic Billing)" will be used and must be set to "Home". If this dictionary data element is not defined, then "(578) Place Of Service (HCFA 24-B)" will be used and must be set to "Home". A service code must be defined that has "Yes" selected in the 'Does This Service Require Electronic Visit Verification' field in the 'Service Codes' form and must be assigned to "Program A" (Service Code A). This service code must also have a CPT-4/HCPCS code associated to it in the 'Service Fee/Cross Reference Maintenance' form (Procedure Code A). Must have a guarantor defined in the 'Guarantors/Payors' form (Guarantor A). A site is defined with hours for scheduling (Site A). A practitioner must be defined as an EVV resource with hours for scheduling at "Site A" and has the following on file: 'Name', 'Date Of Birth', 'Cellular Telephone', 'Staff EVV ID', 'Email Address', and 'Staff EVV Type' (Practitioner A). The following must be set in the "Electronic Visit Verification" section of the 'CarePOV Management' form: "Yes" is selected in the 'Enable Mobile CareGiver+' field. "Yes" is selected in the 'Send Non EVV Payers' field. "No" is selected in the 'Require Authorization' field. "Guarantor A" has a row with all fields populated in the 'Payor Program ID' grid. "Site A" selected in the 'Site' field. "Yes" is selected in the following fields for the 'McgEvvAppointmentUpdated' event: 'Keep Incoming Payload in the Log', 'Keep Outgoing Payload in the Log' and 'Show in the CareFabric Monitor Report' in the 'CareFabric Management' form. This must be done by a Netsmart Representative. A client is enrolled in "Program A" and has the following on file: 'Client Name', 'Address - Street', 'Zipcode', 'Cell Phone', 'Diagnosis', "Guarantor A" selected in 'Financial Eligibility' (Client A). The 'Enable Client Alternate Addresses' registry setting must be set to "Y". "Client A" has an alternate address on file in the 'Client Alternate Addresses' form (Alternate Address A). Steps Add an unscheduled visit in the Mobile CareGiver+ application for "Client A" with "Practitioner A", using "Alternate Address A" as the location of service. Please note: if any of the appointment information sent from Mobile CareGiver+ can't be determined, the appointment will be available for reconciliation in the 'CareFabric Integration Reconciliation' form. Access the 'CareFabric Monitor' form. Enter the current date in the 'From Date' and 'Through Date' fields. Select "Client A" in the 'Client ID' field. Select "McgEvvAppointmentUpdated' in the 'Event/Action Search' field. Click [View Activity Log]. Validate the 'CareFabric Monitor Report' contains an "McgEvvAppointmentUpdated" record. Click [Click To View Record]. Validate the 'clientID- 'id' field contains "Client A". Validate the 'endDate' field contains the appointment end date/time. Validate the 'mcgAppointmentID' - 'id' field contains the MCG+ unique identifier for the appointment. Validate the 'resource' - 'resourceID' field contains "Practitioner A". Validate the 'services' - 'procedureCode' - 'code' field contains "Procedure Code A". Validate the 'locationOfService' fields contain "Alternate Address A". Validate the 'startDate' field contains the appointment start date/time. Validate all other appointment data is displayed. Close the report and the form. Access the 'Scheduling Calendar' form. Validate the appointment for "Client A" with "Practitioner A" that was sent from Mobile CareGiver+ is displayed at "Site A". Right click on the appointment and click [Details/Edit]. Validate the appointment details are displayed as expected. Validate the 'Location' field contains the location associated to "Alternate Address A". Validate the 'Select Address of Service' field contains "Alternate Address A". Close the form and click [Dismiss]. Scenario 6: Mobile CareGiver + - Validate the 'McgEvvAppointmentUpdated' incoming event for multiple recipients Specific Setup: Avatar is configured to integrate with Mobile CareGiver+. Please note: This must be done by a Netsmart Representative. A product is defined in the 'CareFabric Integration Management' form for the "MobileCareGiver+" product and "McgEvvAppointmentUpdated" must be selected in the 'Event Types' field. A program is defined with a value populated in the 'EVV Provider Organization ID' field in the 'Program Maintenance' form (Program A). "Program A" has an associated location (Location A) with the following defined in 'Dictionary Update' for the "Client" file, "(10006 Location)" data element: Extended dictionary data element "(587) Place Of Service (Mobile CareGiver+)" must be set to "Home" (unless an alternate address is being used). If the above dictionary data element is not defined, then the extended dictionary data element "(579) Place Of Service (837 Electronic Billing)" will be used and must be set to "Home". If this dictionary data element is not defined, then "(578) Place Of Service (HCFA 24-B)" will be used and must be set to "Home". A service code must be defined that has "Yes" selected in the 'Does This Service Require Electronic Visit Verification' field in the 'Service Codes' form and must be assigned to "Program A" (Service Code A). This service code must also have a CPT-4/HCPCS code associated to it in the 'Service Fee/Cross Reference Maintenance' form (Procedure Code A). Must have a guarantor defined in the 'Guarantors/Payors' form (Guarantor A). A site is defined with hours for scheduling (Site A). The following must be set in the "Electronic Visit Verification" section of the 'CarePOV Management' form: "Yes" is selected in the 'Enable Mobile CareGiver+' field. "Yes" is selected in the 'Send Non EVV Payers' field. "No" is selected in the 'Require Authorization' field. "Guarantor A" has a row with all fields populated in the 'Payor Program ID' grid. "Site A" selected in the 'Site' field. "Yes" is selected in the following fields for the 'McgEvvAppointmentUpdated' event: 'Keep Incoming Payload in the Log', 'Keep Outgoing Payload in the Log' and 'Show in the CareFabric Monitor Report' in the 'CareFabric Management' form. This must be done by a Netsmart Representative. A practitioner must be defined as an EVV resource with hours for scheduling at "Site A" and has the following on file: 'Name', 'Date Of Birth', 'Cellular Telephone', 'Staff EVV ID', 'Email Address', and 'Staff EVV Type' (Practitioner A). Two clients are enrolled in "Program A" and have the following on file: 'Client Name', 'Address - Street', 'Zipcode', 'Cell Phone', 'Diagnosis', "Guarantor A" selected in 'Financial Eligibility' (Client A & Client B). The 'Enable Client Alternate Addresses' registry setting must be set to "Y". Steps Add an unscheduled visit in the Mobile CareGiver+ application for multiple recipients (Client A & Client B) with "Practitioner A", using the primary home address for "Client A" as the location of service. Please note: if any of the appointment information sent from Mobile CareGiver+ can't be determined, the appointment will be available for reconciliation in the 'CareFabric Integration Reconciliation' form. Access the 'CareFabric Monitor' form. Enter the current date in the 'From Date' and 'Through Date' fields. Select "McgEvvAppointmentUpdated" in the 'Event/Action Search' field. Click [View Activity Log]. Validate the 'CareFabric Monitor Report' contains an "McgEvvAppointmentUpdated" record. Click [Click To View Record]. Validate the 'endDate' field contains the appointment end date/time. Validate the 'isMultipleRecipients' field contains "true". Validate the 'mcgAppointmentID' - 'id' field contains the MCG+ unique identifier for the appointment. Validate the 'resource' - 'resourceID' field contains "Practitioner A". Validate the first - 'services' - 'clientID- 'id' field contains "Client A". Validate the first 'services' - 'procedureCode' - 'code' field contains "Procedure Code A". Validate the second 'services' - 'clientID' - 'id' field contains "Client B". Validate the second 'services' - 'procedureCode' - 'code' field contains "Procedure Code A". Validate the 'locationOfService' fields contain the primary home address for "Client A". Validate the 'startDate' field contains the appointment start date/time. Validate all other appointment data is displayed. Close the report and the form. Access the 'Scheduling Calendar' form. Validate an appointment for "Client A" and "Client B" with "Practitioner A" that was sent from Mobile CareGiver+ is displayed at "Site A". Right click on the appointment for "Client A" and click [Details/Edit]. Validate the appointment details are displayed as expected. Validate the 'Select Address of Service' field contains "Primary Address (Demographics)". Close the form. Right click on the appointment for "Client B" and click [Details/Edit]. Validate the appointment details are displayed as expected. Validate the 'Select Address of Service' field contains "Address created by Mobile Caregiver+". Close the form and click [Dismiss]. Access the 'Client Alternate Addresses' form. Select "Client B" in the 'Client' field. Select "Edit" in the 'Add/Edit' field. Validate the 'Select Existing Address' field contains "Address created by Mobile Caregiver+" and select it. Validate the primary home address details for "Client A" are displayed since this address was used as the location of service. Close the form. Scenario 7: Mobile Caregiver+ - Validate the 'McgEvvAppointmentUpdated' incoming event when for an appointment with multiple recipients using alternate addresses Specific Setup: Avatar is configured to integrate with Mobile CareGiver+. Please note: This must be done by a Netsmart Representative. A product is defined in the 'CareFabric Integration Management' form for the "MobileCareGiver+" product and "McgEvvAppointmentUpdated" must be selected in the 'Event Types' field. A program is defined with a value populated in the 'EVV Provider Organization ID' field in the 'Program Maintenance' form (Program A). "Program A" has an associated location (Location A) with the following defined in 'Dictionary Update' for the "Client" file, "(10006 Location)" data element: Extended dictionary data element "(587) Place Of Service (Mobile CareGiver+)" must be set to "Home" (unless an alternate address is being used). If the above dictionary data element is not defined, then the extended dictionary data element "(579) Place Of Service (837 Electronic Billing)" will be used and must be set to "Home". If this dictionary data element is not defined, then "(578) Place Of Service (HCFA 24-B)" will be used and must be set to "Home". A service code must be defined that has "Yes" selected in the 'Does This Service Require Electronic Visit Verification' field in the 'Service Codes' form and must be assigned to "Program A" (Service Code A). This service code must also have a CPT-4/HCPCS code associated to it in the 'Service Fee/Cross Reference Maintenance' form (Procedure Code A). Must have a guarantor defined in the 'Guarantors/Payors' form (Guarantor A). A site is defined with hours for scheduling (Site A). The following must be set in the "Electronic Visit Verification" section of the 'CarePOV Management' form: "Yes" is selected in the 'Enable Mobile CareGiver+' field. "Yes" is selected in the 'Send Non EVV Payers' field. "No" is selected in the 'Require Authorization' field. "Guarantor A" has a row with all fields populated in the 'Payor Program ID' grid. "Site A" selected in the 'Site' field. "Yes" is selected in the following fields for the 'McgEvvAppointmentUpdated' event: 'Keep Incoming Payload in the Log', 'Keep Outgoing Payload in the Log' and 'Show in the CareFabric Monitor Report' in the 'CareFabric Management' form. This must be done by a Netsmart Representative. A practitioner must be defined as an EVV resource with hours for scheduling at "Site A" and has the following on file: 'Name', 'Date Of Birth', 'Cellular Telephone', 'Staff EVV ID', 'Email Address', and 'Staff EVV Type' (Practitioner A). Two clients are enrolled in "Program A" and have the following on file: 'Client Name', 'Address - Street', 'Zipcode', 'Cell Phone', 'Diagnosis', "Guarantor A" selected in 'Financial Eligibility' (Client A & Client B). The 'Enable Client Alternate Addresses' registry setting must be set to "Y". "Client A" has an alternate address on file in the 'Client Alternate Addresses' form (Alternate Address A). Steps Add an unscheduled visit in the Mobile CareGiver+ application for multiple recipients (Client A & Client B) with "Practitioner A", using "Alternate Address A" for "Client A" as the location of service. Please note: if any of the appointment information sent from Mobile CareGiver+ can't be determined, the appointment will be available for reconciliation in the 'CareFabric Integration Reconciliation' form. Access the 'CareFabric Monitor' form. Enter the current date in the 'From Date' and 'Through Date' fields. Select "McgEvvAppointmentUpdated" in the 'Event/Action Search' field. Click [View Activity Log]. Validate the 'CareFabric Monitor Report' contains an "McgEvvAppointmentUpdated" record. Click [Click To View Record]. Validate the 'endDate' field contains the appointment end date/time. Validate the 'isMultipleRecipients' field contains "true". Validate the 'mcgAppointmentID' - 'id' field contains the MCG+ unique identifier for the appointment. Validate the 'resource' - 'resourceID' field contains "Practitioner A". Validate the first - 'services' - 'clientID- 'id' field contains "Client A". Validate the first 'services' - 'procedureCode' - 'code' field contains "Procedure Code A". Validate the second 'services' - 'clientID' - 'id' field contains "Client B". Validate the second 'services' - 'procedureCode' - 'code' field contains "Procedure Code A". Validate the 'locationOfService' fields contain "Alternate Address A". Validate the 'startDate' field contains the appointment start date/time. Validate all other appointment data is displayed. Close the report and the form. Access the 'Scheduling Calendar' form. Validate an appointment for "Client A" and "Client B" with "Practitioner A" that was sent from Mobile CareGiver+ is displayed at "Site A". Right click on the appointment for "Client A" and click [Details/Edit]. Validate the appointment details are displayed as expected. Validate the 'Select Address of Service' field contains "Alternate Address A". Close the form. Right click on the appointment for "Client B" and click [Details/Edit]. Validate the appointment details are displayed as expected. Validate the 'Select Address of Service' field contains "Alternate Address A". Close the form and click [Dismiss]. Access the 'Client Alternate Addresses' form. Select "Client B" in the 'Client' field. Select "Edit" in the 'Add/Edit' field. Validate the 'Select Existing Address' field contains "Alternate Address A" and select it. Validate the "Alternate Address A" details from "Client A" are displayed since this address was used as the location of service. Close the form.	Topics • CarePOV Management • Electronic Visit Verification
Update 11 Summary \| Details 'Explanation Of Benefits' CareFabric Support - Inpatient Scenario 1: Verification of 'GetExplanationOfBenefitResource' Action for Avatar MSO 837 Institutional/835 EOB Information Steps Internal testing only. Scenario 2: Verification of 'GetExplanationOfBenefitResource' Action for Avatar PM/Cal-PM Inpatient 835 EOB Information Steps Internal testing only. Scenario 3: Verification of 'ListExplanationOfBenefitResource' Action for Avatar MSO 837 Institutional/835 EOB Information Steps Internal testing only. Scenario 4: Verification of 'ListExplanationOfBenefitResource' Action for Avatar PM/Cal-PM Inpatient 835 EOB Information Steps Internal testing only. Scenario 5: Verification of 'GetExplanationOfBenefitResource' Action for Avatar MSO 837 Institutional/835 EOB Information Steps Internal testing only. Scenario 6: Verification of 'GetExplanationOfBenefitResource' Action for Avatar PM/Cal-PM Inpatient 835 EOB Information Steps Internal testing only. Scenario 7: Verification of 'ListExplanationOfBenefitResource' Action for Avatar MSO 837 Institutional/835 EOB Information Steps Internal testing only. Scenario 8: Verification of 'ListExplanationOfBenefitResource' Action for Avatar PM/Cal-PM Inpatient 835 EOB Information Steps Internal testing only. 'Explanation Of Benefits' CareFabric Support - Outpatient Scenario 1: Verification of 'GetExplanationOfBenefitResource' Action for Avatar MSO 837 Professional/835 EOB Information Steps Internal testing only. Scenario 2: Verification of 'GetExplanationOfBenefitResource' Action for Avatar PM/Cal-PM Outpatient 835 EOB Information Steps Internal testing only. Scenario 3: Verification of 'ListExplanationOfBenefitResource' Action for Avatar MSO 837 Professional/835 EOB Information Steps Internal testing only. Scenario 4: Verification of 'ListExplanationOfBenefitResource' Action for Avatar PM/Cal-PM Outpatient 835 EOB Information Steps Internal testing only. Scenario 5: Verification of 'GetExplanationOfBenefitResource' Action for Avatar MSO 837 Professional/835 EOB Information Steps Internal testing only. Scenario 6: Verification of 'GetExplanationOfBenefitResource' Action for Avatar PM/Cal-PM Outpatient 835 EOB Information Steps Internal testing only. Scenario 7: Verification of 'ListExplanationOfBenefitResource' Action for Avatar MSO 837 Professional/835 EOB Information Steps Internal testing only. Scenario 8: Verification of 'ListExplanationOfBenefitResource' Action for Avatar PM/Cal-PM Outpatient 835 EOB Information Steps Internal testing only. 'Explanation Of Benefits' CareFabric Support Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following: 835 Health Care Claim Payment/Advice (PM) CareFabric Monitor 835 Health Care Claim Payment/Advice (MSO) Scenario 1: Verification of 'BulkDataStoreUpdate - Explanation Of Benefits' CareFabric Filing via Avatar PM/Cal-PM 835 Posting Specific Setup: 'BulkDataStoreUpdate' action must be enabled in Avatar system (via 'CareFabric Management' form) Inbound 835 Health Care Claim Payment/Advice file containing one or more successfully compiled entries for Avatar PM/Cal-PM claims/services Steps Open Avatar PM/Cal-PM '835 Health Care Claim Payment/Advice' form. Select 'Load File' in the 'Options' field. Enter 'File Path/Name' value for 835 inbound file to be loaded and click 'Process File' button. Ensure 835 file is successfully loaded. Select 'Compile File' in the 'Options' field. Select loaded inbound 835 file in the 'Select File' field and click 'Process File' button. In 835 Compile Report - ensure that payments/adjustments are successfully compiled for one or more Avatar PM/Cal-PM claims/services. Select 'Post File' in the 'Options' field. Select compiled inbound 835 file in the 'Select File' field, enter values for 'Posting Date' and 'Date of Receipt' fields (as well as any other fields as required/desired), and click 'Process File' button. In 835 Posting Report - ensure that payments/adjustments are successfully posted for one or more Avatar PM/Cal-PM claims/services. Open Avatar PM/Cal-PM 'CareFabric Monitor' form. Enter values for 'From Date' and 'Through Date' fields (using dates which include 274 Provider Directory Provider Definition entry/edit). Enter/select values for any other CareFabric Monitor fields as desired. Click 'View Activity Log' button to display CareFabric Monitor report results. In CareFabric Monitor report results - ensure that 'BulkDataStoreUpdate' Action/Out Activity is present for all Explanation Of Benefits/835 information posted via the Avatar PM/Cal-PM '835 Health Care Claim Payment/Advice' form (activity is per claim with 835 remittance advice posted). Scenario 2: Verification of 'BulkDataStoreUpdate - Explanation Of Benefits' CareFabric Filing via Avatar MSO 835 Generation Specific Setup: 'BulkDataStoreUpdate' action must be enabled in Avatar system (via 'CareFabric Management' form) EOB record(s) eligible for 835 outbound file inclusion including one or more claims/services originating via Avatar MSO 837 inbound processing Steps Open Avatar MSO '835 Health Care Claim Payment/Advice' form. Note - Acceptance testing may also be confirmed in 835 files created via Avatar MSO Claim Processing Automation functions Select 'Sort File' in the 'Options' field. Select 'Contracting Provider' value. Select EOB(s) for 835 outbound file inclusion in the 'Select EOB(s)' field. Click 'Process' button. Ensure that '835 Health Care Claim Payment/Advice Report' is displayed following 835 sorting completion (and includes one or more successfully sorted claims/services for 835 file creation). Open Avatar PM/Cal-PM 'CareFabric Monitor' form. Enter values for 'From Date' and 'Through Date' fields (using dates which include 274 Provider Directory Provider Definition entry/edit). Enter/select values for any other CareFabric Monitor fields as desired. Click 'View Activity Log' button to display CareFabric Monitor report results. In CareFabric Monitor report results - ensure that 'BulkDataStoreUpdate' Action/Out Activity is present for all Explanation Of Benefits information/835s generated in the Avatar MSO '835 Health Care Claim Payment/Advice' form for claims/services originating via Avatar MSO 837 inbound processing (activity is per claim with 835 remittance advice generated). Scenario 3: Verification of 'BulkDataStoreUpdate - Explanation Of Benefits' CareFabric Filing via Avatar PM/Cal-PM 835 Posting Specific Setup: 'BulkDataStoreUpdate' action must be enabled in Avatar system (via 'CareFabric Management' form) Inbound 835 Health Care Claim Payment/Advice file containing one or more successfully compiled entries for Avatar PM/Cal-PM claims/services Steps Open Avatar PM/Cal-PM '835 Health Care Claim Payment/Advice' form. Select 'Load File' in the 'Options' field. Enter 'File Path/Name' value for 835 inbound file to be loaded and click 'Process File' button. Ensure 835 file is successfully loaded. Select 'Compile File' in the 'Options' field. Select loaded inbound 835 file in the 'Select File' field and click 'Process File' button. In 835 Compile Report - ensure that payments/adjustments are successfully compiled for one or more Avatar PM/Cal-PM claims/services. Select 'Post File' in the 'Options' field. Select compiled inbound 835 file in the 'Select File' field, enter values for 'Posting Date' and 'Date of Receipt' fields (as well as any other fields as required/desired), and click 'Process File' button. In 835 Posting Report - ensure that payments/adjustments are successfully posted for one or more Avatar PM/Cal-PM claims/services. Open Avatar PM/Cal-PM 'CareFabric Monitor' form. Enter values for 'From Date' and 'Through Date' fields (using dates which include 274 Provider Directory Provider Definition entry/edit). Enter/select values for any other CareFabric Monitor fields as desired. Click 'View Activity Log' button to display CareFabric Monitor report results. In CareFabric Monitor report results - ensure that 'BulkDataStoreUpdate' Action/Out Activity is present for all Explanation Of Benefits/835 information posted via the Avatar PM/Cal-PM '835 Health Care Claim Payment/Advice' form (activity is per claim with 835 remittance advice posted). Scenario 4: Verification of 'BulkDataStoreUpdate - Explanation Of Benefits' CareFabric Filing via Avatar MSO 835 Generation Specific Setup: 'BulkDataStoreUpdate' action must be enabled in Avatar system (via 'CareFabric Management' form) EOB record(s) eligible for 835 outbound file inclusion including one or more claims/services originating via Avatar MSO 837 inbound processing Steps Open Avatar MSO '835 Health Care Claim Payment/Advice' form. Note - Acceptance testing may also be confirmed in 835 files created via Avatar MSO Claim Processing Automation functions Select 'Sort File' in the 'Options' field. Select 'Contracting Provider' value. Select EOB(s) for 835 outbound file inclusion in the 'Select EOB(s)' field. Click 'Process' button. Ensure that '835 Health Care Claim Payment/Advice Report' is displayed following 835 sorting completion (and includes one or more successfully sorted claims/services for 835 file creation). Open Avatar PM/Cal-PM 'CareFabric Monitor' form. Enter values for 'From Date' and 'Through Date' fields (using dates which include 274 Provider Directory Provider Definition entry/edit). Enter/select values for any other CareFabric Monitor fields as desired. Click 'View Activity Log' button to display CareFabric Monitor report results. In CareFabric Monitor report results - ensure that 'BulkDataStoreUpdate' Action/Out Activity is present for all Explanation Of Benefits information/835s generated in the Avatar MSO '835 Health Care Claim Payment/Advice' form for claims/services originating via Avatar MSO 837 inbound processing (activity is per claim with 835 remittance advice generated).	Topics • CareFabric • 835 Health Care Claim Payment/Advice
Update 12 Summary \| Details 'Client Information' header - Non-episodic client alerts Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following: Client Lookup/Header Configuration Manager CarePOV Management Women's Health History Allergies and Hypersensitivities Scenario 1: CarePOV Management - Client Alerts - 'Duplicate Name - Header' alert type based on 'Full Name (First and Last)' Specific Setup: "Bed Board Alerts" should be configured in the 'Client Header' section of the 'Client Lookup/Header Configuration Manager' form. The user has access to the 'Client Information Header' on the HomeView. Two clients are defined with the same first & last name (Client A & Client B). A third client is defined with a different first & last name (Client C). Steps Access the 'CarePOV Management' form. Select the "Client Alerts" section. Click "Add" in the 'Add or Edit Alert' field. Select "Duplicate Name - Header" in the 'Alert Type' field. Validate the 'Base Duplicate Name Alert On' field is now enabled and required. Select "Full Name (First and Last)" in the 'Base Duplicate Name On' field. Enter the desired value in the 'Client Alert Description' field. Select the desired icon in the 'Select Icon' field. Select "Yes" in the 'Active' field. Select "Yes" in the 'Include in Client Header' field. Click [Save]. Validate a message is displayed stating: Saved. Click [OK] and close the form. Select "Client A" and navigate to the 'Client Information' header. Select "All Episodes" in the 'Episode' field. Validate the icon associated to the duplicate name alert added in the previous steps is displayed. Hover over the icon and validate the 'Client Alert Description' added in the previous steps is displayed. Select "Episode 1" in the 'Episode' field. Validate the icon associated to the duplicate name alert added in the previous steps is displayed. Hover over the icon and validate the 'Client Alert Description' added in the previous steps is displayed. Select "Client B" and navigate to the 'Client Information' header. Select "All Episodes" in the 'Episode' field. Validate the icon associated to the duplicate name alert added in the previous steps is displayed. Hover over the icon and validate the 'Client Alert Description' added in the previous steps is displayed. Select "Episode 1" in the 'Episode' field. Validate the icon associated to the duplicate name alert added in the previous steps is displayed. Hover over the icon and validate the 'Client Alert Description' added in the previous steps is displayed. Select "Client C" and navigate to the 'Client Information' header. Validate the duplicate name alert is not displayed. Scenario 2: CarePOV Management - Client Alerts - 'Duplicate Name - Header' alert type based on 'First Name, Last Initial' Specific Setup: "Bed Board Alerts" should be configured in the 'Client Header' section of the 'Client Lookup/Header Configuration Manager' form. The user has access to the 'Client Information Header' on the HomeView. Two clients are defined with the same first name & last initial (Client A & Client B). A third client is defined with a different first name & last initial (Client C). Steps Access the 'CarePOV Management' form. Select the "Client Alerts" section. Click "Add" in the 'Add or Edit Alert' field. Select "Duplicate Name - Header" in the 'Alert Type' field. Validate the 'Base Duplicate Name Alert On' field is now enabled and required. Select "First Name, Last Initial" in the 'Base Duplicate Name On' field. Enter the desired value in the 'Client Alert Description' field. Select the desired icon in the 'Select Icon' field. Select "Yes" in the 'Active' field. Select "Yes" in the 'Include in Client Header' field. Click [Save]. Validate a message is displayed stating: Saved. Click [OK] and close the form. Select "Client A" and navigate to the 'Client Information' header. Select "All Episodes" in the 'Episode' field. Validate the icon associated to the duplicate name alert added in the previous steps is displayed. Hover over the icon and validate the 'Client Alert Description' added in the previous steps is displayed. Select "Episode 1" in the 'Episode' field. Validate the icon associated to the duplicate name alert added in the previous steps is displayed. Hover over the icon and validate the 'Client Alert Description' added in the previous steps is displayed. Select "Client B" and navigate to the 'Client Information' header. Select "All Episodes" in the 'Episode' field. Validate the icon associated to the duplicate name alert added in the previous steps is displayed. Hover over the icon and validate the 'Client Alert Description' added in the previous steps is displayed. Select "Episode 1" in the 'Episode' field. Validate the icon associated to the duplicate name alert added in the previous steps is displayed. Hover over the icon and validate the 'Client Alert Description' added in the previous steps is displayed. Select "Client C" and navigate to the 'Client Information' header. Validate the duplicate name alert is not displayed. Scenario 3: CarePOV Management - Client Alerts - 'Duplicate Name - Header' alert type based on 'Last Name & First Initial' Specific Setup: "Bed Board Alerts" should be configured in the 'Client Header' section of the 'Client Lookup/Header Configuration Manager' form. The user has access to the 'Client Information Header' on the HomeView. Two clients are defined with the same last name & first initial (Client A & Client B). A third client is defined with a different last name & first initial (Client C). Steps Access the 'CarePOV Management' form. Select the "Client Alerts" section. Click "Add" in the 'Add or Edit Alert' field. Select "Duplicate Name - Header" in the 'Alert Type' field. Validate the 'Base Duplicate Name Alert On' field is now enabled and required. Select "Last Name, First Initial" in the 'Base Duplicate Name On' field. Enter the desired value in the 'Client Alert Description' field. Select the desired icon in the 'Select Icon' field. Select "Yes" in the 'Active' field. Select "Yes" in the 'Include in Client Header' field. Click [Save]. Validate a message is displayed stating: Saved. Click [OK] and close the form. Select "Client A" and navigate to the 'Client Information' header. Select "All Episodes" in the 'Episode' field. Validate the icon associated to the duplicate name alert added in the previous steps is displayed. Hover over the icon and validate the 'Client Alert Description' added in the previous steps is displayed. Select "Episode 1" in the 'Episode' field. Validate the icon associated to the duplicate name alert added in the previous steps is displayed. Hover over the icon and validate the 'Client Alert Description' added in the previous steps is displayed. Select "Client B" and navigate to the 'Client Information' header. Select "All Episodes" in the 'Episode' field. Validate the icon associated to the duplicate name alert added in the previous steps is displayed. Hover over the icon and validate the 'Client Alert Description' added in the previous steps is displayed. Select "Episode 1" in the 'Episode' field. Validate the icon associated to the duplicate name alert added in the previous steps is displayed. Hover over the icon and validate the 'Client Alert Description' added in the previous steps is displayed. Select "Client C" and navigate to the 'Client Information' header. Validate the duplicate name alert is not displayed. Scenario 4: CarePOV Management - Client Alerts - Validate the 'Pregnancy' alert type Specific Setup: "Bed Board Alerts" should be configured in the 'Client Header' section of the 'Client Lookup/Header Configuration Manager' form. The user has access to the 'Client Information Header' on the HomeView. A female client is enrolled in an existing episode (Client A). The "(357) Pregnant Status" dictionary must have a code/value configured for "Pregnant" with "Yes" selected for the 'System Pregnancy Status' extended data element. Steps Access the 'CarePOV Management' form. Select the "Client Alerts" section. Click "Add" in the 'Add or Edit Alert' field. Select "Pregnancy" in the 'Alert Type' field. Enter the desired value in the 'Client Alert Description' field. Select the desired icon in the 'Select Icon' field. Select "Yes" in the 'Active' field. Select "Yes" in the 'Include in Client Header' field. Click [Save]. Validate a message is displayed stating: Saved. Click [OK] and close the form. Select "Client A" and access the 'Women's Health History' form. Enter the desired date in the 'Assessment Date' field. Enter the desired date in the 'Pregnancy Start Date' field. Select "Yes" in the 'Have you ever been pregnant?' field. Select "Pregnant" in the 'Pregnant Status' field. Enter the desired date in the 'Expected Due Date' field. Click [Submit]. Select "Client A" and navigate to the 'Client Information' header. Select "All Episodes" in the 'Episode' field. Validate the icon associated to the Pregnancy alert added in the previous steps is displayed. Hover over the icon and validate the 'Client Alert Description' added in the previous steps is displayed. Select "Episode 1" in the 'Episode' field. Validate the icon associated to the Pregnancy alert added in the previous steps is displayed. Hover over the icon and validate the 'Client Alert Description' added in the previous steps is displayed. Scenario 5: CarePOV Management - Client Alerts - Validate the 'Allergy' alert type Specific Setup: "Bed Board Alerts" should be configured in the 'Client Header' section of the 'Client Lookup/Header Configuration Manager' form. The user has access to the 'Client Information Header' on the HomeView. A client is enrolled in an existing episode (Client A). Steps Access the 'CarePOV Management' form. Select the "Client Alerts" section. Click "Add" in the 'Add or Edit Alert' field. Select "Allergy" in the 'Alert Type' field. Enter the desired value in the 'Client Alert Description' field. Select the desired icon in the 'Select Icon' field. Select "Yes" in the 'Active' field. Select "Yes" in the 'Include in Client Header' field. Click [Save]. Validate a message is displayed stating: Saved. Click [OK] and close the form. Access the 'Allergies and Hypersensitivities' form Click [Update]. Validate the 'Allergies and Hypersensitivities' grid is displayed. Click [New Row]. Add any new active allergy Click [Save] and submit the form. Select "Client A" and navigate to the 'Client Information' header. Select "All Episodes" in the 'Episode' field. Validate the icon associated to the Allergy alert added in the previous steps is displayed. Hover over the icon and validate the 'Client Alert Description' added in the previous steps is displayed. Select "Episode 1" in the 'Episode' field. Validate the icon associated to the Allergy alert added in the previous steps is displayed. Hover over the icon and validate the 'Client Alert Description' added in the previous steps is displayed.	Topics • Client Alerts • CarePOV Management
Update 14 Summary \| Details Avatar CareFabric - Progress Notes Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following: Registry Settings (PM) Scenario 1: 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 2: 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.	Topics • Progress Notes • CareFabric • Bells Notes
Update 15 Summary \| Details Avatar CareFabric - Support for future functionality Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following: CareFabric Monitor Scenario 1: Diagnosis - Validate the 'DiagnosisCreated' and 'DiagnosisUpdated' SDK events Specific Setup: A client is enrolled in an existing episode (Client A). The logged in user has an associated staff member. Steps Select "Client A" and access the 'Diagnosis' form. Select the desired value in the 'Type Of Diagnosis' field. Enter the desired date in the 'Date Of Diagnosis' field. Enter the desired time the 'Time Of Diagnosis' field. Click [New Row]. Select the desired value in the 'Diagnosis Search' field. Select "Active" in the 'Status' field. Select the desired practitioner in the 'Diagnosing Practitioner' field. Click [Submit]. Access the 'CareFabric Monitor' form. Enter the current date in the 'From Date' and 'Through Date' fields. Select "Client A" in the 'Client ID' field. Select "DiagnosisCreated" in the 'Event/Action Search' field. Click [View Activity Log]. Validate the 'CareFabric Monitor Report' displays a 'DiagnosisCreated' record. Click [Click To View Record]. Validate the 'startDate' field contains the 'Date Of Diagnosis' and 'Time Of Diagnosis' populated in the previous steps. Validate the 'statusCode' - 'code' field contains "1". Validate the 'statusCode' - 'displayName' field contains "Active". Validate the 'voidedByStaffMemberID' field contains "null". Validate the 'voidedDate' field contains "null". Validate all other previously filed data displays as expected. Close the report and the form. Select "Client A" and access the 'Diagnosis' form. Select the diagnosis created in the previous steps and click [Edit]. Select the row filed in the previous steps from the 'Diagnoses' grid. Select "Void" in the 'Status' field. Click [Submit]. Access the 'CareFabric Monitor' form. Enter the current date in the 'From Date' and 'Through Date' fields. Select "Client A" in the 'Client ID' field. Select "DiagnosisUpdated" in the 'Event/Action Search' field. Click [View Activity Log]. Validate the 'CareFabric Monitor Report' displays a 'DiagnosisUpdated' record. Click [Click To View Record]. Validate the 'statusCode' - 'code' field contains "5". Validate the 'statusCode' - 'displayName' field contains "Void". Validate the 'voidedByStaffMemberID' - 'id' field contains the logged in staff member. Validate the 'voidedDate' field contains the current date. Close the report and the form.	Topics • CareFabric • Diagnosis
Update 16 Summary \| Details Bells Notes Integration - Support for multiple session start/end times Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following: Registry Settings (PM) Scenario 1: Bells Notes Integration - Validate filing progress notes with multiple session times 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 does not have 'Document Routing' enabled. The 'Multiple Start and End Times to Document Sessions' registry setting must be set to "Y" for the 'Progress Notes (Group and Individual)' form. Must have a note type in Bells for the 'Progress Notes (Group and Individual)' form (Note Type A). A user is defined with the following (User A): Access to Bells Notes Associated practitioner Access to the 'Progress Notes' widget on the HomeView. A client is enrolled in an existing episode (Client A). Steps Log into Bells Notes with existing login credentials for "User A". Search for "Client A". Click [Start Note] and verify the existence of the 'Session Information' window. Fill out all required fields and select "Note Type A". Verify the existence of "Client A" in the client header when note is started. Fill out all required fields. Enter multiple session start/end times. 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". Select "Client A" and navigate to the 'Progress Notes' widget. Validate the progress note filed from Bells Notes is displayed. Validate the multiple session start/end times filed from Bells are displayed as expected with the proper duration. Bells Notes Integration - Progress Note document images Scenario 1: Bells Notes Integration - Validate self approval of progress notes from Bells 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. Must have a note type in Bells for the 'Progress Notes (Group and Individual)' form (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. 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 not displayed for the note sent via Bells Notes since "User A" does not require an approver. Select "Client A" and navigate to the 'Progress Notes' widget. Validate the progress note filed from Bells Notes is displayed. Access the 'Clinical Document Viewer' form. Select "Client" in the 'Select Type' field. Select "Individual" in the 'Select All or Individual Client' field. Select "Client A" in the 'Select Client' field. Select "All" in the 'Episode' field. Click [Process]. Validate a document is displayed for the progress note filed from Bells Notes. Select the document and click [View]. Validate the PDF generated from Bells Notes is displayed with the note details. Click [Close All Documents], [Search], and [Close].	Topics • Progress Notes • CareFabric • Bells Notes
Update 18 Summary \| Details Avatar CareFabric - 'SearchCarePlan' SDK action Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following: Treatment Plan CareFabric Monitor Scenario 1: Treatment Plan - validate the 'SearchCarePlan' SDK action Steps Internal testing only. Avatar CareFabric - 'SearchStaffMember' SDK action Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following: Practitioner Enrollment CareFabric Monitor Practitioner Termination Scenario 1: Validate the 'SearchStaffMember' SDK action Steps Internal testing only.	Topics • Treatment Plan • CareFabric • SearchStaffMember
2023 Update 54 Summary \| Details Avatar CareFabric - TeleHealth Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following: CareFabric Monitor Update Client Data Scenario 1: CareFabric Management - Validate the 'Resend' section Steps Internal testing only.	Topics • Telehealth
2023 Update 61 Summary \| Details Avatar Carefabric - Medication Inventory Management Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following: 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
2023 Update 68 Summary \| Details Avatar CareFabric - Support for other products and modules Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following: Enrollment Diagnosis CareFabric Monitor Update Client Data Back Dated Admission/Discharge Discharge Leaves Pre Admit Pre Admit Discharge Delete Service Change Program/Admission Date Site Specific Section Modeling (CWS) Scenario 1: Update Client Data - Validate the 'EncounterResourceUpdated' SDK event Specific Setup: A client is enrolled in an existing episode (Client A). Steps Select "Client A" and access the 'Update Client Data' form. Enter the desired value in the 'Facility Chart Number' field. Click [Submit]. Access the 'CareFabric Monitor' form. Enter the current date in the 'From Date' and 'Through Date' fields. Select "Client A" in the 'Client ID' field. Click [View Activity Log]. Validate the 'CareFabric Monitor Report' is displayed and contains an "EncounterResourceUpdated" record. Please note: this may be an "EncounterResourceCreated" record if a "Created" message has not yet been triggered for the client. In addition, it may take a few minutes for the event record to display on the report. Click [Click To View Record]. Validate the second 'fhirIdentifiers' - 'id' - 'value' field contains the 'Facility Chart Number' filed in the previous steps. Validate the second 'fhirIdentifiers' - 'type' - 'codings' - 'code' field contains "MR". Validate the second 'fhirIdentifiers' - 'text' - 'value' field contains "PATIENT_REGISTRATION_ID". Close the report and the form. Scenario 2: Admission - Validate the 'EncounterResourceCreated' SDK event Steps Access the 'Admission' form. Add an admission for a new client. This will be referred to as "Client A". Enter the desired date in the 'Preadmit/Admission Date' field. Enter the desired time in the 'Preadmit/Admission Time' field. Select the desired value in the 'Program' field. Select the desired practitioner in the 'Admitting Practitioner' field. Populate all other required and desired fields. Click [Submit]. Access the 'CareFabric Monitor' form. Enter the current date in the 'From Date' and 'Through Date' fields. Select "Client A" in the 'Client ID' field. Click [View Activity Log]. Validate the 'CareFabric Monitor Report' is displayed and contains an "EncounterResourceCreated" record. Please note: it may take a few minutes for the event record to display on the report. Validate the 'fhirIdentifiers' - 'id' - 'value' field contains the PATID for "Client A". Validate the 'period' - 'fromDate' field contains the 'Preadmit/Admission Date' and 'Preadmit/Admission Time' filed in the previous steps. Validate the first 'statusCode' - 'code' field contains "active". Validate the 'participants' - 'individualPractitionerResourceID' - 'id' field contains the ID for the 'Admitting Practitioner' filed in the previous steps. Validate the 'participants' - 'typeCodes' - 'codes' - 'code' field contains "ADMPHYS". Validate the 'participants' - 'typeCodes' - 'displayName' field contains "Admitting Physician". Validate the second 'statusCode' - 'code' field contains "planned". Close the report and the form. Scenario 3: Admission (Outpatient) - Validate the 'EncounterResourceCreated' SDK event Steps Access the 'Admission (OutPatient)' form. Add an admission for a new client. This will be referred to as "Client A". Enter the desired date in the 'Preadmit/Admission Date' field. Enter the desired time in the 'Preadmit/Admission Time' field. Select the desired value in the 'Program' field. Select the desired practitioner in the 'Admitting Practitioner' field. Populate all other required and desired fields. Click [Submit]. Access the 'CareFabric Monitor' form. Enter the current date in the 'From Date' and 'Through Date' fields. Select "Client A" in the 'Client ID' field. Click [View Activity Log]. Validate the 'CareFabric Monitor Report' is displayed and contains an "EncounterResourceCreated" record. Please note: it may take a few minutes for the event record to display on the report. Validate the 'fhirIdentifiers' - 'id' - 'value' field contains the PATID for "Client A". Validate the 'period' - 'fromDate' field contains the 'Preadmit/Admission Date' and 'Preadmit/Admission Time' filed in the previous steps. Validate the 'statusCode' - 'code' field contains "active". Validate the 'participants' - 'individualPractitionerResourceID' - 'id' field contains the ID for the 'Admitting Practitioner' filed in the previous steps. Validate the 'participants' - 'typeCodes' - 'codes' - 'code' field contains "ADMPHYS". Validate the 'participants' - 'typeCodes' - 'displayName' field contains "Admitting Physician". Validate the 'statusCode' - 'code' field contains "planned". Close the report and the form. Scenario 4: Back Dated Admission/Discharge - Validate the 'EncounterResourceCreated' SDK event Specific Setup: A client is enrolled in an existing episode (Client A). Steps Select "Client A" and access the 'Back Dated Admission/Discharge' form. Enter the desired date in the 'Preadmit/Admission Date' field. Enter the desired time in the 'Preadmit/Admission Time' field. Select the desired value in the 'Program' field. Select the desired value in the 'Type Of Admission' field. Select the desired practitioner in the 'Admitting Practitioner' field. Enter the desired date in the 'Date Of Discharge' field. Enter the desired time in the 'Discharge Time' field. Select the desired value in the 'Type Of Discharge' field. Select the desired practitioner in the 'Discharge Practitioner' field. Populate any other desired fields. Click [Submit]. Access the 'CareFabric Monitor' form. Enter the current date in the 'From Date' and 'Through Date' fields. Select "Client A" in the 'Client ID' field. Click [View Activity Log]. Validate the 'CareFabric Monitor Report' is displayed and contains an "EncounterResourceCreated" record. Please note: it may take a few minutes for the event record to display on the report. Validate the 'fhirIdentifiers' - 'id' - 'value' field contains the PATID for "Client A". Validate the 'period' - 'fromDate' field contains the 'Preadmit/Admission Date' and 'Preadmit/Admission Time' filed in the previous steps. Validate the 'period' - 'toDate' field contains the 'Date of Discharge' and 'Discharge Time' filed in the previous steps. Validate the first 'statusCode' - 'code' field contains "active". Validate the second 'statusCode' - 'code' field contains "discharged". Close the report and the form. Scenario 5: Discharge - Validate the 'EncounterResourceUpdated' SDK event Specific Setup: A client is enrolled in an existing episode (Client A). Steps Select "Client A" and access the 'Discharge' form. Enter the desired date in the 'Date of Discharge' field. Enter the desired time in the 'Discharge Time' field. Select the desired value in the 'Type Of Discharge' field. Select the desired practitioner in the 'Discharge Practitioner' field. Populate any other required fields. Click [Submit]. Access the 'CareFabric Monitor' form. Enter the current date in the 'From Date' and 'Through Date' fields. Select "Client A" in the 'Client ID' field. Click [View Activity Log]. Validate the 'CareFabric Monitor Report' is displayed and contains an "EncounterResourceUpdated" record. Please note: this may be an "EncounterResourceCreated" record if a "Created" message has not yet been triggered for the client. In addition, it may take a few minutes for the event record to display on the report. Validate the 'fhirIdentifiers' - 'id' - 'value' field contains the PATID for "Client A". Validate the 'period' - 'fromDate' field contains the 'Preadmit/Admission Date' and 'Preadmit/Admission Time' filed via Admission. Validate the 'period' - 'toDate' field contains the 'Date of Discharge' and 'Discharge Time' filed in the previous steps. Validate the first 'statusCode' - 'code' field contains "active". Validate the second 'statusCode' - 'code' field contains "discharged". Close the report and the form. Scenario 6: Leaves - Validate the 'EncounterResourceUpdated' SDK event Specific Setup: A client is enrolled in an existing inpatient episode (Client A). Steps Select "Client A" and access the 'Leaves' form. Enter the desired date in the 'Leave Date' field. Enter the desired time in the 'Leave Time' field. Select the desired value in the 'Type Of Leave From' field. Select the desired value in the 'Reason For Leave' field. Populate any other desired fields. Click [Submit]. Access the 'CareFabric Monitor' form. Enter the current date in the 'From Date' and 'Through Date' fields. Select "Client A" in the 'Client ID' field. Click [View Activity Log]. Validate the 'CareFabric Monitor Report' is displayed and contains an "EncounterResourceUpdated" record. Please note: this may be an "EncounterResourceCreated" record if a "Created" message has not yet been triggered for the client. In addition, it may take a few minutes for the event record to display on the report. Click [Click To View Record]. Validate the second 'statusCode' - 'code' field contains "on-hold". Close the report and the form. Scenario 7: Return From Leave - Validate the 'EncounterResourceUpdated' SDK event Specific Setup: A client is enrolled in an existing inpatient episode (Client A). Steps Select "Client A" and access the 'Leaves' form. Enter the desired date in the 'Leave Date' field. Enter the desired time in the 'Leave Time' field. Select the desired value in the 'Type Of Leave From' field. Select the desired value in the 'Reason For Leave' field. Populate any other desired fields. Click [Submit]. Access the 'CareFabric Monitor' form. Enter the current date in the 'From Date' and 'Through Date' fields. Select "Client A" in the 'Client ID' field. Click [View Activity Log]. Validate the 'CareFabric Monitor Report' is displayed and contains an "EncounterResourceUpdated" record. Please note: this may be an "EncounterResourceCreated" record if a "Created" message has not yet been triggered for the client. In addition, it may take a few minutes for the event record to display on the report. Click [Click To View Record]. Validate the second 'statusCode' - 'code' field contains "on-hold". Close the report and the form. Select "Client A" and access the 'Return From Leaves' form. Enter the desired date in the 'Return Date' field. Enter the desired time in the 'Return Time' field. Select the desired value in the 'Reason For Close Of Leave' field. Populate any other desired fields. Click [Submit]. Access the 'CareFabric Monitor' form. Enter the current date in the 'From Date' and 'Through Date' fields. Select "Client A" in the 'Client ID' field. Click [View Activity Log]. Validate the 'CareFabric Monitor Report' is displayed and contains an "EncounterResourceUpdated" record. Please note: it may take a few minutes for the event record to display on the report. Click [Click To View Record]. Validate the second 'statusCode' - 'code' field contains "planned". Close the report and the form. Scenario 8: Pre Admit - Validate the 'EncounterResourceCreated' SDK event Steps Access the 'Pre Admit' form. Add a pre-admission for a new client. This will be referred to as "Client A". Enter the desired date in the 'Preadmit/Admission Date' field. Enter the desired time in the 'Preadmit/Admission Time' field. Select the desired value in the 'Program' field. Select the desired practitioner in the 'Admitting Practitioner' field. Populate all other required and desired fields. Click [Submit]. Access the 'CareFabric Monitor' form. Enter the current date in the 'From Date' and 'Through Date' fields. Select "Client A" in the 'Client ID' field. Click [View Activity Log]. Validate the 'CareFabric Monitor Report' is displayed and contains an "EncounterResourceCreated" record. Please note: it may take a few minutes for the event record to display on the report. Validate the 'fhirIdentifiers' - 'id' - 'value' field contains the PATID for "Client A". Validate the 'period' - 'fromDate' field contains the 'Preadmit/Admission Date' and 'Preadmit/Admission Time' filed in the previous steps. Validate the first 'statusCode' - 'code' field contains "active". Validate the 'participants' - 'individualPractitionerResourceID' - 'id' field contains the ID for the 'Admitting Practitioner' filed in the previous steps. Validate the 'participants' - 'typeCodes' - 'codes' - 'code' field contains "ADMPHYS". Validate the 'participants' - 'typeCodes' - 'displayName' field contains "Admitting Physician". Validate the second 'statusCode' - 'code' field contains "planned". Close the report and the form. Scenario 9: Pre Admit Discharge - Validate the 'EncounterResourceUpdated' SDK event Specific Setup: A client is enrolled in an existing Pre Admit program (Client A). Steps Select "Client A" and access the 'Pre Admit Discharge' form. Enter the desired date in the 'Date of Discharge' field. Enter the desired time in the 'Discharge Time' field. Select the desired value in the 'Type Of Discharge' field. Select the desired practitioner in the 'Discharge Practitioner' field. Populate any other required fields. Click [Submit]. Access the 'CareFabric Monitor' form. Enter the current date in the 'From Date' and 'Through Date' fields. Select "Client A" in the 'Client ID' field. Click [View Activity Log]. Validate the 'CareFabric Monitor Report' is displayed and contains an "EncounterResourceUpdated" record. Please note: this may be an "EncounterResourceCreated" record if a "Created" message has not yet been triggered for the client. In addition, it may take a few minutes for the event record to display on the report. Validate the 'fhirIdentifiers' - 'id' - 'value' field contains the PATID for "Client A". Validate the 'period' - 'fromDate' field contains the 'Preadmit/Admission Date' and 'Preadmit/Admission Time' filed via Pre-Admission. Validate the 'period' - 'toDate' field contains the 'Date of Discharge' and 'Discharge Time' filed in the previous steps. Validate the first 'statusCode' - 'code' field contains "active". Validate the second 'statusCode' - 'code' field contains "discharged". Close the report and the form. Scenario 10: Diagnosis - Validate the 'EncounterResourceUpdated' SDK event Specific Setup: A client is enrolled in an existing episode (Client A). Steps Select "Client A" and access the 'Diagnosis' form. Select "Admission" in the 'Type Of Diagnosis' field. Validate the 'Date Of Diagnosis' field contains the date of admission for "Client A". Enter the desired time in the 'Time Of Diagnosis' field. Click [New Row]. Search for and select the desired value in the 'Diagnosis Search' field. Validate "Primary" is selected in the 'Ranking' field. Select the desired practitioner in the 'Diagnosing Practitioner' field. Populate any other desired fields. Click [Submit]. Access the 'CareFabric Monitor' form. Enter the current date in the 'From Date' and 'Through Date' fields. Select "Client A" in the 'Client ID' field. Click [View Activity Log]. Validate the 'CareFabric Monitor Report' is displayed and contains an "EncounterResourceUpdated" record. Please note: this may be an "EncounterResourceCreated" record if a "Created" message has not yet been triggered for the client. In addition, it may take a few minutes for the event record to display on the report. Click [Click To View Record]. Validate the 'diagnoses' - 'conditionResourceID' - 'id' field contains a unique identifier for the diagnosis filed in the previous steps. Validate the 'diagnoses' - 'rank' field contains "1". Validate the 'diagnoses' - 'useCode' - 'codes' - 'code' field contains "AD". Validate the 'diagnoses' - 'useCode' -' displayName' field contains "Admission Diagnosis". Close the report and the form. Scenario 11: Client Charge Input - Validate the 'EncounterResourceCreated' SDK event Specific Setup: A client is enrolled in an existing episode (Client A). Steps Access the 'Client Charge Input' form. Enter the desired date in the 'Date Of Service' field. Enter the desired time in the 'Service Start Time' and 'Service End Time' fields. Select "Client A" in the 'Client ID' field. Select the desired value in the 'Episode Number' field. Select the desired value in the 'Service Codes' field. Select the desired practitioner in the 'Practitioner' field. Select the desired value in the 'Location' field. Click [Submit] and [No]. Access the 'CareFabric Monitor' form. Enter the current date in the 'From Date' and 'Through Date' fields. Select "Client A" in the 'Client ID' field. Click [View Activity Log]. Validate the 'CareFabric Monitor Report' is displayed and contains an "EncounterResourceCreated" record. Please note: it may take a few minutes for the event record to display on the report. Click [Click To View Record]. Validate the 'period' - 'fromDate' field contains the 'Date Of Service' and the 'Service Start Time' filed in the previous steps. Validate the 'period' - 'toDate' field contains the 'Date Of Service' and the 'Service End Time' filed in the previous steps. Validate the first 'statusCode' - 'code' field contains "active". Validate the 'participants' - 'individualPractitionerResourceID' - 'id' field contains the ID associated to the 'Practitioner' filed in the previous steps. Validate the 'participants' - 'typeCodes' - 'codes' - 'code' field contains "PPRF". Validate the 'participants' - 'typeCodes' - 'displayName' field contains "Primary Performer". Validate the second 'statusCode' - 'code' field contains "in-progress". Close the report and the form. Scenario 12: Edit Service Information - Validate the 'EncounterResourceCreated' and 'EncounterResourceUpdated' SDK events Specific Setup: A client is enrolled in an existing episode (Client A). Steps Access the 'Client Charge Input' form. Enter the desired date in the 'Date Of Service' field. Enter the desired time in the 'Service Start Time' and 'Service End Time' fields. Select "Client A" in the 'Client ID' field. Select the desired value in the 'Episode Number' field. Select the desired value in the 'Service Codes' field. Select the desired practitioner in the 'Practitioner' field. Select the desired value in the 'Location' field. Click [Submit] and [No]. Access the 'CareFabric Monitor' form. Enter the current date in the 'From Date' and 'Through Date' fields. Select "Client A" in the 'Client ID' field. Click [View Activity Log]. Validate the 'CareFabric Monitor Report' is displayed and contains an "EncounterResourceCreated" record. Please note: it may take a few minutes for the event record to display on the report. Click [Click To View Record]. Validate the 'period' - 'fromDate' field contains the 'Date Of Service' and the 'Service Start Time' filed in the previous steps. Validate the 'period' - 'toDate' field contains the 'Date Of Service' and the 'Service End Time' filed in the previous steps. Validate the first 'statusCode' - 'code' field contains "active". Validate the 'participants' - 'individualPractitionerResourceID' - 'id' field contains the ID associated to the 'Practitioner' filed in the previous steps. Validate the 'participants' - 'typeCodes' - 'codes' - 'code' field contains "PPRF". Validate the 'participants' - 'typeCodes' - 'displayName' field contains "Primary Performer". Validate the second 'statusCode' - 'code' field contains "in-progress". Close the report and the form. Access the 'Edit Service Information' form. Select "Client A" in the 'Client ID' field. Select the desired episode in the 'Select Episode' field. Click [Select Services To Edit]. Select the service filed in the previous steps and click [OK]. Validate all previously populated data is displayed for the service. Edit the 'Service Start Time' and 'Service End Time' fields to be any new value. Click [Submit] and close the form. Access the 'CareFabric Monitor' form. Enter the current date in the 'From Date' and 'Through Date' fields. Select "Client A" in the 'Client ID' field. Click [View Activity Log]. Validate the 'CareFabric Monitor Report' is displayed and contains both "EncounterResourceCreated" and "EncounterResourceUpdated" records. Please note: it may take a few minutes for the event records to display on the report. Click [Click To View Record] for the "EncounterResourceUpdated" record. Validate the 'period' - 'fromDate' field contains the 'Date Of Service' and the 'Service Start Time' filed via 'Client Charge Input'. Validate the 'period' - 'toDate' field contains the 'Date Of Service' and the 'Service End Time' filed via 'Client Charge Input'. Validate the second 'statusCode' - 'code' field contains "cancelled". Navigate back to the 'CareFabric Monitor Report'. Click [Click To View Record] for the "EncounterResourceCreated" record. Validate the 'period' - 'fromDate' field contains the 'Date Of Service' and the 'Service Start Time' filed via 'Edit Service Information'. Validate the 'period' - 'toDate' field contains the 'Date Of Service' and the 'Service End Time' filed via 'Edit Service Information'. Validate the second 'statusCode' - 'code' field contains "in-progress". Close the report and the form. Scenario 13: Delete Service - Validate the 'EncounterResourceUpdated' SDK event Specific Setup: A client is enrolled in an existing episode (Client A). Steps Access the 'Client Charge Input' form. Enter the desired date in the 'Date Of Service' field. Enter the desired time in the 'Service Start Time' and 'Service End Time' fields. Select "Client A" in the 'Client ID' field. Select the desired value in the 'Episode Number' field. Select the desired value in the 'Service Codes' field. Select the desired practitioner in the 'Practitioner' field. Select the desired value in the 'Location' field. Click [Submit] and [No]. Access the 'CareFabric Monitor' form. Enter the current date in the 'From Date' and 'Through Date' fields. Select "Client A" in the 'Client ID' field. Click [View Activity Log]. Validate the 'CareFabric Monitor Report' is displayed and contains an "EncounterResourceCreated" record. Please note: it may take a few minutes for the event record to display on the report. Click [Click To View Record]. Validate the second 'statusCode' - 'code' field contains "in-progress". Close the report and the form. Access the 'Delete Service' form. Select "Client A" in the 'Client ID' field. Enter the desired date in the 'Start Date' and 'End Date' fields. Click [Display Client]. Select the desired service and click [OK]. Click [Delete], [OK], and [Yes]. Validate a message is displayed stating: Deleted. Click [OK] and close the form. Access the 'CareFabric Monitor' form. Enter the current date in the 'From Date' and 'Through Date' fields. Select "Client A" in the 'Client ID' field. Click [View Activity Log]. Validate the 'CareFabric Monitor Report' is displayed and contains an "EncounterResourceUpdated" record. Please note: it may take a few minutes for the event record to display on the report. Click [Click To View Record]. Validate the second 'statusCode' - 'code' field contains "cancelled". Close the report and the form. Scenario 14: Change Program/Admission Date - Validate the 'EncounterResourceUpdated' SDK event Specific Setup: A client is enrolled in an existing episode (Client A). Steps Access the 'Change Program/Admission Date' form. Select "Client A" in the 'Client ID' field. Select the desired episode in the 'Select Episode' field. Enter any new value in the 'New Admission Date' and 'New Admission Time' fields. Click [Submit] and close the form. Access the 'CareFabric Monitor' form. Enter the current date in the 'From Date' and 'Through Date' fields. Select "Client A" in the 'Client ID' field. Click [View Activity Log]. Validate the 'CareFabric Monitor Report' is displayed and contains an "EncounterResourceUpdated" record. Please note: this may be an "EncounterResourceCreated" record if a "Created" message has not yet been triggered for the client. In addition, it may take a few minutes for the event record to display on the report. Validate the 'period' - 'fromDate' field contains the 'New Admission Date' and 'New Admission Time' filed in the previous steps. Close the report and the form. Scenario 15: Progress Notes - Validate the 'EncounterResourceUpdated' SDK event Specific Setup: A client is enrolled in an existing episode (Client A). The 'Progress Notes (Group and Individual)' form must have a 'SS Note Staff Member' field enabled in 'Site Specific Section Modeling' with "Assign as Primary Care Provider" selected in the 'Product Custom Logic Definition' field. This field will be referred to as the 'Assign as Primary Care Provider' field. 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. Select the desired value in the 'Note Type' field. Enter the desired value in the 'Notes Field'. Select the desired practitioner in the 'Assign as Primary Care Provider' field. Select "Final" in the 'Draft/Final' field. File the note. Access Crystal Reports or other SQL Reporting tool. Select the PM namespace. Create a report using the 'SYSTEM.client_practitioner_assignment' SQL table. Validate a row is displayed for the note finalized in the previous steps with PCL. Validate the 'PATID' field contains the client ID for "Client A". Validate the 'practitioner' field contains the ID for the practitioner selected in the previous steps. Validate the 'date_of_assignment' and 'time_of_assignment' fields contain the date/time the note was filed. Close the report. Access the 'CareFabric Monitor' form. Enter the current date in the 'From Date' and 'Through Date' fields. Select "Client A" in the 'Client ID' field. Click [View Activity Log]. Validate the 'CareFabric Monitor Report' is displayed and contains an "EncounterResourceUpdated" record. Please note: this may be an "EncounterResourceCreated" record if a "Created" message has not yet been triggered for the client. In addition, it may take a few minutes for the event record to display on the report. Click [Click To View Record]. Validate the last 'individualPractitionerResourceID' - 'id' field contains the ID for the practitioner selected in the previous steps. Validate the last 'period' - 'fromDate' field contains the date/time the note was filed, which can be found in the 'SYSTEM.client_practitioner_assignment' SQL table. Validate the last 'typeCodes' - 'codes' - 'code' field contains "PCP". Validate the last 'typeCodes' - 'codes' - 'displayName' field contains "Primary Care Physician". Close the report and the form.	Topics • Diagnosis • CareFabric • Update Client Data • Admission • CareFabric Monitor • Discharge • Leaves • Client Charge Input • Progress Notes
2023 Update 71 Summary \| Details Bells Notes Integration - Patient Signatures Scenario 1: Bells Notes Integration - Validate sending progress notes with signatures when document routing is enabled 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 be configured for Bells Notes with the following: Document routing enabled 3 signature fields added via 'Site Specific Section Modeling' that are imported to a corresponding note type in Bells (Note Type A). Patient Signature Guardian Signature Other Signature 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. Add signatures in the 'Patient Signature', 'Guardian Signature' and 'Other Signature' fields. Click [Sign Note]. Validate the Sign Note' dialog is displayed. Enter the pin for "User A" in the 'Pin' field and click [Sign]. Validate a message is displayed stating: Note Signed Successfully. Log into myAvatar as "User A". Navigate to the "My To Do's" widget. Validate a To-Do is displayed for the progress note sent via Bells Notes for "Client A". Click [Approve Document]. Validate the progress note data is displayed, including the 'Patient Signature', 'Guardian Signature' and 'Other Signature' fields. 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 all progress note data is displayed as expected, including the 'Patient Signature', 'Guardian Signature', and 'Other Signature' fields. Scenario 2: Bells Notes Integration - Validate sending progress notes with signatures when document routing is disabled Specific Setup: myAvatar must be configured to integrate with Bells Notes. Please note: this must be done by a Netsmart Associate. The 'Progress Notes (Group and Individual)' form must be configured for Bells Notes with the following: Document routing is disabled 3 signature fields added via 'Site Specific Section Modeling' that are imported to a corresponding note type in Bells (Note Type A). Patient Signature Guardian Signature Other Signature A user is defined with the following (User A): Access to Bells Notes Associated practitioner Access to the 'Progress Notes' widget on the HomeView. A client is enrolled in an existing episode (Client A). Steps Log into Bells Notes with existing login credentials for "User A". Search for "Client A". Click [Start Note] and verify the existence of the 'Session Information' window. Fill out all required fields and select "Note Type A". Verify the existence of "Client A" in the client header when note is started. Fill out all required fields. Add signatures in the 'Patient Signature', 'Guardian Signature' and 'Other Signature' fields. Click [Sign Note]. Validate the Sign Note' dialog is displayed. Enter the pin for "User A" in the 'Pin' field and click [Sign]. Validate a message is displayed stating: Note Signed Successfully. Select "Client A" and navigate to the 'Progress Notes' widget. Validate the progress note filed from Bells Notes is displayed. Validate all progress note data is displayed as expected, including the 'Patient Signature', 'Guardian Signature', and 'Other Signature' fields. Scenario 3: Bells Notes Integration - Reject a progress note that was sent for approval 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 be configured for Bells Notes with the following: Document routing enabled 3 signature fields added via 'Site Specific Section Modeling' that are imported to a corresponding note type in Bells (Note Type A). Patient Signature Guardian Signature Other Signature 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. Add signatures in the 'Patient Signature', 'Guardian Signature' and 'Other Signature' fields. Click [Sign Note]. Validate the Sign Note' dialog is displayed. Enter the pin for "User A" in the 'Pin' field and click [Sign]. Validate a message is displayed stating: Note Signed Successfully. Log into myAvatar as "User A". Navigate to the "My To Do's" widget. Validate a To-Do is displayed for the progress note sent via Bells Notes for "Client A". Click [Approve Document]. Validate the progress note data is displayed, including the 'Patient Signature', 'Guardian Signature' and 'Other Signature' fields. Click [Reject]. Enter the desired value in the 'Comments for Reject' field and click [OK]. Access the 'Progress Notes (Group and Individual)' form. Select "Client A" in the 'Select Client' field. Select the corresponding episode in the 'Select Episode' field. Select the note rejected in the previous steps in the 'Select Draft Note To Edit' field. Validate the note details sent from Bells Notes are displayed including the signature for 'Patient Signature', 'Guardian Signature', and 'Other Signature'. Validate "Draft" is selected in the 'Draft/Final' field. Close the form. Bells Notes Integration - Site Specific fields Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following: Site Specific Section Modeling (CWS) Scenario 1: Validate the 'GetProgressNoteCustomDisplayPlan' SDK action Steps Internal testing only. Avatar CareFabric - 'StaffMemberUpdated' SDK event Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following: Practitioner Enrollment CareFabric Monitor Practitioner Termination Scenario 1: Practitioner Enrollment/Termination - Validate the 'StaffMemberUpdated' SDK event when a practitioner is terminated and then re-enrolled Specific Setup: An active practitioner must be defined in 'Practitioner Enrollment' (Practitioner A). Steps Access the 'Practitioner Termination' form. Select "Practitioner A" in the 'Select Staff' dialog and click [OK]. Enter any past date in the 'Termination Date' field. Select the desired value in the 'Reason For Termination' field. Click [Submit]. Access the 'CareFabric Monitor' form. Enter the current date in the 'From Date' and 'Through Date' fields. Select "Practitioner A" in the 'Staff ID' field. Click [View Activity Log]. Validate the 'CareFabric Monitor Report' is displayed and contains a "StaffMemberUpdated" record. Select it and click [Click To View Record]. Validate the 'terminatedDate' field contains the 'Termination Date' filed in the previous steps. Close the report and the form. Access the 'Practitioner Enrollment' form. Select "Practitioner A" in the 'Select Staff' dialog and click [OK]. Enter the current date in the 'Registration Date' field. Select the "Categories/Taxonomy" section. Select "Create New" in the 'Category/Taxonomy' field. Enter the current date in the 'Effective Date' field. Select the desired value in the 'Practitioner Category' field. Select the desired value in the 'Discipline' field. Select the desired value in the 'Practitioner Categories For Coverage' field. Click [Add Practitioner Categories] and [OK]. Submit the form. Access the 'CareFabric Monitor' form. Enter the current date in the 'From Date' and 'Through Date' fields. Select "Practitioner A" in the 'Staff ID' field. Click [View Activity Log]. Validate the 'CareFabric Monitor Report' is displayed and contains a "StaffMemberUpdated" record. Select it and click [Click To View Record]. Validate the 'activatedDate' field contains the current date. Validate the 'terminationDate' field contains "null". Close the report and the form. CareManager Integration - Progress Notes Scenario 1: CareManager - Validate the 'PutProgressNote' action when document routing is enabled Specific Setup: myAvatar must be configured to integrate with CareManager. Please note: this must be done by a Netsmart Associate. A progress notes form must be configured for CareManager integration. Document routing is enabled on this progress notes form. A practitioner (Practitioner A) must exist in both myAvatar and CareManager that is associated to an Avatar user (User A). This user does not require a supervisor's approval for document routing. A client is enrolled in an existing episode in myAvatar and CareManager (Client A). Steps Log into CareManager. Search for and select "Client A". File a progress note for a "New Service", populating all required and desired fields. Select "Practitioner A" as the 'Practitioner'. Enter the desired value for the 'Duration'. Select "Final" as the 'Note Status'. Click [Save]. Log into myAvatar as "User A". Navigate to the "My To Do's" widget. Locate the To Do just routed and click [Approve Document]. Validate the document is displayed with the progress note data sent from CareManager. Click [Accept]. Enter the password for "User A" in the 'Verify Password' dialog and click [OK]. Validate the To-Do is no longer displayed. Select "Client A" and navigate to the 'Progress Notes' widget. Validate the 'Progress Notes' widget contains the finalized progress note submitted from CareManager. Validate all progress note data displays as expected. Scenario 2: CareManager - Validate the 'PutProgressNote' action when document routing is disabled Specific Setup: myAvatar must be configured to integrate with CareManager. Please note: this must be done by a Netsmart Associate. A progress notes form must be configured for CareManager integration. Document routing is disabled on this progress notes form. A practitioner (Practitioner A) must exist in both myAvatar and CareManager that is associated to an Avatar user (User A). A client is enrolled in an existing episode in myAvatar and CareManager (Client A). Steps Log into CareManager. Search for and select "Client A". File a progress note for a "New Service", populating all required and desired fields. Select "Practitioner A" as the 'Practitioner'. Enter the desired value for the 'Duration'. Select "Final" as the 'Note Status'. Click [Save]. Log into myAvatar as "User A". Select "Client A" and navigate to the 'Progress Notes' widget. Validate the 'Progress Notes' widget contains the finalized progress note submitted from CareManager. Validate all progress note data displays as expected.	Topics • Progress Notes • Bells Notes • Site Specific Section Modeling • CareFabric • Practitioner
2023 Update 72 Summary \| Details TeleHealth - Email Validation Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following: CareFabric Monitor Update Client Data Scenario 1: Email validations in the 'TeleHealthAppointmentCreated' and 'TeleHealthAppointmentUpdated' SDK events Specific Setup: A service code must be defined as a "Telehealth Service" in the 'Service Codes' form. A client is enrolled in an existing episode and has a phone number and email filed (Client A). A user is defined in 'User Definition' that has the following: "TeleHealth" selected in the 'Netsmart Mobile App Access' field, "System Admin" selected in the 'Netsmart Mobile App User Role' field, an email filed in the 'Organizational Email Address' field, and an associated staff member that has hours for scheduling. Steps Select "Client A" and access the 'Update Client Data' form. Enter any invalid email format in the 'Email Address' field (Ex: TEST). Criteria for a valid email includes the following: There is an @ There is a value before the @ There is an address after the @ There is a . in the address Click [Submit]. Access the 'Scheduling Calendar' form. Right click in the 'Appointment Grid' and click [Add Appointment]. Enter the TeleHealth Service Code in the 'Service Code' field. Enter "Client A" in the 'Client' field. Populate all required and desired fields. Click [Submit]. Validate the 'Appointment Grid' contains the new appointment. Click [Dismiss]. Access the 'CareFabric Monitor' form. Enter the current date in the 'From Date' and 'Through Date' fields. Enter "TeleHealthAppointmentCreated" in the 'Event/Action Search' field. Click [View Activity Log]. Validate the 'CareFabric Monitor Report' field contains a "TeleHealthAppointmentCreated" record. Click [Click To View Record]. Validate the 'participants' - 'email' field contains "null" because the email address on file is invalid. Close the report and the form. Select "Client A" and access the 'Update Client Data' form. Enter any valid email format in the 'Email Address' field (Ex: Test@test.com) Click [Submit]. Access the 'CareFabric Monitor' form. Enter the current date in the 'From Date' and 'Through Date' fields. Enter "TeleHealthAppointmentUpdated" in the 'Event/Action Search' field. Click [View Activity Log]. Validate the 'CareFabric Monitor Report' contains a "TeleHealthAppointmentUpdated" record. Updating the email address in 'Update Client Data' will trigger this message. Click [Click To View Record]. Validate the 'participants' - 'email' field contains the value filed in the previous steps (Ex. Test@test.com). Close the report and the form. TeleHealth - Recurring Appointments Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following: CareFabric Monitor Update Client Data Group Registration Scheduling Calendar - Add/Remove Group Members Registry Settings (PM) Scenario 1: Schedule recurring TeleHealth appointment with a TeleHealth service code and validate the TeleHealthAppointmentCreated/Updated/Deleted SDK events Specific Setup: A service code must be defined as a "Telehealth Service" in the 'Service Codes' form. Using the "Admission" form" Admit a new client into any episode. Navigate to the "Demographics" section. Enter a home address, city, state and zip. Enter an email address. Enter a home telephone number. Steps Open the "Scheduling Calendar" form. Schedule a recurring appointment TeleHealth service using a TeleHealth service code. Open the "CareFabric Monitor" form: Run the Activity Log for the following events "TeleHealthAppointmentCreated". Validate that a "TeleHealthAppointmentCreated" event is generated for however many appointments are in the recurrence. Validate that each "TeleHealthAppointmentCreated" event includes the following: Validate the "isReoccuringAppointment" property is "true". Validate the event includes the "RecurrenceInfo" object. Validate the "appointmentDateRange" object. Ensure the date and time is accurate. Validate the "recurrenceInfo" - "startDate" field. Ensure the date is accurate. Return to the "Scheduling Calendar": Edit the recurring appointment that was created in previous steps. Change the duration of the service. Open the "CareFabric Monitor" form: Run the Activity Log for the following events "TeleHealthAppointmentUpdated". Validate that a "TeleHealthAppointmentUpdated" event is generated for however many appointments are in the recurrence. Validate that each "TeleHealthAppointmentUpdated" event includes the following: Validate the "isReoccuringAppointment" property is "true". Validate the event includes the "RecurrenceInfo" object. Validate the "appointmentDateRange" object. Ensure the date and time is accurate. Validate the "recurrenceInfo" - "startDate" field. Ensure the date is accurate. Return to the "Scheduling Calendar": Delete the recurring appointment that was created and edited in previous steps. Open the "CareFabric Monitor" form: Run the Activity Log for the following events "TeleHealthAppointmentDeleted". Validate that a "TeleHealthAppointmentDeleted" event is generated for however many appointments are in the recurrence. Validate that each "TeleHealthAppointmentDeleted" event includes the following: Validate the "isReoccuringAppointment" property is "true". Validate the event includes the "RecurrenceInfo" object. Scenario 2: Schedule recurring TeleHealth appointment with a TeleHealth location and validate the TeleHealthAppointmentCreated/Updated/Deleted SDK events Specific Setup: Using "Dictionary Update" form: Select the "Client" File. Select data element "(10006) Location". Select one active location and designate it as "Yes" for the extended dictionary data element (586) Is this a Telehealth location?". Using the "Registry Settings" form: Enable the registry setting "Enable Telehealth integration at the location level". Using the "Admission" form: Admit a new client into any episode. Navigate to the "Demographics" section. Enter a home address, city, state and zip. Enter an email address. Enter a home telephone number. Steps Open the "Scheduling Calendar" form: Schedule a recurring appointment TeleHealth service using a TeleHealth location. Open the "CareFabric Monitor" form: Run the Activity Log for the following events "TeleHealthAppointmentCreated". Validate that a "TeleHealthAppointmentCreated" event is generated for however many appointments are in the recurrence. Validate that each "TeleHealthAppointmentCreated" event includes the following: Validate the "isReoccuringAppointment" property is "true". Validate the event includes the "RecurrenceInfo" object. Validate the "appointmentDateRange" object. Ensure the date and time is accurate. Validate the "recurrenceInfo" - "startDate" field. Ensure the date is accurate. Return to the "Scheduling Calendar": Edit the recurring appointment that was created in previous steps. Change the duration of the service. Open the "CareFabric Monitor" form: Run the Activity Log for the following events "TeleHealthAppointmentUpdated". Validate that a "TeleHealthAppointmentUpdated" event is generated for however many appointments are in the recurrence. Validate that each "TeleHealthAppointmentUpdated" event includes the following: Validate the "isReoccuringAppointment" property is "true". Validate the event includes the "RecurrenceInfo" object. Validate the "appointmentDateRange" object. Ensure the date and time is accurate. Validate the "recurrenceInfo" - "startDate" field. Ensure the date is accurate. Return to the "Scheduling Calendar": Delete the recurring appointment that was created and edited in previous steps. Open the "CareFabric Monitor" form: Run the Activity Log for the following events "TeleHealthAppointmentDeleted". Validate that a "TeleHealthAppointmentDeleted" event is generated for however many appointments are in the recurrence. Validate that each "TeleHealthAppointmentDeleted" event includes the following: Validate the "isReoccuringAppointment" property is "true". Validate the event includes the "RecurrenceInfo" object.	Topics • Scheduling Calendar • Update Client Data • Telehealth • CareFabric Monitor
2023 Update 75 Summary \| Details Mobile CareGiver+ - Multiple Recipients Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following: CareFabric Monitor CarePOV Management Client Ledger Scheduling Calendar - Status Update Scenario 1: Mobile CareGiver + - Validate the 'McgEvvAppointmentUpdated' incoming event for multiple recipients Specific Setup: Avatar is configured to integrate with Mobile CareGiver+. Please note: This must be done by a Netsmart Representative. A product is defined in the 'CareFabric Integration Management' form for the "MobileCareGiver+" product and "McgEvvAppointmentUpdated" must be selected in the 'Event Types' field. A program is defined with a value populated in the 'EVV Provider Organization ID' field in the 'Program Maintenance' form (Program A). "Program A" has an associated location (Location A) with the following defined in 'Dictionary Update' for the "Client" file, "(10006 Location)" data element: Extended dictionary data element "(587) Place Of Service (Mobile CareGiver+)" must be set to "Home" (unless an alternate address is being used). If the above dictionary data element is not defined, then the extended dictionary data element "(579) Place Of Service (837 Electronic Billing)" will be used and must be set to "Home". If this dictionary data element is not defined, then "(578) Place Of Service (HCFA 24-B)" will be used and must be set to "Home". A service code must be defined that has "Yes" selected in the 'Does This Service Require Electronic Visit Verification' field in the 'Service Codes' form and must be assigned to "Program A" (Service Code A). This service code must also have a CPT-4/HCPCS code associated to it in the 'Service Fee/Cross Reference Maintenance' form (Procedure Code A). Must have a guarantor defined in the 'Guarantors/Payors' form (Guarantor A). A site is defined with hours for scheduling (Site A). The following must be set in the "Electronic Visit Verification" section of the 'CarePOV Management' form: "Yes" is selected in the 'Enable Mobile CareGiver+' field. "Yes" is selected in the 'Send Non EVV Payers' field. "No" is selected in the 'Require Authorization' field. "Guarantor A" has a row with all fields populated in the 'Payor Program ID' grid. "Site A" selected in the 'Site' field. "Yes" is selected in the following fields for the 'McgEvvAppointmentUpdated' event: 'Keep Incoming Payload in the Log', 'Keep Outgoing Payload in the Log' and 'Show in the CareFabric Monitor Report' in the 'CareFabric Management' form. This must be done by a Netsmart Representative. A practitioner must be defined as an EVV resource with hours for scheduling at "Site A" and has the following on file: 'Name', 'Date Of Birth', 'Cellular Telephone', 'Staff EVV ID', 'Email Address', and 'Staff EVV Type' (Practitioner A). Two clients are enrolled in "Program A" and have the following on file: 'Client Name', 'Address - Street', 'Zipcode', 'Cell Phone', 'Diagnosis', "Guarantor A" selected in 'Financial Eligibility' (Client A & Client B). Steps Add an unscheduled visit in the Mobile CareGiver+ application for multiple recipients (Client A & Client B) with "Practitioner A". Please note: if any of the appointment information sent from Mobile CareGiver+ can't be determined, the appointment will be available for reconciliation in the 'CareFabric Integration Reconciliation' form. Access the 'CareFabric Monitor' form. Enter the current date in the 'From Date' and 'Through Date' fields. Select "McgEvvAppointmentUpdated" in the 'Event/Action Search' field. Click [View Activity Log]. Validate the 'CareFabric Monitor Report' contains an "McgEvvAppointmentUpdated" record. Click [Click To View Record]. Validate the 'endDate' field contains the appointment end date/time. Validate the 'isMultipleRecipients' field contains "true". Validate the 'mcgAppointmentID' - 'id' field contains the MCG+ unique identifier for the appointment. Validate the 'resource' - 'resourceID' field contains "Practitioner A". Validate the first - 'services' - 'clientID- 'id' field contains "Client A". Validate the first 'services' - 'procedureCode' - 'code' field contains "Procedure Code A". Validate the second 'services' - 'clientID' - 'id' field contains "Client B". Validate the second 'services' - 'procedureCode' - 'code' field contains "Procedure Code A". Validate the 'startDate' field contains the appointment start date/time. Validate all other appointment data is displayed. Close the report and the form. Access the 'Scheduling Calendar' form. Validate an appointment for "Client A" and "Client B" with "Practitioner A" that was sent from Mobile CareGiver+ is displayed at "Site A". Right click on the appointment for "Client A" and click [Details/Edit]. Validate the appointment details are displayed as expected. Close the form. Right click on the appointment for "Client B" and click [Details/Edit]. Validate the appointment details are displayed as expected. Close the form and click [Dismiss]. Scenario 2: Mobile Caregiver+ - Validate the 'McgEvvVisitStarted' incoming event for multiple recipients Specific Setup: Avatar is configured to integrate with Mobile CareGiver+. Please note: This must be done by a Netsmart Representative. A product is defined in the 'CareFabric Integration Management' form for the "MobileCareGiver+" product and "McgEvvAppointmentUpdated" must be selected in the 'Event Types' field. A program is defined with a value populated in the 'EVV Provider Organization ID' field in the 'Program Maintenance' form (Program A). "Program A" has an associated location (Location A) with the following defined in 'Dictionary Update' for the "Client" file, "(10006 Location)" data element: Extended dictionary data element "(587) Place Of Service (Mobile CareGiver+)" must be set to "Home" (unless an alternate address is being used). If the above dictionary data element is not defined, then the extended dictionary data element "(579) Place Of Service (837 Electronic Billing)" will be used and must be set to "Home". If this dictionary data element is not defined, then "(578) Place Of Service (HCFA 24-B)" will be used and must be set to "Home". A service code must be defined that has "Yes" selected in the 'Does This Service Require Electronic Visit Verification' field in the 'Service Codes' form and must be assigned to "Program A" (Service Code A). This service code must also have a CPT-4/HCPCS code associated to it in the 'Service Fee/Cross Reference Maintenance' form (Procedure Code A). Must have a guarantor defined in the 'Guarantors/Payors' form (Guarantor A). A site is defined with hours for scheduling (Site A). The following must be set in the "Electronic Visit Verification" section of the 'CarePOV Management' form: "Yes" is selected in the 'Enable Mobile CareGiver+' field. "Yes" is selected in the 'Send Non EVV Payers' field. "No" is selected in the 'Require Authorization' field. "Guarantor A" has a row with all fields populated in the 'Payor Program ID' grid. "Site A" selected in the 'Site' field. "Yes" is selected in the following fields for the 'McgEvvAppointmentUpdated' event: 'Keep Incoming Payload in the Log', 'Keep Outgoing Payload in the Log' and 'Show in the CareFabric Monitor Report' in the 'CareFabric Management' form. This must be done by a Netsmart Representative. A practitioner must be defined as an EVV resource with hours for scheduling at "Site A" and has the following on file: 'Name', 'Date Of Birth', 'Cellular Telephone', 'Staff EVV ID', 'Email Address', and 'Staff EVV Type' (Practitioner A). Two clients are enrolled in "Program A" and have the following on file: 'Client Name', 'Address - Street', 'Zipcode', 'Cell Phone', 'Diagnosis', "Guarantor A" selected in 'Financial Eligibility' (Client A & Client B). An unscheduled visit must be sent from the Mobile CareGiver+ application for multiple recipients using "Client A" and "Client B". Steps Start the unscheduled visit with multiple recipients, "Client A" and "Client B", in the Mobile CareGiver+ application. Access the 'CareFabric Monitor' form. Enter the current date in the 'From Date' and 'Through Date' fields. Select "Client A" in the 'Client ID' field. Select "McgEvvVisitStarted" in the 'Event/Action Search' field. Click [View Activity Log]. Validate the 'CareFabric Monitor Report' contains an "McgEvvVisitStarted" record. Click [Click To View Record]. Validate the 'clockInDetails' - 'deviceRecordedDate' field contains the date of the visit and start time. Validate the 'isMultipleRecipients' field contains "true". Validate the first - 'services' - 'clientID- 'id' field contains "Client A". Validate the first 'services' - 'procedureCode' - 'code' field contains "Procedure Code A". Validate the second 'services' - 'clientID' - 'id' field contains "Client B". Validate the second 'services' - 'procedureCode' - 'code' field contains "Procedure Code A". Validate the last 'status' field contains "INPR" indicating the visit is in progress. Close the report and the form. Access the 'Scheduling Calendar' form. Validate the appointments for "Client A" and "Client B" display with the visit start time. Click [Dismiss]. Access Crystal Reports or other SQL Reporting tool. Select the PM namespace. Create a report using the 'SYSTEM.appt_data' SQL table. Navigate to the appointment for "Client A" and "Client B". Validate the 'carefabric_appt_stat_code' field contains "INPR". Validate the 'carefabric_appt_stat_value' field contains "In Progress". Close the report. Scenario 3: Mobile CareGiver+ - Validate the 'McgEvvVisitDocumented' incoming event for a completed visit for multiple recipients Specific Setup: Avatar is configured to integrate with Mobile CareGiver+. Please note: This must be done by a Netsmart Representative. A product is defined in the 'CareFabric Integration Management' form for the "MobileCareGiver+" product and "McgEvvAppointmentUpdated" must be selected in the 'Event Types' field. In the 'Code Mappings' section of the 'CareFabric Integration Management' form, must have a "Note Type" mapping for the "MobileCareGiver+" product with "EVV" populated in the 'CareFabric Code' and 'Description' fields. This note type will be used for creating a progress note when the 'McgEvvVisitDocumented' incoming SDK event is received. A program is defined with a value populated in the 'EVV Provider Organization ID' field in the 'Program Maintenance' form (Program A). "Program A" has an associated location (Location A) with the following defined in 'Dictionary Update' for the "Client" file, "(10006 Location)" data element: Extended dictionary data element "(587) Place Of Service (Mobile CareGiver+)" set to "Home" (unless an alternate address is being used). If the above dictionary data element is not defined, then the extended dictionary data element "(579) Place Of Service (837 Electronic Billing)" will be used and must be set to "Home". If this dictionary data element is not defined, then "(578) Place Of Service (HCFA 24-B)" will be used and must be set to "Home". A service code must be defined that has "Yes" selected in the 'Does This Service Require Electronic Visit Verification' field in the 'Service Codes' form and must be assigned to "Program A" (Service Code A). This service code must also have a CPT-4/HCPCS code associated to it in the 'Service Fee/Cross Reference Maintenance' form (Procedure Code A). Must have a guarantor defined in the 'Guarantors/Payors' form (Guarantor A). The following must be set in the "Electronic Visit Verification" section of the 'CarePOV Management' form: "Yes" is selected in the 'Enable Mobile CareGiver+' field. "Yes" is selected in the 'Send Non EVV Payers' field. "No" is selected in the 'Require Authorization' field. "No" is selected in the 'Require Cancellation Reason' field. "Yes" is selected in the 'Save Progress Notes' form. A progress note form selected in the 'Progress Note Form' and/or other progress note forms defined in the 'Progress Notes Form Mapping' grid. If nothing is defined in the 'Progress Notes Form Mapping' grid, the default progress note selected in the 'Progress Note Form' field will be used. The following registry settings must be configured for the progress note form: 'Attach Selected Appointment To Notes On Draft' registry setting is set to "1" or "2" 'Post Appointment When the Note Is Submitted' registry setting is set to "Y" "Guarantor A" has a row with all fields populated in the 'Payor Program ID' grid. The 'Progress Notes' widget must be accessible from the HomeView. A practitioner must be defined as an EVV resource with hours for scheduling and has the following on file: 'Name', 'Date Of Birth', 'Cellular Telephone', 'Staff EVV ID', 'Email Address', and 'Staff EVV Type' (Practitioner A). Two clients are enrolled in "Program A" and have the following on file: 'Client Name', 'Address - Street', 'Zipcode', 'Cell Phone', 'Diagnosis', "Guarantor A" selected in 'Financial Eligibility' (Client A & Client B). An unscheduled visit must be started in the Mobile CareGiver+ application for multiple recipients using "Client A" and "Client B". Steps Complete the visit for multiple recipients (Client A & Client B) with "Practitioner A" in the Mobile CareGiver+ application. Ensure the visit includes notes for both "Client A" and "Client B". Access the 'Scheduling Calendar' form. Validate the appointment for both "Client A" and "Client B" is displayed at the correct start/end times for the visit. Validate the appointment for "Client A" is displayed with the draft note disposition icon (if configured in 'Set System Defaults'). Click [Dismiss]. Select "Client A" and navigate to the 'Progress Notes' widget. Validate the draft progress note created when the visit was completed is displayed with the appropriate data for the visit. Validate the 'Notes Field' field for the progress note contains the notes entered when completing the visit. Select "Client B" and navigate to the 'Progress Notes' widget. Validate the draft progress note created when the visit was completed is displayed with the appropriate data for the visit. Validate the 'Notes Field' field for the progress note contains the notes entered when completing the visit. In the Mobile CareGiver+ application, access the Work List. Update the 'Billable Service Start' and 'Billable Service End' times. Release the visit. Access the 'Scheduling Calendar' form. Validate the appointments for "Client A" and "Client B" are displayed at the updated start/end times for the visit. Validate the appointments for "Client A" and "Client B" are still displayed with the draft note disposition icon. Click [Dismiss]. Select "Client A" and navigate to the 'Progress Notes' widget. Validate the draft progress note displays the updated start/end times for the visit. Select "Client B" and navigate to the 'Progress Notes' widget. Validate the draft progress note displays the updated start/end times for the visit. Once the visit is accepted and received by myAvatar, the following will happen: Appointments will be posted, charges will be visible in the 'Client Ledger' Progress notes associated to the visit will be finalized.	Topics • Electronic Visit Verification

Avatar_CareFabric_2024_Quarterly_Release_2024.01_Details.csv