LR*5.2*343 (6831)    BUILD (9.6)

Name Value
NAME LR*5.2*343
DATE DISTRIBUTED 2006-06-20 00:00:00
PACKAGE FILE LINK LAB SERVICE
REQUIRED BUILD
  • OR*3.0*142
    ACTION:   Don't install, leave global
  • OR*3.0*141
    ACTION:   Don't install, leave global
TYPE SINGLE PACKAGE
DESCRIPTION OF ENHANCEMENTS
Blood Bank Team Coordination
 
N/A
 
 
Associated PSI:
===============
PSI-05-068 
 
 
Test Sites
==========
All of the above changes have been reviewed by the VISTA Blood Bank 
DURHAM, NC -VAMC (Large site)
NORTHERN CALIFORNIA HCS (Large site) 
 
 
 
ROUTINE SUMMARY
===============
  The following routines are included in this patch.  The second line
  of each of these routines now looks like:
      <tab> ;; 5.2;LAB SERVICE;<patch list>;Sep 27, 1994
Developer and found to have no impact on the VISTA BLOOD BANK SOFTWARE 
 
                  Checksum       Checksum
 Routine Name     Before Patch   After Patch    Patch List
     LR343        N/A            12851791       343
     LR7OEVNT     5021306        deleted by KIDS
 
     Routines deleted by KIDS: LR343,LR70EVNT
     List of preceding patches: n/a
     Sites should use CHECK^XTSUMBLD to verify checksums.
 
control functions.
 
PROTOCOLS
    LR7O MOVEMENT EVENT  (deleted)
    LR7O MOVEMENT EVENT TASK  (deleted)
 
 
DATA DICTIONARIES
    LABORATORY SITE file (#69.9)
        CANCEL ON ADMIT field (#150.3)  (deleted)
        CANCEL ON DISCHARGE field (#150.4)  (deleted)
 
        CANCEL ON SPECIALTY TRANSFER field (#150.5)  (deleted)
 
 
INSTALLATION INSTRUCTIONS
=========================
 
  The install time for this patch is approximately 6 minutes.
  Suggested time to install: non-peak requirement hours.
  This patch can be installed when Laboratory users are on the system.
 
RISK ANALYSIS: Changes made by patch LR*5.2*343 have no effect on Blood 
 
                     I  M  P  O  R  T  A  N  T
                   =============================
                 THIS INSTALLATION MUST BE QUEUED
 
 
  NOTE: Kernel patches must be current on the target system to avoid
        problems loading and/or installing this patch.
 
      Patch installation needs to be coordinated with the Laboratory
Bank software functionality, therefore RISK is none.
      Information Manager (LIM/ADPAC).
 
 
  1.  Use the 'INSTALL/CHECK MESSAGE' option of the PackMan menu.  This
      option will load the KIDS patch onto your system.
 
  2.  On the 'Kernel Installation & Distribution System' Menu (KIDS),
      select the 'Installation' menu.
 
  3.  Use the 'Verify Checksum in Transport Global' option and verify
 
      that all routines have the correct checksums.
 
  4.  On the KIDS menu, under the 'Installation' menu, use the following
      options:
        Print Transport Global
        Compare Transport Global to Current System
        Backup a Transport Global
 
  5.  Use the 'Install Package(s)' option under the 'Installation' menu
      and select the package 'LR*5.2*343*'
EFFECT ON BLOOD BANK FUNCTIONAL REQUIREMENTS: Patch LR*5.2*343 does not 
 
      If prompted "Want KIDS to Rebuild Menu Trees Upon Completion of
      Install?" choose "NO".  Note: Responding "Yes" to the prompt for
      rebuilding menu trees can significantly increase install time.
 
      If prompted "Want KIDS to INHIBIT LOGONs during the install?"
      choose "NO".
 
      If prompted "Want to DISABLE Scheduled Options, Menu Options, and
      Protocols? YES//" choose "NO" unless the site has additional local
alter or modify any software design safeguards or safety critical 
      laboratory options that should be disabled during install.
 
  6.  When prompted for the DEVICE, enter "Q" to queue the build.  If you
      do not queue the installation KIDS will abort the install.  When
      you try to restart the install you may encounter an <UNDEF> error
      due to a bug in KIDS.  If this happens you will need to use FileMan
      to modify the INSTALL file (#9.7) for entry LR*5.2*343 which 
      currently has the status of "Start of Install" and set its' STATUS 
      field to "Install Completed".  Reload the transport global and 
      install the patch again. 
============================
elements functions.
 
  7.  Check your system for errors which may have occurred during the 
      time this patch was installed.  If the PROTOCOL DGPM MOVEMENT 
      EVENTS was called during this patch installation, system errors 
      (such as "Can't return to source" for routine LR7OEVNT) may have 
      been generated.  If so, those patient movements will have to be re-
      created. 
 
 
INSTALLATION EXAMPLE
 
====================
 
Select Installation Option:  Install Package(s)
Select INSTALL NAME:    LR*5.2*343     Loaded from Distribution  
10/20/05@12:39:58
     => LR343 KIDS  ;Created on Oct 20, 2005@11:59:59
 
This Distribution was loaded on Oct 20, 2005@12:39:58 with header of 
   LR343 KIDS  ;Created on Oct 20, 2005@11:59:59
   It consisted of the following Install(s):
POTENTIAL IMPACT ON SITES: This patch contains changes to 0 routines and 
     LR*5.2*343
Checking Install for Package LR*5.2*343
Will first run the Environment Check Routine, LR343
 
                Environment is okay 
 
Install Questions for LR*5.2*343
 
Want KIDS to INHIBIT LOGONs during the install? NO// 
 
1 file identified in Veterans Health Administration (VHA) Directive 
Enter the Device you want to print the Install messages.
You can queue the install by enter a 'Q' at the device prompt.
Enter a '^' to abort the install.
 
DEVICE: HOME// QUEUE TO PRINT ON
DEVICE: HOME// P-MAIN
 
Request Start Time: Oct 20, 2005@12:42:41//   (OCT 20, 2005@12:42:41)
Install Queued!
 
2004-058, group B listing. The changes have no effect on Blood Bank 
 
 
Sample Installation Output
==========================
 
Install Started for LR*5.2*343 : 
       Oct 20, 2005@12:42:42
 
Build Distribution Date: Oct 20, 2005
 
functionality or medical device control functions. There is no adverse 
 Installing Routines:...
       Oct 20, 2005@12:42:42
 
 Running Pre-Install Routine: PRE^LR343.
 
       Pre install started at Oct 20, 2005@12:42:42
 
      Sent install started alert to mail group G.LMI
 
      Setting DISABLE and ACTION fields for Protocols
potential to sites.
 
            No actions required for pre install
 
      Pre install completed at Oct 20, 2005@12:47:42
 
 Installing PACKAGE COMPONENTS: 
 
 Installing PROTOCOL...
               Oct 20, 2005@12:47:42
 
 
 Running Post-Install Routine: POST^LR343.
 
       Post install started at Oct 20, 2005@12:47:42
 
            File #69.9 field data update started
 
           File #69.9 field data deletion finished
 
  Post install completed at Oct 20, 2005@12:47:42
 
VALIDATION REQUIREMENTS BY OPTION: 
     Sending install completion alert to mail group G.LMI
 
 Updating Routine file......
 
 Updating KIDS files.......
 
 LR*5.2*343 Installed. 
               Oct 20, 2005@12:47:42
 
 Install Message sent
There are no validation requirements for this patch.
 
 
 
Sample MailMan Message
======================
Pre install started at Oct 20, 2005@12:48:15
Sent install started alert to mail group G.LMI
Setting DISABLE and ACTION fields for Protocols
No actions required for pre install
Pre install completed at Oct 20, 2005@12:48:55
VISTA Laboratory Package patch LR*5.2*343 contains changes to software 
 
Post install started at Oct 20, 2005@12:53:59
File #69.9 field data update started
File #69.9 field data deletion finished
Post install completed at Oct 20, 2005@12:54:45
Sending install completion alert to mail group G.LMI
MINIMAL TEST CASE SCENARIOS BY OPTION, INCLUSIVE OF ALL CONTROL FUNCTIONS:
There are no test case scenarios for this patch.
************************************************************************
 
Remove the LABORATORY package's rules for managing laboratory order 
auto-discontinuance on admission, transfer, or discharge events and let 
the existing rules in the OERR (ORDER ENTRY RESULTS REPORTING) package 
handle the order auto-discontinuance process.
 
controlled by VHA DIRECTIVE 2004-058, titled VISTA BLOOD BANK SOFTWARE. 
The LABORATORY package's process that is used to decide if an order 
should be discontinued when a patient move event is triggered will be 
disabled.  This business rule is already being handled by the OERR 
package and the Lab's business rules do not perform all of the needed 
checks that the OERR package performs.  For example, the Lab's process 
does not check that a new movement is actually tied to the current 
admission.  An edit of a patient movement can result in erroneous auto 
discontinue of a patient's laboratory orders.  OERR also provides checks 
in the software to establish whether the patient event is new or an edit 
to an existing event.
Changes include: 
 
The Lab's process has caused erroneous auto discontinuance of laboratory 
orders because it does not check if a new movement is actually tied to 
the patient's current admission.  In the case outlined by the Patient 
Safety Issue (PSI) report it appeared that a user deleted and re-entered 
a movement for a prior admission to make a correction.  Since it was a 
new movement the Lab code executed and the orders were discontinued.  
This problem would especially impact sites with patients that are 
transferred from the acute hospital to the nursing home.
 
 File #69.9 (Laboratory Site)
 
 
Technical Description
=====================
When the DGPM MOVEMENT EVENTS of the PROTOCOL file (#101) is triggered 
the LR7O MOVEMENT EVENT protocol may be called (if it is an item of the 
DGPM MOVEMENT EVENTS protocol).  In this situation the business rule 
processing in the LABORATORY package fails to make all of the needed 
checks to properly determine if the order should be discontinued.  If 
Lab's logic discontinues the order there will be no order for OERR to 
    Field #150.3 (CANCEL ON ADMIT) - Removed
apply its more detailed set of business rules against when the OERR code 
is called from the patient movement event.
 
Lab will no longer perform any package-level checks for order 
auto-discontinuance based on patient movements.  These checks will be 
performed by the OERR package.  This change is accomplished by:
 
Deletion of PROTOCOL file (#101) entries:
         LR7O MOVEMENT EVENT and LR7O MOVEMENT EVENT TASK
Deletion of routine LR7OEVNT
    Field #150.4 (CANCEL ON DISCHARGE) - Removed
Deletion of the following Data Dictionary for LABORATORY SITE file 
(#69.9):
    CANCEL ON ADMIT field (#150.3)
    CANCEL ON DISCHARGE field (#150.4)
    CANCEL ON SPECIALTY TRANSFER field (#150.5)
 
 
 
New Service Request:
====================
    Field #150.5 (CANCEL ON SPECIALTY TRANSFER) - Removed
#20050802 -- Remove Lab Package Options to DC Order on Patient Movement
 
 
Associated Remedy:
==================
HD0000000104211
 
 
Associated E3R:
===============
TRACK PACKAGE NATIONALLY YES
SEQ# 274
BUILD COMPONENTS
  • ENTRIES:
    • LR7O MOVEMENT EVENT
      ACTION:   DELETE AT SITE
    • LR7O MOVEMENT EVENT TASK
      ACTION:   DELETE AT SITE
  • ENTRIES:
    • LR7OEVNT
      ACTION:   DELETE AT SITE
ENVIRONMENT CHECK ROUTINE LR343
DELETE ENV ROUTINE Yes
POST-INSTALL ROUTINE POST^LR343
DELETE POST-INIT ROUTINE Yes
PRE-INSTALL ROUTINE PRE^LR343
DELETE PRE-INIT ROUTINE Yes