$TXT Created by                MNTVBB.DOMAIN.EXT  (KIDS) on Friday, 02/10/23 at 14:18
=============================================================================
Run Date: MAY 04, 2023                     Designation: PSO*7*718
Package : PSO - OUTPATIENT PHARMACY           Priority: Mandatory
Version : 7       SEQ #593                      Status: Released
                  Compliance Date: JUN 04, 2023
=============================================================================

Associated patches: (v)PSO*7*651   <<= must be installed BEFORE `PSO*7*718'

Subject: INBOUND ERX FOR NON-CONTROLLED SUBSTANCES COMING THROUGH AS CONTROLLED 

Category: 
  - Routine

Description:
============

 This patch addresses the following issue:
  
 INBOUND ERX FOR NON-CONTROLLED SUBSTANCES COMING THROUGH AS CONTROLLED
  
  
 Associated ticket(s):
 =====================
  
 1.      INC25956349 - INBOUND ERX FOR NON-CONTROLLED SUBSTANCES COMING 
                       THROUGH AS CONTROLLED
  
 Associated NSR(s):
 ==================
 N/A
  
 Defect Tracking System Ticket(s) & Overview:
 ============================================
  
 1.      INC25956349 - INBOUND ERX FOR NON-CONTROLLED SUBSTANCES COMING 
                       THROUGH AS CONTROLLED
  
 Problem:
 --------
 Site is receiving several inbound eRx for non-controlled substance 
 medications that are designated as controlled substances in the inbound 
 eRx queue.  This is preventing us from processing these orders if the 
 community prescriber does not submit their DEA number.  The problem is 
 that the inbound eRX contains a digital signature, the provider does 
 not have a DEA# sent in the eRX message and the drug is not a controlled 
 drug.  This causes an error to be encountered when processing it in 
 option Complete Orders from eRx [PSO ERX FINISH]. The exception error is
 'eRx Provider does not have a valid DEA#.'
  
 Resolution:
 -----------
 Routine PSOERXUT is modified to not return an exception error when the eRX
 drug is not a controlled drug, the provider doesn't have a DEA#, and
 the eRX is digitally signed.
  
 Technical Resolution:
 ---------------------
 PSOERXUT is modified at line PRDRVAL+58^PSOERXUT to add the condition 
 ACTION="AC"
  
 Line PRDRVAL+58^PSOERXUT after the code change:
  . I ACTION="EP"!(ACTION="VP")!(ACTION="AC"),'VACSDRUG D  Q  ;p718 add 
 accept action
  
  
 Participating Test Sites:
 =========================
 West Palm Beach VAMC, West Palm Beach FL
 Albany VAMC, Albany NY
  
 Software and Documentation Retrieval Instructions:
 --------------------------------------------------
 The software for this patch is being released in a PackMan message.
  
 Patch Installation:
 =================== 
 Pre/Post Installation Overview:
  
 Pre-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.  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*718) 
  
         NOTE: Using <spacebar><enter> 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*718
          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 <enter> and take the default response 
               of "NO".
          v.   When prompted with, "Send mail to: Last name, First 
               Name", press <enter> to take default recipient. Add 
               any additional recipients.
          vi.  When prompted with "Select basket to send to: IN//", 
               press <enter> 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 build 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 build 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 build from the backup created.
  
 No data was modified by this patch installation and, therefore, no 
 rollback strategy is required.

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: PSOERXUT
    Before:B133962223   After:B134426845  **617,667,651,718**
 
Routine list of preceding patches: 651

=============================================================================
User Information:
Entered By  :                               Date Entered  : FEB 08, 2023
Completed By:                               Date Completed: MAY 03, 2023
Released By :                               Date Released : MAY 04, 2023
=============================================================================


Packman Mail Message:
=====================

$END TXT