|
Included Updates
None
Product Update Form Description
The 'OrderEntry.order_entry_cs_utilities' table is updated to improve the performance of certain queries, including those that are used by the 'Order Entry Notifications' form when including order actions across all clients for selected 'Order Types'. Please note: The optimization of this table will be completed via a background process that will continue to run after the Update is reported as being loaded. Depending on the number of rows in this table, it could take a significant amount of time (potentially an hour or longer) to complete this optimization.
|
Topics
• Order Entry Notifications
|
-
Avatar OE - Specimen Collection
Two new extended attributes are added to Order Entry Client Information dictionary #10245 ('Specimen Type'): 'Specimen Site - eMAR' and 'Disable Specimen Site if Included in Order'. 'Specimen Site - eMAR' allows a facility to indicate whether the 'Collection Site' field on the Avatar eMAR 'Specimen Collection' dialog is enabled, disabled, or required. 'Disable Specimen Site if Included in Order' will disable the 'Collection Site' field on the Avatar eMAR 'Specimen Collection' dialog if the order being administered already includes a 'Specimen Site'. Please note that Avatar eMAR 2022 Update 2 and a myAvatar Client Update 3201-006 are required to take advantage of this new functionality.
Included Updates
None
Product Update Form Description
Two new extended attributes are added to Order Entry Client Information dictionary #10245 ('Specimen Type'): 'Specimen Site - eMAR' and 'Disable Specimen Site if Included in Order'. 'Specimen Site - eMAR' allows a facility to indicate whether the 'Collection Site' field on the Avatar eMAR 'Specimen Collection' dialog is enabled, disabled, or required. 'Disable Specimen Site if Included in Order' will disable the 'Collection Site' field on the Avatar eMAR 'Specimen Collection' dialog if the order being administered already includes a 'Specimen Site'. Please note that Avatar eMAR 2022 Update 11 and a myAvatar Client Update or upgrade are required to take advantage of this new functionality.
|
Topics
• Avatar eMAR
|
-
Order Entry Console - Client Merge - OrderEntry.history_client_order
The 'OrderEntry.history_client_order' SQL table is enhanced for better performance, especially when running reports or queries that span clients. Note: A background process will be launched upon installation of this Update to finalize the optimization of this SQL table. This background process might take some time to complete (depending on the number of rows in this table), and any performance improvement will not be evident until this background process completes.
Included Updates
3, 5, 6, 7, 8, 11, 23, 24, 25
Product Update Form Description
The 'OrderEntry.history_client_order' SQL table is enhanced for better performance, especially when running reports or queries that span clients. Note: A background process will be launched upon installation of this Update to finalize the optimization of this SQL table. This background process might take some time to complete (depending on the number of rows in this table), and any performance improvement will not be evident until this background process completes.
|
Topics
• Order Entry Console
• Order Fulfillment
• Client Merge
• NX
|
-
Suppress Printing Of Order Notifications For Discontinued Orders
The 'Order Entry Notifications Routing Table', 'Order Entry Notifications Unit Routing Table', and 'Order Entry Notifications Program Routing Table' forms are enhanced by the addition of a 'Suppress Printing Of Order Notifications For Discontinued Orders On Modify Actions' prompt. These prompts, in conjunction with a new 'Suppress Notification print if Discontinued on Modify' registry setting, allow the application to be configured to suppress the automatic printing of Order Entry Notifications for the Discontinue portion of a Modify action. In addition, when Order Entry Notifications are printed for an automatic Discontinue upon discharge, the client's location prior to discharge is shown (instead of no location being shown).
Included Updates
2, 3, 5, 6, 7, 8, 11, 23, 24, 25, 33
Product Update Form Description
The 'Order Entry Notifications Routing Table', 'Order Entry Notifications Unit Routing Table', and 'Order Entry Notifications Program Routing Table' forms are enhanced by the addition of a 'Suppress Printing Of Order Notifications For Discontinued Orders On Modify Actions' prompt. These prompts, in conjunction with a new 'Suppress Notification print if Discontinued on Modify' registry setting, allow the application to be configured to suppress the automatic printing of Order Entry Notifications for the Discontinue portion of a Modify action. In addition, when Order Entry Notifications are printed for an automatic Discontinue upon discharge, the client's location prior to discharge is shown (instead of no location being shown). Note: As part of the installation of this Update, two indices for the 'OrderEntry.order_entry_cs_utilities' table are rebuilt via a background process that will continue to run after the Update is reported as being loaded. Depending on the number of rows in this table, it could take a significant amount of time (potentially an hour or longer) to complete this task. While these indices are being rebuilt, forms, widgets, and reports that use data from this table might show inconsistent or incomplete results.
|
Topics
• Order Entry Notifications
• NX
• myAvatar/myAvatar NX
|
-
OE NX - Order Group Setup With Line Break
An issue is resolved in the Order Entry Console (Orders This Episode section) where the error "[SUBSCRIPT] GetOrderSets+62^OrderEntryConsoleDataAPIGetOrderSets *orderTypeAllowed" might occur when selecting an 'Order Group'.
Included Updates
3, 5, 6, 7, 8, 11, 23, 24, 25, 33
Product Update Form Description
An issue is resolved in the Order Entry Console (Orders This Episode section) where the error "[SUBSCRIPT] GetOrderSets+62^OrderEntryConsoleDataAPIGetOrderSets *orderTypeAllowed" might occur when selecting an 'Order Group'.
|
Topics
• Order Entry Console
• NX
|
-
Diagnosis mapping for multiple Orders during Order Entry
A change is made to ensure that Diagnosis information entered during Order Entry is saved correctly when multiple orders are added to the Scratchpad before signing.
Included Updates
3, 5, 6, 7, 8, 11, 23, 24, 25, 33, 41
Required Updates
Product Update Form Description
An issue is resolved where orders filed via the Order Entry Console (Orders This Episode section) with a 'Diagnosis' selected may be missing data in the 'OrderEntry.history_client_order' and 'SYSTEM.RadPlus_IMO_Results' tables. The fields missing data in 'OrderEntry.history_client_order' are 'diag_icd9_code', 'diag_icd9_value', 'diag_icd10_code', 'diag_icd10_value', 'diag_imo_value', 'diagnosis_code' and 'diagnosis_value', and the value in the 'JOIN_TO_DIAGNOSIS_OBJECT' field does not correspond to an existing row in 'SYSTEM.RadPlus_IMO_Results'.
|
Topics
• Order Entry Console
• NX
• Diagnosis
|
-
Order Entry Console - Client Reported to Reported
Additional modifications are included to support the change from "Client Reported" to "Reported" in the Order Entry Console (Home Medications, Admission Med Reconciliation, and Discharge Med Reconciliation sections). The change from "Client Reported" to "Reported" was introduced via Avatar OE 2022 Update 23, along with an associated myAvatar Client Update or upgrade.
Included Updates
3, 5, 6, 7, 8, 9, 11, 23, 24, 25, 33, 41, 42
Required Updates
Product Update Form Description
Additional modifications are included to support the change from "Client Reported" to "Reported" in the Order Entry Console (Home Medications, Admission Med Reconciliation, and Discharge Med Reconciliation sections). The change from "Client Reported" to "Reported" was introduced via Avatar OE 2022 Update 23, along with an associated myAvatar Client Update or upgrade.
|
Topics
• Order Entry Console
• NX
|
| |
