$TXT Created by L at CLN1G2.AAC.DOMAIN.EXT (KIDS) on Tuesday, 11/02/21 at 07:46 ============================================================================= Run Date: FEB 01, 2022 Designation: PSS*1*255 Package : PSS - PHARMACY DATA MANAGEMENT Priority: Mandatory Version : 1 SEQ #220 Status: Released Compliance Date: MAR 04, 2022 ============================================================================= Associated patches: (v)PSS*1*189 <<= must be installed BEFORE `PSS*1*255' Subject: CS SCHED 2 DAYS SUPPLY EXCEEDED Category: - Routine Description: ============ This patch will resolve the following issue: A provider, using CPRS, was able to place an order for a DEA Schedule II medication for greater than a 30 day supply. Associated ticket(s): ===================== INC16979135 - Prescriptions for DEA Schedule II medication allowed to be entered for greater than 30 days supply Defect Tracking System Ticket(s) & Overview: -------------------------------------------- INC16979135 - Prescriptions for DEA Schedule II medication allowed to be entered for greater than 30 days supply Problem: ------- A provider was able to enter a prescription through CPRS with a days supply of greater than 30 days for a DEA Schedule II medication. This issue occurs for a pharmacy orderable item that is linked to only 1 drug in the drug file. It was discovered during the testing of version 1 of this patch that the maximum days supply assigned for a DEA Schedule II medication was incorrect when an orderable item has an inactive dispense drug with no DEA schedule assigned to it. It was also discovered during testing that for an orderable item with a dispense drug with a DEA schedule of II and another dispense drug with a DEA schedule III a maximum days of supply was assigned as 90. Resolution: ----------- A modification was made to assign the lowest value of days as the maximum days of supply for any drug linked to the orderable item. For example, if an orderable is linked to two dispense drugs and one has a DEA schedule II (max 30 days) and the other has a DEA schedule III (max 90 days) than the maximum days supply for the orderable will be assigned as 30 days, the lowest schedule of the two. Technical Resolution: --------------------- A modification was made at API MAXDS+11^PSSUTIL1 that will assign the maximum days supply based on the lowest dispense drug schedule for the dispense drugs linked to the orderable. Previous code: . . S DRGMAXDS=$$MXDAYSUP(DRG) I DRGMAXDS>MAXDS S MAXDS=DRGMAXDS Revised code: . . S DRGMAXDS=$$MXDAYSUP(DRG) I DRGMAXDS' Patient Safety Issues (PSIs): ----------------------------- N/A Test Sites: ----------- Atlanta VAMC, Decatur GA Martinsburg VAMC, Martinsburg WV 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 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 2 minutes to install. For this install there are no options that are required to be disabled. 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 PSS*1.0*255. 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 PSS*1.0*255. 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. a. When prompted 'Enter options you wish to mark as 'Out Of Order':', press the Enter key. b. When prompted 'Enter protocols you wish to mark as 'Out Of Order':', press the Enter key. c. When prompted 'Delay Install (Minutes): (0 - 60): 0//', answer 0. Back-out/Rollback Strategy: =========================== Post-Installation Instructions: ------------------------------- 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 (255) in the [PATCH LIST] section. ;;1,0;PHARMACY DATA MANAGEMENT;**[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/Roll Back Plan: ------------------------ 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 PSS*1.0*255 patch have been rolled back, the first two lines of the Routines will no longer contain the designation of patch PSS*1.0*255 in the patch list section on line 2. Routine Information: ==================== The second line of each of these routines now looks like: ;;1.0;PHARMACY DATA MANAGEMENT;**[Patch List]**;9/30/97;Build 2 The checksums below are new checksums, and can be checked with CHECK1^XTSUMBLD. Routine Name: PSSUTIL1 Before: B48136582 After: B48508434 **38,66,69,166,189,255** Routine list of preceding patches: 189 ============================================================================= User Information: Entered By : Date Entered : AUG 13, 2021 Completed By: Date Completed: FEB 01, 2022 Released By : Date Released : FEB 01, 2022 ============================================================================= Packman Mail Message: ===================== $END TXT