============================================================================= Run Date: SEP 17, 2020 Designation: OR*3*413 Package : OR - ORDER ENTRY/RESULTS REPORTING Priority: Mandatory Version : 3 SEQ #447 Status: Released Compliance Date: OCT 18, 2020 ============================================================================= Associated patches: (v)OR*3*377 <<= must be installed BEFORE `OR*3*413' (v)OR*3*397 <<= must be installed BEFORE `OR*3*413' (v)OR*3*462 <<= must be installed BEFORE `OR*3*413' (v)OR*3*481 <<= must be installed BEFORE `OR*3*413' Subject: BACKDOOR CLINIC ORDERS Category: - Routine - Enhancement (Mandatory) Description: ============ The build for this patch is distributed as part of a multi-package build that contains OR*3.0*413 and PSJ*5.0*319. The following issues are addressed by this patch: 1. NSR#20120502, Clinic Orders - Inpatient Medications Edits and New Entry. Pharmacist/pharmacy technician involved with verifying medication orders need to be able to enter/adjust pending clinic medication orders within regular pharmacy workflows, so that patient care is not delayed based on the original provider entry of the clinic medication order. 2. NSR#20090416, Changes to the Nurse Order Verification's Effect on Order Status This enhancement improves patient safety by preventing medication errors; these errors occur when orders that the pharmacist has not completed reviewing are inadvertently activated by the nurse's verification. Patch Components: ----------------- Files & Fields Associated: File Name (Number) Field Name (Number) New/Modified/Deleted ------------------ ------------------- -------------------- N/A Forms Associated: Form Name File # New/Modified/Deleted --------- ------ -------------------- N/A Mail Groups Associated: Mail Group Name New/Modified/Deleted --------------- -------------------- N/A Options Associated: Option Name Type New/Modified/Deleted ----------- ---- -------------------- N/A Protocols Associated: Protocol Name New/Modified/Deleted ------------- -------------------- N/A Security Keys Associated: Security Key Name ----------------- N/A Templates Associated: Template Name Type File Name (Number) New/Modified/Deleted ------------- ---- ------------------ -------------------- N/A Remote Procedures Associated: Remote Procedure Name New/Modified/Deleted --------------------- -------------------- N/A Parameter Definitions Associated: Parameter Name New/Modified/Deleted -------------- -------------------- N/A Additional Information: New Service Requests (NSRs): ---------------------------- 20120502 - Clinic Orders - Inpatient Medications Edits and New Entry. 20090416 - Changes to the Nurse Order Verification's Effect on Order Status Patient Safety Issues (PSIs): ----------------------------- N/A Defect Tracking System Ticket(s) & Overview: -------------------------------------------- 1. INC1288136 - After the install of patch OR*3*452 the tier copay display in CPRS and the $ is not showing for local possible doses. Problem: -------- Site reported after installing patch OR*3*452, which added the display of cost tier co-pay information for Outpatient medications in CPRS, it does not display the $ and tier information for local possible doses. Resolution: ----------- Routine ORWDPS2 at line tag BLDDOSE was modified to address this issue. 2. INC1843817 - MOCHA order checks cannot be performed in CPRS on certain orders that have had a correction made by a pharmacist. Problem: -------- If a site has a one to many orderable item to dispense drugs and has an order that has had a service correction performed on it by a pharmacist, the next renewal or copy on that order will fail the dose check. This was fixed in MOCHA v2.1b but then was broken by the warranty patch for MOCHA v2.1b. This is enterprise wide and is causing providers unnecessary messages that the order checks could not be done. Resolution: ----------- Routine ORDSGCHK was modified to restore the fix that was in MOCHA v2.1b. Also fixed an issue that for complex orders that DRUGIEN was sometimes getting overwritten. Created an additional variable, DISPDRUGIEN which holds the value from OR GTX DISPENSE DRUG, while DRUGIEN will be used to store the Drug IEN from OR GTX DOSE. Test Sites: ----------- MARTINSBURG, VAMC OKLAHOMA CITY VAMC PITTSBURGH VAMC Software and Documentation Retrieval Instructions: -------------------------------------------------- The software for this patch is being released using a host file. The host file is available at the following location: /srv/vista/patches/SOFTWARE/OR_413_PSJ_319.KID File Name Contents FTP Mode ----------------- ---------- --------- OR_413_PSJ_319.KID OR*3.0*413 ASCII PSJ*5.0*319 Documentation describing the new functionality is included in this release. Documentation can be found on the VA Software Documentation Library at: https://www.domain.ext/vdl/ Documentation Title File Name ----------------------------------------------------------------------- Release Notes psj_5_0_319_rn.pdf psj_5_0_319_rn.docx Patch Installation: Pre/Post Installation Overview: ------------------------------- The build for this patch is distributed as part of a multi-package build that contains OR*3.0*413 and PSJ*5.0*319. Pre-Installation Instructions: ------------------------------ This patch may be installed with users on the system although it is recommended that it be installed during non-peak hours to minimize potential disruption to users. This patch should take less than 5 minutes to install. Create a backup of the protocols that were modified in PSJ*5*319 before installing the host file. Follow the instructions below. At the VistA menu prompt enter the option, XPD MAIN. Select OPTION NAME: XPD MAIN Kernel Installation & Distribution System Edits and Distribution ... Select Kernel Installation & Distribution System Option: EDits and Distribution Create a Build Using Namespace Copy Build to Build Edit a Build Select Edits and Distribution Option: EDIT a Build Select BUILD NAME: BCKPSJ*5.0*319 Are you adding 'BCKPSJ*5.0*319' as a new BUILD (the 10793RD)? No// Y (Yes) BUILD PACKAGE FILE LINK: BUILD TYPE: SINGLE PACKAGE// SINGLE PACKAGE BUILD TRACK PACKAGE NATIONALLY: YES// N NO Go to the page 3. Go to the PROTOCOL component and enter these protocols as SEND TO SITE. PSJ LM BRIEF PATIENT INFO MENU PSJ LM IV OE MENU PSJ LM OE MENU PSJ PC IV AC/EDIT ACTION PSJI LM ACTIVE MENU PSJI LM PENDING ACTION At the command prompt, Save and Exit. Next, create a PacMan Message by selecting the Transport a Distribution option. Create a Build Using Namespace Copy Build to Build Edit a Build Transport a Distribution Select Edits and Distribution Option: transport a Distribution Enter the Package Names to be transported. The order in which they are entered will be the order in which they are installed. First Package Name: BCKPSJ*5.0*319 Another Package Name: ORDER PACKAGE 1 BCKPSJ*5.0*319 OK to continue? YES// Transport through (HF)Host File or (PM)PackMan: PM PackMan BCKPSJ*5.0*319... No Package File Link Subject: Backup of PSJ*5*319 Protocols Please enter description of Packman Message Do you wish to secure this message? NO// Send mail to: LAST,FIRST// LAST,FIRST Select basket to send to: IN// And Send to: Check your IN box for the PackMan message. Installation Instructions: -------------------------- 1. Use the Load a Distribution option contained on the Kernel Installation and Distribution System Menu to load the Host file. When prompted to "Enter a Host File:" enter /srv/vista/patches/SOFTWARE/OR_413_PSJ_319.KID 2. From the Kernel Installation and Distribution System Menu, select the Installation Menu. From this menu, A. Select the Verify Checksums in Transport Global option to confirm the integrity of the routines that are in the transport global. When prompted for the INSTALL NAME enter the patch or build name. OR*3.0*413 NOTE: Using will not bring up a Multi-Package build even if it was loaded immediately before this step. It will only bring up the last patch in the build. B. Select the Backup a Transport Global option to create a backup message of any routines exported with this patch. It will not backup any other changes such as DDs or templates. C. You may also elect to use the following options: i. Print Transport Global - This option will allow you to view the components of the KIDS build. ii. Compare Transport Global to Current System - This option will allow you to view all changes that will be made when this patch is installed. It compares all of the components of this patch, such as routines, DDs, templates, etc. D. Select the Install Package(s) option and choose the patch to install. i. If prompted 'Want KIDS to Rebuild Menu Trees Upon Completion of Install? NO//', answer NO ii. When prompted 'Want KIDS to INHIBIT LOGONs during the install? NO//', answer NO. iii. When prompted 'Want to DISABLE Scheduled Options, Menu Options, and Protocols? NO//', answer NO. Post-Installation Instructions: ------------------------------- N/A Back-out, Rollback Instructions: -------------------------------- In the event of a catastrophic failure, the Facility CIO may make the decision to back-out the patch. It is imperative that you have performed a backup of the routines included in this patch prior to installation. The back-out plan is to restore the routine from the backup created. No data was modified by this patch installation and, therefore, no rollback strategy is required. To verify the back-out completed successfully, ensure the checksum matches the pre-patch checksum from the patch description. Backup a Transport Global backs up only routines. In the event of a Rollback, restore the protocols from the backup created for BCKPSJ*5.0*319. Routine Information: ==================== The second line of each of these routines now looks like: ;;3.0;ORDER ENTRY/RESULTS REPORTING;**[Patch List]**;Dec 17, 1997;Build 32 The checksums below are new checksums, and can be checked with CHECK1^XTSUMBLD. Routine Name: ORCACT0 Before: B69260079 After: B80016688 **7,27,48,72,86,92,94,141,165, 177,173,190,215,243,289,204, 306,350,425,434,377,413** Routine Name: ORCDPS2 Before: B68753642 After: B72806724 **94,116,125,131,243,311,350, 377,413** Routine Name: ORDSGCHK Before: B98434392 After: B98880623 **280,352,345,311,384,395,382, 481,413** Routine Name: ORMPS1 Before: B74117658 After: B79616579 **86,92,94,116,134,152,158,149, 190,195,215,265,275,243,280, 350,382,397,413** Routine Name: ORMPS2 Before: B52865592 After: B57616139 **94,116,129,134,186,190,195, 215,265,243,280,363,350,462, 413** Routine Name: ORMPS3 Before: B25338633 After: B28811872 **213,243,413** Routine Name: ORWDPS2 Before: B66925440 After: B67243163 **85,116,125,131,132,148,141, 195,215,258,243,424,420,454, 452,377,413** Routine list of preceding patches: 377, 397, 462, 481 ============================================================================= User Information: Entered By : Date Entered : MAY 05, 2015 Completed By: Date Completed: SEP 14, 2020 Released By : Date Released : SEP 17, 2020 ============================================================================= Packman Mail Message: ===================== No routines included