$TXT Created by ZEIGLER,EDWARD L at SUPVBB.FO-ALBANY.MED.VA.GOV (KIDS) on Friday, 04/25/08 at 10:09 ============================================================================= Run Date: SEP 17, 2008 Designation: BPS*1*6 Package : BPS - E CLAIMS MGMT ENGINE Priority: Mandatory Version : 1 SEQ #6 Status: Released Compliance Date: OCT 18, 2008 ============================================================================= Associated patches: (v)BPS*1*5 <<= must be installed BEFORE `BPS*1*6' Subject: ePHARMACY TRICARE SUPPORT FRAMEWORK Category: - Routine - Enhancement (Mandatory) - Data Dictionary Description: ============ This patch is one of four patches to enhance the ePharmacy software, to provide the framework to support Tricare and Active Duty outpatient pharmacy billing. The Tricare/Active Duty portions of this software enhancement will not be active until a future patch is released. The release of the additional patch is pending the CBO and contracting with the Tricare Fiscal Intermediary. Below is a list of all the applications involved in this project along with their associated patch number: APPLICATION/VERSION PATCH -------------------------------------------------------------- 1. CONSOLIDATED MAIL OUTPATIENT PHARMACY (CMOP) V. 2.0 PSX*2*66 2. OUTPATIENT PHARMACY (OP) V. 7.0 PSO*7*287 3. ELECTRONIC CLAIMS MANAGEMENT ENGINE (ECME) V. 1.0 BPS*1*6 4. INTEGRATED BILLING (IB) V. 2.0 IB*2*383 All four patches are being released separately with a requirement that they be installed in the order outlined above. It is important that all four patches be installed completely one right after the other. If they are not, you may see errors occur during the Outpatient prescription entry process. There are no other dependencies between these patches, except that Tricare/Active Duty billing will not be supported by ePharmacy until all 4 patches are installed. All sites should install these patches regardless of whether or not they have been activated for ePharmacy by the Central Business Office (CBO) or are providing outpatient pharmacy services to Tricare or Active Duty patients. After the installation of these patches, the activation status of the site will not be impacted. Activation of the ePharmacy product will require instructions provided by the CBO. Sites are not to activate ePHarmacy unless instructed specifically by the CBO. Sites should not start to provide outpatient pharmacy services to Tricare without discussions with the CBO. This patch modifies the ECME v1.0 application as described below. The modifications are labeled dormant in the software will remain inactive until the future Tricare patch is released. 1. ECME Status Message Changes (dormant) An update to the message displayed to the pharmacy staff when an ePharmacy claim is being submitted will display the word 'Tricare' indicating it is Tricare related. Since the Outpatient Pharmacy package will process rejects differently all Tricare claims 'E REJECTED' will also display the reject codes and description as shown below. TRICARE prescription 100665 submitted to ECME for claim generation Claim Status: IN PROGRESS-Waiting to start IN PROGRESS-Building the claim IN PROGRESS-Transmitting E REJECTED 07 - M/I Cardholder ID Number 12 - M/I Patient Location 2. Outpatient Pharmacy notifications An update to the API to Outpatient Pharmacy indicating what eligibility was determined for the prescription will notify the Outpatient Pharmacy package to treat Tricare related claims differently. This patch addresses the following New Service Request (NSR): ------------------------------------------------------------- There is no NSR associated with this patch. This patch addresses the following Remedy Ticket(s): ---------------------------------------------------- There are no Remedy tickets associated with this patch. Components Sent With Patch -------------------------- The following is a list of files included in this patch: UP SEND DATA USER DATE SEC. COMES SITE RSLV OVER FILE # NAME DD CODE W/FILE DATA PTS RIDE -------------------------------------------------------------------------- 9002313.32 BPS PAYER RESPONSE OVERRIDES YES YES NO 9002313.59 BPS TRANSACTION YES YES NO NO Partial DD: subDD: 9002313.59 fld: 901.04 DATA SCREEN: Test Sites: ----------- HEARTLAND WEST HCS LOUISVILLE, KY SAGINAW, MI ================== INSTALLATION INSTRUCTIONS ================== If installed during the normal workday, it is recommended that the following selection(s) in the OPTION (#19) file, and all of their descendants be disabled to prevent possible conflicts while running the KIDS Install. Other VISTA users will not be affected. - None Install time - less than 2 minutes. 1. LOAD TRANSPORT GLOBAL --------------------- Choose the PackMan message containing this patch and invoke the INSTALL/CHECK MESSAGE PackMan option. 2. START UP KIDS ------------- Start up the Kernel Installation and Distribution System Menu [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 3. Select Installation Option: --------------------------- NOTE: The following are OPTIONAL - (When prompted for the INSTALL NAME, enter BPS*1.0*6): 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 DD's 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, DD's, 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. 4. Select Installation Option: Install Package(s) ------------------ **This is the step to start the installation of this KIDS patch: a. Choose the Install Package(s) option to start the patch install. b. When prompted "Want KIDS to INHIBIT LOGONs during the install? NO//" answer NO c. When prompted 'Want to DISABLE Scheduled Options, Menu Options, and Protocols? YES//' answer NO. ================ POST INSTALLATION INSTRUCTIONS ================ Post install routine BPS10P6 can be deleted from system upon successful completion of install. Routine Information: ==================== The second line of each of these routines now looks like: ;;1.0;E CLAIMS MGMT ENGINE;**[Patch List]**;JUN 2004;Build 10 The checksums below are new checksums, and can be checked with CHECK1^XTSUMBLD. Routine Name: BPS10P6 Before: n/a After: B1462824 **6** Routine Name: BPSECMP2 Before: B64422717 After: B65371165 **1,5,6** Routine Name: BPSECMPS Before: B69163590 After: B69380294 **1,2,5,6** Routine Name: BPSNCPD1 Before: B40334169 After: B70088175 **1,3,5,6** Routine Name: BPSNCPD2 Before: B37248829 After: B37690318 **1,5,6** Routine Name: BPSNCPD3 Before: B20450751 After: B16349234 **1,5,6** Routine Name: BPSNCPD4 Before: n/a After: B4013558 **6** Routine Name: BPSNCPDP Before: B73597678 After: B71265922 **1,3,4,2,5,6** Routine Name: BPSOSIY Before: B52867161 After: B54076368 **1,3,5,6** Routine Name: BPSSCRRV Before: B14899182 After: B16310738 **1,5,6** Routine Name: BPSTEST Before: n/a After: B48227959 **6** Routine Name: BPSUTIL Before: B11392543 After: B11432819 **1,3,2,5,6** Routine list of preceding patches: 5 ============================================================================= User Information: Entered By : ZEIGLER,EDWARD L Date Entered : SEP 28, 2007 Completed By: ELLZEY,LINDA Date Completed: SEP 17, 2008 Released By : BOTTINI,STEVE Date Released : SEP 17, 2008 ============================================================================= Packman Mail Message: ===================== $END TXT