$TXT Created by at NHM0026D.FO-BAYPINES.DOMAIN.EXT (KIDS) on Friday, 07/11/25 at 19:36 ============================================================================= Run Date: JUL 23, 2025 Designation: PSO*7*770 Package : PSO - OUTPATIENT PHARMACY Priority: Mandatory Version : 7 SEQ #654 Status: Released Compliance Date: AUG 23, 2025 ============================================================================= Associated patches: (v)PSO*7*662 <<= must be installed BEFORE `PSO*7*770' (v)PSO*7*501 <<= must be installed BEFORE `PSO*7*770' (v)PSO*7*545 <<= must be installed BEFORE `PSO*7*770' (v)PSO*7*710 <<= must be installed BEFORE `PSO*7*770' (v)PSO*7*753 <<= must be installed BEFORE `PSO*7*770' (v)PSO*7*765 <<= must be installed BEFORE `PSO*7*770' (v)PSO*7*768 <<= must be installed BEFORE `PSO*7*770' (v)PSO*7*769 <<= must be installed BEFORE `PSO*7*770' (v)PSO*7*783 <<= must be installed BEFORE `PSO*7*770' Subject: MBM CLASS 3 TO CLASS 1 CONVERSION - PHASE 3 Category: - Routine - Data Dictionary Description: ============ The Inbound Electronic Prescribing (eRx) Phase 3 Enhancements delivered in this patch is a continuation effort to convert all of the MbM Class 3 modifications into Class 1. Below is a summary of the changes being delivered in this patch. For a more comprehensive description of the changes please refer to the documents listed in the Documentation section of this description. EHRM Impact Statement: ---------------------- This patch can be installed at all sites, including EHRM converted sites. Patch Components ================ Files & Fields Associated: File Name (#) Field Name (#) New/Modified/Deleted ----------------- ---------------- -------------------- ERX HOLDING QUEUE (#52.49) SUGGESTED VISTA RX (#.15) New MATCHED DRUG/SUPPLY (#3.2) Modified VISTA ROUTING (#20.4) Modified ERX SERVICE REASON CODES file (#52.45) Modified CH REQ REASON TEXT BY DIVISION sub-file (#52.4521) New OUTPATIENT DIVISION (#.01) New CHANGE REQUEST REASON TEXT (#1) New CHANGE REQUEST REASON TEXT (#.01) New Forms Associated: Form Name File Number New/Modified/Deleted --------- ----------- -------------------- N/A Mail Groups Associated: Mail Group Name New/Modified/Deleted --------------- -------------------- N/A Options Associated: Option Name Type New/Modified/Deleted ----------- ---- -------------------- PSO DEA/DOJ NIGHTLY DATA UPD New PSO ERX BATCH CH REQ/DRUG SWAP New PSO RPH Modified PSO SUPERVISOR Modified Protocols Associated: Protocol Name Type New/Modified/Deleted ------------- ----- -------------------- PSO ERX ACCEPT ERX Action Modified PSO ERX ACCEPT VALIDATION Action Modified PSO ERX ACKNOWLEDGE Action Modified PSO ERX ADD COMMENT Action Modified PSO ERX ALL PATIENTS CR DEFAULT TEXT EDIT Action New PSO ERX ALL PATIENTS QUEUE HIDDEN ACTIONS Menu Modified MENU MERGE MENU ITEMS PSO ERX ALL RXS INCLUDE ALL STATUSES Action New PSO ERX ALL RXS QUEUE HIDDEN ACTIONS MENU Menu Modified PSO ERX ALL RXS REMOVE FILTERS Action Modified PSO ERX BATCH CHANGE REQUEST MENU Menu New PSO ERX BATCH CHANGE REQUEST SELECT Action New PSO ERX BATCH CHANGE REQUEST SUBMISSION Action New PSO ERX BATCH INCLUDE ALL STATUSES Action New PSO ERX BATCH VISTA DRUG REPLACEMENT Action New PSO ERX CHANGE REQUEST Action Modified PSO ERX DISPLAY MENU Menu Modified PSO ERX DRUG EDIT FROM SINGLE ERX VIEW Action New PSO ERX DRUG VALIDATION HIDDEN MENU Menu Modified PSO ERX EDIT Action Modified PSO ERX ENTER PROGRESS NOTES Action Modified PSO ERX HIDDEN ACTIONS Action Modified PSO ERX HOLD Action Modified PSO ERX JUMP TO ERX Action Modified PSO ERX JUMP TO ERX PATIENT Action Modified PSO ERX JUMP TO OP Action Modified PSO ERX PATIENT ALLERGIES VIEW Action Modified PSO ERX PRINT Action Modified PSO ERX REJECT Action Delete PSO ERX REMOVE Action Modified PSO ERX RESEND CHANGE REQUEST Action Modified PSO ERX SINGLE PATIENT NEXT DRUG Action Modified PSO ERX SINGLE PATIENT QUEUE HIDDEN Menu Modified ACTIONS MENU PSO ERX STATUS HISTORY Action Modified PSO ERX UN-ACCEPT Action Modified PSO ERX UN-PROCESS Action Modified PSO ERX UN-REMOVE Action Modified PSO ERX UNHOLD Action Modified PSO ERX VALIDATE DRUG Action Modified PSO ERX VALIDATE PATIENT Action Modified PSO ERX VALIDATE PROVIDER Action Modified PSO ERX VALIDATION MENU Menu Modified PSO ERX VIEW AUDIT LOG Action Modified PSO ERX VIEW DRUG SUGGESTIONS Action New PSO ERX VIEW HISTORY LOG Action Modified PSO ERX VIEW ORIGINAL ERX Action Modified PSO ERX VIEW REQUEST ERX Action Modified PSO ERX VIEW RESPONSE ERX Action Modified PSO ERX VIEW SUGGESTED RX Action Modified PSO HIDDEN ACTIONS #2 Menu Modified PSO LM BACKDOOR PRTCL USRSCR VERIFY Action Modified PSO LM EXIT2 Action Modified PSO LMOE MOVE TO NEXT PATIENT Action Modified Security Keys Associated: Security Key Name New/Modified/Deleted ----------------- -------------------- PSO ERX WORKLOAD RPH New PSO ERX WORKLOAD TECH Modified Templates Associated: Template Name Type File Name (#) New/Modified/Deleted ------------- ---- ------------ -------------------- PSO ERX ALL RXS QUEUE List 52.49 Modified PSO ERX BATCH ERX CHANGE List 52 New PSO ERX SINGLE ERX DISPLAY List 52.49 Modified PSO ERX SINGLE PATIENT QUEUE List 52.49 Modified PSO LM ACTIVE ORDERS List 52 Modified Remote Procedures Associated: Remote Procedure Name New/Modified/Deleted --------------------- -------------------- N/A Parameter Definitions Associated: Parameter Name New/Modified/Deleted -------------- -------------------- N/A Additional Information: ----------------------- New Service Requests (NSRs): N/A Patient Safety Issues (PSIs): ----------------------------- N/A Defect Tracking System Ticket(s) & Overview: ============================================ For more detailed information on each item listed below, please refer to the Release Notes document included in the documentation for this patch. 1. [HDSO-8753] Patient address and primary phone displayed on the Single eRx View screen --------------------------------------------------------------------------- To easily confirm the patient's identity, the patient's address and phone number are included on both the eRx and VistA sides of the Single eRx View/Display landing page. 2. [HDSO-9169] Patient Pharmacy Narrative displayed on the Single eRx View screen --------------------------------------------------------------------------- If the VistA patient is matched and it contains text in the Pharmacy Narrative field, it will be displayed in the eRx Single View/Display Screen across the screen at the bottom of the Patient section and just above the Provider section. 3. [HDSO-8751] eRx and VistA Patient SSN display --------------------------------------------------------------------------- To quickly verify the patient's identity, the full SSN is displayed on the eRx and VistA sections of the Single eRx View/Display landing page, aligned with the DOB. 4. [HDSO-9168] Provider phone displayed on the Single eRx View screen --------------------------------------------------------------------------- To quickly verify the Provider, the provider's phone number is included and shown on both the eRx and VistA portions of the Single eRx View/Display landing page alongside the NPI. 5. [HDSO-8749] Missing Patient Instruction alert --------------------------------------------------------------------------- After accepting the suggested Rx on the eRx Drug Validation Edit action screen, the user will be prompted whether they want to copy the patient instructions from the suggested Rx into the eRx. 6. [HDSO-8754] RxChangeRequest 'Script Clarification' reason message templates --------------------------------------------------------------------------- The CHANGE REQUEST CODE for 'Script Clarification' has been updated to allow the pharmacist/technician to choose a reason code linked to a pre-made question template in the field. The user will be prompted to choose a CHANGE REQUEST SUB-CODE from the options provided. 7. [HDSO-9156] Option to Edit RxChangeRequest Reason Template Text --------------------------------------------------------------------------- In the eRx Patient Centric Queue screen, a new hidden action called 'CRT CR Default Text Edit' has been added to enable users who hold the PSDMGR security key to modify the default RxChangeRequest Reason template. Please, refer to the user documentation for more information about this new option. 8. [HDSO-8752] Full drug name display when user selects the DET hidden action --------------------------------------------------------------------------- For the eRx Single Patient Queue and the eRx Medication Queue when the user selects the DET (Show/Hide Details) action it will display the complete eRx Drug name. 9. [HDSO-8750] VistA Drug Search --------------------------------------------------------------------------- A new search option called 'VISTA DRUG' has been added in the SQ Search Queue action, enabling users to search for eRx's by VistA Drug already matched/linked to the eRx drug. 10. [HDSO-8755] RxRenewalResponse Message Types under SQ --------------------------------------------------------------------------- The search query option MESSAGE TYPE has been modified. Upon entering certain message types (RE and CX) as listed below, the user will be prompted to enter the corresponding RESPONSE TYPE as indicated. In this prompt, users have the option to choose ALL to view all response types for the message type selected or select a specific response type as shown below. For additional details on this new change, please refer to the user manual documentation. 11. [HDSO-8856] Search by Remove Reason codes --------------------------------------------------------------------------- The search query option MESSAGE TYPE has been modified. Upon entering certain eRx Status (RM and RJ) as listed below, the user will be prompted to enter the corresponding REMOVAL or REJECT REASON CODE as indicated. In this prompt, users have the option to choose ALL to view all REMOVAL or REJECT REASON CODE or select a specific response type. For additional details on this new change, please refer to the user manual documentation. 12. [HDSO-9157] Provider Auto-Validation for CS Drugs --------------------------------------------------------------------------- The Provider Auto-Validation functionality released with patch PSO*7*700 (see item #5) will now be extended to digitally signed (indicating Controlled Substance) eRx's as well. The only additional check performed for auto-validating is that the VA provider must have a valid DEA# on file that matches the DEA# sent with the eRx. 13. [HDSO-9155] Ability to Un-Process VistA Rx with a DELETED status --------------------------------------------------------------------------- Sometimes an eRx prescriptions that have already been transmitted to CMOP must be un-processed so it can go back to the eRx Holding Queue. Therefore, an exception was implemented in the software to allow non-CS eRx prescriptions with a DELETED status to be un-processed even after they have been transmitted to CMOP. 14. [HDSO-9158] Allow Un-Accept and Re-Accept of Approved eRx Renewals --------------------------------------------------------------------------- When a Renewal request is Approved by the outside prescriber the eRx will got straight to the Pending Order without stopping at the eRx Holding Queue first. The software will now allow the user to Un-Accept such records and send them back to the eRx Holding Queue so an issue (e.g., Eligibility verification, etc.) can be worked on there. Once the issue has been resolved the user will be able to re-accept the record without having to perform any matches or validations. 15. [HDSO-9159] Park Functionality in the eRx Holding Queue --------------------------------------------------------------------------- The Park functionality released by the patch PSO*7*441, released back in September of 2022 has now been implemented in the eRx Holding Queue. If the site has the Park functionality turned ON the user will be able to select PARK as an option for the PICKUP ROUTING besides MAIL or WINDOW. 16. [HDSO-9160] No auto-match if Provider is inactive --------------------------------------------------------------------------- A check was added to prevent an inactive VistA provider from being auto- matched to the eRx even if the NPI matches. Furthermore, if the inactive VistA Provider is a suggestion it will be automatically forgotten. 17. [HDSO-9161] Patient, Provider and Drug/SIG auto-matching based on suggestions --------------------------------------------------------------------------- The auto-matching functionality is being further enhanced to utilize current VistA suggestions for Patient, Provider and Drug/SIG. For Patient and Provider if no auto-match was found the software will look for any existing suggestion and will auto-match to the latest VistA suggestion on file. In the case of Drug/SIG it will be greatly improved by matching not only the dispense drug but all fields from the suggested VistA Rx (if one exists), exactly as if the user accepted the suggestion manually. 18. [HDSO-9162] Updates to existing Accept(AC) action in Single eRx View/Display screen --------------------------------------------------------------------------- The existing Accept(AC) action in the Single eRx View/Display screen will automatically try perform the validation (AV) for Patient (except for MbM), Provider and Drug as well, if needed, before accepting the eRx. This action will still perform all the checks necessary by each individual record match and will display the result for validating each match separately. Note: Please, refer to the user documentation for more detailed information about this new functionality. 19. [HDSO-9163] Ability to change the Hold code w/out Un-holding an eRx --------------------------------------------------------------------------- Users will now be able to switch the Hold code for an eRx on Hold for a different Hold code without having to un-hold the eRx. Once the user selects the Hold (H) action to hold an eRx already on software will inform them the eRx is already on hold and will ask if they want to change the Hold code. 20. [HDSO-8774] First-In-First-Out (FIFO) processing for Complete Orders from OERR [PSO LMOE FINISH] option --------------------------------------------------------------------------- A FIFO order algorithm has been implemented for this option for users that hold the newly created PSO ERX WORKLOAD RPH security key. Once the user holding this key enters the option they will be prompted for the Clinic they want to finish Pending Orders for and then if they want to process Flagged orders only. After answering these two prompts the option will automatically select the patient with the oldest record for the user to work on. The user will not be able to move to the next patient unless all the current patient's pending orders are either finished or flagged. Please, refer to the user documentation for more detailed information about this new functionality. 21. [HDSO-9170] eRx Prescriber Order Number in the Print --------------------------------------------------------------------------- The incoming prescriber order number will be displayed in Print (P) under the PRESCRIPTION INFORMATION section. 22. [HDSO-9185] Page breaking in the Print --------------------------------------------------------------------------- The Print (P) action will now page break one page at time instead of displaying the entire information, which forced the user to scroll up using the terminal scrolling capability. 23. [HDSO-9186] Allow Change Requests for eRx currently on Hold and Responses --------------------------------------------------------------------------- Two changes are being made to the Change Request (EC Action) functionality: a) The Change Request (EC) action will be allowed to be run on eRx's that are currently on Hold. b) The Change Request (EC) action will be allowed to be run Response eRx's. Before, the EC action was restricted to the NewRx records only. 24. [HDSO-9187] RxChangeRequest 'Therapeutic Interchange/Subst.' reason message templates --------------------------------------------------------------------------- The CHANGE REQUEST CODE for 'Therapeutic Interchange/Substitution' has been updated to allow the pharmacist/technician to choose a reason code linked to a pre-made question template in the field. The user will be prompted to choose a CHANGE REQUEST SUB-CODE from the options provided. 25. [HDSO-9188] MbM Only: Auto-Holds for Pt. Eligibility and Non-Allergy Assessment --------------------------------------------------------------------------- Upon arrival from the eRx Hub the eRx will be checked whether the VistA Patient was auto-matched or not. If it was successfully matched, the software will then check if the patient is eligible for ChampVA Rx benefit, if not, the software will automatically hold the eRx with an HEL (PATIENT ELIGIBILITY ISSUE). If eligible, the software will then check if the patient has an Allergy Assessment on file, if not, the software will automatically hold the eRx with an HAL (NO PATIENT ALLERGY ASSESSMENT). 26. [HDSO-9189] Menu changes to the Single eRx View/Display Screen --------------------------------------------------------------------------- The bottom menu for the eRx Single eRx View/Display Screen was modified to increase the listing area by 2 lines. Only 3 actions will be available in the main menu: VP-VALIDATE PATIENT, VM-VALIDATE PROVIDER and VD-VALIDATE DRUG/SIG. The actions P-Print and UH-Un Hold eRx were move to the Hidden actions section. 27. [HDSO-9190] New View Suggested Rx (VSR) action --------------------------------------------------------------------------- A new hidden action VSR was added to the eRx Single eRx View/Display hidden menu. This option will allow the user to view the VistA Rx that was used to suggest populate the prescription information for the current eRx. It will invoke the same layout from the View Prescription [PSO VIEW] option. Once the user selects VSR and there's a Suggested VistA Rx that was used to populate the eRx, the user will receive the following notice before their are taken to viewing the suggested VistA Rx: _____________________________NOTICE______________________________________ You will be taken to the VistA prescription that was used to pre-populate the Drug fields (Product/SIG/Qty/Days Supply/# of Refills/Substitution) for this eRx (aka, 'Suggested VistA Rx'). This VistA Rx may or may not be for the same patient in this eRx being processed. _________________________________________________________________________ Type to continue or '^' to exit: 28. [HDSO-9191] New value for ACTION on SUGGESTION prompt: (V) VIEW RX --------------------------------------------------------------------------- The suggestion prompt for the Drug/Sig will now offer a new option VIEW RX (V) to allow the user to view the VistA Rx information before accepting it. If the user select V a notice will be displayed before taking the user to view the Suggested VistA Rx detail. 29. [HDSO-9192] VistA Prescriber Class displayed on Single eRx and Pending Order --------------------------------------------------------------------------- The VistA Provider Class will now be displayed in the eRx Holding Queue as well as when viewing an eRx Pending Order. 30. [HDSO-9193] New Next Drug (ND) hidden action --------------------------------------------------------------------------- The Next Drug (ND) hidden action was introduced to facilitate the user navigation to the Drug Validation screen for the actionable eRx from a single patient. This new action will work from two different screens in the eRx Holding Queue: a) eRx Single Patient Queue: if the user types "ND" in this screen it will take the user to the Drug Validation directly for the first actionable eRx for the current patient. b) Drug Validation: if the user types "ND" in this screen it will take the user to the Drug Validation screen for the next (based on eRx Received Date/Time) actionable eRx for the patient. If the patient has only one actionable eRx it will stay in the same eRx. If they current eRx is the last eRx on file for the patient it will loop back to the first eRx. 31. [HDSO-9194] Indication functionality added to eRx Holding Queue --------------------------------------------------------------------------- When matching the VistA Drug the user will now be prompted to also enter the Indication. This functionality was only available in CPRS, Complete Orders from OERR [PSO LMOE FINISH] and Patient Prescription Processing [PSO LM BACKDOOR ORDERS] options and it is now being extended to the eRx Holding Queue Processing [PSO ERX QUEUE PROCESSING] option as well. If the patient record includes Indication, the user will now see the Indication shown on the Single eRx View/Display landing page. The Indication field will be displayed in the Single eRx View/Display screen as well as in the Drug Validation screen, where it can be edited. Please, refer to the user documentation for more detailed information about this new functionality. 32. [HDSO-9195] Added RRE and CRE error codes under CCR Filter --------------------------------------------------------------------------- The two error codes listed below have been added under CCR Filter. This will enable technicians to monitor and examine the RxChangeRequest/ RxRenewalRequest sent either by the VA eRx hub software or by the outside prescribers. 33. [HDSO-9206] Patient DOB check on Edit and Accept Validation warning --------------------------------------------------------------------------- When editing or accepting validating the VistA patient, if the DOB of the eRx Patient does not match to the DOB of the VistA Patient, a warning message is displayed. 34. [HDSO-9208] Memorize the VistA patient when eRx is selected () --------------------------------------------------------------------------- When the user selects an eRx that has a VistA Patient matched to it, the VistA patient will now be memorized as the last patient accessed by the user, therefore when the user type at a VistA PATIENT prompt, it will automatically select the VistA Patient matched to the eRx. 35. [HDSO-9209] HFF for Un-Accept and Un-Remove will now ask for Future Fill Date --------------------------------------------------------------------------- When Un-Accepting or Un-Removing an eRx and selecting the hold code HFF (HOLD FOR FUTURE FILL) the software was not prompting the user to select a 'Future Fill Hold Date', which indicates when the eRx should be automatically be un-held. This was causing the eRx to be unheld immediately after being put on hold. This will be fixed with this patch. 36. [HDSO-9210] IAS (Include All Statuses) action extended to Rx Medication Queue as well --------------------------------------------------------------------------- The IAS action that was only available at the eRx Single Patient Queue will now be available in the Rx Medication Queue as well. This action is used to indicate that all eRx statuses should be included in the list and it will behave as such for the Rx Medication Queue as well. 37. [HDSO-9211] eRx Prescriber Phone # displayed on Pending Order and Active Rx --------------------------------------------------------------------------- The eRx Prescriber Phone # will now be displayed for the eRx Pending Order as well as for an ACTIVE eRx prescription. 38. [HDSO-9212] VistA Drug Edit capability on the Single eRx View/Display screen --------------------------------------------------------------------------- When viewing the eRx int he Single eRx View/Display screen the users will now be able to edit the drug fields. Before, this capability was only available in the Validate Drug (VD action) screen. This will allow users to do quick edits such as Indication or Patient Instructions field without having to go into the Validate Drug screen. The edit can be done exclusively by typing the # of the field the user intends to edit, if #1 (Drug) is selected the user will be prompt to edit all other fields as well. 39. [HDSO-9213] After AV it will go back to Single eRx View/Display (VAMC's only) --------------------------------------------------------------------------- A small change was made to streamline the processing of eRx's. Once the user accepts validation (AV action) for a patient, provider or drug, the software will take them automatically to the Single eRx View/Display screen. This ways they don't have to type "^" or 's in order to go back to the Single eRx View/Display screen. 40. [HDSO-9214] Default for Copy PATIENT INSTRUCTIONS from Rx#12345? Y// changed to 'NO' --------------------------------------------------------------------------- When accepting a VistA Drug suggestion for an eRx, the software prompts the user if they also want to copy the Patient Instructions from the suggested VistA Rx if it has this field populated. The default for this prompt was 'YES' and it is being changed to 'NO'. 41. [HDSO-9215] Jump to eRx (JE) action modification at the Patient level --------------------------------------------------------------------------- The Jump to eRx (JE) action used to jump from Backdoor Pharmacy back to the eRx Holding Queue is being modified to included all variations of the eRx Patient that are matched to the same VistA Patient. Instead of jumping to the eRx Single Patient Queue the user will now be taken to the eRx Medication Queue with the VistA Patient filter automatically set with the patient that was selected in Backdoor Pharmacy. Therefore, the list items will include all eRx's from all eRx Patients that have been matched to the VistA Patient. 42. [ERXCS-3575] DEA Nightly Update Job w/ Data from DEA/DOJ --------------------------------------------------------------------------- A new menu option called DEA Number Nightly Update with DEA/DOJ Data [PSO DEA/DOJ NIGHTLY DATA UPD] is being created by this patch. This option is used for automatically updating the Kernel DEA NUMBERS file (#8991.9) with the latest prescriber DEA information from DEA/DOJ database. It will run nightly and it will update DEA data for entries that are 30 days or less from expiring. This new option will be added to the list of options that can be edited via the existing Queue Background Jobs [PSO AUTOQUEUE JOBS] option. 43. [ERXCS-3576] Patient address will ignore differences between similar words --------------------------------------------------------------------------- The patient address comparison between eRx and VistA patients is being enhanced to recognize and ignore these differences listed below by not reversing the video if these are the only difference between the addresses: DR = DRIVE APT = APARTMENT STE = SUITE AVE = AVENUE W = WEST S = SOUTH ST = STREET NW = NORTHWEST SW = SOUTHWEST HGWY = HIGHWAY NE = NORTHEAST SE = SOUTHEAST BLVD = BOULEVARD CT = COURT RD = ROAD TER = TERRACE PKY = PARKWAY 44. [ERXCS-3577] Conversion issue with Patient Weight when prescriber sent in g (grams) --------------------------------------------------------------------------- When the outside prescriber sent in a patient weight in grams (g) the software was not making the proper conversion to kilograms and it was displaying the value in grams with a 'kg' indication in the Patient Validation screen. 45. [ERXCS-3578] HFF (Hold for Future Fill) will now set the Effective Date if none --------------------------------------------------------------------------- If an eRx is received without an Effective Date value and No Refills and the user decides to hold it with a future fill date (HFF), if the date entered by the user is more than 30 days from eRx Written Date the software will set the Effective Date on the eRx with the future date entered by the user when placing the eRx on Hold with the HFF code. 46. [ERXCS-3579] CAO status will automatically be set with CAA (MbM only) --------------------------------------------------------------------------- When a cancelation is received from the outside prescriber and the eRx status is set to CAO (CANCEL PROCESS COMPLETE) the software will automatically set it to CAA (CANCEL REQUEST ACKNOWLEDGED) for Meds-by-Mail sites. The reason is because the volume of CAO records at Meds-by-Mail makes it impossible to acknowledge them manually one by one. 47. [ERXCS-3580] Cancelations of RxRenewal and RxChange were not DCing Pending/Active Order --------------------------------------------------------------------------- When a RxRenewal or Rx Change response had been processed from the eRx Holding queue and were either on the Pending or Active order queue and the outside prescriber sent in a cancellation for the renewal or accepted change request the software was failing to proper cancel (DC) the pending or active order for the corresponding medication. This issue is being addressed by this patch. 48. [ERXCS-3581] Allergies compare between eRx and VistA were Case Sensitive --------------------------------------------------------------------------- When comparing incoming list of allergies from the external prescriber with the list of VistA allergies the software was performing a case sensitive comparison. In other words, if the outside prescriber sent in 'Tomato' and in VistA we had 'TOMATO' it would reverse the video on both because it assumed them to be different. This issue is being addressed by this patch. 49. [ERXCS-3582] Update to the Pharmacist Enter/Edit [PSO RPH] option --------------------------------------------------------------------------- Previously this option was used to allocated and de-allocate the PSORPH key that identifies a user as a pharmacist on the system. It is now being modified to allow allocation and de-allocation of the following eRx keys: PSO ERX WORKLOAD TECH PSO ERX WORKLOAD RPH These keys are mostly used by MbM to flag a user as a workload processing technician or pharmacist, which prevents them from skipping orders, effectively imposing a FIFO (First-In-First-Out) processing of incoming eRx and Pending orders. 50. [ERXCS-3583] New option for Batch Change Request and VistA Drug Replacement --------------------------------------------------------------------------- The new option Batch eRx Change Request/VistA Drug Replacement [PSO ERX BATCH CH REQ/DRUG SWAP] placed under the Supervisor Functions [PSO SUPERVISOR] menu option. It is used to perform two distinct tasks: Submission of Multiple eRx Change Requests Replacement of the Vista Dispense Drug on finished prescriptions (MbM only) The user will respond few prompts, specific to the task they want to perform, a list will be presented before the user actually perform the update. The Replacement of the VistA Dispense Drug is available to MbM (Meds-by-Mail) only users. For more information about this option please review the user documentation released along with this patch. 51. [ERXCS-3584] eRx Pending Order Suggested FILL DATE auto calculation --------------------------------------------------------------------------- Currently, the Fill Date field for an eRx Pending Order is always set to the current date. In some cases this is not ideal because the patient might still have enough medication to last a few more days and a future fill date, based on the last fill for the medication might be more appropriate. The algorithm will auto calculate the suggested Fill Date using the following logic: Requirement: - A previous prescription for the exact same drug must be found on the patient's profile - The SIG from the previous prescription must match exactly with the SIG for the new eRx Pending Order Suggested Future Fill Date: - If the Last Fill in the in the existing prescription is released and the Release Date + Days Supply results in a future date, this future date will be suggested as the Fill Date for the eRx Pending Order. - If the CMOP Transmission status for the Last Fill is TRANSMITTED or RE-TRANSMITTED, the Fill Date for the eRx Pending Order will be today's date + Days Supply for the Suspended fill. - If Last Fill is Suspended with a future Fill Date this future date will be suggested as the Fill Date for the eRx Pending Order. 52. [ERXCS-3622] Added three (3) Remove Reason codes to the ERX SERVICE REASON CODES FILE #52.45. ----------------------------------------------------------------------- The three codes are: REM81 Prior Authorization Denied REM82 No Community Care Authorization for this Prescription REM83 Patient Not Found in Local VA Database Test Sites: ---------- Central Texas VAMC, Temple TX Meds-By-Mail SNOW Change Order #: -------------------- Central Texas VAMC - CO# CHG0628499 Meds-By-Mail - CO# - CHG0628432 Documentation Retrieval Instructions: ------------------------------------- The software for this patch is being released in a PackMan message. Documentation describing the new functionality is included in this release. Documentation can be found on the VA Software Documentation Library at: https://www.domain.ext/vdl/. Documentation can also be obtained at https://download.vista.domain.ext/index.html/SOFTWARE. Title File Name ---------------------------------------------------------------------- Deployment, Installation Back-Out PSO_7_0_P770_DIBRG.DOCX and Rollback Guide PSO_7_0_P770_DIBRG.PDF Release Notes PSO_7_0_P770_RN.DOCX PSO_7_0_P770_RN.PDF Outpatient Pharmacy Version 7 Manager's PSO_7_0_P770_MAN_UM.DOCX User Manual PSO_7_0_P770_MAN_UM.PDF Outpatient Pharmacy Version 7 PSO_7_0_P770_PHARM_UM.DOCX Pharmacist's User Manual PSO_7_0_P770_PHARM_UM.PDF Manual/Security Guide - PSO_7_0_P770_TM.DOCX Outpatient Pharmacy V.7.0 PSO_7_0_P770_TM.PDF Inbound ePrescribing User Manual PSO_7_0_P770_UM_71.DOCX (Unit 7 Part 1) PSO_7_0_P770_UM_71.PDF Inbound ePrescribing User Manual PSO_7_0_P770_UM_72.DOCX (Unit 7 Part 2) PSO_7_0_P770_UM_72.PDF Patch Installation: Pre-Installation Instructions: ============================= This patch should 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 about 2 to 3 hours to complete installation. Installation Instructions: 1. Choose the PackMan message containing this build. Then select the INSTALL/CHECK MESSAGE PackMan option to load the build. 2. From the Kernel Installation and Distribution System Menu, select the Installation Menu. From this menu, A. Select the Verify Checksums in Transport Global option to confirm the integrity of the routines that are in the transport global. When prompted for the INSTALL NAME enter the patch or build name. (ex. PSO*7.0*770) NOTE: Using will not bring up a Multi-Package build even if it was loaded immediately before this step. It will only bring up the last patch in the build. B. Select the Backup a Transport Global option to create a backup message. You must use this option and specify what to backup; the entire Build or just Routines. The backup message can be used to restore the routines and components of the build to the pre-patch condition. i. At the Installation option menu, select Backup a Transport Global ii. At the Select INSTALL NAME prompt, enter your build PSO*7.0*770 iii. When prompted for the following, enter "R" for Routines or "B" for Build. Select one of the following: B Build R Routines Enter response: Build iv. When prompted "Do you wish to secure your build? NO//", press and take the default response of "NO". v. When prompted with, "Send mail to: Last name, First Name", press to take default recipient. Add any additional recipients. vi. When prompted with "Select basket to send to: IN//", press and take the default IN mailbox or select a different mailbox. C. You may also elect to use the following options: i. Print Transport Global - This option will allow you to view the components of the KIDS build. ii. 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 of the components of this patch, such as routines, DDs, templates, etc. D. Select the Install Package(s) option and choose the patch to install. i. If prompted 'Want KIDS to Rebuild Menu Trees Upon Completion of Install? NO//', answer NO. ii. When prompted 'Want KIDS to INHIBIT LOGONs during the install? NO//', answer NO. iii. When prompted 'Want to DISABLE Scheduled Options, Menu Options, and Protocols? NO//', answer NO. Post-Install ============ A few steps will be performed soon after the patch is installed: 1) The eRx status description for CAP (CANCEL PAPER RX OR FAXED RX) will be renamed to UNABLE TO FIND ORIGINAL ERX as it better describes an eRx that is automatically assigned this status. 2) New entries are being added to the ERX SERVICE REASON CODES (#52.45) file to be used for Script Clarification Change Requests. These new codes will also have pre-populated content in the CHANGE REQUEST REASON TEXT (#20) field that will used for as the default text when the user selects one of these new codes: PRN - Indicates that the prescription received is missing dose and/or frequency guidelines. Default CH REQUEST text: VA policy prohibits filling prescriptions with only "AS NEEDED" for directions. Please indicate frequency of administration. UDD - Indicates that the prescription received is missing dose and/or frequency guidelines. Default CH REQUEST text: VA policy prohibits filling prescriptions with only "AS DIRECTED" for directions. Please indicate frequency of administration. COD - Indicates that the prescription received has conflicting directions. Default CH REQUEST text: This prescription contains conflicting directions. Please verify which directions are to be followed. MSD - Indicates that the prescription received has incomplete directions for use. Default CH REQUEST text: Please provide the complete set of patient instructions. RIJ - Indicates that the prescription received is missing the route of injection for medication. Default CH REQUEST text: Please verify the ROUTE of injection. VEF - Indicates that the prescription received is missing the formulation of medication to dispense. Default CH REQUEST text: Please verify which formulation of should be dispensed. VLQ - Indicates the prescription received has a written quantity that is less than typical prescribing. Default CH REQUEST text: The quantity written is less than typically prescribed. Please verify the quantity to dispense. VPQ - Indicates the prescription received has a written quantity that is less than smallest available quantity to dispense from the pharmacy. Default CH REQUEST text: Please verify the quantity to dispense. Our filling sites are only able to provide this product in quantities of [QUANTITY], which is more than the total quantity prescribed. AUT - Indicates the Prescriber is not authorized by VA to see this patient Default CH REQUEST text: VA records show this patient does not have active authorization for care from your office. This prescription will be removed from the VA system. For authorization questions, patients or providers can call the VA Office of Community Care at [PHONE_NUMBER]. 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. To back-out data from a production account could cause broken pointers, errors and hard MUMPS crashes. The back-out plan for data only patches is to report your findings and wait for a repair patch. Contact Help desk to log a ticket. Validation of Back-out Procedure: -------------------------------- The Back-out Procedure can be verified by confirming the checksums have been returned to the pre-patch value using CHECK1^XTSUMBLD. It can also be verified by printing the first 2 lines of the PSO routine(s) contained in this patch using the option First Line Routine Print [XU FIRST LINE PRINT]. Once the routine(s) contained in this patch have been backed out, the Second line of each routine will no longer contain the designation of patch PSO*7*770. Routine Information: ==================== The second line of each of these routines now looks like: ;;7.0;OUTPATIENT PHARMACY;**[Patch List]**;DEC 1997;Build 145 The checksums below are new checksums, and can be checked with CHECK1^XTSUMBLD. Routine Name: PSO770PI Before: n/a After:B184233702 **770** Routine Name: PSOBKDED Before:B101972565 After:B102124543 **11,46,91,78,99,117,133,143, 268,378,416,282,450,402,518, 525,538,457,557,574,598,441, 770** Routine Name: PSODDPRE Before:B144226528 After:B144536536 **251,375,387,379,390,372,416, 411,518,568,768,770** Routine Name: PSODEAUJ Before: n/a After: B20562058 **770** Routine Name: PSODIR Before:B151449083 After:B152006838 **37,46,111,117,146,164,211, 264,275,391,372,416,422,504, 457,572,587,441,682,545,770** Routine Name: PSODIR1 Before:B118115170 After:B118326662 **23,46,78,102,121,131,146,166, 184,222,268,206,266,340,391, 444,446,505,543,457,574,612, 686,700,769,770** Routine Name: PSODRGU0 Before: n/a After: B10898664 **770** Routine Name: PSOERBT Before: n/a After:B170317360 **770** Routine Name: PSOERBT0 Before: n/a After: B9914387 **770** Routine Name: PSOERBT1 Before: n/a After: B18110137 **770** Routine Name: PSOERBT2 Before: n/a After: B4345286 **770** Routine Name: PSOERCR0 Before:B165516091 After:B170774137 **746,770** Routine Name: PSOERCR1 Before: B46252949 After: B88766296 **746,769,770** Routine Name: PSOERHL0 Before:B126138922 After:B125621416 **700,746,770** Routine Name: PSOERPC0 Before:B148442454 After:B157345967 **700,750,746,770** Routine Name: PSOERPC1 Before:B142780336 After:B141378939 **700,750,746,770** Routine Name: PSOERPC3 Before: n/a After: B31946529 **770** Routine Name: PSOERPR1 Before: B53671041 After: B53784163 **700,746,770** Routine Name: PSOERPT0 Before:B116173284 After:B112432602 **700,746,770** Routine Name: PSOERPT1 Before: B98203689 After: B98391328 **700,750,746,769,770** Routine Name: PSOERRX0 Before: B99607386 After:B167933274 **700,746,770** Routine Name: PSOERRX1 Before:B108552724 After:B151562025 **700,769,770** Routine Name: PSOERRX2 Before: n/a After: B11816322 **770** Routine Name: PSOERSE1 Before:B102102684 After:B133027664 **746,769,770** Routine Name: PSOERSE2 Before:B163450869 After:B163451091 **746,770** Routine Name: PSOERSE3 Before: B34918673 After: B71025259 **746,769,770** Routine Name: PSOERUT Before:B107331848 After:B114627152 **692,700,746,769,770** Routine Name: PSOERUT0 Before:B127399770 After:B164559924 **700,750,746,769,770** Routine Name: PSOERUT1 Before: B56849682 After:B100791599 **700,743,746,770** Routine Name: PSOERUT2 Before:B155662863 After:B150913587 **700,746,769,770** Routine Name: PSOERUT3 Before: B84605566 After:B110242465 **700,746,770** Routine Name: PSOERUT4 Before:B173872765 After:B122708956 **700,746,769,770** Routine Name: PSOERUT5 Before:B164844096 After:B150487031 **700,746,769,770** Routine Name: PSOERUT6 Before: B32370212 After:B128242113 **700,746,769,770** Routine Name: PSOERUT7 Before: B37310895 After: B35733744 **746,769,770** Routine Name: PSOERX1A Before:B241525768 After:B195986410 **467,527,508,551,581,617,669, 700,743,746,770** Routine Name: PSOERX1B Before:B187424113 After: B33863508 **467,506,520,527,508,551,591, 606,581,617,700,770** Routine Name: PSOERX1C Before:B135100439 After:B160717921 **467,520,527,508,551,581,617, 646,700,746,769,770** Routine Name: PSOERX1D Before:B163858823 After:B163905413 **581,617,746,769,770** Routine Name: PSOERX1E Before: B74386875 After:B109399901 **581,700,746,770** Routine Name: PSOERX1F Before:B181537376 After:B143851877 **617,651,700,746,770** Routine Name: PSOERX1G Before:B173619495 After:B173619795 **617,646,689,700,743,770** Routine Name: PSOERX1H Before: B99533853 After:B181985166 **700,746,770** Routine Name: PSOERX1I Before: n/a After: B6176883 **770** Routine Name: PSOERXA0 Before: B49036491 After: B50264250 **467,586,617,651,545,743,769,770** Routine Name: PSOERXA1 Before:B136282665 After:B136385329 **467,520,508,551,581,617,743,770** Routine Name: PSOERXA5 Before: B76145450 After: B77895227 **508,581,631,617,651,770** Routine Name: PSOERXD1 Before: B61782724 After: B62978153 **467,520,551,582,581,635,617, 651,689,700,746,769,770** Routine Name: PSOERXD2 Before:B182141502 After:B192209594 **467,506,520,508,551,581,617, 651,689,700,746,770** Routine Name: PSOERXD3 Before: B12463872 After: B20213477 **651,700,770** Routine Name: PSOERXH1 Before: B45587698 After: B41374190 **467,527,508,581,617,700,746, 769,770** Routine Name: PSOERXH2 Before: B5940949 After: B5450949 **700,770** Routine Name: PSOERXI1 Before: B70682385 After:B112507414 **581,617,692,706,700,743,746, 783,770** Routine Name: PSOERXI2 Before: B95050067 After: B95522350 **700,770** Routine Name: PSOERXID Before: B92041544 After: B92464834 **581,635,770** Routine Name: PSOERXIE Before:B160873994 After:B161686459 **581,617,746,770** Routine Name: PSOERXIF Before:B150440707 After:B151144223 **581,635,770** Routine Name: PSOERXIG Before:B148255571 After:B148691921 **581,770** Routine Name: PSOERXIH Before: B56027681 After: B56173187 **581,770** Routine Name: PSOERXII Before: B73900204 After: B74165517 **581,635,770** Routine Name: PSOERXOE Before: B31609262 After: B31254228 **581,770** Routine Name: PSOERXOG Before: B62418789 After: B62724048 **581,746,770** Routine Name: PSOERXOI Before: B20419812 After: B19721912 **581,746,770** Routine Name: PSOERXP1 Before: B6271070 After: B6423600 **467,520,527,551,581,700,746,770** Routine Name: PSOERXR1 Before: B4504672 After: B4693651 **467,520,527,581,545,700,746,770** Routine Name: PSOERXU1 Before:B177649006 After:B177719543 **467,520,508,551,565,581,617, 651,700,746,770** Routine Name: PSOERXU2 Before: B92341812 After:B113811863 **508,598,581,631,617,746,770** Routine Name: PSOERXU3 Before:B169517697 After:B172927175 **508,591,606,581,617,646,700, 746,770** Routine Name: PSOERXU4 Before:B100231000 After:B110372446 **520,508,551,581,635,617,651, 700,746,770** Routine Name: PSOERXU5 Before:B133794438 After:B138498836 **508,581,651,746,769,770** Routine Name: PSOERXU6 Before:B134374696 After:B136993537 **508,551,581,631,617,672,715, 700,746,770** Routine Name: PSOERXU7 Before:B126290133 After:B129576560 **581,617,700,746,769,770** Routine Name: PSOERXU8 Before: B47776897 After: B51979282 **581,617,700,743,746,770** Routine Name: PSOERXU9 Before: B55350716 After: B55389495 **617,700,746,770** Routine Name: PSOERXUX Before: B14973542 After: B16451045 **700,746,770** Routine Name: PSOHELP1 Before: B49158758 After: B49872441 **23,36,88,146,227,222,408,444,770** Routine Name: PSOLMUTL Before: B16012281 After: B16374233 **19,46,84,99,131,132,148,268, 225,305,386,390,622,441,746, 765,770** Routine Name: PSONEW2 Before: B44268923 After: B45057151 **32,37,46,71,94,124,139,157, 143,226,237,239,225,251,375, 372,504,441,770** Routine Name: PSONFI Before: B9591033 After: B9836875 **46,94,131,225,391,700,746,770** Routine Name: PSOORCPY Before: B60045905 After: B60428400 **10,21,27,32,46,100,117,148, 313,411,444,468,504,477,441, 545,700,753,770** Routine Name: PSOORFI1 Before:B130223477 After:B129794962 **7,15,23,27,32,44,51,46,71, 90,108,131,152,186,210,222,258, 260,225,391,408,444,467,505, 617,441,651,700,746,753,770** Routine Name: PSOORFI2 Before: B96811540 After:B100326867 **7,15,23,27,46,130,146,177, 222,225,338,313,408,612,770** Routine Name: PSOORFI3 Before: B85211636 After: B86523001 **15,27,32,46,84,99,130,117, 139,172,225,300,384,372,505, 557,700,770** Routine Name: PSOORFIN Before: B94275893 After:B142326958 **7,15,27,32,44,46,84,106,111, 117,131,146,139,195,225,315, 266,338,391,372,416,446,505, 508,557,628,441,710,770** Routine Name: PSOORNE4 Before:B107080840 After:B106570389 **11,27,32,36,46,75,96,103,99, 117,131,225,386,390,391,313, 411,661,441,700,743,746,769, 770** Routine Name: PSOORNE5 Before: B57070214 After: B57320688 **11,27,32,46,78,99,117,131, 146,171,180,210,222,268,206, 225,391,444,504,441,545,770** Routine Name: PSOORNEW Before:B141817738 After:B141477735 **11,23,27,32,55,46,71,90,94, 106,131,133,143,237,222,258, 206,225,251,386,390,391,372, 416,431,313,408,436,411,444, 486,446,505,517,508,457,581, 617,441,651,700,746,769,770** Routine Name: PSOORUT3 Before: B9927373 After: B14289108 **5,25,243,700,770** Routine Name: PSORENW1 Before: B68220791 After: B70751476 **20,37,51,46,71,117,157,143, 219,239,225,444,548,587,441, 753,770** Routine Name: PSOSPML4 Before:B109923547 After:B116681933 **408,451,625,659,662,770** Routine Name: PSOSUP Before: B8330003 After: B9172286 **10,268,501,770** Routine list of preceding patches: 501, 662, 710, 753, 765, 768, 769, 783 ============================================================================= User Information: Entered By : Date Entered : JUL 10, 2024 Completed By: Date Completed: JUL 23, 2025 Released By : Date Released : JUL 23, 2025 ============================================================================= Packman Mail Message: ===================== $END TXT