3. EPMO Open Source Coordination Office Redaction File Detail Report

Produced by Araxis Merge on 9/28/2018 12:31:23 PM 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_EDI_TAS_IB_2.0_621.zip	IB_2_0_P621_IG.docx	Wed Aug 15 18:02:14 2018 UTC
2	MCCF_EDI_TAS_IB_2.0_621.zip	IB_2_0_P621_IG.docx	Wed Sep 26 23:28:04 2018 UTC

3.2 Comparison summary

Description	Between Files 1 and 2
Description	Text Blocks	Lines
Unchanged	1	780
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	Deployment , Installa tion, Back -Out, and Rollback G uide
	2	Medical C are Collec tion Fund (MCCF) Ele ctronic Da ta Interch ange (EDI) Transacti on Applica tions Suit e (TAS) Ph ase 1
	3	eInsurance IB2.062 1
	4
	5
	6	August 201 8
	7	Document V ersion 0.1
	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	08/14/2018
	18	1.0
	19	IOC Entry
	20	Daniel Mor an
	21	June 2018
	22	0.1
	23	Initial Ve rsion - Dr aft
	24	Daniel Mor an
	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 of t hese activ ities. Its purpose i s to provi de clients , stakehol ders, and support pe rsonnel a smooth tra nsition to the new p roduct or software. This docum ent should be struct ured to re flect the applicatio n of these procedure s to eithe r a single site or t o multiple sites.
	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 to Critical Decision P oint #2 (C D #2), wit h the expe ctation th at it will be update d througho ut the lif ecycle of the projec t for each build, as 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)3
	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 ion5
	52	4.1Pre-ins tallation and System Requireme nts5
	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 rocedure6
	61	4.10System Configura tion6
	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 Testing7
	67	5.2.2User Acceptance Testing7
	68	5.3Back-Ou t Criteria 7
	69	5.4Back-Ou t Risks7
	70	5.5Authori ty for Bac k-Out8
	71	5.6Back-Ou t Procedur e8
	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 Risks9
	77	6.4Authori ty for Rol lback9
	78	6.5Rollbac k Procedur e9
	79	6.6Rollbac k Verifica tion Proce dure9
	80
	81	Table of T ables
	82	Table 1: D eployment, Installat ion, Back- out, and R ollback Ro les and Re sponsibili ties1
	83	Table 2: S ite Prepar ation3
	84	Table 3: F acility-Sp ecific Fea tures3
	85	Table 4: H ardware Sp ecificatio ns3
	86	Table 5: S oftware Sp ecificatio ns4
	87	Table 6: D eployment/ Installati on/Back-Ou t Checklis t4
	88
	89
	90
	91	Introducti on
	92	This docum ent descri bes how to deploy an d install the IB2.0 621 patch and how t o back-out the produ ct and rol lback to a previous version or data set.
	93	Purpose
	94	The purpos e of this plan is to provide a single, c ommon docu ment that describes how, when, where, an d to whom IB2.0621 will be d eployed an d installe d, as well as how th e patches are to be backed out and rolle d back, if necessary . The plan also iden tifies res ources, co mmunicatio ns plan, a nd rollout schedule. Specific instructio ns for ins tallation, back-out, and rollb ack are in cluded in this docum ent.
	95	Dependenci es
	96	The follow ing patche s must be installed before IB* 2.0*621:
	97	IB2.0595
	98	IB2.0519
	99
	100	Constraint s
	101	This patch is intend ed for a f ully patch ed VistA s ystem.
	102	Roles and Responsibi lities
	103	Table 1: D eployment, Installat ion, Back- out, and R ollback Ro les and Re sponsibili ties
	104	ID
	105	Team
	106	Phase / Ro le
	107	Tasks
	108	Project Ph ase (See S chedule)
	109	1
	110	VA OI&T, V A OI&T Hea lth Produc t Support & PMO (Lei dos)
	111	Deployment
	112	Plan and s chedule de ployment ( including orchestrat ion with v endors)
	113	Planning
	114	2
	115	Local VAMC and CPAC processes
	116
	117	Deployment
	118	Determine and docume nt the rol es and res ponsibilit ies of tho se involve d in the d eployment.
	119	Planning
	120	3
	121	Field Test ing (Initi al Operati ng Capabil ity (IOC)) , Health P roduct Sup port Testi ng & VIP R elease Age nt Approva l
	122	Deployment
	123	Test for o perational readiness
	124	Testing
	125	4
	126	Health Pro duct Suppo rt and Fie ld Operati ons
	127	Deployment
	128	Execute de ployment
	129	Deployment
	130	5
	131	Individual Veterans Affairs Me dical Cent ers (VAMCs )
	132	Installati on
	133	Plan and s chedule in stallation
	134	Deployment
	135	6
	136	VIP Relea se Agent
	137	Installati on
	138	Ensure aut hority to operate an d that cer tificate a uthority s ecurity do cumentatio n is in pl ace
	139	Deployment
	140	7
	141	N/A for th is patch a s we are u sing only the existi ng VistA s ystem
	142	Installati on
	143	Validate t hrough fac ility POC to ensure that IT eq uipment ha s been acc epted usin g asset in ventory pr ocesses
	144	N/A
	145	8
	146	VA’s eBusi ness team
	147	Installati on
	148	Coordinate training
	149	Deployment
	150	9
	151	VIP releas e Agent, H ealth Prod uct Suppor t & the de velopment team
	152	Back-out
	153	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)
	154	Deployment
	155	10
	156	No changes to curren t process – we are u sing the e xisting Vi stA system
	157	Post Deplo yment
	158	Hardware, Software a nd System Support
	159	Warranty
	160	Deployment
	161	The deploy ment is pl anned as a national rollout.
	162	This secti on provide s the sche dule and m ilestones for the de ployment.
	163	Timeline
	164	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 .
	165	Site Readi ness Asses sment
	166	This secti on discuss es the loc ations tha t will rec eive the I B2.0621 deployment .
	167	Deployment Topology (Targeted Architectu re)
	168	This patch IB2.062 1 is to be nationall y released to all VA MCs.
	169	Site Infor mation (Lo cations, D eployment Recipients )
	170	The test s ites for I OC testing are: TBD
	171	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.
	172
	173	Upon natio nal releas e all VAMC s are expe cted to in stall this patch wit hin the co mpliance d ates.
	174	Site Prepa ration
	175	The follow ing table describes preparatio n required by the si te prior t o deployme nt.
	176	Table 2: S ite Prepar ation
	177	Site/Other
	178	Problem/Ch ange Neede d
	179	Features t o Adapt/Mo dify to Ne w Product
	180	Actions/St eps
	181	Owner
	182	N/A
	183	N/A
	184	N/A
	185	N/A
	186	N/A
	187	Resources
	188	Facility S pecifics
	189	The follow ing table lists faci lity-speci fic featur es require d for depl oyment.
	190	Table 3: F acility-Sp ecific Fea tures
	191	Site
	192	Space/Room
	193	Features N eeded
	194	Other
	195	N/A
	196	N/A
	197	N/A
	198	N/A
	199	Hardware
	200	The follow ing table describes hardware s pecificati ons requir ed at each site prio r to deplo yment.
	201	Table 4: H ardware Sp ecificatio ns
	202	Required H ardware
	203	Model
	204	Version
	205	Configurat ion
	206	Manufactur er
	207	Other
	208	Existing V istA syste m
	209	N/A
	210	N/A
	211	N/A
	212	N/A
	213	N/A
	214	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.
	215	Software
	216	The follow ing table describes software s pecificati ons requir ed at each site prio r to deplo yment.
	217	Table 5: S oftware Sp ecificatio ns
	218	Required S oftware
	219	Make
	220	Version
	221	Configurat ion
	222	Manufactur er
	223	Other
	224	Fully patc hed Integr ated Billi ng package within Vi stA
	225	N/A
	226	2.0
	227	N/A
	228	N/A
	229	N/A
	230	IB2.059 5
	231	N/A
	232	Nationally released version
	233	N/A
	234	N/A
	235	N/A
	236	IB2.051 9
	237	N/A
	238	Nationally released version
	239	N/A
	240	N/A
	241	N/A
	242	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.
	243	Communicat ions
	244	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 Business e Insurance sub-team, the develo pers, and product su pport pers onnel.
	245	Deployment /Installat ion/Back-O ut Checkli st
	246	The Releas e Manageme nt team wi ll deploy the patch IB2.0621 , which is tracked i n the Nati onal Patch Module (N PM) in For um, nation ally to al l VAMCs. F orum autom atically t racks the patches as they are installed in the dif ferent VAM C producti on systems . One can run a repo rt in Foru m to ident ify when a nd by whom the patch was insta lled in th e VistA pr oduction a t each sit e. A repor t can also be run to identify which site s have not currently installed the patch in their VistA prod uction sys tems. Ther efore, thi s informat ion does n ot need to be manual ly tracked in the ch art below.
	247	Table 6: D eployment/ Installati on/Back-Ou t Checklis t
	248	Activity
	249	Day
	250	Time
	251	Individual who compl eted task
	252	Deploy
	253	N/A
	254	N/A
	255	N/A
	256	Install
	257	N/A
	258	N/A
	259	N/A
	260	Back-Out
	261	N/A
	262	N/A
	263	N/A
	264
	265	Installati on
	266	Pre-instal lation and System Re quirements
	267	IB2.0621 , a patch to the exi sting Vist A Integrat ed Billing 2.0 packa ge, is ins tallable o n a fully patched M( UMPS) Vist A system a nd operate s on top o f the Vist A environm ent provid ed by the VistA infr astructure packages. The latte r provides utilities which com municate w ith the un derlying o perating s ystem and hardware, providing Integrated Billing i ndependenc e from var iations in hardware and operat ing system .
	268	Platform I nstallatio n and Prep aration
	269	Refer to t he IB2.0 621 docume ntation on the Natio nal Patch Module (NP M) on Foru m for the detailed i nstallatio n instruct ions. Thes e instruct ions will include an y pre inst allation s teps if ap plicable.
	270	Download a nd Extract Files
	271	Refer to t he IB2.0 621 docume ntation on the NPM t o find the location of related documenta tion that can be dow nloaded. I B2.0621 will be tr ansmitted via a Pack Man messag e and can be pulled from the N PM. It is not a hos t file, an d therefor e does not need to b e download ed separat ely.
	272	Database C reation
	273	IB2.0621 does modi fy the Vis tA databas e. Changes can be fo und in the NPM docum entation f or this pa tch on For um.
	274	Installati on Scripts
	275	No install ation scri pts are ne eded for I B2.0621 installati on.
	276	Cron Scrip ts
	277	No Cron sc ripts are needed for IB2.062 1 installa tion.
	278	Access Req uirements and Skills Needed fo r the Inst allation
	279	The follow ing staff need acces s to the P ackMan mes sage conta ining the IB2.0621 patch or Forum’s NP M in order to downlo ad the nat ionally re leased IB* 2.0*621 pa tch. The s oftware is to be ins talled by the sites or regions designate d: VA OI&T IT OPERAT IONS SERVI CE, Enterp rise Servi ce Lines, and/or Vis tA Applica tions Divi sion.
	280	Installati on Procedu re
	281	Refer to t he IB2.0 621 docume ntation on the NPM f or the det ailed inst allation i nstruction s.
	282	Installati on Verific ation Proc edure
	283	Refer to t he IB2.0 621 docume ntation on the NPM f or detaile d installa tion instr uctions. T hese instr uctions in clude any post insta llation st eps if app licable.
	284	System Con figuration
	285	No system configurat ion change s are requ ired for t his patch.
	286	Database T uning
	287	No reconfi guration o f the Vist A database , memory a llocations or other resources is necessa ry.
	288	Back-Out P rocedure
	289	Back-Out p ertains to a return to the las t known va lid instan ce of oper ational so ftware and platform settings.
	290	Back-Out S trategy
	291	Although i t is unlik ely, due t o care in collecting , elaborat ing, and d esigning a pproved us er stories , followed by multip le testing stages (D eveloper U nit Testin g, Compone nt Integra tion Testi ng, SQA Te sting, and User Acce ptance Tes ting), a b ack-out de cision due to major issues wit h this pat ch could o ccur durin g site Mir ror Testin g, Site Pr oduction T esting or after Nati onal Relea se to the field (VAM Cs). The best strat egy is dep endent on the stage during whi ch the dec ision is m ade.
	292
	293	If during Mirror tes ting or Si te Product ion Testin g, a new v ersion of a defect c orrecting test patch is produc ed, retest ed and suc cessfully passes dev elopment t eam testin g, it woul d be resub mitted to the site f or testing . If the p atch produ ced catast rophic pro blems, a n ew version of the pa tch can be used to r estore the build com ponents to their pre -patch con dition.
	294
	295	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 pa tch for a patch. 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. Thi s new patc h could be used to a ddress spe cific issu es pertain ing to the original patch or c ould be us ed to rest ore the bu ild compon ents to th eir origin al pre-pat ch conditi on.
	296
	297	After the support pe riod, the VistA Main tenance Pr ogram woul d produce the new pa tch, eithe r to corre ct the def ective com ponents or to back-o ut the pat ch.
	298	Back-Out C onsiderati ons
	299	It is nece ssary to d etermine i f a wholes ale back-o ut of the patch IB2 .0621 is needed or if a bette r course o f action i s to corre ct through a new ver sion of th e patch (i f prior to national release) o r through a subseque nt patch a imed at sp ecific are as modifie d or affec ted by the original patch (aft er nationa l release) . A whole sale back- out of the patch wil l still re quire a ne w version (if prior to nationa l release) or a subs equent pat ch (after national r elease). If the bac k-out is p ost-releas e of this patch IB2 .0621, th is patch s hould be a ssigned st atus of “E ntered in Error” in Forum’s NP M.
	300	Load Testi ng
	301	N/A. The b ack-out pr ocess if n ecessary i s executed at normal , rather t han raised job prior ity, and i s expected to have n o signific ant effect on total system per formance. Subsequent to the re version, t he perform ance deman ds on the system wou ld be unch anged.
	302	User Accep tance Test ing
	303	Adjusted t he VistA s oftware th at purges electronic Insurance Verificat ion (eIV) related
	304	inquiries and respo nses, incl uding reco rds contai ned in the new EIV E ICD TRACKI NG (#365.1 8) file (T RACKING), to correct ly evaluat e the "Do Not Purge" field (#3 65,.11) fo und
	305	on the IIV Response File (#365 ) (RESPONS E) record. When a ca ndidate RE SPONSE
	306	record con tains a "D o Not Purg e" field s et to "1" (Yes), the RESPONSE record, th e
	307	associated IIV TRANS MISSION QU EUE (#365. 1) file (T Q) record and the as sociated
	308	EIV EICD T RACKING (# 365.18) re cord will be retaine d. Only th ose RESPON SE records
	309	(plus the associated TQ and TR ACKING rec ords) that meet the criteria f or purging and
	310	have a "Do Not Purge " field se t to "0" ( No) will b e deleted.
	311
	312	Note: A TR ACKING rec ord may po int to 1 ( one) or mo re sets of TQ and RE SPONSE
	313	records. I f any RESP ONSE recor d associat ed with a TRACKING r ecord cont ains a
	314	"Do Not Pu rge" field set to "1 " (Yes) th en all ass ociated TQ and RESPO NSE record s
	315	of that TR ACKING rec ord will b e retained . There is no limit to the num ber of set s of
	316	TQ and RES PONSE reco rds that c an be asso ciated wit h a TRACKI NG record.
	317
	318
	319	VistA has been enhan ced to cre ate Electr onic Insur ance Cover age Discov ery (EICD) identific ation inqu iries for scheduled patients t hat have n o active i nsurance i nformation .
	320	The "No In surance" e xtract (#4 ) has been recommiss ioned as t he "EICD" extract an d
	321	rewritten to examine upcoming appointmen ts for pat ients with out active insurance .
	322	Those pati ents are t hen forwar ded via He alth Level Seven (HL 7) transac tions to t he
	323	Financial Services C enter (FSC ) which in turn will forward t hem to our discovery service
	324	vendor. Al l identifi cation res ults (disc overed ins urance or not) are r eturned to VistA via
	325	FSC at whi ch time no rmal insur ance verif ication in quiries ma y be issue d to the p roper
	326	payers. Wh en discove red insura nces are f or eIV pay ers that a re both lo cally and
	327	nationally active, V istA will automatica lly genera te and tra nsmit a no rmal 270 m essage
	328	to the pay er for ver ification. Any ident ification results re turned to VistA wher e the
	329	discovered insurance are for a non-eIV p ayer or th e eIV paye r is not l ocally/nat ionally
	330	active, wi ll be save d to the I NSURANCE V ERIFICATIO N PROCESSO R (#355.33 ) file
	331	(Buffer) f or manual processing via VistA or the th ird party software I CB (Insura nce
	332	Capture Bu ffer).
	333	Back-Out C riteria
	334	The projec t is cance led or the requested changes i mplemented by IB2.0 621 are n o longer d esired by VA OI&T an d the eBus iness eIns urance sub -team, or the patch produces c atastrophi c problems .
	335	Back-Out R isks
	336	Since the eInsurance software is tightly integrate d with ext ernal syst ems, any a ttempt at a back-out should in clude clos e consulta tion with the extern al trading partners such as th e Financia l Services Center (F SC) and th e Health C are Cleari ng House ( HCCH) to d etermine r isk.
	337	Authority for Back-O ut
	338	The order would come jointly f rom: relea se coordin ator (prod uct suppor t), portfo lio direct or and hea lth produc t support. This shou ld be done in consul tation wit h the deve lopment te am and ext ernal trad ing partne rs such as FSC and t he HCCH to determine the appro priate cou rse of act ion. eInsu rance is t ightly int egrated wi th these e xternal pa rtners and a back-ou t of the p atch shoul d not be a standalon e decision .
	339	Back-Out P rocedure
	340	The rollba ck plan fo r VistA ap plications is comple x and not a “one siz e fits all ” solution . The gene ral strate gy for a V istA rollb ack is to repair the code with a follow- up patch. The develo pment team recommend s that sit es log a t icket if i t is a nat ionally re leased pat ch. If not , the site should co ntact the Enterprise Program M anagement Office (EP MO) team d irectly fo r specific solutions to its un ique probl ems.
	341
	342	The IB2.0 621 patch contains the follow ing build components :
	343	Routine
	344	Enhancemen t
	345	Data Dicti onary
	346	Input Temp late
	347	Other
	348
	349	While the VistA inst allation p rocedure o f the KIDS build all ows the in staller to back up t he modifie d routines using the ‘Backup a Transport Global’ a ction, the back-out procedure for global , data dic tionary an d other Vi stA compon ents is mo re complex and requi res issuan ce of a fo llow-up pa tch to ens ure all co mponents a re properl y removed and/or res tored. All software components (routines and other items) mu st be rest ored to th eir previo us state a t the same time and in conjunc tion with the restor ation of t he data.
	350
	351	Please con tact the E PMO team f or assista nce since this insta lled patch contains components in additi on to rout ines.
	352	Back-out V erificatio n Procedur e
	353	Successful back-out is confirm ed by veri fication t hat the ba ck-out pat ch was suc cessfully installed.
	354	Rollback P rocedure
	355	Rollback p ertains to data. The only data changes i n this pat ch are spe cific to t he operati onal softw are and pl atform set tings and they are c overed in the Back-o ut procedu res detail ed elsewhe re in this document.
	356	Rollback C onsiderati ons
	357	Not applic able.
	358	Rollback C riteria
	359	Not applic able.
	360	Rollback R isks
	361	Not applic able.
	362	Authority for Rollba ck
	363	Not applic able.
	364	Rollback P rocedure
	365	Not applic able.
	366	Rollback V erificatio n Procedur e
	367	Not applic able.
	368
	369	Template R evision Hi story
	370	Date
	371	Version
	372	Descriptio n
	373	Author
	374	March 2016
	375	2.2
	376	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.
	377	VIP Team
	378	February 2 016
	379	2.1
	380	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
	381	OI&T Docum entation S tandards C ommittee
	382	December 2 015
	383	2.0
	384	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.
	385	OI&T Docum entation S tandards C ommittee
	386	February 2 015
	387	1.0
	388	Initial Dr aft
	389	Lifecycle and Releas e Manageme nt
	390