============================================================================= Run Date: OCT 23, 2007 Designation: PSO*7*260 Package : PSO - OUTPATIENT PHARMACY Priority: Mandatory Version : 7 SEQ #240 Status: Released Compliance Date: NOV 23, 2007 ============================================================================= Associated patches: (v)PSO*7*200 <<= must be installed BEFORE `PSO*7*260' (v)PSO*7*233 <<= must be installed BEFORE `PSO*7*260' (v)PSO*7*258 <<= must be installed BEFORE `PSO*7*260' (v)PSO*7*268 <<= must be installed BEFORE `PSO*7*260' (v)PSS*1*127 <<= must be installed BEFORE `PSO*7*260' Subject: ePHARMACY/ECME ENHANCEMENTS Category: - Routine - Data Dictionary - Enhancement (Mandatory) - Other Description: ============ ****************************** ATTENTION ******************************* An issue was introduced with patch PSO*7*260 that removed the display of Dosage, Verb, Dispense Unit, Noun, Route, and Schedule from the VIEW PRESCRIPTION [PSO VIEW] option. This functionality is restored in PSO*7*264 Q4 Pharmacy Enhancements patch. It is suggested that the Q4 Pharmacy Enhancements patch PSO*7*264 be installed immediately after the ePharmacy/ECME Enhancements bundle of patches in order to restore full functionality of the option. ************************************************************************ This patch has enhancements which extend the capabilities of the Veterans Health Information Systems and Technology Architecture (VistA) electronic pharmacy (ePharmacy) system. Below is a list of all the applications involved in this project along with their patch number: APPLICATION/VERSION PATCH -------------------------------------------------------------- OUTPATIENT PHARMACY (OP) V. 7.0 PSO*7*260 INTEGRATED BILLING (IB) V. 2.0 IB*2*363 ELECTRONIC CLAIMS MANAGEMENT ENGINE (ECME) V. 1.0 BPS*1*5 PHARMACY DATA MANAGEMENT (PDM) V. 1.0 PSS*1*127 CONSOLIDATED MAIL OUTPATIENT PHARMACY (CMOP) V. 2.0 PSX*2*63 The first three patches (BPS*1*5, IB*2*363, and PSO*7*260) will be released in the Kernel Installation and Distribution System (KIDS) multi-build distribution BPS PSO IB BUNDLE 2.0. Patches PSX*2*63 and PSS*1*127 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*63 and PSS*1*127 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. All sites should install these patches regardless of whether or not they have been activated for ePharmacy by the Central Business Office (CBO). After the installation of these patches, the activation status of the site will not be impacted. As before, activation of the ePharmacy product will require instructions provided by the CBO. Sites are not to activate unless instructed specifically by the CBO. This patch modifies the Outpatient Pharmacy V. 7.0 application as described below: ****************************** N O T E ********************************** PSO*7*260 contains routines that may overwrite Class III modifications for some Outpatient Automation. Class III changes must be reinstated after installing PSO*7*260. 1. LAST LOCAL NDC Update Currently, the LAST LOCAL NDC (#1) field in the NDC BY OUTPATIENT SITE (#50.037) sub-file in the DRUG (#50) file is updated only during the release process, manual or automatic (OPAI). The update only occurs if these two conditions are satisfied: 1) the NDC picked at release (or received through OPAI) is different than the original NDC sent to the payer during Rx Finish or Suspense Label Print; 2) the new submission for the released NDC returns a PAYABLE claim. Although the functionality and logic above will be preserved, the LAST LOCAL NDC information will also be updated during the initial claim submission for the specific prescription fill. The initial submission for local filled prescriptions (non-CMOP) occurs either during the prescription finish/refill request or during the Local Label Print process (Print from Suspense File [PSO PNDLBL] option). The only condition for updating the LAST LOCAL NDC in this situation will be the return of a PAYABLE claim. 2. Ignored Rejects Report [PSO IGNORED REJECTS REPORT] A new report is included on the ePharmacy menu option [PSO EPHARMACY MENU] and it is called Ignored Rejects Report [PSO IGNORED REJECTS REPORT]. It lists prescription fills for a given division and date range that were ignored after the 3rd Party Payer rejected the claim. The user may sort by patient, drug, and/or user who marked the fills as ignored. During sort selection, the user may select specific patients, drugs and/or users. 3. Prescription Activity Log 3.1 NDC and DAW CODE edits When the user edits the NDC or DAW CODE fields within a prescription, the editing event is not being logged on the main prescription activity log section as it is for other fields in the prescription. Edits to these two fields will now be logged as indicated in the example below: Activity Log: # Date Reason Rx Ref Initiator Of Activity ==================================================================== 1 09/01/06 EDIT ORIGINAL OPUSER,ONE Comments: NDC changed from 99999-9999-99 to 55555-4444-22 2 09/01/06 EDIT ORIGINAL OPUSER,TWO Comments: DAW CODE changed from 0 to 5 3.2 ECME reversed/NOT re-submitted A new entry in the activity log will indicate that ECME performed a reversal but not a resubmission because for some reason the prescription fill is no longer billable (e.g. Patient is no longer insured) as seen below: Activity Log: # Date Reason Rx Ref Initiator Of Activity ==================================================================== 1 09/01/06 EDIT ORIGINAL OPUSER,ONE Comments: ECME reversed/NOT re-submitted: NOT INSURED. 4. View Prescription [PSO VIEW] 4.1 Display NDC For ePharmacy released prescriptions only, the system will now display the NDC used to dispense the medication for the original prescription and for each refill. The example below shows the NDC used for the original: ... Rx #: 71599999$e Orderable Item: HYDROCODONE/ACETAMINOPHEN TAB CMOP Drug: HYDROCODONE 5/ACETAMINOPHEN 500MG TAB NDC: 55555-4444-22 Verb: TAKE *Dosage: 1 TABLET ... 4.2 Display ECME# The ECME# will be displayed at the right side of the Rx# between parenthesis as shown below: ... Rx #: 71599999$e (ECME#: 1234567) Orderable Item: HYDROCODONE/ACETAMINOPHEN TAB CMOP Drug: HYDROCODONE 5/ACETAMINOPHEN 500MG TAB NDC: 55555-4444-22 Verb: TAKE *Dosage: 1 TABLET ... 4.3 Lookup by ECME# The user will be able to identify the prescription by the ECME# by using the following syntax: VIEW PRESCRIPTION: ? You may enter E.NNNNNNN, where NNNNNN is the prescription ECME# (e.g., E.0289332) or, Answer with PRESCRIPTION RX # Do you want the entire PRESCRIPTION List? N VIEW PRESCRIPTION: E.1234567 5. Third Party Payer Rejects - View/Process [PSO REJECTS VIEW/PROCESS] Date range prompts will be added to this REJECT VIEW/PROCESS menu option to allow the users to see the rejects for a specific period of time. This enhancement is expected to reduce the response time for loading the rejects into the reject list depending on the date range selected. The date range selected will be displayed on the header of the reject list. 6. Third Party Payer Rejects - Worklist [PSO REJECTS WORKLIST] 6.1 Group by Insurance A new option GI (Group by Insurance) is being added to allow users to group the rejects in the Reject Worklist by their insurance companies. If the list is grouped by Insurance, the GI option has the opposite effect, it removes the grouping. This option is also available for the Third Party Payer Rejects - View/Process [PSO REJECTS VIEW/PROCESS] option. 6.2 Add Comments (hidden action) A new hidden action called 'COM Add Comments' is being added to the Reject Worklist to provide users a method to update the status during the processing of rejections. This action is also available for the Third Party Payer Rejects - View/Process [PSO REJECTS VIEW/PROCESS] option. 6.3 Enable OVR (Submit Override Codes) for RTS rejects Currently, the hidden action OVR Override DUR Reject can only be selected for DUR (#88) rejects on the worklist. After this patch is installed, this action will be renamed to Submit Override Codes and the users will also be able to invoke it for Refill Too Soon (#79) rejects on the worklist. 6.4 Submit Clarif. Code (hidden action) A new hidden action called 'CLA Submit Clarif. Code' is being added to the Reject Worklist to allow users to enter appropriate Submission Clarification Code with claims resubmission for rejects. Once a Clarification Code is sent along with the claim, the reject is marked resolved. The second screen shows the changes to the Resolution Information. Furthermore, an entry is logged under the prescription ECME Log, as shown below: ECME Log: # Date/Time Rx Ref Initiator Of Activity ====================================================================== ... 7 2/6/07@17:22:07 ORIGINAL OPUSER,ONE Comments: Submitted to ECME: REJECT WORKLIST(CLARIF. CODE=2) ... 6.5 Prior Authorization Submission (hidden action) A new hidden action called 'PA Submit Prior Auth.' is being added to the Reject Worklist to allow users to send Prior Authorization information with claims resubmission for rejects. Once the Prior Authorization is sent along with the claim, the reject is marked resolved. Furthermore, an entry is logged under the prescription ECME Log, as shown below: ECME Log: # Date/Time Rx Ref Initiator Of Activity ====================================================================== ... 7 2/6/07@17:22:07 ORIGINAL OPUSER,ONE Comments: Submitted to ECME:REJECT WORKLIST(PRIOR AUTH.=1/12345678901) ... 7. ePharmacy Medication Profile (View Only) [PSO PMP] This new menu option will provide users with a 'View Only' version of the current Medication Profile screen seen in the Patient Prescription Processing [PSO LM BACKDOOR ORDERS]. This option will not allow any actions such as Refill, Renewal, Hold, etc., therefore the term 'View Only'. Another main difference is that it will display duplicate drugs for the patient. The main purpose of this option is to provide the Outpatient Pharmacy user with a tool to research 3rd party payer rejects due to Refill Too Soon or Drug Utilization Review (DUR) reasons. Important: Several settings that determine the display of the data in this new option can be configured by Pharmacy Division and also by user. If no configuration is created for a specific Pharmacy Division or user, the system utilizes the 'factory default' which is a pre-configured set of preferences. For more information on how to creating Pharmacy Division or user specific settings read the section below about the new ePharmacy Medication Profile Division Preferences [PSO PMP SITE PREFERENCES] 7.1 Reject Worklist/View Process (new action) The new option above will be accessible in the existing Third Party Payer Rejects - Worklist [PSO REJECTS WORKLIST] and Third Party Payer Rejects - View/Process [PSO REJECTS VIEW/PROCESS] options through the new action MP (Medication Profile). 8. ePharmacy Medication Profile Division Preferences [PSO PMP SITE PREFERENCES] The sole purpose of this option is to support the ePharmacy Medication Profile (View Only) [PSO PMP] option mentioned above by providing the users a way to determine how the data should be displayed. Below is a list of settings that can be configured specifically for each Pharmacy Division: EXP/CANCEL CUTOFF - Indicates the maximum number of days for an expired and/or discontinued prescription to be cut from the ePharmacy Medication Profile. SORT BY - Indicates which field the list should be sorted by. The user can choose from following: Rx#, DRUG NAME, ISSUE DATE or LAST FILL DATE. SORT ORDER - Indicates the sorting order in which the field selected above should be sorted: ASCENDING or DESCENDING. DISPLAY SIG - Indicates whether the SIG should be displayed under each medication order on the list. GROUP BY STATUS - Indicates whether the list of medication orders should be broken up by status (ACTIVE, HOLD, etc.). DISPLAY ORDER COUNT - Indicates whether the number of medication orders under each group should be displayed in front of the group name (e.g., PENDING ORDERS (4 orders)). 9. NCPDP vs. NPI With the transition from NCPDP to NPI number the Reject Information screen in the Third Party Payer Rejects - Worklist [PSO REJECTS WORKLIST] and Third Party Payer Rejects - View/Process [PSO REJECTS VIEW/PROCESS] options will be slightly modified to display the correct information for each reject. The label 'NCPDP#' below will be made dynamic. Depending on which information was used for the prescription (NCPDP or NPI), the label will display either 'NCPDP#:' or 'NPI#:' accordingly. Reject Information(RESOLVED) Sep 14, 2006@19:22 Page: 1 of 1 Division : CHEYENNE VAM&ROC NCPDP#: 4454812 Patient : OPPATIENT,ONE(666-01-0101) Sex: M DOB: JAN 1,1951(55) Rx# : 787480/0 ECME#: 1458404 Fill Date: Jun 28, 2006 CMOP Drug: NICOTINE 10MG/ML SOLN NDC Code: 00009-5194-01 10. NPI INSTITUTION (#101) field in the OUTPATIENT SITE (#59) file Due to some confusion generated after the release of patch PSO*7*254, which introduced the field above, the description for this field is being changed to the following: The value in the field should point to the entry in the INSTITUTION file (#4) that contains the NPI number for the dispensing pharmacy for this Outpatient Pharmacy division. 11. New fields: CLARIFICATION CODE (#24), PRIOR AUTHORIZATION TYPE (#25) and PRIOR AUTHORIZATION NUMBER (#26) The fields above are being added to the REJECT INFO sub-file (#52.25) in the PRESCRIPTION file (#52) to support the changes introduced by this patch for the submission of the Clarification Code and Prior Authorization information to the third party payer. 12. New sub-file: COMMENTS (#52.8551) The sub-file above is being added under the REJECT INFO sub-file (#52.25) in the PRESCRIPTION file (#52) to support the changes introduced by this patch to allow Outpatient Pharmacy users to enter comments on third party payer rejects that they are working on. Below is a list of the fields in this sub-file: 51 COMMENTS (multiple) .01 DATE/TIME 1 USER 2 COMMENTS 13. New file: EPHARMACY MEDICATION PROFILE PREFERENCES (#52.85) The file above is being created to store the division and user preferences for the new ePharmacy Medication Profile [PSO PMP] option introduced by this patch. Below is a list of the fields in this file: .01 DIVISION 1 EXP/CANCEL CUTOFF 2 SORT BY 3 SORT ORDER 4 DISPLAY SIG 5 GROUP BY STATUS 6 DISPLAY ORDER COUNT 51 USER (multiple) .01 USER 1 EXP/CANCEL CUTOFF 2 SORT BY 3 SORT ORDER 4 DISPLAY SIG 5 GROUP BY STATUS 6 DISPLAY ORDER COUNT Associated New Service Request (NSR): ===================================== N/A Associated Remedy Ticket(s): ============================ HD0000000181096 Associated E3Rs: ================ N/A Test Sites: =========== CENTRAL ARKANSAS HEARTLAND WEST, KS 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 -------------------------------------------------------------------- BPS_1_5_EPHARMACY_RN_0907.PDF ePharmacy/ECME Enhancements Release Notes BPS_1_TM_R0907.PDF ECME V. 1.0 Technical Manual/ Security Guide BPS_1_UM_R0907.PDF ECME V. 1.0 User Manual IB_2_P363_RN.PDF IB V. 2.0 Patch IB*2.0*363 Release Notes PSS_1_UM_R0907.PDF PDM V. 1.0 User Manual PSS_1_TM_R0907.PDF PDM V. 1.0 Technical Manual/ Security Guide PSS_1_P127_UM_CP.PDF PDM V. 1.0 User Manual Change Pages PSS_1_P127_TM_CP.PDF PDM V. 1.0 Technical Manual/ Security Guide Change Pages PSS_1_P127_DRUG_ EXCEPTIONS_LIST.PDF PDM Drug Exception List PSX_2_TM_R0907.PDF CMOP V. 2.0 Technical Manual PSX_2_P63_TM_CP.PDF CMOP V. 2.0 Technical Manual Change Pages Please note: There are Outpatient Pharmacy user and technical manual documentation changes related to this patch. They will be included in the documentation issued with PSO*7*264 (the 4th Quarter Release). Installation Instructions: ========================== Post Installation Overview ------------------------------ Patches BPS*1*5, IB*2*363, and PSO*7*260 have post-installs that will run. Please see the post-installation instructions for the details of each of these post-installs. ================INSTALLATION INSTRUCTIONS ================= BEFORE PROCEEDING, please read item number 8e and make sure you have the information needed in order to complete this installation. To avoid disruptions, these patches should be installed when users are not on the system and during non-peak hours. Of particular concern would be the items below. 1. Do not install the patch when ECME claims are being generated by the BPS Nightly Background Job option [BPS NIGHTLY BACKGROUND JOB]. Wait for this job to finish or complete the installation before this job starts. 2. Do not install the patch when prescriptions are being transmitted to CMOP. Wait for the CMOP transmission to finish or complete the installation before the transmission starts. Check with Pharmacy Service or your pharmacy Automated Data Processing Application Coordinator (ADPAC) to find out when CMOP transmissions occur. 3. In addition, note that you will be prompted to disable the following options during the installation: ECME Billing Events Report option [IB ECME BILLING EVENTS] Patient Insurance Info View/Edit option [IBCN PATIENT INSURANCE] Third Party Joint Inquiry option [IBJ THIRD PARTY JOINT INQUIRY] Install Time - Approximately 15 minutes ************** PRE-INSTALLATION INSTRUCTIONS ************** Since the EPHARM IN HL logical link will be deleted by the BPS*1.0*5 patch, please stop this logical link prior to installing the multi-build distribution BPS PSO IB BUNDLE 2.0. This can be done via the Start/Stop Links [HL START] option. *********************************************************** 1. OBTAIN PATCHES -------------- Patches PSX*2*63 and PSS*1*127 will be sent to your system upon release from the National Patch Module. Obtain the host file BPS_1_5_PSO_IB.KID, which contains the following three patch installs: BPS*1.0*5 PSO*7.0*260 IB*2.0*363 Sites can retrieve VistA software from the following FTP addresses. The preferred method is to FTP the files from: download.vista.med.va.gov This will transmit the files from the first available FTP server. Sites may also elect to retrieve software 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 The BPS_1_5_PSO_IB.KID host file is located in the anonymous.software directory. Use ASCII Mode when downloading the file. 2. LOAD TRANSPORT GLOBAL FOR STAND-ALONE PATCHES --------------------------------------------- For patches PSX*2*63 and PSS*1*127, choose the PackMan message containing each of these patches and invoke the INSTALL/CHECK MESSAGE PackMan option. 3. 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: 4. RUN OPTIONAL INSTALLATION OPTIONS FOR STAND-ALONE PATCHES --------------------------------------------------------- From the Installation menu, you may select to use the following options (when prompted for the INSTALL NAME, enter each of the stand-alone patches (PSX*2.0*63 and PSS*1.0*127)): 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 Database Definitions (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. 5. INSTALL STAND-ALONE PATCHES --------------------------- This is the step to start the installation of this KIDS patch. This will need to be run for each of the stand-alone patches (PSX*2*63 and PSS*1*127). a. Choose the Install Package(s) option to start the patch install. b. When prompted for the "Select INSTALL NAME:", enter the patch name. c. When prompted "Want KIDS to INHIBIT LOGONs during the install? YES//" answer NO. d. When prompted "Want to DISABLE Scheduled Options, Menu Options, and Protocols? YES//" answer NO. e. When prompted, "Device: Home//" respond with the correct device. 6. LOAD TRANSPORT GLOBAL FOR MULTI-BUILD ------------------------------------- After the installation of the stand-alone patches is complete, return to the Installation menu. From the Installation menu, select the Load a Distribution option. When prompted for "Enter a Host File:", enter the full directory path where you saved the host file BPS_1_5_PSO_IB.KID (e.g., SYS$SYSDEVICE:[ANONYMOUS]BPS_1_5_PSO_IB.KID). When prompted for "OK to continue with Load? NO//", enter "YES." The following will display: Loading Distribution... BPS PSO IB BUNDLE 2.0 BPS*1.0*5 PSO*7.0*260 IB*2.0*363 Use INSTALL NAME: BPS PSO IB BUNDLE 2.0 to install this Distribution. 7. RUN OPTIONAL INSTALLATION OPTIONS FOR MULTI-BUILD ------------------------------------------------- From the Installation menu, you may select to use the following options (when prompted for the INSTALL NAME, enter BPS PSO IB BUNDLE 2.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 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. 8. 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 BUNDLE 2.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 BUNDLE 2.0. c. For the BPS*1*5 patch, when prompted "Want KIDS to Rebuild Menu Trees Upon Completion of Install? YES//" enter YES unless your system does this in a nightly TaskMan process. d. For the PSO*7*260 patch, when prompted "Want KIDS to Rebuild Menu Trees Upon Completion of Install? YES//" enter YES unless your system does this in a nightly TaskMan process. e. For the IB*2*363 patch, when prompted "Enter the Coordinator for Mail Group 'IBCNR EPHARM':", enter the appropriate person. To determine this, please contact your Medical Care Cost Recovery (MCCR) business department prior to installation to determine who will be the coordinator for this new mail group. This mail group will be used by the IB package when forwarding bulletins related to ePharmacy processing. f. When prompted "Want KIDS to INHIBIT LOGONs during the install? YES//" enter NO. g. When prompted "Want to DISABLE Scheduled Options, Menu Options, and Protocols? YES//" enter YES. h. When prompted "Enter options you wish to mark as 'Out Of Order':" enter the following options: ECME Billing Events Report option [IB ECME BILLING EVENTS] Patient Insurance Info View/Edit option [IBCN PATIENT INSURANCE] Third Party Joint Inquiry option [IBJ THIRD PARTY JOINT INQUIRY] i. When prompted "Enter protocols you wish to mark as 'Out Of Order':" enter . j. When prompted "Delay Install (Minutes): (0-60): 0//" enter an appropriate number of minutes to delay the installation in order to give users enough time to exit the disabled options before the installation starts. k. When prompted "Device: Home//" respond with the correct device. ************** POST-INSTALLATION INSTRUCTIONS ************** There is a bug in the KIDs installation process for multi-builds. Even though you may have requested that the menu rebuild occur for patches BPS*1*5 and PSO*7*260 while answering the installation questions, it is possible that the menu rebuild did not occur. If the rebuild did not occur and your system does not do an automatic menu rebuild in a nightly TaskMan process, you should do a manual rebuild via the Build Primary Menu Trees option [XQBUILDTREE] found in the Menu Rebuild Menu [XQBUILDMAIN] option. The BPS post-install routine delivered with BPS*1*5 will do the tasks listed below. This post-install will be tasked and may take several hours to run. When it is complete, it will send an email to the installer and the users in the BPS OPECC mail group. The post-install routines BPS01P5* are being left on the system after the install. They will be deleted with a future patch. 1. Delete the files listed in the 'The following is a list of files deleted in this patch:' section of the BPS*1*5 patch. 2. Delete the fields listed in the 'The following is a list of fields deleted in this patch:' section of the BPS*1*5 patch. 3. Delete obsolete records from the BPS NCPDP FIELD DEFS (#9002313.91) file. These records are for National Council for Prescription Drug Programs (NCPDP) version 3x, which make these records obsolete. 4. Populate the new BPS STATISTICS file (#9002313.58) categories (Accepted Reversals, Rejected Reversals, and Dropped to Paper). 5. Populate the new SUBMIT DATE/TIME (#6) field of the BPS TRANSACTIONS file (#9002313.59). 6. Convert the ECME log data from global ^BPSECP("LOG") to the new BPS LOG file (#9002313.12). 7. Convert the submit processing queue from global ^BPSECP("BPSOSRX") to the temporary global ^XTMP("BPS-PROC"). The IB post-install routine delivered with IB*2*363 will populate the E-PHARMACY DIVISION field (#.09) of the IB NCPDP EVENT LOG file (#366.14). This is a new field delivered with this patch. The time required to accomplish this task may vary from site to site and is dependent upon how many electronic pharmacy claims are processed daily at the site. The post install routine IB20P363 is being left on the system after the install. It will be deleted with a future patch. The PSO post-install routine delivered with PSO*7*260 will set the REJECT INFO sub-file (#52.25) in the PRESCRIPTION file (#52) as READ ONLY. This will prevent users from entering rejects through FileMan, which causes problems to the Outpatient Pharmacy application. The post install routine PSO260PI is being left on the system after the install. It will be deleted with a future patch. ************************************************************ Routine Summary: =============== The second line now reads as follows: ;;7.0;OUTPATIENT PHARMACY;**[patch list]**;DEC 1997 CHECK^XTSUMBLD results: Routine Before Patch After Patch Patch List -------- ------------ ----------- ------------------------------- PSO260PI NEW 15839 260 PSOBPSR1 NEW 11292166 260 PSOBPSRP NEW 4304588 260 PSOBPSU1 9463097 11058261 148,260 PSOBPSU2 NEW 2461199 260 PSOBPSUT 8457300 8458702 148,247,260 PSODAWUT 737634 1021627 148,260 PSON52 24038314 24337465 1,16,23,27,32,46,71,111,124, 117,131,139,157,143,219,148, 239,201,268,260 PSONVAVW NEW 7743917 260 PSOORAL2 15285725 15546231 258,260 PSOORED2 25064703 25615171 2,51,46,78,102,114,117,133, 159,148,247,260 PSOORED6 22473655 22866555 78,104,117,133,143,219,148, 247,268,260 PSOOREDT 28221803 28428502 4,20,27,37,57,46,78,102,104, 119,143,148,260 PSOORFI1 32991576 33015417 7,15,23,27,32,44,51,46,71, 90,108,131,152,186,210,222, 258,260 PSOPMP0 NEW 16790190 260 PSOPMP1 NEW 7139990 260 PSOPMPPF NEW 12217254 260 PSOR52 11646969 12162819 10,22,27,181,148,201,260 PSOREJP0 9772950 12675350 148,260 PSOREJP1 12677183 14105061 148,247,260 PSOREJP2 12844088 14326074 148,247,260 PSOREJP3 NEW 3204080 260 PSOREJU1 12590765 12745085 148,247,260 PSOREJU2 8911764 10538737 148,260 PSOREJUT 8010182 8982314 148,247,260 PSORXL1 23744907 23819738 36,46,148,260 PSORXVW 31226487 31298640 14,35,46,96,103,88,117,131, 146,156,185,210,148,233,260 PSORXVW1 33116253 33546554 35,47,46,71,99,117,156,193, 210,148,258,260 PSOSULBL 22651215 23168926 139,173,174,148,200,260 Number of routines modified: 20 Number of new routines: 9 Routine Information: ==================== The second line of each of these routines now looks like: ;;7.0;OUTPATIENT PHARMACY;**[Patch List]**;DEC 1997;Build 82 The checksums below are new checksums, and can be checked with CHECK1^XTSUMBLD. Routine Name: PSO260PI Before: n/a After: B23082 **260** Routine Name: PSOBPSR1 Before: n/a After: B37279361 **260** Routine Name: PSOBPSRP Before: n/a After: B12525106 **260** Routine Name: PSOBPSU1 Before: B40165335 After: B46417153 **148,260** Routine Name: PSOBPSU2 Before: n/a After: B7051944 **260** Routine Name: PSOBPSUT Before: B49521138 After: B49534340 **148,247,260** Routine Name: PSODAWUT Before: B1596507 After: B2108992 **148,260** Routine Name: PSON52 Before: B60158603 After: B62362504 **1,16,23,27,32,46,71,111,124, 117,131,139,157,143,219,148, 239,201,268,260** Routine Name: PSONVAVW Before: n/a After: B19285655 **260** Routine Name: PSOORAL2 Before: B19471221 After: B19960223 **258,260** Routine Name: PSOORED2 Before: B63154079 After: B64502991 **2,51,46,78,102,114,117,133, 159,148,247,260** Routine Name: PSOORED6 Before: B61440766 After: B62756399 **78,104,117,133,143,219,148, 247,268,260** Routine Name: PSOOREDT Before: B64105311 After: B64908254 **4,20,27,37,57,46,78,102,104, 119,143,148,260** Routine Name: PSOORFI1 Before: B72196979 After: B72652086 **7,15,23,27,32,44,51,46,71, 90,108,131,152,186,210,222,258, 260** Routine Name: PSOPMP0 Before: n/a After: B76827234 **260** Routine Name: PSOPMP1 Before: n/a After: B26858864 **260** Routine Name: PSOPMPPF Before: n/a After: B55558822 **260** Routine Name: PSOR52 Before: B31117928 After: B33265182 **10,22,27,181,148,201,260** Routine Name: PSOREJP0 Before: B37884354 After: B65585833 **148,260** Routine Name: PSOREJP1 Before: B63661734 After: B80456147 **148,247,260** Routine Name: PSOREJP2 Before: B51774949 After: B62487288 **148,247,260** Routine Name: PSOREJP3 Before: n/a After: B10158946 **260** Routine Name: PSOREJU1 Before: B55340266 After: B58727208 **148,247,260** Routine Name: PSOREJU2 Before: B36306554 After: B47862203 **148,260** Routine Name: PSOREJUT Before: B27390673 After: B34569551 **148,247,260** Routine Name: PSORXL1 Before: B42190830 After: B42620106 **36,46,148,260** Routine Name: PSORXVW Before: B61807519 After: B66871354 **14,35,46,96,103,88,117,131, 146,156,185,210,148,233,260** Routine Name: PSORXVW1 Before: B63759557 After: B67149111 **35,47,46,71,99,117,156,193, 210,148,258,260** Routine Name: PSOSULBL Before: B61486377 After: B64818200 **139,173,174,148,200,260** Routine list of preceding patches: 200, 233, 258, 268 ============================================================================= User Information: Entered By : ROCHA,MARCELO Date Entered : OCT 12, 2006 Completed By: LEONARD,KEN Date Completed: OCT 15, 2007 Released By : VECE,VIRGINIA Date Released : OCT 23, 2007 ============================================================================= Packman Mail Message: ===================== No routines included