Skip to main content

Avatar eMAR 2023 Update 16

  1. Last updated
  2. Save as PDF

Product Requirements and Recommendations

Avatar CWS required
Avatar eMAR required
RADplus required

Recommended Update Level

Avatar CWS 2023 Monthly Release 2023.04.00
Avatar eMAR 2023 Monthly Release 2023.04.00
Avatar OE 2023 Update 17
RADplus 2023 Monthly Release 2023.04.00

Product Update Description

The eMAR NX 'Administration Follow-Up' dialog is enhanced to support 'Require Result Text / Comment on eMAR Follow-Up', which can be specified per 'Order Code' via the Avatar OE 'Order Code Setup' form, as well per 'Order Type' and 'Reason Code' via an extended attribute that is available for each of those dictionaries. (Note: The extended attributes for 'Order Type' and 'Reason Code Setup' were introduced via Avatar OE 2023 Update 17.)

Required Updates

None

Included Updates

9, 10, 11, 15

Details
NEW0 CHANGED0 FIXED1
Fixed (1)
eMAR NX - Result/Comment field in 'Administration Follow-Up'
The eMAR NX 'Administration Event - Results' dialog (for Follow-ups) is enhanced to support the 'Require Result Text On Administration Event Result' value from 'Order Code Setup' as well as the 'Require Result Text / Comment on eMAR Follow-Up' extended attributes introduced via Avatar OE 2023 Update 17.
Topics
• eMAR NX • Order Entry Console
 
Acceptance Tests
AV-87507 Summary | Details
eMAR NX - Result/Comment field in 'Administration Follow-Up'
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Dictionary Update (CWS)
  • eMAR
  • Order Code Setup
  • Orders This Episode
Scenario 1: eMAR NX - Follow-Up 'Result/Comment' field when 'Require Result Text On Administration Event Result' is set to "No" for Pharmacy order type
Specific Setup:
  • The ‘(570) Require Result Text / Comment on Avatar eMAR Follow-up’ extended attribute must be set to “Yes" in the Order Entry Tabled Files ‘(500) Order Types’ dictionary for “Pharmacy”.
  • The ‘(571) Require Result Text / Comment on Avatar eMAR Follow-up’ extended attribute must be set to “Yes" in the Order Entry Tabled Files ‘(504) Reason Code Setup’ dictionary for dictionary code "2 - For pain or fever".
  • The 'Require Result Text On Administration Event Result' field in the 'Order Code Setup' form must be set to "No" for a pharmacy-type order code. (Order Code A)
  • 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 "Order Code A" using a 'Frequency Code' with no administration times associated with it and no 'Reason Code' selected.
  3. Access 'eMAR NX'.
  4. Validate an order for "Order Code A" is displayed with no administration times.
  5. Validate there is a [Due] in the 'Overdue/Unscheduled' column.
  6. Click [Scan Client] and complete the 'Wristband Scan Override'.
  7. Perform 'Order Acknowledgement' and 'Medication Education' for the order.
  8. Administer the order with a successful administration event.
  9. Validate a [Follow Up] is displayed in the 'Overdue/Unscheduled' column for "Order Code A".
  10. Click [Follow Up].
  11. Validate the 'Administration Follow-Up' dialog is displayed and that the 'Comment' field is required.
  12. Populate the 'Comment' field, click [Save], and validate [Follow Up] is not displayed.
  13. Access the Order Entry Console.
  14. Select the order created for "Order Code A" and click [Modify].
  15. Select "For pain or fever" in the 'Reason' field and enter any value in the 'Reason Text' field and click [Add to Scratchpad] and [Sign].
  16. Access 'eMAR NX'.
  17. Validate the original order for "Order Code A" appears under 'Discontinued' and that the new order for "Order Code A" is displayed under 'Scheduled' with no administration times under the current date.
  18. Validate there is a [Due] in the 'Overdue/Unscheduled' column.
  19. Perform 'Order Acknowledgement' and 'Medication Education' on the order.
  20. Administer the order with a successful administration event.
  21. Validate a [Follow Up] is displayed in the 'Overdue/Unscheduled' column for "Order Code A".
  22. Click [Follow Up].
  23. Validate the 'Administration Follow-Up' dialog is displayed and that the 'Comment' field is required.
  24. Populate the 'Comment' field, click [Save], and validate [Follow Up] is not displayed.
Scenario 2: eMAR NX - Follow-Up 'Result/Comment' field when 'Require Result Text On Administration Event Result' is set to "Yes" for Pharmacy order type.
Specific Setup:
  • The ‘(570) Require Result Text / Comment on Avatar eMAR Follow-up’ extended attribute must be set to "No" in the Order Entry Tabled Files ‘(500) Order Types’ dictionary for “Pharmacy”.
  • The ‘(571) Require Result Text / Comment on Avatar eMAR Follow-up’ extended attribute must be set to “No" in the Order Entry Tabled Files ‘(504) Reason Code Setup’ dictionary for "2 - For pain or fever".
  • The 'Require Result Text on Administration Event Result' field in the 'Order Code Setup' form must be set to "Yes" for a pharmacy-type order code. (Order Code A)
  • 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 "Order Code A" using a 'Frequency Code' with no administration times associated with it and no 'Reason Code' selected.
  3. Access 'eMAR NX'.
  4. Validate an order for "Order Code A" is displayed with no administration times.
  5. Validate there is a [Due] in the 'Overdue/Unscheduled' column.
  6. Click [Scan Client] and complete the 'Wristband Scan Override'.
  7. Perform 'Order Acknowledgement' and 'Medication Education' for the order.
  8. Administer the order with a successful administration event.
  9. Validate a [Follow Up] is displayed in the 'Overdue/Unscheduled' column for "Order Code A".
  10. Click [Follow Up].
  11. Validate the 'Administration Follow-Up' dialog is displayed and that the 'Comment' field is not required.
  12. Click [Save] and validate [Follow Up] is not displayed.
  13. Access the Order Entry Console.
  14. Select the order for "Order Code A" and click [Modify].
  15. Select "For pain or fever" in the 'Reason' field and enter any value in the 'Reason Text' field and click [Add to Scratchpad] and [Sign].
  16. Access 'eMAR NX'.
  17. Validate the original order for "Order Code A" appears under 'Discontinued' and that the new order for "Order Code A" is displayed under 'Scheduled' with no administration times under the current date.
  18. Validate there is a [Due] in the 'Overdue/Unscheduled' column.
  19. Perform 'Order Acknowledgement' and 'Medication Education' on the order.
  20. Administer the order with a successful administration event.
  21. Validate a [Follow Up] is displayed in the 'Overdue/Unscheduled' column for "Order Code A".
  22. Click [Follow Up].
  23. Validate the 'Administration Follow-Up' dialog is displayed and that the 'Comment' field is not required.
  24. Click [Save] and validate [Follow Up] is not displayed.
Scenario 3: eMAR NX - Follow-Up 'Result/Comment' field when 'Require Result Text On Administration Event Result' is set to "No" and extended attributes are set to "YX" and "Yes"
Specific Setup:
  • The ‘(570) Require Result Text / Comment on Avatar eMAR Follow-up’ extended attribute must be set to “Yes, but allow exceptions based on the 'Reason Code' and/or 'Order Code'” in the Order Entry Tabled Files ‘(500) Order Types’ dictionary for “Pharmacy”.
  • The ‘(571) Require Result Text / Comment on Avatar eMAR Follow-up’ extended attribute must be set to “Yes" in the Order Entry Tabled Files ‘(504) Reason Code Setup’ dictionary for dictionary code "2 - For pain or fever".
  • The 'Require Result Text On Administration Event Result' field in the 'Order Code Setup' form must be set to "No" for a pharmacy-type order code. (Order Code A)
  • 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 "Order Code A" using a 'Frequency Code' with no administration times associated with it and no 'Reason Code' selected.
  3. Access 'eMAR NX'.
  4. Validate an order for "Order Code A" is displayed with no administration times.
  5. Validate there is a [Due] in the 'Overdue/Unscheduled' column.
  6. Click [Scan Client] and complete the 'Wristband Scan Override'.
  7. Perform 'Order Acknowledgement' and 'Medication Education' for the order.
  8. Administer the order with a successful administration event.
  9. Validate a [Follow Up] is displayed in the 'Overdue/Unscheduled' column for "Order Code A".
  10. Click [Follow Up].
  11. Validate the 'Administration Follow-Up' dialog is displayed and that the 'Comment' field is not required.
  12. Click [Save] and validate [Follow Up] is not displayed.
  13. Access the Order Entry Console.
  14. Select the order for "Order Code A" and click [Modify].
  15. Select "For pain or fever" in the 'Reason' field and enter any value in the 'Reason Text' field and click [Add to Scratchpad] and [Sign].
  16. Access 'eMAR NX'.
  17. Validate the original order for "Order Code A" appears under 'Discontinued' and that the new order for "Order Code A" is displayed under 'Scheduled' with no administration times under the current date.
  18. Validate there is a [Due] in the 'Overdue/Unscheduled' column.
  19. Perform 'Order Acknowledgement' and 'Medication Education' on the order.
  20. Administer the order with a successful administration event.
  21. Validate a [Follow Up] is displayed in the 'Overdue/Unscheduled' column for "Order Code A".
  22. Click [Follow Up].
  23. Validate the 'Administration Follow-Up' dialog is displayed and that the 'Comment' field is required.
  24. Populate the 'Comment' field and click [Save].
  25. Validate [Follow Up] is not displayed.
Scenario 4: eMAR NX - Follow-Up 'Result/Comment' field when 'Require Result Text On Administration Event Result' is set to "Yes" and extended attributes are set to "NX" and "No"
Specific Setup:
  • The ‘(570) Require Result Text / Comment on Avatar eMAR Follow-up’ extended attribute must be set to “No, but allow exceptions based on the 'Reason Code' and/or 'Order Code'” in the Order Entry Tabled Files ‘(500) Order Types’ dictionary for “Pharmacy”.
  • The ‘(571) Require Result Text / Comment on Avatar eMAR Follow-up’ extended attribute must be set to "No" in the Order Entry Tabled Files ‘(504) Reason Code Setup’ dictionary for dictionary code "2 - For pain or fever".
  • The 'Require Result Text On Administration Event Result' field in the 'Order Code Setup' form must be set to "Yes" for a pharmacy-type order code. (Order Code A)
  • 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 "Order Code A" using a 'Frequency Code' with no administration times associated with it and no 'Reason Code' selected.
  3. Access 'eMAR NX'.
  4. Validate an order for "Order Code A" is displayed with no administration times.
  5. Validate there is a [Due] in the 'Overdue/Unscheduled' column.
  6. Click [Scan Client] and complete the 'Wristband Scan Override'.
  7. Perform 'Order Acknowledgement' and 'Medication Education' for the order.
  8. Administer the order with a successful administration event.
  9. Validate a [Follow Up] is displayed in the 'Overdue/Unscheduled' column for "Order Code A".
  10. Click [Follow Up].
  11. Validate the 'Administration Follow-Up' dialog is displayed and that the 'Comment' field is required.
  12. Populate the 'Comment' field, click [Save], and validate [Follow Up] is not displayed.
  13. Access the Order Entry Console.
  14. Select the order created for "Order Code A" and click [Modify].
  15. Select "For pain or fever" in the 'Reason' field and enter any value in the 'Reason Text' field and click [Add to Scratchpad] and [Sign].
  16. Access 'eMAR NX'.
  17. Validate the original order for "Order Code A" appears under 'Discontinued' and that the new order for "Order Code A" is displayed under 'Scheduled' with no administration times under the current date.
  18. Validate there is a [Due] in the 'Overdue/Unscheduled' column.
  19. Perform 'Order Acknowledgement' and 'Medication Education' on the order.
  20. Administer the order with a successful administration event.
  21. Validate a [Follow Up] is displayed in the 'Overdue/Unscheduled' column for "Order Code A".
  22. Click [Follow Up].
  23. Validate the 'Administration Follow-Up' dialog is displayed and that the 'Comment' field is not required.
  24. Click [Save] and validate [Follow Up] is not displayed.
Scenario 5: eMAR NX - Follow-Up 'Result/Comment' field when 'Require Result Text On Administration Event Result' is set to "Yes" and extended attributes are set to "YX" and "YX"
Specific Setup:
  • The ‘(570) Require Result Text / Comment on Avatar eMAR Follow-up’ extended attribute must be set to “Yes, but allow exceptions based on the 'Reason Code' and/or 'Order Code'” in the Order Entry Tabled Files ‘(500) Order Types’ dictionary for “Pharmacy”.
  • The ‘(571) Require Result Text / Comment on Avatar eMAR Follow-up’ extended attribute must be set to "Yes, but allow exceptions based on the 'Order Code'" in the Order Entry Tabled Files ‘(504) Reason Code Setup’ dictionary for dictionary code "2 - For pain or fever".
  • The 'Require Result Text On Administration Event Result' field in the 'Order Code Setup' form must be set to "Yes" for a pharmacy-type order code. (Order Code A)
  • 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 "Order Code A" using a 'Frequency Code' with no administration times associated with it and no 'Reason Code' selected.
  3. Access 'eMAR NX'.
  4. Validate an order for "Order Code A" is displayed with no administration times.
  5. Validate there is a [Due] in the 'Overdue/Unscheduled' column.
  6. Click [Scan Client] and complete the 'Wristband Scan Override'.
  7. Perform 'Order Acknowledgement' and 'Medication Education' for the order.
  8. Administer the order with a successful administration event.
  9. Validate a [Follow Up] is displayed in the 'Overdue/Unscheduled' column for "Order Code A".
  10. Click [Follow Up].
  11. Validate the 'Administration Follow-Up' dialog is displayed and that the 'Comment' field is required.
  12. Populate the 'Comment' field, click [Save], and validate [Follow Up] is not displayed.
  13. Access the Order Entry Console.
  14. Select the order created for "Order Code A" and click [Modify].
  15. Select "For pain or fever" in the 'Reason' field and enter any value in the 'Reason Text' field and click [Add to Scratchpad] and [Sign].
  16. Access 'eMAR NX'.
  17. Validate the original order for "Order Code A" appears under 'Discontinued' and that the new order for "Order Code A" is displayed under 'Scheduled' with no administration times under the current date
  18. Validate there is a [Due] in the 'Overdue/Unscheduled' column.
  19. Perform 'Order Acknowledgement' and 'Medication Education' on the order.
  20. Administer the order with a successful administration event.
  21. Validate a [Follow Up] is displayed in the 'Overdue/Unscheduled' column for "Order Code A".
  22. Click [Follow Up].
  23. Validate the 'Administration Follow-Up' dialog is displayed and that the 'Comment' field is required.
  24. Populate the 'Comment' field, click [Save], and validate [Follow Up] is not displayed.
Scenario 6: eMAR NX - Follow-Up 'Result/Comment' field when 'Require Result Text On Administration Event Result' is set to "No" and extended attributes are set to "NX" and "NX"
Specific Setup:
  • The ‘(570) Require Result Text / Comment on Avatar eMAR Follow-up’ extended attribute must be set to “No, but allow exceptions based on the 'Reason Code' and/or 'Order Code'” in the Order Entry Tabled Files ‘(500) Order Types’ dictionary for “Pharmacy”.
  • The ‘(571) Require Result Text / Comment on Avatar eMAR Follow-up’ extended attribute must be set to “No, but allow exceptions based on the 'Order Code'" in the Order Entry Tabled Files ‘(504) Reason Code Setup’ dictionary for dictionary code "2 - For pain or fever".
  • The 'Require Result Text on Administration Event Result' field in the 'Order Code Setup' form must be set to "No" for a pharmacy-type order code. (Order Code A)
  • 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 "Order Code A" using a 'Frequency Code' with no administration times associated with it and no 'Reason Code' selected.
  3. Access 'eMAR NX'.
  4. Validate an order for "Order Code A" is displayed with no administration times.
  5. Validate there is a [Due] in the 'Overdue/Unscheduled' column.
  6. Click [Scan Client] and complete the 'Wristband Scan Override'.
  7. Perform 'Order Acknowledgement' and 'Medication Education' for the order.
  8. Administer the order with a successful administration event.
  9. Validate a [Follow Up] is displayed in the 'Overdue/Unscheduled' column for "Order Code A".
  10. Click [Follow Up].
  11. Validate the 'Administration Follow-Up' dialog is displayed and that the 'Comment' field is not required.
  12. Click [Save] and validate [Follow Up] is not displayed.
  13. Access the Order Entry Console.
  14. Select the order created for "Order Code A" and click [Modify].
  15. Select "For pain or fever" in the 'Reason' field and enter any value in the 'Reason Text' field and click [Add to Scratchpad] and [Sign].
  16. Access 'eMAR NX'.
  17. Validate the original order for "Order Code A" appears under 'Discontinued' and that the new order for "Order Code A" is displayed under 'Scheduled' with no administration times under the current date.
  18. Validate there is a [Due] in the 'Overdue/Unscheduled' column.
  19. Perform 'Order Acknowledgement' and 'Medication Education' on the order.
  20. Administer the order with a successful administration event.
  21. Validate a [Follow Up] is displayed in the 'Overdue/Unscheduled' column for "Order Code A".
  22. Click [Follow Up].
  23. Validate the 'Administration Follow-Up' dialog is displayed and that the 'Comment' field is not required.
  24. Click [Save] and validate [Follow Up] is not displayed.
Topics
• eMAR NX • Order Entry Console