SR*3.0*178 (9739)    BUILD (9.6)

Name Value
NAME SR*3.0*178
DATE DISTRIBUTED 2014-03-06 00:00:00
PACKAGE FILE LINK SURGERY
REQUIRED BUILD
  • SR*3.0*174
    ACTION:   Don't install, remove global
  • SR*3.0*109
    ACTION:   Don't install, remove global
TYPE SINGLE PACKAGE
ALPHA/BETA TESTING NO
DESCRIPTION OF ENHANCEMENTS
  This patch will correct the following issues currently occurring in
  Next, the FIELD field (#2) for the ATTENDING CODE entry of the Surgery
  Interface Parameter file (#133.2) points to the ATTENDING CODE field
  (#.165) of the SURGERY file (#130) which is no longer used.  It should
  point to ATTENDING CODE field (#.166) of the SURGERY file.
 
 
  Finally, when printing the 'LONG' form version of an operation request
  for a particular surgical specialty in the Operation Requests for a
  Day [SROP REQ] option in the Surgery Menu, a site noticed the Case
  Order number is not displaying correctly.
  the VistA Surgery application:
 
  In the Surgery option Exclusion Criteria (Enter/Edit) [SR NO
  ASSESSMENT REASON] when users try to enter exclusion criteria
  beginning with 'EXCEEDS' at the 'Reason an Assessment was not
  Created:' prompt, the response 'EXCEEDS MAX ASSMNTS' is always
  always displaying no matter what the user has entered/selected.
 
TRACK PACKAGE NATIONALLY YES
XPI1 NO
XPO1 NO
XPZ1 NO
SEQ# 173
BUILD COMPONENTS
  • ENTRIES:
    • SRONASS
      ACTION:   SEND TO SITE
      CHECKSUM:   B17680159
    • SROREQ2
      ACTION:   SEND TO SITE
      CHECKSUM:   B17559293
    • SR178PST
      ACTION:   SEND TO SITE
      CHECKSUM:   B524049
POST-INSTALL ROUTINE SET^SR178PST
DELETE POST-INIT ROUTINE No