Skip to main content

Avatar CareFabric 2024 Quarterly Release 2024.02 Acceptance Tests

  1. Last updated
  2. 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
  1. Open the "Product Updates" form.
  2. Select the appropriate [Namespace] from the Application dropdown list
  3. Click [Select Update/Customization Pack].
  4. Browse to the location for the updates and select the Update 1.
  5. Click [OK] on the "File Upload Complete" window.
  6. Click [Review Update/Customization Pack Contents].
  7. Verify Update 1 is included.
  8. Click [Install Update/Customization Pack].
  9. Click [OK] when the install completes.
  10. 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:
  • 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
  1. Search for and select "Client A" and navigate to the 'Medical Note'.
  2. Click [Add Note] and create a new note such that:
  3. 'Location' = "Office".
  4. 'Client Type' = "New".
  5. Select the ‘Document’ tab and navigate to the 'Diagnosis' section.
  6. Add two new diagnoses for the client and add them both to the problem list.
  7. Navigate to the 'MDM' section.
  8. Check the 'Problem Addressed?' checkbox for one of the newly added diagnoses.
  9. Validate the 'Problem Category' field is enabled.
  10. Select "Acute, uncomplicated illness or injury requiring hospital inpatient or observation-level of care" from the 'Problem Category' field.
  11. Check the following checkboxes in the 'Amount and/or Complexity of Data to be Reviewed and Analyzed' section:
  12. "Review of prior external note(s) from each unique source".
  13. Select "Low" from the 'Risk of Complications and/or Morbidity or Mortality of Patient Management' section.
  14. Complete any remaining required sections.
  15. Select the 'Finalize' tab and navigate to the 'CPT Selection' section.
  16. Set 'Face-to-Face Time with Client' field to "30".
  17. Click [Debug] and verify the popup window 'CPT Debug' is displayed.
  18. Verify the Results section contains:
  19. 'CPT Guidelines Version:' = "2024".
  20. 'Visit Type:' = "New".
  21. 'Location Type:' = "Office or another outpatient setting".
  22. 'Visit Duration:' = "30 Minute(s)".
  23. Verify the 'MDM: Low' section contains:
  24. 'Problem Points:' = "Low".
  25. 'Data Points:' = "Minimal or none".
  26. 'Risk:' = "Low".
  27. Validate the 'CPT Codes: Office or other outpatient visit – new patient' section contains a row such that:
  28. 'Code' = "99203".
  29. 'MDM Score' = "Low".
  30. 'Min Duration' = "30".
  31. 'Doc?' = checked.
  32. 'Dur?' = checked.
  33. Close the 'CPT Debug' window.
  34. Validate that code '99203' is displayed on the 'Document-Based Recommendation' card under the section 'CPT Selection'.
  35. Validate that code '99203' is displayed on the 'Time-Based Recommendation:' card under the section 'CPT Selection'.
  36. Select the 'Document' tab and navigate to the 'MDM' section.
  37. Select "Stable, acute illness" from the 'Problem Category' field.
  38. Check the following checkboxes in the 'Amount and/or Complexity of Data to be Reviewed and Analyzed' section:
  39. "Review of prior external note(s) from each unique source".
  40. "Review of the result(s) of each unique test".
  41. "Ordering of each unique test".
  42. Select the 'Finalize' tab and navigate to the 'CPT Selection' section.
  43. Click [Debug] and verify the popup window 'CPT Debug' is displayed.
  44. Verify the 'MDM: Low' section contains:
  45. 'Problem Points:' = "Low".
  46. 'Data Points:' = "Moderate".
  47. 'Risk:' = "Low".
  48. Close the 'CPT Debug' window.
  49. Validate that code '99203' is displayed on the 'Document-Based Recommendation' card under the section 'CPT Selection'.
  50. Validate that code '99203' is displayed on the 'Time-Based Recommendation:' card under the section 'CPT Selection'.
  51. Select the 'Document' tab and navigate to the 'MDM' section.
  52. Check the 'Problem Addressed?' checkbox for the other newly added diagnoses.
  53. Validate the 'Problem Category' field is enabled.
  54. Select "Acute, uncomplicated illness or injury requiring hospital inpatient or observation-level of care" from the 'Problem Category' field.
  55. Check all remaining checkboxes in the 'Amount and/or Complexity of Data to be Reviewed and Analyzed' section
  56. Select the 'Finalize' tab and navigate to the 'CPT Selection' section.
  57. Click [Debug] and verify the popup window 'CPT Debug' is displayed.
  58. Verify the 'MDM: Low' section contains:
  59. 'Problem Points:' = "Low".
  60. 'Data Points:' = "Extensive".
  61. 'Risk:' = "Low".
  62. Close the 'CPT Debug' window.
  63. Validate that code '99203' is displayed on the 'Document-Based Recommendation' card under the section 'CPT Selection'.
  64. Validate that code '99203' is displayed on the 'Time-Based Recommendation:' card under the section 'CPT Selection'.
  65. Click 'Accept' on the 'Document-Based Recommendation' card.
  66. Validate "99203-Office or other outpatient visit - new patient" is selected in the 'CPT Code Selected' field.
  67. Click [Generate Note] and validate the note summary contains a section for 'Medical Decision Making'.
  68. Validate the 'Amount and/or Complexity of Data to be Reviewed and Analyzed:" section contains the following:
  69. "Review of prior external note(s) from each unique source".
  70. "Review of the result(s) of each unique test".
  71. "Ordering of each unique test".
  72. "Assessment requiring an independent historian(s)".
  73. "Independent interpretation of a test performed by another physician/other qualified health care professional (not separately reported)".
  74. "Discussion of management or test interpretation with external physician/other qualified health care professional/appropriate source (not separately reported)".
  75. 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
  1. Search for and select "Client A" and navigate to the 'Medical Note'.
  2. Click [Add Note] and create a new note such that:
  3. 'Location' = "Office".
  4. 'Client Type' = "Established".
  5. Select the ‘Document’ tab and navigate to the 'Diagnosis' section.
  6. Add a new diagnosis for the client.
  7. Navigate to the 'MDM' section.
  8. Check the 'Problem Addressed?' checkbox for the newly added diagnosis.
  9. Validate the 'Problem Category' field is enabled.
  10. Select "Acute, uncomplicated illness or injury requiring hospital inpatient or observation-level of care" from the 'Problem Category' field.
  11. Check the following checkboxes in the 'Amount and/or Complexity of Data to be Reviewed and Analyzed' section:
  12. "Ordering of each unique test".
  13. "Independent interpretation of a test performed by another physician/other qualified health care professional (not separately reported)".
  14. Select "Low" from the 'Risk of Complications and/or Morbidity or Mortality of Patient Management' section.
  15. Complete any remaining required sections.
  16. Select the 'Finalize' tab and navigate to the 'CPT Selection' section.
  17. Set 'Face-to-Face Time with Client' field to "20".
  18. Click [Debug] and verify the popup window 'CPT Debug' is displayed.
  19. Verify the Results section contains:
  20. 'CPT Guidelines Version:' = "2024".
  21. 'Visit Type:' = "Established".
  22. 'Location Type:' = "Office or another outpatient setting".
  23. 'Visit Duration:' = "20 Minute(s)".
  24. Verify the 'MDM: Low' section contains:
  25. 'Problem Points:' = "Low".
  26. 'Data Points:' = "Moderate".
  27. 'Risk:' = "Low".
  28. Validate the 'CPT Codes: Office or other outpatient visit – established patient' section contains a row such that:
  29. 'Code' = "99213".
  30. 'MDM Score' = "Low".
  31. 'Min Duration' = "20".
  32. 'Doc?' = checked.
  33. 'Dur?' = checked.
  34. Close the 'CPT Debug' window.
  35. Verify that code '99213' is displayed on the 'Document-Based Recommendation' card under the section 'CPT Selection'.
  36. 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
  1. Log in with "System Code 1".
  2. Access the 'CareFabric Assessment Mapping' form.
  3. Select "Assessment A" in the 'Select Assessment' field.
  4. Select "Form A" in the 'Select Modeled Form' field.
  5. Validate the 'System Code(s)' field is displayed. This will display when there are multiple root system codes defined.
  6. Validate "System Code 2" is displayed in the 'System Code(s)' field.
  7. Click [Launch Mapping Grid].
  8. Validate no mappings are displayed.
  9. Click [Close/Cancel] and close the form.
  10. Log out.
  11. Log in with "System Code 2".
  12. Access the 'CareFabric Assessment Mapping' form.
  13. Select "Assessment A" in the 'Select Assessment' field.
  14. Select "Form A" in the 'Select Modeled Form' field.
  15. Validate the 'System Code(s)' field is displayed. This will display when there are multiple root system codes defined.
  16. Select "System Code 1" in the 'System Code(s)' field.
  17. Click [Launch Mapping Grid].
  18. Add the desired mappings.
  19. Click [Save] and [Yes].
  20. Click [File Mappings] and close the form.
  21. Log out.
  22. Log in with "System Code 1".
  23. Access the 'CareFabric Assessment Mapping' form.
  24. Select "Assessment A" in the 'Select Assessment' field.
  25. Select "Form A" in the 'Select Modeled Form' field.
  26. Validate a message is displayed stating: The form is already mapped in this system code: "System Code 2".
  27. Please note: The mapping can only be edited in the root system code it was filed in.
  28. Click [OK].
  29. Close the form.
  30. Navigate to the 'Generic Assessment' widget for "Client A".
  31. File "Assessment A" for the client, populating all required and desired fields that are mapped via 'CareFabric Assessment Mapping'.
  32. Select "Client A" and access "Form A".
  33. Validate a record is displayed for the assessment filed via the 'Generic Assessment' widget.
  34. Click [Edit].
  35. Validate all fields display as expected based on the mappings defined via 'CareFabric Assessment Mapping'.
  36. 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
  1. Access the 'CarePOV Management' form.
  2. Select the "Client Alerts" section.
  3. Select "Edit" in the 'Add or Edit Alert' field.
  4. Select "Alcohol Detox" in the 'Client Alert' field.
  5. Validate the 'Selected Diagnosis' field contains a list of diagnoses with codes/descriptions.
  6. Validate the 'Selected Problem' field contains a list of problems with codes/descriptions.
  7. Select "Fall Risk" in the 'Client Alert' field.
  8. Validate the 'Selected Diagnosis' field contains a list of diagnoses with codes/descriptions.
  9. Validate the 'Selected Problem' field contains a list of problems with codes/descriptions.
  10. Select "High Blood Pressure" in the 'Client Alert' field.
  11. Validate the 'Selected Diagnosis' field contains a list of diagnoses with codes/descriptions.
  12. Validate the 'Selected Problem' field contains a list of problems with codes/descriptions.
  13. 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
  1. Open the "Scheduling Calendar" form.
  2. Schedule a recurring appointment TeleHealth service using a TeleHealth service code.
  3. Open the "CareFabric Monitor" form:
  4. Run the Activity Log for the following events "TeleHealthAppointmentCreated".
  5. Validate that a "TeleHealthAppointmentCreated" event is generated for however many appointments are in the recurrence.
  6. Validate that each "TeleHealthAppointmentCreated" event includes the following:
  7. Validate the "isReoccuringAppointment" property is "true".
  8. Validate the event includes the "RecurrenceInfo" object.
  9. Validate the "appointmentDateRange" object. Ensure the date and time are accurate.
  10. Validate the "recurrenceInfo" - "startDate" field. Ensure the date and time are accurate.
  11. Return to the "Scheduling Calendar":
  12. Edit the recurring appointment that was created in previous steps.
  13. Change the duration of the service.
  14. Open the "CareFabric Monitor" form:
  15. Run the Activity Log for the following events "TeleHealthAppointmentUpdated".
  16. Validate that a "TeleHealthAppointmentUpdated" event is generated for however many appointments are in the recurrence.
  17. Validate that each "TeleHealthAppointmentUpdated" event includes the following:
  18. Validate the "isReoccuringAppointment" property is "true".
  19. Validate the event includes the "RecurrenceInfo" object.
  20. Validate the "appointmentDateRange" object. Ensure the date and time are accurate.
  21. Validate the "recurrenceInfo" - "startDate" field. Ensure the date and time are accurate.
  22. Return to the "Scheduling Calendar":
  23. Delete the recurring appointment that was created and edited in previous steps.
  24. Open the "CareFabric Monitor" form:
  25. Run the Activity Log for the following events "TeleHealthAppointmentDeleted".
  26. Validate that a "TeleHealthAppointmentDeleted" event is generated for however many appointments are in the recurrence.
  27. Validate that each "TeleHealthAppointmentDeleted" event includes the following:
  28. Validate the "isReoccuringAppointment" property is "true".
  29. 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
  1. Open the "Scheduling Calendar" form:
  2. Schedule a recurring appointment TeleHealth service using a TeleHealth location.
  3. Open the "CareFabric Monitor" form:
  4. Run the Activity Log for the following events "TeleHealthAppointmentCreated".
  5. Validate that a "TeleHealthAppointmentCreated" event is generated for however many appointments are in the recurrence.
  6. Validate that each "TeleHealthAppointmentCreated" event includes the following:
  7. Validate the "isReoccuringAppointment" property is "true".
  8. Validate the event includes the "RecurrenceInfo" object.
  9. Validate the "appointmentDateRange" object. Ensure the date and time are accurate.
  10. Validate the "recurrenceInfo" - "startDate" field. Ensure the date and time are accurate.
  11. Return to the "Scheduling Calendar":
  12. Edit the recurring appointment that was created in previous steps.
  13. Change the duration of the service.
  14. Open the "CareFabric Monitor" form:
  15. Run the Activity Log for the following events "TeleHealthAppointmentUpdated".
  16. Validate that a "TeleHealthAppointmentUpdated" event is generated for however many appointments are in the recurrence.
  17. Validate that each "TeleHealthAppointmentUpdated" event includes the following:
  18. Validate the "isReoccuringAppointment" property is "true".
  19. Validate the event includes the "RecurrenceInfo" object.
  20. Validate the "appointmentDateRange" object. Ensure the date and time are accurate.
  21. Validate the "recurrenceInfo" - "startDate" field. Ensure the date and time are accurate.
  22. Return to the "Scheduling Calendar":
  23. Delete the recurring appointment that was created and edited in previous steps.
  24. Open the "CareFabric Monitor" form:
  25. Run the Activity Log for the following events "TeleHealthAppointmentDeleted".
  26. Validate that a "TeleHealthAppointmentDeleted" event is generated for however many appointments are in the recurrence.
  27. Validate that each "TeleHealthAppointmentDeleted" event includes the following:
  28. Validate the "isReoccuringAppointment" property is "true".
  29. 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
  1. Using the "Scheduling Calendar"
  2. Add a new group telehealth appointment.
  3. Leave this form open.
  4. Using the "CareFabric Monitor" form
  5. Using filters, locate the "TeleHealthAppointmentCreated" event that was triggered when the appointment was created.
  6. Validate the event includes all clients in the group.
  7. Leave this form open.
  8. Using the "Scheduling Calendar"
  9. Right click on the appointment that was just scheduled.
  10. Click on "Add/Remove Group Members" to remove a client from the group appointment.
  11. Using the "CareFabric Monitor" form
  12. Using filters, locate the "TeleHealthAppointmentUpdated" event that was triggered when a group member was removed from the group.
  13. Validate the event includes all clients who remain in the group.
  14. Leave this form open.
  15. Using the "Scheduling Calendar"
  16. Right click on the appointment that was just updated.
  17. Click on "Delete".
  18. Validate the appointment is removed from the calendar.
  19. Using the "CareFabric Monitor" form
  20. Using filters, locate the "TeleHealthAppointmentDeleted" event that was triggered when the appointment was deleted.
  21. 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
  1. Using the "Scheduling Calendar"
  2. Add a new group telehealth appointment.
  3. Leave this form open.
  4. Using the "CareFabric Monitor" form
  5. Using filters, locate the "TeleHealthAppointmentCreated" event that was triggered when the appointment was created.
  6. Validate the event includes all clients in the group.
  7. Leave this form open.
  8. Using the "Scheduling Calendar"
  9. Right click on the appointment that was just scheduled.
  10. Click on "Add/Remove Group Members" to remove a client from the group appointment.
  11. Using the "CareFabric Monitor" form
  12. Using filters, locate the "TeleHealthAppointmentUpdated" event that was triggered when a group member was removed from the group.
  13. Validate the event includes all clients who remain in the group.
  14. Leave this form open.
  15. Using the "Scheduling Calendar"
  16. Right click on the appointment that was just updated.
  17. Click on "Delete".
  18. Validate the appointment is removed from the calendar.
  19. Using the "CareFabric Monitor" form
  20. Using filters, locate the "TeleHealthAppointmentDeleted" event that was triggered when the appointment was deleted.
  21. 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
  1. Log into the application as "User A".
  2. Access the 'Scheduling Calendar' and create an appointment for "Client A" and close the form
  3. Select "Client A" and access 'Medical Note'.
  4. Click [Today's Appts Notes].
  5. Find the appointment for "Client A" and click [Start].
  6. Populate all required fields and click [Save].
  7. Click [Today's Appts Notes] and validate that [Edit] is displayed.
  8. Open a new browser and log into the application as "User B".
  9. Access the 'Scheduling Calendar'.
  10. Right click on the appointment created for "Client A" and select 'Details/Edit'.
  11. Access the first browser where "User A" is logged in.
  12. Validate that "Client A" is selected and that you are on 'Medical Note'.
  13. Click [Today's Appts Notes].
  14. Find the appointment for "Client A" and click [Edit].
  15. Validate an "Appointment Locked. The appointment is currently locked by "User B". Editing is unavailable at this time." and click [Close].
  16. Click on "Client A's" name and click [Select Note].
  17. Find the note for appointment for "Client A" and click [Edit].
  18. Validate an "Appointment Locked. The appointment is currently locked by "User B". Editing is unavailable at this time." and click [Close].
  19. Click [My Draft Notes].
  20. Find the appointment for "Client A" and click [Edit].
  21. 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
  1. Access the 'Clinical Notes Mapping' form.
  2. Select "Progress Note" in the 'Type of CCDA Document' field.
  3. Select "[Avatar CWS] Progress Notes (Group and Individual) (CWSPN22000)" in the 'Care Record Form to Map' field.
  4. Select "Activities" in the 'Note Type to Map' field.
  5. Validate the 'CCDA Document Title' field contains "Progress Note".
  6. Select "Social History" in the 'Standard Sections To Include To CCD' field.
  7. Select "Yes" in the 'Enabled' field.
  8. Click [New Row] in the 'Field Settings' grid.
  9. Select "History of Present Illness" in the 'CCDA Field Name' field.
  10. Select "[Avatar CWS] Health and Review of Systems (CWS42000)" in the 'Care Record Form/Assessment' field.
  11. Select "Past History" in the 'Care Record Field Name' field.
  12. Click [Submit] and close the form.
  13. Select "Client A" and access the 'Health and Review of Systems' form.
  14. Enter the current date in the 'Assessing Date' field.
  15. Select the desired value in the 'Type of Client' field.
  16. Enter the desired value in the 'Past History' field.
  17. Select the desired value in the 'Include In Syndromic Reporting' field.
  18. Populate any other desired fields.
  19. Select "Final" in the 'Draft/Final' field.
  20. Click [Submit] and close the form.
  21. Access the 'Progress Notes (Group and Individual)' form.
  22. Select "Client A" in the 'Select Client' field.
  23. Select the existing episode in the 'Select Episode' field.
  24. Select "New Service" in the 'Progress Note For' field.
  25. Select "Activities" in the 'Note Type' field.
  26. Enter the desired value in the 'Notes Field' field.
  27. Select the desired practitioner in the 'Practitioner' field.
  28. Enter the current date in the 'Date Of Service' field.
  29. Select the desired service code in the 'Service Charge Code' field.
  30. 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.
  31. Select "External" in the 'Are you releasing to myHealthPointe or External providers?' field.
  32. Select "Final" in the 'Draft/Final' field.
  33. Click [File Note].
  34. Validate a message is displayed stating: Note Filed.
  35. Click [OK] and close the form.
  36. Access the 'CareFabric Monitor' form.
  37. Enter the current date in the 'From Date' and 'Through Date' fields.
  38. Select "Client A" in the 'Client ID' field.
  39. Select "ClinicalNoteFinalized" in the 'Event/Action Search' field.
  40. Click [View Activity Log].
  41. Validate a 'ClinicalNoteFinalized' record is displayed.
  42. Click [Click To View Record].
  43. Validate the 'documentDescription' field contains "Progress Note".
  44. Validate the 'documentID' - 'id' field contains a unique identifier.
  45. Validate the 'documentTitle' field contains "Progress Note".
  46. Validate the 'historyOfPresentIllness' field contains the 'Past History' filed in the 'Health and Review of Systems' form.
  47. Validate the 'includedSectionCodes' - 'code' field contains "Social History".
  48. Validate the 'includedSectionCodes' - 'displayName' field contains "Social History".
  49. Validate the 'isReleaseExternal' field contains "true".
  50. Validate the 'isReleaseToPatient' field contains "false".
  51. 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
  1. Access the 'Clinical Notes Mapping' form.
  2. Select "Progress Note" in the 'Type of CCDA Document' field.
  3. Select "[Avatar CWS] Progress Notes (Group and Individual) (CWSPN22000)" in the 'Care Record Form to Map' field.
  4. Select "Activities" in the 'Note Type to Map' field.
  5. Validate the 'CCDA Document Title' field contains "Progress Note".
  6. Select "Yes" in the 'Enabled' field.
  7. Click [New Row] in the 'Field Settings' grid.
  8. Select "ProgressNote" in the 'CCDA Field Name' field.
  9. Select "[Avatar CWS] Progress Notes (Group and Individual) (CWSPN22000)" in the 'Care Record Form/Assessment' field.
  10. Select "Notes Field" in the 'Care Record Field Name' field.
  11. Click [Submit] and close the form.
  12. Access the 'Progress Notes (Group and Individual)' form.
  13. Select "Client A" in the 'Select Client' field.
  14. Select the existing episode in the 'Select Episode' field.
  15. Select "Existing Appointment" in the 'Progress Note For' field.
  16. Select the existing appointment for "Client A" in the 'Note Addresses Which Existing Service/Appointment' field.
  17. Select "Activities" in the 'Note Type' field.
  18. Enter the desired value in the 'Notes Field' field.
  19. 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.
  20. Select "External" in the 'Are you releasing to myHealthPointe or External providers?' field.
  21. Select "Final" in the 'Draft/Final' field.
  22. Click [File Note].
  23. Validate the document routing image is displayed with all note details.
  24. Click [Accept].
  25. Enter the password associated to the logged in user and click [OK].
  26. Validate a message is displayed stating: Note Filed. Do you want to return to the Progress Notes form?
  27. Click [No].
  28. Access the 'CareFabric Monitor' form.
  29. Enter the current date in the 'From Date' and 'Through Date' fields.
  30. Select "Client A" in the 'Client ID' field.
  31. Select "ClinicalNoteFinalized" in the 'Event/Action Search' field.
  32. Click [View Activity Log].
  33. Validate a 'ClinicalNoteFinalized' record is displayed.
  34. Click [Click To View Record].
  35. Validate the 'notes' field contains the value entered in the 'Notes Field' field in the previous steps.
  36. Validate the 'documentDescription' field contains "Progress Note".
  37. Validate the 'documentID' - 'id' field contains a unique identifier.
  38. Validate the 'documentTitle' field contains "Progress Note".
  39. Validate the 'isReleaseExternal' field contains "true".
  40. Validate the 'isReleaseToPatient' field contains "false".
  41. Validate the 'serviceEndDate' and 'serviceStartDate' fields contain the appointment start/end date & time.
  42. 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
  1. Select "Client A" and access the 'Update Client Data' form.
  2. Select the desired value in the 'Sex' field.
  3. Enter the desired value in the 'Address - Street' field.
  4. Enter the desired value in the 'Apartment or Unit' field.
  5. Enter the desired value in the 'Zip Code' field.
  6. Enter the desired value in the 'City' field.
  7. Select the desired value in the 'State' field.
  8. Enter the desired date in the 'Address Start Date' field.
  9. Populate any other desired fields.
  10. Click [Submit].
  11. Access the 'CareFabric Monitor' form.
  12. Enter the current date in the 'From Date' and 'Through Date' fields.
  13. Enter "Client A" in the 'Client ID' field.
  14. Click [View Activity Log].
  15. Validate the 'CareFabric Monitor Report' contains a "ClientUpdated" record and select it.
  16. Click [Click To View Record].
  17. Validate the 'addresses' - 'city' field contains the value entered in the previous steps.
  18. Validate the 'addresses' - 'fromDate' field contains the 'Address Start Date' entered in the previous steps.
  19. Validate the 'addresses' - 'stateCode' field contains the value entered in the previous steps.
  20. Validate the 'addresses' - 'street1' field contains the value entered in the previous steps.
  21. Validate the 'addresses' - 'street2' field contains the value entered in the previous steps.
  22. Validate the 'addresses' - 'zipCode' field contains the value entered in the previous steps.
  23. Validate the 'addresses' - 'typeCode' - 'code' field contains "H".
  24. Validate the 'addresses' - 'typeCode' - 'codeSystem' field contains "2.16.840.1.113883.4.642.3.67".
  25. Validate the 'addresses' - 'typeCode' - 'codeSystemName' field contains "Address".
  26. Validate the 'addresses' - 'typeCode' - 'displayName' field contains "Home".
  27. Validate the 'birthDetails' - 'birthSexCode' - 'code' field contains the code associated to the value selected in the 'Sex' field.
  28. Validate the 'birthDetails' - 'birthSexCode' - 'displayName' field contains the value selected in the 'Sex' field.
  29. Validate any other filed data is displayed.
  30. Navigate back to the 'CareFabric Monitor Report' and select the "ClientDemographicsCreated" record.
  31. Click [Click To View Record].
  32. Validate the 'addresses' - 'city' field contains the value entered in the previous steps.
  33. Validate the 'addresses' - 'fromDate' field contains the 'Address Start Date' entered in the previous steps.
  34. Validate the 'addresses' - 'stateCode' field contains the value entered in the previous steps.
  35. Validate the 'addresses' - 'street1' field contains the value entered in the previous steps.
  36. Validate the 'addresses' - 'street2' field contains the value entered in the previous steps.
  37. Validate the 'addresses' - 'zipCode' field contains the value entered in the previous steps.
  38. Close the report and the form.
Scenario 2: Admission - Validate the 'ClientCreated' SDK event
Steps
  1. Access the 'Admission' form.
  2. Verify the 'Select Client' dialog is displayed.
  3. Enter any new value in the 'Last Name' field.
  4. Enter any new value in the 'First Name' field.
  5. Select any value in the 'Sex' field.
  6. Click [Search].
  7. Validate a "Search Results" message is displayed stating: No matches found.
  8. Click [New Client].
  9. Validate a "Client" message is displayed stating: Auto Assign Next ID Number?
  10. Click [Yes].
  11. Enter any value in the 'Date of Birth' field.
  12. Enter the current date in the 'Preadmit/Admission Date' field.
  13. Enter the current time in the 'Preadmit/Admission Time' field.
  14. Select any outpatient program in the 'Program' field.
  15. Select any value in the 'Type Of Admission' field.
  16. Select the desired practitioner in the 'Admitting Practitioner' field.
  17. Populate any other required and desired fields.
  18. Click [Submit].
  19. Access the 'CareFabric Monitor' form.
  20. Enter the current date in the 'From Date' field.
  21. Enter the current date in the 'Through Date' field.
  22. Enter the client admitted in the previous steps in the 'Client ID' field.
  23. Click [View Activity Log].
  24. Select "ClientCreated" in the 'Activity Type' field.
  25. Click [Click to View Record]
  26. Validate the 'clientID' - 'id' field contains the ID for the newly admitted client.
  27. Validate the 'birthSexCode' - 'code' field contains the code associated to the value selected in the 'Sex' field.
  28. Validate the 'birthSexCode' - 'displayName' field contains the value selected in the 'Sex' field.
  29. Validate the 'genderCode' - 'code' field contains the code associated to the value selected in the 'Sex' field.
  30. Validate the 'genderCode' - 'displayName' field contains the value selected in the 'Sex' field.
  31. Validate the 'name' fields contain the name of the newly admitted client.
  32. 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
  1. Select "Client A" and access the 'Next of Kin' form.
  2. Click [Add] if the pre-display is displayed.
  3. Enter the desired value in the 'Next Of Kin Name' field.
  4. Select the desired value in the 'Next Of Kin Relationship' field.
  5. Select the desired value in the 'Next Of Kin Living With Client' field.
  6. Populate all other desired fields.
  7. Click [Submit].
  8. Access the 'CareFabric Monitor' form.
  9. Enter the current date in the 'From Date' and 'Through Date' fields.
  10. Select "Client A" in the 'Client ID' field.
  11. Click [View Activity Log].
  12. Validate the 'CareFabric Monitor' report is displayed and contains "ClientUpdated" and "AssociatedPersonCreated" records.
  13. Click [Click To View Record] for the "AssociatedPersonCreated" record.
  14. Validate the 'associatedPersonID' - 'id' field contains a unique ID for the record.
  15. Validate the 'associatedWithClientID' - 'id' field contains the PATID for "Client A".
  16. Validate next of kin information is displayed as expected.
  17. Close the report and the form.
  18. Select "Client A" and access the 'Next of Kin' form.
  19. Click [Edit].
  20. Enter any new value in the 'Next Of Kin Name' field.
  21. Click [Submit].
  22. Access the 'CareFabric Monitor' form.
  23. Enter the current date in the 'From Date' and 'Through Date' fields.
  24. Select "Client A" in the 'Client ID' field.
  25. Click [View Activity Log].
  26. Validate the 'CareFabric Monitor' report is displayed and contains "ClientUpdated" and "AssociatedPersonUpdated" records.
  27. Click [Click To View Record] for the "AssociatedPersonUpdated" record.
  28. Validate the 'associatedPersonID' - 'id' field contains a unique ID for the record.
  29. Validate the 'associatedWithClientID' - 'id' field contains the PATID for "Client A".
  30. Validate the updated next of kin information is displayed as expected.
  31. Close the report and the form.
  32. Select "Client A" and access the 'Next of Kin' form.
  33. Click [Delete] and [Yes].
  34. Access the 'CareFabric Monitor' form.
  35. Enter the current date in the 'From Date' and 'Through Date' fields.
  36. Select "Client A" in the 'Client ID' field.
  37. Click [View Activity Log].
  38. Validate the 'CareFabric Monitor' report is displayed and contains "ClientUpdated" and "AssociatedPersonDeleted" records.
  39. Click [Click To View Record] for the "AssociatedPersonDeleted" record.
  40. Validate the 'associatedPersonID' - 'id' field contains a unique ID for the deleted record.
  41. 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
  1. Select "Client A" and access the 'Next of Kin' form.
  2. Click [Add] if the pre-display is displayed.
  3. Enter the desired value in the 'Next Of Kin Name' field.
  4. Select the desired value in the 'Next Of Kin Relationship' field.
  5. Select the desired value in the 'Next Of Kin Living With Client' field.
  6. Populate all other desired fields.
  7. Click [Submit].
  8. Access the 'CareFabric Monitor' form.
  9. Enter the current date in the 'From Date' and 'Through Date' fields.
  10. Select "Client A" in the 'Client ID' field.
  11. Click [View Activity Log].
  12. Validate the 'CareFabric Monitor' report is displayed and contains "ClientUpdated" and "AssociatedPersonCreated" records.
  13. Click [Click To View Record] for the "ClientUpdated" record.
  14. Validate the 'clientID' - 'id' field contains the PATID for "Client A".
  15. Validate the 'name' - 'first' field contains the first name for "Client A".
  16. Validate the 'name' - 'last' field contains the last name for "Client A".
  17. 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
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
  1. Access the 'System Task Scheduler' form.
  2. Select "Avatar CareFabric - Send Facility Bed Information (HL-7) Recurrence Pattern : Hourly -Inactive" in the 'Schedule(s)' field.
  3. Validate "Hourly" is selected in the 'Recurrence Pattern' field.
  4. Validate the 'Start Time' field contains "12:00 AM".
  5. Validate the 'End Time' field contains "11:59 PM".
  6. Validate "Yes" is selected in the 'Inactive Task' field.
  7. Enter the current date in the 'Start By' field.
  8. Select "No" in the 'Inactive Task' field.
  9. Click [Schedule Task] and close the form.
  10. Wait for the task to run.
  11. Access the 'CareFabric Monitor' form.
  12. Enter the current date in the 'From Date' and 'Through Date' fields.
  13. Select "ClientUpdated" in the 'Event/Action Search' field.
  14. Click [View Activity Log].
  15. Validate the 'CareFabric Monitor Report' is displayed with a "ClientUpdated" record for each unit configured in the pre-conditions.
  16. Click [Click To View Record] for the first record.
  17. Validate the 'assignedFacilityInformation' - 'facilityMneumonic' field contains the value defined in the "(22055) Facility Abbreviation" extended dictionary element for the unit.
  18. 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.
  19. Validate the 'assignedFacilityInformation' - 'levelOfCareCode' - 'displayName' field contains the value selected in the "(22056) Level of Care" extended dictionary element for the unit.
  20. Validate the 'assignedFacilityInformation' - 'totalNumberOfBeds' field contains the total number of beds in the unit.
  21. Validate the 'assignedFacilityInformation' - 'totalNumberOfBedsOccupied' field contains the total number of occupied beds in the unit.
  22. Validate the 'clientID' - 'id' field contains "NO_ID".
  23. Validate the 'name' - 'first' field contains "NO_NAME".
  24. Validate the 'name' - 'last' field contains "NO_LASTNAME".
  25. Navigate back to the 'CareFabric Monitor Report' and repeat steps 3e-3m as needed for the additional units that are configured.
  26. 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
  1. Access the 'Dictionary Update' PM form.
  2. Select "Client" in the 'File' field.
  3. Select "Data Element Number" in the 'Data Element' field.
  4. Select "(202) Unit" in the 'Data Element' field.
  5. Enter the code associated to "Unit A" in the 'Dictionary Code' field.
  6. Validate "Unit A" is displayed in the 'Dictionary Value' field.
  7. Select "(22055) Facility Abbreviation" in the 'Extended Dictionary Data Element' field.
  8. Validate the 'Extended Dictionary Value (Free Text)' field is now enabled. Enter the desired value.
  9. Select "(22056) Level of Care" in the 'Extended Dictionary Data Element' field.
  10. Validate the 'Extended Dictionary Value (Single Dictionary)' field is now enabled and contains the following values:
  11. Inpatient
  12. Observation
  13. Outpatient
  14. Select the desired value in the 'Extended Dictionary Value (Single Dictionary)' field.
  15. Click [Apply Changes].
  16. Validate a message is displayed stating: Filed!
  17. Click [OK] and close the form.
  18. Access the 'Admission' form
  19. Verify the 'Select Client' dialog is displayed.
  20. Enter any new value in the 'Last Name' field.
  21. Enter any new value in the 'First Name' field.
  22. Select any value in the 'Sex' field.
  23. Click [Search].
  24. Validate a "Search Results" message is displayed stating: No matches found.
  25. Click [New Client].
  26. Validate a "Client" message is displayed stating: Auto Assign Next ID Number?
  27. Click [Yes].
  28. Enter any value in the 'Date of Birth' field.
  29. Enter the current date in the 'Preadmit/Admission Date' field.
  30. Enter the current time in the 'Preadmit/Admission Time' field.
  31. Select any inpatient program in the 'Program' field.
  32. Select any value in the 'Type Of Admission' field.
  33. Select any value in the 'Source Of Admission' field.
  34. Enter the desired practitioner in the 'Admitting Practitioner' field.
  35. Enter the desired practitioner in the 'Attending Practitioner' field.
  36. Select the "Inpatient/Partial/Day Treatment" section.
  37. Select "Unit A" in the 'Unit' field.
  38. Select the desired room in the 'Room' field.
  39. Select the desired bed in the 'Bed' field.
  40. Select the desired value in the 'Room And Board Billing Code' field.
  41. Submit the form. Note: this will now be referred to as "Client A".
  42. Access the 'CareFabric Monitor' form.
  43. Enter the current date in the 'From Date' and 'Through Date' fields.
  44. Select "Client A" in the 'Client ID' field.
  45. Click [View Activity Log].
  46. Validate the 'CareFabric Monitor' report is displayed and contains "ClientCreated" record.
  47. Click [Click To View Record] for the "ClientCreated" record.
  48. Validate the 'assignedFacilityInformation' - 'facilityMneumonic' field contains the value defined in the "(22055) Facility Abbreviation" extended dictionary element for "Unit A".
  49. 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".
  50. Validate the 'assignedFacilityInformation' - 'levelOfCareCode' - 'displayName' field contains the value selected in the "(22056) Level of Care" extended dictionary element for "Unit A".
  51. Validate the 'assignedFacilityInformation' - 'totalNumberOfBeds' field contains the total number of beds in "Unit A".
  52. Validate the 'assignedFacilityInformation' - 'totalNumberOfBedsOccupied' field contains the total number of occupied beds in "Unit A".
  53. Close the report and the form.
  54. Select "Client A" and access the 'Update Client Data' form.
  55. Enter the desired value in the 'Date Of Birth' field.
  56. Click [Submit].
  57. Access the 'CareFabric Monitor' form.
  58. Enter the current date in the 'From Date' and 'Through Date' fields.
  59. Select "Client A" in the 'Client ID' field.
  60. Click [View Activity Log].
  61. Validate the 'CareFabric Monitor' report is displayed and contains "ClientUpdated" record.
  62. Click [Click To View Record] for the "ClientUpdated" record.
  63. Validate the 'assignedFacilityInformation' - 'facilityMneumonic' field contains the value defined in the "(22055) Facility Abbreviation" extended dictionary element for "Unit A".
  64. 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".
  65. Validate the 'assignedFacilityInformation' - 'levelOfCareCode' - 'displayName' field contains the value selected in the "(22056) Level of Care" extended dictionary element for "Unit A".
  66. Validate the 'assignedFacilityInformation' - 'totalNumberOfBeds' field contains the total number of beds in "Unit A".
  67. Validate the 'assignedFacilityInformation' - 'totalNumberOfBedsOccupied' field contains the total number of occupied beds in "Unit A".
  68. Validate the 'birthDate' field contains the 'Date Of Birth' filed in the previous steps.
  69. Close the report and the form.
  70. Select "Client A" and access the 'Discharge' form.
  71. Enter the desired date in the 'Date Of Discharge' field.
  72. Enter the desired time in the 'Time Of Discharge' field.
  73. Select the desired value in the 'Type Of Discharge' field.
  74. Select the desired value in the 'Discharge Practitioner' field.
  75. Click [Submit].
  76. Access the 'CareFabric Monitor' form.
  77. Enter the current date in the 'From Date' and 'Through Date' fields.
  78. Select "Client A" in the 'Client ID' field.
  79. Click [View Activity Log].
  80. Validate the 'CareFabric Monitor' report is displayed and contains "ClientUpdated" record.
  81. Click [Click To View Record] for the "ClientUpdated" record.
  82. Validate the 'assignedFacilityInformation' field contains "null".
  83. Validate the 'birthDate' field contains the 'Date Of Birth' filed in the previous steps.
  84. 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
  1. Access the 'CarePOV Management' form.
  2. Validate the 'Submit' button is disabled.
  3. Validate a [Submit 'CarePOV Management'] button is displayed.
  4. Select any desired values and click [Submit 'CarePOV Management'].
  5. Validate a message is displayed stating: Saved.
  6. Click [OK].
  7. Validate successful form submission.
  8. Access the 'CarePOV Management' form.
  9. Validate previously saved values are displayed.
  10. Select the "Bed Board - POV" section.
  11. Validate the 'Submit' button is disabled.
  12. Validate a [Submit 'Bed Board - POV'] button is displayed.
  13. Select any desired values and click [Submit 'Bed Board - POV'].
  14. Validate a message is displayed stating: Saved.
  15. Click [OK].
  16. Validate successful form submission.
  17. Access the 'CarePOV Management' form.
  18. Select the "Bed Board - POV" section.
  19. Validate previously saved values are displayed.
  20. Select the "Electronic Visit Verification" section.
  21. Validate the 'Submit' button is disabled.
  22. Validate a [Submit 'Electronic Visit Verification'] button is displayed.
  23. Select any desired values and click [Submit 'Electronic Visit Verification'].
  24. Validate a message is displayed stating: Saved.
  25. Click [OK].
  26. Validate successful form submission.
  27. Access the 'CarePOV Management' form.
  28. Select the "Electronic Visit Verification" section.
  29. Validate previously saved values are displayed.
  30. Select the "Client Alerts" section.
  31. Validate the 'Submit' button is disabled.
  32. Validate the [Save] button is displayed. Note: this button is existing functionality and remains unchanged.
  33. Select the "Lab Results Flowsheet Mapping" section.
  34. Validate the 'Submit' button is disabled.
  35. Validate the [Save] button is displayed. Note: this button is existing functionality and remains unchanged.
  36. Select the "Group Check In" section.
  37. Validate the 'Submit' button is disabled.
  38. Validate the [Submit 'Group Check In'] button is displayed.
  39. Enter any desired values and click [Submit 'Group Check In'].
  40. Validate a message is displayed stating: Saved.
  41. Click [OK].
  42. Validate successful form submission.
  43. Access the 'CarePOV Management' form.
  44. Select the "Group Check In" section.
  45. Validate previously saved values are displayed.
  46. Select the "Bells Notes" section.
  47. Validate the 'Submit' button is disabled.
  48. 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.
  49. Select the "Telehealth" section.
  50. Validate the 'Submit' button is disabled.
  51. Validate the [Submit 'Telehealth'] button is displayed.
  52. Enter the desired value and click [Submit 'Telehealth'].
  53. Validate a message is displayed stating: Saved.
  54. Click [OK].
  55. Validate successful form submission.
  56. Access the 'CarePOV Management' form.
  57. Select the "Telehealth" section.
  58. Validate previously saved values are displayed.
  59. 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
  1. Access the 'Client Alternate Addresses' form.
  2. Select "Client A" in the 'Client' field.
  3. Select "Add" in the 'Add/Edit' field.
  4. Enter the desired value in the 'Description' field.
  5. Enter the desired date in the 'Address Start Date' field.
  6. Enter the desired date in the 'Address End Date' field.
  7. Enter the desired value in the 'Address Line 1' field.
  8. Enter the desired value in the 'Address Line 2' field.
  9. Enter the desired value in the 'Zip' field.
  10. Enter the desired value in the 'City' field.
  11. Select the desired value in the 'State' field.
  12. Enter the desired value in the 'Contact Name field.
  13. Enter the desired value in the 'Contact Phone' field.
  14. Enter the desired value in the 'Address Notes' field.
  15. Select the desired value in the 'Address Type' field. Please note: this will display values defined in the '(10006) Location' dictionary.
  16. Select "Yes" in the 'Enabled' field.
  17. Click [File].
  18. Validate a message is displayed stating: Saved.
  19. Click [OK].
  20. Validate the 'Client' field contains "Client A".
  21. Select "Edit" in the 'Add/Edit' field.
  22. 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'.
  23. Select the address filed in the previous steps in the 'Select Existing Address' field.
  24. Validate all previously filed data is displayed.
  25. Close the form.
  26. Access Crystal Reports or other SQL Reporting Tool.
  27. Select the PM namespace.
  28. Create a report using the 'SYSTEM.client_alternate_address' SQL table.
  29. Validate there is a row for "Client A" will all previously filed data.
  30. Validate the 'addr_type_code' and 'addr_type_value' fields contain the code/value filed in the previous steps.
  31. 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
  1. Access the 'CarePOV Management' form.
  2. Select the "Electronic Visit Verification" section.
  3. Validate the 'Require Address Type' field is displayed with "Yes" and "No" values. The default value will be "No".
  4. Validate the 'Default Address Type for Client Demographics' field is displayed with values from the '(10006) Location' dictionary.
  5. Select "Yes" in the 'Require Address Type' field.
  6. Validate the 'Default Address Type for Client Demographics' field becomes required.
  7. Select the desired value in the 'Default Address Type for Client Demographics' field.
  8. Click [Submit 'Electronic Visit Verification'].
  9. Validate a message is displayed stating: Saved.
  10. Click [OK].
  11. Validate successful submission.
  12. Access the 'Client Alternate Addresses' form.
  13. Select "Add" in the 'Add/Edit' field.
  14. Enter the desired value in the 'Description' field.
  15. Enter the desired date in the 'Address Start Date' field.
  16. Enter the desired date in the 'Address End Date' field.
  17. Enter the desired value in the 'Address Line 1' field.
  18. Enter the desired value in the 'Address Line 2' field.
  19. Enter the desired value in the 'Zip' field.
  20. Enter the desired value in the 'City' field.
  21. Select the desired value in the 'State' field.
  22. Enter the desired value in the 'Contact Name field.
  23. Enter the desired value in the 'Contact Phone' field.
  24. Enter the desired value in the 'Address Notes' field.
  25. Validate the 'Address Type' field is required.
  26. Select the desired value in the 'Address Type' field. Please note: this will display values defined in the '(10006) Location' dictionary.
  27. Select "Yes" in the 'Enabled' field.
  28. Click [File].
  29. Validate a message is displayed stating: Saved.
  30. Click [OK] and close the form.
  31. Access the 'CarePOV Management' form.
  32. Select the "Electronic Visit Verification" section.
  33. Validate the previously selected values are displayed.
  34. Select "No" in the 'Require Address Type' field.
  35. Validate the 'Default Address Type for Client Demographics' field is no longer required.
  36. Remove the value from the 'Default Address Type for Client Demographics' field.
  37. Click [Submit 'Electronic Visit Verification'].
  38. Validate a message is displayed stating: Saved.
  39. Click [OK].
  40. Validate successful submission.
  41. Access the 'Client Alternate Addresses' form.
  42. Select "Edit" in the 'Add/Edit' field.
  43. 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'.
  44. Select the address filed in the previous steps in the 'Select Existing Address' field.
  45. Validate all previously filed data is displayed.
  46. Validate the 'Address Type' field is no longer required.
  47. Remove the value from the 'Address Type' field.
  48. Click [File].
  49. Validate a message is displayed stating: Saved.
  50. 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
  1. Access the 'CarePOV Management' form.
  2. Select the "Electronic Visit Verification" section.
  3. Select "Site A" in the 'Site' field.
  4. Click [Submit].
  5. Add an unscheduled visit in the Mobile CareGiver+ application with associated tasks for "Client A" with "Practitioner A".
  6. 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.
  7. Access the 'CareFabric Monitor' form.
  8. Enter the current date in the 'From Date' and 'Through Date' fields.
  9. Select "Client A" in the 'Client ID' field.
  10. Select "McgEvvAppointmentUpdated' in the 'Event/Action Search' field.
  11. Click [View Activity Log].
  12. Validate the 'CareFabric Monitor Report' contains an "McgEvvAppointmentUpdated" record.
  13. Click [Click To View Record].
  14. Validate the 'clientID- 'id' field contains "Client A".
  15. Validate the 'endDate' field contains the appointment end date/time.
  16. Validate the 'mcgAppointmentID' - 'id' field contains the MCG+ unique identifier for the appointment.
  17. Validate the 'resource' - 'resourceID' field contains "Practitioner A".
  18. Validate the 'services' - 'procedureCode' - 'code' field contains "Procedure Code A".
  19. Validate the 'startDate' field contains the appointment start date/time.
  20. Validate all other appointment data is displayed.
  21. Close the report and the form.
  22. Access the 'Scheduling Calendar' form.
  23. Validate the appointment for "Client A" with "Practitioner A" that was sent from Mobile CareGiver+ is displayed at "Site A".
  24. Right click on the appointment and click [Details/Edit].
  25. Validate the appointment details are displayed as expected.
  26. Validate the 'Available Tasks' field contains the tasks sent from Mobile CareGiver+.
  27. 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
  1. Access the 'Dictionary Update' PM form.
  2. Select "Client" in the 'File' field.
  3. Select "(10006) Location" in the 'Data Element' field.
  4. Enter the desired value in the 'Dictionary Code' field.
  5. Enter "MCG+ Alternate Location" in the 'Dictionary Value' field.
  6. Select "(587) Place Of Service (Mobile CareGiver+)" in the 'Extended Dictionary Data Element' field.
  7. Select "(53) Community Mental Health Center" (or any other non "Home" value) in the 'Extended Dictionary Value (Single Dictionary)' field.
  8. Select "(579) Place Of Service (837 Electronic Billing)" in the 'Extended Dictionary Data Element' field.
  9. Select "Other Unlisted Facility" (or any other non "Home" value) in the 'Extended Dictionary Value (Single Dictionary)' field.
  10. Select "(578) Place Of Service (HCFA 24-B)" in the 'Extended Dictionary Data Element' field.
  11. Select "Other Unlisted Facility" (or any other non "Home" value) in the 'Extended Dictionary Value (Single Dictionary)' field.
  12. Click [Apply Changes].
  13. Validate a message is displayed stating: Filed!
  14. Click [OK] and close the form.
  15. Access the 'Client Alternate Addresses' form.
  16. Select "Client A" in the 'Client' field.
  17. Select "Add" in the 'Add/Edit' field.
  18. Enter "Inactive Alternate Address" in the 'Description' field.
  19. Enter the desired date in the 'Address Start Date' field.
  20. Enter the desired date in the 'Address Line 1' field.
  21. Enter the desired value in the 'Zip' field.
  22. Enter the desired value in the 'City' field.
  23. Select the desired value in the 'State' field.
  24. Select "MCG+ Alternate Location" in the 'Address Type' field.
  25. Select "No" in the 'Enabled' field.
  26. Click [File].
  27. Validate a message is displayed stating: Saved.
  28. Click [OK].
  29. Select "Add" in the 'Add/Edit' field.
  30. Enter "Active Alternate Address" in the 'Description' field.
  31. Enter the desired date in the 'Address Start Date' field.
  32. Enter the desired date in the 'Address Line 1' field.
  33. Enter the desired value in the 'Zip' field.
  34. Enter the desired value in the 'City' field.
  35. Select the desired value in the 'State' field.
  36. Select "MCG+ Alternate Location" in the 'Address Type' field.
  37. Select "Yes" in the 'Enabled' field.
  38. Click [File].
  39. Validate a message is displayed stating: Saved.
  40. Click [OK] and close the form.
  41. Access the 'CareFabric Monitor' form.
  42. Enter the current date in the 'From Date' and 'Through Date' fields.
  43. Select "Client A" in the 'Client ID' field.
  44. Select "EvvClientUpdated" in the 'Event/Action Search' field.
  45. Click [View Activity Log].
  46. Validate the 'CareFabric Monitor Report' contains an "EvvClientUpdated" record for "Client A".
  47. Click [Click to View Record].
  48. Validate the 'addresses' section contains only the "Active Alternate Address" and the client's home address defined in demographics.
  49. 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
  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 'auditInformation' - 'lastUpdatedByStaffMemberID' - 'id' field contains the logged in user ID.
  21. Validate the 'auditInformation' - 'lastUpdatedDate' field contains the date/time the appointment was scheduled.
  22. Validate the 'appointmentID' - 'id' field contains the appointment ID.
  23. Validate the 'canceledDate' field contains "null".
  24. Validate the 'canceledReasonCode' field contains "null".
  25. Validate the 'providerOrganizationID' - 'id' field contains the 'Provider Organization ID' assigned to "Program A".
  26. Validate the 'clientID' - 'id' field contains the ID for "Client A".
  27. Validate the 'diagnosisCodes' - 'code' field contains the diagnosis code on file for "Client A".
  28. Validate the 'diagnosisCodes' - 'displayName' field contains the diagnosis value on file for "Client A".
  29. Validate the 'endDate' field contains the appointment end date/time.
  30. Validate the 'insPayerID' - 'id' field contains the 'MCG+ Payer ID' on file in the 'CarePOV Management' form for "Guarantor A".
  31. Validate the 'insPlanID' - 'id' field contains the 'MCG+ Insurance Plan ID' on file in the 'CarePOV Management' form for "Guarantor A".
  32. Validate the 'isEVV' field contains "true".
  33. Validate the 'locationOfService' fields contain "Client A's" home address.
  34. Validate the 'mcgInsPayerID' - 'id' field contains the 'MCG+ Payer ID' on file in the 'CarePOV Management' form for "Guarantor A".
  35. Validate the 'mcgInsPlanID' - 'id' field contains the 'MCG+ Insurance Plan ID' on file in the 'CarePOV Management' form for "Guarantor A".
  36. Validate the 'services' - 'description' field contains the description for "Service Code A".
  37. Validate the 'services' - 'name' field contains the code for "Service Code A".
  38. Validate the 'services' - 'procedureCode' - 'code' field contains the code for "Procedure A".
  39. Validate the 'services' - 'procedureCode' - 'displayName' field contains the name for "Procedure A".
  40. Validate the 'serviceID' - 'id' field contains the code for "Service Code A".
  41. Validate the 'tasks' - 'taskCode' fields contain the value(s) selected in the 'Available Tasks' field when scheduling the appointment.
  42. Validate the 'startDate' field contains the appointment start date/time.
  43. Validate all other relevant information is displayed for "Client A" and "Practitioner A".
  44. 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
  1. Access the 'CarePOV Management' form.
  2. Select the "Electronic Visit Verification" section.
  3. Select "Site A" in the 'Site' field.
  4. Click [Submit].
  5. Add an unscheduled visit in the Mobile CareGiver+ application with associated tasks for "Client A" with "Practitioner A".
  6. 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.
  7. Access the 'CareFabric Monitor' form.
  8. Enter the current date in the 'From Date' and 'Through Date' fields.
  9. Select "Client A" in the 'Client ID' field.
  10. Select "McgEvvAppointmentUpdated' in the 'Event/Action Search' field.
  11. Click [View Activity Log].
  12. Validate the 'CareFabric Monitor Report' contains an "McgEvvAppointmentUpdated" record.
  13. Click [Click To View Record].
  14. Validate the 'clientID- 'id' field contains "Client A".
  15. Validate the 'endDate' field contains the appointment end date/time.
  16. Validate the 'mcgAppointmentID' - 'id' field contains the MCG+ unique identifier for the appointment.
  17. Validate the 'resource' - 'resourceID' field contains "Practitioner A".
  18. Validate the 'services' - 'procedureCode' - 'code' field contains "Procedure Code A".
  19. Validate the 'startDate' field contains the appointment start date/time.
  20. Validate all other appointment data is displayed.
  21. Close the report and the form.
  22. Access the 'Scheduling Calendar' form.
  23. Validate the appointment for "Client A" with "Practitioner A" that was sent from Mobile CareGiver+ is displayed at "Site A".
  24. Right click on the appointment and click [Details/Edit].
  25. Validate the appointment details are displayed as expected.
  26. Validate the 'Available Tasks' field contains the tasks sent from Mobile CareGiver+.
  27. 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
  1. Access the 'Scheduling Calendar' form.
  2. Right click in any available future 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. Populate all other required and desired fields.
  8. Click [Submit].
  9. Validate the new appointment is displayed.
  10. Click [Dismiss].
  11. Access the 'CareFabric Monitor' form.
  12. Enter the current date in the 'From Date' and 'Through Date' fields.
  13. Select "Client A" in the 'Client ID' field.
  14. Select "EvvAppointmentUpdated' in the 'Event/Action Search' field.
  15. Click [View Activity Log].
  16. Validate the 'CareFabric Monitor Report' contains an "EvvAppointmentUpdated" record.
  17. Click [Click To View Record].
  18. Validate the 'appointmentAuthorization' field contains "null".
  19. Validate the 'auditInformation' - 'lastUpdatedByStaffMemberID' - 'id' field contains the logged in user ID.
  20. Validate the 'auditInformation' - 'lastUpdatedDate' field contains the date/time the appointment was scheduled.
  21. Validate the 'appointmentID' - 'id' field contains the appointment ID.
  22. Validate the 'canceledDate' field contains "null".
  23. Validate the 'canceledReasonCode' field contains "null".
  24. Validate the 'providerOrganizationID' - 'id' field contains the 'Provider Organization ID' assigned to "Program A".
  25. Validate the 'clientID' - 'id' field contains the ID for "Client A".
  26. Validate the 'diagnosisCodes' - 'code' field contains the diagnosis code on file for "Client A".
  27. Validate the 'diagnosisCodes' - 'displayName' field contains the diagnosis value on file for "Client A".
  28. Validate the 'endDate' field contains the appointment end date/time.
  29. Validate the 'insPayerID' - 'id' field contains the 'MCG+ Payer ID' on file in the 'CarePOV Management' form for "Guarantor A".
  30. Validate the 'insPlanID' - 'id' field contains the 'MCG+ Insurance Plan ID' on file in the 'CarePOV Management' form for "Guarantor A".
  31. Validate the 'isEVV' field contains "true".
  32. Validate the 'locationOfService' fields contain "Client A's" home address.
  33. Validate the 'mcgInsPayerID' - 'id' field contains the 'MCG+ Payer ID' on file in the 'CarePOV Management' form for "Guarantor A".
  34. Validate the 'mcgInsPlanID' - 'id' field contains the 'MCG+ Insurance Plan ID' on file in the 'CarePOV Management' form for "Guarantor A".
  35. Validate the 'services' - 'description' field contains the description for "Service Code A".
  36. Validate the 'services' - 'name' field contains the code for "Service Code A".
  37. Validate the 'services' - 'procedureCode' - 'code' field contains the code for "Procedure A".
  38. Validate the 'services' - 'procedureCode' - 'displayName' field contains the name for "Procedure A".
  39. Validate the 'serviceID' - 'id' field contains the code for "Service Code A".
  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.
  43. Access the 'Scheduling Calendar' form.
  44. Right click on the appointment for "Client A".
  45. Click [Status Update].
  46. Select "Cancelled" in the 'Appointment Status' field.
  47. Validate the 'Cancellation Reason' field is not required.
  48. Click [Submit] and [Dismiss].
  49. Access the 'CareFabric Monitor' form.
  50. Enter the current date in the 'From Date' and 'Through Date' fields.
  51. Select "Client A" in the 'Client ID' field.
  52. Select "EvvAppointmentUpdated' in the 'Event/Action Search' field.
  53. Click [View Activity Log].
  54. Validate the 'CareFabric Monitor Report' contains an "EvvAppointmentUpdated" record.
  55. Click [Click To View Record].
  56. Validate the 'auditInformation' - 'lastUpdatedByStaffMemberID' - 'id' field contains the logged in user ID.
  57. Validate the 'auditInformation' - 'lastUpdatedDate' field contains the date/time the appointment was cancelled.
  58. Validate the 'canceledDate' field contains the canceled date/time.
  59. Validate the 'canceledReasonCode' field contains "null".
  60. 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
  1. Access the 'Dictionary Update' PM form.
  2. Select "Client" in the 'File' field.
  3. Select "(10006) Location" in the 'Data Element' field.
  4. Enter the desired value in the 'Dictionary Code' field.
  5. Enter "MCG+ Alternate Location" in the 'Dictionary Value' field.
  6. Select "(587) Place Of Service (Mobile CareGiver+)" in the 'Extended Dictionary Data Element' field.
  7. Select "(53) Community Mental Health Center" (or any other non "Home" value) in the 'Extended Dictionary Value (Single Dictionary)' field.
  8. Select "(579) Place Of Service (837 Electronic Billing)" in the 'Extended Dictionary Data Element' field.
  9. Select "Other Unlisted Facility" (or any other non "Home" value) in the 'Extended Dictionary Value (Single Dictionary)' field.
  10. Select "(578) Place Of Service (HCFA 24-B)" in the 'Extended Dictionary Data Element' field.
  11. Select "Other Unlisted Facility" (or any other non "Home" value) in the 'Extended Dictionary Value (Single Dictionary)' field.
  12. Click [Apply Changes].
  13. Validate a message is displayed stating: Filed!
  14. Click [OK] and close the form.
  15. Access the 'Client Alternate Addresses' form.
  16. Select "Client A" in the 'Client' field.
  17. Select "Add" in the 'Add/Edit' field.
  18. Enter "Alternate Address Test" in the 'Description' field.
  19. Enter the desired value in the 'Address Line 1' field.
  20. Enter the desired date in the 'Address Start Date' field.
  21. Enter the desired value in the 'Zip' field.
  22. Enter the desired value in the 'Contact Name' field.
  23. Enter the desired value in the 'Contact Phone' field.
  24. Enter the desired value in the 'Address Notes' field.
  25. Select "MCG+ Alternate Location" in the 'Address Type' field.
  26. Select "Yes" in the 'Enabled' field.
  27. Click [File].
  28. Validate a message is displayed stating: Saved.
  29. Click [OK] and close the form.
  30. Access the 'Scheduling Calendar' form.
  31. Right click in any available future time slot for "Practitioner A" and click [Add Appointment].
  32. Select "Service Code A" in the 'Service Code' field.
  33. Select "Client A" in the 'Client' field.
  34. Validate the 'Program' field contains "Program A".
  35. Select "MCG+ Alternate Location" in the 'Location' field.
  36. Validate the 'Select Address of Service' field is displayed and does not contain any value, by default.
  37. Click [Submit].
  38. Validate a message is displayed stating: Mobile CareGiver+: Missing Client Information: Location (LocationOfService) is missing.
  39. 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.
  40. Click [OK].
  41. Validate the 'Select Address of Service' field contains "Primary Address (Demographics)" and "Alternate Address Test".
  42. Select "Alternate Address Test" in the 'Select Address of Service' field.
  43. Click [Submit].
  44. Validate the new appointment is displayed.
  45. Click [Dismiss].
  46. Access the 'CareFabric Monitor' form.
  47. Enter the current date in the 'From Date' and 'Through Date' fields.
  48. Select "Client A" in the 'Client ID' field.
  49. Select "EvvAppointmentUpdated" in the 'Event/Action Search' field.
  50. Click [View Activity Log].
  51. Validate the 'CareFabric Monitor Report' contains an "EvvAppointmentUpdated" record.
  52. Click [Click To View Record].
  53. Validate the 'locationOfService' fields contain "Client A's" alternate address values (Alternate Address Test).
  54. Validate the 'locationOfService' - 'typeCode' - 'code' field contains the code selected for the '(587) Place Of Service (Mobile CareGiver+)' extended dictionary data element.
  55. Validate the 'locationOfService' - 'typeCode' - 'displayName' field contains the value selected for the '(587) Place Of Service (Mobile CareGiver+)' extended dictionary data element.
  56. Validate all other data displays as expected.
  57. Close the report and the form.
  58. Access the 'Client Alternate Addresses' form.
  59. Select "Client A" in the 'Client' field.
  60. Select "Edit" in the 'Add/Edit' field.
  61. Select "Alternate Address Test" in the 'Select Existing Address' field.
  62. Enter the desired new value in the 'Address Line 1' field.
  63. Click [File].
  64. Validate a message is displayed stating: Saved.
  65. Click [OK] and close the form.
  66. Access the 'CareFabric Monitor' form.
  67. Enter the current date in the 'From Date' and 'Through Date' fields.
  68. Select "Client A" in the 'Client ID' field.
  69. Select "EvvAppointmentUpdated" in the 'Event/Action Search' field.
  70. Click [View Activity Log].
  71. Validate the 'CareFabric Monitor Report' contains an "EvvAppointmentUpdated" record.
  72. Click [Click To View Record].
  73. Validate the 'locationOfService' fields contain "Client A's" new alternate address values.
  74. Validate the 'locationOfService' - 'typeCode' - 'code' field contains the code selected for the '(587) Place Of Service (Mobile CareGiver+)' extended dictionary data element.
  75. Validate the 'locationOfService' - 'typeCode' - 'displayName' field contains the value selected for the '(587) Place Of Service (Mobile CareGiver+)' extended dictionary data element.
  76. Validate all other data displays as expected.
  77. 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
  1. Add an unscheduled visit in the Mobile CareGiver+ application for "Client A" with "Practitioner A", using "Alternate Address A" as the location of service.
  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 'CareFabric Monitor' form.
  4. Enter the current date in the 'From Date' and 'Through Date' fields.
  5. Select "Client A" in the 'Client ID' field.
  6. Select "McgEvvAppointmentUpdated' in the 'Event/Action Search' field.
  7. Click [View Activity Log].
  8. Validate the 'CareFabric Monitor Report' contains an "McgEvvAppointmentUpdated" record.
  9. Click [Click To View Record].
  10. Validate the 'clientID- 'id' field contains "Client A".
  11. Validate the 'endDate' field contains the appointment end date/time.
  12. Validate the 'mcgAppointmentID' - 'id' field contains the MCG+ unique identifier for the appointment.
  13. Validate the 'resource' - 'resourceID' field contains "Practitioner A".
  14. Validate the 'services' - 'procedureCode' - 'code' field contains "Procedure Code A".
  15. Validate the 'locationOfService' fields contain "Alternate Address A".
  16. Validate the 'startDate' field contains the appointment start date/time.
  17. Validate all other appointment data is displayed.
  18. Close the report and the form.
  19. Access the 'Scheduling Calendar' form.
  20. Validate the appointment for "Client A" with "Practitioner A" that was sent from Mobile CareGiver+ is displayed at "Site A".
  21. Right click on the appointment and click [Details/Edit].
  22. Validate the appointment details are displayed as expected.
  23. Validate the 'Location' field contains the location associated to "Alternate Address A".
  24. Validate the 'Select Address of Service' field contains "Alternate Address A".
  25. 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
  1. 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.
  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 'CareFabric Monitor' form.
  4. Enter the current date in the 'From Date' and 'Through Date' fields.
  5. Select "McgEvvAppointmentUpdated" in the 'Event/Action Search' field.
  6. Click [View Activity Log].
  7. Validate the 'CareFabric Monitor Report' contains an "McgEvvAppointmentUpdated" record.
  8. Click [Click To View Record].
  9. Validate the 'endDate' field contains the appointment end date/time.
  10. Validate the 'isMultipleRecipients' field contains "true".
  11. Validate the 'mcgAppointmentID' - 'id' field contains the MCG+ unique identifier for the appointment.
  12. Validate the 'resource' - 'resourceID' field contains "Practitioner A".
  13. Validate the first - 'services' - 'clientID- 'id' field contains "Client A".
  14. Validate the first 'services' - 'procedureCode' - 'code' field contains "Procedure Code A".
  15. Validate the second 'services' - 'clientID' - 'id' field contains "Client B".
  16. Validate the second 'services' - 'procedureCode' - 'code' field contains "Procedure Code A".
  17. Validate the 'locationOfService' fields contain the primary home address for "Client A".
  18. Validate the 'startDate' field contains the appointment start date/time.
  19. Validate all other appointment data is displayed.
  20. Close the report and the form.
  21. Access the 'Scheduling Calendar' form.
  22. Validate an appointment for "Client A" and "Client B" with "Practitioner A" that was sent from Mobile CareGiver+ is displayed at "Site A".
  23. Right click on the appointment for "Client A" and click [Details/Edit].
  24. Validate the appointment details are displayed as expected.
  25. Validate the 'Select Address of Service' field contains "Primary Address (Demographics)".
  26. Close the form.
  27. Right click on the appointment for "Client B" and click [Details/Edit].
  28. Validate the appointment details are displayed as expected.
  29. Validate the 'Select Address of Service' field contains "Address created by Mobile Caregiver+".
  30. Close the form and click [Dismiss].
  31. Access the 'Client Alternate Addresses' form.
  32. Select "Client B" in the 'Client' field.
  33. Select "Edit" in the 'Add/Edit' field.
  34. Validate the 'Select Existing Address' field contains "Address created by Mobile Caregiver+" and select it.
  35. Validate the primary home address details for "Client A" are displayed since this address was used as the location of service.
  36. 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
  1. 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.
  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 'CareFabric Monitor' form.
  4. Enter the current date in the 'From Date' and 'Through Date' fields.
  5. Select "McgEvvAppointmentUpdated" in the 'Event/Action Search' field.
  6. Click [View Activity Log].
  7. Validate the 'CareFabric Monitor Report' contains an "McgEvvAppointmentUpdated" record.
  8. Click [Click To View Record].
  9. Validate the 'endDate' field contains the appointment end date/time.
  10. Validate the 'isMultipleRecipients' field contains "true".
  11. Validate the 'mcgAppointmentID' - 'id' field contains the MCG+ unique identifier for the appointment.
  12. Validate the 'resource' - 'resourceID' field contains "Practitioner A".
  13. Validate the first - 'services' - 'clientID- 'id' field contains "Client A".
  14. Validate the first 'services' - 'procedureCode' - 'code' field contains "Procedure Code A".
  15. Validate the second 'services' - 'clientID' - 'id' field contains "Client B".
  16. Validate the second 'services' - 'procedureCode' - 'code' field contains "Procedure Code A".
  17. Validate the 'locationOfService' fields contain "Alternate Address A".
  18. Validate the 'startDate' field contains the appointment start date/time.
  19. Validate all other appointment data is displayed.
  20. Close the report and the form.
  21. Access the 'Scheduling Calendar' form.
  22. Validate an appointment for "Client A" and "Client B" with "Practitioner A" that was sent from Mobile CareGiver+ is displayed at "Site A".
  23. Right click on the appointment for "Client A" and click [Details/Edit].
  24. Validate the appointment details are displayed as expected.
  25. Validate the 'Select Address of Service' field contains "Alternate Address A".
  26. Close the form.
  27. Right click on the appointment for "Client B" and click [Details/Edit].
  28. Validate the appointment details are displayed as expected.
  29. Validate the 'Select Address of Service' field contains "Alternate Address A".
  30. Close the form and click [Dismiss].
  31. Access the 'Client Alternate Addresses' form.
  32. Select "Client B" in the 'Client' field.
  33. Select "Edit" in the 'Add/Edit' field.
  34. Validate the 'Select Existing Address' field contains "Alternate Address A" and select it.
  35. Validate the "Alternate Address A" details from "Client A" are displayed since this address was used as the location of service.
  36. Close the form.
Topics
• CarePOV Management • Electronic Visit Verification
Update 10 Summary | Details
CareFabric - processing cloud hosted Micromedex data
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • eMAR
  • Order Code Load/Update Utility Via Micromedex Red Book Database
Scenario 1: OE NX - Orders This Episode - mixed case/Tall Man Lettering with validation in eMAR NX.
Specific Setup:
  • A client must have an active inpatient episode whose program or unit are configured in the 'External Pharmacy Setup' form. (Client A)
  • “Client A” must have a ‘Date of Birth’, ‘Sex’ and address on file in the ‘Update Client Data’ form, as well as information filed in the ‘Allergies and Hypersensitivities’ form, ‘Diagnosis’ form, and in the ‘Height’ and ‘Weight’ fields in the ‘Vitals Entry’ form.
  • "Client A" must have 3 active orders for "PREDNISONE 10 MG TABLET ORAL", "AMBIEN (ZOLPIDEM TARTRATE) 10 MG TABLET ORAL (Schedule IV)", and "FUROSEMIDE 80 MG TABLET ORAL" that frequency codes that are configured as "Routine".
Steps
  1. Select "Client A" and access the Order Entry Console.
  2. Validate the 'Order grid' contains orders for "PREDNISONE 10 MG TABLET ORAL", "AMBIEN (ZOLPIDEM TARTRATE) 10 MG TABLET ORAL (Schedule IV)", and "FUROSEMIDE 80 MG TABLET ORAL".
  3. Access "eMAR NX".
  4. Validate that the following orders are displayed under 'Scheduled/Routine':
  5. AMBIEN (ZOLPIDEM TARTRATE) 10 MG ORAL TABLET
  6. FUROSEMIDE 80 MG ORAL TABLET
  7. PREDNISONE 10 MG ORAL TABLET
  8. Go to 'myDay'.
  9. Access the 'Order Code Load/Update Utility Via Micromedex Red Book Database' form.
  10. Validate the two new fields:
  11. Use mixed-case lettering (including Tall Man Lettering, when available) for product names used to create new Order Codes
  12. Update the 'Description' of previously-created Order Codes using mixed-case lettering (including Tall Man Lettering, when available)
  13. Select "Yes" in the 'Use mixed-case lettering (including Tall Man Lettering, when available) for product names used to create new Order Codes' field.
  14. Select "Yes" in the 'Update the 'Description' of previously-created Order Codes using mixed-case lettering (including Tall Man Lettering, when available)' field.
  15. Validate a 'Warning' dialog is displayed stating "WARNING: Setting this prompt to "Yes" will cause the main 'Description' field to be updated on 'Order Codes' that were previously created via this process. This will result in any edits that might have been made by the facility to be overwritten. This includes changes that might have been performed via the 'Order Code Setup' form or via the 'File Import' for Avatar OE 'Order Codes'. Note: 'Order Codes' that have had their 'Description' field updated via Formulary Sync (enhanced mode) will NOT have their 'Description' re-updated via this process. The Order Entry Console (Orders This Episode section and other sections that display OE orders), the 'Client Profile/Physicians Orders' form, and other places within Avatar that display the current description of orders will reflect the updated 'Order Code' 'Description' values immediately, for all orders that use such updated 'Order Codes'. A process will be run in the background to update the descriptions of active orders in Avatar eMAR for orders that use such updated 'Order Codes'. Are you sure that you want to select "Yes"?"
  16. Click [Yes].
  17. Click [Create/Update Order Codes].
  18. Validate a message is displayed stating: "Warning: this version of the 'REDBOOK Database' has already been processed. Are you sure you want to continue?" and click [Yes].
  19. Validate a message is displayed stating: "Note: Processing will take several minutes." and click [OK].
  20. Once completed a message will be displayed stating how many order codes were processed and click [OK].
  21. Close the form.
  22. Access the Order Entry Console.
  23. Click [Refresh].
  24. Validate the 'Order grid' contains orders for "predniSONE 10 MG TABLET ORAL", "Ambien (zolpidem tartrate) 10 MG TABLET ORAL (Schedule IV)", and "Furosemide 80 MG TABLET ORAL".
  25. Access 'eMAR NX'.
  26. Validate that the following orders are displayed under 'Scheduled/Routine':
  27. Ambien (zolpidem tartrate) 10 MG ORAL TABLET
  28. Furosemide 80 MG ORAL TABLET
  29. predniSONE 10 MG ORAL TABLET
Topics
• Order Entry Console
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
  1. Open Avatar PM/Cal-PM '835 Health Care Claim Payment/Advice' form.
  2. Select 'Load File' in the 'Options' field.
  3. Enter 'File Path/Name' value for 835 inbound file to be loaded and click 'Process File' button.
  4. Ensure 835 file is successfully loaded.
  5. Select 'Compile File' in the 'Options' field.
  6. Select loaded inbound 835 file in the 'Select File' field and click 'Process File' button.
  7. In 835 Compile Report - ensure that payments/adjustments are successfully compiled for one or more Avatar PM/Cal-PM claims/services.
  8. Select 'Post File' in the 'Options' field.
  9. 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.
  10. In 835 Posting Report - ensure that payments/adjustments are successfully posted for one or more Avatar PM/Cal-PM claims/services.
  11. Open Avatar PM/Cal-PM 'CareFabric Monitor' form.
  12. Enter values for 'From Date' and 'Through Date' fields (using dates which include 274 Provider Directory Provider Definition entry/edit).
  13. Enter/select values for any other CareFabric Monitor fields as desired.
  14. Click 'View Activity Log' button to display CareFabric Monitor report results.
  15. 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
  1. Open Avatar MSO '835 Health Care Claim Payment/Advice' form.
  2. Note - Acceptance testing may also be confirmed in 835 files created via Avatar MSO Claim Processing Automation functions
  3. Select 'Sort File' in the 'Options' field.
  4. Select 'Contracting Provider' value.
  5. Select EOB(s) for 835 outbound file inclusion in the 'Select EOB(s)' field.
  6. Click 'Process' button.
  7. 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).
  8. Open Avatar PM/Cal-PM 'CareFabric Monitor' form.
  9. Enter values for 'From Date' and 'Through Date' fields (using dates which include 274 Provider Directory Provider Definition entry/edit).
  10. Enter/select values for any other CareFabric Monitor fields as desired.
  11. Click 'View Activity Log' button to display CareFabric Monitor report results.
  12. 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
  1. Open Avatar PM/Cal-PM '835 Health Care Claim Payment/Advice' form.
  2. Select 'Load File' in the 'Options' field.
  3. Enter 'File Path/Name' value for 835 inbound file to be loaded and click 'Process File' button.
  4. Ensure 835 file is successfully loaded.
  5. Select 'Compile File' in the 'Options' field.
  6. Select loaded inbound 835 file in the 'Select File' field and click 'Process File' button.
  7. In 835 Compile Report - ensure that payments/adjustments are successfully compiled for one or more Avatar PM/Cal-PM claims/services.
  8. Select 'Post File' in the 'Options' field.
  9. 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.
  10. In 835 Posting Report - ensure that payments/adjustments are successfully posted for one or more Avatar PM/Cal-PM claims/services.
  11. Open Avatar PM/Cal-PM 'CareFabric Monitor' form.
  12. Enter values for 'From Date' and 'Through Date' fields (using dates which include 274 Provider Directory Provider Definition entry/edit).
  13. Enter/select values for any other CareFabric Monitor fields as desired.
  14. Click 'View Activity Log' button to display CareFabric Monitor report results.
  15. 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
  1. Open Avatar MSO '835 Health Care Claim Payment/Advice' form.
  2. Note - Acceptance testing may also be confirmed in 835 files created via Avatar MSO Claim Processing Automation functions
  3. Select 'Sort File' in the 'Options' field.
  4. Select 'Contracting Provider' value.
  5. Select EOB(s) for 835 outbound file inclusion in the 'Select EOB(s)' field.
  6. Click 'Process' button.
  7. 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).
  8. Open Avatar PM/Cal-PM 'CareFabric Monitor' form.
  9. Enter values for 'From Date' and 'Through Date' fields (using dates which include 274 Provider Directory Provider Definition entry/edit).
  10. Enter/select values for any other CareFabric Monitor fields as desired.
  11. Click 'View Activity Log' button to display CareFabric Monitor report results.
  12. 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
  1. Access the 'CarePOV Management' form.
  2. Select the "Client Alerts" section.
  3. Click "Add" in the 'Add or Edit Alert' field.
  4. Select "Duplicate Name - Header" in the 'Alert Type' field.
  5. Validate the 'Base Duplicate Name Alert On' field is now enabled and required.
  6. Select "Full Name (First and Last)" in the 'Base Duplicate Name On' field.
  7. Enter the desired value in the 'Client Alert Description' field.
  8. Select the desired icon in the 'Select Icon' field.
  9. Select "Yes" in the 'Active' field.
  10. Select "Yes" in the 'Include in Client Header' field.
  11. Click [Save].
  12. Validate a message is displayed stating: Saved.
  13. Click [OK] and close the form.
  14. Select "Client A" and navigate to the 'Client Information' header.
  15. Select "All Episodes" in the 'Episode' field.
  16. Validate the icon associated to the duplicate name alert added in the previous steps is displayed.
  17. Hover over the icon and validate the 'Client Alert Description' added in the previous steps is displayed.
  18. Select "Episode 1" in the 'Episode' field.
  19. Validate the icon associated to the duplicate name alert added in the previous steps is displayed.
  20. Hover over the icon and validate the 'Client Alert Description' added in the previous steps is displayed.
  21. Select "Client B" and navigate to the 'Client Information' header.
  22. Select "All Episodes" in the 'Episode' field.
  23. Validate the icon associated to the duplicate name alert added in the previous steps is displayed.
  24. Hover over the icon and validate the 'Client Alert Description' added in the previous steps is displayed.
  25. Select "Episode 1" in the 'Episode' field.
  26. Validate the icon associated to the duplicate name alert added in the previous steps is displayed.
  27. Hover over the icon and validate the 'Client Alert Description' added in the previous steps is displayed.
  28. Select "Client C" and navigate to the 'Client Information' header.
  29. 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
  1. Access the 'CarePOV Management' form.
  2. Select the "Client Alerts" section.
  3. Click "Add" in the 'Add or Edit Alert' field.
  4. Select "Duplicate Name - Header" in the 'Alert Type' field.
  5. Validate the 'Base Duplicate Name Alert On' field is now enabled and required.
  6. Select "First Name, Last Initial" in the 'Base Duplicate Name On' field.
  7. Enter the desired value in the 'Client Alert Description' field.
  8. Select the desired icon in the 'Select Icon' field.
  9. Select "Yes" in the 'Active' field.
  10. Select "Yes" in the 'Include in Client Header' field.
  11. Click [Save].
  12. Validate a message is displayed stating: Saved.
  13. Click [OK] and close the form.
  14. Select "Client A" and navigate to the 'Client Information' header.
  15. Select "All Episodes" in the 'Episode' field.
  16. Validate the icon associated to the duplicate name alert added in the previous steps is displayed.
  17. Hover over the icon and validate the 'Client Alert Description' added in the previous steps is displayed.
  18. Select "Episode 1" in the 'Episode' field.
  19. Validate the icon associated to the duplicate name alert added in the previous steps is displayed.
  20. Hover over the icon and validate the 'Client Alert Description' added in the previous steps is displayed.
  21. Select "Client B" and navigate to the 'Client Information' header.
  22. Select "All Episodes" in the 'Episode' field.
  23. Validate the icon associated to the duplicate name alert added in the previous steps is displayed.
  24. Hover over the icon and validate the 'Client Alert Description' added in the previous steps is displayed.
  25. Select "Episode 1" in the 'Episode' field.
  26. Validate the icon associated to the duplicate name alert added in the previous steps is displayed.
  27. Hover over the icon and validate the 'Client Alert Description' added in the previous steps is displayed.
  28. Select "Client C" and navigate to the 'Client Information' header.
  29. 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
  1. Access the 'CarePOV Management' form.
  2. Select the "Client Alerts" section.
  3. Click "Add" in the 'Add or Edit Alert' field.
  4. Select "Duplicate Name - Header" in the 'Alert Type' field.
  5. Validate the 'Base Duplicate Name Alert On' field is now enabled and required.
  6. Select "Last Name, First Initial" in the 'Base Duplicate Name On' field.
  7. Enter the desired value in the 'Client Alert Description' field.
  8. Select the desired icon in the 'Select Icon' field.
  9. Select "Yes" in the 'Active' field.
  10. Select "Yes" in the 'Include in Client Header' field.
  11. Click [Save].
  12. Validate a message is displayed stating: Saved.
  13. Click [OK] and close the form.
  14. Select "Client A" and navigate to the 'Client Information' header.
  15. Select "All Episodes" in the 'Episode' field.
  16. Validate the icon associated to the duplicate name alert added in the previous steps is displayed.
  17. Hover over the icon and validate the 'Client Alert Description' added in the previous steps is displayed.
  18. Select "Episode 1" in the 'Episode' field.
  19. Validate the icon associated to the duplicate name alert added in the previous steps is displayed.
  20. Hover over the icon and validate the 'Client Alert Description' added in the previous steps is displayed.
  21. Select "Client B" and navigate to the 'Client Information' header.
  22. Select "All Episodes" in the 'Episode' field.
  23. Validate the icon associated to the duplicate name alert added in the previous steps is displayed.
  24. Hover over the icon and validate the 'Client Alert Description' added in the previous steps is displayed.
  25. Select "Episode 1" in the 'Episode' field.
  26. Validate the icon associated to the duplicate name alert added in the previous steps is displayed.
  27. Hover over the icon and validate the 'Client Alert Description' added in the previous steps is displayed.
  28. Select "Client C" and navigate to the 'Client Information' header.
  29. 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
  1. Access the 'CarePOV Management' form.
  2. Select the "Client Alerts" section.
  3. Click "Add" in the 'Add or Edit Alert' field.
  4. Select "Pregnancy" in the 'Alert Type' field.
  5. Enter the desired value in the 'Client Alert Description' field.
  6. Select the desired icon in the 'Select Icon' field.
  7. Select "Yes" in the 'Active' field.
  8. Select "Yes" in the 'Include in Client Header' field.
  9. Click [Save].
  10. Validate a message is displayed stating: Saved.
  11. Click [OK] and close the form.
  12. Select "Client A" and access the 'Women's Health History' form.
  13. Enter the desired date in the 'Assessment Date' field.
  14. Enter the desired date in the 'Pregnancy Start Date' field.
  15. Select "Yes" in the 'Have you ever been pregnant?' field.
  16. Select "Pregnant" in the 'Pregnant Status' field.
  17. Enter the desired date in the 'Expected Due Date' field.
  18. Click [Submit].
  19. Select "Client A" and navigate to the 'Client Information' header.
  20. Select "All Episodes" in the 'Episode' field.
  21. Validate the icon associated to the Pregnancy alert added in the previous steps is displayed.
  22. Hover over the icon and validate the 'Client Alert Description' added in the previous steps is displayed.
  23. Select "Episode 1" in the 'Episode' field.
  24. Validate the icon associated to the Pregnancy alert added in the previous steps is displayed.
  25. 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
  1. Access the 'CarePOV Management' form.
  2. Select the "Client Alerts" section.
  3. Click "Add" in the 'Add or Edit Alert' field.
  4. Select "Allergy" in the 'Alert Type' field.
  5. Enter the desired value in the 'Client Alert Description' field.
  6. Select the desired icon in the 'Select Icon' field.
  7. Select "Yes" in the 'Active' field.
  8. Select "Yes" in the 'Include in Client Header' field.
  9. Click [Save].
  10. Validate a message is displayed stating: Saved.
  11. Click [OK] and close the form.
  12. Access the 'Allergies and Hypersensitivities' form
  13. Click [Update].
  14. Validate the 'Allergies and Hypersensitivities' grid is displayed.
  15. Click [New Row].
  16. Add any new active allergy
  17. Click [Save] and submit the form.
  18. Select "Client A" and navigate to the 'Client Information' header.
  19. Select "All Episodes" in the 'Episode' field.
  20. Validate the icon associated to the Allergy alert added in the previous steps is displayed.
  21. Hover over the icon and validate the 'Client Alert Description' added in the previous steps is displayed.
  22. Select "Episode 1" in the 'Episode' field.
  23. Validate the icon associated to the Allergy alert added in the previous steps is displayed.
  24. 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
  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 "Note Type A".
  5. Verify the existence of "Client A" in the client header when note is started.
  6. Fill out all required fields.
  7. Select the desired value(s) in the 'Evidence-Based Practices' field.
  8. Click [Sign Note].
  9. Validate the Sign Note' dialog is displayed.
  10. Enter the pin for "User A" in the 'Pin' field and click [Sign].
  11. Validate a message is displayed stating: Note Signed Successfully.
  12. Log into myAvatar as "User A".
  13. Navigate to the "My To Do's" widget.
  14. Validate a To-Do is displayed for the note sent via Bells Notes for "Client A".
  15. Click [Approve Document].
  16. Validate the progress note data is displayed, including the value(s) selected in the 'Evidence-Based Practices' field.
  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.
  20. Select "Client A" and navigate to the 'Progress Notes' widget.
  21. Validate the progress note filed from Bells Notes is displayed.
  22. 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
  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 "Note Type A".
  5. Verify the existence of "Client A" in the client header when note is started.
  6. Fill out all required fields.
  7. Select the desired value(s) in the 'Evidence-Based Practices' field.
  8. Click [Sign Note].
  9. Validate the Sign Note' dialog is displayed.
  10. Enter the pin for "User A" in the 'Pin' field and click [Sign].
  11. Validate a message is displayed stating: Note Signed Successfully.
  12. Log into myAvatar as "User A".
  13. Navigate to the "My To Do's" widget.
  14. Validate a 'To-Do' is displayed for the note sent via Bells Notes for "Client A".
  15. Click [Approve Document].
  16. Validate the progress note data is displayed, including the value(s) selected in the 'Evidence-Based Practices' field.
  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.
  20. Select "Client A" and navigate to the 'Progress Notes' widget.
  21. Validate the progress note filed from Bells Notes is displayed.
  22. 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
  1. Select "Client A" and access the 'Diagnosis' form.
  2. Select the desired value in the 'Type Of Diagnosis' field.
  3. Enter the desired date in the 'Date Of Diagnosis' field.
  4. Enter the desired time the 'Time Of Diagnosis' field.
  5. Click [New Row].
  6. Select the desired value in the 'Diagnosis Search' field.
  7. Select "Active" in the 'Status' field.
  8. Select the desired practitioner in the 'Diagnosing Practitioner' field.
  9. Click [Submit].
  10. Access the 'CareFabric Monitor' form.
  11. Enter the current date in the 'From Date' and 'Through Date' fields.
  12. Select "Client A" in the 'Client ID' field.
  13. Select "DiagnosisCreated" in the 'Event/Action Search' field.
  14. Click [View Activity Log].
  15. Validate the 'CareFabric Monitor Report' displays a 'DiagnosisCreated' record.
  16. Click [Click To View Record].
  17. Validate the 'startDate' field contains the 'Date Of Diagnosis' and 'Time Of Diagnosis' populated in the previous steps.
  18. Validate the 'statusCode' - 'code' field contains "1".
  19. Validate the 'statusCode' - 'displayName' field contains "Active".
  20. Validate the 'voidedByStaffMemberID' field contains "null".
  21. Validate the 'voidedDate' field contains "null".
  22. Validate all other previously filed data displays as expected.
  23. Close the report and the form.
  24. Select "Client A" and access the 'Diagnosis' form.
  25. Select the diagnosis created in the previous steps and click [Edit].
  26. Select the row filed in the previous steps from the 'Diagnoses' grid.
  27. Select "Void" in the 'Status' field.
  28. Click [Submit].
  29. Access the 'CareFabric Monitor' form.
  30. Enter the current date in the 'From Date' and 'Through Date' fields.
  31. Select "Client A" in the 'Client ID' field.
  32. Select "DiagnosisUpdated" in the 'Event/Action Search' field.
  33. Click [View Activity Log].
  34. Validate the 'CareFabric Monitor Report' displays a 'DiagnosisUpdated' record.
  35. Click [Click To View Record].
  36. Validate the 'statusCode' - 'code' field contains "5".
  37. Validate the 'statusCode' - 'displayName' field contains "Void".
  38. Validate the 'voidedByStaffMemberID' - 'id' field contains the logged in staff member.
  39. Validate the 'voidedDate' field contains the current date.
  40. 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
  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 "Note Type A".
  5. Verify the existence of "Client A" in the client header when note is started.
  6. Fill out all required fields.
  7. Enter multiple session start/end times.
  8. Click [Sign Note].
  9. Validate the Sign Note' dialog is displayed.
  10. Enter the pin for "User A" in the 'Pin' field and click [Sign].
  11. Validate a message is displayed stating: Note Signed Successfully.
  12. Log into myAvatar as "User A".
  13. Select "Client A" and navigate to the 'Progress Notes' widget.
  14. Validate the progress note filed from Bells Notes is displayed.
  15. 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
  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 "Note Type A".
  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. Validate a 'To-Do' is not displayed for the note sent via Bells Notes since "User A" does not require an approver.
  14. Select "Client A" and navigate to the 'Progress Notes' widget.
  15. Validate the progress note filed from Bells Notes is displayed.
  16. Access the 'Clinical Document Viewer' form.
  17. Select "Client" in the 'Select Type' field.
  18. Select "Individual" in the 'Select All or Individual Client' field.
  19. Select "Client A" in the 'Select Client' field.
  20. Select "All" in the 'Episode' field.
  21. Click [Process].
  22. Validate a document is displayed for the progress note filed from Bells Notes.
  23. Select the document and click [View].
  24. Validate the PDF generated from Bells Notes is displayed with the note details.
  25. Click [Close All Documents], [Search], and [Close].
Topics
• Progress Notes • CareFabric • Bells Notes
Update 17 Summary | Details
Medical Note - Interaction Checking
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Drug Interaction
  • Allergies and Hypersensitivities
Scenario 1: Medical Note - In-Office Administrations - Interaction Checking - Drug-Drug Interaction
Specific Setup:
  • At least two dictionary codes must exist in the Order Entry Client Information ‘(20559) Override Code’ dictionary. (Override Code A) (Override Code B).
  • The ‘(20590) Require Override Text With This Override Code’ extended attribute must be set to “No” in the Order Entry Client Information ‘(20559) Override Code’ dictionary for “Override Code A”.
  • The ‘(20590) Require Override Text With This Override Code’ extended attribute must be set to “Yes” in the Order Entry Client Information ‘(20559) Override Code’ dictionary for “Override Code B”.
  • Please log out of the application and log back in after completing the above configuration.
  • Two pharmacy-type order codes must exist. (Medication A) (Medication B)
  • When "Medication A" and "Medication B" are ordered concurrently, a 'Drug-drug interaction' alert must be created.
  • A procedure-type service code (Administration A) must be configured in the 'Service Codes' form such that:
  • 'Procedure Type' = "Medication Administration".
  • 'Medication Equivalent' = "Medication A".
  • A client must have an active episode. (Client A)
Steps
  1. Select "Client A" and access the Order Entry Console.
  2. Select the 'Home Medications' tab and uncheck the 'Reported' checkbox.
  3. Search for and select "Medication B" from the 'New Order' field.
  4. Fill in any required fields, click [Add to Scratchpad] and [Final Review].
  5. Select "None" in the 'Output' field and click [Sign].
  6. Validate the 'Order grid' contains the new order for "Medication B".
  7. Navigate to the 'Medical Note' tab, click [Add Note], and create a new note.
  8. Select the 'Document' tab and then navigate to the 'In-Office Administrations' section.
  9. Click [Add], select "Administration A" from the 'In-Office Administrations Search' field and click [Continue].
  10. Validate an 'Alert' banner is displayed, surrounded by a red border, and that it states "Clinical Screening Alert".
  11. Click [Override Alert] and validate a 'Drug Interaction' dialog displays.
  12. Validate a 'Drug-drug' interaction between "Medication B" and "Administration A" is shown.
  13. Validate both the 'Override Reason' and 'Notes' fields are showing as required.
  14. Validate the 'Save' and 'Save and Close' buttons are disabled.
  15. Select "Override Code A" from the 'Override Reason' field and validate the 'Notes' field is not required.
  16. Validate the 'Save' and 'Save and Close' buttons are enabled.
  17. Click [Save and Close].
  18. Validate an 'Alert' banner is displayed, surrounded by a yellow border, and that it states "Clinical Screening Alert".
  19. Click [View Overrides] and validate the 'Override Reason' and 'Notes' fields are disabled.
  20. Validate the 'Drug-drug interaction' field contains the override reason code provided.
  21. Click [Edit] and validate the 'Override Reason' and 'Notes' fields are enabled.
  22. Select "Override Code B" from the 'Override Reason' field and validate the 'Notes' field is required.
  23. Set the 'Notes' field to any value and click [Save and Close].
  24. Validate an 'Alert' banner is displayed, surrounded by a yellow border, and that it states "Clinical Screening Alert".
  25. Click [View Overrides] and validate the 'Override Reason' and 'Notes' fields are disabled.
  26. Validate the 'Drug-drug interaction' field contains the override reason code and text provided and click [Close].
  27. Fill in any required fields and click [Order].
  28. Validate "Administration A" is listed in the 'Pending Administrations' field and that an 'Alert' icon is shown to the right of the name.
  29. Hover over the 'Alert' icon and validate a tooltip displays stating "Click to view overrides".
  30. Click the 'Alert' icon and validate the 'Drug Interaction' dialog appears in read-only mode.
  31. Validate all information provided is accurate and click [Close].
Scenario 2: Medical Note - In-Office Administrations - Pending Orders - Interaction Checking - Drug-Drug Interaction
Specific Setup:
  • At least one dictionary codes must exist in the Order Entry Client Information ‘(20559) Override Code’ dictionary. (Override Code A)
  • The ‘(20590) Require Override Text With This Override Code’ extended attribute must be set to “No” in the Order Entry Client Information ‘(20559) Override Code’ dictionary for “Override Code A”.
  • Please log out of the application and log back in after completing the above configuration.
  • Two pharmacy-type order codes must exist. (Medication A) (Medication B)
  • When "Medication A" and "Medication B" are ordered concurrently, a 'Drug-drug interaction' alert must be created.
  • A procedure-type service code (In-Office A) must be configured in the 'Service Codes' form such that:
  • 'Procedure Type' = "Medication Administration".
  • 'Medication Equivalent' = "Medication A".
  • A procedure-type service code (In-Office B) must be configured in the 'Service Codes' form such that:
  • 'Procedure Type' = "Medication Administration".
  • 'Medication Equivalent' = "Medication B".
  • A client must have an active episode. (Client A)
  • "Client A" should have no current orders in OrderConnect.
Steps
  1. Search for and select "Client A" and navigate to the 'Medical Note'.
  2. Click [Add Note] and create a new note.
  3. Select the 'Document' tab and then navigate to the 'In-Office Administrations' section.
  4. Click [Add], search for and select "In-Office A" from the 'In-Office Administrations Search' field and click [Continue].
  5. Populate any required fields and click [Order].
  6. Click [Add], search for and select "In-Office B" from the 'In-Office Administrations Search' field and click [Continue].
  7. Validate an 'Alert' banner is displayed, surrounded by a red border, and that it states "Clinical Screening Alert".
  8. Click [Override Alert] and validate a 'Drug Interaction' dialog displays.
  9. Validate a 'Drug-drug' interaction between "In-Office A" and "In-Office B" is shown.
  10. Select "Override Code A" from the 'Override Reason' field.
  11. Click [Save and Close].
  12. Validate an 'Alert' banner is displayed, surrounded by a yellow border, and that it states "Clinical Screening Alert".
  13. Fill in any required fields and click [Order].
  14. Validate "In-Office A" and "In-Office B" are both listed in the 'Pending Administrations' field and that an 'Alert' icon is shown only to the right of "In-Office B".
  15. Hover over the 'Alert' icon and validate a tooltip displays stating "Click to view overrides".
  16. Click the 'Alert' icon and validate the 'Drug Interaction' dialog appears in read-only mode.
  17. Validate all information provided is accurate and click [Close].
Scenario 3: Medical Note - In-Office Administrations - Interaction Checking - Therapeutic Class Duplication
Specific Setup:
  • At least two dictionary codes must exist in the Order Entry Client Information ‘(20559) Override Code’ dictionary. (Override Code A) (Override Code B).
  • The ‘(20590) Require Override Text With This Override Code’ extended attribute must be set to “No” in the Order Entry Client Information ‘(20559) Override Code’ dictionary for “Override Code A”.
  • The ‘(20590) Require Override Text With This Override Code’ extended attribute must be set to “Yes” in the Order Entry Client Information ‘(20559) Override Code’ dictionary for “Override Code B”.
  • Please log out of the application and log back in after completing the above configuration.
  • Two pharmacy-type order codes must exist. (Medication A) (Medication B)
  • When "Medication A" and "Medication B" are ordered concurrently, a 'Therapeutic Class Duplication' alert must be created.
  • A procedure-type service code (In-Office A) must be configured in the 'Service Codes' form such that:
  • 'Procedure Type' = "Medication Administration".
  • 'Medication Equivalent' = "Medication A".
  • A client must have an active episode. (Client A)
  • "Client A" should have no current orders in OrderConnect.
Steps
  1. Select "Client A" and access the Order Entry Console.
  2. Select the 'Home Medications' tab and uncheck the 'Reported' checkbox.
  3. Search for and select "Medication B" from the 'New Order' field.
  4. Fill in any required fields, click [Add to Scratchpad] and [Final Review].
  5. Select "None" in the 'Output' field and click [Sign].
  6. Validate the 'Order grid' contains the new order for "Medication B".
  7. Navigate to the 'Medical Note' tab, click [Add Note], and create a new note.
  8. Select the 'Document' tab and then navigate to the 'In-Office Administrations' section.
  9. Click [Add], select "In-Office A" from the 'In-Office Administrations Search' field and click [Continue].
  10. Validate an 'Alert' banner is displayed, surrounded by a red border, and that it states "Clinical Screening Alert".
  11. Click [Override Alert] and validate a 'Drug Interaction' dialog displays.
  12. Validate a 'Therapeutic Class Duplication' interaction between "Medication B" and "In-Office A" is shown.
  13. Validate both the 'Override Reason' and 'Notes' fields are showing as required.
  14. Validate the 'Save' and 'Save and Close' buttons are disabled.
  15. Select "Override Code A" from the 'Override Reason' field and validate the 'Notes' field is not required.
  16. Validate the 'Save' and 'Save and Close' buttons are enabled.
  17. Click [Save and Close].
  18. Validate an 'Alert' banner is displayed, surrounded by a yellow border, and that it states "Clinical Screening Alert".
  19. Click [View Overrides] and validate the 'Override Reason' and 'Notes' fields are disabled.
  20. Validate the 'Therapeutic Class Duplication' field contains the override reason code provided.
  21. Click [Edit] and validate the 'Override Reason' and 'Notes' fields are enabled.
  22. Select "Override Code B" from the 'Override Reason' field and validate the 'Notes' field is required.
  23. Set the 'Notes' field to any value and click [Save and Close].
  24. Validate an 'Alert' banner is displayed, surrounded by a yellow border, and that it states "Clinical Screening Alert".
  25. Click [View Overrides] and validate the 'Override Reason' and 'Notes' fields are disabled.
  26. Validate the 'Therapeutic Class Duplication' field contains the override reason code and text provided and click [Close].
  27. Fill in any required fields and click [Order].
  28. Validate "In-Office A" is listed in the 'Pending Administrations' field and that an 'Alert' icon is shown to the right of the name.
  29. Hover over the 'Alert' icon and validate a tooltip displays stating "Click to view overrides".
  30. Click the 'Alert' icon and validate the 'Drug Interaction' dialog appears in read-only mode.
  31. Validate all information provided is accurate and click [Close].
Scenario 4: Medical Note - In-Office Administrations - Pending Orders - Interaction Checking - Therapeutic Class Duplication
Specific Setup:
  • At least one dictionary codes must exist in the Order Entry Client Information ‘(20559) Override Code’ dictionary. (Override Code A)
  • The ‘(20590) Require Override Text With This Override Code’ extended attribute must be set to “No” in the Order Entry Client Information ‘(20559) Override Code’ dictionary for “Override Code A”.
  • Please log out of the application and log back in after completing the above configuration.
  • Two pharmacy-type order codes must exist. (Medication A) (Medication B)
  • When "Medication A" and "Medication B" are ordered concurrently, a 'Therapeutic Class Duplication' alert must be created.
  • A procedure-type service code (In-Office A) must be configured in the 'Service Codes' form such that:
  • 'Procedure Type' = "Medication Administration".
  • 'Medication Equivalent' = "Medication A".
  • A procedure-type service code (In-Office B) must be configured in the 'Service Codes' form such that:
  • 'Procedure Type' = "Medication Administration".
  • 'Medication Equivalent' = "Medication B".
  • A client must have an active episode. (Client A)
  • "Client A" should have no current orders in OrderConnect.
Steps
  1. Search for and select "Client A" and navigate to the 'Medical Note'.
  2. Click [Add Note] and create a new note.
  3. Select the 'Document' tab and then navigate to the 'In-Office Administrations' section.
  4. Click [Add], search for and select "In-Office A" from the 'In-Office Administrations Search' field and click [Continue].
  5. Populate any required fields and click [Order].
  6. Click [Add], search for and select "In-Office B" from the 'In-Office Administrations Search' field and click [Continue].
  7. Validate an 'Alert' banner is displayed, surrounded by a red border, and that it states "Clinical Screening Alert".
  8. Click [Override Alert] and validate a 'Drug Interaction' dialog displays.
  9. Validate a 'Therapeutic Class Duplication' interaction between "In-Office A" and "In-Office B" is shown.
  10. Validate both the 'Override Reason' and 'Notes' fields are showing as required.
  11. Validate the 'Save' and 'Save and Close' buttons are disabled.
  12. Set the 'Notes' field to any value.
  13. Validate the 'Override Reason' field is not required.
  14. Validate the 'Save' and 'Save and Close' buttons are enabled and click [Save and Close].
  15. Validate an 'Alert' banner is displayed, surrounded by a yellow border, and that it states "Clinical Screening Alert".
  16. Fill in any required fields and click [Administer].
  17. Fill in any required fields and click [Save].
  18. Validate no 'Alert' icon is shown to the right of "In-Office A" in the 'Pending Administrations' table.
  19. Expand the 'Administration History' table and validate "In-Office B" is listed and that an 'Alert' icon is shown to the right of the name.
  20. Hover over the 'Alert' icon and validate a tooltip displays stating "Click to view overrides".
  21. Click the 'Alert' icon and validate the 'Drug Interaction' dialog appears in read-only mode.
  22. Validate all information provided is accurate and click [Close].
Scenario 5: Medical Note - In-Office Administrations - Interaction Checking - Drug-Allergy Interaction
Specific Setup:
  • At least one dictionary code must exist in the Order Entry Client Information ‘(20559) Override Code’ dictionary. (Override Code A)
  • The ‘(20590) Require Override Text With This Override Code’ extended attribute must be set to “No” in the Order Entry Client Information ‘(20559) Override Code’ dictionary for “Override Code A”.
  • Please log out of the application and log back in after completing the above configuration.
  • A pharmacy-type order code must exist. (Medication A)
  • A procedure-type service code (In-Office A) must be configured in the 'Service Codes' form such that:
  • 'Procedure Type' = "Medication Administration".
  • 'Medication Equivalent' = "Medication A".
  • A client must have an active episode. (Client A)
  • "Client A" should have no current orders in OrderConnect.
  • "Client A" should have a current allergy with a status of "Confirmed" for "Medication A". (Allergy A)
Steps
  1. Search for and select "Client A" and navigate to the 'Medical Note'.
  2. Click [Add Note] and create a new note.
  3. Select the 'Document' tab and then navigate to the 'In-Office Administrations' section.
  4. Click [Add], search for and select "In-Office A" from the 'In-Office Administrations Search' field and click [Continue].
  5. Validate an 'Alert' banner is displayed, surrounded by a red border, and that it states "Clinical Screening Alert".
  6. Click [Override Alert] and validate a 'Drug Interaction' dialog displays.
  7. Validate a 'Drug-allergy' interaction between "In-Office A" and "Allergy A" is shown.
  8. Validate both the 'Override Reason' and 'Notes' fields are showing as required.
  9. Validate the 'Save' and 'Save and Close' buttons are disabled.
  10. Set the 'Override Reason' field to "Override Code A".
  11. Validate the 'Notes' field is not required.
  12. Validate the 'Save' and 'Save and Close' buttons are enabled and click [Save and Close].
  13. Validate an 'Alert' banner is displayed, surrounded by a yellow border, and that it states "Clinical Screening Alert".
  14. Fill in any required fields and click [Order].
  15. Validate "In-Office A" is listed in the 'Pending Administrations' field and that an 'Alert' icon is shown to the right of the name.
  16. Hover over the 'Alert' icon and validate a tooltip displays stating "Click to view overrides".
  17. Click the 'Alert' icon and validate the 'Drug Interaction' dialog appears in read-only mode.
  18. Validate all information provided is accurate and click [Close].
Scenario 6: Medical Note - In-Office Administrations - Interaction Checking - Multiple Interactions
Specific Setup:
  • At least two dictionary codes must exist in the Order Entry Client Information ‘(20559) Override Code’ dictionary. (Override Code A) (Override Code B).
  • The ‘(20590) Require Override Text With This Override Code’ extended attribute must be set to “No” in the Order Entry Client Information ‘(20559) Override Code’ dictionary for “Override Code A”.
  • The ‘(20590) Require Override Text With This Override Code’ extended attribute must be set to “Yes” in the Order Entry Client Information ‘(20559) Override Code’ dictionary for “Override Code B”.
  • Please log out of the application and log back in after completing the above configuration.
  • Three pharmacy-type order codes must exist. (Medication A)(Medication B)(Medication C)
  • When "Medication A" and "Medication C" are ordered concurrently, a 'Drug-drug interaction' alert must be created.
  • When "Medication B" and "Medication C" are ordered concurrently, a 'Drug-drug interaction' alert must be created.
  • When "Medication A" and "Medication B" are ordered concurrently, a 'Therapeutic Class Duplication' alert must be created.
  • A procedure-type service code (In-Office A) must be configured in the 'Service Codes' form such that:
  • 'Procedure Type' = "Medication Administration".
  • 'Medication Equivalent' = "Medication A".
  • A procedure-type service code (In-Office B) must be configured in the 'Service Codes' form such that:
  • 'Procedure Type' = "Medication Administration".
  • 'Medication Equivalent' = "Medication B".
  • A client must have an active episode. (Client A)
  • "Client A" should have no current orders in OrderConnect.
  • "Client A" should have a current allergy with a status of "Confirmed" for "Medication A". (Allergy A)
Steps
  1. Search for and select "Client A" and navigate to the 'Medical Note'.
  2. Click [Add Note] and create a new note.
  3. Select the 'Document' tab and then navigate to the 'In-Office Administrations' section.
  4. Click [Add], search for and select "In-Office A" from the 'In-Office Administrations Search' field and click [Continue].
  5. Populate any required fields and click [Order].
  6. Access the Order Entry Console.
  7. Select the 'Home Medications' tab and uncheck the 'Reported' checkbox.
  8. Search for and select "Medication C" from the 'New Order' field.
  9. Fill in any required fields, click [Add to Scratchpad] and [Final Review].
  10. If an 'Interaction' dialog appears, override all interactions and click [Save Override and Exit].
  11. Select "None" in the 'Output' field and click [Sign].
  12. Validate the 'Order grid' contains the new order for "Medication C".
  13. Navigate to the 'Medical Note' and then to the 'In-Office Administrations' section.
  14. Click [Add], search for and select "In-Office B" from the 'In-Office Administrations Search' field and click [Continue].
  15. Validate an 'Alert' banner is displayed, surrounded by a red border, and that it states "Clinical Screening Alert".
  16. Click [Override Alert] and validate a 'Drug Interaction' dialog displays.
  17. Validate the 'Drug Interaction' dialog contains 'Drug-allergy interaction', 'Drug-drug interaction' and 'Therapeutic Class Duplication' alerts.
  18. Validate no checkbox defaults as "Checked".
  19. Check the 'Drug-allergy interaction' checkbox and select "Override Code A" from the 'Override Reason' field.
  20. Click [Save] and validate a green checkmark is displayed next to the Drug-allergy interaction.
  21. Check the 'Drug-drug interaction' checkbox and set the 'Notes' field to any value.
  22. Click [Save] and validate a green checkmark is displayed next to the Drug-drug interaction.
  23. Click [Close] Validate the 'Alert' banner is displayed, surrounded by a red border, and that it states "Clinical Screening Alert".
  24. Click [Override Alert] and validate the 'Drug Interaction' dialog displays.
  25. Check the 'Therapeutic Class Duplication' checkbox and select "Override Code B" from the 'Override Reason' field.
  26. Validate the 'Notes' field is required and set it to any value.
  27. Click [Save and Close].
  28. Validate an 'Alert' banner is displayed, surrounded by a yellow border, and that it states "Clinical Screening Alert".
  29. Fill in any required fields and click [Order].
  30. Validate "In-Office B" is listed in the 'Pending Immunizations' field and that an 'Alert' icon is shown to the right of the name.
  31. Hover over the 'Alert' icon and validate a tooltip displays stating "Click to view overrides".
  32. Click the 'Alert' icon and validate the 'Drug Interaction' dialog appears in read-only mode.
  33. Validate all information provided is accurate and click [Close].
Scenario 7: Medical Note - Immunizations - Interaction Checking - Drug-Drug Interaction
Specific Setup:
  • At least two dictionary codes must exist in the Order Entry Client Information ‘(20559) Override Code’ dictionary. (Override Code A) (Override Code B).
  • The ‘(20590) Require Override Text With This Override Code’ extended attribute must be set to “No” in the Order Entry Client Information ‘(20559) Override Code’ dictionary for “Override Code A”.
  • The ‘(20590) Require Override Text With This Override Code’ extended attribute must be set to “Yes” in the Order Entry Client Information ‘(20559) Override Code’ dictionary for “Override Code B”.
  • Please log out of the application and log back in after completing the above configuration.
  • Two pharmacy-type order codes must exist. (Medication A) (Medication B)
  • When "Medication A" and "Medication B" are ordered concurrently, a 'Drug-drug interaction' alert must be created.
  • A procedure-type service code (Immunization A) must be configured in the 'Service Codes' form such that:
  • 'Procedure Type' = "Vaccination/Immunization".
  • 'Medication Equivalent' = "Medication 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
  1. Select "Client A" and access the Order Entry Console.
  2. Select the 'Home Medications' tab and uncheck the 'Reported' checkbox.
  3. Search for and select "Medication B" from the 'New Order' field.
  4. Fill in any required fields, click [Add to Scratchpad] and [Final Review].
  5. Select "None" in the 'Output' field and click [Sign].
  6. Validate the 'Order grid' contains the new order for "Medication B".
  7. Navigate to the 'Medical Note' tab, click [Add Note], and create a new 'Primary Care' note.
  8. Select the 'Document' tab and then navigate to the 'Immunizations' section.
  9. Click [Add] and then [Order Immunizations], select "Immunization A" from the 'Immunization Search' field and click [Continue].
  10. Validate an 'Alert' banner is displayed, surrounded by a red border, and that it states "Clinical Screening Alert".
  11. Click [Override Alert] and validate a 'Drug Interaction' dialog displays.
  12. Validate a 'Drug-drug' interaction between "Medication B" and "Immunization A" is shown.
  13. Validate both the 'Override Reason' and 'Notes' fields are showing as required.
  14. Validate the 'Save' and 'Save and Close' buttons are disabled.
  15. Select "Override Code A" from the 'Override Reason' field and validate the 'Notes' field is not required.
  16. Validate the 'Save' and 'Save and Close' buttons are enabled.
  17. Click [Save and Close].
  18. Validate an 'Alert' banner is displayed, surrounded by a yellow border, and that it states "Clinical Screening Alert".
  19. Click [View Overrides] and validate the 'Override Reason' and 'Notes' fields are disabled.
  20. Validate the 'Drug-drug interaction' field contains the override reason code provided.
  21. Click [Edit] and validate the 'Override Reason' and 'Notes' fields are enabled.
  22. Select "Override Code B" from the 'Override Reason' field and validate the 'Notes' field is required.
  23. Set the 'Notes' field to any value and click [Save and Close].
  24. Validate an 'Alert' banner is displayed, surrounded by a yellow border, and that it states "Clinical Screening Alert".
  25. Click [View Overrides] and validate the 'Override Reason' and 'Notes' fields are disabled.
  26. Validate the 'Drug-drug interaction' field contains the override reason code and text provided and click [Close].
  27. Fill in any required fields and click [Order].
  28. Validate "Immunization A" is listed in the 'Pending Immunizations' field and that an 'Alert' icon is shown to the right of the name.
  29. Hover over the 'Alert' icon and validate a tooltip displays stating "Click to view overrides".
  30. Click the 'Alert' icon and validate the 'Drug Interaction' dialog appears in read-only mode.
  31. Validate all information provided is accurate and click [Close].
Scenario 8: Medical Note - Immunizations - Pending Orders - Interaction Checking - Drug-Drug Interaction
Specific Setup:
  • At least one dictionary code must exist in the Order Entry Client Information ‘(20559) Override Code’ dictionary. (Override Code A)
  • The ‘(20590) Require Override Text With This Override Code’ extended attribute must be set to “No” in the Order Entry Client Information ‘(20559) Override Code’ dictionary for “Override Code A”.
  • Please log out of the application and log back in after completing the above configuration.
  • Two pharmacy-type order codes must exist. (Medication A) (Medication B)
  • When "Medication A" and "Medication B" are ordered concurrently, a 'Drug-drug interaction' alert must be created.
  • A procedure-type service code (Immunization A) must be configured in the 'Service Codes' form such that:
  • 'Procedure Type' = "Vaccination/Immunization".
  • 'Medication Equivalent' = "Medication A".
  • A procedure-type service code (In-Office A) must be configured in the 'Service Codes' form such that:
  • 'Procedure Type' = "Medication Administration".
  • 'Medication Equivalent' = "Medication B".
  • 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" should have no current orders in OrderConnect.
Steps
  1. Search for and select "Client A" and navigate to the 'Medical Note'.
  2. Click [Add Note] and create a new 'Primary Care' note.
  3. Select the 'Document' tab and then navigate to the 'In-Office Administrations' section.
  4. Click [Add], search for and select "In-Office A" from the 'In-Office Administrations Search' field and click [Continue].
  5. Populate any required fields and click [Order].
  6. Navigate to the 'Immunizations' section.
  7. Click [Add] and then [Order Immunizations], select "Immunization A" from the 'Immunization Search' field and click [Continue].
  8. Validate an 'Alert' banner is displayed, surrounded by a red border, and that it states "Clinical Screening Alert".
  9. Click [Override Alert] and validate a 'Drug Interaction' dialog displays.
  10. Validate a 'Drug-drug' interaction between "In-Office A" and "Immunization A" is shown.
  11. Select "Override Code A" from the 'Override Reason' field.
  12. Click [Save and Close].
  13. Validate an 'Alert' banner is displayed, surrounded by a yellow border, and that it states "Clinical Screening Alert".
  14. Fill in any required fields and click [Order].
  15. Validate "Immunization A" is listed in the 'Pending Immunizations' field and that an 'Alert' icon is shown to the right of the name.
  16. Hover over the 'Alert' icon and validate a tooltip displays stating "Click to view overrides".
  17. Click the 'Alert' icon and validate the 'Drug Interaction' dialog appears in read-only mode.
  18. Validate all information provided is accurate and click [Close].
Scenario 9: Medical Note - Immunizations - Interaction Checking - Therapeutic Class Duplication
Specific Setup:
  • At least two dictionary codes must exist in the Order Entry Client Information ‘(20559) Override Code’ dictionary. (Override Code A) (Override Code B).
  • The ‘(20590) Require Override Text With This Override Code’ extended attribute must be set to “No” in the Order Entry Client Information ‘(20559) Override Code’ dictionary for “Override Code A”.
  • The ‘(20590) Require Override Text With This Override Code’ extended attribute must be set to “Yes” in the Order Entry Client Information ‘(20559) Override Code’ dictionary for “Override Code B”.
  • Please log out of the application and log back in after completing the above configuration.
  • Two pharmacy-type order codes must exist. (Medication A) (Medication B)
  • When "Medication A" and "Medication B" are ordered concurrently, a 'Therapeutic Class Duplication' alert must be created.
  • A procedure-type service code (Immunization A) must be configured in the 'Service Codes' form such that:
  • 'Procedure Type' = "Vaccination/Immunization".
  • 'Medication Equivalent' = "Medication 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" should have no current orders in OrderConnect.
Steps
  1. Select "Client A" and access the Order Entry Console.
  2. Select the 'Home Medications' tab and uncheck the 'Reported' checkbox.
  3. Search for and select "Medication B" from the 'New Order' field.
  4. Fill in any required fields, click [Add to Scratchpad] and [Final Review].
  5. Select "None" in the 'Output' field and click [Sign].
  6. Validate the 'Order grid' contains the new order for "Medication B".
  7. Navigate to the 'Medical Note' tab, click [Add Note], and create a new 'Primary Care' note.
  8. Select the 'Document' tab and then navigate to the 'Immunizations' section.
  9. Click [Add] and then [Order Immunizations], select "Immunization A" from the 'Immunization Search' field and click [Continue].
  10. Validate an 'Alert' banner is displayed, surrounded by a red border, and that it states "Clinical Screening Alert".
  11. Click [Override Alert] and validate a 'Drug Interaction' dialog displays.
  12. Validate a 'Therapeutic Class Duplication' interaction between "Medication B" and "Immunization A" is shown.
  13. Validate both the 'Override Reason' and 'Notes' fields are showing as required.
  14. Validate the 'Save' and 'Save and Close' buttons are disabled.
  15. Select "Override Code A" from the 'Override Reason' field and validate the 'Notes' field is not required.
  16. Validate the 'Save' and 'Save and Close' buttons are enabled.
  17. Click [Save and Close].
  18. Validate an 'Alert' banner is displayed, surrounded by a yellow border, and that it states "Clinical Screening Alert".
  19. Click [View Overrides] and validate the 'Override Reason' and 'Notes' fields are disabled.
  20. Validate the 'Therapeutic Class Duplication' field contains the override reason code provided.
  21. Click [Edit] and validate the 'Override Reason' and 'Notes' fields are enabled.
  22. Select "Override Code B" from the 'Override Reason' field and validate the 'Notes' field is required.
  23. Set the 'Notes' field to any value and click [Save and Close].
  24. Validate an 'Alert' banner is displayed, surrounded by a yellow border, and that it states "Clinical Screening Alert".
  25. Click [View Overrides] and validate the 'Override Reason' and 'Notes' fields are disabled.
  26. Validate the 'Therapeutic Class Duplication' field contains the override reason code and text provided and click [Close].
  27. Fill in any required fields and click [Order].
  28. Validate "Immunization A" is listed in the 'Pending Immunizations' field and that an 'Alert' icon is shown to the right of the name.
  29. Hover over the 'Alert' icon and validate a tooltip displays stating "Click to view overrides".
  30. Click the 'Alert' icon and validate the 'Drug Interaction' dialog appears in read-only mode.
  31. Validate all information provided is accurate and click [Close].
Scenario 10: Medical Note - Immunizations - Pending Orders - Interaction Checking - Therapeutic Class Duplication
Specific Setup:
  • At least one dictionary code must exist in the Order Entry Client Information ‘(20559) Override Code’ dictionary. (Override Code A)
  • The ‘(20590) Require Override Text With This Override Code’ extended attribute must be set to “No” in the Order Entry Client Information ‘(20559) Override Code’ dictionary for “Override Code A”.
  • Please log out of the application and log back in after completing the above configuration.
  • Two pharmacy-type order codes must exist. (Medication A) (Medication B)
  • When "Medication A" and "Medication B" are ordered concurrently, a 'Therapeutic Class Duplication' alert must be created.
  • A procedure-type service code (Immunization A) must be configured in the 'Service Codes' form such that:
  • 'Procedure Type' = "Vaccination/Immunization".
  • 'Medication Equivalent' = "Medication A".
  • A procedure-type service code (Immunization B) must be configured in the 'Service Codes' form such that:
  • 'Procedure Type' = "Vaccination/Immunization".
  • 'Medication Equivalent' = "Medication B".
  • 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" should have no current orders in OrderConnect.
Steps
  1. Search for and select "Client A" and navigate to the 'Medical Note'.
  2. Click [Add Note] and create a new 'Primary Care' note.
  3. Select the 'Document' tab and then navigate to the 'Immunizations' section.
  4. Click [Add] and then [Order Immunizations].
  5. Search for and select "Immunization A" from the 'Immunization Search' field and click [Continue].
  6. Populate any required fields and click [Order].
  7. Click [Add] and then [Order Immunizations], select "Immunization B" from the 'Immunization Search' field and click [Continue].
  8. Validate an 'Alert' banner is displayed, surrounded by a red border, and that it states "Clinical Screening Alert".
  9. Click [Override Alert] and validate a 'Drug Interaction' dialog displays.
  10. Validate a 'Therapeutic Class Duplication' interaction between "Immunization A" and "Immunization B" is shown.
  11. Validate both the 'Override Reason' and 'Notes' fields are showing as required.
  12. Validate the 'Save' and 'Save and Close' buttons are disabled.
  13. Set the 'Notes' field to any value.
  14. Validate the 'Override Reason' field is not required.
  15. Validate the 'Save' and 'Save and Close' buttons are enabled and click [Save and Close].
  16. Validate an 'Alert' banner is displayed, surrounded by a yellow border, and that it states "Clinical Screening Alert".
  17. Fill in any required fields and click [Administer].
  18. Fill in any required fields and click [Save].
  19. Expand the 'Immunization History' table and validate "Immunization B" is listed and that an 'Alert' icon is shown to the right of the name.
  20. Hover over the 'Alert' icon and validate a tooltip displays stating "Click to view overrides".
  21. Click the 'Alert' icon and validate the 'Drug Interaction' dialog appears in read-only mode.
  22. Validate all information provided is accurate and click [Close].
Scenario 11: Medical Note - Immunizations - Interaction Checking - Drug-Allergy Interaction
Specific Setup:
  • At least one dictionary code must exist in the Order Entry Client Information ‘(20559) Override Code’ dictionary. (Override Code A)
  • The ‘(20590) Require Override Text With This Override Code’ extended attribute must be set to “No” in the Order Entry Client Information ‘(20559) Override Code’ dictionary for “Override Code A”.
  • Please log out of the application and log back in after completing the above configuration.
  • A pharmacy-type order code must exist. (Medication A)
  • A procedure-type service code (Immunization A) must be configured in the 'Service Codes' form such that:
  • 'Procedure Type' = "Vaccination/Immunization".
  • 'Medication Equivalent' = "Medication 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" should have no current orders in OrderConnect.
  • "Client A" should have a current allergy with a status of "Confirmed" for "Medication A". (Allergy A)
Steps
  1. Search for and select "Client A" and navigate to the 'Medical Note'.
  2. Click [Add Note] and create a new 'Primary Care' note.
  3. Select the 'Document' tab and then navigate to the 'Immunizations' section.
  4. Click [Add] and then [Order Immunizations].
  5. Search for and select "Immunization A" from the 'Immunization Search' field and click [Continue].
  6. Validate an 'Alert' banner is displayed, surrounded by a red border, and that it states "Clinical Screening Alert".
  7. Click [Override Alert] and validate a 'Drug Interaction' dialog displays.
  8. Validate a 'Drug-allergy' interaction between "Immunization A" and "Allergy A" is shown.
  9. Validate both the 'Override Reason' and 'Notes' fields are showing as required.
  10. Validate the 'Save' and 'Save and Close' buttons are disabled.
  11. Set the 'Override Reason' field to "Override Code A".
  12. Validate the 'Notes' field is not required.
  13. Validate the 'Save' and 'Save and Close' buttons are enabled and click [Save and Close].
  14. Validate an 'Alert' banner is displayed, surrounded by a yellow border, and that it states "Clinical Screening Alert".
  15. Fill in any required fields and click [Order].
  16. Validate "Immunization A" is listed in the 'Pending Immunizations' field and that an 'Alert' icon is shown to the right of the name.
  17. Hover over the 'Alert' icon and validate a tooltip displays stating "Click to view overrides".
  18. Click the 'Alert' icon and validate the 'Drug Interaction' dialog appears in read-only mode.
  19. Validate all information provided is accurate and click [Close].
Scenario 12: Medical Note - Immunizations - Interaction Checking - Multiple Interactions
Specific Setup:
  • At least two dictionary codes must exist in the Order Entry Client Information ‘(20559) Override Code’ dictionary. (Override Code A) (Override Code B).
  • The ‘(20590) Require Override Text With This Override Code’ extended attribute must be set to “No” in the Order Entry Client Information ‘(20559) Override Code’ dictionary for “Override Code A”.
  • The ‘(20590) Require Override Text With This Override Code’ extended attribute must be set to “Yes” in the Order Entry Client Information ‘(20559) Override Code’ dictionary for “Override Code B”.
  • Please log out of the application and log back in after completing the above configuration.
  • Three pharmacy-type order codes must exist. (Medication A)(Medication B)(Medication C)
  • When "Medication A" and "Medication C" are ordered concurrently, a 'Drug-drug interaction' alert must be created.
  • When "Medication B" and "Medication C" are ordered concurrently, a 'Drug-drug interaction' alert must be created.
  • When "Medication A" and "Medication B" are ordered concurrently, a 'Therapeutic Class Duplication' alert must be created.
  • A procedure-type service code (Immunization A) must be configured in the 'Service Codes' form such that:
  • 'Procedure Type' = "Vaccination/Immunization".
  • 'Medication Equivalent' = "Medication A".
  • A procedure-type service code (In-Office A) must be configured in the 'Service Codes' form such that:
  • 'Procedure Type' = "Medication Administration".
  • 'Medication Equivalent' = "Medication C".
  • 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" should have no current orders in OrderConnect.
  • "Client A" should have a current allergy with a status of "Confirmed" for "Medication A". (Allergy A)
Steps
  1. Search for and select "Client A" and navigate to the 'Medical Note'.
  2. Click [Add Note] and create a new 'Primary Care' note.
  3. Select the 'Document' tab and then navigate to the 'In-Office Administrations' section.
  4. Click [Add], search for and select "In-Office A" from the 'In-Office Administrations Search' field and click [Continue].
  5. Populate any required fields and click [Order].
  6. Access the Order Entry Console.
  7. Select the 'Home Medications' tab and uncheck the 'Reported' checkbox.
  8. Search for and select "Medication B" from the 'New Order' field.
  9. Fill in any required fields, click [Add to Scratchpad] and [Final Review].
  10. If an 'Interaction' dialog appears, override all interactions and click [Save Override and Exit].
  11. Select "None" in the 'Output' field and click [Sign].
  12. Validate the 'Order grid' contains the new order for "Medication B".
  13. Navigate to the 'Medical Note' and then to the 'Immunization' section.
  14. Click [Add] and then [Order Immunizations], select "Immunization A" from the 'Immunization Search' field and click [Continue].
  15. Validate an 'Alert' banner is displayed, surrounded by a red border, and that it states "Clinical Screening Alert".
  16. Click [Override Alert] and validate a 'Drug Interaction' dialog displays.
  17. Validate the 'Drug Interaction' dialog contains 'Drug-allergy interaction', 'Drug-drug interaction' and 'Therapeutic Class Duplication' alerts.
  18. Validate no checkbox defaults as "Checked".
  19. Check the 'Drug-allergy interaction' checkbox and select "Override Code A" from the 'Override Reason' field.
  20. Click [Save] and validate a green checkmark is displayed next to the Drug-allergy interaction.
  21. Check the 'Drug-drug interaction' checkbox and set the 'Notes' field to any value.
  22. Click [Save] and validate a green checkmark is displayed next to the Drug-drug interaction.
  23. Click [Close] Validate the 'Alert' banner is displayed, surrounded by a red border, and that it states "Clinical Screening Alert".
  24. Click [Override Alert] and validate the 'Drug Interaction' dialog displays.
  25. Check the 'Therapeutic Class Duplication' checkbox and select "Override Code B" from the 'Override Reason' field.
  26. Validate the 'Notes' field is required and set it to any value.
  27. Click [Save and Close].
  28. Validate an 'Alert' banner is displayed, surrounded by a yellow border, and that it states "Clinical Screening Alert".
  29. Fill in any required fields and click [Order].
  30. Validate "Immunization A" is listed in the 'Pending Immunizations' field and that an 'Alert' icon is shown to the right of the name.
  31. Hover over the 'Alert' icon and validate a tooltip displays stating "Click to view overrides".
  32. Click the 'Alert' icon and validate the 'Drug Interaction' dialog appears in read-only mode.
  33. Validate all information provided is accurate and click [Close].
Topics
• Medical Note
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
Update 19 Summary | Details
ProviderConnect Enterprise - 'Cal-OMS Admission'
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Cal-OMS Admission
  • CareFabric Monitor
  • Registry Settings (PM)
Scenario 1: ProviderConnect Enterprise - Cal-OMS Admission - Validate the 'PutEhrAssessment' action
Specific Setup:
  • Avatar CareFabric->ProviderConnect Enterprise->Contracting Providers->->->Enable External Connections' must be set to "Y"
  • The 'Managing Organization Definition' form must be defined for a valid managing organization
  • Avatar Cal-PM Registry Setting 'Enable LA County Reporting Requirements' may optionally be enabled (set to 'Y' or 'YC')
  • A client must be enrolled in an existing episode and be mapped to the defined managing organization in the 'ProviderConnect Enterprise Identifiers' section of the 'Admission' form (Client A)
  • Client A's episode must be in a program that has "Yes" selected in the 'Substance Abuse Program (Cal-OMS)' field in the 'Program Maintenance' form
Steps
  1. Select "Client A" and access the 'Cal-OMS Admission' form.
  2. Select the desired episode in the Pre-Display and click [OK].
  3. Populate all required and desired fields - including values for one or more fields added to/present in form where Avatar Cal-PM Registry Setting 'Enable LA County Reporting Requirements' is enabled.
  4. Click [Submit].
  5. Access the 'ProviderConnect Enterprise Action Log'.
  6. Enter the desired dates in the 'From Date' and 'Through Date' fields.
  7. Enter the desired times in the 'From Time' and 'Through Time' fields.
  8. Select the desired organization in the 'Managing Organization' field.
  9. Select "PutEhrAssessment" in the 'Action Name' field.
  10. Click [View Action Log].
  11. Validate the 'ProviderConnect Enterprise Action Log' Report is displayed.
  12. Validate the 'ProviderConnect Enterprise Action Log' Report contains the 'PutEhrAssessment' action that was triggered from the 'Cal-OMS Admission' form with a "Success" result.
  13. Close the report and the form.
ProviderConnect Enterprise - 'Cal-OMS Annual Update'
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Cal-OMS Annual Update
  • CareFabric Monitor
  • Registry Settings (PM)
Scenario 1: ProviderConnect Enterprise - Cal-OMS Annual Update - Validate the 'PutEhrAssessment' action
Specific Setup:
  • Avatar CareFabric->ProviderConnect Enterprise->Contracting Providers->->->Enable External Connections' must be set to "Y"
  • The 'Managing Organization Definition' form must be defined for a valid managing organization
  • Avatar Cal-PM Registry Setting 'Enable LA County Reporting Requirements' may optionally be enabled (set to 'Y' or 'YC')
  • A client must be enrolled in an existing episode and be mapped to the defined managing organization in the 'ProviderConnect Enterprise Identifiers' section of the 'Admission' form (Client A)
  • Client A's episode must be in a program that has "Yes" selected in the 'Substance Abuse Program (Cal-OMS)' field in the 'Program Maintenance' form
  • Client A must have a 'Cal-OMS Admission' filed
Steps
  1. Select "Client A" and access the 'Cal-OMS Annual Update' form.
  2. Select the desired episode in the Pre-Display and click [OK].
  3. Populate all required and desired fields - including values for one or more fields added to/present in form where Avatar Cal-PM Registry Setting 'Enable LA County Reporting Requirements' is enabled.
  4. Click [Submit].
  5. Access the 'ProviderConnect Enterprise Action Log'.
  6. Enter the desired dates in the 'From Date' and 'Through Date' fields.
  7. Enter the desired times in the 'From Time' and 'Through Time' fields.
  8. Select the desired organization in the 'Managing Organization' field.
  9. Select "PutEhrAssessment" in the 'Action Name' field.
  10. Click [View Action Log].
  11. Validate the 'ProviderConnect Enterprise Action Log' Report is displayed.
  12. Validate the 'ProviderConnect Enterprise Action Log' Report contains the 'PutEhrAssessment' action that was triggered from the 'Cal-OMS Annual Update' form with a "Success" result.
  13. Close the report and the form.
ProviderConnect Enterprise - 'Cal-OMS Discharge'
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Cal-OMS Youth/Detox Discharge
  • CareFabric Monitor
  • Registry Settings (PM)
  • Cal-OMS Discharge
  • Cal-OMS Administrative Discharge
Scenario 1: ProviderConnect Enterprise - Cal-OMS Youth/Detox Discharge - Validate the 'PutEhrAssessment' action
Specific Setup:
  • Avatar CareFabric->ProviderConnect Enterprise->Contracting Providers->->->Enable External Connections' must be set to "Y"
  • The 'Managing Organization Definition' form must be defined for a valid managing organization
  • Avatar Cal-PM Registry Setting 'Enable LA County Reporting Requirements' may optionally be enabled (set to 'Y' or 'YC')
  • A client must be enrolled in an existing episode and be mapped to the defined managing organization in the 'ProviderConnect Enterprise Identifiers' section of the 'Admission' form (Client A)
  • Client A's episode must be in a program that has "Yes" selected in the 'Substance Abuse Program (Cal-OMS)' field in the 'Program Maintenance' form
  • Client A must be a youth and have a 'Cal-OMS Admission' filed
Steps
  1. Select "Client A" and access the 'Cal-OMS Youth/Detox Discharge' form.
  2. Select the desired episode in the Pre-Display and click [OK].
  3. Populate all required and desired fields - including values for one or more fields added to/present in form where Avatar Cal-PM Registry Setting 'Enable LA County Reporting Requirements' is enabled.
  4. Click [Submit].
  5. Access the 'ProviderConnect Enterprise Action Log'.
  6. Enter the desired dates in the 'From Date' and 'Through Date' fields.
  7. Enter the desired times in the 'From Time' and 'Through Time' fields.
  8. Select the desired organization in the 'Managing Organization' field.
  9. Select "PutEhrAssessment" in the 'Action Name' field.
  10. Click [View Action Log].
  11. Validate the 'ProviderConnect Enterprise Action Log' Report is displayed.
  12. Validate the 'ProviderConnect Enterprise Action Log' Report contains the 'PutEhrAssessment' action that was triggered from the 'Cal-OMS Youth/Detox Discharge' form with a "Success" result.
  13. Close the report and the form.
Scenario 2: ProviderConnect Enterprise - Cal-OMS Discharge - Validate the 'PutEhrAssessment' action
Specific Setup:
  • Avatar CareFabric->ProviderConnect Enterprise->Contracting Providers->->->Enable External Connections' must be set to "Y"
  • The 'Managing Organization Definition' form must be defined for a valid managing organization
  • Avatar Cal-PM Registry Setting 'Enable LA County Reporting Requirements' may optionally be enabled (set to 'Y' or 'YC')
  • A client must be enrolled in an existing episode and be mapped to the defined managing organization in the 'ProviderConnect Enterprise Identifiers' section of the 'Admission' form (Client A)
  • Client A's episode must be in a program that has "Yes" selected in the 'Substance Abuse Program (Cal-OMS)' field in the 'Program Maintenance' form
  • Client A must have a 'Cal-OMS Admission' filed
Steps
  1. Select "Client A" and access the 'Cal-OMS Discharge' form.
  2. Select the desired episode in the Pre-Display and click [OK].
  3. Populate all required and desired fields - including values for one or more fields added to/present in form where Avatar Cal-PM Registry Setting 'Enable LA County Reporting Requirements' is enabled.
  4. Click [Submit].
  5. Access the 'ProviderConnect Enterprise Action Log'.
  6. Enter the desired dates in the 'From Date' and 'Through Date' fields.
  7. Enter the desired times in the 'From Time' and 'Through Time' fields.
  8. Select the desired organization in the 'Managing Organization' field.
  9. Select "PutEhrAssessment" in the 'Action Name' field.
  10. Click [View Action Log].
  11. Validate the 'ProviderConnect Enterprise Action Log' Report is displayed.
  12. Validate the 'ProviderConnect Enterprise Action Log' Report contains the 'PutEhrAssessment' action that was triggered from the 'Cal-OMS Discharge' form with a "Success" result.
  13. Close the report and the form.
Scenario 3: ProviderConnect Enterprise - Cal-OMS Administrative Discharge - Validate the 'PutEhrAssessment' action
Specific Setup:
  • Avatar CareFabric->ProviderConnect Enterprise->Contracting Providers->->->Enable External Connections' must be set to "Y"
  • The 'Managing Organization Definition' form must be defined for a valid managing organization
  • Avatar Cal-PM Registry Setting 'Enable LA County Reporting Requirements' may optionally be enabled (set to 'Y' or 'YC')
  • A client must be enrolled in an existing episode and be mapped to the defined managing organization in the 'ProviderConnect Enterprise Identifiers' section of the 'Admission' form (Client A)
  • Client A's episode must be in a program that has "Yes" selected in the 'Substance Abuse Program (Cal-OMS)' field in the 'Program Maintenance' form
  • Client A must have a 'Cal-OMS Admission' filed
Steps
  1. Select "Client A" and access the 'Cal-OMS Administrative Discharge' form.
  2. Select the desired episode in the Pre-Display and click [OK].
  3. Populate all required and desired fields - including values for one or more fields added to/present in form where Avatar Cal-PM Registry Setting 'Enable LA County Reporting Requirements' is enabled.
  4. Click [Submit].
  5. Access the 'ProviderConnect Enterprise Action Log'.
  6. Enter the desired dates in the 'From Date' and 'Through Date' fields.
  7. Enter the desired times in the 'From Time' and 'Through Time' fields.
  8. Select the desired organization in the 'Managing Organization' field.
  9. Select "PutEhrAssessment" in the 'Action Name' field.
  10. Click [View Action Log].
  11. Validate the 'ProviderConnect Enterprise Action Log' Report is displayed.
  12. Validate the 'ProviderConnect Enterprise Action Log' Report contains the 'PutEhrAssessment' action that was triggered from the 'Cal-OMS Administrative Discharge' form with a "Success" result.
  13. Close the report and the form.
Topics
• Cal-OMS • ProviderConnect Enterprise
Update 20 Summary | Details
Medical Note - Appointment Date
Scenario 1: Medical Note - Add Appointment from Scheduling Calendar, validate My Draft Notes() button return the right number count
Specific Setup:
  • Avatar CareFabric 2024 Update 20 and CarePOV.E&M Note 2.20.0 are needed in order to utilize full functionality.
  • Must be logged in as a user who is configured as a provider. (User A)
  • An outpatient program must exist. (Program A)
  • A client must have an active episode in "Program A", and have been admitted prior to January 22,2024. (Client A)
Steps
  1. Select "Client A", access the 'Medical Note' widget and take note of the count for 'Today's Appts/Notes' and 'My Draft Notes'.
  2. Navigate to the 'Scheduling Calendar' form.
  3. Right click inside the calendar and click [Add Appointment].
  4. Create a new appointment such that:
  5. 'Client' = "Client A".
  6. 'Appointment Status' = "Scheduled".
  7. 'Appointment Date' = "Today's Date".
  8. Complete any remaining required fields and click [Submit].
  9. Close out of the 'Scheduling Calendar' form and Navigate to the 'Medical Note' tab.
  10. Validate the counter for 'Today's Appts/Notes' and 'My Draft Notes' has increased by one.
  11. Navigate to the 'Scheduling Calendar' form.
  12. Create four new appointments for "Client A" such that:
  13. 'Appointment Date' = 3/06/2024.
  14. 'Appointment Date' = 2/01/2024.
  15. 'Appointment Date' = 1/22/2024.
  16. 'Appointment Date' = 3/11/2024.
  17. Close out of the 'Scheduling Calendar' form and Navigate to the 'Medical Note' tab.
  18. Validate the counter for 'Today's Appts/Notes' has remained the same and the counter for 'My Draft Notes' has increased by four.
  19. Click [Select Note] and validate all available notes are listed in chronological order.
  20. Click on [My Draft Notes] and validate all available notes are listed in chronological order.
  21. Launch the 'Scheduling Calendar' form.
  22. Right click [Add Appointment]
  23. Right click inside the calendar and click [Add Appointment].
  24. Create a new appointment such that:
  25. 'Client' = "Client A".
  26. 'Appointment Status' = "Scheduled".
  27. 'Appointment Date' = "a future date".
  28. Complete any remaining required fields and click [Submit].
  29. Navigate to Medical Note
  30. Validate the counter for 'Today's Appts/Notes' and 'My Draft Notes' has remained the same.
  31. Launch 'Scheduling Calendar' form.
  32. Right click on the appointment for today's date for "Client A" and click [Copy].
  33. Right Click on the 'Scheduling Calendar' grid for today's date and click [Paste Appointment].
  34. Validate a 'Warning-Same Day Existing Appointment(s)' message stating "Client "Client A" has the following appointment(s) scheduled" and click [OK].
  35. Close out of the 'Scheduling Calendar' form and Navigate to the 'Medical Note' tab.
  36. Validate the counter for 'Today's Appts/Notes' and 'My Draft Notes' has increased by one.
  37. Launch the 'Scheduling Calendar' form.
  38. Right click on one of the appointments for today's date and click [Delete].
  39. Validate a popup stating "Are you sure" appears and click [Yes].
  40. Close out of the 'Scheduling Calendar' form and Navigate to the 'Medical Note' tab.
  41. Validate the counter for 'Today's Appts/Notes' and 'My Draft Notes' has decreased by one.
  42. Click [Select Note] and validate there is no row for the deleted appointment date/time.
Scenario 2: Medical Note - Validate My Draft Notes() button returned the right number count
Specific Setup:
  • Avatar CareFabric 2024 Update 20 and CarePOV.E&M Note 2.20.0 are needed in order to utilize full functionality.
  • Must be logged in as a user who is configured as a provider. (User A)
  • An outpatient program must exist. (Program A)
  • A client must have an active episode in "Program A", and have been admitted more than 90 days ago. (Client A)
Steps
  1. Select "Client A" and access the 'Medical Note' widget.
  2. Take note of the [Today's Appts/Notes (X)] and [My Draft Notes (X] buttons.
  3. Click [Add Note] and create a new note for "Client A" such that:
  4. 'Date of Service/Note' = "Today's Date".
  5. 'Time of Service /Note' = "08:00 am".
  6. 'Duration' = "15".
  7. Complete any remaining required fields, click [Save] and [Refresh].
  8. Validate the counter for 'Today's Appts/Notes' and 'My Draft Notes' has increased by one.
  9. Click [My Draft Notes]
  10. Validate the 'Date of Service/Note' column contains a row with "Today's date" and the 'Service Time' column shows "08:00-08:15".
  11. Click [Add Note] and create a new note for "Client A" such that:
  12. 'Date of Service/Note' = "30 days ago".
  13. Complete any remaining required fields, click [Save] and [Refresh].
  14. Validate the counter for 'Today's Appts/Notes' has not changed but the counter for 'My Draft Notes' has increased by one.
  15. Click [Add Note] and create a new note for "Client A" such that:
  16. 'Date of Service/Note' = "60 days ago".
  17. Complete any remaining required fields, click [Save] and [Refresh].
  18. Validate the counter for 'Today's Appts/Notes' has not changed but the counter for 'My Draft Notes' has increased by one.
  19. Click [Add Note] and create a new note for "Client A" such that:
  20. 'Date of Service/Note' = ">90 days ago".
  21. Complete any remaining required fields, click [Save] and [Refresh].
  22. Validate the counter for 'Today's Appts/Notes' and 'My Draft Notes' has remained the same.
  23. Click [Select Note].
  24. Validate the 'Date of Service/Note' column contains a row for all notes added except for the note created with a 'Date of Service/Note' greater than 90 days in the past.
  25. Validate all appointments appear in Chronological order
  26. Click [My Draft Notes]
  27. Validate the 'Date of Service/Note' column contains a row for all notes added except for the note created with a 'Date of Service/Note' greater than 90 days in the past.
  28. Validate appointment appears in Chronological order
  29. Navigate to the 'Scheduling Calendar' form.
  30. Validate all 4 newly created appointments were added to the calendar.
Medical Note - Non-Provider Documentation
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Facesheet.Lab Results
  • Client Ledger
  • Facesheet.Lab Results.Results Pending Review
Scenario 1: Medical Note - Nurse - Full Work flow
Specific Setup:
  • Avatar CareFabric 2024 Update 20 and CarePOV.E&M Note 2.20.0 are needed in order to utilize full functionality.
  • The ‘(37) CPT Code Recommendation’ extended attribute must be set to “No” in the Other Tabled Files ‘(31) Group Code’ dictionary for “Psychiatric Evaluation”. (Group Code A)
  • Please log out of the application and log back in after completing the above configuration.
  • A service code (Service Code A) must be configured in the 'Service Codes' form such that;
  1. 'Is This Service A Visit' field = "Yes".
  2. 'Service Code Type' field = "Evaluation Management".
  3. 'Group Code' field = "Group Code A".
  • An outpatient program must exist. (Program A)
  • A client must have an active episode in "Program A". (Client A)
  • Must be logged in as a user who is configured as a nurse. (User A)
Steps
  1. Search for and select "Client A" and navigate to the 'Medical Note'.
  2. Click [Add Note].
  3. Create a 'Psychiatry' note such that;
  4. 'Provider' field = "User A".
  5. 'Service Code' field = "Service Code A".
  6. Fill out all required fields and click [Save].
  7. Select the 'Facesheet' tab.
  8. Click the 'Lab Results' section.
  9. Click 'Add/Edit Point of Care Results' field.
  10. Set a value for any lab result and click [Save].
  11. Validate the lab is displayed in the 'Results Pending Review' grid.
  12. Set the 'Start Date' to a date two days from now.
  13. Set the 'End Date' to a date ten days from now.
  14. Click the 'Search' field.
  15. Validate "No Lab Results" is displayed in the 'Results Pending Review' grid.
  16. Click the '7 days' field and the 'Search' field.
  17. Validate the lab is displayed in the 'Results Pending Review' grid.
  18. Navigate to the 'Vitals' section and click [Add].
  19. Validate the 'Date Taken' field is set to "Today's Date" and the 'Refused Vitals' field is set to "No".
  20. Complete any desired fields in the 'Vitals' section and click [Save].
  21. Click [Pull to Note], check the 'Select All' checkbox and click [Save].
  22. Select the ‘Document’ tab.
  23. Validate the 'Chief Complaint' and 'HPI' sections are not required and complete the sections.
  24. Select the ‘Finalize’ tab.
  25. Populate all required fields and click [Generate Note].
  26. Validate the ‘Note Summary’ is displayed and contains the appropriate information:
  27. The populated sections of the 'Facesheet' tab that were pulled into the note. (Vitals)
  28. The not required and populated sections of the 'Document' tab. (Chief Complaint and HPI)
  29. 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 - Create Note By Another Provider Setting Nurse As Provider
Specific Setup:
  • Avatar CareFabric 2024 Update 20 and CarePOV.E&M Note 2.20.0 are needed in order to utilize full functionality.
  • The ‘(37) CPT Code Recommendation’ extended attribute must be set to “No” in the Other Tabled Files ‘(31) Group Code’ dictionary for “Psychiatric Evaluation”. (Group Code A)
  • Please log out of the application and log back in after completing the above configuration.
  • A service code (Service Code A) must be configured in the 'Service Codes' form such that;
  1. 'Is This Service A Visit' field = "Yes".
  2. 'Service Code Type' field = "Evaluation Management".
  3. 'Group Code' field = "Group Code 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
  1. Log into the application as "User A".
  2. Search for and select "Client A" and navigate to the 'Medical Note'.
  3. Click [Add Note].
  4. Create a 'Psychiatry' note such that;
  5. 'Provider' field = "User A".
  6. 'Service Code' field = "Service Code A".
  7. Fill out any remaining required fields and click [Save].
  8. Click [Add Note].
  9. Create a 'Psychiatry' note such that;
  10. 'Provider' field = "User B".
  11. 'Service Code' field = "Service Code A".
  12. Fill out any remaining required fields and click [Save].
  13. Click [Send To Do].
  14. Set "User B" in the 'To-Do Recipient'.
  15. Set the 'Notes' field to any value and click [Send].
  16. Log out of the application and log back in as "User B".
  17. Access the 'My To Do's' widget.
  18. Select "Client A" from the 'Additional ToDos' list and click [Review To Do Item].
  19. Click [Select Note].
  20. Validate the note with "User A" as the provider is displayed without a [Delete] option.
  21. Validate the note with "User B" as the provider is displayed including a [Delete] option.
  22. Refresh 'Medical Note' and click ['Today's Appts/Notes'].
  23. Search for and select "User A" in the 'Providers' field.
  24. Validate the note with "User A" as the provider is displayed without a [Delete] option.
  25. Validate the note with "User B" as the provider is displayed including a [Delete] option.
  26. Click [My Draft Notes].
  27. Validate the note with "User B" as the provider is displayed including a [Delete] and [Edit] option.
  28. Click [Edit].
  29. Select the ‘Document’ tab.
  30. Validate the 'Chief Complaint', 'HPI' and 'Mental Status Exam' sections are not required and complete the sections.
  31. Select the ‘Finalize’ tab.
  32. Populate all required fields and click [Generate Note].
  33. Validate the ‘Note Summary’ is displayed and contains the appropriate information:
  34. The not required and populated sections of the 'Document' tab. (Chief Complaint, HPI and Mental Status Exam)
  35. 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 - Nurse - Primary Care - Full Work Flow
Specific Setup:
  • Avatar CareFabric 2024 Update 20 and CarePOV.E&M Note 2.20.0 are needed in order to utilize full functionality.
  • The ‘(37) CPT Code Recommendation’ extended attribute must be set to “No” in the Other Tabled Files ‘(31) Group Code’ dictionary for “Psychiatric Evaluation”. (Group Code A)
  • Please log out of the application and log back in after completing the above configuration.
  • A service code (Service Code A) must be configured in the 'Service Codes' form such that;
  1. 'Is This Service A Visit' field = "Yes".
  2. 'Service Code Type' field = "Evaluation Management".
  3. 'Group Code' field = "Group Code 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)
  • Must be logged in as a user who is configured as a nurse. (User A)
Steps
  1. Search for and select "Client A" and navigate to the 'Medical Note'.
  2. Click [Add Note].
  3. Create a 'Primary Care' note such that;
  4. 'Provider' field = "User A".
  5. 'Service Code' field = "Service Code A".
  6. Fill out all required fields and click [Save].
  7. Select the ‘Document’ tab.
  8. Validate the 'Chief Complaint', 'HPI' and 'Physical Exam' sections are not required and complete the sections.
  9. Select the ‘Finalize’ tab.
  10. Populate all required fields and click [Generate Note].
  11. Validate the ‘Note Summary’ is displayed and contains the appropriate information:
  12. The not required and populated sections of the 'Document' tab. (Chief Complaint, HPI and Physical Exam)
  13. Click [Sign Off] validate the Document is displayed and click [Accept], set the ‘Password’ field to the appropriate value and click [Verify].
Scenario 4: Medical Note - Nurse Completing Procedure From Different Providers Finalized Note
Specific Setup:
  • Avatar CareFabric 2024 Update 20 and CarePOV.E&M Note 2.20.0 are needed in order to utilize full functionality.
  • A procedure-type service code must be configured in the 'Service Codes' form. (Medication A)
  • The ‘(37) CPT Code Recommendation’ extended attribute must be set to “No” in the Other Tabled Files ‘(31) Group Code’ dictionary for “Psychiatric Evaluation”. (Group Code A)
  • Please log out of the application and log back in after completing the above configuration.
  • A service code (Service Code A) must be configured in the 'Service Codes' form such that;
  1. 'Is This Service A Visit' field = "Yes".
  2. 'Service Code Type' field = "Evaluation Management".
  3. 'Group Code' field = "Group Code 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
  1. Log into the application as "User A".
  2. Search for and select "Client A" and navigate to the 'Medical Note' tab.
  3. Click [Add Note].
  4. Create a 'Psychiatry' note such that;
  5. 'Provider' field = "User A".
  6. 'Service Code' field = "Service Code A".
  7. Fill out any remaining required fields and click [Save].
  8. Select the 'Document' tab and then navigate to the 'Procedure' section.
  9. Click [Add] and select "Medication A" from the 'Procedure Search' field.
  10. Select ‘Diagnosis’ and enter a diagnosis.
  11. Click the 'Active' field.
  12. Click the 'Routine' field.
  13. Populate all remaining required fields and click [Save].
  14. Validate the 'Current Procedures' field contains a row for "Medication A".
  15. Populate all required sections in the 'Document' tab.
  16. Select the ‘Finalize’ tab.
  17. Populate all required fields and click [Generate Note].
  18. Validate the ‘Note Summary’ is displayed and contains the appropriate information and click [Sign Off].
  19. Validate the Document is displayed and click [Accept], set the ‘Password’ field to the appropriate value and click [Verify].
  20. Log out of the application and log back in as "User B".
  21. Search for and select "Client A" and navigate to the 'Medical Note'.
  22. Click [Add Note].
  23. Create a 'Psychiatry' note such that;
  24. 'Provider' field = "User B".
  25. 'Service Code' field = "Service Code A".
  26. Select the 'Document' tab and then navigate to the 'Procedure' section.
  27. Validate the 'Diagnosis' section is not required.
  28. Validate the 'MDM' section does not exist.
  29. Validate the 'Current Procedures' field contains a row for "Medication A".
  30. Click [Complete] and [Save].
  31. Validate the 'Current Procedures' field contains a row for "Medication A" marked as complete.
Medical Note - Draft Count
Scenario 1: Medical Note - Add Appointment from Scheduling Calendar, validate My Draft Notes() button return the right number count
Specific Setup:
  • Avatar CareFabric 2024 Update 20 and CarePOV.E&M Note 2.20.0 are needed in order to utilize full functionality.
  • Must be logged in as a user who is configured as a provider. (User A)
  • An outpatient program must exist. (Program A)
  • A client must have an active episode in "Program A", and have been admitted prior to January 22,2024. (Client A)
Steps
  1. Select "Client A", access the 'Medical Note' widget and take note of the count for 'Today's Appts/Notes' and 'My Draft Notes'.
  2. Navigate to the 'Scheduling Calendar' form.
  3. Right click inside the calendar and click [Add Appointment].
  4. Create a new appointment such that:
  5. 'Client' = "Client A".
  6. 'Appointment Status' = "Scheduled".
  7. 'Appointment Date' = "Today's Date".
  8. Complete any remaining required fields and click [Submit].
  9. Close out of the 'Scheduling Calendar' form and Navigate to the 'Medical Note' tab.
  10. Validate the counter for 'Today's Appts/Notes' and 'My Draft Notes' has increased by one.
  11. Navigate to the 'Scheduling Calendar' form.
  12. Create four new appointments for "Client A" such that:
  13. 'Appointment Date' = 3/06/2024.
  14. 'Appointment Date' = 2/01/2024.
  15. 'Appointment Date' = 1/22/2024.
  16. 'Appointment Date' = 3/11/2024.
  17. Close out of the 'Scheduling Calendar' form and Navigate to the 'Medical Note' tab.
  18. Validate the counter for 'Today's Appts/Notes' has remained the same and the counter for 'My Draft Notes' has increased by four.
  19. Click [Select Note] and validate all available notes are listed in chronological order.
  20. Click on [My Draft Notes] and validate all available notes are listed in chronological order.
  21. Launch the 'Scheduling Calendar' form.
  22. Right click [Add Appointment]
  23. Right click inside the calendar and click [Add Appointment].
  24. Create a new appointment such that:
  25. 'Client' = "Client A".
  26. 'Appointment Status' = "Scheduled".
  27. 'Appointment Date' = "a future date".
  28. Complete any remaining required fields and click [Submit].
  29. Navigate to Medical Note
  30. Validate the counter for 'Today's Appts/Notes' and 'My Draft Notes' has remained the same.
  31. Launch 'Scheduling Calendar' form.
  32. Right click on the appointment for today's date for "Client A" and click [Copy].
  33. Right Click on the 'Scheduling Calendar' grid for today's date and click [Paste Appointment].
  34. Validate a 'Warning-Same Day Existing Appointment(s)' message stating "Client "Client A" has the following appointment(s) scheduled" and click [OK].
  35. Close out of the 'Scheduling Calendar' form and Navigate to the 'Medical Note' tab.
  36. Validate the counter for 'Today's Appts/Notes' and 'My Draft Notes' has increased by one.
  37. Launch the 'Scheduling Calendar' form.
  38. Right click on one of the appointments for today's date and click [Delete].
  39. Validate a popup stating "Are you sure" appears and click [Yes].
  40. Close out of the 'Scheduling Calendar' form and Navigate to the 'Medical Note' tab.
  41. Validate the counter for 'Today's Appts/Notes' and 'My Draft Notes' has decreased by one.
  42. Click [Select Note] and validate there is no row for the deleted appointment date/time.
Scenario 2: Medical Note - Validate My Draft Notes() button returned the right number count
Specific Setup:
  • Avatar CareFabric 2024 Update 20 and CarePOV.E&M Note 2.20.0 are needed in order to utilize full functionality.
  • Must be logged in as a user who is configured as a provider. (User A)
  • An outpatient program must exist. (Program A)
  • A client must have an active episode in "Program A", and have been admitted more than 90 days ago. (Client A)
Steps
  1. Select "Client A" and access the 'Medical Note' widget.
  2. Take note of the [Today's Appts/Notes (X)] and [My Draft Notes (X] buttons.
  3. Click [Add Note] and create a new note for "Client A" such that:
  4. 'Date of Service/Note' = "Today's Date".
  5. 'Time of Service /Note' = "08:00 am".
  6. 'Duration' = "15".
  7. Complete any remaining required fields, click [Save] and [Refresh].
  8. Validate the counter for 'Today's Appts/Notes' and 'My Draft Notes' has increased by one.
  9. Click [My Draft Notes]
  10. Validate the 'Date of Service/Note' column contains a row with "Today's date" and the 'Service Time' column shows "08:00-08:15".
  11. Click [Add Note] and create a new note for "Client A" such that:
  12. 'Date of Service/Note' = "30 days ago".
  13. Complete any remaining required fields, click [Save] and [Refresh].
  14. Validate the counter for 'Today's Appts/Notes' has not changed but the counter for 'My Draft Notes' has increased by one.
  15. Click [Add Note] and create a new note for "Client A" such that:
  16. 'Date of Service/Note' = "60 days ago".
  17. Complete any remaining required fields, click [Save] and [Refresh].
  18. Validate the counter for 'Today's Appts/Notes' has not changed but the counter for 'My Draft Notes' has increased by one.
  19. Click [Add Note] and create a new note for "Client A" such that:
  20. 'Date of Service/Note' = ">90 days ago".
  21. Complete any remaining required fields, click [Save] and [Refresh].
  22. Validate the counter for 'Today's Appts/Notes' and 'My Draft Notes' has remained the same.
  23. Click [Select Note].
  24. Validate the 'Date of Service/Note' column contains a row for all notes added except for the note created with a 'Date of Service/Note' greater than 90 days in the past.
  25. Validate all appointments appear in Chronological order
  26. Click [My Draft Notes]
  27. Validate the 'Date of Service/Note' column contains a row for all notes added except for the note created with a 'Date of Service/Note' greater than 90 days in the past.
  28. Validate appointment appears in Chronological order
  29. Navigate to the 'Scheduling Calendar' form.
  30. Validate all 4 newly created appointments were added to the calendar.
Topics
• Medical Note • NX
Update 21 Summary | Details
ProviderConnect Enterprise - 'Admission' data
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Update Client Data
  • CareFabric Monitor
Scenario 1: ProviderConnect Enterprise- Validate the 'PutProgramAdmission' action
Specific Setup:
  • The 'Avatar CareFabric->ProviderConnect Enterprise->Contracting Providers->->->Enable External Connections' must be set to "Y".
  • The 'Managing Organization Definition' form must be configured for a valid managing organization.
  • A client must exist in the configured managing organization's system with the following on file: 'Date of Birth' and 'Social Security Number' (Client A).
  • A practitioner must have a NPI that is mapped to a matching practitioner in the managing organization's system (Practitioner A).
Steps
  1. Access the 'Admission' form.
  2. Verify the 'Select Client' dialog is displayed.
  3. Enter the last name of the client that exists in the managing organization's system in the 'Last Name' field.
  4. Enter the first name of the client that exists in the managing organization's system in the 'First Name' field.
  5. Enter the sex of the client that exists in the managing organization's system in the 'Sex' field.
  6. Click [Search].
  7. Validate a "Search Results" message is displayed stating: No matches found.
  8. Click [OK] and [New Client].
  9. Validate a "Client" message is displayed stating: Auto Assign Next ID Number?
  10. Click [Yes].
  11. Enter the desired date in the 'Preadmit/Admission Date' field.
  12. Enter the desired time in the 'Preadmit/Admission Time' field.
  13. Select any program that is selected in the 'Associated Admission Programs' field in the 'Managing Organization Definition' form in the 'Program' field.
  14. Select the desired value in the 'Type Of Admission' field.
  15. Select desired value in the 'Source Of Admission' field.
  16. Enter "Practitioner A" in the 'Admitting Practitioner' field.
  17. Enter "Practitioner A" in the 'Attending Practitioner' field.
  18. Select the "Other Client Data" section.
  19. Select "Yes" in the 'Informed of Smoking Policy' field.
  20. Select the "ProviderConnect Enterprise Identifiers" section.
  21. Click [Add New Item].
  22. Select the defined managing organization in the 'External Organization' field.
  23. Click [Search].
  24. Select the matching client record in the 'Select Matching Client Record' dialog.
  25. Click [OK].
  26. Validate the 'External ID' field contains the client ID for the client in the managing organization's system.
  27. Click [Update Demographics].
  28. Validate an "Information" message is displayed stating: Client Demographics Information Updated.
  29. Click [OK].
  30. Select the "Admission" section.
  31. Validate the 'Date of Birth' field contains the value on file in the managing organization's system.
  32. Validate the 'Social Security Number' field contains the value on file in the managing organization's system.
  33. Click [Submit].
  34. Access the 'ProviderConnect Enterprise Action Log'.
  35. Enter the desired date in the 'From Date' and 'Through Date' fields.
  36. Enter the desired time in the 'From Time' and 'Through Time' fields.
  37. Select the desired organization in the 'Managing Organization' field.
  38. Select "PutProgramAdmission" in the 'Action Name' field.
  39. Click [View Action Log].
  40. Verify the 'ProviderConnect Enterprise Action Log' Report is displayed.
  41. Validate the 'ProviderConnect Enterprise Action Log' Report contains a row for the 'PutProgramAdmission' action that was triggered from the 'Admission' form with a result of "Success".
  42. Close the report and the form.
Scenario 2: ProviderConnect Enterprise- Validate the 'PutProgramAdmission' action
Specific Setup:
  • The 'Avatar CareFabric->ProviderConnect Enterprise->Contracting Providers->->->Enable External Connections' must be set to "Y".
  • The 'Managing Organization Definition' form must be configured for a valid managing organization.
  • A client must exist in the configured managing organization's system with the following on file: 'Date of Birth' and 'Social Security Number' (Client A).
  • A practitioner must have a NPI that is mapped to a matching practitioner in the managing organization's system (Practitioner A).
Steps
  1. Access the 'Admission' form.
  2. Verify the 'Select Client' dialog is displayed.
  3. Enter the last name of the client that exists in the managing organization's system in the 'Last Name' field.
  4. Enter the first name of the client that exists in the managing organization's system in the 'First Name' field.
  5. Enter the sex of the client that exists in the managing organization's system in the 'Sex' field.
  6. Click [Search].
  7. Validate a "Search Results" message is displayed stating: No matches found.
  8. Click [OK] and [New Client].
  9. Validate a "Client" message is displayed stating: Auto Assign Next ID Number?
  10. Click [Yes].
  11. Enter the desired date in the 'Preadmit/Admission Date' field.
  12. Enter the desired time in the 'Preadmit/Admission Time' field.
  13. Select any program that is selected in the 'Associated Admission Programs' field in the 'Managing Organization Definition' form in the 'Program' field.
  14. Select the desired value in the 'Type Of Admission' field.
  15. Select desired value in the 'Source Of Admission' field.
  16. Enter "Practitioner A" in the 'Admitting Practitioner' field.
  17. Enter "Practitioner A" in the 'Attending Practitioner' field.
  18. Select the "Other Client Data" section.
  19. Select "Yes" in the 'Informed of Smoking Policy' field.
  20. Select the "ProviderConnect Enterprise Identifiers" section.
  21. Click [Add New Item].
  22. Select the defined managing organization in the 'External Organization' field.
  23. Click [Search].
  24. Select the matching client record in the 'Select Matching Client Record' dialog.
  25. Click [OK].
  26. Validate the 'External ID' field contains the client ID for the client in the managing organization's system.
  27. Click [Update Demographics].
  28. Validate an "Information" message is displayed stating: Client Demographics Information Updated.
  29. Click [OK].
  30. Select the "Admission" section.
  31. Validate the 'Date of Birth' field contains the value on file in the managing organization's system.
  32. Validate the 'Social Security Number' field contains the value on file in the managing organization's system.
  33. Click [Submit].
  34. Access the 'ProviderConnect Enterprise Action Log'.
  35. Enter the desired date in the 'From Date' and 'Through Date' fields.
  36. Enter the desired time in the 'From Time' and 'Through Time' fields.
  37. Select the desired organization in the 'Managing Organization' field.
  38. Select "PutProgramAdmission" in the 'Action Name' field.
  39. Click [View Action Log].
  40. Verify the 'ProviderConnect Enterprise Action Log' Report is displayed.
  41. Validate the 'ProviderConnect Enterprise Action Log' Report contains a row for the 'PutProgramAdmission' action that was triggered from the 'Admission' form with a result of "Success".
  42. Close the report and the form.
Scenario 3: ProviderConnect Enterprise- Validate the 'PutProgramAdmission' action
Specific Setup:
  • The 'Avatar CareFabric->ProviderConnect Enterprise->Contracting Providers->->->Enable External Connections' must be set to "Y".
  • The 'Managing Organization Definition' form must be configured for a valid managing organization.
  • A client must exist in the configured managing organization's system with the following on file: 'Date of Birth' and 'Social Security Number' (Client A).
  • A practitioner must have a NPI that is mapped to a matching practitioner in the managing organization's system (Practitioner A).
Steps
  1. Access the 'Admission' form.
  2. Verify the 'Select Client' dialog is displayed.
  3. Enter the last name of the client that exists in the managing organization's system in the 'Last Name' field.
  4. Enter the first name of the client that exists in the managing organization's system in the 'First Name' field.
  5. Enter the sex of the client that exists in the managing organization's system in the 'Sex' field.
  6. Click [Search].
  7. Validate a "Search Results" message is displayed stating: No matches found.
  8. Click [OK] and [New Client].
  9. Validate a "Client" message is displayed stating: Auto Assign Next ID Number?
  10. Click [Yes].
  11. Enter the desired date in the 'Preadmit/Admission Date' field.
  12. Enter the desired time in the 'Preadmit/Admission Time' field.
  13. Select any program that is selected in the 'Associated Admission Programs' field in the 'Managing Organization Definition' form in the 'Program' field.
  14. Select the desired value in the 'Type Of Admission' field.
  15. Select desired value in the 'Source Of Admission' field.
  16. Enter "Practitioner A" in the 'Admitting Practitioner' field.
  17. Enter "Practitioner A" in the 'Attending Practitioner' field.
  18. Select the "Other Client Data" section.
  19. Select "Yes" in the 'Informed of Smoking Policy' field.
  20. Select the "ProviderConnect Enterprise Identifiers" section.
  21. Click [Add New Item].
  22. Select the defined managing organization in the 'External Organization' field.
  23. Click [Search].
  24. Select the matching client record in the 'Select Matching Client Record' dialog.
  25. Click [OK].
  26. Validate the 'External ID' field contains the client ID for the client in the managing organization's system.
  27. Click [Update Demographics].
  28. Validate an "Information" message is displayed stating: Client Demographics Information Updated.
  29. Click [OK].
  30. Select the "Admission" section.
  31. Validate the 'Date of Birth' field contains the value on file in the managing organization's system.
  32. Validate the 'Social Security Number' field contains the value on file in the managing organization's system.
  33. Click [Submit].
  34. Access the 'ProviderConnect Enterprise Action Log'.
  35. Enter the desired date in the 'From Date' and 'Through Date' fields.
  36. Enter the desired time in the 'From Time' and 'Through Time' fields.
  37. Select the desired organization in the 'Managing Organization' field.
  38. Select "PutProgramAdmission" in the 'Action Name' field.
  39. Click [View Action Log].
  40. Verify the 'ProviderConnect Enterprise Action Log' Report is displayed.
  41. Validate the 'ProviderConnect Enterprise Action Log' Report contains a row for the 'PutProgramAdmission' action that was triggered from the 'Admission' form with a result of "Success".
  42. Close the report and the form.
ProviderConnect Enterprise - 'Client Demographic' data
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Update Client Data
  • CareFabric Monitor
  • Postman
Scenario 1: ProviderConnect Enterprise- Validate the 'PutClient' action
Specific Setup:
  • The 'Avatar CareFabric->ProviderConnect Enterprise->Contracting Providers->->->Enable External Connections' must be set to "Y".
  • The 'Managing Organization Definition' form must be defined for a valid managing organization.
  • A client must be enrolled in an existing episode and be mapped to the defined managing organization in the 'ProviderConnect Enterprise Identifiers' section of the 'Admission' form (Client A).
  • The 'Client Demographics - Additional Fields' registry setting must be set to include "Multi-Select Race".
Steps
  1. Select "Client A" and access the 'Update Client Data' form.
  2. Update any desired fields.
  3. Select the desired value in the 'Client Race' field.
  4. Select the desired value in the 'Occupation' field.
  5. Enter the desired name in the 'Preferred Name' field.
  6. Select the desired value in the 'Gender Identity' field.
  7. Select "Yes" in the 'Veteran' field.
  8. Select the desired value in the 'Sexual Orientation' field.
  9. Select the desired value in the 'Gender Identity' field.
  10. Select the desired value in the 'Other Race(s)'.
  11. Click [Submit].
  12. Access the 'ProviderConnect Enterprise Action Log'.
  13. Enter the desired dates in the 'From Date' and 'Through Date' fields.
  14. Enter the desired times in the 'From Time' and 'Through Time' fields.
  15. Select the desired organization in the 'Managing Organization' field.
  16. Select "PutClient" in the 'Action Name' field.
  17. Click [View Action Log].
  18. Validate the 'ProviderConnect Enterprise Action Log' Report is displayed.
  19. Validate the 'ProviderConnect Enterprise Action Log' Report contains the 'PutClient' action that was triggered from the 'Update Client Data' form with a "Success" result.
  20. Close the report and the form.
ProviderConnect Enterprise - 'Financial Eligibility' data
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Postman
  • Update Client Data
Scenario 1: ProviderConnect Enterprise - Validate sending Financial Eligibility data via the 'PutFhirInsurancePolicy' action
Specific Setup:
  • The 'Avatar CareFabric->ProviderConnect Enterprise->Contracting Providers->->->Enable External Connections' must be set to "Y".
  • The 'Managing Organization Definition' form must be defined for a valid managing organization. Guarantors/Payors must be selected in the 'Associated Guarantor/Payor' field, including a "Medi-Cal" guarantor (Guarantor A).
  • A client must be enrolled in an existing episode and be mapped to the defined managing organization in the 'ProviderConnect Enterprise Identifiers' section of the 'Admission' form (Client A).
Steps
  1. Select "Client A" and access the 'Financial Eligibility' form.
  2. Select the episode mapped to the managing organization in the Episode Pre-Display.
  3. Click [OK].
  4. Select the "Guarantor Selection" tab.
  5. Click [Add New Item].
  6. Select "Guarantor A" in the 'Guarantor #' field.
  7. Select "(Non-Contract) Medi-Cal" in the 'Guarantor Plan' field.
  8. Select the desired value in the 'Customize Guarantor Plan' field.
  9. Enter the desired date in the 'Effective Date Of Contract' field.
  10. Select "Self" in the 'Client's Relationship To Subscriber' field.
  11. Enter the desired value in the 'Subscriber's Address - Street Line 1' field.
  12. Enter the desired value in the 'Subscriber's Address - Zip' field.
  13. Enter the desired value in the 'Subscriber's Address - City' field.
  14. Enter the desired value in the 'Subscriber's Address - State' field.
  15. Enter the desired value in the 'Subscriber's Social Security #' field.
  16. Select the desired value in the 'Eligibility Verified' field.
  17. Enter the desired date in the 'Coverage Effective Date' field.
  18. Enter the desired date in the 'Coverage Expiration Date' field.
  19. Enter the desired value in the 'Subscriber's Birth Date' field.
  20. Enter the desired value in the 'Subscriber's Client Index Number' field.
  21. Select the desired value in the 'Subscriber's Assignment of Benefits' field.
  22. Select the desired value in the 'Subscriber's Release Of Info' field.
  23. Enter the desired date in the 'Effective Date Of Medi-Cal Eligibility' field.
  24. Select the desired value in the 'Eligibility Code' field.
  25. Select the desired value in the 'Aid Code' field.
  26. Select the "Financial Eligibility" tab.
  27. Select "Guarantor A" in the 'Guarantor #1' field.
  28. Click [Submit].
  29. Access the 'ProviderConnect Enterprise Action Log' form.
  30. Enter the desired date in the 'From Date' and 'Through Date' fields.
  31. Enter the desired time in the 'From Time' and 'Through Time' fields.
  32. Select the desired organization in the 'Managing Organization' field.
  33. Select "PutFhirInsurancePolicy" in the 'Action Name' field.
  34. Click [View Action Log].
  35. Validate the 'ProviderConnect Enterprise Action Log' Report is displayed.
  36. Validate the 'ProviderConnect Enterprise Action Log' Report contains the 'PutFhirInsurancePolicy' action that was triggered from the 'Financial Eligibility' form with a "Success" result.
  37. Close the report and the form.
Scenario 2: ProviderConnect Enterprise - Validate sending Financial Eligibility data via the 'PutFhirInsurancePolicy' action
Specific Setup:
  • The 'Avatar CareFabric->ProviderConnect Enterprise->Contracting Providers->->->Enable External Connections' must be set to "Y".
  • The 'Managing Organization Definition' form must be defined for a valid managing organization. Guarantors/Payors must be selected in the 'Associated Guarantor/Payor' field, including a "Medi-Cal" guarantor (Guarantor A).
  • A client must be enrolled in an existing episode and be mapped to the defined managing organization in the 'ProviderConnect Enterprise Identifiers' section of the 'Admission' form (Client A).
Steps
  1. Select "Client A" and access the 'Financial Eligibility' form.
  2. Select the episode mapped to the managing organization in the Episode Pre-Display.
  3. Click [OK].
  4. Select the "Guarantor Selection" tab.
  5. Click [Add New Item].
  6. Select "Guarantor A" in the 'Guarantor #' field.
  7. Select "(Non-Contract) Medi-Cal" in the 'Guarantor Plan' field.
  8. Select the desired value in the 'Customize Guarantor Plan' field.
  9. Enter the desired date in the 'Effective Date Of Contract' field.
  10. Select "Self" in the 'Client's Relationship To Subscriber' field.
  11. Enter the desired value in the 'Subscriber's Address - Street Line 1' field.
  12. Enter the desired value in the 'Subscriber's Address - Zip' field.
  13. Enter the desired value in the 'Subscriber's Address - City' field.
  14. Enter the desired value in the 'Subscriber's Address - State' field.
  15. Enter the desired value in the 'Subscriber's Social Security #' field.
  16. Select the desired value in the 'Eligibility Verified' field.
  17. Enter the desired date in the 'Coverage Effective Date' field.
  18. Enter the desired date in the 'Coverage Expiration Date' field.
  19. Enter the desired value in the 'Subscriber's Birth Date' field.
  20. Enter the desired value in the 'Subscriber's Client Index Number' field.
  21. Select the desired value in the 'Subscriber's Assignment of Benefits' field.
  22. Select the desired value in the 'Subscriber's Release Of Info' field.
  23. Enter the desired date in the 'Effective Date Of Medi-Cal Eligibility' field.
  24. Select the desired value in the 'Eligibility Code' field.
  25. Select the desired value in the 'Aid Code' field.
  26. Select the "Financial Eligibility" tab.
  27. Select "Guarantor A" in the 'Guarantor #1' field.
  28. Click [Submit].
  29. Access the 'ProviderConnect Enterprise Action Log' form.
  30. Enter the desired date in the 'From Date' and 'Through Date' fields.
  31. Enter the desired time in the 'From Time' and 'Through Time' fields.
  32. Select the desired organization in the 'Managing Organization' field.
  33. Select "PutFhirInsurancePolicy" in the 'Action Name' field.
  34. Click [View Action Log].
  35. Validate the 'ProviderConnect Enterprise Action Log' Report is displayed.
  36. Validate the 'ProviderConnect Enterprise Action Log' Report contains the 'PutFhirInsurancePolicy' action that was triggered from the 'Financial Eligibility' form with a "Success" result.
  37. Close the report and the form.
Topics
• Admission • ProviderConnect Enterprise • Update Client Data • Financial Eligibility
2023 Update 25 Summary | Details
Flowsheet - 'Complete Tasks' dialog
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Flowsheet
  • Complete Task
  • Task List
Scenario 1: Flowsheet: Flowsheet Charting - PRN Unscheduled Tasks
Specific Setup:
  • In order to utilize full functionality Avatar CareFabric 2023 Update 25 and Flowsheet 1.7.3 are required.
  • A pharmacy-type order code must exist. (Order Code A)
  • A task code must be set up through the 'Task Definition' form such that:
  • 'Task Action Type' = "Flowsheet". (Task Code A)
  • In the 'Task Association' form, "Task Code A" must be associated to "Order Code A", such that 'Order Event' = "Order Entry".
  • A collection must be set up in the flowsheet admin tool. (Collection A)
  • An assessment must be set up in the flowsheet admin tool.(Assessment A)
  • "Assessment A" must be added to "Collection A".
  • In the Flowsheet Admin tool "Task Code A" must be added as a 'Task Code' tag to "Assessment A".
  • A PRN frequency code must exist. (Frequency Code A)
  • A client must have an active episode. (Client A).
  • “Client A” must have a ‘Date of Birth’, ‘Sex’ and address on file in the ‘Update Client Data’ form, as well as information filed in the ‘Allergies and Hypersensitivities’ form, ‘Diagnosis’ form, and in the ‘Height’ and ‘Weight’ fields in the ‘Vitals Entry’ form.
Steps
  1. Select "Client A" and access the Order Entry Console.
  2. Search for and select "Order Code A" from the 'New Order' field.
  3. Select "Frequency Code A" from the 'Frequency' field.
  4. Set the 'Duration' field to "1" and click [Day].
  5. Fill in any remaining required fields, click [Add to Scratchpad], and [Sign].
  6. Access the 'Task List' widget.
  7. Search for and select "Client A" from the 'Search Patients' field.
  8. Hover over the 'PRN Tasks' link and validate a task for "Task Code A" is shown.
  9. Navigate to the Flowsheet Tab.
  10. Click on the tab for "Collection A".
  11. Navigate to "Assessment A"
  12. Populate any required fields in "Assessment A" and click [Sign].
  13. Validate the 'Complete Tasks' dialog appears with the unscheduled task and that it states "Due: Unscheduled".
  14. Check the checkbox for the unscheduled task and click [Complete].
  15. Access the 'Task List' widget.
  16. Search for and select "Client A" from the 'Search Patients' field.
  17. Hover over the 'PRN Tasks' link and validate a task for "Task Code A" is shown.
  18. Click the 'PRN Tasks' link.
  19. Hover over the task for "Task Code A" and validate it displays the date and time the flowsheet assessment was completed next to the 'Last Completed' label.
Scenario 2: Flowsheet: Flowsheet Charting - Scheduled Tasks
Specific Setup:
  • In order to utilize full functionality Avatar CareFabric 2023 Update 25 and Flowsheet 1.7.3 are required.
  • A pharmacy-type order code must exist. (Order Code A)
  • A task code must be set up through the 'Task Definition' form such that:
  • 'Task Action Type' = "Flowsheet". (Task Code A)
  • In the 'Task Association' form, "Task Code A" must be associated to "Order Code A", such that 'Order Event' = "Order Entry".
  • A collection must be set up in the flowsheet admin tool. (Collection A)
  • An assessment must be set up in the flowsheet admin tool.(Assessment A)
  • "Assessment A" must be added to "Collection A".
  • In the Flowsheet Admin tool "Task Code A" must be added as a 'Task Code' tag to "Assessment A".
  • A routine frequency, with scheduled hours of administration every hour, must exist. (Frequency Code A)
  • A client must have an active episode. (Client A).
  • “Client A” must have a ‘Date of Birth’, ‘Sex’ and address on file in the ‘Update Client Data’ form, as well as information filed in the ‘Allergies and Hypersensitivities’ form, ‘Diagnosis’ form, and in the ‘Height’ and ‘Weight’ fields in the ‘Vitals Entry’ form.
Steps
  1. Select "Client A" and access the Order Entry Console.
  2. Search for and select "Order Code A" from the 'New Order' field.
  3. Select "Frequency Code A" from the 'Frequency' field.
  4. Set the 'Duration' field to "1" and click [Hours].
  5. Fill in any remaining required fields, click [Add to Scratchpad], and [Sign].
  6. Access the 'Task List' widget.
  7. Search for and select "Client A" from the 'Search Patients' field.
  8. Validate a task for "Task Code A" is generated in the 'Next Hour' column.
  9. Navigate to the Flowsheet Tab.
  10. Click on the tab for "Collection A".
  11. Navigate to "Assessment A"
  12. Populate any required fields in "Assessment A" and click [Sign].
  13. Validate the 'Complete Tasks' dialog appears with the scheduled task and that it states "Due: Scheduled Date/Time".
  14. Check the checkbox for the scheduled task and click [Complete].
  15. Access the 'Task List' widget.
  16. Search for and select "Client A" from the 'Search Patients' field.
  17. Validate the task for "Task Code A" is no longer shown in the 'Next Hour' column.
Scenario 3: Flowsheet: Flowsheet Charting - Routine Unscheduled Tasks
Specific Setup:
  • In order to utilize full functionality Avatar CareFabric 2023 Update 25 and Flowsheet 1.7.3 are required.
  • A pharmacy-type order code must exist. (Order Code A)
  • A task code must be set up through the 'Task Definition' form such that:
  • 'Task Action Type' = "Flowsheet". (Task Code A)
  • In the 'Task Association' form, "Task Code A" must be associated to "Order Code A", such that 'Order Event' = "Order Entry".
  • A collection must be set up in the flowsheet admin tool. (Collection A)
  • An assessment must be set up in the flowsheet admin tool.(Assessment A)
  • "Assessment A" must be added to "Collection A".
  • In the Flowsheet Admin tool "Task Code A" must be added as a 'Task Code' tag to "Assessment A".
  • A Routine frequency code, with no scheduled hours of administration, must exist. (Frequency Code A)
  • A client must have an active episode. (Client A).
  • “Client A” must have a ‘Date of Birth’, ‘Sex’ and address on file in the ‘Update Client Data’ form, as well as information filed in the ‘Allergies and Hypersensitivities’ form, ‘Diagnosis’ form, and in the ‘Height’ and ‘Weight’ fields in the ‘Vitals Entry’ form.
Steps
  1. Select "Client A" and access the Order Entry Console.
  2. Search for and select "Order Code A" from the 'New Order' field.
  3. Select "Frequency Code A" from the 'Frequency' field.
  4. Fill in any remaining required fields, click [Add to Scratchpad], and [Sign].
  5. Access the 'Task List' widget.
  6. Search for and select "Client A" from the 'Search Patients' field.
  7. Validate a task for "Task Code A" is shown in the 'Unscheduled' column.
  8. Navigate to the Flowsheet Tab.
  9. Click on the tab for "Collection A".
  10. Navigate to "Assessment A"
  11. Populate any required fields in "Assessment A" and click [Sign].
  12. Validate the 'Complete Tasks' dialog appears with the unscheduled task and that it states "Due: Unscheduled".
  13. Check the checkbox for the unscheduled task and click [Complete].
  14. Access the 'Task List' widget.
  15. Search for and select "Client A" from the 'Search Patients' field.
  16. Validate a task for "Task Code A" is not shown in the 'Unscheduled' column.
Topics
• Assessments • Task List
Update 26 Summary | Details
Avatar CareFabric - Voided Progress Notes and Vital Signs
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Vitals Entry
  • CareFabric Monitor
  • Void Progress Notes
Scenario 1: 'Void Progress Notes' form - void a progress note and validate the 'ProgressNoteDeleted' payload
Specific Setup:
  • A client is enrolled in an existing episode and has a progress note on file (Client A).
Steps
  1. Access the 'Void Progress Notes' form.
  2. Select "Client A" in the 'Client ID' field.
  3. Select the desired episode in the 'Episode Number' field.
  4. Enter the desired dates in the 'Start Date' and 'End Date' fields.
  5. Click [Select Note To Void].
  6. Select the desired note in the 'Select Note To Void' field and click [OK].
  7. Select the desired value in the 'Reason For Voiding The Note' field.
  8. Enter the desired value in the 'Comments' field.
  9. Submit the form.
  10. Access the 'CareFabric Monitor' form.
  11. Enter the current date in the 'From Date' and 'Through Date' field.
  12. Select "Client A" in the 'Client ID' field.
  13. Click [View Activity Log].
  14. Validate the 'CareFabric Monitor' report is displayed with a "ProgressNoteDeleted" record.
  15. Click [Click To View Record].
  16. Validate the 'voidedByStaffMemberID' - 'humanReadableValue' field contains the user who voided the note.
  17. Validate the 'voidedByStaffMemberID' - 'id' field contains the user ID who voided the note.
  18. Validate the 'voidedDate' field contains the current date.
  19. Close the report and the form.
Scenario 2: Vitals Entry - Validate the ability to void Vital Signs
Specific Setup:
  • The 'Avatar CWS->CWS Utilities->Set System Defaults->Vitals Entry->->Vitals Entry Restrictions' registry setting must be set to "N".
  • At least one dictionary code must exist in the CWS '(14112) Void Reason' dictionary.
  • A client must have an active episode and no vitals on file (Client A).
Steps
  1. Select “Client A” and access the ‘Vitals Entry’ form.
  2. Select "Add" in the 'Update Vital Sign' field.
  3. Enter the desired date in the 'Date' field.
  4. Enter the desired time in the 'Time' field.
  5. Enter the desired value in the 'Height' field.
  6. Enter the desired value in the 'Weight' field.
  7. Validate the 'BMI' is populated based on the height/weight filed.
  8. Populate all desired fields.
  9. Click [Submit] and [No] to exit the form.
  10. Double click on "Client A" to access the Chart View.
  11. Validate the ‘Height, ‘Weight’, and ‘BMI’ fields in the Client Header display with the current data filed.
  12. Close the chart.
  13. Select “Client A” and access the ‘Vitals Entry’ form.
  14. Select "Void" in the 'Update Vital Sign' field.
  15. Click [Select Vital Sign].
  16. Select the previously filed vitals record and click [OK].
  17. Validate the previously filed data is displayed.
  18. Select the desired value in the ‘Void Reason’ field.
  19. Click [Submit] and [Yes] to return to form.
  20. Select "Edit" in the 'Update Vital Sign' field.
  21. Click [Select Vital Sign].
  22. Validate “*** VOIDED ***” displays in the Vitals Entry row and click [Cancel].
  23. Close the form.
  24. Double click on "Client A" to access the Chart View.
  25. Validate the ‘Height, ‘Weight’, and ‘BMI’ fields in the Client Header no longer display since the vitals have been voided.
  26. Close the chart.
  27. Access the 'CareFabric Monitor' form.
  28. Enter the current date in the 'From Date' and 'Through Date' field.
  29. Select "Client A" in the 'Client ID' field.
  30. Click [View Activity Log].
  31. Validate the 'CareFabric Monitor' report is displayed with a "VitalSignSetUpdated" record.
  32. Click [Click To View Record].
  33. Validate the 'voidedByStaffMemberID' - 'humanReadableValue' fields contains the user who voided the vitals.
  34. Validate the 'voidedByStaffMemberID' - 'id' fields contains the user ID who voided the vitals.
  35. Validate the 'voidedDate' fields contains the current date.
  36. Close the report and the form.
Topics
• Vitals • Progress Notes • CareFabric Monitor • Vitals Entry
Update 27 Summary | Details
Avatar CareFabric - 'SearchClientAuthorization' SDK action
Scenario 1: Validate the 'SearchClientAuthorization' SDK action
Steps
  • Internal testing only.
Topics
• CareFabric
Update 28 Summary | Details
ProviderConnect Enterprise - 'Women's Health History' data
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Postman
  • Women's Health History
  • Dynamic Form - Pre-Display Confirmation
Scenario 1: ProviderConnect Enterprise- Validate the 'PutProgramAdmission' action
Specific Setup:
  • The 'Avatar CareFabric->ProviderConnect Enterprise->Contracting Providers->->->Enable External Connections' must be set to "Y".
  • The 'Managing Organization Definition' form must be configured for a valid managing organization.
  • A client must exist in the configured managing organization's system with the following on file: 'Date of Birth' and 'Social Security Number' (Client A).
  • A practitioner must have a NPI that is mapped to a matching practitioner in the managing organization's system (Practitioner A).
Steps
  1. Access the 'Admission' form.
  2. Verify the 'Select Client' dialog is displayed.
  3. Enter the last name of the client that exists in the managing organization's system in the 'Last Name' field.
  4. Enter the first name of the client that exists in the managing organization's system in the 'First Name' field.
  5. Enter the sex of the client that exists in the managing organization's system in the 'Sex' field.
  6. Click [Search].
  7. Validate a "Search Results" message is displayed stating: No matches found.
  8. Click [OK] and [New Client].
  9. Validate a "Client" message is displayed stating: Auto Assign Next ID Number?
  10. Click [Yes].
  11. Enter the desired date in the 'Preadmit/Admission Date' field.
  12. Enter the desired time in the 'Preadmit/Admission Time' field.
  13. Select any program that is selected in the 'Associated Admission Programs' field in the 'Managing Organization Definition' form in the 'Program' field.
  14. Select the desired value in the 'Type Of Admission' field.
  15. Select desired value in the 'Source Of Admission' field.
  16. Enter "Practitioner A" in the 'Admitting Practitioner' field.
  17. Enter "Practitioner A" in the 'Attending Practitioner' field.
  18. Select the "Other Client Data" section.
  19. Select "Yes" in the 'Informed of Smoking Policy' field.
  20. Select the "ProviderConnect Enterprise Identifiers" section.
  21. Click [Add New Item].
  22. Select the defined managing organization in the 'External Organization' field.
  23. Click [Search].
  24. Select the matching client record in the 'Select Matching Client Record' dialog.
  25. Click [OK].
  26. Validate the 'External ID' field contains the client ID for the client in the managing organization's system.
  27. Click [Update Demographics].
  28. Validate an "Information" message is displayed stating: Client Demographics Information Updated.
  29. Click [OK].
  30. Select the "Admission" section.
  31. Validate the 'Date of Birth' field contains the value on file in the managing organization's system.
  32. Validate the 'Social Security Number' field contains the value on file in the managing organization's system.
  33. Click [Submit].
  34. Access the 'ProviderConnect Enterprise Action Log'.
  35. Enter the desired date in the 'From Date' and 'Through Date' fields.
  36. Enter the desired time in the 'From Time' and 'Through Time' fields.
  37. Select the desired organization in the 'Managing Organization' field.
  38. Select "PutProgramAdmission" in the 'Action Name' field.
  39. Click [View Action Log].
  40. Verify the 'ProviderConnect Enterprise Action Log' Report is displayed.
  41. Validate the 'ProviderConnect Enterprise Action Log' Report contains a row for the 'PutProgramAdmission' action that was triggered from the 'Admission' form with a result of "Success".
  42. Close the report and the form.
Scenario 2: ProviderConnect Enterprise - Women's Health History - Validate the 'PutPregnancy' action
Specific Setup:
  • The 'Avatar CareFabric->ProviderConnect Enterprise->Contracting Providers->->->Enable External Connections' must be set to "Y".
  • The 'Managing Organization Definition' form must be defined for a valid managing organization.
  • A female client must be enrolled in an existing episode that is mapped to the defined managing organization in the 'ProviderConnect Enterprise Identifiers' section of the 'Admission' form (Client A).
Steps
  1. Access the 'Women's Health History' form.
  2. Select "Add" in the 'Add, Edit, or Delete a Record' field.
  3. Enter "Client A" in the 'Client ID' field.
  4. Select the episode mapped to the managing organization in the 'Episode Number' field.
  5. Enter the desired date in the 'Assessment Date' field.
  6. Enter the desired value in the 'LMP' field.
  7. Enter the desired option in the field 'LMP Frequency'.
  8. Enter the desired date in the 'Pregnancy Start Date' field.
  9. Enter the desired date in the 'Pregnancy End Date' field.
  10. Select "Yes" in the 'Have you ever been pregnant?' field.
  11. Select the desired value in the 'Pregnancy Status' field.
  12. Enter the desired date in the 'Expected Due Date' field.
  13. Select the desired value in the 'Abortion(s)' field.
  14. Select the desired value in the 'Have you ever had a miscarriage?' field.
  15. Select the desired value in the 'Contraception' field.
  16. Select the desired value in the 'Sexually Active' field.
  17. Click [Submit].
  18. Validate a "Form Return" message is displayed stating: Submitting has completed. Do you wish to return to form?
  19. Click [No].
  20. Access the 'ProviderConnect Enterprise Action Log' form.
  21. Enter the desired dates in the 'From Date' and 'Through Date' fields.
  22. Enter the desired times in the 'From Time' and 'Through Time' fields.
  23. Select the desired organization in the 'Managing Organization' field.
  24. Select "PutPregnancy" in the 'Action Name' field.
  25. Click [View Action Log].
  26. Validate the 'ProviderConnect Enterprise Action Log' Report is displayed.
  27. Validate the 'ProviderConnect Enterprise Action Log' Report contains the 'PutPregnancy' action that was triggered from the 'Women's Health History' form with a "Success" result.
  28. Close the report and the form.
Scenario 3: ProviderConnect Enterprise - Women's Health History - Validate the 'PutPregnancy' action
Specific Setup:
  • The 'Avatar CareFabric->ProviderConnect Enterprise->Contracting Providers->->->Enable External Connections' must be set to "Y".
  • The 'Managing Organization Definition' form must be defined for a valid managing organization.
  • A female client must be enrolled in an existing episode that is mapped to the defined managing organization in the 'ProviderConnect Enterprise Identifiers' section of the 'Admission' form (Client A).
Steps
  1. Access the 'Women's Health History' form.
  2. Select "Add" in the 'Add, Edit, or Delete a Record' field.
  3. Enter "Client A" in the 'Client ID' field.
  4. Select the episode mapped to the managing organization in the 'Episode Number' field.
  5. Enter the desired date in the 'Assessment Date' field.
  6. Enter the desired value in the 'LMP' field.
  7. Enter the desired option in the field 'LMP Frequency'.
  8. Enter the desired date in the 'Pregnancy Start Date' field.
  9. Enter the desired date in the 'Pregnancy End Date' field.
  10. Select "Yes" in the 'Have you ever been pregnant?' field.
  11. Select the desired value in the 'Pregnancy Status' field.
  12. Enter the desired date in the 'Expected Due Date' field.
  13. Select the desired value in the 'Abortion(s)' field.
  14. Select the desired value in the 'Have you ever had a miscarriage?' field.
  15. Select the desired value in the 'Contraception' field.
  16. Select the desired value in the 'Sexually Active' field.
  17. Click [Submit].
  18. Validate a "Form Return" message is displayed stating: Submitting has completed. Do you wish to return to form?
  19. Click [No].
  20. Access the 'ProviderConnect Enterprise Action Log' form.
  21. Enter the desired dates in the 'From Date' and 'Through Date' fields.
  22. Enter the desired times in the 'From Time' and 'Through Time' fields.
  23. Select the desired organization in the 'Managing Organization' field.
  24. Select "PutPregnancy" in the 'Action Name' field.
  25. Click [View Action Log].
  26. Validate the 'ProviderConnect Enterprise Action Log' Report is displayed.
  27. Validate the 'ProviderConnect Enterprise Action Log' Report contains the 'PutPregnancy' action that was triggered from the 'Women's Health History' form with a "Success" result.
  28. Close the report and the form.
Topics
• Admission • ProviderConnect Enterprise • Women's Health History
Update 29 Summary | Details
Medical Note - 'Women's Health History'
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Women's Health History
  • CareFabric Monitor
  • Facesheet.Women's Health History
  • Update Client Data
Scenario 1: Medical Note - Validate the 'Women's Health History' section
Specific Setup:
  • A user must be defined as a "Provider" and have the following:
  • Female client enrolled in an existing episode (Client A)
  • The 'Medical Note' widget accessible on the HomeView
Steps
  1. Select "Client A" and access the 'Women's Health History' form.
  2. Click [Add].
  3. Enter the desired value in the 'Assessment Date' field.
  4. Select the desired value in the 'Pregnant Status' field.
  5. Populate any other desired fields.
  6. Submit the form.
  7. Select "Client A" and access the 'Medical Note' widget.
  8. Validate the Facesheet is displayed for "Client A".
  9. Select the "Women's Health History" section.
  10. Validate the 'Pregnancy Status' field contains the value filed via 'Women's Health History'.
  11. Select "Client A" and access the 'Update Client Data' form.
  12. Select any new value in the 'Pregnant Status' field.
  13. Submit the form.
  14. Select "Client A" and access the 'Medical Note' widget.
  15. Refresh the widget.
  16. Validate the Facesheet is displayed for "Client A".
  17. Validate the 'Pregnancy Status' field contains the updated value filed via 'Update Client Data'.
Dictionary Update - 'Claim Adjustment Reason Code' dictionary
Scenario 1: Dictionary Update - Validate the 'Claim Adjustment Reason Code' dictionary
Steps
  1. Access the 'Dictionary Update' form.
  2. Select "Other Tabled Files" in the 'File' field.
  3. Select "Data Element Number" in the 'Data Element' field.
  4. Select "1214" in the 'Data Element' field.
  5. Enter "D1" in the 'Dictionary Code' field.
  6. Press the tab key.
  7. Validate the 'Dictionary Value' field populates accordingly.
  8. Update any desired values.
  9. Click [Apply Changes].
  10. Validate a message is displayed stating: Filed!
  11. Click [OK] and close the form.
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:
  • Women's Health History
  • Treatment Plan
  • CareFabric Monitor
  • Patient Health Questionnaire-9
  • CSI Assessment
  • Financial Investigation
  • Vitals Entry
  • Facesheet.Women's Health History
  • Update Client Data
  • Dynamic Form - Pre-Display Confirmation
Scenario 1: Treatment Plan - Validate the 'CarePlanCreated', 'CarePlanGoalCreated', 'CarePlanInterventionCreated', and 'CarePlanProblemCreated' SDK events
Specific Setup:
  • A client is enrolled in an existing episode (Client A).
  • The extended dictionary "(60150) FHIR Care Plan Category" must be defined for the dictionary values defined for "(52003) Plan Type".
  • The following extended dictionaries must be defined for the "(16214) Status" CWS dictionary values for 'Problem Status':
  • (16254) ONC Clinical Status
  • (16255) ONC Verified Status
Steps
  1. Select "Client A" and access the 'Treatment Plan' form.
  2. Enter the desired date in the 'Plan Date' field.
  3. Select the desired value in the 'Plan Type' field.
  4. Select "Draft" in the 'Treatment Plan Status' field.
  5. Validate "Draft" is selected in the 'Current Status' field.
  6. Enter the desired value in the 'Strengths' field.
  7. Enter the desired value in the 'Weaknesses' field.
  8. Enter the desired value in the 'Discharge Planning' field.
  9. Click [Launch Plan].
  10. Add a problem, goal, objective, and intervention.
  11. Populate all required and desired fields.
  12. Click [Back To Plan Page].
  13. Select "Final" in the 'Treatment Plan Status' field.
  14. Select "Active" in the 'Current Status' field.
  15. Click [Submit].
  16. Access the 'CareFabric Monitor' form.
  17. Enter the current date in the 'From Date' and 'Through Date' fields.
  18. Click [View Activity Log].
  19. Validate the 'CareFabric Monitor Report' contains a "CarePlanCreated", "CarePlanGoalCreated", "CarePlanInterventionCreated", and "CarePlanProblemCreated" record.
  20. Click [Click To View Record] for the "CarePlanCreated" record.
  21. Validate the 'auditInformation' - 'lastUpdatedByStaffMemberID' - 'id' field contains the logged in staff member.
  22. Validate the 'auditInformation' - 'lastUpdatedDate' field contains the current date/time.
  23. Validate the 'carePlanDetails' - 'statusCode' - 'code' field contains "active".
  24. Validate the 'carePlanDetails' - 'statusCode' - 'displayName' field contains "Active".
  25. Validate the 'planTypeCode' - 'code' field contains the "FHIR Care Plan Category" extended dictionary code for the plan type selected.
  26. Validate the 'planTypeCode' - 'codeSystem' field contains "2.16.840.1.113883.6.96".
  27. Validate the 'planTypeCode' - 'displayNAme' field contains the "FHIR Care Plan Category" extended dictionary value for the plan type selected.
  28. Validate the 'summaryText' - 'xhtmlContent' field contains the values entered in the 'Strengths', 'Weaknesses', and 'Discharge Planning' fields.
  29. Validate all other information displays.
  30. Navigate back to the 'CareFabric Monitor Report'.
  31. Click [Click To View Record] for the "CarePlanGoalCreated" record.
  32. Validate the 'auditInformation' - 'lastUpdatedByStaffMemberID' - 'id' field contains the logged in staff member.
  33. Validate the 'auditInformation' - 'lastUpdatedDate' field contains the current date/time.
  34. Validate the 'goalCode' - 'codeSystem' field contains "2.16.840.1.113883.4.642.3.271".
  35. Validate all other information displays.
  36. Navigate back to the 'CareFabric Monitor Report'.
  37. Click [Click To View Record] for the "CarePlanInterventionCreated" record.
  38. Validate the 'auditInformation' - 'lastUpdatedByStaffMemberID' - 'id' field contains the logged in staff member.
  39. Validate the 'auditInformation' - 'lastUpdatedDate' field contains the current date/time.
  40. Validate the 'programAdmissionID' - 'id' field contains an ID in the format of PATID||Episode.
  41. Validate all other information displays.
  42. Navigate back to the 'CareFabric Monitor Report'.
  43. Click [Click To View Record] for the "CarePlanProblemCreated" record.
  44. Validate the 'auditInformation' - 'lastUpdatedByStaffMemberID' - 'id' field contains the logged in staff member.
  45. Validate the 'auditInformation' - 'lastUpdatedDate' field contains the current date/time.
  46. Validate the 'clinicalStatusCode' - 'code' field contains the "ONC Clinical Status" extended dictionary code defined for the status selected.
  47. Validate the 'clinicalStatusCode' - 'codeSystem' field contains "2.16.840.1.113883.4.642.3.164".
  48. Validate the 'clinicalStatusCode' - 'codeSystemName' field contains "Condition-Clinical".
  49. Validate the 'clinicalStatusCode' - 'displayName' field contains the "ONC Clinical Status" extended dictionary value defined for the status selected.
  50. Validate the 'verificationStatusCode' - 'code' field contains the "ONC Verified Status" extended dictionary code defined for the status selected.
  51. Validate the 'verificationStatusCode' - 'codeSystem' field contains "2.16.840.1.113883.4.642.3.166".
  52. Validate the 'verificationStatusCode' - 'codeSystemName' field contains "Condition-Ver-Status".
  53. Validate the 'verificationStatusCode' - 'displayName' field contains the "ONC Verified Status" extended dictionary value defined for the status selected.
  54. Validate the 'programAdmissionID' - 'id' field contains an ID in the format of PATID||Episode.
  55. Validate all other information displays.
  56. Close the reports and the form.
Scenario 2: Patient Health Questionnaire-9 - Validate the 'EhrAssessmentResultCreated' SDK event
Specific Setup:
  • A client is enrolled in an existing episode (Client A).
Steps
  1. Select "Client A" and access the 'Patient Health Questionnaire-9' form.
  2. Populate all required fields.
  3. Select "Final" in the 'Assessment Status' field.
  4. Click [OK] and [Submit].
  5. Access the 'CareFabric Monitor' form.
  6. Enter the current date in the 'From Date' and 'Through Date' fields.
  7. Click [View Activity Log].
  8. Validate the 'CareFabric Monitor Report' contains a "EhrAssessmentResultCreated" record.
  9. Click [Click To View Record].
  10. Validate the 'auditInformation' - 'lastUpdatedByStaffMemberID' - 'id' field contains the logged in staff member.
  11. Validate the 'auditInformation' - 'lastUpdatedDate' field contains the current date/time.
  12. Validate the assessment data is displayed.
  13. Validate the 'programAdmissionID' - 'id' field contains an ID in the format of PATID||Episode.
  14. Close the report and the form.
Scenario 3: Women's Health History - Validate the 'PregnancyCreated' and 'PregnancyUpdated' SDK events
Specific Setup:
  • The following extended dictionaries must be defined for the "(357) Pregnancy Status" PM dictionary values:
  • (70492) Clinical Status - Pregnancy (FHIR)
  • (70493) Verification Status (FHIR)
  • A client is enrolled in an existing episode (Client A).
Steps
  1. Select "Client A" and access the 'Women's Health History' form.
  2. Enter the desired date in the 'Assessment Date' field.
  3. Enter the desired date in the 'Pregnancy Start Date' field.
  4. Select the desired value in the 'Pregnant Status' field.
  5. Click [Submit].
  6. Access the 'CareFabric Monitor' form.
  7. Enter the current date in the 'From Date' and 'Through Date' fields.
  8. Select "Client A" in the 'Client ID' field.
  9. Select "PregnancyCreated" in the 'Event/Action Search' field.
  10. Click [View Activity Log].
  11. Validate the 'clinicalStatusCode' - code' field contains the "Clinical Status - Pregnancy (FHIR)" extended dictionary code defined for the status selected.
  12. Validate the 'clinicalStatusCode' - 'codeSystem' field contains "2.16.840.1.113883.4.642.3.164".
  13. Validate the 'clinicalStatusCode' - 'codeSystemName' field contains "Condition-Clinical".
  14. Validate the 'clinicalStatusCode' - 'displayName' field contains the "Clinical Status - Pregnancy (FHIR)" extended dictionary value defined for the status selected.
  15. Validate the 'verificationStatusCode' - code' field contains the "Verification Status (FHIR)" extended dictionary code defined for the status selected.
  16. Validate the 'verificationStatusCode' - 'codeSystem' field contains "2.16.840.1.113883.4.642.3.166".
  17. Validate the 'verificationStatusCode' - 'codeSystemName' field contains "Condition-Ver-Status".
  18. Validate the 'verificationStatusCode' - 'displayName' field contains the "Verification Status (FHIR)" extended dictionary value defined for the status selected.
  19. Validate the 'programAdmissionID' - 'id' field contains an ID in the format of PATID||Episode.
  20. Close the report and the form.
  21. Select "Client A" and access the 'Women's Health History' form.
  22. Select the record filed in the previous steps and click [Edit].
  23. Enter the desired value in the 'Pregnancy End Date' field.
  24. Select any new value in the 'Pregnant Status' field.
  25. Click [Submit].
  26. Access the 'CareFabric Monitor' form.
  27. Enter the current date in the 'From Date' and 'Through Date' fields.
  28. Select "Client A" in the 'Client ID' field.
  29. Select "PregnancyUpdated" in the 'Event/Action Search' field.
  30. Click [View Activity Log].
  31. Validate the 'clinicalStatusCode' - code' field contains the "Clinical Status - Pregnancy (FHIR)" extended dictionary code defined for the status selected.
  32. Validate the 'clinicalStatusCode' - 'codeSystem' field contains "2.16.840.1.113883.4.642.3.164".
  33. Validate the 'clinicalStatusCode' - 'codeSystemName' field contains "Condition-Clinical".
  34. Validate the 'clinicalStatusCode' - 'displayName' field contains the "Clinical Status - Pregnancy (FHIR)" extended dictionary value defined for the status selected.
  35. Validate the 'endDate' field contains the 'Pregnancy End Date'.
  36. Validate the 'startDate' field contains the 'Pregnancy Start Date'.
  37. Validate the 'verificationStatusCode' - code' field contains the "Verification Status (FHIR)" extended dictionary code defined for the status selected.
  38. Validate the 'verificationStatusCode' - 'codeSystem' field contains "2.16.840.1.113883.4.642.3.166".
  39. Validate the 'verificationStatusCode' - 'codeSystemName' field contains "Condition-Ver-Status".
  40. Validate the 'verificationStatusCode' - 'displayName' field contains the "Verification Status (FHIR)" extended dictionary value defined for the status selected.
  41. Close the report and the form.
Scenario 4: Admission - Validate the 'BehavioralHealthEpisodeCreated' and 'BehavioralHealthEpisodeUpdated' SDK events
Specific Setup:
  • A client is enrolled in an existing episode (Client A).
Steps
  1. Select "Client A" and access the 'Admission' form.
  2. Select the existing episode and click [Edit].
  3. Navigate to the "Other Client Data" section.
  4. Enter the desired value in the 'Number Living In Household' field.
  5. Submit the form.
  6. Access the 'CareFabric Monitor' form.
  7. Enter the current date in the 'From Date' and 'Through Date' fields.
  8. Select "Client A" in the 'Client ID' field.
  9. Click [View Activity Log].
  10. Validate the 'CareFabric Monitor Report' is displayed and contains a "BehavioralHealthEpisodeUpdated" record.
  11. Click [Click To View Record].
  12. Validate the 'numberOfPeopleLivingInHousehold' field contains the value entered in the previous steps.
  13. Validate the 'programAdmissionID' - 'id' field contains an ID in the format of PATID||Episode.
  14. Close the report and the form.
Scenario 5: Vitals Entry - Validate the 'ObservationResourceCreated', 'ObservationResourceUpdated', and 'ObservationResourceDeleted' SDK events
Specific Setup:
  • A client is enrolled in an existing episode (Client A).
Steps
  1. Select "Client A" and access the 'Vitals Entry' form.
  2. Select "Add" in the 'Update Vital Sign' field.
  3. Enter the current date in the 'Date' field.
  4. Enter the current time in the 'Time' field.
  5. Enter the desired value in the 'Blood Pressure - Systolic' and 'Blood Pressure - Diastolic' fields.
  6. Select the desired value in the 'Position' field.
  7. Click [Submit] and close the form.
  8. Access the 'CareFabric Monitor' form.
  9. Enter the current date in the 'From Date' and 'Through Date' fields.
  10. Select "Client A" in the 'Client ID' field.
  11. Click [View Activity Log].
  12. Validate an "ObservationResourceCreated" record is displayed for "Client A". Note: this record will be triggered for each individual vital sign that is created.
  13. Click [Click To View Record].
  14. Validate the 'categoryCode' - 'code' field contains "vital_signs".
  15. Validate the 'clientID' - 'id' field contains the ID for "Client A".
  16. Validate the 'Diastolic Blood Pressure' and 'Systolic Blood Pressure' values are displayed as expected.
  17. Validate the 'effectiveDateRange' - 'fromDate' field contains the date/time entered in 'Vitals Entry'.
  18. Validate the 'issuedDate' field contains the date/time entered in 'Vitals Entry'.
  19. Validate the 'observationResourceID' - 'id' field contains a unique identifier such as "vital-signs||18||20231205131800166813,65956.521||BloodPressure1".
  20. Validate the 'statusCode' - 'code' field contains "final".
  21. Validate the 'subject' field contains the ID for "Client A".
  22. Validate the 'programAdmissionID' - 'id' field contains an ID in the format of PATID||Episode.
  23. Close the report and the form.
  24. Select "Client A" and access the 'Vitals Entry' form.
  25. Select "Edit" in the 'Update Vital Sign' field.
  26. Click [Select Vital Sign].
  27. Select the vitals filed in the previous steps and click [OK].
  28. Enter any new value in the 'Blood Pressure - Systolic' and 'Blood Pressure - Diastolic' fields.
  29. Click [Submit] and close the form.
  30. Access the 'CareFabric Monitor' form.
  31. Enter the current date in the 'From Date' and 'Through Date' fields.
  32. Select "Client A" in the 'Client ID' field.
  33. Click [View Activity Log].
  34. Validate an "ObservationResourceUpdated" record is displayed for "Client A". Note: this record will be triggered for each individual vital sign that is updated.
  35. Validate the updated 'Diastolic Blood Pressure' and 'Systolic Blood Pressure' values are displayed as expected.
  36. Close the report and the form.
  37. Select "Client A" and access the 'Vitals Entry' form.
  38. Select "Delete" in the 'Update Vital Sign' field.
  39. Click [Select Vital Sign].
  40. Select the vitals filed in the previous steps and click [OK].
  41. Validate the previously filed vitals are displayed and fields are disabled.
  42. Click [Submit].
  43. Validate a message is displayed stating: Are you sure you wish to delete this row?
  44. Click [Yes].
  45. Validate a message is displayed stating: Deleted.
  46. Click [OK] and close the form.
  47. Access the 'CareFabric Monitor' form.
  48. Enter the current date in the 'From Date' and 'Through Date' fields.
  49. Select "Client A" in the 'Client ID' field.
  50. Click [View Activity Log].
  51. Validate an "ObservationResourceDeleted" record is displayed for "Client A". Note: this record will be triggered for each individual vital sign that is deleted.
  52. Validate the 'statusCode' - 'code' field contains "cancelled".
  53. Close the report and the form.
  54. Repeat as needed for additional types of vital signs.
Scenario 6: 'Admission' form - Validate the 'ProgramAdmissionCreated' payload
Steps
  1. Access the 'Admission' form.
  2. Verify the 'Select Client' dialog is displayed.
  3. Enter any new value in the 'Last Name' and 'First Name' fields.
  4. Select any value in the 'Sex' field.
  5. Click [Search].
  6. Validate a "Search Results" message is displayed stating: No matches found.
  7. Click [New Client].
  8. Validate a "Client" message displays indicating "Auto Assign Next ID Number?"
  9. Click [Yes].
  10. Enter a date prior to daylight savings time in the 'Preadmit/Admission Date' field (Ex. 03/10/2023).
  11. Enter "10:00 AM" in the 'Preadmit/Admission Time' field.
  12. Select the desired program in the 'Program' field.
  13. Enter any value in the 'Type Of Admission' field.
  14. Enter the desired practitioner in the 'Admitting Practitioner' field.
  15. Click [Submit].
  16. Access the 'CareFabric Monitor' form.
  17. Enter the current date in the 'From Date' field.
  18. Enter the current date in the 'Through Date' field.
  19. Enter the client admitted in the previous steps in the 'Client ID' field.
  20. Click [View Activity Log].
  21. Validate the 'CareFabric Monitor Report' is displayed.
  22. Select the 'ProgramAdmissionCreated' activity type.
  23. Click [Click to View Record].
  24. Validate all filed information is populated.
  25. Validate the 'admissionDate' field contains the 'Preadmit/Admission Date' and 'Preadmit/Admission Time' populated in the previous steps with the correct time zone offset prior to daylight savings time (Ex: 2023-03-01T10:00:00.000-05:00).
  26. Validate the 'programAdmissionID' - 'id' field contains an ID in the format of PATID||Episode.
  27. Close the report and the form.
  28. Access the 'Admission' form.
  29. Verify the 'Select Client' dialog is displayed.
  30. Enter any new value in the 'Last Name' and 'First Name' fields.
  31. Select any value in the 'Sex' field.
  32. Click [Search].
  33. Validate a "Search Results" message is displayed stating: No matches found.
  34. Click [New Client].
  35. Validate a "Client" message displays indicating "Auto Assign Next ID Number?"
  36. Click [Yes].
  37. Enter a date during daylight savings time in the 'Preadmit/Admission Date' field (Ex. 05/01/2023).
  38. Enter "10:00 AM" in the 'Preadmit/Admission Time' field.
  39. Select the desired program in the 'Program' field.
  40. Enter any value in the 'Type Of Admission' field.
  41. Enter the desired practitioner in the 'Admitting Practitioner' field.
  42. Click [Submit].
  43. Access the 'CareFabric Monitor' form.
  44. Enter the current date in the 'From Date' field.
  45. Enter the current date in the 'Through Date' field.
  46. Enter the second client admitted in the previous steps in the 'Client ID' field.
  47. Click [View Activity Log].
  48. Validate the 'CareFabric Monitor Report' is displayed.
  49. Select the 'ProgramAdmissionCreated' activity type.
  50. Click [Click to View Record].
  51. Validate all filed information is populated.
  52. Validate the 'admissionDate' field contains the 'Preadmit/Admission Date' and 'Preadmit/Admission Time' populated in the previous steps with the correct time zone offset during daylight savings time (Ex: 2023-05-01T10:00:00.000-04:00).
  53. Validate the 'programAdmissionID' - 'id' field contains an ID in the format of PATID||Episode.
  54. Close the report and the form.
Scenario 7: 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
  1. Select "Client A" and access the 'Diagnosis' form.
  2. Select the desired value in the 'Type Of Diagnosis' field.
  3. Enter the desired date in the 'Date Of Diagnosis' field.
  4. Enter the desired time the 'Time Of Diagnosis' field.
  5. Click [New Row].
  6. Select the desired value in the 'Diagnosis Search' field.
  7. Select "Active" in the 'Status' field.
  8. Select the desired practitioner in the 'Diagnosing Practitioner' field.
  9. Click [Submit].
  10. Access the 'CareFabric Monitor' form.
  11. Enter the current date in the 'From Date' and 'Through Date' fields.
  12. Select "Client A" in the 'Client ID' field.
  13. Select "DiagnosisCreated" in the 'Event/Action Search' field.
  14. Click [View Activity Log].
  15. Validate the 'CareFabric Monitor Report' displays a 'DiagnosisCreated' record.
  16. Click [Click To View Record].
  17. Validate the 'startDate' field contains the 'Date Of Diagnosis' and 'Time Of Diagnosis' populated in the previous steps.
  18. Validate the 'statusCode' - 'code' field contains "1".
  19. Validate the 'statusCode' - 'displayName' field contains "Active".
  20. Validate the 'voidedByStaffMemberID' field contains "null".
  21. Validate the 'voidedDate' field contains "null".
  22. Validate all other previously filed data displays as expected.
  23. Validate the 'programAdmissionID' - 'id' field contains an ID in the format of PATID||Episode.
  24. Close the report and the form.
  25. Select "Client A" and access the 'Diagnosis' form.
  26. Select the diagnosis created in the previous steps and click [Edit].
  27. Select the row filed in the previous steps from the 'Diagnoses' grid.
  28. Select "Void" in the 'Status' field.
  29. Click [Submit].
  30. Access the 'CareFabric Monitor' form.
  31. Enter the current date in the 'From Date' and 'Through Date' fields.
  32. Select "Client A" in the 'Client ID' field.
  33. Select "DiagnosisUpdated" in the 'Event/Action Search' field.
  34. Click [View Activity Log].
  35. Validate the 'CareFabric Monitor Report' displays a 'DiagnosisUpdated' record.
  36. Click [Click To View Record].
  37. Validate the 'statusCode' - 'code' field contains "5".
  38. Validate the 'statusCode' - 'displayName' field contains "Void".
  39. Validate the 'voidedByStaffMemberID' - 'id' field contains the logged in staff member.
  40. Validate the 'voidedDate' field contains the current date.
  41. Validate the 'programAdmissionID' - 'id' field contains an ID in the format of PATID||Episode.
  42. Close the report and the form.
Avatar CareFabric - 'ListProgramAdmission' SDK action
Scenario 1: Validate the 'ListProgramAdmission' SDK action
Steps
  • Internal testing only.
Avatar CareFabric - 'BehavioralHealthEpisode' SDK events
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • CareFabric Monitor
Scenario 1: Admission - Validate the 'BehavioralHealthEpisodeCreated' and 'BehavioralHealthEpisodeUpdated' SDK events
Specific Setup:
  • A client is enrolled in an existing episode (Client A).
Steps
  1. Select "Client A" and access the 'Admission' form.
  2. Select the existing episode and click [Edit].
  3. Navigate to the "Other Client Data" section.
  4. Enter the desired value in the 'Number Living In Household' field.
  5. Submit the form.
  6. Access the 'CareFabric Monitor' form.
  7. Enter the current date in the 'From Date' and 'Through Date' fields.
  8. Select "Client A" in the 'Client ID' field.
  9. Click [View Activity Log].
  10. Validate the 'CareFabric Monitor Report' is displayed and contains a "BehavioralHealthEpisodeUpdated" record.
  11. Click [Click To View Record].
  12. Validate the 'numberOfPeopleLivingInHousehold' field contains the value entered in the previous steps.
  13. Validate the 'programAdmissionID' - 'id' field contains an ID in the format of PATID||Episode.
  14. Close the report and the form.
Avatar CareFabric - HL7 integrations
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • System Task Scheduler
  • CareFabric Monitor
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
  1. Access the 'System Task Scheduler' form.
  2. Select "Avatar CareFabric - Send Facility Bed Information (HL-7) Recurrence Pattern : Hourly -Inactive" in the 'Schedule(s)' field.
  3. Validate "Hourly" is selected in the 'Recurrence Pattern' field.
  4. Validate the 'Start Time' field contains "12:00 AM".
  5. Validate the 'End Time' field contains "11:59 PM".
  6. Validate "Yes" is selected in the 'Inactive Task' field.
  7. Enter the current date in the 'Start By' field.
  8. Select "No" in the 'Inactive Task' field.
  9. Click [Schedule Task] and close the form.
  10. Wait for the task to run.
  11. Access the 'CareFabric Monitor' form.
  12. Enter the current date in the 'From Date' and 'Through Date' fields.
  13. Select "ClientUpdated" in the 'Event/Action Search' field.
  14. Click [View Activity Log].
  15. Validate the 'CareFabric Monitor Report' is displayed with a "ClientUpdated" record for each unit configured in the pre-conditions.
  16. Click [Click To View Record] for the first record.
  17. Validate the 'assignedFacilityInformation' - 'facilityMneumonic' field contains the value defined in the "(22055) Facility Abbreviation" extended dictionary element for the unit.
  18. 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.
  19. Validate the 'assignedFacilityInformation' - 'levelOfCareCode' - 'displayName' field contains the value selected in the "(22056) Level of Care" extended dictionary element for the unit.
  20. Validate the 'assignedFacilityInformation' - 'totalNumberOfBeds' field contains the total number of beds in the unit.
  21. Validate the 'assignedFacilityInformation' - 'totalNumberOfBedsOccupied' field contains the total number of occupied beds in the unit.
  22. Validate the 'clientID' - 'id' field contains "NO_ID".
  23. Validate the 'name' - 'first' field contains "NO_NAME".
  24. Validate the 'name' - 'last' field contains "NO_LASTNAME".
  25. Navigate back to the 'CareFabric Monitor Report' and repeat steps 3e-3m as needed for the additional units that are configured.
  26. Close the report and the form.
Topics
• Update Client Data • Medical Note • Women's Health History • Dictionary • Treatment Plan • CareFabric Monitor • Admission • CareFabric • Diagnosis • Patient Health Questionnaire 9 • Vitals • System Task Scheduler
Update 30 Summary | Details
Avatar CareFabric - SubjectID values
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • CSI Assessment
  • CareFabric Monitor
  • Financial Investigation
  • CSI Admission
  • User Modeled Form
Scenario 1: ProviderConnect Enterprise - CSI Assessment - Validate the 'PutEhrAssessment' action
Specific Setup:
  • Avatar CareFabric->ProviderConnect Enterprise->Contracting Providers->->->Enable External Connections' must be set to "Y".
  • The 'Managing Organization Definition' form must be defined for a valid managing organization.
  • A client must be enrolled in an existing episode and be mapped to the defined managing organization in the 'ProviderConnect Enterprise Identifiers' section of the 'Admission' form (Client A).
  • Client A's episode must be in a program that has "Yes" selected in the 'Mental Health Program (CSI)' field in the 'Program Maintenance' form.
Steps
  1. Select "Client A" and access the 'CSI Assessment' form.
  2. Select the desired episode in the Pre-Display and click [OK].
  3. Populate all required and desired fields.
  4. Click [Submit].
  5. Access the 'ProviderConnect Enterprise Action Log'.
  6. Enter the desired dates in the 'From Date' and 'Through Date' fields.
  7. Enter the desired times in the 'From Time' and 'Through Time' fields.
  8. Select the desired organization in the 'Managing Organization' field.
  9. Select "PutEhrAssessment" in the 'Action Name' field.
  10. Click [View Action Log].
  11. Validate the 'ProviderConnect Enterprise Action Log' Report is displayed.
  12. Validate the 'ProviderConnect Enterprise Action Log' Report contains the 'PutEhrAssessment' action that was triggered from the 'CSI Assessment' form with a "Success" result.
  13. Close the report and the form.
Scenario 2: ProviderConnect Enterprise - Financial Investigation - Validate the 'PutEhrAssessment' action and 'EhrAssessmentResultCreated' event
Specific Setup:
  • The 'Avatar CareFabric->ProviderConnect Enterprise->Contracting Providers->->->Enable External Connections' registry setting must be set to "Y".
  • The 'Managing Organization Definition' form must be defined for a valid managing organization.
  • A client must be enrolled in an existing episode and be mapped to the defined managing organization in the 'ProviderConnect Enterprise Identifiers' section of the 'Admission' form (Client A).
Steps
  1. Select "Client A" and access the 'Financial Investigation' form.
  2. Enter the desired date in the 'Financial Investigation Effective Date' field.
  3. Enter the desired value in the 'Income-Responsible Party Annual Income' field.
  4. Enter the desired value in the 'Income-Household Gross Annual Income' field.
  5. Enter the desired value in the 'Family Size' field.
  6. Enter the desired value in the 'Number of Dependents' field.
  7. Click [Submit].
  8. Access the 'ProviderConnect Enterprise Action Log' form.
  9. Enter the desired dates in the 'From Date' and 'Through Date' fields.
  10. Enter the desired times in the 'From Time' and 'Through Time' fields.
  11. Select the desired organization in the 'Managing Organization' field.
  12. Select "PutEhrAssessment" in the 'Action Name' field.
  13. Click [View Action Log].
  14. Validate the 'ProviderConnect Enterprise Action Log' Report is displayed.
  15. Validate the 'ProviderConnect Enterprise Action Log' Report contains the 'PutEhrAssessment' action that was triggered from the 'Financial Investigation' form with a "Success" result.
  16. Close the report and the form.
Scenario 3: ProviderConnect Enterprise - CSI Admission - Validate the 'PutEhrAssessment' action
Specific Setup:
  • Avatar CareFabric->ProviderConnect Enterprise->Contracting Providers->->->Enable External Connections' must be set to "Y".
  • The 'Managing Organization Definition' form must be defined for a valid managing organization.
  • A client must be enrolled in an existing episode and be mapped to the defined managing organization in the 'ProviderConnect Enterprise Identifiers' section of the 'Admission' form (Client A).
  • Client A's episode must be in a program that has "Yes" selected in the 'Mental Health Program (CSI)' field in the 'Program Maintenance' form.
Steps
  1. Select "Client A" and access the 'CSI Admission' form.
  2. Select the desired episode in the Pre-Display and click [OK].
  3. Populate all required and desired fields.
  4. Click [Submit].
  5. Access the 'ProviderConnect Enterprise Action Log'.
  6. Enter the desired dates in the 'From Date' and 'Through Date' fields.
  7. Enter the desired times in the 'From Time' and 'Through Time' fields.
  8. Select the desired organization in the 'Managing Organization' field.
  9. Select "PutEhrAssessment" in the 'Action Name' field.
  10. Click [View Action Log].
  11. Validate the 'ProviderConnect Enterprise Action Log' Report is displayed.
  12. Validate the 'ProviderConnect Enterprise Action Log' Report contains the 'PutEhrAssessment' action that was triggered from the 'CSI Admission' form with a "Success" result.
  13. Close the report and the form.
Topics
• CSI Assessment • ProviderConnect Enterprise • CareFabric • Csi Admission
Update 31 Summary | Details
Bells Notes Integration - Group Appointments
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Client Ledger
Scenario 1: Bells Notes Integration - Validate group appointment progress notes
Specific Setup:
  • myAvatar must be configured to integrate with Bells Notes. Please note: this must be done by a Netsmart Associate.
  • The 'Progress Notes (Group and Individual)' form must have 'Document Routing' enabled.
  • The 'Post Appointment When the Note Is Submitted' 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 (Practitioner A)
  • 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 group is defined (Group A) with two clients (Client A & Client B).
  • An appointment for "Group A" must be scheduled for the current date with "Practitioner A".
Steps
  1. Log into Bells Notes as "User A".
  2. Navigate to the 'Agenda' section.
  3. Validate the appointment for "Group A" is displayed and select it.
  4. Click [Start Note].
  5. Validate the 'Group Session Information' window is displayed.
  6. Validate "Client A" and "Client B" are displayed for the appointment.
  7. Click [Start Note] and [Assign].
  8. Enter the desired value in the 'Group Summary' field.
  9. Populate required and desired details for "Client A" and "Client B", then mark reviewed.
  10. Click [Sign Reviewed Notes].
  11. Enter the pin for "User A" and click [Sign].
  12. Validate a message is displayed stating: Note Signed Successfully.
  13. Log into myAvatar as "User A".
  14. Access the 'Scheduling Calendar' form.
  15. Validate the appointment for "Group A" with "Practitioner A" has the posted disposition icon.
  16. Right click and select [View Summary] for the group appointment.
  17. Validate the appointment details are displayed and the 'Current Group Members' field contains "Client B" and "Client C".
  18. Click [Dismiss] and [OK].
  19. Select "Client A" and navigate to the 'Progress Notes' widget.
  20. Validate the 'Progress Notes' widget contains the finalized progress note submitted from Bells Notes for the appointment.
  21. Validate all progress note data displays as expected.
  22. Select "Client B" and navigate to the 'Progress Notes' widget.
  23. Validate the 'Progress Notes' widget contains the finalized progress note submitted from Bells Notes for the appointment.
  24. Validate all progress note data displays as expected.
  25. Access the 'Client Ledger' form.
  26. Select "Client A" in the 'Client ID' field.
  27. Select "All Episodes" in the 'Claim/Episode/All Episodes' field.
  28. Select "Simple" in the 'Ledger Type' field.
  29. Select "Yes" in the 'Include Zero Charges' field.
  30. Click [Process].
  31. Validate the group service posted in the previous steps is displayed as expected.
  32. Click [Close] and [Yes] to return to form.
  33. Select "Client B" in the 'Client ID' field.
  34. Select "All Episodes" in the 'Claim/Episode/All Episodes' field.
  35. Select "Simple" in the 'Ledger Type' field.
  36. Select "Yes" in the 'Include Zero Charges' field.
  37. Click [Process].
  38. Validate the group service posted in the previous steps is displayed as expected.
  39. Click [Close] and close the form.
Scenario 2: Bells Notes Integration - Validate adding/removing clients from a group appointment
Specific Setup:
  • myAvatar must be configured to integrate with Bells Notes. Please note: this must be done by a Netsmart Associate.
  • The 'Progress Notes (Group and Individual)' form must have 'Document Routing' enabled.
  • The 'Post Appointment When the Note Is Submitted' 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 (Practitioner A)
  • 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 group is defined (Group A) with two clients (Client A & Client B).
  • An appointment for "Group A" must be scheduled for the current date with "Practitioner A".
  • A client is defined (Client C) that is not part of "Group A".
Steps
  1. Log into Bells Notes as "User A".
  2. Navigate to the 'Agenda' section.
  3. Validate the appointment for "Group A" is displayed and select it.
  4. Click [Start Note].
  5. Validate the 'Group Session Information' window is displayed.
  6. Validate "Client A" and "Client B" are displayed for the appointment.
  7. Remove "Client A" from the group appointment.
  8. Search for and select to add "Client C" to the group appointment.
  9. Click [Start Note] and [Assign].
  10. Enter the desired value in the 'Group Summary' field.
  11. Populate required and desired details for "Client B" and "Client C", then click [Mark Reviewed] for each client.
  12. Click [Sign Reviewed Notes].
  13. Enter the pin for "User A" and click [Sign].
  14. Validate a message is displayed stating: Note Signed Successfully.
  15. Log into myAvatar as "User A".
  16. Access the 'Scheduling Calendar' form.
  17. Validate the appointment for "Group A" with "Practitioner A" has the posted disposition icon.
  18. Right click and select [View Summary] for the group appointment.
  19. Validate the appointment details are displayed and the 'Current Group Members' field contains "Client B" and "Client C".
  20. Click [Dismiss] and [OK].
  21. Select "Client B" and navigate to the 'Progress Notes' widget.
  22. Validate the 'Progress Notes' widget contains the finalized progress note submitted from Bells Notes for the appointment.
  23. Validate all progress note data displays as expected.
  24. Select "Client C" and navigate to the 'Progress Notes' widget.
  25. Validate the 'Progress Notes' widget contains the finalized progress note submitted from Bells Notes for the appointment.
  26. Validate all progress note data displays as expected.
  27. Access the 'Client Ledger' form.
  28. Select "Client B" in the 'Client ID' field.
  29. Select "All Episodes" in the 'Claim/Episode/All Episodes' field.
  30. Select "Simple" in the 'Ledger Type' field.
  31. Select "Yes" in the 'Include Zero Charges' field.
  32. Click [Process].
  33. Validate the group service posted in the previous steps is displayed as expected.
  34. Click [Close] and [Yes] to return to form.
  35. Select "Client C" in the 'Client ID' field.
  36. Select "All Episodes" in the 'Claim/Episode/All Episodes' field.
  37. Select "Simple" in the 'Ledger Type' field.
  38. Select "Yes" in the 'Include Zero Charges' field.
  39. Click [Process].
  40. Validate the group service posted in the previous steps is displayed as expected.
  41. Click [Close] and close the form.
Topics
• Scheduling Calendar • Progress Notes • Bells Notes • CareFabric
Update 32 Summary | Details
OE NX - MedNote - Problem Classification
Scenario 1: OE NX - Registry Setting "Problem Classification Required" set to "R" - MedNote: Validating 'Problem Classification' in Diagnosis - Document tab.
Specific Setup:
  • The 'Avatar CWS->Problem List->->->->Problem Classification Required' registry setting must be set to "R".
  • Please log out of the application and log back in after completing the above configuration.
  • A client must have an active episode. (Client A)
  • “Client A” must have a ‘Date of Birth’, ‘Sex’ and address on file in the ‘Update Client Data’ form, as well as information filed in the ‘Allergies and Hypersensitivities’ form, ‘Diagnosis’ form, and in the ‘Height’ and ‘Weight’ fields in the ‘Vitals Entry’ form.
Steps
  1. Select "Client A” and access the 'Medical Note'.
  2. Click [Add Note] and create a new note.
  3. Select the 'Document' tab and navigate to the 'Diagnosis' section.
  4. Click [Add] and [Add New Diagnosis].
  5. Fill out all required fields and select "Yes" from the 'Add to Problem List' field.
  6. Validate the 'Problem Classification' field is both enabled and required and the 'Save New Diagnosis' button is disabled.
  7. Select any value from the 'Problem Classification' field and validate the 'Save New Diagnosis' button is now enabled.
  8. Click [Save New Diagnosis] and [Save Diagnosis Set].
  9. Select the newly created diagnosis from the 'Current Diagnoses' list.
  10. Validate "Yes" is selected from the 'Add to Problem List' field and the previously selected value is displayed in the 'Problem Classification' field.
  11. Validate the 'Add to Problem List' field is disabled while the 'Problem Classification' field is enabled.
  12. Click [Cancel].
  13. Click [Add] and [Add New Diagnosis].
  14. Fill out all required fields and select "No" from the 'Add to Problem List' field.
  15. Validate the 'Problem Classification' field is both disabled and not required.
  16. Click [Save New Diagnosis] and [Save Diagnosis Set].
  17. Select the newly created diagnosis from the 'Current Diagnoses' list.
  18. Validate "No" is selected from the 'Add to Problem List' field and that the field is enabled.
Scenario 2: OE NX - Registry Setting "Problem Classification Required" set to "Y" - MedNote: Validating 'Problem Classification' in Diagnosis - Document tab.
Specific Setup:
  • The 'Avatar CWS->Problem List->->->->Problem Classification Required' registry setting must be set to "Y".
  • Please log out of the application and log back in after completing the above configuration.
  • A client must have an active episode. (Client A)
  • “Client A” must have a ‘Date of Birth’, ‘Sex’ and address on file in the ‘Update Client Data’ form, as well as information filed in the ‘Allergies and Hypersensitivities’ form, ‘Diagnosis’ form, and in the ‘Height’ and ‘Weight’ fields in the ‘Vitals Entry’ form.
Steps
  1. Select "Client A” and access the 'Medical Note'.
  2. Click [Add Note] and create a new note.
  3. Select the 'Document' tab and navigate to the 'Diagnosis' section.
  4. Click [Add] and [Add New Diagnosis].
  5. Fill out all required fields and select "Yes" from the 'Add to Problem List' field.
  6. Validate the 'Problem Classification' field is enabled but not required and the 'Save New Diagnosis' button is enabled.
  7. Select any value from the 'Problem Classification' field.
  8. Click [Save New Diagnosis] and [Save Diagnosis Set].
  9. Select the newly created diagnosis from the 'Current Diagnoses' list.
  10. Validate "Yes" is selected from the 'Add to Problem List' field and the previously selected value is displayed in the 'Problem Classification' field.
  11. Validate the 'Add to Problem List' field is disabled while the 'Problem Classification' field is enabled.
  12. Click [Cancel].
  13. Click [Add] and [Add New Diagnosis].
  14. Fill out all required fields and select "Yes" from the 'Add to Problem List' field.
  15. Validate the 'Problem Classification' field is enabled but not required and the 'Save New Diagnosis' button is enabled.
  16. Do not select any value from the 'Problem Classification' field.
  17. Click [Save New Diagnosis] and [Save Diagnosis Set].
  18. Select the newly created diagnosis from the 'Current Diagnoses' list.
  19. Validate "Yes" is selected from the 'Add to Problem List' field and no value is displayed in the 'Problem Classification' field.
  20. Validate the 'Add to Problem List' field is disabled while the 'Problem Classification' field is enabled.
  21. Click [Cancel].
  22. Click [Add] and [Add New Diagnosis].
  23. Fill out all required fields and select "No" from the 'Add to Problem List' field.
  24. Validate the 'Problem Classification' field is disabled and the 'Save New Diagnosis' button is enabled.
  25. Click [Save New Diagnosis] and [Save Diagnosis Set].
  26. Select the newly created diagnosis from the 'Current Diagnoses' list.
  27. Validate "No" is selected from the 'Add to Problem List' field and no value is displayed in the 'Problem Classification' field.
  28. Validate the 'Add to Problem List' field is enabled while the 'Problem Classification' field is disabled.
  29. Click [Cancel].
Scenario 3: OE NX - Registry Setting "Problem Classification Required" set to "N" - MedNote: Validating 'Problem Classification' in Diagnosis - Document tab.
Specific Setup:
  • The 'Avatar CWS->Problem List->->->->Problem Classification Required' registry setting must be set to "N".
  • Please log out of the application and log back in after completing the above configuration.
  • A client must have an active episode. (Client A)
  • “Client A” must have a ‘Date of Birth’, ‘Sex’ and address on file in the ‘Update Client Data’ form, as well as information filed in the ‘Allergies and Hypersensitivities’ form, ‘Diagnosis’ form, and in the ‘Height’ and ‘Weight’ fields in the ‘Vitals Entry’ form.
Steps
  1. Select "Client A” and access the 'Medical Note'
  2. Click [Add Note] and create a new note.
  3. Select the 'Document' tab and navigate to the 'Diagnosis' section.
  4. Click [Add] and [Add New Diagnosis].
  5. Fill out all required fields and select "Yes" from the 'Add to Problem List' field.
  6. Validate the 'Problem Classification' field is not shown and the 'Save New Diagnosis' button is enabled.
  7. Click [Save New Diagnosis] and [Save Diagnosis Set].
  8. Select the newly created diagnosis from the 'Current Diagnoses' list.
  9. Validate "Yes" is selected from the 'Add to Problem List' field and that the field is disabled.
  10. Click [Cancel].
  11. Click [Add] and [Add New Diagnosis].
  12. Fill out all required fields and select "No" from the 'Add to Problem List' field.
  13. Validate the 'Problem Classification' field is not shown and the 'Save New Diagnosis' button is enabled.
  14. Click [Save New Diagnosis] and [Save Diagnosis Set].
  15. Select the newly created diagnosis from the 'Current Diagnoses' list.
  16. Validate "No" is selected from the 'Add to Problem List' field and that the field is enabled.
  17. Click [Cancel].
Topics
• Diagnosis • Medical Note
Update 33 Summary | Details
Avatar CareFabric - Support for Bells Notes Integration
Scenario 1: Validate the 'GetValueSet' SDK action
Steps
  • Internal testing only.
Scenario 2: Validate the 'PutProgressNote' SDK action
Steps
  • Internal testing only.
Topics
• CareFabric • Progress Notes
Update 33.1 Summary | Details
Avatar CareFabric - Support for Bells Notes Integration
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Client Ledger
Scenario 1: Validate the 'GetValueSet' SDK action
Steps
  • Internal testing only.
Scenario 2: Validate the 'PutProgressNote' SDK action
Steps
  • Internal testing only.
Scenario 3: Bells Notes Integration - Validate document routing for existing appointment progress notes
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.
  • The 'Clear Selected Client After Filing' registry setting set to "Y".
  • 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.
  • 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 the desired value 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 as "User A".
  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 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.
  32. Select "Client A" and access the 'Progress Notes' widget.
  33. Validate the 'Progress Notes' widget contains the finalized progress note submitted from Bells Notes.
  34. Validate all progress note data displays as expected.
Scenario 4: Medical Note - Validate progress note sign off with Document Routing
Specific Setup:
  • The Medical Note POV is configured and accessible from the HomeView.
  • Have two users with associated practitioners (User A & User B).
  • Must be logged in as "User A" initially
  • Both users have the "My To Do's" widget on their home view
  • Document Routing is enabled in the 'Document Routing Setup' form.
  • A client has an existing progress note with all the required fields filled out (ClientA).
Steps
  1. Select "Client A" and access the 'Medical Note' application.
  2. Click [Select Note].
  3. Select [Edit] from the "Client's E&M Appointment" row.
  4. Verify the existence of the “Facesheet” section.
  5. Complete all required fields on "Document" and "Finalize" tabs.
  6. Click the "Finalize" tab and complete all the required fields.
  7. Do not select any add-on service codes.
  8. Click [Generate Note].
  9. Select "Complete" in the 'Completion Status' field.
  10. Click [Sign Off].
  11. Validate a "Confirm Document" dialog is displayed with the note details.
  12. Click [Accept and Route].
  13. Enter the password for "User A" in the 'Verify Password' field.
  14. Click [OK].
  15. Select the practitioner associated to "User B" as the approver.
  16. Click [Submit].
  17. Log out and log in as "User B".
  18. Navigate to the "My To Do's" widget.
  19. Locate the 'To Do' just routed and click [Approve Document].
  20. Validate the progress note details are displayed.
  21. Click [Accept] and [Sign].
  22. Enter the password for "User B" in the 'Verify Password' field.
  23. Click [OK].
  24. Validate the To Do is removed from the list.
  25. Access the 'Client Ledger' form.
  26. Enter "Client A" in the 'Client ID' field.
  27. Select "All Episodes" from the 'Claim/Episode/All Episodes' field.
  28. Select "Simple" from the 'Ledger Type' field.
  29. Select "Yes" from the 'Include Zero Charges' field.
  30. Click [Process].
  31. Verify the 'Client Ledger Report' page exists.
  32. Validate the 'Client Ledger Report' page contains the service created in the previous steps.
  33. Validate no add-on codes are displayed since none were selected in Medical Note.
  34. Click [Dismiss] and close the form.
Topics
• CareFabric • Progress Notes • Scheduling Calendar
Update 34 Summary | Details
Dictionary Update - 'AZ DAP' site specific extended attributes
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Update Client Data
  • CareFabric Monitor
Scenario 1: Dictionary Update - Validate the 'AZ DAP Ethnicity' site specific extended dictionary attribute
Specific Setup:
  • A client is enrolled in an existing episode (Client A).
  • A dictionary code/value is defined for the '(8) Ethnic Origin' data element (Dictionary A).
Steps
  1. Access the 'Dictionary Update' PM form.
  2. Select "Client" in the 'File' field.
  3. Select "(8) Ethnic Origin" in the 'Data Element' field.
  4. Enter "Dictionary A" in the 'Dictionary Code' field.
  5. Validate the 'Dictionary Value' field populates accordingly.
  6. Validate the 'Extended Dictionary Data Element' field contains "(40003) AZ DAP Ethnicity" and select it.
  7. Validate the 'Extended Dictionary Value (Single Dictionary)' field contains the following values:
  8. Hispanic or Latino
  9. Not Hispanic or Latino
  10. Unknown
  11. Select the desired value in the 'Extended Dictionary Value (Single Dictionary)' field.
  12. Click [Apply Changes].
  13. Validate a message is displayed stating: Filed!
  14. Click [OK] and close the form.
  15. Select "Client A" and access the 'Update Client Data' form.
  16. Select "Dictionary A" in the 'Ethnic Origin' field.
  17. Submit the form.
  18. Access the 'CareFabric Monitor' form.
  19. Enter the current date in the 'From Date' and 'Through Date' fields.
  20. Select "Client A" in the 'Client ID' field.
  21. Click [View Activity Log].
  22. Validate a "ClientUpdated" record is displayed.
  23. Click [Click To View Record].
  24. Validate the 'ethnicityCode' - 'code' field contains the code associated to the extended dictionary value selected in the previous steps.
  25. Validate the 'ethnicityCode' - 'displayName' field contains the extended dictionary value selected in the previous steps.
  26. Validate the 'ethnicityCode' - 'ehrCode' field contains the code associated to "Dictionary A".
  27. Validate the 'ethnicityCode' - 'ehrDisplayName' field contains the value associated to "Dictionary A".
  28. Close the report and the form.
Scenario 2: Dictionary Update - Validate the 'AZ DAP Admission Type' site specific extended dictionary attribute
Specific Setup:
  • A client is enrolled in an existing episode (Client A).
  • A dictionary code/value is defined for the '(158) Source of Admission' data element (Dictionary A).
Steps
  1. Access the 'Dictionary Update' PM form.
  2. Select "Client" in the 'File' field.
  3. Select "(158) Source Of Admission" in the 'Data Element' field.
  4. Enter "Dictionary A" in the 'Dictionary Code' field.
  5. Validate the 'Dictionary Value' field populates accordingly.
  6. Validate the 'Extended Dictionary Data Element' field contains "(40002) AZ DAP Admission Type" and select it.
  7. Validate the 'Extended Dictionary Value (Single Dictionary)' field contains the following values:
  8. ACCIDENT
  9. ELECTIVE
  10. EMERGENCY
  11. LABOR AND DELIVERY
  12. NEWBORN
  13. PETITION
  14. PICK-UP ORDER
  15. POLICE
  16. ROUTINE
  17. UNIQUE
  18. URGENT
  19. VOLUNTARY
  20. Select the desired value in the 'Extended Dictionary Value (Single Dictionary)' field.
  21. Click [Apply Changes].
  22. Validate a message is displayed stating: Filed!
  23. Click [OK] and close the form.
  24. Select "Client A" and access the 'Admission' form.
  25. Select any existing episode and click [Edit].
  26. Select "Dictionary A" in the 'Source Of Admission' field.
  27. Submit the form.
  28. Access the 'CareFabric Monitor' form.
  29. Enter the current date in the 'From Date' and 'Through Date' fields.
  30. Select "Client A" in the 'Client ID' field.
  31. Click [View Activity Log].
  32. Validate a "ProgramAdmissionUpdated" record is displayed.
  33. Click [Click To View Record].
  34. Validate the 'sourceOfAdmissionCode' - 'code' field contains the code associated to the extended dictionary value selected in the previous steps.
  35. Validate the 'sourceOfAdmission' - 'displayName' field contains the extended dictionary value selected in the previous steps.
  36. Validate the 'sourceOfAdmissionCode' - 'ehrCode' field contains the code associated to the extended dictionary value selected in the previous steps.
  37. Validate the 'sourceOfAdmission' - 'ehrDisplayName' field contains the extended dictionary value selected in the previous steps.
  38. Close the report and the form.
Avatar CareFabric - 'ProgramAdmission' and 'Client' event types
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • CareFabric Monitor
  • Update Client Data
  • CareFabric Event Attribute Mapping
Scenario 1: Inpatient Admission - Validate the 'ClientCreated' and 'ClientUpdated' SDK events
Specific Setup:
  • Please note: this is for Avatar PM systems only.
  • A unit must be defined with available rooms and beds (Unit A).
Steps
  1. Access the 'Dictionary Update' PM form.
  2. Select "Client" in the 'File' field.
  3. Select "Data Element Number" in the 'Data Element' field.
  4. Select "(202) Unit" in the 'Data Element' field.
  5. Enter the code associated to "Unit A" in the 'Dictionary Code' field.
  6. Validate "Unit A" is displayed in the 'Dictionary Value' field.
  7. Select "(22055) Facility Abbreviation" in the 'Extended Dictionary Data Element' field.
  8. Validate the 'Extended Dictionary Value (Free Text)' field is now enabled. Enter the desired value.
  9. Select "(22056) Level of Care" in the 'Extended Dictionary Data Element' field.
  10. Validate the 'Extended Dictionary Value (Single Dictionary)' field is now enabled and contains the following values:
  11. Inpatient
  12. Observation
  13. Outpatient
  14. Select the desired value in the 'Extended Dictionary Value (Single Dictionary)' field.
  15. Click [Apply Changes].
  16. Validate a message is displayed stating: Filed!
  17. Click [OK] and close the form.
  18. Access the 'Admission' form
  19. Verify the 'Select Client' dialog is displayed.
  20. Enter any new value in the 'Last Name' field.
  21. Enter any new value in the 'First Name' field.
  22. Select any value in the 'Sex' field.
  23. Click [Search].
  24. Validate a "Search Results" message is displayed stating: No matches found.
  25. Click [New Client].
  26. Validate a "Client" message is displayed stating: Auto Assign Next ID Number?
  27. Click [Yes].
  28. Enter any value in the 'Date of Birth' field.
  29. Enter the current date in the 'Preadmit/Admission Date' field.
  30. Enter the current time in the 'Preadmit/Admission Time' field.
  31. Select any inpatient program in the 'Program' field.
  32. Select any value in the 'Type Of Admission' field.
  33. Select any value in the 'Source Of Admission' field.
  34. Enter the desired practitioner in the 'Admitting Practitioner' field.
  35. Enter the desired practitioner in the 'Attending Practitioner' field.
  36. Select the "Inpatient/Partial/Day Treatment" section.
  37. Select "Unit A" in the 'Unit' field.
  38. Select the desired room in the 'Room' field.
  39. Select the desired bed in the 'Bed' field.
  40. Select the desired value in the 'Room And Board Billing Code' field.
  41. Submit the form. Note: this will now be referred to as "Client A".
  42. Access the 'CareFabric Monitor' form.
  43. Enter the current date in the 'From Date' and 'Through Date' fields.
  44. Select "Client A" in the 'Client ID' field.
  45. Click [View Activity Log].
  46. Validate the 'CareFabric Monitor' report is displayed and contains "ClientCreated" record.
  47. Click [Click To View Record] for the "ClientCreated" record.
  48. Validate the 'assignedFacilityInformation' - 'facilityMneumonic' field contains the value defined in the "(22055) Facility Abbreviation" extended dictionary element for "Unit A".
  49. 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".
  50. Validate the 'assignedFacilityInformation' - 'levelOfCareCode' - 'displayName' field contains the value selected in the "(22056) Level of Care" extended dictionary element for "Unit A".
  51. Validate the 'assignedFacilityInformation' - 'totalNumberOfBeds' field contains the total number of beds in "Unit A".
  52. Validate the 'assignedFacilityInformation' - 'totalNumberOfBedsOccupied' field contains the total number of occupied beds in "Unit A".
  53. Close the report and the form.
  54. Select "Client A" and access the 'Update Client Data' form.
  55. Enter the desired value in the 'Date Of Birth' field.
  56. Click [Submit].
  57. Access the 'CareFabric Monitor' form.
  58. Enter the current date in the 'From Date' and 'Through Date' fields.
  59. Select "Client A" in the 'Client ID' field.
  60. Click [View Activity Log].
  61. Validate the 'CareFabric Monitor' report is displayed and contains "ClientUpdated" record.
  62. Click [Click To View Record] for the "ClientUpdated" record.
  63. Validate the 'assignedFacilityInformation' - 'facilityMneumonic' field contains the value defined in the "(22055) Facility Abbreviation" extended dictionary element for "Unit A".
  64. 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".
  65. Validate the 'assignedFacilityInformation' - 'levelOfCareCode' - 'displayName' field contains the value selected in the "(22056) Level of Care" extended dictionary element for "Unit A".
  66. Validate the 'assignedFacilityInformation' - 'totalNumberOfBeds' field contains the total number of beds in "Unit A".
  67. Validate the 'assignedFacilityInformation' - 'totalNumberOfBedsOccupied' field contains the total number of occupied beds in "Unit A".
  68. Validate the 'birthDate' field contains the 'Date Of Birth' filed in the previous steps.
  69. Close the report and the form.
  70. Select "Client A" and access the 'Discharge' form.
  71. Enter the desired date in the 'Date Of Discharge' field.
  72. Enter the desired time in the 'Time Of Discharge' field.
  73. Select the desired value in the 'Type Of Discharge' field.
  74. Select the desired value in the 'Discharge Practitioner' field.
  75. Click [Submit].
  76. Access the 'CareFabric Monitor' form.
  77. Enter the current date in the 'From Date' and 'Through Date' fields.
  78. Select "Client A" in the 'Client ID' field.
  79. Click [View Activity Log].
  80. Validate the 'CareFabric Monitor' report is displayed and contains "ClientUpdated" record.
  81. Click [Click To View Record] for the "ClientUpdated" record.
  82. Validate the 'assignedFacilityInformation' - 'facilityMneumonic' field contains the value defined in the "(22055) Facility Abbreviation" extended dictionary element for "Unit A". If a client is no longer occupying a bed, the system will calculate the last unit the client was in and populate this field accordingly.
  83. 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".
  84. Validate the 'assignedFacilityInformation' - 'levelOfCareCode' - 'displayName' field contains the value selected in the "(22056) Level of Care" extended dictionary element for "Unit A".
  85. Validate the 'assignedFacilityInformation' - 'totalNumberOfBeds' field contains the total number of beds in "Unit A".
  86. Validate the 'assignedFacilityInformation' - 'totalNumberOfBedsOccupied' field contains the updated total number of occupied beds in "Unit A" after "Client A" has been discharged.
  87. Close the report and the form.
Scenario 2: Validate the "ProgramAdmission" event type in the 'CareFabric Event Attribute Mapping' form
Specific Setup:
  • A dictionary code/value is defined for the '(158) Source of Admission' data element (Dictionary A).
  • A client is enrolled in an existing episode (Client A).
Steps
  1. Access the 'Dictionary Update' PM form.
  2. Select "Client" in the 'File' field.
  3. Select "(158) Source Of Admission" in the 'Data Element' field.
  4. Enter "Dictionary A" in the 'Dictionary Code' field.
  5. Validate the 'Dictionary Value' field populates accordingly.
  6. Select "(40002) AZ DAP Admission Type" in the 'Extended Dictionary Data Element' field.
  7. Select "ROUTINE" in the 'Extended Dictionary Value (Single Dictionary)' field.
  8. Click [Apply Changes].
  9. Validate a message is displayed stating: Filed!
  10. Click [OK] and close the form.
  11. Access the 'CareFabric Event Attribute Mapping' form.
  12. Select "ProgramAdmission" in the 'Associated Event' field.
  13. Click [New Row].
  14. Select "[PM] Admission" in the 'Form' field.
  15. Select "Source Of Admission" in the 'Field' field.
  16. Select "SourceOfAdmissionCode" in the 'CareFabric Element' field.
  17. Select "AZ DAP Admission Type" in the 'Extended Attribute to Pull the Code From' field.
  18. Enter the desired value in the 'Non-standard Code System Code' field.
  19. Enter the desired value in the 'Non-standard Code System Name' field.
  20. Select the desired value in the 'Allow CarePOV Access' field.
  21. Click [Field Translation].
  22. Validate the 'CareFabric Event Attribute Mapping' grid is displayed with the dictionary codes/values for the '(40002) AZ DAP Admission Type' extended dictionary element.
  23. Navigate to the row for the "ROUTINE" dictionary value and select it.
  24. Select "Yes" in the 'Include?' field.
  25. Enter the desired value in the 'Reporting Code' field.
  26. Enter the desired value in the 'Reporting Value' field.
  27. Click [Save], [Yes], and [Submit].
  28. Select "Client A" and access the 'Admission' form.
  29. Select any existing episode and click [Edit].
  30. Select "Dictionary A" in the 'Source Of Admission' field.
  31. Submit the form.
  32. Access the 'CareFabric Monitor' form.
  33. Enter the current date in the 'From Date' and 'Through Date' fields.
  34. Select "Client A" in the 'Client ID' field.
  35. Click [View Activity Log].
  36. Validate a "ProgramAdmissionUpdated" record is displayed.
  37. Click [Click To View Record].
  38. Validate the 'sourceOfAdmissionCode' - 'code' field contains the 'Reporting Code' filed in the previous steps.
  39. Validate the 'sourceOfAdmission' - 'displayName' field contains the 'Reporting Value' filed in the previous steps.
  40. Validate the 'sourceOfAdmissionCode' - 'ehrCode' field contains the 'Reporting Code' filed in the previous steps.
  41. Validate the 'sourceOfAdmission' - 'ehrDisplayName' field contains the 'Reporting Value' filed in the previous steps.
  42. Close the report and the form.
  43. Access the 'CareFabric Event Attribute Mapping' form.
  44. Select "ProgramAdmission" in the 'Associated Event' field.
  45. Select the existing row in the 'Additional Attributes' grid.
  46. Click [Field Translation].
  47. Navigate to the row for the "ROUTINE" dictionary value and select it.
  48. Select "No" in the 'Include?' field.
  49. Click [Save], [Yes], and [Submit].
  50. Select "Client A" and access the 'Admission' form.
  51. Select any existing episode and click [Edit].
  52. Update the 'Preadmit/Admission Time' field.
  53. Click [Submit].
  54. Access the 'CareFabric Monitor' form.
  55. Enter the current date in the 'From Date' and 'Through Date' fields.
  56. Select "Client A" in the 'Client ID' field.
  57. Click [View Activity Log].
  58. Validate a "ProgramAdmissionUpdated" record is displayed.
  59. Click [Click To View Record].
  60. Validate the 'sourceOfAdmissionCode' field contains "null".
  61. Close the report and the form.
Scenario 3: Validate the "Client" event type in the 'CareFabric Event Attribute Mapping' form
Specific Setup:
  • A client is enrolled in an existing episode (Client A).
  • A dictionary code/value is defined for the '(8) Ethnic Origin' data element (Dictionary A).
Steps
  1. Access the 'Dictionary Update' PM form.
  2. Select "Client" in the 'File' field.
  3. Select "(8) Ethnic Origin" in the 'Data Element' field.
  4. Enter "Dictionary A" in the 'Dictionary Code' field.
  5. Validate the 'Dictionary Value' field populates accordingly.
  6. Select "(40003) AZ DAP Ethnicity" in the 'Extended Dictionary Data Element' field.
  7. Select "Not Hispanic or Latino" in the 'Extended Dictionary Value (Single Dictionary)' field.
  8. Click [Apply Changes].
  9. Validate a message is displayed stating: Filed!
  10. Click [OK] and close the form.
  11. Access the 'CareFabric Event Attribute Mapping' form.
  12. Select "Client" in the 'Associated Event' field.
  13. Click [New Row].
  14. Select "[PM] Update Client Data" in the 'Form' field.
  15. Select "Ethnic Origin" in the 'Field' field.
  16. Select "EthnicityCode" in the 'CareFabric Element' field.
  17. Select "AZ DAP Ethnicity" in the 'Extended Attribute to Pull the Code From' field.
  18. Enter the desired value in the 'Non-standard Code System Code' field.
  19. Enter the desired value in the 'Non-standard Code System Name' field.
  20. Select the desired value in the 'Allow CarePOV Access' field.
  21. Click [Field Translation].
  22. Validate the 'CareFabric Event Attribute Mapping' grid is displayed with the dictionary codes/values for the '(40003) AZ DAP Ethnicity' extended dictionary element.
  23. Navigate to the row for the "Not Hispanic or Latino" dictionary value and select it.
  24. Select "Yes" in the 'Include?' field.
  25. Enter the desired value in the 'Reporting Code' field.
  26. Enter the desired value in the 'Reporting Value' field.
  27. Click [Save], [Yes], and [Submit].
  28. Select "Client A" and access the 'Update Client Data' form.
  29. Select "Dictionary A" in the 'Ethnic Origin' field.
  30. Click [Submit].
  31. Access the 'CareFabric Monitor' form.
  32. Enter the current date in the 'From Date' and 'Through Date' fields.
  33. Select "Client A" in the 'Client ID' field.
  34. Click [View Activity Log].
  35. Validate a "ClientUpdated" record is displayed.
  36. Click [Click To View Record].
  37. Validate the 'ethnicityCode' - 'code' field contains the 'Reporting Code' filed in the previous steps.
  38. Validate the 'ethnicityCode' - 'displayName' field contains the 'Reporting Value' filed in the previous steps.
  39. Validate the 'ethnicityCode' - 'ehrCode' field contains the code associated to "Dictionary A".
  40. Validate the 'ethnicityCode' - 'ehrDisplayName' field contains the value associated to "Dictionary A".
  41. Close the report and the form.
  42. Access the 'CareFabric Event Attribute Mapping' form.
  43. Select "Client" in the 'Associated Event' field.
  44. Select the existing row in the 'Additional Attributes' grid.
  45. Click [Field Translation].
  46. Navigate to the row for the "Not Hispanic or Latino" dictionary value and select it.
  47. Select "No" in the 'Include?' field.
  48. Click [Save], [Yes], and [Submit].
  49. Select "Client A" and access the 'Update Client Data' form.
  50. Update the 'Date Of Birth' field.
  51. Click [Submit].
  52. Access the 'CareFabric Monitor' form.
  53. Enter the current date in the 'From Date' and 'Through Date' fields.
  54. Select "Client A" in the 'Client ID' field.
  55. Click [View Activity Log].
  56. Validate a "ClientUpdated" record is displayed.
  57. Click [Click To View Record].
  58. Validate the 'ethnicityCode' field contains "null".
  59. Close the report and the form.
Topics
• Dictionary • CareFabric • Admission • Discharge • Update Client Data • CareFabric Monitor • CareFabric Event Attribute Mapping
Update 35 Summary | Details
Avatar CareFabric - 'GetClientServiceHistory' SDK action
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • SoapUI - ClientServices - ClientServicesService - GetClientServicesByDate
  • SoapUI - ClientServices - ClientServicesService - GetClientServicesByDate - GetClientServicesByDateResult
Scenario 1: Validate the 'GetClientServiceHistory' SDK action
Steps
  • Internal testing only.
Topics
• CareFabric • Web Services
Update 36 Summary | Details
Delete Last Movement - SDK events
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Delete Last Movement
  • CareFabric Monitor
Scenario 1: Delete Last Movement - Delete a 'Discharge' movement and validate the 'ProgramDischargeDeleted' and 'BehavioralHealthEpisodeUpdated' SDK events
Specific Setup:
  • A client has an existing episode that has been discharged (Client A).
Steps
  1. Select "Client A" and access the 'Delete Last Movement' form.
  2. Select the existing episode that has been discharged in the 'Episode Number' field.
  3. Validate the 'Client Information' field populates as expected.
  4. Click [Submit].
  5. Validate a message is displayed stating: You are about to delete a Discharge movement. Do you want to continue?
  6. Click [Yes].
  7. Access the 'CareFabric Monitor' form.
  8. Enter the current date in the 'From Date' and 'Through Date' fields.
  9. Select "Client A" in the 'Client ID' field.
  10. Click [View Activity Log].
  11. Validate the 'CareFabric Monitor Report' is displayed and contains "ProgramDischargeDeleted" and "BehavioralHealthEpisodeUpdated" records.
  12. Select the "ProgramDischargeDeleted" record and click [Click To View Record].
  13. Validate the 'programDischargeID' - 'id' field contains the discharge ID for "Client A".
  14. Navigate back to the 'CareFabric Monitor Report'.
  15. Select the "BehavioralHealthEpisodeUpdated" record and click [Click To View Record].
  16. Validate the 'behavioralHealthEpisodeID' - 'id' field contains the episode ID for "Client A".
  17. Close the report and the form.
Scenario 2: Delete Last Movement - Delete an 'Admission' movement and validate the 'ProgramAdmissionDeleted' and 'BehavioralHealthEpisodeUpdated' SDK events
Specific Setup:
  • A client has an existing episode (Client A).
Steps
  1. Select "Client A" and access the 'Delete Last Movement' form.
  2. Select the existing episode in the 'Episode Number' field.
  3. Validate the 'Client Information' field populates as expected.
  4. Click [Submit].
  5. Validate a message is displayed stating: You are about to delete an Admission movement. Do you want to continue?
  6. Click [Yes].
  7. Access the 'CareFabric Monitor' form.
  8. Enter the current date in the 'From Date' and 'Through Date' fields.
  9. Select "Client A" in the 'Client ID' field.
  10. Click [View Activity Log].
  11. Validate the 'CareFabric Monitor Report' is displayed and contains "ProgramAdmissionDeleted" and "BehavioralHealthEpisodeDeleted" records.
  12. Select the "ProgramAdmissionDeleted" record and click [Click To View Record].
  13. Validate the 'programAdmissionID' - 'id' field contains the admission ID for "Client A".
  14. Navigate back to the 'CareFabric Monitor Report'.
  15. Select the "BehavioralHealthEpisodeDeleted" record and click [Click To View Record].
  16. Validate the 'behavioralHealthEpisodeID' - 'id' field contains the episode ID for "Client A".
  17. 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:
  • System Task Scheduler
  • CareFabric Monitor
  • Update Client Data
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
  1. Access the 'System Task Scheduler' form.
  2. Select "Avatar CareFabric - Send Facility Bed Information (HL-7) Recurrence Pattern : Hourly -Inactive" in the 'Schedule(s)' field.
  3. Validate "Hourly" is selected in the 'Recurrence Pattern' field.
  4. Validate the 'Start Time' field contains "12:00 AM".
  5. Validate the 'End Time' field contains "11:59 PM".
  6. Validate "Yes" is selected in the 'Inactive Task' field.
  7. Enter the current date in the 'Start By' field.
  8. Select "No" in the 'Inactive Task' field.
  9. Click [Schedule Task] and close the form.
  10. Wait for the task to run.
  11. Access the 'CareFabric Monitor' form.
  12. Enter the current date in the 'From Date' and 'Through Date' fields.
  13. Select "ClientUpdated" in the 'Event/Action Search' field.
  14. Click [View Activity Log].
  15. Validate the 'CareFabric Monitor Report' is displayed with a "ClientUpdated" record for each unit configured in the pre-conditions.
  16. Click [Click To View Record] for the first record.
  17. Validate the 'assignedFacilityInformation' - 'facilityMneumonic' field contains the value defined in the "(22055) Facility Abbreviation" extended dictionary element for the unit.
  18. 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.
  19. Validate the 'assignedFacilityInformation' - 'levelOfCareCode' - 'displayName' field contains the value selected in the "(22056) Level of Care" extended dictionary element for the unit.
  20. Validate the 'assignedFacilityInformation' - 'totalNumberOfBeds' field contains the total number of beds in the unit.
  21. Validate the 'assignedFacilityInformation' - 'totalNumberOfBedsOccupied' field contains the total number of occupied beds in the unit.
  22. Validate the 'clientID' - 'id' field contains "NO_ID".
  23. Validate the 'name' - 'first' field contains "NO_NAME".
  24. Validate the 'name' - 'last' field contains "NO_LASTNAME".
  25. Navigate back to the 'CareFabric Monitor Report' and repeat steps 3e-3m as needed for the additional units that are configured.
  26. Close the report and the form.
Topics
• Admission • Discharge • CareFabric Monitor • System Task Scheduler • CareFabric
Update 38 Summary | Details
Medical Note - Add-on Service Codes
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Client Ledger
  • Document.In-Office Administration.LotNumberManager
  • Registry Settings (PM)
Scenario 1: Medical Note - Verify multiple add-on charge codes with Document Routing and validate services in the 'Client Ledger' form
Specific Setup:
  • Test client (Client A) enrolled in an existing service program
  • Service program must be filtered by "Individual Service Codes". This must be done in the 'Program Maintenance' form
  • Existing E&M service codes and non-E&M service codes are assigned to the current program
  • A Service Code must exist with the assigned add-on service codes
  • Tester must schedule two appointments (Appointment A and Appointment B) for the current date
  • Document routing must be enabled for the Medical Note Progress Note
  • Registry Setting "Enable Multiple Add-On code Per Primary Code Functionality" is enabled
  • User with access to the 'Client Ledger' form
Steps
  1. Open the "Medical Note" widget.
  2. Open "Appointment A" that was created in preconditions.
  3. Enter data for any of the required sections.
  4. Navigate to the "Finalize" tab.
  5. Be sure to fill out the "CPT Selection" section by selecting a CPT code that is defined to include "Add on Services".
  6. Make sure to select at least one of the "Add On Services" that are attached to the CPT code.
  7. Generate the progress note.
  8. Once the medical note is completed, click "Sign Off".
  9. Note that the "Add on Services" information is included toward the end of the progress note.
  10. Click "Accept" on the .tif preview screen.
  11. Open the 'Client Ledger' form for the test client.
  12. Select "Client A" in the 'Client ID' field.
  13. Select "Episode" from the 'All Episodes - Claim/Episode/All Episodes' field.
  14. Select the episode the appointment was created for from the 'Episode Number' field.
  15. Select "Simple" in the 'Ledger Type' field.
  16. Click [Process].
  17. Verify that the ledger displays the service code from the posted appointment.
  18. Verify that the ledger displays the add-on charge codes from the posted appointment.
  19. Click [Dismiss].
  20. Open "Appointment B" that was created in preconditions.
  21. Enter data for any of the required sections.
  22. Navigate to the "Finalize" tab.
  23. Be sure to fill out the "CPT Selection" section by selecting a CPT code that is defined to include "Add on Services".
  24. Make sure to select at least one of the "Add on Services" that are attached to the CPT code.
  25. Generate the progress note.
  26. Once the medical note is completed, click "Sign Off".
  27. Note that the "Add on Service" information is included toward the end of the progress note.
  28. Click "Accept&Route" on the .tif preview screen and route the document to a supervisor or approver.
  29. Log in to Avatar as the user the document was routed to.
  30. In the "myToDo" widget, approve the document that was routed to that user.
  31. Open the 'Client Ledger' form for the test client.
  32. Select "Client A" in the 'Client ID' field.
  33. Select "Episode" from the 'All Episodes - Claim/Episode/All Episodes' field.
  34. Select the episode the appointment was created for from the 'Episode Number' field.
  35. Select "Simple" in the 'Ledger Type' field.
  36. Click [Process].
  37. Verify that the ledger displays the service code from the posted appointment.
  38. Verify that the ledger displays the add-on charge codes from the posted appointment.
  39. Click [Dismiss].
  40. Validate that a 'Form Return' message is displayed stating: Processing report has completed. Do you wish to return to form?
  41. Click [No].
Scenario 2: 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
  1. Search for and select "Client A" and navigate to the 'Medical Note'.
  2. Click [Add Note].
  3. Create a 'Primary Care' note.
  4. Select the ‘Document’ tab.
  5. Select ‘Immunizations’.
  6. Click [Add] and select "Medication A" from the 'Immunization Search' field.
  7. Validate the 'Dose', 'Unit', and 'Route' fields automatically populate based on the entries made in "Template A".
  8. Fill in any remaining required fields and click [Order].
  9. Validate the 'Pending Administrations' field contains a row for "Medication A"
  10. Click [Add] and select "Medication B" from the 'Immunization Search' field.
  11. Validate the 'Dose', 'Unit', and 'Route' fields automatically populate based on the entries made in "Template B".
  12. Fill in any remaining required fields and click [Administer].
  13. Validate, in the first section, the 'Dose', 'Unit', and 'Route' fields are correctly populated with the updated values and that all fields are disabled.
  14. Select "Yes" for the 'Consent Obtained' radio button.
  15. Select "Not VFC eligible" from the 'VFC Eligibility Code' field.
  16. Select "Facility" from the 'Provided By' field.
  17. Click the 'Lot Number Search' button and validate the 'Lot Number Manager' dialog is launched.
  18. Select the row for "Inventory B" and click [Select].
  19. Validate the 'Lot Number', 'Manufacturer', 'Expiration Date', and 'NDC' are all correctly populated and disabled.
  20. Fill in any remaining required fields and click [Save].
  21. Expand the 'Immunization History' field and validate it contains a row for "Medication B" and that all columns are accurate.
  22. Populate any remaining required sections in the 'Document' tab.
  23. Select the ‘Finalize’ tab.
  24. Populate all required fields and click [Generate Note].
  25. Validate the ‘Note Summary’ is displayed and contains the appropriate information and click [Sign Off].
  26. Validate the 'Progress Note' is displayed and click [Accept], set the ‘Password’ field to the appropriate value, and click [Verify].
  27. Refresh Medical Note.
  28. Click [Add Note].
  29. Create a 'Primary Care' note.
  30. Select the 'Document' tab and navigate to the 'Immunization' section.
  31. Validate the 'Pending Administrations' field contains a row for "Medication A"
  32. Click the ellipses under the 'Action' column for "Medication A" and click [Administer].
  33. Validate, in the first section, the 'Dose', 'Unit', and 'Route' fields are correctly populated with the updated values and that all fields are disabled.
  34. Select "Yes" for the 'Consent Obtained' field.
  35. Select "Not VFC eligible" from the 'VFC Eligibility Code' field.
  36. Select "Facility" from the 'Provided By' field.
  37. Click the 'Lot Number Search' button and validate the 'Lot Number Manager' dialog is launched.
  38. Select the row for "Inventory A" and click [Select].
  39. Validate the 'Lot Number', 'Manufacturer', 'Expiration Date', and 'NDC' are all correctly populated and disabled.
  40. Populate all remaining required fields and click [Save].
  41. Expand the 'Immunization History' field and validate it contains a row for "Medication A" and that all columns are accurate.
Scenario 3: Bells Notes Integration - Validate Multiple Add-On Service Code Functionality 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 'Enable Multiple Add-On Code Per Primary Code Functionality' registry setting is enabled.
  • A primary service code is defined (Service Code A) with multiple add-on codes associated (Add On 1, Add On 2, Add On 3).
  • The 'Progress Notes (Group and Individual)' form must be configured for Bells Notes with the following:
  • Document routing enabled
  • The following fields added via 'Site Specific Section Modeling':
  • Add-On Service
  • Add-On Duration
  • Save Add-On Service
  • Selected Add-On Services
  • Select Add-On Service Entry to Edit/Remove
  • Remove Add-On Service
  • Add-On Service Notes
  • 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 'Progress Notes' and 'My To Do's' widget on the HomeView.
  • A client is enrolled in an existing episode (Client A).
Steps
  1. Log into Bells Notes as "User A".
  2. Search for "Client A".
  3. Click [Start Note] and verify the existence of the 'Session Information' window.
  4. Select "Service Code A" in the 'Service Code' field.
  5. Fill out all required fields and select the desired note type.
  6. Verify the existence of "Client A" in the client header when note is started.
  7. Fill out all required fields.
  8. Select "Add On 1", "Add On 2", and "Add On 3" in the 'Add-On Services' field.
  9. Enter the desired duration/comments for each add-on.
  10. Click [Sign Note].
  11. Validate the Sign Note' dialog is displayed.
  12. Enter the pin for "User A" in the 'Pin' field and click [Sign].
  13. Validate a message is displayed stating: Note Signed Successfully.
  14. Log into myAvatar as "User A".
  15. Navigate to the "My To Do's" widget.
  16. Validate a 'To-Do' is not displayed for the note sent via Bells Notes since "User A" does not require an approver.
  17. Access the 'Clinical Document Viewer' form.
  18. Select "Client" in the 'Select Type' field.
  19. Select "Individual" in the 'Select All or Individual Client' field.
  20. Select "Client A" in the 'Select Client' field.
  21. Select "All" in the 'Episode' field.
  22. Click [Process].
  23. Validate a document is displayed for the progress note filed from Bells Notes.
  24. Select the document and click [View].
  25. Validate the PDF generated from Bells Notes is displayed with the note details, including the add-on codes.
  26. Click [Close All Documents], [Search], and [Close].
  27. Select "Client A" and access the 'Progress Notes' widget.
  28. Validate the note filed in the previous steps is displayed and contains all progress note data, including the 'Selected Add-On Services'.
  29. Access the 'Client Ledger' form.
  30. Select "Client A" in the 'Client ID' field.
  31. Select "All Episodes" in the 'Claim/Episode/All Episodes' field.
  32. Select "Simple" in the 'Ledger Type' field.
  33. Select "Yes" in the 'Include Zero Charges' field.
  34. Click [Process].
  35. Validate the 'Client Ledger' report contains "Service Code A", "Add On 1", "Add On 2" and "Add On 3".
  36. Close the report and the form.
Scenario 4: Bells Notes Integration - Validate Multiple Add-On Service Code Functionality 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 'Enable Multiple Add-On Code Per Primary Code Functionality' registry setting is enabled.
  • A primary service code is defined (Service Code A) with multiple add-on codes associated (Add On 1, Add On 2, Add On 3).
  • The 'Progress Notes (Group and Individual)' form must be configured for Bells Notes with the following:
  • The following fields added via 'Site Specific Section Modeling':
  • Add-On Service
  • Add-On Duration
  • Save Add-On Service
  • Selected Add-On Services
  • Select Add-On Service Entry to Edit/Remove
  • Remove Add-On Service
  • Add-On Service Notes
  • 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
  1. Log into Bells Notes as "User A".
  2. Search for "Client A".
  3. Click [Start Note] and verify the existence of the 'Session Information' window.
  4. Select "Service Code A" in the 'Service Code' field.
  5. Fill out all required fields and select the desired note type.
  6. Verify the existence of "Client A" in the client header when note is started.
  7. Fill out all required fields.
  8. Select "Add On 1", "Add On 2", and "Add On 3" in the 'Add-On Services' field.
  9. Enter the desired duration/comments for each add-on.
  10. Click [Sign Note].
  11. Validate the Sign Note' dialog is displayed.
  12. Enter the pin for "User A" in the 'Pin' field and click [Sign].
  13. Validate a message is displayed stating: Note Signed Successfully.
  14. Select "Client A" and access the 'Progress Notes' widget.
  15. Validate the note filed in the previous steps is displayed and contains all progress note data, including the 'Selected Add-On Services'.
  16. Access the 'Client Ledger' form.
  17. Select "Client A" in the 'Client ID' field.
  18. Select "All Episodes" in the 'Claim/Episode/All Episodes' field.
  19. Select "Simple" in the 'Ledger Type' field.
  20. Select "Yes" in the 'Include Zero Charges' field.
  21. Click [Process].
  22. Validate the 'Client Ledger' report contains "Service Code A", "Add On 1", "Add On 2" and "Add On 3".
  23. Close the report and the form.
Topics
• Progress Notes • Medical Note • Add-On • CareFabric • Bells Notes
Update 39 Summary | Details
Avatar CareFabric - Progress Notes
Scenario 1: Bells Notes Integration - validate 'Site Specific Section Modeling' in progress notes 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
  • 'Site Specific Section Modeling' fields that are imported to a corresponding note type in Bells (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' widget on the HomeView.
  • A client is enrolled in an existing episode (Client A).
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 "Note Type A".
  5. Verify the existence of "Client A" in the client header when note is started.
  6. Fill out all required fields including fields added via 'Site Specific Section Modeling'.
  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. Select "Client A" and navigate to the 'Progress Notes' widget.
  13. Validate the progress note filed from Bells Notes is displayed and contains the 'Site Specific Section Modeling' fields.
  14. Access the 'Clinical Document Viewer' form.
  15. Select "Client" in the 'Select Type' field.
  16. Select "Individual" in the 'Select All or Individual Client' field.
  17. Select "Client A" in the 'Select Client' field.
  18. Select "All" in the 'Episode' field.
  19. Click [Process].
  20. Validate a document is displayed for the progress note filed from Bells Notes.
  21. Select the document and click [View].
  22. Validate the PDF generated from Bells Notes is displayed and contains the progress note data filed including the 'Site Specific Section Modeling' fields.
  23. Click [Close All Documents], [Search], and [Close].
Scenario 2: Bells Notes Integration - validate 'Site Specific Section Modeling' in progress notes when document routing is disabled
Specific Setup:
  • myAvatar must be configured to integrate with Bells Notes. Please note: this must be done by a Netsmart Associate.
  • The 'Enable Multiple Add-On Code Per Primary Code Functionality' registry setting is enabled.
  • A primary service code is defined (Service Code A) with multiple add-on codes associated (Add On 1, Add On 2, Add On 3).
  • The 'Progress Notes (Group and Individual)' form must be configured for Bells Notes with the following:
  • Document routing disabled
  • 'Site Specific Section Modeling' fields that are imported to a corresponding note type in Bells (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 'Progress Notes' and 'My To Do's' widget on the HomeView.
  • A client is enrolled in an existing episode (Client A).
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 "Note Type A".
  5. Verify the existence of "Client A" in the client header when note is started.
  6. Fill out all required fields including fields added via 'Site Specific Section Modeling'.
  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. Validate a To-Do is not displayed for the progress note sent via Bells Notes for "Client A" since document routing is not enabled.
  14. Navigate to the 'My Clients' widget.
  15. Double click on "Client A" to access the Chart View.
  16. Select "Form A" from the left-hand side,
  17. Validate the progress note sent via Bells Notes is displayed and contains the progress note data filed including the 'Site Specific Section Modeling' fields.
  18. Click [Close Chart].
Avatar CareFabric - 'SearchCarePlan' SDK action
Scenario 1: Treatment Plan - validate the 'SearchCarePlan' SDK action
Steps
  • Internal testing only.
Topics
• Progress Notes • Bells Notes • Site Specific Section Modeling • CareFabric • Treatment Plan
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
  1. Search for and select "Client A" and access 'Medical Note'.
  2. Click [Add Note] and create a new "Primary Care" Note.
  3. In the Facesheet:
  4. Select the ‘Vitals’ section and enter Blood Pressure, Height, Weight, and Temperature information, click [Save], and pull to note.
  5. Select the ‘Immunization’ section and enter a “Historical Immunization” record for yesterday.
  6. Select the ‘Allergies’ section and enter an allergy to “Shellfish” and pull to note.
  7. Select the ‘Document’ tab.
  8. Complete the 'Chief Complaint', 'HPI', 'Physical Exam' and 'Diagnosis' sections as necessary.
  9. Select the ‘Immunizations’ section.
  10. Expand the ‘Immunization History’ section and validate the Historical Immunization Record for the precious day is correctly shown.
  11. Click [Add] and then [Order Immunizations], select "Immunization A" from the 'Immunization Search' field and click [Continue].
  12. Fill in any required fields and click [Order].
  13. Click [Add] and then [Order Immunizations], select "Immunization B" from the 'Immunization Search' field and click [Continue].
  14. Fill in any required fields and click [Administer].
  15. Validate "Immunization A" is listed under the 'Pending Administrations' section and " Immunization B" is listed under the 'Immunization History' section.
  16. Populate all required fields and click [Save].
  17. Select the ‘Procedures’ section and click [Add].
  18. Select "Procedure A" from the 'Procedure' field.
  19. Select "Complete" from the 'Status' field.
  20. Set the 'Completion Date' field to "Today's Date.
  21. Populate any remaining required fields and click [Save].
  22. Validate "Procedure A" is listed under the 'Current Procedures' Section.
  23. Select the ‘In Office Administrations’ section.
  24. Click [Add], select "Medication A" from the 'In-Office Administrations Search' field and click [Continue].
  25. Populate all required fields and click [Administer].
  26. Populate all required fields and click [Save].
  27. Click [Add], select "Medication A" from the 'In-Office Administrations Search' field and click [Continue].
  28. Populate all required fields and click [Order].
  29. Validate "Medication A" is listed under the 'Pending Administrations' section and " Medication A" is listed under the 'Administration History' section.
  30. Select the ‘Finalize’ tab.
  31. Populate all required fields and click [Generate Note].
  32. Validate the ‘Note Summary’ is displayed and contains the appropriate information:
  33. The populated sections of the 'Facesheet' tab that were pulled into the note. (Allergies and Vitals)
  34. The required and populated sections of the 'Document' tab. (Chief Complaint, HPI, Physical Exam, Diagnosis)
  35. The 'Immunizations' section shows "Immunization A" in the 'Ordered (Pending)' section and "Immunization B" in the 'Administered In-Office' section.
  36. The 'Procedures' section shows "Procedure A" as complete.
  37. The 'In-Office Administrations' section shows "Medication A" in the 'Ordered (Pending)' section and "Medication B" in the 'Administered In-Office' section.
  38. 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
  1. Search for and select "Client A" and navigate to the 'Medical Note'.
  2. Click [Add Note].
  3. Create a 'Psychiatry' note.
  4. Select the ‘Document’ tab.
  5. Populate all required sections in the 'Document' tab.
  6. Click the 'In-Office Administration' section.
  7. Click [Add] and select "Medication A" from the 'In-Office Administration Search' field.
  8. Validate the 'Dose', 'Unit', and 'Route' fields automatically populate based on the entries made in "Template A"
  9. Fill in any remaining required fields and click [Order].
  10. Validate the 'Pending Administrations' field contains a row for "Medication A".
  11. Click the ellipses under the 'Action' column for "Medication A" and click [Administer].
  12. Validate, in the first section, the 'Dose', 'Unit', and 'Route' fields are correctly populated with the updated values and that all fields are disabled.
  13. Click the 'Lot Number Search' button and validate the 'Lot Number Manager' dialog is launched.
  14. Select the row for "Inventory A" and click [Select].
  15. Validate the 'Lot Number', 'Manufacturer', 'Expiration Date', and 'NDC" are all correctly populated and disabled.
  16. Fill in any remaining required fields and click [Save].
  17. Expand the 'Administration History' field and validate it contains a row for "Medication A" and that all columns are accurate.
  18. Click the ellipses under the 'Action' column for "Medication A" and click [Document Reaction].
  19. Select any value for the 'Reaction' field and click [Save].
  20. Click the ellipses under the 'Action' column for "Medication A" and click [View Details].
  21. Validation the 'Reaction' field contains the correct value and click [Close]
  22. Select the ‘Finalize’ tab.
  23. Populate all required fields and click [Generate Note].
  24. Validate the ‘Note Summary’ is displayed and contains the appropriate information and click [Sign Off].
  25. 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
  1. Search for and select "Client A" and navigate to the 'Medical Note'.
  2. Click [Add Note] and create a new 'Primary Care' note.
  3. Select the 'Document' tab.
  4. Navigate to the 'Diagnosis' section.
  5. Add a new diagnosis for "Client A".
  6. Navigate to the 'In-Office Administrations' section.
  7. Click [Add] and select "Medication A" from the 'In-Office Administrations Search' field.
  8. Validate the new diagnosis is listed under the 'Diagnosis' dropdown and select it.
  9. Fill in any remaining required fields and click [Order].
  10. Validate the 'Pending Administrations' field contains a row for "Medication A"
  11. Click the ellipses under the 'Action' column for "Medication A" and click [Administer].
  12. Validate, in the first section, the 'Dose', 'Unit', and 'Route' fields are correctly populated and that all fields are disabled.
  13. Fill in all required fields and click [Save].
  14. Validate the 'Pending Administrations' field no longer contains a row for "Medication A".
  15. 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
  1. Search for and select "Client A" and navigate to the 'Medical Note'.
  2. Click [Add Note] and create a new note.
  3. Select the 'Document' tab and then navigate to the 'In-Office Administration' section.
  4. Click [Add], select "Medication A" from the 'In-Office Administration Search' field and click [Continue].
  5. Populate all required fields and click [Order].
  6. Validate the 'Pending Administrations' field contains a row for "Medication A".
  7. Click [Add], select "Medication B" from the 'In-Office Administration Search' field and click [Continue].
  8. Populate all required fields and click [Order].
  9. Validate the 'Pending Administrations' field contains a row for "Medication A" and one for "Medication B".
  10. Click the ellipses under the 'Action' column for "Medication A" and click [Administer].
  11. Populate all required fields and click [Save].
  12. Expand the 'Administration History' field and validate it contains a row for "Medication A" and that all columns are accurate.
  13. Click the ellipses under the 'Action' column for "Medication B" and click [Refuse].
  14. Set the 'Refusal Reason' field to any value and click [Save].
  15. Validate the 'Administration History' field contains a row for "Medication A" and the status shows as "Administered".
  16. Validate the 'Administration History' field contains a row for "Medication B" and the status shows as "Refused".
  17. Click the ellipses under the 'Action' column for "Medication B" and click [Void].
  18. Set the 'Comments' field to any value and click [Save].
  19. 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
  1. Search for and select "Client A" and navigate to the 'Medical Note'.
  2. Click [Add Note] and create a new note.
  3. Select the 'Document' tab and then navigate to the 'In-Office Administrations' section.
  4. Click [Add] and select "Medication A" from the 'In-Office Administrations Search' field.
  5. Validate the 'Dose', 'Unit', and 'Route' fields automatically populate based on the entries made in "Template A".
  6. Fill in any remaining required fields and click [Order].
  7. Validate the 'Pending Administrations' field contains a row for "Medication A".
  8. Click the ellipses under the 'Action' column for "Medication A" and click [Edit].
  9. Set the 'Dose' and 'Unit' fields to any other values and click [Update].
  10. Validate the row for "Medication A" in the 'Pending Administrations field reflects the updated values.
  11. Click the ellipses under the 'Action' column for "Medication A" and click [Administer].
  12. Validate, in the first section, the 'Dose', 'Unit', and 'Route' fields are correctly populated with the updated values and that all fields are disabled.
  13. Click the 'Lot Number Search' button and validate the 'Lot Number Manager' dialog is launched.
  14. Select the row for "Inventory A" and click [Select].
  15. Validate the 'Lot Number', 'Manufacturer', 'Expiration Date', and 'NDC" are all correctly populated and disabled.
  16. Fill in any remaining required fields and click [Save].
  17. Validate the 'Pending Administrations' field no longer contains a row for "Medication A".
  18. 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
  1. Log into the application as "User A".
  2. Search for and select "Client A" and navigate to 'Medical Note'.
  3. Click [Add Note] and create a new note.
  4. Select the 'Document' tab and then navigate to the 'In-Office Administrations' section.
  5. Click [Add], search for and select "Medication A" from the 'In-Office Administrations Search' field, and click [Continue].
  6. Validate the 'Dose', 'Unit', and 'Route' fields automatically populate based on the entries made in "Template A".
  7. Populate any remaining required fields and click [Order].
  8. Validate the 'Pending Administrations' field contains a row for "Medication A" and click [Save Draft].
  9. Log out of the application and then log in as "User B".
  10. Search for and select "Client A" and navigate to the 'Medical Note'.
  11. Click [Select Note] and select the newly created note.
  12. Select the 'Document' tab and then navigate to the 'In-Office Administrations' section.
  13. Validate the 'Pending Administrations' field contains a row for "Medication A".
  14. Click the ellipses under the 'Action' column for "Medication A" and click [Administer].
  15. Validate, in the first section, the 'Dose', 'Unit', and 'Route' fields are correctly populated and that all fields are disabled.
  16. Validate the 'Entered By' and 'Ordered By' fields contain "User A" and the 'Administered By' field contains "User B".
  17. Click the 'Lot Number Search' button and validate the 'Lot Number Manager' dialog is launched.
  18. Select the row for "Inventory A" and click [Select].
  19. Validate the 'Lot Number', 'Manufacturer', 'Expiration Date', and 'NDC" are all correctly populated and disabled.
  20. Populate all remaining required fields and click [Save].
  21. Validate the 'Pending Administrations' field no longer contains a row for "Medication A".
  22. Expand the 'Administration History' field and validate it contains a row for "Medication A" and that all columns are accurate.
  23. Log out of the application and then log in as "User A".
  24. Search for and select "Client A" and navigate to the 'Medical Note'.
  25. Click [Select Note] and select the newly created note.
  26. Select the 'Document' tab and then navigate to the 'In-Office Administrations' section.
  27. Validate the 'Pending Administrations' field no longer contains a row for "Medication A".
  28. 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
  1. Search for and select "Client A" and navigate to the 'Medical Note'.
  2. Click [Add Note] and create a new 'Primary Care' note.
  3. Select the 'Document' tab and then navigate to the 'Immunizations' section.
  4. Click [Add] and then [Order Immunizations], select "Immunization A" from the 'Immunization Search' field and click [Continue].
  5. Fill in any required fields and click [Order].
  6. Click [Add] and then [Order Immunizations], select "Immunization B" from the 'Immunization Search' field and click [Continue].
  7. Fill in any required fields and click [Order].
  8. Click the ellipses under the 'Action' column for "Immunization A" and click [Edit].
  9. Change the values for the 'Dose' and 'Route' fields and click [Update].
  10. Click the ellipses under the 'Action' column for "Immunization B" and click [Cancel].
  11. 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."
  12. Click [Continue], populate the 'Comments' field and click [Save].
  13. Validate the 'Pending Immunizations' section only contains a row for "Immunization A".
  14. Click the ellipses under the 'Action' column for "Immunization A" and click [Administer].
  15. 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.
  16. Select "Facility" from the 'Provided By' field.
  17. Click the 'Lot Number Search' button and validate the 'Lot Number Manager' dialog is launched.
  18. Select the row for "Inventory A" and click [Select].
  19. Validate all fields in the "Administration Details' section are populated correctly.
  20. Populate any remaining required fields and click [Save].
  21. Expand the 'Immunization History' field and validate it contains a row for "Immunization A" and all columns are correctly populated.
  22. Click [Add] and then [Order Immunizations], select "Immunization A" from the 'Immunization Search' field and click [Continue].
  23. Populate any required fields and click [Administer].
  24. Set the 'Provided By' field to "Facility".
  25. Click the 'Lot Number Search' button and validate the 'Lot Number Manager' dialog is launched.
  26. Select the row for "Inventory A" and click [Select].
  27. Validate all fields in the "Administration Details' section are populated correctly.
  28. Populate any remaining required fields and click [Save].
  29. Click [Group By Vaccine] in the 'Immunization History' section.
  30. 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
  1. Search for and select "Client A" and navigate to the 'Medical Note'.
  2. Click [Add Note] and create a new 'Primary Care' note.
  3. Select the 'Document' tab and then navigate to the 'Immunizations' section.
  4. Click [Add], select "Immunization A" from the 'Immunization Search' field and click [Continue].
  5. Validate the 'Dose', 'Unit', and 'Route' fields automatically populate based on the entries made in "Template A".
  6. Fill in any remaining required fields and click [Administer].
  7. Select "Facility" from the 'Provided By' field.
  8. Click the 'Lot Number Search' button and validate the 'Lot Number Manager' dialog is launched.
  9. Select the row for "Inventory A" and click [Select].
  10. Validate the fields in the 'Administration Details' section are all accurately populated.
  11. Fill in any remaining required fields and click [Save].
  12. Validate the 'Pending Administrations' field does not contain a row for "Immunization A".
  13. Expand the 'Immunization History' field and validate it contains a row for "Immunization A" and that all columns are accurate.
  14. Click the ellipses under the 'Action' column for "Immunization A" and click [Void].
  15. Populate the 'Comments' field and click [Save].
  16. Validate the 'Immunization History' field still contains a row for "Immunization A" and that the 'Status' column shows "Voided".
  17. Access the 'Medication Inventory Management' form.
  18. Click [Adjust Inventory] and select the row for "Inventory A" from the 'Select Row' field.
  19. Validate that the 'Event Log' field contains a row for the previously given administration.
  20. Validate the 'Current Balance' is correctly calculated.
  21. Select 'Add to inventory' from the 'Event Type' field.
  22. Set the 'Quantity' field, such that when added to the current balance, the total is equal to the amount originally added to inventory.
  23. 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
  1. Search for and select "Client A" and navigate to the 'Medical Note'.
  2. Click [Add Note].
  3. Create a 'Primary Care' note.
  4. Select the ‘Document’ tab.
  5. Select ‘Immunizations’.
  6. Click [Add] and select "Medication A" from the 'Immunization Search' field.
  7. Validate the 'Dose', 'Unit', and 'Route' fields automatically populate based on the entries made in "Template A".
  8. Fill in any remaining required fields and click [Order].
  9. Validate the 'Pending Administrations' field contains a row for "Medication A"
  10. Click [Add] and select "Medication B" from the 'Immunization Search' field.
  11. Validate the 'Dose', 'Unit', and 'Route' fields automatically populate based on the entries made in "Template B".
  12. Fill in any remaining required fields and click [Administer].
  13. Validate, in the first section, the 'Dose', 'Unit', and 'Route' fields are correctly populated with the updated values and that all fields are disabled.
  14. Select "Yes" for the 'Consent Obtained' radio button.
  15. Select "Not VFC eligible" from the 'VFC Eligibility Code' field.
  16. Select "Facility" from the 'Provided By' field.
  17. Click the 'Lot Number Search' button and validate the 'Lot Number Manager' dialog is launched.
  18. Select the row for "Inventory B" and click [Select].
  19. Validate the 'Lot Number', 'Manufacturer', 'Expiration Date', and 'NDC' are all correctly populated and disabled.
  20. Fill in any remaining required fields and click [Save].
  21. Expand the 'Immunization History' field and validate it contains a row for "Medication B" and that all columns are accurate.
  22. Populate any remaining required sections in the 'Document' tab.
  23. Select the ‘Finalize’ tab.
  24. Populate all required fields and click [Generate Note].
  25. Validate the ‘Note Summary’ is displayed and contains the appropriate information and click [Sign Off].
  26. Validate the 'Progress Note' is displayed and click [Accept], set the ‘Password’ field to the appropriate value, and click [Verify].
  27. Refresh Medical Note.
  28. Click [Add Note].
  29. Create a 'Primary Care' note.
  30. Select the 'Document' tab and navigate to the 'Immunization' section.
  31. Validate the 'Pending Administrations' field contains a row for "Medication A"
  32. Click the ellipses under the 'Action' column for "Medication A" and click [Administer].
  33. Validate, in the first section, the 'Dose', 'Unit', and 'Route' fields are correctly populated with the updated values and that all fields are disabled.
  34. Select "Yes" for the 'Consent Obtained' field.
  35. Select "Not VFC eligible" from the 'VFC Eligibility Code' field.
  36. Select "Facility" from the 'Provided By' field.
  37. Click the 'Lot Number Search' button and validate the 'Lot Number Manager' dialog is launched.
  38. Select the row for "Inventory A" and click [Select].
  39. Validate the 'Lot Number', 'Manufacturer', 'Expiration Date', and 'NDC' are all correctly populated and disabled.
  40. Populate all remaining required fields and click [Save].
  41. 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
  1. Search for and select "Client A" and navigate to the 'Medical Note'.
  2. Click [Add Note] and create a new 'Primary Care' note.
  3. Select the 'Document' tab and then navigate to the 'Immunizations' section.
  4. Click [Add] and then [Order Immunizations], select "Immunization A" from the 'Immunization Search' field and click [Continue].
  5. Fill in any required fields and click [Administer].
  6. Select "Facility" from the 'Provided By' field.
  7. Fill in any remaining required fields and click [Save].
  8. Expand the 'Immunization History' field and validate it contains a row for "Immunization A" and all columns are correctly populated.
  9. Complete any remaining required sections in the 'Document' tab.
  10. Select the 'Finalize' tab and click [End Face-to-Face Time].
  11. Choose one of the options in the 'CPT Code Selected' field and click [Generate Note].
  12. Validate the 'Note Summary' field shows the correct information.
  13. 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
  1. Access the 'Service Code Upload Process' form.
  2. Click [Select File].
  3. Select and open "File A".
  4. Select "Compile" in the 'Compile or Post' field.
  5. Select "Yes" in the 'Override Existing Service Codes' field.
  6. Click [Submit].
  7. Validate a "Compiled completed" message is displayed and click [OK].
  8. Select "Post" in the 'Compile or Post' field and click [Submit].
  9. Validate a "Post completed" message is displayed and click [OK].
  10. Access the 'Service Codes' form.
  11. Select "Edit" in the 'Add New or Edit Existing' field.
  12. 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.
  13. 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
  1. Access the 'Medication Inventory Management' form.
  2. Click [Template Definition] and select "Add New" from the 'Select Template Definition' field.
  3. Set the 'Service Code' field to "Medication A".
  4. Populate any remaining required fields and click [Submit].
  5. Click [Medication Definition] and select the previously made template from the 'Select Template' field.
  6. Select "Location A" from the 'Inventory Location' field.
  7. Set the 'Lot #' field to "72293".
  8. Set the 'Expiration Date' field to a future date.
  9. Set the 'Container Size' field to 50.
  10. Populate any remaining required fields and click [Submit].
  11. Click [Adjust Inventory] and set the 'Lot #' field to "72293"
  12. Validate the new medication definition is shown in the 'Inventory Items' field.
  13. Select the new medication definition from the 'Select Row' field.
  14. Select "Add to inventory" from the 'Event Type' field.
  15. Validate "Add (A)" is selected from the 'Impact' field and that the field is disabled.
  16. Set the 'Quantity' field to "50" and click [Submit] and close the form.
  17. Search for and select "Client A" and navigate to the 'Medical Note'.
  18. Click [Add Note] and create a new note.
  19. Select the 'Document' tab and then navigate to the 'In-Office Administrations' section.
  20. Click [Add], search for and select "Medication A" from the 'In-Office Administrations Search' field and click [Continue].
  21. Validate the 'Dose', 'Unit', and 'Route' fields automatically populate based on selections made in the "Template Definition" section of the 'Medication Inventory Management' form.
  22. Fill in any remaining required fields and click [Administer].
  23. Click the 'Lot Number Search' button and validate the 'Lot Number Manager' dialog is launched.
  24. Select the row for new medication definition and click [Select].
  25. Validate the 'Administration Details' section is correctly populated based on selections made in the "Medication Definition" section of the 'Medication Inventory Management' form.
  26. Populate any remaining required fields and click [Save].
  27. Expand the 'Administration History' field and validate it contains a row for "Medication A" and that all columns are accurate.
  28. Click the ellipses under the 'Action' column for "Medication A" and click [Document Reaction].
  29. Set the 'Reaction' field to any value and click [Save].
  30. Click the ellipses under the 'Action' column for "Medication A" and click [View Details].
  31. Validate the details are read-only, that all fields are correctly populated and then click [Cancel].
  32. Access the 'Medication Inventory Management' form.
  33. Click [Adjust Inventory] and select the new medication definition from the 'Select Row' field.
  34. Validate that the 'Event Log' field contains a row for the previously given administration.
  35. 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
  1. Search for and select "Client A" and navigate to the 'Medical Note'.
  2. Click [Add Note] and create a new note.
  3. Select the 'Document' tab and then navigate to the 'In-Office Administrations' section.
  4. Click [Add], select "Medication A" from the 'In-Office Administrations Search' field and click [Continue].
  5. Populate any required fields and click [Order].
  6. Validate the 'Pending Administrations' field contains a row for "Medication A".
  7. Click the ellipses under the 'Action' column for "Medication A" and click [Refuse].
  8. Select any value from the 'Refused Reason' field and click [Save].
  9. Validate the 'Pending Administrations' field no longer contains a row for "Medication A".
  10. Expand the 'Administration History' field and validate it contains a row for "Medication A" and that "Refused" is shown in the 'Status' column.
  11. Click the ellipses under the 'Action' column for "Medication A" and click [View Details].
  12. Validate the 'Refused Reason' field matches to what was previously selected and click [Cancel].
  13. Select the 'Finalize' tab and click [Generate Note].
  14. 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
  1. Search for and select "Client A" and navigate to the 'Medical Note'.
  2. Click [Add Note] and create a new note.
  3. Select the 'Document' tab and then navigate to the 'In-Office Administration' section.
  4. Click [Add], search for and select "Medication A" from the 'In-Office Administration Search' field and click [Continue].
  5. Populate any required fields and click [Order].
  6. Validate that a row for "Medication A" is listed in the 'Pending Immunizations' section.
  7. Click the ellipses under the 'Action' column for "Medication A" and click [Cancel].
  8. 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].
  9. Populate the 'Comments' field and click [Save].
  10. Validate the 'Pending Administrations' field no longer contains a row for "Medication A".
  11. Expand the 'Administration History' field and validate it does not contain a row for "Medication A".
  12. Click [Select Note] and then click [Delete] for the newly created note.
  13. 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."
  14. 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
  1. Search for and select "Client A" and navigate to the 'Medical Note'.
  2. Click [Add Note] and create a new note.
  3. Select the 'Document' tab and then navigate to the 'In-Office Administrations' section.
  4. Click [Add], search for and select "Medication A" from the 'In-Office Administrations Search' field and click [Continue].
  5. Validate the 'Dose', 'Unit', and 'Route' fields automatically populate based on the entries made in "Template A".
  6. Fill in any remaining required fields and click [Administer].
  7. Click the 'Lot Number Search' button and validate the 'Lot Number Manager' dialog is launched.
  8. Select the row for "Inventory A" and click [Select].
  9. Populate any remaining required fields and click [Save].
  10. Expand the 'Administration History' field and validate it contains a row for "Medication A" and that all columns are accurate.
  11. Click [Select Note] and then click [Delete] for the newly created note.
  12. 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.".
  13. 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.".
  14. Select the 'Document' tab and then navigate to the 'In-Office Administrations' section.
  15. Expand the 'Administration History' field, click the ellipses under the 'Action' column for "Medication A" and click [Void].
  16. Populate the 'Comments' field and click [Save].
  17. 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."
  18. Validate the 'Status' column shows "Voided" for "Medication A".
  19. Click [Select Note] and then click [Delete] for the newly created note.
  20. 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].
  21. Access the 'Medication Inventory Management' form.
  22. Click [Adjust Inventory] and select the row for "Inventory A" from the 'Select Row' field.
  23. Validate that the 'Event Log' field contains a row for the previously given administration.
  24. Validate the 'Current Balance' is correctly calculated.
  25. Select 'Add to inventory' from the 'Event Type' field.
  26. 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
  1. Search for and select "Client A" and navigate to the 'Medical Note'.
  2. Navigate to the 'Immunizations' section of the Facesheet.
  3. Click [Add] and then [Historical Immunization Record].
  4. Select any immunization listed in the 'Historical Immunization Record Search' field.
  5. Fill out any required fields and click [Save].
  6. Validate the 'Immunization History' section contains a row for the new historical immunization record.
  7. Click [Add Note] and create a 'Primary Care' note.
  8. Select the 'Document' tab and then navigate to the 'Immunization' section.
  9. Click [Add] and then [Order Immunizations], select "Immunization A" from the 'Immunizations Search' field and click [Continue].
  10. Validate the 'Dose', 'Unit', and 'Route' fields automatically populate based on the entries made in "Template A".
  11. Fill in any remaining required fields and click [Order].
  12. Validate the 'Pending Immunizations' field contains a row for "Immunization A"
  13. Click the ellipses under the 'Action' column for "Immunization A" and click [Edit].
  14. Clear the 'Diagnosis' field, enter in a new value and click [Update].
  15. Click the ellipses under the 'Action' column for "Immunization A" and click [Administer].
  16. Validate the 'Diagnosis' field contains the updated value.
  17. Validate the following fields, restricted to pediatric clients only, show and are required:
  18. 'Consent Obtained'.
  19. 'VFC Eligibility Code'.
  20. 'Funding Source'.
  21. Click the 'Lot Number Search' button and validate the 'Lot Number Manager' dialog is launched.
  22. Select the row for "Inventory A" and click [Select].
  23. Fill in any remaining required fields and click [Save].
  24. Validate the 'Pending Immunizations' field no longer contains a row for "Immunization A".
  25. Expand the 'Immunization History' field and validate it contains a row for "Immunization A" and that all columns are accurate.
  26. Click the ellipses under the 'Action' column for "Immunization A" and click [Document Reaction].
  27. Populate the 'Reaction' field and click [Save].
  28. Click the ellipses under the 'Action' column for "Immunization A" and click [View Details].
  29. Validate all fields are correctly populated and disabled and click [Cancel].
  30. Click [Add] and then [Order Immunizations], select "Immunization B" from the 'Immunizations Search' field and click [Continue].
  31. Populate all required fields and click [Order].
  32. Select the 'Finalize' tab and click [Generate Note].
  33. Validate the 'Note Summary' field contains a section for pending immunizations and has "Immunization B" listed.
  34. Validate the 'Note Summary' field contains a section for administered in-office immunizations and has "Immunization A" listed.
  35. Validate the 'Note Summary' field does not contain the new Historical Immunization Record.
  36. Select the 'Document' tab and then navigate to the 'Immunization' section.
  37. Click the ellipses under the 'Action' column for "Immunization B" and click [Cancel].
  38. 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."
  39. Click [Continue], populate the 'Comments' field and click [Save].
  40. Select the 'Finalize' tab and click [Generate Note].
  41. 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
  1. Search for and select "Client A" and navigate to the 'Medical Note'.
  2. Click [Add Note].
  3. Create a 'Primary Care' note.
  4. Select the 'Document' tab and then navigate to the 'Immunization' section.
  5. Populate all required fields and click [Order].
  6. Validate the 'Pending Administrations' field contains a row for "Medication A".
  7. Click the ellipses under the 'Action' column for "Medication A" and click [Administer].
  8. Select "Yes" for the 'Consent Obtained' radio button.
  9. Select "Not VFC eligible" from the 'VFC Eligibility Code' field.
  10. Select "Other" from the 'Provided By' field.
  11. Populate all required fields and click [Save].
  12. Expand the 'Immunization History' field and validate it contains a row for "Medication A" and that all columns are accurate.
  13. Click the ellipses under the 'Action' column for "Medication B" and click [Document Reaction].
  14. Select any value for the 'Reaction' field and click [Save].
  15. Click the ellipses under the 'Action' column for "Medication B" and click [View Details].
  16. 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
  1. Search for and select "Client A" and navigate to the 'Medical Note'.
  2. Navigate to the 'Immunizations' section of the Facesheet.
  3. Click [Add] and then [Historical Immunization Record].
  4. Select any immunization listed in the 'Historical Immunization Record Search' field.
  5. Fill out any required fields and click [Save].
  6. Validate the 'Immunization History' section contains a row for the new historical immunization record.
  7. Access the 'Client Health Maintenance' form.
  8. Search for and select "Client A" from the 'Client ID' field.
  9. Click [List Immunizations] and validate the 'Immunizations History and Alerts' report is launched.
  10. Validate the 'Immunization History' section contains data for the new historical immunization record and click [Close Report].
  11. Click [Update] and then [New Row].
  12. Populate the 'Vaccine', 'Dose', 'Provided By' and 'Date' cells and click [Save].
  13. Navigate to the 'Medical Note'.
  14. Navigate to the 'Immunizations' section of the Facesheet.
  15. 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
  1. Search for and select "Client A" and navigate to the 'Medical Note'.
  2. Click [Add Note].
  3. Create a 'Psychiatry' note.
  4. Select the 'Document' tab and then navigate to the 'Procedure' section.
  5. Click [Add] and select "Medication A" from the 'Procedure Search' field.
  6. Select ‘Diagnosis’ and enter a diagnosis.
  7. Click 'Complete' field.
  8. Click 'Routine' field.
  9. Populate all remaining required fields and click [Save].
  10. Validate the 'Current Procedures' field contains a row for "Medication A".
  11. Access the 'Service Codes' form.
  12. Select "Edit" in the 'Add New or Edit Existing' field.
  13. Search for and select "Medication A" and select "Medication Administration" in the 'Procedure Type' field.
  14. Click [Submit].
  15. Validate a message is displayed stating "Service Codes has completed. Do you wish to return to form?" and click [Yes].
  16. Refresh 'Medical Note'.
  17. Click [Select Note] and click [Edit].
  18. Select the 'Document' tab and then navigate to the 'In-Office Administration' section.
  19. Expand the 'Administration History' field.
  20. 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
  1. Search for and select "Client A" and navigate to the 'Medical Note'.
  2. Click [Add Note] and create a new note.
  3. Select the 'Document' tab and then navigate to the 'In-Office Administration' section.
  4. Click [Add] and select "Medication A" from the 'In-Office Administration Search' field.
  5. Populate any required fields and click [Order].
  6. Validate the 'Pending Administrations' field contains a row for "Medication A".
  7. Click [Add] and select "Medication B" from the 'In-Office Administration Search' field.
  8. Populate any required fields and click [Order].
  9. Validate the 'Pending Administrations' field contains a row for "Medication B".
  10. Click [Send To Do].
  11. Set "User B" in the 'To-Do Recipient'.
  12. Set the 'Notes' field to any value and click [Send].
  13. Log out of the application and log back in as "User B".
  14. Access the 'My To Do's' widget.
  15. Select "Client A" from the 'Additional ToDos' list and click [Review To Do Item].
  16. Click 'In-Office Administrations'.
  17. Validate the 'Pending Administrations' field contains a row for "Medication A".
  18. Click the ellipses under the 'Action' column for "Medication A" and click [Administer].
  19. Validate, in the first section, the 'Dose', 'Unit', and 'Route' fields are correctly populated and disabled.
  20. Populate any required fields and click [Save].
  21. Expand the 'Administration History' field and validate it contains a row for "Medication A" and that all columns are accurate.
  22. Click the ellipses under the 'Action' column for "Medication B" and click [Refuse].
  23. Select any value in the 'Refused Reason' field and click [Save].
  24. 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
  1. Search for and select "Client A" and navigate to the 'Medical Note'.
  2. Click [Add Note] and create a 'Primary Care' note.
  3. Select the ‘Document’ tab.
  4. Enter a value in the ‘Chief Complaint’ field.
  5. Select ‘HPI’ and add a value along with symptoms.
  6. Select ‘Physical Exam’ and select the ‘Constitutional’ tab.
  7. Check off the appropriate values.
  8. Select ‘Diagnosis’ and enter a diagnosis.
  9. Select ‘Immunizations’.
  10. Click [Add] and select "Medication A" from the 'Immunization Search' field.
  11. Validate the 'Dose', 'Unit', and 'Route' fields automatically populate based on the entries made in "Template A".
  12. Fill in any remaining required fields and click [Order].
  13. Validate the 'Pending Administrations' field contains a row for "Medication A"
  14. Click [Add] and select "Medication B" from the 'Immunization Search' field.
  15. Validate the 'Dose', 'Unit', and 'Route' fields automatically populate based on the entries made in "Template B".
  16. Fill in any remaining required fields and click [Administer].
  17. Validate, in the first section, the 'Dose', 'Unit', and 'Route' fields are correctly populated with the updated values and that all fields are disabled.
  18. Click the 'Lot Number Search' button and validate the 'Lot Number Manager' dialog is launched.
  19. Select the row for "Inventory B" and click [Select].
  20. Validate the 'Lot Number', 'Manufacturer', 'Expiration Date', and 'NDC' are all correctly populated and disabled.
  21. Fill in any remaining required fields and click [Save].
  22. Expand the 'Immunization History' field and validate it contains a row for "Medication B" and that all columns are accurate.
  23. Click the ellipses under the 'Action' column for "Medication B" and click [Document Reaction].
  24. Select any value for the 'Reaction' field and click [Save].
  25. Click the ellipses under the 'Action' column for "Medication B" and click [View Details].
  26. Validate the 'Reaction' field contains the correct value and click [Close].
  27. Select the ‘Finalize’ tab.
  28. Populate all required fields and click [Generate Note].
  29. Validate the ‘Note Summary’ is displayed and contains the appropriate information and click [Sign Off].
  30. Validate the Document is displayed and click [Accept], set the ‘Password’ field to the appropriate value and click [Verify].
  31. Refresh Medical Note.
  32. Click [Add Note].
  33. Select "Primary Care" from the 'Appointment/Note Workflow' field.
  34. Select "Main Street Center" from the 'Site' field.
  35. Select "Program A" from the 'Service Program' field.
  36. Search for and select "Service Code A" from the 'Service Code' field.
  37. Fill out any remaining required fields and click [Save].
  38. Select the 'Document' tab and then navigate to the 'Immunization' section.
  39. Validate the 'Pending Administrations' field contains a row for "Medication A"
  40. Click the ellipses under the 'Action' column for "Medication A" and click [Administer].
  41. Validate, in the first section, the 'Dose', 'Unit', and 'Route' fields are correctly populated with the updated values and that all fields are disabled.
  42. Click the 'Lot Number Search' button and validate the 'Lot Number Manager' dialog is launched.
  43. Select the row for "Inventory A" and click [Select].
  44. Validate the 'Lot Number', 'Manufacturer', 'Expiration Date', and 'NDC' are all correctly populated and disabled.
  45. Fill in any remaining required fields and click [Save].
  46. Expand the 'Immunization History' field and validate it contains a row for "Medication A" and that all columns are accurate.
  47. Select the 'Facesheet' tab and then navigate to the 'Immunization' section.
  48. Validate "Medication A" and "Medication B" are displayed.
  49. Select the 'Document' tab and then navigate to the 'Immunization' section.
  50. Void the administrations of "Medication A" and "Medication B".
  51. Refresh Medical Note.
  52. Click [Select Note] and click [Delete].
  53. 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."
  54. 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
  1. Log into the application as "User A".
  2. Search for and select "Client A" and navigate to the 'Medical Note'.
  3. Click [Add Note] and create a 'Primary Care' note.
  4. Select the 'Document' tab and then navigate to the 'Immunization' section.
  5. Click [Add] and then [Order Immunizations], select "Immunization A" from the 'Immunizations Search' field and click [Continue].
  6. Validate the 'Dose', 'Unit', and 'Route' fields automatically populate based on the entries made in "Template A".
  7. Fill in any remaining required fields and click [Order].
  8. Validate the 'Pending Immunizations' field contains a row for "Immunization A" and click [Save Draft].
  9. Log out of the application and then log in as "User B".
  10. Search for and select "Client A" and navigate to the 'Medical Note'.
  11. Click [Select Note] and select the newly created 'Primary Care' note.
  12. Select the 'Document' tab and then navigate to the 'Immunizations' section.
  13. Validate the 'Pending Immunizations' field contains a row for "Immunization A".
  14. Click the ellipses under the 'Action' column for "Immunization A" and click [Administer].
  15. Validate, in the first section, the 'Dose', 'Unit', and 'Route' fields are correctly populated and that all fields are disabled.
  16. Validate the 'Entered By' and 'Ordered By' fields contains "User A" and the 'Administered By' field contains "User B".
  17. Select "Facility" from the 'Provided By' field.
  18. Click the 'Lot Number Search' button and validate the 'Lot Number Manager' dialog is launched.
  19. Select the row for "Inventory A" and click [Select].
  20. Validate all fields in the 'Administration Details' section are populated correctly.
  21. Fill in any remaining required fields and click [Save].
  22. Validate the 'Pending Immunizations' field no longer contains a row for "Immunization A".
  23. Expand the 'Immunization History' field and validate it contains a row for "Immunization A" and that all columns are accurate.
  24. Log out of the application and then log in as "User A".
  25. Search for and select "Client A" and navigate to the 'Medical Note'.
  26. Click [Select Note] and select the 'Primary Care' note.
  27. Select the 'Document' tab and then navigate to the 'Immunizations' section.
  28. Validate the 'Pending Immunizations' field no longer contains a row for "Immunization A".
  29. 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
  1. Search for and select "Client A" and navigate to the 'Medical Note'.
  2. Click [Add Note].
  3. Create a 'Primary Care' note.
  4. Select the 'Document' tab and then navigate to the 'Immunization' section.
  5. Click [Add] and select "Medication A" from the 'Immunization Search' field.
  6. Populate all required fields and click [Order].
  7. Validate the 'Pending Administrations' field contains a row for "Medication A".
  8. Click [Add] and select "Medication B" from the 'Immunization Search' field.
  9. Populate all required fields and click [Order].
  10. Validate the 'Pending Administrations' field contains a row for "Medication B".
  11. Click [Send To Do].
  12. Set "User A" in the 'To-Do Recipient'.
  13. Set the 'Notes' field to any value and click [Send].
  14. Log out of the application and log back in as "User B".
  15. Access the 'My To Do's' widget.
  16. Select "Client A" from the 'Additional ToDos' list and click [Review To Do Item].
  17. Select the 'Immunization' section.
  18. Validate the 'Pending Administrations' field contains a row for "Medication A".
  19. Click the ellipses under the 'Action' column for "Medication A" and click [Administer].
  20. Validate, in the first section, the 'Dose', 'Unit', and 'Route' fields are correctly populated with the updated values and that all fields are disabled.
  21. Select "Yes" for the 'Consent Obtained' radio button.
  22. Select "Not VFC eligible" from the 'VFC Eligibility Code' field.
  23. Select "Facility" from the 'Provided BY' field.
  24. Populate all required fields and click [Save].
  25. Expand the 'Immunization History' field and validate it contains a row for "Medication A" and that all columns are accurate.
  26. Click the ellipses under the 'Action' column for "Medication B" and click [Refuse].
  27. Select any value for the 'Refused Reason' field and click [Save].
  28. 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
  • 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
  1. Select "Client A" and access the 'Update Client Data' form.
  2. Enter the desired value in the 'Facility Chart Number' field.
  3. Click [Submit].
  4. Access the 'CareFabric Monitor' form.
  5. Enter the current date in the 'From Date' and 'Through Date' fields.
  6. Select "Client A" in the 'Client ID' field.
  7. Click [View Activity Log].
  8. 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.
  9. Click [Click To View Record].
  10. Validate the second 'fhirIdentifiers' - 'id' - 'value' field contains the 'Facility Chart Number' filed in the previous steps.
  11. Validate the second 'fhirIdentifiers' - 'type' - 'codings' - 'code' field contains "MR".
  12. Validate the second 'fhirIdentifiers' - 'text' - 'value' field contains "PATIENT_REGISTRATION_ID".
  13. Close the report and the form.
Scenario 2: Admission - Validate the 'EncounterResourceCreated' SDK event
Steps
  1. Access the 'Admission' form.
  2. Add an admission for a new client. This will be referred to as "Client A".
  3. Enter the desired date in the 'Preadmit/Admission Date' field.
  4. Enter the desired time in the 'Preadmit/Admission Time' field.
  5. Select the desired value in the 'Program' field.
  6. Select the desired practitioner in the 'Admitting Practitioner' field.
  7. Populate all other required and desired fields.
  8. Click [Submit].
  9. Access the 'CareFabric Monitor' form.
  10. Enter the current date in the 'From Date' and 'Through Date' fields.
  11. Select "Client A" in the 'Client ID' field.
  12. Click [View Activity Log].
  13. 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.
  14. Validate the 'fhirIdentifiers' - 'id' - 'value' field contains the PATID for "Client A".
  15. Validate the 'period' - 'fromDate' field contains the 'Preadmit/Admission Date' and 'Preadmit/Admission Time' filed in the previous steps.
  16. Validate the first 'statusCode' - 'code' field contains "active".
  17. Validate the 'participants' - 'individualPractitionerResourceID' - 'id' field contains the ID for the 'Admitting Practitioner' filed in the previous steps.
  18. Validate the 'participants' - 'typeCodes' - 'codes' - 'code' field contains "ADMPHYS".
  19. Validate the 'participants' - 'typeCodes' - 'displayName' field contains "Admitting Physician".
  20. Validate the second 'statusCode' - 'code' field contains "planned".
  21. Close the report and the form.
Scenario 3: Admission (Outpatient) - Validate the 'EncounterResourceCreated' SDK event
Steps
  1. Access the 'Admission (OutPatient)' form.
  2. Add an admission for a new client. This will be referred to as "Client A".
  3. Enter the desired date in the 'Preadmit/Admission Date' field.
  4. Enter the desired time in the 'Preadmit/Admission Time' field.
  5. Select the desired value in the 'Program' field.
  6. Select the desired practitioner in the 'Admitting Practitioner' field.
  7. Populate all other required and desired fields.
  8. Click [Submit].
  9. Access the 'CareFabric Monitor' form.
  10. Enter the current date in the 'From Date' and 'Through Date' fields.
  11. Select "Client A" in the 'Client ID' field.
  12. Click [View Activity Log].
  13. 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.
  14. Validate the 'fhirIdentifiers' - 'id' - 'value' field contains the PATID for "Client A".
  15. Validate the 'period' - 'fromDate' field contains the 'Preadmit/Admission Date' and 'Preadmit/Admission Time' filed in the previous steps.
  16. Validate the 'statusCode' - 'code' field contains "active".
  17. Validate the 'participants' - 'individualPractitionerResourceID' - 'id' field contains the ID for the 'Admitting Practitioner' filed in the previous steps.
  18. Validate the 'participants' - 'typeCodes' - 'codes' - 'code' field contains "ADMPHYS".
  19. Validate the 'participants' - 'typeCodes' - 'displayName' field contains "Admitting Physician".
  20. Validate the 'statusCode' - 'code' field contains "planned".
  21. 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
  1. Select "Client A" and access the 'Back Dated Admission/Discharge' form.
  2. Enter the desired date in the 'Preadmit/Admission Date' field.
  3. Enter the desired time in the 'Preadmit/Admission Time' field.
  4. Select the desired value in the 'Program' field.
  5. Select the desired value in the 'Type Of Admission' field.
  6. Select the desired practitioner in the 'Admitting Practitioner' field.
  7. Enter the desired date in the 'Date Of Discharge' field.
  8. Enter the desired time in the 'Discharge Time' field.
  9. Select the desired value in the 'Type Of Discharge' field.
  10. Select the desired practitioner in the 'Discharge Practitioner' field.
  11. Populate any other desired fields.
  12. Click [Submit].
  13. Access the 'CareFabric Monitor' form.
  14. Enter the current date in the 'From Date' and 'Through Date' fields.
  15. Select "Client A" in the 'Client ID' field.
  16. Click [View Activity Log].
  17. 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.
  18. Validate the 'fhirIdentifiers' - 'id' - 'value' field contains the PATID for "Client A".
  19. Validate the 'period' - 'fromDate' field contains the 'Preadmit/Admission Date' and 'Preadmit/Admission Time' filed in the previous steps.
  20. Validate the 'period' - 'toDate' field contains the 'Date of Discharge' and 'Discharge Time' filed in the previous steps.
  21. Validate the first 'statusCode' - 'code' field contains "active".
  22. Validate the second 'statusCode' - 'code' field contains "discharged".
  23. 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
  1. Select "Client A" and access the 'Discharge' form.
  2. Enter the desired date in the 'Date of Discharge' field.
  3. Enter the desired time in the 'Discharge Time' field.
  4. Select the desired value in the 'Type Of Discharge' field.
  5. Select the desired practitioner in the 'Discharge Practitioner' field.
  6. Populate any other required fields.
  7. Click [Submit].
  8. Access the 'CareFabric Monitor' form.
  9. Enter the current date in the 'From Date' and 'Through Date' fields.
  10. Select "Client A" in the 'Client ID' field.
  11. Click [View Activity Log].
  12. 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.
  13. Validate the 'fhirIdentifiers' - 'id' - 'value' field contains the PATID for "Client A".
  14. Validate the 'period' - 'fromDate' field contains the 'Preadmit/Admission Date' and 'Preadmit/Admission Time' filed via Admission.
  15. Validate the 'period' - 'toDate' field contains the 'Date of Discharge' and 'Discharge Time' filed in the previous steps.
  16. Validate the first 'statusCode' - 'code' field contains "active".
  17. Validate the second 'statusCode' - 'code' field contains "discharged".
  18. 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
  1. Select "Client A" and access the 'Leaves' form.
  2. Enter the desired date in the 'Leave Date' field.
  3. Enter the desired time in the 'Leave Time' field.
  4. Select the desired value in the 'Type Of Leave From' field.
  5. Select the desired value in the 'Reason For Leave' field.
  6. Populate any other desired fields.
  7. Click [Submit].
  8. Access the 'CareFabric Monitor' form.
  9. Enter the current date in the 'From Date' and 'Through Date' fields.
  10. Select "Client A" in the 'Client ID' field.
  11. Click [View Activity Log].
  12. 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.
  13. Click [Click To View Record].
  14. Validate the second 'statusCode' - 'code' field contains "on-hold".
  15. 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
  1. Select "Client A" and access the 'Leaves' form.
  2. Enter the desired date in the 'Leave Date' field.
  3. Enter the desired time in the 'Leave Time' field.
  4. Select the desired value in the 'Type Of Leave From' field.
  5. Select the desired value in the 'Reason For Leave' field.
  6. Populate any other desired fields.
  7. Click [Submit].
  8. Access the 'CareFabric Monitor' form.
  9. Enter the current date in the 'From Date' and 'Through Date' fields.
  10. Select "Client A" in the 'Client ID' field.
  11. Click [View Activity Log].
  12. 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.
  13. Click [Click To View Record].
  14. Validate the second 'statusCode' - 'code' field contains "on-hold".
  15. Close the report and the form.
  16. Select "Client A" and access the 'Return From Leaves' form.
  17. Enter the desired date in the 'Return Date' field.
  18. Enter the desired time in the 'Return Time' field.
  19. Select the desired value in the 'Reason For Close Of Leave' field.
  20. Populate any other desired fields.
  21. Click [Submit].
  22. Access the 'CareFabric Monitor' form.
  23. Enter the current date in the 'From Date' and 'Through Date' fields.
  24. Select "Client A" in the 'Client ID' field.
  25. Click [View Activity Log].
  26. 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.
  27. Click [Click To View Record].
  28. Validate the second 'statusCode' - 'code' field contains "planned".
  29. Close the report and the form.
Scenario 8: Pre Admit - Validate the 'EncounterResourceCreated' SDK event
Steps
  1. Access the 'Pre Admit' form.
  2. Add a pre-admission for a new client. This will be referred to as "Client A".
  3. Enter the desired date in the 'Preadmit/Admission Date' field.
  4. Enter the desired time in the 'Preadmit/Admission Time' field.
  5. Select the desired value in the 'Program' field.
  6. Select the desired practitioner in the 'Admitting Practitioner' field.
  7. Populate all other required and desired fields.
  8. Click [Submit].
  9. Access the 'CareFabric Monitor' form.
  10. Enter the current date in the 'From Date' and 'Through Date' fields.
  11. Select "Client A" in the 'Client ID' field.
  12. Click [View Activity Log].
  13. 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.
  14. Validate the 'fhirIdentifiers' - 'id' - 'value' field contains the PATID for "Client A".
  15. Validate the 'period' - 'fromDate' field contains the 'Preadmit/Admission Date' and 'Preadmit/Admission Time' filed in the previous steps.
  16. Validate the first 'statusCode' - 'code' field contains "active".
  17. Validate the 'participants' - 'individualPractitionerResourceID' - 'id' field contains the ID for the 'Admitting Practitioner' filed in the previous steps.
  18. Validate the 'participants' - 'typeCodes' - 'codes' - 'code' field contains "ADMPHYS".
  19. Validate the 'participants' - 'typeCodes' - 'displayName' field contains "Admitting Physician".
  20. Validate the second 'statusCode' - 'code' field contains "planned".
  21. 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
  1. Select "Client A" and access the 'Pre Admit Discharge' form.
  2. Enter the desired date in the 'Date of Discharge' field.
  3. Enter the desired time in the 'Discharge Time' field.
  4. Select the desired value in the 'Type Of Discharge' field.
  5. Select the desired practitioner in the 'Discharge Practitioner' field.
  6. Populate any other required fields.
  7. Click [Submit].
  8. Access the 'CareFabric Monitor' form.
  9. Enter the current date in the 'From Date' and 'Through Date' fields.
  10. Select "Client A" in the 'Client ID' field.
  11. Click [View Activity Log].
  12. 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.
  13. Validate the 'fhirIdentifiers' - 'id' - 'value' field contains the PATID for "Client A".
  14. Validate the 'period' - 'fromDate' field contains the 'Preadmit/Admission Date' and 'Preadmit/Admission Time' filed via Pre-Admission.
  15. Validate the 'period' - 'toDate' field contains the 'Date of Discharge' and 'Discharge Time' filed in the previous steps.
  16. Validate the first 'statusCode' - 'code' field contains "active".
  17. Validate the second 'statusCode' - 'code' field contains "discharged".
  18. 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
  1. Select "Client A" and access the 'Diagnosis' form.
  2. Select "Admission" in the 'Type Of Diagnosis' field.
  3. Validate the 'Date Of Diagnosis' field contains the date of admission for "Client A".
  4. Enter the desired time in the 'Time Of Diagnosis' field.
  5. Click [New Row].
  6. Search for and select the desired value in the 'Diagnosis Search' field.
  7. Validate "Primary" is selected in the 'Ranking' field.
  8. Select the desired practitioner in the 'Diagnosing Practitioner' field.
  9. Populate any other desired fields.
  10. Click [Submit].
  11. Access the 'CareFabric Monitor' form.
  12. Enter the current date in the 'From Date' and 'Through Date' fields.
  13. Select "Client A" in the 'Client ID' field.
  14. Click [View Activity Log].
  15. 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.
  16. Click [Click To View Record].
  17. Validate the 'diagnoses' - 'conditionResourceID' - 'id' field contains a unique identifier for the diagnosis filed in the previous steps.
  18. Validate the 'diagnoses' - 'rank' field contains "1".
  19. Validate the 'diagnoses' - 'useCode' - 'codes' - 'code' field contains "AD".
  20. Validate the 'diagnoses' - 'useCode' -' displayName' field contains "Admission Diagnosis".
  21. 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
  1. Access the 'Client Charge Input' form.
  2. Enter the desired date in the 'Date Of Service' field.
  3. Enter the desired time in the 'Service Start Time' and 'Service End Time' fields.
  4. Select "Client A" in the 'Client ID' field.
  5. Select the desired value in the 'Episode Number' field.
  6. Select the desired value in the 'Service Codes' field.
  7. Select the desired practitioner in the 'Practitioner' field.
  8. Select the desired value in the 'Location' field.
  9. Click [Submit] and [No].
  10. Access the 'CareFabric Monitor' form.
  11. Enter the current date in the 'From Date' and 'Through Date' fields.
  12. Select "Client A" in the 'Client ID' field.
  13. Click [View Activity Log].
  14. 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.
  15. Click [Click To View Record].
  16. Validate the 'period' - 'fromDate' field contains the 'Date Of Service' and the 'Service Start Time' filed in the previous steps.
  17. Validate the 'period' - 'toDate' field contains the 'Date Of Service' and the 'Service End Time' filed in the previous steps.
  18. Validate the first 'statusCode' - 'code' field contains "active".
  19. Validate the 'participants' - 'individualPractitionerResourceID' - 'id' field contains the ID associated to the 'Practitioner' filed in the previous steps.
  20. Validate the 'participants' - 'typeCodes' - 'codes' - 'code' field contains "PPRF".
  21. Validate the 'participants' - 'typeCodes' - 'displayName' field contains "Primary Performer".
  22. Validate the second 'statusCode' - 'code' field contains "in-progress".
  23. 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
  1. Access the 'Client Charge Input' form.
  2. Enter the desired date in the 'Date Of Service' field.
  3. Enter the desired time in the 'Service Start Time' and 'Service End Time' fields.
  4. Select "Client A" in the 'Client ID' field.
  5. Select the desired value in the 'Episode Number' field.
  6. Select the desired value in the 'Service Codes' field.
  7. Select the desired practitioner in the 'Practitioner' field.
  8. Select the desired value in the 'Location' field.
  9. Click [Submit] and [No].
  10. Access the 'CareFabric Monitor' form.
  11. Enter the current date in the 'From Date' and 'Through Date' fields.
  12. Select "Client A" in the 'Client ID' field.
  13. Click [View Activity Log].
  14. 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.
  15. Click [Click To View Record].
  16. Validate the 'period' - 'fromDate' field contains the 'Date Of Service' and the 'Service Start Time' filed in the previous steps.
  17. Validate the 'period' - 'toDate' field contains the 'Date Of Service' and the 'Service End Time' filed in the previous steps.
  18. Validate the first 'statusCode' - 'code' field contains "active".
  19. Validate the 'participants' - 'individualPractitionerResourceID' - 'id' field contains the ID associated to the 'Practitioner' filed in the previous steps.
  20. Validate the 'participants' - 'typeCodes' - 'codes' - 'code' field contains "PPRF".
  21. Validate the 'participants' - 'typeCodes' - 'displayName' field contains "Primary Performer".
  22. Validate the second 'statusCode' - 'code' field contains "in-progress".
  23. Close the report and the form.
  24. Access the 'Edit Service Information' form.
  25. Select "Client A" in the 'Client ID' field.
  26. Select the desired episode in the 'Select Episode' field.
  27. Click [Select Services To Edit].
  28. Select the service filed in the previous steps and click [OK].
  29. Validate all previously populated data is displayed for the service.
  30. Edit the 'Service Start Time' and 'Service End Time' fields to be any new value.
  31. Click [Submit] and close the form.
  32. Access the 'CareFabric Monitor' form.
  33. Enter the current date in the 'From Date' and 'Through Date' fields.
  34. Select "Client A" in the 'Client ID' field.
  35. Click [View Activity Log].
  36. 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.
  37. Click [Click To View Record] for the "EncounterResourceUpdated" record.
  38. Validate the 'period' - 'fromDate' field contains the 'Date Of Service' and the 'Service Start Time' filed via 'Client Charge Input'.
  39. Validate the 'period' - 'toDate' field contains the 'Date Of Service' and the 'Service End Time' filed via 'Client Charge Input'.
  40. Validate the second 'statusCode' - 'code' field contains "cancelled".
  41. Navigate back to the 'CareFabric Monitor Report'.
  42. Click [Click To View Record] for the "EncounterResourceCreated" record.
  43. Validate the 'period' - 'fromDate' field contains the 'Date Of Service' and the 'Service Start Time' filed via 'Edit Service Information'.
  44. Validate the 'period' - 'toDate' field contains the 'Date Of Service' and the 'Service End Time' filed via 'Edit Service Information'.
  45. Validate the second 'statusCode' - 'code' field contains "in-progress".
  46. 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
  1. Access the 'Client Charge Input' form.
  2. Enter the desired date in the 'Date Of Service' field.
  3. Enter the desired time in the 'Service Start Time' and 'Service End Time' fields.
  4. Select "Client A" in the 'Client ID' field.
  5. Select the desired value in the 'Episode Number' field.
  6. Select the desired value in the 'Service Codes' field.
  7. Select the desired practitioner in the 'Practitioner' field.
  8. Select the desired value in the 'Location' field.
  9. Click [Submit] and [No].
  10. Access the 'CareFabric Monitor' form.
  11. Enter the current date in the 'From Date' and 'Through Date' fields.
  12. Select "Client A" in the 'Client ID' field.
  13. Click [View Activity Log].
  14. 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.
  15. Click [Click To View Record].
  16. Validate the second 'statusCode' - 'code' field contains "in-progress".
  17. Close the report and the form.
  18. Access the 'Delete Service' form.
  19. Select "Client A" in the 'Client ID' field.
  20. Enter the desired date in the 'Start Date' and 'End Date' fields.
  21. Click [Display Client].
  22. Select the desired service and click [OK].
  23. Click [Delete], [OK], and [Yes].
  24. Validate a message is displayed stating: Deleted.
  25. Click [OK] and close the form.
  26. Access the 'CareFabric Monitor' form.
  27. Enter the current date in the 'From Date' and 'Through Date' fields.
  28. Select "Client A" in the 'Client ID' field.
  29. Click [View Activity Log].
  30. 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.
  31. Click [Click To View Record].
  32. Validate the second 'statusCode' - 'code' field contains "cancelled".
  33. 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
  1. Access the 'Change Program/Admission Date' form.
  2. Select "Client A" in the 'Client ID' field.
  3. Select the desired episode in the 'Select Episode' field.
  4. Enter any new value in the 'New Admission Date' and 'New Admission Time' fields.
  5. Click [Submit] and close the form.
  6. Access the 'CareFabric Monitor' form.
  7. Enter the current date in the 'From Date' and 'Through Date' fields.
  8. Select "Client A" in the 'Client ID' field.
  9. Click [View Activity Log].
  10. 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.
  11. Validate the 'period' - 'fromDate' field contains the 'New Admission Date' and 'New Admission Time' filed in the previous steps.
  12. 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
  1. Access the 'Progress Notes (Group and Individual)' form.
  2. Select "Client A" in the 'Select Client' field.
  3. Select the desired episode in the 'Select Episode' field.
  4. Select "Independent Note" in the 'Progress Note For' field.
  5. Select the desired value in the 'Note Type' field.
  6. Enter the desired value in the 'Notes Field'.
  7. Select the desired practitioner in the 'Assign as Primary Care Provider' field.
  8. Select "Final" in the 'Draft/Final' field.
  9. File the note.
  10. Access Crystal Reports or other SQL Reporting tool.
  11. Select the PM namespace.
  12. Create a report using the 'SYSTEM.client_practitioner_assignment' SQL table.
  13. Validate a row is displayed for the note finalized in the previous steps with PCL.
  14. Validate the 'PATID' field contains the client ID for "Client A".
  15. Validate the 'practitioner' field contains the ID for the practitioner selected in the previous steps.
  16. Validate the 'date_of_assignment' and 'time_of_assignment' fields contain the date/time the note was filed.
  17. Close the report.
  18. Access the 'CareFabric Monitor' form.
  19. Enter the current date in the 'From Date' and 'Through Date' fields.
  20. Select "Client A" in the 'Client ID' field.
  21. Click [View Activity Log].
  22. 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.
  23. Click [Click To View Record].
  24. Validate the last 'individualPractitionerResourceID' - 'id' field contains the ID for the practitioner selected in the previous steps.
  25. 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.
  26. Validate the last 'typeCodes' - 'codes' - 'code' field contains "PCP".
  27. Validate the last 'typeCodes' - 'codes' - 'displayName' field contains "Primary Care Physician".
  28. 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
  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 "Note Type A".
  5. Verify the existence of "Client A" in the client header when note is started.
  6. Fill out all required fields.
  7. Add signatures in the 'Patient Signature', 'Guardian Signature' and 'Other Signature' fields.
  8. Click [Sign Note].
  9. Validate the Sign Note' dialog is displayed.
  10. Enter the pin for "User A" in the 'Pin' field and click [Sign].
  11. Validate a message is displayed stating: Note Signed Successfully.
  12. Log into myAvatar as "User A".
  13. Navigate to the "My To Do's" widget.
  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, including the 'Patient Signature', 'Guardian Signature' and 'Other Signature' fields.
  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.
  20. Select "Client A" and navigate to the 'Progress Notes' widget.
  21. Validate the progress note filed from Bells Notes is displayed.
  22. 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
  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 "Note Type A".
  5. Verify the existence of "Client A" in the client header when note is started.
  6. Fill out all required fields.
  7. Add signatures in the 'Patient Signature', 'Guardian Signature' and 'Other Signature' fields.
  8. Click [Sign Note].
  9. Validate the Sign Note' dialog is displayed.
  10. Enter the pin for "User A" in the 'Pin' field and click [Sign].
  11. Validate a message is displayed stating: Note Signed Successfully.
  12. Select "Client A" and navigate to the 'Progress Notes' widget.
  13. Validate the progress note filed from Bells Notes is displayed.
  14. 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
  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 "Note Type A".
  5. Verify the existence of "Client A" in the client header when note is started.
  6. Fill out all required fields.
  7. Add signatures in the 'Patient Signature', 'Guardian Signature' and 'Other Signature' fields.
  8. Click [Sign Note].
  9. Validate the Sign Note' dialog is displayed.
  10. Enter the pin for "User A" in the 'Pin' field and click [Sign].
  11. Validate a message is displayed stating: Note Signed Successfully.
  12. Log into myAvatar as "User A".
  13. Navigate to the "My To Do's" widget.
  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, including the 'Patient Signature', 'Guardian Signature' and 'Other Signature' fields.
  17. Click [Reject].
  18. Enter the desired value in the 'Comments for Reject' field and click [OK].
  19. Access the 'Progress Notes (Group and Individual)' form.
  20. Select "Client A" in the 'Select Client' field.
  21. Select the corresponding episode in the 'Select Episode' field.
  22. Select the note rejected in the previous steps in the 'Select Draft Note To Edit' field.
  23. Validate the note details sent from Bells Notes are displayed including the signature for 'Patient Signature', 'Guardian Signature', and 'Other Signature'.
  24. Validate "Draft" is selected in the 'Draft/Final' field.
  25. 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
  1. Access the 'Practitioner Termination' form.
  2. Select "Practitioner A" in the 'Select Staff' dialog and click [OK].
  3. Enter any past date in the 'Termination Date' field.
  4. Select the desired value in the 'Reason For Termination' field.
  5. Click [Submit].
  6. Access the 'CareFabric Monitor' form.
  7. Enter the current date in the 'From Date' and 'Through Date' fields.
  8. Select "Practitioner A" in the 'Staff ID' field.
  9. Click [View Activity Log].
  10. Validate the 'CareFabric Monitor Report' is displayed and contains a "StaffMemberUpdated" record.
  11. Select it and click [Click To View Record].
  12. Validate the 'terminatedDate' field contains the 'Termination Date' filed in the previous steps.
  13. Close the report and the form.
  14. Access the 'Practitioner Enrollment' form.
  15. Select "Practitioner A" in the 'Select Staff' dialog and click [OK].
  16. Enter the current date in the 'Registration Date' field.
  17. Select the "Categories/Taxonomy" section.
  18. Select "Create New" in the 'Category/Taxonomy' field.
  19. Enter the current date in the 'Effective Date' field.
  20. Select the desired value in the 'Practitioner Category' field.
  21. Select the desired value in the 'Discipline' field.
  22. Select the desired value in the 'Practitioner Categories For Coverage' field.
  23. Click [Add Practitioner Categories] and [OK].
  24. Submit the form.
  25. Access the 'CareFabric Monitor' form.
  26. Enter the current date in the 'From Date' and 'Through Date' fields.
  27. Select "Practitioner A" in the 'Staff ID' field.
  28. Click [View Activity Log].
  29. Validate the 'CareFabric Monitor Report' is displayed and contains a "StaffMemberUpdated" record.
  30. Select it and click [Click To View Record].
  31. Validate the 'activatedDate' field contains the current date.
  32. Validate the 'terminationDate' field contains "null".
  33. 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
  1. Log into CareManager.
  2. Search for and select "Client A".
  3. File a progress note for a "New Service", populating all required and desired fields.
  4. Select "Practitioner A" as the 'Practitioner'.
  5. Enter the desired value for the 'Duration'.
  6. Select "Final" as the 'Note Status'.
  7. Click [Save].
  8. Log into myAvatar as "User A".
  9. Navigate to the "My To Do's" widget.
  10. Locate the To Do just routed and click [Approve Document].
  11. Validate the document is displayed with the progress note data sent from CareManager.
  12. Click [Accept].
  13. Enter the password for "User A" in the 'Verify Password' dialog and click [OK].
  14. Validate the To-Do is no longer displayed.
  15. Select "Client A" and navigate to the 'Progress Notes' widget.
  16. Validate the 'Progress Notes' widget contains the finalized progress note submitted from CareManager.
  17. 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
  1. Log into CareManager.
  2. Search for and select "Client A".
  3. File a progress note for a "New Service", populating all required and desired fields.
  4. Select "Practitioner A" as the 'Practitioner'.
  5. Enter the desired value for the 'Duration'.
  6. Select "Final" as the 'Note Status'.
  7. Click [Save].
  8. Log into myAvatar as "User A".
  9. Select "Client A" and navigate to the 'Progress Notes' widget.
  10. Validate the 'Progress Notes' widget contains the finalized progress note submitted from CareManager.
  11. 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
  1. Select "Client A" and access the 'Update Client Data' form.
  2. Enter any invalid email format in the 'Email Address' field (Ex: TEST).
  3. Criteria for a valid email includes the following:
  4. There is an @
  5. There is a value before the @
  6. There is an address after the @
  7. There is a . in the address
  8. Click [Submit].
  9. Access the 'Scheduling Calendar' form.
  10. Right click in the 'Appointment Grid' and click [Add Appointment].
  11. Enter the TeleHealth Service Code in the 'Service Code' field.
  12. Enter "Client A" in the 'Client' field.
  13. Populate all required and desired fields.
  14. Click [Submit].
  15. Validate the 'Appointment Grid' contains the new appointment.
  16. Click [Dismiss].
  17. Access the 'CareFabric Monitor' form.
  18. Enter the current date in the 'From Date' and 'Through Date' fields.
  19. Enter "TeleHealthAppointmentCreated" in the 'Event/Action Search' field.
  20. Click [View Activity Log].
  21. Validate the 'CareFabric Monitor Report' field contains a "TeleHealthAppointmentCreated" record.
  22. Click [Click To View Record].
  23. Validate the 'participants' - 'email' field contains "null" because the email address on file is invalid.
  24. Close the report and the form.
  25. Select "Client A" and access the 'Update Client Data' form.
  26. Enter any valid email format in the 'Email Address' field (Ex: Test@test.com)
  27. Click [Submit].
  28. Access the 'CareFabric Monitor' form.
  29. Enter the current date in the 'From Date' and 'Through Date' fields.
  30. Enter "TeleHealthAppointmentUpdated" in the 'Event/Action Search' field.
  31. Click [View Activity Log].
  32. Validate the 'CareFabric Monitor Report' contains a "TeleHealthAppointmentUpdated" record. Updating the email address in 'Update Client Data' will trigger this message.
  33. Click [Click To View Record].
  34. Validate the 'participants' - 'email' field contains the value filed in the previous steps (Ex. Test@test.com).
  35. 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
  1. Open the "Scheduling Calendar" form.
  2. Schedule a recurring appointment TeleHealth service using a TeleHealth service code.
  3. Open the "CareFabric Monitor" form:
  4. Run the Activity Log for the following events "TeleHealthAppointmentCreated".
  5. Validate that a "TeleHealthAppointmentCreated" event is generated for however many appointments are in the recurrence.
  6. Validate that each "TeleHealthAppointmentCreated" event includes the following:
  7. Validate the "isReoccuringAppointment" property is "true".
  8. Validate the event includes the "RecurrenceInfo" object.
  9. Validate the "appointmentDateRange" object. Ensure the date and time is accurate.
  10. Validate the "recurrenceInfo" - "startDate" field. Ensure the date is accurate.
  11. Return to the "Scheduling Calendar":
  12. Edit the recurring appointment that was created in previous steps.
  13. Change the duration of the service.
  14. Open the "CareFabric Monitor" form:
  15. Run the Activity Log for the following events "TeleHealthAppointmentUpdated".
  16. Validate that a "TeleHealthAppointmentUpdated" event is generated for however many appointments are in the recurrence.
  17. Validate that each "TeleHealthAppointmentUpdated" event includes the following:
  18. Validate the "isReoccuringAppointment" property is "true".
  19. Validate the event includes the "RecurrenceInfo" object.
  20. Validate the "appointmentDateRange" object. Ensure the date and time is accurate.
  21. Validate the "recurrenceInfo" - "startDate" field. Ensure the date is accurate.
  22. Return to the "Scheduling Calendar":
  23. Delete the recurring appointment that was created and edited in previous steps.
  24. Open the "CareFabric Monitor" form:
  25. Run the Activity Log for the following events "TeleHealthAppointmentDeleted".
  26. Validate that a "TeleHealthAppointmentDeleted" event is generated for however many appointments are in the recurrence.
  27. Validate that each "TeleHealthAppointmentDeleted" event includes the following:
  28. Validate the "isReoccuringAppointment" property is "true".
  29. 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
  1. Open the "Scheduling Calendar" form:
  2. Schedule a recurring appointment TeleHealth service using a TeleHealth location.
  3. Open the "CareFabric Monitor" form:
  4. Run the Activity Log for the following events "TeleHealthAppointmentCreated".
  5. Validate that a "TeleHealthAppointmentCreated" event is generated for however many appointments are in the recurrence.
  6. Validate that each "TeleHealthAppointmentCreated" event includes the following:
  7. Validate the "isReoccuringAppointment" property is "true".
  8. Validate the event includes the "RecurrenceInfo" object.
  9. Validate the "appointmentDateRange" object. Ensure the date and time is accurate.
  10. Validate the "recurrenceInfo" - "startDate" field. Ensure the date is accurate.
  11. Return to the "Scheduling Calendar":
  12. Edit the recurring appointment that was created in previous steps.
  13. Change the duration of the service.
  14. Open the "CareFabric Monitor" form:
  15. Run the Activity Log for the following events "TeleHealthAppointmentUpdated".
  16. Validate that a "TeleHealthAppointmentUpdated" event is generated for however many appointments are in the recurrence.
  17. Validate that each "TeleHealthAppointmentUpdated" event includes the following:
  18. Validate the "isReoccuringAppointment" property is "true".
  19. Validate the event includes the "RecurrenceInfo" object.
  20. Validate the "appointmentDateRange" object. Ensure the date and time is accurate.
  21. Validate the "recurrenceInfo" - "startDate" field. Ensure the date is accurate.
  22. Return to the "Scheduling Calendar":
  23. Delete the recurring appointment that was created and edited in previous steps.
  24. Open the "CareFabric Monitor" form:
  25. Run the Activity Log for the following events "TeleHealthAppointmentDeleted".
  26. Validate that a "TeleHealthAppointmentDeleted" event is generated for however many appointments are in the recurrence.
  27. Validate that each "TeleHealthAppointmentDeleted" event includes the following:
  28. Validate the "isReoccuringAppointment" property is "true".
  29. 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
  1. Add an unscheduled visit in the Mobile CareGiver+ application for multiple recipients (Client A & Client B) 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 'CareFabric Monitor' form.
  4. Enter the current date in the 'From Date' and 'Through Date' fields.
  5. Select "McgEvvAppointmentUpdated" in the 'Event/Action Search' field.
  6. Click [View Activity Log].
  7. Validate the 'CareFabric Monitor Report' contains an "McgEvvAppointmentUpdated" record.
  8. Click [Click To View Record].
  9. Validate the 'endDate' field contains the appointment end date/time.
  10. Validate the 'isMultipleRecipients' field contains "true".
  11. Validate the 'mcgAppointmentID' - 'id' field contains the MCG+ unique identifier for the appointment.
  12. Validate the 'resource' - 'resourceID' field contains "Practitioner A".
  13. Validate the first - 'services' - 'clientID- 'id' field contains "Client A".
  14. Validate the first 'services' - 'procedureCode' - 'code' field contains "Procedure Code A".
  15. Validate the second 'services' - 'clientID' - 'id' field contains "Client B".
  16. Validate the second 'services' - 'procedureCode' - 'code' field contains "Procedure Code A".
  17. Validate the 'startDate' field contains the appointment start date/time.
  18. Validate all other appointment data is displayed.
  19. Close the report and the form.
  20. Access the 'Scheduling Calendar' form.
  21. Validate an appointment for "Client A" and "Client B" with "Practitioner A" that was sent from Mobile CareGiver+ is displayed at "Site A".
  22. Right click on the appointment for "Client A" and click [Details/Edit].
  23. Validate the appointment details are displayed as expected.
  24. Close the form.
  25. Right click on the appointment for "Client B" and click [Details/Edit].
  26. Validate the appointment details are displayed as expected.
  27. 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
  1. Start the unscheduled visit with multiple recipients, "Client A" and "Client B", in the Mobile CareGiver+ application.
  2. Access the 'CareFabric Monitor' form.
  3. Enter the current date in the 'From Date' and 'Through Date' fields.
  4. Select "Client A" in the 'Client ID' field.
  5. Select "McgEvvVisitStarted" in the 'Event/Action Search' field.
  6. Click [View Activity Log].
  7. Validate the 'CareFabric Monitor Report' contains an "McgEvvVisitStarted" record.
  8. Click [Click To View Record].
  9. Validate the 'clockInDetails' - 'deviceRecordedDate' field contains the date of the visit and start time.
  10. Validate the 'isMultipleRecipients' field contains "true".
  11. Validate the first - 'services' - 'clientID- 'id' field contains "Client A".
  12. Validate the first 'services' - 'procedureCode' - 'code' field contains "Procedure Code A".
  13. Validate the second 'services' - 'clientID' - 'id' field contains "Client B".
  14. Validate the second 'services' - 'procedureCode' - 'code' field contains "Procedure Code A".
  15. Validate the last 'status' field contains "INPR" indicating the visit is in progress.
  16. Close the report and the form.
  17. Access the 'Scheduling Calendar' form.
  18. Validate the appointments for "Client A" and "Client B" display with the visit start time.
  19. Click [Dismiss].
  20. Access Crystal Reports or other SQL Reporting tool.
  21. Select the PM namespace.
  22. Create a report using the 'SYSTEM.appt_data' SQL table.
  23. Navigate to the appointment for "Client A" and "Client B".
  24. Validate the 'carefabric_appt_stat_code' field contains "INPR".
  25. Validate the 'carefabric_appt_stat_value' field contains "In Progress".
  26. 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
  1. Complete the visit for multiple recipients (Client A & Client B) with "Practitioner A" in the Mobile CareGiver+ application.
  2. Ensure the visit includes notes for both "Client A" and "Client B".
  3. Access the 'Scheduling Calendar' form.
  4. Validate the appointment for both "Client A" and "Client B" is displayed at the correct start/end times for the visit.
  5. Validate the appointment for "Client A" is displayed with the draft note disposition icon (if configured in 'Set System Defaults').
  6. Click [Dismiss].
  7. Select "Client A" and navigate to the 'Progress Notes' widget.
  8. Validate the draft 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.
  10. Select "Client B" and navigate to the 'Progress Notes' widget.
  11. Validate the draft progress note created when the visit was completed is displayed with the appropriate data for the visit.
  12. Validate the 'Notes Field' field for the progress note contains the notes entered when completing the visit.
  13. In the Mobile CareGiver+ application, access the Work List.
  14. Update the 'Billable Service Start' and 'Billable Service End' times.
  15. Release the visit.
  16. Access the 'Scheduling Calendar' form.
  17. Validate the appointments for "Client A" and "Client B" are displayed at the updated start/end times for the visit.
  18. Validate the appointments for "Client A" and "Client B" are still displayed with the draft note disposition icon.
  19. Click [Dismiss].
  20. Select "Client A" and navigate to the 'Progress Notes' widget.
  21. Validate the draft progress note displays the updated start/end times for the visit.
  22. Select "Client B" and navigate to the 'Progress Notes' widget.
  23. Validate the draft progress note displays the updated start/end times for the visit.
  24. Once the visit is accepted and received by myAvatar, the following will happen:
  25. Appointments will be posted, charges will be visible in the 'Client Ledger'
  26. Progress notes associated to the visit will be finalized.
Topics
• Electronic Visit Verification
 

Avatar_CareFabric_2024_Quarterly_Release_2024.02_Details.csv