$TXT Created by MALMROSE,CARY at DEVCUR.FO-SLC.MED.VA.GOV  (KIDS) on Monday, 09/29/03 at 13:12
=============================================================================
Run Date: OCT 07, 2003                     Designation: GMTS*2.7*64
Package : GMTS - HEALTH SUMMARY               Priority: Mandatory
Version : 2.7        SEQ #60                    Status: Released
                  Compliance Date: NOV 07, 2003
=============================================================================


Subject: TWEAK TO STANDARD REMOTE HEALTH SUMMARIES

Category: 
  - Other

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

  This patch addresses a problem reported by several sites when trying
  to access remote data using the Health Summary Remote Reports on the
  CPRS Reports Tab.  Some of the Remote Reports on some patients contain
  more data than can be returned within the timeout period set by
  the remote broker, which can range from 10-20 minutes.  Users become
  impatient and either CTRL-ALT-DEL out of CPRS or continually click
  on the report, causing more remote processes to begin, which further
  exacerbates the problem.  The network and the remote site becomes
  inundated with remote queries that does nothing but clog the system.
  
  We have determined that any report that contains Progress Notes has
  the potential to create this problem.  This patch is being released
  to add an occurrence limit of 50 to the Progress Notes Health Summary
  component for the following reports:
  
    REMOTE CLINICAL DATA (1Y)
    REMOTE CLINICAL DATA (3M)
    REMOTE CLINICAL DATA (4Y)
    REMOTE TEXT REPORTS (1Y)
    REMOTE TEXT REPORTS (3M)
  
  We have done some testing at some of the sites reporting this problem
  and found that setting this limit higher than 50 tends to overload the
  system.
  
  Users should be instructed to use the Progress Notes option(s) under
  Clinical Reports when there is a need to get more than 50 Notes.
  Progress Notes under Clinical Reports has greater flexibility to 
  return data within user specified time ranges and occurrence limits.
  
  TEST SITES FOR THIS PATCH:
  ==========================
  COATESVILLE, PA
  ILLIANA HCS
  HINES, IL
  LOMA LINDA, CA
  PRESCOTT, AZ
  WHITE RIVER JUNCTION, VT
  
  RELATED NOIS:
  =============
  LOM 0902-61043
  WRJ-0602-12508
  PRE-0602-63275
  LOM-0802-62088
  HIN-0802-41367
  DAN-0403-41032
  COA-1102-20982
  
  ROUTINE SUMMARY:
  ================
  The following is a list of the routine(s) included in this patch.  The
  second line of each of these routine(s) will look like:
  
      <tab>;;2.7;Health Summary;**[patch list]**;Oct 20, 1995
  
                             CHECK^XTSUMBLD results
  Routine name         Before Patch          After Patch         Patch List
  ============         ============          ===========         ==========
  GMTSY64                       N/A               475461             64
  
  INSTALLATION INSTRUCTIONS:
  ==========================
  This patch should be loaded during non-peak hours to minimize disruption
  to users.  Installation will take less than 1 minute.  Users may remain
  on the system.
   
  1.  Use the INSTALL/CHECK MESSAGE option on the PackMan menu.
   
  2.  Review your mapped set.  If any of the routines listed in the
      ROUTINE SUMMARY section are mapped, they should be removed
      from the mapped set at this time.
   
  3.  From the Kernel Installation and Distribution System Menu, select
      the Installation menu.
   
  4.  From this menu, you may elect to use the following options
      (when prompted for INSTALL NAME, enter GMTS*2.7*64):
          a.  Backup a Transport Global
          b.  Compare Transport Global to Current System
          c.  Verify Checksums in Transport Global
   
  5.  Use the Install Package(s) option and select the package GMTS*2.7*64.
   
  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 the mapped set once the installation has run to completion.
  
  9.  You can now use the appropriate utility to delete the Post-init
      routine GMTSY64.

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

Routine Name:
  - GMTSY64

  

Routine Checksum:
 

=============================================================================
User Information:
Entered By  : MALMROSE,CARY                 Date Entered  : MAY 05, 2003
Completed By: STERNHAGEN,SHERRIL            Date Completed: OCT 01, 2003
Released By : SCOTT,JEAN M                  Date Released : OCT 07, 2003
=============================================================================


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

$END TXT