$TXT Created by at CLN2G2.AAC.DOMAIN.EXT (KIDS) on Tuesday, 01/14/20 at 10:10 ============================================================================= Run Date: MAR 10, 2020 Designation: PSO*7*591 Package : PSO - OUTPATIENT PHARMACY Priority: Mandatory Version : 7 SEQ #480 Status: Released Compliance Date: APR 09, 2020 ============================================================================= Associated patches: (v)PSO*7*567 <<= must be installed BEFORE `PSO*7*591' Subject: NON-ACTIONABLE RRP RECORDS REMAIN ON ERX WORK QUEUE + TYPO Category: - Routine Description: ============ This patch will address the following ePrescribing (eRx) issues: 1. INC7957997 - Grammar error in eRx processing screen 2. INC6442610 - inbound eRx issue - order stuck in queue DUPLICATE - INC6659074 - Wrong eRx status code generated in VistA inbound eRx software version 3.0 DUPLICATE - INC6245922 - eRX issue with acknowledging messages in RRD status that change to RRP status for 1 patient Note: RRD stated in the ticket is not correct. It is actually RXD (REFILL RESPONSE DENIED/DNTF). Defect Tracking System Ticket(s) & Overview: -------------------------------------------- 1. INC7957997 - Grammar error in eRx processing screen Problem: -------- Alaska VA Healthcare System reported a grammar issue while accepting an eRx prescription into VistA via the Complete Orders from eRx [PSO ERX FINISH] option. After validating a patient via this option the software checks whether the same patient has other eRx prescriptions waiting to be validated and if any additional are found it will issue the following message/prompt (example): This patient has other prescriptions for: Dec 04, 2019 Patient: XXXXXX,XXXXXXX DRUG PROVIDER REC DATE -------------------------------------------------------------------------- 1.) GABAPENTIN 300 MG ORAL CAPSUPROVIDER,TEST JAN 04, 2020 2.) METOPROLOL SUCCINATE ER 100 PROVIDER,TEST JAN 04, 2020 Would you like apply the above validation to these prescriptions? Enter Yes or No: N// The issue is with "...like apply..." which should read "...like to apply..." Resolution: ----------- Inserted "to" between "like" and "apply". Technical Resolution: --------------------- Changed the routine PSOERX1B at line tag BPROC+41 to include "to" between "like" and "apply". 2. INC6442610 - inbound eRx issue - order stuck in queue DUPLICATE - INC6659074 - Wrong eRx status code generated in VistA inbound eRx software version 3.0 DUPLICATE - INC6245922 - eRX issue with acknowledging messages in RRD status that change to RRP status for 1 patient Note: RRD stated in the ticket is not correct. It is actually RXD (REFILL RESPONSE DENIED/DNTF). Problem: -------- VA Puget Sound Health Care System reported that Refill Response eRx records with a status of RRP (REFILL REQUEST PROCESSED) are accumulating on their eRx Work Queue and the users do not have a mechanism to remove them. This problem interferes with their work because these types of records fill up pages of their Work Queue and there is no further processing needed to be performed on them. Upon extensive research it was determined that RXA (REFILL RESPONSE ACKNOWLEDGED) Refill Request records were erroneously being updated to RRP once a new prescription was accepted via eRx for the same medication that was previously denied. To illustrate a little further the sequence of events happened the following way: 1) Patient had eRx 'A' that had already been previously filled and did not have any more refills left. 2) The VA Pharmacist uses the RR (eRx Refill Request) through the Patient Prescription Processing [PSO LM BACKDOOR ORDERS] option and a message is sent out to the Dr's Office. 3) The Dr's Office denies the Refill/Renewal by sending a new eRx record to VistA which creates a 'Refill Response' record with a status of RXD (REFILL RESPONSE DENIED/DNTF). 4) The VA Pharmacist then acknowledges the RXD record through the Complete Orders from eRx [PSO ERX FINISH] option, which changes the status of the 'Refill Response' from RXD to RXA, successfully removing it from the eRx Work Queue. 5) Later, the Dr's Office sends to VistA a new prescription for the patient with the same medication. 6) The VA Pharmacist processes the new eRx prescription and accepts it. This action creates the problem because it mistakenly changes the status of the previously updated 'Refill Response' record from RXA to RRP, bringing it back to the eRx Work Queue which does not offer any means for the users to remove such records from the Work Queue. Resolution: ----------- This patch will stop the status update from RXA to RRP described in step #6 above. Furthermore, it will remove all RRP records from the eRx Work Queue. The RRP records will still be visible if users intentionally are looking for them through the SR (Search Queue) action, which is how the Work Queue was designed to work originally. Technical Resolution: --------------------- 1) Changed the routine PSOERX at line tag BLDITEM+22 to include "RRP" in the list of status screened out for "Refill Response" type records, which will drop the erroneous RRP records from the Work Queue as soon as the patch is installed. 2) Changed the routine PSOERX1B at line tag ADD+64 and the routine PSOERXU3 at line tag AUTODC+38 to only update the record status to RRP if the record type is a "Refill Request". This will prevent "Refill Response" records from being wrongly updated to RRP. Test Sites: ----------- Fayetteville VAMC Sioux Falls HCS Documentation Retrieval Instructions: ------------------------------------- Files can be obtained from the ANONYMOUS.SOFTWARE directory at one of the OI Field Offices. The preferred method is to retrieve the file using Secure File Transfer Protocol (SFTP) from DOWNLOAD.VISTA.DOMAIN.EXT, which will transmit the file from the first available server. Alternatively, sites may elect to retrieve the file from a specific OI Field Office. OI FIELD OFFICE FTP ADDRESS DIRECTORY Hines DOMAIN.EXT Salt Lake City DOMAIN.EXT The documentation will be in the form of Adobe Acrobat files. Documentation can also be found on the VA Software Documentation Library at: http://www.domain.ext/vdl/ Title File Name FTP Mode ---------------------------------------------------------------------- User Manual - pso_7_0_iep_um.pdf Binary Inbound ePrescribing 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. Staff should not be processing prescriptions while patch is being installed. This patch should take less than 5 minutes to install. 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, select 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. When prompted for INSTALL NAME, enter the patch #, PSO*7.0*591. 4. From the Kernel Installation & Distribution System menu, select the Installation menu. From this menu, you may select to use the following options: when prompted for INSTALL NAME, enter the patch #, PSO*7.0*591: a. 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, DDs, templates, etc. b. Verify Checksums in Transport Global - This option will allow you to ensure the integrity of the routines that are in the transport global. 5. From the Installation menu, select the Install Package(s) option and choose the patch to install. 6. When prompted 'Want KIDS to INHIBIT LOGONs during the install? NO//', respond NO. 7. When prompted 'Want to DISABLE Scheduled Options, Menu Options, and Protocols? NO//', respond NO. 8. If prompted 'Delay Install (Minutes): (0-60): 0//' respond 0. Back-out/Rollback Strategy: --------------------------- Back-out will be done only with the concurrence and participation of development team and appropriate VA site/region personnel. The decision to back-out or rollback software will be a joint decision between development team, VA site/region personnel and other appropriate VA personnel. Prior to installing an 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 (this is done at time of install). 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 routines onto the VistA System. The back-out plan is to restore the routines from the backup created. No data was modified by this patch installation and, therefore, no rollback strategy is required. Validation of Roll Back Procedure --------------------------------- The Roll Back Procedure can be verified by printing the first 2 lines of the PSO Routines contained in this patch using the option First Line Routine Print [XU FIRST LINE PRINT]. Once the routines contained in the PSO*7.0*591 patch have been rolled back, the first two lines of the Routines will no longer contain the designation of patch PSO*7.0*591 in the patch list section on line 2. Routine Information: ==================== The second line of each of these routines now looks like: ;;7.0;OUTPATIENT PHARMACY;**[Patch List]**;DEC 1997;Build 2 The checksums below are new checksums, and can be checked with CHECK1^XTSUMBLD. Routine Name: PSOERX Before:B134582097 After:B134630031 **467,527,508,551,567,591** Routine Name: PSOERX1B Before:B203269485 After:B204199349 **467,506,520,527,508,551,591** Routine Name: PSOERXU3 Before:B170900975 After:B171565124 **508,591** Routine list of preceding patches: 567 ============================================================================= User Information: Entered By : Date Entered : DEC 19, 2019 Completed By: Date Completed: MAR 09, 2020 Released By : Date Released : MAR 10, 2020 ============================================================================= Packman Mail Message: ===================== $END TXT