Skip to main content

Avatar CareFabric 2024 Monthly Release 2024.01.02 Acceptance Tests

  1. Last updated
  2. Save as PDF
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
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 32 Summary | Details
OE NX - MedNote - Problem Classification
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Registry Settings (CWS)
  • Medical Note
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 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
  • Crystal Report Viewer
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
  • Crystal Report Viewer
  • Dictionary Update (PM)
  • Admission
  • 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:
  • Medical Note
  • Client Ledger
  • Document.Chief Complaint
  • Document.Diagnosis
  • Document.Medical Decision Making
  • 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
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • User Definition
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
 

Avatar_CareFabric_2024_Monthly_Release_2024.01.02_Details.csv