$TXT Created by NNE at MNTVBB.DOMAIN.EXT (KIDS) on Wednesday, 12/18/24 at 09:27 ============================================================================= Run Date: JAN 29, 2025 Designation: PSO*7*783 Package : PSO - OUTPATIENT PHARMACY Priority: Mandatory Version : 7 SEQ #641 Status: Released Compliance Date: FEB 05, 2025 ============================================================================= Associated patches: (v)PSO*7*746 <<= must be installed BEFORE `PSO*7*783' Subject: ERX ERROR HANDLING Category: - Routine Description: ============ This patch addresses the following issue: Ticket INC36783061: Multiple users are experiencing delays at the Inbound eRx hub. Users are not receiving e-prescriptions, there is a lag time. **This patch is approved for both VA VistA and EHRM sites.** Patch Components: ----------------- Files & Fields Associated: File Name (Number) Field Name (Number) New/Modified/Deleted ------------------ ------------------- -------------------- N/A Forms Associated: Form Name File Number 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 New Service Requests (NSRs): N/A Patient Safety Issues (PSIs): Defect Tracking System Ticket(s) & Overview: -------------------------------------------- Ticket INC36783061: Multiple users are experiencing delays at the Inbound eRx hub. Users are not receiving e-prescriptions, there is a lag time. Problem: -------- Error handling in the VistA Incoming eRx routine does not always return a result, therefore causing a delay in the eRx hub. Resolution: ----------- Update the error handling in the VistA Incoming eRx routine to always return a result in order to prevent delays at the eRx hub. Technical Resolution: --------------------- Routine PSOERXI1 will be updated in the INCERX tag to add logic for error handling, and there will be the addition of a new ERROR tag. These changes will prevent delays at the eRx hub since it will always return a result. Before changes INCERX tag: INCERX(RES,XML,PRCHK,PACHK,DACHK,STATION,DIV,ERXHID,ERXVALS,XML2,VADAT, XML3) ; N CURREC,FDA,EIEN,ERRTXT,ERRSEQ,PACNT,PASCNT,PAICN,PAIEN,VAINST,NPI,VAOI, VPATINST,PRVAUTOV After changes INCERX tag: INCERX(RES,XML,PRCHK,PACHK,DACHK,STATION,DIV,ERXHID,ERXVALS,XML2,VADAT, XML3) ; ;p783 This error handling prevents delays at the eRx Hub because it always returns a result N $ESTACK,$ETRAP S $ETRAP="D ERROR^PSOERXI1" N CURREC,FDA,EIEN,ERRTXT,ERRSEQ,PACNT,PASCNT,PAICN,PAIEN,VAINST,NPI,VAOI, VPATINST,PRVAUTOV New ERROR tag: ERROR ;p783 Error Handling D ^%ZTER S RES="1^eRx received but there was an error. See error trap at "_$P($TR($$SITE^VASITE(),"^","-"),"-",1,2) Q Test Sites: ----------- Fayetteville VAMC, Fayetteville AR Erie VAMC, Erie PA SNOW Change Order #: -------------------- Fayetteville VAMC - CO# - CHG0559395 Erie VAMC - CO# - CHG0560310 Software and Documentation Retrieval Instructions: -------------------------------------------------- The software for this patch is being released in a PackMan message. Patch Installation: ------------------- Pre-Installation Instructions: This patch may be loaded with users on the system. You may wish to install it during non-peak hours. Installation will take less than 1 minute. Installation Instructions: 1. Choose the PackMan message containing this build. Then select the INSTALL/CHECK MESSAGE PackMan option to load the build. 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. (ex. PSO*7.0*783) 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. You must use this option and specify what to backup; the entire Build or just Routines. The backup message can be used to restore the routines and components of the build to the pre-patch condition. i. At the Installation option menu, select Backup a Transport Global. ii. At the Select INSTALL NAME prompt, enter your build PSO*7.0*783. iii. When prompted for the following, enter "R" for Routines or "B" for Build. Select one of the following: B Build R Routines Enter response: Build iv. When prompted "Do you wish to secure your build? NO//", press and take the default response of "NO". v. When prompted with, "Send mail to: Last name, First Name", press to take default recipient. Add any additional recipients. vi. When prompted with "Select basket to send to: IN//", press and take the default IN mailbox or select a different mailbox. 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 Back-out/Rollback Strategy: --------------------------- Back-out will be done only with the concurrence and participation of development team and appropriate VA site/region personnel. The decision to back-out or rollback software will be a joint decision between development team, VA site/region personnel and other appropriate VA personnel. Prior to installing an updated KIDS package, the site/region should have saved a backup of the BUILD in a mail message using the Backup a Transport Global [XPD BACKUP] menu option (this is done at time of install). The message containing the backed-up build can be loaded with the "Xtract PackMan" function at the Message Action prompt. The Packman function "INSTALL/CHECK MESSAGE" is then used to install the backed up routines onto the VistA System. The back-out plan is to restore the build from the backup created. No data was modified by this patch installation and, therefore, no rollback strategy is required. Validation of Back-out Procedure: --------------------------------- The Back-out Procedure can be verified by confirming the checksums have been returned to the pre-patch value using CHECK1^XTSUMBLD. It can also be verified by printing the first 2 lines of the PSO routine(s) contained in this patch using the option First Line Routine Print [XU FIRST LINE PRINT]. Once the routine(s) contained in this patch have been backed out, the Second line of each routine will no longer contain the designation of patch PSO*7.0*783. Routine Information: ==================== The second line of each of these routines now looks like: ;;7.0;OUTPATIENT PHARMACY;**[Patch List]**;DEC 1997;Build 1 The checksums below are new checksums, and can be checked with CHECK1^XTSUMBLD. Routine Name: PSOERXI1 Before: B67204950 After: B70682385 **581,617,692,706,700,743,746,783** Routine list of preceding patches: 746 ============================================================================= User Information: Entered By : Date Entered : DEC 18, 2024 Completed By: Date Completed: JAN 28, 2025 Released By : Date Released : JAN 29, 2025 ============================================================================= Packman Mail Message: ===================== $END TXT