1. EPMO Open Source Coordination Office Redaction File Detail Report

Produced by Araxis Merge on 4/17/2018 8:06:16 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.

1.1 Files compared

#	Location	File	Last Modified
1	MCCF EDI TAS ePharmacy 031218.zip\MCCF EDI TAS ePharmacy 031218	bps_1_0_p23_ig.docx	Wed Feb 14 13:52:53 2018 UTC
2	MCCF EDI TAS ePharmacy 031218.zip\MCCF EDI TAS ePharmacy 031218	bps_1_0_p23_ig.docx	Mon Apr 16 17:05:54 2018 UTC

1.2 Comparison summary

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

1.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

1.4 Active regular expressions

No regular expressions were active.

1.5 Comparison detail

	1	Medical Ca re Collect ion Fund ( MCCF) Elec tronic Dat a Intercha nge (EDI) Transactio n Applicat ions Suite (TAS) ePh armacy Bui ld 3 & 4
	2	Electronic Claims Ma nagement E ngine BPS* 1.023Outp atient Pha rmacy PSO 7.0482Int egrated Bi lling IB2 .0*591
	3	Deployment , Installa tion, Back -Out, and Rollback G uide
	4	Version 1. 0
	5
	6
	7	June 2018
	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	June 2018
	18	1.0
	19	Initial Ve rsion
	20	Mark Dawso n
	21
	22	Artifact R ationale
	23	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.
	24	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.
	25
	26
	27
	28
	29	Table of C ontents
	30	1Introduct ion1
	31	1.1Purpose 1
	32	1.2Depende ncies1
	33	1.3Constra ints1
	34	2Roles and Responsib ilities1
	35	3Deploymen t2
	36	3.1Timelin e2
	37	3.2Site Re adiness As sessment2
	38	3.2.1Deplo yment Topo logy (Targ eted Archi tecture)2
	39	3.2.2Site Informatio n (Locatio ns, Deploy ment Recip ients)2
	40	3.2.3Site Preparatio n3
	41	3.3Resourc es3
	42	3.3.1Facil ity Specif ics3
	43	3.3.2Hardw are3
	44	3.3.3Softw are3
	45	3.3.4Commu nications4
	46	3.3.4.1Dep loyment/In stallation /Back-Out Checklist4
	47	4Installat ion4
	48	4.1Pre-ins tallation and System Requireme nts4
	49	4.2Platfor m Installa tion and P reparation 5
	50	4.3Downloa d and Extr act Files5
	51	4.4Databas e Creation 5
	52	4.5Install ation Scri pts5
	53	4.6Cron Sc ripts5
	54	4.7Access Requiremen ts and Ski lls Needed for the I nstallatio n5
	55	4.8Install ation Proc edure5
	56	4.9Install ation Veri fication P rocedure5
	57	4.10System Configura tion5
	58	4.11Databa se Tuning5
	59	5Back-Out Procedure6
	60	5.1Back-Ou t Strategy 6
	61	5.1.1Mirro r Testing or Site Pr oduction T esting6
	62	5.1.2After National Release bu t During t he Designa ted Suppor t Period6
	63	5.1.3After National Release an d Warranty Period6
	64	5.2Back-Ou t Consider ations6
	65	5.2.1Load Testing6
	66	5.2.2User Acceptance Testing6
	67	5.3Back-Ou t Criteria 8
	68	5.4Back-Ou t Risks8
	69	5.5Authori ty for Bac k-Out8
	70	5.6Back-Ou t Procedur e8
	71	5.7Back-ou t Verifica tion Proce dure9
	72	6Rollback Procedure9
	73	6.1Rollbac k Consider ations9
	74	6.2Rollbac k Criteria 9
	75	6.3Rollbac k Risks9
	76	6.4Authori ty for Rol lback9
	77	6.5Rollbac k Procedur e9
	78	6.6Rollbac k Verifica tion Proce dure9
	79
	80	Table of T ables
	81	Table 1: D eployment, Installat ion, Back- out, and R ollback Ro les and Re sponsibili ties1
	82	Table 2: S ite Prepar ation3
	83	Table 3: F acility-Sp ecific Fea tures3
	84	Table 4: H ardware Sp ecificatio ns3
	85	Table 5: S oftware Sp ecificatio ns4
	86	Table 6: D eployment/ Installati on/Back-Ou t Checklis t4
	87
	88
	89
	90	Introducti on
	91	This docum ent descri bes how to deploy an d install the multi- build BPS IB PSO BUN DLE 11.0 ( which incl udes BPS1 .023, IB* 2.0591, P SO7.0*482 ) and how to back-ou t the prod uct and ro llback to a previous version o r data set .
	92	Purpose
	93	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 multi- build BPS IB PSO BUN DLE 11.0 ( which incl udes BPS1 .023, IB* 2.0591, P SO7.0*482 ) will be deployed a nd install ed, as wel l as how i t is to be backed ou t and roll ed back, i f necessar y. The pla n 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.
	94	Dependenci es
	95	BPS1.021 and BPS1 .022 must be instal led BEFORE BPS123.
	96	IB2.0550 must be i nstalled B EFORE IB2 .0591.
	97	PSO7.031 8, PSO7.0 409, PSO* 7.0422, P SO7.0459 , and PSO 7.0478 mu st be inst alled BEFO RE PSO7*4 82.
	98	Constraint s
	99	This patch is intend ed for a f ully patch ed VistA s ystem.
	100	Roles and Responsibi lities
	101	Table 1: D eployment, Installat ion, Back- out, and R ollback Ro les and Re sponsibili ties
	102	ID
	103	Team
	104	Phase / Ro le
	105	Tasks
	106	Project Ph ase (See S chedule)
	107	1
	108	VA OI&T, V A OI&T Hea lth Produc t Support, and PMO ( Leidos)
	109	Deployment
	110	Plan and s chedule de ployment ( including orchestrat ion with v endors)
	111	Planning
	112	2
	113	Local VAMC and CPAC processes
	114
	115
	116	Deployment
	117	Determine and docume nt the rol es and res ponsibilit ies of tho se involve d in the d eployment.
	118	Planning
	119	3
	120	Field Test ing (Initi al Operati ng Capabil ity - IOC) , Health P roduct Sup port Testi ng & VIP R elease Age nt Approva l
	121	Deployment
	122	Test for o perational readiness
	123	Testing
	124	4
	125	Health pro duct Suppo rt and Fie ld Operati ons
	126	Deployment
	127	Execute de ployment
	128	Deployment
	129	5
	130	Individual Veterans Administra tion Medic al Centers (VAMCs)
	131	Installati on
	132	Plan and s chedule in stallation
	133	Deployment
	134	6
	135	VIP Relea se Agent
	136	Installati on
	137	Ensure aut hority to operate an d that cer tificate a uthority s ecurity do cumentatio n is in pl ace
	138	Deployment
	139	7
	140
	141	Installati on
	142	Validate t hrough fac ility POC to ensure that IT eq uipment ha s been acc epted usin g asset in ventory pr ocesses
	143	N/A; only existing V istA syste m will be used
	144	8
	145	VA’s eBusi ness team
	146	Installati ons
	147	Coordinate training
	148	Deployment
	149	9
	150	VIP releas e Agent, H ealth Prod uct Suppor t & the de velopment team
	151	Back-out
	152	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)
	153	Deployment
	154	10
	155	VA OI&T, V A OI&T Hea lth Produc t Support, and MCCF EDI TAS De velopment Team (Half aker)
	156	Post Deplo yment
	157	Hardware, Software a nd System Support
	158	Warranty
	159	Deployment
	160	The deploy ment is pl anned as a national rollout.
	161	This secti on provide s the sche dule and m ilestones for the de ployment.
	162	Timeline
	163	The durati on of depl oyment and installat ion is 30 days, as d epicted in the maste r deployme nt schedul e.
	164	Site Readi ness Asses sment
	165	This secti on discuss es the loc ations tha t will rec eive the d eployment of the mul ti-build B PS IB PSO BUNDLE 11. 0 (which i ncludes BP S1.023, IB2.0591 , PSO7.0 482).
	166	Deployment Topology (Targeted Architectu re)
	167	This multi -build BPS IB PSO BU NDLE 11.0 (which inc ludes BPS* 1.023, IB 2.0591, PSO7.0*48 2) is to b e national ly release d to all V AMCs.
	168	Site Infor mation (Lo cations, D eployment Recipients )
	169	The IOC si tes are:
	170	Birmingham
	171	Eastern Ka nsas
	172	Lexington
	173	Little Roc k
	174	Richmond
	175
	176	Upon natio nal releas e all VAMC s are expe cted to in stall this patch pri or to or o n the comp liance dat e.
	177	Site Prepa ration
	178	The follow ing table describes preparatio n required by the si te prior t o deployme nt.
	179	Table 2: S ite Prepar ation
	180	Site/Other
	181	Problem/Ch ange Neede d
	182	Features t o Adapt/Mo dify to Ne w Product
	183	Actions/St eps
	184	Owner
	185	N/A
	186	N/A
	187	N/A
	188	N/A
	189	N/A
	190	Resources
	191	Facility S pecifics
	192	The follow ing table lists faci lity-speci fic featur es require d for depl oyment.
	193	Table 3: F acility-Sp ecific Fea tures
	194	Site
	195	Space/Room
	196	Features N eeded
	197	Other
	198	N/A
	199	N/A
	200	N/A
	201	N/A
	202	Hardware
	203	The follow ing table describes hardware s pecificati ons requir ed at each site prio r to deplo yment.
	204	Table 4: H ardware Sp ecificatio ns
	205	Required H ardware
	206	Model
	207	Version
	208	Configurat ion
	209	Manufactur er
	210	Other
	211	Existing V istA syste m
	212	N/A
	213	N/A
	214	N/A
	215	N/A
	216	N/A
	217	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.
	218	Software
	219	The follow ing table describes software s pecificati ons requir ed at each site prio r to deplo yment.
	220	Table 5: S oftware Sp ecificatio ns
	221	Required S oftware
	222	Make
	223	Version
	224	Configurat ion
	225	Manufactur er
	226	Other
	227	Fully patc hed Electr onic Claim s Manageme nt Engine package wi thin VistA
	228	N/A
	229	1.0
	230	N/A
	231	N/A
	232	N/A
	233	Fully patc hed Integr ated Billi ng package within Vi stA
	234	N/A
	235	2.0
	236	N/A
	237	N/A
	238	N/A
	239	Fully patc hed Outpat ient Pharm acy packag e within V istA
	240	N/A
	241	7.0
	242	N/A
	243	N/A
	244	N/A
	245	Prerequisi te patches in BPS, I B, PSO yet to be det ermined
	246	N/A
	247	Nationally released version
	248	N/A
	249	N/A
	250	N/A
	251	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.
	252	Communicat ions
	253	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 Pharmacy e Business t eam, the d evelopers, and produ ct support personnel .
	254	Deployment /Installat ion/Back-O ut Checkli st
	255	The Releas e Manageme nt team wi ll deploy the multi- build BPS IB PSO BUN DLE 11.0, which is t racked nat ionally fo r all VAMC s in the N ational Pa tch Module (NPM) in Forum. For um automat ically tra cks the pa tches as t hey are in stalled in the diffe rent VAMC production systems. One can ru n a report in Forum to identif y when and by whom t he patch w as install ed into 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 into thei r VistA pr oduction s ystem. The refore, th is informa tion does not need t o be manua lly tracke d in the c hart below .
	256
	257	Table 6: D eployment/ Installati on/Back-Ou t Checklis t
	258	Activity
	259	Day
	260	Time
	261	Individual who compl eted task
	262	Deploy
	263	N/A
	264	N/A
	265	N/A
	266	Install
	267	N/A
	268	N/A
	269	N/A
	270
	271	Installati on
	272	Pre-instal lation and System Re quirements
	273	Multi-buil d BPS IB P SO BUNDLE 11.0 is in stallable on a fully patched M (UMPS) Vis tA system and operat es on the top of the VistA env ironment p rovided by the VistA infrastru cture pack ages. The latter pro vides util ities whic h communic ate with t he underly ing operat ing system and hardw are, there by providi ng each Vi stA packag e independ ence from variations in hardwa re and ope rating sys tem.
	274	Platform I nstallatio n and Prep aration
	275	Refer to t he BPS1.0 23 docume ntation on the NPM i n Forum fo r the deta iled insta llation in structions . These in structions include a ny pre-ins tallation steps if a pplicable.
	276	Download a nd Extract Files
	277	Refer to t he BPS1.0 23, IB2. 0591, PSO 7.0482 d ocumentati on on the NPM to fin d related documentat ion that c an be down loaded. Th e patch de scription of each pa tch will b e transmit ted as a M ailMan mes sage from the NPM an d this mes sage can b e pulled f rom the NP M. The pat ches thems elves are bundled to gether int o the mult i-build BP S IB PSO B UNDLE 11.0 . The host file cont aining the se patches must be d ownloaded separately . The file name is B PS_1_23_IB _PSO.KID a nd it can be found o n the ANON YMOUS.SOFT WARE direc tory on an y of the V istA SFTP servers (H ines, Salt Lake City ).
	278	Database C reation
	279	Multi-buil d BPS IB P SO BUNDLE 11.0 modif ies the Vi stA databa se. All ch anges can be found o n the NPM documentat ion for th is patch.
	280	Installati on Scripts
	281	No install ation scri pts are ne eded for m ulti-build BPS IB PS O BUNDLE 1 1.0 instal lation.
	282	Cron Scrip ts
	283	No Cron sc ripts are needed for multi-bui ld BPS IB PSO BUNDLE 11.0 inst allation.
	284	Access Req uirements and Skills Needed fo r the Inst allation
	285	Staff perf orming the installat ion of thi s multi-bu ild will n eed access to FORUM’ s NPM to v iew all pa tch descri ptions. St aff will a lso need a ccess and ability to download the host f ile from o ne of the VA’s SFTP servers. T he softwar e is to be installed by each s ite’s or r egion’s de signated V A OI&T IT OPERATIONS SERVICE, Enterprise Service L ines, Vist a Applicat ions Divis ion.
	286	Installati on Procedu re
	287	Detailed i nstruction s for inst alling the multi-bui ld BPS IB PSO BUNDLE 11.0 (whi ch include s BPS1.0 23, IB2.0 591, PSO* 7.0482) c an be foun d on the p atch descr iption for BPS1.02 3, which c an be foun d on the N PM. Instal ling the m ulti-build BPS IB PS O BUNDLE 1 1.0 will i nstall all three com ponent pat ches (BPS 1.023, IB 2.0591, PSO7.0*48 2).
	288	Installati on Verific ation Proc edure
	289	Refer to t he BPS1.0 23 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.
	290	System Con figuration
	291	No system configurat ion change s are requ ired for t his patch.
	292	Database T uning
	293	No reconfi guration o f the Vist A database , memory a llocations or other resources is necessa ry.
	294	Back-Out P rocedure
	295	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 .
	296	Back-Out S trategy
	297	A decision to back o ut could b e made dur ing Site M irror Test ing, durin g Site Pro duction Te sting, or after Nati onal Relea se to the field (VAM Cs). The b est strate gy decisio n is depen dent on th e stage of testing d uring whic h the deci sion is ma de.
	298	Mirror Tes ting or Si te Product ion Testin g
	299	If a decis ion to bac k out is m ade during Mirror Te sting or S ite Produc tion Testi ng, a new version of the patch can be us ed to rest ore the bu ild compon ents to th eir pre-pa tch condit ion.
	300	After Nati onal Relea se but Dur ing the De signated S upport Per iod
	301	If a decis ion to bac k out is m ade after national r elease and within th e designat ed support period, a new patch will be e ntered int o the NPM in Forum a nd will go through a ll the nec essary mil estone rev iews, etc. as a patc h for a pa tch. This patch coul d be defin ed as an e mergency p atch, and it could b e used to address sp ecific iss ues pertai ning to th e original patch or it could b e used to restore th e build co mponents t o their or iginal pre -patch con dition.
	302	After Nati onal Relea se and War ranty Peri od
	303	After the support pe riod, the VistA Main tenance Pr ogram will produce t he new pat ch, either to correc t the defe ctive comp onents or restore th e build co mponents t o their or iginal pre -patch con dition.
	304	Back-Out C onsiderati ons
	305	Changes im plemented with multi -build BPS IB PSO BU NDLE 11.0 can be bac ked out in their ent irety or o n an enhan cement-by- enhancemen t basis. E ither coul d be accom plished vi a a new ve rsion of m ulti-build BPS IB PS O BUNDLE 1 1.0 if bef ore nation al release or a new multi-buil d if after national release.
	306	Load Testi ng
	307	N/A. The b ack-out pr ocess will be execut ed at norm al rather than raise d job prio rity 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 wil l be uncha nged.
	308	User Accep tance Test ing
	309	Below are the accept ance crite ria for ea ch story i ncluded in BPS IB PS O BUNDLE 1 1.0.
	310
	311	US19
	312	VistA ECME stores pe rmanent ph armacy cla im data us ing correc t field si zes as man dated by t he HIPAA N CPDP stand ard.
	313	VistA ECME sends pha rmacy clai m data usi ng correct field siz es as mand ated by th e HIPAA NC PDP standa rd.
	314	The follow ing screen s have bee n modified to displa y correct field leng ths for Na me of Insu red, Group Number, G roup Name, and Subsc riber ID:
	315	Match Mult iple Group Plans Opt ion [IBCNR GROUP PLA N MATCH]
	316	Match Grou p Plan to a Pharmacy Option [I BCNR PLAN MATCH]
	317	Third Part y Payer Re jects – Vi ew/Process [PSO REJE CTS VIEW/P ROCESS] (R eject Noti fication S creen)
	318	Third Part y Payer Re jects - Wo rklist [PS O REJECTS WORKLIST] (Reject No tification Screen)
	319	The follow ing report s have bee n modified to displa y correct field leng ths for Na me of Insu red, Group Number, G roup Name, and Subsc riber ID:
	320	Group Plan Worksheet Report [I BCNR GROUP PLAN WORK SHEET]
	321	Rejected C laims Repo rt [BPS RP T REJECTIO N]
	322	Closed Cla ims Report [BPS RPT CLOSED CLA IMS]
	323	Payable Cl aims Repor t [BPS RPT PAYABLE]
	324	Reversal C laims Repo rt [BPS RP T REVERSAL ]
	325	Claims Sub mitted, No t Yet Rele ased [BPS RPT NOT RE LEASED]
	326	Recent Tra nsactions [BPS RPT R ECENT TRAN SACTIONS]
	327	File IB NC PDP EVENT LOG popula tes with t he correct informati on before and after the instal lation of patch IB2 .0497 for the follo wing field s:
	328	GROUP ID ( .06)
	329	CARDHOLDER ID (.07)
	330	CARDHOLDER FIRST NAM E (.101)
	331	CARDHOLDER LAST NAME (.102)
	332	GROUP NAME (.301)
	333
	334	US124
	335	Fill a pre scription for a pati ent with T RICARE eli gibility, primary OH I insuranc e and TRIC ARE Expres s Scripts secondary coverage. The prima ry claim w ill transm it automat ically if the insura nce file i s set up c orrectly. Use the t esting too l to make the primar y claim pa yable and to add an amount for PATIENT P AY AMOUNT. Bill the TRICARE s econdary c overage us ing the PR O option. The PRO o ptions sho w the corr ect inform ation, the secondary transacti on populat ed with th e correct primary cl aim inform ation in t he COB fie lds (liste d above) a nd the inf ormation i s stored i n VistA. Use CRI Cl aim Respon se Inquiry to verify informati on is stor ed in Vist A.
	336	Fill a pre scription for a pati ent with T RICARE eli gibility, primary OH I insuranc e and TRIC ARE Expres s Scripts secondary coverage. The prima ry claim w ill transm it automat ically if the insura nce file i s set up c orrectly. Close the primary c laim on th e ECME Use r Screen. Bill the TRICARE se condary co verage usi ng the PRO option. The PRO op tion shows the corre ct informa tion, the secondary transactio n populate d with the correct i nformation from the primary cl aim in the COB field s (listed above) and the infor mation is stored in VistA. Use CRI Claim Response Inquiry to verify in formation is stored in VistA.
	337	VistA stor es the Pat ient Pay A mount. Us e CRI Clai m Response Inquiry t o verify i nformation is stored in VistA.
	338	The Patien t Pay Amou nt is avai lable in t he ePharma cy testing tool.
	339	RES Resubm it with Ed its on the ECME User screen sh ow the cor rect infor mation for a seconda ry claim, the second ary transa ction is p opulated w ith the co rrect prim ary claim informatio n in the C OB fields and the in formation is stored in VistA. Use CRI Cl aim Respon se Inquiry to verify informati on is stor ed in Vist A.
	340
	341	US170
	342	Comments e ntered fro m the Reje ct Informa tion scree n are disp layed in t he ECME Lo g of View Prescripti on.
	343	All commen ts, includ ing those made using the COM Add Commen ts action displayed in the ECM E Log of V iew Prescr iption, co ntinue to display al l existing details a ssociated with comme nts (e.g. date/time stamp, Ref ill number , Initiato r of Activ ity, etc.) . Please see screen shot incl uded in th e conversa tion for h ow the com ments shou ld appear in the ECM E Log.
	344	The types of comment s currentl y displaye d in the E CME Log co ntinue to display as they do n ow.
	345
	346	US399
	347	Enhance th e RED Resu bmit Claim w/Edits a ction on t he ECME Us er screen to prompt for NCPDP fields tha t are not on a payer sheet and that are not stubs.
	348	Data in th e transact ion reflec ts the val ues of the fields se lected by the user.
	349	"^" will a llow the u ser to lea ve the act ion and re turn to th e main scr een.
	350	A comment is stored in the ECM E log with wording f rom the fu nctional d esign.
	351	The activi ty log com ment can b e 100 char acters.
	352
	353	US433
	354	Label beha vior match es the tab le for the following functiona lity:
	355	Medication Profile, Action ED Edit
	356	Worklist, Action ED Edit
	357	Edit Presc riptions [ PSO RXEDIT ]
	358
	359	Type
	360	Label Prin ted
	361	Released
	362	Prompt use r to print /reprint?
	363	CMOP, tran smitted
	364	Y
	365	Y
	366	N
	367	CMOP, tran smitted
	368	Y
	369	N
	370	N
	371	Window fil l
	372	Y
	373	N
	374	Y
	375	Window fil l
	376	Y
	377	Y
	378	N
	379	Window fil l
	380	N
	381	N
	382	Y
	383
	384	US434
	385	Label beha vior match es the tab le for the following functiona lity:
	386	Medication Profile, Action RES Resubmit
	387	Worklist, Actions RE S Resubmit , OVR Subm it Overrid e Codes, C LA Submit Clarif. Co de, PA Sub mit Prior Auth., SMA Submit Mu lt. Action s
	388
	389	Type
	390	Label Prin ted
	391	Released
	392	Prompt use r to print /reprint?
	393	CMOP, tran smitted
	394	Y
	395	Y
	396	N
	397	CMOP, tran smitted
	398	Y
	399	N
	400	N
	401	Window fil l
	402	Y
	403	N
	404	Y
	405	Window fil l
	406	Y
	407	Y
	408	N
	409	Window fil l
	410	N
	411	N
	412	Y
	413
	414	US572
	415	The follow ing filter questions have been added: P rescriber, Patient N ame, Bille d Amount.
	416	The follow ing filter questions allow sel ection of one, many or all: C MOP/Mail/W indow, Bil ling Type (Real time , etc.), R eject Code , Eligibil ity, Drug/ Drug Class , Prescrib er, Patien t.
	417	Prescriber can be se lected by name or NP I.
	418	Billed Amo unt can be selected for all am ounts or a range.
	419	Excel capt ure instru ctions hav e been rew orded as p er the fun ctional de sign.
	420	The report heading h as changed :
	421	Add Prescr iber
	422	Add Patien t
	423	Move trans action dat e to a new line
	424	The follow ing labels have a va lue of ALL or SELECT ED: Insura nce, Rejec t Code, Dr ugs/Classe s, Prescri ber, Patie nt
	425	Eligibilit y has a va lue of ALL , VET, TRI and/or CV A
	426	The report column he adings hav e changed:
	427	Remove the column he ading for DRUG (only the headi ng is remo ved, the d rug will s till displ ay)
	428	In place o f DRUG, ad d Prescrib er ID and Name
	429	The report display h as changed :
	430	Display th e Prescrib er ID and Name under the corre ct column headings
	431	Remove the Claim ID
	432	Display th e Drug nam e where th e Claim ID previousl y displaye d
	433	Shorten la bels in th e Excel fo rmat headi ng, as not ed in the chart in t he functio nal design
	434	Add labels for Presc riber ID a nd Prescri ber
	435	Remove the label for Claim ID
	436	To avoid w rapping of the Excel format, l imit the d ata line l ength to 2 55 charact ers
	437	Remove par entheses a round the Patient ID
	438	Truncate t he data fi elds as no ted in the chart in the functi onal desig n
	439	If needed, truncate the Reject Explanati on to redu ce the lin e length t o 255 char acters.
	440
	441	Non-billab le Status Report all ows select ion of one , many or all for th e Eligibil ity filter
	442
	443	US575
	444	The reject codes hav e been upd ated in fi le BPS NCP DP REJECT CODES to r eflect the codes tha t have bee n added an d renamed per the fu nctional d esign.
	445	The clarif ication co des have b een update d in file BPS NCPDP CLARIFICAT ION CODES to reflect the codes that have been adde d and rena med per th e function al design.
	446	The result of servic e codes ha ve been up dated in f ile BPS NC PDP RESULT OF SERIVI CE CODE to reflect t he codes t hat have b een rename d per the functional design.
	447	The other payer amou nt qualifi ers have b een update d in file BPS NCPDP OTHER PAYE R AMT PAID QUAL to r eflect the codes tha t have bee n added an d renamed per the fu nctional d esign.
	448	New and re named reje ct codes c an be
	449	selected i n the test ing tool
	450	received i n a claim response a nd stored in VistA w ith the cl aim respon se
	451	displayed on the ECM E User scr een and th e Pharmaci sts’ Workl ist
	452	displayed on the Rej ected Clai ms Report and Closed Claims Re port
	453	displayed on the LOG Print Cla im Log (EC ME User Sc reen)
	454	New and re named subm ission cla rification codes can be
	455	selected i n VistA fo r claim su bmission
	456	sent in a claim requ est and st ored in Vi stA with t he claim r equest
	457	displayed on the ECM E User scr een and th e Pharmaci sts’ Workl ist
	458	The new re named othe r payer am ount quali fiers can be
	459	received i n a claim response a nd stored in VistA w ith the cl aim respon se
	460
	461	US580
	462	The ECME U ser screen display m atches the user’s sa ved profil e or the u ser select ion from C V, even if the store d fill typ e is somet hing other than M or W.
	463	The follow ing report s display correct in formation even if th e stored f ill type i s somethin g other th an M or W:
	464	PAY Pay able Claim s Report
	465	REJ Rej ected Clai ms Report
	466	REV Rev ersal Clai ms Report
	467	NYR Cla ims Submit ted, Not Y et Release d
	468	REC Rec ent Transa ctions
	469	DAY Tot als by Dat e
	470	CLO Clo sed Claims Report
	471	NBS Non -Billable Status Rep ort
	472
	473	US591
	474	Acceptance Criteria refers to the follow ing prompt s in the C V Change V iew action of the EC ME User Sc reen:
	475	Select Ce rtain Phar macy (D)iv isions or (A)LL: A//
	476	Select Cer tain Eligi bility Typ e or (A)ll : A//
	477	Display On e ECME (U) ser or (A) LL: A//
	478	Display On e (P)atien t or (A)LL : A//
	479	Display On e (R)x or (A)LL: A//
	480	Display (R )ejects or (P)ayable s or (U)ns tranded or (A)LL: A/ /
	481	Display (C )MOP or (M )ail or (W )indow or (A)LL: A//
	482	Display (R )ealTime, (B)ackbill s, (P)RO O ption, Re( S)ubmissio n or (A)LL : A//
	483	Display Sp ecific (R) eject Code or (A)LL: A// REJEC T CODE
	484	All prompt s allow mu ltiple sel ections, s ingle sele ction or A LL.
	485	The system will filt er out dup licate res ponses.
	486	The system will allo w individu al entries and a sel ection of ALL.
	487	Help text is availab le.
	488
	489	US594
	490	Action MP Med Profil e are avai lable from option Vi ew ePharma cy Rx.
	491	Select act ion MP Med Profile a nd the dis played inf ormation m atched the informati on display ed in acti on MP Medi cation Pro file from the Reject Informati on screen.
	492	When scrol ling throu gh all scr eens in op tion View ePharmacy Rx, the MP Med Profi le informa tion is in the right order.
	493	The action s will not display w ith the Me d Profile action.
	494	MP Medicat ion Profil e is avail able to be printed.
	495
	496	US598
	497	New option ePharmacy Patient C omment is on the ePh armacy Men u and requ ires secur ity key PS O EPHARMAC Y SITE MAN AGER.
	498	The Add Co mment acti on will al low the us er to ente r a new pa tient bill ing commen t.
	499	The Inacti vate or Ac tivate Com ment actio n will all ow the use r to inact ivate or a ctivate an existing patient bi lling comm ent.
	500	The Commen t History action wil l display history fo r the comm ent, which includes additions, activatio ns and ina ctivations .
	501	Comments a re display ed in reve rse chrono logical or der.
	502	The Reject Informati on screen displays t he new com ments in r everse chr onological order in a new sect ion called “Comments – Patient ” and the original c omment sec tion is re named to “ Comments – Reject”.
	503	The Reject Informati on screen action of COM Add Co mments wil l allow th e user to enter a re ject comme nt or a pa tient bill ing commen t.
	504	Help text is availab le when us ing the CO M Add Comm ents actio n
	505	Patient Co mments can not be edi ted or ina ctivated f rom the CO M action.
	506	The Reject Notificat ion screen displays the patien t billing comment un der the Ca rdholder I D.
	507	Patient Co mments def ault to ac tive when entered fr om both th e option e Pharmacy P atient Com ment and t he COM Add Comments on the Rej ect Inform ation Scre en.
	508	The Patien t Comment captures, stores and displays the commen t, user, d ate and ti me.
	509	Only activ e Patient Comments a re display ed on the Reject Inf ormation S creens.
	510
	511	US599
	512	ePharmacy Site Param eters cont ains a pro mpt for Ig nore Thres hold in th e General Parameters section.
	513	The action EA Edit A ll Paramet ers and EG Edit Gene ral Parame ters inclu de the new parameter .
	514	The Ignore Threshold is not re quired and can be up date or de leted.
	515	Users can enter a va lue of 0 a nd 9999999 .
	516	The Reject Notificat ion Screen and the R eject Info rmation Sc reen will allow the user to ig nore when the thresh old has be en met or exceeded b ut only if the user holds secu rity key E PHARMACY S ITE MANAGE R.
	517	The Reject Notificat ion Screen and the R eject Info rmation Sc reen both display a message wh en IGNORE is chosen and the gr oss amount due equal s or excee ds the thr eshold.
	518
	519	US1441
	520	The ECME D evelopers Log displa ys the cla im status at the tim e of label printing.
	521	The ECME D evelopers Log displa ys the men u option a nd action (if availa ble) used to print t he label.
	522	The ECME D evelopers Log displa ys the ope n rejects on the Thi rd Party R ejects Wor klist at t he time of label pri nting.
	523
	524	US1907
	525	A new prom pt is adde d allowing the user to specify a Date Ra nge or Tim eframe
	526	Help text is availab le explain ing the di fference b etween the Date Rang e and Time frame
	527	An ‘Activi ty Date Ra nge’ promp t has been added all owing the user to en ter a date range by entering a n ‘Activit y Beginnin g Date’ an d an ‘Acti vity Endin g Date’.
	528	The timefr ame lookba ck restric tion of 99 9 days is changed to 180 days.
	529	A rule has been adde d to preve nt user fr om exceedi ng a 180-d ay date ra nge.
	530	A rule has been adde d to preve nt user fr om enterin g an end d ate that p recedes th e beginnin g date.
	531	A warning ‘Ending Da te precede s Beginnin g Date’ is displayed when the end date p recedes th e beginnin g date
	532	A warning ‘Date rang e exceeds 180 day li mit. Selec t an Endin g Date whi ch is no m ore than 1 80 days af ter the Be ginning Da te.’ if ra nge exceed s 180 days .
	533	Add functi onality: If Activit y ‘Date Ra nge’ is se lected, th en show da te range i n report h eader.
	534
	535	US3387
	536	When enter ing a new order, a C HAMPVA pat ient’s pre scription does not g enerate a label prom pt if the insurer is asleep.
	537	When enter ing a new order, a T RICARE pat ient’s pre scription does not g enerate a label prom pt if the insurer is asleep.
	538	When enter ing a new order, a V eteran pat ient’s pre scription DOES gener ate a labe l prompt i f the insu rer is asl eep which is existin g behavior .
	539
	540	US3481
	541	The defaul t value fo r the Pres criber fil ter questi on is “A”.
	542
	543	Back-Out C riteria
	544	It may be decided to back out this patch if the pr oject is c anceled, t he request ed changes implement ed by mult i-build BP S IB PSO B UNDLE 11.0 are no lo nger desir ed by VA O I&T and th e ePharmac y eBusines s team, or the patch produces catastroph ic problem s.
	545	Back-Out R isks
	546	Since the ePharmacy software i s tightly integrated with exte rnal syste ms, any at tempt at a back-out should inc lude close consultat ion with t he externa l trading partners s uch as the Financial Services Center (FS C) and the Health Ca re Clearin g House (H CCH) to de termine ri sk.
	547	Authority for Back-O ut
	548	The order would come from: rel ease coord inator (pr oduct supp ort), port folio dire ctor, and health pro duct suppo rt. The or der should be done i n consulta tion with the develo pment team and exter nal tradin g partners such as F SC and the HCCH to d etermine t he appropr iate cours e of actio n. ePharma cy is tigh tly integr ated with these exte rnal partn ers and a decision t o back-out should no t be made without th eir consul tation.
	549	Back-Out P rocedure
	550	Backing ou t enhancem ents to a VistA appl ication is often com plex. Norm ally, defe cts are re paired via a follow- up patch. The develo pment team recommend s that sit es log a t icket if t here is a nationally released patch to b e implemen ted. If no t, the sit e should c ontact the Enterpris e Program Management Office (E PMO) team directly f or specifi c solution s to their unique pr oblems.
	551
	552	Multi-buil d BPS IB P SO BUNDLE 11.0 conta ins the fo llowing bu ild compon ents:
	553	Routines
	554	File entri es in mult iple files
	555	Data Dicti onary Chan ges
	556	Protocols
	557	List Templ ates
	558	Menu Optio ns
	559
	560	While the VistA KIDS installat ion proced ure allows the insta ller to ba ck up the modified r outines us ing the ‘B ackup a Tr ansport Gl obal’ acti on, the ba ck-out pro cedure for global, d ata dictio nary and o ther VistA component s is more complex an d requires issuance of a follo w-up patch to ensure all compo nents are properly r emoved and /or restor ed. All so ftware com ponents (r outines an d other it ems) must be restore d to their previous state at t he same ti me and in conjunctio n with the restorati on of the data.
	561
	562	Please con tact the E PMO team f or assista nce since this insta lled patch contains components in additi on to rout ines.
	563	Back-out V erificatio n Procedur e
	564	Successful back-out is confirm ed by veri fication t hat the ba ck-out pat ch was suc cessfully installed.
	565	Rollback P rocedure
	566	Rollback p ertains to data. The data chan ges in thi s patch ar e specific to the op erational software a nd platfor m settings . These da ta changes are cover ed in the Back-out p rocedures detailed e lsewhere i n this doc ument.
	567	Rollback C onsiderati ons
	568	Not applic able.
	569	Rollback C riteria
	570	Not applic able.
	571	Rollback R isks
	572	Not applic able.
	573	Authority for Rollba ck
	574	Not applic able.
	575	Rollback P rocedure
	576	Not applic able.
	577	Rollback V erificatio n Procedur e
	578	Not applic able.
	579
	580
	581	Template R evision Hi story
	582	Date
	583	Version
	584	Descriptio n
	585	Author
	586	March 2016
	587	2.2
	588	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.
	589	VIP Team
	590	February 2 016
	591	2.1
	592	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
	593	OI&T Docum entation S tandards C ommittee
	594	December 2 015
	595	2.0
	596	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.
	597	OI&T Docum entation S tandards C ommittee
	598	February 2 015
	599	1.0
	600	Initial Dr aft
	601	Lifecycle and Releas e Manageme nt