PSO*7.0*119 (4876)    BUILD (9.6)

Name Value
NAME PSO*7.0*119
DATE DISTRIBUTED 2003-06-06 00:00:00
PACKAGE FILE LINK OUTPATIENT PHARMACY
REQUIRED BUILD
  • PSO*7.0*82
    ACTION:   Don't install, leave global
  • PSO*7.0*104
    ACTION:   Don't install, leave global
TYPE SINGLE PACKAGE
DESCRIPTION OF ENHANCEMENTS
1. This patch contains a post-install job, which will correct a status
 
   For deleted Outpatient Pharmacy V. 7.0 orders, the post-install 
   job will change CPRS V. 1.0 orders with an active status to a status of
   deleted and will also change the stop date in CPRS V. 1.0 to the date
   deleted if the CPRS V. 1.0 status is Discontinued by Provider.
 
2. This patch also corrects the problem of an extra delimiter being
   stored in the PRESCRIPTION file (#52) if an up-arrow (^) was entered
   for the LOT# field (#24) when editing a prescription. A symptom of this
   problem is a null subscript error when trying to access the DIVISION
   mismatch between Outpatient Pharmacy V. 7.0 orders which have been
   field (#20) of the PRESCRIPTION file (#52).
 
   The post-install job will look for any entries with a null division and
   if the positions of the date fields appear to be shifted, it will
   remove the extra delimiter from the PRESCRIPTION file (#52).
 
    
   Upon completion of the post-install job a MailMan message will be sent
   to the patch installer with a subject of "Subj: Outpatient/CPRS Status
   clean-up". The message will indicate how many mismatched statuses were
   deleted and the corresponding orders in the Computerized Patient Record
   corrected and how many prescriptions with missing divisions were
   corrected.
 
    
 3. During the building of the Patient Profile through the Patient 
    Prescription Processing [PSO LM BACKDOOR] option, one of the 
    criteria for forcing the Status to SUSPENDED of prescriptions 
    that had an entry in the RX SUSPENSE file (#52.5) was at times
    found to be incorrect. If the entry in the RX SUSPENSE file
    (#52.5) was flagged as not printed, the software would force the
   System (CPRS) V. 1.0. The initial problem could have occurred if the
    prescription status to SUSPENDED. After this patch is installed,
    the software will also check if the prescription has already been
    transmitted to Consolidated Mail Outpatient Pharmacy (CMOP) V. 2.0
    system, and if so, the status will not be changed.
 
4. When trying to edit a prescription, and the edit is not allowed 
   because either the order or patient is locked by another user, the 
   message indicating that the order or patient is locked will not always 
   contain the person's name that has the lock. This patch corrects the 
   problem.
   Outpatient Pharmacy V. 7.0 package mistakenly sent an "active" message
 
5. When the user edited a prescription in such a way that caused a new
   prescription to be created, the new prescription was not being 
   displayed in the Bingo Board. This patch corrects the problem.
   The prescription number from the previous edit could be associated to
   the next patient's list of prescriptions to be listed on the Bingo
   Board.  This patch also corrects this problem.
   to CPRS V. 1.0 on an old order, making it active in CPRS V. 1.0 when it
   should be Discontinued, Expired, or Canceled. Patch PSO*7*86 updated
   the status in CPRS V. 1.0 for orders that were Canceled or
   Discontinued.
TRACK PACKAGE NATIONALLY YES
BUILD COMPONENTS
  • ENTRIES:
    • PSOBUILD
      ACTION:   SEND TO SITE
      CHECKSUM:   B33444335
    • PSOELPS2
      ACTION:   SEND TO SITE
      CHECKSUM:   B39367755
    • PSOOREDT
      ACTION:   SEND TO SITE
      CHECKSUM:   B56836092
POST-INSTALL ROUTINE PSOELPS2