Skip to main content

Avatar OE 2024 Monthly Release 2024.00.01 Acceptance Tests

  1. Last updated
  2. Save as PDF
Update 6 Summary | Details
OE NX - Orders This Episode - creating pharmacy-type orders in external pharmacy mode
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Orders This Episode
  • Home Medications
Scenario 1: OE NX - Orders This Episode - Multiple Orders - Create, Copy and D/C - External Pharmacy Mode
Specific Setup:
  • A client must have an 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.
Steps
  1. Select "Client A" and access the Order Entry Console.
  2. Search for and select any pharmacy-type order code, that is in the form of "Tablet" and is not a controlled substance, in the 'New Order' field.
  3. Set the 'Dose' field to any value.
  4. Validate the 'Dose Unit' field contains "Tablet".
  5. Populate all required fields and click [Add to Scratchpad] and [Final Review].
  6. Validate the 'Interactions' dialog is displayed
  7. Override all interactions and click [Save Override and Exit].
  8. Validate the 'Final Review' dialog is displayed and click [Sign].
  9. Validate the 'Order grid' contains a new order.
  10. Create four additional orders using pharmacy-type order codes.
  11. Validate that all orders are displayed in the 'Order grid'.
Topics
• Order Entry Console • NX
Update 9 Summary | Details
Laboratory Orders sent to an external interface
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Orders This Episode
Scenario 1: OE NX - Orders This Episode - Lab orders - Ensure group order number or placer order number are displayed in 'Order Details' when 'Enable Order Message Queue and Multi-Test Lab Orders' is set to "Y"
Specific Setup:
  • The 'Enable Order Message Queue and Multi-Test Lab Orders' registry setting must be set to "Y".
  • Please log out of the application and log back in after completing the above configuration.
  • An external lab vendor must exist who is configured as follows:(Lab Vendor A)
  • 'External Application Type' = "Lab"
  • 'eVendor' = "Yes"
  • 'Lab Vendor Company' = "LabCorp"
  • 'Group Order Messages' = "Yes"
  • A lab vendor must exist that is not an eVendor. (Lab Vendor B)
  • Two lab-type order codes must exist. Each order code must have different 'Compendium Order Codes', but both must have "Lab Vendor A" selected in the 'External Lab Definition' grid in the 'Order Code Setup' form. (Lab Code A and Lab Code B)
  • A one time only frequency code must exist. (One Time Only)
  • A client must have an active inpatient episode. (Client A)
Steps
  1. Select "Client A" and access the Order Entry Console.
  2. Search for and select "Lab Code A".
  3. Select "One Time Only" in the 'Frequency' field.
  4. Validate that "Lab Vendor A" is displayed in the 'External Lab Vendor Destination' field.
  5. Select "Lab Vendor Staff will Collect" in the 'Specimen Collection' field.
  6. Populate all remaining required fields and click [Add to Scratchpad].
  7. Search for and select "Lab Code B".
  8. Select "One Time Only" in the 'Frequency' field.
  9. Validate that "Lab Vendor A" is displayed in the 'External Lab Vendor Destination' field.
  10. Select "Lab Vendor Staff will Collect" in the 'Specimen Collection' field.
  11. Populate all remaining required fields, click [Add to Scratchpad] and [Sign].
  12. Validate the 'Order grid' contains two orders that have the same "Requisition # GR-#" after the 'Order Details'.
  13. Create a new order for "Lab Code A" where "Lab Vendor A" is defaulted into the 'External Lab Destination' field, where "Lab Vendor Staff will Collect" is selected in the 'Specimen Collection' field, and click [Add to Scratchpad].
  14. Create a new order for "Lab Code B" where "Lab Vendor A" is defaulted into the 'External Lab Destination' field, where "Facility Staff will Collect" is selected in the 'Specimen Collection' field, and click [Add to Scratchpad] and [Sign].
  15. Validate the 'Order grid' contains a new order for "Lab Code A" with a "Requisition #" after the 'Order Details' that is the same as the 'Order Number' that is displayed in the 'Order Type' column.
  16. Validate the 'Order grid' contains a new order for "Lab Code B" with a "Requisition #" after the 'Order Details' that is the same as the 'Order Number' that is displayed in the 'Order Type' column.
  17. Create a new order for "Lab Code A" and deselect the value in the 'External Lab Destination' field and click [Add to Scratchpad] and [Sign].
  18. Validate the 'Order grid' contains a new order for "Lab Code A" with no 'Requisition #' after the 'Order Details'.
  19. Create a new order for "Lab Code A", select "Lab Vendor B" in the 'External Lab Destination' field and click [Add to Scratchpad] and [Sign].
  20. Validate the 'Order grid' contains a new order for "Lab Code B" with a "Requisition #" after the 'Order Details' that is the same as the 'Order Number' that is displayed in the 'Order Type' column.

Please Note: In order for orders to be grouped, they must have the same Lab Vendor, must both have one-time-only 'Frequency' codes, the same 'Specimen Collection' value, and the order codes must have different 'Compendium Order Codes'.
Topics
• Order Entry Console • NX
2023 Update 34 Summary | Details
OE NX - Client with Cross Episode Financial Eligibility - Creating Lab Orders
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Orders This Episode
Scenario 1: OE NX - Orders This Episode - Creating Lab orders for a client with two guarantors in Cross Episode Financial Eligibility
Specific Setup:
  • A lab vendor must exist that is a configured as an 'eVendor', has a 'Lab Vendor Company' of "LabCorp" or "Quest", and has 'ABN Required' set to "Yes". (Lab Vendor A)
  • Two lab-type order codes must exist. (Order Code A, Order Code B)
  • "Order Code A" and "Order Code B" must be associated with "Lab Vendor A" and must be associated with different 'Compendium Order Codes'.
  • A client must have an active inpatient episode. (Client A).
  • “Client A” must have a ‘Date of Birth’, ‘Sex’ and address on file in the ‘Update Client Data’ form, as well as information filed in the ‘Allergies and Hypersensitivities’ form, ‘Diagnosis’ form, in the ‘Height’ and ‘Weight’ fields in the ‘Vitals Entry’ form, and at least two guarantors filed in the 'Cross-Episode Financial Eligibility' form.
Steps
  1. Select "Client A" and access the Order Entry Console.
  2. Search for and select "Order Code A" in the 'New Order' field.
  3. Validate that the 'External Lab Vendor Destination' field contains "Lab Vendor A".
  4. Populate all required fields.
  5. Click [Add to Scratchpad] and [Sign].
  6. Validate the 'Order grid' contains an order for "Order Code A".
  7. Search for and select "Order Code B" in the 'New Order' field.
  8. Validate that the 'External Lab Vendor Destination' field contains "Lab Vendor A".
  9. Populate all required fields.
  10. Click [Add to Scratchpad] and [Sign].
  11. Validate the 'Order grid' contains an order for "Order Code A" and "Order Code B".
OE NX - Orders This Episode -
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Orders This Episode
  • eMAR
Scenario 1: OE NX – Create new pharmacy-type order when ‘Treatment Setting Processed by eMAR’ is set to “O”
Specific Setup:
  • The 'Avatar Order Entry->eMAR->Settings->->->Treatment Settings Processed By eMAR' registry setting must be set to "O" (Outpatient Only).
  • Please log out of the application and log back in after completing the above configuration.
  • A client must have an 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.
Steps
  1. Select "Client A" and access the Order Entry Console.
  2. Search for and select any pharmacy-type order code in the 'New order' field.
  3. Populate all required fields.
  4. Click [Add to Scratchpad] and [Final Review].
  5. Validate the ‘Interactions’ dialog is displayed.
  6. Override all interactions and click [Save Override and Exit].
  7. Validate the 'Final Review' dialog is displayed.
  8. Select "None" in the 'Output' field and click [Sign].
  9. Validate the 'Order grid' contains a new order.
  10. Access the 'eMAR' widget.
  11. Validate that the order created is not displayed.
OE NX - Orders This Episode - Validate Orders
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Orders This Episode
  • eMAR
  • eMAR NX - Dynamic Form - MEDICATION WARNING
Scenario 1: OE NX - Orders This Episode - Validating a one-time-only order that requires validation and has been administered in eMAR
Specific Setup:
  • Two Users must exist. One whose order actions require validation and who is not associated with a Staff Member. (User A) One whose actions do not require validation and who is associated with a Staff Member. (User B)
  • A client must have an 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.
  • "User A" must be logged into the application.
Steps
  1. Select "Client A" and access the Order Entry Console.
  2. Search for and select any pharmacy-type order code in the 'New order' field.
  3. Populate all required fields and ensure a one-time-only frequency code is selected.
  4. Click [Add to Scratchpad].
  5. Search for and select the staff member associated with “User B” in the ‘Ordering Practitioner’ field.
  6. Click [Final Review].
  7. Validate the ‘Interactions’ dialog is displayed.
  8. Override all interactions and click [Save Override and Exit].
  9. Validate the 'Final Review' dialog is displayed.
  10. Validate “Pending” is selected in the ‘Output’ field and click [Sign].
  11. Validate the ‘Order grid’ contains a new order with an ‘Order Status’ of “Requires Validation (staff member last name, first name – Create New Order)”.
  12. Access the 'eMAR' widget.
  13. Validate the order created is displayed.
  14. Complete ‘Order Acknowledgement’ and ‘Client Education’ on the order.
  15. Populate all required fields and administer the order.
  16. Validate that the order is now Discontinued.
  17. Access the Order Entry Console.
  18. Select the order in the ‘Order grid’ and click [Validate].
  19. Validate the 'Final Review' dialog is displayed.
  20. Select "None" in the 'Output' field and click [Sign].
  21. Validate the ‘Order grid’ contains the same order with an ‘Order Status’ of “Active”.
Topics
• Order Entry Console • NX
2023 Update 35 Summary | Details
"Avatar Order Entry" - application mappings
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Application Namespace Connections Validation
Scenario 1: Application Namespace Connection Validation
Specific Setup:
  1. Have a system with one or more child namespaces. For example: "PM" or "CWS" namespaces
  2. Have a system that the following modules installed in the system: "Avatar Data Warehouse", " Avatar CWS State Forms" or "Avatar ProviderConnect NX 2023 " and any other desired modules
Steps
  1. Open form "Applications Namespace Connection Validations"
  2. Validate "Currently Connected Namespaces" text box lists the expected child applications and namespace(s):
  3. Validate "Currently Connected Namespaces" text box indicates there are no application namespace connection or mapping errors.
  4. Click [Process]
  5. Validate the "Application Namespace Connections Validation" report list the expected connected child applications and namespace(s)
  6. Validate "Currently Connected Namespaces" text box indicates there are no application namespace connection or mappings errors.
Scenario 2: Avatar OE - Validate the migration of global entries in the "^NTSTMAP" Global to the "^RADplusMap" Global
Steps
  1. Internal Testing Only
Topics
• Forms
 

Avatar_OE_2024_Monthly_Release_2024.00.01_Details.csv