Page tree

Header Text

Skip to end of metadata
Go to start of metadata

No one single entity is in charge of decision making for deployment, installation, back out and rollback of CPRS v30c. Rather, the Critical Decision Point representatives (commonly referred to as the three in the box) under the Veterans In Process will meet and approve deployment and install from an OI&T perspective. If an issue with the software arises, then the same three in the box members under VIP will meet along with input from Patient Safety and Health Product Support to initiate a back out and rollback decision of the software along with Region and Site leadership. The following table provides CPRSv30c project information.
Table 1: Deployment, Installation, Back-out, and Rollback Roles and Responsibilities

ID

Team

Phase / Role

Tasks

Project Phase (See Schedule)

 

Site personnel in conjunction with IT support – which may be local or regional.

Deployment

Plan and schedule deployment (including orchestration with vendors)

After national release.

 

Site personnel in conjunction with IT support – which may be local or regional.

Deployment

Determine and document the roles and responsibilities of those involved in the deployment.

After national release.

 

Site personnel.

Deployment

Test for operational readiness

After national release.

 

Site personnel in conjunction with IT support – which may be local or regional. The IT support will need to include person(s) to install the KIDS build as well as the personnel to deploy the GUI – which may be done on each machine, a shared network and/or the Citrix access gateway

Deployment

Execute deployment

After national release.

 

Site personnel in conjunction with IT support – which may be local or regional. The IT support will need to include person(s) to install the KIDS build as well as the personnel to deploy the GUI – which may be done on each machine, a shared network and/or the Citrix access gateway

Installation

Plan and schedule installation

After national release.

 

N/A – will work under the VistA ATO and security protocols.

Installation

Ensure authority to operate and that certificate authority security documentation is in place

 

 

N/A – no equipment is being added.

Installation

Validate through facility POC to ensure that IT equipment has been accepted using asset inventory processes

 

 

N/A – no new functionality is being introduced.

Installations

Coordinate training

 

 

Facility CIO and IT support – which may be local or regional.

Back-out

Confirm availability of back-out instructions and back-out strategy (what are the criteria that trigger a back-out)

After national release.

 

Hardware and System support – no changes.
Software support will be the CPRS Development Team during the compliance period. At the end of the compliance period, support will be transitioned to VistA Maintenance.

Post Deployment

Hardware, Software and System Support

After national release.

  • No labels