Skip to main content

Avatar eMAR 2023 Update 8

  1. Last updated
  2. Save as PDF

Product Requirements / Recommendations

Avatar CWS required
Avatar eMAR required
RADplus required

Recommended Update Level

Avatar OE 2023 Update 17

Product Update Form Description

The eMAR 'Administration Event - Results' dialog (for Follow-ups) is enhanced to support the 'Require Result Text / Comment on eMAR Follow-Up' extended attributes introduced via Avatar OE 2023 Update 17.

Included Updates

None

Required Updates

None

Details
NEW1 CHANGED0 FIXED0
New (1)
eMAR NX - 'Results' text for follow-ups
The eMAR 'Administration Event - Results' dialog (for Follow-ups) is enhanced to support the 'Require Result Text / Comment on eMAR Follow-Up' extended attributes introduced via Avatar OE 2023 Update 17.
Value Added: Adds the ability to require the 'Result' field for follow-ups.
Topics
• Avatar eMAR • NX
 
Acceptance Tests
AV-87999 Summary | Details
eMAR NX - 'Results' text for follow-ups
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Dictionary Update (CWS)
  • Order Code Setup
  • Orders This Episode
Scenario 1: eMAR - Follow-Up 'Result' field when extended attribute off of 'Order Type' is set to "Yes".
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 following extended attributes must be set in the Order Entry Tabled Files ‘(504) Reason Code Setup’ dictionary for dictionary code "2 - For pain or fever”:
  • The '(537) Time Interval For eMAR Follow-Up Reminder (Minutes)' extended attribute must not contain a value.
  • The '(571) Require Result Text / Comment on Avatar eMAR Follow-up' extended attribute must be set to "No" or "No, but allow exceptions based on the 'Order Code'"
  • The 'Require Result Text/Comment on Avatar eMAR Follow-up' 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 the 'eMAR' widget.
  4. Validate an order for "Order Code A" is displayed with no administration times under the current date.
  5. Perform 'Order Acknowledgement' and 'Client Education' on the order.
  6. Click 'Click here to provide override reason' and select a value in the 'Please provide a reason for not scanning the client wristband' field and click [Ok].
  7. Administer the order with a successful administration event.
  8. Validate a follow-up row for "Order Code A" exists.
  9. Double click the 'Follow-up' cell under the current date.
  10. Validate the 'Administration Record - Results' dialog is displayed and that the 'Result' field is required.
  11. Access the Order Entry Console.
  12. Create a second order for "Order Code A" using a 'Frequency Code with no administration times associated with it and select a 'Reason' of "For pain or fever".
  13. Access the 'eMAR' widget.
  14. Validate an order for "Order Code A" is displayed with no administration times under the current date.
  15. Perform 'Order Acknowledgement' and 'Client Education' on the order.
  16. Click 'Click here to provide override reason' and select a value in the 'Please provide a reason for not scanning the client wristband' field and click [Ok].
  17. Administer the order with a successful administration event.
  18. Validate a follow-up row for "Order Code A" exists.
  19. Double click the 'Follow-up' cell under the current date.
  20. Validate the 'Administration Record - Results' dialog is displayed and that the 'Result' field is required.
Scenario 2: eMAR - Follow-Up 'Result' field when extended attribute off of 'Order Type' is set to "No".
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 following extended attributes must be set in the Order Entry Tabled Files ‘(504) Reason Code Setup’ dictionary for dictionary code "2 - For pain or fever”:
  • The '(537) Time Interval For eMAR Follow-Up Reminder (Minutes)' extended attribute must not contain a value.
  • The '(571) Require Result Text / Comment on Avatar eMAR Follow-up' extended attribute must be set to "Yes" or "Yes, but allow exceptions based on the 'Order Code'"
  • The 'Require Result Text/Comment on Avatar eMAR Follow-up' 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 the 'eMAR' widget.
  4. Validate an order for "Order Code A" is displayed with no administration times under the current date.
  5. Perform 'Order Acknowledgement' and 'Client Education' on the order.
  6. Click 'Click here to provide override reason' and select a value in the 'Please provide a reason for not scanning the client wristband' field and click [Ok].
  7. Administer the order with a successful administration event.
  8. Validate a follow-up row for "Order Code A" exists.
  9. Double click the 'Follow-up' cell under the current date.
  10. Validate the 'Administration Record - Results' dialog is displayed and that the 'Result' field is not required.
  11. Access the Order Entry Console.
  12. Create a second order for "Order Code A" using a 'Frequency Code with no administration times associated with it and select a 'Reason' of "For pain or fever".
  13. Access the 'eMAR' widget.
  14. Validate an order for "Order Code A" is displayed with no administration times under the current date.
  15. Perform 'Order Acknowledgement' and 'Client Education' on the order.
  16. Click 'Click here to provide override reason' and select a value in the 'Please provide a reason for not scanning the client wristband' field and click [Ok].
  17. Administer the order with a successful administration event.
  18. Validate a follow-up row for "Order Code A" exists.
  19. Double click the 'Follow-up' cell under the current date.
  20. Validate the 'Administration Record - Results' dialog is displayed and that the 'Result' field is not required.
Scenario 3: eMAR - Follow-Up 'Result' field when extended attribute off of 'Reason Code Setup' is set to "Yes".
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 'Reason Code' and/or 'Order Code'” in the Order Entry Tabled Files ‘(500) Order Types’ dictionary for “Pharmacy”.
  • The following extended attributes must be set in the Order Entry Tabled Files ‘(504) Reason Code Setup’ dictionary for dictionary code "2 - For pain or fever”:
  • The '(537) Time Interval For eMAR Follow-Up Reminder (Minutes)' extended attribute must not contain a value.
  • The '(571) Require Result Text / Comment on Avatar eMAR Follow-up' extended attribute must be set to "Yes".
  • The 'Require Result Text/Comment on Avatar eMAR Follow-up' 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 administration times associated with it and select a 'Reason' of "For pain or fever"
  3. Access the 'eMAR' widget.
  4. Validate an order for "Order Code A" is displayed with administration times under the current date.
  5. Perform 'Order Acknowledgement' and 'Client Education' on the order.
  6. Click 'Click here to provide override reason' and select a value in the 'Please provide a reason for not scanning the client wristband' field and click [Ok].
  7. Administer the order with a successful administration event.
  8. Validate a follow-up row for "Order Code A" exists.
  9. Double click the 'Follow-up' cell under the current date.
  10. Validate the 'Administration Record - Results' dialog is displayed and that the 'Result' field is required.
  11. Access the Order Entry Console.
  12. Create a second order for "Order Code A" using a 'Frequency Code with no administration times associated with it and no 'Reason Code' selected.
  13. Access the 'eMAR' widget.
  14. Validate a second order for "Order Code A" is displayed with administration times under the current date.
  15. Perform 'Order Acknowledgement' and 'Client Education' on the order.
  16. Click 'Click here to provide override reason' and select a value in the 'Please provide a reason for not scanning the client wristband' field and click [Ok].
  17. Administer the order with a successful administration event.
  18. Validate a follow-up row for "Order Code A" exists.
  19. Double click the 'Follow-up' cell under the current date.
  20. Validate the 'Administration Record - Results' dialog is displayed and that the 'Result' field is not required.
Scenario 4: eMAR - Follow-Up 'Result' field when extended attribute off of 'Reason Code Setup' is set to "No".
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 'Reason Code' and/or 'Order Code'” in the Order Entry Tabled Files ‘(500) Order Types’ dictionary for “Pharmacy”.
  • The following extended attributes must be set in the Order Entry Tabled Files ‘(504) Reason Code Setup’ dictionary for dictionary code "2 - For pain or fever”:
  • The '(537) Time Interval For eMAR Follow-Up Reminder (Minutes)' extended attribute must not contain a value.
  • The '(571) Require Result Text / Comment on Avatar eMAR Follow-up' extended attribute must be set to "No".
  • The 'Require Result Text/Comment on Avatar eMAR Follow-up' 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 the 'eMAR' widget.
  4. Validate an order for "Order Code A" is displayed with no administration times under the current date.
  5. Perform 'Order Acknowledgement' and 'Client Education' on the order.
  6. Click 'Click here to provide override reason' and select a value in the 'Please provide a reason for not scanning the client wristband' field and click [Ok].
  7. Administer the order with a successful administration event.
  8. Validate a follow-up row for "Order Code A" exists.
  9. Double click the 'Follow-up' cell under the current date.
  10. Validate the 'Administration Record - Results' dialog is displayed and that the 'Result' field is required.
  11. Access the Order Entry Console.
  12. Select the order created for "Order Code A" and click [Modify].
  13. 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].
  14. Access the 'eMAR' widget.
  15. Validate a second order for "Order Code A" is displayed with no administration times under the current date and that the original order is discontinued.
  16. Perform 'Order Acknowledgement' and 'Client Education' on the order.
  17. Click 'Click here to provide override reason' and select a value in the 'Please provide a reason for not scanning the client wristband' field and click [Ok].
  18. Administer the order with a successful administration event.
  19. Validate a follow-up row for "Order Code A" exists.
  20. Double click the 'Follow-up' cell under the current date.
  21. Validate the 'Administration Record - Results' dialog is displayed and that the 'Result' field is not required.
Scenario 5: eMAR - Follow-Up 'Result' field when 'Require Result Text/Comment on Avatar eMAR Follow-up' is set to "No".
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 'Reason Code' and/or 'Order Code'” in the Order Entry Tabled Files ‘(500) Order Types’ dictionary for “Pharmacy”.
  • The following extended attributes must be set in the Order Entry Tabled Files ‘(504) Reason Code Setup’ dictionary for dictionary code "2 - For pain or fever”:
  • The '(537) Time Interval For eMAR Follow-Up Reminder (Minutes)' extended attribute must not contain a value.
  • 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'".
  • The 'Require Result Text/Comment on Avatar eMAR Follow-up' 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 the 'eMAR' widget.
  4. Validate an order for "Order Code A" is displayed with no administration times under the current date.
  5. Perform 'Order Acknowledgement' and 'Client Education' on the order.
  6. Click 'Click here to provide override reason' and select a value in the 'Please provide a reason for not scanning the client wristband' field and click [Ok].
  7. Administer the order with a successful administration event.
  8. Validate a follow-up row for "Order Code A" exists.
  9. Double click the 'Follow-up' cell under the current date.
  10. Validate the 'Administration Record - Results' dialog is displayed and that the 'Result' field is not required.
  11. Access the Order Entry Console.
  12. Select the order created for "Order Code A" and click [Modify].
  13. 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].
  14. Access the 'eMAR' widget.
  15. Validate a second order for "Order Code A" is displayed with no administration times under the current date and that the original order is discontinued.
  16. Perform 'Order Acknowledgement' and 'Client Education' on the order.
  17. Click 'Click here to provide override reason' and select a value in the 'Please provide a reason for not scanning the client wristband' field and click [Ok].
  18. Administer the order with a successful administration event.
  19. Validate a follow-up row for "Order Code A" exists.
  20. Double click the 'Follow-up' cell under the current date.
  21. Validate the 'Administration Record - Results' dialog is displayed and that the 'Result' field is not required.
Scenario 6: eMAR - Follow-Up 'Result' field when 'Require Result Text/Comment on Avatar eMAR Follow-up' is set to "Yes".
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 'Reason Code' and/or 'Order Code'” in the Order Entry Tabled Files ‘(500) Order Types’ dictionary for “Pharmacy”.
  • The following extended attributes must be set in the Order Entry Tabled Files ‘(504) Reason Code Setup’ dictionary for dictionary code "2 - For pain or fever”:
  • The '(537) Time Interval For eMAR Follow-Up Reminder (Minutes)' extended attribute must not contain a value.
  • 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'".
  • The 'Require Result Text/Comment on Avatar eMAR Follow-up' 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 the 'eMAR' widget.
  4. Validate an order for "Order Code A" is displayed with no administration times under the current date.
  5. Perform 'Order Acknowledgement' and 'Client Education' on the order.
  6. Click 'Click here to provide override reason' and select a value in the 'Please provide a reason for not scanning the client wristband' field and click [Ok].
  7. Administer the order with a successful administration event.
  8. Validate a follow-up row for "Order Code A" exists.
  9. Double click the 'Follow-up' cell under the current date.
  10. Validate the 'Administration Record - Results' dialog is displayed and that the 'Result' field is required.
  11. Access the Order Entry Console.
  12. Select the order created for "Order Code A" and click [Modify].
  13. 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].
  14. Access the 'eMAR' widget.
  15. Validate a second order for "Order Code A" is displayed with no administration times under the current date and that the original order is discontinued.
  16. Perform 'Order Acknowledgement' and 'Client Education' on the order.
  17. Click 'Click here to provide override reason' and select a value in the 'Please provide a reason for not scanning the client wristband' field and click [Ok].
  18. Administer the order with a successful administration event.
  19. Validate a follow-up row for "Order Code A" exists.
  20. Double click the 'Follow-up' cell under the current date.
  21. Validate the 'Administration Record - Results' dialog is displayed and that the 'Result' field is required.
Scenario 7: eMAR - Follow-Up 'Result' field is required when extended attribute off of 'Reason Code Setup' is set to "No" for one reason code and "Yes" for another - Multiple Reasons
Specific Setup:
  • The following extended attributes must be set in Order Entry Tabled Files '(500) Order Types' dictionary for "Pharmacy":
  • The '(548) Enable Multiple Reasons at Order Entry' extended attribute must be set to "Yes".
  • The ‘(570) Require Result Text / Comment on Avatar eMAR Follow-up’ extended attribute must be set to “Yes, but allow exceptions based on 'Reason Code'".
  • The following extended attributes must be set in the Order Entry Tabled Files ‘(504) Reason Code Setup’ dictionary for dictionary code "1 - agitation”:
  • The '(537) Time Interval For eMAR Follow-Up Reminder (Minutes)' extended attribute must not contain a value.
  • The '(571) Require Result Text / Comment on Avatar eMAR Follow-up' extended attribute must be set to "Yes".
  • The following extended attributes must be set in the Order Entry Tabled Files ‘(504) Reason Code Setup’ dictionary for dictionary code "2 - For pain or fever”:
  • The '(537) Time Interval For eMAR Follow-Up Reminder (Minutes)' extended attribute must not contain a value.
  • The '(571) Require Result Text / Comment on Avatar eMAR Follow-up' extended attribute must be set to "No".
  • The 'Require Result Text/Comment on Avatar eMAR Follow-up' field in the 'Order Code Setup' form does not have a value selected for a pharmacy-type order code. (Order Code A)
  • Please log out of the application and log back in after completing the above configuration.
  • 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 selecting "For agitation" and "For pain or fever" in the 'Multiple Reasons' dialog.
  3. Access the 'eMAR' widget.
  4. Validate an order for "Order Code A" is displayed with no administration times under the current date.
  5. Perform 'Order Acknowledgement' and 'Client Education' on the order.
  6. Click 'Click here to provide override reason' and select a value in the 'Please provide a reason for not scanning the client wristband' field and click [Ok].
  7. Administer the order with a successful administration event.
  8. Validate a follow-up row for "Order Code A" exists.
  9. Double click the 'Follow-up' cell under the current date.
  10. Validate the 'Administration Record - Results' dialog is displayed and that the 'Result' field is required.
Scenario 8: eMAR - Dietary order - Follow-Up 'Results' field
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 'Reason Code' and/or 'Order Code'” in the Order Entry Tabled Files ‘(500) Order Types’ dictionary for “Dietary”.
  • The following extended attributes must be set in the Order Entry Tabled Files ‘(504) Reason Code Setup’ dictionary for dictionary code "2 - For pain or fever”:
  • The '(537) Time Interval For eMAR Follow-Up Reminder (Minutes)' extended attribute must not contain a value.
  • The '(571) Require Result Text / Comment on Avatar eMAR Follow-up' extended attribute must be set to "No".
  • The 'Require Result Text/Comment on Avatar eMAR Follow-up' field in the 'Order Code Setup' form must be set to "Yes" for a dietary-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' without administration times associated with it and do not select a value in the 'Reason' field.
  3. Access the 'eMAR' widget.
  4. Validate an order for "Order Code A" is displayed with no administration times under the current date.
  5. Perform 'Order Acknowledgement' and 'Client Education' on the order.
  6. Administer the order with a successful administration event.
  7. Double click the administered cell.
  8. Validate the 'Administration Record - Results' dialog is displayed and that the 'Result' field is required.
  9. Access the Order Entry Console.
  10. Create a second order for "Order Code A" using a 'Frequency Code with no administration times associated with it and select "For pain or fever" in the 'Reason' field and enter 'Reason Text'.
  11. Access the 'eMAR' widget.
  12. Validate a second order for "Order Code A" is displayed with administration times under the current date.
  13. Perform 'Order Acknowledgement' and 'Client Education' on the order.
  14. Administer the order with a successful administration event.
  15. Double click the administered cell.
  16. Validate the 'Administration Record - Results' dialog is displayed and that the 'Result' field is not required.
Topics
• Avatar eMAR • NX

 

  1. Back to top
  • Was this article helpful?

Recommended articles

  1. Page type
    Reference
  2. Tags
    1. content:release
    2. llm-no-index
    3. role:sysadmin
    4. search:ready