$TXT Created by F at CLN1G1.AAC.DOMAIN.EXT (KIDS) on Tuesday, 08/18/20 at 15:06 ============================================================================= Run Date: NOV 30, 2020 Designation: PSO*7*621 Package : PSO - OUTPATIENT PHARMACY Priority: Mandatory Version : 7 SEQ #509 Status: Released Compliance Date: DEC 30, 2020 ============================================================================= Associated patches: (v)PSO*7*512 <<= must be installed BEFORE `PSO*7*621' (v)PSO*7*612 <<= must be installed BEFORE `PSO*7*621' Subject: CLOZAPINE ISSUES - FACTIONAL QTY, EXPIRATION DATE CALCULATION & REG. DATE RESET Category: - Routine Description: ============ This patch will address the following issues: 1. INC11549905 - when you enter a new prescription the QTY rounds up unless you change the days supply. 2. INC11595547 - CLOZAPINE ORDER - Day Supply- Quantity - # of Refill - Expiration date calculation 3. INC11627662 - PSOL EDIT - Edit Data for a Patient in the Clozapine Program Defect Tracking System Ticket(s) & Overview: -------------------------------------------- 1. INC11549905 - when you enter a new prescription the QTY rounds up unless you change the days supply. Problem: -------- The Oscar G. Johnson VA Medical Center reported that when editing the Days Supply fields for a Clozapine prescription that the QTY field value is not rounding up, instead it remains a factional value, forcing the user to fix it manually. Resolution: ----------- The issue was confirmed and the calculation of the QTY value was fixed to round any fractional value up. So, if the automatic calculation results in a value such 4.2, for example, it will be rounded up to 5. Technical Resolution: --------------------- Changed the routine PSOCLUTL at line tag QTYCHK+9 to always round the value of the variable QTY up. S:QTY PSORXARY("QTY")=(QTY+.99)\1,$P(PSORXARY("RX0"),U,7)=(QTY+.99)\1 2. INC11595547 - CLOZAPINE ORDER - Day Supply- Quantity - # of Refill - Expiration date calculation Problem: -------- After the installation of patch PSO*7*574 the expiration date calculation for clozapine prescriptions is wrong for some scenarios after editing the # of Refills or Days Supply fields. For example, when you edited a prescription with 28-day supply and 0 refills, with an expiration date of 28 past the issue date, to 14-day supply and 1 refill it was setting the expiration to 14 days past the issue date, instead of keeping the 28 days. Resolution: ----------- The calculation of the expiration date for clozapine prescriptions was resolved to correctly calculate the total number of days supply of the entire prescription, including the refills. Technical Resolution: --------------------- Removed a line of code in the PSOEXDT routine (shown below) introduced by PSO*7*574 that was preventing the expiration date from being calculated correctly for clozapine prescriptions. ; Added Clozapine check to not modify Expires date ; PSO*574 A Q:+$G(PSORXED("CLOZ EDIT")) 3. INC11627662 - PSOL EDIT - Edit Data for a Patient in the Clozapine Program Problem: -------- After the installation of patch PSO*7*574 the option Edit Data for A Patient in the Clozapine Program [PSOL EDIT] started resetting the REGISTRATION DATE field (#58) in the PHARMACY PATIENT file (#55) even after the user simply returns through the 3 fields in the option without modifying any of them. The REGISTRATION DATE field should only be reset when the user changes the value of the CLOZAPINE REGISTRATION NUMBER. Edit Data for a Patient in the Clozapine Program [PSOL EDIT] Edit Data for a Patient in the Clozapine Program Select clozapine patient : CLOZPAT,TEST CLOZAPINE REGISTRATION NUMBER: MR12345// MR12345 CLOZAPINE STATUS: ACTIVE TREATMENT RESPONSIBLE PROVIDER: TEST,PROVIDER// TEST,PROVIDER Resolution: ----------- The Clozapine REGISTRATION DATE will only be reset when the value of the CLOZAPINE REGISTRATION NUMBER is modified. Furthermore, if the user just through the fields without making any changes it will display "No changes made." Edit Data for a Patient in the Clozapine Program [PSOL EDIT] Edit Data for a Patient in the Clozapine Program Select clozapine patient : CLOZPAT,TEST CLOZAPINE REGISTRATION NUMBER: MR12345// MR12345 CLOZAPINE STATUS: ACTIVE TREATMENT RESPONSIBLE PROVIDER: TEST,PROVIDER// TEST,PROVIDER No Changes Made. Technical Resolution: --------------------- There were two changes made to the routine PSOCLUTL to address this problem: 1) Added code at the line tag PHY1+4 to check whether any of the fields being edited were modified, if none just display the message "No changes made." and quit. 2) Added a condition at the line tag SAVE+1 to only reset the REGISTRATION DATE value if the CLOZAPINE REGISTRATION NUMBER value was modified. Test Sites: ----------- Oscar G. Johnson VA Medical Center (Iron Mountain, MI) VA New Jersey Health Care System (East Orange, Lyons) Software and Documentation Retrieval Instructions: ------------------------------------- The software for this patch is being released in a PackMan message. 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. Staff should not be processing prescriptions while patch is being installed. 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 PSO*7.0*621 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 Back-out/Rollback Strategy: =========================== Post Installation Instructions: ------------------------------- None. Installation Verification: -------------------------- Successful installation can be verified by reviewing the first 2 lines of the routines contained in the patch. The second line will contain the patch number (618) in the [PATCH LIST] section. ;;7.0;OUTPATIENT PHARMACY;**[Patch List]**;DEC 1997 The option Calculate and Show Checksum Values [XTSUMBLD-CHECK] can be run to compare the routine checksums to what is documented in the patch description. 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 routines 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 routines 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. 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 PSO Routines contained in this patch using the option First Line Routine Print [XU FIRST LINE PRINT]. Once the routines contained in the PSO*7.0*621 patch have been rolled back, the first two lines of the Routines will no longer contain the designation of patch PSO*7.0*621 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 13 The checksums below are new checksums, and can be checked with CHECK1^XTSUMBLD. Routine Name: PSOCLO1 Before:B203292395 After:B206896982 **1,23,37,222,457,574,612,621** Routine Name: PSOCLUTL Before:B131109888 After:B133770797 **28,56,122,222,268,457,574,612,621** Routine Name: PSOEXDT Before: B6664815 After: B6289216 **23,73,222,486,574,621** Routine Name: PSORXED Before:B106523584 After:B107438931 **2,16,21,26,56,71,125,201,246, 289,298,366,385,403,421,482, 512,621** Routine list of preceding patches: 512, 612 ============================================================================= User Information: Entered By : Date Entered : JUL 28, 2020 Completed By: Date Completed: NOV 30, 2020 Released By : Date Released : NOV 30, 2020 ============================================================================= Packman Mail Message: ===================== $END TXT