1. EPMO Open Source Coordination Office Redaction File Detail Report

Produced by Araxis Merge on 9/19/2018 12:09:29 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	ePharmacy_Bundle 12.zip	bps_1_0_p24_ig.docx	Wed Sep 12 15:14:00 2018 UTC
2	ePharmacy_Bundle 12.zip	bps_1_0_p24_ig.docx	Thu Sep 13 16:08:05 2018 UTC

1.2 Comparison summary

Description	Between Files 1 and 2
Description	Text Blocks	Lines
Unchanged	2	1082
Changed	1	2
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 5 & 6
	2	Electronic Claims Ma nagement E ngine BPS* 1.0*24
	3	Outpatient Pharmacy PSO7.051 2
	4	Integrated Billing I B2.0617
	5	Pharmacy D ata Manage ment PSS1 .0214
	6
	7	Deployment , Installa tion, Back -Out, and Rollback G uide
	8	Version 1. 0
	9
	10
	11	November 2 018
	12	Department of Vetera ns Affairs
	13	Office of Informatio n and Tech nology (OI &T)
	14
	15
	16	Revision H istory
	17	Date
	18	Version
	19	Descriptio n
	20	Author
	21	November 2 018
	22	1.0
	23	Initial Ve rsion
	24	PII
	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 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	This patch is intend ed for a f ully patch ed VistA s ystem.1
	39	2Roles and Responsib ilities1
	40	3Deploymen t2
	41	3.1Timelin e2
	42	3.2Site Re adiness As sessment3
	43	3.2.1Deplo yment Topo logy (Targ eted Archi tecture)3
	44	3.2.2Site Informatio n (Locatio ns, Deploy ment Recip ients)3
	45	3.2.3Site Preparatio n3
	46	3.3Resourc es3
	47	3.3.1Facil ity Specif ics3
	48	3.3.2Hardw are3
	49	3.3.3Softw are4
	50	3.3.4Commu nications4
	51	3.3.4.1Dep loyment/In stallation /Back-Out Checklist4
	52	4Installat ion5
	53	4.1Pre-ins tallation and System Requireme nts5
	54	4.2Platfor m Installa tion and P reparation 5
	55	4.3Downloa d and Extr act Files5
	56	4.4Databas e Creation 5
	57	4.5Install ation Scri pts5
	58	4.6Cron Sc ripts6
	59	4.7Access Requiremen ts and Ski lls Needed for the I nstallatio n6
	60	4.8Install ation Proc edure6
	61	4.9Install ation Veri fication P rocedure6
	62	4.10System Configura tion6
	63	4.11Databa se Tuning6
	64	5Back-Out Procedure6
	65	5.1Back-Ou t Strategy 6
	66	5.1.1Mirro r Testing or Site Pr oduction T esting7
	67	5.1.2After National Release bu t During t he Designa ted Suppor t Period7
	68	5.1.3After National Release an d Warranty Period7
	69	5.2Back-Ou t Consider ations7
	70	5.2.1Load Testing7
	71	5.2.2User Acceptance Testing7
	72	5.3Back-Ou t Criteria 12
	73	5.4Back-Ou t Risks12
	74	5.5Authori ty for Bac k-Out12
	75	5.6Back-Ou t Procedur e13
	76	5.7Back-ou t Verifica tion Proce dure13
	77	6Rollback Procedure1 3
	78	6.1Rollbac k Consider ations13
	79	6.2Rollbac k Criteria 13
	80	6.3Rollbac k Risks13
	81	6.4Authori ty for Rol lback14
	82	6.5Rollbac k Procedur e14
	83	6.6Rollbac k Verifica tion Proce dure14
	84
	85	Table of T ables
	86	Table 1: D eployment, Installat ion, Back- out, and R ollback Ro les and Re sponsibili ties1
	87	Table 2: S ite Prepar ation3
	88	Table 3: F acility-Sp ecific Fea tures3
	89	Table 4: H ardware Sp ecificatio ns4
	90	Table 5: S oftware Sp ecificatio ns4
	91	Table 6: D eployment/ Installati on/Back-Ou t Checklis t5
	92
	93
	94
	95	Introducti on
	96	This docum ent descri bes how to deploy an d install the multi- build BPS PSO IB PSS BUNDLE 12 .0 (which includes B PS1.024, PSO7.05 12, IB2.0 617, PSS* 1.0*214) a nd how to back-out t he product and rollb ack to a p revious ve rsion or d ata set.
	97	Purpose
	98	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 PSO IB PSS BUNDLE 12 .0 (which includes B PS1.024, PSO7.05 12, IB2.0 617, PSS* 1.0*214) w ill be dep loyed and installed, as well a s how it i s to be ba cked out a nd rolled back, if n ecessary. The plan i dentifies resources, communica tions plan , and roll out schedu le. Specif ic instruc tions for installati on, back-o ut, and ro llback are included in this do cument.
	99	Dependenci es
	100	BPS1.023 must be i nstalled B EFORE BPS* 1.0*24.
	101	PSO7.040 8, PSO7.0 467 and P SO7.0482 must be i nstalled B EFORE PSO* 7*512.
	102	IB2.0550 must be i nstalled B EFORE IB2 .0617.
	103	PSS1.021 3 must be installed BEFORE PSS 1.0214.
	104	Constraint s
	105	This patch is intend ed for a f ully patch ed VistA s ystem.
	106	Roles and Responsibi lities
	107	Table 1: D eployment, Installat ion, Back- out, and R ollback Ro les and Re sponsibili ties
	108	ID
	109	Team
	110	Phase / Ro le
	111	Tasks
	112	Project Ph ase (See S chedule)
	113	1
	114	VA OI&T, V A OI&T Hea lth Produc t Support, and PMO ( Leidos)
	115	Deployment
	116	Plan and s chedule de ployment ( including orchestrat ion with v endors)
	117	Planning
	118	2
	119	Local VAMC and CPAC processes
	120
	121
	122	Deployment
	123	Determine and docume nt the rol es and res ponsibilit ies of tho se involve d in the d eployment.
	124	Planning
	125	3
	126	Field Test ing (Initi al Operati ng Capabil ity - IOC) , Health P roduct Sup port Testi ng & VIP R elease Age nt Approva l
	127	Deployment
	128	Test for o perational readiness
	129	Testing
	130	4
	131	Health pro duct Suppo rt and Fie ld Operati ons
	132	Deployment
	133	Execute de ployment
	134	Deployment
	135	5
	136	Individual Veterans Administra tion Medic al Centers (VAMCs)
	137	Installati on
	138	Plan and s chedule in stallation
	139	Deployment
	140	6
	141	VIP Relea se Agent
	142	Installati on
	143	Ensure aut hority to operate an d that cer tificate a uthority s ecurity do cumentatio n is in pl ace
	144	Deployment
	145	7
	146
	147	Installati on
	148	Validate t hrough fac ility POC to ensure that IT eq uipment ha s been acc epted usin g asset in ventory pr ocesses
	149	N/A; only existing V istA syste m will be used
	150	8
	151	VA’s eBusi ness team
	152	Installati ons
	153	Coordinate training
	154	Deployment
	155	9
	156	VIP releas e Agent, H ealth Prod uct Suppor t & the de velopment team
	157	Back-out
	158	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)
	159	Deployment
	160	10
	161	VA OI&T, V A OI&T Hea lth Produc t Support, and MCCF EDI TAS De velopment Team (Half aker)
	162	Post Deplo yment
	163	Hardware, Software a nd System Support
	164	Warranty
	165	Deployment
	166	The deploy ment is pl anned as a national rollout.
	167	This secti on provide s the sche dule and m ilestones for the de ployment.
	168	Timeline
	169	The durati on of depl oyment and installat ion is 30 days, as d epicted in the maste r deployme nt schedul e.
	170	Site Readi ness Asses sment
	171	This secti on discuss es the loc ations tha t will rec eive the d eployment of the mul ti-build B PS PSO IB PSS BUNDLE 12.0 (whi ch include s BPS1.0 24, PSO7. 0512, IB* 2.0617, P SS1.0*214 ).
	172	Deployment Topology (Targeted Architectu re)
	173	This multi -build BPS PSO IB PS S BUNDLE 1 2.0 (which includes BPS1.024 , PSO7.0 512, IB2. 0617, PSS 1.0214) is to be n ationally released t o all VAMC s.
	174	Site Infor mation (Lo cations, D eployment Recipients )
	175	The IOC si tes are:
	176	Birmingham
	177	Eastern Ka nsas
	178	Little Roc k
	179	Richmond
	180
	181	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.
	182	Site Prepa ration
	183	The follow ing table describes preparatio n required by the si te prior t o deployme nt.
	184	Table 2: S ite Prepar ation
	185	Site/Other
	186	Problem/Ch ange Neede d
	187	Features t o Adapt/Mo dify to Ne w Product
	188	Actions/St eps
	189	Owner
	190	N/A
	191	N/A
	192	N/A
	193	N/A
	194	N/A
	195	Resources
	196	Facility S pecifics
	197	The follow ing table lists faci lity-speci fic featur es require d for depl oyment.
	198	Table 3: F acility-Sp ecific Fea tures
	199	Site
	200	Space/Room
	201	Features N eeded
	202	Other
	203	N/A
	204	N/A
	205	N/A
	206	N/A
	207	Hardware
	208	The follow ing table describes hardware s pecificati ons requir ed at each site prio r to deplo yment.
	209	Table 4: H ardware Sp ecificatio ns
	210	Required H ardware
	211	Model
	212	Version
	213	Configurat ion
	214	Manufactur er
	215	Other
	216	Existing V istA syste m
	217	N/A
	218	N/A
	219	N/A
	220	N/A
	221	N/A
	222	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.
	223	Software
	224	The follow ing table describes software s pecificati ons requir ed at each site prio r to deplo yment.
	225	Table 5: S oftware Sp ecificatio ns
	226	Required S oftware
	227	Make
	228	Version
	229	Configurat ion
	230	Manufactur er
	231	Other
	232	Fully patc hed Electr onic Claim s Manageme nt Engine package wi thin VistA
	233	N/A
	234	1.0
	235	N/A
	236	N/A
	237	N/A
	238	Fully patc hed Integr ated Billi ng package within Vi stA
	239	N/A
	240	2.0
	241	N/A
	242	N/A
	243	N/A
	244	Fully patc hed Outpat ient Pharm acy packag e within V istA
	245	N/A
	246	7.0
	247	N/A
	248	N/A
	249	N/A
	250	Fully patc hed Pharma cy Data Ma nagement p ackage wit hin VistA
	251	N/A
	252	1.0
	253	N/A
	254	N/A
	255	N/A
	256	Prerequisi te patches in BPS, P SO, IB, PS S yet to b e determin ed
	257	N/A
	258	Nationally released version
	259	N/A
	260	N/A
	261	N/A
	262	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.
	263	Communicat ions
	264	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 .
	265
	266	Deployment /Installat ion/Back-O ut Checkli st
	267	The Releas e Manageme nt team wi ll deploy the multi- build BPS PSO IB PSS BUNDLE 12 .0, which is tracked nationall y for all VAMCs in t he Nationa l Patch Mo dule (NPM) in Forum. Forum aut omatically tracks th e patches as they ar e installe d in the d ifferent V AMC produc tion syste ms. One ca n run a re port in Fo rum to ide ntify when and by wh om the pat ch was ins talled int o the Vist A producti on at each site. A r eport can also be ru n to ident ify which sites have not curre ntly insta lled the p atch into their Vist A producti on system. Therefore , this inf ormation d oes not ne ed to be m anually tr acked in t he chart b elow.
	268
	269	Table 6: D eployment/ Installati on/Back-Ou t Checklis t
	270	Activity
	271	Day
	272	Time
	273	Individual who compl eted task
	274	Deploy
	275	N/A
	276	N/A
	277	N/A
	278	Install
	279	N/A
	280	N/A
	281	N/A
	282
	283	Installati on
	284	Pre-instal lation and System Re quirements
	285	Multi-buil d BPS PSO IB PSS BUN DLE 12.0 i s installa ble on a f ully patch ed M(UMPS) VistA sys tem and op erates on the top of the VistA environme nt provide d by the V istA infra structure packages. The latter provides utilities which comm unicate wi th the und erlying op erating sy stem and h ardware, t hereby pro viding eac h VistA pa ckage inde pendence f rom variat ions in ha rdware and operating system.
	286	Platform I nstallatio n and Prep aration
	287	Refer to t he BPS1.0 24 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.
	288	Download a nd Extract Files
	289	Refer to t he BPS1.0 24, PSO7 .0512, IB 2.0617, PSS1.021 4 document ation on t he NPM to find relat ed documen tation tha t can be d ownloaded. The patch descripti on of each patch wil l be trans mitted as a MailMan message fr om the NPM . This mes sage can a lso be pul led from t he NPM. Th e patches themselves are bundl ed togethe r into the multi-bui ld BPS PSO IB PSS BU NDLE 12.0. The host file conta ining thes e patches must be do wnloaded s eparately. The file name is BP S_1_24_PSO _IB_PSS.KI D and it c an be foun d on the A NONYMOUS.S OFTWARE di rectory on any of th e VistA SF TP servers (Hines, S alt Lake C ity).
	290	Database C reation
	291	Multi-buil d BPS PSO IB PSS BUN DLE 12.0 m odifies th e VistA da tabase. Al l changes can be fou nd on the NPM docume ntation fo r this pat ch.
	292	Installati on Scripts
	293	No install ation scri pts are ne eded for m ulti-build BPS PSO I B PSS BUND LE 12.0 in stallation .
	294	Cron Scrip ts
	295	No Cron sc ripts are needed for multi-bui ld BPS PSO IB PSS BU NDLE 12.0 installati on.
	296	Access Req uirements and Skills Needed fo r the Inst allation
	297	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.
	298	Installati on Procedu re
	299	Detailed i nstruction s for inst alling the multi-bui ld BPS PSO IB PSS BU NDLE 12.0 (which inc ludes BPS* 1.024, PS O7.0512, IB2.061 7, PSS1.0 214) can be found o n the patc h descript ion for BP S1.024, which can be found o n the NPM. Installin g the mult i-build BP S PSO IB P SS BUNDLE 12.0 will install al l four com ponent pat ches (BPS 1.024, PS O7.0512, IB2.061 7, PSS1.0 *214).
	300	Installati on Verific ation Proc edure
	301	Refer to t he BPS1.0 24 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.
	302	System Con figuration
	303	No system configurat ion change s are requ ired for t his patch.
	304	Database T uning
	305	No reconfi guration o f the Vist A database , memory a llocations or other resources is necessa ry.
	306	Back-Out P rocedure
	307	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 .
	308	Back-Out S trategy
	309	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 du ring which the decis ion is mad e.
	310	Mirror Tes ting or Si te Product ion Testin g
	311	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.
	312	After Nati onal Relea se but Dur ing the De signated S upport Per iod
	313	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.
	314	After Nati onal Relea se and War ranty Peri od
	315	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.
	316	Back-Out C onsiderati ons
	317	Changes im plemented with multi -build BPS PSO IB PS S BUNDLE 1 2.0 can be backed ou t in their entirety or on an e nhancement -by-enhanc ement basi s. Either could be a ccomplishe d via a ne w version of multi-b uild BPS P SO IB PSS BUNDLE 12. 0 if befor e national release o r a new mu lti-build if after n ational re lease.
	318	Load Testi ng
	319	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. After the reversion, the perfo rmance dem ands on th e system w ill be unc hanged.
	320	User Accep tance Test ing
	321	Below are the accept ance crite ria for ea ch story i ncluded in BPS PSO I B PSS BUND LE 12.0.
	322
	323	US177
	324	Add new hi dden actio n of ECS E dit Claim Submitted to the Rej ect Inform ation scre en and OP Medication screen (a vailable o n both Thi rd Party P ayer Rejec ts - Workl ist and Th ird Party Payer Reje cts - View /Process).
	325	The new EC S Edit Cla im Submitt ed action can be use d for both rejected and payabl e claims.
	326	Prompt for the Date of Service , only for released prescripti ons.
	327	Date of Se rvice will allow use rs to ente r the date of servic e from the original transactio n (the 'cu rrent' dat e from whe n the clai m transmit ted) or th e release date when the prescr iption is released.
	328	Prompt for NCPDP fie lds that a re not on a payer sh eet and th at are not stubs.
	329	Data in th e transact ion reflec ts the val ue entered by the us er.
	330	"^" will a llow the u ser to lea ve the act ion and re turn to th e main scr een.
	331	A date of service ov erride dis plays in t he ECME lo g.
	332
	333	US211
	334	Pharmacist can enter informati on from an y action f or a TRICA RE dual-el igible pat ient from the Third Party Paye r Rejects – Worklist . The cla im transmi ts.
	335	Pharmacist can enter informati on from an y action f or a CHAMP VA dual-el igible pat ient from the Third Party Paye r Rejects – Worklist . The cla im transmi ts.
	336	Pharmacist can enter informati on from an y action f or a TRICA RE dual-el igible pat ient from the Third Party Paye r Rejects - View/Pro cess optio n. The cl aim transm its.
	337	Pharmacist can enter informati on from an y action f or a CHAMP VA dual-el igible pat ient from the Third Party Paye r Rejects - View/Pro cess optio n. The cl aim transm its.
	338	When the T RICARE dua l-eligible claim is resubmitte d using an y action f rom the re ject infor mation scr een, the c oordinatio n of benef it (e.g. p rimary or secondary) , Rate Typ e and insu rance comp any on the resubmitt ed claim s hould be t he same as what was selected w hen the pr evious cla im was sub mitted.
	339	When the C HAMPVA dua l-eligible claim is resubmitte d using an y action f rom the re ject infor mation scr een, the c oordinatio n of benef it (e.g. p rimary or secondary) , Rate Typ e and insu rance comp any on the resubmitt ed claim s hould be t he same as what was selected w hen the pr evious cla im was sub mitted.
	340	Verify tha t this cha nge does n ot affect the OP Med ications s creen.
	341
	342	US582
	343	In the act ivity log section of View Pres cription, the ECME L og label o f “BILLING QUANTITY submitted” is replac ed with “Q UANTITY SU BMITTED ON CLAIM”.
	344	On the cla im log, ac cessed fro m the ECME User Scre en action of LOG, th e label of “NCPDP Qt y” is repl aced with “Quantity Submitted on Claim”.
	345	On the cla im log, ac cessed fro m the ECME User Scre en action of LOG, th e label of “Billed Q ty” is rep laced with “Rx Qty”.
	346	Verify the quantity submitted on the cla im is calc ulated cor rectly (re gression t esting of current fu nctionalit y).
	347
	348	US584
	349	The help t ext below the select ion of the bingo boa rd display refers to “a locall y filled o r CMOP Rx” .
	350	The help t ext for ac tion EA Ed it All Par ameters, b efore the prompt “TR ANSFER REJ ECT CODE:” , refers t o “a local ly filled or CMOP Rx ”.
	351	The help t ext for ac tion ET Ed it Transfe r Reject C ode, befor e the prom pt “TRANSF ER REJECT CODE:”, re fers to “a locally f illed or C MOP Rx”.
	352
	353	US586
	354	The PRESCR IPTION fil ter questi on for opt ion Third Party Paye r Rejects – View/Pro cess [PSO REJECTS VI EW/PROCESS ] will acc ept an ECM E number w ith a pref ix of “E.” or “e.”. The next t hree accep tance crit eria refer to the sa me prescri ption filt er questio n.
	355	The ECME n umber is a cceptable with or wi thout lead ing zeros.
	356	An entry o f “?” or “ ??” displa ys help te xt that ma tches the help text for option View ePha rmacy Rx [ BPS RPT VI EW ECME RX ].
	357	Model the display of any error message a fter optio n View ePh armacy Rx [BPS RPT V IEW ECME R X].
	358	The option Third Par ty Payer R ejects – V iew/Proces s [PSO REJ ECTS VIEW/ PROCESS] d isplays th e correct prescripti on number that match es the ECM E number e ntered by the user.
	359
	360	US597
	361	The menu o ption is n amed ROC R e Open CLO SED/Resubm it Claim.
	362	The patien t name pro mpt is rew orded to i nclude pre scription number.
	363	The patien t/prescrip tion promp t accepts all previo us formats in additi on to one or many pr escription numbers.
	364	The screen display m atches the functiona l design.
	365	A new acti on of RES Resubmit C laim is av ailable an d behaves like the a ction on t he ECME Us er screen.
	366	The RE Reo pen Claim action all ows multi- selection.
	367
	368	US601
	369	The wordin g of the i nformation al line an d prompt f or OCN Ope n/Close No n-Billable Entry ref lect the p ossibility of multip le selecti on.
	370	A user is able to se lect a ran ge of entr ies.
	371	A user is able to se lect comma separated entries.
	372	A user is able to se lect a com bination o f ranges a nd comma s eparated e ntries.
	373	A user is able to se lect a sin gle entry.
	374
	375	US1668
	376	In option Lookup int o Dispense Drug File [PSS LOOK ], the val ue for NCP DP QUANTIT Y MULTIPLI ER display s up to fi ve decimal places.
	377
	378	US2540
	379	Insert an additional line with Matched b y, and the date and time the p lan was ma tched or d eleted inf ormation.
	380
	381	US2542
	382	The label of “Insura nce:” and the insura nce name d isplays un der the pr escription number.
	383	The label of “Reject :” display s under th e label of “Insuranc e:”.
	384	Ignored re jects disp lay with t he label o f “Reject: ” and each reject co de is on a separate line. The reject co de and des cription a re display ed.
	385
	386	US2601
	387	The follow ing filter questions have been added: Patient Na me, Billed Amount.
	388	The follow ing filter questions allow sel ection of one, many or all: C MOP/Mail/W indow, Bil ling Type (Real time , etc.), E ligibility , Drug/Dru g Class, P atient Nam e.
	389	Billed Amo unt can be selected for all am ounts or a range.
	390	The report displays informatio n that mat ches the a nswers to the filter questions .
	391	The report heading h as changed : the fol lowing lab els have a value of ALL or SEL ECTED: Ins urance and Drugs/Cla sses.
	392	Excel capt ure instru ctions hav e been rew orded as p er the fun ctional de sign.
	393	In the Exc el version , the foll owing head ings have been abbre viated as per functi onal desig n: Eligibi lity, Rele ased On, F ill Locati on, Fill T ype, Rx CO B, VA Ingr edient Cos t, VA Disp ensing Fee , and Pati ent Name.
	394	In the Exc el version , remove t he parenth eses aroun d the Pati ent ID.
	395	In the Exc el version , truncate the follo wing field s: Divisio n(12), Ins urance Nam e(21), Pat ient Name( 13), Patie nt ID(4), and Drug(1 5).
	396
	397	US2603
	398	The follow ing filter questions have been added: Patient Na me and Bil led Amount .
	399	The follow ing filter questions allow sel ection of one, many or all: C MOP/Mail/W indow, Bil ling Type (Real time , etc.), E ligibility , Drug/Dru g Class, a nd Patient Name.
	400	Billed Amo unt can be selected for all am ounts or a range.
	401	The report displays informatio n that mat ches the a nswers to the filter questions .
	402	The report heading h as changed . The fol lowing lab els have a value of ALL or SEL ECTED: Ins urance and Drugs/Cla sses.
	403	Excel capt ure instru ctions hav e been rew orded as p er the fun ctional de sign.
	404	In the Exc el version , the foll owing head ings have been abbre viated as per functi onal desig n: Eligibi lity, Rele ased On, F ill Locati on, Fill T ype, Rx CO B, VA Ingr edient Cos t, VA Disp ensing Fee , and Pati ent Name.
	405	In the Exc el version , remove t he parenth eses aroun d the Pati ent ID.
	406	In the Exc el version , truncate the follo wing field s: Divisio n(12), Ins urance Nam e(21), Pat ient Name( 13), Patie nt ID(4), and Drug(1 5).
	407	In the Exc el version , evaluate the lengt h of the l ine after truncating specified values. If the len gth exceed s 255 char acters, tr uncate the Reason fi eld to red uce the li ne length to 255 cha racters.
	408
	409	US2604
	410	The follow ing filter questions have been added: Patient Na me, and Bi lled Amoun t.
	411	The follow ing filter questions allow sel ection of one, many or all: C MOP/Mail/W indow, Bil ling Type (Real time , etc.), E ligibility , Drug/Dru g Class, a nd Patient Name.
	412	Billed Amo unt can be selected for all am ounts or a range.
	413	The report heading h as changed : the fol lowing lab els have a value of ALL or SEL ECTED: Ins urance, Pa tient Name , and Drug s/Classes.
	414	The report heading h as been ch anged to i nclude ELI G as a col umn headin g and the data displ ays on the report.
	415	Excel capt ure instru ctions hav e been rew orded as p er the fun ctional de sign.
	416	In the Exc el version , the foll owing head ings have been abbre viated as per functi onal desig n: Fill Lo cation, Fi ll Type, R x COB, VA Ingredient Cost, VA Dispensing Fee, and Patient Na me.
	417	In the Exc el version , remove t he parenth eses aroun d the Pati ent ID.
	418	The Excel version ha s been cha nged to in clude ELIG as a colu mn heading and the d ata displa ys on the report.
	419	In the Exc el version , truncate the follo wing field s: Divisio n(12), Ins urance Nam e(21), Pat ient Name( 13), Patie nt ID(4), and Drug(1 5).
	420
	421	US2607
	422	The follow ing filter question has been a dded: Pa tient Name .
	423	The follow ing filter questions allow sel ection of one, many or all: C MOP/Mail/W indow, Bil ling Type (Real time , etc.), E ligibility , Drug/Dru g Class, P atient, an d Closed C laim Reaso n.
	424	The report displays informatio n that mat ches the a nswers to the filter questions .
	425	Excel capt ure instru ctions hav e been rew orded as p er the fun ctional de sign.
	426	An informa tional mes sage has b een added above the Excel capt ure questi on.
	427	The report heading h as changed . The fol lowing lab els have a value of ALL or SEL ECTED: Ins urance, Cl osed Claim Reason, D rugs/Class es, Patien t Name.
	428	Excel capt ure instru ctions hav e been rew orded as p er the fun ctional de sign.
	429	In the Exc el version , the foll owing head ings have been abbre viated as per functi onal desig n: Eligibi lity, Fill Location, Fill Type , and Pati ent Name.
	430	In the Exc el version , remove C ardholder ID from th e column h eading and the data.
	431	In the Exc el version , remove R eject Code s from the column he ading and replace wi th MULT RE J. The da ta changes to Y or N depending on whethe r there ar e multiple rejects.
	432	In the Exc el version , remove t he parenth eses aroun d the Pati ent ID.
	433	In the Exc el version , truncate the follo wing field s: Divisio n(12), Ins urance Nam e(21), Pat ient Name( 13), Patie nt ID(4), and Drug(1 5).
	434	In the Exc el version , evaluate the lengt h of the l ine after truncating specified values. If the len gth exceed s 255 char acters, tr uncate the Reject Ex planation to reduce the line l ength to 2 55 charact ers.
	435
	436	US2608
	437	The follow ing filter questions have been added: Patient Na me, and Bi lled Amoun t.
	438	The follow ing filter questions allow sel ection of one, many or all: C MOP/Mail/W indow, Eli gibility, Drug/Drug Class, and Patient N ame.
	439	Billed Amo unt can be selected for all am ounts or a range.
	440	The report heading h as changed . The fol lowing lab els have a value of ALL or SEL ECTED: Ins urance, Pa tient Name , and Drug s/Classes.
	441	Eligibilit y and Pati ent Name h ave been a dded to th e report h eading.
	442	Excel capt ure instru ctions hav e been rew orded as p er the fun ctional de sign.
	443	In the Exc el version , the foll owing head ings have been abbre viated as per functi onal desig n: Eligibi lity, Fill Location and Patien t Name.
	444	In the Exc el version , remove t he parenth eses aroun d the Pati ent ID.
	445	In the Exc el version , truncate the follo wing field s: Divisio n(12), Ins urance Nam e(21), Pat ient Name( 13), Patie nt ID(4), and Drug(1 5).
	446
	447	US2823
	448	The NPI nu mber displ ays for al l Pharmacy claims in TPJI, in the Claim Informatio n section of the Cla im Informa tion scree n.
	449
	450	US3529
	451	New fields are in Vi stA file B PS NCPDP F IELD DEFS #9002313.9 1.
	452	Updated fi elds have the correc t name in VistA file BPS NCPDP FIELD DEF S #9002313 .91.
	453	Developed fields can be transm itted on a n outgoing claim.
	454	TPJI displ ays the ad ditional f ield.
	455	The reject informati on screen displays a dditional fields.
	456	The ECME U ser Screen claim log displays additional fields.
	457	The testin g tool all ows a test er to spec ify values for addit ional fiel ds.
	458	New incomi ng claim r esponse fi elds are s tored in V istA and c an be view ed via CRI .
	459
	460
	461	US3682
	462	If enterin g a new it em or edit ing an exi sting item and the e Pharmacy B illable fi eld is not marked, p rovide a m essage whe n exiting the option , – The eP harmacy Bi llable fie ld is not marked. e Pharmacy c laims will not be bi lled if no t marked. Do you wi sh to mark it? Yes/N o. If yes the user would be t aken back to the ePh armacy Bil lable fiel d.
	463
	464	US3918
	465	Functional RPC devel opment com plete.
	466	Completed integratio n smoke te st with Vi stA Link b y Product developers .
	467	Completed performanc e benchmar ks against VistA rep ort.
	468
	469	US3969
	470	A new prom pt asks th e user to select by patient na me or by p rescriptio n number.
	471	The patien t prompt a ccepts all previous formats.
	472	The prescr iption pro mpt accept s the pres cription n umber or E CME number preceded by “E.”.
	473	The screen display m atches the user stor y examples .
	474
	475	US4039
	476	The prompt for Drug/ Drug Class will allo w a drug t o be delet ed.
	477	The prompt for Drug/ Drug Class will allo w a drug c lass to be deleted.
	478	The prompt for Rejec t Codes wi ll allow a reject co de to be d eleted.
	479	The prompt for Presc ribers wil l allow a prescriber to be del eted.
	480	The prompt for Patie nts will a llow a pat ient to be deleted.
	481	The prompt for Close Claim Rea son will a llow a clo se claim r eason to b e deleted.
	482
	483
	484	Back-Out C riteria
	485	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 PSO IB P SS BUNDLE 12.0 are n o longer d esired by VA OI&T an d the ePha rmacy eBus iness team , or the p atch produ ces catast rophic pro blems.
	486	Back-Out R isks
	487	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.
	488	Authority for Back-O ut
	489	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.
	490	Back-Out P rocedure
	491	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 backed o ut, or sit es could c ontact the Enterpris e Program Management Office (E PMO) team directly f or specifi c solution s to their unique pr oblems.
	492
	493	Multi-buil d BPS PSO IB PSS BUN DLE 12.0 c ontains th e followin g build co mponents:
	494	Routines
	495	File entri es in mult iple files
	496	Data Dicti onary Chan ges
	497	Protocols
	498	List Templ ates
	499	Menu Optio ns
	500
	501	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.
	502
	503	Please con tact the E PMO team f or assista nce since this insta lled patch contains components in additi on to rout ines.
	504	Back-out V erificatio n Procedur e
	505	Successful back-out is confirm ed by veri fication t hat the ba ck-out pat ch was suc cessfully installed.
	506	Rollback P rocedure
	507	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.
	508	Rollback C onsiderati ons
	509	Not applic able.
	510	Rollback C riteria
	511	Not applic able.
	512	Rollback R isks
	513	Not applic able.
	514	Authority for Rollba ck
	515	Not applic able.
	516	Rollback P rocedure
	517	Not applic able.
	518	Rollback V erificatio n Procedur e
	519	Not applic able.
	520
	521
	522	Template R evision Hi story
	523	Date
	524	Version
	525	Descriptio n
	526	Author
	527	March 2016
	528	2.2
	529	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.
	530	VIP Team
	531	February 2 016
	532	2.1
	533	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
	534	OI&T Docum entation S tandards C ommittee
	535	December 2 015
	536	2.0
	537	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.
	538	OI&T Docum entation S tandards C ommittee
	539	February 2 015
	540	1.0
	541	Initial Dr aft
	542	Lifecycle and Releas e Manageme nt