$TXT Created by ELLZEY,LINDA at CHEY9.FO-BAYPINES.MED.VA.GOV (KIDS) on Wednesday, 05/13/09 at 08:45 ============================================================================= Run Date: JUL 09, 2009 Designation: PSX*2*65 Package : PSX - CMOP Priority: Mandatory Version : 2 SEQ #59 Status: Released Compliance Date: AUG 09, 2009 ============================================================================= Associated patches: (v)PSX*2*63 <<= must be installed BEFORE `PSX*2*65' (v)PSX*2*66 <<= must be installed BEFORE `PSX*2*65' Subject: ePharmacy Enhancements II Category: - Routine Description: ============ This patch has enhancements which extend the capabilities of the Veterans Health Information Systems and Technology Architecture (VistA) electronic pharmacy (ePharmacy) billing system. Below is a list of all the applications involved in this project along with their patch number: APPLICATION/VERSION PATCH -------------------------------------------------------------- CONSOLIDATED MAIL OUTPATIENT PHARMACY (CMOP) V. 2.0 PSX*2*65 PHARMACY DATA MANAGEMENT (PDM) V. 1.0 PSS*1*131 OUTPATIENT PHARMACY (OP) V. 7.0 PSO*7*289 INTEGRATED BILLING (IB) V. 2.0 IB*2*384 ELECTRONIC CLAIMS MANAGEMENT ENGINE (ECME) V. 1.0 BPS*1*7 The last three patches (PSO*7*289, IB*2*384 and BPS*1*7) will be released in the Kernel Installation and Distribution System (KIDS) multi-build distribution BPS PSO IB BUNDLE 3.0. Patches PSX*2*65 and PSS*1*131 will be released as stand-alone patches. Since there is an implementation dependency between the multi-build distribution and the stand-alone patches, PSX*2*65 and PSS*1*131 must be installed prior to the installation of the multi-build. For more specific instructions please refer to the installation steps provided in each of the patches. This patch modifies the CMOP v2.0 application as described below: 1. When the CMOP transmission starts, all prescriptions in suspense are evaluated to see if they should be submitted to ECME first and if so are submitted. This is done to allow ECME enough time to process third party claim submissions prior to sending the prescriptions to CMOP so that any third party rejections may be properly evaluated. Next the system re-evaluates suspended prescriptions to pull the latest list of fills to be sent to CMOP. Between the time that the ePharmacy submissions are made and the CMOP batch is built, subsequent prescriptions are filled and have not been submitted to ECME. These "in between" prescriptions were not being submitted for 3rd party claims. A code change was made to make ECME submissions for these prescriptions. 2. New functionality was added to prevent prescriptions from being filled/sent to CMOP when a host processing error occurs when a claim is submitted through ECME. The host processing errors are identified by reject codes M6, M8, NN, and 99. The following conditions apply when this scenario occurs. a. The transmission of the Rx/fill will be delayed 1 day in hopes that the host processing issues will be resolved. b. An activity log entry will be defined to state the date/time along with a comment stating that the Rx/fill was left in suspense hold due to a host processing error. c. This added functionality does not include the Pull Early from Suspense function. NOTE: There is a known issue where the system may not automatically resubmit all claims rejected due to a host processing error. A test facility found where the software did not resubmit an electronic pharmacy claim automatically when a claim rejected for a host processing error. The following day the prescription was transmitted to CMOP as anticipated and was filled. The claim did appear on the ECME User Screen so it could be manually resubmitted, which is the process facilities followed before this patch was installed. Based upon analysis, this is an infrequent scenario (less than 1%) and will only occur in a particular set of circumstances. This issue will be fixed in the next ePharmacy patch release. 3. New functionality was added to the Print from Suspense File [PSO PNDLBL] option to prevent ePharmacy prescriptions from being printed from suspense or transmitted to CMOP until 3/4 of the days supply of the Rx/fill has elapsed. These prescriptions will be placed in a Suspense Hold status until the hold date is reached. Prescriptions in a Suspense Hold status can still be manually pulled early from suspense. 4. The 'CMOP/ECME Activity Report' [BPS RPT CMOP/ECME ACTIVITY] has been modified. a. The CMOP-STATUS column will display 'D' for Dispensed or 'T' for Transmitted instead of partially spelling out the status. b. A prompt will be added to select detailed or summary information. Detailed information will reflect what is currently displayed. Summary information will shorten the batch header section of the report. c. A prompt will be added to select a list of patients (or ^ALL). Only patients on the list will be included in the detail. d. The division prompt will be modified to be consistent with other ECME options, i.e., the selection prompt will show 'A ALL DIVISIONS' first, 'S SELECT DIVISIONS' second, and will roll into particular divisions if the user selects an 'S'. e. A prompt will be added to select released, unreleased, or all prescriptions. f. Summary reports will only display information from batches that have ECME Rxs. g. Header information will be centered. Associated New Service Request (NSR): ===================================== N/A Associated Remedy Ticket(s): ============================ N/A Associated E3Rs: ================ N/A Test Sites: =========== Heartland-West HCS Louisville, KY Saginaw, MI Documentation Retrieval: ======================== Sites may retrieve documentation in one of the following ways: 1. The preferred method is to FTP the files from download.vista.med.va.gov, which will transmit the files from the first available FTP server. 2. Sites may also elect to retrieve documentation directly from a specific server as follows: Albany ftp.fo-albany.med.va.gov Hines ftp.fo-hines.med.va.gov Salt Lake City ftp.fo-slc.med.va.gov 3. Documentation can also be retrieved from the VistA Documentation Library (VDL) on the Internet at the following address, http://www.va.gov/vdl. The documentation distribution includes: FILE NAME DESCRIPTION -------------------------------------------------------------------- PSX_2_P65_RN.pdf Release Notes PSX_2_P65_TM_cp.pdf Technical Manual change pages PSX_2_TM_R0709.pdf Technical Manual PSX_2_P65_UM_cp.pdf User Manual change pages PSX_2_UM_R0709.pdf User Manual Installation Instructions: ========================== This patch should be installed prior to ECME/ePharmacy Enhancements multi-build distribution BPS PSO IB BUNDLE 3.0. Install instructions for the multi-build distribution can be found under patch PSO*7*289 install instructions section. This patch can be installed with users on the system. Installation will take less than 2 minutes. There should be no transmissions being processed during the installation. This patch may be queued as long as no CMOP transmissions are processed at and during the time of install. 1. Use the INSTALL/CHECK MESSAGE option on the PackMan menu. 2. From the Kernel Installation & Distribution System menu, select the Installation menu. 3. From this menu, you may select to use the following options (when prompted for INSTALL NAME, enter PSX*2.0*65): a. Backup a Transport Global - this option will create a backup message of any routines exported with the patch. It will NOT backup any other changes such as DDs or templates. b. Compare Transport Global to Current System - this option will allow you to view all changes that will be made when the patch is installed. It compares all components of the patch (routines, DDs, templates, etc.). c. Verify Checksums in Transport Global - this option will ensure the integrity of the routines that are in the transport global. 4. From the Installation menu, select the Install Package(s) option follow the instructions below: a. When prompted for the "Select INSTALL NAME:", enter PSX*2.0*65. b. When prompted "Want KIDS to INHIBIT LOGONs during the install? NO//", respond "NO." c. When prompted "Want to DISABLE Scheduled Options, Menu Options, and Protocols? NO//", respond "NO." d. When prompted, "Device: Home//" respond with the correct device. 5. The patch will begin installation. Please verify that installation completes. Routine Information: ==================== The second line of each of these routines now looks like: ;;2.0;CMOP;**[Patch List]**;11 Apr 97;Build 31 The checksums below are new checksums, and can be checked with CHECK1^XTSUMBLD. Routine Name: PSXBPSR1 Before: n/a After: B14975439 **65** Routine Name: PSXBPSRP Before: B75301229 After: B78524997 **63,65** Routine Name: PSXBPSUT Before: B5692316 After: B5782836 **48,63,65** Routine Name: PSXRPPL Before: B67673391 After: B63013526 **3,23,33,28,40,42,41,48,62, 58,66,65** Routine Name: PSXRPPL1 Before: B48850294 After: B52609779 **3,48,62,66,65** Routine Name: PSXRPPL2 Before: n/a After: B46802908 **65** Routine list of preceding patches: 63, 66 ============================================================================= User Information: Entered By : ELLZEY,LINDA Date Entered : OCT 25, 2007 Completed By: LYNCH,MARY F. Date Completed: JUL 08, 2009 Released By : VECE,VIRGINIA Date Released : JUL 09, 2009 ============================================================================= Packman Mail Message: ===================== $END TXT