$TXT Created by MNTVBB.DOMAIN.EXT (KIDS) on Thursday, 10/14/21 at 12:52 ============================================================================= Run Date: FEB 03, 2022 Designation: PSO*7*656 Package : PSO - OUTPATIENT PHARMACY Priority: Mandatory Version : 7 SEQ #542 Status: Released Compliance Date: MAR 06, 2022 ============================================================================= Associated patches: (v)PSO*7*365 <<= must be installed BEFORE `PSO*7*656' Subject: REMOTE MEDS (RDI) DISPLAYS INCORRECT NUMBER OF REFILLS Category: - Routine Description: ============ This patch will resolve the following issue: INC19182976 - Remote Data Interoperability (RDI) displays incorrect number of refills remaining for remote prescriptions Patient Safety Issues (PSIs): ----------------------------- N/A Defect Tracking System Ticket(s) & Overview: ============================================ INC19182976 - Remote Data Interoperability (RDI) displays incorrect number of refills remaining for remote prescriptions Problem: -------- Patch PSO*7*294 introduced API RDI^PSOQ0595 for creation of TIU objects and Health Summary Components to gather remote VA medications via the Remote Data Interoperability (RDI) web service. On remote outpatient prescriptions the API was displaying the original number of refills for prescriptions but incorrectly labeled them as "X refills remaining". The corresponding expiration date displayed is correct. Below is an example of the incorrect labeling for the refill count: Active Medications from Remote Data DIPHENHYDRAMINE HCL 25MG CAP Sig: TAKE ONE CAPSULE BY MOUTH DAILY FOR 30 DAYS Quantity: 30 Days Supply: 90 3 refills remaining until 04/22/22 Last filled 05/23/21 at DAYTSHR TEST LAB (Active) The reporting site said this is misleading and users must use JLV to verify prescriptions information. Since actual number of refills is not available to the API, the code needs to be updated to correctly label the original refill count. Resolution: ----------- The following changes were made to address the issue listed above: Change the name of description to match with the data Technical Resolution: --------------------- The RDI web service only provides the original number of refills to the RDI^PSOQ0595 API. The number of refills remaining is not provided and so cannot be displayed. To match up with the data, the API code was changed at OBJ+15^PSOQ0595 so that the label "X refills remaining until MM/DD/YY" becomes "Original # of Refills" and "Rx Expiration". The new display now looks like: Active Medications from Remote Data DIPHENHYDRAMINE HCL 25MG CAP Sig: TAKE ONE CAPSULE BY MOUTH DAILY FOR 30 DAYS Quantity: 30 Days Supply: 90 Original # of Refills: 3 Rx Expiration: 04/22/22 Last filled 05/23/21 at DAYTSHR TEST LAB (Active) Test Sites: ----------- Detroit/Allen Park - John D. Dingell VA Medical Center (Detroit, MI) Black Hills HCS - (Fort Meade, SD) 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. It is not necessary to disable any options. 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*656) 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*656. 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/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. If the patch was backed up for the build, from the Kernel Installation and Distribution System Menu, select the Installation Menu. Then select the Install Package(s) option and choose the patch (PSO*7.0*656b) to install. The back-out plan is to restore the routines 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 two lines of the routines contained in this patch using the First Line Routine Print [XU FIRST LINE PRINT] option. After the routines contained in this patch have been backed out, the second line of the routines will no longer contain the designation of this patch in the patch list section. 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: PSOQ0595 Before: B12587476 After: B12903505 **294,365,656** Routine list of preceding patches: 365 ============================================================================= User Information: Entered By : Date Entered : SEP 24, 2021 Completed By: Date Completed: FEB 02, 2022 Released By : Date Released : FEB 03, 2022 ============================================================================= Packman Mail Message: ===================== $END TXT