$TXT Created by                  at CLN1G1.AAC.DOMAIN.EXT  (KIDS) on Tuesday, 11/19/19 at 18:49
=============================================================================
Run Date: MAR 26, 2020                     Designation: VPR*1*18
Package : VPR - VIRTUAL PATIENT RECORD        Priority: Mandatory
Version : 1        SEQ #20                      Status: Released
                  Compliance Date: APR 26, 2020
=============================================================================

Associated patches: (v)VPR*1*4     <<= must be installed BEFORE `VPR*1*18'

Subject: MEDS DOMAIN SHOWING INCORRECT MED

Category: 
  - Routine

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

 This patch will resolve the following issues in the Virtual Patient 
 Record (VPR)
 package:
  
 1.      INC8143771 - Wrong medication displaying on Essential Med List 
 and JLV; OEL^PSOORRL API used incorrectly
  
 New Service Requests (NSRs):
 ----------------------------  
 N/A
  
 Patient Safety Issues (PSIs):
 -----------------------------
 N/A
  
 Defect Tracking System Ticket(s) & Overview:
 --------------------------------------------
 1. INC8143771 - Wrong medication displaying on Essential Med List and 
 JLV; OEL^PSOORRL API used incorrectly
  
 Problem 1:
 ----------
 The VPR [MEDS] Domain displays an incorrect drug for a pending Inpatient 
 Med package order if there is an IEN match in file #52.51. This is due 
 to an incorrect use of the OEL^PSOORRL API passing in the [PATIENT CLASS] 
 field in file #100 (Which is whether the patient was an
 inpatient/outpatient when the order was written). This causes the 
 inpatient medication IEN to get routed though the outpatient medication 
 logic, and if there is an IEN match the match is displayed instead of the 
 correct drug.  
  
 Resolution 1:
 -------------
 Routines VPRDPSOR and VPRDJ05 were modified to check for and use the 
 [PACKAGE] field in file #100 first and default to [PATIENT CLASS] if the 
 package is not INPATIENT MEDICATIONS or OUTPATIENT PHARMACY.
  
 Test Sites:
 -----------
 North Chicago
 Tuscaloosa
  
 Patch Installation:
 ===================
  
 Pre/Post Installation Overview:
 -------------------------------
 No special pre or post install steps needed, just install as normal.
  
 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 patch.
  
 2. Choose the INSTALL/CHECK MESSAGE PackMan option. 
  
 3. From the Kernel Installation and Distribution System Menu, select 
    the Installation Menu. From this menu, use the following option(s).
    When prompted for the INSTALL NAME enter the patch #(VPR*1.0*18):
   a. Backup a Transport Global - (Mandatory) This option will create a
      backup message of any routines exported with this patch. It will not 
      backup any other changes such as DDs or templates.
   b. Compare Transport Global to Current System - (Optional) This 
      option will (allow you to view all changes that will be made when
      this patch is installed. It compares all components of this patch
      routines, DDs, templates, etc.).
   c. Verify Checksums in Transport Global - (Optional) This option 
      will allow you to ensure the integrity of the routines that are in
      the transport global.
  
  4. From the Installation Menu, select the Install Package(s) option 
    and choose the patch to install.
  
  5. When prompted 'Want KIDS to INHIBIT LOGONs during the install? NO//',
    Enter "No".
  
  6. When prompted 'Want to DISABLE Scheduled Options, Menu Options, and
    Protocols? NO//', Enter "No".
  
  7. If prompted 'Delay Install (Minutes):  (0 - 60): 0//', respond 0.
  
 Post-Installation Instructions:
 -------------------------------
 No special post install steps, just install as normal.
  
 Back-out/Rollback Strategy:
 ---------------------------
 In the event of a catastrophic failure, the Facility CIO may make the 
 decision to back-out the patch.
  
 It is imperative that you have performed a backup of the routines included
 in this patch prior to installation.
  
 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.
  
 To verify the back-out completed successfully, ensure the checksum 
 matches the pre-patch checksum from the patch descriptions.

Routine Information:
====================
The second line of each of these routines now looks like:
 ;;1.0;VIRTUAL PATIENT RECORD;**[Patch List]**;Sep 01, 2011;Build 2

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

Routine Name: VPRDJ05
    Before: B76359424   After: B79505921  **2,18**
Routine Name: VPRDPSOR
    Before: B39578958   After: B42281306  **1,4,18**
 
Routine list of preceding patches: 2, 4

=============================================================================
User Information:
Entered By  :                               Date Entered  : NOV 15, 2019
Completed By:                               Date Completed: MAR 25, 2020
Released By :                               Date Released : MAR 26, 2020
=============================================================================


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

$END TXT