Skip to main content

Avatar HL7 2024 Monthly Release 2024.01.00 Acceptance Tests

  1. Last updated
  2. Save as PDF
Update 3 Summary | Details
New form 'HL7 Facility Definition' is added
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • HL7 Facility Definition
  • Update Client Data
  • HL7 Connection Monitor
  • Order Entry Console
Scenario 1: Validate 'HL7 Facility Definition'
Steps
  1. Open the HL7 Facility Definition - Avatar PM / HL7 Interface / System Maintenance form.
  2. Verify the following fields are displayed on the form:
  3. 'HL7 Facility’
  4. Verify that only upper-case alphanumeric values are allowed (10 characters max).
  5. ‘Description’
  6. Free text. No restrictions.
  7. ‘Remove’
  8. If checked and the form is filed, then the selected facility will be deleted.
  9. ‘Associated Programs’
  10. Multi-select program dictionary (no call-intake programs)
  11. List will include inactive.
  12. ‘HL7 Facility ID’
  13. Verify that only alphanumeric values are allowed (10 characters only).
  14. Validate that any number of ‘facilities’ can be defined.
  15. Validate that the ‘HL7 Facility ID’ value does not need to be unique meaning multiple defined ‘facilities’ can share the same id value.
Scenario 2: Validate ADT message with different settings in 'HL7 Facility Definition'
Specific Setup:
  • An 'Outbound' ADT connection must exist that is configured with "FAC1" selected in the 'HL7 Facility Definition Supported' field with no sub system code supported.(Connection A)
  • An 'Outbound' ADT connection must exist that is configured with "FAC2" selected in the 'HL7 Facility Definition Supported' field with no sub system code supported. (Connection B)
  • An 'Outbound' ADT connection must exist that is configured with "FAC3" selected in the 'HL7 Facility Definition Supported' field with no sub system code supported. (Connection C)
  • An 'Outbound' ADT connection must exist that is configured with "FAC1", "FAC2", "FAC3" selected in the 'HL7 Facility Definition Supported' field with no sub system code supported. (Connection D)
  • Three facilities must be defined in the 'HL7 Facility Definition' form. (Fac1 - Psych facilities, Fac2 - Substance Abuse facilities, Fac3 - Miscellaneous facilities)
  • A client has an inpatient episode (Inp. Adult Psych.) and an outpatient episode (O.P. Adult Psych).
Steps
  1. Select "Client A" and access the 'Update Client Data' form.
  2. Make any change on the form and click [Submit].
  3. Access the 'HL7 Connection Monitor' form.
  4. Select "Connection A" from the 'Select Row' field.
  5. Click [Show Transaction Log].
  6. Validate there is a transaction for 'Event type' = "ADT^A08".
  7. Click the 'View HL7 Message' link.
  8. Validate 'MSH-4', 'PV1-3.4' and 'PV1-6.4' contain "HL7 Facility ID".
  9. Select "Connection B" from the 'Select Row' field.
  10. Click [Show Transaction Log].
  11. Validate there is no new transaction for 'Event type' = "ADT^A08".
  12. Select "Connection C" from the 'Select Row' field.
  13. Click [Show Transaction Log].
  14. Validate there is no new transaction for 'Event type' = "ADT^A08".
  15. Select "Connection D" from the 'Select Row' field.
  16. Click [Show Transaction Log].
  17. Validate there is a transaction for 'Event type' = "ADT^A08".
  18. Click the 'View HL7 Message' link.
  19. Validate 'MSH-4', 'PV1-3.4' and 'PV1-6.4' contain "HL7 Facility ID".
Scenario 3: Validate Order message with different settings in 'HL7 Facility Definition'
Specific Setup:
  • Three facilities must be defined in the 'HL7 Facility Definition' form. (Fac1 - Psych facilities, Fac2 - Substance Abuse facilities, Fac3 - Miscellaneous facilities)
  • An 'Outbound' Orders connection must exist that is configured with "FAC1" selected in the 'HL7 Facility Definition Supported' field with no sub system code supported.(Connection A)
  • An 'Outbound' Orders connection must exist that is configured with "FAC2" selected in the 'HL7 Facility Definition Supported' field with no sub system code supported. (Connection B)
  • An 'Outbound' Orders connection must exist that is configured with "FAC3" selected in the 'HL7 Facility Definition Supported' field with no sub system code supported. (Connection C)
  • An 'Outbound' Orders connection must exist that is configured with "FAC1", "FAC2", "FAC3" selected in the 'HL7 Facility Definition Supported' field with no sub system code supported. (Connection D)
  • A client has an inpatient episode (Inp. Adult Psych.) and an outpatient episode (O.P. Adult Psych).
Steps
  1. Select "Client A" and access the Order Entry Console.
  2. Create an order for a pharmacy-type order code.
  3. Access the 'HL7 Connection Monitor' form.
  4. Select "Connection A" from the 'Select Row' field.
  5. Click [Show Transaction Log].
  6. Validate there is a transaction for 'Event type' = "ORM^O01".
  7. Click the 'View HL7 Message' link.
  8. Validate 'MSH-4', 'PV1-3.4' and 'PV1-6.4' contain "HL7 Facility ID".
  9. Select "Connection B" from the 'Select Row' field.
  10. Click [Show Transaction Log].
  11. Validate there is no new transaction for 'Event type' = "ORM^O01".
  12. Click the 'View HL7 Message' link.
  13. Validate 'MSH-4', 'PV1-3.4' and 'PV1-6.4' contain "HL7 Facility ID".
  14. Select "Connection C" from the 'Select Row' field.
  15. Click [Show Transaction Log].
  16. Validate there is no new transaction for 'Event type' = "ORM^O01".
  17. Click the 'View HL7 Message' link.
  18. Validate 'MSH-4', 'PV1-3.4' and 'PV1-6.4' contain "HL7 Facility ID".
  19. Select "Connection D" from the 'Select Row' field.
  20. Click [Show Transaction Log].
  21. Validate there is a transaction for 'Event type' = "ORM^O01".
  22. Click the 'View HL7 Message' link.
  23. Validate 'MSH-4', 'PV1-3.4' and 'PV1-6.4' contain "HL7 Facility ID".
Topics
• HL7
 

Avatar_HL7_2024_Monthly_Release_2024.01.00_Details.csv