Avatar OE 2022 Quarterly Release 2022.02 Details

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

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

Included Updates

None

Product Update Form Description

In the Order Entry Console (Home Medications section), an issue is resolved where no orders are displayed if any of the client's Home Medications contain multiple 'Reason Codes'. At present, this can happen only if an order from the Orders This Episode section has multiple 'Reason Codes' and that order is then "added to the Scratchpad" during Discharge Med Reconciliation.

Topics

• NX • Order Entry Console

Included Updates

None

Product Update Form Description

An issue is resolved where the 'Order Code Load/Update Utility via Micromedex Red Book Database' process might sometimes define an 'Order Code' with a Micromedex 'Product Name ID' for an equivalent product rather than for the medication name used in the 'Order Code' 'Description'. This data issue could result in behavior where an order for a generic name 'Order Code' converts to a Brand name product in the Order Entry Console (Discharge Med Reconciliation section) when the inpatient order is added to the 'Home Medications Scratchpad (Post-Discharge)'. This data issue could also result in behavior where an order being placed in the Order Entry Console (Order This Episode section), when in "external pharmacy mode" to display the name of an equivalent product on the 'Final Review' dialog, rather than showing the medication name that was shown while adding the order to the Scratchpad. Also, the 'Order Code Load Utility Via Micromedex Red Book Database' process is modified to better ensure that the NDCs selected for defining 'Order Codes' are recognized by CKO Server during clinical screening.

Topics

• NX

Included Updates

None

Product Update Form Description

In the Order Entry Console (Home Medications section), the 'External RxHx' and 'Prescriber's Queue' hyperlinks now use the 'Program' that is specified below the Scratchpad when launching to OrderConnect. The below-the-Scratchpad 'Program' is mapped to an OrderConnect 'Agency', which is then used during the authentication process when launching via these hyperlinks. Prior to this change, if a user launched to OrderConnect via either of these two hyperlinks (rather than the 'Order Labs' hyperlink), certain functions that the user might then navigate to within OrderConnect might be attributed to the wrong 'Agency' (location). The effect of this could include the printing of the wrong address on printed prescriptions. Note: A RADplus middleware upgrade or Update is required to make use of this new functionality.

Topics

• Order Entry Console • NX

Included Updates

None

Product Update Form Description

The registry setting 'Default Duration for PRN prescriptions in OE Console (Home Meds)' is added. When this registry setting is set to a value greater than 0, then for PRN Rx orders in the Order Entry Console (Home Medications section) the 'Stop Date' will be calculated as the 'Start Date' plus the value of this registry setting, in days. Note: A myAvatar Client Update or upgrade must also be installed to enable this functionality. Also note that this functionality is available only in myAvatar NX.

Topics

• Order Entry Console • Home Medications • NX

Included Updates

3, 5, 6, 7, 8

Product Update Form Description

The following enhancements are introduced: 1) The 'Reported Source Text' field is added to the Order Entry Console (Home Medications section) for use with "Client Reported" medications. The 'Reported Source Text' field will be required when using a selection for the 'Reported Source' prompt that is defined with the extended attribute 'Require Reported Source Text' set to "Yes". The value from the 'Reported Source Text' field is displayed in the 'Order Details' column of the lists of a client's existing Home Medications in the Order Entry Console (Home Medications, Admission Med Reconciliation, and Discharge Med Reconciliation sections). 2) In the Order Entry Console (Home Medications, Admission Med Reconciliation, and Discharge Med Reconciliation sections), the phrase "Client Reported" and the abbreviation "CR" are replaced with "Reported". Note: A myAvatar Client Update or upgrade must also be installed to enable the functionality included in this Update. Also, note that these enhancements are available only in myAvatar NX.

Topics

• Order Entry Console • Discharge Med Reconciliation

Included Updates

3, 5, 6, 8, 11

Product Update Form Description

The following enhancements are introduced in the Order Entry Console (Orders This Episode section) in support of interfaces with external lab vendors: 1) Support is added for displaying and printing lab order requisition forms and ABN documents (Advance Beneficiary Notice of Noncoverage for Medicare beneficiaries). 2) Support is added for multi-select and date types of responses for Compendium AOEs for external lab vendors. Note: Avatar CareFabric 2022 Update 28 and a myAvatar Client Update or upgrade must also be installed for full functionality. Also note that these enhancements are available only in myAvatar NX.

Topics

• NX • Ask on Order Entry questions

Included Updates

3, 5, 6, 8, 11, 24

Product Update Form Description

The 'Future Start Time' field is added to the 'Order Code Setup' form. In the Order Entry Console (Orders This Episode section), a new order that uses an 'Order Code' that is defined with a 'Future Start Time' will have its 'Start Date' and 'Start Time' automatically default to the next occurrence of the indicated 'Future Start Time' (relative to the current time). If the 'Order Code' being used for the new order is defined with 'Automatic Discontinue of Order Types', then any existing orders that are selected to be automatically DC'd will have their 'DC Effective Date/Time' set to the new order's 'Start Date/Time'. Note: A myAvatar Client Update or upgrade must also be installed to make use of this functionality in the Order Entry Console. Also note that this functionality in the Order Entry Console is available only in myAvatar NX.

Topics

• Order Entry Console • NX

Included Updates

None

Product Update Form Description

In the 'Order Entry Forms Printing' form, an issue is resolved where the product strength for a medication order on any of the "Administration Record" forms might display the total dose to be administered rather than the actual product strength. For example, an order for "Zoloft 100 mg tablet, 200 mg twice daily" might be shown as "Zoloft 200 mg tablet, 200 mg = 2 tablets twice daily". These reports will now display the product strength within the description of the medication / product, which matches what is shown in Avatar eMAR. The actual content and format of the dosing instructions are based on what is received in the pharmacy fill details (when they are being used for these reports). Note that this issue occurs only when pharmacy fill details are being used to build the "Order Description". Also note that the format of the notation "200 mg = 2 tablets" shown in this example is the default format used in RxConnect, but that this format can be changed, resulting in less clear dosing information.

Topics

• NX • Order Entry Forms Printing

Included Updates

None

Product Update Form Description

An issue is resolved where the 'Change Ordering Practitioner' and 'Change Ordering Practitioner (My Orders)' forms do not update the corresponding order in RxConnect.

Topics

• Change Ordering Practitioner

Included Updates

9

Product Update Form Description

In the Order Entry Console, an issue is resolved where users might not be warned and prevented from accessing the Admission Med Reconciliation or Discharge Med Reconciliation sections for a client/episode when that Medication Reconciliation is currently in use by another user.

Topics

• Admission Med Reconciliation • Discharge Med Reconciliation

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

Included Updates

None

Product Update Form Description

In the Order Entry Console (Orders This Episode section), an issue is resolved where an HL7 message to convey an order to a pharmacy, lab, or other system might not be generated when the 'Activate' button is used for "Pre-Admit Orders". This issue occurs when a "Pre-Admit Order" required Validation and was Validated before being "activated".

Topics

• Order Entry Console • NX

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

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

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

Included Updates

2, 3, 5, 6, 7, 8, 11, 23, 24, 25, 33, 36, 41, 42

Product Update Form Description

The following issues are resolved: 1) The 'Order Code Setup' form is modified to no longer allow the selection of "inactive" 'Dispense Quantity Units' for the 'Default Dispense Quantity Unit' prompt. If an 'Order Code' is already defined with a 'Default Dispense Quantity Unit' that is currently "inactive", that "inactive" code will not be used as the default within the Order Entry Console (Home Medications and Discharge Med Reconciliation sections, and Orders This Episode and Admission Med Reconciliation sections when in "external pharmacy mode"). 2) In the Order Entry Console (Home Medications section), the error "Error: ExternalMed.Dose_Form_Abbr Exceeds Maximum Size of 30" that might occur when saving a "Reported" medication. 3) In the Order Entry Console (Orders This Episode section), an issue where an order could be renewed for longer than the 'Maximum Eventual Order Duration' value for the order. 4) In the Order Entry Console (Home Medications section), an issue where the 'No Known Medications' checkbox, once checked, might not display as checked after navigating away and returning to the 'Home Medications' section. In addition, the Order Entry Console (Home Medications and Orders This Episode sections) is enhanced to provide a 'Priority' filter to support filtering the list of the client's Home Medications by 'Priority'. 'Reported' medications that do not have a 'Frequency' selected (and therefore have no 'Priority' attribute) will be displayed only if "All" or "Unknown" are selected in the new filter. Note: A myAvatar Client Update or upgrade must be installed in order to make use of this enhancement. Also note that this enhancement is available only in myAvatar NX.

Topics

• Order Entry Console • NX • myAvatar/myAvatar NX • Home Medications • myAvatar NX Only

Included Updates

2, 3, 5, 6, 7, 8, 11, 16, 23, 24, 25, 33, 36, 41, 42, 43

Product Update Form Description

The following enhancements are introduced: 1) The 'Order Validation' form is added. This form provides another way to Validate orders placed through the Order Entry Console (Orders This Episode section) and the 'Client Profile / Physicians Orders' form. 2) The 'Physician Order Validation' and 'Order Validation' forms are enhanced to support the ability to remove the 'Refills Allowed' and 'Dispense Quantity' information that displays in the 'Details of Selected Orders' field. This functionality is enabled via the registry setting 'Display Refills Allowed and Dispense Quantity in Order Validation forms'. 3) The 'Enable Team filter in 'Physician Order Validation' form' and 'Allow multiple Client selection in 'Physician Order Validation' form' registry settings are renamed to 'Enable filters in Order Validation forms' and 'Allow multiple Client selection in Order Validation forms', respectively, to encompass the new 'Order Validation' form. Additionally, the 'Enable filters in Order Validation forms' registry setting now supports the ability to hide/show 'Unit', 'Program', and 'Team' filters. Note: Avatar RADplus 2022 Update 71 must be installed for full functionality of the new 'Order Validation' form. Also a myAvatar Client Update or upgrade should be installed for optimal performance. In addition, the following issues are resolved: 1) The 'Physician Order Validation' form allows the original (now-DC'd) order that was acted on with a Modify action to be selected and Validated while the new order that was created via the Modify action still has an 'Order Status' of 'Validation Required' from when it was first created. 2) The 'Physician Order Validation' form does not also Validate the original (now-DC'd) order from a Modify action when Validating the order that was created via the Modify action. 3) The Order Entry Orders Web Service allows the original order that was acted on with a Modify action to be Validated while the new order that was created via the Modify action still has an 'Order Status' of 'Validation Required' from when it was first created. 4) The Order Entry Orders Web Service does not also Validate the original (now-DC'd) order from a Modify action when Validating the order that was created via the Modify action. Note: These changes bring the behavior of the 'Physician Order Validation' form into alignment with the Order Entry Console (Order This Episode section).

Topics

• Physician Order Validation • NX • Order Validation • Forms

Included Updates

None

Product Update Form Description

An issue is resolved where the 'Last Activity' column in the Order Entry Console (Orders This Episode section) might not show the latest activity.

Topics

• Order Entry Console • myAvatar/myAvatar NX

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

Included Updates

2, 3, 5, 6, 7, 8, 9, 11, 16, 23, 24, 25, 31, 33, 36, 41, 42, 43, 44, 46

Product Update Form Description

The following issues are resolved in the Order Entry Console (Orders This Episode and Admission Med Reconciliation sections): 1) When using Micromedex CKO Server via "direct connection" for clinical screening, if an 'Order Code' is defined with an 'NDC' that is not recognized by CKO Server, the messages displayed to the user show only the invalid NDC, and do not show a description of the item that cannot be processed for clinical screening. 2) When using Micromedex CKO Server for clinical screening, a message might not be displayed that alerts the user when the client has an active allergy that cannot be screened because the 'Allergen Code' is defined for use with FDB (and therefore cannot be screened by CKO Server).

Topics

• Order Entry Console • NX • myAvatar/myAvatar NX

Included Updates

None

Product Update Form Description

In the Order Entry Console (Orders This Episode section), the 'Sliding Scale Instructions' dialog is enhanced to allow the user to removed all saved rows.

Topics

• Sliding Scale Insulin • NX