$TXT Created by MNTVBB.DOMAIN.EXT (KIDS) on Wednesday, 11/27/24 at 14:03 ============================================================================= Run Date: JAN 14, 2025 Designation: PSO*7*768 Package : PSO - OUTPATIENT PHARMACY Priority: Mandatory Version : 7 SEQ #637 Status: Released Compliance Date: FEB 14, 2025 ============================================================================= Associated patches: (v)PSO*7*324 <<= must be installed BEFORE `PSO*7*768' (v)PSO*7*441 <<= must be installed BEFORE `PSO*7*768' (v)PSO*7*568 <<= must be installed BEFORE `PSO*7*768' Subject: PROCESSING STATUS INACCURATE Category: - Routine Description: ============ This patch addresses the following issue: PROCESSING STATUS INACCURATE - This patch is approved to be installed at EHRM converted 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 Additional Information: ----------------------- New Service Requests (NSRs): N/A Patient Safety Issues (PSIs): ----------------------------- N/A Defect Tracking System Ticket(s) & Overview: INC33057335 - PROCESSING STATUS INACCURATE Problem: -------- Processing status during order checks is showing Released by CMOP for an RX that was released at Window. The issue occurs when a RX is dispensed to CMOP and is refilled for Window dispense. Resolution: ----------- PSOCMOPA was returning a variable containing the most recent CMOP data when the most recent fill was dispensed to Window. Modify routine PSOCMOPA, PSODDPRE, PSODRDUP and PSODRDU2 so that CMOP data is not displayed when the most recent fill was window for a CMOP RX. Technical Resolution: --------------------- Routine PSOCMOPA is modified to return variable PSOCMOP as null the most recent fill was not a CMOP fill. PSOCMOPA+14^PSOCMOPA is modified to ;PSO*7*768 QUIT IF THE FILL IS NOT CMOP I CMOP("L")>0,$P(^PSRX(DA,1,CMOP("L"),0),U,2)'="M" Q PRSTAT^PSODDPRE is modified to display (Mail) or (Window) based on the refill record value in field MAIL/WINDOW/PARK in the PRESCRIPTION file #52. PRSTAT+12 is added tom initialize new variable PSORFL .S PSORFL="" PRSTAT+14 is added to save refill# value ..S PSORFL=PSOX ;PSO*7*768 PRSTAT+19 IS MODIFIED TO .;PSO*7*768 display refill MAIL/WINDOW/PARK value .S PSOMW="" .I PSORFL S PSOMW=$S($P(^PSRX(RXREC,1,PSORFL,0),"^",2)="W":" (Window)",1:" (Mail)") .I PSOMW="" S PSOMW=$S($P(^PSRX(RXREC,0),"^",11)="W":" (Window)",1:" (Mail)") .W:'$G(PSODUPF) $S(PSOLRD="":"Not released locally",1:"Released locally on "_$$FMTE^XLFDT($P(PSOLRD,"^"),2)_" "_$P(PSOLRD,"^",2))_PSOMW PRSTAT^PSODRDUP is modified to display (Mail) or (Window) based on the refill record value in field MAIL/WINDOW/PARK in the PRESCRIPTION file #52. PRSTAT+15 added: ..S PSORFL=PSOX ;PSO*7*768 PRSTAT+20 is changed to .;PSO*7*768 .S PSOMW="" .I PSORFL S PSOMW=$S($P(^PSRX(RXREC,1,PSORFL,0),"^",2)="W":" (Window)",1:" (Mail)") .I PSOMW="" S PSOMW=$S($P(^PSRX(RXREC,0),"^",11)="W":" (Window)",1:" (Mail)") .W $S(PSOLRD="":"Not released locally",1:"Released locally on "_$$FMTE^XLFDT($P(PSOLRD,"^"),2)_" "_$P(PSOLRD,"^",2))_PSOMW PRSTAT^PSODRDU2 is modified to display (Mail) or (Window) based on the refill record value in field MAIL/WINDOW/PARK in the PRESCRIPTION file #52. PRSTAT+13 added: ..S PSORFL=PSOX ;PSO*7*768 PRSTAT+18 is changed to .;pso768 .S PSOMW="" .I PSORFL S PSOMW=$S($P(^PSRX(RXREC,1,PSORFL,0),"^",2)="W":" (Window)",1:" (Mail)") .I PSOMW="" S PSOMW=$S($P(^PSRX(RXREC,0),"^",11)="W":" (Window)",1:" (Mail)") .W $S(PSOLRD="":"Not released locally",1:"Released locally on "_$$FMTE^XLFDT($P(PSOLRD,"^"),2)_" "_$P(PSOLRD,"^",2))_PSOMW Test Sites: ----------- Chillicothe VAMC (Chillicothe, OH) VA New Jersey HCS (East Orange, NJ) Test Sites - SNOW Change Order #: -------------------------------- Chillicothe VAMC - CHG0552224 VA New Jersey HCS - CHG0552408 Software and Documentation Retrieval Instructions: -------------------------------------------------- The software for this patch is being released in a PackMan message. Documentation describing the new functionality is not included in this release. Patch Installation: ------------------- 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. 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*768) 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*768 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 printing the first 2 lines of the routines contained in this patch using the option First Line Routine Print [XU FIRST LINE PRINT]. Once the build contained in the PSO*7.0*768 patch has been backed out, the first two lines of the routine will no longer contain the designation of this patch in the patch list section on line 2. Routine Information: ==================== The second line of each of these routines now looks like: ;;7.0;OUTPATIENT PHARMACY;**[Patch List]**;DEC 1997;Build 12 The checksums below are new checksums, and can be checked with CHECK1^XTSUMBLD. Routine Name: PSOCMOPA Before: B21736960 After: B22326197 **61,76,443,508,441,768** Routine Name: PSODDPRE Before:B141793853 After:B144226528 **251,375,387,379,390,372,416, 411,518,568,768** Routine Name: PSODRDU2 Before: B22803524 After: B23856111 **132,251,375,387,441,768** Routine Name: PSODRDUP Before: B48009751 After: B49168107 **11,23,27,32,39,56,130,132, 192,207,222,243,305,324,768** Routine list of preceding patches: 324, 441, 568 ============================================================================= User Information: Entered By : Date Entered : JUL 08, 2024 Completed By: Date Completed: JAN 13, 2025 Released By : Date Released : JAN 14, 2025 ============================================================================= Packman Mail Message: ===================== $END TXT