Skip to main content

Avatar HL7 2022 Quarterly Release 2022.03 Acceptance Tests

  1. Last updated
  2. Save as PDF
Update 2 Summary | Details
Validate order code description in an outbound order message has additional information based on system configuration.
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Order Entry Console
  • HL7 Connection Monitor
Scenario 1: Validate 'Order Code Description' in an Outbound HL7 Order Message
Specific Setup:
  • Avatar HL7 must be installed and configured for 4 outbound order connections. Other than the Default connection, a customization pack will be needed if not already supplemented by vendor profile.
  • Default connection 1 (ORDERS-Default) - Only Description
  • Connection 2 (ORDERS - Connection 2) - Dosage (20066) + Dosage Unit (20067) + Route (20068) + Dosage Form (20069) (from order)
  • Connection 3 (ORDERS - Connection 3) - Medication strength (10109) + Strength unit (10110) (from order code table)
  • Connection 4 (ORDERS - Connection 4) - Dosage (20066) + Dosage Unit (20067) (from order)
  • Must have a client with an active episode. (Client A).
  • One medication with missing "Strength" field in 'Order Code Setup' form.
Steps
  1. Select "Client A" and access the 'Order Entry Console'.
  2. Enter an order for medication that is missing the "Strength" field in 'Order Code Setup'.
  3. Access the 'HL7 Connection Monitor' form.
  4. Select the outbound order connection (ORDERS-Default) in the 'Select Row' field.
  5. Click [Show Transaction Log].
  6. Validate a row with an event type of "O01-ORM" is displayed for "Client A".
  7. Click 'View HL7 Message' link.
  8. Validate segment 'RXO:1.1' is equal to "Description only".
  9. Close the report.
  10. Select the outbound order connection (ORDERS - Connection 2) in the 'Select Row' field.
  11. Click [Show Transaction Log].
  12. Validate a row with an event type of "O01-ORM" is displayed for "Client A".
  13. Click 'View HL7 Message' link.
  14. Validate segment 'RXO:1.1' is equal to "Description, Dosage, Dosage Unit, Route, and Dosage Form".
  15. Close the report.
  16. Select the outbound order connection (ORDERS - Connection 3) in the 'Select Row' field.
  17. Click [Show Transaction Log].
  18. Validate a row with an event type of "O01-ORM" is displayed for "Client A".
  19. Click 'View HL7 Message' link.
  20. Validate segment 'RXO:1.1' is equal to "Description, Medication strength, and Strength unit".
  21. Close the report.
  22. Select the outbound order connection (ORDERS - Connection 4) in the 'Select Row' field.
  23. Click [Show Transaction Log].
  24. Validate a row with an event type of "O01-ORM" is displayed for "Client A".
  25. Click 'View HL7 Message' link.
  26. Validate segment 'RXO:1.1' is equal to "Description, Dosage, and Dosage Unit".
  27. Close the report.
  28. Close the form.
Topics
• HL7
Update 5 Summary | Details
Support is added for the A12 (Cancel Transfer) HL7 inbound message.
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • HL7 Connection Monitor
  • Bed Reservation
Scenario 1: Validate Inbound ADT message support for A12 for 'Delete Bed Assignment'
Specific Setup:
  • Avatar HL7 must be installed.
  • There must be an Inbound ADT connection for 'ADT-GENERIC'.
  • Client A must exist with multiple Bed Assignments.
  • Client A must have an external PATID assigned.
  • Client A must have external episode number assigned.
Steps
  1. Send an inbound A12 (Delete Bed Assignment) message to Avatar with 'Current Bed Information' in segment ''PV1-3.1^3.2^3.3''.
  2. Validate the Filing Status is equal to "Err - The client is already assigned to the bed listed in PV1-3. Filing aborted.".
  3. Send an inbound A12 (Delete Bed Assignment) message to Avatar with 'Unit/Room/Bed Information that does not match any Bed Assignment' in segment ''PV1-3.1^3.2^3.3''.
  4. Validate the Filing Status is equal to "Err - The indicated unit does not match the information on file. Filing aborted.".
  5. Send an inbound A12 (Delete Bed Assignment) message to Avatar with 'Correct Unit but incorrect Room/Bed' in segment ''PV1-3.1^3.2^3.3''.
  6. Validate the Filing Status is equal to "Err - The indicated room does not match the information on file. Filing aborted.".
  7. Send an inbound A12 (Delete Bed Assignment) message to Avatar with 'Correct Unit / Room but incorrect Bed' in segment ''PV1-3.1^3.2^3.3''.
  8. Validate the Filing Status is equal to "Err - The indicated bed does not match the information on file. Filing aborted.".
  9. Send an inbound A12 (Delete Bed Assignment) message to Avatar with 'Correct Unit / Room / Bed (Bed Assigned before the current Bed Assignment)' in segment ''PV1-3.1^3.2^3.3''.
  10. Validate the Filing Status is equal to "OK".
  11. Continue sending A12 messages for the client until client will have no bed assignments remaining.
  12. Send an inbound A12 (Delete Bed Assignment) message to Avatar with 'Correct Unit / Room / Bed (Last Bed Assigned)' in segment ''PV1-3.1^3.2^3.3''.
  13. Validate the Filing Status is equal to "Err - Client has only one bed assignment for this episode, which cannot be deleted".
Scenario 2: Validate Inbound ADT message support for A12 for 'Delete Bed Assignment' with bed assigned to another client
Specific Setup:
  • Avatar HL7 must be installed.
  • There must be an Inbound ADT connection for 'ADT-GENERIC'.
  • Client A must have an external PATID assigned.
  • Client A must have external episode number assigned.
  • Client A must exist with multiple Bed Assignments.
  • Client B is assigned Client A's next to last Bed Assigned.
Steps
  1. Send an inbound A12 (Delete Bed Assignment) message to Avatar with 'Correct Unit / Room / Bed (Bed Assigned before the current Bed Assignment)' in segment ''PV1-3.1^3.2^3.3''.
  2. Validate the Filing Status is equal to "Err - Prior bed is currently occupied. Cannot reassign.".
Scenario 3: Validate Inbound ADT message support for A12 for 'Delete Bed Assignment' with bed reserved to another client as 'High Priority' reservation
Specific Setup:
  • Avatar HL7 must be installed.
  • There must be an Inbound ADT connection for 'ADT-GENERIC'.
  • Client A must have an external PATID assigned.
  • Client A must have external episode number assigned.
  • Client A must exist with multiple Bed Assignments.
  • Client B has 'High Priority' reservation of Client A's next to last Bed Assigned.
Steps
  1. Send an inbound A12 (Delete Bed Assignment) message to Avatar with 'Correct Unit / Room / Bed (Bed Assigned before the current Bed Assignment)' in segment ''PV1-3.1^3.2^3.3''.
  2. Validate the Filing Status is equal to "Err - Prior bed is reserved for (Client B) with a HIGH Priority.".
  3. Move Client B to 'Standard Priority' in same Unit/Room/Bed.
  4. Send an inbound A12 (Delete Bed Assignment) message to Avatar with 'Correct Unit / Room / Bed (Bed Assigned before the current Bed Assignment)' in segment ''PV1-3.1^3.2^3.3''.
  5. Validate the Filing Status is equal to "OK".
Support is added for the PD1 (Patient Additional Demographic) segment
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • HL7 Connection Monitor
  • Bed Reservation
Scenario 1: Validate Inbound ADT message support for A12 for 'Delete Bed Assignment'
Specific Setup:
  • Avatar HL7 must be installed.
  • There must be an Inbound ADT connection for 'ADT-GENERIC'.
  • Client A must exist with multiple Bed Assignments.
  • Client A must have an external PATID assigned.
  • Client A must have external episode number assigned.
Steps
  1. Send an inbound A12 (Delete Bed Assignment) message to Avatar with 'Current Bed Information' in segment ''PV1-3.1^3.2^3.3''.
  2. Validate the Filing Status is equal to "Err - The client is already assigned to the bed listed in PV1-3. Filing aborted.".
  3. Send an inbound A12 (Delete Bed Assignment) message to Avatar with 'Unit/Room/Bed Information that does not match any Bed Assignment' in segment ''PV1-3.1^3.2^3.3''.
  4. Validate the Filing Status is equal to "Err - The indicated unit does not match the information on file. Filing aborted.".
  5. Send an inbound A12 (Delete Bed Assignment) message to Avatar with 'Correct Unit but incorrect Room/Bed' in segment ''PV1-3.1^3.2^3.3''.
  6. Validate the Filing Status is equal to "Err - The indicated room does not match the information on file. Filing aborted.".
  7. Send an inbound A12 (Delete Bed Assignment) message to Avatar with 'Correct Unit / Room but incorrect Bed' in segment ''PV1-3.1^3.2^3.3''.
  8. Validate the Filing Status is equal to "Err - The indicated bed does not match the information on file. Filing aborted.".
  9. Send an inbound A12 (Delete Bed Assignment) message to Avatar with 'Correct Unit / Room / Bed (Bed Assigned before the current Bed Assignment)' in segment ''PV1-3.1^3.2^3.3''.
  10. Validate the Filing Status is equal to "OK".
  11. Continue sending A12 messages for the client until client will have no bed assignments remaining.
  12. Send an inbound A12 (Delete Bed Assignment) message to Avatar with 'Correct Unit / Room / Bed (Last Bed Assigned)' in segment ''PV1-3.1^3.2^3.3''.
  13. Validate the Filing Status is equal to "Err - Client has only one bed assignment for this episode, which cannot be deleted".
Scenario 2: Validate Inbound ADT message support for A12 for 'Delete Bed Assignment' with bed assigned to another client
Specific Setup:
  • Avatar HL7 must be installed.
  • There must be an Inbound ADT connection for 'ADT-GENERIC'.
  • Client A must have an external PATID assigned.
  • Client A must have external episode number assigned.
  • Client A must exist with multiple Bed Assignments.
  • Client B is assigned Client A's next to last Bed Assigned.
Steps
  1. Send an inbound A12 (Delete Bed Assignment) message to Avatar with 'Correct Unit / Room / Bed (Bed Assigned before the current Bed Assignment)' in segment ''PV1-3.1^3.2^3.3''.
  2. Validate the Filing Status is equal to "Err - Prior bed is currently occupied. Cannot reassign.".
Scenario 3: Validate Inbound ADT message support for A12 for 'Delete Bed Assignment' with bed reserved to another client as 'High Priority' reservation
Specific Setup:
  • Avatar HL7 must be installed.
  • There must be an Inbound ADT connection for 'ADT-GENERIC'.
  • Client A must have an external PATID assigned.
  • Client A must have external episode number assigned.
  • Client A must exist with multiple Bed Assignments.
  • Client B has 'High Priority' reservation of Client A's next to last Bed Assigned.
Steps
  1. Send an inbound A12 (Delete Bed Assignment) message to Avatar with 'Correct Unit / Room / Bed (Bed Assigned before the current Bed Assignment)' in segment ''PV1-3.1^3.2^3.3''.
  2. Validate the Filing Status is equal to "Err - Prior bed is reserved for (Client B) with a HIGH Priority.".
  3. Move Client B to 'Standard Priority' in same Unit/Room/Bed.
  4. Send an inbound A12 (Delete Bed Assignment) message to Avatar with 'Correct Unit / Room / Bed (Bed Assigned before the current Bed Assignment)' in segment ''PV1-3.1^3.2^3.3''.
  5. Validate the Filing Status is equal to "OK".
Topics
• HL7
Update 7 Summary | Details
Sliding Scale Insulin Orders - Qty and Qty Unit
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Order Code Setup
  • Orders This Episode
  • HL7 Connection Monitor
  • Launch RxConnect
  • RxConnect
  • Client Profile / Physicians Orders
Scenario 1: OE NX - Order Entry Console - Sliding Scale Insulin Orders with a template selected - ensure 'Qty' and 'Units' are sent via Avatar HL7 as "0 Units" and verify "0 Units' show in RxConnect
Specific Setup:
  • RxConnect must be configured to communicate with Avatar via Avatar HL7.
  • Must have 'Outbound Orders' configured.
  • Must have a pharmacy-type order code that has the 'Enable Sliding Scale Insulin Instructions' checkbox checked in 'Order Code Setup'. (HUMALOG 100 UNITS/1 ML SOLUTION INJECTION)
  • 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, and in the ‘Height’ and ‘Weight’ fields in the ‘Vitals Entry’ form.
Steps
  1. Select "Client A" and access the Order Entry Console.
  2. Create an order for "HUMALOG 100 UNITS/1 ML SOLUTION INJECTION" and ensure to select a 'Sliding Scale Instructions' template.
  3. Access the 'HL7 Connection Monitor' form.
  4. Select the "(Outbound) ORDERS-RXCONNECT" value in the 'Select Row' field and click [Show Transaction Log].
  5. Validate the 'HL7 Outbound Transaction Log' report is displayed.
  6. Find the message that is closest to the time in which the order was created.
  7. Validate the 'Event Type' is "ORM-O01" and that 'ID' contains "Client A's PATID".
  8. Click [View HL7 Message].
  9. Validate that segment 'ORC-7.1' contains "0&UNITS".
  10. Validate that segment 'RXO-2' contains "0" and 'RXO-4' contains "^UNITS".
  11. Close the report and the form.
  12. Access the 'Launch RxConnect' form and click [Launch RxConnect].
  13. Access 'Rx Summary' and select the hospital associated with the myAvatar application and click [Change and Resume].
  14. Find "Client A" and the order that was just created and right click on it and select "Process".
  15. Validate that 'Quantity' under order details contains "0 UNITS".
  16. Select the appropriate drug and validate that the 'Administer' field contains "0 UNITS".
  17. Continue processing the order.
Scenario 2: Client Profile/Physicians Orders - Sliding Scale Insulin Orders with a template selected - ensure 'Qty' and 'Units' are sent via Avatar HL7 as "0 Units" and verify "0 Units' show in RxConnect
Specific Setup:
  • RxConnect must be configured to communicate with Avatar via Avatar HL7.
  • Must have 'Outbound Orders' configured.
  • Must have a pharmacy-type order code that has the 'Enable Sliding Scale Insulin Instructions' checkbox checked in 'Order Code Setup'. (HUMALOG 100 UNITS/1 ML SOLUTION INJECTION)
  • 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, and in the ‘Height’ and ‘Weight’ fields in the ‘Vitals Entry’ form.
Steps
  1. Select "Client A" and access the 'Client Profile/Physicians Orders' form.
  2. Create an order for "HUMALOG 100 UNITS/1 ML SOLUTION INJECTION" and ensure to select a 'Sliding Scale Instructions' template.
  3. Access the 'HL7 Connection Monitor' form.
  4. Select the "(Outbound) ORDERS-RXCONNECT" value in the 'Select Row' field and click [Show Transaction Log].
  5. Validate the 'HL7 Outbound Transaction Log' report is displayed.
  6. Find the message that is closest to the time in which the order was created.
  7. Validate the 'Event Type' is "ORM-O01" and that 'ID' contains "Client A's PATID".
  8. Click [View HL7 Message].
  9. Validate that segment 'ORC-7.1' contains "0&UNITS".
  10. Validate that segment 'RXO-2' contains "0" and 'RXO-4' contains "^UNITS".
  11. Close the report and the form.
  12. Access the 'Launch RxConnect' form and click [Launch RxConnect].
  13. Access 'Rx Summary' and select the hospital associated with the myAvatar application and click [Change and Resume].
  14. Find "Client A" and the order that was just created and right click on it and select "Process".
  15. Validate that 'Quantity' under order details contains "0 UNITS".
  16. Select the appropriate drug and validate that the 'Administer' field contains "0 UNITS".
  17. Continue processing the order.
Topics
• HL7 • NX • Order Entry Console • RxConnect