============================================================================= Run Date: APR 09, 2020 Designation: BPS*1*26 Package : BPS - E CLAIMS MGMT ENGINE Priority: Mandatory Version : 1 SEQ #24 Status: Released Compliance Date: MAY 09, 2020 ============================================================================= Associated patches: (v)BPS*1*24 <<= must be installed BEFORE `BPS*1*26' Subject: MCCF EDI TAS EPHARMACY BUILD 13 Category: - Enhancement (Mandatory) - Routine - Data Dictionary Description: ============ This patch has enhancements that extend the capabilities of the Veterans Health Information Systems and Technology Architecture (VistA) electronic pharmacy (ePharmacy) billing system. This release was developed as part of the Medical Care Collection Fund (MCCF) Electronic Data Interchange (EDI) Transaction Application Suite (TAS) project. Below is a list of all the applications involved in this project along with their patch numbers: APPLICATION/VERSION PATCH --------------------------------------------------------------- ELECTRONIC CLAIMS MANAGEMENT ENGINE (ECME) V. 1.0 BPS*1*26 OUTPATIENT PHARMACY (OP) V. 7.0 PSO*7*544 INTEGRATED BILLING (IB) V. 2.0 IB*2*636 CMOP V. 2.0 PSX*2*87 All four of these patches are being released via Kernel Installation and Distribution System (KIDS) multi-build distribution. KIDS multi-build name: BPS PSO IB PSX BUNDLE 13.0 KIDS Host File name: BPS_1_26_PSO_IB_PSX.KID This patch contains the following functionality: --------------------------------------------------------- 1. With this enhancement, the system will automatically close certain rejects on the pharmacy worklist that were back-billed and/or resubmitted. 2. The system will automatically enter a comment for a claim that cannot be resubmitted due to an existing bill in Claims Tracking. 3. When a user attempts to resubmit a claim that has been identified as non-billable in Claims Tracking (CT), the system will now display a message indicating that the claim cannot be resubmitted until the non-billable reason has been removed in CT. 4. When a claim request is sent to a payer, if the value calculated to populate the field Ingredient Cost is $0.00, the system will now send a value of $0.01. 5. The system will be updated to support new and modified Reject Codes as prescribed by the National Council for Prescription Drug Programs (NCPDP) Implementation Guide versions published through July 2019. Patch Components: ----------------- Files & Fields Associated: File Name (#) New/Modified/ Sub-File Name (#) Field Name (Number) Deleted ------------------- --------------------------------- ------------- BPS PAYER RESPONSE OVERRRIDES (#9002313.32) REASON FOR SERVICE CODE (2.11) New BPS NCPDP REJECT CODES (#9002313.93) Modified Forms Associated: New/Modified/ Form Name File Name (Number) Deleted --------- ------------------ ------------- N/A Mail Groups Associated: New/Modified/ Mail Group Name Deleted --------------- ------------ N/A Options Associated: New/Modified/ Option Name Type Deleted ----------- ---- ------------- N/A Protocols Associated: New/Modified/ Protocol Name Deleted ------------- ------------ N/A Security Keys Associated: New/Modified/ Security Key Name Deleted ----------------- ------------ N/A Templates Associated: New/Modified/ Template Name File Name (Number) Deleted ------------- ------------------ ------------- N/A Additional Information: N/A New Service Requests (NSRs) --------------------------- N/A Patient Safety Issues (PSIs) ---------------------------- N/A Defect Tracking System Ticket(s) & Overview ------------------------------------------- N/A Test Sites: ----------- BIRMINGHAM VAMC (521) VA HEARTLAND-WEST, VISN 15 (589) LEXINGTON VAMC-LEESTOWN (596) Software and Documentation Retrieval Instructions: ---------------------------------------------------- Software being released as a host file and/or documentation describing the new functionality introduced by this patch are available. Retrieval of files from download.vista.domain.ext is the preferred method. This transmits the files from the first available server. Sites may retrieve the software and/or documentation directly using Secure File Transfer Protocol (SFTP) from DOWNLOAD.VISTA.DOMAIN.EXT Documentation can also be found on the VA Software Documentation Library at: https://www.domain.ext/vdl/ The documentation includes: Title File Name Transfer Mode ----------------------------------------------------------------------- ECME User Manual BPS_1_0_P26_UM.PDF Binary ECME Deploy Install Rollback Guide (BPS*1*26) BPS_1_0_P26_IG.PDF Binary Patch Installation: Pre/Post Installation Overview: ------------------------------- N/A Pre-Installation Instructions: ------------------------------ **************************** IMPORTANT NOTE **************************** * * * * * This multi-build should not be installed while the ePharmacy * * Logical Links are running, and it should not be installed when * * CMOP processing is taking place. * * * * Logical Links * * ============= * * The ePharmacy Logical Links must be stopped before patch * * installation. This can be done with the option "Start/Stop Links" * * [HL START]. The ePharmacy Logical Links which need to be stopped * * are the following: * * * * BPS NCPDP * * EPHARM OUT * * * * To avoid disruptions, these patches should be installed during * * non-peak hours when there is minimal activity on the system. * * Avoid times when ECME claims are being transmitted. Of particular * * concern are the options below. * * * * 1. BPS NIGHTLY BACKGROUND JOB [BPS NIGHTLY BACKGROUND JOB] * * Do not install the patch when ECME claims are being generated * * by the BPS Nightly Background Job option. Wait for this job * * to finish or Complete the installation before this job starts. * * * * 2. Scheduled CS Transmission [PSXR SCHEDULED CS TRANS] and * * Scheduled Non-CS Transmission [PSXR SCHEDULED NON-CS TRANS * * Do not install the patch when prescriptions are being * * transmitted to CMOP. Wait for the CMOP transmissions to * * finish or complete the installation before the transmissions * * start. Both the CS (Controlled Substances) and the non-CS * * CMOP transmission options should be checked. Check with * * Pharmacy Service or your Pharmacy ADPAC to find out when CMOP * * transmissions occur. * * * * CMOP Processing * * =============== * * To avoid disruptions, this multi-build should not be installed * * when prescriptions are being transmitted to CMOP. There are two * * scheduled jobs which should be checked: Scheduled CS Transmission * * [PSXR SCHEDULED CS TRANS] and Scheduled Non-CS Transmission [PSXR * * SCHEDULED NON-CS TRANS]. Wait for the CMOP transmissions to finish * * or complete the installation before the transmissions start. Both * * the CS (Controlled Substances) and the non-CS CMOP transmission * * options should be checked. Check with Pharmacy Service or your * * Pharmacy ADPAC to find out when CMOP transmissions occur. * * * ************************************************************************ This multi-build installation may take up to 2 minutes to install. This multi-build installation can be queued but should not be queued at a time when the BPS NIGHTY BACKGROUND JOB or CMOP transmission processes are scheduled. Installation Instructions: -------------------------- 1. OBTAIN PATCHES -------------- Obtain the host file BPS_1_26_PSO_IB_PSX.KID, which contains the following patches: BPS*1.0*26 PSO*7.0*544 IB*2.0*636 PSX*2.0*87 Sites may retrieve VistA software from download.vista.domain.ext. This transmits the file from the first available server. Sites may also elect to retrieve this file directly from a specific server. Sites may retrieve the software directly using Secure File Transfer (SFTP) from the ANONYMOUS.SOFTWARE directory at the following Field Offices: Hines: domain.ext Salt Lake City: domain.ext File Name Transfer Mode -------------------------------------------------- BPS_1_26_PSO_IB_PSX.KID ASCII 2. START UP KIDS ------------- Start up the Kernel Installation and Distribution System Menu option [XPD MAIN]: Edits and Distribution ... Utilities ... Installation ... Select Kernel Installation & Distribution System Option: Installation --- Load a Distribution Print Transport Global Compare Transport Global to Current System Verify Checksums in Transport Global Install Package(s) Restart Install of Package(s) Unload a Distribution Backup a Transport Global Select Installation Option: 3. LOAD TRANSPORT GLOBAL FOR MULTI-BUILD ------------------------------------- From the Installation menu, select the Load a Distribution option. When prompted for "Enter a Host File:", enter the full directory path where the host file BPS_1_26_PSO_IB_PSX.KID was saved (e.g., SYS$SYSDEVICE:[ANONYMOUS]BPS_1_26_PSO_IB_PSX.KID). When prompted for "OK to continue with Load? NO//", enter "YES." The following will display: Loading Distribution... BPS PSO IB PSX BUNDLE 13.0 BPS*1.0*26 PSO*7.0*544 IB*2.0*636 PSX*2.0*87 Use INSTALL NAME: BPS PSO IB PSX BUNDLE 13.0 to install this Distribution. 4. RUN INSTALLATION OPTIONS FOR MULTI-BUILD ------------------------------------------------- From the Installation menu, select to use the following options (when prompted for the INSTALL NAME, enter BPS PSO IB PSX BUNDLE 13.0): 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 data dictionaries 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, data dictionaries, 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. 5. INSTALL MULTI-BUILD ------------------- This is the step to start the installation of this KIDS patch. This will need to be run for the BPS PSO IB PSX BUNDLE 13.0. a. Choose the Install Package(s) option to start the patch install. b. When prompted for the "Select INSTALL NAME:", enter BPS PSO IB PSX BUNDLE 13.0. c. When prompted "Want KIDS to INHIBIT LOGONs during the install? NO//", press Enter to accept the default. d. When prompted "Want to DISABLE Scheduled Options, Menu Options, and Protocols? NO//", press Enter to accept the default. e. When prompted "Device: HOME//", respond with the correct device. Post-Installation Instructions: ------------------------------- ************************** IMPORTANT NOTE ****************************** * * * Please re-start the ePharmacy Logical Links using the "Start/Stop * * Links" [HL START] menu option. The ePharmacy Logical Links are * * the following: * * * * BPS NCPDP * * EPHARM OUT * * * * Using ^%RDELETE, please delete the pre-install for BPS*1.0*26 and * * the post-install for PSO*7.0*544, listed below: * * * * BPS26PRE * * PSO544POST * * * ************************************************************************ Back-Out Plan: -------------- For a description of how to back-out this patch, please refer to the PSO Deploy Install Rollback Guide listed above (BPS_1_0_P26_IG.PDF). **NOTE** please disregard the "second line of each of these routines now looks like:" below the Routine Information. **NOTE** The second line of each of these routines now looks like: ;;1.0;E CLAIMS MGMT ENGINE;**[Patch List]**;JUN 2004;Build 24 Routine Information: ==================== The second line of each of these routines now looks like: ;;1.0;E CLAIMS MGMT ENGINE;**[Patch List]**;;Build 24 The checksums below are new checksums, and can be checked with CHECK1^XTSUMBLD. Routine Name: BPS26PRE Before: n/a After: B5930569 **26** Routine Name: BPSNCPD4 Before: B43404653 After: B48988720 **6,7,8,10,11,24,26** Routine Name: BPSOSIY Before: B74487088 After: B74487088 **1,3,5,6,7,8,10,11,20,26** Routine Name: BPSSCRRS Before: B80029514 After: B83065109 **1,3,5,7,8,10,11,20,26** Routine Name: BPSTEST Before:B101618182 After:B102604269 **6,7,8,10,11,15,19,20,22,23,24,26** Routine Name: BPSTEST1 Before: B196424 After: B196424 **6,7,8,10,11,15,19,20,22,26** Routine Name: BPSTEST2 Before: B99644333 After:B102272726 **24,26** Routine list of preceding patches: 24 ============================================================================= User Information: Entered By : Date Entered : OCT 25, 2018 Completed By: Date Completed: APR 09, 2020 Released By : Date Released : APR 09, 2020 ============================================================================= Packman Mail Message: ===================== No routines included