$TXT Created by CLN1G1.AAC.DOMAIN.EXT (KIDS) on Thursday, 11/07/19 at 17:32 ============================================================================= Run Date: FEB 20, 2020 Designation: PSO*7*570 Package : PSO - OUTPATIENT PHARMACY Priority: Mandatory Version : 7 SEQ #477 Status: Released Compliance Date: MAR 22, 2020 ============================================================================= Associated patches: (v)PSO*7*482 <<= must be installed BEFORE `PSO*7*570' (v)PSO*7*504 <<= must be installed BEFORE `PSO*7*570' (v)PSO*7*564 <<= must be installed BEFORE `PSO*7*570' Subject: BARCODE BATCH WRONG SIG, ERX '&', ERX DD, CLINICAL ALERTS PROMPT Category: - Routine - Data Dictionary Description: ============ This patch will resolve the following issues. INC6718169 - Barcode Batch Prescription Entry option changed RX sig INC6810860 - eRX Files should have fileman access same as other pharmacy INC7092487 - HRC - Incomplete VISTA entry for Inbound Electronic Prescription VISTA team -- Electronic RX denotation not in all menu options INC6075139 - Fix a programming standards error, routine PSODEMSB INC7535060 - New Prompt while Processing Rxs Patient Safety Issues (PSIs): ----------------------------- HITPS-6573: Barcode Batch Prescription Entry option changed RX sig Summary: When processing renewals with option "Barcode Batch Prescription Entry" [PSO BATCH BARCODE], if a user answers "YES" to "Edit renewed RX" and then uses "^" to exit the prescription, the renewal RX is deleted but the SIG from the deleted RX is applied to the next prescription to be renewed. This results in the second prescription renewal having the SIG from the prior prescription. Defect Tracking System Ticket(s) & Overview: -------------------------------------------- 1. INC6718169 - Barcode Batch Prescription Entry option changed RX sig Problem: -------- In certain situations when renewing prescriptions using the Barcode Batch Prescription Entry [PSO BATCH BARCODE] option, the sigs from one prescription can carry over to the next prescription, overwriting the second prescription's sig thereby causing the subsequent prescription to be saved with the wrong sig. Resolution: ----------- This patch fixes the "SIG" carry over to the next prescription when using the Barcode Batch Prescription Entry [PSO BATCH BARCODE] option to renew prescriptions. Technical Resolution: --------------------- Changed routine PSOBBC at PROCESS+5 label to kill the SIG variable when starting the Barcode Batch Prescription Entry [PSO BATCH BARCODE] option. 2. INC6810860 - eRX Files should have Fileman access same as other pharmacy Problem: -------- For sites using Classic Fileman file access, the following eRX files can't be accessed by Fileman for reading since these eRX files are currently set to "@" (developer) access. These eRX files are useful for running workload related to eRX orders filled by pharmacy by local ADPACs and supervisors. However, these files require @ access. Access levels should be set to "P" like all other pharmacy files. eRX Files: ERX EXTERNAL PATIENT (#52.46) ERX EXTERNAL PERSON (#52.48) ERX EXTERNAL PHARMACY (#52.47) ERX HOLDING QUEUE (#52.49) ERX SERVICE REASON CODES (#52.45) Resolution: ----------- This patch fixes the Data Dictionaries (DD) for the 5 eRX files #52.45 thru #52.49 to allow all users Read access to these files. Technical Resolution: --------------------- A Post install routine, PSO7P570, will change the "RD" (read) access only from "@" to "Pp", which allows standard users and Supervisor users to read these files via Fileman inquiry, search, and printing options. This fix only applies to VAMC sites that are still using the Classic Fileman file access and have not enabled the File Access Security (Formerly Part 3 of Kernel) file access. 3. INC7092487 - HRC - Incomplete VISTA entry for Inbound Electronic Prescription VISTA team -- Electronic RX denotation not in all menu options Problem: -------- The electronic prescription (eRx) notation "&" is missing for eRx prescriptions when listing the medications using the Medication Profile and Refill [PSO HRC PROFILE/REFILL] option. This option can be found under the HRC Pharmacy Menu [DVBA HRC MENU PHARMACY] option. This was inadvertently left out during the original eRx development. Resolution: ----------- This patch fixes this issue by printing the eRx notation "&" before listing the prescription number for the Medication Profile and Refill [PSO HRC PROFILE/REFILL] option. Technical Resolution: --------------------- Routine PSOPMP0 was modified at label SETLINE to print the eRx notation "&" after making sure that it's an eRx prescription. 4. INC6075139 - Fix a programming standards error, routine PSODEMSB Problem: ------- Non-standard code (violates the SACC standard) exists in routine PSODEMSB for testing for the output device to determine if the report is running from VistA or from CPRS. Technical Resolution: ----------------------- The corrected code of IO=IO(0) will replace the non-standard code of $I=$P in routine PSODEMSB. This will correct the code to match VA programming standards. 5. INC7535060 - New Prompt while Processing Rxs Problem: ------- In routine PSODEMSB at line HDR+3, the variable PG was removed from the "IF" condition check, causing this extra prompt to display when printing to the screen: Type to continue or '^' to exit Clinical Alerts: Technical Resolution: ----------------------- Revert the removed code related to variable PG specifically connected to the display of the prompt back into routine PSODEMSB as it originally was. Test Sites: ----------- North Florida/South Georgia - VA HCS Heartland - West (Kansas City, Columbia, Topeka, Leavenworth, Wichita) Pre/Post Installation Overview: ------------------------------- It is not necessary to disable any options. Pre-Installation Instructions: ------------------------------ This patch should be installed during non-peak hours to minimize potential disruption to users. This patch should take less than 2 minutes to install. Installation Instructions: -------------------------- 1. Choose the PackMan message containing this patch. 2. Choose the INSTALL/CHECK MESSAGE PackMan option. 3. From the Kernel Installation and Distribution System Menu, select the Installation Menu. From this menu, you may elect to use the following options. When prompted for the INSTALL NAME enter the patch # (ex. PSO*7.0*570): a. Backup a Transport Global - This option will create a backup message of any routines exported with this patch. It will not backup any other changes, such as DDs or templates. b. 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 components of this patch: routines, DDs, templates, etc.). c. Verify Checksums in Transport Global - This option will allow you to ensure the integrity of the routines that are in the transport global. 4. From the Installation Menu, select the Install Package(s) option and choose the patch to install. 5. When Prompted "Want KIDS to INHIBIT LOGONs during the install? NO//" respond NO. 6. When Prompted "Want to DISABLE Scheduled Options, Menu Options, and Protocols? NO//" respond NO. 7. If prompted 'Delay Install (Minutes): (0-60): 0//' respond 0. 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 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 Procedures: -------------------- 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. Routine Information: ==================== The second line of each of these routines now looks like: ;;7.0;OUTPATIENT PHARMACY;**[Patch List]**;13 Feb 97;Build 8 The checksums below are new checksums, and can be checked with CHECK1^XTSUMBLD. Routine Name: PSO7P570 Before: n/a After: B1693421 **570** Routine Name: PSOBBC Before:B111560977 After:B111978693 **11,22,27,34,46,130,146,185, 242,264,300,337,313,473,504, 570** Routine Name: PSODEMSB Before: B62149131 After: B62722413 **452,564,570** Routine Name: PSOPMP0 Before: B96962935 After:B100823451 **260,281,303,289,382,313,427, 500,482,570** Routine list of preceding patches: 482, 504, 564 ============================================================================= User Information: Entered By : Date Entered : AUG 05, 2019 Completed By: Date Completed: FEB 19, 2020 Released By : Date Released : FEB 20, 2020 ============================================================================= Packman Mail Message: ===================== $END TXT