PSO*7.0*486 (10586)    BUILD (9.6)

Name Value
NAME PSO*7.0*486
DATE DISTRIBUTED 2017-07-03 00:00:00
PACKAGE FILE LINK OUTPATIENT PHARMACY
REQUIRED BUILD
  • PSO*7.0*444
    ACTION:   Don't install, leave global
  • PSO*7.0*450
    ACTION:   Don't install, leave global
TYPE SINGLE PACKAGE
ALPHA/BETA TESTING NO
DESCRIPTION OF ENHANCEMENTS
The patch addresses two (3) issues:
   Outpatient Rx, the Rx Expiration Date is reset to an incorrect date.
   Rx #100001973 STERI-STRIPS^401962 will be discontinued after the
   acceptance of the new order.  
  
   Now doing allergy checks.  Please wait...
 
   Now processing Clinical Reminder Order Checks. Please wait ...
   Now Processing Enhanced Order Checks!  Please wait...
    
    
   Press return to continue: ^ <<< [This up (^) character causes the problem]    
 
 
   Rx # 100001977         06/26/17
   TESTATNM,CLETUS               #8
   APPLY 1 BANDAGE OVER AFFECTED AREA THREE TIMES A DAY
 
   ACER BANDAGE
   ROCHA,MARCELO            ROCHA,MARCELO
   # of Refills: 0
  
          SC Percent: 30%
3. R15046343FY17 - A drug with same tab strength did NOT discontinue after
        Disabilities: 
 
   Was treatment for Service Connected condition? NO// 
   
   Are you sure you want to Accept this Order? NO// YES
   ...
  
Resolution:
--------
Changed PSOORNEW routine to initialize the array variable PSORX("DFLG") 
   duplicate (new order) processing. This created a duplicate active order in
right before the call to file the new order and subsequent DC of the existing
duplicate order. This initialization will cause the code responsible for 
discontinuing the existing order (DCORD^PSONEW2) to perform the DCing of the
existing order without skipping it, like it was doing before this fix.
   the patient's profile.
 
Associated NSR(s):
=================
N/A
 
 
Associated CA SDM Ticket(s):
============================
1. R10380204FY16 - When entering a new outpatient Rx, the Rx is Deleted on
   editing the dosage and entering an up (^) character to exit.
2. R9361753FY16 - When editing/modifying the Issue Date or Fill Date of an
   Outpatient Rx, the Rx expires on an incorrect date.
3. R15046343FY17 - A drug with same tab strength did NOT discontinue after
   duplicate (new order) processing.
 
Participating Test Sites:
1. R10380204FY16 - when entering a new Rx using the Patient Prescription 
========================
OKLAHOMA CITY
TAMPA BAY
 
Ticket Overview:
===============
1. R10380204FY16- When entering a new RX using LM BACKDOOR ORDERS, the RX
   is Deleted on editing the dosage and entering an up (^) character to 
   exit. 
 
   Processing [PSO LM BACKDOOR ORDERS], and then editing the dosage and 
Problem:
--------
When user enters a new Outpatient prescription and answers "NO" to the prompt
"Is this correct? YES//" and then user edits the dosage and enter an up (^)
character to exit the prompt "Dosage:" and accepts Rx then new Rx will be
deleted. 
 
Resolution:
--------
Correct routine code ASK^PSOORED5 to call line tag EXE instead EX to escape 
   entering an up (^) character to exit, the Rx will be deleted as user
killing required data before saving.
 
  
2. R9361753FY16 - Outpatient Rx expired on an incorrect date, when Issue Date
   or Fill Date is modified.
 
Problem:
--------
When editing/modifying the Issue Date or Fill Date of an Outpatient Rx using
the backdoor pharmacy, the Rx expiration date is reset to an incorrect Date.
   accepts the Rx.
  
Resolution:
--------
Corrected A^PSOEXDT to set up expiration date for prescription without
refills not less than 30 days after issue date unless it is a Clozapine
prescription. In addition, if the newly calculated Rx Expiration Date is
earlier than the Rx Fill Date the Rx Expiration Date will be re-calculated
to be the Rx Fill Date plus the Days Supply value.
 
  
 
3. R15046343FY17 - A drug with same tab strength did NOT discontinue after
   duplicate (new order) processing. This created a duplicate active order
   in patient's profile.
  
Problem: 
--------
When using the options Patient Prescription Processing [PSO LM BACKDOOR
ORDERS] or Complete Orders from OERR [PSO LMOE FINISH] for finishing 
pending orders there was a scenario where duplicate active orders could
remain on the patient profile as ACTIVE. The screen capture example below
2. R9361753FY16 - Using the Patient Prescription Processing [PSO LM BACKDOOR
shows the prompt "Press return to continue:" where if the user entered an
up (^) character at this prompt, the duplicate existing order would not be
DC'd.
 
   ...
   --------------------------------------------------------------------------
   Duplicate Drug in Local Rx:
 
                    Rx: 100001973
                  Drug: ACER BANDAGE
   ORDERS] option, when users edit/modify the Issue Date or Fill Date of an
                   SIG: APPLY 1 BANDAGE OVER AFFECTED AREA THREE TIMES A DAY
                   QTY: 9                      Refills remaining: 1
              Provider: ROCHA,MARCELO                     Issued: 06/25/17
                Status: Active                       Last filled: 06/26/17
     Processing Status: Not released locally (Window)
                                                     Days Supply: 9
   --------------------------------------------------------------------------
 
   Discontinue RX # 100001973 STERI-STRIPS Y/N? YES  
  
TRACK PACKAGE NATIONALLY YES
XPI1 NO
XPO1 NO
XPZ1 NO
SEQ# 403
BUILD COMPONENTS
  • ENTRIES:
    • PSOEXDT
      ACTION:   SEND TO SITE
      CHECKSUM:   B6433054
    • PSOORED5
      ACTION:   SEND TO SITE
      CHECKSUM:   B61813792
    • PSOORNEW
      ACTION:   SEND TO SITE
      CHECKSUM:   B98142553