PSO*7.0*59 (3493)    BUILD (9.6)

Name Value
NAME PSO*7.0*59
DATE DISTRIBUTED 2001-03-07 00:00:00
PACKAGE FILE LINK OUTPATIENT PHARMACY
REQUIRED BUILD
  • PSO*7.0*7
    ACTION:   Don't install, leave global
  • PSO*7.0*32
    ACTION:   Don't install, leave global
  • PSO*7.0*39
    ACTION:   Don't install, leave global
TYPE SINGLE PACKAGE
ALPHA/BETA TESTING NO
DESCRIPTION OF ENHANCEMENTS
1) During the order entry process using Patient Prescription Processing
Outpatient Pharmacy when requested from Computerized Patient Record
System (CPRS). This problem only occurs when invalid data is found in the
PENDING OUTPATIENT ORDERS file (#52.41).
 
3) When renewing a prescription using Patient Prescription Processing
[PSO LM BACKDOOR ORDERS] option, it was observed by some sites (set for
auto suspend), that the renewed prescription is getting suspended to the
wrong date. The renewal process calculates the FILL DATE field (#22)
based on the NEXT POSSIBLE FILL field (#102) of PRESCRIPTION file (#52).
It also checks to see if a record exits in RX SUSPENSE file (#52.5)
[PSO LM BACKDOOR ORDERS] option, if the user opts to address more than
and its PRINTED field (#2) is set. For some reason (timing delay/system
problems), this field is not being set for CMOP drugs even when the drug
was released. In such situations the renewal process tends to set the FILL
DATE field (#22) to the LAST DISPENSED DATE field (#101) of PRESCRIPTION
file (#52). This patch ensures that, for these situations, if the
calculated FILL DATE field (#22) of PRESCRIPTION file (#52) is less than
the current date then it gets set to the current date unless a lesser date
than the current date is requested by the users.
one prescription at a time simultaneously, the word "Release" is being
displayed along with the routing type (Mail/Window) for each prescription
even though it is not released. It had picked up the release status of a
prior prescription. This is due to one of the variables not being killed.
This patch fixes this problem.
 
2) This patch corrects a problem of a refill request not being seen in
TRACK PACKAGE NATIONALLY YES
BUILD COMPONENTS
  • ENTRIES:
    • PSOHLNE2
      ACTION:   SEND TO SITE
      CHECKSUM:   B54522863
    • PSOORNE3
      ACTION:   SEND TO SITE
      CHECKSUM:   B66349836
    • PSORENW0
      ACTION:   SEND TO SITE
      CHECKSUM:   B56062118