$TXT Created by F at CLN1G1.AAC.DOMAIN.EXT (KIDS) on Wednesday, 11/03/21 at 15:49 ============================================================================= Run Date: NOV 19, 2021 Designation: PSO*7*617 Package : PSO - OUTPATIENT PHARMACY Priority: Mandatory Version : 7 SEQ #535 Status: Released Compliance Date: DEC 20, 2021 ============================================================================= Associated patches: (v)PSO*7*52 <<= must be installed BEFORE `PSO*7*617' (v)PSO*7*477 <<= must be installed BEFORE `PSO*7*617' (v)PSO*7*505 <<= must be installed BEFORE `PSO*7*617' (v)PSO*7*524 <<= must be installed BEFORE `PSO*7*617' (v)PSO*7*557 <<= must be installed BEFORE `PSO*7*617' (v)PSO*7*586 <<= must be installed BEFORE `PSO*7*617' (v)PSO*7*597 <<= must be installed BEFORE `PSO*7*617' (v)XU*8*739 <<= must be installed BEFORE `PSO*7*617' (v)PSO*7*631 <<= must be installed BEFORE `PSO*7*617' (v)PSO*7*635 <<= must be installed BEFORE `PSO*7*617' Subject: CONTROLLED SUBSTANCE (CS) eRx ENHANCEMENTS Category: - Routine Description: ============ The Inbound Electronic Prescribing (eRx) v5.0 enhancements include updates to the current eRx functionality to allow the VA to receive and dispense electronic prescriptions for controlled substance medications. Up until now the eRx Holding Queue restricted the selection of a controlled substance VA dispense drug for any incoming electronic prescription due to the fact that the functionality was not 100% compliant with the DEA requirements (21 CFR Part 1311 Subpart C) for receiving, processing and dispensing controlled substance electronic prescriptions. This project addresses all the DEA requirements and enables the eRx Holding Queue to process incoming electronic prescriptions for controlled substance medications. Below is a list of all the applications involved in this project along with their patch number: APPLICATION/VERSION PATCH ----------------------------------------------------------------- OUTPATIENT PHARMACY (PSO) V. 7.0 PSO*7*617 CONTROLLED SUBSTANCE (PSD) V. 3.0 PSD*3*89 Below is a list of new and changed functionality delivered by this patch to satisfy the DEA requirements for receiving, processing and dispensing electronic prescriptions for controlled substance medications. 1. New HOLD, REJECT and REMOVE codes --------------------------------------------------------------------------- The following new codes have been added: HOLD Codes: ----------- HCR - PRESCRIBER'S CS CREDENTIAL IS NOT APPROPRIATE (New) HWR - CS PRESCRIPTION WRITTEN/ISSUE DATE HAS PROBLEMS (New) HIS - PROVIDER DEA# ISSUE (New) HRX - HOLD FOR RX EDIT (New) HDE - DRUG USE EVALUATION (New) HTI - THERAPUTIC INTERCHANGE (New) HSC - SCRIPT CLARIFICATION (New) HGS - GENERIC SUBSTITUTION (New) REJECT Codes: ------------- PVD03 - Missing/bad digital signature on inbound CS ERX (New) PVD04 - Prescriber's CS credential is not appropriate (New) PTT03 - Patient's mailing address is missing/mismatched (New) DRU06 - Controlled Substances are disallowed (Renamed) DRU06 - CS prescription written/issue date has problems (New name) ERR99 - Other REMOVE Codes: ------------- REM09 - ERX Issue not resolved-Provider contacted (New) 2. CMOP Controlled Substance Rx Dispense Report [PSO CMOP CS RX DISPENSE REPORT] --------------------------------------------------------------------------- The report option above was modified to include the ampersand sign (&) before the Rx # to indicate the prescription is an eRx prescription (e.g., &29039001A) 3. Released and Unreleased Prescription Report [PSO RELEASE REPORT] --------------------------------------------------------------------------- The report option above was modified to include the ampersand sign (&) before the Rx # to indicate the prescription is an eRx prescription (e.g., &29039001A) 4. Complete Orders from eRx [PSO ERX FINISH] --------------------------------------------------------------------------- A few changes have bene made to the eRx Holding queue option above to comply and facilitate the processing of controlled substance medication prescriptions. a) A new filter was introduced to allow the user to select the type of prescriptions to be loaded on the eRx Holding Queue as shown below: Select one of the following: Non-CS Non-Controlled Substance CS Controlled Substance B Both Select eRx Record Type: B// b) If the selection above is either CS or B, a new filter prompt was added to allow the user to further filter based on the CS Schedule of the controlled substance medication as shown below: Select one of the following: 1 Schedule II 2 Schedules III - V 3 Schedules II - V Select Schedule(s): 3// c) In the Patient Centric View if a patient has a prescription for a controlled substance medication the line item will be marked with a closing square bracket (]) following the line number as shown below: --------------------------------------------------------------------------- PSO ERX PATIENT CENTRIC VIEW Feb 26, 2021@14:19:30 Page: 1 of 2 Patient Centric View ERX LOOK-BACK DAYS: Default value 365 (Feb 27, 2020) ERX PATIENT DOB ED LOCKED BY NW WT IP HD CCR OTH TOT --------------------------------------------------------------------------- 1] TESTONE,ONE 08/12/1956 12 0 0 4 0 0 0 4 2] TESTTWO,TWO 08/12/1956 12 0 0 7 1 0 0 8 3. TESTSIX,SIX 09/30/1938 6 0 0 1 1 0 0 2 4. TESTFOUR,FOUR 11/10/1965 3 0 0 4 0 0 0 4 5] TESTNINE,NINE 12/18/2014 1 1 0 2 0 0 0 3 ... In the example above lines 1, 2 and 5 have a ']' indicating that those patients have at least one controlled substance medication prescription. d) In the Prescription View the prescriptions for controlled substance medication will also be marked with ']' as shown below: --------------------------------------------------------------------------- PSO ERX HOLDING QUEUE Feb 26, 2021@14:26:24 Page: 1 of 1 PSO ERX HOLDING QUEUE ERX LOOK-BACK DAYS: Default value 365 (Feb 27, 2020) Patient DOB Drug Provider STA Rec Date --------------------------------------------------------------------------- 1] TESTONE,ONE 8/12/56 ALPRAZOLAM 1MG TAB PROV,TEST I 02/28/21 2] TESTONE,ONE 8/12/56 TESTOSTERONE PATCH PROV,TEST I 02/12/21 3] TESTONE,ONE 8/12/56 METHYLPHENIDATE 5MG T PROV,TEST I 01/31/21 4. TESTONE,ONE 8/12/56 ALBUTEROL INHALER PROV,TEST I 01/29/21 ... In the example above lines 1, 2 and 3 have a ']' indicating that the prescription is for a controlled substance. e) In the Patient Centric View the SORT ENTRIES (SO) action was modified to add a new option to sort: ELAPSED DAYS (ED). The action was also changed to allow the user to separate the sorted prescriptions into two groups: Controlled and Non-Controlled Substances. Independently of which option the user picks they will be prompted whether they want to group the list by controlled substance or not as shown in the example below: Select Item(s): Next Screen// SO SORT ENTRIES 1.) PATIENT NAME 2.) DATE OF BIRTH 3.) ELAPSED DAYS (ED) Select one of the following sort criteria: Enter response: 3 ELAPSED DAYS (ED) Do you want to group by controlled substance? Enter Yes or No: YES// If the user answers YES the patients with at least one prescriptions for a controlled substance medication will be moved to the top of the list while the others will be moved to the bottom as shown below: --------------------------------------------------------------------------- 1] TESTONE,ONE 08/12/1956 6 0 0 4 0 0 0 4 2] TESTTWO,TWO 08/12/1956 5 0 0 7 1 0 0 8 3] TESTNINE,NINE 12/18/2014 2 1 0 2 0 0 0 3 3. TESTSIX,SIX 09/30/1938 3 0 0 1 1 0 0 2 5. TESTFOUR,FOUR 11/10/1965 0 0 0 4 0 0 0 4 ... f) When a DO NOT FILL marked record is received in the eRx Holding Queue it will be identified in the header with the text below (in reverse video) when the user is view viewing such record, as shown below: eRx Holding Queue Display Apr 01, 2021@09:58:15 Page: 1 of 3 eRx Patient: TEST,PATIENT eRx Reference #: 2002894 ERX HAS DO NOT FILL INDICATOR PER PROVIDER eRx HT: (cm)() eRx WT: (kg)() --------------------------------------------------------------------------- ... Note: The only two actions that can be performed on a DO NOT FILL record are REJECT and REMOVE. g) When viewing an eRx record the DEA# will be displayed along with the other information about the Provider (eRx and VistA) as shown below: ... eRx Provider Primary Telephone: 555-220-0303 eRx Provider: TEST,PROVIDER DEA#: TP1234568 NPI: 123456789 Vista Provider: TEST, PROVIDER F. DEA#: TP1234568 NPI: 123456789 ... h) For controlled substance medication eRx records the DEA Schedule will be displayed right after the drug name (eRx and Vista) in the following format: eRx Holding Queue Display Apr 06, 2021@10:22:57 Page: 1 of 3 eRx Patient: CS-ONLY,ONE eRx Reference #: 4928403 eRx HT: (cm)() eRx WT: (kg)() --------------------------------------------------------------------------- eRx Drug: MEPHOBARBITAL 100MG TABLET [C-IV] eRx Qty: 30 eRx Refills: 0 eRx Days Supply: 30 eRx Date: APR 06, 2021 eRx Sig: TAKE ONE TABLET BY MOUTH ONCE DAILY Vista Drug: MEPHOBARBITAL 100MG TAB [C-IV] Vista Qty: 30 Vista Refills: 0 Vista Days Supply: 30 ... i) The VistA Patient selection/validation for controlled substance medication eRx records will perform a check whether the selected VistA patient has a ZIP CODE on file or not. If the VistA patient does not have a ZIP CODE on file the following message will be displayed: i1. VistA Patient Selection/Edit (user will be allowed to proceed): **************************** WARNING(S) ***************************** Patient does not have a current mailing or residential address on file. ************************************************************************ i2. VistA Patient Validation (user will not be allowed to proceed): Unable to validate - VistA Patient does not have a current mailing or residential address on file. j) The VistA Provider selection/validation for controlled substance medication eRx records will perform a few checks to validate whether the selected VistA Provider is eligible to write the prescription: j1. Provider does not have a valid not expired DEA# on file: ***************************INVALID PROVIDER***************************** Missing VistA Provider DEA# ************************************************************************ j2. The VistA Drug was previously selected and VistA Provider is not authorized to write to the VistA drug DEA schedule: ***************************INVALID PROVIDER***************************** VistA Provider TEST,PROVIDER is NOT authorized to write to the schedule (C-II) of the VistA drug selected. ************************************************************************ j3. VistA Provider's DEA # expires prior to eRx written/issue date: ***************************INVALID PROVIDER***************************** eRx Written Date/Issue Date is after the VistA Provider DEA expiration date (MM/DD/YY). ************************************************************************ j4. eRx Provider's DEA # does not match VistA Provider DEA # (allows selecting the provider with a warning but blocks validation) *********** WARNING (edit) / INVALID PROVIDER (validation) ************* Provider DEA mismatch (eRx: TP123456 | VistA: TP654321) ************************************************************************ j5. The VistA Drug was previously selected and is a DETOX drug and VistA Provider does not have a valid not expired DETOX # on file (VistA drug must be previously selected): *********** WARNING (edit) / INVALID PROVIDER (validation) ************* VistA Provider TEST,PROVIDER does not have a valid DETOX# ************************************************************************ j6. During Provider validation the functionality that allows the user to assign the same provider to other prescriptions that match the eRx provider was changed to check whether the VistA provider is authorized to write each prescription if they are for a controlled substance or detox medication. If the VistA provider is not authorized a message will be displayed for the eRx and it will not be selected/validated for the prescription. k) The VistA Drug selection/validation for controlled substance medication eRx records will perform a few checks to validate whether the selected VistA Drug can be used for the prescription: k1. When the user selects the VALIDATE DRUG/SIG (VD) action and then selects the Edit (E) action to select the VistA dispense drug to associate it with the eRx record the prompt 'Select GENERIC DRUG NAME:' will now allow the selection of a drug marked as Controlled Substance. Before, CS drugs were not allowed to be selected. k2. VistA Drug selected is NOT marked as a controlled substance medication the eRx record is for a controlled substance (user will be allowed to proceed with a warning): **********************************WARNING******************************* eRx Drug is indicated by the prescriber as CS ([C-IV]) and VistA Drug selected is Non-CS. Please, review and make sure you selected the correct drug. ************************************************************************ k3. The VistA Drug selected is locally (not NDF matched) marked as a controlled substance medication and the eRx record is not for a controlled substance (does not have a digital signature). User will not be able to select the drug: *******************************INVALID DRUG***************************** eRx is not digitally signed and VistA drug is non-CS and VistA drug is not matched to an NDF item marked with a CS Federal Schedule but is locally marked as a controlled substance ([C-II]). ************************************************************************ k4. The VistA Drug selected is matched to and NDF item marked as a controlled substance medication and the eRx record is not eligible for a controlled substance (does not have a digital signature). User will not be able to select the drug: *******************************INVALID DRUG***************************** eRx is not digitally signed and VistA Drug is marked as CS ([C-III]). ************************************************************************ k5. The VistA Provider was previously selected and is not authorized to write to prescription for the DEA schedule of the VistA Drug : ******************************INVALID DRUG****************************** VistA Provider TEST,PROVIDER is NOT authorized to write to the schedule (C-II) of the VistA drug selected. ************************************************************************ k6. The VistA Provider was previously selected and does not have a valid not expired DETOX # and the VistA Drug selected is a DETOX drug. *********** WARNING (edit) / INVALID PROVIDER (validation) ************** VistA Provider TEST,PROVIDER does not have a valid DETOX# ************************************************************************* l) In the eRx Holding Queue Display where a single prescription is displayed a new hidden action called View Audit Log (AU) was introduced. This new functionality will allow the user to track every edit made to the eRx during the transcription of the eRx data to match the VistA corresponding entries. The log looks like the screen below and can be sorted by DATE/TIME, FIELD NAME or EDITED BY columns. eRx Audit Log May 14, 2021@15:27:57 Page: 1 of 2 ------------------------------------------------------------------------- eRx Patient: TEST,OUTPONE F eRx Reference #: 494949 ------------------------------------------------------------------------- DATE/TIME [^] FIELD NAME EDITED BY ------------------------------------------------------------------------- Jan 28, 2021@09:47:45 PATIENT TEST,USER F Old Value: New Value: TEST,OUTPONE (L4SSN: 7944 | DOB: DEC 18,2014) Jan 28, 2021@09:48:06 DRUG TEST,USER F Old Value: New Value: LOESTRIN FE 1/20 TAB,28 (NDC#: 51285-0080-70) Jan 28, 2021@09:48:13 SIG TEST,USER F Old Value: New Value: TAKE ONE TABLET PO ONCE DAILY Jan 28, 2021@09:48:18 QTY TEST,USER F Old Value: New Value: 30 ------------------------------------------------------------------------- + Enter ?? for more actions DT Sort by DATE/TIME EB Sort by EDITED BY FN Sort by FIELD SH Show/Hide eRx Value Select Item(s): Next Screen// l1) The actions DT, FN and EB are used to sort the list by the columns DATE/TIME, FIELD NAME and EDITED BY respectively. The SH action will show o hide the original prescription value for the field from the eRx record as shown below: ... Jan 28, 2021@09:47:45 PATIENT TEST,USER F eRx Value: TEST,OUTPONE F (L4SSN: 7944 | DOB: DEC 18, 2014) Old Value: New Value: TEST,OUTPONE (L4SSN: 7944 | DOB: DEC 18,2014) ... m) Besides the "]" (closing square bracket) described in the letter d) above to identify CS (digitally signed) eRx records once you select a specific record it will display on the top right corner of the scrollable are the following note (in reverse video) "EPCS DEA VALIDATED" to indicate to the user processing the record that the electronic digital signature has been validate and also to comply with SureScripts requirements for CS prescriptions. In addition, these records will also contains the foot note: This prescription meets the requirements of the Drug Enforcement Administration (DEA) electronic prescribing for controlled substances rules (21 CFR Parts 1300,1304, 1306, & 1311). n) When the user selects the action EC (eRx Change Request) for a CS eRx record they will be limited to selecting only one of the following two values below (P or U): Select RX change message request code: ? Answer with ERX SERVICE REASON CODES, or NUMBER, or BRIEF DESCRIPTION, or CODE TYPE ABBREVIATION, or NCIT SUBTYPE Do you want the entire ERX SERVICE REASON CODES List? y (Yes) Choose from: 9999 P Prior Authorization Required 9999 U Prescriber Authorization Select RX change message request code: o) When a Pending Order is un-accepted (see 5a below) a new entry will be added to the Status History for the related eRx record to indicate that it was un-accepted and sent back to the eRx Holding Queue. Below is an example how it will display: Select Action:Next Screen// SH Status History ------------------------------------------------------------------------- ... 07/17/20@10:48:50 PR PROCESSED Entered By: USER, NAME F Comments: 07/18/21@14:17:30 HRX HOLD FOR RX EDIT (eRx Un-Accepted) Entered By: USER, NAME F Comments: Wrong Patient associated with Rx Type to continue or '^' to exit: 5. Patient Prescription Processing [PSO LM BACKDOOR ORDERS] Complete Orders from OERR [PSO LMOE FINISH] --------------------------------------------------------------------------- A few changes have been made to the Pharmacy Backdoor options listed above to comply and facilitate the processing of controlled substance medication prescriptions: a) When viewing a Pending eRx Order the user will have the available a new hidden action called 'Un Accept eRx' (UA) which after answering a few prompts the record will be sent back to the eRx Holding Queue for further processing there, as shown below: ... Select Item(s): Next Screen// UA UA Select HOLD reason code: HOLD FOR RX EDIT// HRX HOLD FOR RX EDIT Comments (Optional): Wrong Patient associated with Rx This eRx will be Un-Accepted and sent back to the eRx Holding Queue. Confirm? N// YES Please wait... eRx successfully un-accepted and placed back on the eRx Holding Queue. Type to continue or '^' to exit: b) When viewing a digitally signed eRx pending order the first line of the scrollable area will display the text "Processing Digitally Signed eRx Order" in reverse video to indicate to the user the they are processing a prescription for a controlled substance medication. c) Also, for digitally signed eRx pending orders at the end of the scrollable area there will be a foot note that says: This prescription meets the requirements of the Drug Enforcement Administration (DEA) electronic prescribing for controlled substances rules (21 CFR Parts 1300,1304, 1306, & 1311). d) Digitally signed eRx pending orders cannot be edited. In order to edit any field on this type of pending orders they user would have to either Un-Accept the pending order, edit it in the eRx Holding Queue and then Re-Accept it; or finish the pending order and then edit the Active or Suspended prescription. e) A new hidden action called Jump to eRx (JE) was included in the list of hidden actions available for an eRx pending order or an eRx active prescription. When a user viewing a pending order or an active prescription types JE it will take them to the eRx Holding queue to the screen showing the corresponding eRx record. Once they quit out of eRx record they will return them back to pending order or active prescription. f) When a new CS eRx is finished and becomes an ACTIVE prescription it will display "Digitally Signed eRx Order" on the message bar right above the actions. g) The trailing document of the prescription label will have the "(DSIG)" to indicate that the prescription was digitally signed. h) The 30th piece of the ORC segment in the HL7 message sent over to OPAI (Outpatient Pharmacy Automated Interface) will contain "EL" for Digitally Signed eRx Controlled Substance prescriptions. 6. HPS Sustaintment issues --------------------------------------------------------------------------- The Inbound eRx JAVA application is a component of the PRE IEP program that provides the capability to receive inbound eRx's from an external provider. The JAVA application provides a user interface that allows end users to manage and monitor eRx processing from external sources. This patch resolves the incomplete users list displayed by the User Management screen in the Inbound eRx web-based application. Defect Tracking System Ticket(s) & Overview: ============================================ INC11772378 - Inbound eRX web application not displaying correctly INC18070242 - Inbound eRX web application not displaying correctly Problem: -------- The User Management screen allows Administrators to add new users to one or more sites (Station ID), enable users, disable users, modify user roles and existing user records by assigning them to one or more sites. This screen will only display for users with Administrator access. However, User Management screen is currently displaying limited number of users, not the entire list of users. Resolution: ---------- Refactored Java code in order to fix the User Management component of the Inbound eRx application. After the fix is implemented, complete list of users is displayed on the User Management screen. Patch Components ================ Files & Fields Associated: File Name (#) Field Name (#) New/Modified/Deleted ----------------- -------------------------------------- -------------------- ERX HOLDING QUEUE (#52.49) Modified DO NOT FILL (#10.5) Modified STATUS HISTORY sub-file (#19) Modified - UN-ACCEPTED ERX FLAG (#.04) New AUDIT LOG sub-file (#20) New - EDIT DATE/TIME (#.01) New - FIELD NAME (#.02) New - EDITED BY (#.03) New - NEW VALUE (#.04) New CONTROLLED SUBSTANCE INDICATOR (#95.1) New CS DIG SIGNATURE DIGEST METHOD (#95.2) New CS DIG SIGNATURE DIGEST VALUE (#95.3) New CS DIG SIGNATURE VALUE (#95.4) New CS DIG SIGNATURE X509 DATA (#95.5) New PRESCRIPTION (#52) ERX SIGNATURE STATUS (#312) New Protocols Associated: Protocol Name Type New/Modified/Deleted ------------- ------- -------------------- PSO ERX ACCEPT ERX Action Modified PSO ERX AUDIT LOG MENU Menu New PSO ERX AUDIT LOG SHOW/HIDE ERX VALUE Action New PSO ERX AUDIT LOG SORT BY DATE/TIME Action New PSO ERX AUDIT LOG SORT BY EDITED BY Action New PSO ERX AUDIT LOG SORT BY FIELD NAME Action New PSO ERX HIDDEN ACTIONS Menu Modified PSO ERX JUMP TO ERX Action New PSO ERX UN-ACCEPT Action New PSO ERX VIEW AUDIT LOG Action New PSO HIDDEN ACTIONS Menu Modified PSO HIDDEN ACTIONS #3 Menu Modified PSO PMP HIDDEN ACTIONS MENU #2 Menu Modified Templates Associated: Template Name Type File Name (#) New/Modified/Deleted ------------- ---- ------------- -------------------- PSO ERX AUDIT LOG List N/A New Test Sites: ========== VA Honolulu Regional Office Health Administration Center (Meds by Mail) Indianapolis, IN VA Medical Center Central Texas, Temple VA Medical Center Pharmacy Erie, PA VA Medical Center Software and Documentation Retrieval Instructions: ---------------------------------------------------- Patch PSO*7*617 is being released as a FORUM Patch 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 Documentation Title File Name -------------------------------------------------------------------------- Installation Guide - CS Inbound ePrescribing PSO_7_0_P617_IG.PDF (PSO*7.0*617) PSO_7_0_P617_IG.DOCX User Manual - CS Inbound ePrescribing PSO_7_0_P617_UM_1_2.PDF (PSO*7.0*617) PSO_7_0_P617_UM_1_2.DOCX PSO_7_0_P617_UM_31.PDF PSO_7_0_P617_UM_31.DOCX PSO_7_0_P617_UM_32.PDF PSO_7_0_P617_UM_32.DOCX PSO_7_0_P617_UM_41.PDF PSO_7_0_P617_UM_41.DOCX PSO_7_0_P617_UM_42.PDF PSO_7_0_P617_UM_42.DOCX PSO_7_0_P617_UM_51.PDF PSO_7_0_P617_UM_51.DOCX PSO_7_0_P617_UM_52.PDF PSO_7_0_P617_UM_52.DOCX PSO_7_0_P617_UM_6.PDF PSO_7_0_P617_UM_6.DOCX Technical Manual/Security Guide - Outpatient PSO_7_0_P617_TM.PDF Pharmacy V.7.0 PSO_7_0_P617_TM.DOCX Release Notes - CS Inbound ePrescribing PSO_7_0_P617_RN.PDF (PSO*7.0*617) PSO_7_0_P617_RN.DOCX 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 less than 5 minutes to install. 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*617) 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*617 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. 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 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*617 patch have been backed out, the second line of the Routines will no longer contain the designation of patch PSO*7.0*617 in the patch list section. Routine Information: ==================== The second line of each of these routines now looks like: ;;7.0;OUTPATIENT PHARMACY;**[Patch List]**;DEC 1997;Build 110 The checksums below are new checksums, and can be checked with CHECK1^XTSUMBLD. Routine Name: PSO617PI Before: n/a After: B4936072 **617** Routine Name: PSOCAN Before: B57127881 After: B57342199 **11,21,24,27,32,37,88,117,131, 185,253,251,375,379,390,413, 372,416,508,477,617** Routine Name: PSOCAN1 Before: B64816053 After: B65052176 **8,20,24,27,32,131,163,185, 238,372,442,508,477,617** Routine Name: PSOCAN3 Before: B73878473 After: B73489101 **15,24,27,32,36,94,88,117,131, 146,139,132,223,235,148,249, 225,324,251,375,379,372,540, 508,457,617** Routine Name: PSOCAN4 Before: B51143319 After: B51528354 **20,24,27,63,88,117,131,259, 268,225,358,385,391,508,617** Routine Name: PSOCMOPR Before: B51028555 After: B54050720 **33,52,617** Routine Name: PSODISP1 Before: B49194938 After: B52176319 **15,9,33,391,617** Routine Name: PSOERX Before:B135510353 After:B144901593 **467,527,508,551,567,591,581,617** Routine Name: PSOERX1 Before:B170801530 After: B1264803 **467,520,527,508,551,581,635,617** Routine Name: PSOERX1A Before:B175273948 After:B210939178 **467,527,508,551,581,617** Routine Name: PSOERX1B Before:B148682031 After:B159757583 **467,506,520,527,508,551,591, 606,581,617** Routine Name: PSOERX1C Before:B113785814 After:B114573841 **467,520,527,508,551,581,617** Routine Name: PSOERX1D Before:B217653722 After:B218498146 **581,617** Routine Name: PSOERX1F Before: n/a After:B156976934 **617** Routine Name: PSOERX1G Before: n/a After:B180972623 **617** Routine Name: PSOERXA0 Before: B33354450 After: B33174587 **467,586,617** Routine Name: PSOERXA1 Before:B191218900 After:B135954657 **467,520,508,551,581,617** Routine Name: PSOERXA3 Before: B38164072 After: B96572503 **467,508,617** Routine Name: PSOERXA5 Before: B71429258 After: B71430254 **508,581,631,617** Routine Name: PSOERXAU Before: n/a After: B42209769 **617** Routine Name: PSOERXC1 Before:B109912416 After:B116770859 **508,551,567,581,631,617** Routine Name: PSOERXD1 Before:B164705003 After:B165709901 **467,520,551,582,581,635,617** Routine Name: PSOERXD2 Before:B164315173 After:B184003696 **467,506,520,508,551,581,617** Routine Name: PSOERXEN Before: B16386315 After: B22187992 **508,581,617** Routine Name: PSOERXH1 Before: B36800437 After: B37438342 **467,527,508,581,617** Routine Name: PSOERXI1 Before:B156967276 After:B182379733 **581,617** Routine Name: PSOERXIE Before:B158461983 After:B160758654 **581,617** Routine Name: PSOERXO1 Before:B177621724 After:B177622161 **467,520,508,581,617** Routine Name: PSOERXOA Before: B77421182 After: B77421421 **581,617** Routine Name: PSOERXU1 Before:B157028111 After:B167891410 **467,520,508,551,565,581,617** Routine Name: PSOERXU2 Before: B61501050 After: B53578392 **508,598,581,631,617** Routine Name: PSOERXU3 Before:B187651757 After:B188287287 **508,591,606,581,617** Routine Name: PSOERXU4 Before: B72569032 After: B78849793 **520,508,551,581,635,617** Routine Name: PSOERXU6 Before:B120600986 After:B123957779 **508,551,581,631,617** Routine Name: PSOERXU7 Before: B44585380 After: B44861191 **581,617** Routine Name: PSOERXU8 Before: B10018931 After: B16282202 **581,617** Routine Name: PSOERXU9 Before: n/a After: B30267841 **617** Routine Name: PSOERXUT Before: n/a After: B87471861 **617** Routine Name: PSOERXX1 Before:B174429887 After:B173990318 **467,520,527,508,581,617** Routine Name: PSOHLDS4 Before: B16987762 After: B17192544 **156,255,279,385,505,617** Routine Name: PSOLLL2 Before: B16898415 After: B17164801 **120,138,141,161,200,391,617** Routine Name: PSON52 Before:B118986186 After:B123645958 **1,16,23,27,32,46,71,111,124, 117,131,139,157,143,219,148, 239,201,268,260,225,303,358, 251,387,379,390,391,313,408, 473,504,505,517,457,617** Routine Name: PSOOREDT Before: B96163817 After: B96619177 **4,20,27,37,57,46,78,102,104, 119,143,148,260,281,304,289, 298,379,377,391,313,427,411, 505,517,574,524,617** Routine Name: PSOORFI1 Before: B86566158 After: B92874767 **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** Routine Name: PSOORFI5 Before: B77628062 After: B79004074 **225,315,266,391,372,416,504, 505,557,617** Routine Name: PSOORNE6 Before: B56294478 After: B57081390 **46,103,117,156,210,488,505, 508,617** Routine Name: PSOORNEW Before:B124801369 After:B129961468 **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** Routine Name: PSORN52C Before: B68196793 After: B72268083 **1,7,11,27,46,75,87,100,111, 124,117,131,146,148,200,225, 251,387,379,391,617** Routine Name: PSOVER Before: B87933411 After: B88166634 **16,21,27,117,131,146,251,375, 387,379,391,372,416,597,617** Routine list of preceding patches: 52, 477, 524, 557, 586, 597, 631, 635 ============================================================================= User Information: Entered By : Date Entered : JUN 29, 2020 Completed By: Date Completed: NOV 19, 2021 Released By : Date Released : NOV 19, 2021 ============================================================================= Packman Mail Message: ===================== $END TXT