Introduction This document describes how to deploy and install the HAPE FY16 Revenue Enhancements Accounts Receivable patch PRCA*4.5*315 as well as how to back-out the product and rollback to a previous version or data set. This document is a companion to the project charter and management plan for this effort. Purpose The purpose of this plan is to provide a single, common document that describes how, when, where, and to whom the HAPE FY16 Revenue Enhancements Accounts Receivable patch PRCA*4.5*315 will be deployed and installed, as well as how it is to be backed out and rolled back, if necessary. The plan also identifies resources, communications plan, and rollout schedule. Specific instructions for installation, back-out, and rollback are included in this document. Dependencies This product is a VistA patch. Successful deployment and installation of this patch is dependent upon a fully functional and existing VistA system with functional links with FMS and with Central Fee at the Austin Information Technology Center (AITC). Constraints This product is a VistA patch. The only constraints associated with the patch installation are the required patches as mentioned in the patch description and on the Forum National Patch Module (NPM). Roles and Responsibilities Table 1: Deployment, Installation, Back-out, and Rollback Roles and Responsibilities Team Phase / Role Tasks Plan and schedule deployment (including Health Product Support Deployment orchestration with vendors) Health Product Support and Determine and document the roles and existing local VAMC and CPAC Deployment responsibilities of those involved in the processes deployment. Health Product Support and VIP Deployment Test for operational readiness Release Agent Health Product Support Deployment Execute deployment Designated VistA patch installer Installation Plan and schedule installation for this package Designated VistA patch installer Ensure authority to operate and that for this package and VIP Release Installation certificate authority security Agent documentation is in place
Introduction This document describes how to deploy and install the HAPE FY16 Revenue Enhancements Accounts Receivable patch PRCA*4.5*315 as well as how to back-out the product and rollback to a previous version or data set. This document is a companion to the project charter and management plan for this effort. Purpose The purpose of this plan is to provide a single, common document that describes how, when, where, and to whom the HAPE FY16 Revenue Enhancements Accounts Receivable patch PRCA*4.5*315 will be deployed and installed, as well as how it is to be backed out and rolled back, if necessary. The plan also identifies resources, communications plan, and rollout schedule. Specific instructions for installation, back-out, and rollback are included in this document. Dependencies This product is a VistA patch. Successful deployment and installation of this patch is dependent upon a fully functional and existing VistA system with functional links with FMS and with Central Fee at the Austin Information Technology Center (AITC). Constraints This product is a VistA patch. The only constraints associated with the patch installation are the required patches as mentioned in the patch description and on the Forum National Patch Module (NPM). Roles and Responsibilities Table 1: Deployment, Installation, Back-out, and Rollback Roles and Responsibilities Team Phase / Role Tasks Health Product Support Deployment Plan and schedule deployment (including orchestration with vendors) Health Product Support and existing local VAMC and CPAC processes Deployment Determine and document the roles and responsibilities of those involved in the deployment. Health Product Support and VIP Release Agent Deployment Test for operational readiness Health Product Support Deployment Execute deployment Designated VistA patch installer for this package Installation Plan and schedule installation Designated VistA patch installer for this package and VIP Release Agent Installation Ensure authority to operate and that certificate authority security documentation is in place
prca_4_5_p315_ig.docx