2. EPMO Open Source Coordination Office Redaction File Detail Report

Produced by Araxis Merge on 8/4/2017 8:56:44 AM Eastern 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.

2.1 Files compared

#	Location	File	Last Modified
1	IB_2.0_577.zip	ib_2_0_p577_ig.docx	Tue Aug 1 17:53:50 2017 UTC
2	IB_2.0_577.zip	ib_2_0_p577_ig.docx	Fri Aug 4 11:38:50 2017 UTC

2.2 Comparison summary

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

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

2.4 Active regular expressions

No regular expressions were active.

2.5 Comparison detail

	1	Medical Ca re Collect ion Fund ( MCCF) Elec tronic Dat a Intercha nge (EDI) Transactio n Applicat ions Suite (TAS) eBi lling Buil d 2
	2	Integrated Billing I B2.0577
	3	Version 1. 0
	4	Deployment , Installa tion, Back -Out, and Rollback G uide
	5
	6
	7	June 2017
	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 2017
	18	1.0
	19	Initial Ve rsion
	20	Vito D’Ami co
	21
	22
	23
	24
	25
	26	Artifact R ationale
	27	This docum ent descri bes the De ployment, Installati on, Back-o ut, and Ro llback Pla n for new products g oing into the VA Ent erprise. T he plan in cludes inf ormation a bout syste m support, issue tra cking, esc alation pr ocesses, a nd roles a nd respons ibilities involved i n all thos e activiti es. Its pu rpose is t o provide clients, s takeholder s, and sup port perso nnel with a smooth t ransition to the new product o r software , and shou ld be stru ctured app ropriately , to refle ct particu lars of th ese proced ures at a single or at multipl e location s.
	28	Per the Ve teran-focu sed Integr ated Proce ss (VIP) G uide, the Deployment , Installa tion, Back -out, and Rollback P lan is req uired to b e complete d prior 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)2
	44	3.2.3Site Preparatio n3
	45	3.3Resourc es3
	46	3.3.1Facil ity Specif ics3
	47	3.3.2Hardw are3
	48	3.3.3Softw are4
	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 n6
	59	4.8Install ation Proc edure6
	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.1.1Mirro r Testing or Site Pr oduction T esting7
	66	5.1.2After National Release bu t During t he Designa ted Suppor t Period7
	67	5.1.3After National Release an d Warranty Period7
	68	5.2Back-Ou t Consider ations7
	69	5.2.1Load Testing7
	70	5.2.2User Acceptance Testing7
	71	Back-Out C riteria9
	72	5.3Back-Ou t Risks9
	73	5.4Authori ty for Bac k-Out9
	74	5.5Back-Ou t Procedur e9
	75	5.6Back-ou t Verifica tion Proce dure10
	76	6Rollback Procedure1 0
	77	6.1Rollbac k Consider ations10
	78	6.2Rollbac k Criteria 10
	79	6.3Rollbac k Risks10
	80	6.4Authori ty for Rol lback10
	81	6.5Rollbac k Procedur e10
	82	6.6Rollbac k Verifica tion Proce dure10
	83
	84	Table of T ables
	85	Table 1: D eployment, Installat ion, Back- out, and R ollback Ro les and Re sponsibili ties1
	86	Table 2: T EST Site P reparation 3
	87	Table 3: S ite Prepar ation3
	88	Table 4: F acility-Sp ecific Fea tures3
	89	Table 5: H ardware Sp ecificatio ns4
	90	Table 6: S oftware Sp ecificatio ns4
	91	Table 7: 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 IB2.0 577 and h ow to back -out the p roduct and rollback to a previ ous versio n or data 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 IB2.0 577 will be deploye d and inst alled, as well as ho w it is to be backed out and r olled back , if neces sary. The plan ident ifies reso urces, com munication s plan, an d rollout schedule. Specific i nstruction s for inst allation, back-out, and rollba ck are inc luded in t his docume nt.
	99	Dependenci es
	100	IB2.0407 , IB2.05 22, IB2.0 547, IB2 .0550, IB 2.0554 a nd IB2.0 576 must b e installe d before I B2.0577.
	101	Constraint s
	102	This patch is intend ed for a f ully patch ed VistA s ystem.
	103	Roles and Responsibi lities
	104	Table 1: D eployment, Installat ion, Back- out, and R ollback Ro les and Re sponsibili ties
	105	ID
	106	Team
	107	Phase / Ro le
	108	Tasks
	109	Project Ph ase (See S chedule)
	110	1
	111	VA OI&T, V A OI&T Hea lth Produc t Support & PMO (Lei dos)
	112	Deployment
	113	Plan and s chedule de ployment ( including orchestrat ion with v endors)
	114	Planning
	115	2
	116	Local VAMC and CPAC processes
	117
	118
	119	Deployment
	120	Determine and docume nt the rol es and res ponsibilit ies of tho se involve d in the d eployment.
	121	Planning
	122	3
	123	Field Test ing (Initi al Operati ng Capabil ity - IOC) , Health P roduct Sup port Testi ng & VIP R elease Age nt Approva l
	124	Deployment
	125	Test for o perational readiness
	126	Testing
	127	4
	128	Health pro duct Suppo rt and Fie ld Operati ons
	129	Deployment
	130	Execute de ployment
	131	Deployment
	132	5
	133	Individual Veterans Administra tion Medic al Centers (VAMCs)
	134	Installati on
	135	Plan and s chedule in stallation
	136	Deployment
	137	6
	138	VIP Relea se Agent
	139	Installati on
	140	Ensure aut hority to operate an d that cer tificate a uthority s ecurity do cumentatio n is in pl ace
	141	Deployment
	142	7
	143	N/A for th is patch a s we are u sing only the existi ng VistA s ystem
	144	Installati on
	145	Validate t hrough fac ility POC to ensure that IT eq uipment ha s been acc epted usin g asset in ventory pr ocesses
	146
	147	8
	148	VA’s eBusi ness team
	149	Installati ons
	150	Coordinate training
	151	Deployment
	152	9
	153	VIP releas e Agent, H ealth Prod uct Suppor t & the de velopment team
	154	Back-out
	155	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)
	156	Deployment
	157	10
	158	No changes to curren t process – we are u sing the e xisting Vi stA system
	159	Post Deplo yment
	160	Hardware, Software a nd System Support
	161	Warranty
	162	Deployment
	163	The deploy ment is pl anned as a national rollout.
	164	This secti on provide s the sche dule and m ilestones for the de ployment.
	165	Timeline
	166	The durati on of depl oyment and installat ion is 30 days, as d epicted in the maste r deployme nt schedul e.
	167	Site Readi ness Asses sment
	168	This secti on discuss es the loc ations tha t will rec eive the I B2.0577 deployment .
	169	Deployment Topology (Targeted Architectu re)
	170	This patch IB2.057 7 is to be nationall y released to all VA MCs.
	171	Site Infor mation (Lo cations, D eployment Recipients )
	172	The test s ites for I OC testing are: TBD
	173	These site s will not be define d here unt il the sit es have ea ch signed a Memorand um of Unde rstanding (MOU) and testing is complete, as someti mes a site must stop testing p rior to th e end of I OC.
	174
	175	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.
	176	Site Prepa ration
	177	The follow ing table describes preparatio n required by the “T EST” site prior to d eployment.
	178	Table 2: T EST Site P reparation
	179	Site/Other
	180	Problem/Ch ange Neede d
	181	Features t o Adapt/Mo dify to Ne w Product
	182	Actions/St eps
	183	Owner
	184	N/A
	185	Testers ne ed to obta in access to the Tes t Environm ent(s)
	186	N/A
	187	Grant the assigned t esters the necessary access to the Test Environmen t(s)
	188	N/A
	189
	190	The follow ing table describes preparatio n required by the si te prior t o deployme nt.
	191	Table 3: S ite Prepar ation
	192	Site/Other
	193	Problem/Ch ange Neede d
	194	Features t o Adapt/Mo dify to Ne w Product
	195	Actions/St eps
	196	Owner
	197	N/A
	198	N/A
	199	N/A
	200	N/A
	201	N/A
	202	Resources
	203	Facility S pecifics
	204	The follow ing table lists faci lity-speci fic featur es require d for depl oyment.
	205	Table 4: F acility-Sp ecific Fea tures
	206	Site
	207	Space/Room
	208	Features N eeded
	209	Other
	210	N/A
	211	N/A
	212	N/A
	213	N/A
	214	Hardware
	215	The follow ing table describes hardware s pecificati ons requir ed at each site prio r to deplo yment.
	216	Table 5: H ardware Sp ecificatio ns
	217	Required H ardware
	218	Model
	219	Version
	220	Configurat ion
	221	Manufactur er
	222	Other
	223	Existing V istA syste m
	224	N/A
	225	N/A
	226	N/A
	227	N/A
	228	N/A
	229	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.
	230	Software
	231	The follow ing table describes software s pecificati ons requir ed at each site prio r to deplo yment.
	232	Table 6: S oftware Sp ecificatio ns
	233	Required S oftware
	234	Make
	235	Version
	236	Configurat ion
	237	Manufactur er
	238	Other
	239	Fully patc hed Integr ated Billi ng package within Vi stA
	240	N/A
	241	2.0
	242	N/A
	243	N/A
	244	N/A
	245	IB2.0407
	246	N/A
	247	Nationally released version
	248	N/A
	249	N/A
	250	N/A
	251	IB2.0522
	252	N/A
	253	Nationally released version
	254	N/A
	255	N/A
	256	N/A
	257	IB2.0547
	258	N/A
	259	Nationally released version
	260	N/A
	261	N/A
	262	N/A
	263	IB2.0550
	264	N/A
	265	Nationally released version
	266	N/A
	267	N/A
	268	N/A
	269	IB2.0554
	270	N/A
	271	Nationally released version
	272	N/A
	273	N/A
	274	N/A
	275	IB2.0576
	276	N/A
	277	Nationally released version
	278	N/A
	279	N/A
	280	N/A
	281	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.
	282	Communicat ions
	283	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 Billing eB usiness te am, the de velopers, and produc t support personnel.
	284	Deployment /Installat ion/Back-O ut Checkli st
	285	The Releas e Manageme nt team wi ll deploy the patch IB2.0577 , which is tracked n ationally for all VA MCs in the NPM in Fo rum. Forum automatic ally track s the patc hes as the y are inst alled in t he differe nt VAMC pr oduction s ystems. On e can run a report i n Forum to identify when the p atch was i nstalled i n the Vist A producti on at each site, and by whom. A report c an also be run, to i dentify wh ich sites have not c urrently i nstalled t he patch i n their Vi stA produc tion syste m.
	286
	287	Therefore, this info rmation do es not nee d to be ma nually tra cked in th e chart be low.
	288	Table 7: D eployment/ Installati on/Back-Ou t Checklis t
	289	Activity
	290	Day
	291	Time
	292	Individual who compl eted task
	293	Deploy
	294	N/A
	295	N/A
	296	N/A
	297	Install
	298	N/A
	299	N/A
	300	N/A
	301
	302	Installati on
	303	Pre-instal lation and System Re quirements
	304	IB2.0577 , 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 the t op of the VistA envi ronment pr ovided by the VistA infrastruc ture packa ges. The l atter prov ides utili ties which communica te with th e underlyi ng operati ng system and hardwa re, thereb y providin g Integrat ed Billing independe nce from v ariations in hardwar e and oper ating syst em.
	305	Platform I nstallatio n and Prep aration
	306	Refer to t he IB2.0 577 docume ntation on the Natio nal Patch Module (NP M) in Foru m for the detailed i nstallatio n instruct ions. Thes e instruct ions would include a ny pre-ins tallation steps if a pplicable.
	307	Download a nd Extract Files
	308	Refer to t he IB2.0 577 docume ntation on the NPM t o find rel ated docum entation t hat can be downloade d. IB2.0 577 will b e transmit ted via a PackMan me ssage and can be pul led from t he NPM. It is not a host file, and there fore does not need t o be downl oaded sepa rately.
	309	Database C reation
	310	IB2.0577 modifies the VistA database. All change s can be f ound on th e NPM docu mentation for this p atch.
	311	Installati on Scripts
	312	No install ation scri pts are ne eded for I B2.0577 installati on.
	313	Cron Scrip ts
	314	No Cron sc ripts are needed for IB2.057 7 installa tion.
	315	Access Req uirements and Skills Needed fo r the Inst allation
	316	The follow ing staff will need access to the PackMa n message containing the IB2. 0577 patc h or to Fo rum’s NPM for downlo ading the nationally released IB2.0577 patch. Th e software is to be installed by the sit e’s or reg ion’s desi gnated: VA OI&T IT O PERATIONS SERVICE, E nterprise Service Li nes, Vista Applicati ons Divisi on.
	317	Installati on Procedu re
	318	Refer to t he IB2.0 577 docume ntation on the NPM f or detaile d installa tion instr uctions.
	319	Installati on Verific ation Proc edure
	320	Refer to t he IB2.0 577 docume ntation on the NPM f or specifi c and deta iled insta llation in structions . These in structions include a ny post in stallation steps if applicable . The post installat ion routin e will acc omplish th e followin g:
	321
	322	Recompile the Billin g Screen I nput Templ ates
	323	Survey the Form Type file (#35 3) to iden tify which form numb ers are be ing used a t the site . Then an email will be sent t o the MCCF EDI TAS D evelopment Team with this info rmation wh ich will b e used to determine which form numbers a re availab le for fut ure develo pment.
	324	System Con figuration
	325	No system configurat ion change s are requ ired for t his patch.
	326	Database T uning
	327	No reconfi guration o f the Vist A database , memory a llocations or other resources is necessa ry.
	328	Back-Out P rocedure
	329	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 .
	330	Back-Out S trategy
	331	Although i t is unlik ely due to care in c ollecting, elaborati ng, and de signing ap proved use r stories, followed by multipl e testing stages (De veloper Un it Testing , Componen t Integrat ion Testin g, SQA Tes ting, and User Accep tance Test ing), a ba ck-out dec ision due to major i ssues with this patc h could oc cur. A dec ision to b ack out co uld be mad e during s ite Mirror Testing, Site Produ ction Test ing or aft er Nationa l Release to the fie ld (VAMCs) . The best strategy decision i s dependen t on the s tage of te sting duri ng which t he decisio n is made.
	332	Mirror Tes ting or Si te Product ion Testin g
	333	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 will be resubm itted to t he site fo r testing. If the pa tch produc es catastr ophic prob lems, a ne w version of the pat ch can be used to re store the build comp onents to their pre- patch cond ition.
	334	After Nati onal Relea se but Dur ing the De signated S upport Per iod
	335	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 in Forum and will go th rough all the necess ary milest one review s etc. as a patch fo r a patch. It is up to VA OI&T and produ ct support whether t his new pa tch would be defined as an eme rgency pat ch or not. This new patch coul d be used to address specific issues per taining to the origi nal patch or be used to restor e the buil d componen ts to thei r original pre-patch condition .
	336	After Nati onal Relea se and War ranty Peri od
	337	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 restore t he build c omponents to their o riginal pr e-patch co ndition.
	338	Back-Out C onsiderati ons
	339	It is nece ssary to d etermine i f a wholes ale back-o ut of the patch IB2 .0577 is needed or if a bette r course o f action i s needed t o correct through a new versio n of the p atch (if p rior to na tional rel ease) or a subsequen t patch ai med at spe cific area s modified or affect ed by the original p atch (afte r national release). A wholesa le back-ou t of the p atch will still requ ire a new version (i f prior to national release) o r a subseq uent patch (after na tional rel ease). If the back-o ut is post -release o f patch IB 2.0577, this patch should be assigned status of “Entered i n Error” i n Forum’s NPM.
	340	Load Testi ng
	341	N/A. The b ack-out pr ocess woul d be execu ted at nor mal, rathe r than rai sed job pr iority, an d is expec ted to hav e no signi ficant eff ect on tot al system performanc e. Subsequ ent to the reversion , the perf ormance de mands on t he system would be u nchanged.
	342	User Accep tance Test ing
	343	Cloning a Primary Cl aim:
	344	The Copy a nd Cancel [IB COPY A ND CANCEL] option ca n be used to cancel a primary claim and create a n ew primary claim whi ch is to b e submitte d as a rep lacement c laim.
	345	If the pri mary claim (Medicare or non-Me dicare) ha s one or m ore associ ated MRAs or EOBs in VistA, th e IB syste m will not copy the COB data t o the new primary cl aim except for COB1, Piece 7 - Other Pay er Claim C ontrol Num ber (ICN). The ICN i s required for repla cement cla ims.
	346	The new pr imary clai m should b e able to be transmi tted and t here shoul d be no CO B data exc ept for th e COB1, Pi ece 7 - IC N. The MOA 1, MIA1, M IA2, CCAS, LCOB and LCAS recor ds will no t exist in the outbo und transa ction.
	347
	348	Field Leng th Adjustm ents:
	349	Up to the maximum nu mber of ch aracters s hould be a llowed to be entered in the X1 2N/005010X 222 Health Care Clai m (837) an d X12N/005 010X223 He alth Care Claim (837 ) guides f or the fie lds affect ed by the updated IB screens.
	350	VistA file s can stor e the long er data fo r the modi fied data fields of the files affected b y this cha nge.
	351	The IB sys tem should display i ndicators in front o f or after the bill numbers ap pearing on the MRW.
	352	VistA shou ld be able to transm it up to t he maximum number of character s allowed in the X12 N/005010X2 22 Health Care Claim – Profess ional (837 ) guide fo r the fiel ds affecte d by this change.
	353	VistA shou ld be able to transm it up to t he maximum number of character s allowed in the X12 N/005010X2 23 Health Care Claim - Institu tional (83 7) guide f or the fie lds affect ed by this change.
	354	VistA IB s hould not receive an y HIPAA co mpliance e rrors asso ciated wit h field si ze complia nce.
	355	The X12 83 7-I and 83 7-P transa ctions con taining up to the ma ximum fiel d sizes ar e transmit ted from F SC to the HCCH and o n to the p ayer witho ut any fie ld size co mpliance e rrors.
	356	The data e ntered in the longer data fiel ds in IB s creens and IB report s should b e viewable where it has been d etermined that there is enough room to d isplay.
	357
	358	Units or B asis for M easurement s Codes fo r Drugs:
	359	When enter ing a bill using the Enter/Edi t Billing Informatio n option, select Sec tion 4 on Screen 5, and enter a HCPCS/CP T code for a procedu re that re quires the inclusion of a Nati onal Drug Code (NDC) for the a dministrat ion of a n on-prescri ption (RX) medicatio n.
	360	An NDC sho uld be abl e to be en tered that is associ ated with the proced ure.
	361	A Unit/Bas is of Meas urement sh ould be ab le to be e ntered by accepting the defaul t value of UNITS or by enterin g a code s uch as F2, GR, ME, M L, UN or b y entering “??” at t he prompt for unit o r basis fo r measurem ent code a nd then se lecting a code.
	362	Upon enter ing the Un it/Basis o f Measurem ent, the I B system s hould prom pt for the entry of the approp riate unit (quantity ).
	363	The IB sys tem should allow the user to c omplete an d authoriz e the bill .
	364	The IB sys tem should be able t o transmit the NDC n umber, the Units/Bas is of Meas urement an d the Quan tity in PR F, Pieces 22, 23, 25 , for a Pr ofessional claim in the flat f ile.
	365	The IB sys tem should be able t o transmit the NDC n umber, the Units/Bas is of Meas urement an d the Quan tity in IN S, Pieces 15, 16, 17 , for an I nstitution al claim i n the flat file.
	366
	367	Print NDC Number on UB04:
	368	The IB sys tem should print eac h non-pres cription, line level NDC quali fier, NDC number, un it of meas urement qu alifier an d the quan tity of th e medicati on deliver ed in FL 4 3 of the U B04 in a l eft justif ied format : Qualifie rNDC#UnitQ ualifierQu antity. (F or example : N4000390 06013ME1).
	369	The IB sys tem should print who le number Quantities with no d ecimal.
	370	The IB sys tem should print non -whole num ber Quanti ties with up to 3 de cimal plac es.
	371	The IB sys tem should no longer print non -prescript ion, line level NDC qualifier, NDC numbe r, unit of measureme nt qualifi er and the quantity of the med ication de livered in FL80 of t he UB04.
	372
	373	Process Pa yer ID – S tore HCCH Payer ID:
	374	The IB sys tem should be able t o accept a n inbound 277STAT me ssage from HCCH.
	375	The IB sys tem should be able t o process a 277STAT message an d attempt to update the EDI ID NUMBER – PROF [3.02 ] field or the EDI I D NUMBER – INST [3.0 4] field w ith any Pa yer IDs id entified b y the HCCH in the 27 7STAT tran saction.
	376	The IB sys tem should update th e EDI ID N UMBER – PR OF [3.02] field or E DI ID NUMB ER – INST [3.04] fie ld in the Insurance Company fi le [#36] w ith the va lues sent by the HCC H only if the field( s) is blan k.
	377
	378	Payer ID R eport:
	379	The IB sys tem should provide a ccess to a new “HCCH Payer ID Report” [I B HCCH PAY ER ID REPO RT] option (on the M CCR System Definitio n Menu) fo r tracking Payer ID (EDI ID NU MBER – PRO F [3.02] o r EDI ID N UMBER – IN ST [3.04]) updates t hat are a result of a 277STAT message.
	380	Upon selec ting the n ew report option, th e IB syste m should a llow for a n entry to specify a date rang e for whic h to searc h for syst em changes to the ED I ID NUMBE R – PROF [ 3.02] fiel d or EDI I D NUMBER – INST [3.0 4] field.
	381	The new HC CH Payer I D Report s hould prov ide the fo llowing da ta element s: insuran ce company name; add ress; Prof ID and/or Inst ID v alues that were upda ted; Prof ID and Ins t ID value s that the system di d not upda te and dat e of updat e or attem pted updat e.
	382	The new HC CH Payer I D Report w ill only s how one at tempt per day per In surance Co mpany per ID (Instit utional or Professio nal) unles s subseque nt attempt s involve a differen t ID value .
	383	Back-Out C riteria
	384	The projec t is cance led, the r equested c hanges imp lemented b y IB2.05 77 are no longer des ired by VA OI&T and the Integr ated Billi ng eBusine ss team, o r the patc h produces catastrop hic proble ms.
	385	Back-Out R isks
	386	Since the eBilling s oftware is tightly i ntegrated with exter nal system s, any att empt at a back-out s hould incl ude close consultati on with th e external trading p artners su ch as the Financial Services C enter (FSC ) and the Health Car e Clearing House (HC CH) to det ermine ris k.
	387	Authority for Back-O ut
	388	The order would come from: rel ease coord inator (pr oduct supp ort), port folio dire ctor and h ealth prod uct suppor t. This sh ould be do ne in cons ultation w ith the de velopment team and e xternal tr ading part ners such as FSC and the HCCH to determi ne the app ropriate c ourse of a ction. eBi lling 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 .
	389	Back-Out P rocedure
	390	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 their unique pro blems.
	391
	392	The IB2.0 577 patch contains the follow ing build components .
	393	Routines
	394	New Menu O ption
	395	Protocols
	396	Modificati ons to the following files:
	397	Insurance File [#36]
	398	IB Error F ile [#350. 8]
	399	IB Site Pa rameters F ile
	400	IB Non/Oth er VA Bill ing Provid er File
	401	IB Form Sk eleton Def inition Fi le
	402	IB Form Fi eld Conten t File
	403	Bill/Claim s File [#3 99]
	404	Data Dicti onary Chan ges
	405
	406	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.
	407
	408	Please con tact the E PMO team f or assista nce since this insta lled patch contains components in additi on to rout ines.
	409	Back-out V erificatio n Procedur e
	410	Successful back-out is confirm ed by veri fication t hat the ba ck-out pat ch was suc cessfully installed.
	411	Rollback P rocedure
	412	Rollback p ertains to data. The data that is affect ed by the installati on of IB2 .0577 are those fie lds that h ad their f ield lengt hs expande d.
	413	Rollback C onsiderati ons
	414	Not applic able.
	415	Rollback C riteria
	416	Not applic able.
	417	Rollback R isks
	418	Not applic able.
	419	Authority for Rollba ck
	420	Not applic able.
	421	Rollback P rocedure
	422	Not applic able.
	423	Rollback V erificatio n Procedur e
	424	Should it be decided to back-o ut IB2.0 577, a uti lity routi ne is avai lable to i dentify th e data tha t exceeds the restor ed field l engths. Th is utility will not fix/recove r any of t he data.
	425
	426	If a decis ion is mad e to back- out the lo nger field s, this ut ility will be includ ed with a future ver sion of th e patch if backed-ou t during I OC. If thi s is backe d-out post national release, t he utility will be p art of a w arranty pa tch which restores t he prior f ield lengt hs.