$TXT Created by SCOTT at IVMVEE.DOMAIN.EXT (KIDS) on Friday, 07/09/21 at 15:25 ============================================================================= Run Date: AUG 12, 2021 Designation: IB*2*676 Package : IB - INTEGRATED BILLING Priority: EMERGENCY Version : 2 SEQ #642 Status: Released Compliance Date: AUG 13, 2021 ============================================================================= Associated patches: (v)IB*2*563 <<= must be installed BEFORE `IB*2*676' (v)IB*2*637 <<= must be installed BEFORE `IB*2*676' (v)IB*2*645 <<= must be installed BEFORE `IB*2*676' Subject: Pharmacy Copay EHRM Web Services Category: - Routine - Other Description: ============ *************************************************************** NOTICE!!!!! 24 HOUR COMPLIANCE PERIOD *************************************************************** The Pharmacy Copay Synchronization Between OEHRM and VistA project seeks to interface the Cerner Millennium (EHRM) solution with VistA Integrated Billing(IB) package. This is necessary to prevent overpayment by veterans responsible for Medication Copayment. Both EHRM and VistA will keep Veterans pharmacy copay data synchronized via the Veterans Data Integration and Federation-Enterprise Platform (VDIF-EP). This VISTA interface solution will implement an HL7 connection (IBARXVDF) for query and receive to the VistA IB package in order to send transactional data to the VDIF-EP and EHRM solution. The following features will be implemented with this IB patch: 1. Query non-VISTA (Cerner) sites for RX Copay data when running the Query Medication Copay Billing Events [IBARXM COPAY QUERY] menu option. The first received query on a patient will result in a message that contains all previous RX Copay transactions. This is called Seeding. 2. Pushing Rx Copay transactions to non-VISTA (Cerner) sites for RX Copay data when modifying RX Copay charges using the Cancel/Edit/Add Patient Charges [IB CANCEL/EDIT/ADD CHARGES] menu option. This transmission will contain a fix to a previous charge using the Treating Facility List Application Program Interface (TFL API). 3. Pushing Rx Copay transactions to non-VISTA (CERNER) sites for RX Copay data when releasing RX to Patient and creating a new Billable event in Integrated Billing. 4. Query VISTA sites from Cerner for RX Copay Data when updating Medication Copay Patient data in Millennium. The first received query on a patient will result in a message that contains all previous RX Copay transactions. This is called Seeding. 5. Pushing Rx Copay transactions to VISTA sites for RX Copay Data when canceling RX Copay charges in Millennium. 6. Pushing Rx Copay transactions to VISTA sites for RX Copay Data when releasing RX to Patient and Creating a Billable event in Millennium 7. Push RX Copay transactions to VDIF for remote non-VISTA (Cerner) sites when running the IBARX Nightly Background Job so that Cerner has the most updated RX Copay Cap amounts. 8. Back billing is implemented so that any charges that have already been applied to existing transactions that have been canceled or updated will be corrected and synced between systems. Backbilling only functions from VistA to Cerner. VistA to VistA back billing is already in place. 9. The following incidents are addressed by this patch (INC12315265, INC12551348, INC11428719). A Push Rx Co-pays error message that occurs because there is no HL7 connection to Cerner. This patch creates the VistA side component that resolves the error. Patch Components: ----------------- Files & Fields Associated: File Name (Number) Field Name (Number) New/Modified/Deleted ------------------ ------------------- -------------------- N/A Forms Associated: Form Name File # 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 Functions Associated: Function Name 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 Additional Information: ----------------------- The patch installs the following entries in the HLO APPLICATION REGISTRY file (#779.2): IBARXC-QRY IBARXC-QRYRESP IBARXC-RECV IBARXC-SEND New Service Requests (NSRs): ---------------------------- Pharmacy Copay Synchronization between OEHRM and VistA (SR-002241) Patient Safety Issues (PSIs): ----------------------------- N/A Defect Tracking System Ticket(s) & Overview: -------------------------------------------- 1. INC12315265,INC12551348,INC11428719 All these incidents are the same issue i.e. 200 PUSH RX COPAY CAP ERROR Problem: ------- The RxCopay system sends RxCopay transactions to all members of a patients Treating Facility List. If Cerner is a member of the Treating Facility List then the RxCopay system will attempt to send transactions to Cerner. Resolution: ---------- Patch IB*2.0*676 creates a connection between the RxCopay system and Cerner. Test Sites: ---------- Mann-Grandstaff VA Medical Center (Spokane, WA) Software and Documentation Retrieval Instructions: ---------------------------------------------------- The software for this patch is being released in a PackMan message. This release is also available at: /srv/vista/patches/SOFTWARE Documentation describing the new functionality is included in this release. Documentation Title File Name -------------------------------------------------------------------- IB*2*676 Deployment, Installation, Back-Out, IB_2_0_P676_DIBR.PDF and Rollback Guide IB*2*676 Integrated Billing Version 2 IB_2_0_P676_TM.PDF Technical Manual IB*2*676 Integrated Billing Version 2 IB_2_0_P676_UM.PDF User Manual The documentation can be found in the VA Software Documentation Library at: "domain.ext/vdl/" Documentation can also be obtained at download.vista.domain.ext/index.html/SOFTWARE, and /srv/vista/patches/SOFTWARE in binary format. Patch Installation: Pre/Post Installation Overview: ------------------------------- N/A 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. There are no pre-install instructions for HL7. Installation Instructions: -------------------------- 1. Choose the PackMan message containing this patch. 2. Choose the INSTALL/CHECK MESSAGE PackMan option. 3. From the Kernel Installation & 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 IB*2.0*676. 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 IB*2.0*676 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: Routines 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. 4. From the Installation Menu, select the Install Package(s) option and choose the patch to install. 5. If prompted Want KIDS to Rebuild Menu Trees Upon Completion of Install? NO// answer NO 6. If prompted Want KIDS to INHIBIT LOGONs during the install? NO// answer NO 7. If prompted 'Want to DISABLE Scheduled Options, Menu Options, and Protocols? YES// answer No 8. If prompted Delay Install (Minutes): (0 60): 0// respond 0. Post-Installation Instructions ------------------------------ In order for the new Logical links to function properly the appropriate DNS and Port number will need to be manually entered for each site. The link should also be set to AUTOSTART in order to ensure the link is restarted when the system restarts. Use FILEMAN to edit the HL LOGICAL LINK file: Edit the following fields: DNS DOMAIN AUTOSTART TCP/IP PORT (OPTIMIZED) Select HL LOGICAL LINK NODE: IBARXCVDF NODE: IBARXCVDF// DNS DOMAIN: Replace AUTOSTART: Enabled TCP/IP PORT (OPTIMIZED): ***WARNING*** It is essential that when entering DNS or Port information you do NOT include trailing spaces. Cut and pasting of information can include a trailing or preceeding space. This will cause the Logical Link to fail when connecting. You will need to input the DNS domain and Port number for the site being installed from the following list: "Station ID" Facility Name DNS domain Port REDACTED VERIFY Connectivity Post Configuration --------------------------------------- Once you have configured the IBARXCVDF Logical Link you will need to test it to ensure connectivity to VDIF. *Note: Be aware this will only function in production. As test systems are not connected to VDIF unless specifically configured to do so. In VistA use the HL7 Main Menu, Filer and Link Management Options, Ping, HLO options. Follow the directions below to ensure the Logical Link connects to VDIF. HL MAIN MENU HL7 Main Menu Event monitoring menu ... Systems Link Monitor Filer and Link Management Options ... Message Management Options ... Interface Developer Options ... Site Parameter Edit Select HL7 Main Menu Option: FILer and Link Management Options SM Systems Link Monitor FL Monitor, Start, Stop Filers LM TCP Link Manager Start/Stop SA Stop All Messaging Background Processes RA Restart/Start All Links and Filers DF Default Filers Startup SL Start/Stop Links PI Ping (TCP Only) ED Link Edit ER Link Errors ... Select Filer and Link Management Options Option: PI Ping (TCP Only) What HL Logical Link do you want to test? Select a TCP link:IBARXCVDF 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 #XXXX <<< This should be the Configured Port # 2 HL7 1.6 --> Port #XXXX Enter response: 1// HLO --> Port #XXXX Trying to connect... Connected! Sending PING ... PING sent! Reading acknowledgment.... Acknowledgment received! <<<< Successful Connection *Note: If you do not get a successful connection please recheck your values in the Logical Link. If you verify your values and still do not get a successful connection in Production, please log a help desk ticket. Back-Out Plan: -------------- Prior to installing the 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. 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 routnes onto the VistA system. The decision to back out the patch will be a joint decision between VA Site/Region personnel and other appropriate VA personnel. For more information pertaining to the Backout procedure, please refer to the the DIBORG document. (i.e. IB*2*676 Deployment, Installation, Back-Out, and Rollback Guide) Routine Information: ==================== The second line of each of these routines now looks like: ;;2.0;INTEGRATED BILLING;**[Patch List]**;21-MAR-94;Build 34 The checksums below are new checksums, and can be checked with CHECK1^XTSUMBLD. Routine Name: IBARX Before: B56596853 After: B56490639 **101,150,156,168,186,237,308, 563,604,645,676** Routine Name: IBARXCBK Before: n/a After: B7219623 **676** Routine Name: IBARXCFL Before: n/a After: B7284187 **676** Routine Name: IBARXCHL Before: n/a After: B9030593 **676** Routine Name: IBARXCQR Before: n/a After: B7131942 **676** Routine Name: IBARXCR2 Before: n/a After: B3408179 **676** Routine Name: IBARXCRC Before: n/a After: B9869860 **676** Routine Name: IBARXCRD Before: n/a After: B11532495 **676** Routine Name: IBARXCSH Before: n/a After: B19225986 **676** Routine Name: IBARXMA Before: B27254647 After: B29428888 **150,158,676** Routine Name: IBARXMB Before: B22706384 After: B24262454 **156,563,676** Routine Name: IBARXMC Before: B44624308 After: B48554758 **156,186,237,552,563,676** Routine Name: IBARXMN Before: B34322540 After: B36697970 **150,158,156,186,308,563,676** Routine Name: IBARXMP Before: B8996586 After: B9005942 **150,158,637,676** Routine Name: IBARXMQ Before: B16386930 After: B18060511 **150,156,186,199,563,676** Routine Name: IBARXMU Before: B14583290 After: B17535981 **150,158,156,178,186,676** Routine list of preceding patches: 637, 645 ============================================================================= User Information: Entered By : E Date Entered : JUN 03, 2020 Completed By: Date Completed: AUG 12, 2021 Released By : Date Released : AUG 12, 2021 ============================================================================= Packman Mail Message: ===================== $END TXT