Skip to main content

Avatar CareFabric 2023 Monthly Release 2023.01.00 Acceptance Tests


Update 5 Summary | Details
Mobile CareGiver+ - Appointment Tasks
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
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 "(579) Place Of Service (837 Electronic Billing)" is set to "Home".
  • If the above dictionary data element is not defined, then the extended dictionary data element "(578) Place Of Service (HCFA 24-B)" will be used.
  • 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
  1. Access the 'Scheduling Calendar' form.
  2. Right click in any available time slot for "Practitioner A" and click [Add Appointment].
  3. Select "Service Code A" in the 'Service Code' field.
  4. Select "Client A" in the 'Client' field.
  5. Validate the 'Program' field contains "Program A".
  6. Validate the 'Location' field contains "Location A".
  7. Select the desired value(s) in the 'Available Tasks' field.
  8. Populate all other required and desired fields.
  9. Click [Submit].
  10. Validate the new appointment is displayed.
  11. Click [Dismiss].
  12. Access the 'CareFabric Monitor' form.
  13. Enter the current date in the 'From Date' and 'Through Date' fields.
  14. Select "Client A" in the 'Client ID' field.
  15. Select "EvvAppointmentUpdated" in the 'Event/Action Search' field.
  16. Click [View Activity Log].
  17. Validate the 'CareFabric Monitor Report' contains an "EvvAppointmentUpdated" record.
  18. Click [Click To View Record].
  19. Validate the 'appointmentAuthorization' field contains "null".
  20. Validate the 'appointmentID' - 'id' field contains the appointment ID.
  21. Validate the 'canceledDate' field contains "null".
  22. Validate the 'canceledReasonCode' field contains "null".
  23. Validate the 'providerOrganizationID' - 'id' field contains the 'Provider Organization ID' assigned to "Program A".
  24. Validate the 'clientID' - 'id' field contains the ID for "Client A".
  25. Validate the 'diagnosisCodes' - 'code' field contains the diagnosis code on file for "Client A".
  26. Validate the 'diagnosisCodes' - 'displayName' field contains the diagnosis value on file for "Client A".
  27. Validate the 'endDate' field contains the appointment end date/time.
  28. Validate the 'insPayerID' - 'id' field contains the 'MCG+ Payer ID' on file in the 'CarePOV Management' form for "Guarantor A".
  29. Validate the 'insPlanID' - 'id' field contains the 'MCG+ Insurance Plan ID' on file in the 'CarePOV Management' form for "Guarantor A".
  30. Validate the 'isEVV' field contains "true".
  31. Validate the 'locationOfService' fields contain "Client A's" home address.
  32. Validate the 'mcgInsPayerID' - 'id' field contains the 'MCG+ Payer ID' on file in the 'CarePOV Management' form for "Guarantor A".
  33. Validate the 'mcgInsPlanID' - 'id' field contains the 'MCG+ Insurance Plan ID' on file in the 'CarePOV Management' form for "Guarantor A".
  34. Validate the 'services' - 'description' field contains the description for "Service Code A".
  35. Validate the 'services' - 'name' field contains the code for "Service Code A".
  36. Validate the 'services' - 'procedureCode' - 'code' field contains the code for "Procedure A".
  37. Validate the 'services' - 'procedureCode' - 'displayName' field contains the name for "Procedure A".
  38. Validate the 'serviceID' - 'id' field contains the code for "Service Code A".
  39. Validate the 'tasks' - 'taskCode' fields contain the value(s) selected in the 'Available Tasks' field when scheduling the appointment.
  40. Validate the 'startDate' field contains the appointment start date/time.
  41. Validate all other relevant information is displayed for "Client A" and "Practitioner A".
  42. Close the report and the form.
Scenario 2: Mobile Caregiver+ - Validate the 'McgEvvVisitDocumented' incoming event for a completed visit
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 "(579) Place Of Service (837 Electronic Billing)" is set to "Home".
  • If the above dictionary data element is not defined, then the extended dictionary data element "(578) Place Of Service (HCFA 24-B)" will be used.
  • 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.
  • "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).
  • 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).
  • "Client A" has a visit with "Practitioner A" that has been started in Mobile CareGiver+.
Steps
  1. Complete the visit for "Client A" with "Practitioner A" in the Mobile CareGiver+ application.
  2. Ensure the visit includes completed tasks & notes.
  3. Access the 'Scheduling Calendar' form.
  4. Validate the appointment for "Client A" is displayed at the correct start/end times for the visit.
  5. Validate the appointment for "Client A" is displayed with the posted and finalized note disposition icons.
  6. Click [Dismiss].
  7. Select "Client A" and navigate to the 'Progress Notes' widget.
  8. Validate the progress note created when the visit was completed is displayed with the appropriate data for the visit.
  9. Validate the 'Notes Field' field for the progress note contains the notes entered when completing the visit, followed by a list of the tasks completed during the visit.
  10. Access Crystal Reports or other SQL Reporting tool.
  11. Select the PM namespace.
  12. Create a report using the 'SYSTEM.appt_data' SQL table.
  13. Navigate to the appointment for "Client A".
  14. Validate the 'carefabric_appt_stat_code' field contains "COMP".
  15. Validate the 'carefabric_appt_stat_value' field contains "Completed".
  16. Close the report.
Mobile CareGiver+ - Unscheduled Visits
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • CareFabric Monitor
  • CareFabric Integration Reconciliation
  • Registry Settings (PM)
Scenario 1: Mobile Caregiver+ - Validate the 'McgEvvAppointentUpdated' incoming event when the 'Enable 'Admission vs. Service Program' Functionality' registry setting is enabled
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.
  • The 'Enable 'Admission vs. Service Program' Functionality' registry setting is set to "Y".
  • An admission program is defined with a value populated in the 'EVV Provider Organization ID' field in the 'Program Maintenance' form (Program A).
  • "Program A" must have an associated service program in the 'Associated Service Program' field in the 'Program Maintenance' form (Program B).
  • "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 "(579) Place Of Service (837 Electronic Billing)" is set to "Home".
  • If the above dictionary data element is not defined, then the extended dictionary data element "(578) Place Of Service (HCFA 24-B)" will be used.
  • 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.
  • 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).
  • 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
  1. Add an unscheduled visit in the Mobile CareGiver+ application with associated tasks for "Client A" with "Practitioner A".
  2. 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.
  3. Access the 'Scheduling Calendar' form.
  4. Validate the appointment for "Client A" with "Practitioner A" that was sent from Mobile CareGiver+ is displayed.
  5. Right click on the appointment and click [Details/Edit].
  6. Validate the appointment details are displayed as expected.
  7. Validate the 'Service Code' field contains "Service Code A".
  8. Validate the 'Client' field contains "Client A".
  9. Validate the 'Episode Number' field contains the episode in "Program A".
  10. Validate the 'Practitioner' field contains "Practitioner A".
  11. Validate the 'Program' field contains "Program B".
  12. Validate the 'Available Tasks' field contains the tasks sent from Mobile CareGiver+.
  13. Close the form and click [Dismiss].

Topics
• Scheduling Calendar • Add New Appointment • CareFabric Monitor • Electronic Visit Verification • Registry Settings
Update 6 Summary | Details
Bells Notes Integration - Document Approver
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Dynamic Form - document routing - Route Document To
  • HomeView - Progress Notes Widget
  • HomeView - my Clients
Scenario 1: Validate the 'SelectDocumentApprover' SDK action
Steps

Internal testing only.

Bells Notes Integration - Document Routing
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Dynamic Form - document routing - Route Document To
  • HomeView - Progress Notes Widget
  • HomeView - my Clients
Scenario 1: Bells Notes Integration - Validate document routing for progress notes when a supervisor is not required
Specific Setup:
  • myAvatar must be configured to integrate with Bells Notes. Please note: this must be done by a Netsmart Associate.
  • The 'Progress Notes (Group and Individual)' form is configured and selected in the "Bells Notes" section of the 'CarePOV Management' form. Please note: this must be done by a Netsmart Associate.
  • The 'Progress Notes (Group and Individual)' form must have document routing enabled.
  • A user is defined with the following (User A):
  • Access to Bells Notes
  • Associated practitioner (Practitioner A)
  • Does not require a supervisor's approval for document routing
  • Access to the 'My To Do's' widget on the HomeView.
  • The 'Activate Program/Location Filter' registry setting is enabled.
  • A program is defined (Program A) with two associated locations (Location A, Location B). "Location A" is the default location for this program.
  • A client is enrolled in "Program A" (Client A).
Steps
  1. Access the 'Scheduling Calendar' form.
  2. Right click in the 'Appointment Grid' and click [Add Appointment].
  3. Enter the desired service code in the 'Service Code' field.
  4. Enter "Client A" in the 'Client' field.
  5. Select the desired value in the 'Episode Number' field.
  6. Validate "Program A" is selected in the 'Program' field.
  7. Select "Location B" in the 'Location' field.
  8. Validate the 'Practitioner' field is populated with "Practitioner A"
  9. Fill out all required fields.
  10. Click [Submit].
  11. Validate successful submission.
  12. Validate the scheduled appointment is added to the 'Scheduling Calendar' form.
  13. Log into Bells Notes with existing login credentials.
  14. Click the 'Agenda' section and verify the existence of the scheduled appointment from the 'Scheduling Calendar' form in myAvatar.
  15. Select the scheduled appointment and validate the summary of the scheduled appointment is displayed on the right side of the Bells Notes.
  16. Click [Start Note] and verify the existence of the 'Session Information' window.
  17. Fill out all required fields and select the desired note type.
  18. Validate user is able to start a note successfully.
  19. Verify the existence of "Client A" in the client header when note is started.
  20. Fill out all required fields.
  21. Click [Sign Note].
  22. Validate the Sign Note' dialog is displayed.
  23. Enter the pin for "User A" in the 'Pin' field and click [Sign].
  24. Validate a message is displayed stating: Note Signed Successfully.
  25. Log into myAvatar as [UserA].
  26. Navigate to the "My To Do's" widget.
  27. Locate the To Do just routed and click [Approve Document].
  28. Validate the document is displayed with the progress note data, including the correct location (Location B) and an electronic signature at the bottom for "Practitioner A" as Author.
  29. Click [Accept].
  30. Enter the password for "User A" in the 'Verify Password' dialog and click [OK].
  31. Validate the To-Do is no longer displayed.
Scenario 2: Bells Notes Integration - Validate document routing for progress notes when a supervisor is required
Specific Setup:
  • myAvatar must be configured to integrate with Bells Notes. Please note: this must be done by a Netsmart Associate.
  • The 'Progress Notes (Group and Individual)' form is configured and selected in the "Bells Notes" section of the 'CarePOV Management' form. Please note: this must be done by a Netsmart Associate.
  • The 'Progress Notes (Group and Individual)' form must have document routing enabled.
  • A user is defined [UserA] with the following:
  • Access to Bells Notes
  • Associated practitioner (Practitioner A)
  • Requires a supervisor's approval for document routing (Practitioner B)
  • Access to the 'My To Do's' widget on the HomeView
  • Must be logged in as this user
  • A user is defined [UserB] with the following:
  • Associated practitioner (Practitioner B)
  • Does not require a supervisor's approval for document routing
  • Access to the 'My To Do's' widget on the HomeView
  • The 'Activate Program/Location Filter' registry setting is enabled.
  • A program is defined (Program A) with two associated locations (Location A, Location B). "Location A" is the default location for this program.
  • A client is enrolled in "Program A" (Client A).
Steps
  1. Access the 'Scheduling Calendar' form.
  2. Right click in the 'Appointment Grid' and click [Add Appointment].
  3. Enter the desired service code in the 'Service Code' field.
  4. Enter "Client A" in the 'Client' field.
  5. Select the desired value in the 'Episode Number' field.
  6. Validate "Program A" is selected in the 'Program' field.
  7. Select "Location B" in the 'Location' field.
  8. Validate the 'Practitioner' field is populated with "Practitioner A"
  9. Fill out all required fields.
  10. Click [Submit].
  11. Validate successful submission.
  12. Validate the scheduled appointment is added to the 'Scheduling Calendar' form.
  13. Log into Bells Notes with existing login credentials.
  14. Click the 'Agenda' section and verify the existence of the scheduled appointment from the 'Scheduling Calendar' form in myAvatar.
  15. Select the scheduled appointment and validate the summary of the scheduled appointment is displayed on the right side of the Bells Notes.
  16. Click [Start Note] and verify the existence of the 'Session Information' window.
  17. Fill out all required fields and select the desired note type.
  18. Validate user is able to start a note successfully.
  19. Verify the existence of "Client A" in the client header when note is started.
  20. Fill out all required fields.
  21. Click [Sign Note].
  22. Validate the Sign Note' dialog is displayed.
  23. Enter the pin for "User A" in the 'Pin' field and click [Sign].
  24. Validate a message is displayed stating: Note Signed Successfully.
  25. Log into myAvatar as [UserB].
  26. Navigate to the "My To Do's" widget.
  27. Locate the To Do just routed and click [Approve Document].
  28. Validate the document is displayed with the progress note data, including the correct location (Location B) and an electronic signature at the bottom for "Practitioner A" as Author and "Practitioner B" as Supervisor.
  29. Click [Accept].
  30. Enter the password for [UserB] in the 'Verify Password' dialog and click [OK].
  31. Validate the To-Do is no longer displayed.
Scenario 3: Bells Notes Integration - Accept a note via the "Sign" section of the 'My To Do's' widget
Specific Setup:
  • myAvatar must be configured to integrate with Bells Notes. Please note: this must be done by a Netsmart Associate.
  • The 'Progress Notes (Group and Individual)' form is configured and selected in the "Bells Notes" section of the 'CarePOV Management' form. Please note: this must be done by a Netsmart Associate.
  • 'Progress Notes (Group and Individual)' must have document routing enabled.
  • A user is defined with the following (User A):
  • Access to Bells Notes
  • Associated practitioner
  • Does not require a supervisor's approval for document routing
  • Access to the 'My To Do's' widget on the HomeView.
  • A client is enrolled in an existing episode (Client A).
  • The 'Warning Message for "Draft" Forms' registry setting is enabled with a value.
Steps
  1. Log into Bells Notes with existing login credentials for "User A".
  2. Search for "Client A".
  3. Click [Start Note] and verify the existence of the 'Session Information' window.
  4. Fill out all required fields and select the desired note type.
  5. Verify the existence of "Client A" in the client header when note is started.
  6. Fill out all required fields.
  7. Click [Sign Note].
  8. Validate the Sign Note' dialog is displayed.
  9. Enter the pin for "User A" in the 'Pin' field and click [Sign].
  10. Validate a message is displayed stating: Note Signed Successfully.
  11. Log into myAvatar as "User A".
  12. Navigate to the "My To Do's" widget.
  13. Select the "Sign" section.
  14. Validate the 'Search Documents' field contains the progress note document sent via Bells Notes for "Client A".
  15. Validate the 'Document' field contains the progress note data.
  16. Click [Accept].
  17. Validate the 'Search Documents' field no longer contains the progress note document for "Client A".
  18. Validate the 'Accepted Documents' field contains the accepted progress note document for "Client A".
  19. Click [Sign All].
  20. Enter the password for "User A" in the 'Verify Password' dialog and click [OK].
  21. Validate the 'Accepted Documents' field no longer contains the progress note document for "Client A".
Scenario 4: Bells Notes Integration - Accept a note via the "All" section of the 'My To Do's' widget
Specific Setup:
  • myAvatar must be configured to integrate with Bells Notes. Please note: this must be done by a Netsmart Associate.
  • The 'Progress Notes (Group and Individual)' form is configured and selected in the "Bells Notes" section of the 'CarePOV Management' form. Please note: this must be done by a Netsmart Associate.
  • The 'Progress Notes (Group and Individual)' form must have document routing enabled.
  • A user is defined with the following (User A):
  • Access to Bells Notes
  • Associated practitioner
  • Does not require a supervisor's approval for document routing
  • Access to the 'My To Do's' widget on the HomeView.
  • A client is enrolled in an existing episode (Client A).
  • The 'Warning Message for "Draft" Forms' registry setting is enabled with a value.
Steps
  1. Log into Bells Notes with existing login credentials for "User A".
  2. Search for "Client A".
  3. Click [Start Note] and verify the existence of the 'Session Information' window.
  4. Fill out all required fields and select the desired note type.
  5. Verify the existence of "Client A" in the client header when note is started.
  6. Fill out all required fields.
  7. Click [Sign Note].
  8. Validate the Sign Note' dialog is displayed.
  9. Enter the pin for "User A" in the 'Pin' field and click [Sign].
  10. Validate a message is displayed stating: Note Signed Successfully.
  11. Log into myAvatar as "User A".
  12. Navigate to the "My To Do's" widget.
  13. Select the "All" section.
  14. Validate a To-Do is displayed for the progress note sent via Bells Notes for "Client A".
  15. Click [Approve Document].
  16. Validate the progress note data is displayed.
  17. Click [Accept].
  18. Enter the password for "User A" in the 'Verify Password' field and click [OK].
  19. Validate the To-Do is no longer displayed.
Avatar CareFabric - Service Strategy Codes
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Ambulatory Progress Notes (Diagnosis Entry)
Scenario 1: Progress Notes (Group and Individual) - Service Strategy Codes
Specific Setup:
  • The logged in user is associated to a staff member ("Staff Member A").
  • A client is enrolled in an existing episode ("Client A").
  • Document Routing is enabled in the 'Document Routing Setup' form for 'Progress Notes (Group and Individual)' form.
  • "Avatar PM->Services->->->->Enable Evidence Based Practice Fields" registry setting is set to "Y".
  • "Avatar PM ->California Required EDI->CSI->->->Enable MHSA/DIG Data Collection Fields" registry setting is set to "N"
  • Existing Progress Note with 'Evidence-Based Practices / Service Strategies (CSI)' field enabled in 'Site Specific Section Modeling' form: 'Exclude From Data Collection Instrument' field set to "No".
  • One or more service strategy dictionary codes defined in CWS (70680) "Evidence-Based Practices / Service Strategies (CSI)" with selected values.
  • One or more service strategy dictionary codes defined in PM (10560) "Evidence-Based Practices" with selected values.
Steps
  1. Select "Client A" and access the 'Progress Notes (Group and Individual)' form.
  2. Select any value from the 'Select Episode' field.
  3. Select "New Service" from the 'Progress Notes For' field.
  4. Select any value from the 'Note Type' field.
  5. Set the 'Notes Field' to any value.
  6. Set the 'Date Of Service' field to the current date.
  7. Set the 'Service Charge Code' field to any value.
  8. Select the desired value in the 'Evidence Based Practices' field.
  9. Select the desired value in the 'Evidence Based Practices / Service Strategies (CSI)' field.
  10. Complete the required fields with the desired value.
  11. Select "Draft" from the 'Draft/Final' field.
  12. Click [File Note].
  13. Validate a 'Progress Notes message' is displayed stating: "Note Filed".
  14. Click [OK] and close the form.
  15. Select "Client A" and navigate to the "Progress Notes" widget.
  16. Locate the note that was just filed in the previous steps.
  17. Validate the saved strategy service codes are displayed under the "Evidence Based Practices" section.
  18. Validate the saved strategy service codes are displayed under the "Evidence Based Practices / Service Strategies (CSI)" section.
Bells Notes Integration - CPT Code Calculation
Scenario 1: Progress Notes (Group and Individual) - Validate CPT code calculation
Specific Setup:
  • Have two users: [UserA] and [UserB]
  • Both users have the "My To Do's" widget on their home view
  • [UserA] is defined with the following:
  • An associated staff member ("Staff Member A").
  • User with existing client admitted with financial eligibility on file ("Client A").
  • Document Routing is enabled in the 'Document Routing Setup' form for 'Progress Notes (Group and Individual)' form.
  • "Avatar CWS->Progress Notes->Additional Fields->->->Guarantors To Capture Additional Service Info On Progress Notes" registry setting is set to multiple guarantor codes (e.g. 1&2&100)
  • The 'Progress Notes (Group and Individual)' form has a 'Scrolling Free Text' field (CPT Code, Modifiers, Total Units) enabled with a 'Product Custom Logic Definition' for "Capture CPT Code, Modifiers, Total Units For All Rendered Services". This can be done via 'Site Specific Section Modeling'.
  • [UserB] with an associated staff member ("Staff Member B")
Steps
  1. Select "Client A" and access the 'Progress Notes (Group and Individual)' form.
  2. Select any value from the 'Select Episode' field.
  3. Select "New Service" from the 'Progress Notes For' field.
  4. Select any value from the 'Note Type' field.
  5. Set the 'Notes Field' to any value.
  6. Set the 'Date Of Service' field to the current date.
  7. Set the 'Service Charge Code' field to any value.
  8. Complete the required fields with the desired value.
  9. Verify the existence of the 'CPT Code, Modifier, Total Units' field.
  10. Select "Final" in the 'Draft/Final' field.
  11. Click [File Note].
  12. Validate that the 'Confirm Document' dialog is displayed with the progress note data, including an electronic signature at the bottom for "Staff Member A" as the Author.
  13. Validate the "Product Custom Logic" field configured in 'Site Specific Section Modeling' form is displayed with the CPT Code, Modifiers and Total Units in the document.
  14. Click [Accept and Route].
  15. Enter the desired value in the 'Password' field.
  16. Click [OK].
  17. Validate the 'Route Document To' dialog is displayed.
  18. Search for "Staff Member B" in the "Add Approver" field.
  19. Click [Add].
  20. Validate "Staff Member B" is added as an "Approver" and the "Approver" check box is selected.
  21. Click [Submit].
  22. Validate a 'Progress Notes message' is displayed stating: "Note Filed".
  23. Click [OK].
  24. Click [Discard].
  25. Log in as [UserB] and navigate to the "My To Do's" widget.
  26. Validate there is a To-Do for the progress note filed in the previous steps.
  27. Click [Approve Document].
  28. Validate the document is displayed with the progress note data, including an electronic signature at the bottom for "Staff Member A" as Author and "Staff Member B" as Final Approver.
  29. Validate the "Product Custom Logic" field configured in 'Site Specific Section Modeling' form is displayed with the CPT Code, Modifiers and Total Units in the document.
  30. Click [Acknowledge].
  31. Enter the password for "User B" in the 'Verify Password' dialog and click [OK].
  32. Validate the To-Do is no longer displayed.
  33. Log in as [UserA] and navigate to the "Progress Notes" widget.
  34. Select "ClientA" in the 'Select Client' field.
  35. Locate the note that was just finalized in the previous steps.
  36. Validate the "Product Custom Logic" field configured in 'Site Specific Section Modeling' form is displayed with the CPT Code, Modifiers and Total Units in the progress note.
  37. Access the 'Clinical Document Viewer' form.
  38. Select "Individual" in the 'Select All or Individual Patient' field.
  39. Select "Client A" in the 'Select Client' field.
  40. Select the desired value in the "Episode" field.
  41. Click [Process].
  42. Select the document that was just finalized from the document list.
  43. Validate the document is displayed with the progress note data, including an electronic signature at the bottom for "Practitioner A" as Author and "Practitioner B" as Attending Practitioner.
  44. Validate the "Product Custom Logic" field configured in 'Site Specific Section Modeling' form is displayed with the CPT Code, Modifiers and Total Units in the document.
  45. Click [Close All Documents].
  46. Validate the document is closed.

Topics
• CareFabric • Progress Notes
Update 9 Summary | Details
Orders This Episode - Lab Orders with multiple diagnosis
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Orders This Episode
  • Registry Settings (PM)
Scenario 1: OE NX - Orders This Episode - Multiple Diagnosis on Lab Orders
Specific Setup:
  • Avatar OE 2023 Update 8, Avatar CareFabric 2023 Update 9, and Avatar NX Release 2023.03.00 are required in order to utilize full functionality.
  • The 'Avatar Order Entry->Facility Defaults->Client Profile->->->Enable Supplemental Diagnoses for Lab Orders in OE Console (Orders This Episode)' registry setting must be set to "Y".
  • A lab-type order code must have an external lab vendor selected in the 'External Lab Definition' portion of the 'Order Code Setup' form. (Complete Blood Count)
  • Please log out of the application and log back in after completing the above configuration.
  • A client must have an active inpatient episode. (Client A)
  • “Client A” must have a ‘Date of Birth’, ‘Sex’ and address on file in the ‘Update Client Data’ form, as well as information filed in the ‘Allergies and Hypersensitivities’ form, and in the ‘Height’ and ‘Weight’ fields in the ‘Vitals Entry’ form.
  • "Client A" must have two values filed in the 'Diagnosis' form. (Diagnosis A and Diagnosis B)
Steps
  1. Select "Client A" and access the Order Entry Console.
  2. Search for and select "Complete Blood Count" in the 'New Order' field.
  3. Validate the 'External Lab Vendor Destination' field contains a value.
  4. Set the 'Duration' field to any value and click [Days].
  5. Validate a [+] is displayed in front of the 'Diagnosis' fields.
  6. Validate the 'Diagnosis' fields are not required.
  7. Click the [+] three times.
  8. Validate two additional 'Diagnoses' rows were added.
  9. Validate that all 'Diagnoses' fields are required.
  10. Select "Diagnosis A" in the 1st 'Diagnosis' selection field.
  11. Search for and select any value in the 1st 'Diagnosis' search field and validate the 1st 'Diagnosis' selection field is cleared.
  12. Select "Diagnosis A" in the 1st 'Diagnosis' selection field and validate the 1st 'Diagnosis' search field is cleared.
  13. Click in the 2nd 'Diagnosis' selection field and validate that "Diagnosis A" is not displayed.
  14. Select "Diagnosis B" in the 2nd 'Diagnosis' selection field.
  15. Search for and select any value in the 3rd 'Diagnosis' search field.
  16. Validate the 4th 'Diagnoses' fields do not contain a value.
  17. Click [Add to Scratchpad].
  18. Validate the order is displayed in the 'Scratchpad' with a red flag in the 'Action' column.
  19. Select the order in the 'Scratchpad' and click the red [x] next to the 4th 'Diagnoses' fields and click [Update Order].
  20. Validate the red flag is no longer displayed and click [Sign].
  21. Validate the 'Order grid' contains the "Complete Blood Count" order.
  22. Select the order in the 'Order grid' and click [Copy].
  23. Validate the 'Diagnoses' fields contain the same values that were selected and that all values appear in the search fields on the right.
  24. Click Refresh.
  25. Select the order in the 'Order grid' and click [Modify].
  26. Validate the 'Diagnoses' fields contain the same values that were selected and that all values appear in the search fields on the right.
  27. Click Refresh.

Topics
• Order Entry Console • NX
Update 10 Summary | Details
Avatar CareFabric - 'ListIntegratedCareVisit' SDK action
Scenario 1: Validate the 'ListIntegratedCareVisit' SDK action
Steps
  • Internal testing only.

Topics
• CareFabric
Update 11 Summary | Details
Avatar CareFabric - BedBoard
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Homeview.BedBoard widget
  • Client Summary Display
  • Admission
  • Diagnosis
  • Allergies and Hypersensitivities
  • Financial Eligibility
Scenario 1: BedBoard - Field/Data Validations
Specific Setup:
  • The 'BedBoard' POV is configured and accessible on the user's HomeView.
  • A client (Client A) is enrolled in an existing inpatient episode with the following on file: Emergency Contact, Alias, Diagnosis, Financial Eligibility, Allergies, Date of Birth, Race, New Order.
Steps
  1. Access the 'BedBoard' POV.
  2. Select the unit "Client A" is admitted into from the left-hand side.
  3. Validate "Client A" displays under the correct room.
  4. Click on "Client A" to launch the client summary.
  5. Validate the 'Client Name' field contains the first name, last initial, age, gender, and any applicable client alerts.
  6. Validate the 'Attending Physician' field contains the attending physician for "Client A".
  7. Validate the 'Discharge Status' field contains the discharge status for "Client A".
  8. Validate the 'Room Assignment' field contains the room "Client A" is assigned to.
  9. Validate the 'Bed Assignment' field contains the bed "Client A" is assigned to.
  10. Validate the 'Emergency Contact' field contains the emergency contact on file for "Client A".
  11. Validate the 'Alias' field contains the alias on file for "Client A".
  12. Validate the 'Primary Dx' field contains the primary diagnosis on file for "Client A".
  13. Validate the 'Treatment Team' field contains the treatment team for "Client A".
  14. Validate the 'Payor' field contains the guarantor on file in 'Financial Eligibility' for "Client A".
  15. Validate the 'Allergies' field contains the allergy on file for "Client A".
  16. Validate the 'DOB' field contains the date of birth for "Client A".
  17. Validate the 'Admission Date' field contains the admission date for "Client A".
  18. Validate the 'Race' field contains the race on file for "Client A".
  19. Validate the 'Next Med Admin Time' field contains the time of next medication administration for "Client A".
  20. Close the client summary.

Topics
• Bed Board • CareFabric
Update 13 Summary | Details
Avatar CareFabric - Practitioner Credentials
Scenario 1: Validate the 'ListBehavioralHealthEpisode' SDK action
Steps
  • Internal testing only
Scenario 2: Validate the 'GetBehavioralHealthEpisode' SDK action
Steps
  • Internal testing only
Topics
• CareFabric