$TXT Created by              . at MNTVBB.DOMAIN.EXT  (KIDS) on Thursday, 08/07/25 at 12:53
=============================================================================
Run Date: SEP 19, 2025                     Designation: PSO*7*800
Package : PSO - OUTPATIENT PHARMACY           Priority: EMERGENCY
Version : 7       SEQ #661                      Status: Released
                  Compliance Date: SEP 23, 2025
=============================================================================

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

Subject: ERRORS IN INBOUND ELECTRONIC PRESCRIPTIONS

Category: 
  - Routine

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

  
 This patch addresses one issue:
  
 Electronic Prescriptions (eRx's) are generating errors and failing to 
 file in VistA. This issue occurs because the eRx messages from the vendor 
 are being split into three messages in VistA, and the split messages do 
 not contain the parameters necessary from the original message to 
 interpret data on some of the XML key tags.  This patch addresses the 
 issue by maintaining the required header information in the split XML 
 message blocks to allow the data to be parsed correctly, allowing the eRx 
 orders to file into VistA without error.
  
 EHRM Impact Statement:
 ----------------------
 This patch should have no EHRM impact, and can be installed at all sites,
 including EHRM converted sites.
  
 Patch Components:
 -----------------
  
 Files & Fields Associated:
  
 File Name (Number)          Field Name (Number)       New/Modified/Deleted
 ------------------          -------------------       --------------------
 N/A
  
 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
 -----------                 ----                      --------------------
 N/A
  
 Protocols Associated:
  
 Protocol Name               New/Modified/Deleted
 -------------               --------------------
 N/A
  
 Security Keys Associated: 
  
 Security Key Name
 -----------------
 N/A
  
 Templates Associated:
  
 Template Name         Type    File Name (Number)      New/Modified/Deleted
 -------------         ----    ------------------      --------------------
 N/A
  
 Remote Procedures Associated:
  
 Remote Procedure Name       New/Modified/Deleted
 ---------------------       --------------------
 N/A 
  
 Parameter Definitions Associated:
  
 Parameter Name              New/Modified/Deleted
 --------------              --------------------
 N/A
  
 Additional Information:
 -----------------------
 N/A
  
 New Service Requests (NSRs):
 N/A
  
 Patient Safety Issues (PSIs):
 HITPS-12818 - INC39590213 
  
 Defect Tracking System Ticket(s) & Overview:
 ============================================
  
 INC39622229 - Error in VistA error trap with eRx.
 INC39566836 - (duplicate)
 INC39583133 - (duplicate)
 INC39587849 - (duplicate)
 INC39590213 - (duplicate)
  
 Problem:
 --------
 Inbound eRx messages are generating errors in VistA when parsing the XML 
 messages. The typical errors in the VistA error trap are:
 <ECODETRAP>STATCHK+12^XOBWLIB
 with the error message text:
 prefix 'xsi' can not be resolved to namespace URI while processing...
   
 Some XML tags in these inbound NewRx transactions contain xsi:type="..." 
 parameters present to clarify the tag.  Specific examples are the tags:
   <Pharmacy xsi:type="MandatoryPharmacy"> . . . /</Pharmacy>  and
   < Quantity xsi:type="Quantity"> . . . </Quantity>
 Those xsi:type parameters need information from the message header tag in 
 order to be processed.  Example:
 <Message xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
 That xmlns definition in the <Message...> tag provides the schema needed 
 to interpret the xsi:type information in the tags.
   
 When the VistA process importing these XML messages breaks the message 
 into three messages, the first message has the correct message header 
 information, but VistA is not maintaining that xmlns definition in the 
 message headers for the subsequent XML messages, causing the errors 
 trying to parse the tags in those messages that require the definition.
  
 Resolution:
 -----------
 This patch modifies code in ^PSOERXI1 to preserve the message parameters 
 from the first message in each order and make those parameters available 
 to the remaining message blocks for that order.  This allows each 
 complete eRx order to process completely and file successfully into the 
 eRx Holding Queue for normal processing. 
  
 Test Sites:
 -----------
 HAC/MBM - Meds by mail
 Las Vegas, Las Vegas NV
  
 Test Sites - SNOW Change Order #:
 ---------------------------------
 HAC/MBM - Meds by mail - CO# - CHG0645472 
 Las Vegas, - CO# - CHG0645488
  
  
  
 Software and Documentation Retrieval Instructions:
 --------------------------------------------------
 The software for this patch is being released in a PackMan message.
  
 Documentation updates are not included in this release.
  
 Patch Installation:
 -------------------
  
 Pre/Post Installation Overview:
 This patch is installed using typical PackMan procedures.  There are
 no unique pre installation or post installation steps required.
  
 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*800>)
  
         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*800
          iii. When prompted for the following, enter "R" for 
               Routines or "B" for Build.
  
      Select one of the following:
  
           B         Build (including Routines)
           R         Routines Only
  
 Backup Type: B//
  
          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.
  
  
 Post-Installation Instructions:
 There are no specific post-installation steps.
  
 Back-Out/Roll Back Plan:
 ------------------------
 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. If the patch was backed up for the build,
 from the Kernel Installation and Distribution System Menu, select the
 Installation Menu. Then select the Install Package(s) option and choose 
 the patch (PSO*7.0*800b) to install.
  
 The back-out plan is to restore the routines from the backup created.
  
 No data was modified by this patch installation and, therefore no 
 rollback strategy is required.
  
 Validation of Backout Procedure:
 ---------------------------------
 The Backout 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 two lines of the routine(s) contained in
 this patch using the option First Line Routine Print [XU FIRST LINE
 PRINT].  After 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 [800].

Routine Information:
====================
The second line of each of these routines now looks like:
 ;;7.0;OUTPATIENT PHARMACY;**[Patch List]**;DEC 1997;Build 1

The checksums below are new checksums, and
 can be checked with CHECK1^XTSUMBLD.

Routine Name: PSOERXI1
    Before:B112507414   After:B117310771  **581,617,692,706,700,743,746,
                                           783,770,800**
 
Routine list of preceding patches: 770

=============================================================================
User Information:
Entered By  :                               Date Entered  : JUL 30, 2025
Completed By:                               Date Completed: SEP 18, 2025
Released By :                               Date Released : SEP 19, 2025
=============================================================================


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

$END TXT