$TXT Created by WHITE,ELAINE at INPVAA.FO-BIRM.MED.VA.GOV  (KIDS) on Friday, 01/03/03 at 12:10
=============================================================================
Run Date: JAN 14, 2003                     Designation: PSO*7*124
Package : PSO - OUTPATIENT PHARMACY           Priority: EMERGENCY
Version : 7       SEQ #115                       Status: Released
                  Compliance Date: JAN 16, 2003
=============================================================================

Associated patches: (v)PSO*7*82    <<= must be installed BEFORE `PSO*7*124'
                    (v)PSO*7*94    <<= must be installed BEFORE `PSO*7*124'
                    (v)PSO*7*103   <<= must be installed BEFORE `PSO*7*124'
                    (v)PSO*7*111   <<= must be installed BEFORE `PSO*7*124'

Subject: PRESCRIPTION EXPIRATION DATE MINIMUM OF 30 DAYS FROM ISSUE DATE W/O REFILLS 

Category: 
  - Enhancement ()
  - Routine

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

  
 1. Currently, if a non-controlled substance prescription is entered with
    a day supply less than 5 days and there are no refills, the expiration
    date defaults to 5 days from the issue date.  If a controlled substance
    prescription is entered with a day supply less than 5 days without
    refills, the expiration date is the Issue Date plus the Days Supply.
    The primary problem is that when these prescriptions were being
    transmitted to the CMOPs and they were behind on dispensing, the
    prescriptions were being rejected because the prescriptions had
    already expired. The default of 5 is being changed to 30 to
    accommodate the CMOPs and to allow the patients to receive their
    medications in a timely manner. Prescriptions will no longer expire
    before 30 days elapses from the Issue Date when the day supply is
    less than 30 days and there are no refills.  If a minimum of 1 refill
    is entered the one year/six month rule still applies.
  
  
 2. This patch also includes a correction to initialize the line counter
    for the "SIG1" entries in the PRESCRIPTION file (#52). Before this fix,
    the count could be incorrect sometimes which could cause problems for
    external interfaces.
  
  
 3. This patch corrects a problem that caused a null subscript error when 
    attempting to access the MEDS tab in the Computerized Patient Record 
    System (CPRS). This would happen if records were being created in the 
    PENDING OUTPATIENT ORDERS file (#52.41) and an attempt was made to pull
    up the patient's medications in CPRS at the same moment.
  
  Associated NOISs:
  =================
  MAR-0802-22717
  HUN-0402-21491
  BOI-0402-50716
  SBY-0102-30749
  MAC-1201-62539 
  
  
  
  
  Test Sites:
  ===========
  ASHEVILLE, NC               
  BOISE, ID                    
  MADISON, WI                  
  OKLAHOMA CITY, OK
  SALISBURY, NC
  TOMAH, WI
  
  
  
  
  Routine Summary:
  ================
  
  The second line now reads as follows:
  
     <TAB>;;7.0;OUTPATIENT PHARMACY;**[patch list]**;DEC 1997
  
  
  CHECK^XTSUMBLD results:
  
  Routine      Before Patch   After Patch   Patch List
  =============================================================
  PSODIR2      9909847        9738694       3,9,26,46,124
  PSOHLNEW     37781188       37714103      1,7,15,46,71,98,111,124 
  PSON52       22739842       22609662      1,16,23,27,32,46,71,111,124
  PSONEW2      12666639       12533330      32,37,46,71,94,124
  PSOORNE3     35754034       35602769      11,9,39,59,46,103,124
  PSOORRL      25294443       25945107      4,20,9,34,54,82,124
  PSORN52C     24512686       24531525      1,7,11,27,46,75,87,100,111,124
  
  
  
  Installation Instructions:
  ==========================
  Before installing this patch, use List Tasks [XUTM INQ] option on the
  Taskman Management [XUTM MGR] menu to list currently running
  tasks. Do not install this patch while Outpatient Pharmacy users are
  using the software. Installation will take no longer than 5 minutes.
  There are no scheduling restrictions or recommendations.
  
  
   1. Use the INSTALL/CHECK MESSAGE option on the PackMan menu.
  
   2. Review your mapped set. If the routines are mapped, they should
      be removed from the mapped set at this time.
  
   3. From the Kernel Installation & Distribution System menu, select
      the Installation menu.
  
   4. From this menu, you may select to use the following options:
      (when prompted for INSTALL NAME, enter PSO*7.0*124)
  
     a. Backup a Transport Global - this option will create a backup
        message of any routines exported with the patch. It will NOT
        backup any other changes such as DDs or templates.
  
     b. Compare Transport Global to Current System - this option will
        allow you to view all changes that will be made when the patch
        is installed. It compares all components of the patch (routines,
        DDs, templates, etc.).
  
     c. Verify Checksums in Transport Global - this option will ensure
        the integrity of the routines that are in the transport global.
  
   5. Use the Install Package(s) option and select the package PSO*7.0*124.
  
   6. When Prompted "Want KIDS to INHIBIT LOGONs during the install?
      YES//" respond NO.
  
   7. When Prompted "Want to DISABLE Scheduled Options, Menu Options, and
      Protocols? YES//" respond NO.
  
   8. If Routines were unmapped as part of step 2, they should be returned
      to completion.

Routine Information:
====================

Routine Name:
  - PSORN52C


Routine Checksum:

Routine Name:
  - PSON52


Routine Checksum:

Routine Name:
  - PSODIR2


Routine Checksum:

Routine Name:
  - PSONEW2


Routine Checksum:

Routine Name:
  - PSOORRL


Routine Checksum:

Routine Name:
  - PSOHLNEW


Routine Checksum:

Routine Name:
  - PSOORNE3


Routine Checksum:

=============================================================================
User Information:                               
Entered By  : RUZBACKI,RON T                Date Entered : OCT 09, 2002
Completed By: DAVIS,DOUG                    Date Completed: JAN 13, 2003
Released By : LESIEUR,SHIRLEY               Date Released : JAN 14, 2003
=============================================================================


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

$END TXT