PSO*7.0*473 (10612)    BUILD (9.6)

Name Value
NAME PSO*7.0*473
DATE DISTRIBUTED 2017-07-07 00:00:00
PACKAGE FILE LINK OUTPATIENT PHARMACY
REQUIRED BUILD
  • PSO*7.0*408
    ACTION:   Don't install, leave global
TYPE SINGLE PACKAGE
ALPHA/BETA TESTING NO
DESCRIPTION OF ENHANCEMENTS
The patch addresses three (3) issues:
                   Fill Date issue 
 
 
 ROUTINE:
 =======
 Added new code to DT+1^PSON52 to check if the patient is not a clozapine 
 patient, # of Refills is zero and the Expiration Date is < Filled Date,
 then to set the expiration date.
 The Expiration Date will normally be set to (Fill Date + Day Supply). 
 However, it will be adjusted to comply with the following restrictions:
  - For controlled substances, the maximum Expiration Date allowable is 
 
    (Issue Date + 184 days)
  - For non-controlled substances, the maximum Expiration Date allowable 
    is (Issue Date + 366 days)
  - If the Expiration Date is less than the Fill Date, it will be set to 
    the same as the Fill Date
 Associated PSPO(s):
 ===================
 N/A
    
 Associated NSR(s):
 =================
 N/A 
  
 
 Participating Test Sites:
 ========================
 TBD
 
 Ticket Overview:
 ================
 1. I8924763FY16 - When a Maintenance Rx was created as the result of
    converting a Titration marked Rx instead of retaining the Expiration Date
    from the Titration Rx it was wrongly being assigned a new Expiration
    Date.
 Associated CA ticket(s):
 
 Problem:
 =======
 When using the Patient Prescription Processing [PSO LM BACKDOOR] option
 and using the hidden action Convert Titration Rx (TR) to create a new
 Maintenance dose prescription from a Titration Rx the user noticed that the
 Expiration Date associated with the new Maintenance Rx was calculated 366
 days in the future instead of being assigned the exact same Expiration Data
 from the Titration Rx.
  
 ========================
 Resolution:
 =========
 Changed the routine PSON52 responsible for creating the new Maintenance Rx
 to overwrite the calculated Expiration Date with the Expiration Date from
 the original Titration Rx.
 
 ROUTINE:
 =======
 Added code at DT+1^PSON52 to set the array variable PSOX("STOP DATE") with 
 the Titration Rx Expiration, if a Titration Rx To Maintenance Rx conversion
 1. I8924763FY16 - Expiration date changed for prescription marked as a
 is taking place.
 
 
 2. I9667491FY16 -The site would like to use the PSO BATCH BARCODE option to
    renew prescriptions. When this is attempted the renewal appears to
    succeed and there is a prompt to edit the renewal. If yes is selected the
    session will crash with an undefined variable (hard error).
 
 Problem:
 =======
                   titration script.
 When using the Barcode Batch Prescription Entry [PSO BATCH BARCODE] option
 for renewals the users received a hard error and were logged out of the
 system when they answered YES to the "Edit renewed Rx ?" prompt (before
 accepting it).
  
 Resolution:
 =========
 The root cause of this problem was due to the fact that the PSOACT variable
 that controls which action a specific user can perform on an order, based on
 the user security keys as well as whether the order was digitally signed or
 2. I9667491FY16 - Renewing a script using PSO BATCH BARCODE causes crash
 not. The routine PSOBBC was modified to initialize the PSOACT variable,
 which will prevent the hard error.
  
 ROUTINE:
 =======
 Added code at NEW+9^PSOBBC to initialized the PSOACT variable according to 
 the type of order, user's security keys and system parameters.
 
 
 3. We would like to request for assistance in the identification and 
    
    deployment of the VistA patch used at VHA station #663 (Seattle
    division) that enables pharmacy staff resolves the Fill Date issue and
    generates the error message described below
 
    "The earliest fill date allowed is determined by the Issue Date, the
    Fill Date cannot be before the Issue Date or past the Expiration
    Date. Both the month and day are required."
 
 Problem:
 =======
 3. R8247671FY16 - VistA patch used at VHA station #663 that resolves the 
 When using the speed renewal hidden action in Patient Prescription 
 Processing [PSO LM BACKDOOR] option, it was reported that when the # of 
 refills is zero, there are times the expiration date is set to a date
 earlier than the filled date.
  
 Resolution:
 ==========
 In a situation where the # of refill is zero, patient is not a clozapine 
 patient and the expiration date is < fill date, added new logic to 
 calculate the most appropriate expiration date.
TRACK PACKAGE NATIONALLY YES
XPI1 NO
XPO1 NO
XPZ1 NO
SEQ# 405
BUILD COMPONENTS
  • ENTRIES:
    • PSOBBC
      ACTION:   SEND TO SITE
      CHECKSUM:   B109320592
    • PSON52
      ACTION:   SEND TO SITE
      CHECKSUM:   B99620667