Produced by Araxis Merge on 3/2/2018 12:46:55 PM Central Standard 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.
# | Location | File | Last Modified |
---|---|---|---|
1 | PRCA_IB_EPAYMENTS_BUNDLE_2_0_V25.zip\PRCA_4_5_326 Documents | prca_ib_epayments_bundle_2_0_ig (track changes).doc | Fri Mar 2 17:47:02 2018 UTC |
2 | PRCA_IB_EPAYMENTS_BUNDLE_2_0_V25.zip\PRCA_4_5_326 Documents | prca_ib_epayments_bundle_2_0_ig (track changes).doc | Fri Mar 2 18:00:37 2018 UTC |
Description | Between Files 1 and 2 |
|
---|---|---|
Text Blocks | Lines | |
Unchanged | 7 | 1172 |
Changed | 6 | 12 |
Inserted | 0 | 0 |
Removed | 0 | 0 |
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 |
No regular expressions were active.
1 | Installati on, Back-o ut, and Ro llback Gui de Templat eMedical C are Collec tion Fund (MCCF) Ele ctronic Da ta Interch ange (EDI) Transacti on Applica tions Suit e (TAS) eP ayments Bu ild 2 & 3 | |
2 | Accounts R eceivable PRCA*4.5*3 21 | |
3 | Integrated Billing I B*2.0*596 | |
4 | Accounts R eceivable PRCA*4.5*3 21 | |
5 | Version 13 .0 | |
6 | Deployment , Installa tion, Back -Out, and Rollback G uide | |
7 | ||
8 | October Fe bruary 201 87 | |
9 | Department of Vetera ns Affairs | |
10 | Office of Informatio n and Tech nology (OI &T) | |
11 | Revision H istory | |
12 | DateVersio nDescripti onAuthorJu ly 20171.0 Initial Ve rsionDarle ne White & Chris Edk insOctober 20172.0In corporated the addit ional item s to this document a s the scop e of work (VistA enh ancements) increased when we c ombined Bu ild 2 with Build 3.D arlene Whi te & Fred AltmanDece mber 20173 .0Updated to reflect changes t o build as a result of IOC tes ting.Darle ne WhiteAr tifact Rat ionale | |
13 | 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. | |
14 | 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. | |
15 | Table of C ontents | |
16 | 11 | |
17 | Introducti on | |
18 | ||
19 | ||
20 | 11.1 | |
21 | Purpose | |
22 | ||
23 | ||
24 | 11.2 | |
25 | Dependenci es | |
26 | ||
27 | ||
28 | 11.3 | |
29 | Constraint s | |
30 | ||
31 | ||
32 | 12 | |
33 | Roles and Responsibi lities | |
34 | ||
35 | ||
36 | 23 | |
37 | Deployment | |
38 | ||
39 | ||
40 | 23.1 | |
41 | Timeline | |
42 | ||
43 | ||
44 | 23.2 | |
45 | Site Readi ness Asses sment | |
46 | ||
47 | ||
48 | 23.2.1 | |
49 | Deployment Topology (Targeted Architectu re) | |
50 | ||
51 | ||
52 | 33.2.2 | |
53 | Site Infor mation (Lo cations, D eployment Recipients ) | |
54 | ||
55 | ||
56 | 33.2.3 | |
57 | Site Prepa ration | |
58 | ||
59 | ||
60 | 33.3 | |
61 | Resources | |
62 | ||
63 | ||
64 | 33.3.1 | |
65 | Facility S pecifics | |
66 | ||
67 | ||
68 | 33.3.2 | |
69 | Hardware | |
70 | ||
71 | ||
72 | 33.3.3 | |
73 | Software | |
74 | ||
75 | ||
76 | 43.3.4 | |
77 | Communicat ions | |
78 | ||
79 | ||
80 | 43.3.4.1 | |
81 | Deployment /Installat ion/Back-O ut Checkli st | |
82 | ||
83 | ||
84 | 54 | |
85 | Installati on | |
86 | ||
87 | ||
88 | 54.1 | |
89 | Pre-instal lation and System Re quirements | |
90 | ||
91 | ||
92 | 54.2 | |
93 | Platform I nstallatio n and Prep aration | |
94 | ||
95 | ||
96 | 54.3 | |
97 | Download a nd Extract Files | |
98 | ||
99 | ||
100 | 64.4 | |
101 | Database C reation | |
102 | ||
103 | ||
104 | 64.5 | |
105 | Installati on Scripts | |
106 | ||
107 | ||
108 | 64.6 | |
109 | Cron Scrip ts | |
110 | ||
111 | ||
112 | 64.7 | |
113 | Access Req uirements and Skills Needed fo r the Inst allation | |
114 | ||
115 | ||
116 | 64.8 | |
117 | Installati on Procedu re | |
118 | ||
119 | ||
120 | 64.9 | |
121 | Installati on Verific ation Proc edure | |
122 | ||
123 | ||
124 | 64.10 | |
125 | System Con figuration | |
126 | ||
127 | ||
128 | 64.11 | |
129 | Database T uning | |
130 | ||
131 | ||
132 | 65 | |
133 | Back-Out P rocedure | |
134 | ||
135 | ||
136 | 75.1 | |
137 | Back-Out S trategy | |
138 | ||
139 | ||
140 | 75.2 | |
141 | Back-Out C onsiderati ons | |
142 | ||
143 | ||
144 | 75.2.1 | |
145 | Load Testi ng | |
146 | ||
147 | ||
148 | 75.2.2 | |
149 | User Accep tance Test ing | |
150 | ||
151 | ||
152 | 125.3 | |
153 | Back-Out C riteria | |
154 | ||
155 | ||
156 | 125.4 | |
157 | Back-Out R isks | |
158 | ||
159 | ||
160 | 125.5 | |
161 | Authority for Back-O ut | |
162 | ||
163 | ||
164 | 125.6 | |
165 | Back-Out P rocedure | |
166 | ||
167 | ||
168 | 135.7 | |
169 | Back-out V erificatio n Procedur e | |
170 | ||
171 | ||
172 | 136 | |
173 | Rollback P rocedure | |
174 | ||
175 | ||
176 | 136.1 | |
177 | Rollback C onsiderati ons | |
178 | ||
179 | ||
180 | 136.2 | |
181 | Rollback C riteria | |
182 | ||
183 | ||
184 | 136.3 | |
185 | Rollback R isks | |
186 | ||
187 | ||
188 | 136.4 | |
189 | Authority for Rollba ck | |
190 | ||
191 | ||
192 | 136.5 | |
193 | Rollback P rocedure | |
194 | ||
195 | ||
196 | 136.6 | |
197 | Rollback V erificatio n Procedur e | |
198 | ||
199 | ||
200 | 1 | |
201 | Introducti on | |
202 | 1 | |
203 | 1.1 | |
204 | Purpose | |
205 | 1 | |
206 | 1.2 | |
207 | Dependenci es | |
208 | 1 | |
209 | 1.3 | |
210 | Constraint s | |
211 | 1 | |
212 | 2 | |
213 | Roles and Responsibi lities | |
214 | 1 | |
215 | 3 | |
216 | Deployment | |
217 | 2 | |
218 | 3.1 | |
219 | Timeline | |
220 | 2 | |
221 | 3.2 | |
222 | Site Readi ness Asses sment | |
223 | 2 | |
224 | 3.2.1 | |
225 | Deployment Topology (Targeted Architectu re) | |
226 | 3 | |
227 | 3.2.2 | |
228 | Site Infor mation (Lo cations, D eployment Recipients ) | |
229 | 3 | |
230 | 3.2.3 | |
231 | Site Prepa ration | |
232 | 3 | |
233 | 3.3 | |
234 | Resources | |
235 | 3 | |
236 | 3.3.1 | |
237 | Facility S pecifics | |
238 | 3 | |
239 | 3.3.2 | |
240 | Hardware | |
241 | 3 | |
242 | 3.3.3 | |
243 | Software | |
244 | 4 | |
245 | 3.3.4 | |
246 | Communicat ions | |
247 | 4 | |
248 | 3.3.4.1 | |
249 | Deployment /Installat ion/Back-O ut Checkli st | |
250 | 4 | |
251 | 4 | |
252 | Installati on | |
253 | 5 | |
254 | 4.1 | |
255 | Pre-instal lation and System Re quirements | |
256 | 5 | |
257 | 4.2 | |
258 | Platform I nstallatio n and Prep aration | |
259 | 5 | |
260 | 4.3 | |
261 | Download a nd Extract Files | |
262 | 5 | |
263 | 4.4 | |
264 | Database C reation | |
265 | 6 | |
266 | 4.5 | |
267 | Installati on Scripts | |
268 | 6 | |
269 | 4.6 | |
270 | Cron Scrip ts | |
271 | 6 | |
272 | 4.7 | |
273 | Access Req uirements and Skills Needed fo r the Inst allation | |
274 | 6 | |
275 | 4.8 | |
276 | Installati on Procedu re | |
277 | 6 | |
278 | 4.9 | |
279 | Installati on Verific ation Proc edure | |
280 | 6 | |
281 | 4.10 | |
282 | System Con figuration | |
283 | 6 | |
284 | 4.11 | |
285 | Database T uning | |
286 | 6 | |
287 | 5 | |
288 | Back-Out P rocedure | |
289 | 7 | |
290 | 5.1 | |
291 | Back-Out S trategy | |
292 | 7 | |
293 | 5.2 | |
294 | Back-Out C onsiderati ons | |
295 | 7 | |
296 | 5.2.1 | |
297 | Load Testi ng | |
298 | 7 | |
299 | 5.2.2 | |
300 | User Accep tance Test ing | |
301 | 8 | |
302 | 5.3 | |
303 | Back-Out C riteria | |
304 | 10 | |
305 | 5.4 | |
306 | Back-Out R isks | |
307 | 10 | |
308 | 5.5 | |
309 | Authority for Back-O ut | |
310 | 10 | |
311 | 5.6 | |
312 | Back-Out P rocedure | |
313 | 10 | |
314 | 5.7 | |
315 | Back-out V erificatio n Procedur e | |
316 | 11 | |
317 | 6 | |
318 | Rollback P rocedure | |
319 | 11 | |
320 | 6.1 | |
321 | Rollback C onsiderati ons | |
322 | 11 | |
323 | 6.2 | |
324 | Rollback C riteria | |
325 | 11 | |
326 | 6.3 | |
327 | Rollback R isks | |
328 | 11 | |
329 | 6.4 | |
330 | Authority for Rollba ck | |
331 | 11 | |
332 | 6.5 | |
333 | Rollback P rocedure | |
334 | 11 | |
335 | 6.6 | |
336 | Rollback V erificatio n Procedur e | |
337 | 11 | |
338 | ||
339 | ||
340 | Table of T ables | |
341 | 1Table 1: Deployment , Installa tion, Back -out, and Rollback R oles and R esponsibil ities | |
342 | ||
343 | ||
344 | 3Table 2: Site Prepa ration | |
345 | ||
346 | ||
347 | 3Table 3: Facility-S pecific Fe atures | |
348 | ||
349 | ||
350 | 3Table 4: Hardware S pecificati ons | |
351 | ||
352 | ||
353 | 4Table 5: Software S pecificati ons | |
354 | ||
355 | ||
356 | 5Table 6: Deployment /Installat ion/Back-O ut Checkli st | |
357 | ||
358 | ||
359 | Table 1: D eployment, Installat ion, Back- out, and R ollback Ro les and Re sponsibili ties | |
360 | 1 | |
361 | Table 2: S ite Prepar ation | |
362 | 3 | |
363 | Table 3: F acility-Sp ecific Fea tures | |
364 | 3 | |
365 | Table 4: H ardware Sp ecificatio ns | |
366 | 3 | |
367 | Table 5: S oftware Sp ecificatio ns | |
368 | 4 | |
369 | Table 6: D eployment/ Installati on/Back-Ou t Checklis t | |
370 | 5 | |
371 | ||
372 | ||
373 | Introducti on | |
374 | This docum ent descri bes how to deploy an d install IB*2.0*596 and PRCA* 4.5*321 as well as h ow to back -out the p roduct and rollback to a previ ous versio n or data set. | |
375 | Purpose | |
376 | The purpos e of this plan is to provide a single, c ommon docu ment that describes how, when, where, an d to whom IB*2.0*596 and PRCA* 4.5*321 wi ll be depl oyed and i nstalled, as well as how the p atches are to be bac ked out an d rolled b ack, if ne cessary. T he plan al so identif ies resour ces, commu nications plan, and rollout sc hedule. Sp ecific ins tructions for instal lation, ba ck-out, an d rollback are inclu ded in thi s document . | |
377 | Dependenci es | |
378 | The follow ing patche s must be installed before IB* 2.0*596 an d PRCA*4.5 *321: | |
379 | IB*2.0*511 | |
380 | PRCA*4.5*2 20 | |
381 | PRCA*4.5*3 03317 | |
382 | PRCA*4.5*3 12 | |
383 | PRCA*4.5*3 18 | |
384 | PRCA*4.5*3 19 | |
385 | Constraint s | |
386 | This patch is intend ed for a f ully patch ed VistA s ystem. | |
387 | Roles and Responsibi lities | |
388 | Table 1: D eployment, Installat ion, Back- out, and R ollback Ro les and Re sponsibili ties | |
389 | IDTeamPhas e / RoleTa sksProject Phase (Se e Schedule )1VA OI&T, VA OI&T H ealth Prod uct Suppor t& PMO (Le idos)Deplo ymentPlan and schedu le deploym ent (inclu ding orche stration w ith vendor s)Planning 2Local VAM C and CPAC processes | |
390 | Deployment Determine and docume nt the rol es and res ponsibilit ies of tho se involve d in the d eployment. Planning3F ield Testi ng (Initia l Operatin g Capabili ty - IOC), Health Pr oduct Supp ort Testin g & VIP Re lease Agen t Approval Deploymen tTest for operationa l readines s Testing4 Health Pro duct Suppo rt and Fie ld Operati onsDeploym entExecute deploymen tDeploymen t5Individu al Veteran s Administ ration Med ical Cente rs (VAMCs) Installati onPlan and schedule installati on Deploym ent6 VIP R elease Age ntInstalla tionEnsure authority to operat e and that certifica te authori ty securit y document ation is i n placeDep loyment7N/ A for this patch as we are usi ng only th e existing VistA sys temInstall ationValid ate throug h facility POC to en sure that IT equipme nt has bee n accepted using ass et invento ry process esN/A8VA’s eBusiness teamInsta llationsCo ordinate t raining De ployment9V IP release Agent, He alth Produ ct Support & the dev elopment t eamBack-ou tConfirm a vailabilit y of back- out instru ctions and back-out strategy ( what are t he criteri a that tri gger a bac k-out) Dep loyment10N o changes to current process – we are us ing the ex isting Vis tA systemP ost Deploy mentHardwa re, Softwa re and Sys tem Suppor tWarrantyD eployment | |
391 | The deploy ment is pl anned as a national rollout. | |
392 | This secti on provide s the sche dule and m ilestones for the de ployment. | |
393 | Timeline | |
394 | The deploy ment and i nstallatio n is sched uled to ru n for 30 d ays, as de picted in the master deploymen t schedule | |
395 | . | |
396 | Site Readi ness Asses sment | |
397 | This secti on discuss es the loc ations tha t will rec eive the I B*2.0*596 and PRCA*4 .5*321 dep loyment. | |
398 | Deployment Topology (Targeted Architectu re) | |
399 | These patc hes, IB*2. 0*596 and PRCA*4.5*3 21 are to be nationa lly releas ed to all VAMCs. | |
400 | Site Infor mation (Lo cations, D eployment Recipients ) | |
401 | The test s ites for I OC testing are: TBD | |
402 | These site s will not be define d here unt il the sit es have si gned the M emorandum of Underst anding (MO Us) and te sting has completed as sometim es a site has to sto p testing prior to t he end of IOC. | |
403 | Upon natio nal releas e, all VAM Cs are exp ected to i nstall thi s patch by the compl iance date . | |
404 | Site Prepa ration | |
405 | The follow ing table describes preparatio n required by the si te prior t o deployme nt. | |
406 | Table 2: S ite Prepar ation | |
407 | Site/Other Problem/Ch ange Neede dFeatures to Adapt/M odify to N ew Product Actions/St epsOwnerN/ AN/AN/AN/A N/AResourc es | |
408 | Facility S pecifics | |
409 | The follow ing table lists faci lity-speci fic featur es require d for depl oyment. | |
410 | Table 3: F acility-Sp ecific Fea tures | |
411 | SiteSpace/ RoomFeatur es NeededO therN/AN/A N/AN/AHard ware | |
412 | The follow ing table describes hardware s pecificati ons requir ed at each site prio r to deplo yment. | |
413 | Table 4: H ardware Sp ecificatio ns | |
414 | Required H ardwareMod elVersionC onfigurati onManufact urerOtherE xisting Vi stA system N/AN/AN/AN /AN/APleas e see the Roles and Responsibi lities tab le in Sect ion 2 for details ab out who is responsib le for pre paring the site to m eet these hardware s pecificati ons. | |
415 | Software | |
416 | The follow ing table describes software s pecificati ons requir ed at each site prio r to deplo yment. | |
417 | Table 5: S oftware Sp ecificatio ns | |
418 | Required S oftwareMak eVersionCo nfiguratio nManufactu rerOtherFu lly patche d Accounts Receivabl e package within Vis tAN/A4.5N/ AN/AN/APRC A*4.5*220N /ANational ly release d versionN /AN/AN/APR CA*4.5*303 317N/ANati onally rel eased vers ionN/AN/AN /APRCA*4.5 *312318N/A Nationally released versionN/A N/AN/APRCA *4.5*31831 9N/ANation ally relea sed versio nN/AN/AN/A Fully patc hed Integr ated Billi ng package within Vi stAN/A2.0N /AN/AN/AIB *2.0*511N/ ANationall y released versionN/ AN/AN/APle ase see th e Roles an d Responsi bilities t able in Se ction 2 ab ove for de tails abou t who is r esponsible for prepa ring the s ite to mee t these so ftware spe cification s. | |
419 | Communicat ions | |
420 | The sites that are p articipati ng in fiel d testing (IOC) will use the “ Patch Trac king” mess age in Out look to co mmunicate with the e Payments e Business t eam, the d evelopers, and produ ct support personnel . | |
421 | Deployment /Installat ion/Back-O ut Checkli st | |
422 | The Releas e Manageme nt team wi ll deploy patches IB *2.0*596 a nd PRCA*4. 5*321, whi ch are tra cked in th e NPM in F orum, nati onally to all VAMCs. 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 the patch was insta lled in th e VistA pr oduction a t each sit e, and by whom. A re port can a lso be run to identi fy which s ites have not instal led the pa tch in the ir VistA p roduction system as of that mo ment in ti me. | |
423 | Therefore, this info rmation do es not nee d to be ma nually tra cked in th e chart be low. | |
424 | Table 6: D eployment/ Installati on/Back-Ou t Checklis t | |
425 | ActivityDa yTimeIndiv idual who completed taskDeploy N/AN/AN/AI nstallN/AN /AN/AInsta llation | |
426 | Pre-instal lation and System Re quirements | |
427 | IB*2.0*596 and PRCA* 4.5*321, p atches to the existi ng VistA I ntegrated Billing 2. 0 and Acco unts Recei vable 4.5 packages, are instal lable on a fully pat ched M(UMP S) VistA s ystem and operate on the top o f the Vist A environm ent provid ed by the VistA infr astructure packages. The latte r provides utilities which com municate w ith the un derlying o perating s ystem and hardware, thereby pr oviding In tegrated B illing and Accounts Receivable independe nce from v ariations in hardwar e and oper ating syst em. | |
428 | Platform I nstallatio n and Prep aration | |
429 | Refer to I B*2.0*596 and PRCA*4 .5*321 doc umentation on the Na tional Pat ch Module (NPM) on F orum for t he detaile d installa tion instr uctions. T hese instr uctions wo uld includ e any pre- installati on steps i f applicab le. | |
430 | Download a nd Extract Files | |
431 | Refer to I B*2.0*596 and PRCA*4 .5*321 doc umentation on the NP M to find the locati on of rela ted docume ntation th at can be downloaded . IB*2.0*5 96 and PRC A*4.5*321 will be di stributed via host f ile PRCA_I B_EPAYMENT S_BUNDLE_2 _0.KID. | |
432 | Sites can retrieve V istA softw are from d ownload. DNS . DNS . This tra nsmits the file from the first available server. Sites may also selec t to retri eve this f ile direct ly from a specific s erver. | |
433 | Sites may retrieve s oftware di rectly usi ng Secure File Trans fer Protoc ol (SFTP) from the A NONYMOUS.S OFTWARE di rectory at the follo wing OI Fi eld Office s: | |
434 | Alb any | |
435 | ||
436 | DNS . URL | |
437 | Hin es | |
438 | ||
439 | DNS .U RL | |
440 | Sal t Lake Cit y | |
441 | .URL | |
442 | The PRCA_I B_EPAYMENT S_BUNDLE_2 _0.KID hos t file is located in the anony mous.softw are direct ory. Use t he America n Standard Code for Informatio n Intercha nge (ASCII ) Mode whe n download ing the fi le. | |
443 | Database C reation | |
444 | IB*2.0*596 and PRCA* 4.5*321 mo dify the V istA datab ase. All c hanges can be found on the NPM documenta tion for t hese patch es. | |
445 | Installati on Scripts | |
446 | No install ation scri pts are ne eded for I B*2.0*596 and PRCA*4 .5*321 ins tallation. | |
447 | Cron Scrip ts | |
448 | No Cron sc ripts are needed for IB*2.0*59 6 and PRCA *4.5*321 i nstallatio n. | |
449 | Access Req uirements and Skills Needed fo r the Inst allation | |
450 | The follow ing staff will need access to the host f ile PRCA_I B_EPAYMENT S_BUNDLE_2 _0.KID con taining th e IB*2.0*5 96 and PRC A*4.5*321 patches. T he softwar e is to be installed by the si te’s or re gion’s des ignated: V A OI&T IT OPERATIONS SERVICE, Enterprise Service L ines, Vist A Applicat ions Divis ion | |
451 | . | |
452 | Installati on Procedu re | |
453 | Refer to I B*2.0*596 and PRCA*4 .5*321 doc umentation on the NP M for the detailed i nstallatio n instruct ions. | |
454 | Installati on Verific ation Proc edure | |
455 | Refer to I B*2.0*596 and PRCA*4 .5*321 doc umentation on the NP M for the detailed i nstallatio n instruct ions. Thes e instruct ions would include a ny post in stallation steps if applicable . | |
456 | System Co nfiguratio n | |
457 | No system configurat ion change s are requ ired for t his patch. | |
458 | Database Tuning | |
459 | No reconfi guration o f the Vist A database , memory a llocations or other resources is necessa ry. | |
460 | Back-Out P rocedure | |
461 | 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 . | |
462 | Back-Out S trategy | |
463 | Although i t is unlik ely, due t o care in collecting , elaborat ing, and d esigning a pproved us er stories , followed by multip le testing stages (D eveloper U nit Testin g, Compone nt Integra tion Testi ng, SQA Te sting, and User Acce ptance Tes ting), a b ack-out de cision due to major issues wit h this pat ch could o ccur. A de cision to back out c ould be ma de during site Mirro r Testing, Site Prod uction Tes ting or af ter Nation al Release to the fi eld (VAMCs ). The bes t strategy decision is depende nt on the stage of t esting dur ing which the decisi on is made . | |
464 | 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. | |
465 | If the def ect(s) wer e not disc overed unt il after n ational re lease but during the designate d support period, a new patch will be en tered into the Natio nal Patch Module on Forum and go through all the n ecessary m ilestone r eviews etc ., as a pa tch for a patch. It is up to V A OI&T and product s upport whe ther this new patch would be d efined as an emergen cy patch o r not. Thi s new patc h could be used to a ddress spe cific issu es pertain ing to the original patch or c ould be us ed to rest ore the bu ild compon ents to th eir origin al pre-pat ch conditi on. | |
466 | After the support pe riod, the VistA Main tenance Pr ogram woul d produce the new pa tch, eithe r to corre ct the def ective com ponents or to back-o ut the pat ch. | |
467 | Back-Out C onsiderati ons | |
468 | It is nece ssary to d etermine i f a wholes ale back-o ut of the patches IB *2.0*596 a nd PRCA*4. 5*321 are needed or if a bette r course o f action i s to corre ct through a new ver sion of th e patch (i f prior to national release) o r through a subseque nt patch a imed at sp ecific are as modifie d or affec ted by the original patch (aft er nationa l release) . A wholes ale back-o ut of the patch will still req uire a new version ( if prior t o national release) or a subse quent patc h (after n ational re lease). If the back- out is pos t-release of patches IB*2.0*59 6 and PRCA *4.5*321, these patc hes should be assign ed status of “Entere d in Error ” in Forum ’s NPM. | |
469 | Load Testi ng | |
470 | 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. | |
471 | User Accep tance Test ing | |
472 | Daily Acti vity Repor t Enhancem ents [RCDP E EDI LOCK BOX ACT RE PORT] | |
473 | The Matche d Payment amount pos ted line w as removed from the daily and final tota ls. | |
474 | The report header wi ll display selected Division n umbers ins tead of se lected div ision name s. | |
475 | In detail mode, the report wil l page bre ak on each daily tot al, on the final tot al and whe n an Elect ronic Fund s Transfer (EFT) dep osit canno t be fully displayed on the pa ge. | |
476 | The report will no l onger be s ent via em ail to the mail grou p RCDPE PA YMENTS as part of th e nightly process. | |
477 | A new filt er was add ed to allo w the user to only s elect EFTs with debi t vouchers . | |
478 | A new debi t column w as added t o the repo rt to indi cate which EFTs have debit vou chers. | |
479 | The daily and final totals wil l now disp lay the nu mber of EF Ts with de bit vouche rs and the total amo unt of tho se EFTs. | |
480 | Receipt Co mment Hist ory | |
481 | A comment is now req uired when a clerk p uts funds into suspe nse. The following areas are affected: | |
482 | ERA Workli st [RCDPE EDI LOCKBO X WORKLIST ] Scratchp ad Split/E dit action | |
483 | Auto-Post Awaiting R esolution [RCDPE APA R] (APAR W orklist) S cratchpad Split/Edit action | |
484 | Link Payme nt to Acco unt [RCDP LINK PAYME NT TO ACCO UNT] workl ist in the LP and CS actions | |
485 | The Clerk will have the option of select ing a 'sta ndard' com ment selec ted from a pre-defin ed list, o r entering a free te xt comment that is a t least 3 characters long. | |
486 | The user w ho entered the comme nt and the date/time it was en tered will now be ca ptured by the system . | |
487 | When the c omment is displayed in the ERA Worklist Scratchpad or the AP AR scratch pad, the s ystem will now also display th e user who entered t he comment and the d ate/time i t was ente red. | |
488 | The entire comment h istory wil l be displ ayed in th e Summary SF215 Repo rt [RCDP S UMMARY 215 REPORT] w hen this r eport is r un in deta il mode. | |
489 | The entire comment h istory wil l also be displayed in the Lin k Payment Tracking R eport [RCD PE SUSPENS E AUDIT RE PORT]. | |
490 | Correction s to the E FT Transac tion Audit Report | |
491 | [RCD PE EFT TRA NSACTION A UD REP] | |
492 | The softwa re has bee n modified to fix a bug when o ld cash re ceipts (CR ) are used in calcul ations for the repor t. | |
493 | Corrected EEOB Attac hment to C laims | |
494 | The softwa re has bee n modified such that ERA Workl ist and AP AR will au tomaticall y move an Electronic Explanati on of Bene fits (EEOB ) when a l ine is spl it/edited when possi ble. The a utomatic m oving of a n EEOB wil l follow t he same ru les as the existing EEOB Mo ve/Copy/Re move [RCDP E EEOB MOV E/COPY/REM OVE] menu option. | |
495 | The automa tic update will occu r at recei pt creatio n in the P RCA nightl y auto-pos t job (for APAR chan ges) or at receipt c reation fo r the ERA Worklist. | |
496 | Details of the move/ copy/delet e transact ions and j ustificati on text ma y be viewe d in the E EOB Move/C opy/Remove Audit Rep ort [RCDPE EEOB MOVE /COPY/RMOV E RPT] opt ion and ar e also dis played in Third Part y Joint In quiry [IBJ THIRD PAR TY JOINT I NQUIRY] (T PJI) withi n the acti on Account Profile f ollowed by the actio n Comment History. | |
497 | EFT edits in Receipt Processin g [RCDP RE CEIPT PROC ESSING] | |
498 | The sof tware was modified s uch that: | |
499 | Users who have the R CDPEPP UNM ATCH EFT s ecurity ke y may chan ge the TYP E OF PAYME NT from CH ECK/MO PAY MENT to ED I LOCKBOX on receipt s that hav e pre-exis ting lines and allow the clerk to add/at tach a new EFT to th e receipt. | |
500 | Users who have the R CDPEPP UNM ATCH EFT s ecurity ke y may chan ge the EFT number on receipts when the T YPE OF PAY MENT equal s 'EDI LOC KBOX'. | |
501 | When the E FT number is changed on receip ts with TY PE OR PAYM ENT equals EDI LOCKB OX, the EF T that was removed i s unmatche d and appe ars on the EFT Unmat ched Aging report so it can be matched t o a new ER A. | |
502 | The header of the Re ceipt Proc essing wor klist has been modif ied to inc lude the d isplay of the ERA nu mber, ERA Total, EFT Number an d the EFT Total of t he associa ted deposi t. | |
503 | Two additi onal promp ts were ad ded to the Entered O nline acti on of the Receipt Pr ocessing w orklist. The user w ill nowt b e asked to confirm t he EFT fun ds have be en entered into the 8NZZ accou nt and wil l also be asked to e nter the F MS Referen ce #Number . | |
504 | Payer Name Display a nd Selecti on issues when the P ayer Name is greater than 30 c haracters. | |
505 | The 835 CA RC Data Re port [RCDP E CARC COD E PAYER RE PORT] now allows pay ers with n ames that are longer than 30 c haracters to be sele cted and d isplayed o n the repo rt. | |
506 | The EFT/ER A Trending Report [R CDPE EFT-E RA TRENDIN G REPORT] now allows payers wi th names t hat are lo nger than 30 charact ers to be selected a nd display ed on the report. | |
507 | The Provid er Level A djustments Report [R CDPE PROVI DER LVL AD J REPORT] now allows payers wi th names t hat are lo nger than 30 charact ers to be selected a nd display ed on the report. | |
508 | The ERA Un matched Ag ing Report [RCDPE ER A AGING RE PORT] now allows pay ers with n ames that are longer than 30 c haracters to be sele cted and d isplayed o n the repo rt. | |
509 | Move EEOBs to Claims with Paym ents linke d from Sus pense | |
510 | The Lin k Payment option wil l be modif ied such t hat: | |
511 | When the u ser enters the assoc iated Elec tronic Rem ittance Ad vice (ERA) , the syst em will au tomaticall y find the associate d EEOB and prompt th e user to attach it to the cla im. | |
512 | Only Poste d EEOBs wi ll be disp layed to a llow the u ser to att ach it to the claim. | |
513 | When pProm pting the user to at tach a pos ted EEOB t o the clai m, the sys tem will d isplay the Trace Num ber, Total Amount Pa id, Remove d By user and the Ju stificatio n comment. | |
514 | All restor ed EEOBs w ill appear on the EE OB Move/Co py/Remove Audit Repo rt [RCDPE EEOB MOVE/ COPY/RMOVE RPT]. | |
515 | The menu o ption Move ERA Total to Suspen se [RCDPE MOVE ERA T O SUSPENSE ] was remo ved from t he system. | |
516 | When manua lly creati ng a new r eceipt, he lp text wa s added to the 'PATI ENT NAME O R BILL NUM BER' promp t. | |
517 | The Refres h Scratch Pad action was remov ed from th e Auto-Pos t Awaiting Resolutio n APAR Wor klist. | |
518 | Added Sor t options to the Aut o-Post Awa iting Reso lution (AP AR) Workli st. | |
519 | Added the ability to sort the APAR workl ist by Dat e Created, Payer Nam e, APAR Re ason, Post ed Amount and Unpost ed Amount. If the u ser select s to sort by Date Cr eated, the y are then prompted to display the ERAs in Ascendi ng or Desc ending ord er. If th ey select to sort by Posted or Unposted Amount, th ey are the n prompted to displa y the ERAs in lowest to highes t or highe st to lowe st order. | |
520 | A Date Cre ated Colum n was adde d to the f ar right o f the body of the AP AR worklis t. Note t his column is past t he 80 char acter marg in width s o the user will have to use th eir right arrow key to scroll the displa y if they want to se e the Date Created. | |
521 | EDI Lockb ox 3rd Par ty Excepti ons workli st | |
522 | If a pharm acy claim had an ECM E rejected claim lin e followed by a data exception on a subs equent cla im line, the, the d isplay of the claim line data was incorr ect. This was fixed such that the corre ct claim l ine data i s displaye d for the claim. | |
523 | New Ident ify Payers option wa s added to the EDI L ockbox (eE Payments) menu. | |
524 | The Identi fy Payers menu optio n was adde d as the l ast displa yed option on the ED I Lockbox (eEPayment s) menu. | |
525 | This new o ption disp lay a work list that allows use rs who pos sess the n ew securit y key RCDP E D A N E S
|
|
526 | Identifyin g payers a s Pharmacy and/or Tr icare paye rs will en able futur e sorting/ filtering enhancemen t for Phar macy and T ricare pay ers on var ious repor ts and wor klists. | |
527 | Additional AR Site P arameter s ettings fo r auto-aud iting pape rEDI medic al and pha rmacy clai ms. | |
528 | Prior to t his enhanc ement, onl y electron icpaper me dical and pharmacy c laims coul d be auto- audited. | |
529 | Two new pr ompts ‘Ena ble Auto-A udit for M edical Pap er Bills’ and ‘Enabl e Auto-Aud it for Pha rmacy Pape r Bills’ w ere added. | |
530 | The new si te paramet ers were a re maintai ned throug h the EDI Lockbox Pa rameters [ RCDPE EDI LOCKBOX PA RAMETERS] menu optio n. | |
531 | Changes we re made to the ePaym ents auto- audit nigh tly proces s to auto- audit pape r medical and pharma cy claims based upon the new s etting val ues of the se two new fields. | |
532 | These new site param eter field s have als o been add ed to the EDI Lockbo x Paramete rs Report [RCDPE SIT E PARAMETE R REPORT]. | |
533 | Change to the maxim um allowed values of two EDI L ockbox Par amaters. | |
534 | The maximu m allowed valued of the ‘Numbe r of Days (AGE) of U nposted Me dical EFTs to Preven t Posting’ was decre ased to 60 days. P reviously the maximu m value wa s 99 days. | |
535 | The maximu m allowed valued of the ‘Numbe r of Days (AGE) of U nposted Ph armacy EFT s to Preve nt Posting ’ was decr eased to 3 65 days. Previousl y the maxi mum value was 999 da ys. | |
536 | Auto-Posti ng of manu ally match ed ERAs/EF Ts in the ePayments nightly pr ocess | |
537 | Prior to t his enhanc ement, ERA s and EFTs that were manually matched wo uld not au to-post du ring the n ightly pro cess. Onl y ERAs wit h a paymen t type ACH were auto -post cand idates. N ow ERAs wi th a payme nt type of CHK are a lso auto-p ost candid ates. | |
538 | The manual match act ion on the ERA Workl ist and th e Manual M atch EFT-E RA menu op tion were enhanced t o allow ER As with a payment ty pe of CHK to be be m arked for auto-posti ng. | |
539 | Unbalanced ERAs that were manu ally marke d for auto post will not auto post. The se can be found on t he ERA Wor klist for user actio n. | |
540 | Prevent m anual and auto-match ing of any claims th at have bi lling reje cts on the Claims St atus Await ing Resolu tion (CSA) worklist. | |
541 | Any claims that have billing r ejects on the CSA wi ll not be auto-audit ed in the nightly pr ocess. | |
542 | Users will be preven ted from m anually au diting any claims th at have bi lling reje cts on the CSA using the Audit Setup New Accounts Receivable option. | |
543 | New filte rs, sorts and workli st option added to t he List of Receipts Report. | |
544 | Added the ability to sort the Lists of R eceipts re port by Da te Opened, FMS Statu s or Type of Payment . | |
545 | Added the ability to filter th e report b y FMS Stat us. If th e user cho oses to fi lter by FM S Status, they will be prompte d to enter the FMS S tatus(es) to display on the re port. | |
546 | Added the ability to filter th e report b y Type of Payment. If the use r chooses to filter by Type of Payment, they will be prompte d to enter the Type of Payment (s) to be displayed on the rep ort. | |
547 | Added the option to display th e report i n a workli st that al lows the u ser to sel ect a rece ipt and pe rform the Process Re ceipt acti on. | |
548 | New filte rs added t o the ERA Worklist | |
549 | A new filt er was add ed to the ERA Workli st to filt er ERAs by Zero Doll ar, Paymen t or Both. If the us er selects the Zero Dollar fil ter, only ERAs with a Total Am ount Paid of zero wi ll be disp layed in t he worklis t. Ift th e user sel ects the P ayment fil ter, all E RAs with a Total Amo unt Paid w ill be ski pped. | |
550 | The curren t filter ‘ Medical, P harmacy or Both’ was amended t o ‘Medical , Pharmacy , Tricare or All’. If the Tri care filte r is selec ted, only ERAs with a payer id entified a s a Tricar e payer in the Payer Exclusion file will be displa yed. | |
551 | Allow ERAs matched t o an EFTA with a rec eipt statu s of ‘ON-L INE’ to be auto-post ed and/or processed in the ERA Worklist. | |
552 | Prior to t his enhanc ement, the ePayments nightly a uto-post p rocess wou ld skiptsk ip ERAs th at were ma tched to a n EFT with a receipt status of ‘ON-LINE’ . These ER As will no w auto-pos t. | |
553 | Prior to t his enhanc ement, the Receipt P rocessing action off of the ER A worklist scratch p ad was dis abled for ERAs that were match ed to an E FT with a receipt st atus of ‘O N-LINE’. T his action will now be enabled . | |
554 | Back-Out Criteria | |
555 | The projec t is cance led or the requested changes i mplemented by IB*2.0 *596 and P RCA*4.5*32 1 are no l onger desi red by VA OI&T and t he ePaymen ts eBusine ss team, o r the patc h produces catastrop hic proble ms. | |
556 | Back-Out R isks | |
557 | Since the ePayments 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), the He alth Care Clearing H ouse (HCCH ), the VA 3rd Party Lockbox ba nk, and th e Financia l Manageme nt System (FMS) to d etermine r isk. | |
558 | Authority for Back-O ut | |
559 | The order would come jointly f rom: the r elease coo rdinator ( product su pport), po rtfolio di rector, an d health p roduct sup port. This should be done in c onsultatio n with the developme nt team an d external trading p artners su ch as FSC, the HCCH, VA 3rd Pa rty Lockbo x bank, an d the FMS to determi ne the app ropriate c ourse of a ction. ePa yments is tightly in tegrated w ith these external p artners an d a back-o ut of the patch shou ld not be a standalo ne decisio n. | |
560 | Back-Out P rocedure | |
561 | 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. | |
562 | The IB*2.0 *596 and P RCA*4.5*32 1 patches contain th e followin g build co mponents. | |
563 | Data Dicti onary Chan ges | |
564 | Help Frame | |
565 | Options | |
566 | Parameters | |
567 | Protocols | |
568 | Routines | |
569 | Security K eys | |
570 | Templates | |
571 | 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. | |
572 | Please con tact the E PMO team f or assista nce since this insta lled patch contains components in additi on to rout ines. | |
573 | Back-out V erificatio n Procedur e | |
574 | Successful back-out is confirm ed by veri fication t hat the ba ck-out pat ch was suc cessfully installed. | |
575 | Rollback P rocedure | |
576 | Rollback p ertains to data. IB* 2.0*596 an d Patch PR CA*4.5*321 do impact the data in the Int egrated Bi lling and Accounts R eceivable packages. Therefore, to roll b ack the pa tches one will need to install new patch es to roll back the database c hanges and restore t he system back to it s prior st ate. In th e case whe re a rollb ack is nee ded, refer to the Ba ck-Out pro cedures de tailed els ewhere wit hin this d ocument. | |
577 | Rollback C onsiderati ons | |
578 | Not applic able. | |
579 | Rollback C riteria | |
580 | Not applic able. | |
581 | Rollback R isks | |
582 | Not applic able. | |
583 | Authority for Rollba ck | |
584 | Not applic able. | |
585 | Rollback P rocedure | |
586 | Not applic able. | |
587 | Rollback V erificatio n Procedur e | |
588 | Not applic able. | |
589 | Template R evision Hi story | |
590 | DateVersio nDescripti onAuthorMa rch 20162. 2Changed t he title f rom Instal lation, Ba ck-Out, an d Rollback Guide to Deployment and Insta llation Gu ide, with the unders tanding th at Back-Ou t and Roll back belon g with Ins tallation. VIP TeamF ebruary 20 162.1Chang ed title f rom Instal lation, Ba ck-Out, an d Rollback Plan to I nstallatio n, Back-Ou t, and Rol lback Guid e as recom mended by OI&T Docum entation S tandards C ommitteeOI &T Documen tation Sta ndards Com mitteeDece mber 20152 .0The OI&T Documenta tion Stand ards Commi ttee merge d the exis ting “Inst allation, Back-Out, Rollback P lan” templ ate with t he content requireme nts in the OI&T End- user Docum entation S tandards f or a more comprehens ive Instal lation Pla n.OI&T Doc umentation Standards Committee February 2 0151.0Init ial DraftL ifecycle a nd Release Managemen t� Project schedule (right cli ck and sel ect open h yperlink t o access) � HYPERLIN K "http:// URL /pm/hape/i pt_5010/ED I_Portfoli o/TAS%20In terim%20Re pository/M CCF%20TAS% 20Schedule .zip" \o " http:// URL /pm/hape/i pt_5010/ED I_Portfoli o/TAS%20In terim%20Re pository/M CCF%20TAS% 20Schedule .zip" �htt p:// URL /pm/hape/i pt_5010/ED I_Portfoli o/TAS%20In terim%20Re pository/M CCF%20TAS% 20Schedule .zip� | |
591 | � “Enterpr ise servic e lines, V AD” for sh ort. Forme rly known as the IRM (Informat ion Resour ces Manage ment) or I T support. | |
592 |
Araxis Merge (but not the data content of this report) is Copyright © 1993-2016 Araxis Ltd (www.araxis.com). All rights reserved.