$TXT Created by F at CLN1G1.AAC.DOMAIN.EXT (KIDS) on Friday, 05/29/20 at 07:23 ============================================================================= Run Date: JUN 26, 2020 Designation: PSO*7*603 Package : PSO - OUTPATIENT PHARMACY Priority: EMERGENCY Version : 7 SEQ #493 Status: Released Compliance Date: JUN 30, 2020 ============================================================================= Associated patches: (v)PSO*7*531 <<= must be installed BEFORE `PSO*7*603' Subject: OPAI RELEASE OF FILL/PARTIAL UPDATES WRONG INFORMATION IN VISTA Category: - Routine Description: ============ A prescription has a fill or refill or a partial sent to OPAI, and then the fill/refill/partial is released in OPAI. VistA may file the releasing information in the wrong fill/refill/partial. Users will have to release the missing fill/refill/partial manually. This issue has been seen with both ScriptPro and Optifill OPAI interfaces. The following tickets are addressed by this patch: 1) INC9398751 - Partialed RXs are not releasing automatically from VISTA Duplicates: INC9586108 - outpatient partial Rxs not releasing after PSO*7*531 INC9663815 - VistA: Outpatient Pharmacy: Rx Won't Go to CMOP Because of Local Partial? INC9768476 - Issue with VistA option PSO LM BACKDOOR ORDERS - Refill is released instead of partial then Rx cannot be suspended to CMOP INC9792380 - Scriptpro not releasing partial filled rx since PSO*7*531 INSTALL INC9744639 - kb0107373 - GLA PARTIALS NOT RELEASING/SCRIPTPRO Patient Safety Issues (PSIs): ----------------------------- HITPS-7143 - INC9398751/INC9586108/INC9663815/INC9768476/INC9792380/INC9744639 Defect Tracking System Ticket(s) & Overview: -------------------------------------------- 1) INC9398751 - Partialed RXs are not releasing automatically from VISTA Problem 1: ---------- VA New Jersey Health Care System reported that after the installation of patch PSO*7*531, partial fills are no longer being automatically released when the dispense message is received from the OPAI (Outpatient Pharmacy Automated Interface) dispensing machines. The issue happens because incoming messages from OPAI don't identify whether a fill was a partial or a regular fill. It was confirmed that this issue was indeed caused by the patch PSO*7*531. - A new prescription is entered and is sent to the OPAI dispensing machine (Original Fill) - Before the Original Fill can be processed by the OPAI dispensing machine a Partial Fill is ordered and also sent to the OPAI dispensing machine. - When the OPAI dispensing machine dispenses the Partial Fill and returns the HL7 message back to VistA it will erroneously populate the Release Date for the Original Fill instead of the Partial Fill. Note: This problem has different effects for sites using ScriptPro and OptiFill. OptiFill sites will have a problem with Partial Fills placed on an unreleased prescription without any refills, while ScriptPro will have a problem with Partial Fills placed on a prescription with a single un-released refill. Resolution 1: ------------- This patch changes the logic for matching incoming HL7 message from OPAI dispensing machines by matching it with the outgoing HL7 message via the MESSAGE SERVER ID field (#10) in the PHARMACY EXTERNAL INTERFACE file (#52.51) first. This logic should always find a match, however, if for some reason the matching fails it will resort to matching the Rx# along with the fill, which should work as well. Technical Resolution 1: ----------------------- Changed the routine PSOHLDS at line tag FACK2 to re-write the logic for matching an incoming HL7 OPAI message with a record in the PHARMACY EXTERNAL INTERFACE file (#52.51). The old logic was improved and left in place in case the new logic fails for any reason. The change will assure an accurate matching of an incoming HL7 OPAI message to the corresponding record in the PHARMACY EXTERNAL INTERFACE file (#52.51). Test Sites: ----------- New Jersey Health Care System (East Orange, NJ) Central California VA Health Care System (Fresno, CA) West Palm Beach VA Medical Center (West Palm Beach, FL) Sioux Falls VA Health Care System (Sioux Falls, SD) 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. 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 the patch or build name: PSO*7.0*603 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. When prompted 'Want KIDS to INHIBIT LOGONs during the install? NO//', respond NO. ii. When prompted 'Want to DISABLE Scheduled Options, Menu Options, and Protocols? NO//', respond NO. 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. Validation of Roll Back Procedure --------------------------------- The Roll Back 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*603 patch have been rolled back, the first two lines of the Routines will no longer contain the designation of patch PSO*7.0*603 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 8 The checksums below are new checksums, and can be checked with CHECK1^XTSUMBLD. Routine Name: PSOHLDS Before: B97827687 After:B106593360 **156,312,354,531,603** Routine list of preceding patches: 531 ============================================================================= User Information: Entered By : Date Entered : MAR 05, 2020 Completed By: Date Completed: JUN 26, 2020 Released By : Date Released : JUN 26, 2020 ============================================================================= Packman Mail Message: ===================== $END TXT