Skip to main content

Avatar OE 2023 Monthly Release 2023.02.00 Acceptance Tests

  1. Last updated
  2. Save as PDF
Update 11 Summary | Details
Order Entry Console - Preferred Description for Route of Administration
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Dictionary Update (CWS)
  • Dynamic Form - Dictionary Update - Locked Dictionary
  • eMAR
  • RxConnect
  • Rx Summary
  • Rx Summary.Pending
  • Rx Summary.Pending.Schedule
  • Rx Summary.Order Details
  • eMAR - Order Details
Scenario 1: eMAR NX - Validate Preferred Description for Route of Administration is Respected with Fill Details
Specific Setup:
  • The ‘(10182) Preferred Description’ extended attribute must be set to “SUB-Q” in the Order Entry Tabled Files ‘(10181) Route of Administration’ dictionary for “SUBCUTANEOUS”.
  • The registry setting 'Avatar eMAR->General->Settings->->->Use Pharmacy Fill Details For Order Description' must be set to "Y".
  • Avatar must be configured to communicate with RxConnect via Avatar HL7.
  • Please log out of the application and log back in after completing the above configuration.
  • A pharmacy type order code with a subcutaneous route of administration must exist. (Order Code A)
  • A pharmacy type order code with an oral route of administration must exist. (Order Code B)
  • 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. Validate the 'Route' field is equal to "SUB-Q".
  4. Fill out any remaining required fields and click [Add to Scratchpad] and [Sign].
  5. Validate "SUB-Q" is displayed in the order details.
  6. Search for and select "Order Code B" in the 'New Order' field.
  7. Validate the 'Route' field is equal to "ORAL".
  8. Fill out any remaining required fields and click [Add to Scratchpad] and [Sign].
  9. Validate "ORAL" is displayed in the order details.
  10. Access the 'eMAR' widget.
  11. Validate that an order for "Order Code A" is displayed.
  12. Validate "SUB-Q" is displayed in the order details.
  13. Validate that an order for "Order Code B" is displayed.
  14. Validate "ORAL" is displayed in the order details.
  15. Process the orders for "Order Code A" and "Order Code B" via RxConnect.
  16. Access the 'eMAR' widget.
  17. Validate that an order for "Order Code A" is displayed.
  18. Validate "SUB-Q" is displayed in the order details.
  19. Validate that an order for "Order Code B" is displayed.
  20. Validate "ORAL" is displayed in the order details.
Order Entry Console - Pre-Admit - Give Initial Dose Now
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Frequency Code Setup
  • Dictionary Update (CWS)
Scenario 1: OE NX - Pre-Admit - Order Group - One Time Only Frequency - Custom Administration Time
Specific Setup:
  • The 'Avatar Order Entry->Facility Defaults->Client Profile->->->Allow New Orders For Pre-Admit Episodes' registry setting must be set to "Y".
  • The application must not have pharmacies configured in the 'External Pharmacy Setup' form.
  • The '"Avatar Order Entry->Facility Defaults->Client Profile->->->Defer Activation of Orders in a Pre-Admit Episode" must be set to "Y".
  • The ‘(524) Require Hours of Administration for Routine Orders’ extended attribute must be set to “Hours of Administration are required not for Routine Orders” in the Order Entry Tabled Files ‘(500) Order Types’ dictionary for “Pharmacy”.
  • Please log out of the application and log back in after completing the above configuration.
  • A frequency code must be configured in the 'Frequency Code Setup' form with the following attributes: (Frequency Code A)
  • 'Routine or PRN(As Needed) = "Routine"
  • 'One Time Only' = "Yes"
  • 'Times/24 Hours' = "1"
  • 'Interval Frequency' = "No"
  • 'Daily Administration' = "Daily"
  • 'Default to Give Initial Dose Now' = "Yes"
  • A frequency code must be configured in the 'Frequency Code Setup' form with the following attributes: (Frequency Code B)
  • 'Routine or PRN(As Needed) = "Routine"
  • 'One Time Only' = "Yes"
  • 'Times/24 Hours' = "1"
  • 'Interval Frequency' = "No"
  • 'Daily Administration' = "Daily"
  • 'Default to Give Initial Dose Now' = "No"
  • 'Hours of Administration' = "08:00 AM"
  • Two Pharmacy-type order codes must exist. (Order Code A) (Order Code B)
  • An order group (Order Group A) must be created with at least two pharmacy-type order codes where:
  • "Order Code A" has a default frequency of "Frequency Code A".
  • "Order Code B" has a default frequency of "Frequency Code B".
  • A client must have an active pre-admit 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 Group A" in the 'New Order' field.
  3. Validate the 'Order Group' dialog is displayed.
  4. Click [Select All].
  5. Validate the 'Frequency' fields are defaulted from the 'Order Group Setup' form.
  6. Validate that the 'First Dose Date/Time' fields are hidden.
  7. Validate that the 'Stop Date/Time' fields are hidden.
  8. Validate that the 'Custom' button is visible for both "Order Code A" and "Order Code B".
  9. Click the 'Custom' button for "Order Code A".
  10. Set the 'Scheduled Administration Times;' field to "12:00 PM" and click [Save].
  11. Validate a 'Warning!' dialog appears stating "'Hours of Administration' and 'Give Initial Dose Now' cannot both be specified for an order created in "Pre-Admit mode". 'Give Initial Dose Now' will be cleared." and click [OK].
  12. Click the 'Custom' button for "Order Code B".
  13. Set the 'Scheduled Administration Times;' field to "12:00 AM" and click [Save].
  14. Click [Add to Scratchpad].
  15. Validate the 'Start Date' fields in the scratchpad for both "Order Code A" and "Order Code B" contain "01/01/2099".
  16. Select "Order Code A" from the 'Scratchpad'.
  17. Validate the 'Give Initial Dose Now - Yes' button is enabled and not pressed.
  18. Click [Custom], validate the 'Scheduled Administration Times:' field contains "12:00 PM" and click [Cancel].
  19. Click [Give Initial Dose Now - Yes].
  20. Validate a 'Warning!' dialog appears stating "'Hours of Administration' and 'Give Initial Dose Now' cannot both be specified for an order created in "Pre-Admit mode". 'Hours of Administration' will be cleared." and click [OK].
  21. Click [Custom], validate the 'Scheduled Administration Times' field contains no values and click [Cancel].
  22. Set the 'Duration' field to "1" and click [Days].
  23. Click [Update Order] and, in the 'Scratchpad', validate the 'Stop Date' field for "Order Code A" is "01/01/2099".
  24. Select "Order Code B" from the 'Scratchpad'.
  25. Click [Custom], validate the 'Scheduled Administration Times' field contains "12:00 AM" and click [Cancel].
  26. Set the 'Duration' field to "2" and click [Days].
  27. Click [Update Order] and, in the 'Scratchpad', validate the 'Stop Date' field for "Order Code B" is "01/02/2099".
  28. Click [Sign].
Scenario 2: OE NX - Pre-Admit - One Time Only with Default Give Initial Dose Now - Field Validation
Specific Setup:
  • The 'Avatar Order Entry->Facility Defaults->Client Profile->->->Allow New Orders For Pre-Admit Episodes' registry setting must be set to "Y".
  • The application must not have pharmacies configured in the 'External Pharmacy Setup' form.
  • The '"Avatar Order Entry->Facility Defaults->Client Profile->->->Defer Activation of Orders in a Pre-Admit Episode" must be set to "Y".
  • The ‘(524) Require Hours of Administration for Routine Orders’ extended attribute must be set to “Hours of Administration are required for Routine Orders” in the Order Entry Tabled Files ‘(500) Order Types’ dictionary for “Pharmacy”.
  • Please log out of the application and log back in after completing the above configuration.
  • A frequency code must be configured in the 'Frequency Code Setup' form with the following attributes: (Frequency Code A)
  • 'Routine or PRN(As Needed) = "Routine"
  • 'One Time Only' = "Yes"
  • 'Times/24 Hours' = "1"
  • 'Interval Frequency' = "No"
  • 'Daily Administration' = "Daily"
  • 'Default to Give Initial Dose Now' = "Yes"
  • A Pharmacy-type order code must exist. (Order Code A)
  • A client must have an active pre-admit 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. Set the 'Dose' field to "1" and select "Capsule" from the 'Dose Unit' field.
  4. Validate the "Start Date/Time' fields are hidden.
  5. Validate the 'Stop Date/Time' fields are hidden.
  6. Validate the 'First Dose Date/Time' fields are hidden.
  7. Validate that 'Give Initial Dose Now' [Yes] is disabled.
  8. Validate the 'Custom' button is not hidden.
  9. Search for and select "Frequency Code A" from the 'Freq:' field.
  10. Validate that 'Give Initial Dose Now' [Yes] is pressed.
  11. Validate that 'Give Initial Dose Now' [Yes] is enabled.
  12. Validate that 'Skip 1st Dose' [Yes] is disabled.
  13. Validate that [Custom] is not hidden.
  14. Click [Custom].
  15. Set the 1st 'Scheduled Administration Times' field to "1200" and click [Save].
  16. Validate a warning message is displayed stating: "Hours of Administration' and 'Give Initial Dose Now' cannot both be specified for an order created in "Pre-Admit mode". 'Give Initial Dose Now' will be cleared."
  17. Click [OK] and validate that 'Give Initial Dose Now' [Yes] is not pressed.
  18. Click 'Give Initial Dose Now' [Yes].
  19. Validate a warning message is displayed stating: 'Hours of Administration' and 'Give Initial Dose Now' cannot both be specified for an order created in "Pre-Admit mode". 'Hours of Administration' will be cleared."
  20. Click [OK].
  21. Click [Custom], validate there are no values listed under 'Scheduled Administration Times' and click [Cancel].
  22. Set the 'Duration' field to "1" and click [Days].
  23. Click [Add to Scratchpad].
  24. Validate the 'Start Date' field contains "01/01/2099".
  25. Validate the 'Stop Date' field contains "01/01/2099".
  26. Select "Order Code A" from the scratchpad.
  27. Validate that 'Give Initial Dose Now' [Yes] is pressed.
  28. Validate that 'Give Initial Dose Now' [Yes] is enabled.
  29. Click [Cancel] and then [Sign].
Order Entry Console - Order Validation - iButton
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.
Scenario 2: OE NX - iButton - Orders This Episode
Specific Setup:
  • The 'RADplus->System Security->User Definition->->->Two-Factor Authentication Method' registry setting must be set to "iButton".
  • Please log out of the application and log back in after completing the above configuration.
  • The logged in user must both require validation and must be allowed to validate orders.
  • A client must have an inpatient 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.
Steps
  1. Select "Client A", access the Order Entry Console, and plug in the iButton.
  2. Search for and select "TYLENOL (ACETAMINOPHEN) 325 MG CAPSULE, LIQUID FILLED ORAL" from the 'New Order' field.
  3. Populate all required fields and click [Add to Scratchpad], [Final Review], and [Sign].
  4. Select the "Tylenol" order created from the 'Order grid' and click [Validate].
  5. Validate the "Tylenol" order has been validated.
  6. Search for and select "PREDNISONE 1 MG TABLET ORAL" from the 'New Order' field.
  7. Populate all required fields and click [Add to Scratchpad], [Final Review] and [Sign].
  8. Unplug the iButton.
  9. Select the "Prednisone" order in the 'Order grid' and click [Validate]
  10. Validate a message is displayed stating "Two-Factor Authentication failed. This can happen if the logged-in user is not assigned a Two-Factor Authentication token or if the correct Two-Factor Authentication token is not present. Filing is canceled. Please insert your assigned Two-Factor Authentication token and try again." and click [OK].
Topics
• RxConnect • NX • Order Entry Console
Update 12 Summary | Details
eMAR Downtime Automation - pdf reports available for printing
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Order Entry Forms Definition
  • FTP Setup
  • eMAR Downtime Automation
Scenario 1: NX - eMAR Downtime Automation - 7 Day Administration Record
Specific Setup:
  • An active definition must exist in the 'Order Entry Forms Definition' form for the "Administration Record (7 day grid)" that is configured with the following:
  • 'Form Description' and 'Form Title To Be Printed' = "Administration Record - 7 day grid"
  • 'Order Types To Be Included' = all values selected.
  • 'Printed Time Format (Supported forms Only)' = "Military".
  • 'Include Routine / PRN / STAT/ Other' = all values checked.
  • 'Include Orders That Require Validation' = "Yes"
  • 'Include Expired Orders' = "No".
  • 'Include Future-Start Orders' = "Yes"
  • 'Include Future-Discontinued Orders' = "Yes"
  • An active 'SFTP - Password' configuration must exist for the server where the application resides that communicates with the FTP server.
  • An active configuration must exist for the 'Administration Record - 7 day grid' in the 'eMAR Downtime Automation' form that fits the following criteria:
  • 'Print A Blank Form for Clients With No Qualifying Orders' = "No"
  • 'Sort Clients' = "Alphabetically by Client Name (across Units/Programs)"
  • 'Create a Separate Report File for Each Selected Unit/Program' = "No"
  • 'eMAR Downtime Report to Include' = "Units"
  • 'Include All Units' = "Yes"
  • 'File Path' = a valid directory on the server where the application resides
  • 'Send File to FTP Server' = "Yes"
  • 'FTP Definition' = the definition configured for "SFTP - Password" in the 'FTP Setup' form.
  • Validate "Schedule Description: eMAR Downtime Automation(4) Recurrence Pattern : Daily" exists in the 'System Task Scheduler' and configure the 'Start Date' and 'Start Time'. This is the date and time that this task will run each day.
  • The 'RADplus Install Configuration' form must contain an active server configuration for the cache server where the application resides that uses the 'NX URL'. This is a CSMPROG only form and will be configured by a Netsmart Representative.
  • Please Note: For testing purposes, it is assumed that the 'eMAR Downtime Automation' task has run for the day.
Steps
  1. Access the cache server where the application resides and access the directory specified in the 'File Path' field on the 'eMAR Downtime Automation' form.
  2. Validate a file is displayed in the following format: YYYY-MM-DD_time in military format_Form Description name set up in 'Order Entry Forms Definition'. (ex. 2023-05-31_1036_7 day Administration Record)
  3. Open the pdf and validate that the 'Administration Record - 7 day grid' report is displayed and contains the following:
  4. Validate all clients are in one file and that they are in alphabetical order by client's last name, first name across all units selected.
  5. Validate the 'PRINTED DATE/TIME' field contains the date and time the report was created. The time will be in whichever format was selected in the 'Printed Time Format (Supported forms Only)' field on the 'Order Entry Forms Definition' form.
  6. Validate the 'D.O.B' field contains the Client's Date Of Birth.
  7. Validate the 'PAGE' field contains "Page # of #", and that it will reset for each client. If a client has multiple pages of orders it will read "Page 1 of # of total pages" and then for the next client it will return to "Page 1 of 1".
  8. Close the report and log off of the server.
  9. Access the FTP server and access the directory where the pdf's will be stored.
  10. Validate a file is displayed in the following format: YYYY-MM-DD_time in military format_Form Description name set up in 'Order Entry Forms Definition'. (ex. 2023-05-31_1036_7 day Administration Record)
  11. Open the pdf and validate that the 'Administration Record - 7 day grid' report is displayed and contains the following:
  12. Validate all clients are in one file and that they are in alphabetical order by client's last name, first name across all units selected.
  13. Validate the 'PRINTED DATE/TIME' field contains the date and time the report was created. The time will be in whichever format was selected in the 'Printed Time Format (Supported forms Only)' field on the 'Order Entry Forms Definition' form.
  14. Validate the 'D.O.B' field contains the Client's Date Of Birth.
  15. Validate the 'PAGE' field contains "Page # of #", and that it will reset for each client. If a client has multiple pages of orders it will read "Page 1 of # of total pages" and then for the next client it will return to "Page 1 of 1".
  16. Close the report and log off of the server.
Scenario 2: NX - eMAR Downtime Automation - 1 Day Administration Record
Specific Setup:
  • An active definition must exist in the 'Order Entry Forms Definition' form for the "Administration Record (1 day grid)" that is configured with the following:
  • 'Form Description' and 'Form Title To Be Printed' = "Administration Record - 1 day"
  • 'Order Types To Be Included' = "Pharmacy"
  • 'Printed Time Format (Supported forms Only)' = "AM/PM".
  • 'Include Routine / PRN / STAT/ Other' = all values checked.
  • 'Include Orders That Require Validation' = "Yes"
  • 'Include Expired Orders' = "No".
  • 'Include Future-Start Orders' = "No"
  • 'Include Future-Discontinued Orders' = "No"
  • An active configuration must exist for the 'Administration Record' in the 'eMAR Downtime Automation' form that fits the following criteria:
  • 'Print A Blank Form for Clients With No Qualifying Orders' = "No"
  • 'Sort Clients' = "Alphabetically by Client Name (across Units/Programs)"
  • 'Create a Separate Report File for Each Selected Unit/Program' = "Yes"
  • 'eMAR Downtime Report to Include' = "Programs"
  • 'Include All Programs' = "No"
  • 'Outpatient/Partial Hospitalization Programs to Include' = "(302) O.P. Adult Psych", "(303) O.P. Mature Adult Psych", and "(307) O.P. Mature Adult S.A".
  • 'File Path' = a valid directory on the server where the application resides
  • 'Delete Files After X Days' = "5"
  • 'Send File to FTP Server' = "No"
  • Validate "Schedule Description: eMAR Downtime Automation(4) Recurrence Pattern : Daily" exists in the 'System Task Scheduler' and configure the 'Start Date' and 'Start Time'. This is the date and time that this task will run each day.
  • The 'RADplus Install Configuration' form must contain an active server configuration for the cache server where the application resides that uses the 'NX URL'. This is a CSMPROG only form and will be configured by a Netsmart Representative.
  • The user logged into the application must have their action require validation. (User A)
  • Three clients must have active episodes for the following programs with qualifying orders:
  • "(302) O.P. Adult Psych" (Client A)
  • "(303) O.P. Mature Adult Psych" (Client B)
  • "(307) O.P. Mature Adult S.A" (Client C)
  • Please Note: For testing purposes, it is assumed that the 'eMAR Downtime Automation' task has run for the day.
Steps
  1. Access the cache server where the application resides and access the directory specified in the 'File Path' field on the 'eMAR Downtime Automation' form.
  2. Validate there are 3 files, one for every Outpatient and Partial Hospitalization program that was selected that contains clients with qualifying orders in the following format "Program_YYYY-MM-DD_time in military format_Form Description name set up in 'Order Entry Forms Definition'." (ex. O.P. Adult Psych_2023-06-06_1638_1 Day Administration Record).
  3. Open one of the pdf's and validate that the 'Administration Record - 1 Day' report is displayed and contains the following:
  4. Validate that the pdf will contain all clients in that program sorted in alphabetical order by client's last name, first name.
  5. Validate the 'PRINTED DATE/TIME' field contains the date and time the report was created. The time will be in whichever format was selected in the 'Printed Time Format (Supported forms Only)' field on the 'Order Entry Forms Definition' form.
  6. Validate the 'D.O.B' field contains the Client's Date Of Birth.
  7. Validate the 'PAGE' field contains "Page # of #", and that it will reset for each client. If a client has multiple pages of orders it will read "Page 1 of # of total pages" and then for the next client it will return to "Page 1 of 1".
  8. Close the report and log off of the server.
Scenario 3: NX - eMAR Downtime Automation - Administration Record
Specific Setup:
  • An active definition must exist in the 'Order Entry Forms Definition' form for the "Administration Record" that is configured with the following:
  • 'Form Description' and 'Form Title To Be Printed' = "Administration Record"
  • 'Order Types To Be Included' = all values selected.
  • 'Printed Time Format (Supported forms Only)' = "24-Hr (colon)".
  • 'Include Routine / PRN / STAT/ Other' = all values checked.
  • 'Include Orders That Require Validation' = "Yes"
  • 'Include Expired Orders' = "No".
  • 'Include Future-Start Orders' = "Yes"
  • 'Include Future-Discontinued Orders' = "No"
  • An active configuration must exist for the 'Administration Record' in the 'eMAR Downtime Automation' form that fits the following criteria:
  • 'Print A Blank Form for Clients With No Qualifying Orders' = "No"
  • 'Sort Clients' = "By Unit or Program, then by Room/Bed (for Units) or alphabetically by Client Name (for Programs)"
  • 'Create a Separate Report File for Each Selected Unit/Program' = "Yes"
  • 'eMAR Downtime Report to Include' = "Both"
  • 'Include All Units' = "Yes"
  • 'Include All Programs' = "Yes"
  • 'File Path' = a valid directory on the server where the application resides
  • 'Delete Files After X Days' = "1"
  • 'Send File to FTP Server' = "No"
  • Validate "Schedule Description: eMAR Downtime Automation(4) Recurrence Pattern : Daily" exists in the 'System Task Scheduler' and configure the 'Start Date' and 'Start Time'. This is the date and time that this task will run each day.
  • The 'RADplus Install Configuration' form must contain an active server configuration for the cache server where the application resides that uses the 'NX URL'. This is a CSMPROG only form and will be configured by a Netsmart Representative.
  • Please Note: For testing purposes, it is assumed that the 'eMAR Downtime Automation' task has run for the day.
Steps
  1. Access the cache server where the application resides and access the directory specified in the 'File Path' field on the 'eMAR Downtime Automation' form.
  2. Validate there are files for every unit that contains clients with qualifying orders in the following format "Unit_YYYY-MM-DD_time in military format_Form Description name set up in 'Order Entry Forms Definition'." (ex.1East_2023-06-01_1038_Administration Record).
  3. Validate there are files for every Outpatient and Partial Hospitalization program that contains clients with qualifying orders in the following format "Program_YYYY-MM-DD_time in military format_Form Description name set up in 'Order Entry Forms Definition'." (ex. O.P. Adult Psych_2023-06-01_1038_Administration Record).
  4. Open one of the pdf's and validate that the 'Administration Record' report is displayed and contains the following:
  5. Validate that the pdf for units will contain all clients in that unit and then sorted in Room/Bed order.
  6. Validate that the pdf for programs will contain all client in that program sorted in alphabetical order by client's last name, first name.
  7. Validate the 'PRINTED DATE/TIME' field contains the date and time the report was created. The time will be in whichever format was selected in the 'Printed Time Format (Supported forms Only)' field on the 'Order Entry Forms Definition' form.
  8. Validate the 'D.O.B' field contains the Client's Date Of Birth.
  9. Validate the 'PAGE' field contains "Page # of #", and that it will reset for each client. If a client has multiple pages of orders it will read "Page 1 of # of total pages" and then for the next client it will return to "Page 1 of 1".
  10. Close the report and log off of the server.
Scenario 4: NX - eMAR Downtime Automation - 1 Day Alt Administration Record
Specific Setup:
  • An active definition must exist in the 'Order Entry Forms Definition' form for the "Administration Record (1 day grid Alternate Format 1)" that is configured with the following:
  • 'Form Description' and 'Form Title To Be Printed' = "Administration Record - 1 Day Alternate"
  • 'Order Types To Be Included' = "Pharmacy"
  • 'Printed Time Format (Supported forms Only)' = "AM/PM".
  • 'Include Routine / PRN / STAT/ Other' = all values checked.
  • 'Include Orders That Require Validation' = "Yes"
  • 'Include Expired Orders' = "Yes"
  • 'Incl. Exp. Orders For How Many Days Past Order's Stop Date' = "5"
  • 'Include Future-Start Orders' = "No"
  • 'Include Future-Discontinued Orders' = "No"
  • An active configuration must exist for the 'Administration Record' in the 'eMAR Downtime Automation' form that fits the following criteria:
  • 'Print A Blank Form for Clients With No Qualifying Orders' = "Yes"
  • 'Sort Clients' = "By Unit or Program, then alphabetically by Client Name"
  • 'Create a Separate Report File for Each Selected Unit/Program' = "No"
  • 'eMAR Downtime Report to Include' = "Units"
  • 'Include All Units' = "No"
  • 'Units to Include' = "(1E) 1East" and "(1N) 1North"
  • 'File Path' = a valid directory on the server where the application resides
  • 'Delete Files After X Days' = "1"
  • 'Send File to FTP Server' = "No"
  • Validate "Schedule Description: eMAR Downtime Automation(4) Recurrence Pattern : Daily" exists in the 'System Task Scheduler' and configure the 'Start Date' and 'Start Time'. This is the date and time that this task will run each day.
  • The 'RADplus Install Configuration' form must contain an active server configuration for the cache server where the application resides that uses the 'NX URL'. This is a CSMPROG only form and will be configured by a Netsmart Representative.
  • Please Note: For testing purposes, it is assumed that the 'eMAR Downtime Automation' task has run for the day.
Steps
  1. Access the cache server where the application resides and access the directory specified in the 'File Path' field on the 'eMAR Downtime Automation' form.
  2. Validate there is one pdf that contains clients with qualifying orders in the following format "YYYY-MM-DD_time in military format_Form Description name set up in 'Order Entry Forms Definition'." (ex. 2023-06-06_1638_1 Day Administration Record - Alternate).
  3. Open the pdf and validate that the 'Administration Record - 1 Day Alternate' report is displayed and contains the following:
  4. Validate that the pdf will contain all clients in the two units selected, sorted in alphabetical order by client's last name, first name.
  5. Validate the 'PRINTED DATE/TIME' field contains the date and time the report was created. The time will be in whichever format was selected in the 'Printed Time Format (Supported forms Only)' field on the 'Order Entry Forms Definition' form.
  6. Validate the 'D.O.B' field contains the Client's Date Of Birth.
  7. Validate the 'PAGE' field contains "Page # of #", and that it will reset for each client. If a client has multiple pages of orders it will read "Page 1 of # of total pages" and then for the next client it will return to "Page 1 of 1".
  8. Close the report and log off of the server.
Scenario 5: eMAR Downtime Automation - 7 Day Alt Administration Record
Specific Setup:
  • An active definition must exist in the 'Order Entry Forms Definition' form for the "Administration Record (7 day grid Alternate Format 1)" that is configured with the following:
  • 'Form Description' and 'Form Title To Be Printed' = "Administration Record - 7 Day Alt"
  • 'Order Types To Be Included' = "Pharmacy"
  • 'Printed Time Format (Supported forms Only)' = "Military"
  • 'Include Routine / PRN / STAT/ Other' = all values checked
  • 'Include Orders That Require Validation' = "Yes"
  • 'Include Expired Orders' = "Yes"
  • 'Incl. Exp. Orders For How Many Days Past Order's Stop Date' = "5"
  • 'Include Future-Start Orders' = "No"
  • 'Include Future-Discontinued Orders' = "No"
  • An active 'SFTP - Key Pair' configuration must exist for the server where the application resides that communicates with the FTP server.
  • An active configuration must exist for 'Administration Record - 7 Day Alt' in the 'eMAR Downtime Automation' form that fits the following criteria:
  • 'Print A Blank Form for Clients With No Qualifying Orders' = "Yes"
  • 'Sort Clients' = "Alphabetically by Client Name (across Units/Programs)"
  • 'Create a Separate Report File for Each Selected Unit/Program' = "Yes"
  • 'eMAR Downtime Report to Include' = "Units"
  • 'Include All Units' = "No"
  • 'Units to Include' = "1North"
  • 'File Path' = a valid directory on the server where the application resides
  • 'Send File to FTP Server' = "Yes"
  • 'FTP Definition' = the definition configured for "SFTP - Key Pair" in the 'FTP Setup' form.
  • Validate "Schedule Description: eMAR Downtime Automation(4) Recurrence Pattern : Daily" exists in the 'System Task Scheduler' and configure the 'Start Date' and 'Start Time'. This is the date and time that this task will run each day.
  • The 'RADplus Install Configuration' form must contain an active server configuration for the cache server where the application resides that uses the 'NX URL'. This is a CSMPROG only form and will be configured by a Netsmart Representative.
  • Please Note: For testing purposes, it is assumed that the 'eMAR Downtime Automation' task has run for the day.
Steps
  1. Access the cache server where the application resides and access the directory specified in the 'File Path' field on the 'eMAR Downtime Automation' form.
  2. Validate a file is displayed in the following format: "Units selected_YYYY-MM-DD_time in military format_Form Description name" set up in 'Order Entry Forms Definition'. (ex.1North_2023-05-31_1651_Administration Record - 7 Day Alternate)
  3. Open the pdf and validate that the 'Administration Record - 7 Day Alt' report is displayed and contains the following:
  4. Validate all clients are in one file and that they are in alphabetical order by client's last name, first name across all units selected.
  5. Validate the 'PRINTED DATE/TIME' field contains the date and time the report was created. The time will be in whichever format was selected in the 'Printed Time Format (Supported forms Only)' field on the 'Order Entry Forms Definition' form.
  6. Validate the 'D.O.B' field contains the Client's Date Of Birth.
  7. Validate the 'PAGE' field contains "Page # of #", and that it will reset for each client. If a client has multiple pages of orders it will read "Page 1 of # of total pages" and then for the next client it will return to "Page 1 of 1".
  8. Close the report and log off of the server.
  9. Access the FTP server and access the directory where the pdf's will be stored.
  10. Validate a file is displayed in the following format: "Units selected_YYYY-MM-DD_time in military format_Form Description name" set up in 'Order Entry Forms Definition'. (ex.1North_2023-05-31_1651_Administration Record - 7 Day Alternate)
  11. Open the pdf and validate that the 'Administration Record - 7 Day Alt' report is displayed and contains the following:
  12. Validate all clients are in one file and that they are in alphabetical order by client's last name, first name across all units selected.
  13. Validate the 'PRINTED DATE/TIME' field contains the date and time the report was created. The time will be in whichever format was selected in the 'Printed Time Format (Supported forms Only)' field on the 'Order Entry Forms Definition' form.
  14. Validate the 'D.O.B' field contains the Client's Date Of Birth.
  15. Validate the 'PAGE' field contains "Page # of #", and that it will reset for each client. If a client has multiple pages of orders it will read "Page 1 of # of total pages" and then for the next client it will return to "Page 1 of 1".
  16. Close the report and log off of the server.
Scenario 6: NX - eMAR Downtime Automation - Administration Record Alternate
Specific Setup:
  • An active definition must exist in the 'Order Entry Forms Definition' form for the "Administration Record (Alternate Format 1)" that is configured with the following:
  • 'Form Description' and 'Form Title To Be Printed' = "Administration Record - Alternate"
  • 'Order Types To Be Included' = all values selected.
  • 'Printed Time Format (Supported forms Only)' = "Military".
  • 'Include Routine / PRN / STAT/ Other' = all values checked.
  • 'Include Orders That Require Validation' = "Yes"
  • 'Include Expired Orders' = "No".
  • 'Include Future-Start Orders' = "No"
  • 'Include Future-Discontinued Orders' = "No"
  • An active configuration must exist for the 'Administration Record' in the 'eMAR Downtime Automation' form that fits the following criteria:
  • 'Print A Blank Form for Clients With No Qualifying Orders' = "Yes"
  • 'Sort Clients' = "Alphabetically by Client Name (across Units/Programs)"
  • 'Create a Separate Report File for Each Selected Unit/Program' = "Yes"
  • 'eMAR Downtime Report to Include' = "Both"
  • 'Include All Units' = "No"
  • 'Units to Include' = "(1N) 1North"
  • 'Include All Programs' = "No"
  • 'Programs to Include' = "(306) O.P. Adult S.A."
  • 'File Path' = a valid directory on the server where the application resides
  • 'Delete Files After X Days' = "1"
  • 'Send File to FTP Server' = "No"
  • Validate "Schedule Description: eMAR Downtime Automation(4) Recurrence Pattern : Daily" exists in the 'System Task Scheduler' and configure the 'Start Date' and 'Start Time'. This is the date and time that this task will run each day.
  • The 'RADplus Install Configuration' form must contain an active server configuration for the cache server where the application resides that uses the 'NX URL'. This is a CSMPROG only form and will be configured by a Netsmart Representative.
  • Please Note: For testing purposes, it is assumed that the 'eMAR Downtime Automation' task has run for the day.
Steps
  1. Access the cache server where the application resides and access the directory specified in the 'File Path' field on the 'eMAR Downtime Automation' form.
  2. Validate there is a file for the unit selected (1North) that contains clients with qualifying orders in the following format "Unit_YYYY-MM-DD_time in military format_Form Description name set up in 'Order Entry Forms Definition'." (ex. 1North_2023-05-30_1039_Administration Record - Alternate).
  3. Validate there is a file for every the program selected (O.P. Adult S.A.) that contains clients with qualifying orders in the following format "Program_YYYY-MM-DD_time in military format_Form Description name set up in 'Order Entry Forms Definition'." (ex. O.P. Adult S.A._2023-05-30_1039_Administration Record - Alternate).
  4. Open one of the pdf's and validate that the 'Administration Record - Alternate' report is displayed and contains the following:
  5. Validate that the pdf for units will contain all clients in that unit and then sorted in Room/Bed order.
  6. Validate that the pdf for programs will contain all client in that program sorted in alphabetical order by client's last name, first name.
  7. Validate the 'PRINTED DATE/TIME' field contains the date and time the report was created. The time will be in whichever format was selected in the 'Printed Time Format (Supported forms Only)' field on the 'Order Entry Forms Definition' form.
  8. Validate the 'D.O.B' field contains the Client's Date Of Birth.
  9. Validate the 'PAGE' field contains "Page # of #", and that it will reset for each client. If a client has multiple pages of orders it will read "Page 1 of # of total pages" and then for the next client it will return to "Page 1 of 1".
  10. Close the report and log off of the server.
  11. After 2 days and after the 'eMAR Downtime Automation' task has run for the day,
  12. Access the cache server where the application resides and access the directory specified in the 'File Path' field on the 'eMAR Downtime Automation' form.
  13. Validate the "1North_2023-06-01_1039_Administration Record - Alternate" and "O.P. Adult S.A._2023-06-01_1039_Administration Record - Alternate" files are no longer displayed.
  14. Validate there is a new file for the unit selected (1North) that contains clients with qualifying orders in the following format "Unit_YYYY-MM-DD_time in military format_Form Description name set up in 'Order Entry Forms Definition'." (ex. 1North_2023-06-01_1039_Administration Record - Alternate)
  15. Validate there is a file for every the program selected (O.P. Adult S.A.) that contains clients with qualifying orders in the following format "Program_YYYY-MM-DD_time in military format_Form Description name set up in 'Order Entry Forms Definition'." (ex. O.P. Adult S.A._2023-06-01_1039_Administration Record - Alternate)
Order Entry Forms Printing
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Order Entry Forms Definition
  • Order Entry Forms Printing
Scenario 1: OE NX - Order Entry Forms Printing - Administration Record
Specific Setup:
  • Multiple clients must have multiple active orders.
Steps
  1. Access the 'Order Entry Forms Definition' form.
  2. Create a form for the 'Administration Record'.
  3. Access the 'Order Entry Forms Printing' form.
  4. Select the 'Administration Record' form created above and select to sort clients alphabetically by client name and click [Print Forms].
  5. Validate the 'Administration Record' report is printed with clients listed in alphabetical order by last name and includes separate pages for each client.
  6. Validate the 'PRINTED DATE/TIME' field contains the date and time the report was run. The time will be in whichever format was selected in the 'Printed Time Format (Supported forms Only)' field on the 'Order Entry Forms Definition' form.
  7. Validate the 'D.O.B' field contains the Client's Date of Birth.
  8. Validate the 'PAGE' field contains "Page # of #", and that it will reset for each client. If a client has multiple pages of orders it will read 'Page 1 of # of total pages' and then for the next client is will return to "Page 1 of 1".
Scenario 2: OE NX - Order Entry Forms Printing - 7 Day Administration Record
Specific Setup:
  • Multiple clients must have multiple active orders.
  • A client must have an active inpatient episode. (Client A)
Steps
  1. Access the 'Order Entry Forms Definition' form.
  2. Create a form for the 'Administration Record - 7 Day'.
  3. Select "Client A" and access the Order Entry Console.
  4. Search for and select a pharmacy-type order code.
  5. Populate all required fields.
  6. Populate the 'Reason Text' field with text that has over 48 characters, hit enter and proceed with the same text for six lines.
  7. Populate the 'Addl Instructions' field with text that has over 48 characters, hit enter and proceed with the same text for nine lines.
  8. Access the 'Order Entry Forms Printing' form.
  9. Select the 'Administration Record - 7 Day' form created above and select to sort clients alphabetically by client name and click [Print Forms].
  10. Validate the 'Administration Record - 7 Day' report is printed with clients listed in alphabetical order by last name and includes separate pages for each client.
  11. Validate the 'PRINTED DATE/TIME' field contains the date and time the report was run. The time will be in whichever format was selected in the 'Printed Time Format (Supported forms Only)' field on the 'Order Entry Forms Definition' form.
  12. Validate the 'D.O.B' field contains the Client's Date of Birth.
  13. Validate the 'PAGE' field contains "Page # of #", and that it will reset for each client. If a client has multiple pages of orders it will read 'Page 1 of # of total pages' and then for the next client is will return to "Page 1 of 1".
  14. Select "Client A" from the list of clients on the left.
  15. Validate that the order created above is displayed with an ellipsis after the first five lines of the 'Addl Instructions' and after the first five lines of the 'Reason Text'.
Scenario 3: OE NX - Order Entry Forms Printing - 1 day Administration Record - Alternate format
Specific Setup:
  • Multiple clients must have multiple active orders.
Steps
  1. Access the 'Order Entry Forms Definition' form.
  2. Create a form for the 'Alternate Record (1 day grid Alternate Format 1)'.
  3. Access the 'Order Entry Forms Printing' form.
  4. Select the form created above and select to sort clients alphabetically by client name and click [Print Forms].
  5. Validate the 'Administration Record - 1 Day Alternate' report is printed with clients listed in alphabetical order by last name and includes separate pages for each client.
  6. Validate the 'PRINTED DATE/TIME' field contains the date and time the report was run. The time will be in whichever format was selected in the 'Printed Time Format (Supported forms Only)' field on the 'Order Entry Forms Definition' form.
  7. Validate the 'D.O.B' field contains the Client's Date of Birth.
  8. Validate the 'PAGE' field contains "Page # of #", and that it will reset for each client. If a client has multiple pages of orders it will read 'Page 1 of # of total pages' and then for the next client is will return to "Page 1 of 1".
Scenario 4: OE NX - Order Entry Forms Printing - 7 Day Administration Record - Alternate format with Fill Details
Specific Setup:
  • The application must be configured to communicate with RxConnect via Avatar HL7.
  • 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. Create an order for "ADVIL 200 MG ORAL TABLET" for "2 Tablets, Twice A Day".
  3. Access the 'Launch RxConnect' form and click [Launch RxConnect].
  4. Process the order that was created for "Client A".
  5. Access the 'Order Entry Forms Definition' form.
  6. Create a form for the 'Alternate Record (7 Day grid Alternate Format)'.
  7. Access the 'Order Entry Forms Printing' form.
  8. Select the form created above, select the unit that "Client A" is associated with and select "Client A" and click [Print Forms].
  9. Validate the 'Administration Record - 7 Day Alternate' report is displayed and validate the following:
  10. The correct strength displayed in the 'Order Description' (Ibuprofen 200 mg Tablet Oral Take 400 mg = 2 Tablet by mouth Twice A Day).
  11. The 'PRINTED DATE/TIME' field contains the date and time the report was run. The time will be in whichever format was selected in the 'Printed Time Format (Supported forms Only)' field on the 'Order Entry Forms Definition' form.
  12. The 'D.O.B' field contains the Client's Date of Birth.
  13. The 'PAGE' field contains "Page # of #", and that it will reset for each client. If a client has multiple pages of orders it will read 'Page 1 of # of total pages' and then for the next client is will return to "Page 1 of 1".
Scenario 5: OE NX - Order Entry Forms Printing - 1 Day Administration Record
Steps
  1. Access the 'Order Entry Forms Definition' form.
  2. Create a form for the 'Administration Record - 1 Day'.
  3. Access the 'Order Entry Forms Printing' form.
  4. Select the 'Administration Record - 1 Day' form created above and select to sort clients alphabetically by client name and click [Print Forms].
  5. Validate the 'Administration Record - 1 Day' report is printed with clients listed in alphabetical order by last name and includes separate pages for each client.
  6. Validate the 'PRINTED DATE/TIME' field contains the date and time the report was run. The time will be in whichever format was selected in the 'Printed Time Format (Supported forms Only)' field on the 'Order Entry Forms Definition' form.
  7. Validate the 'D.O.B' field contains the Client's Date of Birth.
  8. Validate the 'PAGE' field contains "Page # of #", and that it will reset for each client. If a client has multiple pages of orders it will read 'Page 1 of # of total pages' and then for the next client is will return to "Page 1 of 1".
Scenario 6: OE NX - Order Entry Forms Printing - Administration Record Alternate
Specific Setup:
  • Multiple clients must have multiple active orders.
  • A client must have an active inpatient episode. (Client A)
Steps
  1. Access the 'Order Entry Forms Definition' form.
  2. Create a form for the 'Administration Record - Alternate'.
  3. Select "Client A" and access the Order Entry Console.
  4. Search for and select a pharmacy-type order code.
  5. Populate all required fields.
  6. Populate the 'Reason Text' field with text that has over 48 characters, hit enter and proceed with the same text for six lines.
  7. Populate the 'Addl Instructions' field with text that has over 48 characters, hit enter and proceed with the same text for nine lines.
  8. Access the 'Order Entry Forms Printing' form.
  9. Select the 'Administration Record - Alternate' form created above and select to sort clients alphabetically by client name and click [Print Forms].
  10. Validate the 'Administration Record - Alternate' report is printed with clients listed in alphabetical order by last name and includes separate pages for each client.
  11. Validate the 'PRINTED DATE/TIME' field contains the date and time the report was run. The time will be in whichever format was selected in the 'Printed Time Format (Supported forms Only)' field on the 'Order Entry Forms Definition' form.
  12. Validate the 'D.O.B' field contains the Client's Date of Birth.
  13. Validate the 'PAGE' field contains "Page # of #", and that it will reset for each client. If a client has multiple pages of orders it will read 'Page 1 of # of total pages' and then for the next client is will return to "Page 1 of 1".
  14. Select "Client A" from the list of clients on the left.
  15. Validate that the order created above is displayed with an ellipsis after the first five lines of the 'Addl Instructions' and after the first five lines of the 'Reason Text'.
Topics
• NX • eMAR Downtime Automation • Order Entry Forms Printing
Update 17 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
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
Update 22 Summary | Details
OE NX - Admission / Discharge Medication Reconciliation
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Order Entry Console - Admission Med Reconciliation
Scenario 1: OE NX - Discharge Med Reconciliation - Validate the correct 'Ordering Practitioner' is displayed
Specific Setup:
  • The logged in user must contain an apostrophe in the 'User Description'
  • Two practitioners must exist. (Practitioner A and Practitioner B)
  • "Practitioner A" is associated with the user who is logged into the application.
  • Two clients must have active inpatient episodes and no active orders. (Client A and Client B).
  • “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. Search for and select "Client A".
  2. Access the Order Entry Console and select the 'Discharge Med Reconciliation' tab.
  3. Click the 'No Prescription Required' checkbox.
  4. Search for and select "Zubsolv 11.4 MG-2.9 MG Tablet Sublingual (Schedule III)" in the 'New Order' field.
  5. Set the 'Dose' field to "1".
  6. Validate the 'Dose Unit' field contains "Tablet".
  7. Select "As Needed" in the 'Freq' field.
  8. Set the 'Days Supply' field to "15" and press Tab.
  9. Validate the 'Dispense Qty' field contains "15".
  10. Validate the 'Dispense Qty Unit' field contains "Tablet".
  11. Click [Add to Scratchpad].
  12. Validate the 'Ordering Practitioner' field contains "Practitioner A".
  13. Search for and select "Practitioner B" in the 'Ordering Practitioner' field, click [Hold in Pending Status].
  14. Validate that the 'Discharge Med Reconciliation' tab is in view-only mode aside from the following being enabled: [Restart Reconciliation], [Edit Pending Reconciliation], and [Activate & Reconcile].
  15. Validate the 'Ordering Practitioner' field contains "Practitioner B".
  16. Select "Client B" in the 'My Clients' widget
  17. Access the 'Discharge Med Reconciliation' tab and validate the 'Ordering Practitioner' field contains "Practitioner A".
  18. Select "Client A" in the 'My Clients' widget
  19. Access the 'Discharge Med Reconciliation' tab and validate the 'Ordering Practitioner' field contains "Practitioner B".
  20. Click [Activate & Reconcile] and [Sign].
  21. Validate that the 'Discharge Med Reconciliation' tab is in view-only mode.
  22. Validate the 'Ordering Practitioner' field contains "Practitioner B".
  23. Select "Client B" in the 'My Clients' widget
  24. Access the 'Discharge Med Reconciliation' tab and validate the 'Ordering Practitioner' field contains "Practitioner A".


Scenario 2: OE NX - Admission Med Reconciliation - Validate the correct 'Ordering Practitioner' is displayed
Specific Setup:
  • The logged in user must contain an apostrophe in the 'User Description'
  • Two practitioners must exist. (Practitioner A and Practitioner B)
  • "Practitioner A" is associated with the user who is logged into the application.
  • Two clients must have active inpatient episodes and no active orders. (Client A and Client B).
  • “Client A” must have two episodes of which the second is the inpatient episode and 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.
  • "Client B" should only have one episode.
Steps
  1. Search for and select "Client A".
  2. Access the Order Entry Console and select the 'Admission Med Reconciliation' tab.
  3. Search for and select " AMBIEN 10 MG TABLET ORAL (Schedule IV)" in the 'New Order' field.
  4. Set the 'Dose' field to "1".
  5. Validate the 'Dose Unit' field contains "Tablet".
  6. Select "Every Day" in the 'Freq' field.
  7. Set the 'Duration' field to "10" and click [Days].
  8. Validate the 'Days Supply' field contains "10".
  9. Validate the 'Dispense Qty' field contains "10".
  10. Select "Tablet" in the 'Dispense Qty Unit' field.
  11. Click [Add to Scratchpad].
  12. Validate the 'Ordering Practitioner' field contains "Practitioner A".
  13. Search for and select "Practitioner B" in the 'Ordering Practitioner' field, click [Reconcile & Sign].
  14. Validate that the 'Admission Med Reconciliation' tab is in view-only mode.
  15. Validate that the 'Ordering Practitioner' field contains "Practitioner B".
  16. Select "Client B" in the 'My Clients' widget
  17. Validate the 'Ordering Practitioner' field contains "Practitioner A".
Topics
• Order Entry Console • NX
Update 28 Summary | Details
OE NX - Discharge Medication Reconciliation
Scenario 1: OE NX - Discharge Med Reconciliation - 12 orders in Orders This Episode, 12 Orders in Home Medications, order actions and Review and Sign
Specific Setup:
  • A client must have an inpatient 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.
  • "Client A" has 12 active orders on the 'Orders This Episode' section and 12 active orders on the 'Home Medications' section.
  • A few of the orders on the 'Orders This Episode' tab must have a large order description (Can use the 'Reason Text' with a large amount of text, and/or 'Ask on Order Entry' questions with a large amount of text.)
Steps
  1. Select "Client A" and access the Order Entry console.
  2. Click the 'Discharge Medication Reconciliation' tab.
  3. Validate all orders are displayed correctly on both the 'Inpatient Medications' list and the 'Home Medications Scratchpad (Post-Discharge)'.
Topics
• Order Entry Console • NX
2022 Update 89 Summary | Details
OE NX - Order Entry Console - External Lab Vendor - Program / Unit
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • External Lab/Radiology Definition for CareConnect
  • Dynamic Form - Client Alert
  • Admission
  • Order Code Setup
Scenario 1: OE NX - Lab Orders - External Lab vendor - Program / Unit
Specific Setup:
  • A client must have an active episode. (Client A)
  • 2 External Lab Vendors must be created ("Lab Vendor Unit", and "Lab Vendor Program"). Each lab vendor must be configured with either the same 'Program' or the same 'Unit' "Client A" is in. ("Lab Vendor Program" must have a few additional programs selected as well).
  • An Order Code (Lab Code A) must be configured to have both 'Lab Vendor Unit' and 'Lab Vendor Program' configured as external labs through the 'External Lab Definition' grid.
Steps
  1. Select "Client A" and access the Order Entry Console.
  2. Search for and select "Lab Code A" in the 'New Order' field.
  3. Validate both 'Lab Vendor Program' and 'Lab Vendor Unit' external labs display in the 'External Lab Vendor Destination' field.
  4. Populate the remaining required fields and file the order.
  5. Validate "Lab Code A" displays in the 'Order grid'.
Topics
• NX
 

Avatar_OE_2023_Monthly_Release_2023.02.00_Details.csv