3. EPMO Open Source Coordination Office Redaction File Detail Report

Produced by Araxis Merge on 3/21/2017 9:01:46 AM Central Daylight Time. See www.araxis.com for information about Merge. This report uses XHTML and CSS2, and is best viewed with a modern standards-compliant browser. For optimum results when printing this report, use landscape orientation and enable printing of background images and colours in your browser.

3.1 Files compared

#	Location	File	Last Modified
1	MCCF.zip\docs	VIP_Deployment_Installation_Roll Back_Back-Out_Guide_ePayment PRCA_4_5_317 v1.docx	Mon Jan 30 18:06:50 2017 UTC
2	MCCF.zip\docs	VIP_Deployment_Installation_Roll Back_Back-Out_Guide_ePayment PRCA_4_5_317 v1.docx	Tue Mar 21 13:55:04 2017 UTC

3.2 Comparison summary

Description	Between Files 1 and 2
Description	Text Blocks	Lines
Unchanged	1	720
Changed	0	0
Inserted	0	0
Removed	0	0

3.3 Comparison options

Whitespace
Character case	Differences in character case are significant
Line endings	Differences in line endings (`CR` and `LF` characters) are ignored
CR/LF characters	Not shown in the comparison detail

3.4 Active regular expressions

No regular expressions were active.

3.5 Comparison detail

	1	Medical Ca re Collect ion Fund ( MCCF) Elec tronic Dat a Intercha nge (EDI) Transactio n Applicat ions Suite (TAS) Pha se 1
	2	ePayments PRCA4.53 17
	3	Version 1. 0
	4	Deployment , Installa tion, Back -Out, and Rollback G uide
	5
	6
	7	January 20 17
	8	Department of Vetera ns Affairs
	9	Office of Informatio n and Tech nology (OI &T)
	10
	11
	12	Revision H istory
	13	Date
	14	Version
	15	Descriptio n
	16	Author
	17	January 20 17
	18	1.0
	19	Initial Ve rsion
	20	Darlene Wh ite
	21
	22
	23
	24
	25
	26	Artifact R ationale
	27	This docum ent descri bes the De ployment, Installati on, Back-o ut, and Ro llback Pla n for new products g oing into the VA Ent erprise. T he plan in cludes inf ormation a bout syste m support, issue tra cking, esc alation pr ocesses, a nd roles a nd respons ibilities involved i n all thos e activiti es. Its pu rpose is t o provide clients, s takeholder s, and sup port perso nnel with a smooth t ransition to the new product o r software , and shou ld be stru ctured app ropriately , to refle ct particu lars of th ese proced ures at a single or at multipl e location s.
	28	Per the Ve teran-focu sed Integr ated Proce ss (VIP) G uide, the Deployment , Installa tion, Back -out, and Rollback P lan is req uired to b e complete d prior t o Critical Decision Point #2 ( CD #2), wi th the exp ectation t hat it wil l be updat ed through out the li fecycle of the proje ct for eac h build, a s needed.
	29
	30
	31
	32
	33	Table of C ontents
	34	1Introduct ion1
	35	1.1Purpose 1
	36	1.2Depende ncies1
	37	1.3Constra ints1
	38	2Roles and Responsib ilities1
	39	3Deploymen t2
	40	3.1Timelin e2
	41	3.2Site Re adiness As sessment2
	42	3.2.1Deplo yment Topo logy (Targ eted Archi tecture)2
	43	3.2.2Site Informatio n (Locatio ns, Deploy ment Recip ients)2
	44	3.2.3Site Preparatio n3
	45	3.3Resourc es3
	46	3.3.1Facil ity Specif ics3
	47	3.3.2Hardw are3
	48	3.3.3Softw are3
	49	3.3.4Commu nications4
	50	3.3.4.1Dep loyment/In stallation /Back-Out Checklist4
	51	4Installat ion4
	52	4.1Pre-ins tallation and System Requireme nts4
	53	4.2Platfor m Installa tion and P reparation 5
	54	4.3Downloa d and Extr act Files5
	55	4.4Databas e Creation 5
	56	4.5Install ation Scri pts5
	57	4.6Cron Sc ripts5
	58	4.7Access Requiremen ts and Ski lls Needed for the I nstallatio n5
	59	4.8Install ation Proc edure5
	60	4.9Install ation Veri fication P rocedure5
	61	4.10System Configura tion5
	62	4.11Databa se Tuning6
	63	5Back-Out Procedure6
	64	5.1Back-Ou t Strategy 6
	65	5.2Back-Ou t Consider ations6
	66	5.2.1Load Testing6
	67	5.2.2User Acceptance Testing6
	68	5.3Back-Ou t Criteria 7
	69	5.4Back-Ou t Risks7
	70	5.5Authori ty for Bac k-Out7
	71	5.6Back-Ou t Procedur e7
	72	5.7Back-ou t Verifica tion Proce dure8
	73	6Rollback Procedure8
	74	6.1Rollbac k Consider ations8
	75	6.2Rollbac k Criteria 8
	76	6.3Rollbac k Risks8
	77	6.4Authori ty for Rol lback8
	78	6.5Rollbac k Procedur e9
	79	6.6Rollbac k Verifica tion Proce dure9
	80
	81	Introducti on
	82	This docum ent descri bes how to deploy an d install the PRCA4 .5317 as well as ho w to back- out the pr oduct and rollback t o a previo us version or data s et.
	83	Purpose
	84	The purpos e of this plan is to provide a single, c ommon docu ment that describes how, when, where, an d to whom the PRCA4 .5317 wil l be deplo yed and in stalled, a s well as how it is to be back ed out and rolled ba ck, if nec essary. Th e plan als o identifi es resourc es, commun ications p lan, and r ollout sch edule. Spe cific inst ructions f or install ation, bac k-out, and rollback are includ ed in this document.
	85	Dependenci es
	86	PRCA4.53 04 must be installed before PR CA4.5317 .
	87	Constraint s
	88	This patch is intend ed for a f ully patch ed VistA s ystem.
	89	Roles and Responsibi lities
	90	Table 1: D eployment, Installat ion, Back- out, and R ollback Ro les and Re sponsibili ties
	91	ID
	92	Team
	93	Phase / Ro le
	94	Tasks
	95	Project Ph ase (See S chedule)
	96	1
	97	VA OI&T, V A OI&T Hea lth Produc t Support & PMO (Le idos)
	98	Deployment
	99	Plan and s chedule de ployment ( including orchestrat ion with v endors)
	100	Planning
	101	2
	102	Local VAMC and CPAC processes
	103
	104
	105	Deployment
	106	Determine and docume nt the rol es and res ponsibilit ies of tho se involve d in the d eployment.
	107	Planning
	108	3
	109	Field Test ing (Initi al Operati ng Capabil ity - IOC) , Health P roduct Sup port Testi ng & VIP R elease Age nt Approva l
	110	Deployment
	111	Test for o perational readiness
	112	Testing
	113	4
	114	Health pro duct Suppo rt and Fie ld Operati ons
	115	Deployment
	116	Execute de ployment
	117	Deployment
	118	5
	119	Individual Veterans Administra tion Medic al Centers (VAMCs)
	120	Installati on
	121	Plan and s chedule in stallation
	122	Deployment
	123	6
	124	VIP Relea se Agent
	125	Installati on
	126	Ensure aut hority to operate an d that cer tificate a uthority s ecurity do cumentatio n is in pl ace
	127	Deployment
	128	7
	129	N/A for th is patch a s we are u sing only the existi ng VistA s ystem
	130	Installati on
	131	Validate t hrough fac ility POC to ensure that IT eq uipment ha s been acc epted usin g asset in ventory pr ocesses
	132
	133	8
	134	VA’s eBusi ness team
	135	Installati ons
	136	Coordinate training
	137	Deployment
	138	9
	139	VIP releas e Agent, H ealth Prod uct Suppor t & the de velopment team
	140	Back-out
	141	Confirm av ailability of back-o ut instruc tions and back-out s trategy (w hat are th e criteria that trig ger a back -out)
	142	Deployment
	143	10
	144	No changes to curren t process – we are u sing the e xisting Vi stA system
	145	Post Deplo yment
	146	Hardware, Software a nd System Support
	147	Warranty
	148	Deployment
	149	The deploy ment is pl anned as a national rollout.
	150	This secti on provide s the sche dule and m ilestones for the de ployment.
	151	Timeline
	152	The deploy ment and i nstallatio n is sched uled to ru n for 30 d ays, as de picted in the master deploymen t schedule .
	153	Site Readi ness Asses sment
	154	This secti on discuss es the loc ations tha t will rec eive the P RCA4.531 7 deployme nt.
	155	Deployment Topology (Targeted Architectu re)
	156	This patch PRCA4.5 317 is to be nationa lly releas ed to all VAMCs.
	157	Site Infor mation (Lo cations, D eployment Recipients )
	158	The test s ites for I OC testing are: TBD
	159	These site s will not be define d here unt il the sit es have si gned the M emorandum of Underst anding (MO Us) and te sting has completed as sometim es a site has to sto p testing prior to t he end of IOC.
	160
	161	Upon natio nal releas e all VAMC s are expe cted to in stall this patch wit hin the co mpliance d ate.
	162	Site Prepa ration
	163	The follow ing table describes preparatio n required by the si te prior t o deployme nt.
	164	Table 2: S ite Prepar ation
	165	Site/Other
	166	Problem/Ch ange Neede d
	167	Features t o Adapt/Mo dify to Ne w Product
	168	Actions/St eps
	169	Owner
	170	N/A
	171	N/A
	172	N/A
	173	N/A
	174	N/A
	175	Resources
	176	Facility S pecifics
	177	The follow ing table lists faci lity-speci fic featur es require d for depl oyment.
	178	Table 3: F acility-Sp ecific Fea tures
	179	Site
	180	Space/Room
	181	Features N eeded
	182	Other
	183	N/A
	184	N/A
	185	N/A
	186	N/A
	187	Hardware
	188	The follow ing table describes hardware s pecificati ons requir ed at each site prio r to deplo yment.
	189	Table 4: H ardware Sp ecificatio ns
	190	Required H ardware
	191	Model
	192	Version
	193	Configurat ion
	194	Manufactur er
	195	Other
	196	Existing V istA syste m
	197	N/A
	198	N/A
	199	N/A
	200	N/A
	201	N/A
	202	Please see the Roles and Respo nsibilitie s table in Section 2 for detai ls about w ho is resp onsible fo r preparin g the site to meet t hese hardw are specif ications.
	203	Software
	204	The follow ing table describes software s pecificati ons requir ed at each site prio r to deplo yment.
	205	Table 5: S oftware Sp ecificatio ns
	206	Required S oftware
	207	Make
	208	Version
	209	Configurat ion
	210	Manufactur er
	211	Other
	212	Fully patc hed Accoun ts Receiva ble packag e within V istA
	213	N/A
	214	4.5
	215	N/A
	216	N/A
	217	N/A
	218	PRCA4.53 04
	219	N/A
	220	Nationally released version
	221	N/A
	222	N/A
	223	N/A
	224	Please see the Roles and Respo nsibilitie s table in Section 2 above for details a bout who i s responsi ble for pr eparing th e site to meet these software specificat ions.
	225	Communicat ions
	226	The sites that are p articipati ng in fiel d testing (IOC) will use the “ Patch Trac king” mess age in Out look to co mmunicate with the e Payments e Business t eam, the d evelopers, and produ ct support personnel .
	227	Deployment /Installat ion/Back-O ut Checkli st
	228	The Releas e Manageme nt team wi ll deploy the patch PRCA4.53 17, which is tracked in the NP M in Forum , national ly to all VAMCs. Fo rum automa tically tr acks the p atches as they are i nstalled i n the diff erent VAMC productio n systems. One can run a repo rt in Foru m to ident ify when t he patch w as install ed in the VistA prod uction at each site, and by wh om. A rep ort can al so be run, to identi fy which s ites have not instal led the pa tch in the ir VistA p roduction system as of that mo ment in ti me.
	229
	230	Therefore, this info rmation do es not nee d to be ma nually tra cked in th e chart be low.
	231	Table 6: 3 .3.4.1Depl oyment/Ins tallation/ Back-Out C hecklist
	232
	233	Activity
	234	Day
	235	Time
	236	Individual who compl eted task
	237	Deploy
	238	N/A
	239	N/A
	240	N/A
	241	Install
	242	N/A
	243	N/A
	244	N/A
	245	Back-Out
	246	N/A
	247	N/A
	248	N/A
	249
	250	Installati on
	251	Pre-instal lation and System Re quirements
	252	PRCA4.53 17, a patc h to the e xisting Vi stA Accoun ts Receiva ble 4.5 pa ckage, is installabl e on a ful ly patched M(UMPS) V istA syste m and oper ates on th e top of t he VistA e nvironment provided by the Vis tA infrast ructure pa ckages. T he later p rovides ut ilities wh ich commun icate with the under lying oper ating syst em and har dware, the reby provi ding Accou nts Receiv able indep endence fr om variati ons in har dware and operating system.
	253	Platform I nstallatio n and Prep aration
	254	Refer to P RCA4.531 7 document ation on t he Nationa l Patch Mo dule (NPM) on Forum for the de tailed ins tallation instructio ns. These instructi ons would include an y pre inst allation s teps if ap plicable.
	255	Download a nd Extract Files
	256	Refer to P RCA4.531 7 document ation on t he NPM for where to find relat ed documen tation tha t can be d ownloaded. PRCA4.5 317 will be transmi tted via a PackMan m essage and can be pu lled from the NPM. It is not a host fil e, and the refore doe s not need to be dow nloaded se parately.
	257	Database C reation
	258	PRCA4.53 17 does no t modify t he VistA d atabase. If it did any change s could be found on the NPM do cumentatio n for this patch.
	259	Installati on Scripts
	260	No install ation scri pts are ne eded for P RCA4.531 7 installa tion.
	261	Cron Scrip ts
	262	No Cron sc ripts are needed for PRCA4.5 317 instal lation.
	263	Access Req uirements and Skills Needed fo r the Inst allation
	264	The follow ing staff will need access to the PackMa n message containing the PRCA* 4.5317 pa tch or For um’s NPM f or downloa ding the n ationally released P RCA4.5*31 7 patch. T he softwar e is to be installed by the si te’s or re gion’s des ignated: V A OI&T IT OPERATIONS SERVICE, Enterprise Service L ines, Vist a Applicat ions Divis ion .
	265	Installati on Procedu re
	266	Refer to P RCA4.531 7 document ation on t he NPM for the detai led instal lation ins tructions.
	267	Installati on Verific ation Proc edure
	268	Refer to P RCA4.531 7 document ation on t he NPM for the detai led instal lation ins tructions. These in structions would inc lude any p ost instal lation ste ps if appl icable.
	269	System Con figuration
	270	No system configurat ion change s are requ ired for t his patch.
	271	Database T uning
	272	No reconfi guration o f the Vist A database , memory a llocations or other resources is necessa ry.
	273	Back-Out P rocedure
	274	Back-Out p ertains to a return to the las t known go od operati onal state of the so ftware and appropria te platfor m settings .
	275	Back-Out S trategy
	276	Although i t is unlik ely a back -out decis ion due to major iss ues with t his patch could occu r during s ite Mirror Testing, Site Produ ction Test ing or aft er Nationa l Release to the fie ld (VAMCs) . The str ategy woul d depend o n during w hich of th ese stages the decis ion is mad e.
	277
	278	If during Mirror tes ting or Si te Product ion Testin g, unless the patch produces c atastrophi c problems , the norm al VistA r esponse wo uld be for a new ver sion of th e test pat ch correct ing defect s to be pr oduced, re tested and upon suc cessfully passing de velopment team testi ng would b e resubmit ted to the site for testing. This proje ct, howeve r, has pre pared a se t of back- out patch instructio ns if nece ssary, as in the cas e that the project i s canceled or the im plemented design is found to b e so wrong and detri mental to the site’s delivery of service s to veter ans that t he softwar e must be removed.
	279
	280	If the def ect(s) wer e not disc overed unt il after n ational re lease but during the designate d support period, a new patch will be en tered into the Natio nal Patch Module on Forum and go through all the n ecessary m ilestone r eviews etc . as a pat ch for a p atch. It is up to V A OI&T and product s upport whe ther this new patch would be d efined as an emergen cy patch o r not. Aft er the sup port perio d, the Vis tA Mainten ance Progr am would p roduce the new patch , either t o correct the defect ive compon ents or to back-out the patch.
	281
	282	In the cas e of PRCA* 4.5*317, a new patch would not be necess ary for ba ck out pur poses as t he site wi ll have a backup tha t they cre ated durin g the init ial instal l.
	283	Back-Out C onsiderati ons
	284	It is nece ssary to d etermine i f a wholes ale back-o ut/rollbac k of the p atch PRCA* 4.5317 is necessary or if a b etter cour se is to c orrect thr ough a new version o f the patc h (if prio r to natio nal releas e) or a su bsequent p atch aimed at specif ic areas m odified or affected by the ori ginal patc h (after n ational re lease). If the back- out is pos t-release of patch P RCA4.5*31 7, this pa tch should be assign ed status of “Entere d in Error ” in Forum ’s NPM.
	285	Load Testi ng
	286	N/A. The b ack-out pr ocess woul d be execu ted at nor mal, rathe r than rai sed job pr iority, an d is expec ted to hav e no signi ficant eff ect on tot al system performanc e. Subseq uent to th e reversio n, the per formance d emands on the system would be unchanged.
	287	User Accep tance Test ing
	288	For the fo llowing th ree areas in VistA, a user wit h a prefer red view o n file sho uld select the menu option or action lis ted below and confir m that the y are no l onger prom pted with the questi on “Use pr eferred vi ew?” prior to the sc reen displ aying the selected d ata.
	289	ERA Workli st [RCDPE EDI LOCKBO X WORKLIST ]
	290	ERA Scratc hpad
	291	ERA Workli st [RCDPE EDI LOCKBO X WORKLIST ] action ‘Select ER A’
	292	Auto-Post Awaiting R esolution [RCDPE APA R]
	293
	294	User with access to the “EDI L ockbox (eP ayments) R eports Men u…” [RCDPE EDI LOCKB OX REPORTS MENU] sho uld pull u p the menu and confi rm that th e “Unappli ed EFT Dep osits Repo rt” [RCDPE UNAPPLIED EFT DEP R EPORT]” op tion is no longer av ailable.
	295
	296	It is expe cted that the IT Sup port can c onfirm tha t the opti on “Unappl ied EFT De posits Rep ort” [RCDP E UNAPPLIE D EFT DEP REPORT] ha s been rem oved from the VistA system.
	297	Back-Out C riteria
	298	The projec t is cance led or the requested changes i mplemented by PRCA4 .5317 are no longer desired b y VA OI&T and the eP ayments eB usiness te am.
	299	Back-Out R isks
	300	Before nat ional rele ase: There are no cu rrent iden tified ris ks of back ing out PR CA4.5317 prior to national r elease.
	301
	302	After nati onal relea se: If th e PRCA4.5 317 patch is to be backed out after it is nationa lly releas ed it may do so acco rding to t his docume nt only if none of t he followi ng stateme nts are tr ue. If an y of the f ollowing s tatements are true, refer to t he sub bul lets below for prope r guidelin es.
	303
	304	Subsequent patch(es) that is c urrently u nder devel opment is dependent upon any a spect chan ged by PRC A4.5317.
	305	Inform the teams res ponsible f or the sub sequent pa tch(es) of the reque st to back out the pa tch so the y can make any neces sary chang es to thei r software and sched ule. With coordinat ion of the se teams f or the sub sequent pa tch(es), p roceed wit h the back out.
	306
	307	Subsequent patch(es) that is n ationally released o r has the status of ‘complete d/not rele ased’ is d ependent u pon any as pect chang ed by PRCA 4.5317.
	308	Back-out p rocedures may not be executed. This req uires a ne w patch to address t he concern .
	309	Authority for Back-O ut
	310	The order would come from: rel ease coord inator (pr oduct supp ort), port folio dire ctor and h ealth prod uct suppor t.
	311	Back-Out P rocedure
	312	A few thin gs need to be done i n order to back out this PRCA* 4.5*317 pa tch. They are as fol lows: rest ore the ro utines to their prev ious state , remove a n option f rom a menu , delete a n option, and rebuil d the menu trees. T his will n eed to be done by th e site’s d esignated IT support .
	313
	314	Restore th e routines to their previous s tate
	315	The user w as instruc ted to exe cute the m enu option “Backup a Transport Global” [ XPD BACKUP ] when the patch was initially installed (the very 1st time if install ed multipl e times). To restor e the rout ines, loca te the Mai lMan messa ge that wa s created as part of that step . While v iewing the MailMan m essage, ex tract the KIDS build , using th e “Xtract PackMan” a ction. Th en select the “INSTA LL/CHECK M ESSAGE” ac tion to re store the modified r outines.
	316
	317	Remove an option fro m a menu
	318	Within Fil eMan, use the “ENTER OR EDIT F ILE ENTRIE S” option and select the file “OPTION” ( #.19). Wh en prompte d for ‘EDI T WHICH FI ELD’, answ er with th e “MENU” m ultiple (# 10). When prompted for ‘EDIT WHICH MENU SUB-FIELD ’, answer with “ITEM ” (#.01). When prom pted for “ Select OPT ION NAME”, answer wi th “EDI Lo ckbox (ePa yments) Re ports Menu …” [RCDPE EDI LOCKBO X REPORTS MENU] and remove/del ete the IT EM [RCDPE UNAPPLIED EFT DEP RE PORT] “Una pplied EFT Deposits Report”.
	319
	320	** IMPORTA NT: If th e site add ed the opt ion “Unapp lied EFT D eposits Re port” [RCD PE UNAPPLI ED EFT DEP REPORT] t o any othe r menus, r emove it f rom those menus as w ell at thi s time.
	321
	322	Delete an option
	323	Within Fil eMan, use the “ENTER OR EDIT F ILE ENTRIE S” option and select the file “OPTION” ( #.19). Wh en prompte d for ‘EDI T WHICH FI ELD’, answ er with th e “NAME” ( #.01). Wh en prompte d for “Sel ect OPTION NAME”, an swer with “Unapplied EFT Depos its Report ” [RCDPE U NAPPLIED E FT DEP REP ORT] . De lete this option. W hen prompt ed for “DO YOU WANT THOSE POIN TERS UPDAT ED (WHICH COULD TAKE QUITE A W HILE)?”, a nswer NO.
	324	Back-out V erificatio n Procedur e
	325	It is expe cted that the IT sup port can u se FileMan to confir m that the menu opti on “Unappl ied EFT De posits Rep ort” [RCDP E UNAPPLIE D EFT DEP REPORT] ha s been suc cessfully removed fr om the Vis tA system.
	326	Rollback P rocedure
	327	Rollback p ertains to data. Si nce patch PRCA4.53 17 does no t impact t he data in the Accou nts Receiv able packa ge there i s no need for a roll back proce dure. The back-out procedure includes i nstruction s of how t o remove a nd delete a menu opt ion so no additional procedure s are nece ssary to r oll back t he VistA s oftware.
	328	Rollback C onsiderati ons
	329	Not applic able.
	330	Rollback C riteria
	331	Not applic able.
	332	Rollback R isks
	333	Not applic able.
	334	Authority for Rollba ck
	335	Not applic able.
	336	Rollback P rocedure
	337	Not applic able.
	338	Rollback V erificatio n Procedur e
	339	Not applic able.
	340	Template R evision Hi story
	341	Date
	342	Version
	343	Descriptio n
	344	Author
	345	March 2016
	346	2.2
	347	Changed th e title fr om Install ation, Bac k-Out, and Rollback Guide to D eployment and Instal lation Gui de, with t he underst anding tha t Back-Out and Rollb ack belong with Inst allation.
	348	VIP Team
	349	February 2 016
	350	2.1
	351	Changed ti tle from I nstallatio n, Back-Ou t, and Rol lback Plan to Instal lation, Ba ck-Out, an d Rollback Guide as recommende d by OI&T Documentat ion Standa rds Commit tee
	352	OI&T Docum entation S tandards C ommittee
	353	December 2 015
	354	2.0
	355	The OI&T D ocumentati on Standar ds Committ ee merged the existi ng “Instal lation, Ba ck-Out, Ro llback Pla n” templat e with the content r equirement s in the O I&T End-us er Documen tation Sta ndards for a more co mprehensiv e Installa tion Plan.
	356	OI&T Docum entation S tandards C ommittee
	357	February 2 015
	358	1.0
	359	Initial Dr aft
	360	Lifecycle and Releas e Manageme nt