Skip to main content

Avatar OE 2024 Update 10

  1. Last updated
  2. Save as PDF

Product Requirements and Recommendations

Avatar CWS required
Avatar OE required
RADplus required

Recommended Update Level

Avatar CWS 2024 Monthly Release 2024.00.01
Avatar OE 2024 Monthly Release 2024.00.01
RADplus 2024 Monthly Release 2024.00.01

Product Update Description

The following enhancements are included: 1) The 'OrderEntry.history_client_order' SQL table is enhanced for better performance. 2) The 'OrderEntry.history_client_order' and 'OrderEntry.history_client_order_lab' SQL tables can be included in Avatar Data Trail auditing. This can be done via the 'Data Trail Configuration' form. Note that the ability to enable Data Trail auditing for the 'OrderEntry.history_client_order' table is dependent on the completion of a process that was initiated by the installation of Avatar OE 2022 Update 33. If that process has not yet completed, then the ability to enable Data Trail auditing for this table will not be available, but will become available when that process does complete.

Required Updates

Avatar OE 2022 Update 33
Avatar OE 2022 Update 85
Avatar OE 2022 Update 92
Avatar OE 2023 Update 11

Included Updates

5

Details
NEW2 CHANGED0 FIXED0
New (2)
'OrderEntry.history_client_order' table.
The 'OrderEntry.history_client_order' SQL table is enhanced for better performance.
Value Added: Enhances the 'OrderEntry.history_client_order' table to capture more information.
Topics
• Order Entry Console
 
Data Trail - OrderEntry.history_client_order and OrderEntry.history_client_order_lab
The 'OrderEntry.history_client_order' and 'OrderEntry.history_client_order_lab' SQL tables can be included in Avatar Data Trail auditing. This can be done via the 'Data Trail Configuration' form. Note that the ability to enable Data Trail auditing for the 'OrderEntry.history_client_order' table is dependent on the completion of a process that was initiated by the installation of Avatar OE 2022 Update 33. If that process has not yet completed, then the ability to enable Data Trail auditing for this table will not be available, but will become available when that process does complete.
Value Added: Enhances Data Trail by adding the 'OrderEntry.history_client_order' and 'OrderEntry.history_client_order_lab' tables.
Topics
• Order Entry Console
 
Acceptance Tests
AV-89182 Summary | Details
'OrderEntry.history_client_order' table.
Scenario 1: OE NX - Orders This Episode - New Order (by Nurse who requires validation), Validation by Prescriber
Specific Setup:
  • The 'RADplus->General->->->->Default Value for Console View Episodes' registry setting must be set to "1". NOTE: This is a Netsmart Staff only registry setting. Please contact your Netsmart representative to have this setting configured.
  • Please log out of the application and log back in after completing the above configuration.
  • Two users must exist in the application: One whose actions require validation (User A) and One whose actions do not require Validation (User B).
  • A client must have an active episode whose program or unit are configured in the 'External Pharmacy Setup' form. (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.
  • "User A" must be logged into the application.
Steps
  1. Select "Client A”.
  2. Validate the 'Header Episode' field contains "All Episodes".
  3. Select the most current episode from the 'Header Episode' field.
  4. Access the Order Entry Console and click 'Orders This Episode' tab.
  5. Make note of the number next to the "V" icon.
  6. Search for and select "Ritalin 5 MG Tablet Oral (Schedule II)" from the ‘New Order’ field.
  7. Populate all required fields and click [Add to Scratchpad].
  8. Search for and select the staff member associated with "User B" in the ‘Ordering Practitioner' field.
  9. Click [Sign].
  10. Validate the ‘Interactions' dialog is displayed.
  11. Override all interactions and click [Save Override and Exit].
  12. Validate the 'Final Review' dialog is displayed.
  13. Select "None" in 'Output' and click [Sign].
  14. Validate the ‘Order grid’ contains an order for "Ritalin” with an 'Order Status' of "Requires Validation".
  15. Log out of the application and log back in as "User B".
  16. Select "Client A”.
  17. Validate the 'Header Episode' field contains "All Episodes".
  18. Select the most recent active episode from the 'Header Episode' field.
  19. Access the Order Entry Console and click 'Orders This Episode' tab.
  20. Validate the number next to the "V" icon has increased by 1.
  21. Select the “Ritalin” order in the ‘Order grid’ and click [Validate].
  22. Validate the 'Final Review' dialog is displayed.
  23. Select "None" in 'Output' and click [Sign].
  24. Validate the 'Order grid' contains an order for "Ritalin" with a 'Status' of "Active".
  25. Validate the number next to the "V" icon has decreased by 1.
Topics
• Order Entry Console
AV-93496 Summary | Details
Data Trail - OrderEntry.history_client_order and OrderEntry.history_client_order_lab
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Change MR#
  • Data Trail Configuration
  • Delete Last Movement
  • Dictionary Update (CWS)
  • Orders This Episode
Scenario 1: OE-NX - Orders This Episode - Create an order, Change MR#, and delete client
Specific Setup:
  • The 'OrderEntry.history_client_order' and 'OrderEntry.history_client_order_lab' tables must be selected in the 'Data Trail Configuration' form.
  • A user must exist who has access to the 'Audit.history_client_order' and 'Audit.history_client_order_lab' tables. (User A)
  • The ‘Require External Lab Vendor Destination’ extended attribute must be set to “Yes” in the Order Entry Tabled Files ‘(500) Order Types’ dictionary for “Lab”.
  • An 'External Lab Vendor' must exist. (Lab Vendor A)
  • An active 'Specimen Type' must exist. (Specimen Type A)
  • The ‘(10253) Specimen Site’ extended attribute must be set to “Required” in the Order Entry Tabled Files ‘(10245) Specimen Type’ dictionary for “Specimen Type A”.
  • An External Lab Vendor must exist. (Lab Vendor A)
  • An active 'Specimen Type' must exist. (Specimen Type A)
  • A lab-type order code must exist that is associated with "Lab Vendor A" and "Specimen Type A". (Order Code A)
  • Please log out of the application and log back in after completing the above configuration
  • A client must have an active 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. Search for and select “Order Code A” in the ‘New Order’ field.
  3. Populate all required fields.
  4. Click [Add to Scratchpad] and [Sign].
  5. Create four reports using the ‘OrderEntry.history_client_order’, ‘OrderEntry.history_client_order_lab’, ‘Audit.history_client_order’, and ‘Audit.history_client_order_lab’ tables.
  6. Validate that one row exists in each table for the order created.
  7. Access the ‘Change MR#’ form and change the MR# for “Client A”.
  8. Refresh the 'OrderEntry.history_client_order' and 'Audit.history_client_order' reports.
  9. Validate the row in the 'OrderEntry.history_client_order' table has been updated with the new PATID.
  10. Validate the row in the 'Audit.history_client_order' table remains for the original PATID and that a new row appears for the new PATID.
  11. Access the ‘Delete Last Movement’ form for “Client A” and delete the admission for “Episode 1”.
  12. Access the ‘Client Delete’ form and delete “Client A”.
  13. Refresh the 'OrderEntry.history_client_order' and 'Audit.history_client_order' reports.
  14. Validate the row in the 'OrderEntry.history_client_order' table no longer exists.
  15. Validate the rows in the 'Audit.history_client_order' table remain for the original PATID and the new PATID.
Topics
• Order Entry Console
Table Changes
Table Column Change
OrderEntry.history_client_order current_stop_date_time add
OrderEntry.history_client_order dis_effective_date_time add
OrderEntry.history_client_order effective_stop_date_time add
OrderEntry.history_client_order latest_hold_eff_date_time add
OrderEntry.history_client_order latest_resm_eff_date_time add
OrderEntry.history_client_order order_date_time add
OrderEntry.history_client_order start_date_time add
OrderEntry.history_client_order validated_date_time add
OrderEntry.history_client_order current_stop_date_time add
OrderEntry.history_client_order current_stop_date_time add
OrderEntry.history_client_order current_stop_date_time add
OrderEntry.history_client_order current_stop_date_time add

 

  1. Back to top
  • Was this article helpful?

Recommended articles

  1. Page type
    Reference
  2. Tags
    1. Avatar OE 2024 Update 10
    2. content:release
    3. llm-no-index
    4. Order Entry Console
    5. role:sysadmin