-
Order Entry Console - Preferred Description for Route of Administration
An issue is resolved to ensure that when orders use a 'Route of Administration' that is defined with a 'Preferred Description', the 'Preferred Description' is still displayed in the Avatar eMAR 'Order Description' after pharmacy fill details are received.
NOTE: The change included in this Update will affect only those orders for which pharmacy fill details are received by Avatar from RxConnect subsequent to the installation of this Update.
-
Order Entry Console - Pre-Admit - Give Initial Dose Now
An issue is resolved to ensure that while in a pre-admit episode, orders placed with a One Time Only frequency that has Give Initial Dose Now selected, are not being filed with the current date and time as its Start Date and Start Time.
-
Order Entry Console - Order Validation - iButton
An issue is resolved to ensure that in the Order Entry Console (Orders This Episode section), the error "Avatar Order Entry Console has encountered the following error: GetDongleId+26^GUIDongleAPI" is no longer presented when attempting to Validate orders.
Note: This error occurs only when using myAvatar NX and only when the 'Two-Factor Authentication Method' registry setting is set to "iButton", and when the 'Two-Factor Authentication Process Points' registry setting includes "3" (Avatar OE for filing pharmacy/medication orders).
Included Updates
8
Product Update Form Description
The following issues are resolved: 1) When attempting to create or update an order in a system running a version of Cache prior to Cache 2011 could generate a "[METHOD DOES NOT EXIST]ValidateObject+4^OrderEntry.histclientorder.2" error. 2) Orders that use a 'Route of Administration' that is defined with a 'Preferred Description' no longer display the 'Preferred Description' in the Avatar eMAR 'Order Description' once pharmacy fill details are received and are used to display the eMAR 'Order Description'. NOTE: The change included in this Update will affect only those orders for which pharmacy fill details are received by Avatar from RxConnect subsequent to the installation of this Update. 3) In the Order Entry Console (Orders This Episode section), the error "Avatar Order Entry Console has encountered the following error: GetDongleId+26^GUIDongleAPI" might be presented when attempting to Validate orders. Note that this error occurs only when using myAvatar NX and only when the 'Two-Factor Authentication Method' registry setting is set to "iButton", and when the 'Two-Factor Authentication Process Points' registry setting includes "3" (Avatar OE for filing pharmacy/medication orders).
|
Topics
• RxConnect
• NX
• Order Entry Console
|
-
eMAR Downtime Automation - pdf reports available for printing
Support is provided for 'eMAR Downtime Automation', a process that can run automatically via the 'System Task Scheduler' to generate any of the product 'Administration Record' forms that are available for the 'Order Entry Forms Printing' process, saving the output as one or more PDF files. These PDF files could then be used to support medication (and other) administrations in the event that Avatar eMAR is unavailable. The 'eMAR Downtime Automation' form is provided to allow for configuration of this functionality.
NOTE: Avatar RADplus 2023 Update 34 is required for full functionality.
In addition, an issue is resolved in the various product "Administration Record" Crystal Reports (generated via the 'Order Entry Forms Printing' form) where the error "A subscript must be between 1 and the size of the array" could occur.
-
Order Entry Forms Printing
Enhancements are introduced on all reports created in 'Order Entry Forms Printing', with the exception of the "Physician Order Validation' form.
Included Updates
None
Additional Requirements
NOTE: Avatar RADplus 2023 Update 34 is required for full functionality.
Product Update Form Description
Support is provided for 'eMAR Downtime Automation', a process that can run automatically via the 'System Task Scheduler' to generate any of the product 'Administration Record' forms that are available for the 'Order Entry Forms Printing' process, saving the output as one or more PDF files. These PDF files could then be used to support medication (and other) administrations in the event that Avatar eMAR is unavailable. The 'eMAR Downtime Automation' form is provided to allow for configuration of this functionality. NOTE: Avatar RADplus 2023 Update 34 is required for full functionality. In addition, an issue is resolved in the various product "Administration Record" Crystal Reports (generated via the 'Order Entry Forms Printing' form) where the error "A subscript must be between 1 and the size of the array" could occur.
|
Topics
• NX
• eMAR Downtime Automation
• Order Entry Forms Printing
|
-
eMAR NX - 'Results' text for follow-ups
Two new extended attributes are added to Avatar Order Entry:
1) 'Require Result Text / Comment on eMAR Follow-Up' (Order Entry Tabled Files, data element 570) is added to 'Order Type' (Order Entry Tabled Files, data element 500).
2) 'Require Result Text / Comment on eMAR Follow-Up' (Order Entry Tabled Files, data element 571) is added to 'Reason Code Setup' (Order Entry Tabled Files, data element 504). Avatar eMAR 2023 Update 8 modifies eMAR to be sensitive to these new extended attributes.
In addition, in the 'Order Code Setup' form, the prompt 'Require Result Text on Administration Event Result' is changed to 'Require Result Text / Comment on Avatar eMAR Follow-up', for consistency with these new extended attributes, which reflect different terminology in use in Avatar eMAR and Avatar eMAR NX.
Included Updates
12
Product Update Form Description
Two new extended attributes are added to Avatar Order Entry: 1) 'Require Result Text / Comment on eMAR Follow-Up' (Order Entry Tabled Files, data element 570) is added to 'Order Type' (Order Entry Tabled Files, data element 500). 2) 'Require Result Text / Comment on eMAR Follow-Up' (Order Entry Tabled Files, data element 571) is added to 'Reason Code Setup' (Order Entry Tabled Files, data element 504). Avatar eMAR 2023 Update 8 modifies eMAR to be sensitive to these new extended attributes. In addition, in the 'Order Code Setup' form, the prompt 'Require Result Text on Administration Event Result' is changed to 'Require Result Text / Comment on Avatar eMAR Follow-up', for consistency with these new extended attributes, which reflect different terminology in use in Avatar eMAR and Avatar eMAR NX.
|
Topics
• Avatar eMAR
• NX
|
-
OE NX - Admission / Discharge Medication Reconciliation
An issue is resolved in the Order Entry Console (Admission Med Reconciliation and Discharge Med Reconciliation sections) where all of the details of a previously-saved medication reconciliation, including the informational message that provides the details (date, time, and user) about the previous save, might not be displayed when subsequently accessing the medication reconciliation.
Included Updates
None
Product Update Form Description
An issue is resolved in the Order Entry Console (Admission Med Reconciliation and Discharge Med Reconciliation sections) where all of the details of a previously-saved medication reconciliation, including the informational message that provides the details (date, time, and user) about the previous save, might not be displayed when subsequently accessing the medication reconciliation. In addition, Avatar Order Entry is enhanced to provide improved auditing of the 'Medication Reconciliation' process.
|
Topics
• Order Entry Console
• NX
|
-
OE NX - Order Entry Console - External Lab Vendor - Program / Unit
In the Order Entry Console (Orders This Episode section), an issue is resolved where the 'External Lab Vendor Destination' field contains vendors that should be excluded based on 'Unit' filtering, or might not contain vendors that should be included based on 'Program' filtering.
Included Updates
2, 3, 4, 5, 6, 7, 8, 9, 11, 16, 23, 24, 25, 26, 30, 31, 33, 35, 36, 41, 42, 43, 44, 46, 47, 48, 52, 59, 63, 64, 65, 66, 68, 70, 71, 72, 73, 76, 77, 79, 82, 84, 86, 87, 88
Product Update Form Description
In the Order Entry Console (Orders This Episode section), an issue is resolved where the 'External Lab Vendor Destination' field contains vendors that should be excluded based on 'Unit' filtering, or might not contain vendors that should be included based on 'Program' filtering.
|
Topics
• NX
|