| DESCRIPTION OF ENHANCEMENTS |
This patch installs updates to the Computerized Patient Record System
New Service Requests (NSRs):
----------------------------
20170604: CPRS Blood Bank Report
Work Items:
-----------
214353 CPRS CQ# 19382: Need to update the VAIS and DBIA 4623
434646 VistA - Fixing canned comments on tests sent to VistA
822792 NSR 20170604: CPRS Blood Bank Report
906324 Transmit the ABO/Rh of Transfused Units to CPRS for Display in
A full description of patch changes, implementation process, and
the CPRS Blood Bank Report
939717 Update VBECS VistA MailMan server to report VBECS VistA version
2 patches
970431 Replace Expiration Date with Issued Date/Time on the CPRS Blood
Bank Report in the Available/Issued Units section
1093252 Remove reaction strengths for DAT tests from CPRS blood bank
report.
1186563 CPRS Blood Bank Report does not differentiate tests completed
on the same date/time
validation scenarios are included in the VBECS 2.3.2 Rev F Release Notes.
1230175 Add reference range for ABS and DAT to CPRS Blood Bank Report
1247284 Cancelled orders remain in Component Requests section CRPS
Blood Bank Report
Patient Safety Issues (PSIs):
-----------------------------
N/A
Defect Tracking System Ticket(s) & Overview:
--------------------------------------------
N/A
Test Sites:
-----------
TBD
Software and Documentation Retrieval Instructions:
The Test and Production accounts will be installed separately. There is
Documentation describing the new functionality introduced by this patch
is available on the VA Software Documentation Library at:
http://www.domain.ext/vdl/application.asp?appid=182
Refer to the VBECS 2.3.2 Rev F Release Notes for a list of the user
documentation associated with this revision letter patch.
Additional VBECS information can be accessed on the VBECS SharePoint site
at: https://dvagov.sharepoint.com/sites/oitepmovbecs
no downtime associated with this patch installation. Refer to the VBECS
Patch Installation:
-------------------
Pre-Installation Instructions:
This patch may be installed with users on the system although it is
recommended that it be installed during non-peak hours to minimize
potential disruption to users. This patch should take less than 5
2.3.2 Rev F Release Notes for further installation details.
minutes to install.
No options need to be disabled during installation.
Installation Instructions:
1. Choose the PackMan message containing this build. Then select the
INSTALL/CHECK MESSAGE PackMan option to load the build.
2. From the Kernel Installation and Distribution System Menu, select the
Installation Menu. From this menu,
A. Select the Verify Checksums in Transport Global option to confirm
the integrity of the routines that are in the transport global.
When prompted for the INSTALL NAME enter the patch name VBEC*2.0*8.
B. Select the Backup a Transport Global option to create a backup
message of any routines exported with this patch. It will not
backup any other changes such as DDs or templates.
C. You may also elect to use the following options:
i. Print Transport Global - This option will allow you to view
the components of the KIDS build.
ii. Compare Transport Global to Current System - This option
will allow you to view all changes that will be made when
this patch is installed. It compares all of the components
of this patch, such as routines, DDs, templates, etc.
D. Select the Install Package(s) option and choose the patch to
install.
i. If prompted 'Want KIDS to Rebuild Menu Trees Upon Completion
of Install? NO//', answer No
ii. When prompted 'Want KIDS to INHIBIT LOGONs during the install?
NO//', answer No
iii. When prompted 'Want to DISABLE Scheduled Options, Menu
Options, and Protocols? NO//', answer No
(CPRS) BLOOD BANK REPORT.
Patch Components:
Post-Installation Instructions:
N/A
Back-Out/Roll Back Plan:
------------------------
This patch consists of five routines. During the VistA Installation
Procedure the installer should back up the modified routines by the
use of the 'Backup a Transport Global' action (step 2B in
the Installations Instructions).
-----------------
If rollback/backout is required, the installer can restore the routines
using the MailMan message that were saved prior to installing the
patch.
If assistance is needed to rollback/backout the patch, please log a
Service Now ticket.
Files & Fields Associated:
File Name (Number) Field Name (Number) New/Modified/Deleted
------------------ ------------------- --------------------
N/A
Forms Associated:
Form Name File Number New/Modified/Deleted
--------- ----------- --------------------
N/A
Mail Groups Associated:
This patch also serves to alert VA facilities using the Vista Blood
Mail Group Name New/Modified/Deleted
--------------- --------------------
N/A
Options Associated:
Option Name Type New/Modified/Deleted
----------- ---- --------------------
N/A
Establishment Computer Software (VBECS) that VBECS 2.3.2 Rev F server
Protocols Associated:
Protocol Name New/Modified/Deleted
------------- --------------------
N/A
Security Keys Associated:
patch has been released for installation. VBECS 2.3.2 Rev F will be
Security Key Name
-----------------
N/A
Templates Associated:
Template Name Type File Name (Number) New/Modified/Deleted
------------- ---- ------------------ --------------------
N/A
installed by System Administrators at the Austin Information Technology
Remote Procedures Associated:
Remote Procedure Name New/Modified/Deleted
--------------------- --------------------
N/A
Parameter Definitions Associated:
Center (AITC).
Parameter Name New/Modified/Deleted
-------------- --------------------
N/A
Additional Information:
-----------------------
Blood Bank Team Coordination:
-----------------------------
EFFECT ON BLOOD BANK FUNCTIONAL REQUIREMENTS: Patch VBEC*2*8 contains
changes to a package referenced in VHA OI SEPG SOP 192-023 Review of
VISTA Patches for Effects on VISTA Blood Bank Software. This patch does
not alter or modify any VistA Blood Bank software design safeguards or
safety critical elements functions.
RISK ANALYSIS: Changes made by patch VBEC*2*8 have no effect on VistA
Blood Bank software functionality, therefore RISK is none.
|
