Constraints The VistA component of CAPRI will be installed into all instances of VistA. The client (GUI) will be installed on the Windows-based workstations of CAPRI’s users according to local policies and procedures. Since the VistA component will make changes to the 2507 Requests File (#396.3) in VistA and since the existing client (GUI) is incompatible with those changes, the new client (GUI) must roll out to VBA first to ensure backwards-compatibility with the old database format and to minimize disruption to VBA’s business processes. There are no identified constraints to the installation of this VistA component of CAPRI. Roles and Responsibilities This section describes the who perform the steps described in this deployment plan. Deployment and installation activities are performed by representatives from the teams listed in the following table. This phase begins after the solution design (including deployment topology) is complete. Design activities are not included in this phase. Team Phase / Role Project Phase (See Schedule) CAPRI Development Team Deployment Plan and schedule deployment Deployment Development Team Deployment Develop O&M Plan Deployment Release Readiness Testing Conduct VIP Release Review Approval Testing Test Testing IOC and BETA Tests Patch DVBA*2.7*193 Testing VBA/VHA Business Offices Deployment Develop Communications Plan and key messages well in advance Deployment Health Product Support Testing Review Patch DVBA*2.7*193 Testing Health Product Support Deployment Release DVBA*2.7*193 nationally Deployment Regional PM/FIS/OPP PM Installation Ensure authority to operate and that certification and authorization (C&A)/security documentation is in place Installation Infrastructure Operations Installation Install the patch as scheduled Installation
Table 1 Deployment Roles and Responsibilities Deployment Deployment and installation of the Compensation and Pension Record Interchange (CAPRI) is planned as follows: National Release: 09/18 18 – 10/11/18. CAPRI GUI v2.7 193 will be deployed to all CAPRI Users, and corresponding VistA Patch DVBA*2.7*193 will be deployed to all 130 instances of VistA within a 24-day compliance period. NOTE: CAPRI GUI V2.7 193.12 requires a Version Control check against VistA patch DVBA*2.7*193 Version Control file that will ensure that all VA Sites and CAPRI Users will be operating under CAPRI GUI v2.7 193 after DVBA*2.7*193 has been installed. NOTE: CAPRI GUI v2.7.193.12 is backward compatible with VistA patch DVBA*2.7*192. It is recommended that CAPRI GUI v2.7.193.12 be deployed to as many users as possible prior to installing VistA Patch DVBA*2.7*193 in order to minimize and avoid disruptions of service to the CAPRI National or Remote Users. The 24-day release schedule is as follows: Day 1-22: Deploy CAPRI GUI v2.7.193.12 to all CAPRI users. Day 22-24: Install VistA Patch DVBA*2.7*193 into all Production VistA Systems. The release of the patch will be performed by Health Product Support (HPS) members, supported by the CAPRI project team, along with representatives from peer organizations. The installation will be performed by Local, VISN, or Regional IT support personnel. Timeline The installation and deployment runs for 90 days, which includes a warranty period to monitor for defects. The approximate timeline for this effort is shown in the table below: Phase Activity Finish General Release IOC Testing 09/05/2018 09/14/2018 National Implementation 09/18/2018 10/11/2018 Warranty Period 09/18/2018 12/17/2018 (Dates shown are subject to change due to unforeseen circumstances.) Table 2 CAPRI Patch DVBA*2.7*193 Deployment Timeline
Site/Other Problem/Change Needed Features to Adapt/Modify to New Product Actions/Steps Owner All Create backups n/a Each facility should back up their 2507 Requests File (396.3) and other VistA elements that will be overwritten. Local facility, VISN, or Region All Install new software (GUI) Installation script(s) If applicable, each facility should create scripts to remove the old client (GUI) software and to install the new version on their user workstations. Local facility, VISN, or Region Table 4 Site Preparation Resources This section describes the resources needed for deployment and installation. 3.2.4 Hardware There are no new hardware requirements for this software update. 3.2.5 Software The following list describes software specifications required at each site prior to deployment. The corresponding GUI requires a Windows-based workstation for each user. Associated patches that must be installed BEFORE `DVBA*2.7*193 CAPRI DVBA*2.7*168 CAPRI DVBA*2.7*184 CAPRI DVBA*2.7*185 CAPRI DVBA*2.7*192 CAPRI DVBA*2.7*194 CAPRI DI*22.2*3 CAPRI DVBA*2.7*205 Table 5 Software Specifications Please see the Roles and Responsibilities table in Section 2 above for details about who is responsible for preparing the site to meet these software specifications.
If you are upgrading CAPRI in the workstation’s local hard drive, this pre-requisite should already have been met by an Action Item initiated by ESE. Reference national change order CO161098FY13. However, if one or more of your workstations have windows 7 and these do not have a CAPRI.EXE on local hard disk, i.e. in case of new installs or running CAPRI from a Network Share, on those workstations this pre-requisite has *not* been automatically met. You can meet this pre-requisite by following the instructions on this link In this document you may use either the SCCM method or the manual method. All workstations that will run CAPRI.EXE, MUST have this MODI package installed in order to view large .TIFF files. Even if running CAPRI from the network, this package MUST still be installed on the workstation. 4.10.3 Shared Network or CAPRI access via CPRS Installations If your site installs on a Shared Network Drive and users access a “shortcut” to launch CAPRI or if your users access CAPRI via CPRS, the following MUST be performed to allow users to view PDF files from DAS. Users will receive the following error if this is not done. Figure 11. CAPRI Shortcut Launch Error If the “Start In” folder for CAPRI shortcut at your site is a read-only only folder, it should be changed to a writable folder. This is the folder where documents from VLER DAS are stored temporarily for users to view documents (ex: PDF). Our recommendation is to use %TEMP% as the default starting directory. This can be set in the shortcut that is used to launch CAPRI. Right-click on the (desktop) CAPRI shortcut, select Properties. On the Shortcut tab, in the Start in field, enter %TEMP%. Click OK. Now, when launching CAPRI, it will be able to write temporary files such as Word documents or PDFs to the temporary directory, and CAPRI will be able to display those files to the user. NOTE: This temp directory change only fixes the “access denied” problem when CAPRI is launched directly from a shortcut. Figure 12. Example of Starting CAPRI from a TEMP Directory Location