$TXT Created by at DOSN.FO-BIRM.DOMAIN.EXT (KIDS) on Thursday, 03/07/24 at 15:08 ============================================================================= Run Date: APR 30, 2024 Designation: PSO*7*736 Package : PSO - OUTPATIENT PHARMACY Priority: Mandatory Version : 7 SEQ #619 Status: Released Compliance Date: MAY 08, 2024 ============================================================================= Associated patches: (v)PSO*7*441 <<= must be installed BEFORE `PSO*7*736' (v)PSO*7*643 <<= must be installed BEFORE `PSO*7*736' Subject: ONEVA PHARMACY FROM IBM WEBSPHERE TO VDIF Category: - Routine - Enhancement (Mandatory) Description: ============ The OneVA Pharmacy application provides the Veterans Health Administration (VHA) with the capability to allow Veterans traveling across the United States to refill/partial fill their active VA prescription at any VA Pharmacy regardless of where the prescription originated. The OneVA Pharmacy application design consists of 3 main components: VistA Medication Profile screen, Health Data Record Clinical Data Service (HDR/CDS), and OneVA Pharmacy message flow. The VistA Medication Profile screen expands available pharmacy information in VistA to provide pharmacists direct access to query, and refill/partial fill patient's active and refillable prescriptions. The HDR/CDS provides a patient's active and refillable prescriptions. The OneVA Pharmacy message flow enables the secure, bi-directional exchange of electronic health records between local/remote VistA Servers, and between VistA servers and HDR. The OneVA software currently uses IBM Websphere as the messaging system. The IBM Websphere messaging system is being decommissioned. This patch provides the move from using IBM Websphere to using the Veterans Data Information Exchange (VDIF). The software changes include the following: 1. Routine PSORRX1 - DNS value modified at REMOTERX+18 2. Routine PSORRX1 - modified argument list and corresponding references to the DRUGMTCH function 3. Routine PSORRX1 - modified to handle HL7 messages with possible overflow nodes at RXPRSE+4 4. Routine PSOHLDS6 - modified to handle HL7 messages with possible overflow nodes at HOST+2 5. Routine PSOORUT1 - modified "PROVIDER HOLD" status abbreviation from "PH" to "HP" at SHOWREM+13 6. Routine PSOORUT1 - added "DISCONTINUED BY PROVIDER", "DISCONTINUED (EDIT)", and "NON-VERIFIED" status abbreviations at SHOWREM+13 7. HL LOGICAL LINK entry - the post-install routine POST^PSO736PO updates the PSORRXSEND entry of the HL LOGICAL LINK (#870) file. The following fields will be updated to reflect VDIF production IP address and port values when installed in the site's production account: DNS DOMAIN, TCP/IP ADDRESS, and TCP/IP PORT Patch Components: ----------------- Files & Fields Associated: File Name (Number) Field Name (Number) New/Modified/Deleted ------------------ ------------------- -------------------- N/A Forms Associated: Form Name File Number New/Modified/Deleted --------- ----------- -------------------- N/A Mail Groups Associated: Mail Group Name New/Modified/Deleted --------------- -------------------- N/A Options Associated: Option Name Type New/Modified/Deleted ----------- ---- -------------------- N/A Protocols Associated: Protocol Name New/Modified/Deleted ------------------------- -------------------- N/A Security Keys Associated: Security Key Name ----------------- N/A Templates Associated: Template Name Type File Name (Number) New/Modified/Deleted ------------- ---- ------------------ -------------------- N/A Remote Procedures Associated: Remote Procedure Name New/Modified/Deleted --------------------- -------------------- N/A HL7 Application Parameters Associated: HL7 Application Parameter Name New/Modified/Deleted ------------------------------ -------------------- N/A Parameter Definitions Associated: Parameter Name New/Modified/Deleted -------------- -------------------- N/A Additional Information: ----------------------- New Service Requests (NSRs): N/A Patient Safety Issues (PSIs): N/A Defect Tracking System Ticket(s) & Overview: N/A Test Sites: ----------- Miami, FL Kansas City, MO East Orange, NJ Software and Documentation Retrieval Instructions: -------------------------------------------------- The software for this patch is being released in a PackMan message. Documentation describing the new functionality is included in this release. Documentation can be found on the VA Software Documentation Library at: https://www.domain.ext/vdl/. Documentation can also be obtained at https://download.vista.domain.ext/index.html/SOFTWARE. Documentation Title File Name --------------------------------------------------------------------- Outpatient Pharmacy v 7.0 PSO_7_0_P736_PHARM_UM.DOCX Pharmacist's User Manual PSO_7_0_P736_PHARM_UM.PDF Outpatient Pharmacy v 7.0 Manager's PSO_7_0_P736_MAN_UM.DOCX User Manual PSO_7_0_P736_MAN_UM.PDF Outpatient Pharmacy v 7.0 PSO_7_0_P736_TECH_UM.DOCX Technician's User Manual PSO_7_0_P736_TECH_UM.PDF OneVA Pharmacy User Manual PSO_7_0_P736_ONEVA_UM.DOCX PSO_7_0_P736_ONEVA_UM.PDF Outpatient Pharmacy Version 7 PSO_7_0_P736_TM.DOCX Technical Manual Security Guide PSO_7_0_P736_TM.PDF Deployment, Installation, Back-out, PSO_7_0_P736_DIBRG.DOCX and Rollback Guide PSO_7_0_P736_DIBRG.PDF Patch Installation: ------------------- Pre/Post Installation Overview: ============================== The post-install routine POST^PSO736PO will update the PSORRXSEND entry of the HL LOGICAL LINK (#870) file. When installed in production, the DNS DOMAIN, TCP/IP ADDRESS, and TCP/IP PORT fields will be updated with the VDIF server production values. However, when installed in a non-production environment, these 3 fields are updated with null (or blank) values. Any values needed in a non-production account will need to be entered manually using the Link Edit option of the HL7 MAIN MENU. Pre-Installation Instructions: The following instructions are for the HL7 LOGICAL LINK: PSORRXSEND 1. Before installation of the patch, confirm that all messages in the link that need to be delivered have been delivered. Otherwise, they will be lost. This confirmation can be performed by running the SYSTEMS LINK MONITOR option which is under the HL7 MAIN MENU. If messages are not caught up, then wait to install the patch until the message queues for PSORRXSEND are caught up. 2. Once caught up, the PSORRXSEND link will need to be stopped. To stop the PSORRXSEND link, run the Start/Stop Links option which is attached to the Filer and Link Management Options of the HL7 MAIN MENU. 3. Use the HL RESET COUNTERS (TCP ONLY) option on the link. This resets message counters, ensuring the counter is initialized correctly. This patch should be installed when Pharmacy applications are not in use, no other pharmacy patches are being installed, and when tasked jobs from Clinical Applications are not running. Installation should also occur when CPRS usage is at a minimum, particularly medication activities. Installation of this patch should take less than 5 minutes. Installation Instructions (KIDS): --------------------------------- 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*736. ** THE BEFORE CHECKSUM OF 184863002 FOR PSORRX1 IS INCORRECT ** ** DUE TO PSO*7.0*729 HAVING BEEN ENTERED IN ERROR ** ** THE CORRECT CHECKSUM FOR PSORRX1 IS 157938249 ** 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*736 iii. When prompted for the following, enter "B" for Build. Select one of the following: B Build (including Routines) R Routines Only Backup Type: B// 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. When prompted 'Want KIDS to INHIBIT LOGONs during the install? NO//', answer NO. ii. When prompted 'Want to DISABLE Scheduled Options, Menu Options, and Protocols? NO//', answer NO. Post-Installation Instructions: ------------------------------- 1. Start the PSORXXSEND link, which can be performed with the Start/Stop Links option under the Filer and Link Management Options of the HL7 MAIN MENU. 2. Once post install is completed on production systems, perform a ping test. This can be done with the PI Ping (TCP Only) option under the Filer and Link Management Options of the HL7 MAIN MENU and verify connection to the VDIF server as is shown in the example below. Select Filer and Link Management Options Option: PI Ping (TCP Only) What HL Logical Link do you want to test? Select a TCP link:PSORRXSEND Do you want to PING the port used by HLO or the one used by HL7 1.6? Select one of the following: 1 HLO --> Port #5001 2 HL7 1.6 --> Port #6230 Enter response: 1// 2 HL7 1.6 --> Port #6230 Trying to connect... Connected! Sending PING ... PING sent! Reading acknowledgment.... Acknowledgment received! 3. 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;[BUILD #] 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 is only needed if there are major problems (examples include the KIDS notice of incompletion or hard errors) resulting from the installation of this patch. You must have concurrence from Health Product Support before a rollback can occur. Enter a ServiceNow ticket to obtain this concurrence. Prior to installing a patch, 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 KIDS" 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. The back-out plan is to restore the routines from the backup created. The message containing the backed-up build can be loaded with the "Xtract PackMan" function at the Message Action prompt, followed by PackMan function "INSTALL/CHECK MESSAGE." From the Kernel Installation & Distribution System Menu [XPD MAIN], select the Installation menu [XPD INSTALLATION MENU]. Then select the Install Package(s) option [XPD INSTALL BUILD] and choose the patch (PSO*7.0*736b) to install. Installing the backed-up build on the VistA system will restore the PSOORUT1, PSORRX1, and PSOHLDS6 routines. This patch does alter data. Upon installation of this patch, an XTMP global copy of the PSORRXSEND entry of the HL LOGICAL LINK (#870) file will be created and stored in ^XTMP("PSO736RR") to be used as a data backup. This XTMP data backup will be purged after 90 days. Before installing the back-out patch, please refer to the "Deployment, Installation, Back-Out, and Rollback Guide" for installation, post-install instructions, and back-out procedures. This document is exported as PSO_7_0_P736_DIBRG. 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*736 patch have been rolled back, the first two lines of the Routines will no longer contain the designation of patch PSO*7.0*736 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 19 The checksums below are new checksums, and can be checked with CHECK1^XTSUMBLD. Routine Name: PSO736PO Before: n/a After: B9672073 **736** Routine Name: PSOHLDS6 Before: B7189480 After: B7594556 **643,736** Routine Name: PSOORUT1 Before:B144576334 After:B146931226 **1,14,30,46,132,148,233,274, 225,305,289,251,387,385,313, 427,444,454,508,562,441,736** Routine Name: PSORRX1 Before:B184863002 After:B156717075 **454,499,509,519,532,594,643,736** Routine list of preceding patches: 441, 643 ============================================================================= User Information: Entered By : Date Entered : AUG 15, 2023 Completed By: Date Completed: APR 29, 2024 Released By : Date Released : APR 30, 2024 ============================================================================= Packman Mail Message: ===================== $END TXT